A53 UI8/Android 16 Software Update SIM not recognized

[josec41]

I am using an A53 on T-Mobile and everything was working OK until the day before yesterday when the Android 16 / One UI 8 update was applied, now my phone is saying the SIM card is no longer recognized.  I went into the carrier local office and they swapped out the SIM with a new one, same issue. They then took that SIM into an different phone and it worked, this is clearly an issue introduced with the update. Going through the message boards it is easy to find other instances of the same issue occurring on other Samsung phones.

While not a brick, the phone is useless right now, is there anything that I can do to get this phone working again?

[meself]

Did you clear the phone cache

[Mujibar]

So they just swapped out your SIM instead of reprovisioning the old one? Nice way to do the least amount of work. Did you reset mobile network settings on the phone?

[josec41]

Here's some more detail I probably should have included. So before I went to the T-Mobile store I factory reset the phone (so the cache was as clear as it's ever going to get) which didn't help anything, at that point I brought it in to the T-Mobile store. T-Mobile checked the SIM's provisioning and everything was correct but the phone still didn't work. Then the SIM was swapped with a new one and it still didn't work, then they put the new SIM in a demo Motorola phone and it worked right away. The rep did mention to me that this was at least the 3rd phone she saw come in with the same problem.

Then I opened a chat with Samsung support. that's an hour of my life I'll never get back, useless conversation, especially after the chat person said he didn't know what a ticket was. He advised me to bring the phone into a local uBreakiFix to get it repaired so I called them. The person who answered mentioned that they also saw a phone come in for repair and they tried to replace some boards in it which didn't help the issue. Then the chat rep said to send the phone in for repair because he said it was a hardware issue.

Wow

[Mujibar]

Ok, that's a little different than how it was presented at first. It very well could have been a corrupted update. If you do send the phone to Samsung, just know that you might be without it for some time. You'll want to have another device you can use.

[meself]

Not sure hardware issue got in with update but as @Mujibar said maybe the uodate failed or didn't complete

[meself]

Potential solutions

Restart the device: A simple restart can fix temporary display and performance issues.

Clear the cache partition: This can help with battery drain and general performance. To do this, boot into recovery mode and select "wipe cache partition" (for some devices, you may need to connect to a computer first).

Reset network settings: This can fix Wi-Fi, mobile data, and Bluetooth connection problems by erasing saved passwords and pairings. Go to Settings > General management > Reset > Reset network settings.

Reset the One UI Home launcher: If you are having problems with the home screen, you can reset the launcher by going to Settings > Apps, finding One UI Home, and clearing both the cache and data.

Check for app updates: Ensure all your apps are updated to their latest versions after the system update, as this can resolve compatibility issues.

[josec41]

Thanks for the suggestions, still no luck. I went into recovery mode, cleared cache and also did a factory reset from there with no luck. Once I rebooted the phone, I applied all app updates from both the Google Playstore and Samsung Appstore and still the same. Powered the phone down for 5 minutes and rebooted, nothing changed. When i drag down on the screen to see notifications, the messages No service and (Searching) flash across the top left of the screen. Attached is a screenshot of the SIM card status.

[Members_geKkIKh]

Hi,  

Misery loves company?  I have done all the steps suggested by Samsung, Mint Mobile and those that were mentioned here.  I Contacted the carrier MINT (owned by T-mobile) and T-mobile directly, because I am a glutton for punishment.  Each one points to the other entity for the source of the UI-8 update. I have been constantly discussing with each entity since Monday, the 17th. 

I tried a 7 day trail Mint sim card and it works in a different phone but the same thing happens with this sim, once it is put into the A53.  No luck, two working sims don't seem to appear in the updated UI-8 phone.

I also dropped off the phone at a Samsung authorized shop.  The initial finding was nothing wrong with the phone but they could try to replace the daughter board for the sim tray and see it that fixes it.  Not really a confidence boost for a solution?  Update - just got a call and they think it is the main board now.  This seems to be a common solution / suggestion from other sites I have read.

I get the same screen as shown (in black) for SIM card status and for the same price of admission, the connections screen loses the mobile setting option and Mobile Hotspot and Tethering. 

My next step was to source a replacement A53.  It worked fine out of the box with the Mint sim card.  I restored all my data to the replacement.  Overnight it updated to UI-8 and guess what?  The replacement phone no longer has any network capability.  I know two points don't make a trend, but i bet Amazon will stop me from buying more A53s and returning them when the update disables them?  Just a guess on my part.

I also manually updated/flashed my original phone with these files "SM-A536U1_XAG_A536U1UEUHGYIB_fac", I was told the XAG might denote Xfinity/T-Mobile as the carrier code/prefix? 

Nothing has worked yet, so I am convinced that the problem is with the update and maybe the association with T-Mobile?  I'm sure Samsung will not agree with this assessment???

   After (UI-8 /16)            Before Update (UI-7 /15)

Just to add insult to injury, my wife has an A53 with Tracfone and the update was not a problem.

Any advice or suggestions would be greatly appreciated.  I can still rent a steam roller to "fix" it for good.

[Members_geKkIKh]

Update - Good news for me.  

My salvation came in the form of a kind and excellent technician named Andrew, at Batteries Plus in Seekonk, Massachusetts (999 Fall River Avenue).  He actually listened to the facts I presented and kept an open mind regarding this being a possible software problem.

This was unexpected and greatly appreciated, as I was just starting the painful search for another phone.  I am really happy with the A53 and didn't want to switch to another, only to find out the update will turn the device into a paper weight, over and over again.

I would suggest that if you are in close proximity to this store, and you have this problem that you contact them.  It is definitely better than trying to get help from Samsung directly. Also it somewhat validates the hypothesis that it is not likely a hardware issue but something deficient in the software update relative to the A53 and possibly isolated to T-Mobile/Mint subscribers?

Maybe some one at Samsung should congratulate him for his prowess with this device.  He really saved my relationship with regard to future Samsung products.