Root Droid X only boots into Bootloader

[johnan2112]

Hey guys. Not sure what's going with my phone. I was running the rooted OTA and my gallery froze up. I pulled my battery and when my phone booted up, it was sitting in the bootloader screen. I tried a few more times but nothing worked. I even went into stock recovery and wiped data to no avail. I figured that I might need to SBF back to Froyo but even once that was completed, it went straight back into the bootloader. Has anyone ever seen this or have any advice?

Thanks!

 

[Deleted User]

What does it say on the bootloader screen?

Also, is it plugged in when it's doing this?

 

[johnan2112]

It's the same bootloader screen as if you were going to SBF normally.

Bootloader
30.04

Battery OK
OK to Program
Connect USB
Data Cable

or the last 2 lines change to
Transfer Mode:
USB

I've tried with and without the phone plugged in.

 

[Deleted User]

Huh.

Uh...

Try it now?



Seriously, though, bizarre. Only thing I can think is something is hosed up in the phone to the point that the bootloader can't even call to the kernel/initialization scripts. That usually shows an error on the screen, though.

 

[johnan2112]

Still a no-go. I guess I have to stop in at VZW during my lunch break. I've SBF'd so many times that I know I'm not doing something wrong when flashing. It looks like this issue is out of my hands.

 

[johnan2112]

Oh, another thing. On a whim, I tried installing the official GB update.zip from my SD card in stock recovery and I'm getting the following error:

E: Can't find MISC:
.Finding update package...
E: Can't mount dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E: Can't mount SDCARD:update.zip
Installation aborted
E: Can't mount CACHE:recovery.log
E: Can't find MISC:

 

[Deleted User]

Sounds like some of your storage partitions aren't even accessible, which would explain why it's booting straight into the bootloader.

 

[aloha.android]

Wow. Could this be a sign of a virus??

 

[droidfan1]

Try a different computer. Install the correct drivers - use a full froyo 2.3.340 SBF, and then see what happens.

 

[johnan2112]

Try a different computer. Install the correct drivers - use a full froyo 2.3.340 SBF, and then see what happens.

Tried on 2 computers with the latest Moto drivers and with the full Froyo SBF and the GB SBF. Still a no-go.

 

[sic0048]

You used the 4th SBF file listed in this guide called the Android 2.2.1 System Version 2.3.340 Full (VRZ_MB810_2.3.34_1FF_01)? It might appear on other sites as simply VRZ_MB810_2.3.34_1FF_01.

Other .340 SBFs may not full images. It sounds like you know what you are talking about, but we have to start at the basics because it is usually something simple causing the issue.

 

[johnan2112]

You used the 4th SBF file listed in this guide called the Android 2.2.1 System Version 2.3.340 Full (VRZ_MB810_2.3.34_1FF_01)? It might appear on other sites as simply VRZ_MB810_2.3.34_1FF_01.

Other .340 SBFs may not full images. It sounds like you know what you are talking about, but we have to start at the basics because it is usually something simple causing the issue.

Yup. In fact, it was the same image file on my computer that I used to SBF back from leaked versions of GB before. In any event, I ended up taking it to the VZW store and they shipped a replacement out to me so all is good.