Database Users

[Guide]relock your bl

This guide will help you re lock the bootloader and fix the bootloader is damaged error download a stock rom for the cedric extract it into adb and fast boot . (Not into its own folder just all the files in adb ) link to stock roms :
Now copy these commands
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
If it worked there shouldn't be a bl warning and in fastboot it should say flashing-locked
Note any problems caused are not my fault I have tested on my device and on g5+ both are fine !

Thank you so much, my Bootloader is locked again.
̶C̶a̶n̶ ̶y̶o̶u̶ ̶p̶l̶e̶a̶s̶e̶ ̶g̶i̶v̶e̶ ̶u̶s̶ ̶f̶i̶r̶m̶w̶a̶r̶e̶ ̶f̶i̶l̶e̶ ̶t̶h̶a̶t̶ ̶y̶o̶u̶ ̶u̶s̶e̶d̶?̶

First its the command to relock de BL?
before the commands to flash system?

AlmapekeDj said:
First its the command to relock de BL?
before the commands to flash system?
Click to expand...
Click to collapse
You need to reflash system

With me didn't worked. It says "Not signed rom"

CypherPotato said:
With me didn't worked. It says "Not signed rom"
Click to expand...
Click to collapse
Redownload stock

CypherPotato said:
With me didn't worked. It says "Not signed rom"
Click to expand...
Click to collapse
Did you get it already? Still need it?
Anyway, if anyone else needs it https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
This is the only one that worked signed for me, XT1672

my imei is 0 already tried everything but I did not have any results help me please it's an xt1672

jonathars said:
my imei is 0 already tried everything but I did not have any results help me please it's an xt1672
Click to expand...
Click to collapse
Reflash stock rom

CypherPotato said:
Reflash stock rom
Click to expand...
Click to collapse
I already did this and it did not work
---------- Post added at 02:36 AM ---------- Previous post was at 02:30 AM ----------
CypherPotato said:
Reflash stock rom
Click to expand...
Click to collapse
I already did this and it did not work

infixremix said:
This guide will help you re lock the bootloader and fix the bootloader is damaged error download a stock rom for the cedric extract it into adb and fast boot . (Not into its own folder just all the files in adb ) link to stock roms :
Now copy these commands
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
If it worked there shouldn't be a bl warning and in fastboot it should say flashing-locked
Note any problems caused are not my fault I have tested on my device and on g5+ both are fine !
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------
You are amazing !!

Hi,
doesn't work for me. Tried from here:
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
Moto G5 - Jan 2017 firmware NPP25.137-15 and
Moto G5 - Nov 2017 firmware NPP25.137-93 (Moto G5 - Aug 2017 firmware NPP25.137-33/NPP25.137.33-10 not tested yet).
Error when flashing boot.img:
C:\g5\010117\platform-tools>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.583s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 1.035s
anyone an idea what's going wrong?
D.

