Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Razr hd bricked.

OP meat-rack

12th May 2014, 07:42 PM   |  #1  
OP Junior Member
Thanks Meter: 2
 
23 posts
Join Date:Joined: Jul 2012
I have a razr hd. I can boot into ap fastboot but thats it. Anything else it sits on red m logo. Cant boot into recovery or anything. I can flash xml using one of matts utility without any fails but rebooting just sits on red m.Please help.
13th May 2014, 01:23 AM   |  #2  
bweN diorD's Avatar
Senior Member
Thanks Meter: 971
 
2,039 posts
Join Date:Joined: Jun 2011
More
Quote:
Originally Posted by meat-rack

I have a razr hd. I can boot into ap fastboot but thats it. Anything else it sits on red m logo. Cant boot into recovery or anything. I can flash xml using one of matts utility without any fails but rebooting just sits on red m.Please help.

we are going to need a bit more information to possibly help you.
what did you do to get into this predicament?
are you locked or unlocked?
if locked, what was your system version prior to the issue?
16th May 2014, 05:23 AM   |  #3  
Slickville's Avatar
Junior Member
Flag Blaine
Thanks Meter: 0
 
1 posts
Join Date:Joined: May 2014
More
Quote:
Originally Posted by bweN diorD

we are going to need a bit more information to possibly help you.
what did you do to get into this predicament?
are you locked or unlocked?
if locked, what was your system version prior to the issue?

Same issue for me after OTA. Just processed the OTA as normal and phone will not climb out of the Red M loop. Non rooted, locked device. Attempted to utilize RSD with a few flash files and no luck. Very inexperienced with this. Sorry to be so dense, just looking for any direction possible.
16th May 2014, 11:25 PM   |  #4  
bweN diorD's Avatar
Senior Member
Thanks Meter: 971
 
2,039 posts
Join Date:Joined: Jun 2011
More
Quote:
Originally Posted by Slickville

Same issue for me after OTA. Just processed the OTA as normal and phone will not climb out of the Red M loop. Non rooted, locked device. Attempted to utilize RSD with a few flash files and no luck. Very inexperienced with this. Sorry to be so dense, just looking for any direction possible.

i wish i could help you but without knowing exactly what the ota flashed before failing, any advice i give has the real possibility of making your phone worse or possibly perma bricked. the problem is you are locked and we dont yet have a fxz for kk.

that being said, if you still want to try and fix it against my advice i will tell you what to try but I AM NOT RESPONSIBLE IF THIS BRICKS YOUR PHONE OR MAKES IT WORSE IN ANY WAY.
download this xml file http://www.mediafire.com/view/p217ak...W_CFC_DOWN.xml
download the 9.30.1 ota from sbf droid devs
extract it to a folder and DELETE the xml file, then copy the one above into the folder
make sure you have the latest rsd, i think its 6.1.5 (not positive)
load the xml file into rsd and flash as usual

if this does not work, there is no way to fix your phone until the kk fxz is leaked, assuming this doesnt make it worse.
The Following User Says Thank You to bweN diorD For This Useful Post: [ View ]
16th May 2014, 11:46 PM   |  #5  
killrhythm09's Avatar
Senior Member
Flag California
Thanks Meter: 86
 
244 posts
Join Date:Joined: May 2011
More
6.1.6 is the newest RSDLite I've seen.
The Following 2 Users Say Thank You to killrhythm09 For This Useful Post: [ View ]
17th May 2014, 08:57 PM   |  #6  
iBolski's Avatar
Senior Member
Flag Columbus
Thanks Meter: 527
 
1,593 posts
Join Date:Joined: Nov 2010
More
Go here if you haven't applied the OTA yet and your bootloader is locked.

http://www.droidrzr.com/index.php/to...to-kitkat-ota/

If you have applied the OTA and you're locked, don't do it. You'll have to wait for the FXZ to come out. Otherwise, it will brick even further.

If you have applied the OTA AND your bootloader is UNLOCKED, then you can use the tool to flash back to stock 9.30.1.
19th May 2014, 01:37 AM   |  #7  
Junior Member
Thanks Meter: 1
 
6 posts
Join Date:Joined: May 2014
I too am bricked. unrooted and locked. Ran the ota and when it reset, it now hangs at the red M. Can get into fast boot and recovery. Tried factory restore and wipe cache. Once I did that my phone now randomly boots to andy all opened up, waiting for me to press the buttons to go into recovery. If I leave it like that, it just reboots after a time and does it all over again . I'm going to assume the only way forward is the xfz file? Any body have an idea of when that might become available and where about I can pick it up? I.E. which forum might have it and will it be a new thread?
19th May 2014, 01:55 PM   |  #8  
iBolski's Avatar
Senior Member
Flag Columbus
Thanks Meter: 527
 
