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

Root I Really Hosed it This Time

S

sosomething

Newbie
Hey guys... 1st post. Sucks it has to be under these circumstances. :(

Imagine the worst-case scenario.

Rooted Droid X (using Visionary) running 2.2 stuck on infinite red-eye boot loop.

It's been running fine for weeks after rooting, but this morning I installed Metamorph and tried to get a black notification bar using this:

MetaMorph – Notification & Icons – droidpirate.com

...and I did not heed the warning when installing the packs in OD.zip.

I have already tried to wipe all user data and reset to factory defaults (to my great dismay) and even after that, the phone still goes into a boot loop.

I think I overwrote or corrupted some system file that the phone considers factory-installed.

I do not have a backup.

At this point I will try anything to at least get it back up and running.

Your help would be greatly (GREATLY!) appreciated.

-adam
 
RoOoLeR said:
Guide to restoring your Droid X to stock 2.2 OTA VIA RSD Lite "SBF"

->-> Droidxforums, Roooler, and Myself take no resposibility for any damage this may directly or indirectly cause your phone.
->->By following this guide YOU take all responsibility for the outcome good or bad.

*******************************************************************************************
I Take no credit for the methods used here. They are a combination of information I found at various sites.
I only read, retained, reworded, and regurgitated it for you. Hopefully in an easy to understand and follow form.
*******************************************************************************************

***Required Files and Hardware***
--------------------------------------------------------------------------------------------------------

- Motorola USB drivers (Windows 32 bit) (Windows 64 bit)
- RSD Lite 4.8 (Get It Here) No longer needs patched.
- Droid X 2.2 SBF (Get It Here)
- USB 2.0

************************************************************************
DO NOT PROCEED UNLESS YOUR BATTERY IS @ 80% OR HIGHER. YOU HAVE BEEN WARNED.
************************************************************************

***Instructions***
--------------------------------------------------------------------------------------------------------
- Unzip the 2.2 sbf to a working/temp folder
- Open RSD Lite, tap the
Click to expand...
 
I'm afraid I do not know which my phone was on. I'm not sure how to find out.

I know it came stock from Verizon running Froyo, and I don't think I ever updated anything beyond that. Would that mean it was set up with 2.2?

Sorry for my noobishness here. I wish I could provide better information.
 
It's really not that big a deal if you flash the wrong SBF.

If you flash the wrong one, when you boot up you'll get the bootloader - black screen with white lettering that will say "Err" and then some letters and numbers on it, and you can flash the correct SBF.

If you think you were on 2.2, flash the 2.2 SBF. If you get the symptom described above, then flash the 2.2.1 SBF.
 
I am guessing that you are on .315... SBF is your friend....

Just to be safe though you might as well either flash the .320 leak or if you can get your hands on the full .340 sbf then use that. I don't believe there is a full .340 in the wild though. At least not yet...
 
ECFfighter7232 said:
when did you get it? over a month ago?
Click to expand...

Yeah, I've had it 1.5 or 2 months.

binary visions said:
It's really not that big a deal if you flash the wrong SBF.

If you flash the wrong one, when you boot up you'll get the bootloader - black screen with white lettering that will say "Err" and then some letters and numbers on it, and you can flash the correct SBF.

If you think you were on 2.2, flash the 2.2 SBF. If you get the symptom described above, then flash the 2.2.1 SBF.
Click to expand...

Fair enough. That's exactly what I'll do.

Unfortunately I'm at work right now so I won't be able to try anything until I get home.

Thanks guys.
 
BIG CAT 7 said:
I am guessing that you are on .315... SBF is your friend....

Just to be safe though you might as well either flash the .320 leak or if you can get your hands on the full .340 sbf then use that. I don't believe there is a full .340 in the wild though. At least not yet...
Click to expand...

My bad I didn't realize you could flash back. Thought it did permanent damage. If that is the case then start with the .315 (which is 2.2) if you want or just go with the latest and greatest...
 
I'm going through this process now. RSD lite installed no problem. SBF extracted fine. About 14% through the process.

Odd thing - my phone kept trying to boot the moment it got USB power. I had to pull the battery and stick it back in while holding vol-down and the camera button down to get into Bootloader.

Here's hoping this is the right SBF! Fingers crossed....
 
Looks like it worked.

I'm booted up and running - currently setting up my Google account with the phone.

Now I can embark upon the endless process of reconfiguring months of apps and customizations.

I wanna thank everyone in this thread who offered so quickly to help me out. I really appreciate it!!
 
Good to hear. This time around make a nandroid before playing around. It will save you the trouble of reconfiguring everything. However, now that you're sbf experienced, you know what to do in worst case scenario's.
 
Outlaw71 said:
Good to hear. This time around make a nandroid before playing around. It will save you the trouble of reconfiguring everything. However, now that you're sbf experienced, you know what to do in worst case scenario's.
Click to expand...

Yep, advice I will definitely heed without fail.

thanks again, folks.
 
BuTbKa said:
Next time you bootlooping try wipe data/cashe first ;)
Click to expand...

I did, but that didn't help.

Luckily I'm all set now. I won't be digging around in there again without a full NAND backup.

EDIT: Rebooting now after purchasing Droid X Recovery Bootstrap & creating backup. I definitely feel more secure now!
 
Pick up Rom Manager, then you can name it something other than the date or even go back and easily rename older backups. Just don't use spaces, semicolons or colons.

I know this is old, but this is how I name my backups:

rom_manager.jpg
 
colchiro said:
Pick up Rom Manager, then you can name it something other than the date or even go back and easily rename older backups. Just don't use spaces, semicolons or colons.

I know this is old, but this is how I name my backups:

rom_manager.jpg
Click to expand...


I have ROM Manager, but it's behaving strangely so I'm hesitant to use it.
It keeps prompting me to install Clockwork Recovery, but I already have Droid X Bootstrapper, so I guess I don't understand why I need this other recovery app made by the same guy..
 
You must log in or register to reply here.
Back
Top Bottom