FORUMS

Which OEM Would You Like to Help?

Most manufacturers have moments of greatness and moments of decadence, and in the past few years … more

Root T-Mobile S6/Edge on 5.1.1 Without Tripping Knox

If you purchase phones from a carrier, you may be no stranger to the difficulties … more

IonVR Coming Soon, HTC M9 Dev Edition Gets Android 5.1 – XDA TV

The HTC M9 Developer Edition has received Android 5.1. That and … more

Android 5.1.1 Omni ROM For Motorola Xoom

Back in Feb 2011, the Motorola Xoom became the first device to be sold with Android 3.0 … more

After OTA phone only goes to fastboot

19 posts
Thanks Meter: 1
 
By MadderThanMad, Junior Member on 26th February 2012, 06:11 PM
Post Reply Subscribe to Thread Email Thread
Hello XDAers,

Last night my brother's unrooted Droid X received the newest OTA Update and restarted. After the restart his phone wouldn't boot to android. Instead his phone goes to the fast boot screen (Bootloader 30.04 Battery OK, Connect USB Data Cable). There is also an error: A5,70,00,00,23.

Does anyone know how I can fix this issue under Windows 7?
 
 
26th February 2012, 06:14 PM |#2  
infazzdar's Avatar
Senior Member
Thanks Meter: 232
 
Donate to Me
More
There currently is not a fix for this.

Sent from my DROIDX using Tapatalk
26th February 2012, 11:26 PM |#3  
OP Junior Member
Thanks Meter: 1
 
More
Update
Did some more poking around online and it looks like this is a common issue caused by an unsuccessful update corrupting the bootloader. Knowing this, I headed down to the local Verizon store. Waited about 25 minutes for service then explained to the clerk that the OTA broke my phone. She tries the usual factory restore/wipe data and it fails to fix the problem. After this she seems like she'll replace the phone but then removes the back case and notices the water damage sticker has been triggered-- it briefly fell into shallow puddle a year ago-- and promptly tells me I'm **** out of luck.

Do I have any recourse here? Obviously, it was the OTA that bricked the phone and not water damage from a year ago. Can anyone lend me some advice on what steps I can take to get a working replacement from the big red?

Thanks a lot
27th February 2012, 01:26 AM |#4  
infazzdar's Avatar
Senior Member
Thanks Meter: 232
 
Donate to Me
More
Quote:
Originally Posted by MadderThanMad

Did some more poking around online and it looks like this is a common issue caused by an unsuccessful update corrupting the bootloader. Knowing this, I headed down to the local Verizon store. Waited about 25 minutes for service then explained to the clerk that the OTA broke my phone. She tries the usual factory restore/wipe data and it fails to fix the problem. After this she seems like she'll replace the phone but then removes the back case and notices the water damage sticker has been triggered-- it briefly fell into shallow puddle a year ago-- and promptly tells me I'm **** out of luck.

Do I have any recourse here? Obviously, it was the OTA that bricked the phone and not water damage from a year ago. Can anyone lend me some advice on what steps I can take to get a working replacement from the big red?

Thanks a lot

You might have luck calling Verizon instead of visiting a store. Other than that, a lawsuit against Motorola would do.

Sent from my DROIDX using Tapatalk
27th February 2012, 01:43 AM |#5  
infazzdar's Avatar
Senior Member
Thanks Meter: 232
 
Donate to Me
More
Null and void.

Sent from my DROIDX using Tapatalk
Last edited by infazzdar; 27th February 2012 at 01:49 AM.
28th February 2012, 08:09 PM |#6  
OP Junior Member
Thanks Meter: 1
 
More
Called Verizon and they basically told me that the update was at fault but once I mentioned the water damage they said it was the water damage and not the update. Next step, we are taking them to
small claims court.

sent from droid 3
29th February 2012, 02:34 AM |#7  
infazzdar's Avatar
Senior Member
Thanks Meter: 232
 
Donate to Me
More
Quote:
Originally Posted by MadderThanMad

Called Verizon and they basically told me that the update was at fault but once I mentioned the water damage they said it was the water damage and not the update. Next step, we are taking them to
small claims court.

sent from droid 3

Geez, as terrible as it is, you shouldn't have told them about the water damage. Often times they will do a lot more when you contact them via phone than when you visit the store.

You can use the newly released .621 SBF file to fix your phone, though.

Sent from my Transformer TF101 using Tapatalk
3rd March 2012, 02:14 AM |#8  
Sleuth255's Avatar
Retired Senior Moderator
Flag Milwaukee
Thanks Meter: 39
 
More
for Windows, you need to do the following:
  • install the moto USB drivers available here
  • install rsdlite available here
  • obtain the .621 SBF from here

uncompress the sbf file from the archive, then place your DX in bootloader mode by holding down camera/volume down then pressing the power button. Connect it to your pc with a USB cable then let the moto driver install. Once the driver has installed, run rsdlite and show it where the sbf file is. Then, do the install and your DX should be good to go again.
3rd March 2012, 03:25 AM |#9  
OP Junior Member
Thanks Meter: 1
 
More
Awesome news guys. I'll try and fix it tonight.

sent from droid 3
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes