Project

General

Profile

Actions

Issue #2223

open

Lost phone modem connectivity

Added by Nepsis Localhost almost 4 years ago. Updated almost 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
02/25/2021
Due date:
% Done:

0%

Estimated time:
Resolution:
Device:
Galaxy S 3 (I9300)
Grant:
Type of work:

Description

Hi!

I'm new to the ambiances of Replicant, and in first of all, let me congratulate and show my utmost respect for this project.
I'll call it a diamond in nowadays PRISM et al world.

To put it to use, I've bought a used Samsung SIII (i9300), for my old one was not charging anymore (hardware fault?).
And yet while using heimdall and reproducing the steps, like indicated -- or I guess I did -- maybe I've missed something:
- the OS was sucessfully installed; or at least it booted in Replicant.
- no SIM card was recognized; no IMEI indication as well;
- installed stock rom; no SIM card recognized as well;
- Installed lineage; no SIM card recognized.
- IMEI doesn't appear anywere;
- Reinstalled Replicant.
Device with Replicant although without comms.

But if its modem drivers work, I'll sure use it as my daily driver: GSM is needed to be in touch :-)
Can this be related to some nvram, baseband overwritten? Is my device "modem-bricked"?

Is there something I can do to restore GSM for it? It was working before I tried to install Replicant.

Best Regards


Files

radio.log (80.1 KB) radio.log Nepsis Localhost, 02/25/2021 07:13 PM
Actions #1

Updated by Denis 'GNUtoo' Carikli almost 4 years ago

If the device boots fine and that IMEI doesn't show up, there is still some hope.

One of the possibilities here would be that the modem firmware is corrupted.

If you have a backup of the modem firmware partition, you could try to restore it.

You can also try to obtain logs with 'adb logcat -b radio' once you get root access on your device (the wiki has information on how to do that). The logs have more information on what is going on.

Note that if you get it working somehow, you should make sure to backup the modem data partition. There is a tutorial for that here: BackupTheEFS. This is because, unlike the modem firmware partition, this modem data partition (EFS) is device specific: it contains your IMEI and we don't know yet how to change the IMEI to be able to use another EFS as a basis to repair a device.

edit1: improved clarity

Denis.

Actions #2

Updated by Nepsis Localhost almost 4 years ago

Denis 'GNUtoo' Carikli wrote in #note-1:

If the device boots fine and that IMEI doesn't show up, there is still some hope.

One of the possibilities here would be that the modem firmware is corrupted.

If you have a backup of the modem firmware partition, you could try to restore it.

You can also try to obtain logs with 'adb logcat -b radio' once you get root access on your device (the wiki has information on how to do that). The logs have more information on what is going on.

Note that if you get it working somehow, you should make sure to backup the modem data partition. There is a tutorial for that here: BackupTheEFS. This is because, unlike the modem firmware partition, this modem data partition (EFS) is device specific: it contains your IMEI and we don't know yet how to change the IMEI to be able to use another EFS as a basis to repair a device.

edit1: improved clarity

Denis.

Thank you very much for the reply.

I took the liberty to attach the log you asked me o see, and honestly, with my lack of experience in this subject, it doesn't say much to me.

What does it sound to you?

Thank you

Actions

Also available in: Atom PDF