I'm having the same issue as in this thread: http://forum.xda-developers.com/showthread.php?t=2417726
But there was no resolution that the OP posted.
I was running the 9/13/13 PacMan rom when I tried to restart because the phone was running slow. When the phone booted back up, it was stuck at the unlocked bootloader message.I could get into CWM, I tried to reflash the rom, and wipe everything but nothing worked. I also tried flashing all 3 of the stock firmwares (found here: sbf.droid-developers.org/dinara/list.php) in RSDLite, but they all fail. I was trying to follow the instructions in post #6 of the other thread, but they weren't making sense to me..... what can I try. Currently I'm just sitting here at the fast boot screen.
Thanks
skatingrocker17 said:
I'm having the same issue as in this thread: http://forum.xda-developers.com/showthread.php?t=2417726
But there was no resolution that the OP posted.
I was running the 9/13/13 PacMan rom when I tried to restart because the phone was running slow. When the phone booted back up, it was stuck at the unlocked bootloader message.I could get into CWM, I tried to reflash the rom, and wipe everything but nothing worked. I also tried flashing all 3 of the stock firmwares (found here: sbf.droid-developers.org/dinara/list.php) in RSDLite, but they all fail. I was trying to follow the instructions in post #6 of the other thread, but they weren't making sense to me..... what can I try. Currently I'm just sitting here at the fast boot screen.
Thanks
Click to expand...
Click to collapse
When you use RSD, why does it fail? If it fails because it can't find the device, go into your device manager(assuming you have windows) and there is going to be a
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(I believe it says Full Android Emulator) right click that one and install the driver by choosing one and use the Motorola ADB driver. Replug the device then try again.
Now, if you are using RSD and the device is showing, is it failing due to the XML files being wrong? Remember you have to delete the GetVar max download size lines, there is two of them, as described here http://forum.xda-developers.com/showthread.php?t=2231249&highlight=rsd
When trying to flash: 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml
RSD Lite is giving the error: "Failed flashing process. Unknown fastboot command. (getvar)"
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC.xml
Error: "Failed flashing process. 1/23 flash partition "gpt_main0.bin" ->Phone returned FAIL."
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml
"Failed flashing process. Unknown fastboot command. (getvar)"
In Device Manager it says ADB Interface -> Mot Single ADB Interface.
I have use ADB commands with this computer to the ATRIX HD before so it should work.
In fast boot, I've noticed it says
"Fastboot reason: Flash Failure
usb connected
downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
UPDATE:
I have removed the "<step operation="getvar" var="max-download-size" />" lines from the .XMF files now I get the "Failed flashing process. 1/23 flash partition "gpt_main0.bin" ->Phone returned FAIL." on all the files.
Make sure the files are put on desktop and not a folder and try again going to stock
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
SVLAN said:
Make sure the files are put on desktop and not a folder and try again going to stock
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
Click to expand...
Click to collapse
That didn't seem to help. Before I just had them on the root of the D drive but I am getting the same errors from the desktop. Not sure if it matters, but I'm running RSD Lite 6.1.5.
Update: Tried 6.1.4... no luck.
Maybe running the rsdlite as admin?
Open a new Fastboot without usb connection to PC then connect and open rsdlite again and try. I had this problem before and playing with it i manage to flash stock. I forgot how exactly I did though. Just keep trying. I know one of my issues was to put the att stock rom on desktop
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
SVLAN said:
Maybe running the rsdlite as admin?
Open a new Fastboot without usb connection to PC then connect and open rsdlite again and try. I had this problem before and playing with it i manage to flash stock. I forgot how exactly I did though. Just keep trying. I know one of my issues was to put the att stock rom on desktop
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
Click to expand...
Click to collapse
Just tried that, I am now using a real Motorola USB cable too.
If I remove the "<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="900113B868E61E8FC4E59F72C0B67193" />" line from all the files, I get an error that says "Failed flashing process. 1/22 flash sbl1 "sbl1.mbn" -> USB error occurred while reading/writing." Otherwise, I get the error "Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> USB error occurred while reading/writing."
I'm not sure what I'm doing wrong here. This isn't my first Motorola phone, I've used RSD Lite before in the past as well as ODIN for Samsung phones and have never had any issues so difficult to solve. I'm not even sure what file I should be flashing. I came from the latest 4.1.1 then flashed 4.3 PacMan rom.
I tried another computer and getting the same errors in RSD Lite. In Myth Tools, it says it's flashing the firmware for about 15 minutes but when it reboots, it seems to just go right back into fastboot.
I tried to manually push something using fastboot and this is what I get:
D:\Parker\Desktop\Myth Tools - AHD>fastboot flash sbl1 sbl1.mbn
sending 'sbl1' (99 KB)...
OKAY [ 0.022s]
writing 'sbl1'...
Battery Low!!
FAILED (remote failure)
finished. total time: 0.283s
D:\Parker\Desktop\Myth Tools - AHD>
Click to expand...
Click to collapse
Is it failing BECAUSE the battery is low? It doesn't seem to be charging.
I bought the Motorola Factory Adapter from Team Black Hat. I saw on write-up on droid life on how to create one but I really don't have the time to do it.
Buying the adapter solved the problem.
Were you able to flash other ROMs successfully & stably after that? I've been in the same boat & can't get past a reboot after flashing a custom ROM.
bsmitty said:
Were you able to flash other ROMs successfully & stably after that? I've been in the same boat & can't get past a reboot after flashing a custom ROM.
Click to expand...
Click to collapse
Yes I was. I installed a different ROM but... I woke up after leaving it on the charger all night a few days ago and the phone was off. Getting the unlocked bootloader message again... the only way to get around it seems to be reflashing. It's really annoying.
skatingrocker17 said:
Yes I was. I installed a different ROM but... I woke up after leaving it on the charger all night a few days ago and the phone was off. Getting the unlocked bootloader message again... the only way to get around it seems to be reflashing. It's really annoying.
Click to expand...
Click to collapse
What was your previous stock fastboot used and what rom are you trying to flash? I ask this because our development is based off of 4.1.2 RAZR HD stock and I've noticed 4.1.1 only flashers here sometimes have issues. Since the unlock, my stock changed to 4.1.2 Mex Retail (manually flashed everything via fastboot) and I've only been stuck on the bootloader screen once (had to do the sticky bit fix ).
Also, if you're an ATT user, the Mex Retail radio will give you a better signal and I can say that with 100% confidence. My Dad and I both have Atrix HD's, his runs stock 4.1.1 unrooted and mine running anything with Mex Retail radio, I've had 2 bars of service in known dead zones and my Dad had no service less than a foot away -- and that's happened in multiple dead zone/bad signal areas.
How do I go about flashing just the radio and staying on pac? @skeevydude
Sent from my PACMAN MATRIX HD MAXX
I think this method will work to flash a new radio without affecting the rom. I installed the Mexico Retail radio onto Holoblur without affecting Holoblur at all.
Assuming you have a Windows machine:
1) install the adb/fastboot files to a single directory on my computer;
2) place the NON-HLOS.bin file you got from the desired rom in the adb/fastboot directory from step 1;
3) open a command prompt window as an administrator;
4) install the Motorola USB drivers and connect my booted phone with USB debugging enabled;
5) from the command line, type "adb reboot bootloader" and press the enter key to get my phone into AP Fastboot Flash mode;
6) from the command line, type "fastboot flash modem NON-HLOS.bin" and press enter; and
7) reboot the phone and check to made sure the baseband is the one you wanted.
audit13 said:
I think this method will work to flash a new radio without affecting the rom. I installed the Mexico Retail radio onto Holoblur without affecting Holoblur at all.
Assuming you have a Windows machine:
1) install the adb/fastboot files to a single directory on my computer;
2) place the NON-HLOS.bin file you got from the desired rom in the adb/fastboot directory from step 1;
3) open a command prompt window as an administrator;
4) install the Motorola USB drivers and connect my booted phone with USB debugging enabled;
5) from the command line, type "adb reboot bootloader" and press the enter key to get my phone into AP Fastboot Flash mode;
6) from the command line, type "fastboot flash modem NON-HLOS.bin" and press enter; and
7) reboot the phone and check to made sure the baseband is the one you wanted.
Click to expand...
Click to collapse
Ya forgot one step
0) download snapdragon-fastboots.zip from Batakang and use that everywhere a fastboot command is used
/can also install it with the Android terminal emulator and a dd....
//su
///dd if=/sdcard/NON-HLOS.bin of=/dev/block/mmcblk0p1
skeevydude said:
Ya forgot one step
0) download snapdragon-fastboots.zip from Batakang and use that everywhere a fastboot command is used
/can also install it with the Android terminal emulator and a dd....
//su
///dd if=/sdcard/NON-HLOS.bin of=/dev/block/mmcblk0p1
Click to expand...
Click to collapse
I just used the adb/fastboot included with Myth Tools. Not sure if those files will work for everyone though. I'm not very good at using Android terminal so I tend to stick with doing things from a Windows command prompt
audit13 said:
I just used the adb/fastboot included with Myth Tools. Not sure if those files will work for everyone though. I'm not very good at using Android terminal so I tend to stick with doing things from a Windows command prompt
Click to expand...
Click to collapse
Myth comes with the correct files. Very important to specify the correct fastboot because the stock sdk fastboot doesn't flash our images correctly and has led to a lot of confusion in the past.
skeevydude said:
Myth comes with the correct files. Very important to specify the correct fastboot because the stock sdk fastboot doesn't flash our images correctly and has led to a lot of confusion in the past.
Click to expand...
Click to collapse
Good advice for AHD owners to follow. Thanks.
skatingrocker17 said:
When trying to flash: 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml
RSD Lite is giving the error: "Failed flashing process. Unknown fastboot command. (getvar)"
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC.xml
Error: "Failed flashing process. 1/23 flash partition "gpt_main0.bin" ->Phone returned FAIL."
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml
"Failed flashing process. Unknown fastboot command. (getvar)"
In Device Manager it says ADB Interface -> Mot Single ADB Interface.
I have use ADB commands with this computer to the ATRIX HD before so it should work.
In fast boot, I've noticed it says
"Fastboot reason: Flash Failure
usb connected
downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
UPDATE:
I have removed the "<step operation="getvar" var="max-download-size" />" lines from the .XMF files now I get the "Failed flashing process. 1/23 flash partition "gpt_main0.bin" ->Phone returned FAIL." on all the files.
Click to expand...
Click to collapse
Old post, but still relevant issue. Hope this helps, anyone else getting these errors.
After unlocking bootloader and having flashed MX retail. When using RSDlite I had to remove the "getvar" lines. I've tried to flash back to ATT stock, but can not get past "gpt_main0.bin".
RSDlite can and will finish flash MX retail and Bell stock after editing out "getvar".
clockcycle said:
Old post, but still relevant issue. Hope this helps, anyone else getting these errors.
After unlocking bootloader and having flashed MX retail. When using RSDlite I had to remove the "getvar" lines. I've tried to flash back to ATT stock, but can not get past "gpt_main0.bin".
RSDlite can and will finish flash MX retail and Bell stock after editing out "getvar".
Click to expand...
Click to collapse
Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me an hour ago. RSD no longer recognizes my phone in fastboot mode even though it did two weeks ago. Myth Tools however does recognize my phone, it just won't complete the whole flashing process without "intervention".
btw I am running Windows 8.1 Pro 64bit, and nothing has changed on that.
When using fastboot (mfastboot) to flash manually through the command prompt I get the same error when flashing "gpt_main0.bin" and a few others. Back to Myth Tools,, I was having problems even starting it until I just double clicked on flashing.bat or main.bat instead of running it as administrator. After all I AM the admin of my PC. Then, it worked perfect...until flashing "tz.mbn", it sent it fine, but froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I unplugged the USB while leaving the Myth Tools window open, which disconnected the phone obviously. I plugged it back in and Myth continued from where it left off, with a failure where I unplugged it obviously. It didn't actually fail though.
(Note: I did this a few weeks ago when I lost my radios and manually flashed "NON-HLOS.bin", which froze, but I followed the same procedure and it successfully flashed it)
Anyway, it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone then repeated the sequence of unplugging and replugging the USB and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock. Well, I had to reflash my radio again, but that was easy.
FYI: My xml file has the two "getvar" lines removes due to my earlier attempts with RSD. Any questions don't hesitate to ask.
Related
Hi people, I have a big problem with my friend's Razr i, I was trying to root it, but i didn't want to unlock my bootloader so tried several methods but not a single one worked, So i tried the one for unlocked bootloaders and ended up bricking my device, Now It's stuck on fastboot mode.
I've tried to flash some brazilian firmwares via RSD lite, but it get stuck on "6/9 flashing radio_signed" SO PLEASE SOMEONE GUIDE ME TO THE SOLUTION WHAT AM I DOING WRONG?
PS: Also tried to flash an argentinian Firmware but it didn't even let me start flashing bringing the error "Faled flashing process. Unknown fastboot command. (getvar)"
PS2: Also tried the eternityprj Alternate method without RSD, and it gets stuck on flashing recovery... and it also prompts some errors you can see in the attached file.
HELP ME PLEASE AS I SAID THE RAZR IS A FRIEND'S PHONE NOT MINE, I NEED TO SAVE IT.
Vaizen said:
Hi people, I have a big problem with my friend's Razr i, I was trying to root it, but i didn't want to unlock my bootloader so tried several methods but not a single one worked, So i tried the one for unlocked bootloaders and ended up bricking my device, Now It's stuck on fastboot mode.
I've tried to flash some brazilian firmwares via RSD lite, but it get stuck on "6/9 flashing radio_signed" SO PLEASE SOMEONE GUIDE ME TO THE SOLUTION WHAT AM I DOING WRONG?
PS: Also tried to flash an argentinian Firmware but it didn't even let me start flashing bringing the error "Faled flashing process. Unknown fastboot command. (getvar)"
PS2: Also tried the eternityprj Alternate method without RSD, and it gets stuck on flashing recovery... and it also prompts some errors you can see in the attached file.
HELP ME PLEASE AS I SAID THE RAZR IS A FRIEND'S PHONE NOT MINE, I NEED TO SAVE IT.
Click to expand...
Click to collapse
your secure level was to high for a non bootloader method and if you done a method with a unlocked bootloader and your bootloader was locked thats bad.
unlock your bootloader >>WARRANTY VOID<< install cwm and use any backup. or flash the 39 gb fw but i think you have yet to unlokc the bootloader to safe it.. and be patient dont try to much stuff if your battery goes low you need a factory adapter or something like this to charge ur razr i if the battery is down.
regards hope you get it waorking again
I solved my problem this way
Vaizen said:
Hi people, I have a big problem with my friend's Razr i, I was trying to root it, but i didn't want to unlock my bootloader so tried several methods but not a single one worked, So i tried the one for unlocked bootloaders and ended up bricking my device, Now It's stuck on fastboot mode.
I've tried to flash some brazilian firmwares via RSD lite, but it get stuck on "6/9 flashing radio_signed" SO PLEASE SOMEONE GUIDE ME TO THE SOLUTION WHAT AM I DOING WRONG?
PS: Also tried to flash an argentinian Firmware but it didn't even let me start flashing bringing the error "Faled flashing process. Unknown fastboot command. (getvar)"
PS2: Also tried the eternityprj Alternate method without RSD, and it gets stuck on flashing recovery... and it also prompts some errors you can see in the attached file.
HELP ME PLEASE AS I SAID THE RAZR IS A FRIEND'S PHONE NOT MINE, I NEED TO SAVE IT.
Click to expand...
Click to collapse
Hello good morning
I brick 2 phones trying to get one of them and in the process did fail at 2, how the recovery?
1. - Use RSD Lite version 6.1.4
2. - Use 1 extra phone (htc wildfire root and backup CWMR in case of failure)
3. - Use a GB retail rom (CFC_8.7.1I-110_IFW-39_S7_UCASMI01E1017.0R_USASMIICSRTGB_P042_A005_S1FF_fb.xml)
4. - The phone to unbrick, put fastboot mode, switching on via the power button and vol (-) until the fastboot mode screen read "fastboot reason:" if it does not, re-try until there is
5. should not say "fastboot reason: flash failure, or anything else xxxxxx xxxx xxxxx ............"
6. - Boot rsd lite 6.1.4, select retail rom, and indicate that only "unzip" connects your motorola razr I, and it connects back to the other phone (in my case htc wildfire), which has a debug mode enabled.
7. - Note, that in the window of the Rsd Lite in row 1, the Razr I phone is detected, then you start flashing in RSD Lite 6.1.4, see screenshot of your razr I to see that data is being sent, (the other phone should not be affected and only serves as a decoy to usb drivers, Rsd lite at least do not damage to my phone)
8. - Remember flashing erase the card was in your internal Razr I therefore will lose programs, photos or music you had or downloaded to the SD or internal virtual
9. - Flashing can stop and have to do everything again, but remember that no fastboot mode screen should read:
"fastboot reason: flash failure or otherwise else xxxxxx xxxxxxx ......." must be clean that is just:
"fastboot reason: "
luck : Good:
Warning, do not take responsibility for any damage to your cell involved in the process, ......... the lure of the phone can be found on youtube and just suits the way because of my need to get my phone ........ in no way am programmer or software developer, for which only comment what turned out ok to me
excuse my bad English
jacbarahona72 said:
Hello good morning
I brick 2 phones trying to get one of them and in the process did fail at 2, how the recovery?
1. - Use RSD Lite version 6.1.4
2. - Use 1 extra phone (htc wildfire root and backup CWMR in case of failure)
3. - Use a GB retail rom (CFC_8.7.1I-110_IFW-39_S7_UCASMI01E1017.0R_USASMIICSRTGB_P042_A005_S1FF_fb.xml)
4. - The phone to unbrick, put fastboot mode, switching on via the power button and vol (-) until the fastboot mode screen read "fastboot reason:" if it does not, re-try until there is
5. should not say "fastboot reason: flash failure, or anything else xxxxxx xxxx xxxxx ............"
6. - Boot rsd lite 6.1.4, select retail rom, and indicate that only "unzip" connects your motorola razr I, and it connects back to the other phone (in my case htc wildfire), which has a debug mode enabled.
7. - Note, that in the window of the Rsd Lite in row 1, the Razr I phone is detected, then you start flashing in RSD Lite 6.1.4, see screenshot of your razr I to see that data is being sent, (the other phone should not be affected and only serves as a decoy to usb drivers, Rsd lite at least do not damage to my phone)
8. - Remember flashing erase the card was in your internal Razr I therefore will lose programs, photos or music you had or downloaded to the SD or internal virtual
9. - Flashing can stop and have to do everything again, but remember that no fastboot mode screen should read:
"fastboot reason: flash failure or otherwise cuarquier xxxxxx xxxxxxx ......." must be clean that is just:
"fastboot reason: "
luck : Good:
Warning, do not take responsibility for any damage to your cell involved in the process, ......... the lure of the phone can be found on youtube and just suits the way because of my need to get my phone ........ in no way am programmer or software developer, for which only comment what turned out ok to me
excuse my bad English
Click to expand...
Click to collapse
Could PM Me with the instructions in spanish, there are some things that i do not understand in your english
Tried to use your method but RSD lite got stuck on "4/11 erase userdata" and the phone says "program dummy sp block for userdata" I don't thin I understood well the part of the second phone, does it have to be on, i mean normal on, or does it have to be in flashmode aswell?
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
I have a stock Verizon Moto X (XT1060) that was running 4.4.4. I was on a flight Friday using the phone in airplane mode to run Spotify and Podkicker - noticed the phone was running a little hot so I shut the apps down for a while. Anyway, upon landing I take the phone off airplane mode and the usual minor flood of emails/texts/updates comes in. About 30 seconds after this the phone begins alternately flashing "Process android.process.acore has stopped" and "Process android.process.media has stopped." These cycled for about 5 displays of each, then would disappear for about 45 seconds, then start again. Tried resetting the phone, letting the battery die, no success.
Saturday I tried to navigate into settings to do a factory reset, but the screen froze whenever I tapped on the "backup and reset" menu. Could access all the other menus from settings (until the error cascade started again....). I was able to boot the phone into recovery mode and wiped the cache - nothing. Went back into recovery mode to do a factory reset and now I appear to be stuck in a boot loop - the Moto logo pops up, buzzes, and then does nothing for about a minute or two before trying again. I can get it into recovery mode and tried to wipe the cache and factory reset again, but still nothing.
Any thoughts? Tried looking at other threads but didn't seem to find anything like this. Thanks!
Try this cmd in fastboot
fastboot oem fb_mode_clear
http://forum.xda-developers.com/showthread.php?t=2738055
hbenz2008 said:
Try this cmd in fastboot
fastboot oem fb_mode_clear
http://forum.xda-developers.com/showthread.php?t=2738055
Click to expand...
Click to collapse
No luck, unfortunately. Still stuck on the Moto screen. I can force the phone to reset by holding down the power button and then get it into fastboot, my computer recognizes the fastboot device, and the code seems to have run fine. Thanks for the idea - any other thoughts?
If you can still get into fastboot mode you can try flashing only the stock 4.4.4 system.img via mfastboot. That will not wipe your data. If that does not work I would do a full return to stock via mfastboot or you can use rsd.
Thanks Travis I'll give it a shot. I never enabled USB debugging and never unlocked my phone before this happened - I imagine I'll need to try and unlock the bootloader first, no?
cmcgowan said:
Thanks Travis I'll give it a shot. I never enabled USB debugging and never unlocked my phone before this happened - I imagine I'll need to try and unlock the bootloader first, no?
Click to expand...
Click to collapse
No, don't need to unlock boot loader to flash the system.img just enable USB debugging in developer options. Tap build number 5 times to enable developer options. If you have never flashed anything before via fastboot rsd might be easier for you.
Thanks - I've used fastboot before on an older phone but never enabled USB debugging on this phone and now can't get to enable it since I'm stuck with this boot loop. Downloading the files from Moto now so will give it a shot tonight anyway. Can't really break it more than it's already broken since all I've got now is a shiny light up paperweight.
You will still need to download the stock images for 4.4.4 for Verizon and extract them. You can flash via rsd or simply flash just the system by running the command "mfastboot flash system system.img"
You will have to have the image file in the same folder as your mfastboot.exe I usually keep all mine in platform tools.
Sigh. Got everything downloaded but when I tried to flash either the boot image, recovery image, or system image, I ran into errors
Here's what displayed (sub boot/recovery for system - same basic error):
c:\{Path}\mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [16.793s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.756s
I was following option 5 from mark @ cdma forum's guide to return motox to stock (can't link b/c I don't have enough posts...) . No issues until I got to the flash boot boot.img step.
I'm assuming this is due to not having USB debugging enabled prior to my phone eating itself, though I'm not sure. Willing to try other things since I love my Moto X but my cheap replacement phone arrives tomorrow (hopefully) so at least its not the end of the world...
You are sure you got the 4.4.4 images? You did not try to downgrade right?
Yup. Definitely got the 4.4.4 images (went back to the Moto site and it will let me download the 4.4.4 immediately but made me request authorization for 4.4.2) and I know I was running the most recent version since I checked for an upgrade on my phone last week in the hope that Moto had released 5.0.
You are following this guide? http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
If USB debugging is not on you can manually boot you device to boot loader mode. Then fastboot or rsd should work fine.
---------- Post added at 11:36 PM ---------- Previous post was at 11:32 PM ----------
Moto X Restore and unbrick for any major US carrier: https://youtu.be/jhhktIkwi7Q
I appreciate the help...but still no luck. That's basically what I've been doing and I went back through following those instructions - at every step I get the "variable not supported" error and then it fails at the flash boot step with the error message I described earlier.
cmcgowan said:
I appreciate the help...but still no luck. That's basically what I've been doing and I went back through following those instructions - at every step I get the "variable not supported" error and then it fails at the flash boot step with the error message I described earlier.
Click to expand...
Click to collapse
You are opening the cmd screen from the same folder as your images and fastboot and mfastboot.exe correct? From your error it looks like your cmd screen is directed to your "C" drive.
Sorry, just didn't type out the whole thing - the cmd path is to the platform-tools folder where all of the files are also located...
Damn was hoping it was something simply like that. Have you tried rsd?
I haven't - didn't enable USB debugging and for whatever reason the package I downloaded from Moto doesn't include the XML file of instructions. Most of the links from the youtube video and some of the links from the XDA guide earlier are also dead so seems like I'm pretty much out of options. Thanks for all of your help - guess I'm going with the $80 replacement till I'm up for an upgrade!
Ok, this is only for the Jedi masters.
I have a Moto X (1st gen - XT1058) bricked. However I think I got the master level bricked.
I was using the ROM Retail BR 4.4.4 and I upgraded to version 5.1 via OTA. All went quiet until the unit began to catch on and off yourself. I reinstalled version 5.1 via RSD Lite smoothly. The device worked for a few weeks but after some time the same problems again.
Until the phone died. Do not leave the boot screen.
I thought it was something not too bad, because I could still access the Fastboot (AP Fastboot Flash Mode (S) 30.BE). However I can not get into Recovery mode and something else I do return with errors involving:
Failed to read signature is aboot partition
Boot up failed
The solutions I found on the internet I've tried:
Reinstall the original ROM by RSD Lite (and earlier also suppressing gpt.bin)
- Always fails when the application tries to apply flash partition gpt.bin. If I delete this line in the XML file, the failure persists, but the next line of execution.
Use original gpt.bin files, boot.img, system.img and recovery.img and try to install them through the mfastboot fastboot command and Windows Terminal 7 (32 and 64bit).
Use a file blankflash & the qflash.exe ... command from the Windows terminal. Can install the drives and recognize the specific port of the device, but the process does not continue.
Does anyone have any light around? Something different than I've ever tried?
My daughter is missed to watch Pocoyo in Youtube. It was the only thing that calms my little child.
Help me! :crying: