Error during SBF back to 2.1, "Code Corrupt" in bootloader, what now?

[the_Fiddler]

I was following the instructions at: How to: Return DROID X Back to Android 2.1 - Droid Life: A Droid Community Blog to go back to stock 2.1 from leaked 2.2, so I can get the OTA 2.2 update, when I got an error about "Error sending RAM download for bootloader..." (there was more to it than that, but I don't have it on my screen anymore). After trying several things, my phone now comes on to the bootloader, but says "Code Corrupt" then "Battery Low" and "Cannot Program" flash on individual lines below. I tried holding down power to shut it off, as well as removing the batter. Both so it could charge faster with the screen off. However, it doesn't do anything. My phone immediately goes back into the bootloader when the battery is replaced.

Any ideas?

[Ads]

[the_Fiddler]

Wow, weird how something always happens right after you post. So I just did the vol-down+camera+power and the phone shut off. I then pulled the USB cable out of the wall adapter and the green light came on. So its charging now. Don't know if that will fix things, but at least I can charge the battery faster (without the screen on) so that warning won't flash on the screen.

But any suggestions on what to do once it's charged would be helpful. One guy said he got that error (I think it was the same one), and he said he just checked "ODM_Serial" under Config>Flash/Flex options and started over and it worked. Can anyone confirm this or tell me what worked for them?

EDIT: Okay, now I'm getting worried. Its been "charging" with the screen off for almost 2 hours now. Normally this would nearly fully charge it. However, the above mentioned "Battery Low" and "Cannot Program" messages are still flashing on the screen. What do I do?

[e3zkiel]

The phone will not be able to charge without the OS installed. Since you did not have a successful flash you will NOT be able to charge the battery. I remember reading a post on how to 'manually' charge the battery by splitting a usb cord and touching the terminals on the battery. I would be very very careful if you try to attempt that. Otherwise, you need to find a friend's X to use their phone to charge your battery. With regards to the .sbf not flashing correctly. The same thing happened to me, and what ended up happening was I had driver issues/conflicts with the X's drivers (Motorola Flash Device; something along those lines in the device manager). Short of reformatting the machine and/or cleaning USB drivers and reinstalling them (via chipset drivers), try and install RSDLite on another machine and also install the X's drivers BEFORE connecting your device (either 32-bit or 64 according to the OS of the machine). After you X's battery is fully charged from another phone, give it a go again. I would not check ODM_Serial under Flash/Flex options because the X doesn't use that protocol anyways. I don't see how that would help. Just my 2 cents. If anyone else has anything to add/correct, let me know! Good luck...

[lifebeginsfriday]

I actually had the same error when I first attempted to flash the 2.1 for the 2.2ota... my heart dropped when i seen that "code corrupt" but a second flash attempt went right through... as stated above though you'll have to find a way to charge the battery or get one that is charged. good luck.

[the_Fiddler]

Thanks guys. I actually got a response on another forum. So the next morning after posting the above messages, I went to the Verizon store and explained that it had run out of battery during an update. I also said I'd researched it extensively and that I was pretty sure I knew how to fix it, if they could just charge the battery for me. They said they could flash it with another battery in it, and would charge mine up. I'm one of the idiots that pulled the "pull" tab without the battery in and ripped it. So the tech tried to get my batt out with a screwdriver and it looked like he tore the outside of the batt up pretty good (I told him a paperclip works much better, but he didn't listen). Anyway, when I returned a short time later they informed me they didn't have the right software to flash it, but that my battery was charged enough and showed me that it now said "battery okay" or whatever. They said they'd let me try to fix it since I said I thought I knew how, but to come back if it didn't work. I went home and restarted the process, and everything went perfectly! I'm now on OTA 2.2 and MyBackupPro restored a lot of my data and apps without much effort. I'm pretty sure that they just stuck a different battery in my phone and let me keep that one. It doesn't have any markings from the screwdriver or anything. So I think I get a new battery out of this deal. Anyway, thanks for your help guys, I'm all good now. Any cautions or anything if I go ahead and attempt to root it now (other than making sure I have a full charge beforehand)? I was thinking of using this method as it seemed like the easiest option: [How-To] Root Your Motorola Droid X Running Android 2.2 Froyo | Android News, Reviews, Applications, Games, Phones, Devices, Tips, Mods, Videos, Podcasts - Android Police

[e3zkiel]

@the_Fiddler

check this post I explained in a different part of this forum... What do I have to do to install roms?

This should give you a good idea of positives/negatives, etc... Good Luck!

[maddox]

I have found that using 32bit xp works better than 64bit vista. On vista I kept getting failed to flash for all kinds of reasons. Plus the software info never showed up. Sometimes it would flash but have a fail something about the boot. So I left the phone plugged in and did not touch anything after a couple min. It would reboot and I would have 2.1 on. It was not right though cause I could not get it to root correcly or install leaked 2.2. On 32 bit it worked wonderfully.

[the_Fiddler]

Thanks guys. I went ahead and rooted. I'm not going to do ROMs or any advanced stuff. Just wanted full access to my phone for things like SetCPU, WiFi hotspot, screenshots, etc. And especially to freeze some of the bloatware, so I don't have to worry about it running and using up mem/batt, or cluttering up my app drawer.