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
I can't unlock the bootloader becouse frp is lock. when I put oem on in development option, frp stay lock. Why Please help me
When I put fastboot oem unlock say remote command not allowed
Wire1122 said:
I can't unlock the bootloader becouse frp is lock. when I put oem on in development option, frp stay lock. Why Please help me
When I put fastboot oem unlock say remote command not allowed
Click to expand...
Click to collapse
The switch "usb debugging on" likes to jump back again. You have to repeat the setting on the screenshot 3 to 4 times if you want to keep debugging.
ChinHon said:
The switch "usb debugging on" likes to jump back again. You have to repeat the setting on the screenshot 3 to 4 times if you want to keep debugging.
Click to expand...
Click to collapse
debugging works. It is oem unlock development that not works in my case
Wire112233 said:
debugging works. It is oem unlock development that not works in my case
Click to expand...
Click to collapse
Remove the google account or make a factoryreset.
Problem still there
Can you help me. Frp still locked. In Huawei support says me that the phone is ok
Wire112233 said:
Can you help me. Frp still locked. In Huawei support says me that the phone is ok
Click to expand...
Click to collapse
You must unlock the phone by huawei unlockcode.
ChinHon said:
You must unlock the phone by huawei unlockcode.
Click to expand...
Click to collapse
ok but command not allowed in fastboot becouse frp still locked
Is the oem now unlocked in developer options?
ChinHon said:
You must unlock the phone by huawei unlockcode.
Click to expand...
Click to collapse
ChinHon said:
Is the oem now unlocked in developer options?
Click to expand...
Click to collapse
yes
Then the unlocking must also work. Restart the pc, take another usb cable, restart the bootloader.
If that doesn't help, go to my root thread and follow the instructions for the UPDATE.APP from the last thread update.
ChinHon said:
Then the unlocking must also work. Restart the pc, take another usb cable, restart the bootloader.
If that doesn't help, go to my root thread and follow the instructions for the UPDATE.APP from the last thread update.
Click to expand...
Click to collapse
I will try
Wire112233 said:
I will try
Click to expand...
Click to collapse
the update is successfull installed but frp still locked such oem development option activated
Wire1122 said:
the update is successfull installed but frp still locked such oem development option activated
Click to expand...
Click to collapse
"Developer options" - "OEM unlocking" must be ON, without this FRP will be locked.
GDStaff said:
"Developer options" - "OEM unlocking" must be ON, without this FRP will be locked.
Click to expand...
Click to collapse
Oem unlocking is on but frp still lock
Problem solved. Disable oem unlock in development option. Factory reset the phone and reanable oem unlock. Now frp is unlocked
Hello I have a new Moto G6. I have enabled developer options and I've enabled OEM unlocking. But it doesn't seem to stay enabled between reboots? I just bought this yesterday. I'm trying to unlock the bootloader, but I can't unless OEM unlocking stays enabled. Am I missing something? I know there's currently no root for the G6, but still I think I should be able to unlock it, or am I mistaken?
jloh1963 said:
Hello I have a new Moto G6. I have enabled developer options and I've enabled OEM unlocking. But it doesn't seem to stay enabled between reboots? I just bought this yesterday. I'm trying to unlock the bootloader, but I can't unless OEM unlocking stays enabled. Am I missing something? I know there's currently no root for the G6, but still I think I should be able to unlock it, or am I mistaken?
Click to expand...
Click to collapse
That just allows the bootloader to be unlocked. You still would need to actually unlock it following the unlocking guide thread in the guides section
dejello said:
That just allows the bootloader to be unlocked. You still would need to actually unlock it following the unlocking guide thread in the guides section
Click to expand...
Click to collapse
Yes I know this is not root, this is just unlocking the bootloader, yes I do have a key from motorola. But I can't do anything if OEM unlocking will not persist between reboots. I'm just trying to unlock the bootloader. And yes it is unlocked for sims.
jloh1963 said:
Yes I know this is not root, this is just unlocking the bootloader, yes I do have a key from motorola. But I can't do anything if OEM unlocking will not persist between reboots. I'm just trying to unlock the bootloader. And yes it is unlocked for sims.
Click to expand...
Click to collapse
I said nothing of root. Unless I am missing something from your original post, "Allow OEM unlocking" just allows the bootloader to be unlockable. After you tick it, reboot directly into fastboot mode (not back into android, that'll untick it again).
[GUIDE] Unlock Bootloader - This states after enabling OEM Unlock in settings (from within Android) to reboot into the bootloader (This guide says power off and then power back on while holding volume down, if you have debugging on you can just "adb reboot bootloader"). Rebooting back into Android with the bootloader still locked I believe does untick the OEM Unlock option.
ok thanks, I'll try again.
I have the XT 1925-6 US unlocked version. One of the first things I do with a new phone is to enable Developer Options and toggle OEM Unlock even though I may not Unlock the Bootloader right away.
The OEM Unlock toggle has stayed persistently on through numerous reboots with the Bootloader still locked.
Hmm.. Well I could have sworn I had seen what was described before, however it has been a while. I unlocked mine all in one go so I can't say. If it's supposed to stay on then I'd really be curious why it isn't for jloh
dejello said:
Hmm.. Well I could have sworn I had seen what was described before, however it has been a while. I unlocked mine all in one go so I can't say. If it's supposed to stay on then I'd really be curious why it isn't for jloh
Click to expand...
Click to collapse
I tried it again and it worked, thanks. I guess I rebooted android at first. Thank you.
I dont know how ( i think i did it when i open oem lock [unlock]) but my FRP lock status is "FRP Unlock"
Can it cause to prevent me to install new roms on my phone and if yes, how can i lock back?
Thanks....
any_body said:
I dont know how ( i think i did it when i open oem lock [unlock]) but my FRP lock status is "FRP Unlock"
Can it cause to prevent me to install new roms on my phone and if yes, how can i lock back?
Thanks....
Click to expand...
Click to collapse
If you don't have Bootloader unlocked just go to Settings /System/ Developer options and switch off OEM Unlock (=FRP Unlock)
Btw, there is no need for panic because of unlocked FRP (and/or because of its warning while booting
zgfg said:
If you don't have Bootloader unlocked just go to Settings /System/ Developer options and switch off OEM Unlock (=FRP Unlock)
Btw, there is no need for panic because of unlocked FRP (and/or because of its warning while booting
Click to expand...
Click to collapse
Dear @zgfg ;
First of all thanks for your reply.
Oem Unlock is enabled (blue) and cant be in changeble status in Settings on my P9 (EVA L09)
any_body said:
Dear @zgfg ;
First of all thanks for your reply.
Oem Unlock is enabled (blue) and cant be in changeble status in Settings on my P9 (EVA L09)
Click to expand...
Click to collapse
You didn't state here but from your another post (you installed RR), you unlocked Bootloader and therefore obviously you had to unlock OEM/FRP
If you don't like unlocked FRP, then you first go back to stock Nougat, re-lock Bootloader and forget about rooting, installing custom ROMs, etc - for all that you must have unlocked Bootloader AND unlocked FRP
i need do UNLOCK FRP but on OREO i cant find setting UNLOCK OEM...
EDIT: sorry i read now "Chinese Brands dont have FRP." so i can install directly OPENKIRIN rom without FRP check . My bootloader is unlock
miksly said:
i need do UNLOCK FRP but on OREO i cant find setting UNLOCK OEM...
Click to expand...
Click to collapse
On the 'Chinese' Oreo there is no OEM unlock option in Developers Options, and OEM/FRP always stays unlocked - please consult HWOTA7 OP instructions.
OEM/FRP stays unlocked also if going to Open Kirin ROMs and back (if f
the required installation procedure is followed)
Check in Fastboot, maybe only your Bootloader is locked, and you just need to unlock Bootloader again in Fastboot
miksly said:
i need do UNLOCK FRP but on OREO i cant find setting UNLOCK OEM...
EDIT: sorry i read now "Chinese Brands dont have FRP." so i can install directly OPENKIRIN rom without FRP check . My bootloader is unlock
Click to expand...
Click to collapse
Ok, be careful to follow OpenKirin installation guide
Btw, there was a trick to re-enable hidden OEM Unlock option in Oreo, post in the HWOTA7 thread:
https://forum.xda-developers.com/p9...date-tool-hwota7-p9-eva-t3820849/post77296996
With root, open from eg MiXPlorer:
/hw_oem/prop/local.prop
find and uncomment the line (remove trailing character #):
ro.frp.pst=/dev/block/platform/hi_mci.0/by-name/frp
Then reboot, open Settings/System/Developer options and find the belowed OEM Unlock option (see attachments)