OEM-Unlock setting grayed out on ON. - Nexus 6 Q&A, Help & Troubleshooting

Just noticed that its default is greyed out on ON setting on 7.0.
I participated in the test build program thingy and did a fresh flash of stock before hand.
And i'm now on default 7.0 NBD90Z.
Did they drop this setting all together now??

ghost010 said:
Just noticed that its default is greyed out on ON setting on 7.0.
I participated in the test build program thingy and did a fresh flash of stock before hand.
And i'm now on default 7.0 NBD90Z.
Did they drop this setting all together now??
Click to expand...
Click to collapse
From what I was told in another forum, its like that on "n" to prevent a accidental press to lock it back....

ghost010 said:
Did they drop this setting all together now??
Click to expand...
Click to collapse
Apparently. And I'm very happy with this, because it was Google's most stupid idea ever. In no way was the risk of bricking your phone with an OTA (a rather high risk, unfortuantely) worth the benefit, that a thief would throw your phone in the garbage, because it's useless for him.

Yeah very bad things happen if you "accidentally" hit that relock button.....

My BL was unlocked on MM but when ota to N the OEM thingy is now greyed on Disabled.
Checked in bootloader mode still shows Unlocked.
Any biggie?
---------- Post added at 01:00 AM ---------- Previous post was at 12:56 AM ----------
To be more precise. When I was bl unlocked on MM I kept the Dev option menu off. When dev options menu is off the OEM switch will slide to disable. It was in this situation that I OTA to release N
Any advice?

baw580 said:
From what I was told in another forum, its like that on "n" to prevent a accidental press to lock it back....
Click to expand...
Click to collapse
It is PURELY a COSMETIC change.
When the bootloader IS unlocked, they disable the button to ENABLE unlocking.
Even if they didn't disable the button, it wouldn't actually make a difference, since IT NEVER CAUSED THE BOOTLOADER TO LOCK TO BEGIN WITH!!!! You would STILL have to go to fastboot and "fastboot oem lock" or "fastboot flashing lock" the thing, which CANNOT be disabled by that button.
All that button EVER did, was ENABLE the UNLOCK process.

doitright said:
It is PURELY a COSMETIC change.
When the bootloader IS unlocked, they disable the button to ENABLE unlocking.
Even if they didn't disable the button, it wouldn't actually make a difference, since IT NEVER CAUSED THE BOOTLOADER TO LOCK TO BEGIN WITH!!!! You would STILL have to go to fastboot and "fastboot oem lock" or "fastboot flashing lock" the thing, which CANNOT be disabled by that button.
All that button EVER did, was ENABLE the UNLOCK process.
Click to expand...
Click to collapse
I think it also disables FRP... But I'm not 100% on that one

I am reading this and decided to have a look-see. Mine is grayed out too, but in the off position. I am unlocked, rooted, stock otherwise.

Related

[Q] I think I hard bricked my N6

