Develop Bugs

P2 (UK) on 3 - Going from 3 to stock rom

Hello all,
I'm a bit confused about the process of taking my current '3' ROM and changing it to the official Lenovo Rom.
I have downloaded the lenovo drivers (installed and ok) phone is in debug mode.
I have downloaded the stock rom from here: https://forum.xda-developers.com/lenovo-p2/development/7-0-lenovo-p2a42-stock-nougat-update-t3581517 and have adb / fastboot.
I know I have to use the volume rocker and powerbutton to get into the boot mode but I don't know the commands for adb or fastboot. I have changed the name of the rom to 'update'
Can someone please advise me on the commands I am meant to enter to get this onto my phone please?
Thanks in advance,
Cue

Copy all the code below, paste it to a new text file on your PC and save it as All Files instead of .txt and name it a fastboot.bat. Place the fastboot.bat in the adb/fastboot directory, also place the unpacked rom in the same path. Run it as admin. Profit.
Code:
fastboot flash partition gpt_both0.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 system systemchunk0.img
fastboot flash system systemchunk1.img
fastboot flash system systemchunk2.img
fastboot flash system systemchunk3.img
fastboot flash system systemchunk4.img
fastboot flash system systemchunk5.img
fastboot flash system systemchunk6.img
fastboot flash system systemchunk7.img
fastboot flash system systemchunk8.img
fastboot flash system systemchunk9.img
fastboot flash system systemchunk10.img
fastboot flash system systemchunk11.img
fastboot flash system systemchunk12.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo pause

Hi, op here.
Firstly, thank you for responding! Your instructions seem very clear. When i had a look at the contents of the ROM (in zip) i couldn't see any of the systemchunk files you mention, are they hidden deep somewhere?
Regards,
Cue.

If your phone is stock the Rom can be updated without fastboot or a PC.
All the instructions are in that thread.

Huh. Surely just boot into recovery and install the update.zip? No need to have it connected to pc.

Hello all,
Yep. I un-encrypted the sd card copied the zip onto it and booted up that way. Very easy. Now running stock directly from Lenovo which I am very happy about! It also pushed the new 78mb update as well.
Thank you for all your input.

same way i did it too theirs no need to do it through fastboot method just like the other people i did it through the built in recovery by renaming the Nougat rom to update.zip works fine and you will get another update ota straight after t obring it right up to date.

Sounds like you guys have this sorted :highfive:
Just for completeness, can somebody upload the original 3 rom? It just helps out the person who thinks they have a hardware issue and may need to return the phone to 3.
If you try and return your phone and it doesn't have the original 3 rom, your chances of a good outcome are obviously less as you have tampered with the phone etc.

The warranty is with Lenovo Not three.
Doubt there'd be an issue as the bootloader will still be locked and it's an official Lenovo Firmware.
Since flashing nougat and a factory wipe my VOLTE is now working.

I did the same flashed nougat and volte is working but only shows up some times not as much as I'd like is their any way to get volte to work more often. In my bedroom where the signal is weak I don't get the volte symbol at all.

philje123 said:
The warranty is with Lenovo Not three.
Doubt there'd be an issue as the bootloader will still be locked and it's an official Lenovo Firmware.
Since flashing nougat and a factory wipe my VOLTE is now working.
Click to expand...
Click to collapse
How you enabled VoLte on nougat? You are on stock rom or branded?

I'm on stock unbranded.
VOLTE settings now show up in phone menu and it just works. I had to factory reset though as initially it didn't work after flashing nougat.

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

Motorola One Vision July update

Good news, motorola anounced the July update for the Motorola One Vision in his blog.
https://support.motorola.com/rola/e...family/motorola-one-vision/documents/MS141417
This update includes the july 1 security update
I don't know the delay but today in August 1 the update is available

I got my device in May and already recieved the June update, so it's not the first for me.
But I believe one vision was released later (June) for some regions.

luisjoseb said:
Good news, motorola publishied the first update for the Motorola One Vision in his blog.
https://support.motorola.com/rola/e...family/motorola-one-vision/documents/MS141417
This update includes the july 1 security update
I will update the post when this come to the device!!!
Click to expand...
Click to collapse
Do you know if this update solve the bootloop caused by enable fingerprint along with developer option ?

