Related
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
newbienic said:
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
Click to expand...
Click to collapse
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Awesome! Thanks for the info... Really glad to know I can convert if need be. Thanks again!
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
newbienic said:
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
Click to expand...
Click to collapse
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
ITGuy11 said:
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
Click to expand...
Click to collapse
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
danaff37 said:
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
danaff37 said:
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Hypathetically, if I didn't want root or anything custom at all, do you think that relocking the bootloader could cause an issue while using the Stock Google image on a Verizon Pixel? I wish I had more knowledge on this, but I'm pretty in the dark on this stuff as of late... Thanks for your help!
Should be fine if all stock I think, just know that you may not be able to unlock later.
Sent from my Pixel using Tapatalk
newbienic said:
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
Click to expand...
Click to collapse
Contrary to what people are saying. You CAN relock your bootloader and then unlock it again later. However, keep in mind that at some point there will likely be an update that blocks the use of dePixel8 and you will no longer be able to unlock the bootloader unless someone writes another exploit.
I would like to find a way to permanently unlock VZW Pixels but until I get one from the Google Store to compare with my Verizon one I don't think I will make much progress.
Relocking your bootloader is as simple as running the "fastboot oem lock" command from the terminal window.
Lastly. If you want to relock the bootloader, make sure your phone is 100% stock image or you risk bricking the phone
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
b316kane said:
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
Click to expand...
Click to collapse
This is exactly what I did, and I am curious as well... We'll see next month I guess, but I'm guessing it will take the OTA just fine. My wife has a Pixel from the Google store, and mine is from Verizon. I've compared everything (including booloaders) since flashing the Google store Pixel image, and every informational detail is identical. Not sure if there is some other place hidden to me that might indicate a difference, but I'm thinking that Verizon's Pixel is only different in its official software image... And, that may be it. Please don't take my word for it, I'm no developer, and know very little about any of this, but in my comparisons, they are identical now since flashing Googles official (Non Verizon, Non European) image.
Sidenote, I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking. I think Verizon used Googles "Allow OEM Unlocking" software toggle in developer options as the only method to actually keep people from unlocking the bootloader (again speculative), and now that I'm on Googles image, that software "block" should no longer be present, so I should in theory, be free to lock/unlock the same as Pixels purchased from the Google store... Again, I've got no proof, or actual skill to back this up, but it's a theory I have, and if I end up locking my BL again, I'll post what I find...
newbienic said:
I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking.
Click to expand...
Click to collapse
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
alluringreality said:
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
Click to expand...
Click to collapse
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
newbienic said:
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
Click to expand...
Click to collapse
I forget where, but I saw written or implied that the "checking for updates" screen about third of way through initial setup of first boot uses WiFi AND sim carrier data to install Verizon custom restrictions and settings that among other effects make depixel8 required.
Even on "non Verizon phones" (which you are saying use the same build images byte to byte?)... You have to either use a SIM card or wifi and google account to allow the developer options to enable OEM unlock.
My theory: In other words, if you don't allow via SIM and a network wifi or data connect, for Verizon to mark your phone, or another carrier, then the phone can not be unlocked. So carrier models may indeed be differentiated from current factory images AFTER boot and setup.
There is a post in Q&A of someone trying to unlock bootloader without loading into the device, not having luck. This is why oem unlock toggle is so important and why people are bricking from locked bootloaders that won't unlock (so no wipe and factory images cannot be flashed.)
Another thing to consider: SIM network lock will not be flashed over.
Sent from my sailfish using XDA Labs
Hey, I have a OnePlus 3 so I have messed around a lot with my phone, today I saw a Google Pixel at sale for a pretty low price but the guy selling it says that the phone has a Google account on it from the previous owner but it doesn't have a security pattern pin or password to get into the phone, it just has swipe to unlock. He says he can't use the play store but he has downloaded apks directly and can use the phone with some limitations. My question is, I use an OnePlus 3 and in that situation I could unlock my bootloader and flash a different ROM and fully unlock it. Is that not possible on the Pixel? I can't just go into the developer settings, enable oem unlocking, boot into fastboot and unlock the bootloader and flash a different rom or factory reset it without triggering FRP? How does that work? Given the circumstances is there any way to factory reset or flash a different rom on that pixel without issues? Thanks!
Hello, the Verizon version of the Pixel has a locked bootloader and can NOT be unlocked, some people have bought a Verizon version but were lucky to get it with 7.1 which is the only version that can have the bootloader unlocked. If the Pixel is the unlocked version (Google Store) or Verizon version, it can be unlocked using different methods until it reaches the December 5th Security Patch, at that point there is only one method right now to bypass the frp for the December 5th patch - current patch.
If I understand correctly, the phone already has frp, you need to find out what version the pixel is and what security patch does it have.
The seller might of used dirty-c0ws method to install a home launcher and other apps but none of the google apps work and you can't add your google account to it until you completely remove frp.
droid4lif3 said:
Hello, the Verizon version of the Pixel has a locked bootloader and can NOT be unlocked, some people have bought a Verizon version but were lucky to get it with 7.1 which is the only version that can have the bootloader unlocked. If the Pixel is the unlocked version (Google Store) or Verizon version, it can be unlocked using different methods until it reaches the December 5th Security Patch, at that point there is only one method right now to bypass the frp for the December 5th patch - current patch.
If I understand correctly, the phone already has frp, you need to find out what version the pixel is and what security patch does it have.
The seller might of used dirty-c0ws method to install a home launcher and other apps but none of the google apps work and you can't add your google account to it until you completely remove frp.
Click to expand...
Click to collapse
It hasn't been reset yet, it's on 7.1.1 so I believe the security patch on it is later than December. I can't access developer options, enable oem unlocking and proceed with the steps to flash a custom ROM?
It's in May Security patch, but the phone isn't yet locked, the guy selling it has access to the phone, he just can't remove the Google account. Is there no way to enable OEM unlocking, open the bootloader, flash twrp and a different ROM? Does any of these steps require the Google account password? The device doesn't seem to have any pattern pin or password, just swipe up to unlock.
Your phone is in FRP state. You can use the phone with the above patch, just you can't get the Google service on it.
imGomez said:
Hey, I have a OnePlus 3 so I have messed around a lot with my phone, today I saw a Google Pixel at sale for a pretty low price but the guy selling it says that the phone has a Google account on it from the previous owner but it doesn't have a security pattern pin or password to get into the phone, <snip>
Click to expand...
Click to collapse
That's why it's such a low price. It's a bogus deal and you should just move on. Could be a lost or stolen device in which case one day it will be blacklisted and you are out of luck. Pay the extra money and buy a legit device.
bobby janow said:
That's why it's such a low price. It's a bogus deal and you should just move on. Could be a lost or stolen device in which case one day it will be blacklisted and you are out of luck. Pay the extra money and buy a legit device.
Click to expand...
Click to collapse
Yeah I figured, I didn't pull the trigger on it. I'll stick with my loyal oneplus 3. Thanks for the heads up tho
Hey everyone,
I bought a second hand Pixel phone and it came with the bootloader locked. I was wondering if I would be able to unlock it.
I have been reading a lot about that and I was able to check using the adb tool that my cid version is VZW_001 and I have the OEM unlock option (under the development menu) greyed out. I am currently using android 8.0 and I do not use Verizon since I live in Brazil.
In light of that, I have two more questions:
- Oreo does not have any specific build for verizon, right? I was only able to find the 'other carriers' image.
- Is it possible that I do not have the 'OEM unlock' option because I am using this new version of android that is only for those enrolled in the Beta program?
Regards,
--
Henrique
That's a Verizon version of Pixel, which means bootloader locked.
Edit: unless you have a brand new, never been activated one... https://forum.xda-developers.com/pixel/help/bootloader-unlock-verizon-pixels-t3616101
mngdew said:
That's a Verizon version of Pixel, which means bootloader locked.
Edit: unless you have a brand new, never been activated one... https://forum.xda-developers.com/pixel/help/bootloader-unlock-verizon-pixels-t3616101
Click to expand...
Click to collapse
I've read on this thread.
What I am curious about is whether you guys that have got a Pixel directly from google, and updated to this new release, have this 'OEM Unlocking' option available?
henrique.mageste said:
I've read on this thread.
What I am curious about is whether you guys that have got a Pixel directly from google, and updated to this new release, have this 'OEM Unlocking' option available?
Click to expand...
Click to collapse
I got my phone straight from google, have since received an Oreo OTA update, and have this option grayed out. However, underneath it says, "bootloader is already unlocked" (which it is). So that makes sense.
You probably have the Verizon version, which requires an exploit to unlock.
15xda said:
I got my phone straight from google, have since received an Oreo OTA update, and have this option grayed out. However, underneath it says, "bootloader is already unlocked" (which it is). So that makes sense.
You probably have the Verizon version, which requires an exploit to unlock.
Click to expand...
Click to collapse
Interesting, this means that I do have a Verizon phone. Hope we can find a exploit that bypass it. I would really like to root my phone. ; )
Thanks you all.
These may be stupid questions but I have tried everything I can think of.
I am on a Verizon pixel 2, locked bootloader, running the current release of android 9.
I am unable to toggle the "OEM Unlocking" option in developer settings
I followed this guide to enable the toggle but ADB/Fastboot still gives me the "Flashing Unlock is not allowed" message when i try to run "fastboot oem unlock" or "fastboot flashing unlock".
Ultimately I would like to be able to root my Pixel 2, but right now I would settle for being able to downgrade Google Play Services to version 12.6.85 because reasons. There does not appear to be a compatible APK for this version of play services and Android 9 on the Pixel 2 (that I have been able to find yet)
Is anyone aware of how I could do the following:
1. unlock my bootloader?
or
2. downgrade to any android 8 version?
or
3. downgrade google play services to 12.6.85 on Pixel 2 Android 9?
The guide you posted is for the original Pixel.
Verizon Pixel 2 has a locked bootloader, and Verizon has disallowed the option of unlocking.
Early in the year, a user here stumbled upon a few commands that would bootloader-unlock the vzw p2. However, any firmware past January (I think) has been updated to protect against this exploit. So you missed the window on that.
I don't think android allows downgrading while the bootloader is locked.
I'm not sure about downgrading play services, but you could easily get the desired .apk from apk-mirror, and attempt to install it. I'm guessing you're going to get an error. In that case, considering you don't have system r/w permission, I don't see any way you'd be able to downgrade play services.
So, short of someone coming along and finding another way to bypass vzw's restrictions, you're stuck on 9.
use skipsoft android toolkit.
bmw9651 said:
use skipsoft android toolkit.
Click to expand...
Click to collapse
That won't work. You can't downgrade to an earlier version, and if you've taken any updates past the January VZW variant, nothing can be done. Sorry....
I was able to wipe system and install 8.1.0 after bricking on 9 pie.
bmw9651 said:
I was able to wipe system and install 8.1.0 after bricking on 9 pie.
Click to expand...
Click to collapse
With a locked bootloader on a Verizon Pixel 2?
yes I wiped it and went back to 810. bootloader has been unlocked as well. use fastboot and adb....... code: fastboot flash lock_critical. to unlock BL.
use skipsoft tool kit to wipe and reinstall OS to 8.1.,0.
bmw9651 said:
yes I wiped it and went back to 810. bootloader has been unlocked as well. use fastboot and adb....... code: fastboot flash lock_critical. to unlock BL.
use skipsoft tool kit to wipe and reinstall OS to 8.1.,0.
Click to expand...
Click to collapse
What I'm getting at is that your bootloader was unlocked _before_ you did everything. OP doesn't have that luxury.
DuckRuckus said:
What I'm getting at is that your bootloader was unlocked _before_ you did everything. OP doesn't have that luxury.
Click to expand...
Click to collapse
Yeah he's full of it if he's saying otherwise. There is no way it would let you downgrade bootloaders in stock recovery.
Yes BL was unlocked before doing the change. I just rooted it with the skipsoft toolkit Magsik way. after trying others on it. with the skipsoft toolkit you can wipe it and go back to jan 2018 builds of you wish. there are many options on it to choose from.
---------- Post added at 05:22 PM ---------- Previous post was at 05:13 PM ----------
when i got my pixel 2 first thing I did was unlock boot-loader. fastboot flash lock_critical. is the command to do this . To the OP don't worry too much the pixel 3 is coming out soon. BUY it From the Google Store. you will be able to unlock BL and do as you please. DO NOT Buy from Verizon.
bmw9651 said:
Yes BL was unlocked before doing the change. I just rooted it with the skipsoft toolkit Magsik way. after trying others on it. with the skipsoft toolkit you can wipe it and go back to jan 2018 builds of you wish. there are many options on it to choose from.
---------- Post added at 05:22 PM ---------- Previous post was at 05:13 PM ----------
when i got my pixel 2 first thing I did was unlock boot-loader. fastboot flash lock_critical. is the command to do this . To the OP don't worry too much the pixel 3 is coming out soon. BUY it From the Google Store. you will be able to unlock BL and do as you please. DO NOT Buy from Verizon.
Click to expand...
Click to collapse
unless you need to get an RMA, in which case you get a device that cannot be unlocked, like mine for example.
crixley said:
unless you need to get an RMA, in which case you get a device that cannot be unlocked, like mine for example.
Click to expand...
Click to collapse
By that do you mean that you submitted a warranty claim to google? You must not have. I am a Project Fi customer so I never have to think about such things. But yeah, if you bought your pixel from the google website, hooked it up to Verizon service and THEN called Verizon customer service and requested a warranty replacement or an Insurance claim then yeah. In that case you probably would receive a device with a locked bootloader because that's all Verizon deals with as far as I know. I submitted a warranty claim to Project Fi and The device they sent me came with an unlocked bootloader. I think I would have thrown a fit if they had sent a locked one. I would have been on the phone with a Supervisor stating that "the unlocked bootloader feature was 100% the reason I chose to buy the phone directly from google!" I would not have left them alone until I got my way. lol
KirkH420 said:
By that do you mean that you submitted a warranty claim to google? You must not have. I am a Project Fi customer so I never have to think about such things. But yeah, if you bought your pixel from the google website, hooked it up to Verizon service and THEN called Verizon customer service and requested a warranty replacement or an Insurance claim then yeah. In that case you probably would receive a device with a locked bootloader because that's all Verizon deals with as far as I know. I submitted a warranty claim to Project Fi and The device they sent me came with an unlocked bootloader. I think I would have thrown a fit if they had sent a locked one. I would have been on the phone with a Supervisor stating that "the unlocked bootloader feature was 100% the reason I chose to buy the phone directly from google!" I would not have left them alone until I got my way. lol
Click to expand...
Click to collapse
Yes, as have many others. I'm from Canada, device was bought through google and RMA'd through google. Has nothing to do with Verizon, there are tons of threads about it.
Another alternative, albeit a bit more convoluted, would be to update your current device to the latest update. Back up your user data as best you can, then factory reset, put it on Swappa, and then use the proceeds to purchase a secondhand Google variant with identical specs as the original. At least that way you won't have to deal with any more bootloader shenanigans. If your device is still in good shape and you're savvy enough about it, you may be able to come close to break-even.
I just unlocked the bootloader on my shiny new Pixel 4 XL. It is the Verizon variant as it was purchased directly from Verizon themselves. I'm unsure whether this is a coincidence, whether Google is no longer offering cell phone service providers a locked bootloader option, or did I just get lucky. The steps I took are...
1: Removed the pre-installed sim card
2: Went through the set-up process via Wi-Fi
3: Immediately turned on Developer options
4: Turned on OEM Unlock
5: Used the "fastboot flashing unlock" command via ADB/Fastboot
Normally the OEM unlock option would be greyed out as it was on my original Pixel XL that I also bought through Verizon but was able to use DePixel to unlock, then flash the Google Factory Image, the bootloader. I was then able to re-lock the bootloader for security and mobile payment reasons while retaining the "OEM unlock" option in the developer settings. I will now attempt to do the same thing when Google releases the Factory Image for the Pixel 4 XL.
It also could be because I removed the sim card before the phone had the opportunity to activate.
I am interested whether anyone else has been able to do this.
BTW: Model# G020J
Kool19 said:
I just unlocked the bootloader on my shiny new Pixel 4 XL. It is the Verizon variant as it was purchased directly from Verizon themselves. I'm unsure whether this is a coincidence, whether Google is no longer offering cell phone service providers a locked bootloader option, or did I just get lucky. The steps I took are...
1: Removed the pre-installed sim card
2: Went through the set-up process via Wi-Fi
3: Immediately turned on Developer options
4: Turned on OEM Unlock
5: Used the "fastboot flashing unlock" command via ADB/Fastboot
Normally the OEM unlock option would be greyed out as it was on my original Pixel XL that I also bought through Verizon but was able to use DePixel to unlock, then flash the Google Factory Image, the bootloader. I was then able to re-lock the bootloader for security and mobile payment reasons while retaining the "OEM unlock" option in the developer settings. I will now attempt to do the same thing when Google releases the Factory Image for the Pixel 4 XL.
It also could be because I removed the sim card before the phone had the opportunity to activate.
I am interested whether anyone else has been able to do this.
BTW: Model# G020J
Click to expand...
Click to collapse
Did this just now on my AT&T Pixel 4 XL 128GB. Nada... Screw this; I'm returning this.
Kool19 said:
I just unlocked the bootloader on my shiny new Pixel 4 XL. It is the Verizon variant as it was purchased directly from Verizon themselves. I'm unsure whether this is a coincidence, whether Google is no longer offering cell phone service providers a locked bootloader option, or did I just get lucky. The steps I took are...
1: Removed the pre-installed sim card
2: Went through the set-up process via Wi-Fi
3: Immediately turned on Developer options
4: Turned on OEM Unlock
5: Used the "fastboot flashing unlock" command via ADB/Fastboot
Normally the OEM unlock option would be greyed out as it was on my original Pixel XL that I also bought through Verizon but was able to use DePixel to unlock, then flash the Google Factory Image, the bootloader. I was then able to re-lock the bootloader for security and mobile payment reasons while retaining the "OEM unlock" option in the developer settings. I will now attempt to do the same thing when Google releases the Factory Image for the Pixel 4 XL.
It also could be because I removed the sim card before the phone had the opportunity to activate.
I am interested whether anyone else has been able to do this.
BTW: Model# G020J
Click to expand...
Click to collapse
What is DePixel?
DePixel8
Who-Lep said:
What is DePixel?
Click to expand...
Click to collapse
It was software that would unlock the bootloader of the Google Pixel and Google Pixel XL that had the bootloader locked to Verizon. The catch was it only worked on Android 7.1.0 I believe. It was patched shortly after so if you updated your device, no luck.
KillerBytes said:
Did this just now on my AT&T Pixel 4 XL 128GB. Nada... Screw this; I'm returning this.
Click to expand...
Click to collapse
Sorry to hear that. Was your model number different. I am truly interested in why I was able to do this so easily.
Kool19 said:
Sorry to hear that. Was your model number different. I am truly interested in why I was able to do this so easily.
Click to expand...
Click to collapse
Model number is G020J as well.
got mine from vzw and was able to unlock bootloader as well, removed sim before turning on, set up phone on wifi and check oem unlocking in dev settings before popping in sim card
I am hoping I am in the same boat. I couldn't pass up getting 450 for a pixel xl so I bought the verizon variant it's coming Monday. I have seen where this has worked in the past with the pixel 2. Here is hoping the toggle gets grayed out when it's sees your on verizon's network. I plan on removing sim booting up and getting to developer options taking the least path of resistance and then trying to unlock. If I am successful I will report back.
Well I'm beat my is locked
bigv5150 said:
Well I'm beat my is locked
Click to expand...
Click to collapse
I'm waiting on a 128 GB white from Verizon, but I tried it on my dad's black 64 GB. His is locked as well unfortunately.