Develop Bugs

Guide to restoring factory Image that works?

There isn't much on restoring this device at all. I'm really disappointed. I had high hopes. Anyway, the root situation is a mess, and after looking on here, I couldn't find a single set of instructions for properly flashing root. After digging around for a couple of hours, the only instructions I can find to revert to stock is:
1) Extract folder on PC.
2) Hold POWER and VOL DOWN on the phone to access the fastboot mode. Try to release the power button first before the VOL DOWN in case you trigger the system boot accidentally.
3) Connect USB cable to PC.
4) Flash in the following order:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
Complete restore
WARNING: May wipe device, and has not been personally tested.
Before flashing the above, flash these first:
Code:
fastboot flash gpt.bin partition
fastboot flash bootloader.img bootloader
fastboot flash NON-HLOS.bin modem
fastboot flash fsg.bin fsg
fastboot flash adspso.bin dsp
fastboot flash logo.bin logo
BUT I cannot get this to work because I keep getting a "Image not signed or corrupt" error. I've confirmed I have the US retail single sim version (Addison).
I also cannot find a working version of RSD Lite that detects my phone. I've tried version 6.2.4.
Would anyone be able to help? I'd really appreciate it. I can get the bootloader up, but I cannot do anything else.

I used the procedure here and it worked for me.
https://giveawaytricks.in/install-stock-rom-moto-z-play/
Also if RSD isnt detecting your phone, ADB might not either.

uberano26 said:
I used the procedure here and it worked for me.
https://giveawaytricks.in/install-stock-rom-moto-z-play/
Also if RSD isnt detecting your phone, ADB might not either.
Click to expand...
Click to collapse
I appreciate the reply. RSD doesn't detect, but ADB can. I can send fastboot commands via the bootloader, so I think drivers are OK. What got me in this mess was flashing the Chinese TWRP posted on the root guide here on XDA so I think the drivers are installed ok. I think it's a Windows thing.
I found that page you're referring to last night and read up on it. I found the retail US stock firmware image posted by another here on XDA and proceeded to go through the steps. After looking, the batch file immediately closed and did nothing. Then I went into the XML file and removed the m in mfastboot. After runnng manually, I found that it kept saying mfastboot.exe is not found. Then it went through every step as I've seen before, but every time a command was finished it would say "Image not signed or corrupt". I believe if I could somehow get RSD lite to work that I would be OK. I'd love to get this thing booting again.

