yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] roirraW "edor" ehT:
Every Verizon variant of phones is locked down, and certainly, historically different models of them have been able to be either unlocked, or most of the time as far as I've experienced a workaround (security vulnerability) to unlocking was found (IIRC, the Stump method on LG phones worked this way), and the (again, as far as I'm aware) single time(s) that a Verizon phone was able to be bootloader unlocked as if it was made to be able to do so from the get-go, more or less: The Pixel 1 on Android 7.10 or below, and there is some foreign hacking method which can exploit some secret vulnerability if you're willing to pay to still be able to bootloader unlock the Pixel 1.

In my opinion, Samsung limits are even worse than the carrier-imposed limits, as Samsung keeps their phones from being bootloader unlocked on every U.S. Carrier, and even the direct from Samsung bought in the U.S. factory carrier unlocked model, but please correct me if I'm wrong. I only know the experience with the phones I've actually owned and what I remember from reading about others' experiences, however. The Exynos-based versions of Samsung phones are able to be bootloader unlocked at least in most countries, and again IIRC, some Snapdragon-based Samsungs in one or a few select countries too. Sony officially allows their bootloaders to be unlocked, but they purposefully and permanently gimp your phone's features if you do - and some other OEMs do similar, I'm given to understand.

I know it's frustrating about Verizon. Besides no longer buying carrier-specific models of phones, I no longer use Verizon as well, but it sucks for those who really need the carrier incentives.
[Google Pixel 6 Pro] lucky_strike33:
NOt every verizon phone, The samsung s20 bootloader was able to be unlocked.
[Google Pixel 6 Pro] roirraW "edor" ehT:
As it came without some temporary trick or vulnerability someone was able to take advantage of?
[Google Pixel 6 Pro] ballin2much:
What do you mean by APN related apps? I was wondering what exactly I needed to freeze, since earlier I froze something I shouldn't have and it bootlooped my phone.
[Google Pixel 6 Pro] tmessy:
Same... Lol
[Google Pixel 6 Pro] theportal2:
Ya calling bs on that. I got a verizon pixel 4a 5g running dec 5 2022 patches and your method is not working for me.
[Google Pixel 6 Pro] theportal2:
Mine showing your phone at the bootloader screen please
[Google Pixel 6 Pro] Yeedatoy:
Sure... Give me just a moment
[Google Pixel 6 Pro] Yeedatoy:
This?
[Google Pixel 6 Pro] Yeedatoy:
One more
[Google Pixel 6 Pro] Yeedatoy:
My advice would be to use the universal Android debloater tool on here that runs on Windows. The developer did an amazing job and there is a description under the majority of the apps so you know whether or not they're safe to remove. There wouldn't be any difference between removing them and freezing them. Honestly, I didn't expect to come on here and state what I did without everyone completely doubting me... I've seen these threads way too many times to be unfamiliar with how they go. That being said, check my XDA history, and I'm not saying this to you directly, but to anyone who reads this in general. I know it's under my response to you but that's why I want to clarify. I have absolutely nothing to gain by coming on here bullshitting. We previously thought that only the carrier could enable or disable this remotely, or possibly even Google themselves through some sort of software that's tied into the work config app /device setup app. That app definitely contains something...whether it's a script permissions..etc that directly affects the OEM unlock button which is why I mentioned to leave that app enabled. I even tried using app ops to set permissions on that specific app to "ignore" which is supposed to change the way the information is transferred from that app back to the carrier, but that didn't work. The one thing I have learned from this though that gives us a bit of information that we didn't have previously, is that it can be done without Google, or Verizon sending some sort of signal to the device itself in order to make it unlockable.
[Google Pixel 6 Pro] ballin2much:
Just for the record, I just gave this a try and no luck (Verizon Pixel 7). Wonder if it's specific to your model or is due to the fact you were originally on xfinity.
[Google Pixel 6 Pro] jamescable:
Because of the new EU/ U.S.A. law on owning a device and being able to repair it, isn't Verizon supposed to legally allow bootloader unlock now?
[Google Pixel 6 Pro] Strephon Alkhalikoi:
Source? The only right to repair law I know of in the US is in New York and is laden with poison pill provisions. The EU's laws do not apply to the US so that won't cause Verizon to budge.
[Google Pixel 6 Pro] jamescable:
Actually EU laws do apply to U.S, because that's where the phones are made....overseas
[Google Pixel 6 Pro] Yeedatoy:
I contacted Xfinity because I figured since they are a Verizon MVNO, they would have the access to the same resources, especially considering there was that situation on eBay where a bunch of people ordered supposed unlocked phones that ended up being locked to Xfinity. I can't really talk about this subject because it violated XDA rules so I believe that post was taken down, but I figured that maybe xfinity's customer service could unlock my bootloader if I said the correct things. I can't be anymore specific than that though, as I told the moderator, I wouldn't make the same mistake twice. I honestly think it has something to do with the December patch specifically, as if you check on Google's website now you can see that there was some type of vulnerability in the bootloader that has been patched, in the section where the developer bootloader images can be downloaded. My phone was never actually on Xfinity, but even so.... They were still able to pull up My devices information, and told me they could unlock it, and if everything looked okay. It would be done in less than 48 hours but that never ended up happening
[Google Pixel 6 Pro] Yeedatoy:
Interestingly, there was one thing in particular that I suspected May be true and is the reason I decided to make that call to Xfinity, is the fact that Verizon will say it can't be done but a Verizon MVNO said the complete opposite.... And all he was given was my IMEI number, I did not give any actual history of the device.
[Google Pixel 6 Pro] Yeedatoy:
From most of the responses I've seen though, Verizon typically claims they can't unlock the device. They will carrier unlock it but claim that they cannot give access to the OEM unlock switch. They tried to put that all on Google. In my case, even after I bootloader unlocked it, it still give me a message telling me to contact the carrier when I tried to put a different E-Sim on the device. After a bit of screwing around, I was able to get around that eventually and to add to the Insanity of it... Now the remaining balance I owed on the device is gone and I even went as far as to see what would happen if I tried to purchase another device and open a new line... And I got to the point where all I had to do was submit the payment and I could have picked up another phone with a new line.
[Google Pixel 6 Pro] theportal2:
Seems your running diffrent firmware then me
[Google Pixel 6 Pro] Nergal di Cuthah:
Your source says when devices reach end of life, it could be argued in court that a bootloader can be unlocked, doesn't say it'd be successful just arguable. I think the people in this thread want something sooner than five(?) years from now.
[Google Pixel 6 Pro] Strephon Alkhalikoi:
Uhh...no. That's not how this works. At all. EU directives cover where the device is sold, not made.
[Google Pixel 6 Pro] kocheko:
i read most of the replies and im still tryin to figure it out where i stand with my phone. i have i pixel 4xl brand new, it does not says VERIZON or any other carrier , it does not bring any bloatware, but still im unable to unlock oem (it is greyed out with message "Connect to the Internet or contact your operator".) i read if the IMEI starts with 35 it is a verizon pixel , and mine does . im on android 11 , my question...am i screwed? should i do ota update or it is better to wait for a workaround to be realeased
[Google Pixel 6 Pro] kocheko:
and also i would put mine to service if it helps since i paid not so much for the piece of junk (as i said it is a pixel 4xl)

