Hi guys, I am wondering that anyway that I can fully return to stock? And if I return to stock, does it still show the warning of the unlocking bootloading when we start the phone?
Thank guy!
chakchak said:
Hi guys, I am wondering that anyway that I can fully return to stock? And if I return to stock, does it still show the warning of the unlocking bootloading when we start the phone?
Thank guy!
Click to expand...
Click to collapse
+1
Sent from my LG-H870 using Tapatalk
1. Use LG Bridge to "repair" the phone will get you back to stock Oreo and LG OTA updates. But will not relock your bootloader so you still see the code orange warning.
2. To relock your bootloader, read the FAQ contained in the unlocking guide. Essentially it's a fastboot command.
Both steps will wipe the phone so backup your data first.
How to in 5 steps Lock your bootloader ,that worked successfully on (H870)
the requirement for a successful lock: flash with LGUP and uppercut LG STOCK FIRMWARE
1. Enable Developer Mode
2. Enable OEM Unlocking
3. Boot into Fastboot Mode
3. Typefollowing command ---> fastboot oem lock
4. Wait for the Command Prompt to tell you the process has finished
5. And.... ---> fastboot reboot
Your bootloader is successful locked
Why is LG UP / uppercut a requirement? I did it using LG Bridge, worked. The requirement I think is just an LG stock firmware. Pretty obvious.
I also wrote "the requirement for a successful lock: .... " ! you can see colon ? I do not say must take LGUP ,It was a suggestion to note
Quote:The requirement I think is just an LG stock firmware.
Yes :good:
Moldeb said:
1. Use LG Bridge to "repair" the phone will get you back to stock Oreo and LG OTA updates. But will not relock your bootloader so you still see the code orange warning.
2. To relock your bootloader, read the FAQ contained in the unlocking guide. Essentially it's a fastboot command.
Both steps will wipe the phone so backup your data first.
Click to expand...
Click to collapse
Bunsenbrenner said:
How to in 5 steps Lock your bootloader ,that worked successfully on (H870)
the requirement for a successful lock: flash with LGUP and uppercut LG STOCK FIRMWARE
1. Enable Developer Mode
2. Enable OEM Unlocking
3. Boot into Fastboot Mode
3. Typefollowing command ---> fastboot oem lock
4. Wait for the Command Prompt to tell you the process has finished
5. And.... ---> fastboot reboot
Your bootloader is successful locked
Click to expand...
Click to collapse
Thank you all!!! :highfive:
Related
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?
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 have a A2017U that I just downgraded to B35 using this guide: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
I want to lock the bootloader to stop the annoying boot warning but can't get into fastboot when using AXON7TOOLKIT.
I tried flashing A2017U_FASTBOOT_UNLOCK_EDL (downloaded from https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128) through miFlash but I still can't get into the bootloader.
What can I do?
EDIT: Thanks everyone! I used the toolkit to unlock the bootloader again, then locked it. For some reason I couldn't access the bootloader even though i got the bootloader ulocked warning.
mateokross said:
I have a A2017U that I just downgraded to B35 using this guide: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
I want to lock the bootloader to stop the annoying boot warning but can't get into fastboot when using AXON7TOOLKIT.
I tried flashing A2017U_FASTBOOT_UNLOCK_EDL (downloaded from https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128) through miFlash but I still can't get into the bootloader.
What can I do?
Click to expand...
Click to collapse
You only want to lock it because of the boot warning? There are flashables to get rid of that... I dom't know which exact files there are for stock B35 or Oreo but there are some going around.
hell you could even go custom and use the splash bootstack if you wanted.
If you want to lock anyways, you have to get an A2017U B19 package and flash it via EDL Tool (or MiFlash). Right after that you'll have fastboot. enable oem unlocking then enter fastboot and issue fastboot oem lock and you're done. But it's way too overkill if you want to just get rid of the 5 sec screen
mateokross said:
I have a A2017U that I just downgraded to B35 using this guide: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
I want to lock the bootloader to stop the annoying boot warning but can't get into fastboot when using AXON7TOOLKIT.
I tried flashing A2017U_FASTBOOT_UNLOCK_EDL (downloaded from https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128) through miFlash but I still can't get into the bootloader.
What can I do?
Click to expand...
Click to collapse
you need to flash original stock rom for your device trough edl. (rom your device came from factory,marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)
Hello. I have a lg v20 H990N. I flashed TWRP by dirty santa method and wanted to go back to stock. As per the instructions on the link https://forum.xda-developers.com/v20...-h990-t3624296, I used method 1a for going back to stock. I ran the code as mentioned in the method while using my backed up "abootbackup.img" but I accidently ran the code twice.
Code:
dd if=abootbackup.img of=/dev/block/bootdevice/by-name/aboot
sync
sleep 30
sync
After booting to bootloader. this is what I see written on the boot loader screen.
___________________________________
Welcome to fastboot mode for bootloader unlock:
*Quick Guidnance
1) Read Device Id
fastboot oem device-id
2) Write unlock key
fastboot flash unlock unlock.bin
3) Check boiotloader is unlocked
Fastboot getvar unlocked
*How to exit fastboot mide
USe "Fastboot reboot' command if fastboot is available
________________________________________
This is the meassage that pops up in fastboot. I can use fastboot but can't use "fastboot flash recovery twrp-3.0.2-1-h990.img" as it exits with error that remote: device is locked. I can't flash kdz with lg Up as Lg up says " there is no haadset connected". TWRP recovery is also not boot neither is the nougat rom that was installed. More \over my device is shown as "Kedacom USB device " in device manager in fastboot mode. Not in Com ports.
It apperas that my bootloader has locked somehow after flashing abootbackup and I can't unlock it as h990N is not supported by LG to unlock bootloader. screenshot attached.
Please help!!!
Yeah flashing the stock bootloader relocks most v20 variants, (the dirty santa bootloader can't truely unlock them, it just ignores the lock)
I'm not sure what you expected? Your link is broken, but it sounds like you reflashed stock firmware and then the stock bootloader and expected to be in a different situation than a fresh unrooted device?
You should be able to boot normally to Android or boot I to download mode and reroot from scratch.
.
Hi,
I am having a problem trying to relock my bootloader.
i am selling my g4, so needed to remove my custom rom, flash stock and relock my bootloader.
I downloaded and flashed via twrp the stock 8.1 ROM on the g4 plus page. ( stock rom in twrp format)
That went fine.
Then I booted into fastboot , and entered fastboot lock command fastboot oem lock
It said the android image was not valid?
So I then entered fastboot flashing lock
it rebooted fine to the stock android , but now the bootloader warning says ''your device has loaded a different operating system'', and thens boots 8.1.
DO you think I should go back anf flash stock rom ( not a twrp flashable version), using fastboot commands, ending with 'fastboot oem lock' ?
Just dont want to brick it, as it is now sold!
Many Thanks for any help
pootler
P.S. the TWRP I am using is a custom one ( i think )
pootler said:
Hi,
I am having a problem trying to relock my bootloader.
i am selling my g4, so needed to remove my custom rom, flash stock and relock my bootloader.
I downloaded and flashed via twrp the stock 8.1 ROM on the g4 plus page. ( stock rom in twrp format)
That went fine.
Then I booted into fastboot , and entered fastboot lock command fastboot oem lock
It said the android image was not valid?
So I then entered fastboot flashing lock
it rebooted fine to the stock android , but now the bootloader warning says ''your device has loaded a different operating system'', and thens boots 8.1.
DO you think I should go back anf flash stock rom ( not a twrp flashable version), using fastboot commands, ending with 'fastboot oem lock' ?
Just dont want to brick it, as it is now sold!
Many Thanks for any help
pootler
P.S. the TWRP I am using is a custom one ( i think )
Click to expand...
Click to collapse
Use LMSA flash rescue option if you have a Windows machine
(Lenovo) MOTO Smart Assistant (PC)
then see
Relocking the bootloader
sd_shadow said:
Use LMSA flash rescue option if you have a Windows machine
(Lenovo) MOTO Smart Assistant (PC)
then see
Relocking the bootloader
Click to expand...
Click to collapse
THanks for the reply.
Strange, thought I had already updated this
I went back to stock firmware and decided to flash with fastboot all individual files.
At some point, I got the same ''verification failed' but the command line suggested flashing system, boot, and ( something else, cant remember) again.
i did this this, and this time, no errors occured, and I had a complete install, with a locked bootloader, and no bootloader warning screen.!
Yay - result
Thanks again for your advice - I will remember it for the future.