Database Develop

[Q] No call sound after back to stock

Hi guys,
I know there are many similiar threads to this one and I'm sure I've read most of them. Either my issue is different, or, if the answer was in one of them, I was too stupid to realize it.
With my S4 Active GT-I9295 I had to go back to stock ROM for the Samsung S-Health and Gear related apps.
I came from spegelius' (absolutely awesome) Google Edition for SGS4A (int'l) v0.9.9.-od2 and flashed the Samsung Stock 4.4.2 with Odin (*). The procedure was: Flash -> Factory Reset -> Flash again to be absolutely sure all files are updated. Currently, I rooted the phone.
My problem persists:
After a reboot I (usually; not always) am able to make normal phone calls.
After some time (sometimes minutes, sometimes hours) I no longer have sound.
I do not hear ringing, the callee can't hear me, I can't hear the callee.
Same problem if I'm being called
Establishing a connection though works always.
Mobile Data is not affected.
WiFi works
Also observed after factory reset -> re-flash, only enter WiFi PW and Google Login Data -> try phone call
I know this problem often arises from a baseband/modem mismatch. So I investigated my CWM backup of the pre-installed 4.2.2 ROM.
That's what was pre-installed:
Bootloader: I9295XXUBMK3
CSC: I9295OXXBMK3
Modem: *I did not find the info in my backup*
This corresponds to the Romanian 4.2.2: http://www.sammobile.com/firmwares/download/22586/I9295XXUBMK3_I9295OXXBMK3_ROM.zip/
That's why I flashed the direct successor http://www.sammobile.com/firmwares/download/37083/I9295XXUCNI1_I9295OXXCNI1_ROM.zip/
PDA: I9295XXUCNI1
CSC: I9295OXXCNI1
MODEM: I9295XXUCNI1
I tried everything I could find online, nothing helped. I am really running out of ideas. Is it possible to go back to 4.2.2 to see if the problem persists?
I do have logcat logs of the radio module before and after the problem occured. But its thousands of lines. If it helps I can upload it!
Thank you guys for your help
(*): I did some intermediate flashing of several other firmware versions (especially different baseband / CSC versions of the same 4.4.2). But I assume this does not affect the result. I used Odin v3.07 & v3.09
Edit: PS: I still think that I might have the wrong CSC Version. I know the 4.2.2 PDA/CSC matches, but I am not from Romania. I'm actually from Germany. And what makes me wonder is that I cannot select the German Keyboard Style without downloading it first. I can't remember doing something similar after unboxing the phone and setting it up for the first time.

Are you aware of this thread?
http://forum.xda-developers.com/showthread.php?p=56955843
Bevare the Thanks Button

Thanks for the answer O-T!
Yes, I was aware of that thread. However, I never made it until here
http://forum.xda-developers.com/showthread.php?p=50787570
Although I did the things basically as described in that posts I have a new question:
Which country is relevant for the search on sammobile? I mean, do they ask me "Where do you live" or "For which country was your device produced?".
Edit: Okay actually they ask me for the 'product code', so it's probably the latter question.
I realized that my 4.2.2 PDA and CSC also match the French version. That would match the language of my original packaging. I already flashed the French 4.4.2 once but heard only noise when calling someone. So I gave up on that one quickly. But I'll give it another shot now.
Is it possible that I had a factory installation of the firmware for country A, and when I first registered with my local carrier I received a modem update OTA for country B?
That would really surprise me. But it could explain my issues, since there is no 4.4.2 for o2 Germany, i.e. I probably wouldn't receive another modem update OTA.
(I never looked into the carrier specific firmwares because I figured they are for sim-locked devices.)
If the above is true, I understand that the only option would be to somehow downgrade my device back to 4.2.2.
I know I'm asking a lot of questions that have been asked and answered elsewhere. But by now I tried so much and nothing worked that I'm really confused and need your guidance.

I know I type too much, so a short summary.
Everything I tried so far didn't help, the stock ROM from sammobile.com doesn't help, currently I'm on 4.4.2 XEF (France)
I'm 80% sure I have the firmware for the correct country
From factory-side I definitely had an XX PDA and OXX CSC, so shouldn't all XX/OXX versions work, even if not the exact country?
What should I try next?
Is there a way to uniquely identify the country code from a backup of the /system or /data parition?

hyperion89 said:
I know I type too much, so a short summary.
Everything I tried so far didn't help, the stock ROM from sammobile.com doesn't help, currently I'm on 4.4.2 XEF (France)
I'm 80% sure I have the firmware for the correct country
From factory-side I definitely had an XX PDA and OXX CSC, so shouldn't all XX/OXX versions work, even if not the exact country?
What should I try next?
Is there a way to uniquely identify the country code from a backup of the /system or /data parition?
Click to expand...
Click to collapse
I am not sure if you have done this, but one thing I always recommend is a phone factory reset from settings (not CWM/TWRP) when you are on stock firmware as this is known to correct a lot of issues caused mainly due to faulty partition / corruption. However beware of the fact that this will wipe your internal SD card therefore back it up before you do that.
If you have flashed the correct firmware for your country & carrier (if it has a separate one) where you are using the phone, and done the above then I do no see any other issue than a faulty IC that requires replacement

