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.
Last edited:
Question Verizon Pixel 6 Pro Bootloader Unlock?
- Thread starter Kpwise509
- Start date
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.
Last edited:
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.
Last edited:
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.
jamescable
Senior Member
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.
jamescable
Senior Member
Actually EU laws do apply to U.S, because that's where the phones are made....overseas
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
Last edited:
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.
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.
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.
Uhh...no. That's not how this works. At all. EU directives cover where the device is sold, not made.
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
Top Liked Posts
-
There are no posts matching your filters.
-
10
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
10
Your insults directed at developers, and other members on Xda violate Forum Rules and are no longer welcome in the forums.
Please make sure you fully understand the following:
1) if you have a proven method to unlock the bootloader on VZW devices, open a thread, make yourself famous, and become the greatest Xda developer ever. If you can't or won't open your own thread and share your method, stop posting your self -righteous comments allover the forums.
2) if you post any further insults directed at Xda members, your account will be restricted. Xda is about sharing and developing, not smoke & mirrors and insulting other members who have actually produced tons of legit development.
No more warnings on this, check your PM.
Thanks for your cooperation.7
Thank you.
This same exact thread happened in the Pixel 5 forum.
He won't provide proof.
And he doesn't have to... It's that simple.
Just ignore, please.7
That has never happened on a VZ Pixel and it is not going to happen on this one. Why is this so hard for people to understand?7
Incorrect. SIM unlocking is not necessarily related to bootloader unlocking. While T-Mobile (and I think AT&T) users on here have found and reported that when they achieve SIM unlocking on their variants, that they can then bootloader unlock as well, Verizon has for a very, very long time enforced bootloader lock with all their will.
The only exceptions that I've ever heard of were not by choice of Verizon, but by hacks/vulnerabilities. Such as the VS985 LG G3, there was an exploit that didn't actually bootloader unlock, but more made it so that the locked bootloader didn't really matter. On the Pixel 1, if you had the Verizon variant and were still on Android 7.10 or below, you could unlock the bootloader, but once the 7.11 OTA came out, if you hadn't already unlocked the bootloader (or at least toggled the toggle), then you were locked in until a foreign national found a hacking way to get in, but they charge for it. All this while Verizon phones have been ultimately SIM unlocked for similarly a very long time.