AndresOrue said:
Do you know if this update solve the bootloop caused by enable fingerprint along with developer option ?
Click to expand...
Click to collapse
Awaiting the update. But I don't think what you have described is the actual issue. I have fingerprint and developer options enabled and the device works just fine.
From what I have read, the issue is fingerprint + changing the default USB configuration. Isn't it?

baunthiyal said:
Awaiting the update. But I don't think what you have described is the actual issue. I have fingerprint and developer options enabled and the device works just fine.
From what I have read, the issue is fingerprint + changing the default USB configuration. Isn't it?
Click to expand...
Click to collapse
I changed that setting the first time and the phone enter in a bootloop and because I had to reset everything, I didn't try again . In this moment, I have developer option enable and the fingerprint disable.

AndresOrue said:
I changed that setting the first time and the phone enter in a bootloop and because i had to reset everything, I didn't try again . In this moment i have developer option enable and the fingerprint disable.
Click to expand...
Click to collapse
Here's my journey with Vision as of now -
1. Got this phone last week
2. Added fingerprints
3. Updated to PSA29.137-17
4. Enabled developer options
5. Changed all animation rates in developer options to 0.5
I'm not sure you should try steps 1-4. But personally, I didn't have the issue you have described.

baunthiyal said:
Here's my journey with Vision as of now -
1. Got this phone last week
2. Added fingerprints
3. Updated to PSA29.137-17
4. Enabled developer options
5. Changed all animation rates in developer options to 0.5
I'm not sure you should try steps 1-4. But personally, I didn't have the issue you have described.
Click to expand...
Click to collapse
Thanks mate. I enabled fingerprint and developer option and it works. Seems that the problem was what You said, enable fingerprint and changing the default USB configuration.

i just installed this update and after i checked the app for new android update it told me:
integrity system corrupted
You will not be able to get any future updates.
Go to the store and official rom will be installed
Something like this .. Do you see this aswell?

I have bought my one vision the day it became available in my country, June 3rd, I have April's security patch and nothing to update, is there any other security patch available?

ᕙ(⇀‸↼)ᕗ said:
i just installed this update and after i checked the app for new android update it told me:
integrity system corrupted
You will not be able to get any future updates.
Go to the store and official rom will be installed
Something like this .. Do you see this aswell?
Click to expand...
Click to collapse
This is normal with bootloader unlocked.
View attachment 4793287

xt1970-3 touch not working
i got a xt1970-3 from customer and touch is not working, i tried to flash with fastboot " XT1970-3_KANE_RETEU_9.0_PSA29.137-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" the same version in phone, i flashed logo.bin, boot.img, system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, system.img_sparsechunk.2, system.img_sparsechunk.3, system.img_sparsechunk.4, system.img_sparsechunk.5, system.img_sparsechunk.6, system.img_sparsechunk.7, system.img_sparsechunk.8, system.img_sparsechunk.9, system.img_sparsechunk.10, system_other.img_sparsechunk.0, system_other.img_sparsechunk.1, system_other.img_sparsechunk.2,
and now phone in bootloop mode, please i want to known how to flash this again

rizni said:
i got a xt1970-3 from customer and touch is not working, i tried to flash with fastboot " XT1970-3_KANE_RETEU_9.0_PSA29.137-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" the same version in phone, i flashed logo.bin, boot.img, system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, system.img_sparsechunk.2, system.img_sparsechunk.3, system.img_sparsechunk.4, system.img_sparsechunk.5, system.img_sparsechunk.6, system.img_sparsechunk.7, system.img_sparsechunk.8, system.img_sparsechunk.9, system.img_sparsechunk.10, system_other.img_sparsechunk.0, system_other.img_sparsechunk.1, system_other.img_sparsechunk.2,
and now phone in bootloop mode, please i want to known how to flash this again
Click to expand...
Click to collapse
This is how I flash full firmware without wiping userdata.
Code:
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.nbl1.bin
fastboot flash ldfw_a ldfw.bin
fastboot flash ldfw_b ldfw.bin
fastboot flash keystorage_a keystorage.bin
fastboot flash keystorage_b keystorage.bin
fastboot flash bootloader_a bootloader.bin
fastboot flash bootloader_b bootloader.bin
fastboot flash modem_a modem.bin
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot fastboot flash vendor_a vendor.img
If you want to wipe userdata you could just add "fastboot erase userdata" at the end.
If that won't work it's probably broken digitizer or something.

