6
SM-996B/DS - not receiving calls, probably as a result of latest update (G996BXX...
source link: https://forum.xda-developers.com/t/sm-996b-ds-not-receiving-calls-probably-as-a-result-of-latest-update-g996bxxu5cvf3.4462619/page-4#post-87164465
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
SM-996B/DS - not receiving calls, probably as a result of latest update (G996BXXU5CVF3)
Thread starter
Start date
After seeing that some people got the July update and the issue wasn't resolved, I've rolled back to the May release and surprise surprise, everything works great now.
Disabled firmware updates for now, thanks @Furious Froyo for the commands.
It's a shame that the device is just 1.5 years old and the software update renders most basic functionality unusable, with no acknowledgment or a fix in sight. All reports go through the same tedious and useless process which ends with "send us your device".
Honestly, being a long-time user (since S2), I'm disappointed in Samsung, hope they get better and fix this mess.
Disabled firmware updates for now, thanks @Furious Froyo for the commands.
It's a shame that the device is just 1.5 years old and the software update renders most basic functionality unusable, with no acknowledgment or a fix in sight. All reports go through the same tedious and useless process which ends with "send us your device".
Honestly, being a long-time user (since S2), I'm disappointed in Samsung, hope they get better and fix this mess.
sbi1
Senior Member
Oct 7, 2011
Boston area
I received July's update this morning (BTU). Was optimistic at first but the optimism went away when I clicked on "What's new" and the only thing that was listed was "The security of your device has improved".
After install and reboot, sure enough as reported before me, Samsung did not fix the problem, so now I am backing up and will fresh flash May firmware.
I am still on the fence about disabling auto updates. I don't really have to update even when they push them, the only 'annoyance' is the repeated notifications. We'll see.
To me, the really frustrating thing is not that the update screwed my phone. $%^& happens, I get it...it shouldn't have, but it happens.
The one thing I am pissed about is that Samsung just don't listen and evern worse - there's no one to talk to. You call the US (because you are in the US), they tell you "oh, no, this is a UK phone, we can't help". You call the UK - "Sorry, you are in the US, you need to call Samsung where you are". You try to explain to them that hundreds if not thousands of people are having the same issue with different models, they insist on walk you through the usual bull$%^& of turning airplan mode on/off, etc.
I emailed Samsung, they received the email because they responded and also called me and confirmed that they read what I reported - but it falls on deaf ears. They just don't care.
After install and reboot, sure enough as reported before me, Samsung did not fix the problem, so now I am backing up and will fresh flash May firmware.
I am still on the fence about disabling auto updates. I don't really have to update even when they push them, the only 'annoyance' is the repeated notifications. We'll see.
To me, the really frustrating thing is not that the update screwed my phone. $%^& happens, I get it...it shouldn't have, but it happens.
The one thing I am pissed about is that Samsung just don't listen and evern worse - there's no one to talk to. You call the US (because you are in the US), they tell you "oh, no, this is a UK phone, we can't help". You call the UK - "Sorry, you are in the US, you need to call Samsung where you are". You try to explain to them that hundreds if not thousands of people are having the same issue with different models, they insist on walk you through the usual bull$%^& of turning airplan mode on/off, etc.
I emailed Samsung, they received the email because they responded and also called me and confirmed that they read what I reported - but it falls on deaf ears. They just don't care.
Reactions: Wrafas and MercuryMat
Wrafas
New member
Jul 4, 2022
I received the July updated and the issue is still existing. Such a disappointment from Samsung. This should not happen to a phone from them
Reactions: MercuryMat
Wrafas
New member
Jul 4, 2022
I received July's update this morning (BTU). Was optimistic at first but the optimism went away when I clicked on "What's new" and the only thing that was listed was "The security of your device has improved".
After install and reboot, sure enough as reported before me, Samsung did not fix the problem, so now I am backing up and will fresh flash May firmware.
I am still on the fence about disabling auto updates. I don't really have to update even when they push them, the only 'annoyance' is the repeated notifications. We'll see.
To me, the really frustrating thing is not that the update screwed my phone. $%^& happens, I get it...it shouldn't have, but it happens.
The one thing I am pissed about is that Samsung just don't listen and evern worse - there's no one to talk to. You call the US (because you are in the US), they tell you "oh, no, this is a UK phone, we can't help". You call the UK - "Sorry, you are in the US, you need to call Samsung where you are". You try to explain to them that hundreds if not thousands of people are having the same issue with different models, they insist on walk you through the usual bull$%^& of turning airplan mode on/off, etc.
I emailed Samsung, they received the email because they responded and also called me and confirmed that they read what I reported - but it falls on deaf ears. They just don't care.
Did you have to wipe your data / do a factory reset by downgrading?
sbi1
Senior Member
Oct 7, 2011
Boston area
Yes, and now the phone is working as it should, including receiving calls (pardon my sarcasm towards Samsung).Did you have to wipe your data / do a factory reset by downgrading?
I didn't "manually" reset the phone, just did a flash with ODIN and I did CSC insteadof HOME_CSC, this will wipe the device.
I didn't get to disable updates via ADB yet.
Reactions: MercuryMat and Wrafas
Wrafas
New member
Jul 4, 2022
Would it be possible to flash an older HOME_CSC and save the files?
sbi1
Senior Member
Oct 7, 2011
Boston area
I don't know, I didn't even try because when you update it specifically says you cannot revert back to the older firmware.Would it be possible to flash an older HOME_CSC and save the files?
Besides, even if it works, I would not take the risk of anything that may have caused the issue staying behind.
Would it be possible to flash an older HOME_CSC and save the files?
I've used HOME_CSC but even after the flash was successful, the phone was boot looping into download mode.
In the end, I had to wipe it through recovery mode and then everything was working great.
As a best practice, don't ever flash your phone without doing a full backup before.
I did all of them, Google, Samsung Cloud, Smart Switch on Windows, WhatsApp (and some other apps I use, make sure to go over yours), and also the manual backup of files, images, screenshots, etc to my NAS.
After the phone booted up and I did the first initial setup, I restored everything with Smart Switch.
Good luck!
Auxityne
New member
Jul 15, 2022
Same thing happened to me with my unlocked S21+, but it's an SM-G996U1 in the USA. CVF1 broke text and calls. CVF5 failed to fix the problem. CVDC, the May patch, works perfectly, so I executed a forced downgrade and have been stuck without security updates until this gets resolved.
My carrier is helpless to fix the problem and has hundreds of other people with the same issue. Samsung is absolutely silent.
My carrier is helpless to fix the problem and has hundreds of other people with the same issue. Samsung is absolutely silent.
Reactions: sbi1 and MercuryMat
Let me tell you my saga about this problem. The last build my phone (SM-G996B/DS) worked correctly was G996BXXU5CVDD; after that I received the update G996BXXU5CVF1 it was when the AT&T voice call was broken. Call-in and call-out became impossible. After several talks to Samsung customer service and AT&T support I followed the ultimate option, "factory reset". No fix. The solution was:
- Fallback to G996BXXU5CVDD using Samsung's tool.
- Using adb, uninstall two packages that cause requests for upgrade.
Reactions: sbi1
There was another update G996BXXS5CVFB that did not fix the problem too.
Reactions: sbi1
Auxityne
New member
Jul 15, 2022
I've gotten a response from Samsung support at last and it seems like they're blaming my mobile network, citing a PCSCF IP null list error.
I of course asked why my phone works fine on said network unless I update to the June or July patches. No reply.
I of course asked why my phone works fine on said network unless I update to the June or July patches. No reply.
Top Liked Posts
-
Yes, and now the phone is working as it should, including receiving calls (pardon my sarcasm towards Samsung).Did you have to wipe your data / do a factory reset by downgrading?
I didn't "manually" reset the phone, just did a flash with ODIN and I did CSC insteadof HOME_CSC, this will wipe the device.
I didn't get to disable updates via ADB yet.
Respectively,1. Which exact version did you use?
2. Can I downgrade without wiping or factory resetting the phone?
3. Did you use CSC_HOME or CSC?
4. Is there any "must-do" steps (other than full backup obviously) that should be done before downgrading? Like removing Google and Samsung accounts from the phone prior to downgrading.
1. For my specific phones, I used 'G991BXXU5CVDD' dated 2022/05/10 on 'sammobile.com'. Something I noticed on my S21s, when I went into the download mode (phone off, plug in USB cable, then hold vol up & down and tap side button), the phone told me the carrier the phone is tied to (in red font no less). In my case this is XSP (Singapore). This might help you figure out exactly what firmware you are supposed to use.
2. I soft bricked one of my phones since I found out that Odin3 doesn't like *any* of my workstation's USB ports (Asrock TRX40 Taichi motherboard running a Threadripper 3970x). I tried a bunch of different ports and different USB cables (side note: I used the latest Samsung USB drivers). The download would start then fail at various points (seemingly never the same point). This actually ended up being my main time suck, otherwise I would have had a resolution much sooner. Switched to my laptop (Lenovo T480s) and it worked flawlessly as before with my S10s, S8s, etc. I fixed the soft brick error using FRP Hijacker.
Neither of the two phones did I do a wipe or factory reset, but I proceeded as if I was as to not have any data loss potential.
3. CSC.
4. Full backup via SmartSwitch and backing up chat history in Signal, Kakaotalk, and WhatsApp. After the firmware write, I did a full restore via SmartSwitch and then the respective chat history restores. Keep in mind this is my specific case. You might have other apps that need specific attention paid to past SmartSwitch.I received July's update this morning (BTU). Was optimistic at first but the optimism went away when I clicked on "What's new" and the only thing that was listed was "The security of your device has improved".
After install and reboot, sure enough as reported before me, Samsung did not fix the problem, so now I am backing up and will fresh flash May firmware.
I am still on the fence about disabling auto updates. I don't really have to update even when they push them, the only 'annoyance' is the repeated notifications. We'll see.
To me, the really frustrating thing is not that the update screwed my phone. $%^& happens, I get it...it shouldn't have, but it happens.
The one thing I am pissed about is that Samsung just don't listen and evern worse - there's no one to talk to. You call the US (because you are in the US), they tell you "oh, no, this is a UK phone, we can't help". You call the UK - "Sorry, you are in the US, you need to call Samsung where you are". You try to explain to them that hundreds if not thousands of people are having the same issue with different models, they insist on walk you through the usual bull$%^& of turning airplan mode on/off, etc.
I emailed Samsung, they received the email because they responded and also called me and confirmed that they read what I reported - but it falls on deaf ears. They just don't care.There was another update G996BXXS5CVFB that did not fix the problem too.
Thanks @blackhawk .It wipes the user data partition I believe which you should do anyway to avoid a conflict.
I never had to reflash any of my Samsung's. Android's aren't the easiest to flash and I avoid it if at all possible. One reason I don't update or upgrade a good load... just not worth the trouble.
Regardless always assume all data will be lost and back it up, redundantly. This should already be the case; while stock Android's are very stable and crashes very rare, they can happen at anytime with little or no warning. Especially if you're messing with the firmware.
In this case, I'll probably just do a complete wipe (after a backup of course) and do everything myself. This is really pissing me off that Samsung sends OTA "Update" (no funky business, no roots, stock phone) that basically turns it into a brick.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK