Database Users

Help!!!Bootloop

Hey guys! So,I flashed nougat firmware through twrp when I was in rr nougat and then my bootloader fried.. Then I ran blankflash and got my bootloader and my previous recovery back.. Now when I flash custom roms it gets stuck in a bootloop.... I've tried aospext and rr nougat both gets such in a bootloop.. Help me please!![emoji24] [emoji24]
Sent from my ONE E1003 using Tapatalk

gouthamgoumi said:
Hey guys! So,I flashed nougat firmware through twrp when I was in rr nougat and then my bootloader fried.. Then I ran blankflash and got my bootloader and my previous recovery back.. Now when I flash custom roms it gets stuck in a bootloop.... I've tried aospext and rr nougat both gets such in a bootloop.. Help me please!![emoji24] [emoji24]
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
Try flashing the stock firmware using fastboot images. After that try flashing custom recovery, followed by custom rom

Hello I got bootloop on my brand new G4 plus too.
I was trying to get root, its not my first time doing it but the first one with the G4. the thing is that I installed Recovery 3.0.3 r4 and SU 2.79 but now my G4 wont go into boot animation so maybe it was because I didnt installed 3.0.2.0 and SU athene.
I was looking for having the most recent versions but now I cannot use it. I already installed recovery 3.0.2 and super user intended for G4plus but it is the same, I can enter into fastboot and recovery but my G4 wont start.
What can I do?? I am from Mexico and I dont know how to get the original fimware so I am not able to install stock firmware using twrp.
I need your help please

hi,
For full stock flashable with twrp:
https://forum.xda-developers.com/moto-g4/development/fxz-athene-twrp-flashable-fastboots-t3562147
Read OP there! you need the right TWRP to flash them!

I already recovered my Moto G4 Plus (XT1641) and now Im using RR Rom
The steps for recovering your phone from bootloop
1.- Flash Stock Rom via Fastboot:
flashed XT1624-XT1643_ATHENE_7.0_NPJ25.93-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC files
Process:
Code:
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 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 reboot
2.-Customize the phone and restart into fastboot
3-Install TWRP 3.0.3r4 via fastboot
4-Install RR Rom and Gapps (Or any other Rom you like)
5-Customize the phone and restart into fastboot
6-Flash custom logo.bin to hide 5s Alert and thats all
I tried flashing new Rom trough recovery but it was not working at all, the only way I recovered my G4 Plus was by flashing the stock rom via fastboot so be aware of that.
Brought to you By Alex Guereque. Greetings.

Flashed wrong Rom

Hi, i have a Moto x Play XT1562, and i was trying to flash a stock rom and i accidentally flashed a wrong rom on it (moto g3 stock rom). I only realised it when i reached the sparsechunk 8 file. I then tried to flash the actual moto x play stock rom but am unable to do so since. Everytime i try to flash any of the files of the rom i get the following error.
(bootloader) preflash validation failed
What should i do?
Any assistance would be of great help.

Is bootloader locked ??

irfanjamal said:
Hi, i have a Moto x Play XT1562, and i was trying to flash a stock rom and i accidentally flashed a wrong rom on it (moto g3 stock rom). I only realised it when i reached the sparsechunk 8 file. I then tried to flash the actual moto x play stock rom but am unable to do so since. Everytime i try to flash any of the files of the rom i get the following error.
(bootloader) preflash validation failed
What should i do?
Any assistance would be of great help.
Click to expand...
Click to collapse
Download latest firmware with October security patch and try again. That is motorola policy, that is not possible downgrade system (You are probably flashing older firmware than you before).
Link: https://firmware.center/firmware/Motorola/Moto X Play/Stock/XT1562/
Flash latest build for your area.

bablu048 said:
Is bootloader locked ??
Click to expand...
Click to collapse
No, the bootloader is unlocked.

irfanjamal said:
No, the bootloader is unlocked.
Click to expand...
Click to collapse
Try flashing a rom through twrp.

Use fastboot to flash the stock rom.Don't use RSD lite.Download Minimal ADB and Fastboot,install it and then extract the firmware to the installed folder and enter the following commands.
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 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 reboot

I have the same problem, I Flash by mistake one Brazilian ROM instead of the one for USA/Mexico.. Now Im not able to flash the correct one using fastboot but I was able to Install TWRP and flash custom ROMS, my question is if I will be able to install Pure Stock again ?

PonchosoftX said:
I have the same problem, I Flash by mistake one Brazilian ROM instead of the one for USA/Mexico.. Now Im not able to flash the correct one using fastboot but I was able to Install TWRP and flash custom ROMS, my question is if I will be able to install Pure Stock again ?
Click to expand...
Click to collapse
Use rsdlite to flash stock rom.

