Database Info

Google Direct Phone - OEM Bootloader Greyed Out

So I picked up a backup a non-Verizon Pixel today New - it is my backup phone - I went to unlock the bootloader and the OEM Bootloader is greyed out under Developer Options. I did stick my VZW sim card in to make a phone call - it is on 7.1.1 and on the February NOF26V - I would liek to root it - is it possible or am I SOL

If it is Google phone it should unlock. You got it from a reliable source? Sometimes that slider needs an internet connection before it will work.
And grab an app from the play store called Get CID. Dig through the output and tell us what the CID is? All 1's or does it start with VZW?

cannot find that app - there was no bloatware on the phone at all - got an app called CID Getter- digging though it what am I looking for it- I do not have my SIM in this phone

bturkel said:
cannot find that app - there was no bloatware on the phone at all - got an app called CID Getter- digging though it what am I looking for it- I do not have my SIM in this phone
Click to expand...
Click to collapse
Bloat doesn't count, both are bloat free
That's a the app. About 60 percent down frim the top. The top line in the pic below ro.boot.cid
Is it all 1's or is does it start with VZW?

needs internet connection for the oem bootloader unlock option to become "ungrayed" unless its really the verizon version. Just connect it to wifi and make sure....

It is the Verizon version - how did it get all the bloatware removed?

Connect to a WiFi router make sure you have enabled security pin password or pattern. Should ungrey

Noe a VZW version on 7.1.1

bturkel said:
It is the Verizon version - how did it get all the bloatware removed?
Click to expand...
Click to collapse
Doesn't have bloatware. Doesn't matter of the phone is from google or Verizon if you activate with a Verizon sim it will download 3 Verizon apps. Other than that the only difference is the google pixel bootloader can be unlocked. If you have a CID of a Verizon pixel then you can't unlock the bootloader if its already on 7.1.1

DELETE

aholeinthewor1d said:
Doesn't have bloatware. Doesn't matter of the phone is from google or Verizon if you activate with a Verizon sim it will download 3 Verizon apps. Other than that the only difference is the google pixel bootloader can be unlocked. If you have a CID of a Verizon pixel then you can't unlock the bootloader if its already on 7.1.1
Click to expand...
Click to collapse
Not true. My CID indicates it's a Verizon version but it's unlockable without dePixel8. This is a Google Play version with a Verizon CID. I'm not alone in this.

PsiPhiDan said:
Not true. My CID indicates it's a Verizon version but it's unlockable without dePixel8. This is a Google Play version with a Verizon CID. I'm not alone in this.
Click to expand...
Click to collapse
aholeinthewor1d said:
Doesn't have bloatware. Doesn't matter of the phone is from google or Verizon if you activate with a Verizon sim it will download 3 Verizon apps. Other than that the only difference is the google pixel bootloader can be unlocked. If you have a CID of a Verizon pixel then you can't unlock the bootloader if its already on 7.1.1
Click to expand...
Click to collapse
Same here. I am on the same boat with PsiPhiDan. I got (VZW__001) Verizon pixel replacement from google customer services rep. Here is what I did, I took the sim card out when i got then phone one hand, and power on, run the update without sim card (updated to 7.1.1 NOF26V). Now I am on 7.1.1 (NOF26V) with ATT, but i am still able to unlock bootloader via OEM method. What wrong with you guy phone ???
My phone show CID = VZW__001
[ro.boot.cid]:[VZW__001]
Following steps:
Unlocked developer mod -> CHECKed OEM unlocking -> CHECKed USB debugs
THEN CMD:
adb reboot bootloader
fastboot flashing unlock
Volume Up + power button = YES
fastboot reboot
Done!

Verizon Unlock?

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

Working root instructions for Verizon Pixel 4 XL

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.

(Help) Unlocked carrier phone with a greyed out OEM

So I bought a unlocked google pixel 3a on ebay a few months ago and the OEM is greyed out. It says under the OEM that it can't be unlocked because it's carrier locked but I checked and it let me switch carriers. I'm not sure what's wrong with it and any help would be great.

