yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] TimTx1:
This worked for me. It was grayed out, but then I ran the install-existing command again after connected to wifi and immediately went into developer tools after that and I was able to unlock. I have a Verizon Pixel. It was running the install-existing command a second time after rebooting that made all the difference for me.
[Google Pixel XL Guides, News, & Discussion] djared704:
Welcome to XDA. Do you think you can attempt the google store imei check to see if your device actually is VZW? (Unlocked is _p, vzw is vz). The post is only a few posts up from this one.

Thanks!
[Google Pixel XL Guides, News, & Discussion] squallvai:
What Android version do you have?

Can you explain step by step of what you've done?

I have Android 10 with October 2019 security patch.

This method doesn't works for me
[Google Pixel XL Guides, News, & Discussion] xiaoyiba:
Hi, Could you share the detailed steps ? what is the command of "install-existing command ".

Thanks.
[Google Pixel XL Guides, News, & Discussion] Bobolainaa:
Pixel 3 XL

Hi! I have a Pixel 3 XL which is blocked by EE UK. Can someone help me with unlocking the bootloader because i fail. I mention that it is with patch from October 5, 2019. Thank you!

Btw I am on Android 10
[Google Pixel XL Guides, News, & Discussion] djared704:
Hey guys. I'm here to shed some light. Previously we have been obviously taunted with the existence of a "hTC-download" mode, with no evidence of it actually being enabled by default on pixel, showing with evidence that some kind of token needs to be sent to the pixel to "fastboot oem reboot-download" (Without this token, your pixel will just reboot normally). I have also seen on HTC devices that you could also "adb reboot-download" right in the system, but without the presence of accurate information, I see no way of this working straight through adb without a exploit. I took this matter into my own hands. There have been claims that "hTC-download" has been disabled on 8.0/9.0 permanently with no way to access it even with this "token". However I am not supporting this kind of theory. I have downloaded latest factory image for pixel 1 and extracted it, and used a tool called imjtool which is a tool to extract bootloader files, or simply view whats inside of them. In this case run "imjtool.(your OS) (drop bootloader.img) extract" and it would extract for you. For our sanity I already done this. It has extracted various files, but I instantly hooked on to the "aboot" file. Many of the files started off with the same unreadable garbage which is pretty much special characters and strings for the bootloader, which I believe must be written in C. However I started scrolling down on the aboot file and it started turning into items you would see on the bootloader. I saw for example "[INFO] %s: chip serial number msm_serial: %04x". I thought I hit jack pot. I started looking around and what do I know. I found the "Download mode token check successfully", and even the failed string. Wow! is this enough to prove that a download mode exists? Even found "Booting to download mode ...". This is simply amazing what I'm looking at. It is almost certainly safe to say, a hTC-download DOES in fact exist on Pixel 1. Our next step. How the hell are we gonna get to it?

With this aboot file in mind, hence all the other garbage type files that show next to no information at all. I will post it here. I want you guys to look at it thoroughly, maybe for a fact you may know something more than me. The way to activate download mode may be right in the file. I stated an argument that Pixel has "core firmware" files, files that are not changed at all, and they are only once produced in the factory. Such as the download mode on LG phones, a mode that is not modifiable. For this fact we may not be able to find how to activate DL mode here, but what am I allowed to talk about, I haven't even looked at the entire piece of code. Thanks so much guys.
[Google Pixel XL Guides, News, & Discussion] jonr2975:
Wait. A. Minute.

Going back to the original post from 2018, factory resetting, not setting up a password, no wifi etc., I ran the command "adb shell pm uninstall --user 0 com.android.phone" proceeded and nothing worked.

BUT, after then running the command "adb shell pm install-existing com.android.phone" after connecting to wifi and going to developer options, I noticed a long delay before the developer options open, mainly a black screen while not even in dark mode, but I see parts of the System UI Navigation.