JASONRR said:
I am not sure if you have done this, but one thing I always recommend is a phone factory reset from settings (not CWM/TWRP) when you are on stock firmware as this is known to correct a lot of issues caused mainly due to faulty partition / corruption. However beware of the fact that this will wipe your internal SD card therefore back it up before you do that.
Click to expand...
Click to collapse
Yes, I always did a factory reset. Most of the times I even flashed the firmware a second time after the factory reset. (This was recommended somewhere else.)
JASONRR said:
If you have flashed the correct firmware for your country & carrier (if it has a separate one) where you are using the phone, and done the above then I do no see any other issue than a faulty IC that requires replacement
Click to expand...
Click to collapse
Now that really helps me! Thanks. BUT: There is a seperate firmware for my carrier. However, I did not purchase the phone from that carrier. That's why I never tested the carrier specific firmware. Moreover, there is only the old 4.2.2 available, so I can't test it, since I cannot downgrade.

hyperion89 said:
Now that really helps me! Thanks. BUT: There is a seperate firmware for my carrier. However, I did not purchase the phone from that carrier. That's why I never tested the carrier specific firmware. Moreover, there is only the old 4.2.2 available, so I can't test it, since I cannot downgrade.
Click to expand...
Click to collapse
You can flash only the modem & non-holos from the 4.2.2 firmware and check

JASONRR said:
You can flash only the modem & non-holos from the 4.2.2 firmware and check
Click to expand...
Click to collapse
Tried it and it didn't work; completely crashed my Phone Application. It rang on the other side, but no conversation was possible. Is this because of the bootloader / modem mismatch?
Does anyone have instructions to safely downgrade to 4.2.2 again? Should I open another thread for this discussion?

hyperion89 said:
Tried it and it didn't work; completely crashed my Phone Application. It rang on the other side, but no conversation was possible. Is this because of the bootloader / modem mismatch?
Does anyone have instructions to safely downgrade to 4.2.2 again? Should I open another thread for this discussion?
Click to expand...
Click to collapse
Identify the bootloader version and Knox state:
http://forum.xda-developers.com/showthread.php?p=57332718
Knox is not a counter - it's a like a fuse.

Hi O-T,
the bootloader is I9295XXUBMK3 and it does not yet have the warranty bit which I assume you mean by KNOX state.
Are there maybe any new ideas?

hyperion89 said:
Hi O-T,
the bootloader is I9295XXUBMK3 and it does not yet have the warranty bit which I assume you mean by KNOX state.
Are there maybe any new ideas?
Click to expand...
Click to collapse
There's 3 stock 4.2.2 TW ROM I9295XXUBMK3 to choose for flash by Odin. All have different Germany CSC (Carrier Specific Code) - Generic, O2, T-Mobile. PDA=MODEM=I9295XXUBMK3 for all of them. Not sure if O2 or T-Mobile versions are locked, but they usually have operators bloat apps.
Remember to power OFF before entering download mode, flash ROM in Odin, factory reset.
https://www.samdownloads.de/download/i9295xxubmk3-dbt-4-2-2-germany/
https://www.samdownloads.de/download/i9295xxubmk3-via-4-2-2-germany-o2/
https://www.samdownloads.de/download/i9295xxubmk3-dtm-4-2-2-germany-t-mobile/
Your choice.

O-T I'm so sorry. My post from yesterday was a lie; I can't read my own OP. :crying: :angel:
I9295XXUBMK3 was preinstalled
Now I'm on I9295XXUCNH2, which implies 4.4.2 and makes a downgrade to 4.2.2 impossible (afaik).
Please note that I already tried the generic German (4.4.2) firmware. I never had operater bloat apps and I bought a simlock-free version of the device. Thus I never tested the o2 / T-Mobile ones. (I did, however, once flash the o2 modem over the generic 4.4.2, which turned out to be a bad idea).
I would love to extract the modem info from my CWM backup. The bootloader / CSC strongly suggest I have a French phone, but the modem would ultimately clarify that.
What is your opinion on trying a different custom-ROM? I never built one so I have no idea from where designers obtain their NON-HLOS and modem files. I know many don't come with any of those and require an already working ROM before flashing so these drivers can be kept. On the other hand, Darkman's StockyROM has an additional modem pack.... which, in my case, didn't help.
I simply cannot believe that it's a hardware issue. Everything worked fine until the update to 4.4.2 and new radio drivers should be thoroughly tested before distribution.

