Related
Hi all,
I build a image from AOSP for my Droid (motorola sholes).
It all went well, but the only way I know to flash those images into Droid are through: "fastboot -w flashall".
However, from my googling result, Droid doesn't seem to have fastboot mode.
(If there is a fastboot mode, can someone shows me how to enter it?)
If that is the case, how to flash those images into Droid without fastboot?
Many thanks for any help!
Good people, help:
Trying to install a mod from the camera of Nexus, rebooted, I see the icon lying android.
Tried to install xenonhd (4.2.2), reboot, and see the inscription on a black background:
Device is LOCKED. Status code: 0
Battery OK
Connect USB
Data Cable
failed to hab check for boot: 0x56
fastboot reason: boot failure
Please help me!
Sorry for bad English
Well you tried to flash a rom through stock recovery with a locked bootloader. Not the best decision. Go look at the tutorial in general.
Sent from my PACMAN MATRIX HD MAXX
iv-med said:
Good people, help:
Trying to install a mod from the camera of Nexus, rebooted, I see the icon lying android.
Tried to install xenonhd (4.2.2), reboot, and see the inscription on a black background:
Device is LOCKED. Status code: 0
Battery OK
Connect USB
Data Cable
failed to hab check for boot: 0x56
fastboot reason: boot failure
Please help me!
Sorry for bad English
Click to expand...
Click to collapse
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
skeevydude said:
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
Click to expand...
Click to collapse
i have the same problem but flashing back to stock rom with rsd will not work
I get a 1/23 partition type erro
and myth will now work due to fastboot, adb and attrib is not known as and internal or external command
skeevydude said:
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
Click to expand...
Click to collapse
Having this same problem when trying ota Kit Kat update from T-Mobile. The only way I can get back into 4.2.2 is to use Minimal Fastboot and give the command 'fastboot erase cache'. Even when I do this the phone never says if the cache erasure is complete but Minimal Fastboot says that it is. I have RSD lite installed on my CPU but can't seem to find a working link to the stock T-Mo images. Any help would be appreciated.
Just to add...if I attempt ota I get 'failed to hab check boot'. When trying to boot into recovery I get 'failed to hab check recovery'.
Edit: could I just unlock and root to solve this problem? If so, would someone point me to a different method than the Moto Toolkit found here? It doesn't recognize my moto even though all drivers and Motorola Device Manager are installed.
Sent from my XT1053 using Tapatalk
Ota KitKat update?
What phone do you have?
I have the T Mobile motomaker. Solved the problem with RSD Lite and factory Kit Kat images.
Sent from my Galaxy Nexus using Tapatalk
Hey guys I'm not exactly experienced with troubleshooting these kinds of problems. Hopefully I can learn something with the help of the community. I'll go ahead and lay out the situation and problem.
Problem:
Whenever I flash a rom with CWM, the phone will either A: Get stuck on a blank screen with the green LED on or B: Go through the boot animation and crash on "preparing android" and loop the process.
Info:
My AT&T Atrix HD has an unlocked bootloader, I have had several successful flashes in the past, and they have all worked well. I am able to flash the stock firmware back to the phone and it will load just fine. I have tried to go back to stock and start over, but I keep getting the same result. I've tried multiple roms with no change. This started happening when I was trying to load HoloBlur X according to the directions. It went through the whole installation in CWM without errors, but boot looped until it went dead. I did format and clear all the caches and all that too.
I'm not really sure what I'm missing here. I just hope someone might have a suggestion for me.
Thanks in advance for any help!
you could try format system in cwm
frog1982 said:
you could try format system in cwm
Click to expand...
Click to collapse
Thank you, and I appreciate the suggestion, but I have done that multiple times with no change in result.
Your positive your unlocked? Rooted?
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
Your positive your unlocked? Rooted?
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Absolutely positive.
I unlocked using the Motopocalypse method, and have rooted using Motochopper with the Mythtools tool.
does cwm say that it cannot mount the cache after flashing the rom
Safestrap VS. CWM
Austin Connell said:
Absolutely positive.
I unlocked using the Motopocalypse method, and have rooted using Motochopper with the Mythtools tool.
Click to expand...
Click to collapse
Are you using a version of Safestrap recovery or are you ABSOLUETLY positive that you are using a custom recovery? Most newer ROMs (4.1 and up) usually require you to use a custom recovery.
I'm sure he knows the difference between the 2.
Sent from my PACMAN MATRIX HD MAXX
Wipe and Restore
Hey guys I'm not exactly experienced with troubleshooting these kinds of problems. Hopefully I can learn something with the help of the community. I'll go ahead and lay out the situation and problem.
Problem:
Whenever I flash a rom with CWM, the phone will either A: Get stuck on a blank screen with the green LED on or B: Go through the boot animation and crash on "preparing android" and loop the process.
Info:
My AT&T Atrix HD has an unlocked bootloader, I have had several successful flashes in the past, and they have all worked well. I am able to flash the stock firmware back to the phone and it will load just fine. I have tried to go back to stock and start over, but I keep getting the same result. I've tried multiple roms with no change. This started happening when I was trying to load HoloBlur X according to the directions. It went through the whole installation in CWM without errors, but boot looped until it went dead. I did format and clear all the caches and all that too.
I'm not really sure what I'm missing here. I just hope someone might have a suggestion for me.
Thanks in advance for any help!
Click to expand...
Click to collapse
If you indeed are positive that you flashed the correct custom recovery, then follow these steps to fully Wipe, Restore to stock, and reflash.
Please read all of these steps before attempting to follow them!
** Note: I am not responsible for any damage done to your phone by following these instructions. **
Charge your device to a reccomended 80% (at least)
Make sure you have a Windows computer
Download the latest USB drivers from Motorola
Boot into your current recovery and make a nandroid backup, just in case.
Boot your device into Fastboot by powering off device and holding the Power+Volume Up+Volume Down and scrolling using the Volume Down button.
Plug your device into your computer
Download Fastboot if you don't already have it. (A simple Google search should result in a download link)
Type "fastboot erase data"
Type "fastboot erase cache"
Type "fastboot erase system"
Type "fastboot erase boot"
Type "fastboot reboot"
All of these commands should pass without conflict.
Your phone should reboot, but have no bootable OS. Don't panic if you get this error. Just manually power off your device and put it in bootloader mode once again (Power+Volume Up+Volume Down).
After that, follow these steps to flash to stock.
Download and install RSD Lite 6.1 here : www.mediafire.com/?3ckiknmwcpjolb2
Download the correct Fastboot Package for Jellybean here: http://sbf.droid-developers.org/dinara/list.php -- It should be MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip for 4.1.1 Jellybean on AT&T.
Make sure your phone is in bootloader mode with the directions in the first set of instructions and select Fastboot flash mode.
Open RSD Lite and select the downloaded Zip file in the box at the top.
Your device should appear at the list view towards the bottom of the screen. Click it and the "Start" button should be clickable. Click start and wait.
Wait for RSD Lite to say success and do not unplug it until the phone COMPLETELY BOOTS UP.
After all of this, you can now root, unlock bootloader, flash CWM, and install your custom rom. This should take care of any bootloops while installing Custom ROMs.
Click the thanks button if I helped!
PM me if you have any problems during this so I can help!
lol no, I'm not using a safestrap. I'm using a CWM Recovery.
I will give the rsd method a try tonight. thank you guys for all the help so far. luckily i have another phone to use in the meantime.
PHP:
Austin Connell said:
lol no, I'm not using a safestrap. I'm using a CWM Recovery.
I will give the rsd method a try tonight. thank you guys for all the help so far. luckily i have another phone to use in the meantime.
Click to expand...
Click to collapse
Okay. Make sure to tell us the results! Good luck!
I had very similar problems because I unwittingly attempted to flash the wrong cwm recovery file... which seems to have affected the Boatloader behaviour. I made it to #6 of the RSD steps in the help offered by lucasantarella (I was using RSD Lite 6.1.4), but the flash fails with:
Model Port No. Port Type IMEI / ESN / MEID Status Progress Result
Fastboot QINARA S 1 USB N/A Failed flashing process. Unknown fastboot command. (getvar) FAIL
Here's the complete story on the phone:
Brand new Factory Atrix HD, 4.1.1.
Installed MythTools (V1.1) on Windows XP and downloaded the USB Motorola Drivers
Used MythTools to unlock the bootloader
Installed superuser-4.3-beta2.zip
Installed ROM Manager 5.5.2.0 (which I can't use until the customized CWM for AHD is installed)
Downloaded mb886-cwm-6.0.3.6-touch-recovery-flashable-signed.zip
Using MythTools, I selected the wrong recovery file (selected a stock cwm instead) which failed to flash,
and the bootloader is now reporting a Flash failure. Here's the entire screen:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is UNLOCKED. Status Code: 3
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Flash Failure
usb connected
When I power it down and then hold the vol + and - together, I get the following menu:
Boot Mode Selection Menu (10.9B)
Vol Up Selects, Vol Down Scrolls
Available Boot Modes:
Normal Powerup
Recovery
AP Fastboot
Factory
BP Tools
Selecting any of those puts the AHD into the stock AT&T 4.1.1 normal screen and its ready for use.
Using Myth Tools to "Reboot normally" (option A) does the same thing as Option B, "Reboot to fastboot mode", which puts me back into the fastboot screen showing "Flash failure".
It appears that I'm locked to 4.1.1... because of Bootloader problems.
Any comments/thoughts/insight? It's been a year since I did any flash/RSD work and have poured over the various pages/threads on the AHD for the last three days... Apparently I didn't read enough...
Am currently using a Motorola Bravo running the CyanogenMod-72-20120506-NIGHTLY-Kobe and was hoping to migrate up to the AHD.
-ricer1
whew!!! The Atrix HD works!!!!
I thought my phone was crippled forever.. but I followed leanix's instructions here and am running epinter's rom on my Atrix HD:
http://forum.xda-developers.com/showthread.php?p=45306485#post45306485
Many thanks to leanix for posting his MUCH needed help.
- ricer1
lucasantarella said:
If you indeed are positive that you flashed the correct custom recovery, then follow these steps to fully Wipe, Restore to stock, and reflash.
Please read all of these steps before attempting to follow them!
** Note: I am not responsible for any damage done to your phone by following these instructions. **
Charge your device to a reccomended 80% (at least)
Make sure you have a Windows computer
Download the latest USB drivers from Motorola
Boot into your current recovery and make a nandroid backup, just in case.
Boot your device into Fastboot by powering off device and holding the Power+Volume Up+Volume Down and scrolling using the Volume Down button.
Plug your device into your computer
Download Fastboot if you don't already have it. (A simple Google search should result in a download link)
Type "fastboot erase data"
Type "fastboot erase cache"
Type "fastboot erase system"
Type "fastboot erase boot"
Type "fastboot reboot"
All of these commands should pass without conflict.
Your phone should reboot, but have no bootable OS. Don't panic if you get this error. Just manually power off your device and put it in bootloader mode once again (Power+Volume Up+Volume Down).
After that, follow these steps to flash to stock.
Download and install RSD Lite 6.1 here : www.mediafire.com/?3ckiknmwcpjolb2
Download the correct Fastboot Package for Jellybean here: http://sbf.droid-developers.org/dinara/list.php -- It should be MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip for 4.1.1 Jellybean on AT&T.
Make sure your phone is in bootloader mode with the directions in the first set of instructions and select Fastboot flash mode.
Open RSD Lite and select the downloaded Zip file in the box at the top.
Your device should appear at the list view towards the bottom of the screen. Click it and the "Start" button should be clickable. Click start and wait.
Wait for RSD Lite to say success and do not unplug it until the phone COMPLETELY BOOTS UP.
After all of this, you can now root, unlock bootloader, flash CWM, and install your custom rom. This should take care of any bootloops while installing Custom ROMs.
Click the thanks button if I helped!
PM me if you have any problems during this so I can help!
Click to expand...
Click to collapse
Hey i tried this in bot rsd lite and myth tools but it won't work
I can't get back into recovery, or boot up the phone. it only boot into fast boot
my phone is locked and status code 0
I really don't know what to do.
when I use myth tools is says fastboot not found or as a command on internal or externel
or attrib internal or external
please help me
alki1979 said:
Hey i tried this in bot rsd lite and myth tools but it won't work
I can't get back into recovery, or boot up the phone. it only boot into fast boot
my phone is locked and status code 0
I really don't know what to do.
when I use myth tools is says fastboot not found or as a command on internal or externel
or attrib internal or external
please help me
Click to expand...
Click to collapse
Follow this guide http://forum.xda-developers.com/showthread.php?t=2259661
Having a tough time going back to stock. Decided to give lucasantarella's wipe and restore process a go. At step #8 I got this:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>fastboot devices
TA30001GGN fastboot
C:\>fastboot erase data
erasing 'data'...
Invalid partition name data
FAILED (remote failure)
finished. total time: 0.105s
C:\>
I've ensured that I have the latest drivers installed and have the latest fastboot. Any help on what to try next would be appriciated. Thanks.
Edit: Would trying leanix's post on using the command lines be advisable for me at this time? PhilZ touch and CM 11 are currently installed on my device. PhilZ seems to run ok but clearing the dalvik cache doesnt seem to work and all I get is the arrow spinning around CM's head on bootup.
ifixgse said:
Having a tough time going back to stock. Decided to give lucasantarella's wipe and restore process a go. At step #8 I got this:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>fastboot devices
TA30001GGN fastboot
C:\>fastboot erase data
erasing 'data'...
Invalid partition name data
FAILED (remote failure)
finished. total time: 0.105s
C:\>
I've ensured that I have the latest drivers installed and have the latest fastboot. Any help on what to try next would be appriciated. Thanks.
Edit: Would trying leanix's post on using the command lines be advisable for me at this time? PhilZ touch and CM 11 are currently installed on my device. PhilZ seems to run ok but clearing the dalvik cache doesnt seem to work and all I get is the arrow spinning around CM's head on bootup.
Click to expand...
Click to collapse
If you're trying to wipe user data/do factory reset through fastboot, try "fastboot -w". Also are you using the snapdragon fastboot?
Sent from my MB886 using Tapatalk
Back Story:
I cracked the screen on my Moto X a few days ago and just received my insurance replacement. Before I send the old one back I want to return it to stock. I am attempting to do so using RSD Lite and the FXZ from the the Android Development section.
My problem is that the usb drivers are not installing correctly! I downloaded the device manager, and when my phone connects and Windows says it is installing driver software it returns this error. (see attached)
As a result, I cannot get the phone to be recognized by RSD Lite, therefore not being able to return to stock.
PLEASE HELP!
Troubleshooting up to this point:
-Uninstalled and reinstalled drivers
-rebooted computer
-rebooted phone
-tried different usb ports
-tried new phone
In case I cannot resolve this issue, is there another way to return to stock? I really don't think Asurion will like me very much when they try to factory reset this phone and nothing happens
jmcharles said:
Back Story:
I cracked the screen on my Moto X a few days ago and just received my insurance replacement. Before I send the old one back I want to return it to stock. I am attempting to do so using RSD Lite and the FXZ from the the Android Development section.
My problem is that the usb drivers are not installing correctly! I downloaded the device manager, and when my phone connects and Windows says it is installing driver software it returns this error. (see attached)
As a result, I cannot get the phone to be recognized by RSD Lite, therefore not being able to return to stock.
PLEASE HELP!
Click to expand...
Click to collapse
I had this issue too. Simply boot into the bootloader and choose BP Tools. Your computer should recognize it now. Also, make sure you have USB Debugging checked in developer options in the phone settings. If you are running Windows 8 you may run into issues running RSD Lite. If that is the case you can use fastboot to flash back to stock. Simply unzip the FXZ and place the fastboot files in the same folder. Then boot your phone into the bootloader. and connect your phone. Run the following commands:
cd C:\<the directory your files are in>
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin (optional: this is the boot logo)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem config carrier <carrier name>
fastboot oem fb_mode_clear
fastboot reboot
That should reset your phone. You may want to double check the oem commands against the ones listed in the xml file in the zip. I have the AT&T version and that's what I'm basing it off of.
EDIT:
You can also just flash the recovery partition and factory reset that way. However, it might not erase any root files. I've done some factory resets on other devices and maintained root.
EDIT 2:
I attached the fastboot files in case you needed them.
EDIT 3:
Just though of this. Make sure when you run RSD Lite that your phone is booted into the bootloader.
Thank you!
So...I tried to get it recognized using the Motorola drivers, but it just was not working. Instead, I attempted to update the drivers manually to Android ADB interface while in the bootloader. This worked, and my device was recognized. However, RSD Lite still failed to work, so I did it manually thru command prompt. I double checked all the commands with the Verizon XML file, and it worked!
Thank you for giving such an exhaustive reply. I am still unable to get the phone recognized with Motorola drivers, but the Android ADB drivers I already had on my computer seem to work. I'm not too smart on that stuff, so maybe someone can explain why this is and why I was able to get it to work.
jmcharles said:
So...I tried to get it recognized using the Motorola drivers, but it just was not working. Instead, I attempted to update the drivers manually to Android ADB interface while in the bootloader. This worked, and my device was recognized. However, RSD Lite still failed to work, so I did it manually thru command prompt. I double checked all the commands with the Verizon XML file, and it worked!
Thank you for giving such an exhaustive reply. I am still unable to get the phone recognized with Motorola drivers, but the Android ADB drivers I already had on my computer seem to work. I'm not too smart on that stuff, so maybe someone can explain why this is and why I was able to get it to work.
Click to expand...
Click to collapse
Glad to hear you were able to get your phone back to stock. I haven't figured out why it does that either. Never had that issue with my other phones and they were Motos too.
Sent from my XT1058 using XDA Premium 4 mobile app
File Error
Dark9781 said:
I had this issue too. Simply boot into the bootloader and choose BP Tools. Your computer should recognize it now. Also, make sure you have USB Debugging checked in developer options in the phone settings. If you are running Windows 8 you may run into issues running RSD Lite. If that is the case you can use fastboot to flash back to stock. Simply unzip the FXZ and place the fastboot files in the same folder. Then boot your phone into the bootloader. and connect your phone. Run the following commands:
cd C:\<the directory your files are in>
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin (optional: this is the boot logo)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem config carrier <carrier name>
fastboot oem fb_mode_clear
fastboot reboot
That should reset your phone. You may want to double check the oem commands against the ones listed in the xml file in the zip. I have the AT&T version and that's what I'm basing it off of.
EDIT:
You can also just flash the recovery partition and factory reset that way. However, it might not erase any root files. I've done some factory resets on other devices and maintained root.
EDIT 2:
I attached the fastboot files in case you needed them.
EDIT 3:
Just though of this. Make sure when you run RSD Lite that your phone is booted into the bootloader.
Click to expand...
Click to collapse
I'm very new to this. I got caught up in the PwnMyMoto boot loop after the Verizon OTA. I am trying to reload the phone back to Factory Default without root. When I try to use the commands above I get the error "Variable not supported! target reported max download size of 805306368 bytes
I have the files in the same directory as fastboot.exe so they are in the path. Can anyone tell me why I am getting this error, and what I can do to resolve it? Thanks
After reading a lot of threads, it seems like hope is not lost since the device is unlocked. However, the methods that have come up for fixing bricked phones require adb access and or USB debugging enabled.
The file system is also corrupted somehow because flashing TWRP results in hanging at the TWRP logo. CWM works until I make it do a function and the screen hangs.
Help is greatly appreciated
Edit: Trying ADB sideload with a rom or two on hand (CM 11 & 12) induces the error "...Can't install this package on incompatible data. Please try another package or run a factory reset"
> Tried to factory reset on CWM and it hangs, back to square one
But you obviously have fastboot access in fastboot mode?
Try erase commands from there and flash recovery. As last resort flash a factory image?
I get a 'Permission Denied; Remote Failure' error when attempting any of the fastboot erase commands
If you have fastboot you should be able to use either fastboot commands or rsdlite to flash back to 100% stock
Sent from my Moto X using Tapatalk
had same twrp hanging at logo recently after some mess. Here is what brought moto back to life
In the command prompt window type the following commands
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot reboot
this was a factory reset taken from here
https://forum.technofaq.org/discussion/54/motorola-guide-to-factory-reset-via-fastboot-bootloader
flash a rom