Database Users

Stock ROM Nougat 7.0 For Moto G4 Plus XT1643

Hello guyz do you have or post the latest version stock rom for Moto G4 Plus XT1643 ?
Waiting eagerly for your heads up
edit :
head to this link for flashing procedure and lock/ re-lock the bootloader on moto g4 plus :
https://forum.xda-developers.com/showpost.php?p=70383231&postcount=15

http://forum.xda-developers.com/mot...d-ota-nougat-ota-moto-g4-plus-t3517059/page37
Sent from my Moto G (4) using Tapatalk
Sent from my Moto G (4) using Tapatalk

zazzy24 said:
http://forum.xda-developers.com/mot...d-ota-nougat-ota-moto-g4-plus-t3517059/page37
Sent from my Moto G (4) using Tapatalk
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
this is captured ota I'm asking for updated stock rom for flashing.. thanks for your head up (Y)

snd team said:
this is captured ota I'm asking for updated stock rom for flashing.. thanks for your head up (Y)
Click to expand...
Click to collapse
It isn't released. That's already discussed.

snd team said:
Hello guyz do you have or post the latest version stock rom for Moto G4 Plus XT1643 ?
Waiting eagerly for your heads up
Click to expand...
Click to collapse
Find it here. It's flashable ROM zip:
removed link.. mod edit: not flashable..

removed link.. mod edit: not flashable..
Anyone tried this ? is it compatible with Indian (XT1643) version?

Arivendu said:
Find it here. It's flashable ROM zip:
removed link.. mod edit: not flashable..]
Click to expand...
Click to collapse
Don't misguide users. You shouldn't post if you are not sure about something.
First, its not a zip file. Its a rar file.
Second, its not flashable. You need to flash it using fastboot.

Arivendu said:
Find it here. It's flashable ROM zip:
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Click to expand...
Click to collapse
Thanks buddy you're the best
praveenbda said:
Anyone tried this ? is it compatible with Indian (XT1643) version?
Click to expand...
Click to collapse
yes sure see the topic title and also tested on XT1643

also I'm able to re-lock the bootloader

TO relock the bootloader and Flashing
First of all download the stock firmware rar file ( thanks to Arivendu for heads up) - multi platform support (windows linux etc)
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Mirrors :
https://files.fm/u/hfapbktm
https://drive.google.com/open?id=0B-ReAPgYg5ISNFpaeV92V2hRaWc
https://mega.nz/#!0oV33RhI!5U51UqC4v16qTSN5ur6FAV7EOpLTXL0Pfm12n71GGwc
***** this firmware also worked for other moto g4 variants *****
extract it
open folder name : athene_oem_user_7.0_NPJ25.93-11_12_release
under the folder their is a folder name "Windows"
copy files from "windows" folder to root folder
and use below command to re-lock bootloader and flash your phone with latest version of stock 7.0 (tested on xt1643)
SHIFT + Mouse right click >>> open command window here
and enter this commands one by one
Code:
fastboot oem lock begin
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 dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.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
fastboot oem lock
Or download the oem unlock and flash mobile.zip (833.6 KB) from atatchment and place the files in root dir where you extracted the firmware
and run the OEM lock.bat file for automation
if the device not reboot after firmware flash run this command at the end :
Code:
fastboot reboot

I can confirm that rar contains factory images and it's working fine on my Moto G4 Plus XT1644 64GB/4Gb RAM (RETUS). Finally, running Nougat on my device.

snd team said:
no i don't have any link and i confirm it is original moto firmware
Click to expand...
Click to collapse
Thanks, I had a browse and it looks like it's from http://lenovo-forums.ru/topic/22076-moto-g⁴-plus-npj2593-11/
Although the website says they are not an official Lenovo forum, if it's working for people, that's great. It'd be nice if we get a Nougat ROM we can flash in stock recovery without adb fastboot

Massive cleaning on the thread.. Please be warry of whatever type of file you are flashing on your devices.. A little mistake will brick your devices. I hope no one will post again a non-flashable zip.. and pls. put into considerations the knowledge of others. Not everyone knows what a RAR file or a ZIP file is... Please be cautious.. AND LASTLY .. NO FLAMING ..... NEVER ALLOWED HERE

reyscott said:
Massive cleaning on the thread.. Please be warry of whatever type of file you are flashing on your devices.. A little mistake will brick your devices. I hope no one will post again a non-flashable zip.. and pls. put into considerations the knowledge of others. Not everyone knows what a RAR file or a ZIP file is... Please be cautious.. AND LASTLY .. NO FLAMING ..... NEVER ALLOWED HERE
Click to expand...
Click to collapse
thanks for cleaning cheers

Fastboot flashing steps
snd team said:
Hello guyz do you have or post the latest version stock rom for Moto G4 Plus XT1643 ?
Waiting eagerly for your heads up
edit :
head to this link for flashing procedure and lock/ re-lock the bootloader on moto g4 plus :
https://forum.xda-developers.com/showpost.php?p=70383231&postcount=15
Click to expand...
Click to collapse
Hi guys
I have an XT1643 and I have downloaded the firmware mentioned below. It was a 7z compressed file with password as "lenovo-forums.ru"
"athene_oem_user_7.0_NPJ25.93-14_16_release.7z"
I couldn't find the commands for flashing this through bootloader. If someone may know a solution, could you please post the command or guide me?
thanks