Revert to stock after flashing 7.1.2 custom firmware XT1643

Hello folks. I need help getting back to stock firmware on my Moto G4 Plus Indian Variant (xt1643). I have flashed resurrection remix that's on android 7.1.2. I tried to flash the stock firmware (november 1, 2016 security build) through fastboot. As soon as I entered the command to flash the stock boot image, I get a pre-flash validation error message and had to abort the flashing procedure immediately. I was on the latest march build before flashing resurrection remix. I don't know how to go about with it and need to get back to stock firmware asap. Any help is always appreciated.
Thanks in advance,
Krishna16

I am running resurrection remix (7.1.2) on my moto g4 plus currently and have an unlocked bootloader and twrp recovery installed.

Krishna16 said:
I am running resurrection remix (7.1.2) on my moto g4 plus currently and have an unlocked bootloader and twrp recovery installed.
Click to expand...
Click to collapse
If you previously were on the March 2017 security build (should be NPJS25.93-14.4), you may wish to download this stock ROM, which is the latest build that we have available (NPJS25.93-14.4, March 2017 security patch). https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 This stock ROM thread also has scripts to help you flash, though you may wish to edit them to match the commands below. You may also verify if you're on the latest firmware previously by booting to your bootloader - I recall the March 2017 bootloader version is B1.05.
Regardless, you're likely getting that pre-flash validation error due to an attempt of flashing an older bootloader and/or attempting to relock your bootloader with an older firmware. You can only relock your bootloader with firmware of the same build you had previously or newer.
I'd suggest using the latest stock firmware, and provided you were on the March 2017 update previously, omit flashing the GPT and bootloader partitions (whether you're using the latest stock build or your November build - just keep those partitions as they are):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
You may also wish to omit the locking commands if you don't wish to lock your bootloader. Your commands should look therefore like:
Code:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
If you wish to relock your bootloader, use the commands as follows (if the commands complain of needing a signed image, try booting into your flashed stock system, toggle OEM Unlock in Developer Settings and re-flash the stock ROM with the re-locking commands)
Code:
fastboot oem lock begin
fastboot oem lock begin
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem lock
fastboot reboot
I've used the 1st list of flashing commands - the non-locking version - to revert from RR 5.8.3 27/05/2017 to the stock NPJS25.93-14.4 ROM on my XT1642 without issue (apart from the unlocked bootloader warning). Be aware that re-flashing a stock ROM will wipe your device clean (including internal storage) and may result in your SD card being non-functional until wiped. Back up your important data accordingly (you may wish to use Titanium Backup to preserve your app data), and transfer backups off your device until you have flashed.
EDIT - tweaked a couple of sentences for clarity.

echo92 said:
If you previously were on the March 2017 security build (should be NPJS25.93-14.4), you may wish to download this stock ROM, which is the latest build that we have available (NPJS25.93-14.4, March 2017 security patch). https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 This stock ROM thread also has scripts to help you flash, though you may wish to edit them to match the commands below. You may also verify if you're on the latest firmware previously by booting to your bootloader - I recall the March 2017 bootloader version is B1.05.
Regardless, you're likely getting that pre-flash validation error due to an attempt of flashing an older bootloader and/or attempting to relock your bootloader with an older firmware. You can only relock your bootloader with firmware of the same build you had previously or newer.
I'd suggest using the latest stock firmware, and provided you were on the March 2017 update previously, omit flashing the GPT and bootloader partitions (whether you're using the latest stock build or your November build - just keep those partitions as they are):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
You may also wish to omit the locking commands if you don't wish to lock your bootloader. Your commands should look therefore like:
Code:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
If you wish to relock your bootloader, use the commands as follows (if the commands complain of needing a signed image, try booting into your flashed stock system, toggle OEM Unlock in Developer Settings and re-flash the stock ROM with the re-locking commands)
Code:
fastboot oem lock begin
fastboot oem lock begin
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem lock
fastboot reboot
I've used the 1st list of flashing commands - the non-locking version - to revert from RR 5.8.3 27/05/2017 to the stock NPJS25.93-14.4 ROM on my XT1642 without issue (apart from the unlocked bootloader warning). Be aware that re-flashing a stock ROM will wipe your device clean (including internal storage) and may result in your SD card being non-functional until wiped. Back up your important data accordingly (you may wish to use Titanium Backup to preserve your app data), and transfer backups off your device until you have flashed.
EDIT - tweaked a couple of sentences for clarity.
Click to expand...
Click to collapse
I am out of words to thank you??. Thanks a lot for your efforts and time echo92. I still have a perpetual problem and that is my speaker volume is too low while playing YouTube videos. Is there a way to fix that??