uberano26 said:
I used the procedure here and it worked for me.
https://giveawaytricks.in/install-stock-rom-moto-z-play/
Also if RSD isnt detecting your phone, ADB might not either.
Click to expand...
Click to collapse
OK, I found mfastboot.exe located here (http://forum.xda-developers.com/gen...ng-mfastboot-exe-to-unbrick-motorola-t3203518) and had NO idea there was such a thing as mfastboot !
Unfortunately when running this, on all of these lines of mfastboot:
mfastboot flash gpt.bin partition
mfastboot flash bootloader.img bootloader
mfastoot flash NON-HLOS.bin modem
mfastboot flash fsg.bin fsg
mfastboot flash adspso.bin dsp
mfastboot flash logo.bin logo
I get "Image not signed or corrupt"
When I flash all of these, they go through OK:
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
So I'm hoping this helps someone figure out what I'm doing wrong. Again, I'm just trying to get back to stock.

- You are restoring the firmware without wiping the device, i'd try fastboot erase userdata first before flashing the rest, could be worth a try.
- I get "Image not signed or corrupt" when flashing a modified kernel too, but it is flashed regardless.
- I got root with the chinese twrp, the others gave me bootloop.
Good luck.

I too have a freshly-bricked EU dual-SIM Z Play that gives "Image not signed or corrupt" errors when I try to flash recovery and boot. Seen by fastboot, but not by RSD.
edit: more of my saga is here http://forum.xda-developers.com/moto-z-play/help/identifying-firmware-required-phone-t3517360/

yeahhh, i manage to flash my moto z play back to stock, the rom was bad or something i downloaded from here.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETLA/
so happy

joesee said:
There isn't much on restoring this device at all. I'm really disappointed. I had high hopes. Anyway, the root situation is a mess, and after looking on here, I couldn't find a single set of instructions for properly flashing root. After digging around for a couple of hours, the only instructions I can find to revert to stock is:
1) Extract folder on PC.
2) Hold POWER and VOL DOWN on the phone to access the fastboot mode. Try to release the power button first before the VOL DOWN in case you trigger the system boot accidentally.
3) Connect USB cable to PC.
4) Flash in the following order:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
Complete restore
WARNING: May wipe device, and has not been personally tested.
Before flashing the above, flash these first:
Code:
fastboot flash gpt.bin partition
fastboot flash bootloader.img bootloader
fastboot flash NON-HLOS.bin modem
fastboot flash fsg.bin fsg
fastboot flash adspso.bin dsp
fastboot flash logo.bin logo
BUT I cannot get this to work because I keep getting a "Image not signed or corrupt" error. I've confirmed I have the US retail single sim version (Addison).
I also cannot find a working version of RSD Lite that detects my phone. I've tried version 6.2.4.
Would anyone be able to help? I'd really appreciate it. I can get the bootloader up, but I cannot do anything else.
Click to expand...
Click to collapse
joesee said:
OK, I found mfastboot.exe located here (http://forum.xda-developers.com/gen...g-mfastboot-exe-to-unbrick-motorola-t3203518) and had NO idea there was such a thing as mfastboot !
Unfortunately when running this, on all of these lines of mfastboot:
mfastboot flash gpt.bin partition
mfastboot flash bootloader.img bootloader
mfastoot flash NON-HLOS.bin modem
mfastboot flash fsg.bin fsg
mfastboot flash adspso.bin dsp
mfastboot flash logo.bin logo
I get "Image not signed or corrupt"
When I flash all of these, they go through OK:
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
So I'm hoping this helps someone figure out what I'm doing wrong. Again, I'm just trying to get back to stock.
Click to expand...
Click to collapse
The commands that aren't working aren't being given correctly. Should be like this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin

Milly7 said:
The commands that aren't working aren't being given correctly. Should be like this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
Click to expand...
Click to collapse
You just saved my phone. Can I buy you a beer or something?

theodric said:
You just saved my phone. Can I buy you a beer or something?
Click to expand...
Click to collapse
It's all good. Just helping out. Glad it helped.

joesee said:
There isn't much on restoring this device at all. I'm really disappointed. I had high hopes. Anyway, the root situation is a mess, and after looking on here, I couldn't find a single set of instructions for properly flashing root. After digging around for a couple of hours, the only instructions I can find to revert to stock is:
1) Extract folder on PC.
2) Hold POWER and VOL DOWN on the phone to access the fastboot mode. Try to release the power button first before the VOL DOWN in case you trigger the system boot accidentally.
3) Connect USB cable to PC.
4) Flash in the following order:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
Complete restore
WARNING: May wipe device, and has not been personally tested.
Before flashing the above, flash these first:
Code:
fastboot flash gpt.bin partition
fastboot flash bootloader.img bootloader
fastboot flash NON-HLOS.bin modem
fastboot flash fsg.bin fsg
fastboot flash adspso.bin dsp
fastboot flash logo.bin logo
BUT I cannot get this to work because I keep getting a "Image not signed or corrupt" error. I've confirmed I have the US retail single sim version (Addison).
I also cannot find a working version of RSD Lite that detects my phone. I've tried version 6.2.4.
Would anyone be able to help? I'd really appreciate it. I can get the bootloader up, but I cannot do anything else.
Click to expand...
Click to collapse
I had the complete restore section reversed when you saw it on my thread, someone pointed it out and it's been fixed now.
Edit: I see someone's done it here too.
You also don't need to restore fully, just do the restore for ota and it should be enough if you've not flashed over the other stuff.

well i forgot to boot and set up a pin before installing TWRP, soft bricked myself for hours, this thread helped me return to stock so i could set a pin so TWRP would work, THANK YOU!
also if anyone else ends up here, and is having trouble finding the US retail stock image, i used the one from https://mirrors.lolinet.com/firmware/moto/addison/official/RETUS/

Is that an official signed image?
Can i use it to relock bootloader?
Thanks!

dyonissos said:
Is that an official signed image?
Can i use it to relock bootloader?
Thanks!
Click to expand...
Click to collapse
None of the images are signed and won't relock the bootloader.

Would this allow me to return to Marshmallow after sideloading a Nougat OTA, given I unlock my bootloader? I flashed a build from a different region (I think retbr or something) onto my Canadian Z Play, but the build number doesn't match what everyone else is getting from. Just looking to revert to Marshmallow to perform a proper update instead of impatiently sideloading an OTA.

