Database Info

OEM Unlocking issue [SOLVED]

I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.

Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170

depii said:
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
Click to expand...
Click to collapse
Once it boots into fastboot, I enter "fastboot flashing unlock"
I have that same version of fastboot.

Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?

depii said:
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
Click to expand...
Click to collapse
Device state is locked
There's nothing under OEM unlocking saying that the bootloader is already unlocked.
Yes, I have enabled unlocking before booting into fastboot. I've done it five times now.
What's odd is if I use the unlock_critical command, I get "FAILED (remote: Device already : unlocked!)"

geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?

rohanhole said:
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
Click to expand...
Click to collapse
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.

geicogecko said:
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
Click to expand...
Click to collapse
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?

rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.

rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
I first updated to 8.1 OTA, then unlocked.
rohanhole said:
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
Click to expand...
Click to collapse
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.

geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
Read the other threads or check the xda news portal. This command actually unlocks the pixel 2 not XL variant.

geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
I really don't have any clue why it worked ! After reading latest post I executed the above command in leap of faith and it really worked ! Finally unlocked bootloader on pixel 2 128 Gb. But its strange as I don't have Verizon model , as I purchased the device from official google store in India ( flipkart.com )
Here is the XDA post : https://www.xda-developers.com/verizon-google-pixel-2-bootloader-unlock/

geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net

Google Pixel 2 (July Update non Verizon) OEM unlocking issues.

The issue that I'm having is that I am unable to unlock the bootloader even though I should be able to. Here are the steps i'm taking and where the issue happens.
Factory/Wipe reset
Tap about Pixel 2 7 times to get developer options
Go to developer options and enable USB Debugging and OEM Unlocking.
(I Can see that OEM unlocking is enabled).
Then I do "adb reboot bootloader"
and once in the bootloader, I do "fastboot flashing unlock"
Then it tellsme that Flashing Unlock is not allowed and when I go back to the developer options, the OEM Unlocking is greyed out and in the off position and I cannot re enable it no matter what. I have not being able to find anyone with this problem or a solution, any help would be appreciated.
I have tried the above steps many times with no luck, and every time the results are the same. It gives me the OEM Unlock option right after the factory reset, but one I do the "fastboot flashing unlock" it doesn't unlock the bootloader and then it locks the option in developer options.
I updated both ADB and fastboot to the latest version.
Edit #2: running the "fastboot flashing get-unlock-ability" command, returns a (1), which means that it should be able to be unlocked.
Edit #3: Tried to sideload OTA update using ADB and it does not solve the issue.

After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
Try: fastboot oem unlock
Definitely a weird issue. Are you on Verizon’s network?
Edit: were you connected to the internet when you did the oem unlock in the developers options?
Edit 2: you have usb debugging enabled yeah?

Jomama22 said:
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
Try: fastboot oem unlock
Definitely a weird issue. Are you on Verizon’s network?
Edit: were you connected to the internet when you did the oem unlock in the developers options?
Edit 2: you have usb debugging enabled yeah?
Click to expand...
Click to collapse
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
I did not, I assumed that since it is the latest factory image, I did not needed to update, will try this ASAP.
USB Debugging is enabled.
I was connected to the internet when I did the OEM Unlock under developer options, I tried both connected and not connected to the internet. I tried to change the boot partition using fastboot and it does not allow to do so when in "locked" mode.
oem unlock returns that it is unable to be unlocked. (Sorry, not home now, but will post the actual error when I get back)

I am experiencing this issue also. I'm on my 2nd RMA device. The specific error I get after typing
Code:
fastboot flashing unlock
is
Code:
FAILED (remote: Flashing Unlock is not allowed)
Any help is appreciated.

keanon said:
I am experiencing this issue also. I'm on my 2nd RMA device. The specific error I get after typing
Code:
fastboot flashing unlock
is
Code:
FAILED (remote: Flashing Unlock is not allowed)
Any help is appreciated.
Click to expand...
Click to collapse
That is in fact the error I'm getting. I had the OG Pixel and the Pixel 2 rooted since the day they came out and never had a problem, and now with this RMA replacement, I'm having problems, but IDK what could be the cause because with a fresh factory reset, I can at least see the "OEM Unlock" under developer options, so I'm so confused.

