January 5 Update 7.6mb

I just had a preparing when I manually checked then stopped, unlock T-Mobile:(


I get this message now
05fa7fc924e19e7afdc79cd9cdf73c54.jpg
Oh wow I've never seen that before. I'm going to check mine and see if it does the same thing
 
I'm still waiting as well. Last night I had the momentary "Preparing system update" then it just switched to "Your system is up to date". Nothing changed yet today.
Pixel 10 Pro XL on Google Fi.
That's so strange because I'm on Fi and I got the update last night when I checked it.
 
Not trying to stir anything up or criticize. Just wondering why when folks say they get an OTA update they mention their devices are "unlocked." Does everyone realize the locked to a carrier or unlocked has zero to do with when you get an OTA update? Google presents the updates to the carrier, and when the carrier approves it rolls out. Anyone who has the device can mash the update button and get it when the carrier (SIM based) approves it.

That's why this time T-Mobile hadn't approved it yet and those of you on T-Mo got it at the same time yesterday or today, locked or unlocked, when you pressed the update button. I'm not advocating for buying a device from a carrier that could be carrier locked, or buying directly from Google unlocked. You can also use ADB and sideload the update from the Google OTA page with a carrier locked or unlocked device. Where the differences start are your ability to root and whether or not you get bloatware, like Samsung forces on you. People continually think their unlocked devices always get updates directly from Google and bypass the carriers, but this simply isn't true. It is based on the SIM in the device. There are tricks to get past this as I've seen some people take the carrier SIM out and update via wifi successfully.
 
Not trying to stir anything up or criticize. Just wondering why when folks say they get an OTA update they mention their devices are "unlocked." Does everyone realize the locked to a carrier or unlocked has zero to do with when you get an OTA update? Google presents the updates to the carrier, and when the carrier approves it rolls out. Anyone who has the device can mash the update button and get it when the carrier (SIM based) approves it.

That's why this time T-Mobile hadn't approved it yet and those of you on T-Mo got it at the same time yesterday or today, locked or unlocked, when you pressed the update button. I'm not advocating for buying a device from a carrier that could be carrier locked, or buying directly from Google unlocked. You can also use ADB and sideload the update from the Google OTA page with a carrier locked or unlocked device. Where the differences start are your ability to root and whether or not you get bloatware, like Samsung forces on you. People continually think their unlocked devices always get updates directly from Google and bypass the carriers, but this simply isn't true. It is based on the SIM in the device. There are tricks to get past this as I've seen some people take the carrier SIM out and update via wifi successfully.
Your correct and once the carrier approves it then goes to Google's server the carrier doesn't release it out only approves it so sometimes unlock because it doesn't have as many carrier configuration could update before a carrier one with bloat and carrier configuration.

Don't forget when we mentioned unlock or carrier it goes for not just the US but other countries also.
 

Trending Posts

Forum statistics

Threads
960,630
Messages
6,983,101
Members
3,164,544
Latest member
isaackse