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.
Related
Since I have enrolled my Pixel XL in Android beta program, I have received Oreo 8.1 update OTA last night. After the update, OEM unlock in developer options does not work. Anyone have the same issue ? Thanks
Fine here
netma2k said:
Since I have enrolled my Pixel XL in Android beta program, I have received Oreo 8.1 update OTA last night. After the update, OEM unlock in developer options does not work. Anyone have the same issue ? Thanks
Click to expand...
Click to collapse
Same problem the button is gray and says bootloader already unlocked.
That is normal if you are already unlocked, and it was like that before 8.1. It won't un-gray until you issue the fastboot command to relock it. It stops you from sliding while unlocked and creating a situation where you are bricked.
TonikJDK said:
That is normal if you are already unlocked, and it was like that before 8.1. It won't un-gray until you issue the fastboot command to relock it. It stops you from sliding while unlocked and creating a situation where you are bricked.
Click to expand...
Click to collapse
But I never unlocked my boot loader and still it appears to be grayed out. Thanks for your reply.
netma2k said:
But I never unlocked my boot loader and still it appears to be grayed out. Thanks for your reply.
Click to expand...
Click to collapse
Is your device a "Google phone" or is it through a carrier?
DR3W5K1 said:
Is your device a "Google phone" or is it through a carrier?
Click to expand...
Click to collapse
Mine is an unlocked phone purchased from Google Store and never buy phones from Carrier. Thanks for asking
netma2k said:
Mine is an unlocked phone purchased from Google Store and never buy phones from Carrier. Thanks for asking
Click to expand...
Click to collapse
Is it stuck in the locked position or the unlocked position?
Stuck in locked position
TonikJDK said:
Is it stuck in the locked position or the unlocked position?
Click to expand...
Click to collapse
Stuck in locked position
netma2k said:
Stuck in locked position
Click to expand...
Click to collapse
I would unenroll, which will wipe your phone and then hit the slider and leave it there. It might be a bug that will be fixed later but I wouldn't chance it if I wanted to unlock later on.
netma2k said:
Stuck in locked position
Click to expand...
Click to collapse
That is very strange
You are using beta software.
Google doesn't want you to lock the bootloader when using beta software.
Go back to 8.0 and see what happens.
Sent from my Pixel C using Tapatalk
Then, could I downgrade safely to Android 6??
Navalon said:
Then, could I downgrade safely to Android 6??
Click to expand...
Click to collapse
If you can pull it off, let us know!
Sent from my Pixel C using Tapatalk
pkelly517 said:
If you can pull it off, let us know!
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
If the bootloader is unlock, the rollback protection will be desactivated. Not?
I can confirm on mine that OEM unlock is also grayed out on 8.1 DP. Also grayed out in the screenshots on Android Police.
Sent from my Pixel using Tapatalk
Navalon said:
If the bootloader is unlock, the rollback protection will be desactivated. Not?
Click to expand...
Click to collapse
I think the joke was, this device never came with Marshmallow. They were saying if you can get Marshmallow to run on this, then let us know.
Unlocked rooted 8.0 not enrolled in beta.
My unlock button is Not grayed out. Wish it was as it would be easy to accidentally tick the button. Maybe 8.1 fixed this?
Born<ICs said:
Unlocked rooted 8.0 not enrolled in beta.
My unlock button is Not grayed out. Wish it was as it would be easy to accidentally tick the button. Maybe 8.1 fixed this?
Click to expand...
Click to collapse
An accidental tick won't hurt you, you still have to hit it with fastboot and issue the command.
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
So I just got my Google pixel 3 XL straight from Google. First thing I wanted to do was root my phone. I've tried everything from restarting device and updating my phone to the latest updated ( I was told that it needs to update before OEM unlock is enabled) but still it's greyed out. Does anyone know what's going on ? I spent a lot of money to finally get an unlocked version to be able to root it.
I'm using At&t as my network.
If anyone has any input, I'd appreciate it. Thank you.
NVM saw another thread about this. Ignore.
Factory reset, tried that?
Sent from my Pixel 3 XL using Tapatalk
MArtyChubbs said:
Factory reset, tried that?
Click to expand...
Click to collapse
Yes, 4 times ! Lol
GunToYoMouth123 said:
Yes, 4 times ! Lol
Click to expand...
Click to collapse
A factory reset from setting won't work. If you haven't flashed the factory images with the wipe flag enabled, do that.
source: same thing happened to me.
Sent from my crosshatch using XDA Labs
Wondering if you have found a fix for this. I just received my RMA and also cannot unlock due to greyed out OEM Unlock. My first 3XL unlocked fine. Inserted Verizon sim, set up phone and then unlocked in Dev options. Currently Google support say there is no fix and they are looking into it. Just curious where you are in this...
ridobe said:
A factory reset from setting won't work. If you haven't flashed the factory images with the wipe flag enabled, do that.
source: same thing happened to me.
Click to expand...
Click to collapse
Not possible to flash factory image without unlocked bootloader
Larger thread going on here for the same issue (Lol dnd't read 2nd post)
https://forum.xda-developers.com/pixel-3-xl/help/oem-unlocking-grayed-t3860023
https://issuetracker.google.com/issues/119628469 Please star and contribute to the thread here
OEM Unlocking Greyed Out- Pixel 3XL
I purchased a brand new Pixel 3 XL from the Google Store. In the Developer's Option, it shows that the "OEM unlocking" is greyed out. I purchased an unlocked phone. Do not understand why I am not able to unlock it. Your assistance is much appreciated.
I do not have a sim card in it. Don't see the point why I am unable to unlock it.
Bootloader version: b1c1-0.1-5004167
Product revision: crosshatch MP1.0(ROW)
Any assistance is much appreciated.
See this thread..... https://forum.xda-developers.com/pixel-3-xl/help/oem-unlocking-grayed-t3860023/page24
Unfortunately you are not alone with this issue
Has anyone tried just swapping the motherboard with an unlocked one?
Has anyone tried just swapping the motherboard with an unlocked one?
I hate to beat a dead horse here. But in my Verizon 3xl I can switch OEM locking back and forth. It even gives me a warning about unlocking it. I've never tried anything past this point cause I don't want to rework my phone from the begining. Can everyone do this ?! Why isn't mine greyed out ?
MilkMan302 said:
Wondering if you have found a fix for this. I just received my RMA and also cannot unlock due to greyed out OEM Unlock. My first 3XL unlocked fine. Inserted Verizon sim, set up phone and then unlocked in Dev options. Currently Google support say there is no fix and they are looking into it. Just curious where you are in this...
Click to expand...
Click to collapse
Verizon blocks bootloader unlocking
tombaldwin6 said:
I hate to beat a dead horse here. But in my Verizon 3xl I can switch OEM locking back and forth. It even gives me a warning about unlocking it. I've never tried anything past this point cause I don't want to rework my phone from the begining. Can everyone do this ?! Why isn't mine greyed out ?
Click to expand...
Click to collapse
Does it work? Did you do anything specific?
Hi all, I recently bought an "unlocked" google pixel 2 XL on ebay from a generally trusted seller but I have been super frustrated with issues I'm having with trying to unlock my bootloader and enabling OEM unlocking. The button literally remains grey and I have tried many things to get it to toggle but it won't (sim card, terminal commands, resetting multiple times). I'm also doing this on a mac since I don't have a pc. The command tells me it is not allowed.
It is Android 9. I found out from another user that it is because it was originally Verizon. I have looked through a lot of the helpful xda forums and threads but I haven't found one that lays out a method for unlocking Verizon Google Pixel 2 XL.
Is there a simpler way to unlock it, does anyone know? Could I go straight to Verizon and ask them to unlock it for me? I'm super frustrated or am I SOL and should return the phone? This is my first time using an android so I would appreciate any help.
Thank you very much in advance.
Since nobody else is replying. I think your sol if it is indeed a Verizon phone. There's a discussion on xda about it.
Sent from my Pixel 2 XL using Tapatalk
Nothing you can do. Just install the 11 beta and enjoy life.
Think of it this way. Since root isn't possible for you passing Safetynet will never be a problem.
I have the same issue. What I've found is OEM unlock isn't available because your pixel was originally on Verizon
Mine is verizon i just received the QQA3 update oem unlocked was available in a hurry i unlocked it without hesitation
nobreak1970 said:
Nothing you can do. Just install the 11 beta and enjoy life.
Click to expand...
Click to collapse
Hm, if you load dsu, from there it's still locked right? if it's possible... i've seen in dev options, but never tried tho... previously it required unlocked boot, but since it's in dev options.....
tfat1000 said:
Mine is verizon i just received the QQA3 update oem unlocked was available in a hurry i unlocked it without hesitation
Click to expand...
Click to collapse
You got lucky. Most people on here were disappointed.
Hexlay said:
Hm, if you load dsu, from there it's still locked right? if it's possible... i've seen in dev options, but never tried tho... previously it required unlocked boot, but since it's in dev options.....
Click to expand...
Click to collapse
It's not possible as the bootloader will still be locked. Its presence in developer options doesn't change that.
The only way to get past the bootloader lock, if you're not one of the lucky ones like @tfat, is to install a ROM using the device's emergency mode. The problem is getting a firmware package that uses that mode. A regular ROM download won't cut it.
Strephon Alkhalikoi said:
You got lucky. Most people on here were disappointed.
It's not possible as the bootloader will still be locked. Its presence in developer options doesn't change that.
The only way to get past the bootloader lock, if you're not one of the lucky ones like @tfat, is to install a ROM using the device's emergency mode. The problem is getting a firmware package that uses that mode. A regular ROM download won't cut it.
Click to expand...
Click to collapse
Yes, boot will still be locked, but since GSI image is basically a stock version of OS, it would not come with Verizon services and maybe toggle will be unlocked?
Hexlay said:
Yes, boot will still be locked, but since GSI image is basically a stock version of OS, it would not come with Verizon services and maybe toggle will be unlocked?
Click to expand...
Click to collapse
It won't work as you must have an unlocked bootloader to even install the GSI image. There is a 50+ page thread detailing attempts to unlock the Verizon device. No one on that thread succeeded. If what you proposed did work that thread wouldn't exist as yours is one of the easiest solutions.
Unless you can unlock the bootloader or somehow get a tech center restore image using emergency mode you're dead in the water. And don't think you can simply guess the decryption key either. To find the key would currently require spending an amount of time greater than the current age of the universe.
EDIT: Finally, check out the factory images page for our device. Notice how for the most part there are no images specifically for Verizon? That's because the device uses a different method to identify itself as a Verizon device. It's almost a certainty that the IMEI is part of it.
https://www.xda-developers.com/how-to-unlock-bootloader-verizon-google-pixel-xl-running-android-10/
我從使用 Tapatalk 的 Pixel 2 XL 發送
hsiehboss said:
https://www.xda-developers.com/how-to-unlock-bootloader-verizon-google-pixel-xl-running-android-10/
我從使用 Tapatalk 的 Pixel 2 XL 發送
Click to expand...
Click to collapse
Ok...well that link is for the OG Pixel/XL. NOT our 2xl.
nobreak1970 said:
Ok...well that link is for the OG Pixel/XL. NOT our 2xl.
Click to expand...
Click to collapse
Clearly English isn't his first language, but how difficult can it be to distinguish between the OG Pixel and the Pixel 2 XL?
hsiehboss said:
https://www.xda-developers.com/how-to-unlock-bootloader-verizon-google-pixel-xl-running-android-10/
我從使用 Tapatalk 的 Pixel 2 XL 發送
Click to expand...
Click to collapse
This method only works on the Pixel 1. You can get to the point where you can toggle the "OEM Unlocking" switch (in my testing its always defaulted to on once togglable), but running "fastboot flashing unlock" fails.
According to the person who found this method out, it's because the Pixel 2 has an on-board security chip that deals with OEM unlocking, with the 1st gen Pixel doesn't have :/
It's probably a very safe bet, and sad to say, that since no one found a way to unlock the Verizon Pixel 2 XLs in it's 2.5 years of existence, there will be little if any work put into finding a way at the 3 year mark with 2 (maybe 3) newer models on the market since the 2 XL became available.