yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] rrodriguezjr92:
Maybe I missed something....

Background, my Pixel 1 suffered a gruesome end on a racing event this weekend but I had another available (due to some Verizon mistakes where they sent one to a completely wrong address). The "new" one requested to update from 7.1 up to 9.0 and I immediately noticed big time errors such as the speakers and mic not working, not reading the headphone jack etc. All of these worked perfect before the update.

So my idea is to bring it back to 7.1 / 8.0 and see if that will fix it. If it does yay, if it doesn't well I'll just use the phone as possible until I buy a new one.

I've gone through these steps about 10 times already. I get to Step 7 above and by some suggestions throughout the thread I restart twice, even do the hard reset by holding down power. Step 8 and 9 go smoothly.

However, once I load into bootloader, the bootloader still says locked, and the

fastboot oem unlock

or

fastboot flashing unlock

both end up giving me a message where it's waiting for a device.

Any suggestions? I'll likely give it a rest for a bit and see what happens. The phone is currently running Pie w/ the Oct 5th security update which from reading through the comments should still work.

Any help is appreciated :good:
[Google Pixel XL Guides, News, & Discussion] GbizzleMcGrizzle:
I was wondering if the switch to unlock my bootloader in developer settings isn't switched to the ON position, should my phone be able to connect to my computer in fastboot? I don't mean unlock it but just plain old connect?
[Google Pixel XL Guides, News, & Discussion] Phalanx7621:
You can't send fastboot commands to your phone with a locked bootloader. I mean you can use it to unlock your bootloader, but other commands won't work. You can of course use ADB while the OS is booted up as long as you have USB debugging on.
[Google Pixel XL Guides, News, & Discussion] GbizzleMcGrizzle:
But my computer should detect that my phone is connected in bootloader mode though right?
[Google Pixel XL Guides, News, & Discussion] post-mortem:
Yes, unless there is a driver problem.
[Google Pixel XL Guides, News, & Discussion] andrew2432:
Not exactly, mine doesn't. Only the noise when its hooked up, fastboot devices should return something though if I remember
[Google Pixel XL Guides, News, & Discussion] mr0chris:
I just tried it and it fails for me

Edit: Got OEM Unlocked on Oct 2018 security patch

When you get to the step: connect to WiFi and open chrome, use adb to open chrome

adb shell am start -n com.android.chrome/com.google.android.apps.chrome.Main

then browse to a few websites via touch. After that OEM unlocking should be available in developer options.
[Google Pixel XL Guides, News, & Discussion] powerlinecarry:
My wife and I just got two Pixel 3's from Verizon. One must have been an RMA.

Hers is unlocked out of the box. Mine is not, and I'm not having any luck using this method.

I'm at work right now, but would any info from hers be helpful?
[Google Pixel XL Guides, News, & Discussion] lafester:
Might be helpful in the pixel 3 forum.
[Google Pixel XL Guides, News, & Discussion] powerlinecarry:
Posted the same in the bounty thread, but didn't see much else going on over there.
[Google Pixel XL Guides, News, & Discussion] GbizzleMcGrizzle:
So frustrating for me I even replaced the daughterboard but can not connect in fastboot and I really don't think it's a driver problem...

I'm tempted to sell this phone and buy another one. But it's in such mint condition of have to end up with a scratched up phone
[Google Pixel XL Guides, News, & Discussion] mrhisme:
Dear,

I did

1. Remove Google account and any kind of screen lock (fingerprint, PIN, pattern, etc.) from your device.

2. Eject sim card from your device.

3. Reset your device. In setup wizard, skip everything, don't connect to WiFi, don't add fingerprint or any kind of screen lock. (I did it twice)

4. Go to Developer Options and enable USB debugging.

5. Connect your phone to PC.

6. Open CMD in adb directory and type

Code:

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

error: more than one device/emulator

Pls help me with this issue :(
[Google Pixel XL Guides, News, & Discussion] post-mortem:
type adb devices at the command prompt.

What do you get? Are you using a Windows computer?
[Google Pixel XL Guides, News, & Discussion] mrhisme:
Yes I'm on computer, here is the result:

C:\platform-tools>adb devices

List of devices attached

HT68D0200101 device

emulator-5558 offline
[Google Pixel XL Guides, News, & Discussion] post-mortem:
Try this:

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

or this:

adb -s HT68D0200101 shell
pm uninstall --user 0 com.android.phone
[Google Pixel XL Guides, News, & Discussion] HueyT:
Before doing anything, you'll need to type in Command Prompt window: "adb kill-server" and then you can type all other commands
[Google Pixel XL Guides, News, & Discussion] mrhisme:
I used another PC and did it successful, thanks for your kind :)

