[Resolved] OEM Unlocking disabled on Google Store purchased phone

[Gregyski]

EDIT: Resolved: While the OS had said it was up-to-date when I originally checked. It was not. After a bit of time it alerted me that an update was available. After updating the OS the OEM Unlocking option was no longer disabled.

I purchased a Pixel XL specifically from Google Store because I wanted to receive either an bootloader unlocked or bootloader unlockable phone without resorting to any hacks that may not work in the future. It just arrived and I enabled Developer Options and enabled USB Debugging. However, the OEM Unlocking option is off and disabled (greyed).

I booted into the bootloader, it shows as locked. If I try to unlock it I get:
>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s

If I try to flash it with the temporary TWRP boot up image:
>fastboot boot <path-to>\twrp-3.0.2-0-alpha2-fastboot-marlin.img"
downloading 'boot.img'...
OKAY [ 0.874s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.975s

I'd appreciate any suggestions for proceeding. Thank you.

 

[ilatimer1]

(Since this isn't specifically about alternate firmware, I believe this is the correct forum and not the dev forum.)

I purchased a Pixel XL specifically from Google Store because I wanted to receive either an bootloader unlocked or bootloader unlockable phone without resorting to any hacks that may not work in the future. It just arrived and I enabled Developer Options and enabled USB Debugging. However, the OEM Unlocking option is off and disabled (greyed).

I booted into the bootloader, it shows as locked. If I try to unlock it I get:
>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s

If I try to flash it with the temporary TWRP boot up image:
>fastboot boot <path-to>\twrp-3.0.2-0-alpha2-fastboot-marlin.img"
downloading 'boot.img'...
OKAY [ 0.874s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.975s

I'd appreciate any suggestions for proceeding. Thank you.

The command should be fastboot oem unlock

 

[Gregyski]

The command should be fastboot oem unlock

Unfortunately, that is also disallowed:
>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.046s

 

[ilatimer1]

Unfortunately, that is also disallowed:
>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.046s

Did you go into Developer options is Settings and enable OEM unlocking first? If you don't have Developer Options in settings go to Settings/About Phone and then tap Build Number a bunch of times to enable it.

 

[Gregyski]

Did you go into Developer options is Settings and enable OEM unlocking first? If you don't have Developer Options in settings go to Settings/About Phone and then tap Build Number a bunch of times to enable it.

Thanks for your help ilatimer1, but I have resolved it now. I had edited the original post to indicate this but probably should have followed up at the end for your sake. I was just trying to avoid bumping it. At the time I asked the question, I mentioned that that option was disabled.

When I originally setup the phone I didn't enter WiFi data since I knew a factory reset would occur when I unlocked the bootloader. However, as a result of this, I didn't get alerted to the presence of an OS update. Ultimately, I setup WiFi and discovered the availability of an update. I proceeded to update and the OEM Unlocking feature then became enabled. Thanks again.

 

[crypticc]

I unwapped and went stright to fastboot. didn't know update needed. thanks

 

[[email protected]]

Same issue unresolved

When I go into developer options OEM unlocking is still greyed out even after I downloaded the software update. Any leads on what to do?

 

[Mr. Orange 645]

When I go into developer options OEM unlocking is still greyed out even after I downloaded the software update. Any leads on what to do?

Where did you buy your Pixel?

 

[[email protected]]

Where did you buy your Pixel?

verizon store

 

[Mr. Orange 645]

verizon store

The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.

 

[[email protected]]

The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.

so there is no solution if Ive already updated to 7.1.1?

any chance a solution will open up in the future?

 

[Mr. Orange 645]

No there no solution right now. I wouldn't say there's absolutely no chance of finding another exploit, this is XDA after all, but I wouldn't count on it.

 

[[email protected]]

No there no solution right now. I wouldn't say there's absolutely no chance of finding another exploit, this is XDA after all, but I wouldn't count on it.

so this toolkit isnt gonna work: http://www.wugfresh.com/nrt/

?

 

[Mr. Orange 645]

so this toolkit isnt gonna work: http://www.wugfresh.com/nrt/

?

No. That's for Nexus devices not Pixels anyway.

 

[integraGSR]

Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?

 

[[email protected]]

Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?

Im on Verizon

 

[Mr. Orange 645]

Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?

The Allow OEM Unlocking switch asks for a PIN? Do you have a PIN set up for the lockscreen? I'm guessing that's what it's asking for. Your contract status with ATT has nothing to do with the bootloader status. If you think so, just try it without your SIM card in it.

 

[integraGSR]

The Allow OEM Unlocking switch asks for a PIN? Do you have a PIN set up for the lockscreen? I'm guessing that's what it's asking for. Your contract status with ATT has nothing to do with the bootloader status. If you think so, just try it without your SIM card in it.

LoL that was it. Sometimes it's back to the basics, think outside the box. Didn't think about lockscreen pin as I use fingerprint scanner all the time. Thanks.

 

[Mr. Orange 645]

LoL that was it. Sometimes it's back to the basics, think outside the box. Didn't think about lockscreen pin as I use fingerprint scanner all the time. Thanks.

LOL! Glad I could help!

 

[oneandroidnut]

The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.

But pixels purchased at Google store with 7.1.1 are still unlockable correct?

Sent from my Pixel XL using Tapatalk