Help with IMEI Unknown

Good morning,
This cellphone is from a cousin which already sent this phone twice to techservice and it came back this way. Everything seems to be working except that it has no IMEI and no baseband.
What I know is it was never flashed with custom images, just official ones and it is currently with Android 4.4.2.
Any ideas?
Thank you in advance!

fggs said:
Good morning,
This cellphone is from a cousin which already sent this phone twice to techservice and it came back this way. Everything seems to be working except that it has no IMEI and no baseband.
What I know is it was never flashed with custom images, just official ones and it is currently with Android 4.4.2.
Any ideas?
Thank you in advance!
Click to expand...
Click to collapse
Hi, easy way, go to play store and download this apk Network Mode, and change the frecuency of the radio, press the tree pionts ,select Automatic, let he apk works; when finished check your baseand and imei back again, cheers.

Hi! Thanks for your answer! I did exactly what you said, but when I try to select Automatic it just says it failed. Any ideas?!

Hummmm, if you try whit Euro or Usa banda?

Tried every single option, same result

The rom , is an update from a recovery or you douwnload the update fron the ROM?

As far as I know, the update was downloaded from within JellyBean.

One time have the same isue like you, I solved this way, ...............................................

I need help please

First i know i'm an idiot, i thought i knew what i was doing but i had no idea, i figured how hard could it be I've rooted a G1 and a Droid Eris.... but alas i was way over my head.
I have a Note 9 from KSA (Saudi Arabia) i'm a contractor there and it was way cheaper than buy in the states plus a dual sim variant. i tried flashing to the Detonator T-mobile rom, and now i'm left with a phone i can not use, I did not create a partition, i have backup all my personal data, but the original firmware is in the ether. I flashed what i thought was a dual sim international firmware, but all it did network lock my phone so god knows what international network, since neither my T-mobile or STC sim work in it. On top of that even though it has a "stock firmware" it's still rooted so knox has been triggered and even if my sim's worked all Knox linked programs wont work.
So what i need from you fine Ladies' and Gentlemen is a solution to get it as close to the stock version as possible, at this point dual sim functionality or the Wifi calling i was trying to flash on to it are second to having the phone function as a proper note 9 again. IF anyone has the stock firmware or knows of a place where i can get the original firmware, no i'm not asking for hacked version, yes i'm willing to pay for it as long as it works. Any help would be greatly appreciated.

Yeah, I know that Samsung devices purchased in the UAE are partitioned differently than those purchased in the rest of the world. I would recommend that you repartition the storage in your device and reinstall the stock OS back onto it again. That should resolve yoru issue. I don't know how to do this. Maybe somebody else can chime in a help you out.

iceepyon said:
Yeah, I know that Samsung devices purchased in the UAE are partitioned differently than those purchased in the rest of the world. I would recommend that you repartition the storage in your device and reinstall the stock OS back onto it again. That should resolve yoru issue. I don't know how to do this. Maybe somebody else can chime in a help you out.
Click to expand...
Click to collapse
do you by chance know where the Partition would be because i had not had any luck locating it. or the firmware for that specific region.

Samri13 said:
do you by chance know where the Partition would be because i had not had any luck locating it. or the firmware for that specific region.
Click to expand...
Click to collapse
Ok i got the correct firmware loaded, does anyone know how to Unlock network?

Samri13 said:
Ok i got the correct firmware loaded, does anyone know how to Unlock network?
Click to expand...
Click to collapse
Look up-thread, there's another person (besides you and I) whose had the problem and found solution.

Note 9 ATT ROM Update SEPT 2019

