Hi everyone
I am trying to back up my TA partition using @j4nn's tool and I successfully downgraded to 47.1.A.8.49 and archived my partition. Now I am trying to unlock my bootloader.
In the service menu, the rooting status states:
>Bootloader unlock allowed: Yes
and the "ro.oem_unlock_supported" property is set to 'True'.
However, in developer options, the toggle for OEM Unlocking is greyed out and the "ro.boot.flash.locked" property is also set to 1. Also unlocking in fastboot fails with 'command not allowed'
Has anyone encountered a situation like this where bootloader unlocking is allowed but the toggle is disabled? Is it related to downgrading to 47.1.A.8.49?
tabbed said:
Hi everyone
I am trying to back up my TA partition using @j4nn's tool and I successfully downgraded to 47.1.A.8.49 and archived my partition. Now I am trying to unlock my bootloader.
In the service menu, the rooting status states:
>Bootloader unlock allowed: Yes
and the "ro.oem_unlock_supported" property is set to 'True'.
However, in developer options, the toggle for OEM Unlocking is greyed out and the "ro.boot.flash.locked" property is also set to 1. Also unlocking in fastboot fails with 'command not allowed'
Has anyone encountered a situation like this where bootloader unlocking is allowed but the toggle is disabled? Is it related to downgrading to 47.1.A.8.49?
Click to expand...
Click to collapse
You truly got me. Just checked it on my (still locked) xz1c and I had the option greyed too, could not be enabled.
I guess it is not enabled by default unless the phone goes online on internet at least one time.
As suggested with the option, if you connect to internet, it gets enabled - just tested it.
Please post your results in the exploit thread. Thanks.
j4nn said:
You truly got me. Just checked it on my (still locked) xz1c and I had the option greyed too, could not be enabled.
I guess it is not enabled by default unless the phone goes online on internet at least one time.
As suggested with the option, if you connect to internet, it gets enabled - just tested it.
Please post your results in the exploit thread. Thanks.
Click to expand...
Click to collapse
That was it, thank you! I'll post results in the other thread.
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
Hiya! I was in the process of unlocking my bootloader. I flashed a 28.0.A.8.266_R12A_Hong King Generic rom and on the process of fastbooting to unlock the bootloader. I have tried both methods for the command prompt as well as using the flashtool versions 0.9.19 and 0.9.23, to no avail. I've already acquired my key from sony, and respectively replaced the usb driver file indicated to be replaced, disabled my xperia and did the appropriate steps and it says:
FAILED <remote:Command not allowed>
I have already checked with the configuration wherein the rooting status indicates that Bootloader unlock allowed:Yes
I have been scouring the whole day for any plausible solution, right now I have flashed a 6.0.1 and have lost my capabilities of connecting to my mobile internet for some apparent reason and my network/signal has become mundane. Which my case is very similar to the gentleman that posted this Link
Any plausible assistance or solution would be very welcome and very much appreciated. Thank you so much in advance!
On another note, I was wondering if the region of the firmware affects any of the configuration of the signal acquisition or what not, it has been very disheartening to lose my mobile network. But then again thank you very much for any insight whatsover.
EDIT: Solve - Please take down if necessary
Updated to latest firmware in Nougat. It currently has an enable oem to unlock bootloader in developer options. Tick that off then try unlocking bootloader again once all initial conditions are met.
[E6533] Boot Loader Unlock: FAILED <remote:Command not allowed
try this
https://www.youtube.com/watch?v=Qkl9UyrQKSo
try to disable driver check signature
use the lastest update of flashtool
avid_reader said:
Hiya! I was in the process of unlocking my bootloader. I flashed a 28.0.A.8.266_R12A_Hong King Generic rom and on the process of fastbooting to unlock the bootloader. I have tried both methods for the command prompt as well as using the flashtool versions 0.9.19 and 0.9.23, to no avail. I've already acquired my key from sony, and respectively replaced the usb driver file indicated to be replaced, disabled my xperia and did the appropriate steps and it says:
FAILED <remote:Command not allowed>
I have already checked with the configuration wherein the rooting status indicates that Bootloader unlock allowed:Yes
I have been scouring the whole day for any plausible solution, right now I have flashed a 6.0.1 and have lost my capabilities of connecting to my mobile internet for some apparent reason and my network/signal has become mundane. Which my case is very similar to the gentleman that posted this Link
Any plausible assistance or solution would be very welcome and very much appreciated. Thank you so much in advance!
On another note, I was wondering if the region of the firmware affects any of the configuration of the signal acquisition or what not, it has been very disheartening to lose my mobile network. But then again thank you very much for any insight whatsover.
EDIT: Solve - Please take down if necessary
Updated to latest firmware in Nougat. It currently has an enable oem to unlock bootloader in developer options. Tick that off then try unlocking bootloader again once all initial conditions are met.
Click to expand...
Click to collapse
Have you checked the "USB debugging mode". it should be on
Follow this Link: Link
Hiya all!
Thanks for responses! I've actually resolved it for the e6533. I've updated to the latest firmware via the xperia companion and then in the developer options they have a new option which is unlock oem which permitted me to unlock bootloader through fastboot. Thank you again for the ideas!
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.
Good morningI bought a moto g50 italy but the oem developer option is not editable. so despite having received the motorola unlock code I can't unlock bootloader. is there a string in adb to activate it? Thank you
cicciomix said:
Good morningI bought a moto g50 italy but the oem developer option is not editable. so despite having received the motorola unlock code I can't unlock bootloader. is there a string in adb to activate it? Thank you
Click to expand...
Click to collapse
Why is OEM Unlocking greyed out?
I have tried many times to perform the unlocking procedure. Everything perfect I get the code from motorola but the answer is always the same check oem unlocking in android setting developer Failed. I do not know what to do. the phone has been connected to wifi for a day but the oem unlock option is always not editable. Help me
cicciomix said:
I have tried many times to perform the unlocking procedure. Everything perfect I get the code from motorola but the answer is always the same check oem unlocking in android setting developer Failed. I do not know what to do. the phone has been connected to wifi for a day but the oem unlock option is always not editable. Help me
Click to expand...
Click to collapse
You did not read my thread.
It can OEM allow unlock can take 3-14 days, after connection to internet
sd_shadow said:
You did not read my thread.
It can OEM allow unlock can take 3-14 days, after connection to internet
Click to expand...
Click to collapse
Yes thanks I read and I'm waiting.even if it seems absurd to me. I'll let you know. at the moment the phone is always on connected to wifi