IncendiaryPyro said:
Would this allow me to return to Marshmallow after sideloading a Nougat OTA, given I unlock my bootloader? I flashed a build from a different region (I think retbr or something) onto my Canadian Z Play, but the build number doesn't match what everyone else is getting from. Just looking to revert to Marshmallow to perform a proper update instead of impatiently sideloading an OTA.
Click to expand...
Click to collapse
Yep if you have the right factory image for your device.

Leraeniesh said:
Yep if you have the right factory image for your device.
Click to expand...
Click to collapse
Thank you. I've never had issues doing stuff like this before, but for some reason it scares the hell out of me with this phone. Maybe because I haven't had it for very long, lol. Downgraded to Marshmallow successfully. Hopefully I don't run into any issues in the future that would require an RMA, but out of all the phones I've had over the years, I've only had to RMA a Nexus 5 due to a problem with the screen.

Hi everyone. Is this guide is okay for reteu dual sim? And please point me if there is a firmware for reteu nougat. I softbrick my device and my imei is 0. I want to restore it please guide me as i am a noob in fastboot commands and steps. Thanks in advance

Vitxlss said:
yeahhh, i manage to flash my moto z play back to stock, the rom was bad or something i downloaded from here.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETLA/
so happy
Click to expand...
Click to collapse
do you have rooted device with twrp (maybe) ?
also, is the boot.img you got from Android 7 or 6.xx ?
Thanks

I use the DOWNGRADE script found here :
https://drive.google.com/file/d/0B134drJ4-Ed0MHQ5aE1wUmp5eFk/view
The original discussion here :
https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118
Note that the original script is not ideal. The actual script came from @-=MoRpH=- on comment #4

Any concerns flashing ADDISON_NPNS26.118-22-2-3 over ADDISON_NPN26.118-22-1 ?

I am currently running 7.1.1 and the more I read in these forums about hard bricking my device due to some weirdness with the bootloader the more worried I get. Can someone please verify that I can safely flash the image ADDISON_NPNS26.118-22-2-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip using the following commands?
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash dsp adspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system system.img_sparsechunk.8
mfastboot flash system system.img_sparsechunk.9
mfastboot flash system system.img_sparsechunk.10
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase cache
mfastboot erase userdata
mfastboot erase DDR
mfastboot oem fb_mode_clear

Used those exact commands to restore mine to stock. Just make sure when you extract it you flash the correct amount of superchunks. Like if it has 12 flash all 12. Other than that as long as you're not trying to get back to 6.0 you won't brick

justsomeguy007 said:
Used those exact commands to restore mine to stock. Just make sure when you extract it you flash the correct amount of superchunks. Like if it has 12 flash all 12. Other than that as long as you're not trying to get back to 6.0 you won't brick
Click to expand...
Click to collapse
1. Would it be of any concern if I had TWRP installed before doing this process?
2. Is there a way to do this flashing without losing my user data too?

Brutal_Master said:
1. Would it be of any concern if I had TWRP installed before doing this process?
2. Is there a way to do this flashing without losing my user data too?
Click to expand...
Click to collapse
1) TWRP usually will get overwritten by the stock recovery in the flash recovery step, thus it shouldn't affect the flash. You will have to reflash TWRP after you've updated.
2) you can try to save your data by omitting the 'mfastboot erase userdata' command in fastboot. Either skip this command or delete it from the flashing script. I would still caution you back up your data(either in TWRP or copying your files) and transfer the back up off your device, in case you have to factory reset if your device becomes unstable.
Usually, you only experience hard bricks or serious risks of hard bricking if you downgrade your firmware (without downgrading your bootloader) and then attempt to install OTA updates. The OTA update may corrupt your newer bootloader, and generally bootloaders block attempts to downgrade the bootloader patch level. Thus, if you do downgrade, generally do not use OTA updates. Motorola only appears to have designed their firmware and their OTA patches for upgrading.

Moto G5 install ota by zip on rooted phone (Can I just install ota zips with twrp?)

