- May 6, 2015
- 294
- 0
- 0
UPDATE: AT&T tried rolling me out uosayes with no success so they replaced my phone and all seems well on the new device.
Unlocked on Att don't seem to have this problem , it's the carrier version and if you look here in the Forums with Att users it's been plenty since Note 9/S9 series I've known and helped here.I feel lucky not to have experienced this issue with my AT&T Samsungs. But hanging out on the AT&T support forums has certain made me aware of the problem.
AT&T and Samsung blaming each other sounds normal, but AT&T knows they are the ones that control the OS rollout to the phones they sell.
However, as best some of us can tell, it seems the issue is that AT&T does not always get the right IMEI in their back-end OS distribution system. The account system may have it right, but somehow it gets lost on the back end, causing a break where the phone just isn't seen to ever get the OS. That's possibly why even if you get tech support to force sending the OS, it still doesn't get to the phone - possible IMEI mis-match. This is all speculation, but AT&T sure ain't trying to figure out the problem.
It also could be why unlocked phones have problems as well with AT&T.
If using Odin is not possible, you could try to find the nearest uBreakiFix store. They can usually directly upgrade the OS. But you'll have to do a backup as their process usually wipes the system memory to factory defaults.
Hopefully it stays that way going forwardUPDATE: AT&T tried rolling me out uosayes with no success so they replaced my phone and all seems well on the new device.