Database Users

How can I relock Bootloader?

I need to relock my bootloader and it won't do so. I have tried Fastboot oem lock and it says it finishes it but changes nothing on the device. I need to return, PLEASE HELP!

jdellingson7 said:
I need to relock my bootloader and it won't do so. I have tried Fastboot oem lock and it says it finishes it but changes nothing on the device. I need to return, PLEASE HELP!
Click to expand...
Click to collapse
Why do you need to return?

I bought the 16gb because I couldn't not find a 32gb anywhere. Amazon had the 32 available yesterday so I bought one

You can lock it back up. However it will still give you the unlocked bootloader screen, and it will show status 2 in the bootloader menu.
There is no way to reset it without leaving flags that it was unlocked
Sent from my Nexus 6 using Tapatalk

I wouldn't worry about it, if I were you. Flash the stock logo.bin, relock it, and don't worry about what it says in the recovery menu. I'm not making any promises, but that's the way I would play it.

jaben2 said:
You can lock it back up. However it will still give you the unlocked bootloader screen, and it will show status 2 in the bootloader menu.
There is no way to reset it without leaving flags that it was unlocked
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Is there a physical fuse that pops a la modern Samsung phones? Or are we still waiting for developers to figure out how to reset the flags on this particular model? I know that I've seen threads for other devices that walk you through resetting flags, so if it is only done with software on this device, we should be able to restore to 100% stock soon enough.

Here is Motorola's page on re-locking:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Unfortunately they don't have the stock image available yet for the Moto X 2015 (scroll down).
I'm returning mine due to a damage claim and wanted to re-lock but we can't yet, at least officially. Moto still records when you unlocked, now listed under 'My Support History' in my Profile, so there's no way to hide that you unlocked if you did it through their site. The good news is it didn't affect my warranty claim in talking to a few support staff, and of course made sure not mention it myself but nobody there brought it up, so I tend to doubt it will affect your return. I did use the Restore to Stock tool (worked great!) and then removed the Unlocked warning, so it's just as if it had a factory reset.

I just relocked mine, no white screen on boot.
but it says
Device is LOCKED. Status Code: 2
Software status: Modified
Here's how I did it.
download this
open cmd, navigate to the folder extracted from the zip in the link above, this will erase your entire phone, reset to stock firmware and relock the bootloader
boot into bootloader pwr+vol down
run these commands
Code:
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
Now If I can figure out how to remove the status code and make the software status official.
It's probably impossible, for now at least.

Thanks this worked but it didn't remove the bootloader unlock warning. So I just flashed the boot logo and it's good to go. I'm pretty sure Best Buy is no educated on these things.
tylerwatt12 said:
I just relocked mine, no white screen on boot.
but it says
Device is LOCKED. Status Code: 2
Software status: Modified
Here's how I did it.
download this
open cmd, navigate to the folder extracted from the zip in the link above, this will erase your entire phone, reset to stock firmware and relock the bootloader
boot into bootloader pwr+vol down
run these commands
Code:
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
Now If I can figure out how to remove the status code and make the software status official.
It's probably impossible, for now at least.
Click to expand...
Click to collapse

jdellingson7 said:
Thanks this worked but it didn't remove the bootloader unlock warning. So I just flashed the boot logo and it's good to go. I'm pretty sure Best Buy is no educated on these things.
Click to expand...
Click to collapse
Lol I'll be very surprised if someone knows lol. Most of them probably use iPhone anyway. It feels good being a geek ?

if they can change the software status on an M9 i see no reason why they couldn't on the MXP

jdellingson7 said:
Thanks this worked but it didn't remove the bootloader unlock warning. So I just flashed the boot logo and it's good to go. I'm pretty sure Best Buy is no educated on these things.
Click to expand...
Click to collapse
I tried flashing the logo.bin, but that didn't replace the bootloader unlock warning. Where did you get the boot logo to replace the warning and to what partition did you flash it?

http://forum.xda-developers.com/mot...o-remove-unlocked-bootloader-warning-t3201141
Tanker Bob said:
I tried flashing the logo.bin, but that didn't replace the bootloader unlock warning. Where did you get the boot logo to replace the warning and to what partition did you flash it?
Click to expand...
Click to collapse

jdellingson7 said:
http://forum.xda-developers.com/mot...o-remove-unlocked-bootloader-warning-t3201141
Click to expand...
Click to collapse
Thank you! That worked perfectly.

Good deal, sending mine back this week this will come in handy

