I have not been able to find this answer any where. A little while back I got my replacement Google Pixel XL through Asurion on my Verizon warranty due to burn in. When I received the phone I noticed the Verizon account webpage showed it as a blank picture instead of the picture of the Pixel like it should. I am wanting to unlock my bootloader, of course I am on 7.1.1, but in developer options the oem unlock button is able to be switched on instead of being greyed out, which makes me curious if this is a Google Play version and I still have some luck on my side. I have no idea where to check if this is indeed the Google Play version of the phone though. Where can I check? From all the information I have seen, if you have a Verizon version of the phone the oem unlock button is permanently greyed out, this one is not. I don't really want to run through the whole fastboot process and accidentally wipe my phone and it not even be worth it. I just checked my son's Verizon Pixel XL, and his oem unlock switch is indeed greyed out. His is not a replacement phone, but we are both on Verizon. **Solved** Bootloader unlocked!
If you can toggle it then you should be able to unlock. Worst case the unlock command just won't work if it's not a Google version. Can't hurt to try.
Hi... Enable usb debugging and try:
adb shell getprop ro.boot.cid
If it's a Verizon the output is : VZW__001
For Google: 11111111
Or with fastboot (not going to wipe anything )
fastboot oem getcid
I am not able to hook up my phone to a pc at the moment so I downloaded Cid Getter from the play store.
ro.boot.cid: VZW_001
ro.boot.oem_unlock_support:0
but, since I have the OEM Unlock switched toggled to on
sys.oem_unlock_allowed: 1
So with that being said, it is not a google device? Then why the ability to toggle the oem unlock switch?
Hi... Maybe a refurbished unit that someone already tampered before sending it back? Try rebooting in bootloader. Is the bootloader already unlocked? I know it sounds stupid since it's a Verizon device. I don't know. In another thread people who unlocked their Verizon pixel XL reported that the OEM unlock button remained greyed out though. Maybe you got an engineering device?
It says bootloader locked. I read some more that some users of 7.1.1 had this oem switch that could be used but it still didnt make a difference when trying to unlock the bootloader, so maybe i just have a faulty option in my settings that allows me to toggle the switch but it just doesn't matter because it is verizon bootloader?
Well... You just got to try the flashing unlock command and you'll be fixed!
Good luck...
Well, I ran through the ADB commands and it is indeed a verizon model phone, it is just baffling me why the OEM Toggle switch is not greyed out like all the other Verizon models. I don't really want to wipe my phone for no reason, so I will wait until I can find some more info.. thanks eveyrone for your help so far.
Hey. Just run :
fastboot flashing unlock
You can always abort the process. And you'll be fixed
The data wipe is the final step. If you make it that far then it's all good. Just toggle the unlock switch, reboot to fastboot and use 'fastboot oem unlock'. The security check is performed at this point and you will either be presented with the disclaimer or it will fail with no data wipe. You are also provided with an opt out if you get cold feet.
fastboot oem unlock is used for older device, starting with N6P, the proper command is:
fastboot flashing unlock
Cheers
It worked! I am unlocked! I can't believe I was able to get it to unlock even though it showed it as a verizon device on 7.1.1 March update. Thank you for your help!
It worked!
I wonder what's different from others 7.1.1 shipped Verizon Pixel XL... Maybe someone will stop by in this thread and shed some light...
Cheers...
I also got one of these replacement phones with the functional OEM unlock toggle. I haven't had the chance to connect to adb yet. Mine was a free warranty replacement from Verizon not asurion though as my original device was only 2 days old. It's on 7.1.1 with the January patch. My original device was on the February patch and had the option greyed out. So I have my finger crossed in hopes that it will actually unlock.
The CID is not the factor. Originally they thought that was it but obviously, as this thread confirms, that was incorrect.
How did you get a burn in?
Having my brightness up too high and not using auto brightness. Before the PIxel XL, I had been using an Iphone 6 plus for the longest and didn't know that with an amoled device you can't have the brightness up at like 85%. Now that I have learned the correct way, I don't think I could go further than 50% brightness anymore. But the burn in was of my navigation bar and status bar icons, if I went to a grey screen or white screen they would all show a shadow of them..
Someone on reddit stated that they didn't think Asurion stocked Verizon models, only Google models because they handle the Google Store Warranties as well, not sure how accurate that is, but I could see where that would be the case for me getting this one
Try immersive mode... Auto hide notification and navigation bar automatically... Can't live without since i use it...
Related
Okay, so, it turns out that I'm the last person in the world to find out that Verizon decided to make the point of owning an Android null and keep the bootloader on the HTCD530 lock fiveever. The very important OEM unlocking option doesn't appear under developer options. After talking to both Verizon AND HTC, I got a bunch of people who a.) barely spoke English coherently, and b.) had absolutely no idea what I was talking about. So I got no help there. Is it even POSSIBLE to somehow reveal the OEM unlocking option on this device, or has Verizon disappointed me after not even being with them for 24 hours?
Same way as I wrote here.
Only problem is that you need a temporary root to write to the FRP partition.
If someone can figure out how to write to the frp partition then follow my thread here.
http://forum.xda-developers.com/desire-526/help/boot-loader-how-to-unlock-boot-loader-t3472785
Well please let me know if someone figures something out.
totallygoofed said:
Well please let me know if someone figures something out.
Click to expand...
Click to collapse
I wish I'd seen this before I went out and just bought one.
This is not ok.
#VerizonSucks
So still no root possible for vzw version?
Yeah, I escalated this quite high within HTC - and they told me it's not possible. Reading between the lines, Verizon have contractually enforced clauses to remove this option.
anyone tried doing it with fastboot?
Same as other things install the correct driver on the PC and then install the SDK tools with ABD and Fastboot. Within the SDK tools is the ABD and Fastboot exe. Open a Command Prompt within that folder and run fastboot exe and then connect the phone to the PC via the cable and then on the command prompt type fastboot devices and make sure it shows up. once it does type fastboot oem unlock. It will erase all data on the phone. Select Fastboot reboot and then test to see if bootloader is unlocked.
Yeah tbh I'm never using Verizon again, I don't care how much money I'm saving. Their reps are trash, either that, or they're flat out liars. First they told me I could use a GSM unlocked phone with their service (Can't, didn't find that out until I drove to the store to get a SIM, had to get this replacement piece of trash instead, which is the entire reason I have it and not my good rooted BLU phone) Then they said I'd be able to root it quite easily as it's an HTC device (an obvious lie now that I know better.) As soon as my contract is over, I'm switching back to AT&T and telling them exactly why. Disabling rooting on an Android is like putting handcuffs on every person who isn't going to jail. Kind of defeats the purpose of having an Android in the first place.
Like I said before, It is able to be rooted unlocked and S-off. Even Verizon.
I have done this to a few HTC Desire 526. The unlock option in developer options is missing but its only a matter of changing the very last 00 in the FRP partition to a 01. After that your still stuck because even though you will be able to generate the unlock token the HTC DEV Site will reject the Verizon CID.
I have analyzed all of the usual HTC Partitions and can tell you the difference in being Unlocked + S-off is the data that is on the pg2fs , sec, and maybe 1 other partition. I made a image of my s-off 526 and burned it to a SD Card. When put into another device it boots off the sd card and keeps s-off permissions. It's basically running the S-off as the partitions are being read from the sd.
I still need to do some work on this. But i believe I am on to something. To see a totally locked down verizon phone boot and show s-off with the right sd card in it is a promising prospect.
Any updates on this? I bought this device when I was on USA for summer trip, then I came to Mexico and find out that I can only use voice & text but no data because the APN's configurations don't accept other than Verizon's... In order to change that I need to be rooted, but can't root because of Verizon being restrictive with all this things... Any ideas on how can I use my phone completely here in Mexico?
Same here!
I am in the same boat! i hope someone will find something out
Need help here!
Bought an XL via eBay. Found that it's been flashed anyhow. And I can't root/flash ROM or even unlock the bootloader.
Now below is the situation:
1. It's a Verizon, XL, 128GB.
2. It's locked. And OEM unlocking in developer options is GREY.
3. It's stuck in Android O (Opp3.170518.006).
4. dePixel8 doesn't work. Every time I entered the commands "adb shell /data/local/tmp/dePixel8", it ended up with an error.
5. Because of 1., I can't flash TWRP or any bootloader.
I've heard of so-called "FRP Unlock Tool". But it seemed only working on 7.1.2 below and is considered risky for 8.0.
Though 8.0_DP3 is 90% perfect for daily use, I still want to take a chance. But the question is HOW?
doctorm89 said:
Need help here!
Bought an XL via eBay. Found that it's been flashed anyhow. And I can't root/flash ROM or even unlock the bootloader.
Now below is the situation:
1. It's a Verizon, XL, 128GB.
2. It's locked. And OEM unlocking in developer options is GREY.
3. It's stuck in Android O (Opp3.170518.006).
4. dePixel8 doesn't work. Every time I entered the commands "adb shell /data/local/tmp/dePixel8", it ended up with an error.
5. Because of 1., I can't flash TWRP or any bootloader.
I've heard of so-called "FRP Unlock Tool". But it seemed only working on 7.1.2 below and is considered risky for 8.0.
Though 8.0_DP3 is 90% perfect for daily use, I still want to take a chance. But the question is HOW?
Click to expand...
Click to collapse
The only time you could unlock the bootloader on a Verizon Pixel XL was before the operating system updated to Android 7.1.1. Android 7.1.1 was patched so the dePixel8 exploit would no longer work and nobody has found a new way to unlock the bootloader on the Verizon models since then. If you want to downgrade from Android O I think your only option is to deregister your phone from the Android Beta Program. Eventually you will get an OTA that will downgrade your phone back to Nougat but it will also completely wipe your phone including the user data and stored files. You will be starting over from scratch and have to download your user apps again. Unless someone comes up with a new exploit you will not be able to unlock the bootloader or custom flash anything on that phone.
If you wanted to unlock bootloader/flash roms/root etc... you should've come here first to check, then checked with the seller on ebay.
however, your options are:
1) put up with phone in stock (it's really not that bad - which is why development isn't into multiple pages of current roms)
2) sell it and get a google version rather than Verizon
HELP POST
I've purchased a 2nd hand Pixel 2 XL 128GB, Checked with IMEI and found it is a GOOGLE varient and useing it.
But my "OEM UNLOCKING" option is greyed out i'm currently on jun 5 patch. Tried several methods to unlock but OEM unlock toggle is not enabling.
1. Tried basic method, 2. Tried with factory reset, 3. Tried factory reset without sim and proceeded with no setup,
All these method gave no results. Consulted google but they require Order ID which is not possible to get at this point.
Anyone has any ideas which I missed. I really got this phone for all the customization possibilities and camera.
rana103 said:
HELP POST
I've purchased a 2nd hand Pixel 2 XL 128GB, Checked with IMEI and found it is a GOOGLE varient and useing it.
But my "OEM UNLOCKING" option is greyed out i'm currently on jun 5 patch. Tried several methods to unlock but OEM unlock toggle is not enabling.
1. Tried basic method, 2. Tried with factory reset, 3. Tried factory reset without sim and proceeded with no setup,
All these method gave no results. Consulted google but they require Order ID which is not possible to get at this point.
Anyone has any ideas which I missed. I really got this phone for all the customization possibilities and camera.
Click to expand...
Click to collapse
I thought the consensus was there was no way of knowing by just checking the IMEI. I could be wrong though.
Did you try another sim card?
Sent from my Pixel 2 XL using XDA-Developers Legacy app
Try booting into bootloader mode. It should specify what variant it is, and at least show some serial numbers. Contact Google and ask them if they can check for you as well.
If it's a non-Verizon, definitively, you can try flashing the latest factory image from Google using fastboot without your SIM inserted.
Mine was greyed out too until I connected to WiFi, then rebooted. Then I could toggle. Freaked me out too because I bought it off of Swappa. That I was duped for s second.
jaxenroth said:
Did you try another sim card?
Sent from my Pixel 2 XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
No, didn't try another sim. Tried sim and no sim. Now on DP4 from yday. Will give this a shot also then.
Latiken said:
Try booting into bootloader mode. It should specify what variant it is, and at least show some serial numbers. Contact Google and ask them if they can check for you as well.
If it's a non-Verizon, definitively, you can try flashing the latest factory image from Google using fastboot without your SIM inserted.
Click to expand...
Click to collapse
My bootloader screen picture is also shared in this post. As contacted google through chat, they also said it is non-verizon mode.
My CID : 00000000
Even without my sim inserted I've tried and result coming same. dunno why. Did you had this issue ? Can you share the solve you tried ?
djcrystals said:
Mine was greyed out too until I connected to WiFi, then rebooted. Then I could toggle. Freaked me out too because I bought it off of Swappa. That I was duped for s second.
Click to expand...
Click to collapse
Can u share what you did step by step? I've lost here. Tried many things but in the end nothing. :crying:
rana103 said:
Can u share what you did step by step? I've lost here. Tried many things but in the end nothing. :crying:
Click to expand...
Click to collapse
I booted the phone, set it up (added my account) using WiFi. After I set it up I noticed I couldn't toggle the OEM unlock. I rebooted, checked again, at that point I was able to toggle. That was just my situation though.
djcrystals said:
I booted the phone, set it up (added my account) using WiFi. After I set it up I noticed I couldn't toggle the OEM unlock. I rebooted, checked again, at that point I was able to toggle. That was just my situation though.
Click to expand...
Click to collapse
Dunno why mine is making my day painful!!
rana103 said:
Dunno why mine is making my day painful!!
Click to expand...
Click to collapse
Rana, i'm in the same boat. Did you put in your google account? This is the only difference from mine to djcrystals, I did not add my google account. Gonna try and enter it, but i'm also having this trouble with a certified refurbished.
Edit: did not work. Where did you check the imei number that tells you it's google and not verizon
Nergal di Cuthah said:
Rana, i'm in the same boat. Did you put in your google account? This is the only difference from mine to djcrystals, I did not add my google account. Gonna try and enter it, but i'm also having this trouble with a certified refurbished.
Edit: did not work. Where did you check the imei number that tells you it's google and not verizon
Click to expand...
Click to collapse
Try this one. http://www.imeipro.info/check_lg.html
Also when I had chat with google support they clearly mentioned it is a google varient.
But they are unable to support me without me telling them the order ID of this phn. I bought it 2nd hand from Babgladesh.
So, basically I'm screwed.
Pixel 2 xl OEM allow bootloader unlockewd
Hey really anyone..I have been able to duplicate twice each time a little different... I will continue to test and see if I can find a straight forward example that will yield a quick consistent result...The problem is now when I do a adb reboot booloader to actually unlock it still says not allowed when I was looking at the beauty of the toggle flipped on in dev optoins prior to having to reboot to bootloader ...its not wanting to stick ...soooo....wondering if there is a way to stay in the adb session without the adb reboot bootloader command to get to fastboot...or have some sorta multi user attack at this..can one be connected to the phone through the network adb option and fastboot at same time...or is there a adb command to unlock bootloader rather than fastboot...or can one make a script that could..I assume not I'd or at leat not without writing something above my abilities...but anyways I'm on current as of today for the pixel 2 xl verizon...by total mistake...I forgot the kill the dev slider on auto update system and it was to late...so this is achievable on current firmware. but I can read above where ppl have actually got the toggle off and freaked out too...but Ive done it 3 or 4 times now inside of 30 minutes but cant figure out how to issue the unlock command while its off or iff its impossible...so may not have anything here yet but man it sure looks pretty...I have a video of it and more Im making now to try and help someone crack this already...lol
still at it..
so far it appears to follow toggle wifi..flip over to dev...back to wifi...to dev...so forth and you catch it on...if you toggle the wifi on.. then off....then out and into dev oem option ..the wifi on and off few times then in and out of dev oem option then all the sudden I just am about to hit out of dev again when I notice its flippable......flip it on then confirm...but thats where Im stumped...it on is all I know pretty as can be after confirmation...hmmmm
rana103 said:
Try this one. http://www.imeipro.info/check_lg.html
Also when I had chat with google support they clearly mentioned it is a google varient.
But they are unable to support me without me telling them the order ID of this phn. I bought it 2nd hand from Babgladesh.
So, basically I'm screwed.
Click to expand...
Click to collapse
I'm trying to get oem unlocking to show up in Developer Options but am not having any luck. It's a Samsung Galaxy Note 10 + running Android 10. It's the 256gb aura glow color if that matters. Anyways I've had it turned on for 170+ hours without rebooting it. Yet I still don't see any mention of oem unlocking in Developer Options. Did I miss a step? I see some people mentioning stuff to do with changing the time and stuff and I tried that in the past with no success. I just tried to check for software updates then went back to developer options and still don't see anything about oem unlocking. I have put the phone in airplane mode a few times so could that be it?
What is the criteria or whatever you need to do to get oem unlocking to show up?
It's not rooted and I currently have had it on for over 168 hours and tried checking for software update by going to settings>software update>download and install.
Help? Thank you
that1guyyep101 said:
I'm trying to get oem unlocking to show up in Developer Options but am not having any luck. It's a Samsung Galaxy Note 10 + running Android 10. It's the 256gb aura glow color if that matters. Anyways I've had it turned on for 170+ hours without rebooting it. Yet I still don't see any mention of oem unlocking in Developer Options. Did I miss a step? I see some people mentioning stuff to do with changing the time and stuff and I tried that in the past with no success. I just tried to check for software updates then went back to developer options and still don't see anything about oem unlocking. I have put the phone in airplane mode a few times so could that be it?
What is the criteria or whatever you need to do to get oem unlocking to show up?
It's not rooted and I currently have had it on for over 168 hours and tried checking for software update by going to settings>software update>download and install.
Help? Thank you
Click to expand...
Click to collapse
What is your model number? N975(?)
SM-N975U
Your not doing anything wrong and there is nothing you can do.
The SM-N975U and SM-N975U1 do not provide us with the ability to unlock our bootloader. This means we will not be given the OEM Unlock option.
But isn't unlocking bootloader part of rooting? Or is there a way around that? I mean I don't absolutely have to root it but I thought it would be cool to have the option. What's so different about this one that I can't be given the oem unlock option? Sorry if I sound irritated.. I am but not at anyone on here
Also I got this through us cellular. Maybe should have just bought it through Samsung? Model number would probably be different and would probably be able to get oem unlocking option
You should do a little more research. None of the US snapdragon Note10's are bootloader unlockable and hence, are not rootable. Doesn't matter where you purchased it. As far as I know, this is the case for all Samsung phones sold in the US and has been the case for quite a long time.
You can read more here.
that1guyyep101 said:
Also I got this through us cellular. Maybe should have just bought it through Samsung? Model number would probably be different and would probably be able to get oem unlocking option
Click to expand...
Click to collapse
No US versions of the Note 10+ can be OEM unlocked or rooted. Does not matter if you bought it from Samsung carrier unlocked or from a service provider. Carrier versions are SM-N975U and unlocked version is SM-N975U1. It has been a very long time since you could root a Samsung US device. I believe the S6 or S7 were the last rootable Galaxy phones in the US. The Note 8 could be rooted with an engineering kernel but it was more of a hack since you could not fully charge the phone.
Not sure what is going on here. I have a Pixel 3XL that let's me click the OEM unlock. When I restart the phone it still says it's shows the OEM is unlocked, but it shows it's locked in fastboot mode and will not let me flash a recovery image. It's a new phone and I have not put a SIM card in it yet. anyone been through this and found a solution?
If I had read the Wiki more closely I would have seen that I was only allowing the OEM to be unlock. The unlocking took place in another step.
Check it out I got the same thing. I just got a replacement 3XL last week and it's allowing me to unlock it are you saying it's not going to work if I try to unlock the bootloader because I have my original 3xl still and it's grayed out.. don't answer me either I'm surprised you didn't answer me you got the same s*** going that I do ?