shailuo said:
Hi guys
I have an XT1643 and I have downloaded the firmware mentioned below. It was a 7z compressed file with password as "lenovo-forums.ru"
"athene_oem_user_7.0_NPJ25.93-14_16_release.7z"
I couldn't find the commands for flashing this through bootloader. If someone may know a solution, could you please post the command or guide me?
thanks
Click to expand...
Click to collapse
The fastboot commands are the same as in the post you linked in your quote. Alternatively, you may refer to the instructions listed here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
One way to flash your stock ROM is (just expanding on the instructions mentioned previously):
1) Download the Motorola drivers and minimal adb tool from the links here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 Install the drivers and tool as directed by the installers.
2)Extract the 7z ROM with your preferred decompression tool (that can handle .7z file types). The resulting folder should be about 2 GB. Copy the files (from the extracted stock ROM) to your adb folder (may be on your C:\ drive, you may have to give permission to copy).
3)Connect your device to your computer. Enable USB debugging.
3a)Once recognised by your computer, open the adb terminal and type/execute 'adb devices' without the quotes. Your device should return back its serial number if properly detected.
4)Back up all necessary data and files to your computer. Flashing a fastboot ROM may wipe your data from your device.
5)Reboot your device to bootloader mode.
5a) Re-confirm you can still detect your device in fastboot mode by executing 'fastboot devices'. Should get your serial number again.
6)Run the commands as directed in the fastboot ROM thread in the adb terminal.
6a)These commands are for relocking your bootloader:
Code:
fastboot oem lock begin
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 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
6b) If you don't wish to type all this, you may wish to download and run the scripts from this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Ensure you copy the scripts to the adb folder, where your ROM files and the adb terminal should be. There should be 2 scripts there, one for if you want to relock your bootloader, one if you don't wish to.

getting error whilw flashing
snd team said:
First of all download the stock firmware rar file ( thanks to Arivendu for heads up) - multi platform support (windows linux etc)
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Mirrors :
https://files.fm/u/hfapbktm
https://drive.google.com/open?id=0B-ReAPgYg5ISNFpaeV92V2hRaWc
https://mega.nz/#!0oV33RhI!5U51UqC4v16qTSN5ur6FAV7EOpLTXL0Pfm12n71GGwc
***** this firmware also worked for other moto g4 variants *****
extract it
open folder name : athene_oem_user_7.0_NPJ25.93-11_12_release
under the folder their is a folder name "Windows"
copy files from "windows" folder to root folder
and use below command to re-lock bootloader and flash your phone with latest version of stock 7.0 (tested on xt1643)
SHIFT + Mouse right click >>> open command window here
and enter this commands one by one
Code:
fastboot oem lock begin
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 dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.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
fastboot oem lock
Or download the oem unlock and flash mobile.zip (833.6 KB) from atatchment and place the files in root dir where you extracted the firmware
and run the OEM lock.bat file for automation
if the device not reboot after firmware flash run this command at the end :
Code:
fastboot reboot
Click to expand...
Click to collapse
log:
Fastboot device is ready
There are 1 device(s) connected: ZY2237XWMH
Trying to flash device ZY2237XWMH
Starting flashing device ZY2237XWMH...
Flashing partition table ...
Executing ".\Windows\fastboot.exe -s ZY2237XWMH flash partition gpt.bin"
target max-download-size: 512MB
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.048s
All devices are flashed
Press any key to continue .
Iam getting same error even while flshing without bootloader and GPT. (Iam trying downgrade from 7.1.2 to stock 7.0)
please help me with this

Udaya.kr said:
log:
Fastboot device is ready
There are 1 device(s) connected: ZY2237XWMH
Trying to flash device ZY2237XWMH
Starting flashing device ZY2237XWMH...
Flashing partition table ...
Executing ".\Windows\fastboot.exe -s ZY2237XWMH flash partition gpt.bin"
target max-download-size: 512MB
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.048s
All devices are flashed
Press any key to continue .
please help me with this
Click to expand...
Click to collapse
What firmware did you have previously on your device, and are you trying to relock your bootloader? The firmware linked here is quite old (November 2016 security patch), and the warning you're getting suggests you have newer firmware on your device.
If you're on the June update, do not flash this firmware.

echo92 said:
What firmware did you have previously on your device, and are you trying to relock your bootloader? The firmware linked here is quite old (November 2016 security patch), and the warning you're getting suggests you have newer firmware on your device.
If you're on the June update, do not flash this firmware.
Click to expand...
Click to collapse
Successfully flashed june firmware and re locked bootloader. thank you for your help.

Udaya.kr said:
Successfully flashed june firmware and re locked bootloader. thank you for your help.
Click to expand...
Click to collapse
Can you please share the link for june fastboot rom for XT1643?

Yet Another Bootloop Thread

Hello,
So I decided to unlock and root my Pure today. Originally I was going to flash Lineage, but I later decided not to. Anyway, I was following the instructions here.
So I unlocked and installed TWRP succesfully. Then I decided to root. And that's where I screwed up.
Following these instructions, I now have a phone that won't boot past the "M" logo. Apparently my mistake was not using the current SU version.
I have been Googling for an hour now, but almost every solution I've come across has involved plugging the phone into the computer. My issue is that my computer isn't recognizing the phone when I plug it in, so my knowledge of how to fix this is limited (and my expertise in this topic was minimal to begin with...). I can get to recovery mode, and have tried a factory reset. No dice. I also put the latest official factory image from Motorola on the SD card, but when I went to install it, it wouldn't show up.
As you can tell I am quite stuck here. I haven't tried to root a phone since my Incredible back in the day. Any help would be greatly appreciated.
Thanks!

Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.

jason2678 said:
Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.
Click to expand...
Click to collapse
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?

bootloopohgod said:
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?
Click to expand...
Click to collapse
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps

Sagar_1401 said:
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps
Click to expand...
Click to collapse
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.

bootloopohgod said:
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.
Click to expand...
Click to collapse
ignore that partition error
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 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 oem lock
fastboot reboot
make sure
while flashing NON-HLOS.bin you might get error
dont worry
when you reach that step do type it again when you see that error and it'll successful flash the NON-HLOS.bin which is your main step for your modem
im sure this will 100% work
edit: all the files have different no of system system.img_sparsechunk
if you are flashin sept patch it should have 8 i assume but if you just type system system.img_sparsechunk.9 it'll say file not found u won't encounter any error by that

What's the latest U.S build version of Moto g5 plus? (OTA HELP)

Hello! https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
I used that forum to re-lock bootloader and flash stock rom! WHOOHOO, but fastboot is still saying my software status is modified, and I can't tell if I'm receiving OTA updates? How do I check that? I went into settings > About phone > software updates > YOUR SOFTware is up to date.
So I'm wondering if since my fastboot says my firmware is modified, that i'm not receiving OTA. Can someone please confirm they're running un-touched moto g5 plus software, and confirm what latest buildnumber is? U.S. phones only please.
I really need help, I need to receive OTA updates, and I'd assume since it says my "software is up to date" that it is, but I want someone to confirm..
BUILD NUMBER NPNS25.137-33-11