Just to let you know, I returned mine unlocked. Unlocked has more to do with warranty claims, it doesn't void returns. That's a mandated law. Moto will just relock it and restore it to stock.
Sent from my Nexus 7 (2013) using XDA Free mobile app

sent mine back, wasn't completely locked, still had the flag set. I got my money back, just wanted to let everyone know.

Will this restore the stock bootloader as well? In rooting mine it called for installing twrp...so wondering if this is a method back to complete stock?
Also, anyone know if rooted twrp will get ota's?

mcdonsco said:
Will this restore the stock bootloader as well? In rooting mine it called for installing twrp...so wondering if this is a method back to complete stock?
Also, anyone know if rooted twrp will get ota's?
Click to expand...
Click to collapse
The email you get with the unlocked bootloader contract says no OTA's
tylerwatt12 said:
sent mine back, wasn't completely locked, still had the flag set. I got my money back, just wanted to let everyone know.
Click to expand...
Click to collapse
nikeman513 said:
Just to let you know, I returned mine unlocked. Unlocked has more to do with warranty claims, it doesn't void returns. That's a mandated law. Moto will just relock it and restore it to stock.
Sent from my Nexus 7 (2013) using XDA Free mobile app
Click to expand...
Click to collapse
I'm returning mine as well and was stressing over this my bootloader being unlocked. Thank you both for your feedback on what happened after you returned it. People tend to forget to give details about the outcome on threads like this. So I give :good::good: to you guys

Don't worry too much about the unlocked bootloader status messages, especially if you flash the logo.bin to remove the giant notice on bootup.
When you return a phone, the RMA department is interested in just processing the return as fast as possible, and moving on to the next return. They are not in the business of checking every single individual device for voided warranties, for purposes of playing "gotcha" to find reasons to reject a return.
The fact of the matter is that it is a very small minority of people that will unlock / root a phone, and return it. And an even smaller portion of that minority that cause warranty-vouding damage as a result of those software-related changes.
Will there be people that abuse this return policy, and process illegitimate returns? Yes, of course. But it will cost Motorola (or Amazon) more time/money to individually check each return for voided warranties, than it would to just process the RMA as fast as possible and move on.
Sometimes, even if you KNOW people are stealing from you, it's still cheaper to just let then steal, than to take the time to try and stop that theft.
Sent from my XT1575 using Tapatalk

Complicated problem, never came across in the whole lifetime of my android usage.

TLR: Phone boots up and says. Launcher has stopped working, contacts has stopped working and etc.
Ok so i bought Moto G4 XT1625, yesterday. Was very happy with the device. It came with Android 6.0.1, i updated it to nougat 7.0.
But in android 6.0 and 7.0 both i noticed the phone giving random apps freezes and randomly even restarting on 7.0. The problem was minimal so i rebooted the phone 2,3 times and made it working. Then i received another update "NPJS25.93-14-4" on that update the phone got successful but bootlooped when booting for the first time on that update. I thoughts its ok so rebooted to bootloader and booted the phone from bootloader. the phone booted. after that another update came "NPJS25.93-14- (5 or 8) i dont remember properly" in this update the update failed during the installation. Keep in mind that i did not touch anything before this update. The phone was totally stock with stock recovery and everything. On this update the phone failed the update and i got constant bootloop no matter if i factory reset or erase cache it kept bootlooping, now i unlocked the bootloader and installed twrp and flashed a custom stock rom it crash on the boot. Again the random app has stopped working error came continously making the phone unusable. Then i flashed the stock rom correct firmware and everything it bootlooped again, then i rebooted numerous times the phone booted fine. Installed apps. This time did not get any app has stopped working error. Then rebooted the phone to install the sim card phone bootlooped again. Im 99% sure this is a hardware issue. Can somebody enlighten me? Whats going on in here? Thanks. I never faced this kind of problem ever in my life, i have bought more than 100 devices.

@whizinc
The Story is really frustrating especially when you bought it new :laugh:
So let's try to get your device working!
since you unlocked the bootloader you should clean flash the stock rom with fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and see what happens. Don't put sim cards in and disable wifi. Just flash, boot and play around to see if it works without reboot.