Hello, I'm a Motorola Moto G5 owner and I rooted my device some time ago.
Now i found out there is an official motorola update which brings our moto g5 from nougat to oreo. I'd want to update my phone but I have the little problem I cannot update my phone using the regular "System Updates" section in settings because I have a custom recovery and every time I try to update the phone just boots in twrp and to use it I must restart in bootloader and then press on start.
I've found online some official ota updates zips so my question is: Can I just install these zips with the install zip twrp function instead of reflashing stock firmware just to install a few updates? Is there another more simple way to update this damn phone? (I have Magisk 1.19, I'm on build NPPS25.137-93-8 and I'd want to get to the latest one)
(Oh yeh, srry for bad english but it isn't my mother language)

OnionMaster03 said:
Hello, I'm a Motorola Moto G5 owner and I rooted my device some time ago.
Now i found out there is an official motorola update which brings our moto g5 from nougat to oreo. I'd want to update my phone but I have the little problem I cannot update my phone using the regular "System Updates" section in settings because I have a custom recovery and every time I try to update the phone just boots in twrp and to use it I must restart in bootloader and then press on start.
I've found online some official ota updates zips so my question is: Can I just install these zips with the install zip twrp function instead of reflashing stock firmware just to install a few updates? Is there another more simple way to update this damn phone? (I have Magisk 1.19, I'm on build NPPS25.137-93-8 and I'd want to get to the latest one)
(Oh yeh, srry for bad english but it isn't my mother language)
Click to expand...
Click to collapse
No you cannot
Firmware OTA zips can only be installed on a totally unmodified stock system image
You will need to flash the stock firmware via fastboot and I recommend to lock the bootloader to ensure that the firmware is totally unmodified before doing any ota updates else you risk hard bricking the device
Firmware can be found
https://mirrors.lolinet.com/firmware/moto/cedric/official/

TheFixItMan said:
No you cannot
Firmware OTA zips can only be installed on a totally unmodified stock system image
You will need to flash the stock firmware via fastboot and I recommend to lock the bootloader to ensure that the firmware is totally unmodified before doing any ota updates else you risk hard bricking the device
Firmware can be found
Click to expand...
Click to collapse
Ok well, how to lock bootloader (Right now I have unlocked bootloader)? How to reunlock it after (Do I just need the same guide to unlock as the first time?)? But most important, how to install the stock image by fastboot? (What's the exact command?)
Oh well, I just noticed the firmwares you sent me are already on Oreo 8.1.0, Could I just install one of them and then reroot the phone?

OnionMaster03 said:
Ok well, how to lock bootloader (Right now I have unlocked bootloader)? How to reunlock it after (Do I just need the same guide to unlock as the first time?)? But most important, how to install the stock image by fastboot? (What's the exact command?)
Click to expand...
Click to collapse
Use the Oreo TWRP flashable zip for Moto G5 https://forum.xda-developers.com/g5/development/twrp-flashable-soak-test-oreo-t3827913.

Andrej_SK said:
Use the Oreo TWRP flashable zip for Moto G5 https://forum.xda-developers.com/g5/development/twrp-flashable-soak-test-oreo-t3827913.
Click to expand...
Click to collapse
Really thank you!

OnionMaster03 said:
Ok well, how to lock bootloader (Right now I have unlocked bootloader)? How to reunlock it after (Do I just need the same guide to unlock as the first time?)? But most important, how to install the stock image by fastboot? (What's the exact command?)
Oh well, I just noticed the firmwares you sent me are already on Oreo 8.1.0, Could I just install one of them and then reroot the phone?
Click to expand...
Click to collapse
Yes you can flash the latest firmware for your device and root with magisk
Google is always your friend for how tos
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
You can stop here if you intend to root etc or carry on if you want to relock the bootloader
Relock bootloader (note if you do this you won't be able to flash twrp or root etc)
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash boot boot.img
fastboot oem lock
Device will restart
Now flash the entire firmware again (first list)
Note unless you have all the unlock keys you may not be able to unlock it again

I guess i bricked my only phone....:-/

Okay, so im new to this stuff and still i managed to root the phone and flash RR 7.1.2. But i tried to unroot it and this happend:
I only have access to the bootloader and thats it. No recovery, no ROM nothing....when i start ti, it says that my phoe is unlocked and its dangerous and that the phone will boot in 5 secs but it never does....plz help me..and i wanna know where can i learn about all this stuff...its freaking me out since this the only phone i have.....plz help me..

You have two options
1 - flash twrp recovery and then use it to flash a custom rom
Assuming you have named the recovery image recovery.img
fastboot flash recovery recovery.img
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Then wipe system data cache/format data & follow procedure to flash a custom rom
2 - flash stock rom firmware which can be found (plenty of guides out there for how to just search)
https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you have unlocked the bootloader it will always says your device is not secure unless you flash a modified boot image

TheFixItMan said:
You have two options
1 - flash twrp recovery and then use it to flash a custom rom
Assuming you have named the recovery image recovery.img
fastboot flash recovery recovery.img
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Then wipe system data cache/format data & follow procedure to flash a custom rom
2 - flash stock rom firmware which can be found (plenty of guides out there for how to just search)
https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you have unlocked the bootloader it will always says your device is not secure unless you flash a modified boot image
Click to expand...
Click to collapse
Dude, I'm a total idiot at this stuff...
I was trying to flash the stock ROM by some help from a youtube channel called Andoid Doctor. I used the codes he gave me and the stock firmware he provided me for cedric. But all my computer showed was some slot error.
I'd really appreciate it if you helped me out.

Astitva_ said:
Dude, I'm a total idiot at this stuff...
I was trying to flash the stock ROM by some help from a youtube channel called Andoid Doctor. I used the codes he gave me and the stock firmware he provided me for cedric. But all my computer showed was some slot error.
I'd really appreciate it if you helped me out.
Click to expand...
Click to collapse
Firmware must be the same or newer
See the link in my post above for all the firmware - choose the right one for your region
If you don't know which to choose just use this one
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Commands are (assuming you know how to use & have fastboot already setup as you have already unlocked the bootloader)
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin (only flash if newer version of android eg going from nougat to oreo)
fastboot flash bootloader bootloader.img (only flash if going to a newer version of android)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot

TheFixItMan said:
fastboot flash recovery recovery.img
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Then wipe system data cache/format data & follow procedure to flash a custom rom
Click to expand...
Click to collapse
Wasn't trying to go back to stock myself (though I did have to in the end) but this was the only rom I found that worked full stop. Thanks so much for this.

Is there any way to have pie on a sprint variant?

does anyone know if there is some way to flash stock pie on a sprint variant??

Yes, see page 3 of following post:
https://forum.xda-developers.com/z2-force/how-to/verizon-update-t3952591/page3

Copying Hibinoh's work here for simplicity (not my work; this is a copy of the post of the person above):
Since someone asked Sprint, to get 9.0 on your sprint, following the steps:
1, get RETIN 9.0(XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), and the latest Sprint 8.0(XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip)
2, unzip both ROM, find a copy of mfastboot, a copy of TWRP(use nash's TWRP)
3, copy the boot.img from RETIN 9.0 to your phone's sdcard
4, wipe your phone(data + cache)
5, use mfastboot flash following files from RETIN 9.0:
Code:
Code:
mfastboot oem fb_mode_set
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot oem fb_mode_clear
6, use mfastboot flash following files from Sprint 8.0(!!!BECAREFUL, DO NOT FLASHED FOLLOWING FILES FROM 9.0!!!):
Code:
mfastboot oem fb_mode_set
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp adspso.bin
mfastboot oem fb_mode_clear
7, boot into TWRP
Code:
mfastboot boot YOUR_TWRP_FILE_PATH
8, use TWRP to flash the boot.img(step 3) to 'boot'
9, reboot
Well, I am happy on 9.0, but not happy to lost google pay(yea I know there is magisk hide)

quadcrap1 said:
Copying Hibinoh's work here for simplicity (not my work; this is a copy of the post of the person above):
Since someone asked Sprint, to get 9.0 on your sprint, following the steps:
1, get RETIN 9.0(XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), and the latest Sprint 8.0(XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip)
2, unzip both ROM, find a copy of mfastboot, a copy of TWRP(use nash's TWRP)
3, copy the boot.img from RETIN 9.0 to your phone's sdcard
4, wipe your phone(data + cache)
5, use mfastboot flash following files from RETIN 9.0:
Code:
Code:
mfastboot oem fb_mode_set
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot oem fb_mode_clear
6, use mfastboot flash following files from Sprint 8.0(!!!BECAREFUL, DO NOT FLASHED FOLLOWING FILES FROM 9.0!!!):
Code:
mfastboot oem fb_mode_set
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp adspso.bin
mfastboot oem fb_mode_clear
7, boot into TWRP
Code:
mfastboot boot YOUR_TWRP_FILE_PATH
8, use TWRP to flash the boot.img(step 3) to 'boot'
9, reboot
Well, I am happy on 9.0, but not happy to lost google pay(yea I know there is magisk hide)
Click to expand...
Click to collapse
I have done this twice and it's not working i followed all the steps one by one

I'm guessing the answer is no, but, has anybody tried this with the EU version for T-Mobile or ATT? Or Verizon version, even?
I'm tempted to try, but fairly certain it won't work.

worked like a charm, I had to factory reset after flashing the boot in TWRP though

Starkiller2 said:
worked like a charm, I had to factory reset after flashing the boot in TWRP though
Click to expand...
Click to collapse
A) You did this on a US Sprint phone, right?
B) Did you do the factory reset via TWRP, through the bootloader/Recovery Mode, or through the OS?

quadcrap1 said:
A) You did this on a US Sprint phone, right?
B) Did you do the factory reset via TWRP, through the bootloader/Recovery Mode, or through the OS?
Click to expand...
Click to collapse
Yes I did, a Sprint variant, on boost Mobile.
The easiest way for me, if it helps, was to unzip the two firmware files and place the necessary files from each in a separate folder.
In twrp wipe dalvik cache and data.
Reboot to bootloader
Then flash them in the order above, but all in one go.
Boot twrp, flash boot image in twrp
Factory reset in twrp
Reboot to bootloader
Flash modem again
Reboot
I did find that no matter what I can't get twrp to stick or any recovery. It always reboots to fastboot
So you have to use the volume keys to press start

Screenshot

Starkiller2 said:
Yes I did, a Sprint variant, on boost Mobile.
The easiest way for me, if it helps, was to unzip the two firmware files and place the necessary files from each in a separate folder.
In twrp wipe dalvik cache and data.
Reboot to bootloader
Then flash them in the order above, but all in one go.
Boot twrp, flash boot image in twrp
Factory reset in twrp
Reboot to bootloader
Flash modem again
Reboot
I did find that no matter what I can't get twrp to stick or any recovery. It always reboots to fastboot
So you have to use the volume keys to press start
Click to expand...
Click to collapse
So it sounds like you added two extra steps to the original instructions above:
1) Factory reset in TWRP after flashing boot image in TWRP
2) As a last step, rebooting to bootloader one more time and issuing the command
Code:
mfastboot flash modem NON-HLOS.bin
(where NON-HLOS.bin comes from the Sprint image, not the Pie image, just as when it was flashed the first time).
Correct?

quadcrap1 said:
So it sounds like you added two extra steps to the original instructions above:
1) Factory reset in TWRP after flashing boot image in TWRP
2) As a last step, rebooting to bootloader one more time and issuing the command
(where NON-HLOS.bin comes from the Sprint image, not the Pie image, just as when it was flashed the first time).
Correct?
Click to expand...
Click to collapse
Yes