CypherPotato said:
Reflash stock rom
Click to expand...
Click to collapse
can I reflash stock ROM with locked bootloader?
how can do that? using adb fastboot or RSD lite?
i just want to change my channel (today is retin, but i've got a stock ROM with retbr and want to use that)

carlapazin said:
can I reflash stock ROM with locked bootloader?
how can do that? using adb fastboot or RSD lite?
i just want to change my channel (today is retin, but i've got a stock ROM with retbr and want to use that)
Click to expand...
Click to collapse
Yes - via fastboot
I don't know why you would want to change though
You risk either not getting ota updates or potentially hard bricking your device if you flash a future ota update if you have flashed firmware that was not designed for your phones specific varient
Unless you have physically moved locations & the firmware you are using is not compatible with the countries mobile networks I see no benefits in changing firmware versions

TheFixItMan said:
Yes - via fastboot
I don't know why you would want to change though
You risk either not getting ota updates or potentially hard bricking your device if you flash a future ota update if you have flashed firmware that was not designed for your phones specific varient
Unless you have physically moved locations & the firmware you are using is not compatible with the countries mobile networks I see no benefits in changing firmware versions
Click to expand...
Click to collapse
thanx!!!

carlapazin said:
can I reflash stock ROM with locked bootloader?
how can do that? using adb fastboot or RSD lite?
i just want to change my channel (today is retin, but i've got a stock ROM with retbr and want to use that)
Click to expand...
Click to collapse
RSD Lite only emulates Fastboot inside the application.
Idk if you can flash the stock rom with an locked bootloader, if it is signed, you can, otherwise, no.

Moto G boots only into TWRP

My XT1625 has an unlocked bootloader and TWRP installed. Today I got a notification that the Sept security patch was available so I downloaded it and tried to install. I was paying attention until I noticed it booted back into TWRP and does it everytime so I guess accepting and installing that patch was a no-no. I got it to boot into Android from instructions in another post.
Can I locate the patch in TWRP and flash it from there? Btw, I did notice that the patch was only 49MB so it clearly wasn't the entire Nougat ROM.

lmacmil said:
My XT1625 has an unlocked bootloader and TWRP installed. Today I got a notification that the Sept security patch was available so I downloaded it and tried to install. I was paying attention until I noticed it booted back into TWRP and does it everytime so I guess accepting and installing that patch was a no-no. I got it to boot into Android from instructions in another post.
Can I locate the patch in TWRP and flash it from there? Btw, I did notice that the patch was only 49MB so it clearly wasn't the entire Nougat ROM.
Click to expand...
Click to collapse
You cannot flash an official OTA update. You need to be on official recovery for this. Have a look at here, same question https://forum.xda-developers.com/moto-g4-plus/help/luck-moto-g4-plus-flashable-logo-bin-t3701652
For update its advisable to use the full stock rom to be flashed with fastboot like this one https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Please use always search function as this happens every week a few times and same question is answered already enough.
Also worth having a look here https://forum.xda-developers.com/moto-g4-plus/help/help-thread-question-noob-friendly-t3526598 and also ask here.

strongst said:
You cannot flash an official OTA update. You need to be on official recovery for this. Have a look at here, same question https://forum.xda-developers.com/moto-g4-plus/help/luck-moto-g4-plus-flashable-logo-bin-t3701652
I saw that other post and edited mine to acknowledge that I saw the fix (see last sentence of 1st paragraph.)
For update its advisable to use the full stock rom to be flashed with fastboot like this one https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Thanks. I probably won't go to that much trouble.
Please use always search function as this happens every week a few times and same question is answered already enough. I generally do.
Also worth having a look here https://forum.xda-developers.com/moto-g4-plus/help/help-thread-question-noob-friendly-t3526598 and also ask here.
Click to expand...
Click to collapse
I rebooted and it went back to TWRP again. I will ask how to fix this in the help thread.

lmacmil said:
I rebooted and it went back to TWRP again. Will I have to boot to fastboot mode and select factory mode every time now or is there a fix that will boot into Android instead of TWRP?
Click to expand...
Click to collapse
Try to run these commands from fastboot..
fastboot oem fb_mode_set
fastboot oem fb_mode_clear

____Mdd said:
Try to run these commands from fastboot..
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
I will give it a try.

lmacmil said:
I will give it a try.
Click to expand...
Click to collapse
use the following script :
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 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

____Mdd said:
Try to run these commands from fastboot..
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Got error messages:
D:\Computer\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.005s]
finished. total time: 0.008s

siddhesh9146 said:
use the following script :
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 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
Is this going to wipe my system like a factory reset? If so, can I just restore the backup I made after I installed TWRP initially? Or just do a factory reset?

@lmacmil ignore it, use both commands then try to boot.
---------- Post added at 12:41 AM ---------- Previous post was at 12:34 AM ----------
lmacmil said:
Is this going to wipe my system like a factory reset? If so, can I just restore the backup I made after I installed TWRP initially? Or just do a factory reset?
Click to expand...
Click to collapse
Don't use it if you are thinking to just run script and not to flash... since it has "erase modemst1 & 2" it will erase modem, but will not flash fsg/modem, also "erase data" will wipe everything on phone.. this can put you in trouble..
Instead of doing this, as strongst said in his post, flash complete firmware, see the link for september's update he gave in his post.
Then move everything from your phone to PC (images / video/ etc)
Then flash firmware...

____Mdd said:
@lmacmil ignore it, use both commands then try to boot.
---------- Post added at 12:41 AM ---------- Previous post was at 12:34 AM ----------
Don't use it if you are thinking to just run script and not to flash... since it has "erase modemst1 & 2" it will erase modem, but will not flash fsg/modem, also "erase data" will wipe everything on phone.. this can put you in trouble..
Instead of doing this, as strongst said in his post, flash complete firmware, see the link for september's update he gave in his post.
Then move everything from your phone to PC (images / video/ etc)
Then flash firmware...
Click to expand...
Click to collapse
Still boots to TWRP. Maybe this is the time to move to LineageOS 14.1. I was going to wait until 15 was stable but if I'm going to lose everything, I might as well get more up to date.
This seems to have killed my cell signal too. Just noticed that last time I booted to Android.

lmacmil said:
Still boots to TWRP. Maybe this is the time to move to LineageOS 14.1. I was going to wait until 15 was stable but if I'm going to lose everything, I might as well get more up to date.
This seems to have killed my cell signal too. Just noticed that last time I booted to Android.
Click to expand...
Click to collapse
Did you flash complete stock ROM ?
Move your files to External Storage then try it.

____Mdd said:
Did you flash complete stock ROM ?
Move your files to External Storage then try it.
Click to expand...
Click to collapse
I decided since I would have to reinstall all my apps anyway that I would flash LineageOS 14.1, which I did. I did the appropriate wipes (data, system, cache, Dalvik/ART), then flashed the latest nightly and Gapps. It was successful but it's still booting into TWRP and I still have no cell service. I thought that a complete wipe and installation of new ROM would correct those issues but it did not. And since it didn't, I'm not confident that flashing the stock ROM would either but unless there's something else to try, I will do it. One concern I have is I have a plain G4 and the ROM is for the G4 Plus. My build was NPJ25.93-14.5 and I think the Plus build is NPJS... Not sure if that makes a difference.
Maybe I should restore my original Nandroid backup first and see if that fixes things.

lmacmil said:
. My build was NPJ25.93-14.5 and I think the Plus build is NPJS... Not sure if that makes a difference.
Click to expand...
Click to collapse
NPJ25.93-14.5 was for Amazon variant if i am not wrong.
I don't know but in past that two commands [fb_mode_set and fb_mode_clear] worked fine for this problem.
Try this thing, [reboot to bootloader and flash TWRP but with fb_mode_ commands]
- fastboot oem fb_mode_set
- fastboot flash recovery twrp(name).img
- fastboot oem fb_mode_clear
If this too doesn't work, then you have to find correct firmware for your phone and flash it..
EDIT: for easiness to find correct firmware, restore backup, then see "about phone" for build number, it will help to find firmware..
EDIT-2:
I found 2 firmware of version you said,
But one says Amazon and another doesn't. You have Nandroid, restore and check your phone build..
Then go for following one correctly..
AMAZON : Click here
Non-AMAZON : Click here

____Mdd said:
NPJ25.93-14.5 was for Amazon variant if i am not wrong.
I don't know but in past that two commands [fb_mode_set and fb_mode_clear] worked fine for this problem.
Try this thing, [reboot to bootloader and flash TWRP but with fb_mode_ commands]
- fastboot oem fb_mode_set
- fastboot flash recovery twrp(name).img
- fastboot oem fb_mode_clear
If this too doesn't work, then you have to find correct firmware for your phone and flash it..
EDIT: for easiness to find correct firmware, restore backup, then see "about phone" for build number, it will help to find firmware..
EDIT-2:
I found 2 firmware of version you said,
But one says Amazon and another doesn't. You have Nandroid, restore and check your phone build..
Then go for following one correctly..
AMAZON : Click here
Non-AMAZON : Click here
Click to expand...
Click to collapse
Mine was the non-Amazon version. See attachment. The software channel was "retus" and the baseband version also said "ATHENE_RETUSA_CUST" The Amazon version software channel is amz.
I was able to get the bootloader unlock code from Motorola and they don't allow the Amazon versions to be unlocked.
I'll try your suggestions. Thanks for your continued help.

____Mdd said:
NPJ25.93-14.5 was for Amazon variant if i am not wrong.
I don't know but in past that two commands [fb_mode_set and fb_mode_clear] worked fine for this problem.
Try this thing, [reboot to bootloader and flash TWRP but with fb_mode_ commands]
- fastboot oem fb_mode_set
- fastboot flash recovery twrp(name).img
- fastboot oem fb_mode_clear
Click to expand...
Click to collapse
This is what I got:
D:\Computer\Minimal ADB and Fastboot>fastboot devices
ZY223N5GLF fastboot
D:\Computer\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ -0.000s]
finished. total time: -0.000s
D:\Computer\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12530 KB)...
OKAY [ 0.402s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.190s]
finished. total time: 0.595s
D:\Computer\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.001s]
finished. total time: 0.001s
=================================
Not sure why I'm getting the bootloader error messages but I backed up just the bootloader recently so am going to restore that and see what happens.