thank you for quick guide, the phone is on now but the touch not working, it must be something to do with hardware
thank you

luisjoseb said:
Good news, motorola anounced the July update for the Motorola One Vision in his blog.
https://support.motorola.com/rola/e...family/motorola-one-vision/documents/MS141417
This update includes the july 1 security update
I don't know the delay but today in August 1 the update is available
Click to expand...
Click to collapse
I got the update yesterday

wtf
tys0n said:
This is normal with bootloader unlocked.
View attachment 4793287
Click to expand...
Click to collapse
I just noticed that new update is out.. so I tried click to update and woala it works.
OEM unlocked..
So with bootloader unlocked you are still able to get updates..

ᕙ(⇀‸↼)ᕗ said:
I just noticed that new update is out.. so I tried click to update and woala it works.
OEM unlocked..
So with bootloader unlocked you are still able to get updates..
Click to expand...
Click to collapse
There is no update for me
And Google Duo not work

ed.shevsky said:
There is no update for me
And Google Duo not work
Click to expand...
Click to collapse
i dont use duo, but i tried to root it and failed.. so i flashed stock boot.img
then tried to update
Maybe that flashed boot.img helped it or IDK.
you can try it- find your firmware
download it - extract it- find boot.img- place it in your home folder
use fastboot (instal adb tools and drivers ) with command (fastboot flash boot boot.img)
your phone must be in download mode - (power off, then press power and volume down button)
Is it avaible for your country?

ᕙ(⇀‸↼)ᕗ said:
i dont use duo, but i tried to root it and failed.. so i flashed stock boot.img
then tried to update
Maybe that flashed boot.img helped it or IDK.
you can try it- find your firmware
download it - extract it- find boot.img- place it in your home folder
use fastboot (instal adb tools and drivers ) with command (fastboot flash boot boot.img)
your phone must be in download mode - (power off, then press power and volume down button)
Is it avaible for your country?
Click to expand...
Click to collapse
Sorry, my fault. My phone is locked, so I don't need to flash boot.img
May be you know a method to force OTA update?
And about Google Duo. The program stop working after Play Market version updated. Once I fix it by factory reset. But I don't want do it every time

ᕙ(⇀‸↼)ᕗ said:
I just noticed that new update is out.. so I tried click to update and woala it works.
OEM unlocked..
So with bootloader unlocked you are still able to get updates..
Click to expand...
Click to collapse
Ok nice. Still didn't work for me but I'm flashing it with fastboot now instead.

ᕙ(⇀‸↼)ᕗ said:
i dont use duo, but i tried to root it and failed.. so i flashed stock boot.img
then tried to update
Maybe that flashed boot.img helped it or IDK.
you can try it- find your firmware
download it - extract it- find boot.img- place it in your home folder
use fastboot (instal adb tools and drivers ) with command (fastboot flash boot boot.img)
your phone must be in download mode - (power off, then press power and volume down button)
Is it avaible for your country?
Click to expand...
Click to collapse
Did you also get error about "too many links" when trying to flash magisk patched boot?

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?

How to revert Moto G5 XT1670 to stock rom

