phone boots straight into bootloader and will not flash

---

I recently tried to upgrade to the new OTA gingerbread and it said that it installed okay, but after I reboot the phone it went straight to the bootloader with these errors: bootloader 30.04 err: a5,69,35,00,27. I then tried SBFing back to VRZ_MB810_2.3.34_1FF_01, but then it got through 97% of the flashing and got this error:: interface BP: loading RAM Downloader for Bootloader
failed flashing process. failed flashing process. interface BP: Error sending RAM Download for bootloader.
I have tried reinstalling the moto drivers with no luck. And it is also not charging. now when it boots into the bootloader it is flashing "battery low, cannot program" I searched all over the Internet and tried all of the recommended solutions like pulling the battery for a few minutes, I tried flashing four or five times, tried using older sbf, all with no luck. I would appreciate the help, thanks

You are going to need to charge your battery before you can sbf again. You might want to redownload the sbf again. If you go to droidxforums there is a linux distro that you download and burn as an iso to a cd that is really easy to run. First get your battery above 80 percent before you flash again. When I get to my computer I willingly post the link.

Sent from my DROIDX using XDA App

update: here is the link for the linux distro......http://www.droidxforums.com/forum/dr...-problems.html

It sounds like you are missing a driver that installs towards the end of the flash. Sorry I can't post the link, but you can google moto driver download. It's the 4.90 drivers.

Sent from my DROID X in Western Illinois

Originally Posted by Xodus83

I recently tried to upgrade to the new OTA gingerbread and it said that it installed okay, but after I reboot the phone it went straight to the bootloader with these errors: bootloader 30.04 err: a5,69,35,00,27. I then tried SBFing back to VRZ_MB810_2.3.34_1FF_01, but then it got through 97% of the flashing and got this error:: interface BP: loading RAM Downloader for Bootloader
failed flashing process. failed flashing process. interface BP: Error sending RAM Download for bootloader.
I have tried reinstalling the moto drivers with no luck. And it is also not charging. now when it boots into the bootloader it is flashing "battery low, cannot program" I searched all over the Internet and tried all of the recommended solutions like pulling the battery for a few minutes, I tried flashing four or five times, tried using older sbf, all with no luck. I would appreciate the help, thanks

When you get your battery charged SBF again, when it fails do the "SYSTEM" only SBF and it will work. I believe the error (err: a5,69,35,00,27) you are getting has to do with the stock GB recovery. I had that problem but I was still able to boot into CWR and install a recovery patch by TBH. Let me know if this works for you.

I was wondering if there was a resolution to this issue. I am getting the exact same issue, Err:A5,69,35,00,27 and I have done everything but stand on my head. Previous to reading bigshotrob22's post, I had re-SBF'd from multiple computers, using different SBF versions, driver versions, and RSD Lite versions. All resulted in getting the darn ERR:A5,69,35,00,27.

The only way I ever got anything different was to flash 1.13.604 and then I got an error message Err:A5,70,70,00,1F.

Again, I goto a new version and I go right back to original error though.

I tried bigshotrob22's suggestion and downloaded the system and full sbf files for 340. I flashed the full, got error... Then flashed system, still get error.

I am using RSD Lite 5.4 on Vista 32 with UAC disabled (full admin mode), latest Moto drivers as of this post. Again, I have tried all of the versions of bootable linux SBF's as well. All yield the same result.

Wife's phone, she is very unhappy with me, and if I don't get her back up and running, I guess I will be dropping $500 on a new phone, as she is still under contract. If Mama ain't happy, I sure ain't getting any! LOL!

You could try taking it to a VZ store and telling them that this happened after the OTA. Seems to me that this is their fault and they should fix it.