strongst said:
@whizinc
The Story is really frustrating especially when you bought it new :laugh:
So let's try to get your device working!
since you unlocked the bootloader you should clean flash the stock rom with fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and see what happens. Don't put sim cards in and disable wifi. Just flash, boot and play around to see if it works without reboot.
Click to expand...
Click to collapse
I used the OEMLock.bat script. So far the phone booted first time properly without any issue. Sim is working as well. Current its on setup wizard checking network. Lets hope its fixed permanently. I will play with the phone for 5,10 hours constantly and report back. Thanks alot man!

whizinc said:
I used the OEMLock.bat script. So far the phone booted first time properly without any issue. Sim is working as well. Current its on setup wizard checking network. Lets hope its fixed permanently. I will play with the phone for 5,10 hours constantly and report back. Thanks alot man!
Click to expand...
Click to collapse
Good luck:good:

UPDATE
It did not get past the "Checking Network" thing and after pressing the power button screen went black but i could see nav bar and status bar only. The phone has faulty hardware. Im now sure. Going to get it back tomorrow from where i bought it. Lets hope i get a refund or replacement. I bought it from a local mobile mall.

strongst said:
Good luck:good:
Click to expand...
Click to collapse
this phone has faulty hardware. IT failed. Again random apps saying "keeps stop working" such as : snapchat has stopped working

whizinc said:
this phone has faulty hardware. IT failed. Again random apps saying "keeps stop working" such as : snapchat has stopped working
Click to expand...
Click to collapse
Have you installed any third-party apps or restored them?

strongst said:
Have you installed any third-party apps or restored them?
Click to expand...
Click to collapse
nope, not a single app. Everything is clean and properly flashed.

whizinc said:
nope, not a single app. Everything is clean and properly flashed.
Click to expand...
Click to collapse
Snapchat is pre-installed?

strongst said:
Snapchat is pre-installed?
Click to expand...
Click to collapse
You did not get me brother. I was giving an example. Here is a real example:
"Contacts has stopped working"
".com android process keeps stopping"
these are the random errors.

whizinc said:
You did not get me brother. I was giving an example. Here is a real example:
"Contacts has stopped working"
".com android process keeps stopping"
these are the random errors.
Click to expand...
Click to collapse
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?

strongst said:
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
Click to expand...
Click to collapse
posted in a new thread because the problem did not belong to the rom's thread, im sorry did i do something wrong? No. I did not flash the stock custom rom before all of this. I never wanted to flash a custom rom. The thing is the phone failed an OTA update which let me to come to this decision. The phone failed ".5" update and after that it bootlooped. So i thought flashing twrp and flash a custom rom with a clean install would fix it but even the custom rom the " xxx app stopped working error" came continously.
After that i followed echo92's guide and flashed the whole stock rom through fastboot. Still same issue. Random apps crashing.
I think this is hardware issue. Because every idea has been fail till now.
What do u say?
edit: note: when the phone failed ".npj25.93-14-5" update it was completely stock and i did not even touch anything, i dont know why it failed on the first place?