Hi everyone.
Below is the link for last update for Note ATT.
{https://androidfilehost.com/?fid=1899786940962593461}
I've trying to update the ATT note 9 , but is very difficult to found the update.
Finally I found this link for TMobile, and is working 100% actually on my ATT phone.
All the applications are working ok, and the ATT apps are woking too.
On my first try I forgot use the USER DATA using ODIN and phone stuck on updating logo.
Then I've reinstalled using, AP,BL, CSC, CP, AND USER DATA, and all works OK.
Please remember
"Backup all your data previously with Samsung SMART SWITCH"
""""FLASH IT UNDER YOUR RISK"""
On my phone is working perfectly.

I was just about to do this myself. Figured it'd be ok. Still running right? And is there a change in Service Provider SW version or does it self-correct based on SIM?

Sticks210 said:
I was just about to do this myself. Figured it'd be ok. Still running right? And is there a change in Service Provider SW version or does it self-correct based on SIM?
Click to expand...
Click to collapse
My phone was updated using the rom provided in the link.
All is working OK at this moment , without any problem.
All the options and applications still working without issues
Nothing in Service provider was changed , still sending ATT logo during normal restart or reboot.
Also still unlocked like before update.

Thunderxxx said:
My phone was updated using the rom provided in the link.
All is working OK at this moment , without any problem.
All the options and applications still working without issues
Nothing in Service provider was changed , still sending ATT logo during normal restart or reboot.
Also still unlocked like before update.
Click to expand...
Click to collapse
Can confirm its working flawlessly for me as well.

On further use background data is trash, and sound work that great over the built in speakers. Trying to find the causes. Radio issue isn't that surprising, audio is.

Just got OTA on Att U2CSI3. Pretty sure its October security patch.
Sent from my SM-N960U using Tapatalk

Got the update today also. October security but no clue what if anything else.

Yeah with other carriers they usually show a change log..but At&t, nope..lol
Sent from my SM-N975U using Tapatalk

butchieboy said:
Yeah with other carriers they usually show a change log..but At&t, nope..lol
Click to expand...
Click to collapse
They never do. It's like they love keeping us in the dark

KingVekxin said:
They never do. It's like they love keeping us in the dark
Click to expand...
Click to collapse
Guess I should give up searching for more info then.

pixel 4 xl mobile network problem

need some help here , my pixel 4 xl just updated to jan 2021 update
, post update im unable to connect to mobile network .
already tried hard reset not working
also flashed previous factory image still aint working
is any other thing i can try to solve the problem or im doomed?

capayam said:
need some help here , my pixel 4 xl just updated to jan 2021 update
, post update im unable to connect to mobile network .
already tried hard reset not working
also flashed previous factory image still aint working
is any other thing i can try to solve the problem or im doomed?
Click to expand...
Click to collapse
Who is your provider? Are you using SIM or eSIM? Are you rooted? Did you disable all the Magisk modules before the update? If you forgot that step, have you since disabled all Magisk modules and started over?
While you may be out of commission on the phone side (although, Google Voice would be a good band-aid), you may not be out of commission on the SMS side. Google's text app, Messaging, recently went live with RCS messaging and it can send texts via WiFi.
Incidentally, if it's Google Fi that's giving you fits, the same thing happens to me every time I do a clean install. Fi refuses to connect until I've rebooted two or three times and then the final confirmation comes several hours later.

im in malaysia bought secondhand 1 year ago on grey market , check my sim with another phone , working well on that phone. had been running my phone on regular stock since bought.

capayam said:
im in malaysia bought secondhand 1 year ago on grey market , check my sim with another phone , working well on that phone. had been running my phone on regular stock since bought.
Click to expand...
Click to collapse
Okay, you answered almost none of my questions but it's irrelevant at this point because it sounds like the phone was stolen. If the IMEI is reported as stolen, it's flagged in a database and alerted carriers will shut off the service.
If that's the case, at this point, I'd be more concerned about the police knocking on my door than lack of mobile service. I'd send you over to IMEI.info to verify but I'm guessing I haven't told you anything you didn't already know.

imei number legit not reported or blacklisted, but yeah i think this phone is doomed unless there some magic update resolved this

capayam said:
imei number legit not reported or blacklisted, but yeah i think this phone is doomed unless there some magic update resolved this
Click to expand...
Click to collapse
Why don't you try to reset using the last official 10 firmware (to reset all partitions), then activate through setup, then flash and test a custom rom. This is of course only possible if it's an unlocked bootloader (which you didn't mention) but that's where I'd start especially if it worked before the update. You say is legit and sounds like it worked BEFORE the last update so roll back and then use a custom rom.

GROOVYJOSHCLARK said:
Why don't you try to reset using the last official 10 firmware (to reset all partitions), then activate through setup, then flash and test a custom rom. This is of course only possible if it's an unlocked bootloader (which you didn't mention) but that's where I'd start especially if it worked before the update. You say is legit and sounds like it worked BEFORE the last update so roll back and then use a custom rom.
Click to expand...
Click to collapse
will try it later dude

capayam said:
will try it later dude
Click to expand...
Click to collapse
Unfortunately it's my best guess because I can't reproduce it myself but if it worked prior to the firmware upgrade, it should work by reverting the firmware to the previous firmware in my opinion. I'd take it the step furtherand go with a custom 10 ROM to remove Google firmware updates messing with it in the future (assuming we get it working again).
Interestingly enough, I searched other forums and found other users reporting the same issue. Again, assuming it worked on the previous firmware, I would roll bak to it. Ideally, I would rollback to 10 because I know 10 works (not sure how well it works for you in your local and provider), but thats where I would start. Backup everything you need, then use the last 10 firmware to -w the device and activate then start over.

Why is this posted in development?

shiftr182 said:
Why is this posted in development?
Click to expand...
Click to collapse
who knows