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.
So I have Tmobile with an E-sim and it would not update. So I plugged an ATT sim in from my work phone and disabled the Tmobile e-sim and did a manual update and it worked.
So, I get that things happen and sometimes there is a delay. However, I don't get the lack of communication from T-Mobile and\or Google. Someone, somewhere knows something. And without communication, how will we know if it's just an issue with our phones? What if it turns out that some flag got set on our phones that tells Google's servers that our phones are up to date? We would have waisted a month waiting for them to fix something that isn't broken and they aren't working on...and we just needed to manual side-load the update to reset the flag. Within communication, there's no way to be sure we should wait or we should side load it. Very frustrating, IMO!
wsb_cal wrote:
Could be a security issue. There was a major T Mobile data breach around 25 November 2022 (https://www.theverge.com/2023/1/20/23563825/tmobile-data-breach-api-customer-accounts-hacker-security). It probably took them a while to discover the breach, thus accounting for pulling the December update midstream.
They could be busy fixing the security infrastructure on their hardware and/or making sure the phone security updates don’t propagate/expose the flaw.
No wonder they’re so close-mouthed...
It has nothing to do with the security breach but more to due to Bluetooth connectivity. It's also occurring on the Google Fi network.
Checked for updates on 7 February for unlocked Pixel 7 T Mobile and downloaded and installed February 5 update successfully - no swapped SIM or sideload, just standard update.
The updates come directly from Google. If you put another carrier SIM in your device, it will update the firmware and carrier aggregation to that carrier until you return to the T-Mobile update path, which might make a coue.of updates if the version numbers are dated the same.
The update has been released by Google for the pixel lineup.
Bobaloo wrote:
The update has been released by Google for the pixel lineup.
Most updates are a staggered release, meaning not everyone will get it at the same time. Google might have released the update but that doesn't mean it has been released to everyone.
That’s true but I have heard that its a carrier issue as I am new to T-Mobile.
My 6 hasn't received it either but it seems like every once in a while it's a week late.
That's good to know as i have had a few Pixels but they were unlocked which mightdifference be the difference.
