Hi,
Why is in the DP5 under developer settings the OEM Unlock switch grayed and can't be enabled? The bootloader is unlock and a reboot doesn't help...
Regards
Greg
Perhaps because the bootloader is a u stated unlocked..
Sent from my Nexus 5X using XDA-Developers mobile app
dog121 said:
Perhaps because the bootloader is a u stated unlocked..
Click to expand...
Click to collapse
At Marshmallow my bootloader was unlocked too, but the option was available. Is this new in android N?
Sunnymen1975 said:
At Marshmallow my bootloader was unlocked too, but the option was available. Is this new in android N?
Click to expand...
Click to collapse
lock your BL then it should show as available to toggle.
Its probably by design as why would it let you toggle that when you're unlocked already?
Related
I wasn't able to flash any of the kernels for 5.1.1. root until I checked this off. Was this a new dev option for 5.1.1??
MrKrisKordova said:
I wasn't able to flash any of the kernels for 5.1.1. root until I checked this off. Was this a new dev option for 5.1.1??
Click to expand...
Click to collapse
Yuuuup .
Sent from my SM-G925T using XDA Free mobile app
Some folks that flashed the leaked 5.1.1 claim that they don't have that option in developer options.
Pp.
PanchoPlanet said:
Some folks that flashed the leaked 5.1.1 claim that they don't have that option in developer options.
Pp.
Click to expand...
Click to collapse
Good day sir. Has anyone already found a workaround to root the Korean S6 (SM-G920S) if they don't have the OEM Unlocking option on the Dev Options? Thanks for your reply.
chuckSICS said:
Good day sir. Has anyone already found a workaround to root the Korean S6 (SM-G920S) if they don't have the OEM Unlocking option on the Dev Options? Thanks for your reply.
Click to expand...
Click to collapse
Have not seen any posts stating a work around, possibly going back to stock firmware so that oem unlock can be enabled and safe flashing can be done.
Pp.
PanchoPlanet said:
Have not seen any posts stating a work around, possibly going back to stock firmware so that oem unlock can be enabled and safe flashing can be done.
Pp.
Click to expand...
Click to collapse
Has anyone already found a workaround to root the latinoamerica S6 (SM-G920i) if they don't have the OEM Unlocking option on the Dev Options?
kruzpe said:
Has anyone already found a workaround to root the latinoamerica S6 (SM-G920i) if they don't have the OEM Unlocking option on the Dev Options?
Click to expand...
Click to collapse
I have a SM-G920I Latinoamerican
No OEM Unlocking in Dev option
Any help to root latin america s6's without oem unlock option?
i have no os installed. i have g925t tmobile. how can i unlock usb debugging?? flashing firmware wont work, it just causes boot loop.
Latinamerican S6's may be running the 5.0.2 version of lollipop, that's why it's not present, we got it with 5.1.1 update. Only way to unlock is to install 5.1.1 update.
Pp.
PanchoPlanet said:
Latinamerican S6's may be running the 5.0.2 version of lollipop, that's why it's not present, we got it with 5.1.1 update. Only way to unlock is to install 5.1.1 update.
Pp.
Click to expand...
Click to collapse
OEM Unlock is not present on Latin-American S6 running Lollipop 5.1.1 . Anyway you really don't need that to unlock your bootloader. I did it with no issue. You can follow any procedure in this forum just skip the "OEM Unlock" step and you got it!
PanchoPlanet said:
Latinamerican S6's may be running the 5.0.2 version of lollipop, that's why it's not present, we got it with 5.1.1 update. Only way to unlock is to install 5.1.1 update.
Pp.
Click to expand...
Click to collapse
If you're on 5.0.2 it's already unlocked, right? I thought only 5.1.1 added the lock bootloader and option to disable.
Sent from my SM-G925T using Tapatalk
nyknight77 said:
If you're on 5.0.2 it's already unlocked, right? I thought only 5.1.1 added the lock bootloader and option to disable.
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
Correct.
Pp.
Hi there I am an absolute noob with phones totally deleted my miscellaneous files to make space for my phone only to later realize all my recordings are GONE! I'm trying to do a file restore. I can't seem to find the OEM option on my Samsung galaxy note 3 you seem to look like you figured it out? Any advice/tips? All help would be appreciated thanks!
Rose
Since I have enrolled my Pixel XL in Android beta program, I have received Oreo 8.1 update OTA last night. After the update, OEM unlock in developer options does not work. Anyone have the same issue ? Thanks
Fine here
netma2k said:
Since I have enrolled my Pixel XL in Android beta program, I have received Oreo 8.1 update OTA last night. After the update, OEM unlock in developer options does not work. Anyone have the same issue ? Thanks
Click to expand...
Click to collapse
Same problem the button is gray and says bootloader already unlocked.
That is normal if you are already unlocked, and it was like that before 8.1. It won't un-gray until you issue the fastboot command to relock it. It stops you from sliding while unlocked and creating a situation where you are bricked.
TonikJDK said:
That is normal if you are already unlocked, and it was like that before 8.1. It won't un-gray until you issue the fastboot command to relock it. It stops you from sliding while unlocked and creating a situation where you are bricked.
Click to expand...
Click to collapse
But I never unlocked my boot loader and still it appears to be grayed out. Thanks for your reply.
netma2k said:
But I never unlocked my boot loader and still it appears to be grayed out. Thanks for your reply.
Click to expand...
Click to collapse
Is your device a "Google phone" or is it through a carrier?
DR3W5K1 said:
Is your device a "Google phone" or is it through a carrier?
Click to expand...
Click to collapse
Mine is an unlocked phone purchased from Google Store and never buy phones from Carrier. Thanks for asking
netma2k said:
Mine is an unlocked phone purchased from Google Store and never buy phones from Carrier. Thanks for asking
Click to expand...
Click to collapse
Is it stuck in the locked position or the unlocked position?
Stuck in locked position
TonikJDK said:
Is it stuck in the locked position or the unlocked position?
Click to expand...
Click to collapse
Stuck in locked position
netma2k said:
Stuck in locked position
Click to expand...
Click to collapse
I would unenroll, which will wipe your phone and then hit the slider and leave it there. It might be a bug that will be fixed later but I wouldn't chance it if I wanted to unlock later on.
netma2k said:
Stuck in locked position
Click to expand...
Click to collapse
That is very strange
You are using beta software.
Google doesn't want you to lock the bootloader when using beta software.
Go back to 8.0 and see what happens.
Sent from my Pixel C using Tapatalk
Then, could I downgrade safely to Android 6??
Navalon said:
Then, could I downgrade safely to Android 6??
Click to expand...
Click to collapse
If you can pull it off, let us know!
Sent from my Pixel C using Tapatalk
pkelly517 said:
If you can pull it off, let us know!
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
If the bootloader is unlock, the rollback protection will be desactivated. Not?
I can confirm on mine that OEM unlock is also grayed out on 8.1 DP. Also grayed out in the screenshots on Android Police.
Sent from my Pixel using Tapatalk
Navalon said:
If the bootloader is unlock, the rollback protection will be desactivated. Not?
Click to expand...
Click to collapse
I think the joke was, this device never came with Marshmallow. They were saying if you can get Marshmallow to run on this, then let us know.
Unlocked rooted 8.0 not enrolled in beta.
My unlock button is Not grayed out. Wish it was as it would be easy to accidentally tick the button. Maybe 8.1 fixed this?
Born<ICs said:
Unlocked rooted 8.0 not enrolled in beta.
My unlock button is Not grayed out. Wish it was as it would be easy to accidentally tick the button. Maybe 8.1 fixed this?
Click to expand...
Click to collapse
An accidental tick won't hurt you, you still have to hit it with fastboot and issue the command.
How to unlock bootloader in nokia 6.1 2018 with the latest security patch update (august)?
It's illegal to XDA mods for me to post the link, but if you search techmesto bootloader unlock and downgrade for Nokia should get the info u need.
Try this
1. Turn off developer option
2. Choose cancel
3. Enable oem unlock
Enabled but greyed option.. try if bootloader is unlock..see attachement
dreampillow said:
1. Turn off developer option
2. Choose cancel
3. Enable oem unlock
Enabled but greyed option.. try if bootloader is unlock..see attachement
Click to expand...
Click to collapse
I've done that and have the same screenshot as you, what do I do now?
junglebungle said:
I've done that and have the same screenshot as you, what do I do now?
Click to expand...
Click to collapse
Try to root your phone.. if succes, your phone already bootloader unlocked
johnmark1503 said:
dreampillow said:
Try to root your phone.. if succes, your phone already bootloader unlocked
Click to expand...
Click to collapse
Thanks. Is there a good guide to do that on here?
Click to expand...
Click to collapse
Only way to unlock BL is through techmesto bootloader unlock and downgrade
There's no other way .
Hello All,
I ordered a brand new never-opened Pixel XL from Amazon. I was wondering, what would be the fastest way to update it to Android 10? It most likely will be on 7.1.1 out of the box. Any help is appreciated.
Thanks!:angel:
Jacobgacs said:
Hello All,
I ordered a brand new never-opened Pixel XL from Amazon. I was wondering, what would be the fastest way to update it to Android 10? It most likely will be on 7.1.1 out of the box. Any help is appreciated.
Thanks!:angel:
Click to expand...
Click to collapse
If the IMIE starts with 35 it is a Verizon Pixel XL the bootloader is locked. Before you update you may want to try and unlock the bootloader.
Settings ==> Advanced ==> System updates
Is the bootloader unlocked
Homeboy76 said:
If the IMIE starts with 35 it is a Verizon Pixel XL the bootloader is locked. Before you update you may want to try and unlock the bootloader.
Settings ==> Advanced ==> System updates
Is the bootloader unlocked
Click to expand...
Click to collapse
It said it was an unlocked. I'll figure that out and update you all later today :highfive:
Jacobgacs said:
It said it was an unlocked. I'll figure that out and update you all later today :highfive:
Click to expand...
Click to collapse
It might be 'Carrier Unlocked', that is not the same as bootloader unlocked. Carrier unlock means you should be able to use it on any carrier. Bootloader unlock means you can root it.
Homeboy76 said:
It might be 'Carrier Unlocked', that is not the same as bootloader unlocked. Carrier unlock means you should be able to use it on any carrier. Bootloader unlock means you can root it.
Click to expand...
Click to collapse
It was carrier unlocked, and it works perfectly well. It is on Android 8.0.0 and is offering to update directly to Android 10. Is it possible to do that?
Jacobgacs said:
It was carrier unlocked, and it works perfectly well. It is on Android 8.0.0 and is offering to update directly to Android 10. Is it possible to do that?
Click to expand...
Click to collapse
Yes, Settings ==> Advanced ==> System updates
Homeboy76 said:
Yes, Settings ==> Advanced ==> System updates
Click to expand...
Click to collapse
Update to Android 10 Successful
So, I'll start with my build # PCX29. 159-21-3
I have the OEM unlock option in my dev options and it's toggled on, but whenever I go to try and unlock the bootloader via Motorola's website I'm not able to? Is there a way around this, and why would the OEM bootloader unlock option even be there if I can use it?
MedievalFreakShow said:
So, I'll start with my build # PCX29. 159-21-3
I have the OEM unlock option in my dev options and it's toggled on, but whenever I go to try and unlock the bootloader via Motorola's website I'm not able to? Is there a way around this, and why would the OEM bootloader unlock option even be there if I can use it?
Click to expand...
Click to collapse
Is your phone Verizon by chance?
41rw4lk said:
Is your phone Verizon by chance?
Click to expand...
Click to collapse
It is Verizon sadly, I probably should have added that.
MedievalFreakShow said:
It is Verizon sadly, I probably should have added that.
Click to expand...
Click to collapse
Many Verizon Moto phones are not eligible to unlock the bootloader...
Sent from my LG-LS997 using Tapatalk
cgigate said:
Many Verizon Moto phones are not eligible to unlock the bootloader...
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
Are there any leads on possible exploits? I think I should just get a new phone, but I wanna try and do what I can with this one