Database Users

OTA updates outside T-Mobile networks

I have a US T-Mobile G1, but am in Belgium, and we don't have T network here...
is the update coming to the devices, regardless of the network they're registered on, or do I really need to be in the US, on a T-Mobile network, to get the update?
Anyone from Belgium, or somewhere in Europe that has a G1 that is on another network than it was meant for?
Is there (going to be) any means of pulling the update manually, even on another network?
Thanks for sharing the info...

First, is your phone rooted or not?
Second, what firmware/rom are you running?
You do not need to be on T-mobile to get the update. Your phone checks with a server run by google. If there is an update for it it will get sent to your phone. If your phone is rooted it wont update due to running testkeys instead of releasekeys (unless you are running an ADP firmware).
Once the exact location of the file is known you can manually download it and update your phone if you dont want to wait.
Since you say its a US G1 you should be able to get the 1.5 update which should drop sometime between May 11th and the end of the month. Your location may prevent that from happening, however you can just use the zip file that will get posted on this site somewhere if that happens.

First of all, thanks for the quick response.
The phone is not rooted, it's a normal user phone, no hacks, no custom soft...
Current version is 1.1 RC33 126986 with the release keys intact...
I'll wait until the end of the month and see then...
Just need it to get SipDroid running... (www.sipdroid.org) Wanted to make it a 'cordless phone' for my asterisk server running at home...
Thanks for the info and help!
I'll let you know when I get the update.

Just to let you know, I'm currently abroad with my G1 (UK on T-Mobile), with data roaming turned off.
Connected my G1 to the internet over Wifi and the update was detected and downloaded over Wifi. So looks as though it shouldn't matter what you're connected over.

I have mine secondhand and i have no idea if its rooted or not. but i know i don't have any updates yet. btw im in turkey where no t-mobile service is avaliable.
my device's firware is like that, can you tell its rooted or not? I know im a real newbie. If its rooted how can i take it to original state that can pull the original cupcake
Firmware version 1.0
kernel version
2.6.25-01843-gfea26b0
[email protected] 6#
built number
kila-user 1.0 TC4-RC30 116143
ota-relkeys,release keys

saluk said:
I have mine secondhand and i have no idea if its rooted or not. but i know i don't have any updates yet. btw im in turkey where no t-mobile service is avaliable.
my device's firware is like that, can you tell its rooted or not? I know im a real newbie. If its rooted how can i take it to original state that can pull the original cupcake
Firmware version 1.0
kernel version
2.6.25-01843-gfea26b0
[email protected] 6#
built number
kila-user 1.0 TC4-RC30 116143
ota-relkeys,release keys
Click to expand...
Click to collapse
I think (thx to xda-develpers ) mine is not rooted right? Then why didn't I got the cupcake or the previous version which is newer than mine :/

Im just curious if i will receive the update OTA or not. I rooted my phone however it states that it is release keys and not test keys. Below is what the About Phone screen looks like
Firmware Version
1.1
kernel Version
2.6.25-01843-gfea26b0
[email protected] #1
Build Number
kila-user 1.1 PLAT-rc33 126986
ota-rel-keys, release-keys
Thanks for the help

To answer the actual question. Will you get the OTA T-Mobile update? No, you will not. T-Mobile is pushing it to their customers. T-Mobile and Google are not the same company and T-Mobile has no responsibility to update the "device" but rather to update their customers.
The reason the UK guy got the update is because he is in the customer database for T-Mobile UK. So as his phone is part of that network (regardless of roaming/not roaming) it came to him.
However, I am sure there will be some smart G1 user who, when getting the update downloaded OTA, will FIRST copy the update off their phone BEFORE installing it. Then uploading a copy of the update so those who still have not received it can download it and install it manually. (That is a hint to any US T-Mobile person on this forum who gets the update)

You should get the OTA updates. I bought a dev phone in december and in January I got the OTA ADP1.1h update. I'm not on T-Mo at all and never have. I am on AT&T and all was well and I would assume you should be too.