Now to recap, it is still locked and grayed out for me, but it is interesting that something stopped before returning to normal. Maybe someone else can replicate this as I am not sure its anything at all.
[Google Pixel XL Guides, News, & Discussion] djared704:
You can also put in the serial number too to find it too. I don't think you're able to put in the "model of the pixel" because it is generic, so you either have to do SN or imei. Thanks!
[Google Pixel XL Guides, News, & Discussion] TimTx1:
I tried that, it didn't find the serial number either. I think because it's a motherboard (and wasn't replace by Google, but ubreakifix instead) they probably don't have it in their system.
[Google Pixel XL Guides, News, & Discussion] djared704:
Do you believe that may be why? Since the motherboard isn't by verizon, still basically google, it may require those "stipulations" to unlock. Meaning incorrect information was stored in the phone regarding OEM unlock. Your pixel may be a google store after all. But without evidence, we can't exactly say that, but from the behavior of the OEM unlock, it could just be unlocked.
[Google Pixel XL Guides, News, & Discussion] merikgvr4:
How much did they charge you for the motherboard replacement? I have a pixel they fixed the screen and battery with the local heroes program and now it no longer charges. Guy said sorry we can't fix it.

Thanks in advance for any input.
[Google Pixel XL Guides, News, & Discussion] TimTx1:
The OEM unlock was grayed out until I ran that other command while looking at it, like I said in my last post.

If you're still having problems unlocking you should try the step I mentioned in my last post.

The OEM unlock was not available until I did that.

As to how the motherboard would have impacted things, I don't know. But, I have a hard time believing that they made Verizon-specific motherboards. I think it is the additional step I mentioned that may not have been done before and that may have made all the difference here.

As an additional note, the OEM unlock was grayed out even after all this (it said it was already unlocked after the additional step I mentioned, but became grayed out again). Then recently I replaced the boot.img with one from Google, the stock boot image. Now the OEM unlock is available again always.

It is possible that there is a verizon specific boot image that is causing all of this and that running that command I mentioned while on dev tools forces something to restart just long enough to enable OEM unlock, if you get it just at the right time right after issuing the command.

And it seems that replacing the boot.img with stock fixes the issue for good. It would make a lot more sense to me for this to be software related, than hardware. I doubt the Google parts are any different between a verizon pixel and a Google store pixel.

---------- Post added at 05:05 PM ---------- Previous post was at 05:01 PM ----------

Sorry, I don't have a price. It was through Verizon warranty. Verizon is doing a special enrollment right now. If you call them, you can get on their warranty program and then just take it into ubreakifix like I did. You have to call verizon first to get the warranty set up through them for ubreakifix. Then, you won't pay anything as long as your phone doesn't have any damage. And, the warranty through Verizon is $12 a month plus tax.

I don't know when the special enrollment through Verizon ends but soon I think.
[Google Pixel XL Guides, News, & Discussion] merikgvr4:
Thanks but don't have Verizon service, with tmobile. Appreciate the reply though.
[Google Pixel XL Guides, News, & Discussion] TimTx1:
You're welcome. Too bad it doesn't work for you. I looked up tmobile's policy and it looks like they don't offer these special enrollment periods and even if you sign up they say that a tech would look at your phone before they approve the warranty. Still, maybe they have the special enrollment period and maybe they'd bend the rules about having a tech check it. It never hurts to ask them. Sometimes they'll do things just to retain you as a customer.

Sorry I couldn't be of help. Good luck.
[Google Pixel XL Guides, News, & Discussion] djared704:
These phones were never sold with TMO iirc, it was only verizon. In this case he unlocked it or the seller unlocked it beforehand. Service unlocking does not allow OEM unlocking.
[Google Pixel XL Guides, News, & Discussion] TimTx1:
You're saying if the phone was service unlocked then you can't OEM unlock? I have had my verizon phone for three years. I didn't ask for a service unlock but as far as I know it's automatic after a certain amount of time, with verizon.

Somehow the statement that a service unlock keeps you from being able to do an OEM unlock seems strange. If you're trying to do an OEM unlock, I'd try it anyway.
[Google Pixel XL Guides, News, & Discussion] Dragon Kumera:
It is very possible to unlock the bootloader on pixel xl gen 1.

It not like it fire hdx 4th gen where bootloader if you try to unlock that or go to it your device is bricked.
[Google Pixel XL Guides, News, & Discussion] djared704:
This is correct. Service unlocking does not permit OEM unlocking. This is because the device is still registered in the system as a VZW device (Hence you plug your imei into google store repair, it shows _vz), etc.
[Google Pixel XL Guides, News, & Discussion] TimTx1:
I have an original Verizon Pixel XL from three years ago, bought and shipped directly from Verizon. I have the latest software from Verizon. I just unlocked the bootloader. It can be done.

You just have to follow all the steps as I outlined before, and as the other post mentioned from the past. Then, follow the new additional repeated step exactly as I stated.

---------- Post added at 06:48 PM ---------- Previous post was at 06:41 PM ----------

I don't know about that. Service unlocked would mean you're not locked into the Verizon carrier. I could see this in relation to the device still being service locked, that they'd prevent OEM unlocked while you were still serviced locked, but not the other way around. I had mine on verizon for three years. I don't know how to verify if it was ever service unlocked but per verizon it should have been unlocked at least a year ago automatically. Once you come off contract with them, it's unlocked without you having to ask as far as I know.
[Google Pixel XL Guides, News, & Discussion] TimTx1:
If the phone is doing a query on the internet, I'd do a network trace using wireshark. If you find that it is, then you could set up a fake proxy server and cause it to intercept the call and respond how you want. But that's more complex.

It is possible that my new imei number got around things. Someone that couldn't get it working before and has a verizon phone needs to try this one additional step I mentioned and see if it works for them too.

If not, network tracing would be the next step.

---------- Post added at 07:06 PM ---------- Previous post was at 07:00 PM ----------
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Did he have the original firmware on his Verizon Pixel XL? If he did that would explain why he was able to unlock the bootloader.
[Google Pixel XL Guides, News, & Discussion] TimTx1:
When they swapped out my motherboard, I had 7.1.1. I then connected to Verizon and got all the OTA updates from Verizon. So, my phone was then on the latest Android 10 from Verizon. It was only then that I actually tried to unlock. I had never tried to unlock before. I did this last week.

---------- Post added at 09:54 PM ---------- Previous post was at 09:47 PM ----------

Is no one able to run "adb shell cmd package install-existing com.android.phone" from their computer while sitting at the developer options menu on their phone while watching the grayed-out "OEM unlocking" option on their phone? At least, for anyone still locked. That is what worked for me. It became enabled for just a second or so.

---------- Post added at 10:18 PM ---------- Previous post was at 09:54 PM ----------

Ok, here's my suggestion for the steps to unlock now on a Verizon Pixel XL running the latest Verizon OTA Android 10 update from December (A3, says "October" but it's really "December"):

