OEM Unlock Official Verizon Google Pixel 2 XL (WORKING!) Warranty Replacement

hallr88 · Oct 3, 2018

Started with device on July 5th security patch Android Oreo 8.1. 100% Verizon device. Got replacement phone in the mail. No SIM inside. Turned it on. Plugged it in to a computer. Skipped past everything on setup. Turned on Developer options. OEM Unlock was grayed out.

Turned off automatic system updates in dev options. Turned on USB Debugging. Keep screen awake while charging. Ran ADB "adb shell pm uninstall --user 0 com.android.phone". Turned on wifi and waited a couple minutes in the chrome browser. Returned to Developer options and OEM Unlock was no longer grayed out. Ticked it.

Kept phone running for a few minutes. Turned device off and booted to fastboot. Still locked. Returned to system from bootloader. OEM Unlock still blue. Let apps update and also logged into Google account. Noticed OEM Unlock was staying unlocked through a couple reboots.

Decided to upgrade to Pie. Did it OTA. OEM Unlock stuck through the update. Shut down phone from system. Once phone was off I held down power button and the volume down button to take me to Fastboot mode. Ran "fastboot flashing unlock". BOOM! Got the the screen to say yes or no to bootloader unlock.

Device was erased because I chose yes. OEM Unlock grayed out again but in unlocked position? Hmm...ok with me. The strangest thing happened when I checked my IMEI when I was done. I had checked before I started also and I could have sworn there was different information than what I ended up with at the last check. Im tired..maybe just trippin out. The OEM Unlock toggle is available to toggle again.

v12xke · Sep 30, 2018 at 1:53 PM

hallr88 said:
Started with device on July 5th security patch Android Oreo 8.1. 100% Verizon device. Got replacement phone in the mail. No SIM inside. Turned it on. Plugged it in to a computer. Skipped past everything on setup. Turned on Developer options. OEM Unlock was grayed out.

Turned off automatic system updates in dev options. Turned on USB Debugging. Keep screen awake while charging. Ran ADB "adb shell pm uninstall --user 0 com.android.phone". Turned on wifi and waited a couple minutes. Returned to Developer options and OEM Unlock was no longer grayed out. Ticked it.

Kept phone running for a few minutes. Turned device off and booted to fastboot. Still locked. Returned to system from bootloader. OEM Unlock still blue. Let apps update and also logged into Google account. Noticed OEM Unlock was staying unlocked through a couple reboots.

Decided to upgrade to Pie. Did it OTA. OEM Unlock stuck through the update. Shut down phone from system. Once phone was off I held down power button and the volume down button to take me to Fastboot mode. Ran "fastboot flashing unlock". BOOM! Got the the screen to say yes or no to bootloader unlock.

Device was erased because I chose yes. OEM Unlock grayed out again but in unlocked position? Hmm...ok with me. The strangest thing happened when I checked my IMEI when I was done. I had checked before I started also and I could have sworn there was different information than what I ended up with at the last check. Im tired..maybe just trippin out.

Go to this link http://www.imeipro.info/check_lg.html and plug in your IMEI number. What does it say under buyer code and buyer name? Don't stop with the unlock command, you need to also unlock_critical. This will also wipe your device again but it is needed to flash the bootloader and to be "fully" unlocked.

hallr88 · Sep 30, 2018

Same site wrong checker

v12xke said:
Go to this link http://www.imeipro.info/check_lg.html and plug in your IMEI number. What does it say under buyer code and buyer name? Don't stop with the unlock command, you need to also unlock_critical. This will also wipe your device again but it is needed to flash the bootloader and to be "fully" unlocked.

\

https://imgur.com/a/mEKLSbZ

I didnt have to do the unlock_critical. Just the regular one.

siggey · Sep 30, 2018 at 6:15 PM

So is finally unlocked? Maybe we can try after a factory reset on Pie?

hallr88 · Sep 30, 2018

siggey said:
So is finally unlocked? Maybe we can try after a factory reset on Pie?

I've already done a few factory resets in Pie and its holding tough.

hallr88 · Oct 1, 2018 at 12:15 AM

siggey said:
So is finally unlocked? Maybe we can try after a factory reset on Pie?

I tried many ways to get in with Pie. If you can do it. Props

djmouse · Oct 1, 2018

hallr88 said:
I tried many ways to get in with Pie. If you can do it. Props

I really think it can be done ,9nce that toggle is cooperating ,there is like there's some other step to enforce that toggle,like doing an OEM_UNLOCK permission or state change in the bootloader.I ran fastboot getvar all when toggle was enabled,there is a OEM unlock id =yes, how to pull that id idk,but I think there's still a way.

Aslo I inserted the sim with the OEM toggle enabled,but my sim was never recgonized,I guess uninstalling the com.andriod.phone is the radio,or modem? I feel like I was as close as ever just missing something Stoopid.