if anyone knows anything about this PLEASE post I'm desparate.

OK flashed rom from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ from december
that should be the latest one,
NPN25.137-92
security patch nov 1 2017
HOWEVER, even though i may be on the latest rom it's still disturbing that i don't receive ota updates. any way to get around this?

beatlesfan5858 said:
OK flashed rom from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ from december
that should be the latest one,
NPN25.137-92
security patch nov 1 2017
HOWEVER, even though i may be on the latest rom it's still disturbing that i don't receive ota updates. any way to get around this?
Click to expand...
Click to collapse
I think once you leave stock, you won't receive OTA's again, even if you re-flash and lock bootloader. You will have to download the updated ROM and manually install it.

lol... You are a lot newer than mine (which I thought was current) and I have NPN25-137-83 (August 1, 2017) and I am completely stock with locked bootloader, never touched it. Are you sure you flashed the right software channel image for your device, retus?
There has only been a couple OTA updates for this device ever, your not missing anything. And BTW, your "modified" status is normal until you get your first OTA, it should then become official. Note that Bootloader Status will ALWAYS be a 2 and will never go back to 0, it isn't possible for anyone but Moto to do that.

beatlesfan5858 said:
Hello! https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
I used that forum to re-lock bootloader and flash stock rom! WHOOHOO, but fastboot is still saying my software status is modified, and I can't tell if I'm receiving OTA updates? How do I check that? I went into settings > About phone > software updates > YOUR SOFTware is up to date.
So I'm wondering if since my fastboot says my firmware is modified, that i'm not receiving OTA. Can someone please confirm they're running un-touched moto g5 plus software, and confirm what latest buildnumber is? U.S. phones only please.
I really need help, I need to receive OTA updates, and I'd assume since it says my "software is up to date" that it is, but I want someone to confirm..
BUILD NUMBER NPNS25.137-33-11
Click to expand...
Click to collapse
I flashed the stock ROM for RETUS (US variant of the G5 Plus), compared it with a with a friend who is on RETUS and on the latest version, and found out that the latest version is build number NPN25.137-83 with the August 1st security patch. When I flashed the stock ROM, my bootloader said I was on official software. If you want me to help you out, I can.

reCoded said:
I flashed the stock ROM for RETUS (US variant of the G5 Plus), compared it with a with a friend who is on RETUS and on the latest version, and found out that the latest version is build number NPN25.137-83 with the August 1st security patch. When I flashed the stock ROM, my bootloader said I was on official software. If you want me to help you out, I can.
Click to expand...
Click to collapse
OK where can I find the stock ROM NPN25.137-83? So the steps would be....
1. Download stock rom
2. oem lock device
3. Flash stock rom/ erase everything?
EDIT: to clarify where I'm at right now, I re-unlocked bd and rooted with Magisk, but have root access gives me nothing but trouble. I have a broken camera now since I've rooted, the app doesn't want to open. No doubt about it, I want to go back to the way everything was normally, receiving OTA updates and have official software. I never should've messed with anything.

OK I downloaded 137-83 from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL
Then tried oem locking and reflashing everything with this link https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
But it didn't want to oem lock, because it says it requires a "signed boot img"
So what should I do from here?

beatlesfan5858 said:
OK I downloaded 137-83 from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL
Then tried oem locking and reflashing everything with this link https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
But it didn't want to oem lock, because it says it requires a "signed boot img"
So what should I do from here?
Click to expand...
Click to collapse
You'd likely have to wait for the next US retail firmware to be leaked to be able to lock your device.
Given that you've flashed the NPN25.137-92 firmware, you've likely still got the bootloader from that firmware, and so using an older NPN25.137-83 firmware won't permit you to re-lock your bootloader. You cannot downgrade bootloaders (and probably reports a security downgrade error if you try).
Also, now that you likely have a different system to your bootloader, I would caution against taking OTA updates until you've flashed the newer US firmware. I don't know if bootloaders for US firmware are different or the same as other region's firmware, and hopefully someone knows (or can compare firmwares), but mixing builds with different patch levels or regions could lead to a hard brick if taking OTA updates. Be careful.

Thanks I don't want to brick my device. So what should I flash right now? I want to delete everything (root) and go back to stock rom so my camera works! See above for what rom I'm on, it's December security patch. Should I just reflash that one? I won't try to downgrade now. How do I wipe twrp and restore stock recovery and stock everything? Show me the way Jedi master!

Please someone tell me! I really need my phone to be functional.

beatlesfan5858 said:
Thanks I don't want to brick my device. So what should I flash right now? I want to delete everything (root) and go back to stock rom so my camera works! See above for what rom I'm on, it's December security patch. Should I just reflash that one? I won't try to downgrade now. How do I wipe twrp and restore stock recovery and stock everything? Show me the way Jedi master!
Click to expand...
Click to collapse
You're on the December patch? What's your software channel? If it's not RETUS, you've screwed stuff up. The December patch isn't available to US G5 Pluses.

reCoded said:
You're on the December patch? What's your software channel? If it's not RETUS, you've screwed stuff up. The December patch isn't available to US G5 Pluses.
Click to expand...
Click to collapse
my bad! software channel retus android version 7.0 android security patch level nov 1 2017 baseband version m8953_37.46.07.47R Potter NA_Cust kernel version [email protected] #1 mon nov 20 09:32:29 CST 2017 build number NPN25.137-92 hope this helps

beatlesfan5858 said:
my bad! software channel retus android version 7.0 android security patch level nov 1 2017 baseband version m8953_37.46.07.47R Potter NA_Cust kernel version [email protected] #1 mon nov 20 09:32:29 CST 2017 build number NPN25.137-92 hope this helps
Click to expand...
Click to collapse
When your device starts up, does it say "ID: bad key" by chance?

reCoded said:
When your device starts up, does it say "ID: bad key" by chance?
Click to expand...
Click to collapse
edit it says ID:n/a just checked booting it up, that's on the unlocked bootloader screen by the way