will this do anything? if i leave the lock bootloader unchecked?
[Google Pixel 6 Pro] Strephon Alkhalikoi:
If your device is a Verizon model you're likely up s*** creek without a paddle. Verizon has been pretty diligent in ensuring the bootloaders can't be broken in to since a bootloader was issued back in the 2XL days with a bug that allowed for unlocking. You might as well update, because exploits I don't think exist for your device.
[Google Pixel 6 Pro] TheSayaMan:
Worthless because you can't flash firmware unless the bootloader is unlocked in the first place. This is why I stopped buying Verizon phones. Your screwed and that's that.
[Google Pixel 6 Pro] Prysmalyte:
I don't think it's just the SIM. I wouldn't be surprised if Verizon has a handshake agreement with Google and has something in their devices different from other carriers.

I remember watching the first Pixel be released, and immediately afterwards, I looked at it, and while Google Fi was just taking off as well (good opportunity to use it, anyway,) Verizon was the only national carrier to sell the Pixel out of the gate.

I don't think anyone got their hands on a Pixel outside of Verizon and Google themselves until almost the release of the second one. And even the Google version of the Pixel, I had heard from others, was basically telling other carriers to suck one until the market was opened, before magically resolving themselves (the Google version was supposed to work with "major carriers, with limited availability," but until Verizon lost exclusive access, the Google version had explicit trouble connecting to anything but Verizon, to the point people were complaining about the device functionality. So basically your choice was Verizon, or Google wrapped by Verizon.)