1. Factory Reset

2. skip everything in setup, but turn off free up space, use location, and send usage data

3. Developer Options and enable USB debugging.

4. Connect your phone to computer. (I'm on linux mint)

5. adb shell pm uninstall --user 0 com.android.phone

6. restart from menu

7. Connect to Wifi

8.Visit website

9. Check Dev Options (OEM Grayed out)

10. adb shell cmd package install-existing com.android.phone

11. restart from menu

12. check dev

13. visit new website

14. repeat 12 and 13

15. open the Dev Options menu on your phone. Notice how the OEM unlocking option is still grayed out. Stay in that menu, do not leave the menu on your phone and stay on the part where you see the OEM unlocking option

16. adb shell cmd package install-existing com.android.phone

17. Watch the OEM unlocking option. It will enable itself for a brief moment. Quickly select it to change to unlocked.

18. It will probably disable itself again after that but you will already be unlocked. I know I flashed the latest boot.img, and Magisk, and rooted and now it's available all the time. I don't know if that changed anything.

If that doesn't work, then my new motherboard and IMEI number might have impacted something. But the above worked for me.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Thanks for sharing this information. :good:
[Google Pixel XL Guides, News, & Discussion] Dragon Kumera:
Glad a work around was found :)
[Google Pixel XL Guides, News, & Discussion] jonr2975:
I’ve tried like 3 times and it it didn’t work for me. Until someone else posts a success, I don’t know what to believe.
[Google Pixel XL Guides, News, & Discussion] RaspberryPiBen:
It hasn't worked for me either. I could be doing something wrong, but I want to see if somebody else gets it to work.
[Google Pixel XL Guides, News, & Discussion] X-form:
I have a Verizon Pixel OG I just bought to try this on

