possible zero-day for vzw pixel 2 xl root

[SeanAndre03]

My phone was updated to October so I can't do the temp root obviously but I have an idea.
Why not pull those partitions on someone's devices that is bootloader unlocked then push it on your devices
or find a way to go to edl mode then flash the partitions simultaneously.

 

[wolfu11]

Well, do you have one to share?

I might have them what exactly do you need?

 

[1404zone]

I might have them what exactly do you need?

Interested in vbmeta, frp, and misc partitions.

 

[enigma2446]

Interested in vbmeta, frp, and misc partitions.

I have those in .tar and .img

 

[matheusfdelgado]

I BEG YOU guys, do it, please!

 

[enigma2446]

Here

 

[enigma2446]

And

 

[logan2611]

Interested in vbmeta, frp, and misc partitions.

We have already tried changing misc and FRP, no luck.

EDIT: vbmeta partitions are identical to those on my locked device.

 

[enigma2446]

Been finding alot of oemlock trigger stuff in root directory including an apk. Could this help us? I can't decompile .so files but what I can read is it calls upon a particular server and checks info. Not sure if any of this helps.
Here's a link to all that I can related to oem lock

https://drive.google.com/folderview?id=10E3rrj3jFzt0DpXUtPEdfA5v-7ITZN6E

 

[Whoareyou]

Here

Could you pm me your ftm partition? And perhaps your userdata after a reset and triggering oem unlock?

 

[enigma2446]

Could you pm me your ftm partition? And perhaps your userdata after a reset and triggering oem unlock?

Unfortunately I forgot to state that I am on locked bootloader from Verizon

---------- Post added at 08:37 PM ---------- Previous post was at 08:35 PM ----------

Unfortunately I forgot to state im on a locked bootloader from Verizon. My apologies everyone.

 

[elliwigy]

And

are these vbmetas magisk patched or just unlocked bl? if so its probably the same as on locked.. magisk i believe patches it by zeroing it out but since vbmeta is also signed it probably will not boot if dd'd onto a locked bl device since patching it breaks the sig

edit: i see hes on locked verizon lol that doesnt help

 

[enigma2446]

are these vbmetas magisk patched or just unlocked bl? if so its probably the same as on locked.. magisk i believe patches it by zeroing it out but since vbmeta is also signed it probably will not boot if dd'd onto a locked bl device since patching it breaks the sig

edit: i see hes on locked verizon lol that doesnt help

Ya sorry

 

[enigma2446]

Any movement on this? I have temp root and a spare Verizon pixel to test/pull stuff from.

 

[shwise]

Is this project still active? If so, please PM me the telegram link. It seems my PMs aren't sending.

Thanks!

 

[enigma2446]

Is this project still active? If so, please PM me the telegram link. It seems my PMs aren't sending.

Thanks!

Me to please

 

[IcyAgitator]

I have a VZW P2XL > Bootloader Unlocked > Android 10 Sept 5th 2019 Security patch > Build QP1A.190711.020
Buyer code: VR1
Buyer name: GOOGLE_VRZ_128G

Currently running full stock/non root. Would this be of interest?

 

[shwise]

I have a VZW P2XL > Bootloader Unlocked > Android 10 Sept 5th 2019 Security patch > Build QP1A.190711.020
Buyer code: VR1
Buyer name: GOOGLE_VRZ_128G

Currently running full stock/non root. Would this be of interest?

100%! Would you mind explaining how you managed to unlock?

There's another thread under discussions looking for a user with an unlocked bootloader.

Thank you.

 

[IcyAgitator]

100%! Would you mind explaining how you managed to unlock?

There's another thread under discussions looking for a user with an unlocked bootloader.

Thank you.

