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
hai guys i tried to unlock bootloader by official sony method by selecting xperia xz(because xz1c not listed) and got my unlock code by my imei,but when i hit the unlock command ,its not working, can someone please help me to unlock my bootloader i am on the version(47.1.a.8.49), one more doubt is as iam on the latest version(1st december 2017 security patch) does the twrp for the older security patch works for my version,because i didnt find the proper twrp for the latest security patch
jinishpv said:
hai guys i tried to unlock bootloader by official sony method by selecting xperia xz(because xz1c not listed) and got my unlock code by my imei,but when i hit the unlock command ,its not working, can someone please help me to unlock my bootloader i am on the version(47.1.a.8.49), one more doubt is as iam on the latest version(1st december 2017 security patch) does the twrp for the older security patch works for my version,because i didnt find the proper twrp for the latest security patch
Click to expand...
Click to collapse
Did you enable OEM unlocking in the developer options?
You know you're going to lose you camera right? I mean no pictures whatsoever.
No I'm not sure TWRP is working for December update yet.
You can't flash old version TWRP with new 47.1.A.8.49
Didgesteve said:
You know you're going to lose you camera right? I mean no pictures whatsoever.
Click to expand...
Click to collapse
There's actually a recently released DRM fix, which reportedly fixes the camera: https://forum.xda-developers.com/xp...lopment/oreo-xz1c-drmfix-root-ricoff-t3727029
Didgesteve said:
No I'm not sure TWRP is working for December update yet.
Click to expand...
Click to collapse
modpunk just updated TWRP with December security patch: https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
BetaLyte said:
There's actually a recently released DRM fix, which reportedly fixes the camera: https://forum.xda-developers.com/xp...lopment/oreo-xz1c-drmfix-root-ricoff-t3727029
modpunk just updated TWRP with December security patch: https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
Click to expand...
Click to collapse
My mistake, it's only been out a day so I hadn't spotted it.
Looks like there's some success on the thread, but I'll hold back a bit before I jump.
Didgesteve said:
Looks like there's some success on the thread, but I'll hold back a bit before I jump.
Click to expand...
Click to collapse
Yeah, me too. sToRm// is taking a look at it, at will include it in XperiFix. But it's still important to notice, that it's a fix, and not a DRM backup / restore solution, so the original TA partition / DRM keys will still be lost and won't be recoverable.
BetaLyte said:
Yeah, me too. sToRm// is taking a look at it, at will include it in XperiFix. But it's still important to notice, that it's a fix, and not a DRM backup / restore solution, so the original TA partition / DRM keys will still be lost and won't be recoverable.
Click to expand...
Click to collapse
Yes, it's a one way step and you're reliant on the developer bringing a new version of the fix each time there's a firmware update.
No offence to the developer, but I know nothing of M-Rom or aledoom, it would be good to know a little of their background before I open my phone to some software from a unkown forum.
Since nobody bothered to give an answer...
1. Go to the Sony Bootloader Unlock page here
2. Follow the steps for the Xperia XZ
3. Get the email, click the link, type in your IMEI
4. Follow the instructions on the page.
lokio27 said:
Since nobody bothered to give an answer...
1. Go to the Sony Bootloader Unlock page here
2. Follow the steps for the Xperia XZ
3. Get the email, click the link, type in your IMEI
4. Follow the instructions on the page.
Click to expand...
Click to collapse
It looks more like you didn't bother to read OP's post.
He has already done all that, he's asking why the unlock command isn't working.
Unfortunately, up until recently, unlocking the bootloader on this phone is extremely unappealing, so like almost no one has tried unlocking it, and those who did probably didn't run into this problem, so no one was able to offer an actual answer.
The first reply actually provided some suggestions. If you bothered to read.
mhaha said:
It looks more like you didn't bother to read OP's post.
He has already done all that, he's asking why the unlock command isn't working.
Unfortunately, up until recently, unlocking the bootloader on this phone is extremely unappealing, so like almost no one has tried unlocking it, and those who did probably didn't run into this problem, so no one was able to offer an actual answer.
The first reply actually provided some suggestions. If you bothered to read.
Click to expand...
Click to collapse
I couldn't find any help anywhere when I was looking for help on that, so I felt like a post was needed in general.
problem solved
tried bootloaderunlock on my desktop pc and it worked,flashed latest twrp ,flashed drm fix every thing is working fine,anyone had sucess in magisk and viper4android?
jinishpv said:
tried bootloaderunlock on my desktop pc and it worked,flashed latest twrp ,flashed drm fix every thing is working fine,anyone had sucess in magisk and viper4android?
Click to expand...
Click to collapse
Hi, I have maybe the same issue :
Code:
fastboot -i 0x0fce oem unlock 0xMyKey
returns only
Code:
...
and seems stuck : nothing happens.
So I would like to unlock my bootloader, but I cannot manage to do it (of course *#*#7378423#*#* then Service info > Configuration > Rooting Status Bootloader unlock allowed says Yes).
How did you manage to unlock your bootloader?
OldBeurt said:
How did you manage to unlock your bootloader?
Click to expand...
Click to collapse
I did not find a proper solution. It is still impossible to unlock my XZ1c with my laptop. Fortunately, I did manage to unlock it using my (very) old former laptop (it’s 32 bits, I had to use the old ADB v23), and it worked like a charm.
I don’t know why it failed on my current laptop (either with my usual OS Linux, nor with Windows 10).
Old thread is old? i don't care. because i want to say that looks like Sony finally give the XZ1c into the data base and there is a hot to guide over the Dev mode of the Phone. i will past the Sony guide to it here so this info will spread where it needed:
"To be able to unlock your Xperia XZ1 Compact, prepare it by following these steps:
Go into Settings > About phone and tap seven times on Build number to enable developer options.
From Settings, go into Developer options and enable OEM unlocking.
Warning:
Camera stops working on certain software releases.
Device protection features will not work on this device while this setting is turned on. Note: It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialer and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
"
Source: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
/€: Again, you guys are way to deep into the matter and i found several things that was never mention by any tutorial.
after several testings and also failings i will add: under windows 10, you have to check the Drivers double and make sure you use one that works!
EVEN IF IT APPEARS THAT THE DRIVER IS CORRECT IT MAY NOT THE CASE!
To check this you have to use "ADB DEVICES" and "FASTBOOT DEVICES".
Only if your device appears in the list IN BOTH (!) cases the driver setting is correct. This is very important.
Also you have to consider that after reboot into bootloader ("adb reboot bootloader") the device will NOT RECOGNIZE (!) by windows and appears as new device without any driver! (check Device Manager for this) so you can't access it in that state EVEN it was recognized before!
You have to install the Google Android USB Driver in this case. Also you have to check if the device appears still in both (adb, fastboot) lists.
Only then you can preform the Guides correctly!
summary: you have to install two (!) driver to get proper access to your device, one driver can only be installed in a certain state of your device (bootloader state) you have to make sure that your device is accessible in all states to preform your unlocking AND img pushing correctly.
Your bootloader is unlocked if on Power up the message appears "Your device has been is unlocked and can't be trusted. Your device will boot in 5 seconds"
...and now i go and found a way to get rid of the "non access on external cards for apps" _feature_ ...ands no all the tools and images and guides DON'T WORK.
muhschaf said:
To check this you have to use "ADB DEVICES" and "FASTBOOT DEVICES".
Only if your device appears in the list IN BOTH (!) cases the driver setting is correct. This is very important.
Click to expand...
Click to collapse
So how did you manage to work this out? I have this exact problem. When the phone is in fast mode (volume up) it shows in the "fastboot devices" but not in the "adb devices". When it's turned on it does show up in "adb devices" but (obviously) not in fastboot devices...
As it is, when i try the "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it tells me that it doesn't know command -- i. I have found nothing about this problem at all. nowhere. I'm tried to unlock the bootloader (settings, show it's possible) for 5h and haven't managed to do it yet... I'm really thinking about sending it back, this is just too annoying... please please help me...
mosbyxz1c said:
So how did you manage to work this out? I have this exact problem. When the phone is in fast mode (volume up) it shows in the "fastboot devices" but not in the "adb devices". When it's turned on it does show up in "adb devices" but (obviously) not in fastboot devices...
As it is, when i try the "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it tells me that it doesn't know command -- i. I have found nothing about this problem at all. nowhere. I'm tried to unlock the bootloader (settings, show it's possible) for 5h and haven't managed to do it yet... I'm really thinking about sending it back, this is just too annoying... please please help me...
Click to expand...
Click to collapse
Have you checked that your phone can be unlocked?
Some providers sell phones that can't be unlocked so that they don't have to deal with the warranty mess.
Open your phone and type *#*#7378423#*#* - then look under Service info\Configuration under Rooting status it should say Bootloader unlock allowed: Yes
If it says No, then you need to stop, there is no way round this.
Didgesteve said:
Have you checked that your phone can be unlocked?
Some providers sell phones that can't be unlocked so that they don't have to deal with the warranty mess.
Open your phone and type *#*#7378423#*#* - then look under Service info\Configuration under Rooting status it should say Bootloader unlock allowed: Yes
If it says No, then you need to stop, there is no way round this.
Click to expand...
Click to collapse
I bought it straight from amazon without any carriers but yes it is allowed (that's what I meant with "settings show it's possible", sorry if that was unclear).
I just double checked, just to be 100% sure. And yes:
Rooting status:
bootloader unlock allowed: Yes
mosbyxz1c said:
I bought it straight from amazon without any carriers but yes it is allowed (that's what I meant with "settings show it's possible", sorry if that was unclear).
I just double checked, just to be 100% sure. And yes:
Rooting status:
bootloader unlock allowed: Yes
Click to expand...
Click to collapse
Presumably you've enabled OEM unlocking in the developer options?
Otherwise it's a driver problem, good luck with that.
mosbyxz1c said:
As it is, when i try the "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it tells me that it doesn't know command -- i. I have found nothing about this problem at all. nowhere.
Click to expand...
Click to collapse
I got the same problem, I just removed the "-i 0x0fc" part, so it became "fastboot oem unlock 0x<insert your unlock code>".
I think there may be a newer version of fastboot that lacks the -i option.
Nerre said:
I got the same problem, I just removed the "-i 0x0fc" part, so it became "fastboot oem unlock 0x<insert your unlock code>".
I think there may be a newer version of fastboot that lacks the -i option.
Click to expand...
Click to collapse
Thanks for trying to help.
Got a little hopeful but now i get a
Code:
FAILED (remote: Command did not succeed)
I'm going crazy... I'm really thinking about setting up a dualboot linux (or boot from usb). you guys think thats useful? I have no problems with drivers at least. If yes, ubuntu enough? I don't have a lot of linux experience..
mosbyxz1c said:
So how did you manage to work this out? I have this exact problem. When the phone is in fast mode (volume up) it shows in the "fastboot devices" but not in the "adb devices". When it's turned on it does show up in "adb devices" but (obviously) not in fastboot devices...
As it is, when i try the "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it tells me that it doesn't know command -- i. I have found nothing about this problem at all. nowhere. I'm tried to unlock the bootloader (settings, show it's possible) for 5h and haven't managed to do it yet... I'm really thinking about sending it back, this is just too annoying... please please help me...
Click to expand...
Click to collapse
Your mention of "Volume up" button indicates that your try to reboot it per button pressing. Try to avoid that. Your device should reboot by typing in the fast boot command and press enter. then you have to check the driver state in the Device manager and their install the correct driver (Google ADB driver). Don't unplug your Phone during this.
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.
With that I am on Xfinity they locked OEM carrier locked, phone financed so my goal is to run the developer build of Google 12 but under the instructions on Google Developer site list OEM must be checked before unlocking bootloader?
sillyshyme said:
With that I am on Xfinity they locked OEM carrier locked, phone financed so my goal is to run the developer build of Google 12 but under the instructions on Google Developer site list OEM must be checked before unlocking bootloader?
Click to expand...
Click to collapse
Not all phones can be bootloader unlocked. In settings, about phone, go to "build number". Tap it rapidly 8-9 times untill you see that developer settings are unlocked. Go to system developer options. Tick "usb debugging". Next near the top look for "oem unlocking". Try to tick that option. If you can't, then your bootloader cannot be unlocked.
Unlocking the bootloader will wipe your phone. If you are unfamiliar with all this, I recommend that you stay on 11.