• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root SBF'D back to 2.2 (now what??)

So no alarm clock for apex? I use mine to get up every morning (4am). Ughh. Nothing. Sure how to run a script ...... anything else missing like camera, etc.... thanks again for the guidance!

Apex 1.3.1 has an alarm clock. Did not need a script to add it... :)

-bob
 
I had to use the script to get the blur version with 1.3.0. Maybe 1.3.1 is different.

The scripts are used if you want to switch the aosp or blur versions.
 
okay. today i thinkl i'll get onto ROM's. Firstly, i need to Z4 my way back in charge of this device.

after that, i wasnt to delete all my black glassy backups (best way??)
then de-odex(best way?)
then back up a stock nanroid(best way?)

....then apex and onward......
 
Don't need to deodex unless you plan on running stock rom with themes. Roms are already deodexed.

Installing rom manager is a good way to manage your backups. You can create, rename, delete from there easily.

After rooting, make sure you have recovery installed. Tap the top button, it should say "success", then tap the bottom to make sure it boots into recovery. Vol up/dn move cursor, camera button does the action, back goes back. Reboot into the phone.

Open rom manager. Should be able to see old backups under "manage" and delete them. Then you can create a backup, but don't use spaces. Mine look like this:

apex_rom_manager.jpg


Paid version of RM lets you download roms/themes directly to your phone. Found a neat theme that way.

If you have trouble rooting (takes a long time), you can speed that up by removing/inserting repeatedly the battery.
 
running Z4 now......

rooted in four minutes (with reboot thru recovery)

d/l'ing rom manager......

gonna look for the back-ups ive created previously....
 
I'm sorry if I'm taking this OT, but I have been trying to get this done on my phone for over three hours and have not been able to. I've tried using RSD Lite and flashing all .SBF files recommended here and oon other sites and I always get the following error:

Failed flashing process. Phone [0000]: Phone is not compatible with multi-interface super-file. (0X703B); Phone connected.

I have a Moto X that's been rooted and deodexed and all I'm looking to do is to clear it back to Verizon fresh and start again from there. Any help will be appreciated.

Thanks.
 
well, it's a start, eh???

Very nice start, and a screenshot to boot. I'm impressed. :D Next need to get an adblock app installed.

I'm sorry if I'm taking this OT, but I have been trying to get this done on my phone for over three hours and have not been able to. I've tried using RSD Lite and flashing all .SBF files recommended here and oon other sites and I always get the following error:

Failed flashing process. Phone [0000]: Phone is not compatible with multi-interface super-file. (0X703B); Phone connected.

I have a Moto X that's been rooted and deodexed and all I'm looking to do is to clear it back to Verizon fresh and start again from there. Any help will be appreciated.

Thanks.

Make sure you have at least RSD Lite 4.8 (or 4.9) and the latest Motorola drivers. You can get those here: http://androidforums.com/droid-x-all-things-root/232866-sbfing-back-2-2-a.html

If that doesn't work, you can try this: http://androidforums.com/droid-x-all-things-root/254605-update-2-3-340-easily.html

I haven't read that thread for a day or so, but it sounded good when I browsed it days ago.
 
Very nice start, and a screenshot to boot. I'm impressed. :D Next need to get an adblock app installed.

yea..... i have the overclock adblock and the app adblock, but they needed to be reminded to work, i guess.....

Im now trying to make a de-odexed backup for just using themes now.... any idea where to go?

-SMS
 
First, thanks for the help. It worked. But... and this is the part I hate, I think I messed up somewhere afterwards. I perfomed the flash and all worked fine but after installing the OTA update from VZN I noticed my phone wasn't acting so snappy. So I tried to flash the file in your link and that totally screwed me to the point that I am not able to do anything with my phone. Essentially, I've bricked it. So what would be my very next step to undo the mess that I have made?

Edit: Just extra info, the bootloader screen in which I'm stuck shows the following:

MEM_MAP Blank

I went through the steps again with the file named VRZ_MB810_2.3.15_1FF_01.sbf and RSD Lite showed all was a success but the phone remains in its current state.


Thanks again.




Very nice start, and a screenshot to boot. I'm impressed. :D Next need to get an adblock app installed.



Make sure you have at least RSD Lite 4.8 (or 4.9) and the latest Motorola drivers. You can get those here: http://androidforums.com/droid-x-all-things-root/232866-sbfing-back-2-2-a.html

If that doesn't work, you can try this: http://androidforums.com/droid-x-all-things-root/254605-update-2-3-340-easily.html

I haven't read that thread for a day or so, but it sounded good when I browsed it days ago.
 
First, thanks for the help. It worked. But... and this is the part I hate, I think I messed up somewhere afterwards. I perfomed the flash and all worked fine but after installing the OTA update from VZN I noticed my phone wasn't acting so snappy. So I tried to flash the file in your link and that totally screwed me to the point that I am not able to do anything with my phone. Essentially, I've bricked it. So what would be my very next step to undo the mess that I have made?

Edit: Just extra info, the bootloader screen in which I'm stuck shows the following:

MEM_MAP Blank

I went through the steps again with the file named VRZ_MB810_2.3.15_1FF_01.sbf and RSD Lite showed all was a success but the phone remains in its current state.


Thanks again.

Nobody's phone is peppy after an update. It takes a while for things to smooth out.