beatlesfan5858 said:
edit it says ID:n/a just checked booting it up, that's on the unlocked bootloader screen by the way
Click to expand...
Click to collapse
Alright, you seem to have a similar situation to what I had. I cannot confirm that this will work but if you're willing, you can try it. Doing this fixed my device. My device software status is official and I pass SafetyNet. Again, I'm not sure if this will brick your device or not and I'm not responsible for anything that goes wrong.
First download the NPN25.137-83 firmware here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Now reboot your device to bootloader and type these commands ONE AT A TIME.
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
Now reboot and set up your device. After doing that, restart to bootloader and type these commands again, ONE AT A TIME.
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 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
Hopefully, you should be back to stock and able to receive software updates.

reCoded said:
Alright, you seem to have a similar situation to what I had. I cannot confirm that this will work but if you're willing, you can try it. Doing this fixed my device. My device software status is official and I pass SafetyNet. Again, I'm not sure if this will brick your device or not and I'm not responsible for anything that goes wrong.
First download the NPN25.137-83 firmware here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Now reboot your device to bootloader and type these commands ONE AT A TIME.
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
Now reboot and set up your device. After doing that, restart to bootloader and type these commands again, ONE AT A TIME.
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 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
Hopefully, you should be back to stock and able to receive software updates.
Click to expand...
Click to collapse
Alright i'm going to do everything exactly like you said. I'll be about 15 minutes, will report back. stick around please, and thanks so much for all your help.