zach183323 said:
So I bought a unlocked google pixel 3a on ebay a few months ago and the OEM is greyed out. It says under the OEM that it can't be unlocked because it's carrier locked but I checked and it let me switch carriers. I'm not sure what's wrong with it and any help would be great.
Click to expand...
Click to collapse
There is nothing out of place in your description, what you are asking about is not an issue, it is a matter of you not understanding the difference between bootloader unlock and carrier/network/SIM unlock.
OEM unlock setting and network unlock are two different things.
The OEM unlock setting deals with unlocking bootloader in order to use unapproved/modified software and/or root android devices.
Carrier/network/SIM unlock deals with switching to a different country/region/carrier/network.
You can have a carrier unlocked device while also having a locked bootloader. In your case, your device is not network locked "to" a specific carrier, it is merely bootloader locked "by" a specific carrier.
If it is a US Verizon branded Pixel 3a, the bootloader is locked and cannot be unlocked. I believe the US AT&T Pixel 3a is also bootloader locked, but I could be wrong.
What is your Pixel's exact model number? Is it a carrier branded device? If so, what carrier name is printed on the device or what carrier name shows during boot animation or what kind of carrier bloatware is on the device?
Sent from my SM-S767VL using Tapatalk

Thanks for the response, my model number is "G020C" and on the ebay page says the locked version is locked to sprint however there aren't any sprint bloatware on the device nor is there any carrier name on the boot up animation just the google logo. Do you think it still would be possible at all to unlock the bootloader at all?

zach183323 said:
Thanks for the response, my model number is "G020C" and on the ebay page says the locked version is locked to sprint however there aren't any sprint bloatware on the device nor is there any carrier name on the boot up animation just the google logo. Do you think it still would be possible at all to unlock the bootloader at all?
Click to expand...
Click to collapse
I'm not familiar with your specific device. It seems to me that it is probably a Sprint Pixel 3aXL(your model number shows up as a Pixel 3aXL, not as a Pixel 3a as referenced by your posted above) but has been flashed with the Vanilla Google stock firmware instead of a bloated Sprint stock firmware.
As for unlocking bootloader, you should be able to unlock it, but, you will have to research the exact method to unlock the bootloader, sometimes devices require a method that is specific to that device, the generic bootloader unlock methods do not work on all devices.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
I'm not familiar with your specific device. It seems to me that it is probably a Sprint Pixel 3aXL(your model number shows up as a Pixel 3aXL, not as a Pixel 3a as referenced by your posted above) but has been flashed with the Vanilla Google stock firmware instead of a bloated Sprint stock firmware.
As for unlocking bootloader, you should be able to unlock it, but, you will have to research the exact method to unlock the bootloader, sometimes devices require a method that is specific to that device, the generic bootloader unlock methods do not work on all devices.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Okay that actually explains a lot, do you think it would be possible to enable the OEM from a pc? I'm just having trouble finding a guide to unlocking the bootloader because a lot of them require the OEM to be unlocked in the developer options.

zach183323 said:
Okay that actually explains a lot, do you think it would be possible to enable the OEM from a pc? I'm just having trouble finding a guide to unlocking the bootloader because a lot of them require the OEM to be unlocked.
Click to expand...
Click to collapse
You may have to wait for a certain period of time before you can enable OEM unlock. Some devices just require being in a powered state with a constant mobile data connection for at least 7 days straight, then the OEM unlock setting can be enabled. Some devices have other additional requirements for unlocking bootloader.
What you probably should have done is unlock the bootloader before you switched the device to a different network, then, after the bootloader was unlocked, then you could have switched networks. An incomplete SIM unlock can cause the OEM unlock setting to be grayed out, correctly or completely unlocking the SIM might make the setting available.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
You may have to wait for a certain period of time before you can enable OEM unlock. Some devices just require being in a powered state with a constant mobile data connection for at least 7 days straight, then the OEM unlock setting can be enabled. Some devices have other additional requirements for unlocking bootloader.
What you probably should have done is unlock the bootloader before you switched the device to a different network, then, after the bootloader was unlocked, then you could have switched networks. An incomplete SIM unlock can cause the OEM unlock setting to be grayed out, correctly or completely unlocking the SIM might make the setting available.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Yeah I heard about that you have to use a device for a certain amount of time for certain carriers, but I've been using this phone for months now and the option hasn't been available yet. I'm not sure what requirements I have to do since the device is carrier unlocked now. Could I hard reset it and before I put the sim card in would the OEM option be available?

