Develop Bugs

Flashing Instructions stock rom. Please HELP

Can anybody provide with the flashing instruction for moto g5

yolomonkey said:
Can anybody provide with the flashing instruction for moto g5
Click to expand...
Click to collapse
Assuming you have fastboot installed on your pc
Download firmware and unzip to where you have fastboot
Open command prompt at fastboot location with firmware
type the following although I have marked lines that you should not use unless you have to as flashing wrong firmware can damage your device
Code:
fastboot oem fb_mode_set Only required if you wish to relock bootloader - if not skip it
fastboot flash partition gpt.bin Do not use unless you want to repartition your device - incorrect file will damage your phone
fastboot flash bootloader bootloader.img Do not use unless you want to replace the bootloader - flashing wrong file will hard brick
fastboot flash logo logo.bin No need to flash if you are going to flash a custom rom after and have already flashed a modded version
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata Will erase everything on internal storage but you need to do it
fastboot erase customize Not sure about this - might be for other device
fastboot erase clogo Not sure about this - might be for other device
fastboot oem fb_mode_clear Only required to relock bootloader if you used the very first command
fastboot reboot

NOt working
My device keeps booting to the recovery
even though i flashed my recovery. it boots to twrp

yolomonkey said:
My device keeps booting to the recovery
even though i flashed my recovery. it boots to twrp
Click to expand...
Click to collapse
have you read the FAQs on my twrp thread because the answer is there (assuming you have flashed a custom rom and can boot it through the bootloader by selecting start)

TheFixItMan said:
have you read the FAQs on my twrp thread because the answer is there (assuming you have flashed a custom rom and can boot it through the bootloader by selecting start)
Click to expand...
Click to collapse
could you please link it. I am so grateful for you replying this fast

yolomonkey said:
could you please link it. I am so grateful for you replying this fast
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
FAQs are on 2nd post

[GUIDE][Perry(Qualcomm)][Windows, macOS & Linux] Flash Stock Firmware and Recovery

