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

[baj24]

Wait I just checked my imei number in the imeipro.info/check_lg.html, sorry if i am dumb in asking this but i forgot the verizon model name. It says the buyer code is VRX and the buyer name is GOOGLE_VRZ_64G. Is this a verizon model or a google one?

Verizon

 

[RyuHacks]

I have an idea, since we are still allowed to sideload an update file, what if we modify the update file to allow oem unlocking?

 

[CyberpodS2]

I have an idea, since we are still allowed to sideload an update file, what if we modify the update file to allow oem unlocking?

I'm fairly confident you need a key to sign the update file. Without that you're shat outta luck...

Sent from my Pixel 2 XL using XDA Labs

 

[Hexlay]

My only hope is GSI... i doubt we can modify image and boot, but booting alone in generic plain aosp should remove verizon apps that controls switch, no? however i have not read it in details, so idk if it needs unlocked boot

 

[RyuHacks]

Ok I'll try putting the contents of the magisk zip into the official signed ota update zip and sideload it.

 

[RyuHacks]

Nevermind that did not work it needs the signed key.

 

[pixelgasm]

Is this will work with android Q?

 

[wolfu11]

Hey all. 2 coworkers and I had our 2 XL's warranty replaced by Verizon. I'm not sure if it's dumb luck, an actual work around or Verizon just goofing up and not submitting the MEID's to Google for BL lock. But I now have 3 Pixel 2 XL at my desk warranty replacements from Verizon that are bootloader unlocked and rooted.

First booted without sim, OEM Unlocked - grayed out. Factory reset - added sim, the moment the phones showed activated I removed the sim and put them in the old phones. Went thru setup and while enabling USB debugging I noticed that OEM unlock was able to be selected. Rebooted to fastboot and was able to fastboot flashing unlock_critical on all 3.

Well I just unlocked a bootloader on a Verizon refurb in this similar fashion but when I went to check the IMEI it is indeed a Verizon version. But what threw me off is the manufacturing date this phone is pretty much brand new maybe Google decided to not honor Verizon in this case LOL. It came with a may 2019 build

 

[CyberpodS2]

I would think it's more likely they are getting to the end of stock and either only had Google versions or it's easier to keep one version on hand?? Cool either way! Heh what do I know??

Sent from my Pixel 2 XL using XDA Labs

 

[wolfu11]

I would think it's more likely they are getting to the end of stock and either only had Google versions or it's easier to keep one version on hand?? Cool either way! Heh what do I know??

Sent from my Pixel 2 XL using XDA Labs

I thought they stop selling them in April but yet I get a "refurbished" that was manufactured in July of this year it's only 2 months old so definitely not a refurb.
But yeah same here what do I know. I'm just happy to get it bootloader unlocked. Well I also have a Google version. This one is my back up.

 

[Some1CP]

This could be used to get root access and unlock the bootloader.

 

[CyberpodS2]

This could be used to get root access and unlock the bootloader.

If indeed that is the case, anyone with a Verizon phone should consider what and how they take updates until this is proven out one way or another...

Sent from my Pixel 2 XL using XDA Labs

 

[Hexlay]

This could be used to get root access and unlock the bootloader.

Yep, great chance if someone actually makes it...

 

[sgtslaughter64]

Yep, great chance if someone actually makes it...

Wish I knew more about programming

 

[Hexlay]

https://forum.xda-developers.com/showpost.php?p=80469545&postcount=6

temporary root has already been achieved !

 

[pixelgasm]

@Hexlay what do you mean temporary? It will gone after restart? It will brick the phone?

 

[cammykool]

https://forum.xda-developers.com/showpost.php?p=80469545&postcount=6

temporary root has already been achieved !

I'll disable automatic updates then!

Sent from my Pixel 2 XL using Tapatalk

 

[Hexlay]

@Hexlay what do you mean temporary? It will gone after restart? It will brick the phone?

Not an expert, but i don't think it will go away (unless you install October OTA) or brick anything, but probably you should ask the guy who made it.

 

[Rumold]

Correct me if I'm wrong.
After checking the following file (/data/misc/update_engine_log/update_engine.19700110-053335 ; you'll need root for that and yours could be different than mine), it shows up that the /dev/block/sda8 (which is the B system in the A/B system update), has been modified, even with automatic updates disabled (from long time ago not just after the October OTA) and without accepting anything. Would the update apply on reboot unless I modify this block device?

Thanks in advance!

 

[cammykool]

Edit:
You should be fine with that unchecked.