strongst said:
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
Click to expand...
Click to collapse
Yep, I've been tracking the topic over both topics, gonna reply here to keep the other ROM thread clean too As I understand it:
Bought the device, had random issues with apps crashing on MM and Nougat.
Flashed TWRP and accidentally took the OTA, soft bricking in the process.
Flashed J-X's NPJS25.93-14-8 modified stock ROM, still app errors.
Reverted back to stock, still app errors, to the point where the device isn't useable and is now bootlooping...
However, @whizinc it's odd that you're experiencing these errors across flashes of the stock ROM and even a modified stock ROM and the data's been wiped each time...
Can you just confirm that with the NPJS25.93-14-4 (March 2017 fastboot ROM) that the stock ROM was flashed with these instructions as well, given that something odd's happening with your device...
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
The difference is that these include re-flashing your GPT/bootloader (just in case) and also include the equivalent of a factory reset (so effectively a clean install of the stock, unmodified, ROM). I recall you've mentioned doing this, just want to ensure we have a clean slate to work with.
If you can, can you post the output of your flash commands, just want to see if the flash worked, hold fire on updating to NPJ25.93-14.5 for now (or if you want to try your luck, you can get the fastboot file from here - you need to flash it with the above instructions, as it's an upgrade: https://androidfilehost.com/?fid=673368273298984458 )
Else, it may be a hardware failure - when you bought the device, was it new or sold as used? Do you have a warranty with the shop you bought the device from? If you can, can you boot into bootloader, attach your device to your computer, and in the adb terminal, type 'fastboot getvar all' without the quotes, please? This should output a list of the basic details of your device, please post that here - you may wish to edit out your IMEI if you wish.

I have difficulty understanding why someone would void the warranty (by unlocking the bootloader) of a phone that is seemingly defective out if the box. Not a very good idea.

echo92 said:
Yep, I've been tracking the topic over both topics, gonna reply here to keep the other ROM thread clean too As I understand it:
Bought the device, had random issues with apps crashing on MM and Nougat.
Flashed TWRP and accidentally took the OTA, soft bricking in the process.
Flashed J-X's NPJS25.93-14-8 modified stock ROM, still app errors.
Reverted back to stock, still app errors, to the point where the device isn't useable and is now bootlooping...
However, @whizinc it's odd that you're experiencing these errors across flashes of the stock ROM and even a modified stock ROM and the data's been wiped each time...
Can you just confirm that with the NPJS25.93-14-4 (March 2017 fastboot ROM) that the stock ROM was flashed with these instructions as well, given that something odd's happening with your device...
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
The difference is that these include re-flashing your GPT/bootloader (just in case) and also include the equivalent of a factory reset (so effectively a clean install of the stock, unmodified, ROM). I recall you've mentioned doing this, just want to ensure we have a clean slate to work with.
If you can, can you post the output of your flash commands, just want to see if the flash worked, hold fire on updating to NPJ25.93-14.5 for now (or if you want to try your luck, you can get the fastboot file from here - you need to flash it with the above instructions, as it's an upgrade: https://androidfilehost.com/?fid=673368273298984458 )
Else, it may be a hardware failure - when you bought the device, was it new or sold as used? Do you have a warranty with the shop you bought the device from? If you can, can you boot into bootloader, attach your device to your computer, and in the adb terminal, type 'fastboot getvar all' without the quotes, please? This should output a list of the basic details of your device, please post that here - you may wish to edit out your IMEI if you wish.
Click to expand...
Click to collapse
No no, You got the story wrong. Let me make it correct.
1: Bought the phone from a local mobile mall i have 3 days warranty left. (Phone was on Android 6.0 update)
2: Did not touch the phone. Just installed my daily apps. i.e: whatsapp,facebook and stuff.
3hone started doing odd things like auto touch while charging and apps saying "force stopped" error
4:Then i thought that this is Android 6.0 bug on Moto g4, so i should update it via OTA.
5: Updated to 7.0 same issues.
6:I saw another update did it as well 14-4 update. This update caused bootloop but i managed to make it through by booting from bootloader.
7: Then saw another update 14-5 and that update failed. (WHILE THE WHOLE PHONE WAS ON STOCK STATE) Why did the update fail? I didnt even touch the recovery or anything at that time.
8: Then i flashed the custom rom and the rest of the story goes on as u mentioned in the post.
And yes i cleaned flash the rom with the OEMlock.bat script that the guy above gave to me. It included all things such as boot,modem and all stuff. So it was def a clean install.
"fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
fastboot reboot"
This was the script i used to flash the fastboot rom which is 14-4.
Then again got force stop errors and the 14-5 update failed causing bootloop again.
I just have 2 hours to check the devices further or else im gonna return it today. Thanks

MisterSteve said:
I have difficulty understanding why someone would void the warranty (by unlocking the bootloader) of a phone that is seemingly defective out if the box. Not a very good idea.
Click to expand...
Click to collapse
The phone was not in the official warranty from the start lol. I bought it used from a local mobile mall, they give 3 days checking warranty tho. I will try to get another handset. If i cant get it working.

whizinc said:
The phone was not in the official warranty from the start lol. I bought it used from a local mobile mall, they give 3 days checking warranty tho. I will try to get another handset. If i cant get it working.
Click to expand...
Click to collapse
Oh, you didn't mention that you have bought a used device! Bring it back to the shop and buy another/new one. Who knows what's wrong with that device or which history it has...

Apologies for getting the story mixed up, the information you provided in your corrected post and subsequently makes the situation worse though. Sounds like you bought a device exhibiting ghost touching or the beginnings of ghost touch and possibly was hard bricked/had the incorrect firmware flashed previously. As strongst mentioned, return that device. It sounds like it'll be more trouble than it's worth... especially for a used device.

UPDATE
I returned the handset to the shop guy, he was skeptical at first but then he gave it to another guy who said that the phone would go in used market claim and then after that he'll either return me the money or give me a new G4 device. I'll have to wait till monday. It sucks. Anyways Thanks alot guys for the help i appreciate it alot.
Feel free to lock the thread @ moderators.

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.

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.