ExploreMN said:
To answer the actual question. Will you get the OTA T-Mobile update? No, you will not. T-Mobile is pushing it to their customers. T-Mobile and Google are not the same company and T-Mobile has no responsibility to update the "device" but rather to update their customers.
The reason the UK guy got the update is because he is in the customer database for T-Mobile UK. So as his phone is part of that network (regardless of roaming/not roaming) it came to him.
However, I am sure there will be some smart G1 user who, when getting the update downloaded OTA, will FIRST copy the update off their phone BEFORE installing it. Then uploading a copy of the update so those who still have not received it can download it and install it manually. (That is a hint to any US T-Mobile person on this forum who gets the update)
Click to expand...
Click to collapse
I beg to differ, I might be wrong but everyone was getting the previous updates because they aren't sent from T-Mobile. They are sent from Google. It is just a T-Mobile build so as long as you have internet it will download the update.

neoobs said:
I beg to differ, I might be wrong but everyone was getting the previous updates because they aren't sent from T-Mobile. They are sent from Google. It is just a T-Mobile build so as long as you have internet it will download the update.
Click to expand...
Click to collapse
I beg to differ your begging to differ! Google, from what I understand, has its own 1.5 cupcake update which is similar to the T-mobile version in just about every respect. However, while searching for cupcake I read an article that noted there were some differences between the two builds. Perhaps Google was responsible for the G1 update to 1.1, but from the sounds of it, that is not the case now.

ExploreMN said:
I beg to differ your begging to differ! Google, from what I understand, has its own 1.5 cupcake update which is similar to the T-mobile version in just about every respect. However, while searching for cupcake I read an article that noted there were some differences between the two builds. Perhaps Google was responsible for the G1 update to 1.1, but from the sounds of it, that is not the case now.
Click to expand...
Click to collapse
I am not saying that Google created it but rather it is hosted on Google Servers, this can't change because the update script pulls the update from Google servers. Maybe in 1.5 it will change but as of 1.1 it still checks Google for the update.
Basically as long as you can reach the google address it all will update.

You will NOT get an OTA.
You only get an OTA IF:
1) You have a G1 and are a tmobile customer. The update may come from google's servers, but the update is controlled by tmobile, and its user database. It is a tmobile phone.
2) You have an ADP, and have already *MANUALLY* updated to 1.1 firmware. Then, you will get the official google (via HTC) ADP 1.5 update. OTA functionality for ADP was only rolled out in the 1.1 firmware.
Other than that, no, you will NOT get the update, and you will need to root the phone and manually update to either the ADP release, one of the t-mobile releases or any of the 'cooked' roms on here.
Also there seems to be some confusion on the ADP vs. G1 versions. Infact, it is the exact same phone, and the *exact* same software, but the tmobile release has the t-mobile logo and all their spam apps (my favs etc). Otherwise, they are the same thing!
Hope this cleared some stuff up.

I bought the phone second hand and use it on orange and i got the update. im not a tmobile user, but the person i bought the phone off was. but have never personally used it on tmobile and received the 1.5 update fine. hope this helps

menov321 said:
I bought the phone second hand and use it on orange and i got the update. im not a tmobile user, but the person i bought the phone off was. but have never personally used it on tmobile and received the 1.5 update fine. hope this helps
Click to expand...
Click to collapse
You probably got the google generic 1.5 update and not the t-mobile specific update.

bakgwailo said:
You will NOT get an OTA.
You only get an OTA IF:
1) You have a G1 and are a tmobile customer. The update may come from google's servers, but the update is controlled by tmobile, and its user database. It is a tmobile phone.
2) You have an ADP, and have already *MANUALLY* updated to 1.1 firmware. Then, you will get the official google (via HTC) ADP 1.5 update. OTA functionality for ADP was only rolled out in the 1.1 firmware.
Other than that, no, you will NOT get the update, and you will need to root the phone and manually update to either the ADP release, one of the t-mobile releases or any of the 'cooked' roms on here.
Also there seems to be some confusion on the ADP vs. G1 versions. Infact, it is the exact same phone, and the *exact* same software, but the tmobile release has the t-mobile logo and all their spam apps (my favs etc). Otherwise, they are the same thing!
Hope this cleared some stuff up.
Click to expand...
Click to collapse
Where did you get your info? We had tons of users getting the update OTA for the 1.1 and even previous 1.0 builds. BTW there are 3 versions of software, 2 by t-mobile, 1 by google. The 2 t-mobile versions are US and UK which have different applications because of the way company each works.
ExploreMN said:
You probably got the google generic 1.5 update and not the t-mobile specific update.
Click to expand...
Click to collapse
Where did you hear there is a generic google version? So far only the ADP 1.5 has been made available to us, and we only know of the ADP and T-Mobile versions.

