Database Info

[Q] If Wi-Fi Xoom is bricked, can (RSD) flashing the 3G SBF, then fastbooting work?

Damn, I can't fit the whole question in the subject.
Let's say someone hypothetically bricked their wifi Xoom. Can't connect with fastboot anymore. However, it does get picked up by RSD Lite.
If the Wi-Fi Xoom is bricked, can flashing the 3G SBF using RSD Lite be used JUST to enable fastboot? And if so, would just doing a "fastboot flash boot boot.img" and "fastboot flash system system.img" (with the right wi-fi files) be able to save it? And possibly the same with recovery.img?
I noticed that the boot.img and system.img files are the same size between the wifi version and the 3G/4G. Same with the recovery partition. That's why I ask.

If you can enable fastboot using RSD then I don't see why you wouldn't be able to unbrick it.
If I were you I would try it. I don't think you can brick anymore than what it already is
Sent from my Xoom using Tapatalk

Kas206 said:
If you can enable fastboot using RSD
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1037094
when i hold power and Volume up restart the xoom and hold power + volume down its show
failed to boot LNX 0x0004
Starting Fastboot protocol support
but the problem the computer not Recognize on the xoom . i installing drivers and still not Recognize
whats i do ?
i have Windows and Mac

try uninstalling your drivers and use this to reinstall
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.0.40_Driver_4.9.0.exe

A Question very important?
Xoom wifi is good or the xoom 3g? information about it,, I appreciate it

At this moment, I can only get the wifi version in Canada. I don't know if I would need it on 3G/4G.
Dinar, I assume you used to be able to connect? But not after the 0x0004 error? Can you get in RSD mode at all? When you are in Fastboot mode, does "fastboot devices" on your computer show a device?

What's wrong with that appears in the
Scourge1024 said:
Dinar, I assume you used to be able to connect? But not after the 0x0004 error? Can you get in RSD mode at all? When you are in Fastboot mode, does "fastboot devices" on your computer show a device?
Click to expand...
Click to collapse
no not show a device
when i connect a xoom in computer the computer never show the xoom
Scourge, what is the error message in your xoom?

It was something like LNX 0x0004 and the following message was about Fastboot or RSD mode 2. It changed depending on if I held the down button on reboot. I lost the ability to scroll through the boot options.
I couldn't get fastboot, adb or RSD Lite to see my Xoom in either mode.

Did you get RSDLite to flash the .sbf file? I tried that on my bricked device and I couldn't see anything happening on the screen of the xoom. I waited for about one or two minutes and stopped the process. What about the drivers? Are there different drivers for adb, fastboot and RSDLite? I have motohelper installed and it says all necessary drivers are installed. Can it be a driver issue? Thats something I haven't tried.

My Motohelper updated itself and I was still not connecting with my first Xoom. There are different drivers. Different ones become active depending on what mode you're in.
But I couldn't even see my Xoom so I declared it bricked as of April 14th at 3:47am. I seriously don't know the exact time.
When I use adb or fastboot from my Mac, I don't need drivers. It just works.

i have Mac and Windows same problem not show xoom
give me steps for the mac i want try

mine is just like yours says failed image LNX 0x0002
starting rsd mode 2
will cycle with the power and up button to the above. push the down button says it is in the fastboot protocol mode but computer doesn see it. cmd module says waiting on device. have current usb drivers. anybody out there can repair it. moto wants an arm and a leg for a repair because it was fastboot oem unlocked and voided warranty

Yeah, if nothing can see it... What exactly does Motorola want to charge to fix it? Can't you return it to where you bought and get an exchange? I'd only feel okay with that if you bought at a big store though and not a mom and pop sorta shop.

I dont know if this will help, but I noticed that in your first post your commands may not be complete:
fastboot flash boot boot.img
fastboot flash system system.img
Your are missing the words in red above. I may be wrong and you dont need them, but Im sure you do. At least all I got was a bunch of command options scroll in my command prompt without the entire command.
I thought I had a bricked xoom after messing around with the frameworks-res.apk through "root explorer" app. I flashed the boot.img like crazy, but it was my frameworks that I had messed with last before the locked boot sequence. I found an image on the boards for the 3g system.img and I was back in business.

cvela said:
I dont know if this will help, but I noticed that in your first post your commands may not be complete:
fastboot flash boot boot.img
fastboot flash system system.img
Your are missing the words in red above. I may be wrong and you dont need them, but Im sure you do. At least all I got was a bunch of command options scroll in my command prompt without the entire command.
I thought I had a bricked xoom after messing around with the frameworks-res.apk through "root explorer" app. I flashed the boot.img like crazy, but it was my frameworks that I had messed with last before the locked boot sequence. I found an image on the boards for the 3g system.img and I was back in business.
Click to expand...
Click to collapse
I did the same. Only thing is after I had WiFi showing "Error" under it and it wouldn't start. Had to insmod the bcm4329.ko and I was back in business.

