Related
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
First of all: Is it normal for my OEM unlocking to be greyed out with status "Bootloader already unlocked" on this device after unlocking the bootloader? On my pixel2xl the option is not greyed out even after unlocking the bootloader, so I'm confused.
More info: Trying to set up a Pixel 2 64GB unlocked version from google store, it came on 8.0 November update. I was able to unlock the bootloader, had trouble flashing to the latest February 8.1 straight from November 8.0, but was able to boot back into 8.0 and let it do the OTA to 8.1 February update successfully. I factory reset after updating to 8.1 February update and have been connected to wifi and have a sim card in while setting up (if that matters), and now the option for OEM unlocking is still greyed out with status "Bootloader already unlocked". Not that it really matters I guess since I want the bootloader to remain unlocked, but the fact that it's different on my 2 pixel devices makes me think I did something wrong somewhere or misconfigured something.
KnifeSkills said:
First of all: Is it normal for my OEM unlocking to be greyed out with status "Bootloader already unlocked" on this device after unlocking the bootloader? On my pixel2xl the option is not greyed out even after unlocking the bootloader, so I'm confused.
More info: Trying to set up a Pixel 2 64GB unlocked version from google store, it came on 8.0 November update. I was able to unlock the bootloader, had trouble flashing to the latest February 8.1 straight from November 8.0, but was able to boot back into 8.0 and let it do the OTA to 8.1 February update successfully. I factory reset after updating to 8.1 February update and have been connected to wifi and have a sim card in while setting up (if that matters), and now the option for OEM unlocking is still greyed out with status "Bootloader already unlocked". Not that it really matters I guess since I want the bootloader to remain unlocked, but the fact that it's different on my 2 pixel devices makes me think I did something wrong somewhere or misconfigured something.
Click to expand...
Click to collapse
Dont worry, its normal.
shagbag913 said:
Dont worry, its normal.
Click to expand...
Click to collapse
But what if I need to re-lock my bootloader? Don't I need this switch available?
lucasdeeiroz said:
But what if I need to re-lock my bootloader? Don't I need this switch available?
Click to expand...
Click to collapse
Nope.
To lock the bootloader, connect via USB to a computer that has the SDK Platform Tools on it, and reboot to the bootloader.
Open a command prompt in your "platform tools" folder and type:
Code:
fastboot flashing lock
This will lock your bootloader and wipe the device. I believe this also sets the "get_unlock_ability" flag to 0 (which the OEM unlock switch corresponds to).
To explain this a little more simply:
There are three components in play here.
First, there is a firmware flag that determines whether the device can be unlocked at all: "ro.oem_unlock_supported". If this is set to 0, OEM Unlocking will be greyed out and unlocking is not possible.
Second, there is another firmware flag that determines whether the bootloader can be unlocked:
"get_unlock_ability". This corresponds to the OEM Unlocking switch - off is 0, on is 1. If the switch is on/flag is set to 1, the bootloader may be unlocked.
Third, there's the bootloader itself. If the "get_unlock_ability" flag is set to 0, the bootloader will refuse unlock commands. If the bootloader is already unlocked, it will override the flag.
Hope this helps and makes sense!
KnifeSkills said:
First of all: Is it normal for my OEM unlocking to be greyed out with status "Bootloader already unlocked" on this device after unlocking the bootloader? On my pixel2xl the option is not greyed out even after unlocking the bootloader, so I'm confused.
More info: Trying to set up a Pixel 2 64GB unlocked version from google store, it came on 8.0 November update. I was able to unlock the bootloader, had trouble flashing to the latest February 8.1 straight from November 8.0, but was able to boot back into 8.0 and let it do the OTA to 8.1 February update successfully. I factory reset after updating to 8.1 February update and have been connected to wifi and have a sim card in while setting up (if that matters), and now the option for OEM unlocking is still greyed out with status "Bootloader already unlocked". Not that it really matters I guess since I want the bootloader to remain unlocked, but the fact that it's different on my 2 pixel devices makes me think I did something wrong somewhere or misconfigured something.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net
i came here just to say that i love you, great tips
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.
I just got the Moto G 5G 2022 from metro yesterday after I broke the digitizer in my N200 5G. I was able to get the unlock code from Motorola's bootloader unlock website, but unfortunately the OEM unlock option is greyed out and says to connect to the internet or contact my carrier. From the little information I was able to find online it seems like this should resolve itself in 3+ days, but because I am impatient I was wondering if anybody knows the package that is responsible for the timer or whatever it is that motorola is using to prevent activating the OEM unlock for a specific time period. I know on the N200, you had to be network unlocked to enable the OEM unlock option, but there was a Qualcomm package that could be removed via ADB that instantly enabled the option. This is my first device with a mediatek chipset so I'm not sure if there is anything similar that can be done. Any help would be greatly appreciated.
Hey mate. I had the same issue. You need to wait 7 days to activate that option. It was greyed out for my phone, too, but on the 7th day, I was able to unlock the bootloader.
Yet, I could not root my phone. Even there's no TWRP right now working for this phone. If you know how to root it, please let me know.
enaykey said:
Hey mate. I had the same issue. You need to wait 7 days to activate that option. It was greyed out for my phone, too, but on the 7th day, I was able to unlock the bootloader.
Yet, I could not root my phone. Even there's no TWRP right now working for this phone. If you know how to root it, please let me know.
Click to expand...
Click to collapse
Just root it by patching the boot img with magisk and flashing from a PC.
https://mirrors.lolinet.com/firmware/motorola/austin/official/TMO/XT2213-3_AUSTIN_TMO_12_S1SAS32.47-59-7_subsidy-TMO_UNI_RSU_QCOM_regulatory-DEFAULT_cid50_CFC.xml.zip
Here's a link to stock firmware if you need the boot img
Pixel 6a OEM Unlocking Greyed Out STILL in August Update
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...
forum.xda-developers.com
Similar to the above thread?
Unlocked without a problem last week. I bought my phone from the google store. Did you get it some where else?
Just factory reset the device once and OEM unlocking becomes visible again. Just unlocked my device and flashed GrapheneOS without any issue.