Database Users

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

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.

[Guide] Relock Oreo bootloader, go back to stock ROM and get OTA

This method is only works, if you are in Oreo
unlocked bootloader, and use custom rom,
DISCLAIMER
Not taking responsibility if it goes wrong
We have found a way to get back to stock, and relock the bootloader! for now, it only works for the XT-1635-02 because we dont have a signed stock image for any other phone model.
you can use this on any software channel!
How it works.
YOU NEED TO BE ON A CUSTOM ROM TO RELOCK THE BOOTLOADER!
1 - Download Stock ROM in the first post down below
2 - install adb minimal fastboot
3 - after install adb minimal fastboot, go to the install location and paste all the files there
5 - Copy all commands how is in this site and past it on the cmd screen and wait. (you need to press enter for the last command)
Stock Oreo Signed ROM
If u are in June bootloader Kindly use June Security Patch rom, otherwise, phone should be Brick
June Security Patch
Commands
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 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 system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash boot boot.img
fastboot oem lock
Now youre phone will reboot, and your phone is locked again.

I'm using this ROM here:
[ROM][Stock+] [7.1.1] Dec. Patch NPNS26.118-22-2-12 Prerooted
https://forum.xda-developers.com/moto-z-play/development/rom-nov-patch-npns26-118-22-2-8-t3717037
Do I need to perform any procedures before starting this installation?

I think fast boot erase modemmst 1 & 2 may get a result of IMEI 0 error.

talktosam said:
DISCLAIMER
Not taking responsibility if it goes wrong
We have found a way to get back to stock, and relock the bootloader! for now, it only works for the XT-1635-02 because we dont have a signed stock image for any other phone model.
you can use this on any software channel!
Click to expand...
Click to collapse
talktosam said:
So how does this differ from the method below that was posted here months ago by someone else on doing the same thing? Looks like you copied and pasted....
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
Click to expand...
Click to collapse

Jimi Mack said:
talktosam said:
DISCLAIMER
Not taking responsibility if it goes wrong
We have found a way to get back to stock, and relock the bootloader! for now, it only works for the XT-1635-02 because we dont have a signed stock image for any other phone model.
you can use this on any software channel!
Click to expand...
Click to collapse
talktosam said:
So how does this differ from the method below that was posted here months ago by someone else on doing the same thing? Looks like you copied and pasted....
Yes, text is copied, but rom is different Oreo... procedure is same...
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
Click to expand...
Click to collapse
Click to expand...
Click to collapse

talktosam said:
Thanks for clearing that up. So the older was to fully restore to Nougat and yours it to restore to Oreo. So being I never updated to Oreo I should restore with the old file, as I am sure yours would cause issues being I never updated to Oreo. You should clearly document that in the thread as well and not just the Title as well if this is the case. Just because most people do not thoroughly read but skim quickly and then jump without looking.
Click to expand...
Click to collapse

Jimi Mack said:
talktosam said:
Thanks for clearing that up. So the older was to fully restore to Nougat and yours it to restore to Oreo. So being I never updated to Oreo I should restore with the old file, as I am sure yours would cause issues being I never updated to Oreo. You should clearly document that in the thread as well and not just the Title as well if this is the case. Just because most people do not thoroughly read but skim quickly and then jump without looking.
Click to expand...
Click to collapse
Yes, if you are in 0xC182 Oreo bootloader, in title i mentioned its works only if u are in oreo bootloader unlocked
Click to expand...
Click to collapse

Can I use this tutorial if I have 0xC114 bootloader (february patch)???

gercdgcat said:
Can I use this tutorial if I have 0xC114 bootloader (february patch)???
Click to expand...
Click to collapse
Yes, but u are in custom rom, u can,

I was in AOSP 8.1 with Oreo bootloader (I had stock oreo before installing the ROM) and just did this procedure, everything went fine ! IMEI is safe and system works as intended, thank you !

If I have the bootloader blocked and I want to update to OREO with your tutorial which commands would I have to skip?

Dude you are a lifesaver..
---------- Post added at 12:32 PM ---------- Previous post was at 12:30 PM ----------
Mario3DS said:
I was in AOSP 8.1 with Oreo bootloader (I had stock oreo before installing the ROM) and just did this procedure, everything went fine ! IMEI is safe and system works as intended, thank you !
Click to expand...
Click to collapse
I am in the exact same situation as you. I will give this a try and report

