Unable to lock/relock bootloader

schmeggy929

Recognized Themer
Apr 13, 2008
2,781
1,917
193
New Jersey
No, but i got answer from HTC that unlocking bootloader does NOT void warranty. As long as firmware is official and not modified.
This is funny because on the U11 where do you find that your Firmware is official or modified? In bootloader it states *** Software status: Modified *** and has stayed that way since unlocking. Running RUU doesn't change it to Official.
 
G

GuestK0062

Guest
This is funny because on the U11 where do you find that your Firmware is official or modified? In bootloader it states *** Software status: Modified *** and has stayed that way since unlocking. Running RUU doesn't change it to Official.
Exactly, but i believe if we flash official firmware .EXE, then it would say official. But those are hard to find. :mad:

 
G

GuestK0062

Guest
What did you do to ungrey the unlock oem option in dev settings? I’m not able to figure it out.
By flashing TWRP for some reason, later it locked again and was not able to do it again. Anyway while it was unchecked i was still not able to relock bootloader.
 

shivadow

Senior Member
Jan 26, 2012
2,559
471
0
Managed to check OEM Unlocking option, an still getting this error..

C:\Android\com>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.020s]
finished. total time: 0.021s
Factory Reset Protection is stopping it. Disable FRP and then the command should work if the option to allow bootloader unlocking is checked in dev settings *BUT you have no reason to lock the bootloader again as it isn't causing any issues except the red writing on the boot screen.*

*locking bootloader has been known to cause bricks on some m9's.* ONLY LOCK THE BOOTLOADER IF YOU KNOW WHAT YOU'RE DOING AND DON'T MIND IF THE DEVICE BRICKS, OTHERWISE LEAVE IT ALONE. YOU HAVE BEEN WARNED!.

Beamed in by telepathy
 

OMJ

Recognized Developer / Recognized Contributor
Jun 11, 2007
7,839
15,968
0
MN
twitter.com
just a note about relocking...I would normally recommend not relocking but if you want to be stock & have working Android Pay or passing SafetyNet, you will need to lock bootloader :)
 
Last edited:

Shubham-goswami

Senior Member
Mar 3, 2016
96
12
8
indore
What is the right way to do it and is it possible to remove that boot warning message.? i'm on stock unrooted firmware.

I tried fastboot oem lock, all goes fine and OKAY, but after reboot it still says Unlocked/Modified.
see this thread https://forum.xda-developers.com/u11/help/relock-bootloader-t3683331

---------- Post added at 03:19 AM ---------- Previous post was at 03:18 AM ----------

see this thread https://forum.xda-developers.com/u11/help/relock-bootloader-t3683331

---------- Post added at 03:23 AM ---------- Previous post was at 03:19 AM ----------

see this thread https://forum.xda-developers.com/u11/help/relock-bootloader-t3683331
 

rowihel2012

Senior Member
Oct 13, 2012
2,469
374
153
This is funny because on the U11 where do you find that your Firmware is official or modified? In bootloader it states *** Software status: Modified *** and has stayed that way since unlocking. Running RUU doesn't change it to Official.
i used fastboot lock bootloader
it says software status: Modified
it wont boot sto software
just stuck with htc logo
what do do?
 

dryspuri

Senior Member
Oct 15, 2009
740
84
0
Chennai
Factory Reset Protection is stopping it. Disable FRP and then the command should work if the option to allow bootloader unlocking is checked in dev settings *BUT you have no reason to lock the bootloader again as it isn't causing any issues except the red writing on the boot screen.*

*locking bootloader has been known to cause bricks on some m9's.* ONLY LOCK THE BOOTLOADER IF YOU KNOW WHAT YOU'RE DOING AND DON'T MIND IF THE DEVICE BRICKS, OTHERWISE LEAVE IT ALONE. YOU HAVE BEEN WARNED!.

Beamed in by telepathy
How to disable FRP please
 

shivadow

Senior Member
Jan 26, 2012
2,559
471
0
FRP has to be disabled before you reset the device and it is as simple as "delete the Google account from the device before you start the factory reset process".

If you don't, when the device boots after the factory reset, you'll be hit with the Google login "factory reset protection".

If you are stuck at the frp login you'll have search on YouTube for "frp bypassing". The video should explain how to work around the frp by the use of other accounts and exploitation of glitches within the process. There are different methods depending on which os the device is using.
 

royalcrown

Member
Feb 8, 2011
38
14
0
FRP does not have to be disabled, that is incorrect. I can unlock and relock all day long with FRP on.

---------- Post added at 01:37 AM ---------- Previous post was at 01:26 AM ----------

What is the right way to do it and is it possible to remove that boot warning message.? i'm on stock unrooted firmware.

I tried fastboot oem lock, all goes fine and OKAY, but after reboot it still says Unlocked/Modified.
If it just says, "OKAY" that doesn't mean anything.

Have USB Debugging enabled, forget about OEM UNLOCK and factory reset protection, that is misinformation on here by people usually just guessing.

REMOVE MICRO SD CARDS or U11 won't relock, even if the card is "ejected" under storage menu. THE CARD CANNOT PHYSICALLY BE IN THE PHONE IN MOST CASES, IT CAUSES ISSUES.

After USB debugging enabled, reboot into download mode (while hooked up to the factory USB cable) by:

typing, "adb reboot download" OR

holding power button and volume down until it reboots into download mode (yellow text)

then type, "fastboot oem lock" from the command line in your fastboot directory.

you should see a screen pop up on the U11 asking if you want to relock along with a bunch of other text, select YES via volume button and use power button to confirm. If you don't get the message on your phone screen it isn't working, you need that message. Good luck.
 

royalcrown

Member
Feb 8, 2011
38
14
0
There is no reason to lock the bootloader. It isn't necessary and serves no purpose.
It does if you want to pass Safetynet checks, or use Android Pay as far as I know, currently Majisks does not allow Android Pay to work while rooted as of beta 14.5. Other banking apps may be the same or not. I also was unable to transfer bluetoth files to my windows 10 machine until I relocked..could just be a bug or bad cache data though.
 

newyesor

Senior Member
Jul 27, 2014
606
226
0
Bangkok
Yesterday,I found this problem about oem unlock greay(can not tik) on my device.
My devices is status unlock,s-on.
I want to downgrade oreo to nougat with s-off method.
I was downgrade successfull with s-off.
I flash ruu right follow cid phone and i want to update ota for update oreo again but oem unlock greay.
I was flash custom rom for fix it.
When i flashed custom rom finish,i can tik oem unlock again.:cowboy:
 

shivadow

Senior Member
Jan 26, 2012
2,559
471
0
It does if you want to pass Safetynet checks, or use Android Pay as far as I know, currently Majisks does not allow Android Pay to work while rooted as of beta 14.5. Other banking apps may be the same or not. I also was unable to transfer bluetoth files to my windows 10 machine until I relocked..could just be a bug or bad cache data though.
Not true. Unlocked bootloader and s-off do not affect android pay or safety checks. It works fine on my phone that is unlocked everything on a stock rom.

Root is what breaks safetynet checks and is the reason banking apps, android pay etc fail to load.