Database Develop

[Q] Why does OEM unlocking automatically turn itself off -- Verizon

I'm trying to root my Verizon Nexus 6, and for some reason, when I try to toggle OEM unclocking and boot into the bootloader, it says device is locked - status code 2.
Any Verizon owners experience this problem, or know how to fix it? It would certainly be unfortunate if this is how Verizon keeps its customers from modifying their phones.

RootTheWorld said:
I'm trying to root my Verizon Nexus 6, and for some reason, when I try to toggle OEM unclocking and boot into the bootloader, it says device is locked - status code 2.
Any Verizon owners experience this problem, or know how to fix it? It would certainly be unfortunate if this is how Verizon keeps its customers from modifying their phones.
Click to expand...
Click to collapse
The toggle is a new feature of Android 5.0 and up. The toggle does not unlock your bootloader, rather it allows the process to happen. You need to use fastboot to OEM unlock. Click the top link in my signature for more info. Also, I suggest you read the beginners guide in the general forum.

RootTheWorld said:
I'm trying to root my Verizon Nexus 6, and for some reason, when I try to toggle OEM unclocking and boot into the bootloader, it says device is locked - status code 2.
Any Verizon owners experience this problem, or know how to fix it? It would certainly be unfortunate if this is how Verizon keeps its customers from modifying their phones.
Click to expand...
Click to collapse
After you toggle enable OEM unlock you need to reboot into boot loader and run the command "fastboot OEM unlock"
Everything is here
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Sent from my Nexus 6 using XDA Premium HD app

RootTheWorld said:
I'm trying to root my Verizon Nexus 6, and for some reason, when I try to toggle OEM unclocking and boot into the bootloader, it says device is locked - status code 2.
Any Verizon owners experience this problem, or know how to fix it? It would certainly be unfortunate if this is how Verizon keeps its customers from modifying their phones.
Click to expand...
Click to collapse
It is a security feature. All "enable oem unlocking" does is allow you to unlock the bootloader by fastboot. It doesnt actually unlock it.

RootTheWorld said:
I'm trying to root my Verizon Nexus 6, and for some reason, when I try to toggle OEM unclocking and boot into the bootloader, it says device is locked - status code 2.
Any Verizon owners experience this problem, or know how to fix it? It would certainly be unfortunate if this is how Verizon keeps its customers from modifying their phones.
Click to expand...
Click to collapse
When you toggle "allow bootloader unlock" in developer options, it does just that; it allows you to unlock the bootloader.
Then you boot to bootloader and type "fastboot OEM unlock".
Assuming you have the android SDK on your PC, and device connected by USB cable. Look in the sticky roll up thread in general section for specific directions.

Intub8 said:
After you toggle enable OEM unlock you need to reboot into boot loader and run the command "fastboot OEM unlock"
Everything is here
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
That's what I'm doing. However, the issue is that it relocks itself. Hence the "device is locked - status code 2". You shouldn't unlock the bootloader when it's locked, or else you could cause a bootloop.

RootTheWorld said:
That's what I'm doing. However, the issue is that it relocks itself. Hence the "device is locked - status code 2". You shouldn't unlock the bootloader when it's locked, or else you could cause a bootloop.
Click to expand...
Click to collapse
Are you sure its relocking? Are you sure you're unlocking it?
So you go into settings > developer options
You tick "allow OEM unlock"
You boot into bootloader
Connect USB to computer
Open command prompt
Type "fastboot OEM unlock"
Does it unlock and change to status 3?
When does it change back to 2?

rootSU said:
Are you sure its relocking? Are you sure you're unlocking it?
So you go into settings > developer options
You tick "allow OEM unlock"
You boot into bootloader
Connect USB to computer
Open command prompt
Type "fastboot OEM unlock"
Does it unlock and change to status 3?
When does it change back to 2?
Click to expand...
Click to collapse
Here's my rundown:
So you go into settings > developer options
tick "allow OEM unlock"
boot into bootloader
shows: device is locked - status code 2
boot back into OS
go to settings > developer options
allow OEM unlock is unticked

RootTheWorld said:
Here's my rundown:
So you go into settings > developer options
tick "allow OEM unlock"
boot into bootloader
shows: device is locked - status code 2
boot back into OS
go to settings > developer options
allow OEM unlock is unticked
Click to expand...
Click to collapse
and you misses a step.. You need to get ur ass in dos or terminal and run the fastboot oem unlock command