Ok, so I'm not exactly sure what happened. I had just downloaded the Android 10 update. The phone said it needed to reboot to finish the install. The device turned off like it was going to reboot and install the update as normal. But it never rebooted. It remained in a power off state. I decided to power-on the device. After doing so the device immediately went to the recovery. It sat there in recovery like 30 minutes or so doing nothing. I could not enter a menu setting, nothing. I Hard rebooted the device and the same thing happened. I searched google and found nothing related to this. So I decided to push/flash the last Android 9 update [ 10.0.0 QP1A.190711.020, Sep 2019 ] to the device manually.

I removed the sim card and tray from the device.
I was able to power up the device into the bootloader. From There I I used fastboot to erase; modemst1 , modemst2 , fastboot erase cache, and userdata. Not going to lie. I do not remember if all these commands worked or not.


I then followed the guide here; Pixel 2 XL Images & Directions to flash the image. With the sim-card still removed. I proceeded. After the flashing was complete I powered the device up. Again, not simcard. I was met with the lovely white boot screen with the G. The setup menu followed. I skipped everything. I enabled the developer menu. The OEM lock was greyed out. It read "Connect to the internet or contact your carrier. I connected to the internet via wifi. after about 30 seconds the OEM Lock menu was no longer greyed out. I enabled the toggle. A warning popped up. I agreed.

I immediately rebooted to bootloader. I used this; "fastboot flashing unlock_critical" a warning appeared about unlocking....blah blah blah. The device performed a factory reset. The device then rebooted as normal and there was a disclaimer about the device bootloader being unlocked. After a few seconds it booted into the OS normally. I again skipped all the hoopwa and went directly to enabling the Developer Menu and verifying the Bootloader status. It showed it was still unlocked.

I have not reinstalled the VZW simcard yet. The device it literally stock factory state witht he exception of the bootloader now being unlocked.

So.....that is how this all came to pass. I hope this helps.


**Note** I did not use the " fastboot flashing unlock" because I read it has caused a bootloop to many of devices.

 

[enigma2446]

Ok, so I'm not exactly sure what happened. I had just downloaded the Android 10 update. The phone said it needed to reboot to finish the install. The device turned off like it was going to reboot and install the update as normal. But it never rebooted. It remained in a power off state. I decided to power-on the device. After doing so the device immediately went to the recovery. It sat there in recovery like 30 minutes or so doing nothing. I could not enter a menu setting, nothing. I Hard rebooted the device and the same thing happened. I searched google and found nothing related to this. So I decided to push/flash the last Android 9 update [ 10.0.0 QP1A.190711.020, Sep 2019 ] to the device manually.

I removed the sim card and tray from the device.
I was able to power up the device into the bootloader. From There I I used fastboot to erase; modemst1 , modemst2 , fastboot erase cache, and userdata. Not going to lie. I do not remember if all these commands worked or not.


I then followed the guide here; Pixel 2 XL Images & Directions to flash the image. With the sim-card still removed. I proceeded. After the flashing was complete I powered the device up. Again, not simcard. I was met with the lovely white boot screen with the G. The setup menu followed. I skipped everything. I enabled the developer menu. The OEM lock was greyed out. It read "Connect to the internet or contact your carrier. I connected to the internet via wifi. after about 30 seconds the OEM Lock menu was no longer greyed out. I enabled the toggle. A warning popped up. I agreed.

I immediately rebooted to bootloader. I used this; "fastboot flashing unlock_critical" a warning appeared about unlocking....blah blah blah. The device performed a factory reset. The device then rebooted as normal and there was a disclaimer about the device bootloader being unlocked. After a few seconds it booted into the OS normally. I again skipped all the hoopwa and went directly to enabling the Developer Menu and verifying the Bootloader status. It showed it was still unlocked.

I have not reinstalled the VZW simcard yet. The device it literally stock factory state witht he exception of the bootloader now being unlocked.

So.....that is how this all came to pass. I hope this helps.


**Note** I did not use the " fastboot flashing unlock" because I read it has caused a bootloop to many of devices.

Damn I want to leave work and try this at home lol. Thank you sir.