There is also this one, cupcake for holiday phone europe
http://android.clients.google.com/updates/signed-dream_gfh_eu-ota-147201.ea8cd686.zip
posted here
http://phandroid.com/2009/05/05/official-german-cupcake-url-leaks-for-developers/

I have a T-mobile G1 on Rogers in canada with a data plan,
YES, YOU WILL EVENTUALLY GET THE UPDATE.
Originally i believed that i do not get updates, so i manually upgraded fron RC29, to RC30,
one day, at work, i got a notification to go from RC30 to RC33 OTA.

petko64 said:
I have a T-mobile G1 on Rogers in canada with a data plan,
YES, YOU WILL EVENTUALLY GET THE UPDATE.
Originally i believed that i do not get updates, so i manually upgraded fron RC29, to RC30,
one day, at work, i got a notification to go from RC30 to RC33 OTA.
Click to expand...
Click to collapse
That could be because updates were stopped halfway through on one of the updates to make sure they fixed some security holes.

The last update I got before any T-mobile customers and I was on AT&T. I actually pulled the file off my phone and gave it to JesusFreke but by the time he got it the link had already been posted.

T-Mobile UK first to offer 2.2 OTA update for Galaxy S !!

Samsung Galaxy S 2.2 update
Posted: 5 hours ago
Hi folks
Thanks a lot for all your patience regarding the Galaxy S froyo update.
Our handset team have been working closely with Samsung regarding this update and future updates and would like to share their news with you.
Our goal is to make the update process smoother and we are working to become the only mobile operator offering FOTA (Firmware over the Air) updates for the Samsung product range. The aim was and still is to have the FOTA update available at some point today. If for reasons outwith our control we are unable to have a FOTA update process fully functioning by close of play today, then we will make the update available for download via Samsung KIES tomorrow (Dec 1st)
Thanks again for all the feedback you've given us through our forums.
Cheers
Barry
T-Mobile forum team
http://support.t-mobile.co.uk/discussions/index?page=forums&topic=80103825157760012c52e07803002f32

I wonder if they are just creating a package for FOTA or sorting out the bugs in the 2.2 update also? Probably just adding all the t-mobile crap

OTA is an interesting choice....
How do they know whether a phone has the T-mobile product code? Does that mean the update will be sent to all the T-mobile Galaxy S phones?
Or what if you originally had a T-mobile product code and now have XEU after using the KIES hack, will T-mobile try to send you the upgrade?
These are probably very simple questions, but I'm new to smartphones

enigmameusa said:
OTA is an interesting choice....
How do they know whether a phone has the T-mobile product code? Does that mean the update will be sent to all the T-mobile Galaxy S phones?
Or what if you originally had a T-mobile product code and now have XEU after using the KIES hack, will T-mobile try to send you the upgrade?
These are probably very simple questions, but I'm new to smartphones
Click to expand...
Click to collapse
I doubt they even can push it out it looks like another line to me as they said it would be out by the end of november via kies in the first place. There is still no update in kies at the moment

[Q] Android 4.4 can't connect to mobile internet

Hi everybody, although this is my first post here, I've been a avid "anonymous user" of the xda forums for a while.
Yesterday I decided to flash the android 4.4 factory image on my nexus 4 using the Nexus Root Toolkit, and all seemed well but today I realised I was unable to use the mobile internet, despite having the correct APN settings. Reverting to Jelly Bean (Android 4.3) solves the problem, so unfortunately I'm back to square one.
I flashed the android 4.4 factory image a few more times using the batch file and manually but still no luck...
I even tried flashing the radio-baseband from android 4.3 M9615A-CEFWMAZM-2.0.1700.84 but that didn't help either.
Has anybody else experienced this problem?