So I've tried the above instructions on a Sprint Z2 Force. The first time, I got into an instant bootloop. So I went through the entire procedure again, and this time, I get to about 1 minute past when the Moto M is spinning around, to where the Lenovo color blocks are supposed to appear, and the screen goes black with occasional flashes on. Eventually, it just boot loops again.
Hmmm...
I do realize that I am using for the Sprint firmware (from which a few files come):
NASH_SPRINT_OCXS27.109_48_17_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
This is a nominally different than the xml file the OP mentioned:
NASH_SPRINT_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Unfortunately, I can't find a working link to the latter...I wonder if that could be the issue? Anyone have a working link for the 48-20 version?

quadcrap1 said:
So I've tried the above instructions on a Sprint Z2 Force. The first time, I got into an instant bootloop. So I went through the entire procedure again, and this time, I get to about 1 minute past when the Moto M is spinning around, to where the Lenovo color blocks are supposed to appear, and the screen goes black with occasional flashes on. Eventually, it just boot loops again.
Hmmm...
I do realize that I am using for the Sprint firmware (from which a few files come):
NASH_SPRINT_OCXS27.109_48_17_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
This is a nominally different than the xml file the OP mentioned:
NASH_SPRINT_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Unfortunately, I can't find a working link to the latter...I wonder if that could be the issue? Anyone have a working link for the 48-20 version?
Click to expand...
Click to collapse
I used the -20 version from here
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