plgonzalezrx8 said:
That is in fact the error I'm getting. I had the OG Pixel and the Pixel 2 rooted since the day they came out and never had a problem, and now with this RMA replacement, I'm having problems, but IDK what could be the cause because with a fresh factory reset, I can at least see the "OEM Unlock" under developer options, so I'm so confused.
Click to expand...
Click to collapse
My OEM Unlock option will "take" when I click it, but it's disabled again when I reboot.

If they're RMA replacements, there's a possibility you got a Verizon Pixel 2 instead of a Google. This happened to me as well, I just traded for my wife's Pixel 2, because she has no interest in BL Unlocking and all that goes with it. There have been others who kept returning phones until they got one that allowed BL Unlocking. If you purchased from Google originally, just tell them the problem and they should send you another RMA replacement, from what I've seen elsewhere.
Edit for clarification: Supposedly, they've been getting Verizon and Google Pixel 2s mixed up when they get refurbished.

lightningdude said:
If they're RMA replacements, there's a possibility you got a Verizon Pixel 2 instead of a Google. This happened to me as well, I just traded for my wife's Pixel 2, because she has no interest in BL Unlocking and all that goes with it. There have been others who kept returning phones until they got one that allowed BL Unlocking. If you purchased from Google originally, just tell them the problem and they should send you another RMA replacement, from what I've seen elsewhere.
Edit for clarification: Supposedly, they've been getting Verizon and Google Pixel 2s mixed up when they get refurbished.
Click to expand...
Click to collapse
I ordered a new open OEM Pixel 2 XL 64gb in Just Black arriving from eBay in 48hrs. I am now concerned.

MrKillroy said:
I ordered a new open OEM Pixel 2 XL 64gb in Just Black arriving from eBay in 48hrs. I am now concerned.
Click to expand...
Click to collapse
I am too. I'm still paying mine off and I've been without a well-functioning phone since June 15.

So op, is this the first time you have tried unlocking this rma? If so, sounds like you know the problem and probably have to rma again

Jomama22 said:
So op, is this the first time you have tried unlocking this rma? If so, sounds like you know the problem and probably have to rma again
Click to expand...
Click to collapse
Yes. This is the first time I tried to unlock this RMA, just got it a couple days ago. I have rooted all my android phones for the past 4-5 years and never had a problem similar to this show up before. The thing is that I really want to know what is happening at at deeper level, why is this happening, it doesn't make any sense at all because why would that option change if the fasboot flashing command is returning an error, also when I use "fastboot flashing get_unlock_ability" it returns a (1) and not a (0), which means that it can be unlocked.
We'll see, I started the RMA process lets see what they say.

plgonzalezrx8 said:
Yes. This is the first time I tried to unlock this RMA, just got it a couple days ago. I have rooted all my android phones for the past 4-5 years and never had a problem similar to this show up before. The thing is that I really want to know what is happening at at deeper level, why is this happening, it doesn't make any sense at all because why would that option change if the fasboot flashing command is returning an error, also when I use "fastboot flashing get_unlock_ability" it returns a (1) and not a (0), which means that it can be unlocked.
We'll see, I started the RMA process lets see what they say.
Click to expand...
Click to collapse
I don't remember where exactly I saw it, but in one of the commands, it tells you whether it's allowed to be unlocked. That's a firm 0 in that spot. Like I said, you likely ended up with a refurbished Verizon version. The only difference, to my knowledge, is that Verizon doesn't want you to unlock your bootloader.

There's already a whole thread about this. Please post there
https://forum.xda-developers.com/pixel-2/help/oem-unlocking-grayed-vzw-pixel-2-t3776763/page5
Bottom line. Google pixel 2s refurbished RMAs are botched for OEM unlocking. There's a problem with their refurbishment procedures that makes it behave exactly like show here
Only solution is trying to convince them to send you a new RMA, but good luck with that.

