Coverting Moto X 1097 Telus to Pure hab check failed - X 2014 Q&A, Help & Troubleshooting

I'm trying to convert my Moto X 1097 to 1095 pure. When I try flashing files with mfastboot I get hab check failed for boot and hab check failed for recovery. It's running 4.4.4 pure but I assume still has old recovery as it won't boot into recovery. I have abd all and downloaded mfastboot v2. Why am I getting these errors? Bootloader unlocked.

Are you trying to flash 4.4.4 or 5.0?
Motoboot and gpt can never be downgraded, some files will always show they failed the hab check even though they are ok as they aren't the original files.
If you flash the entire 4.4.4 or 5.0 Pure firmware package you will have no radio at all and will need to use the original NON-HLOS.bin from the matching Telus package to get it back.
If you want to try the Pure 5.1 soak/leak then flash the full Pure 5.0 package and then apply the soak update via stock recovery. At that point your radios will work as the 5.1 soak appears to include a modem/radio that works with the XT1097.

Ok thanks for info. So i flashed over my telus lollipop to 4.4.4 tmobile and then ota. So when I reboot into bootloader and choose recovery it just goes to a white screen with a ? in it. But if I use cmd adb reboot recovery it works and goes into recovery so I was able to ota to 5.0. Do you think I have the wrong bootloader or what? I've ota to 5.1 now and still can't get bootloader to launch recovery. Also once in recovery I chose wipe cache and it rebooted phone not sure if that's normal. I came from nexus phone so just learning this moto stuff. I'll post a couple pictures thanks in advance. Basically if I want to flash back to stock telus or if I brick my phone and need to get to recovery I won't be able too. Hopefully just something simple.

matt1515 said:
Ok thanks for info. So i flashed over my telus lollipop to 4.4.4 tmobile and then ota. So when I reboot into bootloader and choose recovery it just goes to a white screen with a ? in it. But if I use cmd adb reboot recovery it works and goes into recovery so I was able to ota to 5.0. Do you think I have the wrong bootloader or what? I've ota to 5.1 now and still can't get bootloader to launch recovery. Also once in recovery I chose wipe cache and it rebooted phone not sure if that's normal. I came from nexus phone so just learning this moto stuff. I'll post a couple pictures thanks in advance. Basically if I want to flash back to stock telus or if I brick my phone and need to get to recovery I won't be able too. Hopefully just something simple. Also so what do I have to do to make these commands work [fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img. Only flash these when it's the exact version? /QUOTE]
Click to expand...
Click to collapse

matt1515 said:
matt1515 said:
Ok thanks for info. So i flashed over my telus lollipop to 4.4.4 tmobile and then ota. So when I reboot into bootloader and choose recovery it just goes to a white screen with a ? in it. But if I use cmd adb reboot recovery it works and goes into recovery so I was able to ota to 5.0. Do you think I have the wrong bootloader or what? I've ota to 5.1 now and still can't get bootloader to launch recovery. Also once in recovery I chose wipe cache and it rebooted phone not sure if that's normal. I came from nexus phone so just learning this moto stuff. I'll post a couple pictures thanks in advance. Basically if I want to flash back to stock telus or if I brick my phone and need to get to recovery I won't be able too. Hopefully just something simple. Also so what do I have to do to make these commands work [fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img. Only flash these when it's the exact version? /QUOTE]
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Stop using the power button to try to select recovery like you would on a Nexus device - use the volume up button and you'll be fine

Hahah dang I feel dumb

