How to Relock Bootloader Moto G4 Plus...
Using Fast boot
And only Relock the Bootloader Don't Replace the Stock ROM....
Please Help....
How to Relock Bootloader Moto G4 Plus
Download firware from here
drive[dot]google[dot]com/open?id=0B6TKJzgog8cjYWZseC1JSTBDd1k
now flash this Official Rom using fastboot by entering following commands.
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 method is replaced the Stock ROM
And I need only Relock Bootloader
Jayesh143 said:
This method is replaced the Stock ROM
And I need only Relock Bootloader
Click to expand...
Click to collapse
You can only lock it if you have OEM image flshed into the system, which, by default requires all of the commands to be executed and will restore the OEM. You cannot lock it with custom ROM
my boot-loader was unlock in another pc and now i want to relock it but i dont have any files what should i do?
piyu8897 said:
my boot-loader was unlock in another pc and now i want to relock it but i dont have any files what should i do?
Click to expand...
Click to collapse
Just download the files and relock the bootloader. You can do this from any PC.
Related
if i relock my bootlader with cmd flashing stock rom and oem lock than i get error your device has failed verification and may not work properly
than i tried with moto tool than it says device unlock and annot be trusted
pls help me i want to relock bootloader
Try the following commands, they worked for me. On my device no more bootloader unlocked warning-
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
i have moto g4 play.. unlocked bootloader,twrpinstalled,lineage 14.1 installed. but now iwant to rollback to my original firmware. and want to lock my bootloader( dont care og my warranty). how to do this
Here's a guide: https://forum.xda-developers.com/g4-play/how-to/guide-return-to-stock-firmware-recovery-t3551797
As for the bootloader, I'm not sure if it can be relocked
fireball0093 said:
Here's a guide: https://forum.xda-developers.com/g4-play/how-to/guide-return-to-stock-firmware-recovery-t3551797
As for the bootloader, I'm not sure if it can be relocked
Click to expand...
Click to collapse
It can, but it won't remove the "bootloader locked" boot logo and the status code will be 2 instead of 1 (stock).
look here:
https://forum.xda-developers.com/showpost.php?p=68487371&postcount=28
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
i tried it with fastboot oem lock begin and fastboot oem lock but it was not working...checksum fails....
sgace2 said:
look here:
https://forum.xda-developers.com/showpost.php?p=68487371&postcount=28
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
i tried it with fastboot oem lock begin and fastboot oem lock but it was not working...checksum fails....
Click to expand...
Click to collapse
I will try
bsevcenk said:
It can, but it won't remove the "bootloader locked" boot logo and the status code will be 2 instead of 1 (stock).
Click to expand...
Click to collapse
Any way to get stock boot logo
Akash Sharma123 said:
Any way to get stock boot logo
Click to expand...
Click to collapse
see https://forum.xda-developers.com/g4-play/help/stock-boot-logo-unlocked-bootloader-t3566139 specifically the reply by @bsevcenk at https://forum.xda-developers.com/showpost.php?p=71257130&postcount=2
Worked for me.
Was it sucsess full? Is the Boot loader locked again?
In these months i am using LTE. But today i am in rural area so I wish to use 2g/3g. But i face problems.. those who are familior with motorola mobiles.. they watch that type of connection shown after the network.. when i am using the network ... E is workinh great. H is working great. But after few minutes it switched to 3g and intenet won't connect. But its showing 3g but not connecting. Whats the problem. Anyone has any solution
sgace2 said:
Was it sucsess full? Is the Boot loader locked again?
Click to expand...
Click to collapse
The bootloader not locking.. it saying to flash signed files.but i am already flashing original factory stock images
My questions are at bottom.
Context:
I recently tried to go back to my stock from lineageos. I successfully did it through this youtube video but I've run into a couple of problems.
Youtube Video Titled: MOTO G5 PLUS STOCK ROM FLASHING | UNBRICK/UNROOT MOTO G5 PLUS
(I'm not allowed to post links)
I used firmware NPN25.137-35
after I flashed twrp, no-verity-check and magisk v14
After mistakenly tried to apply an OTA update(I know better now) my phone always boots into recovery. I discovered this when the updated tried to restart to install. I have to boot to bootloader and press the power button when the selection is on "start". I'm not sure if the OTA had anything to do with that.
The fastboot commands I used where this to install the stock ROM
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
Questions:
1. If I want to download the stock image directly from the "firmware.center" which one do I choose and how do I know? There are 9 of them..
2. Do I ever need to unlock my bootloader again or is that a one time thing?
3. Do those fastboot commands and the stock image bring my moto g5 plus back to the way it was completely when I unpackaged it (minus unlocked bootloader)?
4. Can I run those fastboot commands without unzipping the stock *.xml.zip?
5. Where did these commands come from? Is it common knowledge that they work? Or is a fastboot sequence provided by motorola?
6. Does "just" attempting an OTA update mess stuff up on a rooted android?
So I wanted to revert back from lineage OS 14.1 to stock and do all the stock ROM OTA updates to oreo. After flashing retail 137-35 it would not properly update boot.img during that process and would not relock bootloader.
It booted fine though and stock ROM immediately OTA updated each of the following:
137-35-5
137-83
137-93
137-93-4
137-93-8
137-93-10
137-93-14
137-93-18
I'm getting close to the oreo update patch w/ an open bootloader. Is there a concern here? I know the oreo updates have been causing problems for some. Do I need to stop the updates?
badtlc said:
So I wanted to revert back from lineage OS 14.1 to stock and do all the stock ROM OTA updates to oreo. After flashing retail 137-35 it would not properly update boot.img during that process and would not relock bootloader.
It booted fine though and stock ROM immediately OTA updated each of the following:
137-35-5
137-83
137-93
137-93-4
137-93-8
137-93-10
137-93-14
137-93-18
I'm getting close to the oreo update patch w/ an open bootloader. Is there a concern here? I know the oreo updates have been causing problems for some. Do I need to stop the updates?
Click to expand...
Click to collapse
It's pretty normal to get OTA updates with an unlocked bootloader, Motorola itself gives you the unlock key. It's a common misconception that the BL status has anything to do with OTA.
Only rooting, twrp and any change in system or vendor prevents the update process.
Just being on untouched stock firmware incl stock recovery and boot.img is enough.
You can install the updates if that's the case for you.
Wolfcity said:
It's pretty normal to get OTA updates with an unlocked bootloader, Motorola itself gives you the unlock key. It's a common misconception that the BL status has anything to do with OTA.
Only rooting, twrp and any change in system or vendor prevents the update process.
Just being on untouched stock firmware incl stock recovery and boot.img is enough.
You can install the updates if that's the case for you.
Click to expand...
Click to collapse
I dont think the stock boot.img every wrote properly and I cannot seem to get the bootloader locked no matter what I do. Is there a way to verify everything really is stock?
badtlc said:
I dont think the stock boot.img every wrote properly and I cannot seem to get the bootloader locked no matter what I do. Is there a way to verify everything really is stock?
Click to expand...
Click to collapse
Try locking again with the updated firmware. If the boot.img failed to write then it would have shown error in cmd.
badtlc said:
I dont think the stock boot.img every wrote properly and I cannot seem to get the bootloader locked no matter what I do. Is there a way to verify everything really is stock?
Click to expand...
Click to collapse
Agree, if there was no error in the fastboot log it was ok. If you want to relock the bootloader (there's no good reason for it unless you want to sell the device) here are the locking and flashing commands. You need the exact same firmware you're on for locking!
For Oreo the whole sets of commands are for
Locking:
-----------------
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4 fastboot flash system system.img_sparsechunk.5 fastboot flash system system.img_sparsechunk.6 fastboot flash system system.img_sparsechunk.7 fastboot flash system system.img_sparsechunk.8
fastboot flash boot boot.img
fastboot oem lock
-------------------
Flashing:
-------------------
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0 fastboot flash system system.img_sparsechunk.1 fastboot flash system system.img_sparsechunk.2 fastboot flash system system.img_sparsechunk.3 fastboot flash system system.img_sparsechunk.4 fastboot flash system system.img_sparsechunk.5 fastboot flash system system.img_sparsechunk.6 fastboot flash system system.img_sparsechunk.7 fastboot flash system system.img_sparsechunk.8 fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
-----------------------------------
The same commands for Nougat:
Flashing:
-----------------------------------
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
--------------------------
Locking:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
I will try those. They look very similar to what I tried already. I always got a fastboot write error for the boot.img and of course the can't OEM lock error.
If the boot.img didn't write properly, would I even be able to boot into the stock ROM? The fact it is working just has me paranoid I'm missing something and about to brick my phone by mistake.
badtlc said:
If the boot.img didn't write properly, would I even be able to boot into the stock ROM?
Click to expand...
Click to collapse
No
Hi, I need help since 1 week ago I unlocked my bootloader and install HavocOS, but in the end I did not like it and decided to go back to the Stock ROM and block my Bootloader (All for ADB) but when I try, the Bootloader does not block, before if it worked for me but in this last situation, no, does anyone know what it could be? The Stock version that I try to install is 8.1.0, February patch. I want to block my Bootloader to be calmer. Thank you.
JuanM28 said:
Hi, I need help since 1 week ago I unlocked my bootloader and install HavocOS, but in the end I did not like it and decided to go back to the Stock ROM and block my Bootloader (All for ADB) but when I try, the Bootloader does not block, before if it worked for me but in this last situation, no, does anyone know what it could be? The Stock version that I try to install is 8.1.0, February patch. I want to block my Bootloader to be calmer. Thank you.
Click to expand...
Click to collapse
Why? What's the advantage of a locked bootloader?
If you want to lock it:
Commands to flash stock (Oreo!) ROM:
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
Commands to relock the bootloader:
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
Sent from my Moto G5 Plus using XDA Labs