@lmacmil that "not found" is ignorable, just check you get "OKAY" after one command ends... Since GPT and Bootloader commands got "OKAY" they are flashed successfully..... Go for complete firmware...

____Mdd said:
@lmacmil that "not found" is ignorable, just check you get "OKAY" after one command ends... Since GPT and Bootloader commands got "OKAY" they are flashed successfully..... Go for complete firmware...
Click to expand...
Click to collapse
I guess I need to bite the bullet and do this. It will install stock recovery and erase TWRP, right? If that's the case, and I don't relock the bootloader, will I be able to accept the OTA update? Or does an unlocked bootloader prevent OTA updates?
Last question: I just extract the firmware .zip file to the same folder where fastboot and adb reside? Then type the commands one by one (or copy/paste from the script shown in the thread about flashing stock firmware.)
Thanks again.

lmacmil said:
I guess I need to bite the bullet and do this. It will install stock recovery and erase TWRP, right?
Click to expand...
Click to collapse
Yes, it will install stock recovery, you will have to install TWRP again.
If that's the case, and I don't relock the bootloader, will I be able to accept the OTA update? Or does an unlocked bootloader prevent OTA updates?
Click to expand...
Click to collapse
It will be fine, You will have successful installation with unlocked bootloader too, no need to lock back..
Last question: I just extract the firmware .zip file to the same folder where fastboot and adb reside? Then type the commands one by one (or copy/paste from the script shown in the thread about flashing stock firmware.)
Thanks again.
Click to expand...
Click to collapse
You did right, that's why there is "OKAY" when command end, see your own post where you asked for "not found" error... Keep Going..

