Forum Discussion
Pixel 7 Security Update
My Pixel 7 will not receive the January 2023 security update . Tried doing it manually and no luck, have heard it's a T-Mobile issue but that's just hearsay. Heard you can just pull your sim out and put another one in and it will update haven't tried that one yet.
pixel12a wrote:
So that only leaves something behind the scenes. Something tmo and google are hashing it out. Its got to be something that the two cant agree on. I highly suspect something feature related. I keep saying I think tmo wants something removed or blocked?
We're just going to have to wait it out. Once we do get a update. I'm pretty sure it will be a specific android build for tmo. We can pick it apart then and look for whats different.
- It’s more likely the time necessary to modify and fully test code, which is significant,
- It won’t be a specific T-Mo build for factory unlocked phones (like mine).
- It’s more likely a functional issue specific to the T-Mo network than something T-Mo wants removed or blocked.
I can confirm that it is very likely being held by T-mo. I too have a Pixel 7 Pro unlocked (not purchased through Tmobile) and cannot get the update installed, no matter how many “check for updates” I try.
I got the same answer from Google as another user here (wait until 1/15).
I then fished out a very old expired SIM from another carrier and as soon as I put it in, the update appeared for Jan. I put my Tmo SIM back in too quickly and that killed the update almost immediately. So I had to do it all over again and put the other SIM back in and it started again…
gramps28 wrote:
The Pixels on Fi are having issues with the update and in turn Fi uses the Tmobile network which is probably causing the issues on updates for Tmobile for the Pixel line.
It was never released for fi. No one on fi got it without forcing it. Tmobile is blocking the update.
Google can't let it go to mint, fi, metro or any device on the tmo network. Untill tmo says so. Or Google
So much speculation blaming T-Mobile with no proof at all.
As I said before if people believed it was T-Mobile they can take out the sim and factory reset their unlocked device. Connect to WiFi and the update should be there. If it isn't then it can't be carriers as the phone is unlocked and not associated with a carrier in anyway and is missing the carrier partition. None are willing to do it because it's easier to blame the carrier than it is to blame Google. Google has a lot of strong fanboys thinking they can do no wrong.
As I said before Google has Always staggered the release of their OTAs. The ones that are unwilling to wait they offer the OTA file for people do download and install. Doesn't matter which version they are all the same unless specified by Google before the release of the update. They are marked as such but subsequently the next version gets rolled back into one afterwards. Just side load it if you want it now. It's actually safer than doing it OTA to boot.
Let's just hope it's resolved soon. We can all help by talking about it. And send in complaints to both Google and tmo. The more they know that we care. The more effort they'll put into resolving it.
I factory reset my wife's pixel 6a with out a sim. It updated and is on the January release. That was 1/14. everything looks good. Lte, 5g, 5g uc. And visual voicemail are all working fine. Bluetooth works fine. I'm holding off on my pixel 7. As I just did a factory reset coming from Android 13 beta to standard release.
pixel12a wrote:
I factory reset my wife's pixel 6a with out a sim. It updated and is on the January release. That was 1/14. everything looks good. Lte, 5g, 5g uc. And visual voicemail are all working fine. Bluetooth works fine. I'm holding off on my pixel 7. As I just did a factory reset coming from Android 13 beta to standard release.
The only issues I've heard about are with a small handful of cars.
I might side load if it doesn't come in the next couple days. Resets are enough of a pain and I'm on esim so I doubt a reset would do anything.
My two cents. T-Mobile has no right to hold back security updates on unlocked phones not even purchased from T-Mobile. I opted into the beta program and I have the January 5th update. Fingerprint sensor works much better and no Bluetooth issues at all. I can use Bluetooth on any of my devices and it works as it always did on my Hyundai sonata using Android Auto. I pay T-Mobile only for data. They don't own my phone's. They did the same thing with OnePlus if any of you remember. I certainly remember security updates once every 2 months.
My two cents. T-Mobile has no right to hold back security updates on unlocked phones not even purchased from T-Mobile. I opted into the beta program and I have the January 5th update. Fingerprint sensor works much better and no Bluetooth issues at all. I can use Bluetooth on any of my devices and it works as it always did on my Hyundai sonata using Android Auto. I pay T-Mobile only for data. They don't own my phone's. They did the same thing with OnePlus if any of you remember. I certainly remember security updates once every 2 months.
Bobaloo wrote:
Spoke with a technical rep from T-Mobile and was told they do not block updates and that December is the latest update that they have. So my guess now is that it's a Google issue as they tried to connect me to Google and they were closed. Must have MLK day off so really nothing more to add to the story!
That's a flat lie from them.
Literally only one carrier and it's connected carriers are having this issue. I can't find one singular t mobile phone that has updated to the January update without outside assistance across here, Reddit and xda. Literally every other carrier anyone who goes to check it's there.
