17-09-2021 09:51 AM
23-09-2021 11:57 AM - last edited 23-09-2021 11:57 AM
24-09-2021 08:17 AM - last edited 24-09-2021 08:18 AM
Yes, I just talked to the service team. There's not enough users affected by this error in order to motivate them to work on a fix, what they suggested were to hand in the phone to Samsung and get it replaced. Not happy with the response since I have a Snapdragon, they'll most likely try to replace it with an Exynos which obviously isn't the same thing. I'll update on how smooth the phone replacement/compensation goes.
24-09-2021 08:23 AM
24-09-2021 09:42 AM - last edited 24-09-2021 09:43 AM
I know right, I think their initial response was an attempt to make me feel content. I've been in further contact with my local Samsung repair shop. They wont accept my phone. Apparently warranty is strictly region bound and only an Asian repair shop are able to work on my phone.
Given the issue is purely software, which I heavily suspect - there are two paths going forward. First, patiently wait for One UI 4 beta to drop. Potentially it could make everything work all of a sudden, in the same way last update made everything not work all of a sudden... If that won't fix it, the last option is root and flash some custom ROM, either LOS/AOSP or maybe change region code on the phone in order to flash an EU ROM (sine hardware wise, the Korea model supports the GSM bands utilized within EU).
A curve ball would be the scenario where some circuit regarding SIM & baseband got fried during the latest firmware upgrade. That would mark end of life for this phone.
24-09-2021 03:29 PM - last edited 24-09-2021 03:32 PM
24-09-2021 07:10 PM - last edited 24-09-2021 07:11 PM
Oh wow, that really sucks. July! I'm shocked the software downgrade didn't fix the problem. Either some drivers or module separate from the core ROM got overwritten with new instructions, which later on doesn't get overwritten by downgrading to an older OS, since the module have already have later instruction sets with later revision numbers. In that case the phone would need to be fully wiped on all levels, not just OS. Then get a fresh set of matching software, preferably the latest confirmed functioning OS.
The pattern does honestly feed the theory of some obscure hardware defect (so obscure that Samsung's diagnostic tools aren't programmed to even look for this odd issue).
I can't think of any other possible scenario.
I have been in quite a lot of software development with Android and I work with wireless network communication. I have never encountered this odd of a behavior, not with any Samsung or any other manufacturers. And I've gone through A LOT of devices.
24-09-2021 07:19 PM - last edited 24-09-2021 07:21 PM
01-11-2021 11:23 PM
Worked for me after October 1st update. Thanks
15-11-2021 03:56 PM
15-11-2021 05:04 PM
Still not working.. placing all my hopes in one UI 4, unfortunately there's no beta files in circulation for SM-G9810.
Also, Samsung service still refuses to touch or help me with my device.