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.
Related
Is there still no method to unlock the Verizon Pixel? Running 7.1.2
mackentosh said:
Is there still no method to unlock the Verizon Pixel? Running 7.1.2
Click to expand...
Click to collapse
NO. Not right now. Probably never.
A lot of people are reporting that the latest VZ Pixel shipments can be unlocked using adb. Search around, consider an RMA.
I literally just got my Pixel today. Ordered it from an authorized retailer here on the NEX in the naval base and it came with 7.1.1
To my surprise, the OEM unlock switch in Developer options wasn't greyed out, so I followed the instructions, unlocked the bootloader, took the update to 7.1.2 (bootloader still unlocked) and flashed TWRP and verifiedsigner (because the new 7.1.2 bootloader requires a signed recovery smh).
I think the new shipments of Pixels from Verizon are all from Google now.
Just had Asurion warranty replace the phone I bought from Verizon. I got my replacement last week (original phone had the hairline crack in the microphone, a known issue). Unfortunately, my phone I received had the 7.1.1 April build AND OEM unlock is greyed out in developer options. So I wasn't lucky enough to get a replacement from Google but from Verizon.
---------- Post added at 02:43 PM ---------- Previous post was at 02:40 PM ----------
w0rdie said:
A lot of people are reporting that the latest VZ Pixel shipments can be unlocked using adb. Search around, consider an RMA.
Click to expand...
Click to collapse
This sounds incorrect. Before the 7.1.1 update from Verizon, yes, you could do this using the dePixel8 utility which works off of adb. You would adb push the file to system, chmod it and execute it.
I just did a search and there's no new adb method that will work if your phone is from Verizon AND has 7.1.x on it.
So here's the deal, remove the sim before you boot it, then update to 7.1.2 without the sim, OEM unlock will not be greyed out then I just ran fastboot OEM unlock command and it unlocked the bl. I work at Verizon and have tried it on 4 phones out of the box. Something with the sim locks the bl permanently
Are you serious?
seshaz said:
So here's the deal, remove the sim before you boot it, then update to 7.1.2 without the sim, OEM unlock will not be greyed out then I just ran fastboot OEM unlock command and it unlocked the bl. I work at Verizon and have tried it on 4 phones out of the box. Something with the sim locks the bl permanently
Click to expand...
Click to collapse
This almost sounds too good to be true. If this is for real then you should start your own thread and shout it from a mountaintop.
I didn't find it, people were talking about it In another thread.
I work for Verizon and have tried it on a few phones, I remove the sim and do the update and every time it let's you OEM unlock
So do you think factory reset, update to newer monthly os/android o while keeping the sim out will do the trick as well?
con4n007 said:
So do you think factory reset, update to newer monthly os/android o while keeping the sim out will do the trick as well?
Click to expand...
Click to collapse
nobody could say it should or shouldn't without trying it. if you have to go back from android o to 7.1.2 though, it will factory reset your phone so consider making a backup.
Really!?!?
I am able to unlock my Pixel XL 32GB from Verizon, below is my fumbling around. Maybe this helps others, maybe I got dumb luck.
Bought phone at Verizon (Had to activate in store with 1 month pre-paid)
Phone powered on at Verizon store with sim in
As soon as the phone made it to the setup screen sim was removed
Fi sim was put in
Rebooted
Accidentally skipped through setup (I didn't know by saying don't use internet connection it would not allow the transfer of files)
Attempted to activate phone with Fi sim
Cannot activate due to v1 of the Fi sim (Error B034)
Factory default (Wanted to copy everything from N6 over)
Copied N6 files over, setup phone (Google account, wifi, apps, etc)
Received 7.1.2 update
Updated phone, rebooted
Tapped to enable dev options
Slider to enable oem unlocking
Checked CID, shows VZW_001
Enabled USB debugging
adb reboot-bootloader
fastboot oem unlock
From here I chose not to click yes to unlock as I just setup the phone, but can later for science if there is doubt. I am currently waiting for my new Fi sim to show.
gubarz said:
I am able to unlock my Pixel XL 32GB from Verizon, below is my fumbling around. Maybe this helps others, maybe I got dumb luck.
Bought phone at Verizon (Had to activate in store with 1 month pre-paid)
Phone powered on at Verizon store with sim in
As soon as the phone made it to the setup screen sim was removed
Fi sim was put in
Rebooted
Accidentally skipped through setup (I didn't know by saying don't use internet connection it would not allow the transfer of files)
Attempted to activate phone with Fi sim
Cannot activate due to v1 of the Fi sim (Error B034)
Factory default (Wanted to copy everything from N6 over)
Copied N6 files over, setup phone (Google account, wifi, apps, etc)
Received 7.1.2 update
Updated phone, rebooted
Tapped to enable dev options
Slider to enable oem unlocking
Checked CID, shows VZW_001
Enabled USB debugging
adb reboot-bootloader
fastboot oem unlock
From here I chose not to click yes to unlock as I just setup the phone, but can later for science if there is doubt. I am currently waiting for my new Fi sim to show.
Click to expand...
Click to collapse
You received the update without the verizon sim in, using wifi I assume?
Yes WiFi was connected
gubarz said:
I am able to unlock my Pixel XL 32GB from Verizon, below is my fumbling around. Maybe this helps others, maybe I got dumb luck.
Bought phone at Verizon (Had to activate in store with 1 month pre-paid)
Phone powered on at Verizon store with sim in
As soon as the phone made it to the setup screen sim was removed
Fi sim was put in
Rebooted
Accidentally skipped through setup (I didn't know by saying don't use internet connection it would not allow the transfer of files)
Attempted to activate phone with Fi sim
Cannot activate due to v1 of the Fi sim (Error B034)
Factory default (Wanted to copy everything from N6 over)
Copied N6 files over, setup phone (Google account, wifi, apps, etc)
Received 7.1.2 update
Updated phone, rebooted
Tapped to enable dev options
Slider to enable oem unlocking
Checked CID, shows VZW_001
Enabled USB debugging
adb reboot-bootloader
fastboot oem unlock
From here I chose not to click yes to unlock as I just setup the phone, but can later for science if there is doubt. I am currently waiting for my new Fi sim to show.
Click to expand...
Click to collapse
Do I need a Fi sim for that, I'm not from US and using a local provider sim. I'm on 7.1.2 and have tried to factory reset it once but still get oem unlock greyed.
So if I just wait for the latest update to come out and then I update via wifi only and no sim I can then unlock the phone? Or does it mean that because I'm on O if I just remove the sim I can unlock or something? This would be amazing. I know I'm probably wrong but still...
cntryby429 said:
This almost sounds too good to be true. If this is for real then you should start your own thread and shout it from a mountaintop.
Click to expand...
Click to collapse
I bought my phone from Verizon and took the SIM out before turning it on. I went through the setup without connecting to WiFi or setting up an account. After that I opened settings and my Verizon device was running 7.1.1 February patch I believe. I enabled developer options and my OEM unlock switch wasn't greyed out. I flipped it and connected my device to my PC and rebooted it to the bootloader through ADB. I issues 'fastboot oem unlock' and the device unlocked without dePixel8 despite being a Verizon device. Its true, the SIM determines its gender.
beez1717 said:
So if I just wait for the latest update to come out and then I update via wifi only and no sim I can then unlock the phone? Or does it mean that because I'm on O if I just remove the sim I can unlock or something? This would be amazing. I know I'm probably wrong but still...
Click to expand...
Click to collapse
Perhaps. Won't know until a new update comes out. Either it will remember what it is and stay grayed out or it will do another check and enable it if not a Verizon sim.
I think it's long shot but let's hope.
This is all assuming that it is the sim that determines the lock status lol
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.
VERIZON PIXEL 4 XL Root Instructions
NOTE: You must do this PRIOR to activating the phone with Verizon. On my phone once I activated it the OEM bootloader unlock switch became greyed out. (Edit - after rebooting once activated the OEM lock is available again).
Steps I took:
1. Turn on the phone, do not activate the SIM with the carrier.
2. Update to the latest firmware version.
3. Reboot.
4. Enable developer settings, turn on OEM unlock
5. Boot in fastboot mode, run fastboot flash unlock in a shell, reboot.
6. Set up and activate (mine required a chat with Verizon to activate, it wouldn’t activate through the app).
7. Reboot into fastboot, flash a boot.img that has been patched (magisk_patched.img). You can find instructions on this elsewhere.
8. Reboot.
9. Install magisk manager (canary builds). It will say it needs to download a zip to fully install. Allow.
10. Reboot. You’re now rooted.
11. Magisk manager and magisk install may want to upgrade, feel free.
Enjoy!
NOTE: There are several who this has worked for, and some who haven't been able to get it to work. Suggest reading the thread and providing info on phones that do and don't unlock for whatever reason.
Any idea if this would work with the Pixel 4? Thanks
Sent from my [device_name] using XDA-Developers Legacy app
Menardo said:
Any idea if this would work with the Pixel 4? Thanks
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I can't say for certain, but I think it would just the same. I don't know of any reason it wouldn't.
Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.
mr.marcus said:
Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.
Click to expand...
Click to collapse
Did they ever get TWRP working correctly on the 3xl??
mr.marcus said:
Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.
Click to expand...
Click to collapse
TWRP isn't working on Android 10 currently. It'll need a lot of time to develop, as Google moved a lot of things related to recovery to new sections.
If you really want to root you should definitely patch the appropriate boot image (found here: https://developers.google.com/android/images) and follow the above mentioned steps.
Regarding AdAway: I'm using DNS66 since years. You can download an active the AdAway DNS serting to this app as well an AdBlock will work like a charm. No root needed.
Sent from my HTC U12+ using XDA Labs
Man I wish I saw this first. Well I hope another method comes along for those of us who activated already.
billydroid said:
Man I wish I saw this first. Well I hope another method comes along for those of us who activated already.
Click to expand...
Click to collapse
Well don't feel bad I tried it today before activating and it didn't work. It may wind up being a random occurrence with units that didn't have the IMEI's registered. That's probably why he had to contact Verizon to get the phone to work on their network.
CyberpodS2 said:
Did they ever get TWRP working correctly on the 3xl??
Click to expand...
Click to collapse
Not that I know of. I have been patching boot files for my 3 xl.
wolfu11 said:
Well don't feel bad I tried it today before activating and it didn't work. It may wind up being a random occurrence with units that didn't have the IMEI's registered. That's probably why he had to contact Verizon to get the phone to work on their network.
Click to expand...
Click to collapse
Perhaps. It knew it was a Verizon phone, it had a Verizon activation app. I was very careful to skip activation of any type at the store or when taking it home, so it might be that you need to tell Verizon that you'll activate it later to have the chance to unlock it.
Also, the OEM bootloader unlock has remained available after reboot. I think if it's unlocked in the way I describe it stays unlocked.
mr.marcus said:
Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.
Click to expand...
Click to collapse
You might be waiting awhile.
https://www.androidpolice.com/2019/10/24/android-10-twrp-pixel-3-4/?amp
Nice!
madscribblerz said:
VERIZON PIXEL 4 XL Root Instructions
NOTE: You must do this PRIOR to activating the phone with Verizon. On my phone once I activated it the OEM bootloader unlock switch became greyed out. (Edit - after rebooting once activated the OEM lock is available again).
Steps I took:
1. Turn on the phone, do not activate the SIM with the carrier.
2. Update to the latest firmware version.
3. Reboot.
4. Enable developer settings, turn on OEM unlock
5. Boot in fastboot mode, run fastboot flash unlock in a shell, reboot.
6. Set up and activate (mine required a chat with Verizon to activate, it wouldn’t activate through the app).
7. Reboot into fastboot, flash a boot.img that has been patched (magisk_patched.img). You can find instructions on this elsewhere.
8. Reboot.
9. Install magisk manager (canary builds). It will say it needs to download a zip to fully install. Allow.
10. Reboot. You’re now rooted.
11. Magisk manager and magisk install may want to upgrade, feel free.
Enjoy!
Click to expand...
Click to collapse
I was able to do this a couple days ago. I have heard conflicting reports regarding whether this is possible or not but it certainly worked for me. I don't really have any interest in root access on pixel devices so I will just flash the Google store variant factory image (which I think is the one without the C4 in it's build number) and relock it. Maybe I'll play around with it later
Just did the patched boot image method using Magisk to root my 4XL.
Works perfectly with Magisk Canary, exactly the same process I used to do with my Pixel 3
Just an FYI - while Magisk canary builds were required when Android 10 was first released, the Magisk stable version 20 works on Android 10. So while you may use beta or canary builds if you want to, it is no longer a requirement. You can use the latest stable build and be fine.
madscribblerz said:
Perhaps. It knew it was a Verizon phone, it had a Verizon activation app. I was very careful to skip activation of any type at the store or when taking it home, so it might be that you need to tell Verizon that you'll activate it later to have the chance to unlock it.
Also, the OEM bootloader unlock has remained available after reboot. I think if it's unlocked in the way I describe it stays unlocked.
Click to expand...
Click to collapse
I brought it home sealed in the box .
Removed the sim card and powered into bootloader. From there went to recovery mode and did a factory reset. Set it up without signing into my Google account or WiFi and then went to developer options it was grayed out stating"locked carrier device". Did a factory reset as normal and set it up without signing in then took the updates from WiFi. Rebooted and checked developer options still grayed out with same message. I have yet to put a Verizon sim it but did try a different carrier but still no luck. I did have luck with this procedure with one of my Verizon 2xl so I'm pretty sure I did it right. But anyway I didn't see the app you speak of. Where is it located? I only bought this phone because of the discount Verizon gave. I'll be selling it but was curious if it could be unlocked.
Did you unlock your bootloader or just flip the toggle?
wolfu11 said:
I brought it home sealed in the box .
Removed the sim card and powered into bootloader. From there went to recovery mode and did a factory reset. Set it up without signing into my Google account or WiFi and then went to developer options it was grayed out stating"locked carrier device". Did a factory reset as normal and set it up without signing in then took the updates from WiFi. Rebooted and checked developer options still grayed out with same message. I have yet to put a Verizon sim it but did try a different carrier but still no luck. I did have luck with this procedure with one of my Verizon 2xl so I'm pretty sure I did it right. But anyway I didn't see the app you speak of. Where is it located? I only bought this phone because of the discount Verizon gave. I'll be selling it but was curious if it could be unlocked.
Did you unlock your bootloader or just flip the toggle?
Click to expand...
Click to collapse
Both. I'm rooted using a patched magisk boot image, which I couldn't have flashed otherwise.
There does seem to be some mystery sauce here though. I didn't do anything with my SIM, I left it as it was. The app was carrier setup (in notifications prompting to activate) which I didn't launch until after having turned on the toggle, and having run fastboot flashing unlock, then fastboot flash boot magisk_patched.img. I did update to the .C4 release beforehand though, but didn't think that in any way related.
Maybe it was something to do with misconfiguration on the Verizon side - but that seems pretty unlikely given that they didn't even try to activate it and said when I got home to do so - so like you, I came home with it sealed in the box.
Maybe someone else can shed some light - as it seems we're about 50/50 on the unlocks. I bought mine retail at a verizon store. I essentially got it free, as I traded in a Galaxy 5 for $450, which pays out $18.50 a month, and cancelled Fi, which covers the phone's monthly with money coming in.
Damn my device didn't unlock
I wonder if this will work with Spectrum/Charter Wireless since they use Verizon's towers....If anyone knows or has any thoughts I would appreciate it.
wolfu11 said:
I brought it home sealed in the box .
Removed the sim card and powered into bootloader. From there went to recovery mode and did a factory reset. Set it up without signing into my Google account or WiFi and then went to developer options it was grayed out stating"locked carrier device". Did a factory reset as normal and set it up without signing in then took the updates from WiFi. Rebooted and checked developer options still grayed out with same message. I have yet to put a Verizon sim it but did try a different carrier but still no luck. I did have luck with this procedure with one of my Verizon 2xl so I'm pretty sure I did it right. But anyway I didn't see the app you speak of. Where is it located? I only bought this phone because of the discount Verizon gave. I'll be selling it but was curious if it could be unlocked.
Did you unlock your bootloader or just flip the toggle?
Click to expand...
Click to collapse
Did almost the same procedure with my dad's 64 GB black XL. I didn't go into bootloader but I took out the sim, set it up without signing in, and it gave me a greyed out message to turn on WiFi before I could do anything. Tried a factory reset, got the same message. Did another factory reset, set it up without any account but signed into my Wifi network, and it gave me the greyed out message that I can't OEM unlock on carrier locked devices.
When I get my phone I'm thinking about trying a quick WiFi toggle going back to developer settings and trying to unlock before it can communicate with Verizon. I doubt it'll work, but it's worth a shot.
madscribblerz said:
Both. I'm rooted using a patched magisk boot image, which I couldn't have flashed otherwise.
There does seem to be some mystery sauce here though. I didn't do anything with my SIM, I left it as it was. The app was carrier setup (in notifications prompting to activate) which I didn't launch until after having turned on the toggle, and having run fastboot flashing unlock, then fastboot flash boot magisk_patched.img. I did update to the .C4 release beforehand though, but didn't think that in any way related.
Maybe it was something to do with misconfiguration on the Verizon side - but that seems pretty unlikely given that they didn't even try to activate it and said when I got home to do so - so like you, I came home with it sealed in the box.
Maybe someone else can shed some light - as it seems we're about 50/50 on the unlocks. I bought mine retail at a verizon store. I essentially got it free, as I traded in a Galaxy 5 for $450, which pays out $18.50 a month, and cancelled Fi, which covers the phone's monthly with money coming in.
Click to expand...
Click to collapse
I'm a bit confused by the last part, so are you on a Verizon monthly payment plan?
bosox284 said:
Did almost the same procedure with my dad's 64 GB black XL. I didn't go into bootloader but I took out the sim, set it up without signing in, and it gave me a greyed out message to turn on WiFi before I could do anything. Tried a factory reset, got the same message. Did another factory reset, set it up without any account but signed into my Wifi network, and it gave me the greyed out message that I can't OEM unlock on carrier locked devices.
When I get my phone I'm thinking about trying a quick WiFi toggle going back to developer settings and trying to unlock before it can communicate with Verizon. I doubt it'll work, but it's worth a shot.
I'm a bit confused by the last part, so are you on a Verizon monthly payment plan?
Click to expand...
Click to collapse
I am on a 24 month payment plan, but those payments are negated by the trade in and extra money I save having only verizon without Fi.
OG Pixel from Verizon, had it for years, battery has been really ****ty lately. So I had to send my phone in to get a new battery, and the cost was similar to go thru google store, so I did. Wiped the phone, restored to stock android, but left bootloader unlocked. Got the phone back today and version of android was downgraded and bootloader was locked.
How ****ed am I and what are my recourses? Tried google support, they're nearly useless.
If you never booted the device yet you can try "fastboot flashing unlock" and it will just re-unlock. Other than that I don't think you will ever see a unlock status on that phone. This is why I do my repairs myself.
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Before updating in any way... Search Verizon unlock Pixel and see if that process will unlock. If you allow update past a certain level stuck with no options then if Verizon locked.
Oh, would never allow an update. I'm not crazy. Tried the unlock method with uninstalling the phone app before you get internet access the day I got it, still no dice. Thanks tho.
I just did a credit card chargeback as they sent me back my device in an unusable condition and refused to compensate for it. We'll see how it shakes out in a few weeks probably. Bought a refurb Pixel 3 in the meantime and it was already unlocked, so all is well.
Thanks for the replies though.
-N
n8lee said:
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Click to expand...
Click to collapse
Can you tell me what security patch you are on? If you are somewhere around Android 9 patch (potentially Android 10 early patches) you can re-unlock. If you try ticking the OEM unlock option in Dev options or if i heard correctly the phone wont boot? If you know your exact version you can try flashing it through recovery, or trying "fastboot unlock" after ticking the oem unlock. Also remember those old workarounds of removing android.phone and such? Yeah try those. Good luck. We'll try and get you unlocked again.
I got the Unlock Code from Moto with no problem, but can't get the phone to take it. FAIL, over and over again. I've tried several times, rebooted the phone, powered off, even tried an FDR. I keep getting a 'FAIL" message trying to push the code to the phone.
Just got the phone (used) today and I do have Unlock enabled in Dev Options. CID is 0x0032, obviously unlockabled since I did get the code from Moto. Twice. I redidthe Unlock request with a new string and got the same code again. Nothing is working. I've unlocked 15 or more Moto phones and never had anything like this happen before.
Using "fastboot oem unlock UNIQUE_KEY [20-character unlock code string]". Copied it, typed it manually, etc etc. FAIL FAIL FAIL.
Frustrating. Any clues/suggestions?
- - - - -
Edit to add: This phone has (I presume) the newest firmware on it, QZKS30.Q4-40-95-9 (RETUS), which has not been uploaded to lolinet yet.
Could this newest update be the problem? If so, can I safely roll back to 95-6 or even something older?
= = = = = = = = =
SOLVED. There was apparently an issue with the first phone I tried. Bought a second XT2113-2 relatively cheap (64GB) which came with the same 40-95-9 firmware, and it took the unlock code without a hitch.
I recall that I experienced something similar to this as well. A little bit of searching lead me to believe my issue was an older stock firmware bug. My stock firmware was initially from Jan 2021 and I did ota updates until it got to about Aug 2021 and then the phone unlocked. Can't say for sure that the deviced just needed time to "phone home" before allowing unlocking tho (I've read rumors).
If there is a ota update available, try that. I do know that I am able to relock/unlock on the 40-95-6 (Feb 2022) RETUS stock firmware.
notmyrealhandle said:
I recall that I experienced something similar to this as well. A little bit of searching lead me to believe my issue was an older stock firmware bug. My stock firmware was initially from Jan 2021 and I did ota updates until it got to about Aug 2021 and then the phone unlocked. Can't say for sure that the deviced just needed time to "phone home" before allowing unlocking tho (I've read rumors).
If there is a ota update available, try that. I do know that I am able to relock/unlock on the 40-95-6 (Feb 2022) RETUS stock firmware.
Click to expand...
Click to collapse
Thanks for replying. This phone has 40-95-9 firmware (March 1, 2022) which looks to be the latest OTA.
I have wondered if I'm stuck in another one of the newer Moto's (or Android's) mysterious holding patterns. Maybe it'll work in a few days. I will certainly post here if that's the case. . . . But why give me the Unlock button plus the Unlock Code, but then hold me back from actually pushing it to the phone? That wouldn't make a lot of sense.
This is the exact message returned by the bootloader every time:
(bootloader) usage: fastboot oem unlock < unlock code >
FAILED (remote failure)
I believe I'll try reflashing the 40-95-9 firmware, downloaded this morning via Rescue and Smart Assistant.
Reflashing firmware didn't help.
Edit to add:
I should probably stress, I flashed the entire firmware with no problems at all.
Should that suggest that this bootloader unlocking failure is not a hardware problem? . . . because if broke hardware is a possibility, I would definitely want to return this phone to the seller.
Moondroid said:
Reflashing firmware didn't help.
Edit to add:
I should probably stress, I flashed the entire firmware with no problems at all.
Should that suggest that this bootloader unlocking failure is not a hardware problem? . . . because if broke hardware is a possibility, I would definitely want to return this phone to the seller.
Click to expand...
Click to collapse
Two other things you can try:
1. make sure you are using an up to date fastboot exe (I'm using fastboot version 33.0.1-8253317 on ubuntu linux).
2. Try from both the bootloader mode and fastbootd mode on the device - I forget how to get to fastbootd from stock `adb reboot fastboot` might do it.
EDIT I'm pretty sure you want to be in the bootloader mode. Just thought I'd mention it as fastbootd was new to me and some fastboot commands seem to like the device to be in one mode or the other.
HTH
notmyrealhandle said:
Two other things you can try . . .
Click to expand...
Click to collapse
Still nothing.
I found some newer adb & fastboot utils (2021 vs 2018) and tried those. That just changed the error message a teensy bit (replaced "remote failure" with a couple of bare quote marks).
I also uninstalled & reinstalled my Motorola drivers before trying the newer adb & fastboot. That didn't help either.
Trying to boot twrp gives me a "permission denied" error.
So all I can think to try now is to run another firmware reinstall via LMSA (Rescue and Smart Assistant), just to see if that hiccups anywhere as much as anything. (I manually flashed all the files the first time.)
I think it's past time for me to say something like "this doesn't just suck, it SUPER-sucks." Moto gave me the phreaking Unlock code, but the phone won't let me use it.
Moondroid said:
Moto gave me the phreaking Unlock code, but the phone won't let me use it.
Click to expand...
Click to collapse
It will only work 48 hours after the unlock email is sent, as per this thread <https://forum.xda-developers.com/t/oem-unlocking-grayed-out-on-moto-g-play-2021.4259833/page-2>
I recently went through this myself. It was really baffling because the customer service / tech support would not tell me anything about it. Maybe it's some kind of hyper secret security measure?
Just keep the phone online and wait it out.
slipchicken said:
It will only work 48 hours after the unlock email is sent, as per this thread <https://forum.xda-developers.com/t/oem-unlocking-grayed-out-on-moto-g-play-2021.4259833/page-2>
I recently went through this myself. It was really baffling because the customer service / tech support would not tell me anything about it. Maybe it's some kind of hyper secret security measure?
Just keep the phone online and wait it out.
Click to expand...
Click to collapse
I tried the unlock code 5 minutes after I got it. Why would I wait 48 hours? Lol . . .
If this is another "time-delay" thing it doesn't make any sense at all. OEM Unlock was already enabled, the phone gave me an unlock string to send Moto, and I got the unlock key from Moto with no delays at all. Within an hour after unboxing the phone I was trying to push an unlock code to the phone.
I also tried getting another code from Moto, generated a new string and all, but the second code Moto sent me was exactly the same as the first. I did try it (again) on the phone but got the same "FAILED" message as before.
This is just nuts. Unless the latest OTA 95-9 is in fact the culprit. Moto's unlock-code process might still send unlock codes that possibly will no longer work after a certain point? Hopefully I'll get a definitive answer on this aspect soon.
Moondroid said:
Moto's unlock-code process might still send unlock codes that possibly will no longer work after a certain point? Hopefully I'll get a definitive answer on this aspect soon.
Click to expand...
Click to collapse
I meant that it will only start working once 48 hours have passed. Leaving internet active may be a requirement, and a restart may be a requirement too.
For instance if you get the first code email at 8:00am on June 7th, the code will only work after 8:00am on June 9th.
EDIT: Also I have tried manually changing the time in the phone's settings and it didn't work. I had to wait the full 48 hours for it to start working.
I do agree however that it is absolutely nuts of Motorola to do this without any sort of explanation. That's why I assume it's some kind of secretive or misguided anti-theft measure.
slipchicken said:
I meant that it will only start working once 48 hours have passed. Leaving internet active may be a requirement, and a restart may be a requirement too.
For instance if you get the first code email at 8:00am on June 7th, the code will only work after 8:00am on June 9th.
EDIT: Also I have tried manually changing the time in the phone's settings and it didn't work. I had to wait the full 48 hours for it to start working.
I do agree however that it is absolutely nuts of Motorola to do this without any sort of explanation. That's why I assume it's some kind of secretive or misguided anti-theft measure.
Click to expand...
Click to collapse
I was in that thread you quoted and I don't remember anything about having to wait AFTER getting the unlock code. Wait for OEM Unlock to show as enabled in Dev Options, yes, I'm thoroughly familiar with that. But I have never-never-never had to wait for an unlock code to work after receiving it from Moto. If that's in there somewhere please point more specifically? because I've unlocked a whole bunch of Moto phones and as I said, I've never heard of being able to enable OEM Unlock, getting the unlock code from Moto and then having to wait to use it.
See bottom of top post. The phone had some kind of problem that wouldn't allow it to accept the unlock key.