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?
Related
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.
Currently trying to root my google pixel 2. The guy who sold me this phone said it was unlocked but I guess that was a LIE. When it arived, It had a verizon SIM card and the OEM unlockd button was grayed out. Surprisingly, this method actually managed to get the grayed out OEM unlock button to turn blue:
Here’s an easy method to bootloader unlock a Verizon Pixel or Pixel XL
There's now a simple method to unlock the bootloader of your Verizon-branded Google Pixel or Pixel XL. Give your phone new life!
www.androidauthority.com
However, after I ran "adb reboot bootloader" the command "fastboot oem unlock" still failed. And after the OS booted, the button was grayed out again.
1. What is actually going on here? Why does this method seem to work for some people?
2. Is there any way to get around this?
anon_lastname said:
Currently trying to root my google pixel 2. The guy who sold me this phone said it was unlocked but I guess that was a LIE. When it arived, It had a verizon SIM card and the OEM unlockd button was grayed out. Surprisingly, this method actually managed to get the grayed out OEM unlock button to turn blue:
Here’s an easy method to bootloader unlock a Verizon Pixel or Pixel XL
There's now a simple method to unlock the bootloader of your Verizon-branded Google Pixel or Pixel XL. Give your phone new life!
www.androidauthority.com
However, after I ran "adb reboot bootloader" the command "fastboot oem unlock" still failed. And after the OS booted, the button was grayed out again.
1. What is actually going on here? Why does this method seem to work for some people?
2. Is there any way to get around this?
Click to expand...
Click to collapse
I just tried my AT&T SIM card in the phone and it worked... So the phone is not even carrier locked, but the bootloader is locked.
If you can reactivate the OEM unlock button try using 'fastboot flashing unlock' rather than the OEM unlock command. Mine wasn't carrier locked but fastboot flashing unlock unlocked my bootloader.
Had the same drama unlocking a pixel I had and fastboot flashing unlocked sorted the bootloader once I'd activated the OEM unlock button.
Junglism93 said:
If you can reactivate the OEM unlock button try using 'fastboot flashing unlock' rather than the OEM unlock command. Mine wasn't carrier locked but fastboot flashing unlock unlocked my bootloader.
Had the same drama unlocking a pixel I had and fastboot flashing unlocked sorted the bootloader once I'd activated the OEM unlock button.
Click to expand...
Click to collapse
I tried that after using the exploit in the OP to get the unlock OEM button. Didn't work.
I'm pretty much done with this POS phone.
anon_lastname said:
I tried that after using the exploit in the OP to get the unlock OEM button. Didn't work.
I'm pretty much done with this POS phone.
Click to expand...
Click to collapse
Fair enough mate, worth a try but definitely sounds like it's the end of the road for unlocking it sadly. Might be time to sell it on mad move on to something else.
I have an unlocked variant of the Pixel 2. I put a Verizon SIM in it, and because of that, OEM unlocking was grayed out. However, a factory reset allowed me to enable it in developer settings. But when I tried to go to fastboot and unlock the bootloader, it kept giving me the following:
Code:
FAILED (remote: 'Flashing Unlock is not allowed')
Then when the phone is rebooted, the option is sometimes grayed out again, but it sometimes it stays on. It is running Android 11/RP1A.201005.004.A1/6934943, latest securiy patch.
On Verizon's site, the IEMI reports GOOGLE PIXEL 2 NON-VZW.
Hi i have the exact same problem. Looking for a solution...
I read on a Google forum that if your IMEI starts with 35 then it's an ex-Verizon phone so the bootloader is Verizon. Can you guys confirm that yours is 35* too?
kercre123 said:
I have an unlocked variant of the Pixel 2. I put a Verizon SIM in it, and because of that, OEM unlocking was grayed out. However, a factory reset allowed me to enable it in developer settings. But when I tried to go to fastboot and unlock the bootloader, it kept giving me the following:
Code:
FAILED (remote: 'Flashing Unlock is not allowed')
Then when the phone is rebooted, the option is sometimes grayed out again, but it sometimes it stays on. It is running Android 11/RP1A.201005.004.A1/6934943, latest securiy patch.
On Verizon's site, the IEMI reports GOOGLE PIXEL 2 NON-VZW.
Click to expand...
Click to collapse
Same problem, phone was bought from Google but it was a reburbished replacement after my first one broke.
Ever find a solution?
bill_mcgonigle said:
I read on a Google forum that if your IMEI starts with 35 then it's an ex-Verizon phone so the bootloader is Verizon. Can you guys confirm that yours is 35* too?
Click to expand...
Click to collapse
I have the same problem on two Pixel 2 devices one is from Verizon the other isn't and has OEM unlock. They both start with 35 and both won't unlock the bootloader. Can you post a link to the Google forum post? I would like to read it.
has anybody found a solution to this? Why is this only appearing recently? It seems that these phones might have been flashed with incorrect firmware or a bug in the firmware?
kercre123 said:
I have an unlocked variant of the Pixel 2. I put a Verizon SIM in it, and because of that, OEM unlocking was grayed out. However, a factory reset allowed me to enable it in developer settings. But when I tried to go to fastboot and unlock the bootloader, it kept giving me the following:
Code:
FAILED (remote: 'Flashing Unlock is not allowed')
Then when the phone is rebooted, the option is sometimes grayed out again, but it sometimes it stays on. It is running Android 11/RP1A.201005.004.A1/6934943, latest securiy patch.
On Verizon's site, the IEMI reports GOOGLE PIXEL 2 NON-VZW.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net
kercre123 said:
I have an unlocked variant of the Pixel 2. I put a Verizon SIM in it, and because of that, OEM unlocking was grayed out. However, a factory reset allowed me to enable it in developer settings. But when I tried to go to fastboot and unlock the bootloader, it kept giving me the following:
Code:
FAILED (remote: 'Flashing Unlock is not allowed')
Then when the phone is rebooted, the option is sometimes grayed out again, but it sometimes it stays on. It is running Android 11/RP1A.201005.004.A1/6934943, latest securiy patch.
On Verizon's site, the IEMI reports GOOGLE PIXEL 2 NON-VZW.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net
What could be reason behind "oem unlock failed" if your device bootloader is already unblocked?
You said its "unblocked" which pretty much means its already unlocked or something.
Title pretty much asks it all.
In developer options, OEM unlocking is greyed out. Is there a way to unlock and if so how?
TimmyP said:
Title pretty much asks it all.
In developer options, OEM unlocking is greyed out. Is there a way to unlock and if so how?
Click to expand...
Click to collapse
Have you connected to internet? What version of oxygen os are you on? And does it say "connect to the internet or contact your carrier" by the OEM unlocking toggle?
Yes Internet. Oos 11. I tried the T-Mobile app for permanent unlock it failed. Doesn't say anything but "allows the bl to be unlocked" but it's greyed.
TimmyP said:
Yes Internet. Oos 11. I tried the T-Mobile app for permanent unlock it failed. Doesn't say anything but "allows the bl to be unlocked" but it's greyed.
Click to expand...
Click to collapse
Permanent unlock is sim unlocking, has nothing to do with OEM unlocking
Thats great thanks
I got it. Set to midi connection so ADB detects phone.
adb shell
pm disable-user com.qualcomm.qti.uim
Now OEM unlocking is ungreyed
Its a no go. It reveals the option, but fastboot commands ask for a token.
Going to the Oneplus token generator with the correct info (because get oem info worked in fastboot) results in a window that says
"api router invoker request error"
It seems these phones are no longer rootable. Maybe when its paid off tmobile will give me a token.
Any ideas?
"fastboot flashing unlock" asks for token.
TimmyP said:
Its a no go. It reveals the option, but fastboot commands ask for a token.
Going to the Oneplus token generator with the correct info (because get oem info worked in fastboot) results in a window that says
"api router invoker request error"
It seems these phones are no longer rootable. Maybe when its paid off tmobile will give me a token.
Any ideas?
"fastboot flashing unlock" asks for token.
Click to expand...
Click to collapse
Maybe the site down, probably wait a bit, got the same error too
Thanks Ill get all prudent info in a text file. What a pita. I loathe having a new phone and not knowing whether I can root it. So much setting up already.
I tried it again for the heck of it, and now it says "IMEI number has been applied" ...so I guess I wait for the email?
Never got a confirmation or anything, but searches tell me I should get it in a few days to weeks.
TimmyP said:
I tried it again for the heck of it, and now it says "IMEI number has been applied" ...so I guess I wait for the email?
Never got a confirmation or anything, but searches tell me I should get it in a few days to weeks.
Click to expand...
Click to collapse
i got mine around an hour later after applying mine, maybe check hourly to see if you gotten it or not?
Nothing. Tbh I think Im gonna return this. Its only 128gb version and I was much happier with rooted A32 5G.
Sucks cant even use tasker for fun stuff.
Look through the OP9 forums for the OnePlus Tool..... it helps you get the number you write down to request the unlock code from OnePlus, also it can ungrey the OEM switch
Thanks but I already got that stuff requested. Still no token :-( Been talking to support tho they said they are on it!
underworld737 said:
Have you connected to internet? What version of oxygen os are you on? And does it say "connect to the internet or contact your carrier" by the OEM unlocking toggle?
Click to expand...
Click to collapse
OMG !
I have spent 7 hours attempting to unlock my Boot-Loader, and in the desire to prevent any unintended updates, I did not connect my OP9 to the network.
I Think That This Advice Should be Stickied to the front page:
"Unable to toggle OEM unlocking in <Developer Settings> ?"
"Connect to Internet first to see if it's already done !!"
HOWEVER, I still cannot :
Code:
flashboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
barguybrady said:
OMG !
I have spent 7 hours attempting to unlock my Boot-Loader, and in the desire to prevent any unintended updates, I did not connect my OP9 to the network.
I Think That This Advice Should be Stickied to the front page:
"Unable to toggle OEM unlocking in <Developer Settings> ?"
"Connect to Internet first to see if it's already done !!"
HOWEVER, I still cannot :
Code:
flashboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
Click to expand...
Click to collapse
Try ,,,,,,fastboot oem unlock,,,,
Its fastboot flashing unlock and I wouldnt recommend anything but using a token, because the rooting information here is fragmented and outdated.
Request one from oneplus and check back on that page you requested it on. Mine took about 3 days.
TimmyP said:
Its fastboot flashing unlock and I wouldnt recommend anything but using a token, because the rooting information here is fragmented and outdated.
Request one from oneplus and check back on that page you requested it on. Mine took about 3 days.
Click to expand...
Click to collapse
I already have that... Hence my confusion.
I'm thinking that there's Just One Little Thing I'm doing wrong here... Can't figure it out..!
Aha. I had been doing it in the wrong order.
Bash:
fastboot devices
fastboot flash cust-unlock unlock_code.bin
fastboot oem unlock