Database Develop

[q] help, moto x a few steps to be a briked phone

Ey guys! I really need you help, Im stucked with my Moto X.
I have a Moto X xt1053 with an unlockable bootloader, in the page of motorola says that my phone doesnt qualify to be unlocked.
So, the problem is that I was trying to upgrade to android kitkat 4.4 following the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2545775
All was going good until when I try to flash boot.img, I cant load that file into my phone, So im stucked in the fastboot screen of my phone, because now I cant even get into the TWRP recovery option, just fastboot, I cant load any boot.img file into my phone.
When Im trying to flash the boot.img file, the error that appears in my phone says:
Failed to hab check for boot: 0x56
preflash validation failed for boot
So, what can I do?
Any help?????
THANKS A LOT!!!

What error do you get?

Ctrl-Freak said:
What error do you get?
Click to expand...
Click to collapse
When Im trying to flash the boot.img file, the error that appears in my phone says:
Failed to hab check for boot: 0x56
preflash validation failed for boot

daritoca said:
When Im trying to flash the boot.img file, the error that appears in my phone says:
Failed to hab check for boot: 0x56
preflash validation failed for boot
Click to expand...
Click to collapse
I'm guessing your T-mobile xt-1053 will not accept the boot.img from a AT&T xt-1058 while the bootloader is locked.
First of all, I don't think you are in danger of a 'brick.' You should still be able to flash back to stock 4.2.2, and there are a few tutorials on this subject within this forum.
I have no idea if it would work, but if you want to proceed with an AT&T version of 4.4, you could try flashing the boot.img from the T-mobile 4.4 build. Download "TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.xml.zip" from http://sbf.droid-developers.org/ghost_rcica/list.php, extract boot.img to your fastboot directory, then proceed. If you 'go this route', you should also use the modem (NON-HLOS.bin) and fsg.mbn from T-mobile.

I also do that, i downloaded the att 4.4 kitkat version and try to flash the boot.img but it doesnt work, no boot.img, no sistem.img
I've been trying with other versions and had same problem.
Sent from my XT890 using xda app-developers app