So I wouldn't be surprised at all if the Verizon devices had something tagging along with them to disable OEM. It isn't like this is impossible; Apple of all companies has been known to make different models of the same indistinguishable iPhone model, because they have been sued in some countries for illegal practices (before they lost the charger war, they actually lost two suits in France and Italy, if I remember correctly, over Planned Obselesence, which is actually illegal in those countries and the EU, unlike the US where morals are a joke and the law is a fairy tale.) So those countries get better iProducts than others, despite looking the same, because they use non-obsolete parts in order to comply with the law.

So Verizon, since they obviously had enough of a good relationship to be the first carrier to open the Pixel line, might have asked Google to throw a chip in their devices for their needs. And Google did it, because they're such good friends.

Welcome to the Corporate Tech Industry.
[Google Pixel 6 Pro] Strephon Alkhalikoi:
It's not a chip. If bought from Verizon the bootloader is locked from the start. Insert a Verizon SIM into a new unit bought directly from Google and power it on? The unit phones home, reports that the device is on the Verizon network, and a payload is sent to the unit that encrypts the bootloader and disables the OEM unlocking toggle.

So...if you bought an unlockable unit directly from Google I wouldn't insert the SIM until AFTER you've unlocked the bootloader.
[Google Pixel 6 Pro] jamescable:
Didn't happen here. I have Verizon esim
[Google Pixel 6 Pro] Strephon Alkhalikoi:
Good for you. I wouldn't take that risk.
[Google Pixel 6 Pro] georgesurgeon:
have you done it?
[Google Pixel 6 Pro] TheSayaMan:
Actually, if you bought the unlocked version from Google, you can unlock bootloader no matter the carrier, but if you buy the Verizon version, you can't.
[Google Pixel 6 Pro] adag1:
Hello guys, I became the proud owner of the Verizon version of the pixel 6. Actually, since 2013 I have been unlocking phones, and the fact that the pixel is not unlockable scares me.Naturally, I would like to unlock this miracle, but I read that with the latest updates this is impossible. I began to look for answers myself, why this is happening and how to solve this problem. What I found: see screenshots.

Yes, I understand that now it is not possible to freeze this application through adb and, as a result, to enable the item to be unlocked in the developer settings. Because the command pm uninstall isn't working with December update. However, in fact, we need to disable one activity of the simlock and remove the permission to block oem. Tried do it through adb, but unsuccessfully. What else can do this? I tried to find some option through shizuku, but also so far unsuccessfully.

Perhaps there are experts on the forum who can develop my idea, and we can find a solution ...
[Google Pixel 6 Pro] w_tapper:
tbh i dont understand why people buy verizon phones anyways, cant you just buy it from google and use a sim from verizon or something?
[Google Pixel 6 Pro] TheSayaMan:
There is no solution other than buying the Google store unlocked version
[Google Pixel 6 Pro] adag1:
I'm from Belarus, and we can only buy from small noname shops, because pixels not officially sold ... Oh yes, and in general, I initially had no idea that the phone could be tied to Verizon or at2t and etc.
[Google Pixel 6 Pro] w_tapper:
in australia, even when you buy from a carrier, the bootloader can be unlocked, I bought mine outright from a technology store and just used my old sim in it
[Google Pixel 6 Pro] BROKEN1981:
At least with TMobile variant, it's sim unlock that unlocks the bootloader
[Google Pixel 6 Pro] Nergal di Cuthah:
You of course mean sim unlock allows the bootloader to unlock not immediately unlocks.

Vzw variants are already sim unlocked and cannot have bootloader unlocked ever
[Google Pixel 6 Pro] BROKEN1981:
Verizon sucks. Glad I'm on TMobile.

