Help OTA ICS update bricked my phone - Motorola Droid RAZR

I started high jacking threads to get some help and I don't want to be that person.
So let me start from the beginning, I decided to install the ICS update after my husband's and my mom's phone automatically updated on my completely stock Razr MAXX. I installed let it go and it restarted and got stuck on the DROID splash screen. Tried restarting, same thing. Tried reinstalling the update from the cache, same thing, stuck on the DROID screen. Asked Motorola, they told me to do a hard reset, no results. I've tried to go back to GB using the 1.6 utility which got it stuck to the dual core splash screen. Somebody told me to use the 1.81 utility, used option 1, back to the DROID splash screen.
Currently I'm wondering if I'm just being impatient, so I've let it sit after the last load for about 2 hours now, I've let it sit at the spot for up to 4 hours previously hoping it would start up.
I have some tech skills as long as I understand what I'm doing, right now there are a lot of jargon that I have no idea what it means being thrown around. If anyone has help for me I would greatly appreciate it. I don't want to go through the refurbished phone nightmare (last time I went through 3 phones before I got one that worked). I would be eternally grateful to anyone who has some help for me especially if I could understand it :silly:
Thanks in advance to anyone who can help!

---

Of you are stock then send it back for a warranty repair.
Sent from my DROID RAZR using Tapatalk 2

---

snobunny said:
I started high jacking threads to get some help and I don't want to be that person.
So let me start from the beginning, I decided to install the ICS update after my husband's and my mom's phone automatically updated on my completely stock Razr MAXX. I installed let it go and it restarted and got stuck on the DROID splash screen. Tried restarting, same thing. Tried reinstalling the update from the cache, same thing, stuck on the DROID screen. Asked Motorola, they told me to do a hard reset, no results. I've tried to go back to GB using the 1.6 utility which got it stuck to the dual core splash screen. Somebody told me to use the 1.81 utility, used option 1, back to the DROID splash screen.
Currently I'm wondering if I'm just being impatient, so I've let it sit after the last load for about 2 hours now, I've let it sit at the spot for up to 4 hours previously hoping it would start up.
I have some tech skills as long as I understand what I'm doing, right now there are a lot of jargon that I have no idea what it means being thrown around. If anyone has help for me I would greatly appreciate it. I don't want to go through the refurbished phone nightmare (last time I went through 3 phones before I got one that worked). I would be eternally grateful to anyone who has some help for me especially if I could understand it :silly:
Thanks in advance to anyone who can help!
Click to expand...
Click to collapse
You can try option 1 follow these instructions
Getting back to .211:
This is a fairly simple process, but not as simple as getting back to .211 from .214.
If you are new to this, please fully read all the directions before starting this process. Remember, check how much battery you have.
1) Download Matt's Droid Razr Utility 1.81 from the link above.
2) Extract the files from the .zip (Creates DroidRazrUtility1.81 folder)
3) Go into the DroidRazrUtility folder and start the DroidRazrUtility batch file
4) At the Batman logo, press any key to continue.
5) At the next menu, select option "1" (Fastboot Restore 6.16.211 (ICS 4.0.4 Official OTA Software)) by typing 1 and pressing enter.
** DO NOT PRESS ANYTHING AT THE NEXT SCREEN UNTIL STEP 10**
6) Attach your phone to your PC with a USB cable.
7) Power down your phone
8) While phone is off, hold down both volume keys (up+down) and the power key.
9) Use the Volume Down key to select "AP Fastboot" and then use the Volume Up key to select it.
10) On the DroidRazrUtility, press any key to continue.
11) Keep an eye on your phone, it will turn off and on again.
12) Follow the on screen instructions and press any key why your phone's display turns on.
13) Repeat Steps 11-12 one more time
** .211 install should take around 5-10 minutes **
14) When the screen asks if you want to wipe data, hit any key to continue OR exit the program to KEEP DATA.
15) Tap the power key to bring you out of AP Fastboot, then it should power down.
16) Turn on your phone to see a screen of an Android with his chest open. Wait.