____Mdd said:
Yes, it will install stock recovery, you will have to install TWRP again.
You did right, that's why there is "OKAY" when command end, see your own post where you asked for "not found" error... Keep Going..
Click to expand...
Click to collapse
Success! Just flashed the stock Nougat ROM and as soon as it booted up, I let it download and install the Sept security patch. I am now on NPJ25.93-14.7.
Thanks again for all your help.
Lee

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?

Need help going back to full stock

Hi! I currently have NPNS25.137-92 running thanks to a TWRP backup I did before going custom Pie on my G5+. I'd like to go back to stock so that TWRP is removed, bootloader locked and I can take official OTAs up to Oreo or whatever it is. What is the best way to achieve this? I could flash the latest Oreo TWRP flashable build, but that way it won't accept OTAs right?
Any help will be greatly appreciated.
Cheers

guillermohs9 said:
Hi! I currently have NPNS25.137-92 running thanks to a TWRP backup I did before going custom Pie on my G5+. I'd like to go back to stock so that TWRP is removed, bootloader locked and I can take official OTAs up to Oreo or whatever it is. What is the best way to achieve this? I could flash the latest Oreo TWRP flashable build, but that way it won't accept OTAs right?
Any help will be greatly appreciated.
Cheers
Click to expand...
Click to collapse
First thing: You don't have to lock the bootloader to receive and install OTA, this is a widespread fallacy.
And yes, with a TWRP flashable build you won't be able to apply OTA updates.
To get back on track you will have to flash a full fastboot ROM, best would be the latest one available for your region.
Firmwares can be found here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Oreo builds for the US are ending on 85-17-x (where 17-4 is the latest), for other regions it's 85-13-x , here the latest one is 85-13-5 (December security patch).
You will lose your data so backup your stuff.