Robert_W said:
and you misses a step.. You need to get ur ass in dos or terminal and run the fastboot oem unlock command
Click to expand...
Click to collapse
I thought I'd put my phone into a bootloop if I did that with a device is locked - status code 2 message.
I'll report back shortly

RootTheWorld said:
Here's my rundown:
So you go into settings > developer options
tick "allow OEM unlock"
boot into bootloader
shows: device is locked - status code 2
boot back into OS
go to settings > developer options
allow OEM unlock is unticked
Click to expand...
Click to collapse
You are not doing it correctly. Go here and follow the directions
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481

cam30era said:
You are not doing it correctly. Go here and follow the directions
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Click to expand...
Click to collapse
I was doing everything correctly, but I didn't realize that it was okay to proceed on the "device is locked" message.
One thing that's not covered in the guide however: Is it okay to use the Chainfire root on a 5.1 device? The Chainfire website lists the tool as compatible with 5.0, but could I proceed anyway?

RootTheWorld said:
Here's my rundown:
So you go into settings > developer options
tick "allow OEM unlock"
boot into bootloader
shows: device is locked - status code 2
boot back into OS
go to settings > developer options
allow OEM unlock is unticked
Click to expand...
Click to collapse
As we've said multiple times, ticking the OEM unlock box only allows you to unlock. It doesn't actually unlock. There is only 1 way to unlock and that's with the fastboot commands.
---------- Post added at 03:22 AM ---------- Previous post was at 03:20 AM ----------
RootTheWorld said:
I was doing everything correctly
Click to expand...
Click to collapse
Yes the half of it you did, you did correctly
RootTheWorld said:
I didn't realize that it was okay to proceed on the "device is locked" message.
Click to expand...
Click to collapse
What did you expect it to say? You cant unlock it if its not locked.

rootSU said:
As we've said multiple times, ticking the OEM unlock box only allows you to unlock. It doesn't actually unlock. There is only 1 way to unlock and that's with the fastboot commands.
---------- Post added at 03:22 AM ---------- Previous post was at 03:20 AM ----------
Yes the half of it you did, you did correctly
What did you expect it to say? You cant unlock it if its not locked.
Click to expand...
Click to collapse
Yes, I know. The problem was that the OEM unlock box kept unticking itself, which I had assumed led to the message I saw in the bootloader. Do you understand what I am trying to say? I don't think it was clear.

RootTheWorld said:
Yes, I know. The problem was that the OEM unlock box kept unticking itself, which I had assumed led to the message I saw in the bootloader. Do you understand what I am trying to say? I don't think it was clear.
Click to expand...
Click to collapse
That box un ticks it self on each boot. I also have a Verizon nexus. You check it and USB debugging. Then use wugfresh tool kit to unlock. Or just power down to boot loader mode & use terminal. Its only used to reboot to allow unlock. My phone is a flash whore & that box always off.

RootTheWorld said:
Yes, I know. The problem was that the OEM unlock box kept unticking itself, which I had assumed led to the message I saw in the bootloader. Do you understand what I am trying to say? I don't think it was clear.
Click to expand...
Click to collapse
Yes the box keeps unticking. That's a security feature to stop a thief unlocking your bootloader and using your phone.

i run above method in my lenovo vibe shot z90a40, it gives below error msg: (failed: unknow remote command)

aicts said:
i run above method in my lenovo vibe shot z90a40, it gives below error msg: (failed: unknow remote command)
Click to expand...
Click to collapse
We can't help you. We have nexus 6.

same thing happens with me just mine would untick immediately after i press it oem unlocking in developer settings

Good lord man read the thread.
ON THE NEXT BOOT OF ANDROID, ALLOW OEM UNLOCK IS TICKED BACK OFF AUTOMATICALLY, THIS IS NORMAL AND CORRECT.
The reason it says allow unlock, and not unlock... Is because this command only ALLOWS unlocking to happen.
As a security measure, you need to allow unlock, then immediately do it... YOU CANNOT ENABLED ALLOW OEM UNLOCK FOR USE AT A LATER DATE.
This toggle simply passes the message to your bootloader that you it can be unlocked via the unlock command.
The point is, that if your phone is password protected and locked... No one can flash anything to it. If you could simply boot the phone to bootloader and unlock, it would not be as secure. You need to enter the password to gain access to the running phone, then choose to allow the unlock, then reboot. If you could simply toggle on allow unlock and leave it through reboots it would negate the whole idea that if someone gets your phone they cannot unlock the bootloader with out the phones password.