[GUIDE][Perry(Qualcomm)][Windows, macOS & Linux] Flash Stock Firmware and Recovery
*This has only been personally done and tested using a Sprint Qualcomm variant of the Moto E4. I will be working on expanding this guide to cover all specific models of the Perry to avoid potential confusion as there are minor differences, so if anyone wants to pass along their firmware's flashfile.xml into my inbox it would be greatly appreciated.*
Links:
ADB and Fastboot mini .zip for macOS/Windows (Linux users make sure to have android-sdk installed, no need for this download)
All Stock Firmwares (sperry is Sprint firmware, perry is the rest of the Qualcomm models (Thanks to proudlytm) https://mirrors.lolinet.com/firmware/moto//
What you need:
A Windows/macOS/Linux computer
A USB cable
ADB and Fastboot files
Stock Firmware
Your phone
*Disclaimer* Your warranty is now void if you modify your phone. I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Let's get started! First, backup to your computer/Dropbox/etc. all the files you wish to save. This will wipe all data off your phone including root (Not data saved on any cloud services, such as Google, OneDrive, Dropbox, etc.)
Second, boot your phone into the bootloader. This can be done in certain ROM power menus, or with the ADB command "adb reboot bootloader" in Command Prompt/Terminal, or also by turning off your phone and then holding the power and volume down buttons at the same time. After booting into the bootloader, plug your phone into your computer.
The firmware file will look similar to This when extracted
Make sure to look in the firmware folder to see if you need to change a few lines during flashing. If you are unsure, check the flashfile.xml
Next open up Command Prompt if on Windows, Terminal if on macOS/Linux.
Navigate in CMD Prompt/Terminal to the directory you downloaded and extracted the stock firmware. Copy the Fastboot and ADB files into the same directory as the stock firmware files.
For Windows and Linux users, enter the following commands in Command Prompt/Terminal (use sudo before each command in Linux, or use sudo -s beforehand):
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
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 oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
For macOS, enter the following in Terminal:
./fastboot oem fb_mode_set
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
./fastboot flash modem NON-HLOS.bin
./fastboot flash fsg fsg.mbn
./fastboot erase modemst1
./fastboot erase modemst2
./fastboot flash dsp adspso.bin
./fastboot flash logo logo.bin
./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 oem oem.img_sparsechunk.0
./fastboot flash oem oem.img_sparsechunk.1
./fastboot erase cache
./fastboot erase userdata
./fastboot erase DDR
./fastboot oem fb_mode_clear
./fastboot reboot
Click to expand...
Click to collapse
Hope it helps!

*Reserved*

This is good for the XT1766, but the other variants firmwares have differences. Some have an extra system sparsechunk and an oem.img rather than 2 oem sparsechunks.

</poorly_coded> said:
This is good for the XT1766, but the other variants firmwares have differences. Some have an extra system sparsechunk and an oem.img rather than 2 oem sparsechunks.
Click to expand...
Click to collapse
Thanks for letting me know, I'll add a note

Hello, I have followed all of the directions and when I reboot the device, it says "bad key" then it goes to a screen where it says "erasing" and just keeps on doing this. Any help would be appreciated. Thanks

codyalan said:
Hello, I have followed all of the directions and when I reboot the device, it says "bad key" then it goes to a screen where it says "erasing" and just keeps on doing this. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
Because your bootloader is unlocked.

codyalan said:
Hello, I have followed all of the directions and when I reboot the device, it says "bad key" then it goes to a screen where it says "erasing" and just keeps on doing this. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
I have restored stock on my E4's (I have two, one with a cracked screen) a whole bunch of times, from soft-bricked stock and also from custom ROM's. The key for me was to NOT flash gpt.bin. Leave that step out.
First thing I'd try is re-flashing just the stock boot.img, then see if you can get boot normally... if not...
Try re-flashing stock bootloader and stock recovery, reboot to stock recovery and factory reset. Reboot to bootloader and start stock flashing again (thanks @acejavelin), but don't flash the gpt.bin.
If that fails, one thing that worked for me when I was bootlooped was to completely install a custom ROM and Recovery (I used LineageOS and TWRP), get it up and running, then go ahead and restore the whole business back to stock.
The bad key thing.... it will say that for a few seconds (up to 30 seconds, maybe?) on boot when you restore stock but should get past it. I think it keeps echoing that every time you restart until you've replaced your recovery with a custom one, then the message turns into 'N/A'.
HTH

Ok so I wanted to update this thread. I have the XT1768 and the instructions are a bit different. For the XT1768 there is a Sparsechunk.5 and also for the XT1768 there is only a oem.img. By changing those steps I was able to get unstuck and back in business.

Vicpdx18 said:
Ok so I wanted to update this thread. I have the XT1768 and the instructions are a bit different. For the XT1768 there is a Sparsechunk.5 and also for the XT1768 there is only a oem.img. By changing those steps I was able to get unstuck and back in business.
Click to expand...
Click to collapse
Do you happen to have a copy of the flashfile.xml for your model number you could send to me? I've been wanting to further expand this guide to encompass each individual QComm model

fireball0093 said:
Do you happen to have a copy of the flashfile.xml for your model number you could send to me? I've been wanting to further expand this guide to encompass each individual QComm model
Click to expand...
Click to collapse
For the Xt1768??

codyalan said:
For the Xt1768??
Click to expand...
Click to collapse
Yes, if you have one for it that'd be awesome

fireball0093 said:
Yes, if you have one for it that'd be awesome
Click to expand...
Click to collapse
No Problem,

Would you by chance have a stock rom for the XT1769? Anything I would need to know about restoring it to stock?
---------- Post added at 02:45 AM ---------- Previous post was at 02:43 AM ----------
And not sure if there is a thread for this, if there is could you point me in that direction?Is there a way to create a ROM from a stock phone?

McTRASH692 said:
Would you by chance have a stock rom for the XT1769? Anything I would need to know about restoring it to stock?
---------- Post added at 02:45 AM ---------- Previous post was at 02:43 AM ----------
And not sure if there is a thread for this, if there is could you point me in that direction?Is there a way to create a ROM from a stock phone?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ap...perr-s-kitchen-v3-0-0-0-t3601702/post72168885
How to start building

madbat99 said:
https://forum.xda-developers.com/ap...perr-s-kitchen-v3-0-0-0-t3601702/post72168885
How to start building
Click to expand...
Click to collapse
Thanks heaps, it'd be nice to create stock rom before root just incase the phone bricks.

McTRASH692 said:
Would you by chance have a stock rom for the XT1769? Anything I would need to know about restoring it to stock?
---------- Post added at 02:45 AM ---------- Previous post was at 02:43 AM ----------
And not sure if there is a thread for this, if there is could you point me in that direction?Is there a way to create a ROM from a stock phone?
Click to expand...
Click to collapse
I built the XT1765 Flashable rom in Assaayd's Kitchen. Followed the instructions to a T, and had no problems. Try him out too.

Articul8Madness said:
I built the XT1765 Flashable rom in Assaayd's Kitchen. Followed the instructions to a T, and had no problems. Try him out too.
Click to expand...
Click to collapse
Cheers mate,
I have since found a stock rom for my phone and fixed it completely,
Thank you for helping though,

Hi guys,
Could someone please post the contents of their stock build.prop file? I have corrupted mine and can't find one anywhere,
Device is moto e4 xt1769

Moto E4 Qualcomm (Owens) completely back to stock

WARNING: if the gpt.bin flash did not work, please stop and do not continue with the rest of the commands. It has been brought to my attention that software upgrades to the phone has changed the gpt and may not allow you to go back to the original stock firmware.
For all of you who DID NOT do a System image backup in TWRP and then found out your backup doesn't work.
First get your stock firmware here, the only place to get Moto stock firmware!
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/
Then get fastboot. Google fastboot or grab the one from here: This one still works:
https://forum.xda-developers.com/showthread.php?t=2317790
If your fastboot directory isn't in your $PATH or you don't know how to do that, then copy fastboot into the same folder where you unzipped your stock firmware.
Got to the folder where you put everythig, open up a command or powershell prompt. Hold down shift, right click, "open command window here".
Now for the fun. You veterans can just look at the flashfile.xml to see the order. Those of you who are new, here are the commands you need to do. You could probably copy the entire thing and past it in your command window at one time. But I like to type it out.... line by line. You know, old school.
Commands:
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem hlos.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
the command to erase ddr will probably fail, but that shouldn't affect anything. I have tested by bringing my Moto E4 Plus that was running Lineage OS back to 100% stock. Of course, then I went right back to Lineage

Outstanding. Thank you for the post. I'm sure this will get used quite a bit. I did do a backup but it's always nice to have contingencies at the ready.
Sent from my Nexus 10 using XDA Premium HD app

I know this may sound like a stupid question, but which firmware package should I download and use for the Device purchased straight from Motorola? There are quite a few there and I don't want to flash the wrong one. This device was supposed too work on any US carrier and I would like to keep it that way, but my carrier is Verizon. All I had to do, when I got the device was install my Verizon Sim out of my Nexus 6 and it worked great. I do test for Cricket network too and that is a GSM radio so as I said, I would like it to have the firmware that would have come right from Motorola for this specific device. Thank you in advance.

glockman4519 said:
I know this may sound like a stupid question, but which firmware package should I download and use for the Device purchased straight from Motorola? There are quite a few there and I don't want to flash the wrong one. This device was supposed too work on any US carrier and I would like to keep it that way, but my carrier is Verizon. All I had to do, when I got the device was install my Verizon Sim out of my Nexus 6 and it worked great. I do test for Cricket network too and that is a GSM radio so as I said, I would like it to have the firmware that would have come right from Motorola for this specific device. Thank you in advance.
Click to expand...
Click to collapse
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

aj2333 said:
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thank you very much. You sir are an awesome person.

I have another question and forgive me for being a pain but all steps went ok but at the end where the re-boot takes place it just keeps flashing back and forth from a black screen with "Bad Key" in the upper left corner and then to a screen with a colorful circle that says "erasing". I figured it was just doing a factory reset but it just keeps flashing back and forth between the 2 screens. Any idea what to try ? I tryed to boot to recovery and get the same thing. Thank you for any help.

glockman4519 said:
I have another question and forgive me for being a pain but all steps went ok but at the end where the re-boot takes place it just keeps flashing back and forth from a black screen with "Bad Key" in the upper left corner and then to a screen with a colorful circle that says "erasing". I figured it was just doing a factory reset but it just keeps flashing back and forth between the 2 screens. Any idea what to try ? I tryed to boot to recovery and get the same thing. Thank you for any help.
Click to expand...
Click to collapse
Did you remember to do an fastboot OEM fb_mode_clear?

no I didn't do that. I will go back over your instructions and re-do it. Thank you again for your assistance. I usually don't bug people for help and try to fix things on my own so I really appreciate you help.
Sent from my G3223 using XDA Premium HD app

Actually that is the command input right before the reboot command so I guess I did do that command. I will research this more and thank you for your help once again.

glockman4519 said:
Actually that is the command input right before the reboot command so I guess I did do that command. I will research this more and thank you for your help once again.
Click to expand...
Click to collapse
The cmd commands above aren't written correctly for carrier unlocked E4 Plus's. Hlos.bin isn't in the unlocked stock ROM, NON-HLOS.bin is. Also, "flasty" should be flash. Here is the correct commands. This worked on my unlocked phone.
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot

doodalydoo said:
The cmd commands above aren't written correctly for carrier unlocked E4 Plus's. Hlos.bin isn't in the unlocked stock ROM, NON-HLOS.bin is. Also, "flasty" should be flash. Here is the correct commands. This worked on my unlocked phone.
Click to expand...
Click to collapse
You Sir are the man. I can't thank you enough for your help.
Update: Awesome.... It worked like a charm. I have everything copied now in case I hit the wall again. Thank you once again.

So I have used this and it worked great. However does anyone know when the firmware in that download will be updated to the latest version?

XT1775 rom's is possible install on XT1776 ?

almao11 said:
XT1775 rom's is possible install on XT1776 ?
Click to expand...
Click to collapse
Not Stock ROM, no. Custom ROMs should work fine tho
---------- Post added at 11:41 AM ---------- Previous post was at 11:32 AM ----------
For OP @zerogun & those of you wondering which stock ROM Firmware to grab for Boost Mobile's XT1776 (owens), I used this one and it worked 100%. The Fastboot cmd list in the 10th post or so i nears perfect, (all the rest is Golden) except that for the Boost Mobile FW's:
fastboot flash oem.img
..needs to actually be:
fastboot flash oem.img_sparsechunk.0
fastboot flash oem.img_sparsechunk.1

Cool miner malware that pops up on firmware.center.

mattleft said:
Cool miner malware that pops up on firmware.center.
Click to expand...
Click to collapse
I haven't had that problem. Have you scanned your PC for virus/malware?

I would like to relock my bootloader but on this firmware it says the boot is not signed. Can I relock it after I do the ota as they should be signed then right?

bcrichster said:
Not Stock ROM, no. Custom ROMs should work fine tho
---------- Post added at 11:41 AM ---------- Previous post was at 11:32 AM ----------
For OP @zerogun & those of you wondering which stock ROM Firmware to grab for Boost Mobile's XT1776 (owens), I used this one and it worked 100%. The Fastboot cmd list in the 10th post or so i nears perfect, (all the rest is Golden) except that for the Boost Mobile FW's:
fastboot flash oem.img
..needs to actually be:
fastboot flash oem.img_sparsechunk.0
fastboot flash oem.img_sparsechunk.1
Click to expand...
Click to collapse
Did this allow you to use a non Boost/Sprint sim card?
Thanks,
Victor

mindstream98 said:
Did this allow you to use a non Boost/Sprint sim card?
Thanks,
Victor
Click to expand...
Click to collapse
I read in another thread that it was possible by using a Custom ROM but haven't tried it myself..
Although the Custom ROMs should work on several Carriers, this is a "Completely Back to Stock" thread..
Running an Xp3r!meπt with my XT1776

zerogun said:
For all of you who DID NOT do a System image backup in TWRP and then found out your backup doesn't work.
First get your stock firmware here, the only place to get Moto stock firmware!
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/
Then get fastboot. Google fastboot or grab the one from here: This one still works:
https://forum.xda-developers.com/showthread.php?t=2317790
If your fastboot directory isn't in your $PATH or you don't know how to do that, then copy fastboot into the same folder where you unzipped your stock firmware.
Got to the folder where you put everythig, open up a command or powershell prompt. Hold down shift, right click, "open command window here".
Now for the fun. You veterans can just look at the flashfile.xml to see the order. Those of you who are new, here are the commands you need to do. You could probably copy the entire thing and past it in your command window at one time. But I like to type it out.... line by line. You know, old school.
Commands:
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem hlos.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
the command to erase ddr will probably fail, but that shouldn't affect anything. I have tested by bringing my Moto E4 Plus that was running Lineage OS back to 100% stock. Of course, then I went right back to Lineage
Click to expand...
Click to collapse
I used this to go back to stock, now my phone wont even turn on, at all.

Question About IMEI and Reflashing Stock ROM

I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.

CompostKicker said:
I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.
Click to expand...
Click to collapse
Hey man, have you have any success on this?

CompostKicker said:
I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.
Click to expand...
Click to collapse
ogabriel said:
Hey man, have you have any success on this?
Click to expand...
Click to collapse
Yes and no. I was able to get a backup of the EFS partition from the LineageOS 15.1 ROM, which does restore cell service. However, it does not provide 4G LTE. I can get LTE on LineageOS, but when I reflash stock and then restore the EFS partition, it only gets me 3G connectivity. So far, the only way that I have been able to get LTE is to flash LineageOS, then run this:
Code:
fastboot erase modemst1 && fastboot erase modemst2
Apparently, those are cache files for something that has an effect on connectivity, though I don't know specifically what. Unfortunately, I must remain on LineageOS in order to keep the LTE. If I try erasing the modem caches on stock, it wipes all connectivity and returns me to IMEI 0. Downsides to this are bluetooth calls don't work at all, GPS navigation doesn't work, absolutely no torch (even with a third party app) and battery life is poo.
I am still looking in to this, including compiling my own ROM from source. Really, this whole ordeal has taught me two very important things:
1) Always make a complete backup of everything.​2) Don't buy a phone that has no developer support on XDA. Honestly, this is the biggest one right here. Its revolting how little support there is for this device.​I will update this thread as I get new information on potential fixes.