Next time I am buying from the Google store only because I need 512GB version.
[Google Pixel 6 Pro] w_tapper:
does vodafone exist in the us?
[Google Pixel 6 Pro] BROKEN1981:
Never heard of it
[Google Pixel 6 Pro] TheSayaMan:
Maybe for unlocked bootloader, otherwise T-Mobile sucks more than Verizon. I'm a truck driver and too many dead spots with T-Mobile's network. Traveling is a nightmare on T-Mobile!!! I tried them to save money 5 to 6 years ago. Big mistake!!!
[Google Pixel 6 Pro] w_tapper:
oh nvm maybe it's just an Australia thing
[Google Pixel 6 Pro] Nergal di Cuthah:
I think they have/had a smalltime pay as you go (burner phone) operation
[Google Pixel 6 Pro] w_tapper:
in Australia its just an average mobile provider, decent prices, meh coverage but as long as you live near a city its ok
[Google Pixel 6 Pro] huztek:
Well since I have found zero threads about AT&T bootloader unlock. Does anyone have any solution? Whenever I put in any other sim, it just says that unable to use any other sim apart from AT&T. So I just factory resetted my phone and blocked the device setup app front accessing the internet. Not a permanent solution but I'd like to know my options. Any chance of me working around a carrier unlock or possibly bootloader unlock? I bought this phone outside the US, and to my stupidity I never factored in that this was also a possibility that it's carrier locked. Learned the hard way, depressed that I've kinda wasted my money
[Google Pixel 6 Pro] vonDubenshire:
Because 99.999% of people never need OEM unlock, or even know what it is.

Otherwise, no one would buy a Samsung in the USA
[Google Pixel 6 Pro] vonDubenshire:
AT&T allows bootloader unblock, but it looks like your phone is SIM locked.

Do you still have a device payment on it?

Did you buy it from someone that could have had an installment plan on it but now they've stopped paying it?

Contact AT&T.
[Google Pixel 6 Pro] vonDubenshire:
@Prysmalyte is correct because that is how the bootloader is locked.

If you go dog into the Android boot source code, you'll find the verification that Android does to decide if OEM Unlock toggle is allowed by the user.

The OEM and the carrier have a say in the bootloader unlock toggle. This is part of what locks the bootloader by other brands like Samsung, on top of having Knox stuff built on top of it.

Verizon has a policy that all phones sold through them must be bootloader locked and they refuse to ever have a way to unlock them.

Other carriers like AT&T and T-Mobile sell Pixels through their own stores, however, they have the policy that many other carriers and phone OEMs have had: the bootloader can be unlocked at request and/or when the device is paid off!

Again, dig into the source code at the boot level for Android and you'll start to see the OEM unlock command/verification.

The Verizon model doesn't lock upon connection to the internet or a SIM activation, it's set at the factory. (Yes, this wasn't 100% true for a few times that the OEM unlock was able to toggle due to mistakes in Android or the manufacturing line, but those were flukes.)

I have a long post I've been writing about why Verizon did all this -- it's SO complex and a battle that will be hard to win because most people don't care.

Verizon basically set this policy before 2012 because of people rooting their phones to get around limitations on data plans & hotspots.

This was a big deal in the 2009-2011 era.

However, it isn't a thing anymore because the cellular technology we use isn't the same and now Verizon has no reason to fear anything like that.

If you look at the Droid-Life guy's website, he and some others raised hell in 2012 and got Verizon's executive to write a public letter explaining that "bootloaders are locked to guarantee safety of our network" etc etc.

Well, that clearly isn't true anymore (and actually wasn't then anymore, either) because they wouldn't allow an unlocked device to be on their network if you could threaten them in any way.

Issue is: gotta spend many hours raising hell with a good, undeniable case that Verizon can't refute to get their attention. That's a huge effort for someone like me to do for free, lol
[Google Pixel 6 Pro] ntice:
I don't believe so...Pixel doesn't have different SKUs for different carriers. It's 100% the same phone, hardware and firmware. The difference isn't in the phone, it's in the IMEI database shared between the carriers and Google.
[Google Pixel 6 Pro] genesan:
Okay so I have a lot of experience rooting flashing and restoring phones and I'm active in a lot of these forums. I have actually never purchased a phone through a carrier before (no reason ) and so normally when I got a new phone in the past ,"OEM Unlock" is immediately available, in Developer Settings" and with the exception of Motorola, I've never had to have to get any token or anything .

Recently I picked up a moto 15gsuw and as soon as I try to root it, in the first day that I have it, I noticed " Options" was greyed out.