Hey, isn't this what previous user warned about? I was on a higher up version of the software so he said I couldn't downgrade?
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (517383 KB)...
OKAY [ 17.424s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.531s
that's when i typed in flash oem and flash sparseimg 0, it's giving me those validation errors.

beatlesfan5858 said:
Hey, isn't this what previous user warned about? I was on a higher up version of the software so he said I couldn't downgrade?
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (517383 KB)...
OKAY [ 17.424s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.531s
that's when i typed in flash oem and flash sparseimg 0, it's giving me those validation errors.
Click to expand...
Click to collapse
It seems so. I was afraid this might of happened. That means that you'll have to wait for RETUS to get the November update or higher for you to relock. Did the commands relock your bootloader or is it still unlocked?

reCoded said:
It seems so. I was afraid this might of happened. That means that you'll have to wait for RETUS to get the November update or higher for you to relock. Did the commands relock your bootloader or is it still unlocked?
Click to expand...
Click to collapse
It wouldn't re-lock because it said the boot img wasn't signed. I know if I try with the current potter version I have, that it will relock, but I was afraid I wouldn't receive OTA updates if I did that.
edit: to clarify, I had downloaded 137-92 from the above link, and managed to relock it before on that version. However I was paranoid about ota updates so i re-unlocked, and re-rooted, which turned out to be a mistake. I'll try re-locking and flashing 137-92, which is the nov 1 2017 security update btw.

Official Oreo 8.1.0 OPP28.85-16 Fastboot Firmware (and how to relock BL with it).

Someone managed to get the RSD Secure link for the FASTBOOT files of the final Oreo 8.1 release for RETAIL Moto G5/cedric.
With these files you'll be able to update to official oreo, relock your bootloader or simply go back to stock.
Using the guide I'll write below you'll be able to flash it from Linux, Windows and MacOS.
The new firmware is named OPP28.85-16 and Blur Version listed within the firmware package is:
Code:
Blur_Version.28.41.15.cedric.retail.en.US
whereas the OTA file for the corresponding Firmware lists it as:
Code:
Blur_Version.25.361.10.cedric.retail.en.US
I dont know which is "correct", but anyways, this should not alter your results when flashing this with fastboot.
DOWNLOAD
Gdrive: https://drive.google.com/file/d/1gNB7vNM8xH5ueTPKh5Qwev87gJpSpyyK/view?usp=sharing
RSD Secure: https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
FLASHING IT
If your seeing this post long after Setember 2018 it may be the case you have updated your firmware past this one and got a different bootloader version, in that case, make sure to check you bootloader version is BELOW B8.31. Flashing bootloader of equal or minor version will hardbrick your device
UPDATING FROM PREVIOUS ANDROID VERSION
1. If you're on Windows/Mac, download motorola USB drivers here. (You shouldn't need these on Linux)
2. Download Android Platform Tools (ADB & Fastboot ) for Windows/Mac/ Linux here (if you're on Linux, get these from your distro's repo instead).
3. Extract the platform tools somewhere
4. Extract the firmware's ZIP too (I recommend extracting it to the same directory as platform tools, this will make your life easier).
5.Open a command prompt/terminal where you extracted platform tools (To do that on windows, Hold SHIFT + right Click some blank area within platform-tools directory, then click "Open Command Prompt Here".
6. Reboot into fastboot (power off and connect USB while holding Vol Down) and Execute the following commands
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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
7. Reboot your phone by typing fastboot reboot or by selecting the "START" option in phone's screen and then pressing the power button
PS: Do not execute commands related to erasing the modemst1 and modemst2 partitions. This has been related to people losing their IMEI's.
RELOCKING YOUR BOOTLOADER
edit
Seems like my instructions on how to relock didn't work, but I want to thank Andrej_SK, who managed to do it and posted instructions on how to do it. Just remember that you should Not flash bootloader if you're already on B8.31 or past it. Flashing gpt.bin can also hardbrick your phone and there have been reports of it happening here on XDA and on telegram. I personally didn't flash it when moving from NPPS25.137-93-2-5 and had no problem at all, and I think you shouldn't too, unless you know you absolutely need it (which I think is unlikely, since the partition scheme looks the same on both nougat and Oreo)
Andrej_SK said:
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
Try this (on your own risk only): input "fastboot oem lock" twice (first time for starting the whole process of locking, second time for confirmation). Then, execute commands below, one by one
Code:
fastboot flash oem oem.img
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
Then, input "fastboot oem lock" for the last time. Your phone should immediately reboot, as mine did. If there will be problem with booting into OS, just reflash the whole system with commands below:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img (do not flash this if you're on B8.31 or further, so as not to hardbrick the device)
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
Click to expand...
Click to collapse
DOWNGRADING FROM A FIRMWARE NEWER THAN OPP28.85-16
1. Follow steps one 1 up to five described in the first section UPDATING FROM PREVIOUS ANDROID VERSION
2. Omit these lines from step 6:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Notice that omitting these two lines is VERY IMPORTANT if you're downgrading, otherwise you'll hardbrick your device.
3.7. Reboot your phone by typing fastboot reboot or by selecting the "START" option in phone's screen and then pressing the power button
That's it. If you liked, press thanks
Ps: some of my friends have reported phone is rebooting right after flashing sparsechunk.5.
phone will apparently boot normally and show the setup wizard screen, but in actuality there will be missing files on the system partition.
in that case, reboot into fastboot and finish flashing the system normally, then boot your phone

Thank you very much! Excuse me if I'm wrong but with this file it's safe to install Oreo from stock Nuggat right? I just need to unlock the bootloader and flash normally?

Thank, you to provide the firmware.
On another thread (https://forum.xda-developers.com/g5...eo-8-1-0-release-opp28-t3849273/post77771786) you wrote it's necessary to be on firmware NPPS25.137-93-2-5. Maybe you forgot to mention that!?

I believe the two threads are separate updates. One being OTA and this thread being fastboot firmware. I was wondering if this would work on my Moto g5 xt1670 (137-93-8)?

Woooow
Thanks

Ahasverus said:
Thank you very much! Excuse me if I'm wrong but with this file it's safe to install Oreo from stock Nuggat right? I just need to unlock the bootloader and flash normally?
Click to expand...
Click to collapse
no need to unlock BL to flash this. If you're on stock Nougat just make sure you're on NPPS25.137-93-2-5 (July security patch), then grab the ota here and sideload or flash it using the stock recovery
if you're not on NPPS25.137-93-2-5 then you'll need to flash it before flashing the ota.
AndroidenKalle said:
Thank, you to provide the firmware.
On another thread (https://forum.xda-developers.com/g5...eo-8-1-0-release-opp28-t3849273/post77771786) you wrote it's necessary to be on firmware NPPS25.137-93-2-5. Maybe you forgot to mention that!?
Click to expand...
Click to collapse
if you're going to install it from fastboot there's no need to be on NPPS25.137-93-2-5

TWRP v3.2.3.0 for Cedric: works
Magisk v17.1: works (don't use safetynet)

Thank you very much for this! I've been using the soak Oreo and could not be happier until this thread, time for the final Oreo for my beloved G5.

Blur_Version.28.41.15 for OPP28.85-16 is correct!
I'm on the 2nd soak test update OPP28.85-13 and tried the OTA update from your other post. This failed due to wrong version (E3002) since it expects the last NPPS25.137-93-2-5 version.
How can I update from OPP28.85-13 to the latest OPP28.85-16 via fastboot flash without losing my current data and settings?
Can I flash without "erase userdata"?

The thing I don't like in your instructions is lack of DDR errase command.
Please explain your point. Also please compare with flashfile.xml from Oreo firmware.

PsyClip-R said:
The thing I don't like in your instructions is lack of DDR errase command.
Please explain your point. Also please compare with flashfile.xml from Oreo firmware.
Click to expand...
Click to collapse
So "fastboot erase ddr" command should be included while flashing stock Oreo through fastboot? What does that command do?

I am on amzin software channel and my build number is NPPS25.137-93-14 (July Security Patch). Will this fastboot method work for me?

Hello,
the bootloader locking seems not to be working. At the last "fastboot oem lock" it says that it needs a signed boot.img. Has anyone else experienced this issue ?

achintyakv said:
I am on amzin software channel and my build number is NPPS25.137-93-14 (July Security Patch). Will this fastboot method work for me?
Click to expand...
Click to collapse
I don't think so since this is definitely a retail version.
BUILD REQUEST INFO:
SW Version: cedric-user 8.1.0 OPP28.85-16 0400 release-keysM8937_22.29.02.70R
MBM Version: B8.31
Modem Version: M8937_22.29.02.70R
FSG Version: FSG-8937-02.65.33
Build Fingerprint: motorola/cedric/cedric:8.1.0/OPP28.85-16/0400:user/release-keys
CQATest App Version: 6.0.6
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 28.41.15.cedric.retail.en.US
Model Number: Moto G (5)
Android Version: 8.1.0
Baseband Version: M8937_22.29.02.70R
Build Id: OPP28.85-16
SW Display Build ID: OPP28.85-16
Build Date: Wed Sep 5 09:46:09 CDT 2018
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.28.41.15.cedric.retail.en.US
Version when read from CPV: cedric-user 8.1.0 OPP28.85-16 0400 release-keys

slsmaster said:
Hello,
the bootloader locking seems not to be working. At the last "fastboot oem lock" it says that it needs a signed boot.img. Has anyone else experienced this issue ?
Click to expand...
Click to collapse
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
Try this (on your own risk only): input "fastboot oem lock" twice (first time for starting the whole process of locking, second time for confirmation). Then, execute commands below, one by one
Code:
fastboot flash oem oem.img
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
Then, input "fastboot oem lock" for the last time. Your phone should immediately reboot, as mine did. If there will be problem with booting into OS, just reflash the whole system with commands below:
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 erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Edit: as you can see at the screenshots in the attachment, I'm able to lock bootloader with this firmware. First, I reflashed the whole Oreo firmware, then rebooted into bootloader using "fastboot reboot-bootloader" command and at last I tried to relock bootloader which was (once again) successful.
Phone specs: XT1676 (3/16), DualSIM, reteu soft. channel

Andrej_SK said:
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
......
......
Click to expand...
Click to collapse
Thank you very much, worked like a charm.

need cedric amzin oreo update before was on soak oreo ,after upate this phone stay in fastboot mode

PsyClip-R said:
The thing I don't like in your instructions is lack of DDR errase command.
Please explain your point. Also please compare with flashfile.xml from Oreo firmware.
Click to expand...
Click to collapse
never heard about this command before, I have never used it ever and I flashed this firmware without any problem so far
Andrej_SK said:
So "fastboot erase ddr" command should be included while flashing stock Oreo through fastboot? What does that command do?
Click to expand...
Click to collapse
As I said above, I and other people I know who flashed this didn't have any problem by flashing without typing "fastboot erase DDR" and in fact I'm curious to know what does this command do.
JoeDoe0 said:
Blur_Version.28.41.15 for OPP28.85-16 is correct!
I'm on the 2nd soak test update OPP28.85-13 and tried the OTA update from your other post. This failed due to wrong version (E3002) since it expects the last NPPS25.137-93-2-5 version.
How can I update from OPP28.85-13 to the latest OPP28.85-16 via fastboot flash without losing my current data and settings?
Can I flash without "erase userdata"?
Click to expand...
Click to collapse
I think it's very unlikely anyone has this OPP25.85-16, otherwise it would've already surfaced somewhere.
(edit)
seems like I was wrong, I just reflashed the firmware and managed to keep my data by not using fastboot erase user data.
(/edit)
regarding the "fastboot erase user data" it doesn't matter if you use it or not, since once you flash all sparse chunks you'll lose your data partition anyways.
what I'd suggest you to do is
1.backup your data partition using twrp and your internal storage to a pc/sdcard/whatever (twrp doesn't backup your internal storage)
2. flash the firmware just as described on the main thread
3 fastboot boot twrp.img PRIOR to the first boot
4. restore your data
5. connect your phone to USB cable with twrp still open and copy back your internal storage through TWRP's MTP(or use twrp's file manager/aroma FM in case you backed internal storage to sd card)
5. boot your phone.
I never tried backing up internal storage but I already did this when fastbooting and managed to keep my data (settings, apps, etc) .
I just advice you to remove any screen lock prior to backing up your data since your previous pattern/pin/password generally won't work after restoring a twrp backup, but in case you forget it use twrp and go to /data/system and delete locksettings.db and your
lock screen protection will be gone
achintyakv said:
I am on amzin software channel and my build number is NPPS25.137-93-14 (July Security Patch). Will this fastboot method work for me?
Click to expand...
Click to collapse
I don't know, this could brick your phone, but I'm not sure
tapan8914 said:
need cedric amzin oreo update before was on soak oreo ,after upate this phone stay in fastboot mode
Click to expand...
Click to collapse
as I said idk what'd happen if someone did this. the best you can do now is to find some old amzin firmware and fastboot it (do not flash gpt.bin or bootloader.bin, so as not to hard brick your device)

Andrej_SK said:
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
Try this (on your own risk only): input "fastboot oem lock" twice (first time for starting the whole process of locking, second time for confirmation). Then, execute commands below, one by one
Code:
fastboot flash oem oem.img
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
Then, input "fastboot oem lock" for the last time. Your phone should immediately reboot, as mine did. If there will be problem with booting into OS, just reflash the whole system with commands below:
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 erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Edit: as you can see at the screenshots in the attachment, I'm able to lock bootloader with this firmware. First, I reflashed the whole Oreo firmware, then rebooted into bootloader using "fastboot reboot-bootloader" command and at last I tried to relock bootloader which was (once again) successful.
Phone specs: XT1676 (3/16), DualSIM, reteu soft. channel
Click to expand...
Click to collapse
many a thanks, I'll put this on the main thread

Currently on OPP28.85-3
Currect me if I'm wrong, but by what I have been reading,
I cant go from OPP28.85-3 to OPP28.85-16
What I've read, I can't be on bootloader B8.31 (which I am) and since this isn't a "full system" image, just a "patch" for official Nougat to upgrade to offical Oreo, I need to be on Nougat.
If this is the case, could I go back to nougat through a TWRP Zip, or would this need to be done through fastboot commands. I know I need a downgraded Bootloader and I don't think ROM flashing affects anything else but /system
PLEASE correct me if I'm wrong. Just a curious guy who loves learning.

Moto G5 plus - Cant' relock bootload : (bootloader) Still require signed boot.img

I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked. That's weird, I thought a phone with open bootloader would not receive OTA, but mine does.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damn thing.
Everything works fine, except for Netflix that can't be installed no longer and my bank software who keeps complaining.
C:\MinimalADBFastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.052s]
writing 'logo'...
OKAY [ 0.099s]
finished. total time: 0.161s
C:\MinimalADBFastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.397s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.285s]
finished. total time: 0.689s
C:\MinimalADBFastboot>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.491s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.364s]
finished. total time: 0.861s
I just dunno what to do to relock, any advice ?

CanadianGixxerman said:
I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked. That's weird, I thought a phone with open bootloader would not receive OTA, but mine does.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damn thing.
Everything works fine, except for Netflix that can't be installed no longer and my bank software who keeps complaining.
C:\MinimalADBFastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.052s]
writing 'logo'...
OKAY [ 0.099s]
finished. total time: 0.161s
C:\MinimalADBFastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.397s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.285s]
finished. total time: 0.689s
C:\MinimalADBFastboot>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.491s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.364s]
finished. total time: 0.861s
I just dunno what to do to relock, any advice ?
Click to expand...
Click to collapse
An unlocked bootloader has nothing to do with getting OTA updates. At least you get the unlock code from the manufacturer himself.
Only changes in /system or /vendor like rooting or other tweaks make OTA fail.
About locking the BL, a bit of research would have taken you here: https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
For Oreo the whole sets of commands are for
Locking:
-----------------
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
-------------------
Flashing:
-------------------
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 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
--------------------
Edited because of wrong number of sparechunk files for Oreo firmwares.