Thank you compostkicker ..would apprentice if you post the solution if you find one..I am also going through a ditto condition

ogabriel said:
Hey man, have you have any success on this?
Click to expand...
Click to collapse
I'm facing the same here. My problems started after the "erase modemst" command. After that I never was able to use my LTE connection again. I was able to use at least a H+ connection after I flashed a stock rom WITHOUT wiping nor formating data from a Lineage install. But, still no LTE. =/
I'm afraid this is caused by wrong modem driver w/ the downloaded stock rom. Don't know if there's a different driver for the Brazillian device.

CompostKicker said:
Yes and no. I was able to get a backup of the EFS partition from the LineageOS 15.1 ROM, which does restore cell service. However, it does not provide 4G LTE. I can get LTE on LineageOS, but when I reflash stock and then restore the EFS partition, it only gets me 3G connectivity. So far, the only way that I have been able to get LTE is to flash LineageOS, then run this:
Code:
fastboot erase modemst1 && fastboot erase modemst2
Apparently, those are cache files for something that has an effect on connectivity, though I don't know specifically what. Unfortunately, I must remain on LineageOS in order to keep the LTE. If I try erasing the modem caches on stock, it wipes all connectivity and returns me to IMEI 0. Downsides to this are bluetooth calls don't work at all, GPS navigation doesn't work, absolutely no torch (even with a third party app) and battery life is poo.
I am still looking in to this, including compiling my own ROM from source. Really, this whole ordeal has taught me two very important things:
1) Always make a complete backup of everything.​2) Don't buy a phone that has no developer support on XDA. Honestly, this is the biggest one right here. Its revolting how little support there is for this device.​I will update this thread as I get new information on potential fixes.
Click to expand...
Click to collapse
YEEEEEEESSS I FIXED IT!!! HAHAHAHAHA
I followed what you said installing Lineage OS and did the "erase modemst" command. After that, I formated data using TWRP and flashed a stock rom but I skipped "erase modemst" command. And now my LTE is working on the stock rom. OMG!!!! \o/
So...
1. Flash Lineage OS 15.1
2. Restart in Bootloader and run the fastboot code [fastboot erase modemst1 && fastboot erase modemst2]
3. Restart the system.
4. Restart and use TWRP to FORMAT data.
5. Flash the stock rom using Fastboot and the following commands:
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 modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
DON'T RUN THE MODEM ERASE CODE AGAIN!!!
This steps will fix the issue!