FAILED (remote: Command not allowed)

Hello friends
if i want to flash recovery or relock the device it tells me "FAILED (remote: Command not allowed)".
Till the nougat update it wasn't a problem, it worked like described in every guide.
I think my drivers are ok, no errors in device manager and on Marshmallow everything worked fine.
The big problem is my home banking app detects the unlocked bootloader and stops working
so i need to either lock my device or root it.
Here are some data may they will help
At fastboot
Phone Unlocked
FRP Lock
About phone
Device Name: Honor 5C
Model number: NEM-L51
Build number: NEM-L51C432B350
EMUI version: 5.0
Android version: 7.0
Developer options
OEM unlocking is in off position and greyed out
USB debugging is on
I use "ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05" on Windows 10
hope you can help
greetings
Max

1 - Go to settings
2 - developer options (Need to enable)
3 - "OEM unlock" is enable
Done .

MHN.1515 said:
1 - Go to settings
2 - developer options (Need to enable)
3 - "OEM unlock" is enable
Done .
Click to expand...
Click to collapse
Hi MHN.1515
Thx for your reply but unfortunately OEM unlocking is greyed out and in off position.
greetings
Max

Maximilian Hauser said:
Hi MHN.1515
Thx for your reply but unfortunately OEM unlocking is greyed out and in off position.
greetings
Max
Click to expand...
Click to collapse
To return to the previous Android (6)

To return to the previous Android (6)
Click to expand...
Click to collapse
Hi MHN.1515,
and thanks for your participation.
this is exactly what i did.
I went back to the stock image "Honor 5C stock ROM images (latest: B102) NEM-L51" from PaulOBrien on MoDaCo. (Thank you for providing the image at this place)
Then i flashed NEM-L51C432B130 from here. (Thanks to Druger too) In this process the bootloader got locked again.
From there i updated to Nougat again, the good things are my phone is locked so i can use my homebanking app
and in developer options i can turn the Unlocking bootloader switch to on or off as is want to root it again one day.
So i hope i described the process well so it can help people with the same problem.
Greetings
Max
Btw. next time i need a better backup strategy, or at least a backup strategy

Maximilian Hauser said:
Hi MHN.1515,
and thanks for your participation.
this is exactly what i did.
I went back to the stock image "Honor 5C stock ROM images (latest: B102) NEM-L51" from PaulOBrien on MoDaCo. (Thank you for providing the image at this place)
Then i flashed NEM-L51C432B130 from here. (Thanks to Druger too) In this process the bootloader got locked again.
From there i updated to Nougat again, the good things are my phone is locked so i can use my homebanking app
and in developer options i can turn the Unlocking bootloader switch to on or off as is want to root it again one day.
So i hope i described the process well so it can help people with the same problem.
Greetings
Max
Btw. next time i need a better backup strategy, or at least a backup strategy
Click to expand...
Click to collapse
As far as I know this is the only way
You try to build in other (For example : NEM-L51C432B120) :
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1165/g104/v61511/f1/full/update.zip
I build my phone is different
So I can not be sure this file , But you try
(Please Thanks for button press )

Can't flash after Nougat-Update

Hi There,
im new here and wish to say hello to you all.
i read a lot of threads but nothing is my specific problem.
I unlocked my bootloader and rooted my 5c under Android 6. Then, the nougat 7 update came in and now i got the following problem:
when entering fastboot to flash twrp-recovery, my honor says "PHONE Unlocked FRP Lock" and the oem-unlock-trigger under developer options is in OFF-position and greyed out with no possibility to enable it.
When i try flashing recovery i always get the message
target reported max download size of 471859200 bytes
sending 'recovery' (21942 KB)...
OKAY [ 0.578s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.587s
i think, that this toggle has to be in ON-position to be able to flash. Bootloader is unlocked
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
Any suggestion or help for me? I need my root access but i'm not able to get it and don't know whats the exact problem. Already tried disabling all screen-locks and thins i read in other posts but nothing worked.

youre on twrp right? if you are thn you need flash stock recovery (extract from B100 firmware)

thelous said:
youre on twrp right? if you are thn you need flash stock recovery (extract from B100 firmware)
Click to expand...
Click to collapse
no, thats the problem. under android 6 i was on twrp and rooted, then updated to nougat. after update twrp was gone but bootloader stayed unlocked and oem-unlock in developers mode is greyed out in off-position.
Now i want to flash twrp-recovery againg, but command not allowed

Nobody here with an idea?

weini1980 said:
Nobody here with an idea?
Click to expand...
Click to collapse
install B100 firmware thru DLOAD folder...

thelous said:
install B100 firmware thru DLOAD folder...
Click to expand...
Click to collapse
where can i get it?
am i back then on android 6?
is it the only way to enable "oem unlock button"?
whats the exact problem? Why this happened to me after update to 7?
Thanx in advance

weini1980 said:
where can i get it?
am i back then on android 6?
is it the only way to enable "oem unlock button"?
whats the exact problem? Why this happened to me after update to 7?
Thanx in advance
Click to expand...
Click to collapse
you can find it from huawei's site, im not sure why it happend to you, just start from B100 firmware again that solves 90% of problems when modding stuff

Hey,
still the same problem. can't find software. any link?
clear credentials greyed out too. oem unlocking greyed out too. need this so badly. any idea?

I can solve this issue

weini1980 said:
Hey,
still the same problem. can't find software. any link?
clear credentials greyed out too. oem unlocking greyed out too. need this so badly. any idea?
Click to expand...
Click to collapse
here is the link search the required firmware
http://hwmt.ru/oth/HWFF/info/view.php?find_model=
download only the zip which has status as full.

But , emui 5 has 3 zips even for full update

weini1980 said:
Hi There,
im new here and wish to say hello to you all.
i read a lot of threads but nothing is my specific problem.
I unlocked my bootloader and rooted my 5c under Android 6. Then, the nougat 7 update came in and now i got the following problem:
when entering fastboot to flash twrp-recovery, my honor says "PHONE Unlocked FRP Lock" and the oem-unlock-trigger under developer options is in OFF-position and greyed out with no possibility to enable it.
When i try flashing recovery i always get the message
target reported max download size of 471859200 bytes
sending 'recovery' (21942 KB)...
OKAY [ 0.578s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.587s
i think, that this toggle has to be in ON-position to be able to flash. Bootloader is unlocked
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
Any suggestion or help for me? I need my root access but i'm not able to get it and don't know whats the exact problem. Already tried disabling all screen-locks and thins i read in other posts but nothing worked.
Click to expand...
Click to collapse
Hey dude, first fastboot oem relock, and then unlock, it should help you 100%, i promise, just try.

SCUZZY1337 said:
Hey dude, first fastboot oem relock, and then unlock, it should help you 100%, i promise, just try.
Click to expand...
Click to collapse
No dude, doesn't work. Command not allowed. Bootloader is unlocked but because of this behaviour i'm not able to flash SuperSU ...

weini1980 said:
No dude, doesn't work. Command not allowed. Bootloader is unlocked but because of this behaviour i'm not able to flash SuperSU ...
Click to expand...
Click to collapse
first of all, you have to relock your BL, then unlock man.

weini1980 said:
No dude, doesn't work. Command not allowed. Bootloader is unlocked but because of this behaviour i'm not able to flash SuperSU ...
Click to expand...
Click to collapse
You have to find a way to turn the FRP off.
Sent from my Honor 8 using XDA Labs

adriansticoid said:
You have to find a way to turn the FRP off.
Click to expand...
Click to collapse
It's easyyyyy, just relock the bootloader and then unlock it again!

gopinaidu77 said:
U cant unlock if frp locked
Click to expand...
Click to collapse
If FRP locked, you have to enable OEM Unlock function, then relock and unlock bootloader. It works, i mean it worked for me correctly.

SCUZZY1337 said:
If FRP locked, you have to enable OEM Unlock function, then relock and unlock bootloader. It works, i mean it worked for me correctly.
Click to expand...
Click to collapse
To be frank , i really dont know why i see frp unlocked or locked status .

huawei P9 bootloader relock fail

Hi, I would like to relock the bootloader but I am getting the following message:
FAILED (remote: stat not match)
I use command line and the following command:
fastboot oem relock *******(unlock code)
Any idea?
Thanks

Goldak said:
Hi, I would like to relock the bootloader but I am getting the following message:
FAILED (remote: stat not match)
I use command line and the following command:
fastboot oem relock *******(unlock code)
Any idea?
Thanks
Click to expand...
Click to collapse
Do you see in the Fastboot that Phone (Bootloader) and FRP are unlocked.
If Phone unlocked but FRP locked, you have to enable OEM Unlocking
Do not attempt unlocking Bootloader with TWRP or custom ROM - it triggers Factory resetting and it can brick the phone
Btw, for OTA updates it doesn't matter if Bootloader is locked or not

I am on stock Nougat. I unlocked the bootloader some time ago, then some OTA update came. Right now, what I see in Fastboot is "Phone locked, FRP unlocked"... So it seems that the bootloader was actually locked by the OTA. However the Safetynet test fails and I cannot use NFC payments now. I suppose its the unlocked FRP that causes this. How could I fix it?
Thanks

Goldak said:
I am on stock Nougat. I unlocked the bootloader some time ago, then some OTA update came. Right now, what I see in Fastboot is "Phone locked, FRP unlocked"... So it seems that the bootloader was actually locked by the OTA. However the Safetynet test fails and I cannot use NFC payments now. I suppose its the unlocked FRP that causes this. How could I fix it?
Thanks
Click to expand...
Click to collapse
Some OTA updates do lock the Bootloader.
FRP should not affect SafetyNet.
Btw, which stock ROM you have and do you have Magisk/root (why are you concerned about SafetyNet)?
I'm not using NFC (pay)... but due to certain Google API changes some apps fail to verify SafetyNet

I am on stock EVA-L09C150B388, no root or other modification. So I think the only reason for NFC payment not working/ Safetynet failure might be the unlocked FRP...

Goldak said:
I am on stock EVA-L09C150B388, no root or other modification. So I think the only reason for NFC payment not working/ Safetynet failure might be the unlocked FRP...
Click to expand...
Click to collapse
You can easily uncheck OEM Unlocking and reboot

zgfg said:
You can easily uncheck OEM Unlocking and reboot
Click to expand...
Click to collapse
Unfortunatelly, that did not help...?

Goldak said:
Unfortunatelly, that did not help...
Click to expand...
Click to collapse
Test if your SafetyNet is really (not) ok with the apps attached to
https://forum.xda-developers.com/showpost.php?p=77339761&postcount=566

zgfg said:
Test if your SafetyNet is really (not) ok with the apps attached to
https://forum.xda-developers.com/showpost.php?p=77339761&postcount=566
Click to expand...
Click to collapse
Those two apps show no fails... However SafetyNet Test app from Google play says 'Failed'

Goldak said:
Those two apps show no fails... However SafetyNet Test app from Google play says 'Failed'
Click to expand...
Click to collapse
There is a link in that post - there was some change in SafetyNet/API or key causing not updated apps to fail

The command is "fastboot oem lock", not "relock"

zgfg said:
There is a link in that post - there was some change in SafetyNet/API or key causing not updated apps to fail
Click to expand...
Click to collapse
Thats probably the problem, thanks!

Unlocking bootloader FAIL

Hey guys,
I am trying to unlock my bootloader on my OP 7 pro Global version. i am currently running android 12 and hate it so much i am trying to downgrade back to 11.
In order to do this i need to unlock my bootloader and flash the old os... but I keep getting this weird error.
When i run command "fastboot oem unlock" i receive -
FAILED (remote: 'Device cannot be unlocked for technical reason.')
fastboot: error: Command failed
When i run "fastboot devices" i can see my device.
under developer setting i have all ready toggled allow oem unlock...
nothing seems to get around this issue and i am currently stuck and have no idea what else to try.

The MSM Tool should help you. Worked for me. I converted my T-Mobile variant, to Global using it. Follow the guide, and the MSM tool will flash your phone back to stock, with bootloader locked once again.
Edit: I should note, the tool will wipe your phone, so backup obviously.

DaveImagery said:
The MSM Tool should help you. Worked for me. I converted my T-Mobile variant, to Global using it. Follow the guide, and the MSM tool will flash your phone back to stock, with bootloader locked once again.
Edit: I should note, the tool will wipe your phone, so backup obviously.
Click to expand...
Click to collapse
Yes thank you! i was gonna write here that i eventually put my phone in edl mode and downgraded through msm tool to OOS 11.
Thank you!

no new for TWRP 3.7, still doesn't works on A12.
Also, A12 BL can't be unlocked for now.