January Security/Software Update

the 2 January updates...a Verizon thing?

Sent from my SM-S908U1

I don't think so. I'm running the unlocked firmware, not the Verizon firmware. My device was purchased unlocked directly from Samsung, and I've been running the unlocked firmware ever since I got it.
 
the 2 January updates...a Verizon thing?
You mean the BWA2 update? It's not the 2nd January update for everyone, either in the sense of the 2nd update released in January, or in the sense of the 2nd update released with the Jan 1 Android Security Patch Level. Some major carriers never released the earlier BVL4 update.

But BWA2 was released several days ago by all major US carriers. As always, you can find the list at sammobile.com, or you can check using Frija.
 
I got mine for AT&T unlocked
 

Attachments

  • Screenshot_20230122_215851_Software update.jpg
    Screenshot_20230122_215851_Software update.jpg
    190.4 KB · Views: 32
Last edited:
Just downloaded the January update on my unlocked S22 Ultra on the Spectrum Mobile network.
 
I can't, for the life of me, understand AT&T treating their flagship model the way they have. My locked S22Ultra is sitting on Sept 1 Security patch with UI 4.1 and Android 12. My wife's locked S21U is on Android 13 and UI 5.0 and my Mom and my Sons Locked A13 are both on Android 13 and UI5.0. I have tried every trick that I have seen, back dating the date, forward dating the date, putting in a different carrier sim.. I have worn out the update check button on my screen because it no longer even teases me by trying to check. I even rebooted into the Samsung boot menu and cleared cache. I have reset the phone from Android 12s menu, and from the Samsu g boot menu. Freji can't find the file for SM-908U nor can Smart Switch. This is a straight up 1st world problem, I understand, but dayum.

Sent from my SM-S908U using AC Forums mobile app
 
I can't, for the life of me, understand AT&T treating their flagship model the way they have. My locked S22Ultra is sitting on Sept 1 Security patch with UI 4.1 and Android 12. My wife's locked S21U is on Android 13 and UI 5.0 and my Mom and my Sons Locked A13 are both on Android 13 and UI5.0. I have tried every trick that I have seen, back dating the date, forward dating the date, putting in a different carrier sim.. I have worn out the update check button on my screen because it no longer even teases me by trying to check. I even rebooted into the Samsung boot menu and cleared cache. I have reset the phone from Android 12s menu, and from the Samsu g boot menu. Freji can't find the file for SM-908U nor can Smart Switch. This is a straight up 1st world problem, I understand, but dayum.

Sent from my SM-S908U using AC Forums mobile app
Att devices had this problem going back from S9 series, it gets stuck on a update and doesn't move past it so you have to flash with Odin to the latest and hopefully gets it going for further updates, best bet to flash unlock firmware you won't have these issues again
 
I can't, for the life of me, understand AT&T treating their flagship model the way they have. My locked S22Ultra is sitting on Sept 1 Security patch with UI 4.1 and Android 12. My wife's locked S21U is on Android 13 and UI 5.0 and my Mom and my Sons Locked A13 are both on Android 13 and UI5.0. I have tried every trick that I have seen, back dating the date, forward dating the date, putting in a different carrier sim.. I have worn out the update check button on my screen because it no longer even teases me by trying to check. I even rebooted into the Samsung boot menu and cleared cache. I have reset the phone from Android 12s menu, and from the Samsu g boot menu. Freji can't find the file for SM-908U nor can Smart Switch. This is a straight up 1st world problem, I understand, but dayum.

Att devices had this problem going back from S9 series, it gets stuck on a update and doesn't move past it so you have to flash with Odin to the latest and hopefully gets it going for further updates, best bet to flash unlock firmware you won't have these issues again

Yeah, that was a nagging problem for a small, but not insignificant number of AT&T users for several years. However, it seemed to be mostly fixed over the past two years.

But as you see, it's not completely fixed. AT&T never acknowledged the issue in the first place, but over at the AT&T support forums, you could tell that it wasn't an isolated issue or device specific either. The best that any of us fellow customers could figure was that somehow the back-end updates servers would lose the connection between an account and the IMEI of the device. Therefore, while a customer service rep could see your phone, the update servers could not. The rep could initiate a command to update your phone (a common remedy), but the update server would never see the phone, thus the phone never receives it. Customer calls the rep and the update command is sent again, the phone never receives it again... wash, rinse and repeat.

Once in a while, something finally clicks, and the updates finally come in. This started happening more often about two years ago now and those that complained about not getting updates on that AT&T forum finally started getting them.

But not everyone.

As Mustang says however, many found that by manually loading the firmware yourself, that tends to kick something in gear so that suddenly subsequent updates finally finds your phone on AT&T's network. We aren't sure what does it exactly, or why, but it's something.

BTW, Frija can't find the firmware because the phone is branded as AT&T and AT&T phones get their firmware from AT&T's servers. Not from Samsung's servers where every other carrier and unlocked phones gets theirs. Frija only looks for the firmware from Samsung's update servers.

Luckily, AT&T branded Samsung phones can have firmware loaded outside of AT&T. It just has to be proper Samsung firmware.
 
Yeah, that was a nagging problem for a small, but not insignificant number of AT&T users for several years. However, it seemed to be mostly fixed over the past two years.

But as you see, it's not completely fixed. AT&T never acknowledged the issue in the first place, but over at the AT&T support forums, you could tell that it wasn't an isolated issue or device specific either. The best that any of us fellow customers could figure was that somehow the back-end updates servers would lose the connection between an account and the IMEI of the device. Therefore, while a customer service rep could see your phone, the update servers could not. The rep could initiate a command to update your phone (a common remedy), but the update server would never see the phone, thus the phone never receives it. Customer calls the rep and the update command is sent again, the phone never receives it again... wash, rinse and repeat.

Once in a while, something finally clicks, and the updates finally come in. This started happening more often about two years ago now and those that complained about not getting updates on that AT&T forum finally started getting them.

But not everyone.

As Mustang says however, many found that by manually loading the firmware yourself, that tends to kick something in gear so that suddenly subsequent updates finally finds your phone on AT&T's network. We aren't sure what does it exactly, or why, but it's something.

BTW, Frija can't find the firmware because the phone is branded as AT&T and AT&T phones get their firmware from AT&T's servers. Not from Samsung's servers where every other carrier and unlocked phones gets theirs. Frija only looks for the firmware from Samsung's update servers.

Luckily, AT&T branded Samsung phones can have firmware loaded outside of AT&T. It just has to be proper Samsung firmware.
Yeah lot of them i recommend and helped get the samung unbranded/unlocked firmware to avoid future issues with this , its exactly how you mentioned to some users.

Sent from my Pixel 7 Pro using Tapatalk
 
I had the no update issue with my s8 plus, note 9, and note 10. It didn't correct until the note 20 ultra and luckily my s22 ultra is still getting the updates.

Sent from my SM-S908U using AC Forums mobile app
 

Trending Posts

Forum statistics

Threads
957,864
Messages
6,974,731
Members
3,163,925
Latest member
dftyuc