@Wolfcity
Unlike you supposed, I just did not throw my problem in the forum and waited for someone else to hand me a solution on a silver plate. I did do my homeworks, I did *MANY* searches, I did see the post you pointed me toward, that one and many many others that resembled it closely. But this whole endeavour did not lead me to my expected objective, which is to relock my phone. I am in the same loop I was in when I started trying : The second time I issue the «fastboot oem lock» command, I get this :
C:\Moto potter>fastboot.exe oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.003s]
finished. total time: 0.003s
And the BL does not lock.

CanadianGixxerman said:
@Wolfcity
Unlike you supposed, I just did not throw my problem in the forum and waited for someone else to hand me a solution on a silver plate. I did do my homeworks, I did *MANY* searches, I did see the post you pointed me toward, that one and many many others that resembled it closely. But this whole endeavour did not lead me to my expected objective, which is to relock my phone. I am in the same loop I was in when I started trying : The second time I issue the «fastboot oem lock» command, I get this :
C:\Moto potter>fastboot.exe oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.003s]
finished. total time: 0.003s
And the BL does not lock.
Click to expand...
Click to collapse
You can get signed images from Lenovo Moto smart assistant app, just go for rescue and let the firmware gets download, then go to the c/LMSA/ROM there you can find the firmware which has signed, use that image for locking bootloader, then you can lock your bootloader.and don't get anger on wolfcity he just try to help you as, some person don't know how to lock bootloader so they just post on XDA without reading the other thread only.