So I managed to get Pie up and running on a Sprint Z2 Force. Everything seems to be working. I'm using it for T-Mobile, and Visual Voice Mail and VoLTE seem to be working.
One thing I can't get to work is Netflix. It won't install. if I sideload it, it won't run.
I use the phone for work (work profile), so I can't use Magisk (and I have no other need to root).
Anyone have a trick to get Netflix installed on a Frankenstein install like this with an unlocked bootloader.
Note: I was able to get Netflix to run on the Z2 Force with the T-Mobile flash on Sprint for Oreo.
---------- Post added at 05:07 PM ---------- Previous post was at 04:58 PM ----------
Starkiller2 said:
I used the -20 version from here
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thank you for the link!

where can I get the two files listed in step one?

delawaresace said:
where can I get the two files listed in step one?
Click to expand...
Click to collapse
The post two above yours has the link to one,
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
That's the other

Updated Tmobile Z2 Force to Pie
Starkiller2 said:
Yes I did, a Sprint variant, on boost Mobile.
The easiest way for me, if it helps, was to unzip the two firmware files and place the necessary files from each in a separate folder.
In twrp wipe dalvik cache and data.
Reboot to bootloader
Then flash them in the order above, but all in one go.
Boot twrp, flash boot image in twrp
Factory reset in twrp
Reboot to bootloader
Flash modem again
Reboot
I did find that no matter what I can't get twrp to stick or any recovery. It always reboots to fastboot
So you have to use the volume keys to press start
Click to expand...
Click to collapse
I want to report that I have followed these instructions and have updated my TMobile Z2 Force to Pie. I am not in an US network.
My steps were pretty similar:
I flashed to stock using the TMO Z2 Force 27.1.5 Flashall
Booted normally
TWRP Wipe Data, Cache and System
Followed the steps as in the Verizon Update thread making sure to follow the steps as indicated by Starkiller2 above (except Factory Reset in TWRP). Using the TMO Z2 FORCE FLASHALL files and NOT the Sprint ones
Voilà

