I just wanted to report that I successfully re-locked my bootloader (did not find that here).
I have an H850 with GPS problems. To return it I wanted it to be as stock as possible.
I used TWRP to flash LG-H85010E-Flashable.COMPLETE.zip from Codefire. Back to unrooted.
I also tried to flash recovery.img from the same source. This seemed to work (no more TWRP), but did not allow for OTAs (update error 0x1125000).
Then I put the phone in download mode, started LG bridge and did the "Updatefehler korrigieren" thing (German, roughly translates to "correct update errors").
To re-lock the bootloader, I put the phone in USB Debugging mode and entered the following commands:
Code:
adb reboot bootlaoder
fastboot oem lock
fastboot reboot
The phone gets wiped by this, but you need to do the initial dialog again: enable developer mode, then go there an disable OEM unlock. After that do a factory data reset one last time.
You should contact @autoprime and have him add this to his all in one thread.
Thanks for the info!
@bornheim2
It's good to see that we have option to turn back to stock, and maybe send phone for warrianty repair. But I have one question... If you had tried to unlock phone once again, would You had to enter LG Unlock Code again?
Hazard17 said:
If you had tried to unlock phone once again, would You had to enter LG Unlock Code again?
Click to expand...
Click to collapse
Obviously. The command to unlock is
Code:
fastboot flash unlock unlock.bin
which means you need to have the unlock.bin file available. You did archive the mail, didn't you?
bornheim2 said:
Obviously. The command to unlock is
Code:
fastboot flash unlock unlock.bin
which means you need to have the unlock.bin file available. You did archive the mail, didn't you?
Click to expand...
Click to collapse
I haven't unlocked my phone yet, but it is important message for me.
bornheim2 said:
Obviously. The command to unlock is
Code:
fastboot flash unlock unlock.bin
which means you need to have the unlock.bin file available. You did archive the mail, didn't you?
Click to expand...
Click to collapse
No I didn't archive the mail
I've got the same problem - seller deceived me and sold phone after water damage. My microphone stopped work and I should send it back. How to lock the bootloader on RS988 model?
Related
It took me about two days to figure out how to unroot and relock my Moto X. Figured I'd create a total noob guide for those who are also looking to do the same. This is for the Verizon Wireless Developer Edition Moto X ONLY! I have no clue if this will work for other variants like Sprint, AT&T, T-Mobile, etc. So just play it safe and don't...
I've unrooted and relocked my VZW Dev Edition Moto X twice using this method, so as long as you follow the steps below you should be fine. Also please note that I'm not at all responsible for anything that happens to your beloved phone.
Btw, this process wipes your phone completely clean, so back your sh** up.
So here goes.
1. You need a Windows PC.
2. Download and install the Motorola Device Manager (USB Drivers) to your PC. This will allow your Moto X to be recognized by your computer.
3. Plug your Moto X into your PC and let the drivers install automatically.
4. Download and unzip the VZW Developer Edition Factory Image for the Moto X to your desktop.
5. Download both the fastboot.exe and AdbWinApi.dll files and place them in the folder you just unzipped in step step 4.
6. Now grab your Moto X, unplug it from your PC and power it off. Once powered off, press and hold both the Power and Volume Down buttons for about 10 seconds or so to access Fastboot mode.
7. Now, back on your PC, open the folder you extracted on Step 4. Hold down the Shift key on your keyboard and Right Click on an empty space within that folder. From the menu that pops up, click on Open command window here. A command prompt window should open. Plug your phone back into your PC.
8. In the command prompt type fastboot devices to make sure your X is being detected. You should see something similar T0620059GA. If you don't see it, then you may have to reinstall the USB Drivers from Step 2.
9. Once your X has been detected by your computer, and while still in Fastboot mode, type the following commands (in the order shown) into the command prompt on your PC:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
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 cache
fastboot oem lock
fastboot reboot
...
That's it! You should now be locked and unrooted; back to the out of the box factory state. Don't forget to hit thanks and share!
Did re-locking ur bootloader get rid of the Bootloader Unlocked Warning Message?
tonyf7 said:
7. Now, back on your PC, open the folder you extracted on Step 4. Hold down the Shift key on your keyboard and Left Click on an empty space within that folder. From the menu that pops up, click on Open command window here. A command prompt window should open. Plug your phone back into your PC.
Click to expand...
Click to collapse
Right click sir.
mschumacher69 said:
Did re-locking ur bootloader get rid of the Bootloader Unlocked Warning Message?
Click to expand...
Click to collapse
Yes.
tonyf7 said:
Yes.
Click to expand...
Click to collapse
Just to make sure we're on the same page here, after re-locking ur bootloader, when u boot the phone, u get the Moto logo instead of the message that says Warning Bootloader Unlocked?
Because many other users said that u would still get this message even if u re-lock ur bootloader.
When I relocked the bootloader and rebooted the phone I didn't get the warning message. Went straight to the Moto logo. But then I immediately rooted and unlocked again. Only reason I unrooted and relocked in the first place was because I flashed a zip file that corrupted and broke Google Voice Search on my phone.
The second time I did this process I stopped right before locking the bootloader since I was going to root again anyways.
So maybe those other people are right. I've only rebooted my phone once since relocking the bootloader.
Sent from my XT1060 using xda app-developers app
If you want to get rid of the warning on startup, just flash the logo.bin. You can do this and remain unlocked. The instructions provided should have your phone looking and acting the same as it did out of the box. However, fastboot may note that it's been unlocked, to the OP, do you recall what status fastboot was reporting?
you need to reflash to stock in order to lock your bootloader? If not, I would appreciate if you separate the steps to just lock your boot loader.
I have my boot loader unlocked and the only reason I am considering to lock it again is so that if the phone is stolen, someone can't reimage it easily. I'm not sure that gives me any sort of protection though. But its just a thought.
In other words, I see unlocking and locking as a switch that stops you from flashing firmware. The OP makes it sound like the switch is tied to the firmware, ie only stock can have bootloader locked. I am not sure which is right.
esidnD Selim
I did it and keep receiving the warning unlock bootloader screen.
lopescesar304 said:
I did it and keep receiving the warning unlock bootloader screen.
Click to expand...
Click to collapse
Did u re-lock on your phone's ROM or after flashing another carrier's ROM?
mschumacher69 said:
Did u re-lock on your phone's ROM or after flashing another carrier's ROM?
Click to expand...
Click to collapse
My phone is Retail, I used the retail ROM to flash.
My device won't lock. I've run your commands listed, as well as the fastboot oem lock on it's own, and I can't seem to lock the device. Any help?
flavinator said:
My device won't lock. I've run your commands listed, as well as the fastboot oem lock on it's own, and I can't seem to lock the device. Any help?
Click to expand...
Click to collapse
Welcome to the "Relock" party..
The OP does not mention (that I can see) what OS version..are you on KK 4.4 and is there a "Factory Image" for KK 4.4 available for your device.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
NWKENT said:
Welcome to the "Relock" party..
The OP does not mention (that I can see) what OS version..are you on KK 4.4 and is there a "Factory Image" for KK 4.4 available for your device.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Click to expand...
Click to collapse
Yes, there is, flashed it, ran commands, and the relock command, multiple times and get:
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.120s]
finished. total time: 0.122s
Not sure what I am doing wrong.
flavinator said:
Yes, there is, flashed it, ran commands, and the relock command, multiple times and get:
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.120s]
finished. total time: 0.122s
Not sure what I am doing wrong.
Click to expand...
Click to collapse
I'd think you ran this as the first flash >> fastboot oem lock begin first!
Then all the OS files and then this for the last command >> fastboot oem lock > as the last command.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
http://forum.xda-developers.com/showthread.php?t=2575586
NWKENT said:
I'd think you ran this as the first flash >> fastboot oem lock begin first!
Then all the OS files and then this for the last command >> fastboot oem lock > as the last command.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Click to expand...
Click to collapse
I have no clue. At first I just flashed back using RSD Lite. Then I ran the lock command and got that error. Afterwards, I searched online, trying a bunch of different fastboots. That's when I stumbled on this list of commands, figured I'd run it from scratch, see if it makes a difference. Once it got to the relock command though, I got the same issue. And now I'm just frustrated...
---------- Post added at 06:41 PM ---------- Previous post was at 06:36 PM ----------
shane1 said:
http://forum.xda-developers.com/showthread.php?t=2575586
Click to expand...
Click to collapse
I think this might work, thanks shane1
@NWKENT have u managed to re-lock your bootloader yet?
mschumacher69 said:
@NWKENT have u managed to re-lock your bootloader yet?
Click to expand...
Click to collapse
Yes Sir..with Kit Kat 4.4..I have successfully"Unlocked", "Relocked" and "Unlocked" again..my XT1080MDEV (Droid Maxx)..No one could tell me exactly how to do it..Motorola Tech Line was absolutely NO HELP either..SO..after hours upon hours..I did figure it out..Now I'm working on "Relock" on JB 4.2.2
Sounds easy..and many have probably "Unlocked and "Relocked" on JB 4.2.2..BUT..The difficult part is once the XT1080 has been on KK 4.4..is when alot more firey hoops must be jumped thru..
ANYONE can chime in with help on this..NOT ADVICE..but proven procedures..
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Yes, thanks guys.
I'm holding off twrp + bootloader unlock because I want to be able to undo in case I need to use my warranty. Is twrp/bootloader unlock reversible? Many thanks
Yes. Flash complete stock everything, boot into bootloader, connect to PC, and "fastboot oem lock".
Is it sure that it works??I have a A2017G and i have open BL and a B29 Custom Rom and i want back to Lock Bootloader
Kevinkuensken said:
Is it sure that it works??I have a A2017G and i have open BL and a B29 Custom Rom and i want back to Lock Bootloader
Click to expand...
Click to collapse
Yup! I've done it plenty of times. You do need to format the data partition though. This could mean that it'll wipe out even your internal storage, so back that up as well!
Im on stock and then i go to edl and then i type fastboot oem lock but nothing happend
Kevinkuensken said:
Im on stock and then i go to edl and then i type fastboot oem lock but nothing happend
Click to expand...
Click to collapse
Boot into bootloader, not EDL.
Erahgon said:
Yup! I've done it plenty of times. You do need to format the data partition though. This could mean that it'll wipe out even your internal storage, so back that up as well!
Click to expand...
Click to collapse
and you can unlock it again afterwards?
Never heard of anyone wanting to lock the bootloader so I'd a newb in this kind of thing.
BlazingBullets said:
and you can unlock it again afterwards?
Never heard of anyone wanting to lock the bootloader so I'd a newb in this kind of thing.
Click to expand...
Click to collapse
Locking it again is good for when you want to sell the device or send it in for warranty repair.
BlazingBullets said:
and you can unlock it again afterwards?
Never heard of anyone wanting to lock the bootloader so I'd a newb in this kind of thing.
Click to expand...
Click to collapse
Yeah, the unlock procedure is the same as before. If you didn't restore the original boot image before the relock, then it's just a matter of booting into fastboot and unlocking the device. Note that this will cause your data to be wiped as well!
If you restore your boot.bin backup file from when your device was locked, does this lock the bootloader? "fastboot oem lock", "fastboot flashing lock" nor "fastboot oem device-info" does nothing for me. Is there any other way to check if your bootloader has been relocked?
Thanks
H0lmEd said:
I'm holding off twrp + bootloader unlock because I want to be able to undo in case I need to use my warranty. Is twrp/bootloader unlock reversible? Many thanks
Click to expand...
Click to collapse
Hi there,
Were you ever able to re-lock your bootloader on your A2017G?
I just want root for now but understand that I'll need to unlock the bootloader first. Before doing that, I want to make sure I can re-lock the bootloader if needed.
Thanks for letting us know!
joaste said:
Hi there,
Were you ever able to re-lock your bootloader on your A2017G?
I just want root for now but understand that I'll need to unlock the bootloader first. Before doing that, I want to make sure I can re-lock the bootloader if needed.
Thanks for letting us know!
Click to expand...
Click to collapse
Guys/Gals, it is seriously as simple as using the fastboot command in reverse. I've done it a few times already with mine.
If you used the following to unlock....
fastboot devices
fastboot oem unlock
.....then you can use the following commands to relock
fastboot devices
fastboot oem lock
fastboot devices is not necessary, but I do it to make sure the devices is being recognized by ADB/FASTBOOT
sauerkraut17 said:
Guys/Gals, it is seriously as simple as using the fastboot command in reverse. I've done it a few times already with mine.
If you used the following to unlock....
fastboot devices
fastboot oem unlock
.....then you can use the following commands to relock
fastboot devices
fastboot oem lock
fastboot devices is not necessary, but I do it to make sure the devices is being recognized by ADB/FASTBOOT
Click to expand...
Click to collapse
Thanks for the answer.
But there are a few files to flash before using that command according to this thread.
Doesn't anything need to be flashed again (e. g. stock files or anything)?
Correct, but you would have already flashed those in order to use the unlock command in the first place.
Are you trying to relock on marshmallow or nougat?
sauerkraut17 said:
Correct, but you would have already flashed those in order to use the unlock command in the first place.
Are you trying to relock on marshmallow or nougat?
Click to expand...
Click to collapse
My phone is only a few days old. I'm debating whether to keep it or not (considering the Mate 9, but the price is not the same - love the form factor and bigger screen though - sound won't be the same and I think I'll miss the MiPop button on the Axon (never thought that would happen )).
I'm on the latest MM (B10 - the A2017G model).
Following the mentioned thread, I got to the point of installing TWRP (the signed version), only to realize that besides making backups, there is not much else I can do with that without unlocking the bootloader. I really just wanted to flash supersu and install adaway fro the time being until development matured for this phone (maybe also play around with viper - had great results on my LG G4).
HI, I get the error "FAILED (remote: unknown command)" in ADB when I enter "fastboot oem lock". Any way to fix this?
Guys, can anyone help me? I really need to lock the bootloader!
How can I fix the error "FAILED (remote: unknown command)" in ADB when I enter "fastboot oem lock"?
I'm on MM B11 Stock.
https://i.imgur.com/fdkgYs6.jpg
Hi Guys,
The Axon 7 Model A2017U I just purchased has the bootloader locked and it is running LineageOS 14.1 - 2018032-Nightly-axon7. I need to relock the bootloader and get back to the stock MiFavor rom so that I can send the phone to ZTE for repair. Can you please explain to a newb in some detail how to achieve that.
Thank you.
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
Hi,
I put all information into "zui.com/iunlock" correctly, but I get a "Please enter the correct IMEI1" error, and I'm entering it correctly
Please help...
If it's a brand new phone, the imei is not registred by the website at the start.
After a couple of day of use it must work.
Same problem for me at the start and after two day of using the phone my imei is working on the website.
Thanks for the reply
Do I need to put my sim in the phone?
Or is it enough just to connect to wifi?
I used my sim for about 3h, and I got the site to take my IMEI!
Now my bootloader is unlocked
Thanks
Your welcome
I received my smartphone for 10 days. but my emei is still not recognized.
I installed a firewall and everything is blocked except the browser and the messages. I have to authorize a specific program for zui to integrate it?
hello, after 25 days of waiting my imei still did not pass. yesterday I sent an email to devworld and today I had my file
YES :good:
lecomte_jean said:
hello, after 25 days of waiting my imei still did not pass. yesterday I sent an email to devworld and today I had my file
YES :good:
Click to expand...
Click to collapse
Good to know, thank's for the feedback
Bypass
I had the exact same issue and for some weird reason the weirdest glitch ever helped my bypass ZUI all together:
I made a little .bat file to automate all the adb and fastboot commands once I'd get the bootloader unlock file
I didn't know for sure if I had referred to the subfolders in my adb map correctly so I wanted to test it out:
adb reboot bootloader
fastboot flash unlock ".\Z6 Pro\Bootloader.img"
fastboot oem unlock-go
fastboot reboot
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta ".\Z6 Pro\vbmeta.img"
fastboot reboot bootloader
fastboot flash recovery ".\Z6 Pro\twrp.img"
that's what it was gonna be^
but to test out if I had referred correctly I changed vbmeta.img's name into bootloader.img since it was the first path and I expected it to fail but this way I'd at least find out if I got a file not found error or a incorrect boot loader unlock file error.
It flashed correcty, the os is stable and I just installed TWRP.
Idk if this can be done with any img, but the vbmeta file shouldn't have done that. XD
i am on pie 073 firmware... i want to unlock my bootloader ... all the drivers are installed even my phone is detected both in adb and fastboot mode... but when i run the unlock both normally or running uts as administrator it doesnt work... nor the application of unlockimg boot loader works on my phone
Did you try manually typing the unlock command?
Code:
fastboot oem unlock
I've tried this , but it says
Comman failed
No error...
I also has the same problem
KVCmoto said:
Did you try manually typing the unlock command?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
You need to download the Asus Unlock Tool.
If you still have issues, go to their forum ZenTalk and they can help you. They are very fast.