I called and spoke to a pretty decent tech for a little bit and he told me that the "OEM Unlock Option" becomes available after 60 days. Then about 5 days later I try it, out of boredom, and the "OEM Unlock " option is no longer greyed out, it is available. I immediately toggled it and tried to unlock the bootloader by first retrieving the unique token from Motorola dot com slash bootloader and it still allows me to click "Get My Token" or whatever but when I do I'm taken to a blue background page kinda similar to the Motorola webpage before it, but all it says is this device is not eligible for unlock. I haven't tried the whole fastboot unlock just yet...in case it's a matter of voiding the warranty, but I doubt it's going to work. I don't understand why that option would come available if it isn't going to work..lol...dangut.

I just figured I should jump in on the conversation because at the moment I'm particularly interested in the topic. ,😁

Clint
[Google Pixel 6 Pro] genesan:
I'm not posting any misinformation. No I actually never have had one that is but I'm also not an idiot.. are you an idiot? I don't know what part of that was personal to you but that's a real screenshot that's a real situation and those are the technical details and if you pull something out of that besides "interesting" then I'm happy for you but you can just keep that s*** to yourself.
[Google Pixel 6 Pro] none24:
Has anyone ever tried to gain root or temporary root access and change get_unlock_ability to 1 in the build prop to see what happens?

On my fold i see this is available but im wondering what it would do if a person with a grayed out OEM Unlock option just changed this.
[Google Pixel 6 Pro] dave678:
For Samsung phones they have been bootloader locked in the USA since the S7 however a bootloader unlocking service is available for the S9 and up.
[Google Pixel 6 Pro] Strephon Alkhalikoi:
No such service exists for Verizon bootloaders. I wish it did. It would put an end to scores of identical threads all complaining about the same thing and with the same root cause: people not doing their homework first before they buy.
[Google Pixel 6 Pro] w_tapper:
this is why you buy unlocked phones
[Google Pixel 6 Pro] Strephon Alkhalikoi:
Mine is unlocked (bought new off Amazon). Regardless, you are 100% correct in saying this.
[Google Pixel 6 Pro] BROKEN1981:
LG V20 and 30 had BL unlock on T-Mobile. Just no FastBoot commands so it was pointless. Only 1 guy was able to defeat it and get us TWRP.
[Google Pixel 6 Pro] c2gemineyes:
Not my experience. I bought an unlocked Pixel 6 pro and used my Verizon sim in it for a month before I rooted mine.
[Google Pixel 6 Pro] lucky_strike33:
There is always a trick or hack to do this. Even the pixel has yet to be hacked since pixel 2 or 3.
[Google Pixel 6 Pro] roirraW "edor" ehT:
That's not what's being talked about. Verizon keeps the bootloader from being unlocked on all their phones to the best of their ability.

There are also usually permanent repercussions of hacks, on some brands other than Google.
[Google Pixel 6 Pro] craznazn:
Utilizing a vulnerability to unlock a BL is kinda completely different than a company's policy allowing you to unlock the BL. You wouldn't say iPhone 1-12 are easily jailbroken, even though you could totally do so <ios 14.2, but to get there, people had to find and leverage exploits.

VZW goes out of their way to prevent their devices from being BL unlocked.
[Google Pixel 6 Pro] The.Jericho.Initiative:
LOL.

If that were the case, VZW rooting would have been much more of a thing for a decade now... The best part of the situation is that no argument is necessary. The topic has been discussed, for nearly ten straight years, on these forums. If you're genuinely curious and of the pedigree you claim, then I recommend you spend an hour searching and you will find the answers you seek.

I'm not going to say you're wrong, I think you already know you are, I'm simply saying that if you actually want an answer - you know how to find it.
[Google Pixel 6 Pro] HipKat:
I just hate that I have to go through a store since dropping $900 bucks on a one shot purchase is just not possible
[Google Pixel 6 Pro] FernBch:
Well, I'm going to dive in again. I unlocked my VZW Pixel 1, the Pixel 2's were vulnerable, and I got close on the P3XL. Actually bricked it with an exploit hack attempt. Someone did manage to unlock the P3XL bootloader but how was never shared. There is a thread on it.

Got my P6Pro yesterday and have not updated it, so I'll be looking into exploits to pop a root shell with. I'm familiar with how the BL unlock process works, just need to find the way to defeat/bypass/fool it.

Wish me luck.....
[Google Pixel 6 Pro] roirraW "edor" ehT:
I definitely wish you luck. It's my favorite thing to be able to do things that someone intended us to not be able to do with technology.