plgonzalezrx8 said:
The issue that I'm having is that I am unable to unlock the bootloader even though I should be able to. Here are the steps i'm taking and where the issue happens.
Factory/Wipe reset
Tap about Pixel 2 7 times to get developer options
Go to developer options and enable USB Debugging and OEM Unlocking.
(I Can see that OEM unlocking is enabled).
Then I do "adb reboot bootloader"
and once in the bootloader, I do "fastboot flashing unlock"
Then it tellsme that Flashing Unlock is not allowed and when I go back to the developer options, the OEM Unlocking is greyed out and in the off position and I cannot re enable it no matter what. I have not being able to find anyone with this problem or a solution, any help would be appreciated.
I have tried the above steps many times with no luck, and every time the results are the same. It gives me the OEM Unlock option right after the factory reset, but one I do the "fastboot flashing unlock" it doesn't unlock the bootloader and then it locks the option in developer options.
I updated both ADB and fastboot to the latest version.
Edit #2: running the "fastboot flashing get-unlock-ability" command, returns a (1), which means that it should be able to be unlocked.
Edit #3: Tried to sideload OTA update using ADB and it does not solve the issue.
Click to expand...
Click to collapse
Please visit this thread for more info. Though I need to mention there is no actual fix as of yet.

Cant unlock bootloader on refurbished pixel 2

I recently bought a refurbished pixel 2 from a phone repair shop and i went through the process to unlock the bootloader, enabling dev options, enabling oem unlocking and usb debugging, ect. but when i boot into the bootloader and run
Code:
fastboot flashing unlock
, it throws an error
Code:
FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed
but when i run fastboot flashing get_unlock_ability it returns
Code:
(bootloader) get_unlock_ability: 1
OKAY [ 0.000s]
Finished. Total time: 0.000s
result of 'adb shell getprop sys.oem_unlock_allowed' is 1
result of 'adb shell getprop ro.boot.cid' is 00000000
im running linux and ive tried running the command as sudo and just launching a root terminal to no avail. If anyone can help, it would be very much appreciated
EDIT: Now im even a bit more confused. i ran
Code:
fastboot oem device_info
and it returns
Code:
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
[B](bootloader) Device critical unlocked: true[/B]
(bootloader) Charger screen enabled: true
OKAY [ 0.000s]
Finished. Total time: 0.000s
so if critical is unlocked why cant i just unlock the bootloader?

How do you know that the pixel was refurbished? I bought one (as new) as well but I fear that it might be refurbished. Is there something to look up in order to check that?

N5X_ita said:
How do you know that the pixel was refurbished? I bought one (as new) as well but I fear that it might be refurbished. Is there something to look up in order to check that?
Click to expand...
Click to collapse
any phone this old listed as new or brand new is 100% refurbished in china using the ****tiest parts and then boxed in a really poor recreation of the stock box and shipped off to a distributor in your country

Any update? Same issue here

maybe you need to use the "oem unlock" command instead of "flashing unlock".

#5
I also have the same problem

is it possible to unlock via some type of APK without PC

I know that the refurbished pixel 2s that Google sends as replacements have locked bootloaders.
Also the Verizon wireless variant of the pixel 2 has a locked bootloader
So it could be that who ever refurbished your device locked the bootloader permanently
Sent from my Pixel 3a XL

I also have the same problem. Reported it to google and they have no solution at this time.
Can I root it with magisk without having to unlock the bootloader first? I know I won't be able to flash twrp to the recovery image though.
If something wen't wrong, could I sideload the last ota and get everything back as long as I can boot to the bootloader?

xp99 said:
I also have the same problem. Reported it to google and they have no solution at this time.
Can I root it with magisk without having to unlock the bootloader first? I know I won't be able to flash twrp to the recovery image though.
If something wen't wrong, could I sideload the last ota and get everything back as long as I can boot to the bootloader?
Click to expand...
Click to collapse
Im fairly certain that you need to have unlocked bootloader to root the phone.
Sent from my Pixel 3a XL

eyeyousee said:
maybe you need to use the "oem unlock" command instead of "flashing unlock".
Click to expand...
Click to collapse
oem unlock gives the same error

I'm just grasping at straws here, but did you try *relocking* the device from the critical_unlock, and the unlocking it with the regular unlock command?

I'm on a Pixel 2 warranty replacement from Google directly. The OEM Unlock option is enabled in developer settings as is USB Debugging. The computer has been authorized by the Pixel.
I'm getting those same errors. It's definitely not a Verizon Wireless phone since it's a Canadian phone sold directly by Google.
I'm guessing there is no workaround for this yet. Why would it be listed as bootloader unlock allowed in developer options yet fail when you go to fastboot flashing unlock?