Wolfcity said:
First thing: You don't have to lock the bootloader to receive and install OTA, this is a widespread fallacy.
And yes, a TWRP flashable build won't be able to apply OTA updates.
To get back on track you will have to flash a full fastboot ROM, best would be the latest one available for your region.
Firmwares can be found here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Oreo builds for the US are ending on 85-17-x (where 17-4 is the latest), for other regions it's 85-13-x , here the latest one is 85-13-5 (December security patch).
Click to expand...
Click to collapse
Thanks for your answer, I'm looking but I guess firmwares for my region (retar) are difficult to find. Flashing retus won't affect the usage? Finally, to flash that image you must unzip it and paste that long chunk of fastboot commands I've seen around here right?

guillermohs9 said:
Thanks for your answer, I'm looking but I guess firmwares for my region (retar) are difficult to find. Flashing retus won't affect the usage? Finally, to flash that image you must unzip it and paste that long chunk of fastboot commands I've seen around here right?
Click to expand...
Click to collapse
No, flashing the US variant won't affect usage. It's possible that you don't receive OTA updates in the future anymore because the ones pushed in your region may be for the other update channel. Would be good to find out which Oreo build has been pushed to your region, maybe you can elaborate it via Google.
Yes, you have to unzip the firmware in your adb/fastboot folder on your PC and enter all fastboot commands, you can also use a flashall.bat with all commands in it. You have to copy that bat into your adb/fastboot folder too and just click it.
Here's one:https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
There are some tutorials around how to do it all but some are a bit outdated. I'm about to write an actual one.
You need Motorola drivers on your PC:
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view?usp=sharing
and something like Minimal Adb & Fastboot:
https://drive.google.com/file/d/10NEzpxKpYWfq-HdK42ctwoEnCg-BfsRQ/view?usp=sharing
If you're not familiar with this procedure you can also give Lenovo Motorola Smart Assistant a shot:
https://support.lenovo.com/de/de/downloads/ds101291

Wolfcity said:
No, flashing the US variant won't affect usage. It's possible that you don't receive OTA updates in the future anymore because the ones pushed in your region may be for the other update channel. Would be good to find out which Oreo build has been pushed to your region, maybe you can elaborate it via Google.
Click to expand...
Click to collapse
I'm searching for images for retar channel but with no luck. Having flashed retus image, won't I be getting OTA updates pushed on retus?
You should write that tutorial, there is no such thing as too many well written tutorials!
I'm comfortable using fastboot and adb, I just never used them to go back to stock and finding the right firmware for potter seems hard for what I'm reading.

