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.

Optimus L90 Unable to Root, Unable to boot into recovery mode

Hi
I have gone through the forums and can't seem to find solution for my problem with my Optimus L90 phone.
I have recently flashed the CM13 on my phone without any errors but below are the issues that I am facing
1. No cellular network signal after inserting SIM card.
2. I read in a different forum that this could happen due to using a wrong version of TWRP, so installed a newer version 2.8.7.0 but things worse.
3. Now I am not able to boot into recovery mode and phone just stays idle with the LG logo screen and few commands appearing like fastboot_iniy() and udc_start().
4. I have tried hard reset and soft reset and both are not successful.
5. I cannot root my phone either. Tried all ways like towelroot, purpledrake, lg root by avicoh etc but in vain
Now my phone, even though has a latest CM version I cannot use it for anything else.
Any help is greatly appreciated.

No SIM is hardly related to TWRP, probably you needed a different bootstack (there is a thread about it).
On CM you don't need anything to root, it's already rooted just not visible to common users, you need to activate Developer Options (it's also explained elsewhere)
Finally, if you cannot reach recovery but still can boot CM13 simply use adb, Flashfy or Hashr to flash another version or TWRP. 2.8.7 is kinda old and not recommended for Marshmallow, you can try 3.0.2 by SlimShady or DarkBlue version from shoxxy's thread.

Thanks for the reply, let me try options you have specified and get back if I am still facing issues

hvramanan said:
Thanks for the reply, let me try options you have specified and get back if I am still facing issues
Click to expand...
Click to collapse
I was able to unblock my phone finally and loaded the stock ROM but the phone is still isn't recognizing cellular network . I am on T-MOBILE. I have tried to insert different SIM, turned off wifi calling but still the phone is not catching any cellular network.
[lfom]: you indicated earlier that a different bootstack might be needed. I am not that knowledgeable about bootstack so can you help me through this or point me to different thread where users might have a similar issue.

Sorry, I meant to say unbrick above

Everything one needs or wants to know about bootstack is here:
http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632

lfom said:
Everything one needs or wants to know about bootstack is here:
http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632
Click to expand...
Click to collapse
Hi,
I followed the steps mention in the above thread to change the bootstack and was able to complete it without any issues, however the problem still persists and my phone is not recognizing the SIM and does not catch the cellular network.
Previously I used to use this phone with my t-mobile number and after I took a new phone haven't been using it for sometime. I want to sell this phone and was trying to ensure that it works fine and thats when I saw that the phone is not catching any cellular networks.
Please help. Let me know if you need any other details to better diagonize the problem.

hvramanan said:
Hi,
I followed the steps mention in the above thread to change the bootstack and was able to complete it without any issues, however the problem still persists and my phone is not recognizing the SIM and does not catch the cellular network.
Previously I used to use this phone with my t-mobile number and after I took a new phone haven't been using it for sometime. I want to sell this phone and was trying to ensure that it works fine and thats when I saw that the phone is not catching any cellular networks.
Please help. Let me know if you need any other details to better diagonize the problem.
Click to expand...
Click to collapse
You didn't say what model you have, maybe you flashed the wrong bootstack for your model (hardware version)? Be very careful, you can hart brick your device, and if it's a D415 it's very hard to unbrick. I'd suggest that first you make sure what model you have by removing the battery and looking in the label below, it says what model you have. Then, use LG Flash Tool to flash stock ROM (KDZ) to latest KitKat, then flash Lollipop or use OTA to update to latest version. The only requirements are that you make sure what model you have and flash the corresponding version, and the phone is still able to enter download mode.

lfom said:
You didn't say what model you have, maybe you flashed the wrong bootstack for your model (hardware version)? Be very careful, you can hart brick your device, and if it's a D415 it's very hard to unbrick. I'd suggest that first you make sure what model you have by removing the battery and looking in the label below, it says what model you have. Then, use LG Flash Tool to flash stock ROM (KDZ) to latest KitKat, then flash Lollipop or use OTA to update to latest version. The only requirements are that you make sure what model you have and flash the corresponding version, and the phone is still able to enter download mode.
Click to expand...
Click to collapse
[lfom]: thank you for responding. My phone model is LG-D415 . Actually my phone was bricked but I was able to get into download mode and then I used the L90 Hardbrick tool to flash stock ROM (KDZ) to latest kitkat like you have specified above. Then with the OTA update I was able update it to latest lollipop. Then I followed this forum below to to change the bootstack to KK 10C version as the issue specified in the below thread was similar to mine.
http://forum.xda-developers.com/lg-l90/development/rom-cyanogenmod-12-lg-l90-t3049512/page235
Image of the label inside my phone attached.
Do you think I should have used the LG flash tool to flash stock ROM. Should I repeat the steps with the LG flash tool ?
Thank you again for helping me on this.

Do you see your IMEI in the about phone page? Does it match the one in the label? Maybe when you bricked you've lost the phone's IMEI, and you can't get it back just flashing ROM...

lfom said:
Do you see your IMEI in the about phone page? Does it match the one in the label? Maybe when you bricked you've lost the phone's IMEI, and you can't get it back just flashing ROM...
Click to expand...
Click to collapse
Yes I checked and it matches. There two fields IMEI which has the number and then there is another field which says IMEI SV and it has a value of 02 in it.

Baseband Unknown

Hi. I got a serious trouble please some one help me. Strangely yesterday my xt 1254 ran out of service i checked but didn't find sim menu. And baseband unknown while imei was missing too. I rebooted device and all got ok sim worked badeband ok & imei shown. But the problem is after sometime( 1 or 2 hour later) my device again ran into same problm. And aftee that the problem continues for sometime baseband works after sometime it gets unknown no sim no imei please help me to get out of this. Thanks

Looks like no one helps noobs

Not that no one helps noobs, but not many people check here any more.
1) The real Droid Turbo forum is over at Moto Maxx, where all the updated Moto Quark custom ROMs are.
2) This phone is 4 years old. No one comes here anymore with a "new" problem. So, feel free to SEARCH for previous answers.
https://forum.xda-developers.com/search/forum/3715?query=baseband
3) Are you still running stock firmware? Is your bootloader unlocked and you're on a custom ROM? What version firmware are you running? You don't mention any of that, which may be relevant.
* If you're still on stock, the best thing to do is reflash same firmware or newer to reset the modem. Be very careful it's not older firmware, or you will brick the phone (if your bootloader is still locked).
* If you're running custom ROM, the best thing is to flash the BHB27 clear modem file in TWRP and then reflash your modem in TWRP. There's TWRP-FLASHABLE modem zip files available for all Moto QUARKS.

