Related
Hi all,
Just got the Pixel 2 device from Official Google partner in INDIA so called flipkart. First thing i tried after getting the device was to go for unlock. But not able to unlock the device since last 2 days. Been to developer settings -> Allow Oem Unlock ( wasnt greyed out ) But actual problem starts when i rebooted into bootloader mode and executed -> fastboot flashing unlock giving me error saying "failed to unlock" and after reboot when i check the setting it was completely greyed out. Updated to Latest 8.1 And Dec Security Patch. Any Solution ? ( tried google , but all are saying pixel 2 bootloader issue has been fixed by google ) What i am missing ?
Thank you in Advance.
Update : Its google official model GO11A (sim unlocked) and not a Verizon model.
I saw you replied to my thread, and I'll reply to this for anyone else that sees it. It's a hardware problem. The only solution I'm aware of is an RMA. My second phone unlocked just fine.
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.
I just unlocked the bootloader on my shiny new Pixel 4 XL. It is the Verizon variant as it was purchased directly from Verizon themselves. I'm unsure whether this is a coincidence, whether Google is no longer offering cell phone service providers a locked bootloader option, or did I just get lucky. The steps I took are...
1: Removed the pre-installed sim card
2: Went through the set-up process via Wi-Fi
3: Immediately turned on Developer options
4: Turned on OEM Unlock
5: Used the "fastboot flashing unlock" command via ADB/Fastboot
Normally the OEM unlock option would be greyed out as it was on my original Pixel XL that I also bought through Verizon but was able to use DePixel to unlock, then flash the Google Factory Image, the bootloader. I was then able to re-lock the bootloader for security and mobile payment reasons while retaining the "OEM unlock" option in the developer settings. I will now attempt to do the same thing when Google releases the Factory Image for the Pixel 4 XL.
It also could be because I removed the sim card before the phone had the opportunity to activate.
I am interested whether anyone else has been able to do this.
BTW: Model# G020J
Kool19 said:
I just unlocked the bootloader on my shiny new Pixel 4 XL. It is the Verizon variant as it was purchased directly from Verizon themselves. I'm unsure whether this is a coincidence, whether Google is no longer offering cell phone service providers a locked bootloader option, or did I just get lucky. The steps I took are...
1: Removed the pre-installed sim card
2: Went through the set-up process via Wi-Fi
3: Immediately turned on Developer options
4: Turned on OEM Unlock
5: Used the "fastboot flashing unlock" command via ADB/Fastboot
Normally the OEM unlock option would be greyed out as it was on my original Pixel XL that I also bought through Verizon but was able to use DePixel to unlock, then flash the Google Factory Image, the bootloader. I was then able to re-lock the bootloader for security and mobile payment reasons while retaining the "OEM unlock" option in the developer settings. I will now attempt to do the same thing when Google releases the Factory Image for the Pixel 4 XL.
It also could be because I removed the sim card before the phone had the opportunity to activate.
I am interested whether anyone else has been able to do this.
BTW: Model# G020J
Click to expand...
Click to collapse
Did this just now on my AT&T Pixel 4 XL 128GB. Nada... Screw this; I'm returning this.
Kool19 said:
I just unlocked the bootloader on my shiny new Pixel 4 XL. It is the Verizon variant as it was purchased directly from Verizon themselves. I'm unsure whether this is a coincidence, whether Google is no longer offering cell phone service providers a locked bootloader option, or did I just get lucky. The steps I took are...
1: Removed the pre-installed sim card
2: Went through the set-up process via Wi-Fi
3: Immediately turned on Developer options
4: Turned on OEM Unlock
5: Used the "fastboot flashing unlock" command via ADB/Fastboot
Normally the OEM unlock option would be greyed out as it was on my original Pixel XL that I also bought through Verizon but was able to use DePixel to unlock, then flash the Google Factory Image, the bootloader. I was then able to re-lock the bootloader for security and mobile payment reasons while retaining the "OEM unlock" option in the developer settings. I will now attempt to do the same thing when Google releases the Factory Image for the Pixel 4 XL.
It also could be because I removed the sim card before the phone had the opportunity to activate.
I am interested whether anyone else has been able to do this.
BTW: Model# G020J
Click to expand...
Click to collapse
What is DePixel?
DePixel8
Who-Lep said:
What is DePixel?
Click to expand...
Click to collapse
It was software that would unlock the bootloader of the Google Pixel and Google Pixel XL that had the bootloader locked to Verizon. The catch was it only worked on Android 7.1.0 I believe. It was patched shortly after so if you updated your device, no luck.
KillerBytes said:
Did this just now on my AT&T Pixel 4 XL 128GB. Nada... Screw this; I'm returning this.
Click to expand...
Click to collapse
Sorry to hear that. Was your model number different. I am truly interested in why I was able to do this so easily.
Kool19 said:
Sorry to hear that. Was your model number different. I am truly interested in why I was able to do this so easily.
Click to expand...
Click to collapse
Model number is G020J as well.
got mine from vzw and was able to unlock bootloader as well, removed sim before turning on, set up phone on wifi and check oem unlocking in dev settings before popping in sim card
I am hoping I am in the same boat. I couldn't pass up getting 450 for a pixel xl so I bought the verizon variant it's coming Monday. I have seen where this has worked in the past with the pixel 2. Here is hoping the toggle gets grayed out when it's sees your on verizon's network. I plan on removing sim booting up and getting to developer options taking the least path of resistance and then trying to unlock. If I am successful I will report back.
Well I'm beat my is locked
bigv5150 said:
Well I'm beat my is locked
Click to expand...
Click to collapse
I'm waiting on a 128 GB white from Verizon, but I tried it on my dad's black 64 GB. His is locked as well unfortunately.
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.
Got an unlocked Pixel 6a delivered yesterday from the Google Store. Was planning to root it immediately upon setup but the "OEM Unlock" option in Dev settings is greyed out, saying "Connect to the internet or contact your carrier". I am connected to the internet, have a Visible SIM installed, and am on the most recent Android 13 update available for the 6a. I have tried all of the options, including factory resetting, going through setup without SIM or internet, etc. Google support has been of little to no help.
Pulled the build.prop using adb shell getprop and the value ro.oem_unlocking_supported does not exist.
Same here - same issue
this is super annoying, i wanted to root also! they need to fix this ASAP
Perhaps you can close this redundant thread since you cross posted to this one and it already has over 200 posts.
6a from Google: Can't unlock bootloader
Hi all, just received my 6a directly from Google and I seem to be unable to unlock the bootloader. The option "OEM unlocking" is greyed out and it says "Connect to the internet or contact your carrier.". I connected it to the internet via Wifi...
forum.xda-developers.com
Odd, when I got June update it became available. But I haven't received any update since, just waiting for ota. I think I'll wait rather than sideload, maybe it will stick.
tcat007 said:
Odd, when I got June update it became available. But I haven't received any update since, just waiting for ota. I think I'll wait rather than sideload, maybe it will stick.
Click to expand...
Click to collapse
Not for me. Just loaded stable 13 via beta; checked the unlock switch; still gray. So, I did the reset (but not the sim-removal-turn off wifi, etc) and still no bootloader unlock. What I haven't done is try the fastboot unlock anyway. It seems it would simply not work. However, trying to sideload the June OTA put my phone into a bootloop (which would have been so easy to fix with an unlocker BL) so not really going to mess around much.
Have you tried factory resetting after updating? That's what worked for me.
Yeah, I have, several times, but unfortunately to no avail.
I did the factory reset from the setting app and that did the trick. I had 13 plus the update before I did this.
mmead1143 said:
I did the factory reset from the setting app and that did the trick. I had 13 plus the update before I did this.
Click to expand...
Click to collapse
Yeah, for whatever reason that hasn't been working for me.
Just a guess, maybe go to settings/about phone/regulatory labels, and check your model number. Make sure they didn't mistakenly send you a locked to carrier phone.
Do you know of a list like that? That would be so helpful to so many.
I did the sign up for beta, get ota 13, sign out of beta, thing. Got 13 instantly (although takes 45 minutes to install), and unlock bootloader is still available.
bobby janow said:
Do you know of a list like that? That would be so helpful to so many.
Click to expand...
Click to collapse
What list are you talking about?
roirraW edor ehT said:
What list are you talking about?
Click to expand...
Click to collapse
A list of model numbers and which is Verizon, unlocked, ATT, Google unlocked etc. Things like that so if someone can't unlock the bl they can check their version/model. For instance I bought a BB unlocked and the model is:
GA03715-US
and in Regulatory Labels is shows GX7AS So I'm pretty much at a loss as to which devices are which if it even matters. I just see so many people that still can't unlock the bl even after updates and factory reset that maybe there is a pattern or versions that will not allow it.
@bobby janow You forgot to type a response when you quoted me. It just seemed like when you said something about a list that maybe you had posted that in the wrong thread, since I didn't notice anything else in the thread that made sense for that response.
Edit: Oh, you edited it now. Nevermind. I understand now.
list of pixel 6a models - Google Search
Although the first search result only lists:
Google Pixel 6a model numbersThe four model numbers are as follows:
A4RGB62Z
A4RG1AZG
A4RGX7AS
A4RGB17L
Click to expand...
Click to collapse
GSMArena only lists three:
ModelsGX7AS, GB62Z, G1AZG
Click to expand...
Click to collapse
tcat007 said:
I did the sign up for beta, get ota 13, sign out of beta, thing. Got 13 instantly (although takes 45 minutes to install), and unlock bootloader is still available.
Click to expand...
Click to collapse
Just received 6a today, straight outta the box set it up no sim installed checked version, it was 12 , OEM unlock greyed out, did a factory reset , no help, still greyed out, took the ota update , it's was just a newer version of 12, oem still greyed out, factory reset this version and it worked, oem unlock granted
HEY THIS MIGHT WORK FOR U!
Was having the same issue, nothing seemed to be working.
I had success finally, though!
Be sure you realize your phone will be wiped, etc.
Airplane Mode & No SIM inserted.
Remove All Accounts From Phone (to prevent issues with locks, etc)
Make sure you can put the phone in fastboot & adb modes
I put the phone in various modes to test, and ended up doing this:
[ REBOOT PHONE INTO SIDELOAD MODE VIA: ]
Code:
$ adb reboot sideload
Once the phone is ready to accept the side load OTA package, push that happy bullsh1t right on down the USB cable to the phone via:
Code:
adb sideload ~/MagicalGarbageDump/bluejay-ota-sd2a.220601.003-ddfde1f7.zip
From the OTA file downloaded directly from Google at THIS SITE. It's this one:
12.1.0 (SD2A.220601.003, Jun 2022)Linkddfde1f7edcdbb2b3de41d24f6c3f31587f836f387cab4cc6d16adee32bcab8a
After downloading and flashing that OTA, I had to "reset to factory settings" about two more times, seemingly randomly, and then it worked!
I made sure to have:
- NO SIM CARD IN THE PHONE.
- NO WIRELESS NETWORKS CONNECTED.
I am kind of annoyed it seemingly randomly decided to work, but also grateful that it finally unfzcked itself.
Also no luck over here. I bought my Pixel 6a directly from Google store as a "non locked device". It was sent from France Google store to Spain.
I'm in the 5th September security update under Android 13.
Tried all the tricks posted before: factory reset from settings and from recovery, sideload OTA, tried with sim and without it... No luck, OEM unlock still greyed out.
I wrote to Google about it. They asked me for the imei. After all, no help received from them to solve it.
Still waiting for "magically" disappear the greyed option...
l would send it back and get the p6 pro. For a few dollars more you get a better phone and no unlock issues.