guillermohs9 said:
I'm searching for images for retar channel but with no luck. Having flashed retus image, won't I be getting OTA updates pushed on retus?
You should write that tutorial, there is no such thing as too many well written tutorials!
I'm comfortable using fastboot and adb, I just never used them to go back to stock and finding the right firmware for potter seems hard for what I'm reading.
Click to expand...
Click to collapse
I'll take a look what firmware has been pushed to your region. If you're on the wrong update channel you won't receive OTA updates because Motorola/Lenovo only pushes one update for every location, either the US version (17-x) or the other one (13-x).
I'm writing on that guide but it will be a bit extensive because it should cover unlocking/flashing/rooting/decrypting/locking, the whole thing.

Sorry for interrupting but I would like you have your advise.
I returned from custom pie to 8.1 stock flashed through fastboot. I'm from Belgium, I took the build OPS28.85-17. Reteu channel. This is sept 18 security patch.
I don't receive an ota for an updated security patch.
How can I flash OPS28.85-17-4 without losing data? With some fastboot commands? Wich ones? Tnx for help:good:

BartKey said:
Sorry for interrupting but I would like you have your advise.
I returned from custom pie to 8.1 stock flashed through fastboot. I'm from Belgium, I took the build OPS28.85-17. Reteu channel. This is sept 18 security patch.
I don't receive an ota for an updated security patch.
How can I flash OPS28.85-17-4 without losing data? With some fastboot commands? Wich ones? Tnx for help:good:
Click to expand...
Click to collapse
No need to apologize for interrupting, this is not a private chat. 17-4 is the US firmware, you'll have to change to OPS28.85-13-x to receive OTA updates here in Europe. Even when your "about phone" setting tells you you're on reteu, the firmware number is what makes the difference.
If your main goal is not to lose your data you can flash the 17-4 firmware by fastboot and omit the line "erase userdata". But you still won't receive future OTA updates as you're on the wrong firmware. You can try to flash the latest available fastboot firmware for Europe which is OPS28.85-13-3 and omit the "erase userdata" line too. The source for the firmwares is posted above, it's https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
As written above, a guide how to do it will follow.
The fastboot commands are the same as in the flashall.bat also posted above:
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

I flashed the retus Oreo firmware you suggested with the commands you uploaded to Dropbox but upon rebooting I get a "No command" screen and it's stuck there.
Edit: flashed Twrp now it says "bad key" on the unlocked device screen but it boots into stock Oreo.
I get the thing about the region. The device still says it's on retar so with retus firmware it will not take OTAs if I understood correctly.

guillermohs9 said:
I flashed the retus Oreo firmware you suggested with the commands you uploaded to Dropbox but upon rebooting I get a "No command" screen and it's stuck there.
Click to expand...
Click to collapse
Have you omitted the "erase userdata" line?
If that screen appears the device seems to be waiting for a reboot.
Edit: Ok, good to hear it's booting now.
The " bad key" screen is normal, you should have seen it after unlocking the bootloader.

Wolfcity said:
Have you omitted the "erase userdata" line?
If that screen appears the device seems to be waiting for a reboot.
Edit: Ok, good to hear it's booting now.
The " bad key" screen is normal, you should have seen it after unlocking the bootloader.
Click to expand...
Click to collapse
It used to say N/A instead. I don't mind. The problem now is that it always tries to boot into recovery.

guillermohs9 said:
....
I get the thing about the region. The device still says it's on retar so with retus firmware it will not take OTAs if I understood correctly.
Click to expand...
Click to collapse
As I said, depends on which firmware has been rolled out in your country.
What's your actual firmware number?

wolfcity said:
as i said, depends on which firmware has been rolled out in your country.
What's your actual firmware number?
Click to expand...
Click to collapse
opss28.85-17-4

