- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
(Last edited
a week ago
by
SamsungChelsea
) in
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago in
Galaxy S22- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago in
Galaxy S22- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago in
Galaxy S22- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago in
Galaxy S22- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago in
Galaxy S22I would second this. Even if the device is unlocked, it still has a t-mobile model number. When a device connects to the update server, it passes it's model number. seeing as how you are on Verizon, the model number is not present so finds no updates. On a t-mobile server it should find the update and allow the install.
No you cannot set this server yourself.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago in
Galaxy S22- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago in
Galaxy S22- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago in
Galaxy S22- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago in
Galaxy S22Aside from that, updates are carrier dependent...Google bakes the plain version (aka vanilla)...Then that is distributed to the carriers so that they can brand it, as drivers and device configuration, then bake in their proprietary bloatware...it's because of that process that updates to Android can take up to 6 months or more after Google releases them...because of the carrier delay.
Now, putting all that together, the device is not still locked to T-Mobile...but it was a T-Mobile imei originally, so it's essentially "registered" that way. What you can do is contact T-Mobile and tell them you want to get the updates. They will ask for imei and tell you how to manually get them...possible even trigger an OTA for you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago in
Galaxy S22![](/skins/images/5202F323D96CEFF962E8D15C6A633297/responsive_peak/images/icon_anonymous_message.png)
![](/skins/images/5202F323D96CEFF962E8D15C6A633297/responsive_peak/images/icon_anonymous_message.png)