13kai13 said:
I'm on a Pixel 2 warranty replacement from Google directly. The OEM Unlock option is enabled in developer settings as is USB Debugging. The computer has been authorized by the Pixel.
I'm getting those same errors. It's definitely not a Verizon Wireless phone since it's a Canadian phone sold directly by Google.
I'm guessing there is no workaround for this yet. Why would it be listed as bootloader unlock allowed in developer options yet fail when you go to fastboot flashing unlock?
Click to expand...
Click to collapse
maybe there is some sort of failsafe in the kernel that stops it from being bootloader unlocked if a component on the board has been replaced? or maybe google just says "frick you, pay more money if you want root"
but that's just a theory.... A GAY THEORY

Hi I just bought a refurb Pixel 2 on Amazon. When i go to developer options I see the "OEM unlocking" option is completely greyed out. Even after i enabled usb debugging.
Does that mean that my bootloader is impossible to be unlocked? And how is one able to know if they have the Verizon variant?

fc3211 said:
Hi I just bought a refurb Pixel 2 on Amazon. When i go to developer options I see the "OEM unlocking" option is completely greyed out. Even after i enabled usb debugging.
Does that mean that my bootloader is impossible to be unlocked? And how is one able to know if they have the Verizon variant?
Click to expand...
Click to collapse
The refurbished units whether is a Google refurbished or Verizon unit all have locked bootloaders [emoji58]
Sent from my Pixel 3a XL

This is why I regret doing a warranty through Google Fi. I even had it replaced twice. Both times, the bootloader was locked. It appears to be unlock-able, but then this happens.
Does anyone know if this is limited to just the Pixel 2? I never had this problem with the Nexus 5X phones I had.

Questionably unlocked bootloader

So I went through steps to "un-grey" the OEM unlocking in dev settings, and success! I got it to work and immediately booped the option and restarted. But when I typed "fastboot flashing unlock", I still get "Flashing unlock is not allowed". Any idea what I'm doing wrong? Afaik, the phone was only ever used on ATT, not the cursed Verizon.

engineer_james said:
So I went through steps to "un-grey" the OEM unlocking in dev settings, and success! I got it to work and immediately booped the option and restarted. But when I typed "fastboot flashing unlock", I still get "Flashing unlock is not allowed". Any idea what I'm doing wrong? Afaik, the phone was only ever used on ATT, not the cursed Verizon.
Click to expand...
Click to collapse
I think there is currently no solution to unlock bootloader yet for greyed out OEM option.
even if you got the un-grey OEM option as Pixel 2 has a security chip that blocks the unlocking ( unlike OG Pixel that doesn't have )

I'm in the same boat as the OP. I have the option to turn on 'OEM unlocking' so when I attempted to unlock my bootloader last night I received FAILED (remote: 'Flashing Unlock is not allowed') in the command prompt. Now 'OEM unlocking has been greyed out after the failed attempt. What's going on here?

OEM unlocking greyed out (Android 10, Pixel 1st Gen)

Trying to enable OEM unlocking from Developer options, its greyed out with "Connect to the internet or contact your carrier". This phone was purchased from the Google Store and therefore isn't SIM locked and it is connected to the Wi-Fi. I have tried to insert my SIM card and this hasn't changed anything.
I have tried to factory reset the phone again, this still leaves OEM unlocking greyed out. Any other solutions to be able to unlock OEM unlocking?

I support. I tried ALL methods of unlocking the bootloader and nothing worked

[How-to] Unlock bootloader on Verizon Pixel/XL
Hi guys. So I finally found a way to unlock a bootloader on a Verizon Pixel. Without further ado, let's get started. This method works on Pixel and Pixel XL. 1. Remove Google account and any kind of screen lock (fingerprint, PIN, pattern, etc.)...
forum.xda-developers.com
I searched for days too. I have the Android 10 Verizon [ :/ ] model but no way has worked for me. I hope it works for you.
Edit : Please let me know if a way is found or found.

cann0tr00t said:
Trying to enable OEM unlocking from Developer options, its greyed out with "Connect to the internet or contact your carrier". This phone was purchased from the Google Store and therefore isn't SIM locked and it is connected to the Wi-Fi. I have tried to insert my SIM card and this hasn't changed anything.
I have tried to factory reset the phone again, this still leaves OEM unlocking greyed out. Any other solutions to be able to unlock OEM unlocking?
Click to expand...
Click to collapse
I answered.

YakupJackob said:
I answered.
Click to expand...
Click to collapse
I also have the same issue as I have authentic Google pixel phone and my oem unlocking is grayed out too.