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.

Telus XT1097 moto x --- Missing my baseband! Help!

Soooo i was a big dumby and i wrote over the modem in order to get the update.
Now i have no signal/service available , or compatible baseband flashed.
Wifi works, everything else is amazing !!
Currently
Android 5.0
Baseband: Unknown <------
System version: 22.11.6.victara_tmo.tmo.en.US tkpca
Build Number: LXE22.39-6
If any one successfully backs up the telus baseband could you please post it ?!!?
So screwed at the moment

If you can tell me how to do so I would be happy to.
---------- Post added at 03:32 PM ---------- Previous post was at 02:51 PM ----------
pipesdl said:
If you can tell me how to do so I would be happy to.
Click to expand...
Click to collapse
I might have figured it out, use at your own risk.
https://drive.google.com/file/d/0B5ErTnQGFRMaVjRaWDV2dFlqMzg/view?usp=sharing

adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.

floepie said:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.
Click to expand...
Click to collapse
Ah, didn't realize two files were needed. Links below.
FSG
https://drive.google.com/file/d/0B5ErTnQGFRMaN0JjLUx1RDVZakk/view?usp=sharing
NON-HLOS
https://drive.google.com/file/d/0B5ErTnQGFRMaWHVXZEhwS2UwU2M/view?usp=sharing