Scourge1024 said:
Yeah, if nothing can see it... What exactly does Motorola want to charge to fix it? Can't you return it to where you bought and get an exchange? I'd only feel okay with that if you bought at a big store though and not a mom and pop sorta shop.
Click to expand...
Click to collapse
i sent it back to moto

cvela said:
I dont know if this will help, but I noticed that in your first post your commands may not be complete:
fastboot flash boot boot.img
fastboot flash system system.img
Your are missing the words in red above. I may be wrong and you dont need them, but Im sure you do. At least all I got was a bunch of command options scroll in my command prompt without the entire command.
I thought I had a bricked xoom after messing around with the frameworks-res.apk through "root explorer" app. I flashed the boot.img like crazy, but it was my frameworks that I had messed with last before the locked boot sequence. I found an image on the boards for the 3g system.img and I was back in business.
Click to expand...
Click to collapse
You are correct. I'll fix my first post!

I'm getting all the same side effects here from attempting to re-lock the wi/fi xoom. Im debating on what to do here.

Oohh... Relocking is not good... If the images aren't exact factory ones, that's a sure brick. No point in relocating the Wi-Fi version. At least not right now.
If RSD Lite and Fastboot can't see it, look for your receipt...

haa yeah. Thats too bad that I'm just a fewww days over my 14 day store warranty and didnt buy the insurance. I sent in a repair order online where i ship it back to them.....dont know if illl ever get anything back though ha

Help With semi-bricked xoom

I searched but I didn't see a solution to my particular problem, so please excuse me if I have over-looked the answer.
I was trying to restore my Xoom (US Verizon 3g) to MZ600_HRI66 (from Moto Dev website) from the latest Tiamat Rom. I flashed boot.img through fastboot with no problem, however when I tried to flash recovery.img I got "Flashed image is larger than partition size, Failed to process command(0x2)". Now when I reboot it is stuck at "Starting RSD mode 3". I can hold volume up + power and then immediately press volume down and the xoom goes into fastboot (but doesn't say it on the screen, just the dual core splash). I flashed boot.img again which finished with no problems, but still reboots to the "starting rsd mode 3". Is there anything that I can do? Based on the error message, if I can change the partition sizes then I should be able to flash everything, but is that possible through fastboot?

brentz said:
I searched but I didn't see a solution to my particular problem, so please excuse me if I have over-looked the answer.
I was trying to restore my Xoom (US Verizon 3g) to MZ600_HRI66 (from Moto Dev website) from the latest Tiamat Rom. I flashed boot.img through fastboot with no problem, however when I tried to flash recovery.img I got "Flashed image is larger than partition size, Failed to process command(0x2)". Now when I reboot it is stuck at "Starting RSD mode 3". I can hold volume up + power and then immediately press volume down and the xoom goes into fastboot (but doesn't say it on the screen, just the dual core splash). I flashed boot.img again which finished with no problems, but still reboots to the "starting rsd mode 3". Is there anything that I can do? Based on the error message, if I can change the partition sizes then I should be able to flash everything, but is that possible through fastboot?
Click to expand...
Click to collapse
When you are in RSD mode3 you did something wrong. It's hard to tell what just from your description. No way that the moto stock recovery image should be too big for the partition.
Before you start changing your partition sizes, first see if there is anyway (by any combinations of key presses) that you can actually enter fastboot protocol on your Xoom. This happened to me once (different cause) and I managed to get to fastboot somehow, but I was sweating bullets. you could try searching "recovery from RSD Mode3 on Xoom" and see if you can get more assistance. There's also a factory (programming) cable I picked up from Black Hat, that will save your bacon. You can also make one (I'm told) if you're handy with a soldering iron.
Don't panic...good luck!

Strange... I followed the exact same steps but this time it worked. Thanks anyway, I don't understand why but now it works.
EDIT: Actually, I did disconnect from my computer, and then I decided to try again so I reconnected it. May be a problem with the installation or something, IDK, but I got it working now, almost gave myself a hemorrhoid from squeezing so hard...

brentz said:
Strange... I followed the exact same steps but this time it worked. Thanks anyway, I don't understand why but now it works.
Click to expand...
Click to collapse
So glad you're all set!

[Q] Can't unbrick. Tried nigh everything.

Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=

If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!

Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
As Always If This Was Helpful Hit the Thanks!

Yeah, what Mjamocha said...

okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.

okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?

Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.

slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.

Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.

slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.

I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.

slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).

Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?

slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?

How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.

slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?

I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?

I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium

I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?

cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium

[Q] Noob Alert! Razr HD xt926 stuck in AP Fastboot. Root, locked bootloader.

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

[Q] Moto G stuck; recovery fails from boot menu: Can I reflash the stock firmware?

I have a Moto G that has gotten "stuck", if that's a good description. If I start it, the initial Moto splash screens go fine and then it becomes a dark screen but backlight On and just stays stuck there for ever. (Is this what is called a boot loop? Not sure)
By using the Power + Down Vol key combo I did manage to get it to the boot menu. Unfortunately the Recovery Option there does not work. Shows a quick Moto bootup splash screen, then Says "Boot up failed" and falls to the boot menu again.
What's my best bet to recover from this?
I did install adb + fastboot on my laptop & then connected the Moto G with a USB Cable. fastboot seems to work. I could get the phone to reboot, and some other basic diagnostics. e.g. "fastboot oem get_unlock_data works". "fastboot devices" also shows my device Serial Number correctly. But I want to be careful before I issue any further erase or flash commands so I thought it best to post on here. What is the logical next step in the debug?
"adb devices" did not succeed.
The phone had the original Google / Motorola software so far and I'd never even attempted to flash it etc. Only whatever automatic updates got pushed by Google / Moto / Carrier over the network. Right before this happened I was in a call and got a bunch of pop ups saying Application xxx was being shut down.
The phone is out of warranty. It is still locked, but when I enter the details on the Moto Website it says it can be unlocked. So I can proceed to get the unlock codes etc. if that helps.
The exact SKU is XT1033. Boot menu says (Version 41.13; Battery OK; Device is locked; Status Code 0) if that is of any help. Was a Dual SIM phone on a GSM Carrier.

Tried issuing the commands
Code:
fastboot erase cache
fastboot erase userdata
Both don't seem to have helped at all.
Any other ideas?

To flash anything you first need to unlock bootloader. Doing that erases all your data including internal memory. Then you can flash a recovery & a custom rom.

legolas06 said:
To flash anything you first need to unlock bootloader. Doing that erases all your data including internal memory. Then you can flash a recovery & a custom rom.
Click to expand...
Click to collapse
Thanks @Legolas!
I did not realize that. So I guess if I just tried a flashboot flash command it would fail since my phone is not unlocked at the moment.
Luckily I can get the unlock code from the Motorola site. I will proceed to do that then first and subsequently try all the other steps needing flashing.

What happened? Did you manage to boot it up?

@carefulcat : i have a similar problem as a well.let me know if and how you managed to fix it

Lucariel said:
What happened? Did you manage to boot it up?
Click to expand...
Click to collapse
@Lucariel
Sadly not. It is still lying dead.
If you have any ideas let me know!

ravibhat said:
@carefulcat : i have a similar problem as a well.let me know if and how you managed to fix it
Click to expand...
Click to collapse
No luck yet. If you find any ideas let me know!

@carefulcat :
Check out my thread @ http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
The only difference I find from what you've shared is that both of us have different bootloaders.
Let me know if this is true.

ravibhat said:
@carefulcat :
Check out my thread @ http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
The only difference I find from what you've shared is that both of us have different bootloaders.
Let me know if this is true.
Click to expand...
Click to collapse
Indeed. Very similar problems. Could be identical.
I've, in fact, even erased via fastboot & unlocked via motorola's site. Hasn't helped so far.
I haven't had the stomach to download a 500 MB stock firmware yet.
Who do you think our bootloader is different?

@carefulcat :
Well,I am on an unlocked unrooted Android L 5.0.2 XT1033 Asia Retail Edition (upgraded via OTA) which has Bootloader version 41.18.
You've just cleared the ROM it seems.
Unlocking the bootloader will wipe off all the data from your device.
It seems yours is still locked,you have the unlock code but didn't use it.
Which OS did you have?Exact version,region and type of upgrade.
And which commands have you used till now?
If you're clear with the basics try stocking a Stock Flash ROM (depending on your bootloader and previous OS) or custom recovery like TWRP or CW.
carefulcat said:
Indeed. Very similar problems. Could be identical.
I've, in fact, even erased via fastboot & unlocked via motorola's site. Hasn't helped so far.
I haven't had the stomach to download a 500 MB stock firmware yet.
Who do you think our bootloader is different?
Click to expand...
Click to collapse

carefulcat said:
@Lucariel
Sadly not. It is still lying dead.
If you have any ideas let me know!
Click to expand...
Click to collapse
Took it to a repair shop, the said something was wrong with my mother, they fixed that and now the phone enters into recovery, what wont boot.
Will try the "qhsusb_dload" thing this week.