Database Develop

KitKat Update Crashed My Moto X - Unrecoverable?

Yesterday my moto x alerted me that the KitKat update had been downloaded and was ready to install. I selected INSTALL and the installation began. About a minute into it, it kicked me to the bootloader with the message, "Failed to hab check for recovery: 0x56. Boot up failed".
Also see my post at androidcentral.com at forums.androidcentral.com/moto-x/336036-kitkat-crashed-my-moto-x-unrecoverable.html
Note that my moto x has never been rooted.
forums.androidcentral.com/attachments/moto-x/92779d1384906583-kitkat-crashed-my-moto-x-unrecoverable-kitkat_error.jpg
I selected "Recovery" and it rebooted and attempted to re-install, but then I was met with a image very similar to this except it said "ERROR":
forums.androidcentral.com/attachments/moto-x/92780d1384906685-kitkat-crashed-my-moto-x-unrecoverable-android-error.jpg
Then a few seconds later it rebooted again and now it just gets stuck at the Motorola logo:
forums.androidcentral.com/attachments/moto-x/92781d1384906724-kitkat-crashed-my-moto-x-unrecoverable-moto_x_boot_logo_featured_small.jpg
If I try any of the other options in the boot loader, the behavior is the same.. it gets stuck at the Motorola logo. Yesterday it sat that way for 4 hours before the battery died.
Today I tried connecting it to my computer via USB. My Mac doesn't appear to recognize that it's been connected even though the drivers have been installed. In a Windows VM with MDM it recognized the first time I connected it, but the MDM icon promptly disappeared from the status bar.
I spoke with Verizon tier 2 tech support yesterday and they didn't seem very knowledgeable - the person I spoke with didn't even know what KitKat is.
Surprisingly, I thought I had set up the Motorola data backup to the cloud, but verizon tech support said I must not have enabled it. So my biggest worry is that I've lost all my data (pictures/videos/contacts/etc...).
I'm hoping that somebody on this forum might have some advice for me.
Thanks,
Chris

cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.

xpc21 said:
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
Click to expand...
Click to collapse
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.

cbridgers said:
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
Click to expand...
Click to collapse
cbridgers, that error happened to me while i was trying to flash through RSD Lite the leaked version of Kitkat. Because it was only to AT&T phones, it gave me that error cause i didnt have an unlocked bootloader. So what i did was flash back the 4.2.2 and for my surprise the phone was with all my config and data, nothing was erased.

Few suggestions...
cbridgers said:
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
Click to expand...
Click to collapse
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!

xpc21 said:
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
Click to expand...
Click to collapse
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
Click to expand...
Click to collapse
Thanks for your detailed instructions! Solution #1 didn't work for me. Solution #2 gives me the following error when I run "fastboot flash system system.img":
load_file: could not allocate 870593756 bytes
error: cannot load 'system.img'
I'm not sure I want to try Solution #3 yet. May try to talk to Motorola first.
Thanks again for the detailed advice!
Chris

SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
Click to expand...
Click to collapse
OK, I got past the previous error by increasing the RAM allocated to my Windows VM. Now I get the following error when running "fastboot flash system system.img":
sending 'system' (850189 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.313s

cbridgers said:
Thanks for your detailed instructions! Solution #1 didn't work for me. Solution #2 gives me the following error when I run "fastboot flash system system.img":
load_file: could not allocate 870593756 bytes
error: cannot load 'system.img'
I'm not sure I want to try Solution #3 yet. May try to talk to Motorola first.
Thanks again for the detailed advice!
Chris
Click to expand...
Click to collapse
Make sure you are using the newest fastboot files, the older ones do not chunk the system image and it is too large to flash.
New fastboot for Mac -- > http://www.teamblackhat.net/Downloads/Darwin.zip
New fastboot for Windows --> http://www.teamblackhat.net/Downloads/fastboot.zip

Use the house if moto save data option you can fxz using rsd or fastboot and it will not erase data at all. I have used it many times works great.

SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
Click to expand...
Click to collapse
How sure are you about this?
Also, I had xt1058 (americamovil) with TMO firmware with the camera update (unlocked BL) and I flashed stock vzw firmware (with the camera update). No problems after a full wipe. The OTA was downloading too slow so I downloaded the OTA zip file in other thread. When I tried to install the update via stock recovery i got this message:
"/modem/image/dsps.b00" has unexpected contents.
Installation aborted
Click to expand...
Click to collapse
So i waited for the normal OTA and it just says installation failed, and i had it just wiped so i can't be free space.
Finally I flashed the 4.4 TMO leak

Try this
fastboot oem fb_mode_clear
fastboot reboot-bootloader
then take all the files from the first OTA sbf and flash them in order
does that work?

waiflih said:
How sure are you about this?
Also, I had xt1058 (americamovil) with TMO firmware with the camera update (unlocked BL) and I flashed stock vzw firmware (with the camera update). No problems after a full wipe. The OTA was downloading too slow so I downloaded the OTA zip file in other thread. When I tried to install the update via stock recovery i got this message:
So i waited for the normal OTA and it just says installation failed, and i had it just wiped so i can't be free space.
Finally I flashed the 4.4 TMO leak
Click to expand...
Click to collapse
There are 5 parts that need to be stock, that is the only thing that needs to be done.
system, boot, recovery, modem, fsg.
the only way to know why it is failing is to sideload, load from recovery, or check the update error log.
If it were me I'd just fastboot all five of those partitions and take the update.

jimmydafish said:
There are 5 parts that need to be stock, that is the only thing that needs to be done.
system, boot, recovery, modem, fsg.
the only way to know why it is failing is to sideload, load from recovery, or check the update error log.
If it were me I'd just fastboot all five of those partitions and take the update.
Click to expand...
Click to collapse
I dont know where to find modem files for stock vzw
Enviado desde mi XT1052

waiflih said:
I dont know where to find modem files for stock vzw
Enviado desde mi XT1052
Click to expand...
Click to collapse
They are in the FXZ file named NON-HLOS.bin

Thx! I didnt know those were modem related. Can i flash back the modem files to tmo or att firmware?
Enviado desde mi XT1052

waiflih said:
Thx! I didnt know those were modem related. Can i flash back the modem files to tmo or att firmware?
Enviado desde mi XT1052
Click to expand...
Click to collapse
Well what are you trying to do? but if unlocked you can flash anything you want. I would stay far away from flashing any bootloader, tz, gpt, or sbl files though.
Only flash those files I named before.

Yes, i only flash the files i know are safe to flash, i dont like to use rsdlite. Thx again
Enviado desde mi XT1052

I seem to have run into the same issue..
Any updates, OP?
Here's my thread: http://forum.xda-developers.com/showthread.php?p=47747140#post47747140

ekraincg said:
I seem to have run into the same issue..
Any updates, OP?
Here's my thread: http://forum.xda-developers.com/showthread.php?p=47747140#post47747140
Click to expand...
Click to collapse
I'm having the same problem with my T-Mo moto x I received yesterday. I tried the fastboot erase cache method. It works to the extent that I can boot back into 4.2.2 but I can't update or perform a factory reset from the settings menu.
When I give the command to fastboot erase cache the bootloader says 'get-var partition type' and 'erasing cache' however the bootloader never says 'cache erased' or any other confirmation message. Fastboot on the desktop does say 'cache erased' though.
Finally, I would try to flash the stock images but I can't seem to find them anywhere. Can someone point me to them please?

endless bootloop after doing the OTA to 4.4.2

So one of my buddies took the OTA update for 4.4.2 while being rooted on 4.4 with TWRP as his recovery. Now he is stuck in an endless bootloop. Any idea what we could do to bring his phone back to life?
By the way, he is on Sprint and has his bootloader unlocked
Any advice would help!
Thanks.

AbstractXart said:
So one of my buddies took the OTA update for 4.4.2 while being rooted on 4.4 with TWRP as his recovery. Now he is stuck in an endless bootloop. Any idea what we could do to bring his phone back to life?
By the way, he is on Sprint and has his bootloader unlocked
Any advice would help!
Thanks.
Click to expand...
Click to collapse
This happened to me too.
Just flash the latest firmware for your device at http://sbf.droid-developers.org/phone.php?device=0
Then accept the OTA.
Re-install TWRP.
Hope this works for you too.

patspdaphone said:
This happened to me too.
Just flash the latest firmware for your device at http://sbf.droid-developers.org/phone.php?device=0
Then accept the OTA.
Re-install TWRP.
Hope this works for you too.
Click to expand...
Click to collapse
So to accept the OTA, did you go through the bootloader/recovery and flash it, or were you able to turn on your phone and accept it? Sorry I don't have his phone on me right now otherwise I would have done it .

Don't flash the full SBF..
boot the phone into fastboot mode... mfastboot erase cache... the reboot the phone. that will remove the OTA zip file from chache and stop the boot loop.
The bootloop is because the phone has TWRP on it rather than stock recovery.
To take the OTA properly, use mfastboot to reflash stock recovery only. Also have him undo any hacks that might have touched system files or the OTA will fail, (mfastboot system will also get /system back to normal)...

KidJoe said:
Don't flash the full SBF..
boot the phone into fastboot mode... mfastboot erase cache... the reboot the phone. that will remove the OTA zip file from chache and stop the boot loop.
The bootloop is because the phone has TWRP on it rather than stock recovery.
To take the OTA properly, use mfastboot to reflash stock recovery only. Also have him undo any hacks that might have touched system files or the OTA will fail, (mfastboot system will also get /system back to normal)...
Click to expand...
Click to collapse
We actually just ended up clearing the system cache and that seemed to do the trick .
I incredibly appreciate all the info! If anyone makes this silly mistake, all you need to do is clear the cache and everything works as intended.

AbstractXart said:
We actually just ended up clearing the system cache and that seemed to do the trick .
I incredibly appreciate all the info! If anyone makes this silly mistake, all you need to do is clear the cache and everything works as intended.
Click to expand...
Click to collapse
until the next time the OTA downloads and tries to install

I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?

Globalrebel said:
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Click to expand...
Click to collapse
KangKat wtih Faux kernel? So you are not running the stock rom? I'm suprised the actually OTA installed.
I don't know anything about that rom, or kernel to begin to tell you how to fix this situation, short of reflashing your rom

KidJoe said:
KangKat wtih Faux kernel? So you are not running the stock rom? I'm suprised the actually OTA installed.
I don't know anything about that rom, or kernel to begin to tell you how to fix this situation, short of reflashing your rom
Click to expand...
Click to collapse
He probably flashed the "Flashable 4.4.2 ZIP" that is flashable through TWRP.
@Globalrebel :
You need to try to get into bootloader (AP Fastboot) mode. Try holding the VOL DOWN while the phone reboots (vibrates). Make sure the phone is unplugged from USB. If you can access fastboot, your best best would probably to flash the entire SBF back to stock.
Always check here first before you do something like trying to flash a stock update on a custom rom. We would have quickly informed you that this is ill-advised.
Good Luck

Ok, so I have held down the power button, and then when vibrating starts, I hold down vol down button. Then, it vibrates 2 times. What now? (Sorry, I'm freaked out as this is my only phones )
How can i check to see if it is actually in Fastboot mode? Since my screen doesn't show ANYTHING at all?
I started up an ADB server and connected my phone and tried "adb devices" but my phone isn't listed.
---------- Post added at 08:49 AM ---------- Previous post was at 08:40 AM ----------
samwathegreat said:
He probably flashed the "Flashable 4.4.2 ZIP" that is flashable through TWRP.
@Globalrebel :
You need to try to get into bootloader (AP Fastboot) mode. Try holding the VOL DOWN while the phone reboots (vibrates). Make sure the phone is unplugged from USB. If you can access fastboot, your best best would probably to flash the entire SBF back to stock.
Always check here first before you do something like trying to flash a stock update on a custom rom. We would have quickly informed you that this is ill-advised.
Good Luck
Click to expand...
Click to collapse
any ideas?
I just checked device manager and it shows "ADB Interface" and then MOT Single ADB Interface.
But its not showing up under devices when running command "ADB Devices" in CMD

Globalrebel said:
Ok, so I have held down the power button, and then when vibrating starts, I hold down vol down button. Then, it vibrates 2 times. What now? (Sorry, I'm freaked out as this is my only phones )
How can i check to see if it is actually in Fastboot mode? Since my screen doesn't show ANYTHING at all?
I started up an ADB server and connected my phone and tried "adb devices" but my phone isn't listed.
---------- Post added at 08:49 AM ---------- Previous post was at 08:40 AM ----------
any ideas?
Click to expand...
Click to collapse
Fastboot getvar all
If you get a response with that, proceed with the entire Sbf manual method as listed in the return to stock thread.

samwathegreat said:
Fastboot getvar all
If you get a response with that, proceed with the entire Sbf manual method as listed in the return to stock thread.
Click to expand...
Click to collapse
I got it to show some info after running the command. Now, I have the following guide open . .
[GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash)
But I don't see anything in RSDLite after running it and clicking "Show Device"
Can I just to the manual method?
For manual method, should I copy all the files into the same folder as my mfastboot.exe?

Globalrebel said:
I got it to show some info after running the command. Now, I have the following guide open . .
[GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash)
But I don't see anything in RSDLite after running it and clicking "Show Device"
Can I just to the manual method?
For manual method, should I copy all the files into the same folder as my mfastboot.exe?
Click to expand...
Click to collapse
Yes,I suggested manual method in last post. Faster and easier.
Yes extract the sbf to the folder containing mfastboot and fastboot.
The only thing you will do differently is one of the last lines that says carrier vzw, change it to carrier sprint.
Make sure u are using the 4.4.2 sprint sbf.
Good luck

samwathegreat said:
Yes,I suggested manual method in last post. Faster and easier.
Yes extract the sbf to the folder containing mfastboot and fastboot.
The only thing you will do differently is one of the last lines that says carrier vzw, change it to carrier sprint.
Make sure u are using the 4.4.2 sprint sbf.
Good luck
Click to expand...
Click to collapse
I am using Tmobile so I put tmo
But, after doing EVERYTHING, the phone reboots and I see it in PC, but screen is still not working?!?!?!
I did everything...
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot 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
fastboot erase clogo
fastboot oem config carrier tmo
fastboot oem fb_mode_clear
then
fastboot reboot
The phone boots and the phone is seen by my computer, but the screen is not working AT ALL
No water damage, and the phone was literally working perfectly fine 15 minutes ago. Just all of a sudden stopped showing the screen

Globalrebel said:
I am using Tmobile so I put tmo
But, after doing EVERYTHING, the phone reboots and I see it in PC, but screen is still not working?!?!?!
I did everything...
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot 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
fastboot erase clogo
fastboot oem config carrier tmo
fastboot oem fb_mode_clear
then
fastboot reboot
The phone boots and the phone is seen by my computer, but the screen is not working AT ALL
Click to expand...
Click to collapse
Bummer. You appear to have used the correct procedure.
This looks to be a hardware failure :/
Sorry, I don't have any further troubleshooting techniques for you...

Its all good. I think the screen just decided to die on me?!?! Which REALLY SUCKS! I'm still in my 1 year warranty policy. After fastbooting the original 4.4.2, will motorola know I did anything to the phone? IE, can they know I flashed anything?

Globalrebel said:
Its all good. I think the screen just decided to die on me?!?! Which REALLY SUCKS! I'm still in my 1 year warranty policy. After fastbooting the original 4.4.2, will motorola know I did anything to the phone? IE, can they know I flashed anything?
Click to expand...
Click to collapse
If you unlocked the bootloader they know it. Technically your warranty is void... But they might replace/fix it anyways. Don't mention it and see what happens. Let us know.

[Q] Cannot flash recovery (TWRP)

I just got a Moto X on Sprint, and after successfully unlocking the bootloader, I do not seem to be able to flash TWRP. The flash seems to go ok, but when I boot the device into recovery, its still the stock recovery. Im attempting to use the official openrecovery-twrp-2.7.1.1-ghost.img image. Ive tried using the standard fastboot on OSX and WIn7-64bit, and in both situations I get this output:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8220 KB)...
OKAY [ 0.749s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.629s
The variable not supported seems to be the 'getvar partition-type:recovery' command (based on the output on the phone).
I have also tried using the fastboot provided by Motorola with the same output and result. On the forums somewhere I found a link to an older moto-fastboot-osx command, which has slightly different output, but the same results:
Code:
moto-fastboot-osx64 flash recovery openrecovery-twrp-2.7.1.1-ghost.img
sending 'recovery' (8220 KB)... OKAY [ 0.787s]
writing 'recovery'... OKAY [ 0.909s]
What am I doing wrong?

Have you double checked that your oprnrecovery-twrp...img file is not corrupt? Make sure to check it against the md5 checksum.

Yes, I verified the MD5, it is correct.

slushpupie said:
I just got a Moto X on Sprint, and after successfully unlocking the bootloader, I do not seem to be able to flash TWRP. The flash seems to go ok, but when I boot the device into recovery, its still the stock recovery. Im attempting to use the official openrecovery-twrp-2.7.1.1-ghost.img image. Ive tried using the standard fastboot on OSX and WIn7-64bit, and in both situations I get this output:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8220 KB)...
OKAY [ 0.749s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.629s
The variable not supported seems to be the 'getvar partition-type:recovery' command (based on the output on the phone).
I have also tried using the fastboot provided by Motorola with the same output and result. On the forums somewhere I found a link to an older moto-fastboot-osx command, which has slightly different output, but the same results:
Code:
moto-fastboot-osx64 flash recovery openrecovery-twrp-2.7.1.1-ghost.img
sending 'recovery' (8220 KB)... OKAY [ 0.787s]
writing 'recovery'... OKAY [ 0.909s]
What am I doing wrong?
Click to expand...
Click to collapse
Just a few thoughts...forgive me if any of this sounds redundant, or obvious....
Just reading your initial post, I would assume that you had used one of the previous root exploits and/or Safestrap BEFORE you got the BL unlocked. If so, it would be necessary to flash the entire stock SBF, before you would be able to successfully flash TWRP recovery........but your OP says you JUST got the phone, which would lead me to believe you didn't use a previous root exploit. Did you receive it NEW? Because the original owner could certainly have used exploit/safestrap.
If any of this is possible, you should follow the "Return to Stock" thread (manual method is suggested - easier and faster) and flash the entire Sprint 4.4.2 SBF. THEN you should be able to successfully flash TWRP. As I have often stated, a full SBF to stock can actually REPAIR a corrupted / modified (exploit / safestrap) filesystem. A "Factory Reset" does not repair any corruption that may be present.
2nd thought: I've seen some people confuse the "bootloader" screen (AP Fastboot Mode) for recovery. From the bootloader screen, you have to arrow down to highlight recovery, and press volume up to boot into recovery.
Alternatively, you can do it from fastboot: just type fastboot reboot-recovery
Let us know if any of this is relevant or solves your issue. If everything else fails, doing a full SBF back to stock fixes all issues nearly 100% of the time.
Good Luck

samwathegreat said:
Just a few thoughts...forgive me if any of this sounds redundant, or obvious....
Just reading your initial post, I would assume that you had used one of the previous root exploits and/or Safestrap BEFORE you got the BL unlocked. If so, it would be necessary to flash the entire stock SBF, before you would be able to successfully flash TWRP recovery........but your OP says you JUST got the phone, which would lead me to believe you didn't use a previous root exploit. Did you receive it NEW? Because the original owner could certainly have used exploit/safestrap.
Click to expand...
Click to collapse
It was purchased used, and the original owner was not very tech savy, so I assumed it was fully stock (it appeared so at first glance, anyway).
samwathegreat said:
If any of this is possible, you should follow the "Return to Stock" thread (manual method is suggested - easier and faster) and flash the entire Sprint 4.4.2 SBF. THEN you should be able to successfully flash TWRP. As I have often stated, a full SBF to stock can actually REPAIR a corrupted / modified (exploit / safestrap) filesystem. A "Factory Reset" does not repair any corruption that may be present.
Click to expand...
Click to collapse
Ill give this a try and report back. Perhaps there is something weird going on in there...
samwathegreat said:
2nd thought: I've seen some people confuse the "bootloader" screen (AP Fastboot Mode) for recovery. From the bootloader screen, you have to arrow down to highlight recovery, and press volume up to boot into recovery.
Alternatively, you can do it from fastboot: just type fastboot reboot-recovery
Let us know if any of this is relevant or solves your issue. If everything else fails, doing a full SBF back to stock fixes all issues nearly 100% of the time.
Good Luck
Click to expand...
Click to collapse
Im familiar with Android enough to know the difference between the bootloader and recovery, but thanks for making sure.

slushpupie said:
It was purchased used, and the original owner was not very tech savy, so I assumed it was fully stock (it appeared so at first glance, anyway).
Ill give this a try and report back. Perhaps there is something weird going on in there...
Im familiar with Android enough to know the difference between the bootloader and recovery, but thanks for making sure.
Click to expand...
Click to collapse
Haha, yes, I was hesitant to suggest there may be confusion between bootloader and recovery.... Glad you were on top of that one...
The return to stock thread is located here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Again, manual method is easier and faster.
You will flash the 4.4.2 Sprint SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
If my first theory was correct, you wouldn't be the first person who received a used phone that had an exploit used on it. The devs make it pretty easy even for not-so-tech-savvy people with all the "one-click" rooting scripts and the like. Often times, the seller just assumes that a "factory reset" will un-do the modifications, but in the case of the Moto X (with all the Write Protect-disable exploits and safestrap), the modifications actually persist through a factory reset.

samwathegreat said:
Haha, yes, I was hesitant to suggest there may be confusion between bootloader and recovery.... Glad you were on top of that one...
The return to stock thread is located here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Again, manual method is easier and faster.
You will flash the 4.4.2 Sprint SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
Click to expand...
Click to collapse
Well, I followed the directions and it seemed to flash ok. Booted it up, wanted to activate (I canceled that- I dont have service on the phone yet), everything seemed normal. Went back to flash TWRP, same behavior as before. Any other ideas?

slushpupie said:
Well, I followed the directions and it seemed to flash ok. Booted it up, wanted to activate (I canceled that- I dont have service on the phone yet), everything seemed normal. Went back to flash TWRP, same behavior as before. Any other ideas?
Click to expand...
Click to collapse
A couple more: some individuals have reported that they had issues using a USB 3.0 port. If possible, use a USB 2.0 port to flash the recovery.
If you flashed ALL the partitions in the SBF file starting with gpt.bin (basically manually executed the commands in the XML file, IN ORDER), it -should- have worked.
You might also try flashing twrp from a different PC...
OR
You can try flashing TWRP 2.6.3.1 from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
This version is confirmed to work on all versions up to and including 4.4.2, so as long as you aren't on 4.4.3 yet, you can give this a shot.
And lastly, since I don't know exactly where you got the mfastboot binary, be sure to try the mfastboot binary linked in the 'return to stock' thread. That one is confirmed to work.

2 suggestions:
- try a different TWRP - I'm using a 2.7 that is referred to in one of the threads here
- after flashing > use the volume down button to highlight boot to recovery, and the volume up button to select (execute) that command ... my first time I tried the power button to select it and that doesn't work. I experienced some strange issues when trying to flash recovery if I didn't immediately boot into recovery (don't power down).

jasoraso said:
2 suggestions:
- try a different TWRP - I'm using a 2.7 that is referred to in one of the threads here
Click to expand...
Click to collapse
Ive tried a few, but will see if I can find some more to try. There seems to be no negative to trying them at this point.
jasoraso said:
- after flashing > use the volume down button to highlight boot to recovery, and the volume up button to select (execute) that command ... my first time I tried the power button to select it and that doesn't work. I experienced some strange issues when trying to flash recovery if I didn't immediately boot into recovery (don't power down).
Click to expand...
Click to collapse
The volume-key navigation is familiar to me (Ive had Android devices going back to the Samsung Moment), and I wasnt sure if I was getting into recovery or not since it just booted normally when I select recovery from the boot menu. However, when I specifically boot to recovery with 'adb reboot recovery' I get the tell-tale "No command" screen indicating I still have stock recovery.

slushpupie said:
Ive tried a few, but will see if I can find some more to try. There seems to be no negative to trying them at this point.
The volume-key navigation is familiar to me (Ive had Android devices going back to the Samsung Moment), and I wasnt sure if I was getting into recovery or not since it just booted normally when I select recovery from the boot menu. However, when I specifically boot to recovery with 'adb reboot recovery' I get the tell-tale "No command" screen indicating I still have stock recovery.
Click to expand...
Click to collapse
If you boot into stock recovery on Moto X, it shouldn't say "No command".... It should show "Dead Andy" - the broken android with the exclaimation point.
Are you trying to do this while android is booted? If so, unplug the USB, turn off the phone. Now hold down VOL DOWN and turn it back on. You should be on the bootloader screen (AP Fastboot mode). Plug the USB back in now
(^ I realize you probably already know the procedure, but good to have it here for others that might visit this thread)
Now VOL DOWN to recovery and VOL UP to boot it
What happens? Do you see Dead Andy?
I just tested the procedure on my phone (after flashing stock recovery back). After I select recovery and VOL UP to boot it, it takes less than 10 seconds for Dead Andy to appear. Pressing VOL UP + POWER brings up the stock recovery menu: reboot, apply update, wipe cache, etc. etc.
EDIT: I also just tried rebooting from within android as you stated you had done. After typing adb reboot bootloader, the phone promptly booted to the Dead Andy Stock Recovery screen.
Nowhere did it say "no command" on either the device itself, or the command prompt from which the adb command was executed...

samwathegreat said:
A couple more: some individuals have reported that they had issues using a USB 3.0 port. If possible, use a USB 2.0 port to flash the recovery.
Click to expand...
Click to collapse
My MacBook Pro only has USB3.0 ports. I would expect an issue to show some error, though (like in the transfer). It seems everything transfers just fine; it just doesn't seem to take.
samwathegreat said:
If you flashed ALL the partitions in the SBF file starting with gpt.bin (basically manually executed the commands in the XML file, IN ORDER), it -should- have worked.
Click to expand...
Click to collapse
It appeared the full SBF flashing process worked. It reset everything and prompted me for activation.
samwathegreat said:
You might also try flashing twrp from a different PC...
Click to expand...
Click to collapse
I dont really have anything different to try. Ive got another MBP, but its pretty much identical, and I get the same results when I try there. I have several VMs I can try- Ive tried with Win7-64bit (as mentioned in the original post) but that was the same too. I could try Linux too, if I get the time to set one up, but my gut says it wont be any different.
samwathegreat said:
You can try flashing TWRP 2.6.3.1 from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
This version is confirmed to work on all versions up to and including 4.4.2, so as long as you aren't on 4.4.3 yet, you can give this a shot.
Click to expand...
Click to collapse
Since I just reflashed back to the stock image, it is 4.4.2. Ive tried this version as well, with the same result.
samwathegreat said:
And lastly, since I don't know exactly where you got the mfastboot binary, be sure to try the mfastboot binary linked in the 'return to stock' thread. That one is confirmed to work.
Click to expand...
Click to collapse
Being on a Mac makes this a bit more challenging, but yes, I did try this in my Win7 virtual machine with the same results.

samwathegreat said:
If you boot into stock recovery on Moto X, it shouldn't say "No command".... It should show "Dead Andy" - the broken android with the exclaimation point.
Are you trying to do this while android is booted? If so, unplug the USB, turn off the phone. Now hold down VOL DOWN and turn it back on. You should be on the bootloader screen (AP Fastboot mode). Plug the USB back in now
(^ I realize you probably already know the procedure, but good to have it here for others that might visit this thread)
Now VOL DOWN to recovery and VOL UP to boot it
What happens? Do you see Dead Andy?
Click to expand...
Click to collapse
Yes, I see the dead andy image, with the no command message below him.
No, I am doing this from the bootloader. When I attempt to load recovery from the bootloader, I see the white unlocked warning image, then it goes and boots normally. Once into Android, I can issue 'adb reboot recovery' and that's when I see dead andy with the no command message. Confused yet? Cause I am.
samwathegreat said:
I just tested the procedure on my phone (after flashing stock recovery back). After I select recovery and VOL UP to boot it, it takes less than 10 seconds for Dead Andy to appear. Pressing VOL UP + POWER brings up the stock recovery menu: reboot, apply update, wipe cache, etc. etc.
EDIT: I also just tried rebooting from within android as you stated you had done. After typing adb reboot bootloader, the phone promptly booted to the Dead Andy Stock Recovery screen.
Nowhere did it say "no command" on either the device itself, or the command prompt from which the adb command was executed...
Click to expand...
Click to collapse
Im really at a loss then.. Ill try to restore the stock images again. Maybe I missed something the first go around.

slushpupie said:
Im really at a loss then.. Ill try to restore the stock images again. Maybe I missed something the first go around.
Click to expand...
Click to collapse
I suggest a slight variation:
After you extract the entire SBF file to the same folder where mfastboot resides:
First, boot to bootloader. Next, issue the following commands:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
Device should reboot right back to bootloader. Now issue these commands (we are going to use mfastboot for ALL commands, and YES, we are repeating gpt and motoboot again. this is intentional):
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem config carrier sprint
mfastboot oem fb_mode_clear
mfastboot reboot
Lets see if we can flash TWRP now. I helped another user on a MAC with a similar issue, and this resolved it for him. I'm hopeful we will fix your issue as well.

samwathegreat said:
I suggest a slight variation:
After you extract the entire SBF file to the same folder where mfastboot resides:
First, boot to bootloader. Next, issue the following commands:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
Device should reboot right back to bootloader. Now issue these commands (we are going to use mfastboot for ALL commands, and YES, we are repeating gpt and motoboot again. this is intentional):
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
<...>
Lets see if we can flash TWRP now. I helped another user on a MAC with a similar issue, and this resolved it for him. I'm hopeful we will fix your issue as well.
Click to expand...
Click to collapse
That did it, thanks! I wonder what is going on that I had to flash partition and motoboot twice. In any event, Im off and running. Thanks again!

slushpupie said:
That did it, thanks! I wonder what is going on that I had to flash partition and motoboot twice. In any event, Im off and running. Thanks again!
Click to expand...
Click to collapse
GPT stands for GUID Partition Table.
We aren't quite sure why this method works with stubborn flashes, but this is the theory:
We think that if the partition table somehow gets corrupted, the bootloader enforces write protection (on some or all partitions) even if you are unlocked...
The trick is to just flash the partition table, and the bootloader images, then immediately reboot, so the bootloader can load the NON-Corrupt partition table. Once the system reboots, all subsequent partition flashes seem to 'stick' without issue. It seems to involve some sort of 'bug' in the write protection implementation.
Regardless, once it is fixed, so is the issue. You shouldn't need to double-flash any partitions after rebooting like we did this time. AFAIK, all the users who got fixed using the above procedure have reported no further problems.
Just remember to never flash a previous version of android without checking here first. Most users who have to undergo the above procedure tried to downgrade for some reason, and many of them ended up having to do the procedures listed in the "Unbrick" thread (Not fun...)
Glad it all worked out.

samwathegreat said:
GPT stands for GUID Partition Table.
We aren't quite sure why this method works with stubborn flashes, but this is the theory:
We think that if the partition table somehow gets corrupted, the bootloader enforces write protection even if you are unlocked...
The trick is to just flash the partition table, and the bootloader images, then immediately reboot, so the bootloader can load the NON-Corrupt partition table. Once the system reboots, all subsequent partition flashes seem to 'stick' without issue. It seems to involve some sort of 'bug' in the write protection implementation.
Click to expand...
Click to collapse
Makes sense. Given that the bootloader is the one area you cant easily fix if you screw up, I would add as much protection as possible too. Of course, I would also add error messages... Makes me wonder if there is some hard coded entries in the event the GTP gets screwed up. Has anyone attempted to inspect the gpt.bin file?
samwathegreat said:
Regardless, once it is fixed, so is the issue. You shouldn't need to double-flash any partitions after rebooting like we did this time. AFAIK, all the users who got fixed using the above procedure have reported no further problems.
Just remember to never flash a previous version of android without checking here first. Most users who have to undergo the above procedure tried to downgrade for some reason, and many of them ended up having to do the procedures listed in the "Unbrick" thread (Not fun...)
Glad it all worked out.
Click to expand...
Click to collapse
Good to know. I dont plan on doing anything fancy, just want root for TI backups, really. I guess Ill see how well flashing the bootloader works again when the 4.4.3 OTA comes around to my phone.

[Q] Attempted to Downgrade and now bricked [solved]

First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
**EDIT**
If you have done the same bone-head move I made, then follow these simple steps.
1. Use RSD lite to update to 4.4.4
2. Follow this guide to then root your device once you have updated to 4.4.4
This works because your bootloader is unlocked, thanks to sunshine.

wisenick said:
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
Click to expand...
Click to collapse
You should have never attempted to downgrade...
Try using fastboot & mfastboot.
Unplug, then turn off the phone. Boot it into bootloader mode. Once in BL, plug usb into PC.
You must have at least minimal adb/fastboot, AND the mfastboot binary (search it).
Unzip the 4.4.4 SBF into the SAME FOLDER that both fastboot and mfastboot are in.
Open a command prompt, browse to the folder containing the unzipped files, fastboot, and mfastboot. Now execute the following commands in this exact order:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
[the device will reboot into the bootloader] ignore the fact that some commands are being run twice...
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img [make absolutely sure to use the Mfastboot binary for flashing 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
fastboot erase clogo
fastboot reboot
If you see an error about variable not supported, ignore it. If you get a different error, post back with a screenshot.
Does it boot into android now? You should be 100% stock, unlocked. Ready to flash TWRP and root.

wisenick said:
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
Click to expand...
Click to collapse
RSD 422 means a downgrade. What did it "say"?
Downgrading is the no no.
---------- Post added at 06:11 PM ---------- Previous post was at 06:07 PM ----------
http://forum.xda-developers.com/showpost.php?p=55491148&postcount=10

samwathegreat said:
You should have never attempted to downgrade...
Try using fastboot & mfastboot.
Unplug, then turn off the phone. Boot it into bootloader mode. Once in BL, plug usb into PC.
You must have at least minimal adb/fastboot, AND the mfastboot binary (search it).
Unzip the 4.4.4 SBF into the SAME FOLDER that both fastboot and mfastboot are in.
Open a command prompt, browse to the folder containing the unzipped files, fastboot, and mfastboot. Now execute the following commands in this exact order:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
[the device will reboot into the bootloader] ignore the fact that some commands are being run twice...
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img [make absolutely sure to use the Mfastboot binary for flashing 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
fastboot erase clogo
fastboot reboot
If you see an error about variable not supported, ignore it. If you get a different error, post back with a screenshot.
Does it boot into android now? You should be 100% stock, unlocked. Ready to flash TWRP and root.
Click to expand...
Click to collapse
Thank you, however when I try the first command "fastboot flash boot loader moto boot.img" it says "(bootloader) Variable not supported! Then says (bootloader) Permission denied
But I followed the rest of the directions and it still will only boot into fastboot.

wisenick said:
Thank you, however when I try the first command "fastboot flash boot loader moto boot.img" it says "(bootloader) Variable not supported! Then says (bootloader) Permission denied
Click to expand...
Click to collapse
Did you really put spaces in between boot and loader? And Moto and boot?

samwathegreat said:
Did you really put spaces in between boot and loader? And Moto and boot?
Click to expand...
Click to collapse
No sorry, auto correct on the wife's phone.

wisenick said:
No sorry, auto correct on the wife's phone.
Click to expand...
Click to collapse
A "Permission denied" error sounds strange to me....don't recall having seen that one before.
Though I'm rather certain that your downgrade attempt (big no-no) is the culprit, I'm curious if @jcase might have any suggestions...

1) I don't think you are bricked, this should be fixable. This is due to you flashing older firmware to a device that has been updated, nothing to do with sunshine.
2) your title makes it sound like sunshine to blame, this is really bad for me. SunShine CANT brick motorola (nor htc) phones. We simply have too many safety checks, and verification. If you were able to flash and boot TWRP (which you were because you took a backup) then it can't be sunshine. It would be great if you changed the title to be more accurate.
Having said that, I have no problem helping you recover your phone, it certainly isn't bricked
I'm out from 10amPST to 2pmPST tomorrow, but please email me jcase AT cunninglogic DOT com, and I will have you up on your feet in minutes. Probably setup teamviewer and I will just remote in and do my best.
wisenick said:
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
Click to expand...
Click to collapse

samwathegreat said:
Now execute the following commands in this exact order:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
I don't have the sbf files handy right now, so I can't check -- are you sure the order is bootloader then gpt? I thought it was the other way around. A quick check of the xml file in the sbf will give the correct order.

jcase said:
...nothing to do with sunshine.
2) your title makes it sound like sunshine to blame...
Click to expand...
Click to collapse
That is what I first thought when I read the subject...
 @wisenick, you even mention in your OP you don't blame Sunshine, so why mention it in the subject?
Can you change the subject of this thread to "Attempted to Downgrade and now bricked" or "Attempted to downgrade and now phone wont boot"? That would be more accurate.

piccit said:
I don't have the sbf files handy right now, so I can't check -- are you sure the order is bootloader then gpt? I thought it was the other way around. A quick check of the xml file in the sbf will give the correct order.
Click to expand...
Click to collapse
Just checked the XML and it is gpt then bootloader. I'll see if that fixes things.

Try flashing an alternate bootloader like TWRP or CWN with mfastboot. My recovery wasn't working for awhile and all I had to do was reflash it.

Verttex said:
Try flashing an alternate bootloader like TWRP or CWN with mfastboot. My recovery wasn't working for awhile and all I had to do was reflash it.
Click to expand...
Click to collapse
Thank you but I've tried that. It says that it flashed but when I try to boot into recovery it simply boots into fastboot

piccit said:
I don't have the sbf files handy right now, so I can't check -- are you sure the order is bootloader then gpt? I thought it was the other way around. A quick check of the xml file in the sbf will give the correct order.
Click to expand...
Click to collapse
Double checked the order and according to the xml , its gpt first. However I still get an error when I try to flash motoboot

Well I couldn't handle not having a phone much longer so I used rsd to go to 4.4.4, have I lost root?

wisenick said:
Well I couldn't handle not having a phone much longer so I used rsd to go to 4.4.4, have I lost root?
Click to expand...
Click to collapse
If Sunshine unlocked your bootloader, you should be able to do whatever.

wisenick said:
Well I couldn't handle not having a phone much longer so I used rsd to go to 4.4.4, have I lost root?
Click to expand...
Click to collapse
Yes you lost root! but
If you used sunshine, you turned your consumer phone into a developer phone, meaning you will always be able to root it trivially and properly.

True. if your back in android w/o root
Download Supersu in a zip file
boot to bootloader
fastboot flash new recovery
reboot into the new recovery
flash supersu zip
you have root! Easy w/ an unlocked bootloader!

Soft bricked XT1052

Soft bricked when trying to flash stock 5.1 back from CM13. Somehow managed to wipe the entire phone and now all I have access to are fastboot and TWRP recovery. I have no ROM ZIPs to access in TWRP since internal storage was wiped. I tried ADB sideload but says it can't mount /data/. My computer recognises the phone as a fastboot device but not as an ADB device.
Is there any coming back from this?

I've downloaded the retail GB stock image file for XT1052 but I can't flash the partition as I just get error 'update gpt_main version failed' 'preflash validation failed for GPT'

Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed

varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I've downloaded the RetGB for 5.1 for XT1052 from here: https://firmware.center/firmware/Motorola/Moto X (1st gen-2013)/Stock/XT1052/
But it seems to be missing a number of key files that are described in option 5 of the link you posted. Am I missing something? I'm also still getting errors each time I try to flash the partition except now CMD is just showing:
"target max-download-size: 768MB error: cannot load 'gpt.bin': no error. Any ideas? Thanks.
My only other thought at this point is to try and flash a ROM in recovery using USB-OTG. Could that work? For example, if I download stock ROM or even the CM 14 I had on previously before everything got wiped and put that on an external drive and flashed in TWRP?

varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I just moved cmd.exe into my platform tools folder where everything else is and tried again to flash the partition. Instead this time I get:
C:\Android-SDK\platform-tools>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.335s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.328s
And then on the phone itself in the fastboot screen it shows:
"downgraded security version. update gpt_main version failed. preflash verification failed for GPT'. I thought this would mean the bootloader I'm trying to flash would represent a downgrade but I checked against the info.txt file in the recovery image zip and it says 30.BE which matches the 30.BE in my fastboot screen...

OK I've now got an OS. Managed to reinstall CM14 using usb-otg. Figured that was the safest bet given it was the last OS installed.
Problem I now have is that I can't get any service (I could previously on CM14 before all this happened). Is it possible that when I managed to completely wipe the phone that I would the relevant modem/radio files?
Thanks

Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Sent from my XT1060 Dev Ed

varunpilankar said:
Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Click to expand...
Click to collapse
That doesn't have my version - xt1052.
Would this be to return my mobile service? I've got back on CM14 but all my IMEI and sim data has wiped so I can't get service. Not sure if I need to use the 5.1 factory image I have and just flash modem files. Seen elsewhere that I could try
Fastboot flash modem NON-hlos.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Would that do the trick do you reckon?

Take a nandroid backup & try doing it!
There is also a 5.1 stock zip Rom & try that too, might be helpful.
Sent from my XT1060 Dev Ed

Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,

hachamacha said:
Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,
Click to expand...
Click to collapse
Thanks. Will give that a look as I would like to know how to easily go back to stock in the event of catastrophe - I've been trying to flash back using both fastboot and TWRP but it fails every time due to 'downgrade security' etc. even though I know I'm using the same bootloader as in the stock ROM.
I managed to get my IMEI and service back by flashing
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
I've now got Resurrection Remix on as I thought I'd see if that would fix my service issues (it didn't - so still had to do the steps above). But have managed to learn a lot over the past few days to bring my phone back from death! I'm mainly used to Sony phones so this has been an experience.