djdelarosa25 said:
Dude you are a lifesaver..
---------- Post added at 12:32 PM ---------- Previous post was at 12:30 PM ----------
I am in the exact same situation as you. I will give this a try and report
Click to expand...
Click to collapse
Just do exactly what OP says and everything will be fine, I even recovered my Software Channel (attmx) somehow
oh and btw, you can "fix" the navbar bug in stock Oreo changing the theme with Custom Navigation Bar (it's an app)
I just did it and it fixed it completely

Mario3DS said:
Just do exactly what OP says and everything will be fine, I even recovered my Software Channel (attmx) somehow
oh and btw, you can "fix" the navbar bug in stock Oreo changing the theme with Custom Navigation Bar (it's an app)
I just did it and it fixed it completely
Click to expand...
Click to collapse
Your software channel isn't supposed to change anyway

Safety net failed, help
CTS profile match only failed. Is it because of unlocked bootloader?

The bootloader unlocked screen doesn't seem to want to go away
EDIT: My bootloader is still unlocked.
EDIT: Fixed. It wasn't mentioned that you need to enable OEM unlocking in Developer options, noobs like me might get confused. Lucky I got that sorted out

djdelarosa25 said:
The bootloader unlocked screen doesn't seem to want to go away
EDIT: My bootloader is still unlocked.
EDIT: Fixed. It wasn't mentioned that you need to enable OEM unlocking in Developer options, noobs like me might get confused. Lucky I got that sorted out
Click to expand...
Click to collapse
So... Now are you in Oreo stock with locked bootloader? In boot image only shows motorola logo? Nothing of bad key or any notification?

gercdgcat said:
So... Now are you in Oreo stock with locked bootloader? In boot image only shows motorola logo? Nothing of bad key or any notification?
Click to expand...
Click to collapse
Yup, 100% stock. No more bootloader warning message. The guide did not mention that within the custom ROM that you are using, you must have OEM Unlocking under Developer options turned on before you flash the commands.

djdelarosa25 said:
Yup, 100% stock. No more bootloader warning message. The guide did not mention that within the custom ROM that you are using, you must have OEM Unlocking under Developer options turned on before you flash the commands.
Click to expand...
Click to collapse
I think OEM Unlocking only exists in the stock ROM. Regardless of whether you're on a stock ROM already or are flashing the stock ROM, as you mentioned, OEM unlocking must be turned on for the OEM locking commands to work.
Of course, with re-locking your bootloader, it's up to you if you wish to keep OEM Unlocking enabled or disabled afterwards. If you disable it, your device will not be unlockable until you boot into system, which can be more secure but if you have any boot issues, then troubleshooting is a lot more difficult, plus you have no warranty. If you leave OEM unlocking on, then you could unlock your bootloader, but then so can anyone else with physical access to your device.

echo92 said:
I think OEM Unlocking only exists in the stock ROM. Regardless of whether you're on a stock ROM already or are flashing the stock ROM, as you mentioned, OEM unlocking must be turned on for the OEM locking commands to work.
Of course, with re-locking your bootloader, it's up to you if you wish to keep OEM Unlocking enabled or disabled afterwards. If you disable it, your device will not be unlockable until you boot into system, which can be more secure but if you have any boot issues, then troubleshooting is a lot more difficult, plus you have no warranty. If you leave OEM unlocking on, then you could unlock your bootloader, but then so can anyone else with physical access to your device.
Click to expand...
Click to collapse
OEM unlocking also exists in custom ROMs. The reason that relocking your bootloader is not possible with the stock ROM is that the option is greyed out if you have your bootloader unlocked, thus making the bootloader lock commands not work. With a custom ROM, I was able to toggle OEM unlocking on, even when my bootloader was already unlocked. This allowed the bootloader lock commands to work and make the warning message disappear.

Help required (if possible) for an idiot

Hi All:
I have been running Pixel Experience 8.1 custom rom on my moto G5 plus and have decided I want to stick the stock rom back on and lock the bootloader. Alas I cannot as Any versions of oem.ini etc are lower than the version in Pixel and I cannot downgrade. Can anyone recommend a way round this or am I stuck until the 8.1 official OTA files become available?
Many thanks

phoenix40uk said:
Hi All:
I have been running Pixel Experience 8.1 custom rom on my moto G5 plus and have decided I want to stick the stock rom back on and lock the bootloader. Alas I cannot as Any versions of oem.ini etc are lower than the version in Pixel and I cannot downgrade. Can anyone recommend a way round this or am I stuck until the 8.1 official OTA files become available?
Many thanks
Click to expand...
Click to collapse
Well i was using ArrowOS 9.0 Pie and then I moved to stock and locked my bootloader again. You just need the firmware files. You cannot downgrade so use one of the latest files. I didn't remember on which firmware I was bt while locking the bootloader i used the 137.92-14 and it worked perfectly.

debdeep98 said:
Well i was using ArrowOS 9.0 Pie and then I moved to stock and locked my bootloader again. You just need the firmware files. You cannot downgrade so use one of the latest files. I didn't remember on which firmware I was bt while locking the bootloader i used the 137.92-14 and it worked perfectly.
Click to expand...
Click to collapse
Alas that doesn't work for me. I installed the 137.93-10 firmware then reboot into fastboot and try to run
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
but I cannot flash any of the files as I get Security version downgrade errors .

phoenix40uk said:
Alas that doesn't work for me. I installed the 137.93-10 firmware then reboot into fastboot and try to run
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
but I cannot flash any of the files as I get Security version downgrade errors .
Click to expand...
Click to collapse
Do you have the nougat backup files? Did you make any backups? Or try flashing nougat stock zip first then try locking the bootloader. Which firmware were you on when you unlocked?

debdeep98 said:
Do you have the nougat backup files? Did you make any backups? Or try flashing nougat stock zip first then try locking the bootloader. Which firmware were you on when you unlocked?
Click to expand...
Click to collapse
I don't have any backup files but I have the installer for the stock version I mentioned above which is Android 7. I can Flash back to 7 usng the adb push method but I cannot relock my boot loader. Based on that I reckon I must have unlocked the bootlocker while on an Oreo custom.

https://forum.xda-developers.com/g5...flashable-stock-builds-coming-t3830482/page35
New stock oreo firmwares.

dokwhoo said:
https://forum.xda-developers.com/g5...flashable-stock-builds-coming-t3830482/page35
New stock oreo firmwares.
Click to expand...
Click to collapse
sorted after updating to Oreo. Many thanks

phoenix40uk said:
sorted after updating to Oreo. Many thanks
Click to expand...
Click to collapse
i am also on pixel experience and want to go back to stock,
so did u flashed those twrp builds or did something else.

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.