CanadianGixxerman said:
@Wolfcity
Unlike you supposed, I just did not throw my problem in the forum and waited for someone else to hand me a solution on a silver plate. I did do my homeworks, I did *MANY* searches, I did see the post you pointed me toward, that one and many many others that resembled it closely. But this whole endeavour did not lead me to my expected objective, which is to relock my phone. I am in the same loop I was in when I started trying : The second time I issue the «fastboot oem lock» command, I get this :
C:\Moto potter>fastboot.exe oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.003s]
finished. total time: 0.003s
And the BL does not lock.
Click to expand...
Click to collapse
I don't wanted to sound rude or something like that.
You didn't mention that you used all the fastboot locking commands in you first post, you just posted three lines of flashing boot, recovery and logo.
So no offense.
What sounds strange to me is that Netflix and your banking app aren't working with an unlocked bootloader. Normally these applications are looking for traces of rooting methods like magisk or SuperSU. I'm unlocked and rooted with magisk and Netflix is working for me if I put in on magisk's hide list. Maybe you have some files on your device that trigger these anti rooting mechanisms? Sometimes just a file or folder named magisk could be enough.

Wolfcity said:
I don't wanted to sound rude or something like that.
You didn't mention that you used all the fastboot locking commands in you first post, you just posted three lines of flashing boot, recovery and logo.
So no offense.
What sounds strange to me is that Netflix and your banking app aren't working with an unlocked bootloader. Normally these applications are looking for traces of rooting methods like magisk or SuperSU. I'm unlocked and rooted with magisk and Netflix is working for me if I put in on magisk's hide list. Maybe you have some files on your device that trigger these anti rooting mechanisms? Sometimes just a file or folder named magisk could be enough.
Click to expand...
Click to collapse
No hard feelings.
It turns out that with your instructions (1st part : Locking) I was sucessful at my aim, finally. It did whine again about the signed image requirement after line 2, I continued [9 sparsechunks though, not 5 ... ], then, upon hitting «enter» after the last line [fastboot oem lock], Shazam, it locked.
You may be right about some left over garbage files [or traces of] that could still be present in the file system. I have loaded many customs roms last year on this phone, magisk and SuperSu as well.
Last but not least : Thank you.

CanadianGixxerman said:
No hard feelings.
It turns out that with your instructions (1st part : Locking) I was sucessful at my aim, finally. It did whine again about the signed image requirement after line 2, I continued [9 sparsechunks though, not 5 ... ], then, upon hitting «enter» after the last line [fastboot oem lock], Shazam, it locked.
You may be right about some left over garbage files [or traces of] that could still be present in the file system. I have loaded many customs roms last year on this phone, magisk and SuperSu as well.
Last but not least : Thank you.
Click to expand...
Click to collapse
Good to hear it worked out for you at last.
Seems that these "unsigned" messages are nothing to worry about to much. Sorry for the "sparechunk thing", copied the wrong flashall.bat file, this is the one for Oreo :https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
with 8 sparechunk files.
Last but not least: You're welcome.

Yeah this same thing happened to me today morning.. most guides have till sparsechunk4.. where as oreo has uptill 8.. so u need to flash the rest i.e 5,6,7,8. And then it will lock..

Wolfcity said:
Good to hear it worked out for you at last.
Seems that these "unsigned" messages are nothing to worry about to much. Sorry for the "sparechunk thing", copied the wrong flashall.bat file, this is the one for Oreo :https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
with 8 sparechunk files.
Last but not least: You're welcome.
Click to expand...
Click to collapse
I also had same error. Followed what you said. Finally locked bootloader. I am very happy now.
Thank you.

Might be good for someone who has gone through it, to make a new write-up, with current info. The longer these phones have been out, and bootloader unlocked, the more fragmented the info gets. It gets harder to know what currently works, and what could possibly "fubar" the phone.

[email protected] said:
Might be good for someone who has gone through it, to make a new write-up, with current info. The longer these phones have been out, and bootloader unlocked, the more fragmented the info gets. It gets harder to know what currently works, and what could possibly "fubar" the phone.
Click to expand...
Click to collapse
What do you mean? An "locking BL guide" or something more complete like "flashing/locking/encrypting/rooting"? I'm willing to that but I have to know what you guys need.

Wolfcity said:
What do you mean? An "locking BL guide" or something more complete like "flashing/locking/encrypting/rooting"? I'm willing to that but I have to know what you guys need.
Click to expand...
Click to collapse
Sure,,,, all of it! I unlocked my first G5 plus a year and a half ago. I have hard bricked it 3 times, and now use it for a test phone, as it has an addison bootloader. My everyday G5 plus is unlocked and rooted, but I've kept it on stock roms and kernels, due to a little fear of how easily these can be corrupted. I am certainly not ignorant of most of the workings with these, even going so far as to use Qualcomm's factory utilities to dig deep inside. However, that being said, what worked when I first unlocked my original, isn't totally pertinent today. Nougat and Oreo factory roms, nougat, oreo, pie developer roms, 64 bit and 32 bit, all add to a confusing set list of what can be safely done without irreversible consequences. I've kept up on these forums for almost 2 years, but the fragmentation of guides makes it confusing enough for myself, much less a novice. Example of things that can go wrong to unsuspecting, is the loss of touchscreen with stock oreo. I haven't experienced it, but it is out there. I'm just saying it would be hugely beneficial for all, if we could get some current guides, stickied in place of our outdated ones. I have the test phone that I have put through the wringer, and am more than willing to use it as a guinea pig for any other processes that may add to the guides.

