Hi friends, first of all I am here because I don't have another options to try or I haven't found it yet here or in internet, I have a MB886 unlocked from AT&T, it was running AOSB 1.3.4(kk 4.4.2) had philz touch recovery and it just stays in infinite boot loops only turning off by entering in the ap fastboot option, from the causes I could mention the installation of the EB40 battery, but it was trouble free, and the cleaned of cache and dalvik from recovery, maybe a bad charge of static when installation? or a failure in philz touch?...
After search all about the problematic, download drivers and the computer ( windows 8) recognizing the fastboot quinara s from my cellphone, this is what I did:
-firstly, followed this post http://forum.xda-developers.com/showthread.php?t=2334000 and nothing positive, then this http://forum.xda-developers.com/dro...-bricked-razr-m-4g-xt907-hd-preflash-t3135462 and nothing positive with the fastboot commands and rsd lite doesn't recognized my cellphone fastboot in wondows 8.( tried to flash MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml, MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml and ATT_MB886_4.1.1-9.8.0Q-97_MB886_FFW-28_CFC_1FF.xml)
- I tried MYTH tools too, but it doesn't work, tried to flash MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml and ATT_MB886_4.1.1-9.8.0Q-97_MB886_FFW-28_CFC_1FF.xml it shows commands like "varable not supported" or "target reported max download size of" but finished the flashing and still bootlooping.
-Followed this guide: http://forum.xda-developers.com/dro...-bricked-razr-m-4g-xt907-hd-preflash-t3135462 by fastboot, windows 8 and the motorola factory cable( pin 1 and 4 with +5v) could flash sucesfully MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml it works like a charm but was while it stayed connected to the computer, after this, flashing process only could be with the gpt_main0 file from the nextel firmware.
- Even in a sometime, I dont remember after how many flashings of the nextel firmware but was using the motocable, I could entered to my twrp recovery, cleaned all and did a clean install for AOSB KK from my SD, rebooted and bootlooping, then, I flashed again and entered to TWRP again and did a factory reset, and nothing.
- I tried MYTH tools again, but it doesn't work, tried to flash MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml and ATT_MB886_4.1.1-9.8.0Q-97_MB886_FFW-28_CFC_1FF.xml with the file gpt_main0 from the nextel firmware and in one time only reach the AT&T animation then froze.
- I combined the method from the razrs and the another one for the AHD to flash all the files from the firmwares and nothing happened, even the moto cable stops of functioned , because it showed responds from the fastboot like "varable not supported" "target reported max download size of " "FAILED (remote failure)"and with a normal usb cable everything was well flashed and nothing.
- flashing with rsd lite 6.1.6 in win xp used to get Error with MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml because the step of flash gpt_main0.
- I substituted gpt_main0 from MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml and it work with rsd in win xp (says SUCCES), just the last step when rebooted the phone, the phone stayed in boot loop.
-flashed MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml with RSD in win xp and fails in the last step when reboot, it stays bootlooping even when rsd says "SUCCES".
-tried to flash in ubuntu(fastboot method) with moto cable and a usb cable but never was like in windows 8, just boot loop and more boot loop.
so, here is the history of what I did it to my cellphone and he doesn't want to live anymore, so the question is, what I missed out? or what I can do it?, discarding throw it to the trash or having like a nice paperweight...
Any kind of help, suggestion, comments, or hardware modification will be appreciated and sorry for my english, I wrote the best I could.
P.D: always had a good porcentage of charge in the battery while did the flashings,charged it with 5v and 500ma directly to the battery and tested with multimeter when fastboot alarmed low battery, and anytime while phone had been flashed with AT&T relase keys rom, bootlooping was with the advertisement about the bootloader unlocked, and when had been flashed with nextel firm it shows motorola dual core logo boot loop.
I don't remember the exact name of the thread but search Atrix HD command line and you should find another guide that always worked for me. I never had luck with rsd lite or mythtools.
Sent from my LG-D850 using XDA Free mobile app
failed flashing partition gpt_main0
thank you for the help, I found that post: http://forum.xda-developers.com/showthread.php?t=2259661 and following the instructions, but I don't have more than a "FAILED" message in the first step when I try to flash gpt_main0 partition, with att release keys and with nextel firm, even when I use "mfastboot" instead of fastboot, it gets error message, there is a newer firmware version than the nextel one? or the partition is corrupted?... thanks.
The nextel firmware is the newest. There was an ota from att for the heartbleed bug, but I think that's all that was in it.
Sent from my Nexus 7 using XDA Free mobile app
---------- Post added at 11:06 PM ---------- Previous post was at 11:04 PM ----------
Are you sure you have an atrix HD? You mentioned TWRP in the op, but we don't have a fully functioning twrp.
Sent from my Nexus 7 using XDA Free mobile app
Philz touch instead twrp
Ok, thanks again buddy, and yes , the cellphone is an atrix hd, but you are right I used to have a philz touch recovery instead twrp (my mistake), the only error I have is flashing gpt_main0 partition and if I flash completely there is no more fails, with "mfastboot" every flash step is running like a charm and with "fastboot" shows messages like bootloader variable not supported or maximum size errors, the cellphone turns on bootlooping but stills enter to boot menu selection and ap fastboot mode...
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?
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
Hey guys, last night I tried to root my device (XT1058) following the guide [here](http://forum.xda-developers.com/moto-x/general/howto-root-moto-x-ver-4-4-4-xt1060-t3118342). Stupid me decided I wouldn't need to go back to stock ROM like it says in the first step. I continue with the guide, follow every step, until I reboot. After rebooting my Moto X gets stuck at the white screen with the blue circle M. I panicked, read a lot of things online, followed them, and nothing worked. I reset the cache partition in recovery mode when rebooting into fastboot, still nothing. I also noticed that my device is no longer detected in ADB at all, even in fastboot. So after just giving up, I read online in multiple places going to recovery mode, and wiping the whole phone/factory resetting would fix it. It still is not recognized by ADB or finishing booting. I realize I should've been more careful. Please help!
First thing... when the phone is in Fastboot AP menu, you can't use ADB. ADB wont work and wont see your phone unless the phone is fully booted. (i.e. adb.exe and fastboot.exe use two different modes on the phone).
Next, I've seen that symptom before, but I don't recall how to fix.
I would really consider asking in the thread for the process you were following.
If no one gives you any suggestion, you could always try re-flashing the stock image for your phone that matches the highest version you've had installed on your phone. (On fastboot screen you can see bootloader version, so match you stock version to that. see the list of known bootloader versions at -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 ) And use mfastboot to flash it (follow option 5 in the 2nd post at -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )
I'm pretty sure I saw this on reddit. You had a mac right?
You need fastboot installed on your mac:
http://forum.xda-developers.com/showthread.php?t=1917237
Assuming you have fastboot working on your mac and your phone this thread method two:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Use fastboot instead of mfastboot for the sytem.img file.
If you receive an error with flashing system you could try:
Code:
fastboot -S 0 flash system system.img
If u can still enter recovery mode, factory data reset from it , if u can't boot still after resetting , u have to flash the full stock ROM.....
Sent from my HM NOTE 1LTE using XDA Free mobile app
Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...
Hello!
I unlocked the bootloader successfully, then I tried to root my phone using The Razr guy method and I used the "RAZRi_Root_Windows" file, while rooting my phone went to the "warning bootloader unlocked" screen and it just loops forever from that screen, the bat file, showed that it successfully rooted my phone. I tried to fix it using rsd lite, but it never detects my phone, so I searched for a way to make my pc able to detect it, so I found I could use Intel xFSTK, installed it but still nothing it doesn't appear as shown in the tutorial, I even downloaded the dll file that it needed to run, but after running the xFSTK DLDR or something like that, the application is completely empty, and I saw it should show some tools to download something. Also tried using Linux Zorin, but it only says that my XT890 cannot be accessed and shows an usb error code.
I am able to enter the fastboot screen, the one you get by pressing POWER and VOLUME DOWN, also it charges my batter completely normal. Also my pc is able to show that the XT890 is connected, but only before installing the drivers and it shows the CD installer for the Motorola Device Manager and some other files (all this while looping), and if I enter the fastboot flash mode, it appears as "fastboot smi S", with a yellow triangle and an exclamation sign while in Windows device manager. It has Jelly Bean update from telcel (mexico), and I already have the xml.zip file to reinstall it.
I use windows 8.1 , and as mentioned Linux Zorin on my PC.
Could some help me with it...if you now how to fix it please list every single step on how to do it T_T, THANKS IN ADVANCE!!!!
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Hazou said:
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Click to expand...
Click to collapse
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
weird_user said:
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
Click to expand...
Click to collapse
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Thanks again!!!
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
I am able to enter RECOVERY MODE NOW (I installed CWM, before this I was only able to see the android lying on the floor ans saty dead right there, I was supposed to press Volume + and - and the camera button at the same time, but nothing happened), it seems to be easier to unbrick it this way, but now the problem is that after I follow the steps to reinstall the original ROM, it aborts installation. I read this may be caused due to a file on the zip file, I looked for it, but nor the Folder META-INF, whic is supposed to contain a "update-script" file, nor that file is anywhere in the ROM folder...
I've even tried cyanogenmod (after first trying Telcel original ROM and then the retail GB ROM) cuz it actually contains the folder previously mentioned and the file is in a different path, but it is there, I modified it, but got a "Can't open tmd/update.zip (bad) Installation aborted" error...I don't know what else to do T_T...
Note: I also used sideload and CWM to install it, but the same thing happens. Also checked some other post about this issue, but none has helped me...
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Hazou said:
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Click to expand...
Click to collapse
It's done! Thanks!
I actually used another computer with windows 10, also I used RSD Lite and it worked just fine, now I have the stock ROM from Telcel and it it is working almost normal. The only abnormality I've seen is that my phone turns itself off when battery is at 20%, I searched info about that problem and it says I may re calibrate the battery, so it may work fine again, but now I need to root again to be able to do that T_T, hope it works this time...
THANKS! again!
I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
carkev said:
I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
Click to expand...
Click to collapse
U said fastboot hangs at flashing the recovery, but on the command lines on your PC it says finished. Have u tried booting into recovery?
What recovery did u use and where did u get it?
USB debugging, simcard and sdcard don't have anything to do with fastboot. But it is likely that u didn't know that
thanks for looking at this.
I did try booting into recovery from my PC by after rebooting it and then taking the recovery option, but the phone hung at the Motorola bootloader unlocked warning screen.
this link was typical of the various tutorials I used: http://androidteen.com/motorola-razr-i-how-to-root-and-install-clockworkmod-cwm-recovery-on-android-4-1-2-jelly-bean-firmware/
to be fair I cannot recall where I got all the recovery images from - I have that many, and had to rename them recovery.img, so cannot remember the original download names
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
carkev said:
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
Click to expand...
Click to collapse
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Hazou said:
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Click to expand...
Click to collapse
thanks HazouPH, I'll give that a go
I have solved my problem with CWM:victory:
whilst I am not 100% certain I am pretty much sure it was a driver problem - for those who this may benefit, here is what I did.
1. I did not reflash my phone, but stayed with the one in my original post.
2. remember that the main problem was that Fastboot said I had succeeded in flashing a Recovery image, but that the phone 'hung'
at flash as in my photo. and then from my phone I could not get to recovery from the fastboot menu .
3. I stumbled across a posting (on XDA, but I cannot remember where) that said the Motorola drivers were not as good as they should be and that the Motohelper one's would be fine - so I downloaded them, and have attached the zip below.
4. I then decided to tidy up my PC and uninstalled all mobile phone drivers, plus any redundant USB Device drivers
5 for the USB tidying up I tend to use USBdview, which is superb and can be found here
6 when all this was done I simply tried the reflash of CWM - and got the same situation I had been having all along
but amazingly, when I selected 'recovery' it went in CWM - I nearly fainted with surprise!
from all this I can only assume it was a driver problem as I had changed nothing else.
perhaps it was Motohelper drivers- perhaps it was USBdview that did it for me - I will never really know, nor care!
I now have CWM v6.0.1.9 - it is touchscreen and permanent, plus I use the cute Reboot by app by Petrus to control my phone.
happy days!