Related
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.
Hey XDA,
So today I got my N Preview 2 OTA update and everything is fine and great. However I went into dev settings today to make sure I had debugging and OEM unlocking on but, if seems the Allow OEM unlock button is grayed out. Is anyone else seeing this? It may even be stuck on the Allow setting but, I really can't tell and it's a bit concerning. Any help would be appreciated thanks!
http://imgur.com/YeWFcO0
I have to ask the obvious question. Is your device already unlocked?
dahawthorne said:
I have to ask the obvious question. Is your device already unlocked?
Click to expand...
Click to collapse
Nope, status code 2 'locked' according to my bootloader.
He's right, I'm unlocked already and on np2 and I don't see OEM unlock in dev options either. They must be moving it to another location or something
Edit: I do see it now but you can't toggle the switch anymore
Sent from my Nexus 6 using XDA-Developers mobile app
looks like after the fiasco of the 1st preview that bricked phones during OTA & most of them have the bootloaders locked & OEM unlock in off position, this preview has put the oem unlock in default on position.
so if I am already unlocked and I flash the 2nd preview- am I OK? will the bootloader stay unlocked?
i believe so
looks like after the fiasco of the 1st preview that bricked phones during OTA & most of them have the bootloaders locked & OEM unlock in off position, this preview has put the oem unlock in default on position.
Click to expand...
Click to collapse
That makes sense...the op screen shot shows the button slider to the right (on position), even though grayed out.
LittleJakub said:
so if I am already unlocked and I flash the 2nd preview- am I OK? will the bootloader stay unlocked?
Click to expand...
Click to collapse
Yea, you're good. As long as you don't run the "fastboot oem lock" command through fastboot, your bootloader should always remain unlocked. Even if the "OEM Unlocking" toggle is switched off, an unlocked bootloader should remain unlocked.
I'm on NPC91K with a Nexus 6 and the "Allow OEM Unlock" option is grayed out and disabled for me. My phone is currently locked and Fastboot oem unlock does not work.
Griff Ellis said:
I'm on NPC91K with a Nexus 6 and the "Allow OEM Unlock" option is grayed out and disabled for me. My phone is currently locked and Fastboot oem unlock does not work.
Click to expand...
Click to collapse
Thanks for checking that out. Officially concerned now
I tried out NPC91K yesterday and the "Allow OEM Unlock" option was also grayed out , but the button was in the enabled position. After a while i out back backup and bootloader is still unlocked. In Bootloader it says Device is Unlocked Status code 3.
I am in the same situation, my phone is locked and N preview 2 now oem unlock is greyed out and disabled, anybody can suggest a way to enable this, TIA.
droidguy22 said:
I am in the same situation, my phone is locked and N preview 2 now oem unlock is greyed out and disabled, anybody can suggest a way to enable this, TIA.
Click to expand...
Click to collapse
Check out my post here on how to get around the oem unlock problem, and get back to marshmallow.
http://forum.xda-developers.com/nexus-6/help/command-device-corrupt-update-t3362317/page2
My redmi 4x (santoni) have twrp installed and I it is running on miui pro rom. But it's bootloader locking automatically after enabling usb debugging and switching off the phone. I can't boot into recovery and system, can only boot into fastboot mode, and I have to use mi flash tool to unlock bootloader again.
If someone face this problem, is there any solution of this. Please reply.
Thank you.
Bootloader can only be locked on all available official MIUI ROM, it can not be locked on modified MIUI versions.
There is no way that it'll get locked by itself by turning on USB Debugging and switching off phone. to lock unlocked bootloader one has to clean flash from Mi flash tools and needs to select lock bootloader before flashing.
I don't know how are you able to unlock bootloader on Mi flash tools because to unlock it official way one will need Mi unlock tool with permission from xiaomi(depending on region)
First make sure you are not on fake MIUI if so then flash official one through mi flash tools and then unlock it by mi unlock tools.
Once it is unlocked as i said earlier there is no way that it will get locked itself unless you choose to lock via mi flash tools.
about unlocking again
sorry for mistake, I have to use mi unlock tool again with my mi account signed in to unlock the bootloader again. And can't unlock by fastboot command "fastboot oem unlock".
yuyutsu said:
sorry for mistake, I have to use mi unlock tool again with my mi account signed in to unlock the bootloader again. And can't unlock by fastboot command "fastboot oem unlock".
Click to expand...
Click to collapse
I still do not get it what exact issue you have and what version of MIUI you are on.
You are saying you are on MIUI Pro and that confirms bootloader is unlocked and now you are saying
"I have to use mi unlock tool again with my mi account signed in to unlock the bootloader again. And can't unlock by fastboot command "fastboot oem unlock"
Click to expand...
Click to collapse
Please share exact and more details if you wish to resolve your issue and possibly some screenshot(s) of about phone and errors if any.
metelhammer said:
I still do not get it what exact issue you have and what version of MIUI you are on.
You are saying you are on MIUI Pro and that confirms bootloader is unlocked and now you are saying
Please share exact and more details if you wish to resolve your issue and possibly some screenshot(s) of about phone and errors if any.
Click to expand...
Click to collapse
I have a similar issue and came across this thread, usb debugging suddenly stopped working, it was working perfectly till yesterday. So when I went to developer options, I saw that the OEM unlocking option is clickable now ( it had remained grayed out ever since I unlocked the bootloader ). The Mi Unlock status option tells me that phone is locked. Toggling usb debugging is not making it work. When I restart the phone, I definitely see the unlocked padlock icon on the boot screen. So I am not sure what is going on. also, magisk is working fine.
In the screenshot you can see that it shows the device is locked. But from the status bar you can make out that exposed is working. I'll have to get another device though to get a picture of the padlock icon though.
Ontropy said:
I have a similar issue and came across this thread, usb debugging suddenly stopped working, it was working perfectly till yesterday. So when I went to developer options, I saw that the OEM unlocking option is clickable now ( it had remained grayed out ever since I unlocked the bootloader ). The Mi Unlock status option tells me that phone is locked. Toggling usb debugging is not making it work. When I restart the phone, I definitely see the unlocked padlock icon on the boot screen. So I am not sure what is going on. also, magisk is working fine.
In the screenshot you can see that it shows the device is locked. But from the status bar you can make out that exposed is working. I'll have to get another device though to get a picture of the padlock icon though.
Click to expand...
Click to collapse
Toggle OEM unlock enabled doesn´t mean that the device is unlocked, it only means that the bootloader can be unlocked, there is other item just lines after to check it; Mi Unlock status, enter to it and confirm it.
Also, you can confirm the bootloader status through fastboot with fastboot oem device-info
SubwayChamp said:
Toggle OEM unlock enabled doesn´t mean that the device is unlocked, it only means that the bootloader can be unlocked, there is other item just lines after to check it; Mi Unlock status, enter to it and confirm it.
Also, you can confirm the bootloader status through fastboot with fastboot oem device-info
Click to expand...
Click to collapse
Yea as I mentioned, the mi unlock status tells me that phone is locked.
Just check via fastboot, and it shows that phone is unlocked.
So do I just believe fastboot, or wait a month and then try to again unlock the bootloader via the mi unlock tool?
Ontropy said:
Yea as I mentioned, the mi unlock status tells me that phone is locked.
Just check via fastboot, and it shows that phone is unlocked.
So do I just believe fastboot, or wait a month and then try to again unlock the bootloader via the mi unlock tool?
Click to expand...
Click to collapse
You said "In the screenshot you can see that it shows the device is locked" but unfortunately the screenshot didn´t reveal that, I wonder, what exactly it says in the Mi Unlock status apart.
In older days, users share an aboot image, this served to unlock bootloader automatically without make the official process to unlock it, it could be that you flashed the official stock images, and it got re-locked. Anyway, we don´t know what happened with the fastboot command or with the Mi Unlock status section, so no respond to those points.
For the part you say to wait a certain time, definitely, no, the bootloader process is not monitored any more, for older devices, they can be unlocked instantly.
SubwayChamp said:
You said "In the screenshot you can see that it shows the device is locked" but unfortunately the screenshot didn´t reveal that, I wonder, what exactly it says in the Mi Unlock status apart.
In older days, users share an aboot image, this served to unlock bootloader automatically without make the official process to unlock it, it could be that you flashed the official stock images, and it got re-locked. Anyway, we don´t know what happened with the fastboot command or with the Mi Unlock status section, so no respond to those points.
For the part you say to wait a certain time, definitely, no, the bootloader process is not monitored any more, for older devices, they can be unlocked instantly.
Click to expand...
Click to collapse
My phone is about a month old, so it does tell me to wait. Contradictory screenshots attached below. After the boot unlock, I did flash flash a magisk edited boot.img and vbmeta.img to disable it. If I remember correctly though it was fine after that.
Bootloader Unlocked & Rooted with magisk 20+ but still gets bootloader locked status
Hi.,
I am using this device from past 6Months when it was in miui 10 everything was normal like after unlocking the device and rooting device showed Bootloader status as unlocked in Developer settings but after updating to miui 11 in Developer settings it shows bootloader is locked, I haven't checked it before but when Using XiaomiAdbFasbootTools to debloat some apps it was showing bootloader locked so went to developer settings to check, while rebooting device it still shows unlocked at the bottom, can anyone check how your device is behaving
its weird..im updating to miui 11 too few weeks ago using twrp method..my device still rooted now..but on developer setting...its showing that my device is locked..i still have magisk running perfectly and still have twrp installed..maybe it is bug?
This is happening also for me! I think that's a bug.
Don't mind that because if you the unlocked is showing to your boot logo meaning you are still unlocked
I was also gonna say I'm having this; bootloader shows as unlocked during boot but both Xiaomi ADB tools and the developer settings sub-menu for unlock status show locked.
The issue is most likely Magisk hiding root. According to a support ticket on Xiaomi ADB tools;
Magisk hides the fact that you are unlocked and rooted and it spoofs ADB too, that's why it reports that you are locked.
Click to expand...
Click to collapse
So this may be a consequence of that.
Hello, yesterday as i was browsing Developer tools in the settings, i came upon a new options they seem to stealthily added sometime ago, OEM Unlock. Just a switch and Bootloader got unlocked. A bit too late since nobody developed any roms for this device.
That isn't how bootloader unlocking works. That setting only allows you to enter the unlock code while in fastboot mode. In the end, you still need a bootloader unlock code to unlock it. I am certain the switch has been present there for a while now.