[Google Pixel XL Guides, News, & Discussion] TimTx1:
I ran it. Unfortunately, I think my recent repair may have something to do with things. I had never tried unlocking before. I only did it now because my motherboard and battery went bad (it might have just been the battery, but they replaced the motherboard as well) and I wanted to limit my charging to 80% with the new battery (it's supposed to prolong the life) which is only possible through an application that requires root.

Using my old IMEI, it shows it as "_pixel_xl_phone_black_128gb_vz". However, the new motherboard gave me a new IMEI, and that one doesn't even show up when I search it (it responds with "We don’t recognize this number. Check that you entered the correct IMEI or serial number for this device."). The new motherboard might have something to do with things.

---------- Post added at 06:46 PM ---------- Previous post was at 06:29 PM ----------

I have Android 10 updated through Verizon. It says security patch "October 6, 2019" but that's not true. That's a Verizon update bug. The Build Number is QP1A.191005.007.A3. A3 is the December 2019 security patch (I think A1 was the October one). If you have A3, you actually have December, even though the "Android security patch level" says October. I learned this when I looked at the Google images. A3 is the latest for the Pixel XL. And then, I googled the issue and found out it was just a Verizon install inaccuracy which listed the patch as October instead of December.

I followed the steps from post #1003:

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 until OEM Unlock is available

Then, that didn't work. I then went into the dev tools menu. While I was sitting at the dev tools menu (after finishing all that, and I was connected to the internet), it was showing that option grayed out. While sitting at the menu, I ran:

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

Right after I ran that command, while sitting at the dev tools menu looking at the grayed-out option, that option suddenly became available. It might have been only temporary. I was able to enable it. From that point forward, it was grayed out but was already unlocked. It was almost like it was a temporary reset after that command, like something restarted and gave me just enough time to enable it.

I have a Verizon phone, but a new motherboard (my phone kept rebooting all of the sudden so they replaced the motherboard and battery but I bet it was just a battery issue all along). So it's also possible that the new motherboard helped in some way. Perhaps the motherboard itself has something that works in conjunction with the Verizon image.

Hopefully this helps someone, but I bet the new motherboard was the key and might have taken away the restrictions I had before. But, I never tried it before with the old motherboard, so that's just an assumption.

---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------

Sit at the developer options, then run the command. I think that's what did it for me. It was like a short period where that option became available, right after running that command. But I was actually sitting at dev tools, staring at the grayed-out option when I ran the command.