varun.katoch said:
Thank you compostkicker ..would apprentice if you post the solution if you find one..I am also going through a ditto condition
Click to expand...
Click to collapse
Sorry to leave you hanging, I stopped getting alerts on this thread for some reason. I am on shift until tomorrow and away from my computer, and it is a lot to type for a phone, but as soon as I am able I will type out the exact steps I used to fix the LTE issue, for both LineageOS and stock ROM.

Rodrigo Fernandes said:
YEEEEEEESSS I FIXED IT!!! HAHAHAHAHA
I followed what you said installing Lineage OS and did the "erase modemst" command. After that, I formated data using TWRP and flashed a stock rom but I skipped "erase modemst" command. And now my LTE is working on the stock rom. OMG!!!! \o/
So...
1. Flash Lineage OS 15.1
2. Restart in Bootloader and run the fastboot code [fastboot erase modemst1 && fastboot erase modemst2]
3. Restart the system.
4. Restart and use TWRP to FORMAT data.
5. Flash the stock rom using Fastboot and the following commands:
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 modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
DON'T RUN THE MODEM ERASE CODE AGAIN!!!
This steps will fix the issue!
Click to expand...
Click to collapse
Thank you bro, can you say which model you have and which retail firmware have you chosen for flashing via fastboot?

HTCDevil said:
Thank you bro, can you say which model you have and which retail firmware have you chosen for flashing via fastboot?
Click to expand...
Click to collapse
Moto Z2 Play - XT1710-07 and the retail firmware was NPSS26.118-19-1-6. Still working ok yet.

