I'm trying to get one of my E4's ready to sell (I have two of them) and need to relock the bootloader so that the N/A message goes away. I reinstalled the stock firmware provided here using fastboot (and followed the appropriate oem locking steps) but at the very end I get:
Code:
Still require signed boot.img
I am assuming nobody has found a workaround for this as Lenovo hasn't provided official stock firmware and I haven't seen any posts about a solution? Would appreciate any insight.
Not possible currently, just let the buyer know that the bootloader is unlocked and it's root ready lol.
Is it still currently not possible to relock the bootloader?
AZImmortal said:
Is it still currently not possible to relock the bootloader?
Click to expand...
Click to collapse
fastboot oem lock_bootloader
Then go to Motorola.com grab a stock image
Fastboot flash boot boot.img and everything else too.
Fastboot flash
bootloader
oem
Boot
Logo
system
Etc....
I did this and had to use my code that they emailed me to unlock the boot loader again.
OEM unlock & usb debugging both are enabled in developer option... but giving same error, FAILED(remote:unknown command)
Follow the procedure as shown in the thread
Just try to flash with older stock firmware using SP Flash Tool.
I had a similar problem and the older firmware gave it up unlock bootloader without any problem.
When unlocking with fastboot keep the order:
fastboot oem unlock
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot format userdata
Please change name of twrp-3xx....img to twrp.img
how to see unlock key when our devices unlocked motorola e4plus
Code:
plcrazyprogrammer said:
Just try to flash with older stock firmware using SP Flash Tool.
I had a similar problem and the older firmware gave it up unlock bootloader without any problem.
When unlocking with fastboot keep the order:
fastboot oem unlock
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot format userdata
Please change name of twrp-3xx....img to twrp.img
Click to expand...
Click to collapse
I am trying to relock the bootloader in adb terminal by using command fastboot oem lock I get a message during boot stating that the system has been destroyed and boot loop.
How to relock bootloader with out flashing stock rom
Thanks in advance ?
Vishal21896 said:
I am trying to relock the bootloader in adb terminal by using command fastboot oem lock I get a message during boot stating that the system has been destroyed and boot loop.
How to relock bootloader with out flashing stock rom
Thanks in advance
Click to expand...
Click to collapse
use reflash tutorial from this site:
HTML:
https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
. Just download tool, extract, then exctract downloaded rom in this tool folder. Conect A1 in fastboot and start flash_all_lock.bat file in folder with room (I used flash_all.bat). This is how I fixed my bootlops...
You need to reflash. There's no other way.
Did you have the original stock Oreo with January security patch?
I would also like to re-lock the bootloader but now I have read your post I am unsure if its safe.
Use this command in adb
fastboot oem relock (your unlock code if needed)
Youssef Reda said:
Use this command in adb
fastboot oem relock (your unlock code if needed)
Click to expand...
Click to collapse
If I enter fastboot oem relock with MagiskManager or Magisk 15.3 installed, will I brick the phone?
amzazine said:
If I enter fastboot oem relock with MagiskManager or Magisk 15.3 installed, will I brick the phone?
Click to expand...
Click to collapse
Maybe
I didn't try it but it may brick your phone
Developers should make clear that Re-locking the bootloader is not as easy as the unlock process and there is a high risk you will brick your phone.
i just have this issue ,which is i unlock then i lock the oem and then the message ' system has been destroyed ' and when i try to unlock back the message 'error: oem unlock is not allowed' so i really need your help ..how can i fix my phone ...plsss send a respond quickly
I wanted to relock the bootloader of my Moto G4 Plus as now I'm in no need of root now. And even want to remove the logo which says my bootloader is unlocked.. I used the code but it is not working still pls help me out
i think you are in the wrong section but nvm. for removing the annoying boot logo you can flash the logo bin
Code:
fastboot flash logo logo.bin
in fastboot mode where "logo.bin" is the filename.bin. you can find the logos at this link
https://forum.xda-developers.com/moto-g4-plus/themes/customized-logo-t3451349
or if you want some more cooler ones just search around.
Now comes to relocking bootloader, you must give more info(what phone you are using) and from where you got the link and what commands you pressed. you can follow this link which uses dec update or (if you check last messages even the feb update though i would recommend dec)
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
and then use the commands given in the code OR the
Code:
OEM Lock file
abhishikth reddy said:
I wanted to relock the bootloader of my Moto G4 Plus as now I'm in no need of root now. And even want to remove the logo which says my bootloader is unlocked.. I used the code but it is not working still pls help me out
Click to expand...
Click to collapse
You may falsh stock rom again in starting write command
fastboot oem lock begain
And at last
fastboot oem lock
it will work
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.