I currently have two Verizon Pixels (One regular and one XL). I unlocked both using the original method back in summer 2019. However, both of those phones have the OEM unlock option greyed out even though the bootloader is unlocked on both phones still. It doesn't bother me since my bootloader is unlocked on those two phones and I am keeping them unlocked. However, what makes me curious is why the OEM unlock is greyed out when the bootloader is unlocked and it is already allowed. It is weird why it got greyed out on both phones a bit later. This is indicative that Google or Verizon patched the method.

I just bought a pixel from eBay to try if I can unlock it. It is a Verizon Pixel and the OEM unlocking options are greyed out. I will try the new method and report back on my findings.
[Google Pixel XL Guides, News, & Discussion] Dragon Kumera:
If I had a spare pixel xl gen 1 verizon phone I would try and help you figure it out but sadly I dont.
[Google Pixel XL Guides, News, & Discussion] X-form:
I still couldn't get it to work

Update, I tried doing what Tim Tx1 recommended and I did it twice, but to no avail. I didn't see the OEM unlocking become not grayed out so I could enable it. I waited around 5 minutes in developer options on the last step, but that didn't work. Since I did it twice and didn't get it unlocked, I am afraid this method doesn't work. It could have worked for Tim Tx1 because he had a different IMEI number. However, I would suggest other people still try Tim Tx1's method as maybe someone will stumble on something that works. Maybe I could be doing it wrong too. I really hope someone can figure this out. I am glad Tim Tx1 got it to work.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Maybe NOT.
[Google Pixel XL Guides, News, & Discussion] kibirone54:
Sad moment

Yesterday I was about to root my Pixel 3XL. I found some tutorial, and as I followed the tutorial I patched a boot img from in the magisk. The result I got that one of my payment app stoped working, so I decided to make a factory reset. And after all I found that my proximity sensor stoped working. And after quick search I found that only the way to fix it, is to unlock OEM, and flash Android again. (persist partition probably damaged) That's my little story, how to make an not functioning phone from scratch. I hope there will be a solution to unlock OEM. None of the previous method worked for me.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Quick Question

Did you know this is a Pixel XL thread?

Also, it might help other Pixel 3 XL owners if you could remember the thread you were reading and post it and your experience in the Pixel 3 XL forum.
[Google Pixel XL Guides, News, & Discussion] TimTx1:
Man, that sucks. I really hoped I had stumbled onto something. Sorry it didn't work out for you. Have you ever heard of WireShark? Perhaps you could try it once more while running a WireShark trace and I could take a look at the network calls.

Or, if anyone knows how I can make mine call out to Google from dev tools without screwing up what I already did and locking my phone again, let me know and I'll do a trace.

Then this confirms that my IMEI number not being in Google's system because of my new motherboard had something to do with this.

I think the other people in this forum were already onto this, but the next step then is to try to create some sort of intercept application on the PC to catch the call to Google and return a fake response.

It may sound weird but in a way, I wish my motherboard was never replaced and I was stuck like everyone else. I have the experience with network tracing and experience with developing service applications, I wonder if I could have figured this out. It would have been a nice challenge.

Well, hopefully somehow someday a solution can be found for everyone. Sorry this didn't pan out. Thank you for trying X-Form.
[Google Pixel XL Guides, News, & Discussion] X-form:
[/COLOR]