So just to conclude if I did want to go back to fresh stock Telus. Would these [fastboot flash partition gpt.bin and fastboot flash motoboot motoboot.img still not work and not be needed? I understand motoboot is bootloader but what is got.bin?

If you go back to Telus firmware those two files likely won't update. I recommend you always go through the motions and if they fail it is fine to continue with the other files. When Telus 5.1 is released you will likely be able to update those two files again - it doesn't seem to really matter though with the 2014 Moto X.

Ok good information one question I have to ask. Does it really matter what fastboot I use and if so what is the best one to use for this phone?

Do you mean fastboot versus mfastboot(motorola specific version) ?
It only matters with the system image which is too large for regular fastboot and required the Motorola specific version which can handle the larger files and/or the sparse files.

Exactly the answer I was looking for. Thanks a lot!
Sent from my XT1095 using XDA Free mobile app

Related

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.

Stuck rebooting to TWRP after OTA Download?

I thought I prevented my phone from downloading the OTA to 4.4.3 on my Dev Edition Unlocked bootloader running 4.4.2 and TWRP. I obviously did not and now my phone keeps rebooting into TWRP.
Is there a way to stop this and clear it out somehow?
reno55 said:
I thought I prevented my phone from downloading the OTA to 4.4.3 on my Dev Edition Unlocked bootloader running 4.4.2 and TWRP. I obviously did not and now my phone keeps rebooting into TWRP.
Is there a way to stop this and clear it out somehow?
Click to expand...
Click to collapse
Try using Titanium Backup to freeze MotorolaOTA
samwathegreat said:
Try using Titanium Backup to freeze MotorolaOTA
Click to expand...
Click to collapse
Actually I think I can fix by flashing stock recovery but where can I find the stock recovery image?
reno55 said:
Actually I think I can fix by flashing stock recovery but where can I find the stock recovery image?
Click to expand...
Click to collapse
YES, you can fix by flashing stock recovery assuming you haven't heavily modified your system. Flashing the stock recovery will make the phone try to flash the OTA.
You'll need to download the SBF for your phone here: http://sbf.droid-developers.org/phone.php?device=0
Unzip the file. I'm assuming you already have the fastboot and mfastboot binaries as well as the android SDK.
Place the file "recovery.img" in the same folder as mfastboot & fastboot. Make sure USB Debugging is enabled (or manually boot into bootloader).
Type mfastboot flash recovery recovery.img
Done.
Good Luck
samwathegreat said:
YES, you can fix by flashing stock recovery assuming you haven't heavily modified your system. Flashing the stock recovery will make the phone try to flash the OTA.
You'll need to download the SBF for your phone here: http://sbf.droid-developers.org/phone.php?device=0
Unzip the file. I'm assuming you already have the fastboot and mfastboot binaries as well as the android SDK.
Place the file "recovery.img" in the same folder as mfastboot & fastboot. Make sure USB Debugging is enabled (or manually boot into bootloader).
Type mfastboot flash recovery recovery.img
Done.
Good Luck
Click to expand...
Click to collapse
I think I just did this correctly.......it is on Android is upgrading now.....
I can just flash a custom recovery now right?
reno55 said:
I think I just did this correctly.......it is on Android is upgrading now.....
I can just flash a custom recovery now right?
Click to expand...
Click to collapse
If the upgrade is successful, absolutely.
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
download twrp from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
samwathegreat said:
If the upgrade is successful, absolutely.
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
download twrp from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
Click to expand...
Click to collapse
Can I flash philz?
reno55 said:
Can I flash philz?
Click to expand...
Click to collapse
Don't see why not. Just substitute the filename for philz recovery instead.
Get Philz here: http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
I have not used Philz personally...I prefer TWRP, but it looks like (unlike TWRP), that there is a different img for each variant of the Moto X. You will need to be careful to download the correct one.
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup, TWRP and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is there no way to complete the OTA without flashing a stock recovery? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
frankie_p said:
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
Click to expand...
Click to collapse
Ugh! I am having all kinds of issues with 4.4.3. There is not a way to go back to 4.4.2 is there?
frankie_p said:
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
Click to expand...
Click to collapse
YES, that is the best way to do it. You can -try- disabling xposed, and un-doing any major modifications you have done (like freezing or removing any system apps). You want it to be as close to stock as possible before you try to accept the OTA, which includes flashing back the stock recovery.
SBFing back to stock 4.4.2 FIRST, and accepting the update, THEN flashing TWRP and rooting, then re-configuring everything and installing your apps is MUCH safer and pretty much guarantees that your filesystem will be 100% intact.
If it were ME, I would SBF first -- for whatever that's worth...
Good Luck
---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------
reno55 said:
Ugh! I am having all kinds of issues with 4.4.3. There is not a way to go back to 4.4.2 is there?
Click to expand...
Click to collapse
Sure. It's just slightly more complicated. You'll need the entire 4.4.2 SBF for your carrier.
Do this: Reboot to bootloader
FIRST, JUST flash gpt.bin and motoboot.img:
fastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
Now you need to REBOOT back into bootloader (to prevent gpt.bin mis-match -- if you don't reboot here, you will get errors). Do this by typing:
mfastboot reboot-bootloader
Now flash the rest of the files:
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
Reboot, and you should be back to stock 4.4.2
And finally the disclaimer: DO NOT TRY TO DOWNGRADE TO ANY VERSION PRIOR TO 4.4.2 .....if you don't want a brick.
It's ok to downgrade 4.4.3 to 4.4.2 because the bootloader version did not change. It is NOT safe to downgrade to anything prior (4.4 or 4.2.2).

[Q] really need some help please. totally borked my new moto x dev edition

just got my brand new developer edition moto x. successfully unlocked the bootloader, successfully installed TWRP recovery, successfully installed SuperSU, rebooted the phone and stupidly tried to update the software through the phone's system software update, got stuck in a reboot loop, and then attempted to flash a ROM. realized i bricked it. now i can't sideload a ROM and every time i try, i reboot to recovery, use the adb sideload, it looks like it's loading, phone says successful, asks if i want to reboot and then tells me that there is no OS.
i am brand new to this, and i've clearly effed it up, but really not sure how to fix it.
i attempted to follow the instructions here http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 but using the step two method but got to fastboot flash partition gpt.bin and got an error in terminal (i'm on a mac)
i would be most grateful for any help at all. i'm really stuck.
thanks in advance.
First... Boot the phone into Fastboot/Bootloader mode.
What is the version listed on the second line?
Next, you'll want to flash the rom that matches that bootloader version using a slight variation of Option 2 on that link... For example, if the bootloader on your phone is 30.B4 then fash the stock 4.4.2 SBF, if 30.B7 flash 4.4.4.
Start the steps with....
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
then use the rest of those commands AS they are written. yes, you'll be repeating the flashing of GPT.Bin and Motoboot.img, and that is intentional!
When you get back to stock, I suggest you take a few minutes/hours to read and familiarize yourself with what has been written.. Like don't take an OTA unless you have the STOCK recovery. If you have a 3rd party recovery and take an OTA you'll be stuck in a boot loop (to get out, boot the phone in fastboot and from the PC.. fastboot erase cache followed by fastboot reboot will stop the loop, then you can flash stock recovery back on there to take the OTA. Never DOWNGRADE the rom on your phone once you have 4.4.2 and up or you will brick, etc.

[Q] Unable to upgrade rooted Nexus 6 to 5.1.1

I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin
rambo8wtv said:
I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin
Click to expand...
Click to collapse
no matter how many times you try, you will never ever be able to update your rooted n6 via ota. if any system files changed from stock, an ota will download but will always error out. you can update several ways.. a. you can flash a 5.1.1 ROM via twrp. or b. you can fastboot flash 5.1.1.
2 things.
1. You must be 100% stock, no root, no custom recovery to OTA
2. The 5.0.2 message if you look probably.mentions deestroy..this is.because TWRP is using 5.0.2 sources - butnits irrelevant anyway give point 1
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
twrp can not flash the ota or system img. you flash the system img via fastboot(not adb) and while you're in your bootloader.
rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
You cannot use the OTA file no matter what vehicle you use.
danarama said:
You cannot use the OTA file no matter what vehicle you use.
Click to expand...
Click to collapse
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data
starfish_001 said:
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data
Click to expand...
Click to collapse
He'll probably want to not flash recovery. And if he has a custom kernel, may not want to flash boot either.
Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.
rambo8wtv said:
Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.
Click to expand...
Click to collapse
here too, many people try it with adb then claim it doesn't work. but its fastboot that you need, and while you are in the bootloader. adb will never work in the bootloader, only fastboot.

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.

Categories

Resources