A single answer and i got all i want. Thank you chazzmatt. The problem was faulty baseband chip cz mistakenly my brother fell down the device. Repair guy said me he changed the chip and now all set. Thank you buddy and thanks xda

No SIM / No WIFI: qcn/xqcn files needed to restore IMEI/MAC

Hello All,
November update... It took a whole time to get my phone booting again but I don't have SIM or WIFI anymore.
I think my IMEI's are gone, even as MAC for WIFI.
I tried recovery image (that's what solved the boot problem).
I took backups but some parts seems to be corrupted so I can't recover from there.
Does someone have the (x)qcn available for flashing over QPST (or even over TWRP to change afterwards over QPST)?
I found different versions online but I think it's checked against model number; mine is: M1804D2SG (SI doesn't work)
Yes... I will change your IMEI!
Thanks!

honda4life1 said:
Hello All,
November update... It took a whole time to get my phone booting again but I don't have SIM or WIFI anymore.
I think my IMEI's are gone, even as MAC for WIFI.
I tried recovery image (that's what solved the boot problem).
I took backups but some parts seems to be corrupted so I can't recover from there.
Does someone have the (x)qcn available for flashing over QPST (or even over TWRP to change afterwards over QPST)?
I found different versions online but I think it's checked against model number; mine is: M1804D2SG (SI doesn't work)
Yes... I will change your IMEI!
Thanks!
Click to expand...
Click to collapse
Did you try to flash older build of stock rom?

Flash via MiFlash Tool, that worked for me

MiFlash tried,
I tried most recent version that was available, but yes that's an older version.
The corrupted data isn't even in the recovery rom.

https://forum.xda-developers.com/mi-a2/how-to/how-to-fix-sensors-camera-stock-pie-10-t3914885 I saw a few people on telgram that fixed wifi and sim with flashing persist partition.

mariosenta said:
https://forum.xda-developers.com/mi-a2/how-to/how-to-fix-sensors-camera-stock-pie-10-t3914885 I saw a few people on telgram that fixed wifi and sim with flashing persist partition.
Click to expand...
Click to collapse
Does not work unfortunately, just tried. In that topic it's more about sensors etc. not working.

Try flashing global firmware via twrp.

Reven jeremiah said:
Try flashing global firmware via twrp.
Click to expand...
Click to collapse
Also tried without errors but problem not solved.

Please someone upload.
My phone is still bricked :crying:

How may I help you? Give me instructions. Also specifically tell me how to remove my original Imei in that file. I'll then upload the files.