Hello, how are you? My Name Is Cristian and I'm from Argentina.
I've had a Moto G5 for a while and a lot of custom roms were installed on it. However, there were many problems in the process. The roms had bugs, performance issues, and some didn't even boot.
So i made the decision to go back to the factory rom and close the bootloader forever. But it couldn't. Something prevented it. Something was causing the phone to not start properly.
Therefore, after doing so many laps, i was able to do the whole process.
And today i publish this topic so that you can do it too. I hope you can come out triumphant in the process just like me. Have lucky!
1) The first thing you should do is download Rescue & Smart assistant. Install on your pc and create account (if you not) or login in.
Code:
https://support.lenovo.com/es/es/downloads/DS101291
2) You will need to find the official firmware of your device. Search for the exact device SKU (model of your phone) and exact region. For example the SKU of my device is XT1670 the region is RETAR (from Argentina). If you are from United States (and try to install RETAR) Rescue & Smart assistant will not recognize the SKU of your device, and will not be able to continue.
Find the exact firmware corresponding to your mobile phone.
Code:
https://mirrors.lolinet.com/firmware/moto/cedric/official/
Unzip the rom in the place that you prefer.
3) Now put your device in bootloader mode and execute the following commands (ignoring any errors in the process)
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 erase cache
fastboot erase userdata
fastboot reboot
4) Once the above process is finished, start your phone normally. Go to the developer options and activate usb debugging. Plug the phone into PC.
Open "Rescue & Smart assistant" and accept usb debugging on your phone. The app installs some control app, dont worry.
Go to Rescue & Smart assistant and select "Rescue". The program will recognize your phone's SKU if you downloaded the correct firmware. Otherwise, if a wrong sign appears, you will have to repeat step 2 and 3 with the correct firmware.
Click on "Rescue now" and the program will download the firmware corresponding to your phone. After this, the firmware installation will begin.
Why do all this process?
The Rescue & Smart app is official from Motorola. When the official firmware is installed, the signed firmware files are also installed with it. The firmware is official because is delivered directly by Motorola, specifically for your mobile phone, and not by unofficial sites.
5) Hey, wait! the bootloader needs to be blocked. True.
Go to C:\ProgramData\LMSA\Download\RomFiles and you will find there the official rom downloaded by "Rescue & Smart". This rom is unique, signed and official. Only for your phone, only for its hardware. Do not lose it. It will save your ass from many inconveniences, if one day you want to continue experimenting with your phone.
Copy the whole directory in other site and open cmd in it. Now shutdown your phone and start it in bootloader mode.
Now put these commands (ignoring bla bla bla errors):
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 boot boot.img
fastboot oem lock
And that's it. Your mobile phone is now official and with its bootloader locked. almost factory-made.
So thank you for reading all this and I hope the information has served you a lot. Any questions about it (about this) do not hesitate to consult.

Great post and thanks for taking the time to post it :good:
For people who might struggle with this I've used Moto Auto Flash Tool v8.2 By Jamesjerss.rar with great success,
https://www.ytechb.com/moto-auto-flash-tool/
Takes a lot of the hard work out of it :good:

R1ffR4ff said:
Great post and thanks for taking the time to post it :good:
For people who might struggle with this I've used Moto Auto Flash Tool v8.2 By Jamesjerss.rar with great success,
https://www.ytechb.com/moto-auto-flash-tool/
Takes a lot of the hard work out of it :good:
Click to expand...
Click to collapse
The reason i made this post was mainly because a lot of people have problems with unsigned firmware and cannot follow normal recovery processes. However, I will consider this application for future experiments. It seems to be an application that already has the commands prepared, so there are no errors. The problem is that it does not offer the official firmware (from Motorola) directly for the specific device. Anyway it is good not to make mistakes in the commands.
Ty.

He.Art said:
The reason i made this post was mainly because a lot of people have problems with unsigned firmware and cannot follow normal recovery processes. However, I will consider this application for future experiments. It seems to be an application that already has the commands prepared, so there are no errors. The problem is that it does not offer the official firmware (from Motorola) directly for the specific device. Anyway it is good not to make mistakes in the commands.
Ty.
Click to expand...
Click to collapse
It's a great little program that I had to use Yesterday on a Moto G3 as the normal ADB way as per your post wouldn't work for whatever reason and I've used ADB loads
I was my own fault on that phone as I,"Soft Bricked" it using the latest version Magisk uninstall option so NEVER use this option in Magisk. I returned the phone to Stock and then upgraded it to my favourite Custom roms