hallr88 · Oct 1, 2018 at 10:56 AM

djmouse said:
I really think it can be done ,9nce that toggle is cooperating ,there is like there's some other step to enforce that toggle,like doing an OEM_UNLOCK permission or state change in the bootloader.I ran fastboot getvar all when toggle was enabled,there is a OEM unlock id =yes, how to pull that id idk,but I think there's still a way.

Aslo I inserted the sim with the OEM toggle enabled,but my sim was never recgonized,I guess uninstalling the com.andriod.phone is the radio,or modem? I feel like I was as close as ever just missing something Stoopid.

I tried as many permissions that I could think of when I got to that point. When I uninstalled the system app I realized that I had to get it back eventually so I did a factory reset with the toggle on and it stuck through it. I was like omg. lol Keep at it!

I also had the SIM unrecognized when I uninstalled com.android.phone. Stopped the connection to Verizon servers I think. Spoof server? JK. There's gotta be some type of encryption in whatever it says to Verizon.

leondestiny · Oct 1, 2018 at 12:29 PM

i will try this if it is indeed working.

djmouse · Oct 1, 2018 at 1:17 PM

hallr88 said:
I tried as many permissions that I could think of when I got to that point. When I uninstalled the system app I realized that I had to get it back eventually so I did a factory reset with the toggle on and it stuck through it. I was like omg. lol Keep at it!

I also had the SIM unrecognized when I uninstalled com.android.phone. Stopped the connection to Verizon servers I think. Spoof server? JK. There's gotta be some type of encryption in whatever it says to Verizon.

I never did a factory reset when the toggle was in the blue,I figured that would reinstall com.andriod.phone.a factory reset will make you have to.go back and enable Dev options ,and your saying OEM toggle was on? I'm not sure that even happens on a Google varient .

hallr88 · Oct 1, 2018 at 9:26 PM

djmouse said:
I never did a factory reset when the toggle was in the blue,I figured that would reinstall com.andriod.phone.a factory reset will make you have to.go back and enable Dev options ,and your saying OEM toggle was on? I'm not sure that even happens on a Google varient .

I think I may have updated to Pie before I actually did the factory reset. I knew I should have recorded my screen. Ok, I remember. I did the update to see if it would give me back my phone use and it didn't. So I ended up saying just factory resetting in Pie and it stuck and gave me phone use.

gcodori · Oct 2, 2018 at 6:43 PM

Anyone else try this, it's been two days...

Sent from my Pixel 2 XL using Tapatalk

shooterlgk · Oct 2, 2018 at 10:59 PM

gcodori said:
Anyone else try this, it's been two days...

I'm going to try today

---------- Post added at 10:59 PM ---------- Previous post was at 10:59 PM ----------

I have a replacement waiting for me at home

shooterlgk · Oct 3, 2018 at 1:12 AM

so the device is on 8.0..tried the method and no go

hallr88 · Oct 3, 2018 at 1:15 AM

shooterlgk said:
so the device is on 8.0..tried the method and no go

Dang. Shoulda Skyped r sumthin. Hate good thoughts that come a little too late.

shooterlgk · Oct 3, 2018 at 1:17 AM

hallr88 said:
Dang. Shoulda Skyped r sumthin. Hate good thoughts that come a little too late.

well i still have it without a sim..i havent quit yet

hallr88 · Oct 3, 2018 at 1:48 AM

hork-bajir12 · Oct 3, 2018

Tried it on pie, no sim, but I was active before. Oem unlock became blue, I could toggle it... But upon going into fastboot, all I got was when doing "fastboot flashing unlock" or unlock_critical was "flashing not allowed

Update: left it charging all day, upon checking up again after hours, the toggle became grey again.

Update 2: Indeed, all i get is FAILED (remote: Flashing Unlock is not allowed) and upon reboot oem unlock becomes grey again

shooterlgk · Oct 4, 2018 at 2:16 AM

hork-bajir12 said:
Tried it on pie, no sim, but I was active before. Oem unlock became blue, I could toggle it... But upon going into fastboot, all I got was when doing "fastboot flashing unlock" or unlock_critical was "flashing not allowed

Update: left it charging all day, upon checking up again after hours, the toggle became grey again.

Update 2: Indeed, all i get is FAILED (remote: Flashing Unlock is not allowed) and upon reboot oem unlock becomes grey again

So u had service on ur phone already, and u tried his method and u got that far?

hork-bajir12 · Jul 4, 2013 19 5 0

shooterlgk said:
So u had service on ur phone already, and u tried his method and u got that far?

Had but not for couple months.

OEM Unlock Official Verizon Google Pixel 2 XL (WORKING!) Warranty Replacement

Did it work for you? Need fresh Pixel (i think)(NO SIM) July patch which is 8.1

Yes

No

Member

Senior Member

Member

Senior Member

Member

Member

Senior Member

Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Member

Attachments

Senior Member

Member