So, i broke my direct from google pixel xl, that was unlocked. I had insurance through verizon and they sent me a new one. Now, i know the verizon versions are locked, which is what i didn;t want, but i had no choice through asurion. The phone i received is on NHG47L which isn't the verizon version, but the OEM unlock is still grayed out. can anyone tell me why i can't unlock even though this seems to be a google fi/tmobile build?
i have no put a sim in it yet, i've only connected it to wifi. i'm waiting till i have a firm answer one way or the other.
@Legacystar,
See post #25 > https://forum.xda-developers.com/pixel-xl/help/oem-unlocking-disabled-google-store-t3507209/page3
cam30era said:
@Legacystar,
See post #25 > https://forum.xda-developers.com/pixel-xl/help/oem-unlocking-disabled-google-store-t3507209/page3
Click to expand...
Click to collapse
i did connect it to wifi, it did not change the OEM unlock option.
@Legacystar,
One can sideload any version of security update via ADB. If you've connected to internet and bootloader unlock is still grayed out, then it sounds like you do indeed have a VZW version.
cam30era said:
@Legacystar,
One can sideload any version of security update via ADB. If you've connected to internet and bootloader unlock is still grayed out, then it sounds like you do indeed have a VZW version.
Click to expand...
Click to collapse
Would flashing a factory image do anything, maybe a previous version?
Legacystar said:
Would flashing a factory image do anything, maybe a previous version?
Click to expand...
Click to collapse
If you can't unlock your bootloader, then you can't flash a factory image. If this is a VZW version, there's nothing you can do.
cam30era said:
If you can't unlock your bootloader, then you can't flash a factory image. If this is a VZW version, there's nothing you can do.
Click to expand...
Click to collapse
so, if the bootloader was never unlockable, how would one change the software version?
Legacystar said:
so, if the bootloader was never unlockable, how would one change the software version?
Click to expand...
Click to collapse
ADB sideload. Or wait for OTA to be pushed.
cam30era said:
ADB sideload. Or wait for OTA to be pushed.
Click to expand...
Click to collapse
i meant, how did this phone's software get changed?
Legacystar said:
i meant, how did this phone's software get changed?
Click to expand...
Click to collapse
The firmware is downloaded based on the sim in the device. Not where it was purchased
pcriz said:
The firmware is downloaded based on the sim in the device. Not where it was purchased
Click to expand...
Click to collapse
So theoretically, I could purchase a VZW pixel XL never connect to WiFi or data, and get home insert a T-Mobile sim and check the "OEM unlocking" then unlock the bootloader via fastboot. Then once I've flashed recovery and pure Nexus or any other rom install my VZW sim and profit?
mattwheat said:
So theoretically, I could purchase a VZW pixel XL never connect to WiFi or data, and get home insert a T-Mobile sim and check the "OEM unlocking" then unlock the bootloader via fastboot. Then once I've flashed recovery and pure Nexus or any other rom install my VZW sim and profit?
Click to expand...
Click to collapse
You still need to use the bootloader exploit before the firmware updates to 7.1.1, can't just unlock via fastboot like a play store model.
pcriz said:
You still need to use the bootloader exploit before the firmware updates to 7.1.1, can't just unlock via fastboot like a play store model.
Click to expand...
Click to collapse
Well I bought the 128gig pixel XL. Didn't let the sales person activate it for me or turn it on. I got it home and pulled the Sim and started it up with no Sim or wifi. My luck the freaking lcd doesn't work. It responds to touch and the phone boots but the screen would not light up a bit. So I took it back and exchanged for another. ....did the same with the Sim and no wifi.... Booted and straight to "About Phone" and of course it's on 7.1.1 already. This is the first phone I've had in 5-6 years that wasn't rooted and bootloader unlocked. What makes it even worse is it's a Google branded phone. I can't believe Google allows VZW to lock it down like this.
mattwheat said:
Well I bought the 128gig pixel XL. Didn't let the sales person activate it for me or turn it on. I got it home and pulled the Sim and started it up with no Sim or wifi. My luck the freaking lcd doesn't work. It responds to touch and the phone boots but the screen would not light up a bit. So I took it back and exchanged for another. ....did the same with the Sim and no wifi.... Booted and straight to "About Phone" and of course it's on 7.1.1 already. This is the first phone I've had in 5-6 years that wasn't rooted and bootloader unlocked. What makes it even worse is it's a Google branded phone. I can't believe Google allows VZW to lock it down like this.
Click to expand...
Click to collapse
Verizon isn't the only carrier to lock it down. Google has never been implicitly root friendly, also I'm sure a partner ship with verizon is to their benefit. Like getting their foot in the door to a wider market. The trade off is the bootloader.
Related
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.
Alright, let's get right to it.
I am receiving a replacement Pixel XL after sending my original one back to Google. I purchased my original Pixel from Verizon and sent back to Google a Verizon Pixel with a locked bootloader (from 7.1.1 patch). Few questions....
1. Am I receiving a Google pixel XL with an unlocked bootloader?
I have read that I can unlock the bootloader and successfully root BEFORE I set up wifi and put the SIM card in... So
2. Will the device ship with 7.1.1 (Verizon), ending any chance of me unlocking the bootloader?
3. If the device ships with 7.1, can I prevent the update being installed in the background?
I put a screenshot with the email from google about the replacement device below.
Splatlame said:
Alright, let's get right to it.
I am receiving a replacement Pixel XL after sending my original one back to Google. I purchased my original Pixel from Verizon and sent back to Google a Verizon Pixel with a locked bootloader (from 7.1.1 patch). Few questions....
1. Am I receiving a Google pixel XL with an unlocked bootloader?
I have read that I can unlock the bootloader and successfully root BEFORE I set up wifi and put the SIM card in... So
2. Will the device ship with 7.1.1 (Verizon), ending any chance of me unlocking the bootloader?
3. If the device ships with 7.1, can I prevent the update being installed in the background?
I put a screenshot with the email from google about the replacement device below.
Click to expand...
Click to collapse
1a. It says Verizon but you won't really know til you get it.
1b. You can only do that if the phone comes with 7.1 to avoid it updating to 7.1.1
2. Verizon does seem to be updating some of the phones now and I would assume the refurbished will have a higher chance of it.
3. You can shut off automatic updates but it seems to ignore it at times, so you should unlock right away if you want to do anything in the future.
jjayzx said:
1a. It says Verizon but you won't really know til you get it.
1b. You can only do that if the phone comes with 7.1 to avoid it updating to 7.1.1
2. Verizon does seem to be updating some of the phones now and I would assume the refurbished will have a higher chance of it.
3. You can shut off automatic updates but it seems to ignore it at times, so you should unlock right away if you want to do anything in the future.
Click to expand...
Click to collapse
Excellent answers.
One more question though, I read that when you put in a Verizon sim card, that's what triggers the locking of the bootloader. So let's say I'm able to lock the bootloader, install TWRP, and SuperSU, and then I put in my sim card so I can actually use the phone, will putting in sim card have any affect on anything?
Splatlame said:
Excellent answers.
One more question though, I read that when you put in a Verizon sim card, that's what triggers the locking of the bootloader. So let's say I'm able to lock the bootloader, install TWRP, and SuperSU, and then I put in my sim card so I can actually use the phone, will putting in sim card have any affect on anything?
Click to expand...
Click to collapse
I have a Pixel XL that I purchased directly from Google and I use it on Verizon. Powering up the phone the first time with the Verizon SIM gave me a message that the phone was activated but it did not re-lock my bootloader. That was my experience. Originally it would only connect to 3G and not LTE. I had previously used it on Fi. I had to delete the data(NOT Factory Reset) from the Fi app(with the Fi SIM still installed) and then power down, switch SIM's, then power up to get full 4G LTE connection on Verizon. After I deleted that Fi app data and powered up with the Verizon SIM it selected the normal VZWINTERNET APN and worked fine. Hope this helps. Again though the Verizon SIM did not re-lock my bootloader. This isn't to say they won't try to re-lock it in the future with an update.
Splatlame said:
I read that when you put in a Verizon sim card, that's what triggers the locking of the bootloader.
Click to expand...
Click to collapse
Not true. I have a VZW Pixel on Project Fi. My bootloader can not be unlocked.
Now does unlocking the bootloader with 7.1 before the update kicks in a confirmed solution? Has this been tested? Or this is a theory?
And if this is a real way of doing it can someone link me to a thread with a verified procedure or help me out here.
I want to be 100% sure by the time the device comes in.
Splatlame said:
Now does unlocking the bootloader with 7.1 before the update kicks in a confirmed solution? Has this been tested? Or this is a theory?
And if this is a real way of doing it can someone link me to a thread with a verified procedure or help me out here.
I want to be 100% sure by the time the device comes in.
Click to expand...
Click to collapse
Here is what you need if it is on 7.1
http://theroot.ninja/depixel8.html
TonikJDK said:
Here is what you need if it is on 7.1
http://theroot.ninja/depixel8.html
Click to expand...
Click to collapse
That method does not work anymore.
bradhoschar said:
That method does not work anymore.
Click to expand...
Click to collapse
He said if it's on 7.1
jjayzx said:
He said if it's on 7.1
Click to expand...
Click to collapse
You're right.
On a side note, if anybody has a TRULY defective device on Verizon and want a Google replacement, see my post here:
https://forum.xda-developers.com/pi...-buying-verizon-edition-t3581406/post71866381
Okay so I just got a replacement on my Verizon Google pixel and after everything was setup I noticed that in the developer options it gave me the option to unlock my Bootloader. I know the Verizon models are locked and after 7.1 the exploit was patched. I have all the Verizon bloatware so is this just a bug or is it possible? I turned off all automatic updates just in case so should I go ahead and try?
youtu.be/yYbhMk4fnLM
The0nlyboss said:
Okay so I just got a replacement on my Verizon Google pixel and after everything was setup I noticed that in the developer options it gave me the option to unlock my Bootloader. I know the Verizon models are locked and after 7.1 the exploit was patched. I have all the Verizon bloatware so is this just a bug or is it possible? I turned off all automatic updates just in case so should I go ahead and try?
youtu.be/yYbhMk4fnLM
Click to expand...
Click to collapse
If you want to try unlocking your bootloader go for it. But there's not much benefit to unlocking your bootloader unless you plan to root or flash a custom rom or custom kernel or something. Simply unlocking the bootloader but otherwise staying fully stock will not allow your phone to pass safety net so you won't be able to use Android Pay. There have been a few other posts from Verizon customers where they got phones with the option to unlock the bootloader enabled so you probably just got lucky.
The0nlyboss said:
Okay so I just got a replacement on my Verizon Google pixel and after everything was setup I noticed that in the developer options it gave me the option to unlock my Bootloader. I know the Verizon models are locked and after 7.1 the exploit was patched. I have all the Verizon bloatware so is this just a bug or is it possible? I turned off all automatic updates just in case so should I go ahead and try?
youtu.be/yYbhMk4fnLM
Click to expand...
Click to collapse
If it was shipped from Carol Stream, Illinois and if you pop in your SIM and the Verizon website calls it a non-VZW phone., then you got a Google Edition. Since OEM unlocking is not grayed out on yours, it's almost for certain a Google Edition. Same happened to me, the bloatware came when the Verizon SIM was inserted.
I agree with the above jhs39 post, though, only do it if you have a reason. I wanted the Pure Nexus ROM and ViPER4Android so I did it.
jhs39 said:
If you want to try unlocking your bootloader go for it. But there's not much benefit to unlocking your bootloader unless you plan to root or flash a custom rom or custom kernel or something. Simply unlocking the bootloader but otherwise staying fully stock will not allow your phone to pass safety net so you won't be able to use Android Pay. There have been a few other posts from Verizon customers where they got phones with the option to unlock the bootloader enabled so you probably just got lucky.
Click to expand...
Click to collapse
I don't have the need for it unlocked now but is it possible that an update can remove the option as I do want to flash a rom in the future.
3aucla1r3 said:
If it was shipped from Carol Stream, Illinois and if you pop in your SIM and the Verizon website calls it a non-VZW phone., then you got a Google Edition. Since OEM unlocking is not grayed out on yours, it's almost for certain a Google Edition. Same happened to me, the bloatware came when the Verizon SIM was inserted.
I agree with the above jhs39 post, though, only do it if you have a reason. I wanted the Pure Nexus ROM and ViPER4Android so I did it.
Click to expand...
Click to collapse
Ah I see. It was shipped from that location and I checked the IMEI on Verizon's website and it says it's not capable for some reason so I'm guessing it's a GE.
The0nlyboss said:
Ah I see. It was shipped from that location and I checked the IMEI on Verizon's website and it says it's not capable for some reason so I'm guessing it's a GE.
Click to expand...
Click to collapse
Yeah but it really is capable, just put the SIM in
If you plan on flashing custom in the future then I would unlock now so you don't have to lose all you're data later. Rather wipe while it's new and doesn't have months of data on it.
You never know when you might get screwed over by an update and or want to flash back a version.
I say unlock to give yourself a few more exit strategies should anything go wrong and if you decide to root and rom at some point later you aren't gonna wipe your device.
If you want to pass safety net for android pay you just need to flash a custom kernel.
The0nlyboss said:
I don't have the need for it unlocked now but is it possible that an update can remove the option as I do want to flash a rom in the future.
Click to expand...
Click to collapse
That's true. But if you use Android Pay or any other apps that require safety net they will stop working unless you flash a custom kernel. If that doesn't matter to you then you should unlock the bootloader while you can.
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...
Is there any way to unlock Pixel 2 XL running android 11? I misses my custom rom adventures :crying:.
bluesaka111 said:
Is there any way to unlock Pixel 2 XL running android 11? I misses my custom rom adventures :crying:.
Click to expand...
Click to collapse
That largely depends on if you have a "google" or "verizon" variant device. If you can enable OEM unlocking in developer options, then you should be able to unlock the bootloader.
Badger50 said:
That largely depends on if you have a "google" or "verizon" variant device. If you can enable OEM unlocking in developer options, then you should be able to unlock the bootloader.
Click to expand...
Click to collapse
I bought unlocked model. Imei checking shows Verizon sim enabled. Will it ne difficult to unlock bootloader and flash custom roms?
sabbeer said:
I bought unlocked model. Imei checking shows Verizon sim enabled. Will it ne difficult to unlock bootloader and flash custom roms?
Click to expand...
Click to collapse
First, make sure that you can enable "OEM unlocking" in the developers options settings section. If you can, then unlocking the bootloader and installing roms is not that difficult provided you have a good understanding of how fastboot works:good:
Badger50 said:
That largely depends on if you have a "google" or "verizon" variant device. If you can enable OEM unlocking in developer options, then you should be able to unlock the bootloader.
Click to expand...
Click to collapse
Where i can see if is a "Google" or "Verizon" variant?
lucasm87 said:
Where i can see if is a "Google" or "Verizon" variant?
Click to expand...
Click to collapse
Go here and enter your IMEI: https://www.verizon.com/od/prepaid/bring-your-own-device/#/checkDevice
It will tell you if it's a Verizon device, or a "NON-VZW" device
Any workaround for Verizon variant running Android 11 or if it can be downgraded to Android 10?
mnsiw said:
Any workaround for Verizon variant running Android 11 or if it can be downgraded to Android 10?
Click to expand...
Click to collapse
Nope, thats why you dont buy devices from carriers
3mutts said:
Nope, thats why you dont buy devices from carriers
Click to expand...
Click to collapse
Yeah, you are right it's running pretty well on stock, no problem, thanks
My phone is not a Verizon variant (NON-VZW), however it was bought from Verizon and cannot be unlocked. Is there any way around that? (Since Verizon says and several other IMEI checkers don't say it's a Verizon only variant).
davis the droid said:
My phone is not a Verizon variant (NON-VZW), however it was bought from Verizon and cannot be unlocked. Is there any way around that? (Since Verizon says and several other IMEI checkers don't say it's a Verizon only variant).
Click to expand...
Click to collapse
For me, it's kinda difficult to identify now as there is no app or setting from Verizon on it, tired checking it on Verizon but their IMEI checking page is down. If yours is non Verizon, unlock oem shouldn't be grayed out by default. I'm not expert on it thoug.
I bought a NON-VZW phone and enabled OEM unlocking, but after I put my Verizon SIM and an update happened, it got grayed out before I could unlock the bootloader. Is there any way to put it back on older software? It is still marked as NON-VZW in the IMEI thing.
kercre123 said:
I bought a NON-VZW phone and enabled OEM unlocking, but after I put my Verizon SIM and an update happened, it got grayed out before I could unlock the bootloader. Is there any way to put it back on older software? It is still marked as NON-VZW in the IMEI thing.
Click to expand...
Click to collapse
Maybe try taking the SIM card out, factory resetting and then see if you can enabled OEM unlocking and USB debugging. If so then unlock the bootloader before putting the SIM back in. Won't put you back on an older software but may allow you to unlock the bootloader.