zach183323 said:
Yeah I heard about that you have to use a device for a certain amount of time for certain carriers, but I've been using this phone for months now and the option hasn't been available yet. I'm not sure what requirements I have to do since the device is carrier unlocked now. Could I hard reset it and before I put the sim card in would the OEM option be available?
Click to expand...
Click to collapse
You would be better off to ask your questions in the Pixel 3a XL Q&A subforum, the members there are users of that device and would know more about the specifics involved for your specific model number/carrier.
https://forum.xda-developers.com/pixel-3a-xl/help
Here is a link to the complete Pixel 3a XL forum, search through the subforims for more information about your specific model number.
Sent from my SM-S767VL using Tapatalk

Can anyone confirm this Verizon bootloader unlock works?

According to this thread( https://slickdeals.net/f/14948867-google-pixel-3-phone-64-gb-pink-169-99?page=16#commentsBox ), one could unlock the bootloader of a Verizon 3 with the following method. I have already installed this month's update, so I cannot test it for now. If you have a Verizon Pixel 3 and have not installed this month's update, can you test this?
"
remove sim (!!!) if you ran it before with the sim inside - remove sim and do factory reset TWICE
connect to wifi
let it download the update
DONT INSTALL UPDATE
go to About Phone -> Build Version. Click it 10 times until it tells you're the Developer now
go to Developer menu
wait until the OEM unlock option becomes clickable (happens after system update is downloaded, but NOT installed)
toggle OEM unlock (result: should be enabled)
Enable USB debug on the phone (also Developer menu)
connect the device to your win/mac/linux machine with adb installed with USB cable with data pins. Phone will ask if you authorize your PC to USB debug it
from your PC run : "adb reboot bootloader". That will reboot your phone to bootloader with message and status "locked"
from your PC while your phone is in fastboot mode: "fastboot flashing unlock" (that should respond with
OKAY [ 0.356s]
Finished. Total time: 0.368s)
You're good now. It's bootloader unlocked. you can install any updates. It will not lock itself and can install any other 3rd party firmware (on your risk, sure)"

No replies... So, the method does not work?

yourrealking said:
No replies... So, the method does not work?
Click to expand...
Click to collapse
According to this thread, you have to do it when initially setting up the phone, before connecting to Verizon.
https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/

dcarvil said:
According to this thread, you have to do it when initially setting up the phone, before connecting to Verizon.
https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
Click to expand...
Click to collapse
That means that only never-used Verizon Pixel3 can be bootloader-unlocked using that method, and used Verizon Pixel3 phones has no chance of unlocking the bootloader, is that right?

yourrealking said:
That means that only never-used Verizon Pixel3 can be bootloader-unlocked using that method, and used Verizon Pixel3 phones has no chance of unlocking the bootloader, is that right?
Click to expand...
Click to collapse
That is the way I understand it.

dcarvil said:
That is the way I understand it.
Click to expand...
Click to collapse
Is there any way for refurbished Pixel 3a XL to get bootloader unlocked? The main issue is OEM unlocking greyed out. Is there any sense to try this method?

Ele Na said:
Is there any way for refurbished Pixel 3a XL to get bootloader unlocked? The main issue is OEM unlocking greyed out. Is there any sense to try this method?
Click to expand...
Click to collapse
It shouldn't hurt to try, but if it is a Verizon phone it is unlikely to work.

Ele Na said:
Is there any way for refurbished Pixel 3a XL to get bootloader unlocked? The main issue is OEM unlocking greyed out. Is there any sense to try this method?
Click to expand...
Click to collapse
I have given up. I will wait until the official software support from Google ends (later this year). End of support means that whatever exploit will be found will not be patched by Google, so if people could find a way to unlock the bootloader using some security vulnerabilities, the method will reliably work from that point on for ever.

yourrealking said:
I have given up. I will wait until the official software support from Google ends (later this year). End of support means that whatever exploit will be found will not be patched by Google, so if people could find a way to unlock the bootloader using some security vulnerabilities, the method will reliably work from that point on for ever.
Click to expand...
Click to collapse
Even for Verizon version?