now should i update from marshmello to nougat???
after reverting back to stock?

sarang25 said:
now should i update from marshmello to nougat???
after reverting back to stock?
Click to expand...
Click to collapse
No. You must flash nougat with latest security patch

sarang25 said:
now should i update from marshmello to nougat???
after reverting back to stock?
Click to expand...
Click to collapse
If you previously had stock Nougat (doesn't matter about custom ROM Nougat) before reverting back to Marshmallow stock, I too would recommend you flash the latest stock Nougat via fastboot. For India, Brazil, EU and UK devices, that stock ROM is the NPJS25.93-14-18 firmware ( https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 )
We've seen previously that attempting to use OTA updates on a device with downgraded stock firmware (again, does not matter what custom ROM you had, what matters is what stock ROM builds you had flashed previously and now) can hard brick your device. Thus, if you want to update, using OTA updates can be potentially risky. Safest way is to use fastboot flashes to update.

Cant flash android 7.x.x based custom roms in TWRP

Hello guys, i have a problem with flashing custom roms.
Device unlocked, twrp tryed : 3.0.2 and newest
dev info : clark xt1572
Flashed androids 6..x.x based roms and works great.
Problems : bootloops or kernel usunes (cant boot) whats is problem ? kernel ? handybad kernel cant flash.
What is problem ?
Sry for bad english.

GeloXD said:
Hello guys, i have a problem with flashing custom roms.
Device unlocked, twrp tryed : 3.0.2 and newest
dev info : clark xt1572
Flashed androids 6..x.x based roms and works great.
Problems : bootloops or kernel usunes (cant boot) whats is problem ? kernel ? handybad kernel cant flash.
What is problem ?
Sry for bad english.
Click to expand...
Click to collapse
What was your last stock rom? 5.1, 6.x, 7.0?

I am suspecting a radio version issue here... try flashing the latest factory image via fastboot for your variant and boot fully. Do not use images from Moto, get the latest ones from https://firmware.center/firmware/Motorola/
After that, only use TWRP 3.1.1-0, then wipe system, data, caches, then flash ROM only and boot, if successful, flash Gapps and/or SuperSU (if recommended by dev of ROM) and test boot again.
If the very first boot fails, I would want to see the output of a "fastboot getvar all" and the recovery logs of the ROM flashes after you have tried the factory image flash.

acejavelin said:
I am suspecting a radio version issue here... try flashing the latest factory image via fastboot for your variant and boot fully. Do not use images from Moto, get the latest ones from https://firmware.center/firmware/Motorola/
After that, only use TWRP 3.1.1-0, then wipe system, data, caches, then flash ROM only and boot, if successful, flash Gapps and/or SuperSU (if recommended by dev of ROM) and test boot again.
If the very first boot fails, I would want to see the output of a "fastboot getvar all" and the recovery logs of the ROM flashes after you have tried the factory image flash.
Click to expand...
Click to collapse
Ok i will try it thanks. How i can flash image via fastboot ? adb sideload ?
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
OK this post will be helpfull
dzidexx said:
What was your last stock rom? 5.1, 6.x, 7.0?
Click to expand...
Click to collapse
Android 7.0 updated from stock recovery (for Germany region)

There isn't flashable working custom rom at stock nougat.
(Another partition table or drivers)
You have to downgrade or wait month-two.
Downgrade isn't safe. @GeloXD
Link in your post isn't good too.
---------- Post added at 05:29 PM ---------- Previous post was at 05:23 PM ----------
This one is better:
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110

dzidexx said:
There isn't flashable working custom rom at stock nougat.
(Another partition table or drivers)
You have to downgrade or wait month-two.
Downgrade isn't safe. @GeloXD
Link in your post isn't good too.
Click to expand...
Click to collapse
This.... We don't have ROMs compatible with the new Nougat radio and partition table. Suggest staying stock for now.

dzidexx said:
There isn't flashable working custom rom at stock nougat.
(Another partition table or drivers)
You have to downgrade or wait month-two.
Downgrade isn't safe. @GeloXD
Link in your post isn't good too.
---------- Post added at 05:29 PM ---------- Previous post was at 05:23 PM ----------
This one is better:
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Click to expand...
Click to collapse
acejavelin said:
This.... We don't have ROMs compatible with the new Nougat radio and partition table. Suggest staying stock for now.
Click to expand...
Click to collapse
Now with downgrade solution have 7.1.2 custom android. System partition cant flash but other bot radio work good now i have what i need but still android pay and root / bootloader unlocked doesnt work ;/

GeloXD said:
Now with downgrade solution have 7.1.2 custom android. System partition cant flash but other bot radio work good now i have what i need but still android pay and root / bootloader unlocked doesnt work ;/
Click to expand...
Click to collapse
What custom do you have? Root with supersu?
Unroot it and use magisk v13(magisk hide &/or core only u need).

Work : fastboot oem lock begin
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Doesnt work :
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
So i flash mixed 6 modem radios and stay in system from android 7
I still have backup android 7 in twrp, but now 7.1.2 with magisk and root work better.

dzidexx said:
What custom do you have? Root with supersu?
Unroot it and use magisk v13(magisk hide &/or core only u need).
Click to expand...
Click to collapse
I dnt know about magisk v13 i meaned 12 is the newest version.
I flashed tesla nougat 7.1.2 rom
now version : tesla clars 7.1.2 rc v4.1 official 20170509-1634 with open gapps nano variant.

GeloXD said:
Work : fastboot oem lock begin
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Doesnt work :
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
Click to expand...
Click to collapse
For 6.0.1 xt1572 should be more:
...
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
...
fastboot flash bluetooth BTFM.bin
...

I'm having the same problem. I had updated to stock 7.0 and now I just can't update to any other 7.x roms, but 6.x roms do work

[Getting Error while installing OTA]

I received an update Oreo, when I tried to install it failed and displayed a message "Error" and restarted. Help me to update my mobile to latest version. I cleared cache partition, still no luck.
I have unlocked bootloader and on latest stock ROM.
Screenshot attached !!!

ksamm97 said:
I received an update Oreo, when I tried to install it failed and displayed a message "Error" and restarted. Help me to update my mobile to latest version. I cleared cache partition, still no luck.
I have unlocked bootloader and on latest stock ROM.
Screenshot attached !!!
Click to expand...
Click to collapse
Flash the complete stock rom using fastboot and lock the bootloader and then update the device through OTA.

ksamm97 said:
I received an update Oreo, when I tried to install it failed and displayed a message "Error" and restarted. Help me to update my mobile to latest version. I cleared cache partition, still no luck.
I have unlocked bootloader and on latest stock ROM.
Screenshot attached !!!
Click to expand...
Click to collapse
Facing the exact same issue here.I think the latest stock oreo needs locked bootloader to flash

No need to relock the bootloader, but you must revert back to unmodified stock firmware on your device before updating. Without seeing what error it is, it's difficult to say. A locked bootloader strictly enforces having the unmodified stock furnace, which is why an OTA update is more likely to work.
Try this:
1) download the NPJS25.93-14-18 firmware from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Only use this if you have not updated to Oreo and you are still on NPJS25.93-14-18.
2)unzip the fastboot ROM, delete any old stock ROMs from your ADB folder and copy the stock ROM over.
3) assuming you had NPJS25.93-14-18 already on your device, flash the firmware with the following instructions - no need for the GPT/bootloader. Ensure you have your data backed up, as you may have to factory reset if you encounter instability.
Code:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
That should get your device into an OTA friendly state without erasing your data. If that doesn't work, I suggest waiting for the Oreo fastboot ROM.