Hi there,
So I just bought a brand new N6.
Did nothing to it, did not unklock the bootloader, di not flash anything.
Just ran it a first time, set my account, donwloaded the 5.1 OTA when proposed to and then it was over.
After the OTA installation my phone displayed a dead android and "Error".
When rebooting my phone, the apps are "optimizing" undefinitely and then the phone will restart.
I tried factory reset from recovery, that did nothing, I mean, the phone will still bootloop endlessly.
My bootloader is not unlocked so I cannot flash my phone..
Is there anything I can do ?
Thank you in advance
Aanze said:
Hi there,
So I just bought a brand new N6.
Did nothing to it, did not unklock the bootloader, di not flash anything.
Just ran it a first time, set my account, donwloaded the 5.1 OTA when proposed to and then it was over.
After the OTA installation my phone displayed a dead android and "Error".
When rebooting my phone, the apps are "optimizing" undefinitely and then the phone will restart.
I tried factory reset from recovery, that did nothing, I mean, the phone will still bootloop endlessly.
My bootloader is not unlocked so I cannot flash my phone..
Is there anything I can do ?
Thank you in advance
Click to expand...
Click to collapse
try fastboot formatting userdata and fastboot formatting cache
simms22 said:
try fastboot formatting userdata and fastboot formatting cache
Click to expand...
Click to collapse
Same story.
Black screen then reboot, then optimizing then reboot and so on...
Aanze said:
Same story.
Black screen then reboot, then optimizing then reboot and so on...
Click to expand...
Click to collapse
Well, since you haven't enabled OEM unlock, there's not much you can do besides RMA at this point.
Aanze said:
Same story.
Black screen then reboot, then optimizing then reboot and so on...
Click to expand...
Click to collapse
unfortunately, that might have been your only option. as you need to boot up first, to enable unlocking of your bootloader, to reflash the factory image. and you cant boot up
Evolution_Tech said:
Well, since you haven't enabled OEM unlock, there's not much you can do besides RMA at this point.
Click to expand...
Click to collapse
That's what I thought.
I thought I could use the fix described here http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518 but my device does not appear as "qhusb_bulk" like specified so I guess its over.
id get the phone refurbished, from google or from motorola, since it wasnt anything that you did, but was the updates fault. btw, that happens, very rarely, but it does happen that updates can cause issues.
simms22 said:
id get the phone refurbished, from google or from motorola, since it wasnt anything that you did, but was the updates fault. btw, that happens, very rarely, but it does happen that updates can cause issues.
Click to expand...
Click to collapse
Well thank you anyway, looks like I have no other choice than send the device back.
One last question, since my phone won't stop rebooting endlessly is there any way to turn it off ? Long press on power does not do anythng, it will stil restart...
Edit: I found how to turn it off through bootloader.
Aanze said:
Well thank you anyway, looks like I have no other choice than send the device back.
One last question, since my phone won't stop rebooting endlessly is there any way to turn it off ? Long press on power does not do anythng, it will stil restart...
Edit: I found how to turn it off through bootloader.
Click to expand...
Click to collapse
exactly. i was just gonna write how to do that.
simms22 said:
exactly. i was just gonna write how to do that.
Click to expand...
Click to collapse
Sorry to come back on this thread.
So now I have noticed that when in fastboot, if I type "fastboot oem unlock" I'm getting the popup proposing to unlock bootloader.
As I never selected USB debugging nor enabled developper option when my phone was working, I doubt it would work properly.
Would I have any chance to recover my phone if choosing to unlock the bootloader ?
Aanze said:
Sorry to come back on this thread.
So now I have noticed that when in fastboot, if I type "fastboot oem unlock" I'm getting the popup proposing to unlock bootloader.
As I never selected USB debugging nor enabled developper option when my phone was working, I doubt it would work properly.
Would I have any chance to recover my phone if choosing to unlock the bootloader ?
Click to expand...
Click to collapse
If getting that it should unlock. Got nothing to lose and if does unlock it is recoverable.
Aanze said:
Sorry to come back on this thread.
So now I have noticed that when in fastboot, if I type "fastboot oem unlock" I'm getting the popup proposing to unlock bootloader.
As I never selected USB debugging nor enabled developper option when my phone was working, I doubt it would work properly.
Would I have any chance to recover my phone if choosing to unlock the bootloader ?
Click to expand...
Click to collapse
yes! if you can unlock the bootloader, then you can flash the factory image via fastboot while youre in your bootloader. which would fix you not booting
prdog1 said:
If getting that it should unlock. Got nothing to lose and if does unlock it is recoverable.
Click to expand...
Click to collapse
Wow.. So I tried.. and.. "Device is unlocked" is displayed... I guess I have a chance to flash something now.
Aanze said:
Wow.. So I tried.. and.. "Device is unlocked" is displayed... I guess I have a chance to flash something now.
Click to expand...
Click to collapse
Your good to go. Just need to fastboot the stock images.
just return it, if you find that you cant recover it after unlocking the bootloader then they wont take it back
Aanze said:
Wow.. So I tried.. and.. "Device is unlocked" is displayed... I guess I have a chance to flash something now.
Click to expand...
Click to collapse
grab a factory image, and read directions for flashing a factory image. you want to flash each individual file inside separately, instead of using the flash-all script.
simms22 said:
grab a factory image, and read directions for flashing a factory image. you want to flash each individual file inside separately, instead of using the flash-all script.
Click to expand...
Click to collapse
Yep, doing it right now.. flashing system currently.. crossing fingers;.
crossing my fingers for you over here as well
It worked !! IT WORKED !
I love you xda ! really do love you.
Thanks a million.
(Although it's a bit strange that I was able to unlock bootloader without usb debbugging mode enabled no ?)
This is very interesting indeed. To the OP, where did you purchase the device? I find it very peculiar that you were able to issue the OEM unlock command without using the toggle in settings.

OEM Unlock is on... but returns as "disabled"

I had to get a new Nexus because I lost my previous one. Now I'm trying to root this one but I can't seem to get the OEM Unlock setting to work. I've rebooted it, factory reset it, enabled/disabled the option countless times, enabled/disabled USB debugging... nothing. Google doesn't seem to have an answer either. Anyone has any idea what's going on? Or if there's another way to unlock this setting?
Thanks for your time!
Just to clarify, are you actually attemping to unlock it? You have to first enable that option in developer settings, but you still have to put the phone in bootloader mode and run the command "fastboot oem unlock", then use the buttons on the phone to confirm it. I think all your data wipes first time you unlock your bootloader too so just be careful.
SilverSix said:
I had to get a new Nexus because I lost my previous one. Now I'm trying to root this one but I can't seem to get the OEM Unlock setting to work. I've rebooted it, factory reset it, enabled/disabled the option countless times, enabled/disabled USB debugging... nothing. Google doesn't seem to have an answer either. Anyone has any idea what's going on? Or if there's another way to unlock this setting?
Thanks for your time!
Click to expand...
Click to collapse
Depending the Android build installed, sometimes the option has been greyed out. Don't know why...
You said you tried to get the "OEM unlock" slider working... But did you try issuing the unlock command in bootloader?
Good luck...
Yeah, I'm aware it wipes your device. Also, don't burn me but I was using a Toolkit to start the process but I just gave up and did it the old fashioned way. After restarting into bootloader and sending the fastboot command it prompted the question to unlock it, so everything went smoothly.
Somewhere I had read that Android purposely locks OEM unlocking after n reboots, and I thought I was completely out of luck, but everything went smoothly. Thanks for your time!

[Exynos] Questions concering OEM Unlock

-This is probably going to be confusing and a bit all over the place, bear with me.-
So, I bought my N8 back in November and directly went in to the dev options and saw OEM Unlock was available.
Now I didn't bother with it and now recently I've been thinking about rooting it, the catch is I've seen countless threads claiming a notorious "RMM"-lock taking place and putting devices in to "Jail".
Here's the sketchy bit:
- I rebooted and checked in DL-Mode and saw no particular line referencing RMM. Then after some reading got buildprop editor and checked what the "ro.security.vaultkeeper.feature" status was; It's 1.
- Rebooted again, double checked and no RMM entry.
- Enabled OEM Unlock and rebooted about 3-6 times (no flashing done) and it booted up fine with the OEM Unlock setting still enabled and present.
- DL Mode still does NOT show any RMM message or line, just "OEM lock" and "FRP lock" are off.
Am I missing some information as to how the "Jail" is triggered or does flashing only trigger the "Jail"?
BTW, here's info on my device:
- N950F, unlocked, Germany
- On latest January Patch, N950FXXU3BRA2
- Non-branded, but marked as DBT
SaadatM said:
-This is probably going to be confusing and a bit all over the place, bear with me.-
So, I bought my N8 back in November and directly went in to the dev options and saw OEM Unlock was available.
Now I didn't bother with it and now recently I've been thinking about rooting it, the catch is I've seen countless threads claiming a notorious "RMM"-lock taking place and putting devices in to "Jail".
Here's the sketchy bit:
- I rebooted and checked in DL-Mode and saw no particular line referencing RMM. Then after some reading got buildprop editor and checked what the "ro.security.vaultkeeper.feature" status was; It's 1.
- Rebooted again, double checked and no RMM entry.
- Enabled OEM Unlock and rebooted about 3-6 times (no flashing done) and it booted up fine with the OEM Unlock setting still enabled and present.
- DL Mode still does NOT show any RMM message or line, just "OEM lock" and "FRP lock" are off.
Am I missing some information as to how the "Jail" is triggered or does flashing only trigger the "Jail"?
BTW, here's info on my device:
- N950F, unlocked, Germany
- On latest January Patch, N950FXXU3BRA2
- Non-branded, but marked as DBT
Click to expand...
Click to collapse
You unlock the toggle and flash twrp, etc., then when you boot back up you must ensure the i.e. unlock is toggled on (or else toggle it). Otherwise you'll end up in jail when you reboot again, since you flashed custom and didn't unlock OEM before the new reboot.
This question could have been asked in the oem unlock thread too
sefrcoko said:
You unlock the toggle and flash twrp, etc., then when you boot back up you must ensure the i.e. unlock is toggled on (or else toggle it). Otherwise you'll end up in jail when you reboot again, since you flashed custom and didn't unlock OEM before the new reboot.
This question could have been asked in the oem unlock thread too
Click to expand...
Click to collapse
Alright, I'll check that and see if i'm also in the boat.
Odd enough that it toggles itself off automaticallly, that is wondering me.
Weird.
sefrcoko said:
You unlock the toggle and flash twrp, etc., then when you boot back up you must ensure the i.e. unlock is toggled on (or else toggle it). Otherwise you'll end up in jail when you reboot again, since you flashed custom and didn't unlock OEM before the new reboot.
This question could have been asked in the oem unlock thread too
Click to expand...
Click to collapse
SaadatM said:
Alright, I'll check that and see if i'm also in the boat.
Odd enough that it toggles itself off automaticallly, that is wondering me.
Click to expand...
Click to collapse
Yep, just as I suspected; Your idea didn't apply @sefrcoko .
I installed TWRP, Magisk, the no-dmverity (in that order) and booted perfectly fine with the following result:
- Dev options were hidden since DATA was formatted
- After opening Dev options the OEM Unlock was still switched on.
That has me thinking if it is either sw or hw related, that some devices lock-up.
SaadatM said:
Yep, just as I suspected; Your idea didn't apply @sefrcoko .
I installed TWRP, Magisk, the no-dmverity (in that order) and booted perfectly fine with the following result:
- Dev options were hidden since DATA was formatted
- After opening Dev options the OEM Unlock was still switched on.
That has me thinking if it is either sw or hw related, that some devices lock-up.
Click to expand...
Click to collapse
You asked what jail was, and I explained it... You're just not in jail. Not every device is affected, and fixes to prevent the issue are being baked into custom roms and .zips now too. Lots of factors at play, hence the monster OEM Unlock thread . RMM seems to be the culprit.
sefrcoko said:
You asked what jail was, and I explained it... You're just not in jail. Not every device is affected, and fixes to prevent the issue are being baked into custom roms and .zips now too. Lots of factors at play, hence the monster OEM Unlock thread . RMM seems to be the culprit.
Click to expand...
Click to collapse
Figured not every device is effected.
Appreciate the input though.

XT1925-3 OEM Unlock disabled/greyed

Hi!
I'm from Brazil and I bought a Moto G6 XT1925-3.
I want to unlock bootloader but the option OEM Unlock is greyed out on Developer Options.
I tried RSD Lite with many firmware available on https://mirrors.lolinet.com/firmware/moto/ali/official but none worked.
Does someone have a tip?
Thanks!
I had the exact same problem. To fix it, I had to enable WiFi and get connected to the Interwebs. Wait a couple minutes to see if the option becomes available. If it does not, disable developer options, and re-enable it. That worked for me.
juicypoot said:
I had the exact same problem. To fix it, I had to enable WiFi and get connected to the Interwebs. Wait a couple minutes to see if the option becomes available. If it does not, disable developer options, and re-enable it. That worked for me.
Click to expand...
Click to collapse
I already tried everything that is possible!
I flahed retail firmware through RSD Lite and nothing happens: allow oem unlock greyed out.
Maybe your OEM is already unlocked. Try running this command: fastboot oem device-info in fastboot and see what it says
Guys, it's true!
After some days the 'Allow OEM Unlock' option became enable!
I did nothing! It's a matter of time, considered as a security measure.
That's it!
adrianogoes said:
Guys, it's true!
After some days the 'Allow OEM Unlock' option became enable!
I did nothing! It's a matter of time, considered as a security measure.
That's it!
Click to expand...
Click to collapse
Still waiting here. How much time did you wait?
You can also try to delete user 999 and oem option should reflect under dev option.
bhati2710 said:
You can also try to delete user 999 and oem option should reflect under dev option.
Click to expand...
Click to collapse
What do you mean? Please explain
You need to connect your mobile to wifi and follow steps for date change to year back.
Then look for software update. This would resolve it.
Here is the reference;
Hope it helps.
bhati2710 said:
You need to connect your mobile to wifi and follow steps for date change to year back.
Then look for software update. This would resolve it.
Here is the reference;
Hope it helps.
Click to expand...
Click to collapse
Thanks for replying, but this didn't work. I tried one year, one month, 7 days before and after and it still is grayed out :crying:
@mrsiri Are you trying to unlock the bootloader or is it already unlocked?
WoKoschekk said:
@mrsiri Are you trying to unlock the bootloader or is it already unlocked?
Click to expand...
Click to collapse
Trying to unlock it. I locked it by mistake and now need to wait 7 days for the OEM Unlock button in developer settings to be enabled. It could also be locked forever ( Is it possible?) but then there's no hope for me.
Edit: I can also boot the stock room boot.img image but that doesn't help with the OEM Unlock button. it is still grayed out. What I could do is boot a magisk patched image to get root, but by doing this all my phone did was reboot twice and forcing me to factory reset and then use the old regular non patched boot image that I'm currently using. My current flashed boot image has verity mode off, in case that could help into anything.
Thanks in advance for replying
mrsiri said:
Trying to unlock it. I locked it by mistake and now need to wait 7 days for the OEM Unlock button in developer settings to be enabled. It could also be locked forever ( Is it possible?) but then there's no hope for me.
Edit: I can also boot the stock room boot.img image but that doesn't help with the OEM Unlock button. it is still grayed out. What I could do is boot a magisk patched image to get root, but by doing this all my phone did was reboot twice and forcing me to factory reset and then use the old regular non patched boot image that I'm currently using. My current flashed boot image has verity mode off, in case that could help into anything.
Thanks in advance for replying
Click to expand...
Click to collapse
Your bootloader seems to be unlocked. It is not possible to flash another boot.img with a locked bootloader. What else should be the purpose of a unlocked bootloader?? This is the prerequisite to flash a ROM or a twrp.img
---------- Post added at 05:52 PM ---------- Previous post was at 05:49 PM ----------
What exactly is the text right under the toggle to turn on the OEM unlocking option?
WoKoschekk said:
Your bootloader seems to be unlocked. It is not possible to flash another boot.img with a locked bootloader. What else should be the purpose of a unlocked bootloader?? This is the prerequisite to flash a ROM or a twrp.img
---------- Post added at 05:52 PM ---------- Previous post was at 05:49 PM ----------
What exactly is the text right under the toggle to turn on the OEM unlocking option?
Click to expand...
Click to collapse
The text is "connect to the internet or contact your carrier". I didn't flash the boot.img, but booted it. Like when you boot TWRP, but in this case it was the original stock boot.img
My bootloader says "flashing_locked", so it is not fully unlocked. And I can't unlock it without enabling the "OEM Unlock" Button ?
Yes, you have to wait.
WoKoschekk said:
Yes, you have to wait.
Click to expand...
Click to collapse
In the end I sent my device to a repair service. Thanks for the help, but I can't rely on waiting 7 days and assuming the button will re-enable itself. I need it fixed as soon as possible.
I think that was a very bad idea! Since four days you are waiting for that button become active and there are only three days left. Do you really think a repair station will send it back in three days?? This button becomes active by itself in three days and after that they will send it back to you and earn the money for nothing!
WoKoschekk said:
I think that was a very bad idea! Since four days you are waiting for that button become active and there are only three days left. Do you really think a repair station will send it back in three days?? This button becomes active by itself in three days and after that they will send it back to you and earn the money for nothing!
Click to expand...
Click to collapse
Maybe you're right. But you have no idea all what was done in my phone. I really don't think that button was ever going to change. I'll actually be surprised if they can fix it without replacing parts. That's why I think this time it's better if the professionals take care of it, and I'll get the phone Thursday with the guarantee it will be fixed ( Motorola service is taking care of it)
---------- Post added at 11:45 PM ---------- Previous post was at 11:42 PM ----------
mrsiri said:
Maybe you're right. But you have no idea all what was done in my phone. I really don't think that button was ever going to change. I'll actually be surprised if they can fix it without replacing parts. That's why I think this time it's better if the professionals take care of it, and I'll get the phone Thursday with the guarantee it will be fixed ( Motorola service is taking care of it)
Click to expand...
Click to collapse
Yet the itch of simply waiting will now stay forever
mrsiri said:
Yet the itch of simply waiting will now stay forever
Click to expand...
Click to collapse
As soon as the bootloader is unlocked you won't have that trouble anymore.
WoKoschekk said:
As soon as the bootloader is unlocked you won't have that trouble anymore.
Click to expand...
Click to collapse
Good and bad News!
The repair service couldn't fix the problem so I wasn't charged for it.
The bad News is I'm back at the same state
This time I'll wait the 7 days.

Bootloader Unlock (Developer Option Bug)

Hi. Today I found a bug in my Nokia 5 allowing me to enable OEM Unlock in the Developer Option Settings. Please note that I am on the new Android Pie with the latest April security patch. So here is what I did:
1. Please enable Developer Option on the Settings menu. If you already did so, skip this.
2. Now, on the Developer Option, you can see the OEM Unlock is greyed out. To toggle the switch on, "you need to disable and re-enable the Developer Option toggle switch at the top of the menu".
3. After then, you can now freely toggle the OEM Unlock switch. You will be prompted then to enter your device password and voila! OEM Unlock is now enable.
4. To switch it off, you just need to do the steps over again.
That's all. I hope this helps. Sorry, I might have posted this in the wrong section cause I am a new member and just wanted to fill my share to you.
Hey there! been lurking xda for ages but your post just made me register! Thanks a lot for sharing mate.
I just downloaded the update and tried this method, worked fine. Btw there's a new security patch as latest update (5/19), didnt bother doing it as they could have patched it probably.
So, i tried flashing twrp and noticed it still wouldn't let me and flashing get_unlock_ability returns 0. Did you manage to get past this?
This actually works. Havent flashed anything yet, as I'm scared of bricking it.
I just love the good old days when I had the Tmobile G2x with the Nvidia chip, flashed the darn thing so many times, even bricked it numerous times, but I was able to go into recovery and reflash it again. That phone was "Flash and Brick Proof"
thanks for sharing, spent countless hours trying to fix with usb driver setups and cmd lines from other tutorials.
question is what's next?
That's a dummy command,
You still need to properly Unlock it, I'm afraid all the options are paid service
Sent from my Xperia 1 using XDA Labs
This thing still works as now it's may 11th 2020.
I'm I ready to unlock bootloader now?
alexben_007 said:
This thing still works as now it's may 11th 2020.
I'm I ready to unlock bootloader now?
Click to expand...
Click to collapse
Try fastboot oem unlock
Mod edit - translated by https://www.deepl.com/translator:
Unlock the bootloader
****************************
Разблокировать загрузчик -358536084114397 -nokia5_nd1
I am N.E.E.T said:
Hi. Today I found a bug in my Nokia 5 allowing me to enable OEM Unlock in the Developer Option Settings. Please note that I am on the new Android Pie with the latest April security patch. So here is what I did:
1. Please enable Developer Option on the Settings menu. If you already did so, skip this.
2. Now, on the Developer Option, you can see the OEM Unlock is greyed out. To toggle the switch on, "you need to disable and re-enable the Developer Option toggle switch at the top of the menu".
3. After then, you can now freely toggle the OEM Unlock switch. You will be prompted then to enter your device password and voila! OEM Unlock is now enable.
4. To switch it off, you just need to do the steps over again.
That's all. I hope this helps. Sorry, I might have posted this in the wrong section cause I am a new member and just wanted to fill my share to you.
Click to expand...
Click to collapse
pretty usefull tip bro, it worked on my nokia 6 TA-1000

Categories

Resources