guillermohs9 said:
opss28.85-17-4
Click to expand...
Click to collapse
Ok, that's the latest US build, so it can't find OTA now. Btw I don't think that we will see too many updates as the Moto G5+ isn't that new anymore so it's not such a big thing.
I haven't found out which firmware is the right one for your country, if I find out something I'll let you know.
As you said, no need to care about the bad key screen, I just flashed a custom bootlogo to get rid of it.
About booting into recovery, here's a thread about it: https://forum.xda-developers.com/showthread.php?p=74109609#post74109609
First try to wipe cache/dalvik in TWRP.
Than try enter "fastboot oem fb_mode_clear" from PC.
If that doesn't help try the mentioned dd commands from the thread in TWRP terminal.
It's a known problem.

Wolfcity said:
Ok, that's the latest US build, so it can't find OTA now. Btw I don't think that we will see too many updates as the Moto G5+ isn't that new anymore so it's not such a big thing.
I haven't found out which firmware is the right one for your country, if I find out something I'll let you know.
As you said, no need to care about the bad key screen, I just flashed a custom bootlogo to get rid of it.
About booting into recovery, here's a thread about it: https://forum.xda-developers.com/showthread.php?p=74109609#post74109609
First try to wipe cache/dalvik in TWRP.
Than try enter "fastboot oem fb_mode_clear" from PC.
If that doesn't help try the mentioned dd commands from the thread in TWRP terminal.
It's a known problem.
Click to expand...
Click to collapse
Thanks! I figured the same about the future updates, now Motorola is focused on newer devices so december security patch is enough.
I am on stock, unrooted, relocked bootloader now. I used the commands you provided (included erase userdata) then had to flash TWRP, flash magisk, use adb shell and dd to clear that misc partition (so it boots into system), and finally did
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
to relock bootloader. It works as expected now and it's ready to be used by anyone.
Thanks a lot

Wolfcity said:
No need to apologize for interrupting, this is not a private chat. 17-4 is the US firmware, you'll have to change to OPS28.85-13-x to receive OTA updates here in Europe. Even when your "about phone" setting tells you you're on reteu, the firmware number is what makes the difference.
If your main goal is not to lose your data you can flash the 17-4 firmware by fastboot and omit the line "erase userdata". But you still won't receive future OTA updates as you're on the wrong firmware. You can try to flash the latest available fastboot firmware for Europe which is OPS28.85-13-3 and omit the "erase userdata" line too. The source for the firmwares is posted above, it's https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
As written above, a guide how to do it will follow.
The fastboot commands are the same as in the flashall.bat also posted above:
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
Click to expand...
Click to collapse
Thanks a lot @Wolfcity
I came from OPS28.85-17, without updates available.
Now I flashed OPS28.85-13 with your instructions not to erase userdata.
Checking for updates: 13.3 available -> installed
13.5 available -> installed and "up to date" security patch dec 2018
:good:

@guillermohs9 @BartKey: Great to hear everything is working! I will add your experiences to the upcoming tutorial.

What is best way to update Security Patches on rooted / Unlocked G7?

What is the safest way to apply the newest updates? I am still on April, been afraid to do anything without asking first.
Is there a simple way, and will I still be able to unlock/root again?

Same question. Accent being on 'safe'.

SmilingPerson said:
What is the safest way to apply the newest updates? I am still on April, been afraid to do anything without asking first.
Is there a simple way, and will I still be able to unlock/root again?
Click to expand...
Click to collapse
maybeme2 said:
Same question. Accent being on 'safe'.
Click to expand...
Click to collapse
Either flash a custom rom that's been updated with the latest security patch
Or flash an official stock firmware but remember the chances of it being the latest security patch is slim
Obviously if your device is not bootloader unlocked you can't flash custom roms - you can flash official stock firmware via fastboot but I wouldn't bother as you will already be on the latest available firmware so just wait for the next ota update to arrive