1,593 posts
Join Date:Joined: Nov 2010
More
Quote:
Originally Posted by Grimaldus3320

I too am bricked. unrooted and locked. Ran the ota and when it reset, it now hangs at the red M. Can get into fast boot and recovery. Tried factory restore and wipe cache. Once I did that my phone now randomly boots to andy all opened up, waiting for me to press the buttons to go into recovery. If I leave it like that, it just reboots after a time and does it all over again . I'm going to assume the only way forward is the xfz file? Any body have an idea of when that might become available and where about I can pick it up? I.E. which forum might have it and will it be a new thread?

This has been posted many times. When installing the OTA manually via recovery, a few things happen:
  1. The first time you apply the OTA in recovery, it replaces the recovery with a new recovery and reboots the phone. This new recovery requires a new key combo to get into it. The new key combo is vol-up + power.

    So, after you attempt to apply the OTA the first time, you need to be around so when it reboots into the Andy screen, you can use the new key combo. Otherwise, if you leave it alone, it will reboot and then you'll see the red Moto logo which means you'll have to reboot the phone and then hold vol-up + power to get the boot menu and select "Recovery" and then go to the next step.
  2. After getting back into the new recovery, you must apply the OTA again so it can continue to upgrade your phone. After this, you'll be upgraded to Kit Kit.
19th May 2014, 05:28 PM   |  #9  
Junior Member
Thanks Meter: 1
 
6 posts
Join Date:Joined: May 2014
Quote:
Originally Posted by iBolski

This has been posted many times. When installing the OTA manually via recovery, a few things happen:

  1. The first time you apply the OTA in recovery, it replaces the recovery with a new recovery and reboots the phone. This new recovery requires a new key combo to get into it. The new key combo is vol-up + power.

    So, after you attempt to apply the OTA the first time, you need to be around so when it reboots into the Andy screen, you can use the new key combo. Otherwise, if you leave it alone, it will reboot and then you'll see the red Moto logo which means you'll have to reboot the phone and then hold vol-up + power to get the boot menu and select "Recovery" and then go to the next step.
  2. After getting back into the new recovery, you must apply the OTA again so it can continue to upgrade your phone. After this, you'll be upgraded to Kit Kit.

Right. By reading your earlier posts instructions I got into recovery. That is how I was able to factory reset and wipe cache. I'm talking about AFTER I did all that, instead of just being hung at red m screen, it hangs for a few seconds, then flickers, hangs a few more seconds, and then goes into andy screen. If I don't touch it for a few minutes, it reboots, and that same process starts over, ending with the andy screen again...Its like it WANTS me to be in recovery to fix it .

I noticed you also said to others that us lot are pretty much screwed until the fxz file is out, which I assume is this OTA as a zip so we can flash with recovery? Any idea when that will be coming out? and where should I look for it once its out?

Heck, because I was unrooted and locked and it was the official OTA from verizon, maybe I should go in to them and demand they replace my phone with the moto x. Though, I rather liked my razr hd and don't quite wanna give up on it...
19th May 2014, 07:51 PM   |  #10  
iBolski's Avatar
Senior Member
Flag Columbus
Thanks Meter: 527
 
1,593 posts
Join Date:Joined: Nov 2010
More
Quote:
Originally Posted by Grimaldus3320

Right. By reading your earlier posts instructions I got into recovery. That is how I was able to factory reset and wipe cache. I'm talking about AFTER I did all that, instead of just being hung at red m screen, it hangs for a few seconds, then flickers, hangs a few more seconds, and then goes into andy screen. If I don't touch it for a few minutes, it reboots, and that same process starts over, ending with the andy screen again...Its like it WANTS me to be in recovery to fix it .

I noticed you also said to others that us lot are pretty much screwed until the fxz file is out, which I assume is this OTA as a zip so we can flash with recovery? Any idea when that will be coming out? and where should I look for it once its out?

Heck, because I was unrooted and locked and it was the official OTA from verizon, maybe I should go in to them and demand they replace my phone with the moto x. Though, I rather liked my razr hd and don't quite wanna give up on it...

No, the FXZ is the full kit-kat image, not an update like the OTA. The FXZ can be used to flash your phone back to full stock, whether you are locked or not. If you are locked, then you can only flash the version that is currently on your phone or newer. You cannot flash back to a previous version unless your bootloader is unlocked.

The ota is used to only update a previous version to the current version, in this case from JB to KK, but once it's applied, you cannot apply it again since you are already upgraded to that version. It's only an upgrade, not a full image like an FXZ.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes