phaelkyn said:

Pretty sure I already know the answer but I'm going to ask anyway.
I have a new in box Pro 6, from vzw sadly. Never powered it on.
Is there any possibility that I could get the bootloader unlocked prior to it connecting to a network of any kind?

Dirty pipe seems promising but there is no link between it and an unlocked vzw bootloader that I can find. Asking before I set up the device and likely kiss an unlocked bootloader goodbye for the life of this device.

There is none at the moment, and probably won't be for the foreseeable future. My best bet for you is to either just deal with it or resell/trade for an unlocked one.

You can do many things to compromise Android to gain root now, and certainly in the future, but it's just going to be a transient root. The attack surface of the bootloader is small, and most importantly, the knowledge is kept secret. Only Google and hardware vendors have access to the inner workings, and only Google is the one to be able to generate the unlock token for a device to allow it's bootloader to unlock itself.
You could try bruteforcing the token for a device, or the key and algorithm for all devices, but it's a numbers game with the odds so infinitesimally small for you. The number of unlock tokens is massive, more than the number of grains of sand on Earth, more than the number of stars in the universe, more than the number of stars in a billion universes. You can't bruteforce it, you're going to have to find a flaw in the bootloader. Problem is, Google has a vested interest in making sure there are no flaws, as they have already patched several of them before.
Previously you could unlock the Verizon Pixels via a flaw in the bootloader, which was patched. Later you could unlock them again along with the Verizon Pixel 2 due to an oversight on Google's part with them handing out unlock tokens, which was also patched. That's where it ended, there haven't been any exploits or oversights since.

It would be nice for an exploit to be discovered, because regardless of the differences in the unlockable variants versus the permanently locked variants, they are all going to be the same if (and a guaranteed when) Google is no longer is generating unlock tokens (read: they cease to exist or their servers go down.)

Which is actually the current situation of my Pixel 6a. It's unlockable, but I can't unlock it, because Google hasn't begun creating unlock tokens, because I got it two days before launch.

Namelesswonder said:

There is none at the moment, and probably won't be for the foreseeable future. My best bet for you is to either just deal with it or resell/trade for an unlocked one.

Thanks, that is what I figured. It's still a tough pill to swallow.

And thanks for the larger context, too.

Az Biker said:

I seriously doubt the "60 day sim unlock" allows the bootloader to be unlocked, otherwise we'd have a ton of VZW variant threads filled with development, and devices that are 61 days old, rooted, and running custom Roms.

But we don't. We don't have even have any developers working on VZW devices, regardless of age. So deductively thinking, the "60 day sim unlock" doesn't sound like it's currently an option.

Just my .02 (USD) worth

The reason Verizon can easily unlock phones isn’t from their own choosing, it’s bcuz the FCC sold them a bunch of bands and one of the requirements with the sale was to allow users the freedom of choice and go with any carrier they chose hence them not carrier locking phones. This was way back before they even had the 60 day rule, Verizon phones came unlocked out of the box.. I’m no XDA writer, just a plain old dude that’s messed around with phones since the turn of the century. Your rant is a broken record that we see in every Verizon bootloader thread on every device here. There’s always someone who made the mistake and bought a Verizon device only to be butthurt when they discover they’re locked the funk down. What’s surprising is your lengthy resume here combined w/ the vast experience you say you have, yet still made that boo-boo.. You clearly didn’t write anything on Verizon, too bad, so sad.. We usually these sort of out bursts from newbies.. A few of them were pretty determined too, emailed everyone they could at Verizon hoping to over turn the way they conduct their business, only to be simply ignored.. womp womp..
The smarter ones gave up and bought an unlockable device.. curious on what an experienced XDA column writer would do,
besides starting to read what others here also wrote…?

Talysdaddy said:

The reason Verizon can easily unlock phones isn’t from their own choosing, it’s bcuz the FCC sold them a bunch of bands and one of the requirements with the sale was to allow users the freedom of choice and go with any carrier they chose hence them not carrier locking phones. This was way back before they even had the 60 day rule, Verizon phones came unlocked out of the box.. I’m no XDA writer, just a plain old dude that’s messed around with phones since the turn of the century. Your rant is a broken record that we see in every Verizon bootloader thread on every device here. There’s always someone who made the mistake and bought a Verizon device only to be butthurt when they discover they’re locked the funk down. What’s surprising is your lengthy resume here combined w/ the vast experience you say you have, yet still made that boo-boo.. You clearly didn’t write anything on Verizon, too bad, so sad.. We usually these sort of out bursts from newbies.. A few of them were pretty determined too, emailed everyone they could at Verizon hoping to over turn the way they conduct their business, only to be simply ignored.. womp womp..
The smarter ones gave up and bought an unlockable device.. curious on what an experienced XDA column writer would do,
besides starting to read what others here also wrote…?

Click to expand...

Think you're directing your unpleasantries at the wrong person.

Talysdaddy said:

You clearly didn’t write anything on Verizon, too bad, so sad.. We usually these sort of out bursts from newbies.. A few of them were pretty determined too, emailed everyone they could at Verizon hoping to over turn the way they conduct their business, only to be simply ignored.. womp womp..
The smarter ones gave up and bought an unlockable device.. curious on what an experienced XDA column writer would do,
besides starting to read what others here also wrote…?

Click to expand...

Not sure who this condescending, self adulating nonsense was intended for, but it certainly isn't me.

JR_44 said:

Would DirtyCred CVE-2022-2588 and it's higher privileges make this possible?

Assuming the Pixel is vulnerable, these exploits have only been useful for temporary root access. Sometimes only very narrow escalated access.

Maybe someone can be bold and try to rewrite the build.prop to allow OEM unlocking, but all of this is insanely risky and inviting permanent bricks.

electronika said:

The thing I hate most about this situation is how badly Verizon even tells people about this. I've asked their support about this multiple times and they ALWAYS say it will be unlocked after multiple days... even if you clarify you mean OEM unlocking. Frankly if I didn't suspect it enough to find this thread I would have bought the phone and been disappointed. The whole thing sucks because carrier deals are always better than Google store trade-ins, but no root is a dealbreaker.
View attachment 5728975

Unfortunately, chat support at Verizon does not focal with the engineers of google nor verizon themselves. They don't understand this because the phone is bootloader locked and can't be unlocked by Verizon's direction. So their cue cards for customer service don't even touch this issue. They have no clue and the best way to know is by going to XDA. I am not sure if google chat can confirm that with you. I think it will be hit or miss with their chat support.

electronika said:

The thing I hate most about this situation is how badly Verizon even tells people about this. I've asked their support about this multiple times and they ALWAYS say it will be unlocked after multiple days... even if you clarify you mean OEM unlocking. Frankly if I didn't suspect it enough to find this thread I would have bought the phone and been disappointed. The whole thing sucks because carrier deals are always better than Google store trade-ins, but no root is a dealbreaker.
View attachment 5728975

Let me know what happens after 60 my days, just got my vzw pixel 7 pro

Talysdaddy said:

The reason Verizon can easily unlock phones isn’t from their own choosing, it’s bcuz the FCC sold them a bunch of bands and one of the requirements with the sale was to allow users the freedom of choice and go with any carrier they chose hence them not carrier locking phones. This was way back before they even had the 60 day rule, Verizon phones came unlocked out of the box.. I’m no XDA writer, just a plain old dude that’s messed around with phones since the turn of the century. Your rant is a broken record that we see in every Verizon bootloader thread on every device here. There’s always someone who made the mistake and bought a Verizon device only to be butthurt when they discover they’re locked the funk down. What’s surprising is your lengthy resume here combined w/ the vast experience you say you have, yet still made that boo-boo.. You clearly didn’t write anything on Verizon, too bad, so sad.. We usually these sort of out bursts from newbies.. A few of them were pretty determined too, emailed everyone they could at Verizon hoping to over turn the way they conduct their business, only to be simply ignored.. womp womp..
The smarter ones gave up and bought an unlockable device.. curious on what an experienced XDA column writer would do,
besides starting to read what others here also wrote…?

Click to expand...

I need to follow up on this later with my documentation on why they did it (you're right) but they have no excuse anymore

sensation4gking said:

Let me know what happens after 60 my days, just got my vzw pixel 7 pro

That's only SIM, won't happen. OEM toggle for unlock CAN be connected, as T-Mobile and AT&T do, but Verizon has a policy against it