daritoca said:
I also do that, i downloaded the att 4.4 kitkat version and try to flash the boot.img but it doesnt work, no boot.img, no sistem.img
I've been trying with other versions and had same problem.
Sent from my XT890 using xda app-developers app
Click to expand...
Click to collapse
Just to be clear, did you download and try the T-mobile boot.img ?
Another random thought, are you using the correct motorola fastboot? (I used the "Motorola Fastboot Files" link from this post: http://forum.xda-developers.com/showthread.php?t=2406409, thanks mattlgroff)

No, i havent try the tmobile version.
Ill try in a few hours and tell you the result.
Thanks a lot!!
Sent from my XT890 using xda app-developers app

Cant flash any *.img file because my bootloader is locked, I cant flash any file becuase of that. As long as I know, to flash an *.img file I need to have my bootloader unlocked, Am I right?

daritoca said:
Cant flash any *.img file because my bootloader is locked, I cant flash any file becuase of that. As long as I know, to flash an *.img file I need to have my bootloader unlocked, Am I right?
Click to expand...
Click to collapse
Not exactly. A locked bootloader keeps you from flashing images that are not properly signed. So if you have a T-mobile phone, the bootloader will allow official T-mobile *.img files. An exception to this is that if you upgrade your bootloader to a newer version (by taking an OTA for example), sometimes the newer bootloader will now allow older T-mobile *.img files. That exception should not apply here, as we are discussing kitkat - the latest version of android.

But when I try to flash any boot.img I just cant flash it, I try with t-mobile and I couldnt, right now Im stucked, I dont know what else to do, my phone is dead and I just cant flash any image, right now Im working at night, so it takes me longer to answer and try to restore my phone.
What else I could do if I cant flash any image in my phone, and if in my phone I erased my boot.img file?

daritoca said:
But when I try to flash any boot.img I just cant flash it, I try with t-mobile and I couldnt, right now Im stucked, I dont know what else to do, my phone is dead and I just cant flash any image, right now Im working at night, so it takes me longer to answer and try to restore my phone.
What else I could do if I cant flash any image in my phone, and if in my phone I erased my boot.img file?
Click to expand...
Click to collapse
Flash the T-MOBILE SBF FILE COMPLETELY
Sent from my XT1058 using XDA Premium 4 mobile app

Ok, I'll do that this morning and tell you how it goes.
Thanks!

When Im flashing the T-mobile completely I have an error.
Failed to hab check for boot: 0x56
preflash validation failed for boot
Im doing with RSD Lite 6.1.5
It stops in step 5, cant flash boot.img
{
"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"
}
What else can I do?

daritoca said:
When Im flashing the T-mobile completely I have an error.
Failed to hab check for boot: 0x56
preflash validation failed for boot
Im doing with RSD Lite 6.1.5
It stops in step 5, cant flash boot.img
...
What else can I do?
Click to expand...
Click to collapse
I see you tried the T-mobile 4.4 SBF, and once again boot.img didn't work...
In your original post, you mention that you are on a xt-1053. Is that a US T-mobile and not a developer edition? I ask because the evidence suggests your phone is somehow different. If you are on a different version, you need to carefully pick the correct SBF from this list: http://sbf.droid-developers.org/ghost_rcica/list.php Then use RSD to flash it.

If you've flashed the wrong bootloader/partition table, you'll need to manually flash your proper gpt and motoboot and reboot before running the sbf.
Sent from my XT1060 using Tapatalk

arcanexvi said:
If you've flashed the wrong bootloader/partition table, you'll need to manually flash your proper gpt and motoboot and reboot before running the sbf.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Good tip.
Question:
I noticed that boot.img was "step 5" within the OP's RSD lite process, and the previous steps include motoboot.img and gpt.bin (at least they do on my AT&T SBF). I didn't think the bootloader would allow itself to be overwritten with a "wrong" version. Am I mistaken? If so then what, if not the the code within motoboot.img and gpt, checks the signatures of images to be flashed?

Ctrl-Freak said:
Good tip.
Question:
I noticed that boot.img was "step 5" within the OP's RSD lite process, and the previous steps include motoboot.img and gpt.bin (at least they do on my AT&T SBF). I didn't think the bootloader would allow itself to be overwritten with a "wrong" version. Am I mistaken? If so then what, if not the the code within motoboot.img and gpt, checks the signatures of images to be flashed?
Click to expand...
Click to collapse
It flashes them but doesn't reboot before trying to flash the rest usually. If the wrong info is currently loaded, it'll need a reboot first. This is really only an issue for unlocked devices as signature checks will stop you from borking yourself up this badly.
Sent from my XT1060 using Tapatalk

arcanexvi said:
It flashes them but doesn't reboot before trying to flash the rest usually. If the wrong info is currently loaded, it'll need a reboot first. This is really only an issue for unlocked devices as signature checks will stop you from borking yourself up this badly.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Gotcha.
The OP stated they had a locked bootloader. My question:
Is it possible, with a locked bootloader, to flash a "wrong signatured" motoboot and gpt? (I certainly have not tried it, and I assumed it was not possible.)
If the answer is no and the OP had the wrong SBF, then why did the OP's SBF attempt fail on step 5 instead of the earlier motoboot or gpt steps?
If the answer is no and the OP had the right SBF, then why did the SBF fail at all?

Ctrl-Freak said:
Gotcha.
The OP stated they had a locked bootloader. My question:
Is it possible, with a locked bootloader, to flash a "wrong signatured" motoboot and gpt? (I certainly have not tried it, and I assumed it was not possible.)
If the answer is no and the OP had the wrong SBF, then why did the OP's SBF attempt fail on step 5 instead of the earlier motoboot or gpt steps?
If the answer is no and the OP had the right SBF, then why did the SBF fail at all?
Click to expand...
Click to collapse
Some files aren't sig checked or share a sig with a different device. Others are. So it's possible to have a partial failure which leads to headaches.
Sent from my XT1060 using Tapatalk

Thanks a lot for your support, Im doing the flash with the original rom ( fastboot-ghost_amxmx-user-4.2.2-13.9.0Q2.X-116-LCX-26-29-release-keys-cid12-AmericaMovil-MX.tar.gz)
When Im trying to flash it, I got another error.
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
So, thats why I was no trying to flash the original rom, because in the first try to upgrade my phone, I try to upgrade to kit kat 4.4
Answering the question if my device is a developer edition, it isnt, thats one of the reasons I cant unlock my bootloader.
So, any other suggestion?

[Q] Corrupted Partition Files - Mega Hard Bricked - [Please Guys]

Hi everyone,
I screwed up my MX last week trying to downgrade to 4.4.2 retail BR by fastboot prompt commands but something went wrong.
Tried to use moto tool kit downloading verizon, and rogers. Nothing. Totaly scared, I´d serching on Q&A help on it since last thursday.
I thought was hardbricked, but maybe partition files corrupted for real.
So I am using windows 8.1(64), and VM Windows XP (32bit) on Dell 2640 - and testing this threads below - but without sucesses. Could not assign drivers on W8 by Dseo13b even disabling at reboot. In XP cannot find device, maybe usb 2.0 ? Both of then with moto-drivers, Sdk, Java updated.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
and..
http://forum.xda-developers.com/showthread.php?t=2623587
Please help me understand this error'
{
"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"
}
s code showed up in the picture.
Thanks for all,
Bruno Sastre.

BrunoX10 said:
Hi everyone,
I screwed up my MX last week trying to downgrade to 4.4.2 retail BR by fastboot prompt commands but something went wrong.
Tried to use moto tool kit downloading verizon, and rogers. Nothing. Totaly scared, I´d serching on Q&A help on it since last thursday.
I thought was hardbricked, but maybe partition files corrupted for real.
So I am using windows 8.1(64), and VM Windows XP (32bit) on Dell 2640 - and testing this threads below - but without sucesses. Could not assign drivers on W8 by Dseo13b even disabling at reboot. In XP cannot find device, maybe usb 2.0 ? Both of then with moto-drivers, Sdk, Java updated.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
and..
http://forum.xda-developers.com/showthread.php?t=2623587
Please help me understand this error'
s code showed up in the picture.
Thanks for all,
Bruno Sastre.
Click to expand...
Click to collapse
Whoa buddy!!
As sad as this is, we have warnings posted in nearly every sub-forum in the Moto X section warning you not to downgrade.
Fortunately, you can still access fastboot so you MIGHT still have some hope, but it is hard telling.
Since the 4.4.3 full SBF for Brazil Retail has not been leaked it is going to be much trickier....
Here is my suggestion:
First, you say you tried to "downgrade" to 4.4.2, so this leads me to believe that you had the 4.4.3 Brazil Retail OTA on your phone.
Find a copy of the 4.4.2 brazil Retail OTA, and extract it. You will also need the entire 4.4.2 Brazil Retail SBF file (and VERIFY THE CHECKSUMS to make sure you do not have corrupted files).
I suggest you extract "gpt.bin" from the 4.4.3 OTA, and extract "motoboot.img" from the 4.4.2 OTA.
Now a little explaination: gpt.bin is "GUID Partition Table". Since we KNOW that you cannot attempt to downgrade gpt.bin OR Motoboot, we are using the MOST RECENT versions of both. The 4.4.3 OTA contained a new gpt.bin, but the most recent bootloader is still the 4.4.2 version.
The idea here is to flash JUST gpt.bin and motoboot.img, then immediately REBOOT, so that the bootloader can LOAD the new partition table BEFORE we flash any other partitions. Give it a shot:
mfastboot flash partition gpt.bin (USE GPT.BIN FROM THE 4.4.3 OTA FILE)
mfastboot flash bootloader motoboot.img
mfastboot reboot-bootloader
NOW, the following fastboot flash commands using the files from the 4.4.2 Brazil Retail SBF:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
now reboot, assuming you were even able to get this far..... Your X already appears to be in awful shape, so I don't see how any of this could hurt you, but it just MIGHT work....
If this works, and you are actually able to get booted into android, DO NOT ACCEPT THE OTA. Doing so will possibly brick you again.
Instead, just wait until the full leaked 4.4.3 SBF is released, and THEN, you can consider trying to flash the ENTIRE 4.4.3 SBF, if you want to upgrade.

samwathegreat said:
Whoa buddy!!
As sad as this is, we have warnings posted in nearly every sub-forum in the Moto X section warning you not to downgrade.
Fortunately, you can still access fastboot so you MIGHT still have some hope, but it is hard telling.
Since the 4.4.3 full SBF for Brazil Retail has not been leaked it is going to be much trickier....
Here is my suggestion:
First, you say you tried to "downgrade" to 4.4.2, so this leads me to believe that you had the 4.4.3 Brazil Retail OTA on your phone.
Find a copy of the 4.4.2 brazil Retail OTA, and extract it. You will also need the entire 4.4.2 Brazil Retail SBF file (and VERIFY THE CHECKSUMS to make sure you do not have corrupted files).
I suggest you extract "gpt.bin" from the 4.4.3 OTA, and extract "motoboot.img" from the 4.4.2 OTA.
Now a little explaination: gpt.bin is "GUID Partition Table". Since we KNOW that you cannot attempt to downgrade gpt.bin OR Motoboot, we are using the MOST RECENT versions of both. The 4.4.3 OTA contained a new gpt.bin, but the most recent bootloader is still the 4.4.2 version.
The idea here is to flash JUST gpt.bin and motoboot.img, then immediately REBOOT, so that the bootloader can LOAD the new partition table BEFORE we flash any other partitions. Give it a shot:
mfastboot flash partition gpt.bin (USE GPT.BIN FROM THE 4.4.3 OTA FILE)
mfastboot flash bootloader motoboot.img
mfastboot reboot-bootloader
NOW, the following fastboot flash commands using the files from the 4.4.2 Brazil Retail SBF:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
now reboot, assuming you were even able to get this far..... Your X already appears to be in awful shape, so I don't see how any of this could hurt you, but it just MIGHT work....
If this works, and you are actually able to get booted into android, DO NOT ACCEPT THE OTA. Doing so will possibly brick you again.
Instead, just wait until the full leaked 4.4.3 SBF is released, and THEN, you can consider trying to flash the ENTIRE 4.4.3 SBF, if you want to upgrade.
Click to expand...
Click to collapse
Since he's international, couldn't he unlock the bootloader and reflash the software image?

sivarticus85 said:
Since he's international, couldn't he unlock the bootloader and reflash the software image?
Click to expand...
Click to collapse
That's not what's at issue here. You don't even need to be unlocked to flash stock firmware because it is signed with release keys.
The issue is that he tried to downgrade. Read the stickies and you should understand.

samwathegreat said:
That's not what's at issue here. You don't even need to be unlocked to flash stock firmware because it is signed with release keys.
The issue is that he tried to downgrade. Read the stickies and you should understand.
Click to expand...
Click to collapse
I know he was trying to downgrade, but I didn't realize what had happened until I re-read his post. I get it now. I think what you suggested should do the trick.

Still working [I hope]
BrunoX10 said:
Hi everyone,
I screwed up my MX last week trying to downgrade to 4.4.2 retail BR by fastboot prompt commands but something went wrong.
Tried to use moto tool kit downloading verizon, and rogers. Nothing. Totaly scared, I´d serching on Q&A help on it since last thursday.
I thought was hardbricked, but maybe partition files corrupted for real.
So I am using windows 8.1(64), and VM Windows XP (32bit) on Dell 2640 - and testing this threads below - but without sucesses. Could not assign drivers on W8 by Dseo13b even disabling at reboot. In XP cannot find device, maybe usb 2.0 ? Both of then with moto-drivers, Sdk, Java updated.
http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
and..
http://forum.xda-developers.com/showthread.php?t=2623587
Please help me understand this error'
s code showed up in the picture.
Thanks for all,
Bruno Sastre.
Click to expand...
Click to collapse
Hi Guys,
Master Samwathegreat!!!
I did flash gpt.bin from 4.4.3 OTA Retail BR and went fine but when I tryed motoboot.img - prompts says:
"(bootloader) Variable not supported!
target max-download-size: 768
sending 'bootloader' (1604 KB)...
OKAY [time]
writing 'bootloader' . . .
(bootloader) Permission denied
FAILED (remote failure)
finished. total time..."
So now I'm getting many firmwares to try flash motoboot.
Thanks for it man, I am still working on it and I ll send good news!! I hope.

BrunoX10 said:
Hi Guys,
Master Samwathegreat!!!
I did flash gpt.bin from 4.4.3 OTA Retail BR and went fine but when I tryed motoboot.img - prompts says:
"(bootloader) Variable not supported!
target max-download-size: 768
sending 'bootloader' (1604 KB)...
OKAY [time]
writing 'bootloader' . . .
(bootloader) Permission denied
FAILED (remote failure)
finished. total time..."
So now I'm getting many firmwares to try flash motoboot.
Thanks for it man, I am still working on it and I ll send good news!! I hope.
Click to expand...
Click to collapse
Try skipping that command. Can you run any of the other fastboot flash commands?
Definitely use caution. I recommend you don't try downgrading the bootloader.

Bad Feelings...
samwathegreat said:
Try skipping that command. Can you run any of the other fastboot flash commands?
Definitely use caution. I recommend you don't try downgrading the bootloader.
Click to expand...
Click to collapse
===================================================================================================
NOPE MAN!
Tryed others flash commands and no one hits.
at the same time, I got and tryed "TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC.xml" too, but without sucess =///
RSD Lite + W8 sucks, cannot find device - and I m going to wallmart tomorow, one week stucked on it... no one desires...
Thank you Xda.

BrunoX10 said:
===================================================================================================
NOPE MAN!
Tryed others flash commands and no one hits.
at the same time, I got and tryed "TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC.xml" too, but without sucess =///
RSD Lite + W8 sucks, cannot find device - and I m going to wallmart tomorow, one week stucked on it... no one desires...
Thank you Xda.
Click to expand...
Click to collapse
Can you tell me what error you get when you type, for instance:
fastboot flash system system.img

Good News - We made it!!!
samwathegreat said:
Can you tell me what error you get when you type, for instance:
fastboot flash system system.img
Click to expand...
Click to collapse
Yahh Man, you´r the one!
I´d just took a coffe [got high] and remake, prompt by prompt on new firmware downloaded from sbrf.
So we made it guys, the MX rebooted normaly and I really dont know how but worths as you said, skipping commands.
Thank you Samwathegreat!:good:
Thank you XDA Family.

BrunoX10 said:
Yahh Man, you´r the one!
I´d just took a coffe [got high] and remake, prompt by prompt on new firmware downloaded from sbrf.
So we made it guys, the MX rebooted normaly and I really dont know how but worths as you said, skipping commands.
Thank you Samwathegreat!:good:
Thank you XDA Family.
Click to expand...
Click to collapse
F-A-N-T-A-S-T-I-C !!!
I'm very glad you had success :highfive: (High-Five)
EDIT: @BrunoX10 can you read this post: http://forum.xda-developers.com/moto-x/moto-x-qa/request-twrp-backup-brazil-retail-t2817522
This user needs your help! He is also using Brazil Retail 4.4.3 and accidently erased /system
Can you help him by making a backup of /system and sharing?

All SBF Flashes Fail

I went on motofirmware.com and all 3 solana sbf's fail at cdt.bin, boot.img, and recovery.img. Can someone please help?

mattyb132 said:
I went on motofirmware.com and all 3 solana sbf's fail at cdt.bin, boot.img, and recovery.img. Can someone please help?
Click to expand...
Click to collapse
i used this to sbf my droid 3
try it=> https://drive.google.com/file/d/0B5OhEXYb3jt_V0JXcGRNUEgtcGs/view?usp=sharing
use windows computer
its for the XT862 btw, assuming that's what you have. Also its a one click SBF so no RSD lite needed.

[Q] version downgraded for primary_gpt

Im trying to flsash a rom stock android 5.0 in moto x 2014 by using RDS Lite but is says: version downgraded for primary_gpt . I bricked my cell or there is a way to fix it. Before this i updated 5.0 via ota to soak test 5.1. but i used twrp to wipe partitions in phone. i did this because was not able to downgrade to 5.0. can you help. now i want to install anything in my phone 5.0 or 5.1. i just want to put this to woak again anyway because i need to use my cellphone.

jrmaiafs said:
Im trying to flsash a rom stock android 5.0 in moto x 2014 by using RDS Lite but is says: version downgraded for primary_gpt . I bricked my cell or there is a way to fix it. Before this i updated 5.0 via ota to soak test 5.1. but i used twrp to wipe partitions in phone. i did this because was not able to downgrade to 5.0. can you help. now i want to install anything in my phone 5.0 or 5.1. i just want to put this to woak again anyway because i need to use my cellphone.
Click to expand...
Click to collapse
You still have twrp right. So a easy way is to download a toolkit from the moto x 2014 thread onto your PC and install it. Then boot your phone into bootloader/fastboot and make sure you also install the moto drivers which the toolkit will ask you to do. Then just follow directions using the toolkit and you will be back up n running. Or you can sideload a rom onto twrp using the 1.0.3.2 version of adb drivers. I have done it successfully many times using Linux but with Linux you just have to type a ./ in front of adb sideload rom.zip for it to work. Just don't worry. As long as you have a bootloader then your phone is never bricked. Toolkit is below...
http://forum.xda-developers.com/showthread.php?t=2897819

im glad to know that "As long as you have a bootloader then your phone is never bric
skulldreamz said:
You still have twrp right. So a easy way is to download a toolkit from the moto x 2014 thread onto your PC and install it. Then boot your phone into bootloader/fastboot and make sure you also install the moto drivers which the toolkit will ask you to do. Then just follow directions using the toolkit and you will be back up n running. Or you can sideload a rom onto twrp using the 1.0.3.2 version of adb drivers. I have done it successfully many times using Linux but with Linux you just have to type a ./ in front of adb sideload rom.zip for it to work. Just don't worry. As long as you have a bootloader then your phone is never bricked. Toolkit is below...
http://forum.xda-developers.com/showthread.php?t=2897819
Click to expand...
Click to collapse
Thank you for your help, but i dont have anymore twrp, and my phone is xt 1097, im glad to know that "As long as you have a bootloader then your phone is never bricked." i have it still!!
Now RSD Lite recognizes my phone, but when i start to flash android 5.0 it says: version downgraded for primary_gpt
I flash this same rom (5.0) before using RSD Lite and it worked perfectly, but now gives this error. How can i fix it?

Have you got your factory image for your phone and mfastboot?

yes, i have it
orangestrawberry said:
Have you got your factory image for your phone and mfastboot?
Click to expand...
Click to collapse
I heard many people reporting this error, say they have posts here on xda that solves the problem but I could not find them . I have seen in a blog that the problem is in doing downgrading from 5.0 to 5.1. and they say that to solve it is necessary to change two lines of a file , but I do not know which file is this , and not how it's done

jrmaiafs said:
Im trying to flsash a rom stock android 5.0 in moto x 2014 by using RDS Lite but is says: version downgraded for primary_gpt . I bricked my cell or there is a way to fix it. Before this i updated 5.0 via ota to soak test 5.1. but i used twrp to wipe partitions in phone. i did this because was not able to downgrade to 5.0. can you help. now i want to install anything in my phone 5.0 or 5.1. i just want to put this to woak again anyway because i need to use my cellphone.
Click to expand...
Click to collapse
Can you get into bootloader mode (fastboot)? What version of the bootloader are you running (you can see this in bootloader mode)?

I have bootloader (fastboot)
{
"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"
}
JulesJam said:
Can you get into bootloader mode (fastboot)? What version of the bootloader are you running (you can see this in bootloader mode)?
Click to expand...
Click to collapse
these are the information appearing:
So I try to install the rom 5.0 with RSD Lite this error occurs :
And that's what the RSD Lite says :
I was using the soak test 5.1 V : 23:11:14 , and went back to retail by 5.0 RSD Lite 6.2.4 , and is giving the following error "version is downgraded primary- gpt "

jrmaiafs said:
I was using the soak test 5.1 V : 23:11:14 , and went back to retail by 5.0 RSD Lite 6.2.4 , and is giving the following error "version is downgraded primary- gpt "
Click to expand...
Click to collapse
Your bootloader is 60.16, which is the 5.1 bootloader. You are getting that error because you are trying to flash a lower version partition table from your bootloader.
You need to stop trying to flash the 5.0 partition table. I would manually flash the 5.0 system, boot, NON-HLOS, fsg and logo using mfastboot version 2.
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.bin
Then after you are done that, boot into recovery and wipe cache and data partition. Then reboot into system.

Thank you
JulesJam said:
Your bootloader is 60.16, which is the 5.1 bootloader. You are getting that error because you are trying to flash a lower version partition table from your bootloader.
You need to stop trying to flash the 5.0 partition table. I would manually flash the 5.0 system, boot, NON-HLOS, fsg and logo using mfastboot version 2.
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.bin
Then after you are done that, boot into recovery and wipe cache and data partition. Then reboot into system.
Click to expand...
Click to collapse
There was no time I try your solution because I was looking for other answers before I saw your comment , I found the solution in this blog , anyway thanks for the help . but it is in Portuguese
http://motox-brasil.blogspot.com.br...howComment=1433025924130#c6945390347560261007

jrmaiafs said:
There was no time I try your solution because I was looking for other answers before I saw your comment , I found the solution in this blog , anyway thanks for the help . but it is in Portuguese
http://motox-brasil.blogspot.com.br...howComment=1433025924130#c6945390347560261007
Click to expand...
Click to collapse
Ok but all that says to do is to flash the 5.0 firmware with RSDLite. I thought that was what you were trying to do and were getting an error?

JulesJam said:
Ok but all that says to do is to flash the 5.0 firmware with RSDLite. I thought that was what you were trying to do and were getting an error?
Click to expand...
Click to collapse
The article lists the edits to make to the flashfile.xml so the gpt & bootloader are not flashed using RSD Lite
Sent from my XT1095 using Tapatalk

3rdstring said:
The article lists the edits to make to the flashfile.xml so the gpt & bootloader are not flashed using RSD Lite
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ah, got it.

So I am having this exact problem now and I think somewhere along the way I flashed files from the wrong version and now my phones seems to not recognize the system storage or doesn't know how to write to it. My bootloader is 60.18....I've tried the system files for 5.1 and 6.0 but nothing seems to work. After I enter all of the commands it just reboots over and over and says erasing...
really strange
JulesJam said:
Your bootloader is 60.16, which is the 5.1 bootloader. You are getting that error because you are trying to flash a lower version partition table from your bootloader.
You need to stop trying to flash the 5.0 partition table. I would manually flash the 5.0 system, boot, NON-HLOS, fsg and logo using mfastboot version 2.
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.bin
Then after you are done that, boot into recovery and wipe cache and data partition. Then reboot into system.
Click to expand...
Click to collapse

KB Smoka said:
So I am having this exact problem now and I think somewhere along the way I flashed files from the wrong version and now my phones seems to not recognize the system storage or doesn't know how to write to it. My bootloader is 60.18....I've tried the system files for 5.1 and 6.0 but nothing seems to work. After I enter all of the commands it just reboots over and over and says erasing...
really strange
Click to expand...
Click to collapse
Is your bootloader unlocked? Last I read you could get the Verizon Moto X 2014 bootloader unlocked.
You can get into bootloader mode and use fastboot commands, correct?

3rdstring said:
The article lists the edits to make to the flashfile.xml so the gpt & bootloader are not flashed using RSD Lite
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Hi there 3rdstring, I don't suppose you could translate it to English for us, could you? Or I guess I can see if Google Chrome will do that.

Dangerous-Beans! said:
Hi there 3rdstring, I don't suppose you could translate it to English for us, could you? Or I guess I can see if Google Chrome will do that.
Click to expand...
Click to collapse
No worries, Chrome did the translating fine. )

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.