VoLTE fix with Lineage OS if operator of SIM not provisioned

## Disclaimer ##
No waranties of any kind given.
This is a guide following a procedure I tested for myself.
If you do not understand a particulary step refer to documentation provided elsewhere already.
## Prerequisites
You already unlocked a device and know what to do.
You are familiar with shell access and editing files.
* OEM unlock possible and code present
* fastboot
* adb (only tested on Linux)
* latest TWRP
* latest Lineage OS build
in case you come from Lineage OS:
* newflasher
* Xperifirm
* latest stock firmware according to your geographical region
## Guide
Reflash stock firmware if you came from Lineage OS or unlock bootloader
Boot into TWRP
Mount system partition
Mount oem partition of active slot
Edit default modem.conf in oem partition according to files found in /system/etc/customizations/modem for your carrier.
In case you already used your SIM before in that phone: reflash cust-reset.ta with newflasher
Insert SIM if not already present and setup phone
Restart to apply customization for your carrier (VoLTE maybe still not working with stock firmware though customization was applied)
Shutdown
Install Lineage OS (all usual instructions apply)
## References
[GUIDE] Enable VoLTE for your non operator handset
I have finally been able to get VoLTE working on my X Performance despite my carrier never having 'supported' my handset (they never sold it here). What you will need? Windows Computer with Flashtool and minimal ADB and fastboot (if you have...
forum.xda-developers.com

After updating LineageOS 18.1 with built-in updater, my phone was endlessly booting (LineageOS symbol showing for ever).
After following many suggestions, like downloading stock ROM with XperiFirm, installing it with newflasher to slots a and b, sideloading LineageOS again, I finally got the OS running but without sensors and communication devices (WIFI, bluetooth and such). After doing everything again, I have the system running with the sensors and the comm devices but WITHOUT working SIM. :-(
SIM card is recognized, PIN excepted but no radio, i.e. connection to the cell. I get "No SIM card" and I can't connect.
I very much hoped your solution can help getting back to normal but can't since it is very brief and files like modem.conf or /system/etc/customizations don't exist on my phone (at least "find" doesn't find 'em). I can't mount oem partition since TWRP doesn't give me the option.
Could you explain a little more why you had to find that solution in the first place and how exactly you fixed it?
Thank you very much! I'm sure other's will benefit as well.
(I'm a little verbose here because I hope that finding this site is easier with more words in it. Once the explanation is refurbished, many people will be happy.)

olivernetzt said:
After updating LineageOS 18.1 with built-in updater, my phone was endlessly booting (LineageOS symbol showing for ever).
After following many suggestions, like downloading stock ROM with XperiFirm, installing it with newflasher to slots a and b, sideloading LineageOS again, I finally got the OS running but without sensors and communication devices (WIFI, bluetooth and such). After doing everything again, I have the system running with the sensors and the comm devices but WITHOUT working SIM. :-(
SIM card is recognized, PIN excepted but no radio, i.e. connection to the cell. I get "No SIM card" and I can't connect.
Click to expand...
Click to collapse
Sounds like you forgot copy_partitions.zip referred in Lineage OS installation instructions maybe?
I somehow remember this problem in a different context.
olivernetzt said:
I very much hoped your solution can help getting back to normal but can't since it is very brief and files like modem.conf or /system/etc/customizations don't exist on my phone (at least "find" doesn't find 'em). I can't mount oem partition since TWRP doesn't give me the option.
Click to expand...
Click to collapse
I tested with latest generic uk firmware and modified modem.conf only present in oem partition of stock firmware while trying to figure out the whole process. Applying settings needs to be done on stock firmware this way.
olivernetzt said:
Could you explain a little more why you had to find that solution in the first place and how exactly you fixed it?
Click to expand...
Click to collapse
I found no way of modifying required settings in modem partition otherwise so far while thinking about a more generic way which could be applied in Lineage OS directly. Switching SIM / carrier involves applying configurations to baseband which need a reboot so far discovered. I cannot replicate this in Lineage directly.
olivernetzt said:
Thank you very much! I'm sure other's will benefit as well.
(I'm a little verbose here because I hope that finding this site is easier with more words in it. Once the explanation is refurbished, many people will be happy.)
Click to expand...
Click to collapse

Thanks for help, xcalc.
I did sideload (ran) "copy-partitions-20210323_1922.zip". No SIM anyway.
I couldn't modify the files you mentioned since I couldn't see them. Couldn't mount oem partition.
I didn't even switch the SIM card. I've been using the same for many years, different phones, different ROMs.
Anyway, thank and take care.