---

dave5777 said:
Here's a Dropbox link to the 1.81 Utility You can try option 1 follow these instructions
Getting back to .211:
This is a fairly simple process, but not as simple as getting back to .211 from .214.
If you are new to this, please fully read all the directions before starting this process. Remember, check how much battery you have.
1) Download Matt's Droid Razr Utility 1.81 from the link above.
2) Extract the files from the .zip (Creates DroidRazrUtility1.81 folder)
3) Go into the DroidRazrUtility folder and start the DroidRazrUtility batch file
4) At the Batman logo, press any key to continue.
5) At the next menu, select option "1" (Fastboot Restore 6.16.211 (ICS 4.0.4 Official OTA Software)) by typing 1 and pressing enter.
** DO NOT PRESS ANYTHING AT THE NEXT SCREEN UNTIL STEP 10**
6) Attach your phone to your PC with a USB cable.
7) Power down your phone
8) While phone is off, hold down both volume keys (up+down) and the power key.
9) Use the Volume Down key to select "AP Fastboot" and then use the Volume Up key to select it.
10) On the DroidRazrUtility, press any key to continue.
11) Keep an eye on your phone, it will turn off and on again.
12) Follow the on screen instructions and press any key why your phone's display turns on.
13) Repeat Steps 11-12 one more time
** .211 install should take around 5-10 minutes **
14) When the screen asks if you want to wipe data, hit any key to continue OR exit the program to KEEP DATA.
15) Tap the power key to bring you out of AP Fastboot, then it should power down.
16) Turn on your phone to see a screen of an Android with his chest open. Wait.
Click to expand...
Click to collapse
Thanks, very clear directions, but I've already tried that....twice and I'm stuck at the DROID splash screen. I let it sit there all night hoping and praying it was slow and eventually boot up, but that is wishful thinking.
I'm going to find out if I can send it in for warranty repair now. In the past they've only been willing to replace and not repair...and always with a crappy refurb.
Wish me luck!

---

snobunny said:
Thanks, very clear directions, but I've already tried that....twice and I'm stuck at the DROID splash screen. I let it sit there all night hoping and praying it was slow and eventually boot up, but that is wishful thinking.
I'm going to find out if I can send it in for warranty repair now. In the past they've only been willing to replace and not repair...and always with a crappy refurb.
Wish me luck!
Click to expand...
Click to collapse
Well thanks a whole bunch Motorola for your lovely use of the ridiculous "water damage indicator" While my phone has never seen water, my guess is "excessive humidity" which I'm sure it encountered while I was on my honey moon in Mexico tripped the indicator. So even though my phone worked perfectly fine until it decided to update and I can't see how the failure to boot could even be conceivably be related to their supposed water damage, they sent the phone back to me without even attempting to fix it (two weeks to send it back unrepaired and warranty voided) stating that the problem was in fact the water damage........AAGGGGGGGGG F#$%^%$%#$#$$^^^&&%&$%$^#$%#@!!&*(&*(%^$
They didn't even bother to call me and say "hey, you have water damage, so your warranty is voided. But it says here that it quit working after you updated your OS, so maybe we can fix it anyway because that probably has nothing to do with the so called water damage" But that would actually require them to know why I sent my phone in the first place. Something you would think that they might have on file, but NOOOOO. So now I can try to warranty through Verizon, which if I try I will most likely get a too bad now give us $600 for your phone that wasn't under warranty. Or I beg Motorola to wipe it and reinstall the OS, but I'm sure they will tell me that is something that isn't possible. Or I "lose" my phone and pay the deductible on insurance. F)*&%$#@$^&*))*&$$#^*(*.
Thanks Motorola for being *&^$heads. :crying:

---