I've custom Oreo installed on my phone. Which firmware package should I install?
echo92 said:
No need to relock the bootloader, but you must revert back to unmodified stock firmware on your device before updating. Without seeing what error it is, it's difficult to say. A locked bootloader strictly enforces having the unmodified stock furnace, which is why an OTA update is more likely to work.
Try this:
1) download the NPJS25.93-14-18 firmware from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Only use this if you have not updated to Oreo and you are still on NPJS25.93-14-18.
2)unzip the fastboot ROM, delete any old stock ROMs from your ADB folder and copy the stock ROM over.
3) assuming you had NPJS25.93-14-18 already on your device, flash the firmware with the following instructions - no need for the GPT/bootloader. Ensure you have your data backed up, as you may have to factory reset if you encounter instability.
Code:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
That should get your device into an OTA friendly state without erasing your data. If that doesn't work, I suggest waiting for the Oreo fastboot ROM.
Click to expand...
Click to collapse

tobey_onk said:
I've custom Oreo installed on my phone. Which firmware package should I install?
Click to expand...
Click to collapse
At the moment, we only have the stock Nougat firmware to revert to - Oreo firmware doesn't seem to be out yet. However, flashing stock Nougat over custom Oreo may appear to come with some risk of losing IMEI, so be careful. You could try the TWRP flashables, be aware the stock ROM is only 32 bit.