Related
Now that the Verizon version is unlocked, is it possible to install the stock Google firmware onto the Verizon model (and subsequently get regular updates from Google, not Verizon)?
The updates still come from Google, regardless of where you bought the device. In fact, if you had a google store version of the pixel witha verizon sim, you would still get the X build as it has a different radio tuned for VZW.
Flashed the google images after unlocking the bootloader and after a few min the verizon build ended up being an update. So far, there is not way to avoid the verizon build unless you are rooted ...
Jalh said:
Flashed the google images after unlocking the bootloader and after a few min the verizon build ended up being an update. So far, there is not way to avoid the verizon build unless you are rooted ...
Click to expand...
Click to collapse
The only difference between the V and X builds are the radio.
So they must identify by Imei, which is which.
death2all110 said:
The only difference between the V and X builds are the radio.
Click to expand...
Click to collapse
In the bootloader thread there was speculation about how they tie each image for which phone. Some speculated about phones being recognized for their IMEI, SIM,CID, etc etc etc but nothing conclusive. The other day I met a person who got the phone from the google play store and have verizon but his latest build remains NDE63V, not NDE63X. Quiet honestly, I'm skeptical as of which is really the difference.
Jalh said:
In the bootloader thread there was speculation about how they tie each image for which phone. Some speculated about phones being recognized for their IMEI, SIM,CID, etc etc etc but nothing conclusive. The other day I met a person who got the phone from the google play store and have verizon but his latest build remains NDE63V, not NDE63X. Quiet honestly, I'm skeptical as of which is really the difference.
Click to expand...
Click to collapse
That doesn't surprise me, It took a week before I got the update. Its a staged rollout, just like any other OTA is.
The question is mine too, I am going to buy a verizon one that the bootloader can not unlock, now we know uts possible to unlockit, I would like to know if possible to flash google play stock on verizon?
Sent from my Nexus 6 using Tapatalk
biijan said:
The question is mine too, I am going to buy a verizon one that the bootloader can not unlock, now we know uts possible to unlockit, I would like to know if possible to flash google play stock on verizon?
Click to expand...
Click to collapse
If you can unlock it, yes. But if it comes with 7.1.1 or you let it update to 7.1.1 before you unlock it you are done. It will be locked without a way to unlock it.
Sent from my Pixel XL using XDA Labs
biijan said:
The question is mine too, I am going to buy a verizon one that the bootloader can not unlock, now we know uts possible to unlockit, I would like to know if possible to flash google play stock on verizon?
Click to expand...
Click to collapse
They are the same phone with the same software. There's nothing to flash
biijan said:
The question is mine too, I am going to buy a verizon one that the bootloader can not unlock, now we know uts possible to unlockit, I would like to know if possible to flash google play stock on verizon?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Verizon phones:
If it has 7.1.0 then you can unlock the bootloader.
If it has 7.1.1 then you cannot unlock the bootloader.
If you cannot unlock the bootloader then you cannot flash older firmware to circumvent the bootloader lock.
If you want to flash ROM's then do not buy a Verizon phone with 7.1.1 already on it.
CZ Eddie said:
Verizon phones:
If it has 7.1.0 then you can unlock the bootloader.
If it has 7.1.1 then you cannot unlock the bootloader.
If you cannot unlock the bootloader then you cannot flash older firmware to circumvent the bootloader lock.
If you want to flash ROM's then do not buy a Verizon phone with 7.1.1 already on it.
Click to expand...
Click to collapse
That version is 7.1.0, so
Let me know please, If I flash with google play stock, then mine will be like google play pixels? And it will be updates like them? And can unlock bootloader even after updates?
Thanks
Sent from my Nexus 6 using Tapatalk
biijan said:
That version is 7.1.0, so
Let me know please, If I flash with google play stock, then mine will be like google play pixels? And it will be updates like them? And can unlock bootloader even after updates?
Thanks
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Unlock your bootloader right away, before you take any 7.1.1 updates.
Then in the future before taking updates, research on XDA first to find out if it causes any problems.
biijan said:
That version is 7.1.0, so
Let me know please, If I flash with google play stock, then mine will be like google play pixels? And it will be updates like them? And can unlock bootloader even after updates?
Thanks
Click to expand...
Click to collapse
If you update before you unlock you will not be able to unlock. Don't matter where you get it from. VZ and Google's update are the same. The google update our full flash to 7.1.1 will lock you. Probably for good.
So if I unlock my bootloader, in 7.1.0 It'll maintain the bootloader unlock atleast in 7.1.1? It'll still allow OTA updates? On the fence on what I want to do with the Pixel but would rather dePixel8 it while i have the chance.
steber04 said:
So if I unlock my bootloader, in 7.1.0 It'll maintain the bootloader unlock atleast in 7.1.1? It'll still allow OTA updates? On the fence on what I want to do with the Pixel but would rather dePixel8 it while i have the chance.
Click to expand...
Click to collapse
My PixelXL came with NDE63P. I used depixel8 to unlock it. After that, it has taken 7.1-NDE63V, 7.1-NDE63X, and 7.11-NMF26O updates through Verizon without relocking the bootloader. I have messed up the phone several times and easily flashed the factory image to fix up each time. Instructions here in the xda PixelXL Forum are helpful. Custom recovery, kernel, or root will stop OTAs from installing.
Whatever you do, be sure to unlock it before taking updates.
Is it possible to overwrite the Verizon/EE bootloader once it is unlocked? So that the bootloader can be relocked and unlocked at will post updating to 7.1.1?
Gold Rusty said:
Is it possible to overwrite the Verizon/EE bootloader once it is unlocked? So that the bootloader can be relocked and unlocked at will post updating to 7.1.1?
Click to expand...
Click to collapse
Bootloader is the same. The unlockable "feature" appears to be IMEI related. Sets a flag, apparently...
cam30era said:
Bootloader is the same. The unlockable "feature" appears to be IMEI related. Sets a flag, apparently...
Click to expand...
Click to collapse
Great, thanks for clearing that up. Seems best to stay clear of Verizon/EE models if I want to be able to unlock and lock at will.
---------- Post added at 12:52 PM ---------- Previous post was at 12:46 PM ----------
Having said that, having to wipe the user data with each unlock makes it pointless relocking it as I want it mainly for app data backups.
Gold Rusty said:
Great, thanks for clearing that up. Seems best to stay clear of Verizon/EE models if I want to be able to unlock and lock at will.
---------- Post added at 12:52 PM ---------- Previous post was at 12:46 PM ----------
Having said that, having to wipe the user data with each unlock makes it pointless relocking it as I want it mainly for app data backups.
Click to expand...
Click to collapse
Don't relock, we have seen lots of people brick phones that way. If you are trying to pass safteynet then flash a kernel that bypasses it.
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.
So I recently got my hand on a pixel 2 xl without the operating system.
I know this is an issue happened to some devices and the best way is to send it back to Google for a replacement.
However neither do I have the box and receive with me nor I am living in the official launch area. So there is no easy way for a replacement from Google. (I can't even post question at there official pixel user forum)
Therefore I really would love to know if I can indeed install the official ROM with tool like this one? https://forum.xda-developers.com/pixel-2-xl/development/tool-tool-one-driversunlocktwrpfactory-t3730226
And hopefully won't wasted a good device.
oliverfongftw said:
So I recently got my hand on a pixel 2 xl without the operating system.
I know this is an issue happened to some devices and the best way is to send it back to Google for a replacement.
However neither do I have the box and receive with me nor I am living in the official launch area. So there is no easy way for a replacement from Google. (I can't even post question at there official pixel user forum)
Therefore I really would love to know if I can indeed install the official ROM with tool like this one? https://forum.xda-developers.com/pi...ol-tool-one-driversunlocktwrpfactory-t3730226
And hopefully won't wasted a good device.
Click to expand...
Click to collapse
Did you have OEM Unlocking checked in Developer options before it happened? If yes you can flash factory images
If you have the stock recovery and can boot into it you can adb sideload the most recent ota zip.
Sent from my Pixel 2 XL using XDA-Developers Legacy app
ram4ufriends said:
Did you have OEM Unlocking checked in Developer options before it happened? If yes you can flash factory images
Click to expand...
Click to collapse
Thanks for the answering guys, however I think it is one of the machine that Google ships with a OS in it... so I don't think OEM unlocking is enabled nor the recovery is working.
oliverfongftw said:
Thanks for the answering guys, however I think it is one of the machine that Google ships with a OS in it... so I don't think OEM unlocking is enabled nor the recovery is working.
Click to expand...
Click to collapse
You can get the bootloader lock status simply by booting into the bootloader. Locked or unlocked? You don't "think" it has a working recovery is not good enough to help you. If it does have a stable recovery, you can flash the OTA. If it does not and the bootloader is locked you are S.O.L. and the phone is dead. Follow this video and let us know.
oliverfongftw said:
Thanks for the answering guys, however I think it is one of the machine that Google ships with a OS in it... so I don't think OEM unlocking is enabled nor the recovery is working.
Click to expand...
Click to collapse
If you can hold down volume and hit power to get into bootloader and choose Recovery, you can fix this phone.
Go here: read instructions at top. You will be booting to bootloader, then to recovery, then choose Apply Update from ADB.
Then give adb OTA command as described. Don't skip or modify any step.
https://developers.google.com/android/ota
I am in this exact same situation. Did you ever figure it out? Or did anyone figure it out?
Got this exact problem with a locked bootloader and no recovery, any solution?
0x0null said:
Got this exact problem with a locked bootloader and no recovery, any solution?
Click to expand...
Click to collapse
How did you lose the recovery with a locked bootloader?
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
How did you lose the recovery with a locked bootloader?
Click to expand...
Click to collapse
Got it that way thinking i could use recovery to recover the phone
0x0null said:
Got it that way thinking i could use recovery to recover the phone
Click to expand...
Click to collapse
It came without a recovery.
Just use deuce script to flash the factory image guys. That's what I did when I got the no os message. Mines started when I ignorantly thought I had to relock bootloader before flashing stock.
mookiexl said:
Just use deuce script to flash the factory image guys. That's what I did when I got the no os message. Mines started when I ignorantly thought I had to relock bootloader before flashing stock.
Click to expand...
Click to collapse
Locked bootloader wont let me use the script.
If your bootloader is locked with no way to unlock it, and with no working recovery, you're screwed. The device needs to be sent to Google to fix, which is rather problematic when the device is in a country where it wasn't sold.
Strephon Alkhalikoi said:
If your bootloader is locked with no way to unlock it, and with no working recovery, you're screwed. The device needs to be sent to Google to fix, which is rather problematic when the device is in a country where it wasn't sold.
Click to expand...
Click to collapse
Yea, your on point. Only edl firehose may save me
0x0null said:
Locked bootloader wont let me use the script.
Click to expand...
Click to collapse
The script unlocks the bootloader and flashes firmware. Did you try or just assumed it wouldn't work?
mookiexl said:
The script unlocks the bootloader and flashes firmware. Did you try or just assumed it wouldn't work?
Click to expand...
Click to collapse
It Unlocks only if 'oem unlock' is engaged from the booted system.
0x0null said:
It Unlocks only if 'oem unlock' is engaged from the booted system.
Click to expand...
Click to collapse
Which is exactly why it should never be in the locked position...
Sent from my Pixel 2 XL using XDA Labs
0x0null said:
Yea, your on point. Only edl firehose may save me
Click to expand...
Click to collapse
and save me to. I try to find firhose for my pixel 2xl but I didn't find it. Hope someone can provide QFIL Firmware to save as.
Sent from my MI 9 using Tapatalk
0x0null said:
It Unlocks only if 'oem unlock' is engaged from the booted system.
Click to expand...
Click to collapse
Did you try? I used it with no 0S installed so oem unlock couldnt have been engaged.
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
I have this issue on the unlocked version running .30. Anyone else running the XL experienced this?
If you got it from Verizon it's locked you can not unlock the bootloader... If you got it from Google maybe it's a mistake you need to call them...
mostyle said:
I have this issue on the unlocked version running .30. Anyone else running the XL experienced this?
Click to expand...
Click to collapse
I had this issue at first. I had to do a factory reset after putting in my sim card. See if either or both of those work.
Sent from my crosshatch using XDA Labs
If your phone is unlocked, please leave it greyed out and spend the time with your kids or call your mother. Time better spent... Unless your OCD, it will bug crap out of you, [emoji23] [emoji23] [emoji23]. Phone is unlocked, you won't unlock it more, no?
Sent from my Pixel 3 XL using Tapatalk
I think he is referring to OEM unlock, that slider not being accessible is most def a serious problem.
krabman said:
I think he is referring to OEM unlock, that slider not being accessible is most def a serious problem.
Click to expand...
Click to collapse
Why? His phone is unlocked. Am I missing something?
Unless, he is referring to a non-vzw as unlocked (to a carrier?) and he can't unlock the bootloader cuz it's greyed out..? If so my bad and the answer posted already worked for me too.
Sent from my Pixel 3 XL using Tapatalk
Which unlock slider do you imagine he would be referring to when there is only the one? Lol Ya screwed up man. And no, I'm not busting your balls. It happens, done it myself.
ridobe said:
I had this issue at first. I had to do a factory reset after putting in my sim card. See if either or both of those work.
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
Done several resets and set up with and without SIM. Still Grayed out.
MArtyChubbs said:
Why? His phone is unlocked. Am I missing something?
Unless, he is referring to a non-vzw as unlocked (to a carrier?) and he can't unlock the bootloader cuz it's greyed out..? If so my bad and the answer posted already worked for me too.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Correct... Sorry, I should have clarified. It is Play Store purchased, non-VZW, non-project FI device running on AT&T.
This isn't my first rodeo so I knew what should have happened (I have 6p, Pixel 1 and have been running customs long before that) when I fired it up. It just didn't behave as expected so I was polling to see if others had a similar experience.
Sorry for the confusion... I shoulda been more explanatory in the OP.
Several non-xl users have said they experienced the issue (posted there as well) so I'm thinking it isn't device specific but rather an OS issue. Found Google support threads that reference the exact same described issue that was resolved by an OS hotfix. We'll see. RMA arrives tomorrow.
mostyle said:
Done several resets and set up with and without SIM. Still Grayed out.
Correct... Sorry, I should have clarified. It is Play Store purchased, non-VZW, non-project FI device running on AT&T.
This isn't my first rodeo so I knew what should have happened (I have 6p, Pixel 1 and have been running customs long before that) when I fired it up. It just didn't behave as expected so I was polling to see if others had a similar experience.
Sorry for the confusion... I shoulda been more explanatory in the OP.
Several non-xl users have said they experienced the issue (posted there as well) so I'm thinking it isn't device specific but rather an OS issue. Found Google support threads that reference the exact same described issue that was resolved by an OS hotfix. We'll see. RMA arrives tomorrow.
Click to expand...
Click to collapse
Same here with a Verizon sim. I had the greyed out OEM and reflashed stock image or reset like you (can't remember cuz my brain is old) and then I was able to toggle it. Well, cool beans on the RMA!
If someone else has the problem, post here and maybe a fix can be documented.
MArtyChubbs said:
Same here with a Verizon sim. I had the greyed out OEM and reflashed stock image or reset like you (can't remember cuz my brain is old) and then I was able to toggle it. Well, cool beans on the RMA!
If someone else has the problem, post here and maybe a fix can be documented.
Click to expand...
Click to collapse
Wait... You have a VZW pixel 3( or xl) and you managed to bypass the OEM unlock? how?
XtazyMike said:
Wait... You have a VZW pixel 3( or xl) and you managed to bypass the OEM unlock? how?
Click to expand...
Click to collapse
I believe, "Verizon sim", are the key words there. I don't think he means he has a Verizon Pixel.
XtazyMike said:
Wait... You have a VZW pixel 3( or xl) and you managed to bypass the OEM unlock? how?
Click to expand...
Click to collapse
No, from Google but I put my VZW sim I got with my Pixel XL in my P3XL. Sorry, like the OP, we had a weird problem unlocking BL with it being greyed out.
Sent from my Pixel 3 XL using Tapatalk
MArtyChubbs said:
No, from Google but I put my VZW sim I got with my Pixel XL in my P3XL. Sorry, like the OP, we had a weird problem unlocking BL with it being greyed out.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Just to be clear, you didn't 'flash' anything originally, correct? Just a factory reset? Since the bootloader is locked, if you flashed something please share. I saw the or in your post. Just making sure that I read that correctly.
I think I wanna say I DID flash leaving the -w in the bat file.
Locked bootloader means you can't flash non stock images, no? You can srill upgrade the bootloader even if it's still locked, right? What I mean is, I can still use the fastboot images on a locked phone or can't I?
I erased the data partition at least and then the OEM unlock was not greyed out. But I am in the habit of fastbooting (that's what I ment by flash) with or without -w so I am pretty sure that is what I did. Maybe not, I dunno...
Sent from my Pixel 3 XL using Tapatalk
You can flash a factory image with a locked bootloader as long as it retains the signature, which would be broken the second it gets modified.
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
You can flash a factory image with a locked bootloader as long as it retains the signature, which would be broken the second it gets modified.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Thanks for the confirmation I felt like I was inventing a memory for a moment there.
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
You can flash a factory image with a locked bootloader as long as it retains the signature, which would be broken the second it gets modified.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Are you sure about that? I don't believe you can flash anything other than sideload an OTA with a locked bl. But I could be mistaken, just like to confirm.
bobby janow said:
Are you sure about that? I don't believe you can flash anything other than sideload an OTA with a locked bl. But I could be mistaken, just like to confirm.
Click to expand...
Click to collapse
This is correct. This is why you can't lock the bootloader while having non-stock firmware. You can't boot because it's "corrupt", you can't flash because you are BL locked and you can't boot to toggle "OEM unlocking".
Sent from my crosshatch using XDA Labs
ridobe said:
This is correct. This is why you can't lock the bootloader while having non-stock firmware. You can't boot because it's "corrupt", you can't flash because you are BL locked and you can't boot to toggle "OEM unlocking".
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
By firmware do you mean a ROM? Because if the rom is signed even if it's not Google's signature then you can lock the bootloader. All it looks for is that signature so it can perform checks to make sure that signature stays the same.
Sent from my Pixel 3 XL using Tapatalk
bobby janow said:
Are you sure about that? I don't believe you can flash anything other than sideload an OTA with a locked bl. But I could be mistaken, just like to confirm.
Click to expand...
Click to collapse
You are not mistaken. Just tried.