Updating Security Patch on Locked AT&T Galaxy S8 (SM-G950U)?

[drewid666]

My AT&T Galaxy S8 is locked (contract expires in March, 2020) and is running Android 9. For some reason it will not update the Security Patch and is stuck on March 1, 2019. This is a big problem with all the vulnerability issues going on so I would very much like to patch it before I can upgrade my phone in two months. On the SamMobile website, the October 2019 firmware for the G950U is listed as "G950USQS6DSJ3" with "Country" selections that include TMB, VZW, Sprint and many others. However, there is no selection for ATT. I have two questions:

1. Which carrier firmware should I [safely] use - TMB, VZW, or Sprint?

2. When I run Odin 3.14.1 there is a message that pops up: "Please be sure to delete your Google account (Samsung account) before downloading the binary. It is not possible to use the device without unlocking. Changing the partition without unlocking will cause problems."

Then there's a bunch of Chinese and Japanese language below that. I am totally confused about that warning (deleting Google account before downloading binary and not possible to use without unlocking). Should I remove my Google account from my phone before using Odin or delete my account entirely? Does this mean it's only for unlocked phones?

Any assistance with both questions is much appreciated.

 

[mustang7757]

Re: Updating Security Patch on Locked AT&T Galaxy S8 (SM-G950U)?

First check smart smart switch, if nothing download Odin 3 13.1 and grab TMO or Verizon firmware as carrier firmware are interchangeable.

..I'll leave a link to register so you can communicate here , as a guest account you can't.https://forums.androidcentral.com/showthread.php?t=409154

 

[drewid666]

Re: Updating Security Patch on Locked AT&T Galaxy S8 (SM-G950U)?

Thanks for the reply. I did check Smart Switch and still nothing available to update. Can I ignore the Odin prompt to delete my Google account or should I act upon it? Screenshot attached.

 

[mustang7757]

Re: Updating Security Patch on Locked AT&T Galaxy S8 (SM-G950U)?

Thanks for the reply. I did check Smart Switch and still nothing available to update. Can I ignore the Odin prompt to delete my Google account or should I act upon it? Screenshot attached. View attachment 315135

Hi, welcome!
Where did you get this version of Odin?

 

[hallux]

carrier firmware are interchangeable

I'd be cautious about this statement - using a Verizon build on an ATT device might cause issues with WiFi calling...

 

[mustang7757]

I'd be cautious about this statement - using a Verizon build on an ATT device might cause issues with WiFi calling...

Thank you for heads up but the sim dictate what goes on the phone , all carrier firmware are interchangeable

 

[drewid666]

I got 3.14.1 directly from SamMobile. When I checked it against 3.13.1 there isn't a warning message in 3.13.

 

[mustang7757]

I got 3.14.1 directly from SamMobile. When I checked it against 3.13.1 there isn't a warning message in 3.13.

Use 3.13.1

 

[drewid666]

Thanks Mustang, will do!

 

[mustang7757]

Thanks Mustang, will do!

Your welcome!
Keep me posted!

 

[drewid666]

I tried to flash it with Odin 3.13.1 on two different PCs and it failed to flash in each case. Here's a summary:

1. Ensured that latest Samsung USB drivers were installed via Samsung Smart Switch.
2. Enabled USB Debugging in Developer Options.
3. Followed the instructions from SamMobile.
4. I turned off my phone. Ran Odin and loaded all the MD5's in their respective fields (and used HOME_CSC to preserve user data), except for the USERDATA MD5. No other settings were changed; default boxes in Options tab were checked (F.Reset Time and Auto-Reboot) and Pit tab was left alone.
5. Rebooted phone in Download mode and connected the USB cable.
6. Started Odin.
7. It kept hanging at "PIT for mapping" for several minutes then failed.

 

[drewid666]

I finally got it to work. Ignore the reply #11. The OEM USB cable was not making good contact and I found this out by using a different cable. All good now. Thanks!

 

[mustang7757]

I finally got it to work. Ignore the reply #11. The OEM USB cable was not making good contact and I found this out by using a different cable. All good now. Thanks!

That's great
Your welcome