Flashing backwards with 2.3.15 from 2.3.340 is a big no-no and it's possible you might just have a brick. I hope your phone is nearly fully charged, b/c I believe it does not charge when in the bootloader.

You should try to flash with the full sbf 2.3.320. If that works, and the phone boots, then flash with .340 (system-only). Only a full-sbf stands a chance of fixing you now.

If you can't get the phone to boot, you've exceeded my experience and you'll need advice from others.
 
yea..... i have the overclock adblock and the app adblock, but they needed to be reminded to work, i guess.....

Im now trying to make a de-odexed backup for just using themes now.... any idea where to go?

-SMS

Try this link: http://androidforums.com/droid-x-al...ly-deodex-2-3-340-without-installing-rom.html

That's the same way I deodexed before installing a rom.

EDIT: Just see you already have posted in that thread.

BTW, it's a LOT easier to just install a blurry rom, like Apex or Rubix Blurry 2.3.20.
 
I was afraid of that kind of a reply. OK, so could you point me out to the SBF file you think I should DL to try to flash? Dealing with this I've come across so many different SBF files that i'm a bit confused and I want to give this the best chance possible.

Thanks a ton for all your help.




Nobody's phone is peppy after an update. It takes a while for things to smooth out.

Flashing backwards with 2.3.15 from 2.3.340 is a big no-no and it's possible you might just have a brick. I hope your phone is nearly fully charged, b/c I believe it does not charge when in the bootloader.

You should try to flash with the full sbf 2.3.320. If that works, and the phone boots, then flash with .340 (system-only). Only a full-sbf stands a chance of fixing you now.

If you can't get the phone to boot, you've exceeded my experience and you'll need advice from others.
 
Sorry, it took awhile to find it.

Try here: Droid X: 2.3.32 Full SBF

There really are only a couple.

2.3.15
2.3.32 or 2.3.320 or .320 (same thing)
and 2.3.340 or .340

They also could go by android versions like 2.2.1 or 2.2, but I find those numbers vague and confusing.

If you went back far enough there would have been some Froyo leaks, but that would have been late summer.
 
I DLed the file and tried. It didn't even run and I got a failed message right away. I can assume that I have killed my phone and will visit VZN tomorrow to see what my options are. As this is my first time dealing with this, does anyone know what I might be facing at the VZN store tomorrow?

Thanks for the help it was completely appreciated.





Sorry, it took awhile to find it.

Try here: Droid X: 2.3.32 Full SBF

There really are only a couple.

2.3.15
2.3.32 or 2.3.320 or .320 (same thing)
and 2.3.340 or .340

They also could go by android versions like 2.2.1 or 2.2, but I find those numbers vague and confusing.

If you went back far enough there would have been some Froyo leaks, but that would have been late summer.
 
Don't give up yet. See this post: bricked x because of 2.2 downgrade

I don't know what it means exactly, but appently the sbf file you use depends on what boot loader you have.

Trust me, the people who know their stuff here (and I don't mean me), can help you more than your local VZ store so give it another day yet.
 
You, my friend, are a complete savior! I read the post about renaming the .SBF file and THAT did the trick! I have my phone back!
I totally and completely appreciate your time and effort and cannot thank you enough!

THANK YOU!!!!!!!



Don't give up yet. See this post: bricked x because of 2.2 downgrade

I don't know what it means exactly, but appently the sbf file you use depends on what boot loader you have.

Trust me, the people who know their stuff here (and I don't mean me), can help you more than your local VZ store so give it another day yet.
 
A couple of things. somehow my wife made my phone lose LPP and I could only load the moto launch homescreen (on which I had deleted everything 'cause I didin't want duplicate apps running), so I had to recover using bootstrap to a prior backup - IT WORKED, YAY!. So, now I know I can do that!. (A HUGE step for me). I now want to see if I can sbf if necessary. I can not get RSDLite 4.9 to show my phone. How do I know it it's connected properly? I've got the usb debugging thingy activated and I'm using the USB Mass Storage connection thingy. What am I missing?
 
A couple of things. somehow my wife made my phone lose LPP and I could only load the moto launch homescreen (on which I had deleted everything 'cause I didin't want duplicate apps running), so I had to recover using bootstrap to a prior backup - IT WORKED, YAY!. So, now I know I can do that!. (A HUGE step for me). I now want to see if I can sbf if necessary. I can not get RSDLite 4.9 to show my phone. How do I know it it's connected properly? I've got the usb debugging thingy activated and I'm using the USB Mass Storage connection thingy. What am I missing?


1) make certain to have the correct drivers....

2) i had mine found NOT selecting USBMS setting (try the other settings??)
 
I'm using motoconnect 4.8.0, just downloaded again. methinks that is the most current?
I;ve tried all four methods, pc mode, charge only, media sync and mass storage. disconnected phone, then reconnected, closed RSD then, re-opened.......
nada.
 
I'm using motoconnect 4.8.0, just downloaded again. methinks that is the most current?
I;ve tried all four methods, pc mode, charge only, media sync and mass storage. disconnected phone, then reconnected, closed RSD then, re-opened.......
nada.

shoot. Im over my head here then. did you try plugging the phone in last?

wish i had more to tell/help you....


SMS
 
okay, a bit carried away here now, but i have it understood at least....

as for the drivers, i believe i used USB_Drivers_32_bit_4.6.0.zip
 

Attachments

  • roms-ging.jpg
    roms-ging.jpg
    87.5 KB · Views: 55
Back
Top Bottom