CHECK THIS LINK IF YOU WANT YOUR VOLTE TO WORK :
100% working
https://forum.xda-developers.com/newthread.php?do=postthread&f=6506

Rodrigo Fernandes said:
Moto Z2 Play - XT1710-07 and the retail firmware was NPSS26.118-19-1-6. Still working ok yet.
Click to expand...
Click to collapse
Without erasing modem1st and 2st, is it right?

HTCDevil said:
Without erasing modem1st and 2st, is it right?
Click to expand...
Click to collapse
That's right! But only after you follow the step 2. Otherwise it won't work.

Rodrigo Fernandes said:
That's right! But only after you follow the step 2. Otherwise it won't work.
Click to expand...
Click to collapse
I would like to pass from ZUI (on xt1710-08) to a retail one without flashing Lineage before. So, if the problem is about modem i should not erase them, so I would leave those present on the initial version unchanged

So, my situation is : signal is ok lte\4g bit IMEI is 0. I think i understand i must flash stock lineage rom with this commands, then backup efs (i've already had It), so flash stock nougat and restore efs and i should have IMEI. Is It correct?
Inviato dal mio Moto Z2 Play utilizzando Tapatalk

Rodrigo Fernandes said:
YEEEEEEESSS I FIXED IT!!! HAHAHAHAHA
I followed what you said installing Lineage OS and did the "erase modemst" command. After that, I formated data using TWRP and flashed a stock rom but I skipped "erase modemst" command. And now my LTE is working on the stock rom. OMG!!!! \o/
So...
1. Flash Lineage OS 15.1
2. Restart in Bootloader and run the fastboot code [fastboot erase modemst1 && fastboot erase modemst2]
3. Restart the system.
4. Restart and use TWRP to FORMAT data.
5. Flash the stock rom using Fastboot and the following commands:
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 modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
DON'T RUN THE MODEM ERASE CODE AGAIN!!!
This steps will fix the issue!
Click to expand...
Click to collapse
Hey, I just flashed 9 on my XT1710-8 and lost singal. do you think this trick works in my case? (havent tried yet cause didnt want to format my device!)

CompostKicker said:
I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.
Click to expand...
Click to collapse
Try Moto lenovo smart asistant to rescue your device @CompostKicker

kevoroid said:
Hey, I just flashed 9 on my XT1710-8 and lost singal. do you think this trick works in my case? (havent tried yet cause didnt want to format my device!)
Click to expand...
Click to collapse
I can't guarantee you can fix it using my step-by-step because I did it for the XT1710-07 model. Maybe you'll have to adapt the solution to yours.

Rodrigo Fernandes said:
I can't guarantee you can fix it using my step-by-step because I did it for the XT1710-07 model. Maybe you'll have to adapt the solution to yours.
Click to expand...
Click to collapse
I fixed it by flashing the original -08's Oreo ROM (Chinese ROM) and then reflashing Pie without doing the "erase modemst1.." steps.

moto z2 play imei repair
Hello everyone . i have moto z2 play xt1710-6 with stock rom. i wanna change my imei coz of lost signal. i tried many softs but i was not ablet to change it. i went to some techical shops , they used sigma and miracle , they couldnt as well. overall , how may i change its imei ? are there any way ?

MOTO G5 PLUS fastboot stock Oreo 8.1.0 Rom

Here it is most awaiting fastboot rom file...
https://drive.google.com/folderview?id=1NR--EZXzMCzbKT0GCBp3gKbp5TrU_ImE
POTTER_RETAIL_8.1.0_OPS28.85-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
fastboot commands
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 erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
if you ever played with your persist, its not fixing those persist who flashed other device persist to gain IMEI and VoLTE, safe for those who never played with their persist and for those who are having baseband with ending with capital R. Direct flashing via fastboot ending with no signals and also not imei if dont skip erase modemst1
erase modemst2.
Guide for those who are not on their own persist but with another persist able to use Signals with volte and using any custom or nougat or twrp rom
first take backup of your current working efs and persist on sd card or otg
Thn flash above rom via fastboot, dont skip anything, reboot system thn again go in fastboot menu
Flash twrp, thn in twrp only flash only FIRMWARE from SOAK Test 1 Aroma by @NZedPred ( https://www.androidfilehost.com/?fid=1322778262903990826 ), Thanks @NZedPred for his great work, now restore your efs and persist, roboot system.
If you want to lock bootloader thn follow these commands in fastboot
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
All of these worked for me as I was also not on my own persist.
everything working fine CAMERA, VOLTE, WIFI, FINGERPRINT, locked bootloader and unlocked also again with my key tht provided by moto, battery also charging faster, battery backup is also good.

Hey, will this work for hard bricked users? I've been using twrp flashable nougat stock ROMs since last year! Can't get back to full stock so!

irfanalinawaz said:
Here it is most awaiting fastboot rom file...
https://drive.google.com/folderview?id=1NR--EZXzMCzbKT0GCBp3gKbp5TrU_ImE
POTTER_RETAIL_8.1.0_OPS28.85-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
fastboot commands
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 erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
skip
fastboot erase modemst1
fastboot erase modemst2
if you ever played with your persist, its not fixing those persist who flashed other device persist to gain IMEI and VoLTE, safe for those who never played with there persist and for those who are having baseband with ending with capital R.
For those who played with their persist, there are IMEI but no network after restoring EFS and Persist backup with TWRP, so be careful.
Click to expand...
Click to collapse
With ota instalation my radio say is off....with the fastboot And jumping erase modems... Rádio Will work?

Same quesrion but nomore but to try anyways

LLegion said:
Same quesrion but nomore but to try anyways
Click to expand...
Click to collapse
Radio will work if your Persist is intact, and you never flashed others persist to gain imei and volte otherwise there are no signal. I have tried all the methods but stll working on it, let see...hope.

irfanalinawaz said:
Radio will work if your Persist is intact, and you never flashed others persist to gain imei and volte otherwise there are no signal. I have tried all the methods but stll working on it, let see...hope.
Click to expand...
Click to collapse
Tried put Oreo with one sim card only?
Another devices doing this work to get radio ?

david.gs.gm said:
Tried put Oreo with one sim card only?
Another devices doing this work to get radio ?
Click to expand...
Click to collapse
I have tried something different I was able to gain network with volte but signals are not stable they coming and going, anyways it will take time, nothing is impossible here, I am also one from those who messed up thier Persist, and I am working on it.

irfanalinawaz said:
Radio will work if your Persist is intact, and you never flashed others persist to gain imei and volte otherwise there are no signal. I have tried all the methods but stll working on it, let see...hope.
Click to expand...
Click to collapse
help me out with an issue about retail or my software channel is retin should this version is good for me to install my build number is NPNS25.137-92-14 and I already got OTA update but my persists is not mine what should I do

This means TWRP flashable is on its way.:good:

devvshukla said:
I got some errors while sending these two commands, device is working regardless of these errors.
Which are these command and whats they do? Also what issues I might be facing on future because of this?
Commands -
fastboot erase customize
fastboot erase clogo
Click to expand...
Click to collapse
These commands are not nessecery, ignore them and proceed. These commands will not affect any future ota or update.

livyansh said:
help me out with an issue about retail or my software channel is retin should this version is good for me to install my build number is NPNS25.137-92-14 and I already got OTA update but my persists is not mine what should I do
Click to expand...
Click to collapse
Bro you need to avoid this to flash, right now there is not any solution for those who are not on their persist, you will end up with no signals. So wait, I am still working on it.

rajeshkoshti said:
This means TWRP flashable is on its way.:good:
Click to expand...
Click to collapse
We already have that from beta. The latest beta was same as official release.

livyansh said:
help me out with an issue about retail or my software channel is retin should this version is good for me to install my build number is NPNS25.137-92-14 and I already got OTA update but my persists is not mine what should I do
Click to expand...
Click to collapse
After upgrading to oreo, download the Oreo flashable zip (Aroma) of SOAK1 and install only the firmware. And restore your efs after this step.
My phone is working perfectly with this, no network issues.

irfanalinawaz said:
Bro you need to avoid this to flash, right now there is not any solution for those who are not on their persist, you will end up with no signals. So wait, I am still working on it.
Click to expand...
Click to collapse
okay, bro, I am waiting just let me know whenever you find out any solution about VOLTE or no network issues

antojamez said:
After upgrading to oreo, download the Oreo flashable zip (Aroma) of SOAK1 and install only the firmware. And restore your efs after this step.
My phone is working perfectly with this, no network issues.
Click to expand...
Click to collapse
There are also many hidden issues after this method, wifi is getting slow while Bluetooth is active, if Bluetooth inactive thn also there are frequent wifi disconnection. Fingerprint also getting so slow while screen is off, I already tested it.

devvshukla said:
I got some errors while sending these two commands, device is working regardless of these errors.
Which are these command and whats they do? Also what issues I might be facing on future because of this?
Commands -
fastboot erase customize
fastboot erase clogo
Click to expand...
Click to collapse
Hey I also got that errors after few time my device got hard bricked.

riyan65 said:
Hey I also got that errors after few time my device got hard bricked.
Click to expand...
Click to collapse
These commands are not responsible for hard bricks, may be there are another reason for hard bricks.

Asking again...
Will this work for hard bricked users? I've been using twrp flashable nougat stock ROMs since last year! Can't get back to full stock so!

roydhritiman said:
Asking again...
Will this work for hard bricked users? I've been using twrp flashable nougat stock ROMs since last year! Can't get back to full stock so!
Click to expand...
Click to collapse
First post your fastboot getvar here, then tell me what is the condition of your persist, imei, volte etc. Also from fatboot menu take a pic and post them also, and describe how you recovered your hard bricked device, then we can explain you. Thanks.

irfanalinawaz said:
Bro you need to avoid this to flash, right now there is not any solution for those who are not on their persist, you will end up with no signals. So wait, I am still working on it.
Click to expand...
Click to collapse
but I got the OTA update on my phone to download and I did that but I am the little bit afraid to install it just because of VOLTE and IMEI