Develop Bugs

Google VS. Non-Google Variant Differences

This thread is to gather technical clarification for those of us who have wondered about this:
If a Google phone (e.g. Pixel / Pixel XL) is purchased from another retailer (e.g. Verizon [with a locked bootloader]), other than the physical hardware, are there any technical differences in SOFTWARE and/or CODING that would restrict flashing OEM firmware from Google after the bootloader is unlocked?
***** (Is the Verizon variant restricted from flashing Google firmware?) *****
My apologies if this has been covered in another thread.

So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.

I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.

Radsolutionz said:
I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.
Click to expand...
Click to collapse
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?

1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.

Radsolutionz said:
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.
Click to expand...
Click to collapse
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.

1up1up said:
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.
Click to expand...
Click to collapse
Set it up on another computer and start from scratch. Windows 10 has some issues.... If it doesn't work and you want it done just get the device to me and I'll do it for u my self. Message me and I'll work it out with u.

My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app

suhailtheboss said:
My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
No. Until you see Jcase or another dev post a full Google Store conversion for the Verizon Pixel, do not relock your bootloader. That is, if you want to root your Verizon Pixel in the future.
Sent from my Pixel XL using XDA-Developers mobile app

1up1up said:
So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.
Click to expand...
Click to collapse
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.

1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.

dbrohrer said:
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.
Click to expand...
Click to collapse
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?

Mike02z said:
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.
Click to expand...
Click to collapse
I updated SDK and all is working.

1up1up said:
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?
Click to expand...
Click to collapse
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.

dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
I see... Thank you very much for explaining that.

dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?

coolhandz said:
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?
Click to expand...
Click to collapse
Unlocking will not disable updates. In Developer Options there is a toggle to disable this. Depending on what you do to your phone after bootloader unlock, disabling this might be important to prevent bootloop during an update.
Aside from root, various flashable mods, custom rom, or custom kernel, there is not really a need to unlock. Your phone is certainly less secure by doing so. If you plan to stay completely stock, keep your bootloader locked.

[Resolved] OEM Unlocking disabled on Google Store purchased phone