TheFixItMan said:
Either flash a custom rom that's been updated with the latest security patch
Or flash an official stock firmware but remember the chances of it being the latest security patch is slim
Obviously if your device is not bootloader unlocked you can't flash custom roms - you can flash official stock firmware via fastboot but I wouldn't bother as you will already be on the latest available firmware so just wait for the next ota update to arrive
Click to expand...
Click to collapse
See this thread ...
https://forum.xda-developers.com/moto-g7/help/ota-rooted-phone-t3956012
I copied out the important parts..
1. Download the latest firmware.
2. Install adb & fastboot
3. Flash with these commands:
Code:
fastboot getvar max-sparse-size
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 dtbo dtbo.img
fastboot flash logo logo.bin
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
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
DO NOT RUN THIS ONE ---- fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
you will then need to patch boot with magisk again.

TheFixItMan said:
Either flash a custom rom that's been updated with the latest security patch
Or flash an official stock firmware but remember the chances of it being the latest security patch is slim
Obviously if your device is not bootloader unlocked you can't flash custom roms - you can flash official stock firmware via fastboot but I wouldn't bother as you will already be on the latest available firmware so just wait for the next ota update to arrive
Click to expand...
Click to collapse
The latest for the xt1962-1 retail is the August security patch. That's pretty good considering Lenovomoto.

I hit the notice for the June 1, 2019. Failed to install. Tried using the Lenovo Moto Smart Assistant and it bricked my phone. Now have to wait on Motorola to send a replacement. Very frustrated right now. WTF an OTA failed and the LMSA bricked the phone. SMH...

Don't try to apply the updates or LSMA without locking the bootloader (again) first. Afterwards unlock and reroot using same method as before. I'm sure there will be plenty of full wipes so back up accordingly.

zenful said:
Don't try to apply the updates or LSMA without locking the bootloader (again) first. Afterwards unlock and reroot using same method as before. I'm sure there will be plenty of full wipes so back up accordingly.
Click to expand...
Click to collapse
Locking the bootloader is not a cinch either.
Makes you wonder if the safest course might not be to just ignore the updates and stay with the android version you have.
Which is more dangerous, staying with the 'not-updated' working phone or trying to update and risking a bricked phone?

maybeme2 said:
Locking the bootloader is not a cinch either.
Click to expand...
Click to collapse
From my understanding, you need a signed/original boot.img that of which if you didn't make a backup of yours before rooting, than the LSMA can help. I'm thinking removing Magisk and full factory resetting will be necessary as well.
As for obtaining a copy of a signed/official boot.img
sd86 said:
Head on over to https://support.lenovo.com/us/en/downloads/ds101291 and download the tool, after installed put your phone in bootloader/fastboot mode and go through the rescue steps up until the firmware is downloaded, do not click rescue after the firmware is fully downloaded just head on over to C:\ProgramData\LMSA\Download\RomFiles and open the downloaded firmware and take the boot image from there and copy it to your fastboot tools folder and flash that boot.img check that the firmware matches the version installed on your phone before flashing the boot.img.
Click to expand...
Click to collapse
About the
fastboot oem lock
Click to expand...
Click to collapse
skuppej said:
The trick is to run `fastboot oem lock` 3x (not 2x) before flashing boot.img, and then run `fastboot oem lock` one last time after this is done.
Click to expand...
Click to collapse
(Above info found in this thread about relocking the bootloader)
maybeme2 said:
Which is more dangerous, staying with the 'not-updated' working phone or trying to update and risking a bricked phone?
Click to expand...
Click to collapse
I can't give you a definite answer, but the way I perceive this is;
Should I keep a version of my OS that does not have the most recent security updates but has been rooted?
Click to expand...
Click to collapse
I hope this info helps and brings some clarity for you.

zenful said:
Don't try to apply the updates or LSMA without locking the bootloader (again) first. Afterwards unlock and reroot using same method as before. I'm sure there will be plenty of full wipes so back up accordingly.
Click to expand...
Click to collapse
Phone was locked and not rooted. It's now FUBAR and Moto is sending me a replacement.