pipesdl said:
Ah, didn't realize two files were needed. Links below.
FSG
NON-HLOS
[
Click to expand...
Click to collapse
Thanks!!! I tried flashing the FSG but it wants the file as a mbn. I tried changing the extension but it still didnt take it.
Although the modem bin file flashed fine, rebooted but still no service

I think I did extract it with an mbn extension, don't know if it will make a difference but I'll upload shortly.
Let me know if it works.
https://drive.google.com/file/d/0B5ErTnQGFRMaQk9fcC05amJvTDg/view?usp=sharing

OscarAlert said:
Thanks!!! I tried flashing the FSG but it wants the file as a mbn. I tried changing the extension but it still didnt take it.
Although the modem bin file flashed fine, rebooted but still no service
Click to expand...
Click to collapse
You need the following commands. Just keep your mbn file.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

I would love to know if those modem files work for the Telus phone after flashing, as the only thing holding me back is that it currently won't let me back up my own. If it does then lollipop here I come!

Those two files worked! Thanks so much to everyone who helped out in this thread. Successfully running Lollipop on my Telus Moto X now!

Awesome, can you let me know what steps you followed in addition to the steps above?

floepie said:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.
Click to expand...
Click to collapse
Hi floepie, does the adb shell and su commands provide temporary root? ie Upon rebooting root will no longer be accessible? I'm looking to back up my modem files before flashing to xt1095 Lollipop.
Also, for anyone else following this thread, I'm a bit confused by the discussion about fsg.bin vs fsg.mbn; are there two different fsg files or is it simply that when pulling fsg.bin you save it as/rename it to have an mbn extension?
---------- Post added at 11:20 AM ---------- Previous post was at 11:13 AM ----------
And I'm wondering what impact the different modems even have... Is it possible that I can run the Telus Modem even though my provider is Wind Mobile (a Telus roaming partner)?
And what if I were to hypothetically take this phone (assuming sim-unlocked) and switch to say Bell, Telus, or Rogers; without tampering it'd still have the original Wind Mobile modem so what impact would that have on functionality/operation if I switched to a new service provider?

Kodiak1 said:
Hi floepie, does the adb shell and su commands provide temporary root? ie Upon rebooting root will no longer be accessible? I'm looking to back up my modem files before flashing to xt1095 Lollipop.
Also, for anyone else following this thread, I'm a bit confused by the discussion about fsg.bin vs fsg.mbn; are there two different fsg files or is it simply that when pulling fsg.bin you save it as/rename it to have an mbn extension?
---------- Post added at 11:20 AM ---------- Previous post was at 11:13 AM ----------
And I'm wondering what impact the different modems even have... Is it possible that I can run the Telus Modem even though my provider is Wind Mobile (a Telus roaming partner)?
And what if I were to hypothetically take this phone (assuming sim-unlocked) and switch to say Bell, Telus, or Rogers; without tampering it'd still have the original Wind Mobile modem so what impact would that have on functionality/operation if I switched to a new service provider?
Click to expand...
Click to collapse
I'm pretty sure that in order to make an image of your baseband files, you need to be rooted. Root access is granted by SuperSU. As for the extensions on the fsg file, it doesn't matter what you call it. You just have to be consistent when copying it or applying it back to your device. I think someone posted on the forum using mbn and then used bin for applying it, which for obvious reasons wouldn't work.

This might be a dumb question, but do you have to always flash the baseband files or modem files (not sure which is correct) every time there is a new update once you have converted to XT1095
I have a moto x 2014 (XT1097 ) from Wind Mobile and am trying to decide if i should keep it or not.
Nvm .... see the answer to my question here......
http://forum.xda-developers.com/moto-x-2014/help/converting-xt1097-to-pure-edition-t2912729/page5

Take pity on me
Ok, so I unboxed my new phone UK (XT1092), unlocked the bootloader after it updated to Lollipop, and messed up somewhere causing me to have to install stock rom again. After installing the stock rom (4.4.4) I do not have signal and the baseband is unknown as with the OP. I have attemped to follow multiple guided concerning the same fixes but have gotten no where and am now extremely stressed and confused. Previously if I had problems with signal I just reflash a radio but times seem to have changed. The phone now shows as a xt1095 when plugged into pc.
Where I went having messed up:
Where I then went having found I had a xt1092
Update on xt1092 worked! I did this:
1. Downloaded the 4.4.4 system image from xt1905 (first post for download link)
2. Extracted the zip
3. flashed over mfastboot.exe
Code:
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 flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
4. sideloaded the OTA update from first post
5. reboot
6. flashed back the original modem and fsg from xt1902, without erasing modemst1 and modemst2 -> https://www.androidfilehost.com/?fid=95784891001608300
Click to expand...
Click to collapse
Then realising I had no signal I followed this post:
YES!
I finally have Lollipop on my XT1092!!
I followed steff999's guide but encountered several problems with the modem and data connections etc.
I just couldn't figure out why flashing the XT1092 modem files didn't work.
Then I went back to my original firmware and did the procedure again.
But now I did not let it boot after the OTA Update and directly booted into fastboot mode and flashed the modem and fsg files.
Then after reboot I immediately had mobile service. IMEI and Baseband is back again.
I use Linux and it is very easy with Linux.
In a terminal just go to the folder with the files (no matter where they are!!).
After getting Android SDK I did:
Code:
$ sudo apt-get install android-tools-fastboot <<-- to install fastboot
$ cd /directory with your files...<<--- choose your folder
$ fastboot flash logo logo.bin
etc
after flashing the files put OTA.zip on phone. Go in recovery mode and apply update.
Then when it reboots directly go in fastboot mode and type:
$ cd /directory with your XT1092 modem files/
$ fastboot flash modem NON-HLOS.bin
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
now it boots into lollipop and it should recognize your sim card.
This is how it worked for me with Linux. Should be similar with Windows but I think the files for flashing have to be in fastboot directory then.
I did not use erase modem commands
I hope this will give hope back to people who encountered similar problems with the modem. I was about to give up but decided to give it a last try.
Click to expand...
Click to collapse
I am unsure how to get the OTA update onto the phone memory unless I power up and download, attempt at sideloading via adb resulted in the phone "aborting" at 100% sent.
So, could someone here please attempt to explain exactly what needs to be done
Currently about phone:
Android version: 5
Baseband version: unknown
System: 22.21.11.victara_tmo.tmo.en.US.retgb
Build number: LXE22.46-11
kernal: 3.4.42-gd7d30ea
Please.

THE-M1GHTY-BUKO said:
Ok, so I unboxed my new phone UK (XT1092), unlocked the bootloader after it updated to Lollipop, and messed up somewhere causing me to have to install stock rom again. After installing the stock rom (4.4.4) I do not have signal and the baseband is unknown as with the OP. I have attemped to follow multiple guided concerning the same fixes but have gotten no where and am now extremely stressed and confused. Previously if I had problems with signal I just reflash a radio but times seem to have changed. The phone now shows as a xt1095 when plugged into pc.
Where I went having messed up:
Where I then went having found I had a xt1092
Then realising I had no signal I followed this post:
I am unsure how to get the OTA update onto the phone memory unless I power up and download, attempt at sideloading via adb resulted in the phone "aborting" at 100% sent.
So, could someone here please attempt to explain exactly what needs to be done
Currently about phone:
Android version: 5
Baseband version: unknown
System: 22.21.11.victara_tmo.tmo.en.US.retgb
Build number: LXE22.46-11
kernal: 3.4.42-gd7d30ea
Please.
Click to expand...
Click to collapse
I converted my xt1097 to xt1095, with the tmo 4.4.4 firmware, I boot it but complete no setup, and just copy the OTA from PC to phones internal storage. No adb sideload.
I've had Brazil radios work on my rogers RAZR before. There is a full lollipop BR firmware in the development section. Is might try it.

drolgnir said:
I converted my xt1097 to xt1095, with the tmo 4.4.4 firmware, I boot it but complete no setup, and just copy the OTA from PC to phones internal storage. No adb sideload.
I've had Brazil radios work on my rogers RAZR before. There is a full lollipop BR firmware in the development section. Is might try it.
Click to expand...
Click to collapse
My problem is now fixed, thankyou.

For future reference for others, how did you fix the problem?
Sent from my XT1095 using Tapatalk

halfez said:
This might be a dumb question, but do you have to always flash the baseband files or modem files (not sure which is correct) every time there is a new update once you have converted to XT1095
I have a moto x 2014 (XT1097 ) from Wind Mobile and am trying to decide if i should keep it or not.
Nvm .... see the answer to my question here......
http://forum.xda-developers.com/moto-x-2014/help/converting-xt1097-to-pure-edition-t2912729/page5
Click to expand...
Click to collapse
Any chance you have a copy of the modem files for your moto x 2014 (XT1097 ) on Wind? I flashed the T-Mobile 5.0 xt1095, and don't think I properly backed up my files.

If you can explain to me how to extract the files from my phone using adb, sure. Coming from a nexus, not so good with adb

floepie said:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.
Click to expand...
Click to collapse
halfez said:
If you can explain to me how to extract the files from my phone using adb, sure. Coming from a nexus, not so good with adb
Click to expand...
Click to collapse
Come on, just do it!

Phone not booting after OTA

So today I got an update for a new firmware, it was a small 125 mb patch, no big deal. I downloaded it and installed it a couple of hours later, I leave it to install and when I'm back my phone is frozen on the Motorola logo and the "Powered by android" text written below, but it won't get past that. I left it for almost an hour and it won't boot, I tried forcing a reboot and it gets me back to the same screen.
Is there any way I could fix it, preferably while keeping my data? Especially the what's app gallery.
Thanks a lot guys, I'm kinda panicking here.
Ps. I'm not rooted, everything is completely stock.

it's Stuck on Moto Boto logo ?

Yes. I tried doing a factory reset and that doesn't work either, it sends me right back to the boot logo.

Sorry to not have any solutions but my girlfriends phone has probably had the exact same thing happen. At about 10PM tonight she got an update notification and told it to install. almost two hours later she checked the phone again to see it stuck on the boot logo and incredibly hot. She restarted it and same thing, stuck on the boot logo. Same as you, completely stock phone. Never been modified in anyway.
I had her go into recovery and wipe cache, no change at all. I've now had her do a factory reset twice as some similar problems mentioned that as a solution. No change, still just gets stuck on the boot screen.
My assumption at this point is that this update has completely trashed the phone and it's completely unrecoverable on the device at least.

I'm willing to learn how to install a new rom from scratch if that would help, preferably a stock one. The problem is that Motorola doesn't have any stores where I live, I ordered my phone off amazon.
So is there any method to fix it? You can instruct me if you could or at least tell me what to look for on google.
Thanks a lot man.

darthlawl said:
I'm willing to learn how to install a new rom from scratch if that would help, preferably a stock one. The problem is that Motorola doesn't have any stores where I live, I ordered my phone off amazon.
So is there any method to fix it? You can instruct me if you could or at least tell me what to look for on google.
Thanks a lot man.
Click to expand...
Click to collapse
I didn't think that you have any way to install urself stock without voiding warranty so u have 2 choices u can go for service or unlock and install any rom u want

vaisakmct said:
I didn't think that you have any way to install urself stock without voiding warranty so u have 2 choices u can go for service or unlock and install any rom u want
Click to expand...
Click to collapse
My warranty is already over, I just want stock because I like it.
Are you sure a rom installation would work?

Ps. I can't unlock the bootloader since I can't access the OS

Unlock boot loader does not acess to os it is simple
---------- Post added at 01:25 AM ---------- Previous post was at 01:23 AM ----------
Just go to fastboot mode and unlocking can done from pc and install twrp then u can flash roms

vaisakmct said:
Unlock boot loader does not acess to os it is simple
---------- Post added at 01:25 AM ---------- Previous post was at 01:23 AM ----------
Just go to fastboot mode and unlocking can done from pc and install twrp then u can flash roms
Click to expand...
Click to collapse
What do you mean?

I'm a total beginner when it comes to android, I'm more of a windows guy. Can you walk me through the steps?

It´s not that easy to guide someone through all the steps. First thing you have to do is unlock your bootloader,described here: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728. Read all the steps,it´s not that difficult.
You need all the drivers,by motorola and android, linked in the tutorial. I recomend Minimal ADB and Fastboot instead of Android SDK, it´s easier. Install it in the root of your windows partition,like C:\Minimal ADB and Fastboot. So if you open a command prompt the path is short and you know it.
After the unlock process you´ll need to flash a custom recovery, you can read how to do that here: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818.
There´s a part called Flashing TWRP Recovery . You don´t need to do that with Flashify (you surely can if you want but I think this way is easier to do), just download the custom recovery TWRP from here: https://dl.twrp.me/titan/.
Place the .img file in the Minimal ADB and Fastboot folder and connect the phone to the PC. After that you open a command prompt again from the Minmal ADB and fastboot folder (open the folder and hold Shift and right click and press "open command window here".
Now type the command
Code:
adb reboot bootloader
When the phone has booted to bootloader type
Code:
fastboot devices
A string of numbers should appear,that means your phone is connected.
Now type
fastboot flash recovery "name of the downloaded TWRP .img file", in your case that should be
Code:
fastboot flash recovery twrp-2.8.6.0-titan.img
Now everytime when you boot to recovery you´ll see a menu with a lot of features like install,wipe,backup,restore etc.
From here you can flash any rom you like, a stock rom, a stock based rom or any other like cyanogen or AOSP.
If you want to flash stock again you´ll need to know the name of your firmware,it differs from country and version. You can search for it here: http://forum.xda-developers.com/moto-g-2014/development/original-motorola-firmware-collection-t3153533.
It´s late now here, if you are at this point and have decided what rom to flash post again or pm me.
I hope my exclamation is understandable and I´ve made no faults, everyone else please correct me then!

Wolfcity said:
It´s not that easy to guide someone through all the steps. First thing you have to do is unlock your bootloader,described here: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728. Read all the steps,it´s not that difficult.
You need all the drivers,by motorola and android, linked in the tutorial. I recomend Minimal ADB and Fastboot instead of Android SDK, it´s easier. Install it in the root of your windows partition,like C:\Minimal ADB and Fastboot. So if you open a command prompt the path is short and you know it.
After the unlock process you´ll need to flash a custom recovery, you can read how to do that here: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818.
There´s a part called Flashing TWRP Recovery . You don´t need to do that with Flashify (you surely can if you want but I think this way is easier to do), just download the custom recovery TWRP from here: https://dl.twrp.me/titan/.
Place the .img file in the Minimal ADB and Fastboot folder and connect the phone to the PC. After that you open a command prompt again from the Minmal ADB and fastboot folder (open the folder and hold Shift and right click and press "open command window here".
Now type the command
Code:
adb reboot bootloader
When the phone has booted to bootloader type
Code:
fastboot devices
A string of numbers should appear,that means your phone is connected.
Now type
fastboot flash recovery "name of the downloaded TWRP .img file", in your case that should be
Code:
fastboot flash recovery twrp-2.8.6.0-titan.img
Now everytime when you boot to recovery you´ll see a menu with a lot of features like install,wipe,backup,restore etc.
From here you can flash any rom you like, a stock rom, a stock based rom or any other like cyanogen or AOSP.
If you want to flash stock again you´ll need to know the name of your firmware,it differs from country and version. You can search for it here: http://forum.xda-developers.com/mot...riginal-motorola-firmware-collection-t3153533.
It´s late now here, if you are at this point and have decided what rom to flash post again or pm me.
I hope my exclamation is understandable and I´ve made no faults, everyone else please correct me then!
Click to expand...
Click to collapse
Its good guide follow these steps

If you want to go stock, I recommend you to go with the mfastboot method . . .
because it doesn't even need unlocked bootloader or any recovery,
The following link is having a mfastboot folder, in which, Moto G 2014(XT1068) stock 5.0.2 factory firmware is stored and, you just have to extract the folder and open it then pressing & holding shift + RMB and select "Open Command Window Here".
(Now press Power + Volume Down simultaneously, and you should go to the bootloader mode, if you don't know that )
Now in the command window, check your phone is connected with USB and type below code and press Enter.
Code:
fastboot devices
if any code(like for eg. ZDMJK2312) is shown, you're connected,
if not, try reconnecting the USB and try again.
Once properly connected, now you can flash the follwing commands one by one, to get your device to life.
Code:
Moto G 2014 Stock 5.0.2 Restore Script
------------------------------------------------------------------|
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
------------------------------------------------------------------|
BTW this happened to me 6 months back and the same helped me.
mfastboot
Note : The above method is for only the model XT1068, because the firmware in the folder is for that model only, so plz make sure your model before proceeding.
And plz follow each and every step properly.
Thanks . . .

Alright thanks people! I'll try ArtRahul's method since it's easier and i was quite satisfied with stock. If that doesn't work I'll try Wolfcity's method.

Alright, so this is an update. ArtRahul's method works great and it's really easy. If anyone looks for a solution and finds this thread, just make sure you find the exact model of your phone and google the firmware. Here's where I found mine
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
It has links to other versions too. Good luck!

darthlawl said:
What do you mean?
Click to expand...
Click to collapse
if ur phone is going to fastboot mode u can install twrp, no os is needed for doing this

darthlawl said:
Ps. I can't unlock the bootloader since I can't access the OS
Click to expand...
Click to collapse
darthlawl said:
What do you mean?
Click to expand...
Click to collapse
you don't have to access to os in order to unlock the bootloader, go to android development section on this forum for moto g 2014 & follow any thread that guides about unlocking bootloader.

darthlawl said:
Alright, so this is an update. ArtRahul's method works great and it's really easy. If anyone looks for a solution and finds this thread, just make sure you find the exact model of your phone and google the firmware. Here's where I found mine
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
It has links to other versions too. Good luck!
Click to expand...
Click to collapse
did anything work?
my moto g2 was rooted .i got notification that update 5.1.1 is available .but after update it is stuck in bootloop::crying:
---------- Post added at 03:17 AM ---------- Previous post was at 03:03 AM ----------
it is giving me failed to validate system image error after first command mfastboot.exe oem lock begin

Stock Pie on Tmo (XT1789-04) Moto Z2 Force (Hybrid of Sprint Pie and Tmo Oreo ROMs)

SPECIAL THANKS
Special Thanks to @Danny XP, @thePromoter, @Hibinoh, and those from the following thread which lead the this thread's inception:
https://forum.xda-developers.com/z2-force/how-to/to-pie-sprint-variant-t3954577
More Special Thanks to the Lineage devs and one of the first real Pie ROMs for the Moto Z2 Force:
Since Morotola decided to not supply a Tmo ROM for Pie on the Tmo variant device, we've only had one good option to go to, Lineage 16. Which, if you like that ROM and want to continue to receive security updates and support, I encourage you to head to this thread and flash LOS 16. The ROM is smooth and works great. Link below:
https://forum.xda-developers.com/z2-force/development/official-lineageos-16-0-t3907036
Please note some current Lineage 16 caveats:
1. Audio routing with Moto Mods does not work. i.e. Gamepad, etc. The Audio HAL is evidently a pain to work with.
2. Efficiency Battery Mode (Allowing the main battery to be charged to 80% from external battery and maintained at that level (Incipio, etc.)) does not work.​
The devs on the LOS 16 ROM have done a lot of work and I can't thank them enough for their efforts. They've helped me personally a ton in understanding the Moto Z2 Force and flashing ROMs on Slotted devices, etc.
Why did I move from LOS 16? Honestly, I wanted my Moto Mods working. I got them to enjoy them. If LOS 16 had the audio routing working, I would still be using it. This was my preference only.
Click to expand...
Click to collapse
DISCLAIMER
Back up your files. YOU are responsible for any files that get wiped. The below instructions will wipe your phone.
YOU are responsible if the phone gets bricked. No one else here told you to perform these steps.
I've attempted to make this as simple as I can to follow. Yes, it appears to be a lot of steps. I've tried to avoid assumptions and have done this to help avoid some issues that have been seen when others have attempted to follow the more assumed instructions.
Even with the details below, there will be mistakes. If I've made any, kindly let me know and we can get them corrected.
In no way is this "fool proof" and not every Moto Z2 Force is the same, even the variants can vary within a carrier. So. this is done at your own risk. Please review the instructions before proceeding to ensure you've covered everything before making changes. This was performed on my XT1789-04 Tmo variant.
Even if everything seems perfect, you can still brick your phone.
No one here is responsible in that instance other than yourself. There is plenty of other information here on XDA where you can perform your own research to resolve your issue and decide if you should proceed or not.
Caveat:
1. the ONLY caveat that I've come across is once this is done, Software Updates will not work since your bootloader will be unlocked.
Click to expand...
Click to collapse
Note: In my case, I had to use the "TMO Moto Z2 Force 27.1.5 Flashall" before to prevent boot looping. I was already on Lineage 16 before doing the below. Which was probably the reason why I got a boot loop after flashing all the below files before going back to stock.
More information on the flashall can be found here:
https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
The below should work fine if you are already on stock.
With all that being said, and you feel comfortable, let's get down to it.
INSTRUCTIONS FOR WINDOWS
Quick and dirty
You can follow these if you've already done this before and just want the high-level steps:
1. Download RETIN 9.0(XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), and the latest TMO 8.0(XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip)
2. Unzip both files, find a copy of mfastboot (or fastboot), a copy of TWRP img (use nash's TWRP)
3. Copy the boot.img from RETIN 9.0 to your phone's sdcard
4. Boot into TWRP and wipe your phone(data + cache)
5. Copy the below RETIN files to a new folder from the RETIN ZIP file, this is the same folder that the Tmo files will also go:
boot.img
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
system.img_sparsechunk.5
system.img_sparsechunk.6
system_other.img
oem.img
6. Copy the below files from the Tmo ZIP file to the same folder where you placed the RETIN files above:
logo.bin
NON-HLOS.bin
fsg.mbn
BTFM.bin
adspso.bin
7. Copy the twrp<version>.img here as well.
8. Use mfastboot (or fastboot) and flash the files from this new folder with both RETIN and Tmo files that you've copied:
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot oem fb_mode_clear
9. Boot into TWRP using mfastboor (or fastboot):
Code:
fastboot boot twrp<version>.img
10. Use TWRP to flash the sdcard copy of boot.img (from step 3) to 'boot'
12. Reboot to finish the install and it should boot for the first time into the new hybrid ROM
13. ENJOY!​
More detailed instructions
The reason I posted this was to help prevent some issues with those that have not followed the process before. It should avoid some issues. It is lengthy.
Prerequisites:
1. Unlocking the Booloader
Is your bootloader unlocked? If not, there is no point in doing any of this. If it can't be unlocked, apologies, there isn't anything that can be done from this thread.
Before you go about unlocking the bootloader via the below Motorola website, you need to Unlock the Bootloader witin Developer Tools. To do this, Go to Settings > System > find the Buid Number. Tap the Build Number 8-10 times and it will inform that you are a Developer. Press Back and select developer Tools. Find Unlock the Bootloader, or OEM Bootloader Unlock (You can search for this option.), and tap to enable. Proceed below.
If you need to do this, or find out if it can be unlocked, head to the Motorola "Unlock your Bootloader" site and follow their instructions.
This process WILL VOID your WARRANTY!
Here's the US English link: https://support.motorola.com/us/en/bootloader​
1a. Once unlocked, you can continue.
2. Downloading the Files
Below are the files you need in quotes and the links where you can download them from.
If the below won't work you for, search Google for the file names and acquire them otherwise. There were plenty of links the last I searched.
It might be easier if you placed these on your Desktop.
2a. Download ADB Platform Tools, "adb - platform tools v28.0.0.zip":
from https://androidfilehost.com/?fid=962339331459003166
Note: This already has fastboot.exe
2b. Download the 64bit versions of the Motorola Mobile Drivers if you are running a 64bit OS, "Motorola_Mobile_Drivers_64bit.msi.zip":
from https://androidfilehost.com/?fid=23501681358556235
2c. Download the 32bit versions of the Motorola Mobile Drivers if you are running a 32bit OS, "Motorola_Mobile_Drivers_32bit.msi.zip":
from https://androidfilehost.com/?fid=23501681358556234
2d. Download "XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip":
from https://mirrors.lolinet.com/firmware/moto/nash/official/RETIN/
Note: This was tested using RETIN, not RETAIL!
2e. Download "XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip":
from https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/
2f. Download "twrp-3.3.1-0-R1-nash.img":
from https://mirrors.lolinet.com/firmware/twrp/nash/
or "twrp-3.2.3-2-nash.img"
from https://dl.twrp.me/nash/
(If you have issues with 3.3.1, use 3.2.3 instead.)
2g. Download fastboot and mfastboot, this link includes both, "Fastboot_all.zip":
from https://androidfilehost.com/?fid=23578570567719065​
3. Preparing the Files and Start the Flashing Process
3a. Unzip the files above in their own folders.
3b. Install the Motorola Drivers based on your OS, 32bit or 64bit.
3c. Connect your phone to a USB 2.0 port. You can use USB 3.0, but you might run into issues running commands. If you don't have a USB 2.0 port, perhaps using a USB 2.0 hub might work.
3d. Go into the platform-tools folder.
3e. Run the following to be sure the phone is detected:
Code:
adb devices
You should get some output informing that the ADB daemon isn't running and it will attempt to correct this. Afterwards, you should get something like the following if the phone was found:
Code:
<xxxxxxx> device
If you don't and the command shows that the connection is "unauthorized", change the USB Preferences to File Transfer. Rerun the above command and it should show it as "device".​
3f. Using the same platform-tools folder you are running from, copy the following files to the platform-tools folder...
First the RETIN files:
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\boot.img
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system.img_sparsechunk.0
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system.img_sparsechunk.1
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system.img_sparsechunk.2
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system.img_sparsechunk.3
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system.img_sparsechunk.4
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system.img_sparsechunk.5
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system.img_sparsechunk.6
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\system_other.img
XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\oem.img​
And, the Tmo files:
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml\logo.bin
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml\NON-HLOS.bin
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml\fsg.mbn
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml\BTFM.bin
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml\adspso.bin​
All of the above files should be within the platform-tools folder.
3g. Copy the XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\boot.img file to your phone's SD Card (Moto Z (2)\SD card). You can use Windows Explorer to do this.
3h. Run the following command to boot into the bootloader (Using either fastboot.exe or mfastboot.exe.):
Code:
adb reboot bootloader
Your phone will reboot and allow fastboot to be used.
3i. Run the following to be sure fastboot detects the phone:
Code:
fastboot devices
3j. Run the following command to boot into TWRP:
Code:
fastboot boot twrp<version>.img
The img file will transfer to the phone and reboot.
Stop here if you have not made a backup of your files or if you have any reservations. This CANNOT be undone!
3k. Select Wipe, select Advanced Wipe, select Internal Storage and Dalivk/ART Cache, and swipe to wipe those partitions.
3l. Tap Back, Back again, select Reboot, and select Bootloader.
You should be back where you can use fastboot.
3m. Use fastboot (or mfastboot) and run the following commands in this order:
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot oem fb_mode_clear
Note: I personally only had one file give me an error, that was boot.img. It informed that "verification failed". Continue on step 3n to flash boot.img from the SD card using TWRP.
3n. Boot into TWRP by running the following, as before:
Code:
fastboot boot twrp<version>.img
3o. Select Install, select Install Image, and select boot.img from SD card. When asked, select boot.
Once done, go back to reboot to System to finish the install.
:victory:Voila!!:highfive:
You should now be booting into Pie on your Moto Z2 Force with a hybrid Sprint + Tmo Stock ROM.
If you get a boot loop during the boot animation, as mentioned before, you might need to perform the Flashall to Tmo Stock, and try the above instructions again. I had to.
My build number shows as PPX29.159-24, my IMEI shows up, Android Version shows 9, and all other fields seem to be correct. Voice, Data, and device functions are all working. You are on a mostly-stock ROM now.
Now, the only caveat that I've seen is that when you attempt to check for an update, it will show that the System integrity is compromised. I assume this is because the bootloader is unlocked, etc.
I hope this works out well for you.
Also, if you want root, install Magisk, following this thread:
https://www.xda-developers.com/how-to-install-magisk/

It seems weird that nobody has responded to this. -- Thank you for posting.
---------- Post added at 04:58 AM ---------- Previous post was at 04:40 AM ----------
johnathanamber said:
1. Download RETIN 9.0(XT1789-06_NASH_RETIN_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), and the latest TMO 8.0(XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip)​
Click to expand...
Click to collapse
Here you're say to use the latest TMO 8.0 firmware; but the the file you're mentioning is not the latest. As per the flashall thread, it says to avoid using the 'August 2019 27.1.7 update and to use the earlier March 2019 Tmobile update.
Is it safe for me to assume that you are intentionally using the 'March update', rather than the 'August update' ?
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip - 2019-08-05 - August Update (suggested to avoid)
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip - 2019-03-08 - March update (last stable version?)
Correct me if I'm wrong, but it looks like what you're doing here is using the device specific firmware files from the TMO 'March 2019' update, and then using fastboot to flash the system image from the XT1789-06 (What country / device variant is XT1789-06 btw?) ?​

Great tutorial,
worked on my XT1789-03
I however used XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20 instead of XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2
I also got stuck into a bootloop at the end which was solved by TWRP fix bootloop
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I tried this but it didn't work at all, the phone turns on but it stays in bootloop and I don't know if I did something wrong, I was using the August ROM since the March one was giving me baseband issues
I had an issue with the fastboot oem fb_mode commands (failed: no such file or directory) I'm not sure if this is the problem or not
Is there any way to fix it? Should I try again?
EDIT: I tried again using the flashall and then flashing the rom without letting the phone turn on after using the flashall and it worked

abense said:
It seems weird that nobody has responded to this. -- Thank you for posting.
---------- Post added at 04:58 AM ---------- Previous post was at 04:40 AM ----------
Here you're say to use the latest TMO 8.0 firmware; but the the file you're mentioning is not the latest. As per the flashall thread, it says to avoid using the 'August 2019 27.1.7 update and to use the earlier March 2019 Tmobile update.
Is it safe for me to assume that you are intentionally using the 'March update', rather than the 'August update' ?
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip - 2019-08-05 - August Update (suggested to avoid)
XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip - 2019-03-08 - March update (last stable version?)
Correct me if I'm wrong, but it looks like what you're doing here is using the device specific firmware files from the TMO 'March 2019' update, and then using fastboot to flash the system image from the XT1789-06 (What country / device variant is XT1789-06 btw?) ?
Click to expand...
Click to collapse
It's possible that I missed the flashall package. I just used what I saw on the aforementioned sites. Apologies for the confusion. You know what, after looking at the quick and dirty vs the full instructions, I had a typo. One shows the XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip file and the other shows XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-7_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip. I'll see about updating that.
Thanks for the catch!
gs512 said:
Great tutorial,
worked on my XT1789-03
I however used XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20 instead of XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2
I also got stuck into a bootloop at the end which was solved by TWRP fix bootloop
Click to expand...
Click to collapse
Good to note, hope that helps others as well.
DjCreeper7115 said:
I tried this but it didn't work at all, the phone turns on but it stays in bootloop and I don't know if I did something wrong, I was using the August ROM since the March one was giving me baseband issues
I had an issue with the fastboot oem fb_mode commands (failed: no such file or directory) I'm not sure if this is the problem or not
Is there any way to fix it? Should I try again?
EDIT: I tried again using the flashall and then flashing the rom without letting the phone turn on after using the flashall and it worked
Click to expand...
Click to collapse
I, too, had to do the flashall, as noted:
Note: In my case, I had to use the "TMO Moto Z2 Force 27.1.5 Flashall" before to prevent boot looping. I was already on Lineage 16 before doing the below. Which was probably the reason why I got a boot loop after flashing all the below files before going back to stock.
More information on the flashall can be found here:
https://forum.xda-developers.com/z2-...march-t3917070
Click to expand...
Click to collapse
I am glad it worked out.

When doing it this way can you still go back to 8.0 with a flash all if wanted?

jpeeler said:
When doing it this way can you still go back to 8.0 with a flash all if wanted?
Click to expand...
Click to collapse
If you follow the directions precisely then yes.

41rw4lk said:
If you follow the directions precisely then yes.
Click to expand...
Click to collapse
That's what I thought just wanted to be sure. Thanks.

gs512 said:
Great tutorial,
worked on my XT1789-03
I however used XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20 instead of XT1789-04_NASH_TMO_C_8.0.0_OCXS27.109-51-14-2
I also got stuck into a bootloop at the end which was solved by TWRP fix bootloop
Click to expand...
Click to collapse
Does this hybrid ROM also remove all the unnecessary sprint apps?

sandner said:
Does this hybrid ROM also remove all the unnecessary sprint apps?
Click to expand...
Click to collapse
Yes

How can I unlock bootloader and install TWRP on my XT1789-04 (AT&T)?
I tried on the website https://motorola-global-portal.custh...-your-device-b but I have received an answer "Your device does not qualify for bootloader unlocking.".

I've been running the T-Mo hybrid on the Sprint hardware (Pie) for a couple of months now (implemented essentially the same way the OP describes).
It mostly works fine, although it has developed an issue where it will frequently freeze and reboot if I try to surf on the phone while I'm on a phone call.
On the reboot, it loops twice before it will reboot.
Also, I am stuck on "H" reception (not LTE) when on a call. Phone is properly provisioned and the settings for T-Mobile are fine and VoLTE is working. But it doesn't see LTE.

I tried doing this but with the Verizon Files, still sees it as a sprint phone. Worse is that it *does* connect to LTE for Data, but not for Voice. Can't make any voice calls at all. Any thoughts?

I finally got around to trying this and have ran into some issues. When I start the individual file flashing I keep getting invalid partition name for each file followed by FAILED (remote failure). Here is an example for the boot file but it does it for all of the retin files from what I can tell.
Sending 'boot__a' (27269 KB) OKAY [ 0.633s]
Writing 'boot__a' (bootloader) Invalid partition name boot__a
FAILED (remote failure)
Finished. Total time: 0.642s

Sending 'boot__a'
Sending 'boot_a'
Sending 'boota'
try

I have been looking for an update for m sprint Z2 force on stock and this is it! Thank you so much for sharing this!
Looks awesome... I am so happy I don't have to deal with all the sprint junk bloatware on this.
Looking forward to a smooth ride , does anyone have any issue on this?

I,ve managed how to get work Stock Pie on the XT1589-05 RETCN version. HERE is a thread . Thanks to @johnathanamber for idea of hybrid rom

@@johnathanamber @doctorman @dannyxp @thePromoter @Hibinoh
My Sprint stock ROM flashed xt1789-03 has hit the 3G shutdown wall (no VoLTE) on Red Pocket AT&T.
Will following this procedure cure that problem (enable VoLTE plus LTE data)? Bootloader is unlocked already.
Thanks for all your hard work.