EDIT: Resolved: While the OS had said it was up-to-date when I originally checked. It was not. After a bit of time it alerted me that an update was available. After updating the OS the OEM Unlocking option was no longer disabled.
I purchased a Pixel XL specifically from Google Store because I wanted to receive either an bootloader unlocked or bootloader unlockable phone without resorting to any hacks that may not work in the future. It just arrived and I enabled Developer Options and enabled USB Debugging. However, the OEM Unlocking option is off and disabled (greyed).
I booted into the bootloader, it shows as locked. If I try to unlock it I get:
>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
If I try to flash it with the temporary TWRP boot up image:
>fastboot boot <path-to>\twrp-3.0.2-0-alpha2-fastboot-marlin.img"
downloading 'boot.img'...
OKAY [ 0.874s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.975s
I'd appreciate any suggestions for proceeding. Thank you.

Gregyski said:
(Since this isn't specifically about alternate firmware, I believe this is the correct forum and not the dev forum.)
I purchased a Pixel XL specifically from Google Store because I wanted to receive either an bootloader unlocked or bootloader unlockable phone without resorting to any hacks that may not work in the future. It just arrived and I enabled Developer Options and enabled USB Debugging. However, the OEM Unlocking option is off and disabled (greyed).
I booted into the bootloader, it shows as locked. If I try to unlock it I get:
>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
If I try to flash it with the temporary TWRP boot up image:
>fastboot boot <path-to>\twrp-3.0.2-0-alpha2-fastboot-marlin.img"
downloading 'boot.img'...
OKAY [ 0.874s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.975s
I'd appreciate any suggestions for proceeding. Thank you.
Click to expand...
Click to collapse
The command should be fastboot oem unlock

ilatimer1 said:
The command should be fastboot oem unlock
Click to expand...
Click to collapse
Unfortunately, that is also disallowed:
>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.046s

Gregyski said:
Unfortunately, that is also disallowed:
>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.046s
Click to expand...
Click to collapse
Did you go into Developer options is Settings and enable OEM unlocking first? If you don't have Developer Options in settings go to Settings/About Phone and then tap Build Number a bunch of times to enable it.

ilatimer1 said:
Did you go into Developer options is Settings and enable OEM unlocking first? If you don't have Developer Options in settings go to Settings/About Phone and then tap Build Number a bunch of times to enable it.
Click to expand...
Click to collapse
Thanks for your help ilatimer1, but I have resolved it now. I had edited the original post to indicate this but probably should have followed up at the end for your sake. I was just trying to avoid bumping it. At the time I asked the question, I mentioned that that option was disabled.
When I originally setup the phone I didn't enter WiFi data since I knew a factory reset would occur when I unlocked the bootloader. However, as a result of this, I didn't get alerted to the presence of an OS update. Ultimately, I setup WiFi and discovered the availability of an update. I proceeded to update and the OEM Unlocking feature then became enabled. Thanks again.

I unwapped and went stright to fastboot. didn't know update needed. thanks

Same issue unresolved
When I go into developer options OEM unlocking is still greyed out even after I downloaded the software update. Any leads on what to do?

[email protected] said:
When I go into developer options OEM unlocking is still greyed out even after I downloaded the software update. Any leads on what to do?
Click to expand...
Click to collapse
Where did you buy your Pixel?

Mr. Orange 645 said:
Where did you buy your Pixel?
Click to expand...
Click to collapse
verizon store

[email protected] said:
verizon store
Click to expand...
Click to collapse
The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.

Mr. Orange 645 said:
The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.
Click to expand...
Click to collapse
so there is no solution if Ive already updated to 7.1.1?
any chance a solution will open up in the future?

No there no solution right now. I wouldn't say there's absolutely no chance of finding another exploit, this is XDA after all, but I wouldn't count on it.

Mr. Orange 645 said:
No there no solution right now. I wouldn't say there's absolutely no chance of finding another exploit, this is XDA after all, but I wouldn't count on it.
Click to expand...
Click to collapse
so this toolkit isnt gonna work: http://www.wugfresh.com/nrt/
?

[email protected] said:
so this toolkit isnt gonna work: http://www.wugfresh.com/nrt/
?
Click to expand...
Click to collapse
No. That's for Nexus devices not Pixels anyway.

Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?

integraGSR said:
Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?
Click to expand...
Click to collapse
Im on Verizon

integraGSR said:
Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?
Click to expand...
Click to collapse
The Allow OEM Unlocking switch asks for a PIN? Do you have a PIN set up for the lockscreen? I'm guessing that's what it's asking for. Your contract status with ATT has nothing to do with the bootloader status. If you think so, just try it without your SIM card in it.

Mr. Orange 645 said:
The Allow OEM Unlocking switch asks for a PIN? Do you have a PIN set up for the lockscreen? I'm guessing that's what it's asking for. Your contract status with ATT has nothing to do with the bootloader status. If you think so, just try it without your SIM card in it.
Click to expand...
Click to collapse
LoL that was it. Sometimes it's back to the basics, think outside the box. Didn't think about lockscreen pin as I use fingerprint scanner all the time. Thanks.

integraGSR said:
LoL that was it. Sometimes it's back to the basics, think outside the box. Didn't think about lockscreen pin as I use fingerprint scanner all the time. Thanks.
Click to expand...
Click to collapse
LOL! Glad I could help!

Mr. Orange 645 said:
The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.
Click to expand...
Click to collapse
But pixels purchased at Google store with 7.1.1 are still unlockable correct?
Sent from my Pixel XL using Tapatalk

OEM Unlocking greyed

Hello I bought a pixel 2 xl from ebay for 450$. I live in France... The pixel was showed as unlocked from google store i recieved it but the oem unlocking is greyed out..
Can someone help me? There's a screenshot of the cid

sabi95190 said:
Hello I bought a pixel 2 xl from ebay for 450$. I live in France... The pixel was showed as unlocked from google store i recieved it but the oem unlocking is greyed out..
Can someone help me? There's a screenshot of the cid
Click to expand...
Click to collapse
You may have to call Google. I think that some versions sold/purchased in the EU have a 6 month waiting period before they can get an unlocking code ?

sabi95190 said:
Hello I bought a pixel 2 xl from ebay for 450$. I live in France... The pixel was showed as unlocked from google store i recieved it but the oem unlocking is greyed out..
Can someone help me? There's a screenshot of the cid
Click to expand...
Click to collapse
If it originally came from EE it is locked, but EE can unlock it. Did you factory reset it? That also was a bug and the reset cleared it.

Badger50 said:
You may have to call Google. I think that some versions sold/purchased in the EU have a 6 month waiting period before they can get an unlocking code ?
Click to expand...
Click to collapse
The device is from usa

sabi95190 said:
The device is from usa
Click to expand...
Click to collapse
Factory reset it then connect to the internet. Early on Google shipped a bunch that had this problem. The fixed it on their end but it requires a fact reset.

TonikJDK said:
Factory reset it then connect to the internet. Early on Google shipped a bunch that had this problem. The fixed it on their end but it requires a fact reset.
Click to expand...
Click to collapse
I reset it from the settings?

sabi95190 said:
I reset it from the settings?
Click to expand...
Click to collapse
Yep...settings/system/reset options :good:

Badger50 said:
Yep...settings/system/reset options :good:
Click to expand...
Click to collapse
Done but nothing change

sabi95190 said:
Hello I bought a pixel 2 xl from ebay for 450$. I live in France... The pixel was showed as unlocked from google store i recieved it but the oem unlocking is greyed out..
Can someone help me? There's a screenshot of the cid
Click to expand...
Click to collapse
Just to be clear, being SIM unlocked and bootloader unlocked are two completely different things. Are you sure the advertising for it being "unlocked" wasn't referring to the SIM status?

Namolas said:
Just to be clear, being SIM unlocked and bootloader unlocked are two completely different things. Are you sure the advertising for it being "unlocked" wasn't referring to the SIM status?
Click to expand...
Click to collapse
Yes I knew that but I thought that the Google Version have a unlockable bootloader...

sabi95190 said:
Yes I knew that but I thought that the Google Version have a unlockable bootloader...
Click to expand...
Click to collapse
Google version does have an unlockable bootloader. The question is are you 100% positive it's the Google version you bought/received and not the Verizon version?

Namolas said:
Google version does have an unlockable bootloader. The question is are you 100% positive it's the Google version you bought/received and not the Verizon version?
Click to expand...
Click to collapse
I looked for the cid of the phone and it appears that the phone isn't from Verizon. And the seller also told me that he bought the phone from Google store

It's likely the previous owner tried to unlock the bootloader and failed. By the looks of things the only current way to fix it is RMA to Google.
https://issuetracker.google.com/issues/68897739

ImWarped said:
It's likely the previous owner tried to unlock the bootloader and failed. By the looks of things the only current way to fix it is RMA to Google.
https://issuetracker.google.com/issues/68897739
Click to expand...
Click to collapse
I don't think it will be possible I'm not original owner

sabi95190 said:
I don't think it will be possible I'm not original owner
Click to expand...
Click to collapse
What version of android is it currently on?
After the factory reset, did you set the phone up at all, or just go to settings to try and enable it?
Set the phone up, connect it to WiFi and let it update system apps. You dont have to set the phone up completely, but let it connect to the internet and update.
Once thats done reboot it and skip thru any setup then go to settings and enable dev options and see if it is toggle-able.
Also make sure you are using the latest adb/fastboot.

uicnren said:
What version of android is it currently on?
After the factory reset, did you set the phone up at all, or just go to settings to try and enable it?
Set the phone up, connect it to WiFi and let it update system apps. You dont have to set the phone up completely, but let it connect to the internet and update.
Once thats done reboot it and skip thru any setup then go to settings and enable dev options and see if it is toggle-able.
Also make sure you are using the latest adb/fastboot.
Click to expand...
Click to collapse
delete

uicnren said:
What version of android is it currently on?
After the factory reset, did you set the phone up at all, or just go to settings to try and enable it?
Set the phone up, connect it to WiFi and let it update system apps. You dont have to set the phone up completely, but let it connect to the internet and update.
Once thats done reboot it and skip thru any setup then go to settings and enable dev options and see if it is toggle-able.
Also make sure you are using the latest adb/fastboot.
Click to expand...
Click to collapse
It didn't work
Edit: I verified the IMEI in a website and it shows as a verizon device...

help: can't OEM unlock Pixel 2 XL anymore

I can not OEM unlock my Pixel 2 XL anymore. It is running a custom ROM that is not being updated anymore. In the developer settings, "OEM unlocking" is gray, and it says "Connect to the Internet or contact your carrier". The phone is connected to the internet and the internet is working flawlessly. This is NOT a Verizon version and there already IS a custom ROM on it, so it's been unlocked in the past.
I have tried to factory reset numerous times, and the option still did not become available.
What else could I try?

oUkcpV9ykzUC said:
I can not OEM unlock my Pixel 2 XL anymore. It is running a custom ROM that is not being updated anymore. In the developer settings, "OEM unlocking" is gray, and it says "Connect to the Internet or contact your carrier". The phone is connected to the internet and the internet is working flawlessly. This is NOT a Verizon version and there already IS a custom ROM on it, so it's been unlocked in the past.
I have tried to factory reset numerous times, and the option still did not become available.
What else could I try?
Click to expand...
Click to collapse
Is it grayed out in the on or off position? Which is not uncommon on custom roms.

Do you have access to the the ROM if you need to reinstall it?
I would backup everything you can using twrp make a full and then also make sure you have boot.img backed up then try flashing factory image or whatever ROM you want to move to if you have an issue just switch back if it will take at all
Sent from my Pixel 2 XL using Tapatalk

So you unlocked it and flashed a custom ROM and then reinstalled the stock recovery and locked it like that for Android pay? Maybe the custom ROM was based off of a Verizon install so you phone thinks it's a Verizon phone now. You may be out of luck.

nukeruss said:
Maybe the custom ROM was based off of a Verizon install so you phone thinks it's a Verizon phone now. You may be out of luck.
Click to expand...
Click to collapse
Verizon Pixels are not unlockable, and no dev ia going to waste time working on a build based on an unlockable device...so this scenario is unlikely.
Flash the factory image for your device and you should be good.

sublimaze said:
Verizon Pixels are not unlockable, and no dev ia going to waste time working on a build based on an unlockable device...so this scenario is unlikely.
Flash the factory image for your device and you should be good.
Click to expand...
Click to collapse
Forgot to mention, this is NOT a ROM that uses TWRP, but its own recovery. Maybe I'm not understanding you right, but how do I flash a factory image if I can't OEM unlock?

gjkrisa said:
Do you have access to the the ROM if you need to reinstall it?
I would backup everything you can using twrp make a full and then also make sure you have boot.img backed up then try flashing factory image or whatever ROM you want to move to if you have an issue just switch back if it will take at all
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
It's not a ROM that uses TWRP but its own recovery. Not sure what you mean by "if you have an issue just switch back if it will take at all".

sublimaze said:
Verizon Pixels are not unlockable, and no dev ia going to waste time working on a build based on an unlockable device...so this scenario is unlikely.
Flash the factory image for your device and you should be good.
Click to expand...
Click to collapse
Flashing the factory image using Deuce's script will fix this.
Don't skip any steps.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Mine is grayed out with a notification underneath telling me the bootloader is already unlocked.

Larzzzz82 said:
Mine is grayed out with a notification underneath telling me the bootloader is already unlocked.
Click to expand...
Click to collapse
What do you get when you run...fastboot oem device-info...?
Is it grayed out in the on or off position?

Grayed off. Can't fastboot now but will when i can. This is not the vzw version and was unlocked within 10 minutes of unboxing it. The option didn't become available until it connected to a network...

Have you tried adb reboot fastboot?
Larzzzz82 said:
Grayed off. Can't fastboot now but will when i can. This is not the vzw version and was unlocked within 10 minutes of unboxing it. The option didn't become available until it connected to a network...
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

gjkrisa said:
Have you tried adb reboot fastboot?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I was no where near a computer... Is that a valid adb command? I go adb reboot- bootloader then fastboot devices before i do anything else.
---------- Post added at 09:33 AM ---------- Previous post was at 09:31 AM ----------
The get device-info returned:
Verity mode: true
Device unlocked: true
Charger screen enabled: true

Google Pixel 3 XL OEM unlocking greyed out ?

So I just got my Google pixel 3 XL straight from Google. First thing I wanted to do was root my phone. I've tried everything from restarting device and updating my phone to the latest updated ( I was told that it needs to update before OEM unlock is enabled) but still it's greyed out. Does anyone know what's going on ? I spent a lot of money to finally get an unlocked version to be able to root it.
I'm using At&t as my network.
If anyone has any input, I'd appreciate it. Thank you.

NVM saw another thread about this. Ignore.

Factory reset, tried that?
Sent from my Pixel 3 XL using Tapatalk

MArtyChubbs said:
Factory reset, tried that?
Click to expand...
Click to collapse
Yes, 4 times ! Lol

GunToYoMouth123 said:
Yes, 4 times ! Lol
Click to expand...
Click to collapse
A factory reset from setting won't work. If you haven't flashed the factory images with the wipe flag enabled, do that.
source: same thing happened to me.
Sent from my crosshatch using XDA Labs

Wondering if you have found a fix for this. I just received my RMA and also cannot unlock due to greyed out OEM Unlock. My first 3XL unlocked fine. Inserted Verizon sim, set up phone and then unlocked in Dev options. Currently Google support say there is no fix and they are looking into it. Just curious where you are in this...

ridobe said:
A factory reset from setting won't work. If you haven't flashed the factory images with the wipe flag enabled, do that.
source: same thing happened to me.
Click to expand...
Click to collapse
Not possible to flash factory image without unlocked bootloader

Larger thread going on here for the same issue (Lol dnd't read 2nd post)
https://forum.xda-developers.com/pixel-3-xl/help/oem-unlocking-grayed-t3860023

https://issuetracker.google.com/issues/119628469 Please star and contribute to the thread here

OEM Unlocking Greyed Out- Pixel 3XL
I purchased a brand new Pixel 3 XL from the Google Store. In the Developer's Option, it shows that the "OEM unlocking" is greyed out. I purchased an unlocked phone. Do not understand why I am not able to unlock it. Your assistance is much appreciated.
I do not have a sim card in it. Don't see the point why I am unable to unlock it.
Bootloader version: b1c1-0.1-5004167
Product revision: crosshatch MP1.0(ROW)
Any assistance is much appreciated.

See this thread..... https://forum.xda-developers.com/pixel-3-xl/help/oem-unlocking-grayed-t3860023/page24
Unfortunately you are not alone with this issue

Has anyone tried just swapping the motherboard with an unlocked one?

Has anyone tried just swapping the motherboard with an unlocked one?

I hate to beat a dead horse here. But in my Verizon 3xl I can switch OEM locking back and forth. It even gives me a warning about unlocking it. I've never tried anything past this point cause I don't want to rework my phone from the begining. Can everyone do this ?! Why isn't mine greyed out ?

MilkMan302 said:
Wondering if you have found a fix for this. I just received my RMA and also cannot unlock due to greyed out OEM Unlock. My first 3XL unlocked fine. Inserted Verizon sim, set up phone and then unlocked in Dev options. Currently Google support say there is no fix and they are looking into it. Just curious where you are in this...
Click to expand...
Click to collapse
Verizon blocks bootloader unlocking

tombaldwin6 said:
I hate to beat a dead horse here. But in my Verizon 3xl I can switch OEM locking back and forth. It even gives me a warning about unlocking it. I've never tried anything past this point cause I don't want to rework my phone from the begining. Can everyone do this ?! Why isn't mine greyed out ?
Click to expand...
Click to collapse
Does it work? Did you do anything specific?