Related
So I think I might have a bricked xoom. Its the 3G/WIFI version. I tried to downgrade it to WIFI only version and got stuck from there.
Now the Xoom is stuck at the red M when booted.
If you go through recovery it says: "Reading ODM fuse:1."
If you go through fastboot it says: "Starting fastboot protocol support."
RSD: battery level
The Xoom freezes after each option is selected and that's about as much action as I can get from it. So am I screwed? If not, what can I do?
Is it recognised via ADB?
Send to service center and they should have special tool to recover it!
re-flashing Rogue Recovery
mikeay93 said:
So I think I might have a bricked xoom. Its the 3G/WIFI version. I tried to downgrade it to WIFI only version and got stuck from there.
Now the Xoom is stuck at the red M when booted.
If you go through recovery it says: "Reading ODM fuse:1."
If you go through fastboot it says: "Starting fastboot protocol support."
RSD: battery level
The Xoom freezes after each option is selected and that's about as much action as I can get from it. So am I screwed? If not, what can I do?
Click to expand...
Click to collapse
If you are getting "Starting fastboot protocol support" then you should be able to then plug in the USB cable and use ADB. I would then try re-flashing Rogue Recovery, then with a working recovery kernel you can flash the correct ROM.
Grege50 said:
If you are getting "Starting fastboot protocol support" then you should be able to then plug in the USB cable and use ADB. I would then try re-flashing Rogue Recovery, then with a working recovery kernel you can flash the correct ROM.
Click to expand...
Click to collapse
Thanks for the help guys,
So I tried re-flashing the Rogue Recovery, and other kernels, but the Xoom says,
"Device still locked. Device must be unlocked first.
Failed to process command error (0x8)"
I'll be some research too and let you guys know what happens
mikeay93 said:
So I think I might have a bricked xoom. Its the 3G/WIFI version. I tried to downgrade it to WIFI only version and got stuck from there.
Now the Xoom is stuck at the red M when booted.
If you go through recovery it says: "Reading ODM fuse:1."
If you go through fastboot it says: "Starting fastboot protocol support."
RSD: battery level
The Xoom freezes after each option is selected and that's about as much action as I can get from it. So am I screwed? If not, what can I do?
Click to expand...
Click to collapse
could you be more specific with your device details before the flash, during the flash, after the flash?
Before the flash; model mz???, ICS/JB, Rooted, custom rom, unlocked bootloader, custom recovery.....etc.
During the flash: you said that you downgraded to the WiFi version......which version? Did you fast boot the image files? Did you use RSD lite and sbf image? Which image and rsd lite image?
After; in detail explain what you did after the flash up til now.
I know that this is a lot but it will help.
From first guess it sounds like your bootloader is locked or you downgraded your boot loader to an earlier version prior to the latest ver#1050 when you downgraded your device to a WiFi version. This would also keep your device in the condition you describe or worse. I would try to unlock your boot loader.....if that fails then you need to find the latest 3G image version sbf (if there is one) using rsd lite. If that is not an option then try to flash with RSD lite the 604 combo sbf for the mz604. I had to flash it a couple times plus do a manual factory restore......good luck.
Galaxy Nexus (SCH-I515 VZW/LTE) using Tapa2
cdexsw said:
could you be more specific with your device details before the flash, during the flash, after the flash?
Before the flash; model mz???, ICS/JB, Rooted, custom rom, unlocked bootloader, custom recovery.....etc.
During the flash: you said that you downgraded to the WiFi version......which version? Did you fast boot the image files? Did you use RSD lite and sbf image? Which image and rsd lite image?
After; in detail explain what you did after the flash up til now.
I know that this is a lot but it will help.
From first guess it sounds like your bootloader is locked or you downgraded your boot loader to an earlier version prior to the latest ver#1050 when you downgraded your device to a WiFi version. This would also keep your device in the condition you describe or worse. I would try to unlock your boot loader.....if that fails then you need to find the latest 3G image version sbf (if there is one) using rsd lite. If that is not an option then try to flash with RSD lite the 604 combo sbf for the mz604. I had to flash it a couple times plus do a manual factory restore......good luck.
Galaxy Nexus (SCH-I515 VZW/LTE) using Tapa2
Click to expand...
Click to collapse
Ok its a MZ600 Xoom 3G+WiFi, rooted, don't know the rom but I can find out.
I don't know too much about the details as to how this problem occurred, but if it is absolutely necessary to know, I can find out.
I can successfully flash all of these images using fastboot. But after I flash all images, clear cache, lock oem, and restart it leads me to the motorola logo and a message that says "Failed to boot LNX 0x0004; Starting RSD mode 2; (battery level)." I tried flashing this sbf file but it gave an error reading "Failed flashing process". (My device is recognizable in RSD) But it's not a recognized device when I run adb devices
So I can scroll through RSD, Fastboot, and Android Recovery fine, but I've tried several images to flash yet I still get stuck on the "M" .
mikeay93 said:
Ok its a MZ600 Xoom 3G+WiFi, rooted, don't know the rom but I can find out.
I don't know too much about the details as to how this problem occurred, but if it is absolutely necessary to know, I can find out.
I can successfully flash all of these images using fastboot. But after I flash all images, clear cache, lock oem, and restart it leads me to the motorola logo and a message that says "Failed to boot LNX 0x0004; Starting RSD mode 2; (battery level)." I tried flashing this sbf file but it gave an error reading "Failed flashing process". (My device is recognizable in RSD) But it's not a recognized device when I run adb devices
So I can scroll through RSD, Fastboot, and Android Recovery fine, but I've tried several images to flash yet I still get stuck on the "M" .
Click to expand...
Click to collapse
the problem is when you relocked the bootloader. It was a "bad lock". You need to UNLOCK the bootloader then the device should boot up normal......RSD will recognized your device but with a screwed up bootloader nothing will flash.......also fastboot and adb will have the same result because of this
**here is what to do**
Option#1 - Try this first
1. connect Xoom to PC with Moto USB Cable (the one shipped with Xoom if possible)
2. ADB command: fastboot reboot-bootloader
3. It will show
4. Then Press Pwr + Vup (reset xoom)
5. When Xoom go into black screen (before the Moto logo appear), press and hold volume down button. I was then successfully get into Fastboot.
In step no. 5, you must press and hold the volume down button, if you release the button, Xoom will reset by itself and you will again caught in the "Failed to boot LNX 0x0004" screen. If you accidentally let go the volume down button, repeat step 4 - 5, and make sure you will not let go the volume down button this time.
Then, one of your hand is holding the volume down button, use your another hand to enter an ADB command: "fastboot oem unlock", you will be able to unlock your bootloader, and xoom will reboot normally.
Yes, I understand your xoom is not working proper but this may take 5 or 6 tries......keep at it. This has had many successes.
-------------
Option#2 - If option#1 does not work
Follow these steps to modify your USB cable to a programming cable
http://forum.xda-developers.com/showthread.php?t=1108518&page=2
Here is a tutorial if you decided to go this route
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
This too works......but make sure your contacts/wires do not touch other wise you zoom may die when everything gets plugged making the cable is a pain but it's a life saver.
------------
Those are your ONLY options for recovering from this brick.
NOTE - DO NOT RELOCK BOOTLOADER WHEN CONVERTING FROM 3G TO WIFI ONLY. I recommend never touching it after it is unlocked, ever.
The only time locking the bootloader will work is only when you return the device to its original factory condition..........and the only time. Best advice.......after you unlock the bootloader never touch it again.
I hope this helps. Good luck.
Sent from my Xoom using Tapatalk 2
Oh ya I forgot to mention that I've been able to unlock the device, but the problems are still there.
Cdexsw, I'll use the second method as a last resort.
mikeay93 said:
Oh ya I forgot to mention that I've been able to unlock the device, but the problems are still there.
Cdexsw, I'll use the second method as a last resort.
Click to expand...
Click to collapse
Do you know what version of the bootloader you currently have on your Xoom?
Galaxy Nexus (SCH-I515 VZW/LTE) using Tapa2
I've been swamped with work and finals guys I didn't forget about this. As soon as school finishes I'll put more time into trying to find a solution in case anyone is going through the same thing. Thanks to anyone trying to help out.
Hey guys I'm back. My memory is a little rusty on the topic so let me just tell you where I'm at.
I will be convinced that I have a messed up bootloader once someone explains me this... the Xoom model number on the box says MZ600. Using RSD lite, I have several sbf files downloaded: MZ600, MZ602, MX604. Running the program under administrator, I can only start RSD with the MZ604 sbfs loaded. But once again, my model is a MZ600 yet it will not load that sbf file. Can someone explain to me what is going on here?
Cdexsw, as for the bootloader I have no idea which one is installed.
The error I get from RSD when I flash the mz600 is "Failed flashing process. Unable to retrieve installation values from INI file. (0x7029); phone connected"
The only difference that sets the 600 apart from the 604 is is 3G chip in the 600. They are basically the same units other than that. You can flash a 604 SBF on a 600 with no issues, hence the term "Gedified" my xoom which means converted a 3G/4G to a WiFi only Google Experience Device.
The bootloader issue......not sure on this. Don't flash any bootloader older than 1050 (I think). And stay away from 601, 602 and other SBF files. Use only 600 or 604.
Have you tried fastboot to flash ALL the images instead of the sbf/rsd? There is a thread in this forum containing all of the stick images from HC, ICS, and JB (wifi only). Start with the images for 600, if no work then try the 604 images.
Here is the link for the images
http://forum.xda-developers.com/showthread.php?t=1049485
Oh and if your bootloader is unlocked, DO NOT LOCK IT!!! Skip any step that says to lock it......again, skip ANY step that says to lock it.....trust me......I am saving you a potential headache since you already have enough issues.
Sent from my Galaxy Nexus using Tapatalk 2
cdexsw said:
The only difference that sets the 600 apart from the 604 is is 3G chip in the 600. They are basically the same units other than that. You can flash a 604 SBF on a 600 with no issues, hence the term "Gedified" my xoom which means converted a 3G/4G to a WiFi only Google Experience Device.
The bootloader issue......not sure on this. Don't flash any bootloader older than 1050 (I think). And stay away from 601, 602 and other SBF files. Use only 600 or 604.
Have you tried fastboot to flash ALL the images instead of the sbf/rsd? There is a thread in this forum containing all of the stick images from HC, ICS, and JB (wifi only). Start with the images for 600, if no work then try the 604 images.
Here is the link for the images
http://forum.xda-developers.com/showthread.php?t=1049485
Oh and if your bootloader is unlocked, DO NOT LOCK IT!!! Skip any step that says to lock it......again, skip ANY step that says to lock it.....trust me......I am saving you a potential headache since you already have enough issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I tried flashing various boot, system, recovery, and userdata files and they all successfully get flashed through. But on reboot, I still get stuck on the Motorola logo. I tried several 604 images, because those are the only ones that actually start in RSD, but those fail as well. I tried finding out my bootloader information with the command fastboot oem get_unlock_data but the command fails and gives an error on the xoom saying Failed to process command error(0x120000)
So I'm really stuck on what to do next...
Where did you buy it
Reading the posts, you have not indicated which country you are in or where the Xoom came from.
I live in Australia and have a European model MZ601 Xoom purchased in Hong Kong. All of that makes a difference in which ROMs I use and why.
Grege50 said:
Reading the posts, you have not indicated which country you are in or where the Xoom came from.
I live in Australia and have a European model MZ601 Xoom purchased in Hong Kong. All of that makes a difference in which ROMs I use and why.
Click to expand...
Click to collapse
U.S.A....
mikeay93 said:
U.S.A....
Click to expand...
Click to collapse
OK, I will butt out. My only other thought is going into recovery and using the format option to re-format the internal partitions, then re-flash.
Read this thread
http://forum.xda-developers.com/showthread.php?t=2069809
I used motochop and got the phone rooted successfully but then my inexperience got the best of me when I tried to use safestrap to flash a 4.3 ROM. Looking back, I realize this was a terrible idea. I am now stuck at fastboot. This is the screen I get
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
I've scoured just about every thread in every forum I can find by searching, unless I'm missing something. I've tried flashing recovery and 4.1.2 using Razr HD Utility and I keep getting stuck right back here. I've tried pwr+volup, pwr+voldwn, and all 3. I've tried so many things, I'm honestly losing track of what I've done. Most threads end in something that requires USB Debugging but I can't even get into android. I'm just stuck at fastboot. I apologize in advance for possibly needing my hand held. I've rooted devices before, but I've never tried any motorolas so I'm not used to having things not go smoothly.
How can I get out of fastboot so I can use my phone again?!
same problem
zsarazan said:
I used motochop and got the phone rooted successfully but then my inexperience got the best of me when I tried to use safestrap to flash a 4.3 ROM. Looking back, I realize this was a terrible idea. I am now stuck at fastboot. This is the screen I get
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
I've scoured just about every thread in every forum I can find by searching, unless I'm missing something. I've tried flashing recovery and 4.1.2 using Razr HD Utility and I keep getting stuck right back here. I've tried pwr+volup, pwr+voldwn, and all 3. I've tried so many things, I'm honestly losing track of what I've done. Most threads end in something that requires USB Debugging but I can't even get into android. I'm just stuck at fastboot. I apologize in advance for possibly needing my hand held. I've rooted devices before, but I've never tried any motorolas so I'm not used to having things not go smoothly.
How can I get out of fastboot so I can use my phone again?!
Click to expand...
Click to collapse
I am having the same problem but i didn't root phone, just tried to flash stock rom after root failed, and says battery ok. Otherwise i've been bricked
zsarazan said:
I used motochop and got the phone rooted successfully but then my inexperience got the best of me when I tried to use safestrap to flash a 4.3 ROM. Looking back, I realize this was a terrible idea. I am now stuck at fastboot. This is the screen I get
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
I've scoured just about every thread in every forum I can find by searching, unless I'm missing something. I've tried flashing recovery and 4.1.2 using Razr HD Utility and I keep getting stuck right back here. I've tried pwr+volup, pwr+voldwn, and all 3. I've tried so many things, I'm honestly losing track of what I've done. Most threads end in something that requires USB Debugging but I can't even get into android. I'm just stuck at fastboot. I apologize in advance for possibly needing my hand held. I've rooted devices before, but I've never tried any motorolas so I'm not used to having things not go smoothly.
How can I get out of fastboot so I can use my phone again?!
Click to expand...
Click to collapse
Did you figure out the solution? Pretty simple... can just hold vol down and power for 10+ seconds and release
STuGGG said:
I am having the same problem but i didn't root phone, just tried to flash stock rom after root failed, and says battery ok. Otherwise i've been bricked
Click to expand...
Click to collapse
sooo... with the phone plugged in ... i repeat plugged in .. hold both volumes and power buttons at the same time until you get the boot menu.. then select either recovery or bp tools.. the tools option will let it charge at least.. recovery will get you going to where you really need to flash a rom or wipe data/cache so you can fix the bootloop hopfully .. good luck
i am in this exact same situation and have tried using rsd lite to flash the stock boot but the xml file has the "get-var" line in it and if i edit out then it says im in the wrong format...im a flash tool operator for a local shop here and i work on everyones phones in this area and now i have ppl messagin me thru email because my OWN PERSONAL phone is bricked haha this is not a good thing for me im sure i lose business because im missing something minor im sure
Topic Starter message have a Battery Low message
It may lock a firmware uploading process ))
hi I'm gaurang patel from Surat india, and I'm face this same pro b but Im findione
zsarazan said:
I used motochop and got the phone rooted successfully but then my inexperience got the best of me when I tried to use safestrap to flash a 4.3 ROM. Looking back, I realize this was a terrible idea. I am now stuck at fastboot. This is the screen I get
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
etMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
I've scoured just about every thread in every forum I can find by searching, unless I'm missing something. I've tried flashing recovery and 4.1.2 using Razr HD Utility and I keep getting stuck right back here. I've tried pwr+volup, pwr+voldwn, and all 3. I've tried so many things, I'm honestly losing track of what I've done. Most threads end in something that requires USB Debugging but I can't even get into android. I'm just stuck at fastboot. I apologize in advance for possibly needing my hand held. I've rooted devices before, but I've never tried any motorolas so I'm not used to having things not go smoothly.
How can I get out of fastboot so I can use my phone again?!
Click to expand...
Click to collapse
Hi I'm gaurang patel from Surat in india,
And I face same prob than I'm trying to finding master of it after 4 month Im findout that man and now my droid RAZR start good
But in that case in my RAZR when I power on it it will going in fastbootmenu
But than run boot menu and normal restart
So if u HV prob than reply me on my gmail account
AP Fastboot, locked bootloader, Flash Failure
Hi all,
I am experiencing similar problem.
I have a Droid Razr Maxx HD from Verizon.
When i power on normally by pressing the power button, phone comes up into the AP Fastboot Flash Mode
Device is LOCKED. Status Code: 0
Batter OK
...
Fastboot Reason: Flash Failure
I can start the phone by powering up into the boot menu, then selecting Normal Powerup.
Phone power's up just fine after that.
Anybody know how to fix this problem?
Some info on my system:
System Version: 182.46.15.Verizon.en.US
Model: DROID RAZR MAXX HD
Android Version: 4.4.2
Baseband Verson: VANQUISH_bp_100731.020.64.21p
Kernel Version: 3.4.42-gdb361ac
Build Number: KDA20.62-15
If i could get a dump of firmware same version and try to flash, would that fix the problem?
Anybody have that?
I am noob to this site and hope I am in the right place, please excuse if not.
kjob said:
Hi all,
I am experiencing similar problem.
I have a Droid Razr Maxx HD from Verizon.
When i power on normally by pressing the power button, phone comes up into the AP Fastboot Flash Mode
Device is LOCKED. Status Code: 0
Batter OK
...
Fastboot Reason: Flash Failure
I can start the phone by powering up into the boot menu, then selecting Normal Powerup.
Phone power's up just fine after that.
Anybody know how to fix this problem?
Some info on my system:
System Version: 182.46.15.Verizon.en.US
Model: DROID RAZR MAXX HD
Android Version: 4.4.2
Baseband Verson: VANQUISH_bp_100731.020.64.21p
Kernel Version: 3.4.42-gdb361ac
Build Number: KDA20.62-15
If i could get a dump of firmware same version and try to flash, would that fix the problem?
Anybody have that?
I am noob to this site and hope I am in the right place, please excuse if not.
Click to expand...
Click to collapse
flash anything with fastboot and it will go away. grab your firmware from sbf droid devs if need be and just flash one part (or all if you want).
bweN diorD said:
flash anything with fastboot and it will go away. grab your firmware from sbf droid devs if need be and just flash one part (or all if you want).
Click to expand...
Click to collapse
Thanks for the reply.
The problem i am having is that my phone is not rooted, so I can't just flash any prior version rom onto it. I have not been able to find the matching firmware version to reflash exactly the same version (182.46.15...) i have back onto my phone. Would you know where I could find the matching ROM? Someone had suggested getting a dump of the ROMS from an existing phone. Is that possible?
kjob said:
Thanks for the reply.
The problem i am having is that my phone is not rooted, so I can't just flash any prior version rom onto it. I have not been able to find the matching firmware version to reflash exactly the same version (182.46.15...) i have back onto my phone. Would you know where I could find the matching ROM? Someone had suggested getting a dump of the ROMS from an existing phone. Is that possible?
Click to expand...
Click to collapse
i didnt realize the sbf want out yet, just looked, its not, sorry.
oops, just looked some more and remembered @SamuriHL posted it here.
just grab one of the img files out of the sbf and flash it.
We're lucky it's back at all. It was down for a few days. Hasn't been updated in quite a while which is depressing cause there's an FXZ I'd like to get my hands on.
To get out of the fastboot screen after a failed flashing attempt (several actually) i only had to use fastboot app (that came with motopocalypse) on my computer and write in console "fastboot continue", then the phone rebooted and started normally.
I still had the locked bootloader then.
gaurangpatel39 said:
Hi I'm gaurang patel from Surat in india,
And I face same prob than I'm trying to finding master of it after 4 month Im findout that man and now my droid RAZR start good
But in that case in my RAZR when I power on it it will going in fastbootmenu
But than run boot menu and normal restart
So if u HV prob than reply me on my gmail account
Click to expand...
Click to collapse
I was looking for the solution for my phone, but after reading this post in english I broke my phone. I didn't understand a single word and he want us to contact him for solution.
Motorola droid razr hd model xt 926
how i fix this problem plz help any body
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
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.
meat-rack said:
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.
Click to expand...
Click to collapse
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?
bweN diorD said:
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?
Click to expand...
Click to collapse
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.
Slickville said:
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.
Click to expand...
Click to collapse
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/p217akcxwmijcr7/VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_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.
6.1.6 is the newest RSDLite I've seen.
Go here if you haven't applied the OTA yet and your bootloader is locked.
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-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.
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?
Grimaldus3320 said:
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?
Click to expand...
Click to collapse
This has been posted many times. When installing the OTA manually via recovery, a few things happen:
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.
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.
iBolski said:
This has been posted many times. When installing the OTA manually via recovery, a few things happen:
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.
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.
Click to expand...
Click to collapse
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...
Grimaldus3320 said:
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...
Click to expand...
Click to collapse
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.
iBolski said:
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.
Click to expand...
Click to collapse
I see, makes sense. Every days a school day I suppose. Thanks for the info. Guess I have to decide to either wait for the FXZ or go to verizon and see if they can get me a new phone.
Same thing happened to my wife, completely stock now stuck at red m. After calling verizon they suggested the factory reset which just gives you a boot to dead android guy to get into recovery on every boot. Then after a couple minutes just reboots and does the same thing, stuck in a loop. They then said it's not their software, rather Motorola's, so Verizon's only recourse is to sell me an overpriced refurb or upgrade to the edge plan. Screw them. I said unacceptable and they gave me a number for Motorola. Moto said that they put in a request to extend my factory warranty because it was the software update that caused the issue and they will let me know tomorrow. I understand stuff happens, but this is not acceptable when their harassing update causes thee issue. I knew I should've unlocked the boot loader on it when I had the chance.
al2fast said:
Same thing happened to my wife, completely stock now stuck at red m. After calling verizon they suggested the factory reset which just gives you a boot to dead android guy to get into recovery on every boot. Then after a couple minutes just reboots and does the same thing, stuck in a loop. They then said it's not their software, rather Motorola's, so Verizon's only recourse is to sell me an overpriced refurb or upgrade to the edge plan. Screw them. I said unacceptable and they gave me a number for Motorola. Moto said that they put in a request to extend my factory warranty because it was the software update that caused the issue and they will let me know tomorrow. I understand stuff happens, but this is not acceptable when their harassing update causes thee issue. I knew I should've unlocked the boot loader on it when I had the chance.
Click to expand...
Click to collapse
Then you're almost there. At the "dead android" screen, press and hold vol up and then press power and then release both buttons. This gets you into recovery.
At this point, reinstall the OTA via the recovery so it can start into the 2nd stage and then you'll be done.
iBolski said:
Then you're almost there. At the "dead android" screen, press and hold vol up and then press power and then release both buttons. This gets you into recovery.
At this point, reinstall the OTA via the recovery so it can start into the 2nd stage and then you'll be done.
Click to expand...
Click to collapse
I don't know how to reinstall the OTA via stock recovery. I tried it do the install update.zip option and nothing happened. Any pointers would be appreciated.
al2fast said:
I don't know how to reinstall the OTA via stock recovery. I tried it do the install update.zip option and nothing happened. Any pointers would be appreciated.
Click to expand...
Click to collapse
Did you download it to your phone? If so, it needs to be on your external SD card and you choose the option to install from there. You'll have to navigate to where you stored it on the external SD card.
If you didn't download it, then you should be able to push it via ADB PUSH when in the recovery. Just hook up your phone to your PC and do it that way. Just obtain the OTA from this thread. Somewhere, someone provided a link to it. Download it to your PC and then do an adb push to the external SD card of the OTA and then install it that way.
iBolski said:
Did you download it to your phone? If so, it needs to be on your external SD card and you choose the option to install from there. You'll have to navigate to where you stored it on the external SD card.
If you didn't download it, then you should be able to push it via ADB PUSH when in the recovery. Just hook up your phone to your PC and do it that way. Just obtain the OTA from this thread. Somewhere, someone provided a link to it. Download it to your PC and then do an adb push to the external SD card of the OTA and then install it that way.
Click to expand...
Click to collapse
Thanks for the tips. I must have done something wrong when I installed adb, I could not see the phone with the adb devices command, yet I could see the phone in the Matt utility as well as in RSD Lite. I'll give it a shot again, can't hurt. Called Moto and they escalated it and are sending me a replacement device.
Hello,
I have a stock RAZR HD and I'm living in Germany. I tried sideloading KitKat on the device since I won't get the OTA update but during the upgrade the device rebooted and is now in a boot loop. In recovery, no matter what key combination I use, I won't show any of the menues to update, factory reset etc. Is the device a lost cause? I was reading through the Droid Razor HD Utility 1.32 and that seems like a way to recover, but I'm a little hesitant.
Any guidence would be greatly appreciated.
Zlynt said:
Hello,
I have a stock RAZR HD and I'm living in Germany. I tried sideloading KitKat on the device since I won't get the OTA update but during the upgrade the device rebooted and is now in a boot loop. In recovery, no matter what key combination I use, I won't show any of the menues to update, factory reset etc. Is the device a lost cause? I was reading through the Droid Razor HD Utility 1.32 and that seems like a way to recover, but I'm a little hesitant.
Any guidence would be greatly appreciated.
Click to expand...
Click to collapse
At the recovery image, press and hold vol up then press power and hold both for about 2 seconds and then let go of both buttons. You'll be in the new recovery. Install the ota again to complete the upgrade.
It's a two stage install. The first time you install the OTA, it replaces the recovery if it senses it's an older recovery and then it reboots you back to the recovery image of Andy lying on his back with a red ! over him. This is where you must do the vol up + power to go back into the recovery. They changed the key combination on is with the new recovery. If you don't go into recovery, it will then proceed to attempt and boot into your phone but it won't be able to so it will reboot again.
Once you are back in recovery after the reboot, go and install the OTA again. This time, it will upgrade your phone to KitKat. It could take up to 15 minutes so be patient.
Sent from my DROID RAZR HD using Tapatalk
Zlynt said:
Hello,
I have a stock RAZR HD and I'm living in Germany. I tried sideloading KitKat on the device since I won't get the OTA update but during the upgrade the device rebooted and is now in a boot loop. In recovery, no matter what key combination I use, I won't show any of the menues to update, factory reset etc. Is the device a lost cause? I was reading through the Droid Razor HD Utility 1.32 and that seems like a way to recover, but I'm a little hesitant.
Any guidence would be greatly appreciated.
Click to expand...
Click to collapse
dont ust the razr utility, if parts of the ota flashed (sounds like it did) before you got stuck, it will just continue to bootloop.
were you running the stock us verizon xt926 software before you sideloaded the ota?
is your bootloader locked or unlocked?
bweN diorD said:
dont ust the razr utility, if parts of the ota flashed (sounds like it did) before you got stuck, it will just continue to bootloop.
were you running the stock us verizon xt926 software before you sideloaded the ota?
is your bootloader locked or unlocked?
Click to expand...
Click to collapse
Hi, thanks for replying. I was running stock verizon software and the bootloader is locked.
Zlynt said:
Hi, thanks for replying. I was running stock verizon software and the bootloader is locked.
Click to expand...
Click to collapse
with your bootloader being locked and you cant get into recovery (im assuming you tried Ibolski's tip and still cant get in), you should wait for the fxz to get leaked. sorry but any other path is risky and likely to make your phone unrecoverable.
bweN diorD said:
with your bootloader being locked and you cant get into recovery (im assuming you tried Ibolski's tip and still cant get in), you should wait for the fxz to get leaked. sorry but any other path is risky and likely to make your phone unrecoverable.
Click to expand...
Click to collapse
Hi, ok i didn't see or try that trick. Yes if I hold vol up and hit power, i can now get into the recovery menu. I think though I need to use a different file to upgrade to Kitkat. Is there a copy out there that doesn't require all the tweaking to that i can just load onto my sd card and apply? I think that's what's messed this up is the file i used I just tried to install like previous files.
Zlynt said:
Hi, ok i didn't see or try that trick. Yes if I hold vol up and hit power, i can now get into the recovery menu. I think though I need to use a different file to upgrade to Kitkat. Is there a copy out there that doesn't require all the tweaking to that i can just load onto my sd card and apply? I think that's what's messed this up is the file i used I just tried to install like previous files.
Click to expand...
Click to collapse
there is no other file.
you need to flash the ota again in recovery.
the file first flashes the new recovery, then reboots to install the remaining files.
what you are experiencing is normal. flash again and the install should complete.
bweN diorD said:
there is no other file.
you need to flash the ota again in recovery.
the file first flashes the new recovery, then reboots to install the remaining files.
what you are experiencing is normal. flash again and the install should complete.
Click to expand...
Click to collapse
thanks, i'll try again. However, since my phone has been boot looping i now have a low battery. any hints on how to charge while in a boot loop? Can i just run this while attached to power? I have a moto cable and charger.
Zlynt said:
thanks, i'll try again. However, since my phone has been boot looping i now have a low battery. any hints on how to charge while in a boot loop? Can i just run this while attached to power? I have a moto cable and charger.
Click to expand...
Click to collapse
When i try to install from SD it shows:
install /sdcard ...
Installation aborted
Not sure if this is because of the low battery or not. I started the process from http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/ however RSD never shows my device, however I know it works as from within the RAZR HD utility, it sees the device.
I'm really not sure what to try next.
Zlynt said:
When i try to install from SD it shows:
install /sdcard ...
Installation aborted
Not sure if this is because of the low battery or not. I started the process from http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/ however RSD never shows my device, however I know it works as from within the RAZR HD utility, it sees the device.
I'm really not sure what to try next.
Click to expand...
Click to collapse
being locked you cant use that link to fix it as some of the KK files (recovery at least) should have flashed and it will brick you.
also, if any kk files flashed razr utility will brick you
im going to have to revert back to what i said in post 5 at this point. sorry im not sure what else you can try that wont make this worse.
as for the charging, if it wont charge, you will need a moto factory adapter (google it) to flash the fxz when it leaks. they are $10 from team black hat and bypass the battery while flashing. it will not charge the battery it just powers the phone directly for those with a low/dead battery.
I was trying to fix boot loop and completely hard bricked my phone. I can only get into AP Fastboot Flash Mode (Secure) in bootloader. I have been trying to flash it with windows batch file copied into firmware folder but not getting anywhere.
'No valid operating system could be found' on the screen when its not in bootloader.
Please help flash the stock ROM.
Thanks
How I fixed my Z4 XT1980-3
TLDR, try downloading and using the Lenovo Moto Smart Assistant (LMSA) tool
Yesterday I was trying to root my new Z4 and flashed a magisk patched boot img after I got the bootloader unlocked, and I'm pretty sure I ended up exactly where you are. I panicked, tried to do a recovery, a factory reset, nada and got suck in fastboot (apparently that's a Motorola thing). Then I stumbled on a thread elsewhere referring to the Lenovo Moto Smart Assistant (LMSA) tool.
I downloaded it thinking it couldn't hurt. After I started the program and waited through the stupid splash screen, I connected my device (which my PC could no longer detect) and it immediately began installing the Motorola drivers (by that point I had uninstalled just about everything).
I used the rescue function, chose my model, and it downloaded the stock rom. After about an hour, it finished and I started the rescue process. It went through fine until it got to 47%, and then it seemed to hang. After I waited (probably not long enough), I restarted fastboot and unplugged then plugged my phone back in, and it installed the rom and restarted. Back to stock! Not rooted, but working with the BL still unlocked. Yay!
I was shocked at how easy it was, I got cocky and immediately proceeded to soft brick it again. I thought I was better off this time because I wasn't stuck in fastboot, but using the LMSA program was not successful several times. Some times it told me my device wasn't compatible, other times it would just fail. After messing around with it all afternoon, I was where I was the night before--no phone. I was bummed and figured I deserved it, but kept messing with it. I rebooted and had the program redownload the rom, tried it again, and it worked!
No idea if this is the same problem or if it can work for you, but probably can't make it worse? --A
aurelya.hyjal said:
TLDR, try downloading and using the Lenovo Moto Smart Assistant (LMSA) tool
Yesterday I was trying to root my new Z4 and flashed a magisk patched boot img after I got the bootloader unlocked, and I'm pretty sure I ended up exactly where you are. I panicked, tried to do a recovery, a factory reset, nada and got suck in fastboot (apparently that's a Motorola thing). Then I stumbled on a thread elsewhere referring to the Lenovo Moto Smart Assistant (LMSA) tool.
I downloaded it thinking it couldn't hurt. After I started the program and waited through the stupid splash screen, I connected my device (which my PC could no longer detect) and it immediately began installing the Motorola drivers (by that point I had uninstalled just about everything).
I used the rescue function, chose my model, and it downloaded the stock rom. After about an hour, it finished and I started the rescue process. It went through fine until it got to 47%, and then it seemed to hang. After I waited (probably not long enough), I restarted fastboot and unplugged then plugged my phone back in, and it installed the rom and restarted. Back to stock! Not rooted, but working with the BL still unlocked. Yay!
I was shocked at how easy it was, I got cocky and immediately proceeded to soft brick it again. I thought I was better off this time because I wasn't stuck in fastboot, but using the LMSA program was not successful several times. Some times it told me my device wasn't compatible, other times it would just fail. After messing around with it all afternoon, I was where I was the night before--no phone. I was bummed and figured I deserved it, but kept messing with it. I rebooted and had the program redownload the rom, tried it again, and it worked!
No idea if this is the same problem or if it can work for you, but probably can't make it worse? --A
Click to expand...
Click to collapse
I really appreciate your reply.
I have tried LMSA tool but it's failing once I select the model number "Failed to match the connected device. Please plug it out and try again.". I have attached the screenshot.
Motorola ADB Interface driver is installed just like you described.
I think the bootloader is locked (Verizon ver.) and don't think there is any way to unlock it.
Thanks again for looking into this.
pate201 said:
I really appreciate your reply.
I have tried LMSA tool but it's failing once I select the model number "Failed to match the connected device. Please plug it out and try again.". I have attached the screenshot.
Motorola ADB Interface driver is installed just like you described.
I think the bootloader is locked (Verizon ver.) and don't think there is any way to unlock it.
Thanks again for looking into this.
Click to expand...
Click to collapse
UPDATE:
I managed to flashed stock ROM successfully without any error. But the phone is still in boot loop at logo instead of bootloader screen. Baseband is <not found> when booting into fastboot mode. LMSA tool still failing to to match the connected device. Verizon Software Upgrade Assistant is recognizing the phone in fastboot mode and trying to repair but software is not installing downloaded updates; it is stuck at 0% even won't do anything.
I think, I need to fix the Baseband but not sure what to do.
Thanks
I'm pretty confused where you are in the process.
Your device is Verizon? My understanding (and I could be wrong) is that Verizon devices can't have their bootloader unlocked, and without unlocking the bootloader, you can't flash a new ROM.
So, is your BL unlocked?
I specifically got the unlocked Amazon variant Z4 XT1980-3 hoping I could unlock the BL and root. I was able to do both, but I could only root after I got the BL unlocked.
I think I could upload my baseband file if you want to play around, but I have no idea if you're gonna brick your device. I'd check around in other forums/online and see what you can find out. I got the z4 because it was super cheap (comparatively) so if I killed it I wouldn't feel too bad buying a replacement. But $$'s still $$.
GL man!
aurelya.hyjal said:
I'm pretty confused where you are in the process.
Your device is Verizon? My understanding (and I could be wrong) is that Verizon devices can't have their bootloader unlocked, and without unlocking the bootloader, you can't flash a new ROM.
So, is your BL unlocked?
I specifically got the unlocked Amazon variant Z4 XT1980-3 hoping I could unlock the BL and root. I was able to do both, but I could only root after I got the BL unlocked.
I think I could upload my baseband file if you want to play around, but I have no idea if you're gonna brick your device. I'd check around in other forums/online and see what you can find out. I got the z4 because it was super cheap (comparatively) so if I killed it I wouldn't feel too bad buying a replacement. But $$'s still $$.
GL man!
Click to expand...
Click to collapse
You are right, it is a Verizon (XT1980-4) device and I cannot get the bootloader unlocked. I was only trying flash stock to unbrick it. I flashed the stock VZW firmware that I found somewhere without any error using fastboot.
Sure, I can give it a try with your baseband file. I already have stock Flash ready to re-flash it if necessary, and my device is not in working condition so nothing to loose.
Thanks for you reply.
I'll try to do that tonight when I get home from work. Sorry my responses have been so dumb. I'm still figuring it all out.
I would also need help to flash stock ROM. I have Z4 XT1980-3 with BL LOCKED. Already tried to reflash factory image via fastboot after an unsuccessful OTA upgrade. I can flash all parts except of boot, dspso and vbmeta. For these I get a "Preflash validation failed" error. So I have not been able to flash an entire factory image. I can only go to fastboot mode, nothing else. LMSA says my device is not compatible. RSD Lite says my device can not be switched to fastboot mode (but I already am in fastboot mode ???). So no joy with these. Can anybody give me any advice how to reanimate my device?
Maheshwara said:
I would also need help to flash stock ROM. I have Z4 XT1980-3 with BL LOCKED. Already tried to reflash factory image via fastboot after an unsuccessful OTA upgrade. I can flash all parts except of boot, dspso and vbmeta. For these I get a "Preflash validation failed" error. So I have not been able to flash an entire factory image. I can only go to fastboot mode, nothing else. LMSA says my device is not compatible. RSD Lite says my device can not be switched to fastboot mode (but I already am in fastboot mode ???). So no joy with these. Can anybody give me any advice how to reanimate my device?
Click to expand...
Click to collapse
I am also on same boat with Z4 XT1980-4 Verizon model. Bootloader is locked and Baseband missing on the fastboot screen. Please help if anyone have recover their phone from this.
Thanks