It help to say what carrier you are using and post your apn settings to verify it.
Anyway, if you have root, download a CM11 rom, extract the file "/etc/apns-conf.xml" from it, put it in "/etc/" folder of the phone, fix permission to rw-r-r. (CM apns-conf have the biggest APN collection I've seen from any roms).
Do a factory reset, now go in settings and see if there are available APN to choose from. If still not working, APN might not be the issue.
Or you can just search the XML for your specific carrier and compare the APN settings.
Here are the Modem collection you can try flashing: http://forum.xda-developers.com/showthread.php?t=2087227

rickxray said:
Hi everybody, although this is my first post here, I've been a avid "anonymous user" of the xda forums for a while.
Yesterday I decided to flash the android 4.4 factory image on my nexus 4 using the Nexus Root Toolkit, and all seemed well but today I realised I was unable to use the mobile internet, despite having the correct APN settings. Reverting to Jelly Bean (Android 4.3) solves the problem, so unfortunately I'm back to square one.
I flashed the android 4.4 factory image a few more times using the batch file and manually but still no luck...
I even tried flashing the radio-baseband from android 4.3 M9615A-CEFWMAZM-2.0.1700.84 but that didn't help either.
Has anybody else experienced this problem?
Click to expand...
Click to collapse
if you are having issue with the factory images why not just flash a zip and call it a day... Or at least trouble shoot it that way

I have the same problem , no data connection while on KitKat 4.4. I tried flashing rooted and unrooted stock images with latest radio, nothing works. Checked my APN settings, at first nothing was selected. I had three options metro pcs , tmobile, and tmobile fast. I chose tmobile fast restarted the phone and nothing. I even called tech support they could not help me, im going back to 4.3 for now.
edit: got it to work, thanks eksasol

Hi guys, thank you for your replies! I'm actually with TalkTalk (UK) and the factory image of android 4.4 actually has the APN settings for the carrier, I tried it but they weren't working. I headed to the TalkTalk website for the manual settings which I, frustratingly, used as follow:
Name: TalkTalk
APN: mobile.talktalk.co.uk
Proxy: Not set
Port: 8799
User name: wap
Password: wap
Server: Not set
MMSC: h t t p : / / mms.talktalk.co.uk/servlets/mms
MMS proxy: 212.183.137.12
MMS port: 8799
MCC: 234
MNC: 15
Authentication type: Not set
APN type: Not set (some Android devices may show Internet + MMS)
Click to expand...
Click to collapse
When using these settings on android 4.3 I am able to connect to the network, but not when I'm on android 4.4. Since there are a few new fields on the APN settings in kitkat I wonder if the problem has to do with that.
My objective with this topic is to discuss the issue and understand its root more than seeking for a solution of my particular problem.
P.S. I had to edit the h t t p : / / of the link on the MMSC as XDA won't allow me to post links due to being a new member, lol

eksasol said:
It help to say what carrier you are using and post your apn settings to verify it.
Anyway, if you have root, download a CM11 rom, extract the file "/etc/apns-conf.xml" from it, put it in "/etc/" folder of the phone, fix permission to rw-r-r. (CM apns-conf have the biggest APN collection I've seen from any roms).
Do a factory reset, now go in settings and see if there are available APN to choose from. If still not working, APN might not be the issue.
Or you can just search the XML for your specific carrier and compare the APN settings.
Here are the Modem collection you can try flashing: http://forum.xda-developers.com/showthread.php?t=2087227
Click to expand...
Click to collapse
Thank you eksasol for your help here! I downloaded the CM ROM you just posted but there are no settings for my carrier so I'm unable to compare them... I just flashed the 0.97 radio on my Jelly Bean stock ROM and I can confirm that is not the reason for this problem since I'm able to use the mobile data connection (Wifi stopped working, though).
So, to summarize: I'm using exaclty the same APN settings on JB and KK, the problem doesn't seem to be related to the radio/baseband version as using the 0.97 (from KRT16O) on my JB ROM still allows me mobile data connectivity (although it stops my wifi). This leaves me with the option of network carrier incompatibility (is that possible anyway??) or some weird problem on Android 4.4 of which I'm the only victim!

I have the same problem. Texting works fine but when I try to use data nothing works. I've tried flashing the radio again but it hasn't helped. I'm using Straight Talk with AT&T.

rickxray said:
Hi guys, thank you for your replies! I'm actually with TalkTalk (UK) and the factory image of android 4.4 actually has the APN settings for the carrier, I tried it but they weren't working. I headed to the TalkTalk website for the manual settings which I, frustratingly, used as follow:
When using these settings on android 4.3 I am able to connect to the network, but not when I'm on android 4.4. Since there are a few new fields on the APN settings in kitkat I wonder if the problem has to do with that.
My objective with this topic is to discuss the issue and understand its root more than seeking for a solution of my particular problem.
P.S. I had to edit the h t t p : / / of the link on the MMSC as XDA won't allow me to post links due to being a new member, lol
Click to expand...
Click to collapse
I looked up their APN from here, and the difference is they do not set anything for the regular Port value:
http://help2.talktalk.co.uk/settings/lg-nexus-4-internet-settings

I've tried both settings but nothing worked. Actually, there are some settings loaded in the stock ROM for this network but the problem remains.
I'm going to try again tomorrow, and post my conclusions here
At the moment I'm running Jelly Bean so I can actually use the phone, lol
Sent from my Nexus 4 using xda app-developers app

Hi guys,
just as promised, here is the update on the situation:
Today I flashed a few different Android 4.4 ROMs, Stock (again, since there is a new build available - KRT16S) , ParanoidAndroid AOSP and CyanogenMOD 11.
Using the same APN settings for all the ROMs I was able to get mobile internet only with CM11 but unfortunately, with this ROM I couldn't get the wifi and bluetooth to work, so... back to Jelly Bean it went!
What I don't understand is that I seem to be the only person with this problem and it definitely has to do with the stock KitKat implementation...
I'll give a real KitKat bar to anybody who manage to find the reason for this trouble

rickxray said:
Hi guys,
just as promised, here is the update on the situation:
Today I flashed a few different Android 4.4 ROMs, Stock (again, since there is a new build available - KRT16S) , ParanoidAndroid AOSP and CyanogenMOD 11.
Using the same APN settings for all the ROMs I was able to get mobile internet only with CM11 but unfortunately, with this ROM I couldn't get the wifi and bluetooth to work, so... back to Jelly Bean it went!
What I don't understand is that I seem to be the only person with this problem and it definitely has to do with the stock KitKat implementation...
I'll give a real KitKat bar to anybody who manage to find the reason for this trouble
Click to expand...
Click to collapse
I heard some people have issues updating to newer bootloader or radio and can't install 4.4.
If you can't get CM11 to have wifi, it's a problem with the driver of your rom. If you for example use a 4.3 kernel that do not have the newer PRIMA driver wifi won't work. You can try flashing the dePRIMAtor package to CM11 and see if you get wifi, or try a PRIMA compatible kernel: http://www.androidfilehost.com/?fid=23212708291674891

A big thanks to eksanol.
The trick on the second post fixed the issue for me.
The APN settings for my operator (TIM Brazil) was wrong on default apns-conf.xml and I could not manually edit.
apns-conf.xml from CM11 has the correct informations.

Hi guys, today I flashed the .zip file for the KitKat OTA upgrade on top of my Jelly Bean stock ROM and everything seems to be fine now, I can finally use my mobile internet connection with the same settings that I've been trying with the Android 4.4 factory images before. I still don't understand what happened here but at least everything works now...
I want to say thanks to everyone who helped me with this issue!

Solved
rickxray said:
Hi guys,
just as promised, here is the update on the situation:
Today I flashed a few different Android 4.4 ROMs, Stock (again, since there is a new build available - KRT16S) , ParanoidAndroid AOSP and CyanogenMOD 11.
Using the same APN settings for all the ROMs I was able to get mobile internet only with CM11 but unfortunately, with this ROM I couldn't get the wifi and bluetooth to work, so... back to Jelly Bean it went!
What I don't understand is that I seem to be the only person with this problem and it definitely has to do with the stock KitKat implementation...
I'll give a real KitKat bar to anybody who manage to find the reason for this trouble
Click to expand...
Click to collapse
I found the answer on the TalkTalk Nexus 5 forum:
You must delete ALL current apn settings for all carriers
add new
Name; TalkTalk Internet
APN; mobile.talktalk.co.uk
Proxy Not set
Port 8799
User name wap
Password wap
Server not set
MMSC: h t t p : / / mms.talktalk.co.uk/servlets/mms[/url]
MMS proxy: 212.183.137.12
MMS port: 8799
MCC: 234
MNC: 15
Authentication type: Not set
APN type: Not set
APN Protocol: IPv4
Bearer: Unspecified
MVNO type: None
MVNO value: not set
save
select it (blue dot)
restart phone
You should now have a small H above the signal bar when its working, and the drop down notification will say TALKTALK
There can be a small delay when it turns on mobile data, if you get offline message in the broswer hit refresh a few times
N.B. As with the original poster, as a new member I was prevented from including the URL for the mms server, so I added the spaces to get round the problem.

You aren't the only with the problem
With the nexus 5 port before the factory images, I never lost signal it was awesome
After the factory images, I lose signal every once in a while
It's annoying, it must be something in the code
Enviado desde mi Nexus 4 mediante Tapatalk

rickxray said:
Hi guys, today I flashed the .zip file for the KitKat OTA upgrade on top of my Jelly Bean stock ROM and everything seems to be fine now, I can finally use my mobile internet connection with the same settings that I've been trying with the Android 4.4 factory images before. I still don't understand what happened here but at least everything works now...
I want to say thanks to everyone who helped me with this issue!
Click to expand...
Click to collapse
Thank you man! The only way that helps me to solve the same issue.

Reviving an old thread but I think I may have similar issue with my mobile internet.
I'm with Three UK and quite often I have full signal and H icon at the top (white) but internet doesn't work at all!
It's driving me absolutely insane. At times, I have the dreaded orange signal icon, which also means no data connection for me. Does anyone know if this is KitKat issue or could it be the network provider issue? I struggle to understand why I wouldn't get any data connection if I'm getting full signal?
I'm even considering selling this stupid phone and getting a new phone as I can't get reliable internet connection. I'm not sure if I'm imagining but it seems to be worse when I'm at work so that makes me think it could be network issue, but who knows....
So sick of these stupid errors and bugs with Android TBH.
I'm running KitKat 4.4.4 btw.
Any help would be greatly appreciated.

Seeking some assistance updating an unlocked (And out of US) G892A from stock

Hello Folks,
As the thread title states, I'm looking for a way to update to the current firmware from stock (G892AUCU1AQG4) - I bought the device a few days after it came out and promptly unlocked it and took it to Canada - OTA Updates are obviously disabled as I'm not on AT&T and there's no indication of a manual update method via USB on AT&T's support pages. Any chance someone has pulled ODIN files for all of the updates (As they seem to be building off of one another, indicating it's basically a nesting doll scenario where I assume I'll need to run update after update in sequence)? Or is there another way to go about this that doesn't involve going stateside and buying a sim and plan?
Did some searching and found a few threads with links or references to the stock files, but didn't see any means to update from stock to current (Or even just the first 8.0 variant)
Cheers and thanks in advance if anyone can save my Canadian bacon.
Edit for background information: I've tried forcing an update via SmartSwitch (RIP Kies) but it says the device is up to date, making me think it's also just checking for an OTA update, but given there's no update available on my wireless network it just dead ends.

S10+ Appears To Be Incapable of Software Updates After Switching Carriers

Hi all,
I have an S10+ that refuses to acknowledge that its software is out of date.
I bought a US Cellular Galaxy S10+ from the Samsung website when the phones launched in March 2019. In late August 2019, I decided to switch to AT&T (had previously been on my parents' plan, wanted to start my own). I transferred the phone and my number over to AT&T.
Recently, I noticed that I have not received a software update or security update since before I switched. My Android version is still 9, my kernel is dated Aug 7, 2019, and my security patch level is Aug 1, 2019.
No matter what I do, my phone says its software is up to date.
I took the following actions:
Called AT&T to have them update the phone in their servers or whatever it is they do.
Changed the date in the phone, restarted and searched for updates.
Cleared the cache data in the phone's BIOS.
Tried using Smart Switch, it said it was up to date.
Did a factory reset of my phone.
Contacted Samsung, was told to talk to my carrier.
Called AT&T again, was told they could not push the updates because the IMEI number is for a US Cellular phone, not an AT&T phone.
Today, I took it to a Samsung representative at a local Best Buy. He plugged the phone in to whatever PC tool he has, it prompted him to download the latest AT&T firmware. He did so and tried flashing the phone. I looked and saw the blue BIOS screen where the phone said it was downloading the firmware. However, when it finished and he started the phone up again, the phone's software information was unchanged. He tried it a second time, and still no change. He told me he had never seen a phone refuse the firmware like this, and he said there was nothing he else he could think of to try. He said even if I could flash the firmware, it might still refuse to receive updates and I'd have to keep flashing it to get all the updates. His suggestion was to just wait and try to see if I could get a deal on an S20.
This phone is paid off, and still in great condition. I'd really rather not have to replace it less than a year after I got it. I've thought about trying to flash the phone myself with Odin, but I'm not sure whether I need to try it with AT&T firmware or US Cellular firmware. Furthermore, I can't find AT&T firmware for the SM-G975U, only the SM-G975U1, and I'm not even sure if it's up to date. What are your suggestions?

You could try updating using the Frija & Odin method found in News & Discussion board, then see if next month you receive OTA?

RuthlessNate said:
Hi all,
I have an S10+ that refuses to acknowledge that its software is out of date.
I bought a US Cellular Galaxy S10+ from the Samsung website when the phones launched in March 2019. In late August 2019, I decided to switch to AT&T (had previously been on my parents' plan, wanted to start my own). I transferred the phone and my number over to AT&T.
Recently, I noticed that I have not received a software update or security update since before I switched. My Android version is still 9, my kernel is dated Aug 7, 2019, and my security patch level is Aug 1, 2019.
No matter what I do, my phone says its software is up to date.
I took the following actions:
Called AT&T to have them update the phone in their servers or whatever it is they do.
Changed the date in the phone, restarted and searched for updates.
Cleared the cache data in the phone's BIOS.
Tried using Smart Switch, it said it was up to date.
Did a factory reset of my phone.
Contacted Samsung, was told to talk to my carrier.
Called AT&T again, was told they could not push the updates because the IMEI number is for a US Cellular phone, not an AT&T phone.
Today, I took it to a Samsung representative at a local Best Buy. He plugged the phone in to whatever PC tool he has, it prompted him to download the latest AT&T firmware. He did so and tried flashing the phone. I looked and saw the blue BIOS screen where the phone said it was downloading the firmware. However, when it finished and he started the phone up again, the phone's software information was unchanged. He tried it a second time, and still no change. He told me he had never seen a phone refuse the firmware like this, and he said there was nothing he else he could think of to try. He said even if I could flash the firmware, it might still refuse to receive updates and I'd have to keep flashing it to get all the updates. His suggestion was to just wait and try to see if I could get a deal on an S20.
This phone is paid off, and still in great condition. I'd really rather not have to replace it less than a year after I got it. I've thought about trying to flash the phone myself with Odin, but I'm not sure whether I need to try it with AT&T firmware or US Cellular firmware. Furthermore, I can't find AT&T firmware for the SM-G975U, only the SM-G975U1, and I'm not even sure if it's up to date. What are your suggestions?
Click to expand...
Click to collapse
Settings > About > Software Information > Service Provider SW Ver
What does it show for you over there?
Your phone is probably still on the US Cellular CSC.
I'd recommend flashing the G975U1 ATT firmware if you want ATT features, or the XAA firmware, to convert your device to a completely unbranded variant with no carrier apps.
You can use SamFirm or Frija to get the firmwares.
Use 'SM-G975U1' as the model and for the CSC, use 'ATT' if you want the AT&T firmware, or 'XAA' if you want the unbranded firmware.
Flash it with patched Odin here:
https://androidfilehost.com/?fid=6006931924117912211
You will have to wipe/reset the entire phone with this process, so make sure to use Smart Switch to backup your data.

MeltdownSpectre said:
Settings > About > Software Information > Service Provider SW Ver
What does it show for you over there?
Your phone is probably still on the US Cellular CSC.
I'd recommend flashing the G975U1 ATT firmware if you want ATT features, or the XAA firmware, to convert your device to a completely unbranded variant with no carrier apps.
You can use SamFirm or Frija to get the firmwares.
Use 'SM-G975U1' as the model and for the CSC, use 'ATT' if you want the AT&T firmware, or 'XAA' if you want the unbranded firmware.
Flash it with patched Odin here:
https://androidfilehost.com/?fid=6006931924117912211
You will have to wipe/reset the entire phone with this process, so make sure to use Smart Switch to backup your data.
Click to expand...
Click to collapse
Hey, thanks for the advice.
My service provider software information version is:
SAOMC_SM-G975U_OYN_ATT_PP_0039
R58M20FYAKW
ATT/ATT/USC
I've looked at both Frija and SamFirm/Updato. Frija doesn't seem to recognize ATT or OYN as a CSC for me when I try using it in the auto search for either SM-G975U or SM-G975U1. Updato has an AT&T firmware, but it's from Nov 2019 and is still Android 9. SamMobile claims to have more up to date firmware, but their download links always send me to the registration page, even after I already registered (I'm guessing they're not as free as they claim to be).

RuthlessNate said:
Hey, thanks for the advice.
My service provider software information version is:
SAOMC_SM-G975U_OYN_ATT_PP_0039
R58M20FYAKW
ATT/ATT/USC
I've looked at both Frija and SamFirm/Updato. Frija doesn't seem to recognize ATT or OYN as a CSC for me when I try using it in the auto search for either SM-G975U or SM-G975U1. Updato has an AT&T firmware, but it's from Nov 2019 and is still Android 9. SamMobile claims to have more up to date firmware, but their download links always send me to the registration page, even after I already registered (I'm guessing they're not as free as they claim to be).
Click to expand...
Click to collapse
Ah, it seems like your device has switched to the ATT CSC but remained on a US cellular build, resulting in there being no available update file on the ATT server.
Download the XAA unbranded G975U1 firmware with Frija.
I completely forgot that ATT doesn't host their firmware files on Samsung servers, instead it uses its own servers for updates.
Updato and SamMobile are both greedy and want you to pay for uncapped download speeds so I wouldn't recommend using them.

With patched Odin can change the csc? I have G977B and cannot change the csc.

DeXTeRrR said:
With patched Odin can change the csc? I have G977B and cannot change the csc.
Click to expand...
Click to collapse
Only applies to US variants when switching from G975U to G975U1.
It's 'patched' as it bypasses the model number check.

MeltdownSpectre said:
Only applies to US variants when switching from G975U to G975U1.
It's 'patched' as it bypasses the model number check.
Click to expand...
Click to collapse
Thank you.

It took me forever to find someone with this problem / solution.
I switched from Verizon to Xfinity Mobile and had not received a security patch since Oct '21 and was still on Android 11.
You'd think that this problem occurs often enough that support would know the solution.
Xfinity Mobile told me Samsung was responsible.
Samsung (Best Buy Geek Squad who is certified Samsung Service Center) said Xfinity Mobile is responsible but gave me the idea that the phone might be 'stuck' on Verizon so it can't pull the updates from Xfinity Mobile.
The build was from Verizon.
I installed the latest build from Xfinity Mobile (CHA) for this model phone (SM-G973U) so it now has Android 12 with Dec '22 security patch.
I'm guessing that the updates will work now but I won't find out for 3 months since the S10 is now on quarterly releases.
Thanks 2x.
Scott