---------- Post added at 09:43 AM ---------- Previous post was at 09:43 AM ----------

thank you :)
[Google Pixel XL Guides, News, & Discussion] ooemir:
hi friends.

My Phone now blue OEM unlocking but i resume now;

adb devices

List of devices attached

712KPKN1033285 device

PS C:\platform-tools> fastboot oem unlock

< waiting for device >

wait wait wait waitt.. Pls help me
[Google Pixel XL Guides, News, & Discussion] post-mortem:
fastboot only works in bootloader mode. adb works when the Android system is running. You can type adb reboot bootloader, the run the fastboot commands from bootloader mode.
[Google Pixel XL Guides, News, & Discussion] ooemir:
Pls look i try do all step . but now this error . Pls help me . My phone last update android 9

PS C:\adb> adb shell pm uninstall --user 0 com.android.phone

adb server is out of date. killing...

* daemon started successfully *

Success

PS C:\adb> adb reboot bootloader

adb server is out of date. killing...

* daemon started successfully *

PS C:\adb> fastboot oem unlock

...

FAILED (remote: unknown command)

finished. total time: 0.002s

PS C:\adb> fastboot flashing unlock

...

FAILED (remote: Flashing Unlock is not allowed

)

finished. total time: 0.019s

PS C:\adb>
[Google Pixel XL Guides, News, & Discussion] ooemir:
This my phone

HTC One A9 cihazımdan Tapatalk kullanılarak gönderildi
[Google Pixel XL Guides, News, & Discussion] post-mortem:
You have a taimen. If you haven't already, follow through the instructions in this thread.
[Google Pixel XL Guides, News, & Discussion] fuzzychicken:
I just got this device updated to Android Pie. Can I still use the instructions in the thread?

I am sorry for the hurried response as I have not checked this thread from start to end, I just made some cursory reading, but I have only 2 weeks to return the device (got from ebay refurb), hence the question.

If I can use these instructions, I will read this thread completely before asking any more questions.

Thanks in advance.
[Google Pixel XL Guides, News, & Discussion] post-mortem:
Yes, there are numerous reports of people doing this successfully on Pie.

:good:
[Google Pixel XL Guides, News, & Discussion] notthatkindofclansman:
OEM still greyed

There must be something I'm doing wrong, but I'm not sifting through all 51 pages of this thread because the first 3 or 4 are filled with people debating whether it works on Pixel 2, which gives me low confidence that I will find this issue there.

So for one, when I type the first command, my phone gives me the "debugging from that computer" prompt despite powershell giving me an error. I continue to restart my phone, and OEM is still grey.

What should I do?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
No go for Pixel 2
[Google Pixel XL Guides, News, & Discussion] notthatkindofclansman:
I should have clarified, I'm using one of the phones the thread is ACTUALLY about, the OG Pixel small. My low level of confidence is generated by my fear that the rest of the pages, like the first four, are dominated by technically off topic comments that can in no way aid my quest for help on the phone(s) the thread is about.
[Google Pixel XL Guides, News, & Discussion] post-mortem:
Several people have reported this working on the Pixel, such as this guy:

The November update was just released today, so I have come across no reports regarding if someone even tried this after installing the November image.

Did you try connecting to the internet by launching Chrome using the am start terminal command, rather than just tapping on the app?
[Google Pixel XL Guides, News, & Discussion] :
I followed the steps in the OP and got it unlocked on 2nd attempt. Not sure if I missed a step 1st time but i got OEM unlock on 2nd attempt. OG pixel on 9.0 running October security patch.

