Replicant

Looks like a segfault. Could you grab the main logcat buffer of when the problem happens with Replicant? No need to do it for CyanogenMod.

Okay things are getting clear. It seems that we are receiving some junk data on the RFS transport, which probably leads to a declared size bigger than the buffer. Or it may be intended data that we do not know how to handle. In any way, I will come up with a particular ril for you to test. It is easy to fix this, but I would like to understand what that data is and how the proprietary RIL reacts to it.

(Note to self: build a ril with hexdump of the rfs buffer, check that declared length <= defined max length and log something when it happens.)

In the meantime, it would be great if you could provide full logs from CyanogenMod (the ones you uploaded has the beginning truncated), on the first boot after replacing the battery.

Can you tell me how the command should be to run on the Terminal Emulator not to get a truncated log?
Thanks.

The best way is to run adb logcat -b radio from the host computer a bit after the phone booted up and you unlocked the sim card. Don't wait more than a minute or two or the log will be truncated.

You should rather enable usb debugging (that's adb) in CyanogenMod and get logs via adb so that the buffer isn't truncated. I think that's why your logs are still truncated. We should really see the RIL starting up, which is not yet the case here :( I could probably work without these full logs but I'd prefer to know exactly what happens and how the proprietary implementation reacts to it, and your current logs don't show that.

This could be the problem: I haven't found the option to enable ist. Not at this version of CyanogenMod. Maybe I have to use another version of CyanogenMod. I have already searched this option yesterday but I was unable to find it. Is there a specific version where you know where usb debuging is available?

If you're using CM 10.1 or later, you have to follow that procedure:
Settings > About phone > Tap Build number 10 times or so > Developer settings should be enabled > Go back > Developer options > Root access for Apps and Adb > Enable Android debugging

You need a recent Android SDK to have adb working (the Replicant versions of adb will not work because they're too old).
Then you can :

sudo adb start-server
adb logcat -b radio

Great, that's a full log now! Is this actually a log with the replaced battery (basically, boot once with the original battery, then turn the device off, replace the battery, turn it on and get radio logs). This may only happen on the first boot after the battery was replaced. If it is, I won't be asking you anymore log. Thanks for your patience by the way!

Ahhhh now I understand, it's a very long multipart RFS message! I know for sure that we don't handle that properly.
Finally this last batch of logs was exactly what I needed to know, so I won't bother you anymore and will come with a fix!

I am experiencing the same thing now. #717 reports the same behavior as well.

Many thanks, it's working!!!

Apparently, this issue causes nv_data to become corrupt. If you made a backup of /efs, restoring it after installing the fixed libsamsung-ril.so would be a good idea. If not, it is possible that the device runs with the default IMEI. There are ways to manually change the IMEI back to its correct number.