I have used Wireshark very briefly in a Network class, but it was such a long time ago that I forgot and would have to learn over again for the most part. However, I think using Wireshark, capturing the information it sends, and being able to deliver a payload via a proxy server to trick the phone would be the solution. I wish I had the time to delve more into this, but I am currently taking more than a full load of online college summer classes and that takes up most of my time.

The good news is you can buy a Pixel 32GB on eBay now for around $60-$80 for excellent condition or even less if you don't care about condition. If I were in a position where I had more money, I would send you one for free, but I am just a broke college student who hasn't graduated yet. I would probably just end up reselling that Pixel I just purchased on eBay. I think someone like you would be more able to troubleshoot this further and more effectively. The good thing is after you purchase the Pixel on eBay, you can resell it and not loose too much money or if you do succeed in unlocking the bootloader, you can sell it for even more money.

I am glad you got around the OEM unlock grayed out, but that is quite interesting with the situation you have. Your phone is probably unique then.
[Google Pixel XL Guides, News, & Discussion] Dragon Kumera:
I saw pixel xl 128gb for like $70 on ebay though a few days ago. It was unlocked to.
[Google Pixel XL Guides, News, & Discussion] X-form:
Pixel for $60 on eBay

I am not sure if I am allowed to post links to eBay listings here, but I searched today and found $60 pixels which were refurbished for $60 and free shipping. They are also in excellent condition. You can find them easily by searching pixel 32 GB in eBay and going to the side bar where you can type in the maximum price. You can type in $80 as the maximum price and eBay will filter the price to everything $80 or under for instance. You can easily get a pixel for $60 on eBay.

I assume the same technique would apply whether it is a Pixel or Pixel XL. Lastly, I am not sure I trust the unlocked description on eBay as I bought and sold several Pixels on eBay which were marked as unlocked, but the OEM unlocking was grayed out. I think sellers mistaken unlocked for meaning sim unlocked not meaning direct from Google and bootloader unlockable.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
What [MENTION=5766127]X-form[/MENTION] said. :good:
[Google Pixel XL Guides, News, & Discussion] Dragon Kumera:
I see ok thx for the update.
[Google Pixel XL Guides, News, & Discussion] djared704:
You need to visit your device board to learn more about your specific device.
[Google Pixel XL Guides, News, & Discussion] TimTx1:
Thanks, yes it is a unique situation. I don't have the interest in buying a phone to try to unlock it. But if there's anyone in the DFW area that wants me to try with their phone, I will.

After some searching around in the code, it leads me to believe even more that the fact that my imei number isn't registered because of my new motherboard made all the difference. I suspect it's a matter of finding when that check is made, where it is made, and how to fake a response that'll solve this for others.

Unfortunately, although I'm a developer, I have never developed for Android so I'm not familiar with a lot of the internals of what is going on. From what I can tell from the code I looked at, I would need to really understand the provisioning process and how the FRP partition is used. That is where I think this flag that I saw may be stored that says whether or not the phone can be unlocked. But beyond that, the oem_lock service is where the work is done to unlock the phone. But, it's impossible to call that service since the code requires the appropriate authorization. It's all well protected. The only real way to bypass this I think is to spoof the imei check so that the flag is set to allow the unlocking.
[Google Pixel XL Guides, News, & Discussion] X-form:
I am in the DFW area

I am in the DFW area.
[Google Pixel XL Guides, News, & Discussion] TimTx1:
I sent you a private message.
[Google Pixel XL Guides, News, & Discussion] k12babes:
Android 10

Does this method work on android 10.0 sorry for posting on old post

google pixel xl verizon android 10

---------- Post added at 09:07 PM ---------- Previous post was at 08:58 PM ----------

can this method work on android 10 verizon pixel xl
[Google Pixel XL Guides, News, & Discussion] n3kf:
If it's a Verizon model, there is not any known way to unlock the bootloader on Android 10. There are people trying, which is a good thing.