I successfully flashed 9.0/Pie to a Sprint phone for use with T-Mobile the other day.
An update. It generally seems stable and working.
Things that do not work:
A) VoLTE: The phone drops down to "H" (HSPA) / 3G when I make/receive a call. That means that while I can use data, it unusably slow 3G. I am not sure how to fix this. It's using T-Mobile as carrier, T-Mobile US as the APN (same as a Sprint/T-Mobile Z2 Force flashed phone running Oreo I am using on T-Mobile and which gives LTE speeds during a phone call/VoLTE).
B) Netflix won't install. It doesn't even show up in the Play Store. If you try to sideload it, it will crash/stop before you can use it. This is probably related to the unlocked bootloader, although I use Netflix on the Oreo Z2 Force with unlocked bootloader with no issue.
Oh, and the Oreo running Z2 Force shows 4GLTE, while the Pie running Z2 Force shows just LTE in the exact same location. The Oreo phone gets download/upload speeds of 24.0/9.1, the Pie phone gets download/upload speeds of 28.0/9.99. FWIW.
When I make a call, I see "HD call" for the Oreo phone, I don't see it for the Pie phone.

quadcrap1 said:
So I managed to get Pie up and running on a Sprint Z2 Force. Everything seems to be working. I'm using it for T-Mobile, and Visual Voice Mail and VoLTE seem to be working.
One thing I can't get to work is Netflix. It won't install. if I sideload it, it won't run.
!
Click to expand...
Click to collapse
If I recall correctly when I flashed my Z2 I(Spring) phone to unlock it from the network and also installed Magisk for Google Pay and other stuff that did't like rootl Netflix also didn't initially. It wasn't critical since I have so many other ways to watch but out of curiosity I searched for a fix and I think it was this
'
https://forum.xda-developers.com/apps/magisk/module-netflix-enabler-enable-netflix-t3708126
I did atually take notes but they are at home and I am currently on the road so I can't confirm but it looks like what I did.

A few questions:
1. Will flashing Pie on a bootloader unlocked Sprint model require the modem from 48-20, even if the phone has only been on an earlier Oreo firmware?
2. Does using the Oreo modem mean the Sprint phone could be flashed back and forth between Pie and Oreo without issues?
3. Would there be any reason this mixed/unofficial firmware would not activate / operate normally on Sprint service?