[email protected] said:
Sure,,,, all of it! I unlocked my first G5 plus a year and a half ago. I have hard bricked it 3 times, and now use it for a test phone, as it has an addison bootloader. My everyday G5 plus is unlocked and rooted, but I've kept it on stock roms and kernels, due to a little fear of how easily these can be corrupted. I am certainly not ignorant of most of the workings with these, even going so far as to use Qualcomm's factory utilities to dig deep inside. However, that being said, what worked when I first unlocked my original, isn't totally pertinent today. Nougat and Oreo factory roms, nougat, oreo, pie developer roms, 64 bit and 32 bit, all add to a confusing set list of what can be safely done without irreversible consequences. I've kept up on these forums for almost 2 years, but the fragmentation of guides makes it confusing enough for myself, much less a novice. Example of things that can go wrong to unsuspecting, is the loss of touchscreen with stock oreo. I haven't experienced it, but it is out there. I'm just saying it would be hugely beneficial for all, if we could get some current guides, stickied in place of our outdated ones. I have the test phone that I have put through the wringer, and am more than willing to use it as a guinea pig for any other processes that may add to the guides.
Click to expand...
Click to collapse
You're lucky you have the ability to financially purchase a second G5 Plus to use as a failsafe. When I purchased mine it was roughly around $300-400 (was brand new) so to have purchased another at the time wasn't an option, and may as well purchase a 700+ flagship with that money. To this day I've owned over 30 devices and tested well over that. Thus far only the Galaxy S2 and the Motorola G5 Plus were the only two that have surpassed a year with good stable service. I don't even purchase the phone cases cause devices are supposed to be visually appealing like cars, because tech will always be sexxy. Anyways, my point was since the Photon Q back in early 2014 to this G5 Plus, I've really liked Motorola. If you take the time the align this phone purrs. But I need to upgrade soon as.. Thinking of getting a Pixel 3 when it reaches my shores.. Anyways, it's 1:28am, goodnight.

I was able to purchase the second phone for less than $100 US, slightly used. So it was a no brainer to have a guinea pig phone.

Wolfcity said:
An unlocked bootloader has nothing to do with getting OTA updates. At least you get the unlock code from the manufacturer himself.
Only changes in /system or /vendor like rooting or other tweaks make OTA fail.
About locking the BL, a bit of research would have taken you here: https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
For Oreo the whole sets of commands are for
Locking:
-----------------
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
-------------------
Flashing:
-------------------
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 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
--------------------
Edited because of wrong number of sparechunk files for Oreo firmwares.
Click to expand...
Click to collapse
Hi!!
I need to relock my Moto G5 Plus, because my country use a Covid App to transit trough states.
And I need it to use because I´m a essential worker. This App check the locked / unlocked devices.
I Know that Netlix do the same, but it never mattered to me to that app.
Now I really need to Re Locked my phone
I have tried several methods.. and doesn´t work any of them

Mr.BUBU said:
Hi!!
I need to relock my Moto G5 Plus, because my country use a Covid App to transit trough states.
And I need it to use because I´m a essential worker. This App check the locked / unlocked devices.
I Know that Netlix do the same, but it never mattered to me to that app.
Now I really need to Re Locked my phone
I have tried several methods.. and doesn´t work any of them
Click to expand...
Click to collapse
You can orientate yourself by this guide but as the one is for Nougat you need to correct the number of the sparechunk files:
How to re-lock Bootloader of all Potter version
Hi guys, finally I succed in relock my XT1685 Bootloader on RETEU, so I will guide you to relock your bootloader. DISCLAIMER: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm...
forum.xda-developers.com
So the first set of commands should be:
First set:
Lock.
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
Second set:
Flashing firmware.
Code:
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 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Device is now full stock with locked bootloader.
For the second set of commands you can use a flashall.bat file like this:
Dropbox - File Deleted - Simplify your life
www.dropbox.com
It may look like the first set would be enough but that's not true, you have to flash the whole firmware afterwards.
Be aware that all of your internal data (apps, settings and everything you have in internal storage) will be erased so make backups of everything. Also backup all partitions with TWRP especially persist and efs!
This tutorial may help you to find the correct firmware for your device (links available) and also guide you through the flashing process of the whole firmware;
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com
Maybe use also the tools and drivers from there.

Wolfcity said:
You can orientate yourself by this guide but as the one is for Nougat you need to correct the number of the sparechunk files:
How to re-lock Bootloader of all Potter version
Hi guys, finally I succed in relock my XT1685 Bootloader on RETEU, so I will guide you to relock your bootloader. DISCLAIMER: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm...
forum.xda-developers.com
So the first set of commands should be:
First set:
Lock.
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
Second set:
Flashing firmware.
Code:
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 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Device is now full stock with locked bootloader.
For the second set of commands you can use a flashall.bat file like this:
Dropbox - File Deleted - Simplify your life
www.dropbox.com
It may look like the first set would be enough but that's not true, you have to flash the whole firmware afterwards.
Be aware that all of your internal data (apps, settings and everything you have in internal storage) will be erased so make backups of everything. Also backup all partitions with TWRP especially persist and efs!
This tutorial may help you to find the correct firmware for your device (links available) and also guide you through the flashing process of the whole firmware;
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com
Maybe use also the tools and drivers from there.
Click to expand...
Click to collapse
Wait so I have to run the bootloader lock first and then flash the firmware for my Motorola one p30 play as well?

smartasiankid said:
Wait so I have to run the bootloader lock first and then flash the firmware for my Motorola one p30 play as well?
Click to expand...
Click to collapse
No, the user who was asking wanted to lock his BL so I gave him the lock commands too.
I don't know anything about your device but normally the BL has to be unlocked to flash firmware on a Moto.

Wolfcity said:
No, the user who was asking wanted to lock his BL so I gave him the lock commands too.
I don't know anything about your device but normally the BL has to be unlocked to flash firmware on a Moto.
Click to expand...
Click to collapse
Oh okay. I tried relocking the bootloader on Moto one p30 play but when repeatedly entering 'fastboot oem lock' it says "still require signed boot.img" and even after I flash the boot.img when it asks to whenever I enter the fastboot oem lock command it says "still require signed boot.img"

Can you help me out please?