snobunny said:
Well thanks a whole bunch Motorola for your lovely use of the ridiculous "water damage indicator" While my phone has never seen water, my guess is "excessive humidity" which I'm sure it encountered while I was on my honey moon in Mexico tripped the indicator. So even though my phone worked perfectly fine until it decided to update and I can't see how the failure to boot could even be conceivably be related to their supposed water damage, they sent the phone back to me without even attempting to fix it (two weeks to send it back unrepaired and warranty voided) stating that the problem was in fact the water damage........AAGGGGGGGGG F#$%^%$%#$#$$^^^&&%&$%$^#$%#@!!&*(&*(%^$
They didn't even bother to call me and say "hey, you have water damage, so your warranty is voided. But it says here that it quit working after you updated your OS, so maybe we can fix it anyway because that probably has nothing to do with the so called water damage" But that would actually require them to know why I sent my phone in the first place. Something you would think that they might have on file, but NOOOOO. So now I can try to warranty through Verizon, which if I try I will most likely get a too bad now give us $600 for your phone that wasn't under warranty. Or I beg Motorola to wipe it and reinstall the OS, but I'm sure they will tell me that is something that isn't possible. Or I "lose" my phone and pay the deductible on insurance. F)*&%$#@$^&*))*&$$#^*(*.
Thanks Motorola for being *&^$heads. :crying:
Click to expand...
Click to collapse
I know it sucks, but to be honest, talk to any phone manufacturer and they would do the same thing (well, maybe they would email/call you to let you know, but you get what I'm saying).
Is there any reason why you can't simply Root and install a custom ROM or even try doing some sort of Fastboot stock restore? It sounds to me like you aren't completely bricked and that it's likely not the hardware if you are certain there is no water damage.
EDIT: Here's what I am talking about using RSD Lite and Fasbooting back to stock: http://forum.xda-developers.com/showthread.php?p=23453478

---

WorldOfJohnboy said:
I know it sucks, but to be honest, talk to any phone manufacturer and they would do the same thing (well, maybe they would email/call you to let you know, but you get what I'm saying).
Is there any reason why you can't simply Root and install a custom ROM or even try doing some sort of Fastboot stock restore? It sounds to me like you aren't completely bricked and that it's likely not the hardware if you are certain there is no water damage.
EDIT: Here's what I am talking about using RSD Lite and Fasbooting back to stock: http://forum.xda-developers.com/showthread.php?p=23453478
Click to expand...
Click to collapse
Thanks, I haven't tried RSD yet. What I think that I'm running into, and I can't be sure because I have very little knowledge about the boot files, but I think that there is a something wrong in those files and I'm not sure that the files contained when flashing back to stock are what it needs for that deficiency.
Deductive reasoning says that water damage has absolutely nothing to do with why it is actually failing to boot since the phone was working just fine before the OTA update.
It really comes down to is all phone manufacturers are trying to decrease the bottom line and cover their own butts. Interestingly someone brought a lawsuit against apple for this very issue and apple has since relaxed it's warranty in regards to water damage, for example if a piece of hardware fails that has nothing to do with water damage they will fix it under warranty....I hate to think this way, but maybe I should switch teams

---

Well, what I have found out today is that Motorola's customer service and warranty center is worse than their ability to program an OTA update that will load correctly on my phone.....
I call them on Wed to find out if they will/can wipe the phone and reload everything. Guy tells me that he will have someone call me back in 24 hours. They don't call, so I called them....they are closed. Yay. Call them today..."we see you have a case started, let me transfer you to a rep..."......ring...ring...."welcome to the viva-la-mailbox system, please enter the mailbox number of the person you would like to talk to..." WHAT THE $%^&??????......0..."invalid response"....000000000000000000000....."invalid response".....::::....hang up try again. Same thing. Call with hubby's phone. Enter my phone number....."we see you have a case started, let me transfer you two a rep..."......ring...ring...."welcome to the viva-la-mailbox system, please enter the mailbox number of the person you would like to talk to..." :::::fuming:::::
Finally beat the system and get to talk to a real human being....at least I think so.... has no idea why I'm calling even though she has the notes right in front of her....ok....transfers me to the "Claim Escalation Dept." I ask if there is a number I can call someone directly so I don't have to go through massive automated phone system glitch irritation again. Nope, this is the only number. Can I get a mailbox? Nope. Name? Nope. $%^&.
They tell me I have damage to my phone. I ask what kind of damage, they say water damage. I tell them that my receipt says the "damage" was the water damage indicator. Nope, they are saying damage to the mother-board....
Side bar- Last time I had the motherboard go on a computer I couldn't get it to boot past the blue screen of death. How is it that the motherboard is damaged but the phone worked FLAWLESSLY until I did the OTA update.
Now they have pictures...pictures they sent to me via email on 8/22....***goes to check email and all spam folders**** Nothing. He says he will resend it to me. I've been stalking my email for the last two hours for the email that he swears he was going to send as soon as he finished the notes and I have yet to see it. I will be finding a torque bit small enough to open this pile of crap up tonight and looking for this magical damage.
Ask him if it is even possible for them to wipe the phone completely and reload the entire system fresh. He tells me that the techs can only do the same that I can from my phone, do a master reset. So the techs are glorified brick and mortar sales guys that get a screw driver too? Seems unfair to them.
I would LOVE for someone who really knows the ins and outs of the hardware and programming of these phones to explain it to me in excruciating detail. Is there a way that a damaged mother board could brick a phone only when an update is installed? Like a time bomb or something.....brick bomb.
So even if the supposedly damaged mother board has nothing to do with Motorola and the Google consortium bricking my phone, there is nothing they can do for my poor dead phone. Fine. F-off.
Call Verizon, they are sending me a new phone, made sure that insurance would cover it even if they decide the warranty is void. Sheniqa, my new sista, says that it doesn't sound like a hardware issue (see, even the lady who deals with people calling with busted phones everyday sees my point). Of course I played dumb, but I'm sure they will void my warranty.
Sooooooo.......I know I'm really just talking to myself at this point and ranting, but can anyone shed light on how damage to a motherboard would cause a phone to brick during an OTA update? I'm not even being facetious, I have half a mind to sue them over this phone and pain and suffering.... Does anyone want to explain the nuts and bolts of how Droid systems boot up? and last who wants to hold my hand through this RSD thing and see if I can make one last attempt to bring it back from the dead.
I really think that I will give up the ability to customize and all the cool features of DROID for *gag* an iPhone next time.....:crying:

---

Forget the iphone. Go for the SGS II or III as samsung made there phones to bring back from the dead.
I am sure you can get this phone up and running again if you are willing to spend lots of time researching all needed info on razr not that you havent but if it doesnt work then you havent tried every thing as i have tried the endless boot a few times with razr my self.
Sent from my XT910 using xda premium

---

Well I decided to go with the warranty replacement route and I'm waiting for the next denial...
I thought I should share my treatment by Motorola. As I said, thy told me the phone has water damage. I still have yet to get a pic and I discovered that the indicator strips are in their original condition, which is white with red x's. I would love to see their picture now. Additionally, I discovered another customer receivedthe same treatment, and after much hassle did get her phone replaced. I'm hoping that Verizon will prevent this from happening, but I may have a battle ahead.
Interestingly the customer with the similar issue was eventually sent a picture of the back of "her" phone with a completely red indicator, but no identifying marks on the battery or elsewhere. Motorola is intentionally defrauding its customers. In fact even with its implicit warranty, there is an implied warranty in their advertising. I will be trudging along again with the old crap phone for a few days until I can get another phone. Hopefully Motorola won't give me any hassle as I am going through Verizon, however if they hassle me it will get ugly. Just for giggles I would love to do some testing on these indicators as well.