Droid X: Bootloader 30.03, Err:A5,70,00,00,23

[ofafeather]

Should be 30.04! Sorry!

Hi, All,

My Droid X informed me that it was ready to install an update so I said OK. It was not plugged in to the computer but was fully charged. It was updating for a while then came up with this message:

Bootloader 30.04
Err:A5,70,00,00,23

Battery OK
Ok to Program
Transfer Mode:
USB (I plugged it in to my desktop hoping that was the solution)

Any ideas where to go from here? I'm not sure of the number of the update but it would have been the most recent one. I have tried powering down, holding the power and home buttons and even removing the battery to no avail.

Help!

Thanks,
Eric

[Ads]

[BHuber09]

Linux solution to your Windows/RSD lite problems

Follow those directions and it'll be fixed. Choose to go to 2.3.4 version .621
All the directions are on the link
If you have any questions ask I'll be happy to help

FreeMyMoto!!!

[ofafeather]

Thanks! Working on it now.

[BHuber09]

No problem. Any questions ask

FreeMyMoto!!!

[ofafeather]

No problem. Any questions ask

FreeMyMoto!!!

Happy to report that it worked! Thanks so much!

Unhappy to report that I am now back to square on having lost all of mys settings, etc.

Oh, Well.

[BHuber09]

Yes I know, that's the bad part. However it beats not having a phone!! Haha

FreeMyMoto!!!

[ofafeather]

Yes I know, that's the bad part. However it beats not having a phone!! Haha

FreeMyMoto!!!

Oh, well. That's life. I did the Froyo version which is 2.3.340. There is an update to 2.3.5. I installed that and am now installing .625. Or at this point, is there any reason to change to one of the Gingerbread systems since I am already wiped clean?

Thanks!

[BHuber09]

Um there's not really a need. There's just some bug fixes in the latest versions.

FreeMyMoto!!!

[ofafeather]

Um there's not really a need. There's just some bug fixes in the latest versions.

FreeMyMoto!!!

Thanks again.

[heykerrdog]

I used this thread to fix my Droid X yesterday. Same issue as ofafeather. While using my stock phone (purchased 8/19/2010), I got the Verizon "update" harassment. I said, "No" but eventually lost the argument and found the phone updating while I had left it on in the middle of doing some work. "Seven minutes" was the last note of optimism, followed by, what's that? A DOS screen? Is there such a thing as DOS anymore? I'm behind the times. I took it to Verizon. They gave me a song and dance, disappearing into the back room, reappearing with sad funeral music. "It's dead." "You're only 17 days away from an upgrade, I can waive that, you can walk out with a new phone if you sign another 2 year contract." Funny, I thought it was 2 years for an upgrade. "Or, you can "try" to get it warrantied, you do have the extended warranty, but there are some scratches on the case and they might reject it." Funny, lady, it's a not yet two year old phone, which I use. Do you want to see some 2 year old underwear? I think I have those with me as well. Here, hold my phone while I unzip my pants. Never mind. I'll take my chances with the free warranty. Why did Verizon update my phone without my approval? Why didn't Verizon back-up all of my phone's settings, information, programs, etc., before scrambling it's brain? Warranty phone should be here tomorrow. Fine. Bye.

Back at home, I started researching and found this forum and signed up. I struggled a bit, but this thread breathed life back into my Droid X, which is bone stock. I've only had the Verizon drug pushers force anything down it's throat. Yesterday, like many other unwanted updates, it F'd my phone.

I used my 2011 Macbook Air with external Super Drive. I was not sure which ".iso file" to download, so I ended up using the first option listed, 2.3.340, FroYo. I had problems with my MacBook Air screen blanking-out portions of the screen display once the program began to execute. So, I had to go back and re-re-read all the posts and watch the videos over and over to figure what keys to push on the Macbook Air, since I couldn't read much of anything. I took photos of the screens. I'll try to post them up.

Thanks to all the folks that worked so hard to make this fix happen. I'm amazed. Now I have about a million questions on what I should do to avoid this kind of catastrophe (at least minimize the pain) when it happens again, because I don't really know if I backup my stuff, or where it goes, or the name of the little Verizon/Google marketing midget that lives inside my phone. But, I'll save that for after I research what rooting and Gingerbread and all that Greek stuff means.

Thanks for the fix! I'm fixed, got my coffee, and ready to march into Verizon and shove some survivor fist up their...