Hope that helps...
[Google Pixel XL Guides, News, & Discussion] notthatkindofclansman:
I did not (I'm not too familiar with adb). Thanks for the suggestion.
[Google Pixel XL Guides, News, & Discussion] Yousvel:
I skipped #2. Eject sim card from your device and it works

Just for your information guys, I have unlocked my bootloader today to flash the latest November update, I skiped #2 in the instruction (2. Eject sim card from your device) and it works. It maybe because my apn is not automatically added. So, my phone is not connected to internet until I manually enter the apn.
[Google Pixel XL Guides, News, & Discussion] jamina1:
I have a Pixel XL that I purchased from ebay about 18 months ago, locked to Verizon. I followed the instructions in #1 and didn't have any luck. I redid them a second time and it worked a charm. I'm on the November 2018 update, too.
[Google Pixel XL Guides, News, & Discussion] arooni:
hey team!

i was able to do this on an OG pixel that i bought from ebay last week. trouble is it worked for a day and then just would't turn on. i didn't try to flash anything, was just using stock. luckily i was within my 30 day return window to ebay so i asked for a replacement device that will be here in a week or so.

i just want to make sure by unlocking the bootloader i didn't accidentally brick the device. can anyone who's done this recently speak to their phone working just fine? i don't plan on flashing anything now but when device security updates stop next year, would be nice to be able to flash lineage if that's available.
[Google Pixel XL Guides, News, & Discussion] post-mortem:
If it worked for a day, then you didn't brick it. The problem was something else.
[Google Pixel XL Guides, News, & Discussion] jassyatwal530:
Can confirm this works on my Verizon model Pixel 1 on Android 9 with August 2018 security patch; worked on first attempt too! :cool:
[Google Pixel XL Guides, News, & Discussion] levinster82:
I can confirm this still works for a Verizon Pixel with the latest updates. Big thanks to the OP :good::good:
[Google Pixel XL Guides, News, & Discussion] notoriouspk:
I have a pixel xl boot loader locked no recovery ....tried flashing factory image ...no use

i have access to fastboot .. non of the commands r working to unlock boot loader "remote unlock not allowed "

can I still unlock my bootloader ?

how do I make it boot :(
[Google Pixel XL Guides, News, & Discussion] eginugraham:
Hey guys

From what i read here

You did this method because the "allow oem unlock" was greyed out right?

What if it was already toggle able, can i just go straight to issue a command unlock?
[Google Pixel XL Guides, News, & Discussion] ryox70:
what security patch are you on? i just installed the Dec 5 before i saw this thread, i got the oem toggle to turn blue but fastboot commands fail with "flashing unlock is not allowed" on both commands
[Google Pixel XL Guides, News, & Discussion] thewraith420:
Does "fastboot oem unlock" work? I just ordered the phone on ebay and don't know what patch it'll be up to. Hoping not the latest if they've made it not unlockable now.

Edit:Nvm I reread your post. That sux hope it gets worked out.
[Google Pixel XL Guides, News, & Discussion] pricem0595:
So can we confirm that this work around was fixed in the December 5th security patch?
[Google Pixel XL Guides, News, & Discussion] alanmeyer:
So my Pixel is on 9 with the December security update and I was able to get it to work first time.

However, I found that when I went from (Step 8) Chrome to (Step 9) the settings that the Unlock toggle was grayed out the first time. I had to exit to the main screen and wait a minute or so and then when I went back the toggle was available.
[Google Pixel XL Guides, News, & Discussion] PrettyPistol555:
Is it safe to Flash the Latest Factory Image "9.0.0 (PQ1A.181205.002.A1, Dec 2018)" If Bootloader is already unlocked?
[Google Pixel XL Guides, News, & Discussion] junglism93:
Should be okay mate as you have to have the bootloader unlocked to be able to flash the factory images.

Haven't tried it on the pixel yet but I've never had any of my nexus devices re lock the bootloader after flashing stock images.
[Google Pixel XL Guides, News, & Discussion] PrettyPistol555:
Thanks, I'm always wary when using Verizon devices... they'll stoop to ANYTHING...

Anybody know if the latest update is supposed to fix the sudden rebooting issue experienced by some pixels?

I had to RMA my XL 3-4 times (With each replacement the reboots would start soon after upgrading to Android 9... sometimes as many as 7 reboots in a day... My original eventually went black and never came back up... after that I started calling support as soon as the I had several within a few days), I haven't used it since they upgraded me to a Pixel 3 XL for Free... used my upgrade, but waived the $579 price, AND let me keep the most recent Pixel XL they had sent, which I didn't even use long enough to get the reboots (On arrival, the screen had a gap at the top edge where it meets the frame).

But I'd rather use the OG XL, as My Call Recording app doesn't work without Root...

I just don't want to start using it only to have the thing reboot itself into a brick like my original...
[Google Pixel XL Guides, News, & Discussion] luxor96:
how to connect wifi when wifi cannot toggle on?
[Google Pixel XL Guides, News, & Discussion] alen_gh:
OEM unlock Disabled after flashing Signed Build

Hello

After signing my own customised AOSP PQ1A.181205.002.A1 on Pixel SailFish I did the big mistake to (re)lock the bootloader with fastboot .

I found no way to unlock it due to "OEM unlock" being disabled !! :( Even Wifi active with access to internet !!!

The device is a Google one, free from any Career

Any idea to solve this isue pls ?

[Edit] : Since the Build on the device is signed , there is also no way to use OTA or Stock update with ADB sideload. The solution provided for Verizon in this Post did'nt help :(

---------- Post added at 10:12 AM ---------- Previous post was at 09:54 AM ----------

what do you mean by "can not toggle on" ?

did it turn off automatically or is it Grey (Disabled) ?
[Google Pixel XL Guides, News, & Discussion] luxor96:
hmmm,
[Google Pixel XL Guides, News, & Discussion] lafester:
How does someone with so much knowledge about building and signing not know when it is ok to lock their bootloader?
[Google Pixel XL Guides, News, & Discussion] alen_gh:
Hi [MENTION=421262]lafester[/MENTION]

Google devices are supposed to be free to hack (customise OS builds) at any time and in any circumstance. That's why AOSP provide platforms for (each/all) google devices. And that's why we always have the ability to unlock bootloader on them ! the aim is just to know how.

If i did lock my bootloader , it is because i wanted to test some security functions. and as you see i was able to unlock back the bootloader.

---------- Post added at 08:19 AM ---------- Previous post was at 08:01 AM ----------

Hi [MENTION=9643380]luxor96[/MENTION]

Try one of those steps If you didn't yet :

- reboot the device (i guess you already did it befor posting your question)

- Reboot in safe mode : if it works , that means one of your downloaded apps is responsible of this dysfunction.

- Otherwize , format cach and userdata (you will loose all your data)

- the last resort : Download and flash the latest factory build .

If none resolve, "Google support team" suggest that it is a hardware isue and they did replace many customer devices because it is a known dysfunction.
[Google Pixel XL Guides, News, & Discussion] bigmike35:
Can confirm it works with latest December updates. Thanks!
[Google Pixel XL Guides, News, & Discussion] Xihexa.io:
So, I'm on the latest December patch, Verizon variant. Not refurbished.

I followed a few threads that "Successfully" got the OEM toggle to turn on.

I got it to switch on and ungrey by following one thread where the guy got a refurb on 8.1.0.

I factory reset, skipped setup, enabled USB Debugging, uninstalled phone via ADB, enabled Wi-Fi, opened Chrome and waited in browser, went back to Developer Options.

OEM toggle was no longer grey, turned it on, logged into my Google account, let apps update, toggle stayed on.

Rebooted to bootloader, still locked.

Rebooted to system, toggle still blue.

At this point, I manually booted to Recovery Mode and mounted system/factory reset via menu.

Turned phone back on, skipped setup again, enabled Developer Options, OEM toggle not grey, switched it back on and setup the phone, installed all my apps and the like.

I've rebooted multiple times and even now it's still on.

I still can't flash unlock, the value for "ro.boot.flash.locked" is still set to 1.

However, the prop value that showed the bootloader being unlockable has disappeared, it was at 1 before.

Tl;Dr I'm not gonna mess with the toggle or bootloader anymore as of this moment so that it doesn't grey out again.

In the thread I followed, the guy was only able to flash unlock after OTAing to 9.0.

My question is, if I keep it set to unlock, on the next security patch or Q upgrade, is there a possibility that O may be able to flash unlock or unlock_critical?

.

.

.

EDIT

My bad y'all, wrong thread. My phone is s Pixel 2 XL. ?
[Google Pixel XL Guides, News, & Discussion] espionage724:
I just got a OG Pixel XL (I assume a Verizon model) and ran into the grayed-out OEM unlock option. Found this thread, did the instructions in the first post (twice), managed to get the OEM unlock option, and did flashing unlock from the bootloader. I now have a bunch of questions:

Is the phone basically unlocked now like a normal Pixel would be?

Are the changes permanent (assuming I keep the bootloader unlocked)?

What if I flash the latest factory image; will the bootloader be unlocked still as long as I don't manually re-lock it?

Is there any possibility this unlock can be undone aside from me manually re-locking it? What about Android security or OS updates?

And if I did re-lock it for some reason, would I have to repeat the process (reset, remove phone, connect to net) again?

If so, can I make this phone work as a regular Pixel and avoid the Verizon-specific bootloader lock?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Yes, the phone is unlocked like the Google Pixel XL Version.

Yes, it will remain unlocked until you relock it. CAUTION: Do not relock the bootloader without returning the phone to Stock or you will brick your phone.

No.

Yes.

Yes, the Pixel XL will work the same as a Google Pixel XL with an unlocked bootloader. You should be able to use it on any carrier.
[Google Pixel XL Guides, News, & Discussion] espionage724:
Thanks; some more questions:

What determines what Pixel XL is a VZW model or a Google model? There has to be something that that OEM unlocking option checks for.

Whatever the thing is that determines the model, can it be changed?

What's the difference between fastboot's flashing unlock and unlock_critical options? I initially ran only unlock and was able to mess with TWRP and LOS just fine, but later on, I ran unlock_critical and it did something else and factory-reset my phone/wiped partitions. Originally, unlock showed as already unlocked when I re-run it. unlock_critical didn't say this originally and went ahead and did something, but after that now it says it's already unlocked too if I try to re-run it. I see no different with unlock_critical and can still mess with TWRP and LOS no problem.

Does the Google model has VZW-specific apps? There's 4-5 VZW-specific apps in the App list (have to show System apps), and only one of them (on LOS 15.1) comes disabled (My Verizon Services/com.verizon.mips.services).
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
- Where you bought it and it you cannot unlock the bootloader without a 'hack'.

- I don't know. Read this post by Qu3ntin0:

[Bounty] Verizon Pixel bootloader unlock Post #138

Also read the one above it by LeoTheRomRasta which was the beginning of finding an unlock method for the Verizon Pixel XL.

- The date of your phone fastboot flashing unlock is fo the newer models.

"I initially ran only unlock and was able to mess with TWRP and LOS just fine, but later on, I ran unlock_critical and it did something else and factory-reset my phone/wiped partitions. Originally, unlock showed as already unlocked when I re-run it. unlock_critical didn't say this originally and went ahead and did something, but after that now it says it's already unlocked too if I try to re-run it. I see no different with unlock_critical and can still mess with TWRP and LOS no problem."

People have bricked their phone 'experimenting', consider yourself extremely lucky.

- Yes, the Google model has Verizon apps if your carrier is Verizon.

You're a Senior member that has rooted your Pixel XL and installed a custom rom. :)
[Google Pixel XL Guides, News, & Discussion] Wahoo92583:
Help Needed!

I can successfully get to step 9. HOWEVER, I cannot complete it. After running the adb shell command, restarting my device, browsing a web page, and going to the developer section, I am unable to toggle OEM unlocking... It remains greyed out. I am using a Google Pixel. My provider is Verizon and I'm running Android version 9. The main reason why I want to root my phone is because I just purchased a new car with Android Auto. Rooting my phone will allow me to stream YouTube videos and movies via the CarStream app. Help, please!!
[Google Pixel XL Guides, News, & Discussion] bigmike35:
I read that sometimes it takes 2 wipes for it to work (factory resets) and also you make need to wait a few minutes in that menu (developer options) for it to appear after visiting a website through google chrome.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
If you have a Google Pixel /Pixel XL, why are you using this method to unlock it? This thread is for unlocking Verizon's Pixel / Pixel XL. Look at the first paragraph in the quote
[Google Pixel XL Guides, News, & Discussion] Wahoo92583:
Verizon is the service provider... I have Verizon as my service provider... Google is the company who makes the Pixel... So, I have the Google Pixel on Verizon's network...
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
[MENTION=9669924]Wahoo92583[/MENTION]

That is correct. This guide is not based on the carrier (service provider) the phone is used on but rather the model phone (Verizon).

If yo bought your phone from Verizon you should be using this guide.

If you bought your phone from Google you should be using this guide. [Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76

See #3

Note: Verizon's Pixels bootloader was not unlockable until the hack in this guide was discovered. Google's Pixels bootloader is always unlockable.
[Google Pixel XL Guides, News, & Discussion] Wahoo92583:
OH, cool!!!! I didn't realize there was a difference!! I purchased my phone from the Verizon store and assumed they're one and the same. I guess there's a difference!! Thanks for the link!!
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
[MENTION=9669924]Wahoo92583[/MENTION];

Read my edited post above. You bought your phone from Verizon so don't use the link use this guide.

Redo the steps in the guide but at #8 do

Connect to WiFi,

adb shell am start com.android.chrome

and go to any website really.