Project

General

Profile

No network on Samsung GT-i9300 (Solved)

Added by bagel bagel over 4 years ago

Thanks to the excellent instructions on the Wiki, I succeeded in installing Replicant 4.2 on a Samsung GT-i9300.

After startup, no network is found (or maybe the SIM is not found).

I see a spinning network icon the notification bar.

In phone status, I see "Unknown" for IMEI, IMEI SV, My phone number, Network. Mobile network type is UNKNOWN:0.

I am in North America with a T-Mobile SIM in the phone.

Attached is output of logcat of a full boot-try-to-look-at-network-then-shutdown session.

Any tips/hints/clues? What am I looking for in the log?

Thanks in advance!

log_with_sim_sanitized.txt (136 KB) log_with_sim_sanitized.txt adb logcat but redacted

Replies (8)

RE: No network on Samsung GT-i9300 - Added by bagel bagel over 4 years ago

Here are radio logs for another boot. Only redacted a file md5sum.

I have no basis for which messages are important and which are not (yet), but this might be helpful:

D/RILB ( 2483): Notifying: radio not available
D/RILJ ( 2483): [0048]< GET_SIM_STATUS error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
D/GSM ( 2483): [GsmSST] Poll ServiceState done: oldSS=[3 home null null null Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] newSS=[1 home null null null Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] oldGprs=1 newData=1 oldMaxDataCalls=1 mNewMaxDataCalls=1 oldReasonDataDenied=-1 mNewReasonDataDenied=-1 oldType=Unknown newType=Unknown
D/RILJ ( 2483): [0049]< SCREEN_STATE error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
D/GSM ( 2483): [GsmSST] updateSpnDisplay: radio is on but out of service, set plmn='No service.'
D/RILJ ( 2483): [0050]< RADIO_POWER error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
D/RILJ ( 2483): [0051]< BASEBAND_VERSION error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
D/GSM ( 2483): [GsmSST] updateSpnDisplay: changed sending intent rule=0 showPlmn='true' plmn='No service.' showSpn='false' spn=''
D/RILJ ( 2483): [0052]< GET_IMEI error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
D/RILJ ( 2483): [0053]< GET_IMEISV error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
D/RILJ ( 2483): [0055]< GET_SIM_STATUS error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
D/RILJ ( 2483): [UNSL]< UNSOL_RESPONSE_CALL_STATE_CHANGED
D/RILJ ( 2483): [UNSL]< UNSOL_RESPONSE_VOICE_NETWORK_STATE_CHANGED
D/RILJ ( 2483): responseDataCallList ver=7 num=0
D/RILJ ( 2483): [UNSL]< UNSOL_DATA_CALL_LIST_CHANGED []
D/GSM ( 2483): [GsmSST] operatorNumeric is null
D/RILJ ( 2483): [UNSL]< UNSOL_RESPONSE_SIM_STATUS_CHANGED
D/RILJ ( 2483): [0056]> GET_CURRENT_CALLS
D/RIL_UiccController( 2483): Received EVENT_GET_ICC_STATUS_DONE
D/RIL ( 1891): 1 RIL request in the queue (1 pending, 0 handled, 0 unhandled)
E/RIL_UiccController( 2483): Error getting ICC status. RIL_REQUEST_GET_ICC_STATUS should never return an error
E/RIL_UiccController( 2483): com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
E/RIL_UiccController( 2483): at com.android.internal.telephony.RILRequest.onError(RIL.java:185)
E/RIL_UiccController( 2483): at com.android.internal.telephony.RIL.processSolicited(RIL.java:2460)
E/RIL_UiccController( 2483): at com.android.internal.telephony.RIL.processResponse(RIL.java:2211)
E/RIL_UiccController( 2483): at com.android.internal.telephony.RIL$RILReceiver.run(RIL.java:598)
E/RIL_UiccController( 2483): at java.lang.Thread.run(Thread.java:856)
D/RIL_UiccController( 2483): Received EVENT_GET_ICC_STATUS_DONE
E/RIL_UiccController( 2483): Error getting ICC status. RIL_REQUEST_GET_ICC_STATUS should never return an error
E/RIL_UiccController( 2483): com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
E/RIL_UiccController( 2483): at com.android.internal.telephony.RILRequest.onError(RIL.java:185)
E/RIL_UiccController( 2483): at com.android.internal.telephony.RIL.processSolicited(RIL.java:2460)
E/RIL_UiccController( 2483): at com.android.internal.telephony.RIL.processResponse(RIL.java:2211)
E/RIL_UiccController( 2483): at com.android.internal.telephony.RIL$RILReceiver.run(RIL.java:598)
E/RIL_UiccController( 2483): at java.lang.Thread.run(Thread.java:856)
D/RILJ ( 2483): [0057]> GET_CURRENT_CALLS
D/RIL ( 1891): 2 RIL requests in the queue (2 pending, 0 handled, 0 unhandled)

RE: No network on Samsung GT-i9300 - Added by bagel bagel over 4 years ago

Also tried cm-11-20150412-NIGHTLY-i9300.zip from https://download.cyanogenmod.org/get/jenkins/106772/cm-11-20150412-NIGHTLY-i9300.zip and it did not connect to the phone network either.

Checked the IMEI at an IMEI checking site and it came up clean.

Is it usually necessary to enter APN information in the phone?

What else am I missing?

RE: No network on Samsung GT-i9300 - Added by Paul Kocialkowski over 4 years ago

It seems like there is something wrong with your /efs/ partition. Please check its contents and the rights.

You might want to paste the output of adb shell busybox ls -la /efs/ with ADB running as root here.

RE: No network on Samsung GT-i9300 - Added by bagel bagel over 4 years ago

./adb shell busybox ls la /efs/
drwxrwx--x 9 radio system 4096 Feb 7 10:54 .
drwxr-xr-x 16 root root 0 Apr 27 10:06 ..
drwxrwxr-x 5 root root 4096 Jan 1 2012 .files
-rw-r--r-
1 root root 1048576 Jan 1 2012 .nv_core.bak
rw-r--r- 1 root root 32 Jan 1 2012 .nv_core.bak.md5
rwx----- 1 radio radio 2097152 Jan 1 2012 .nv_data.bak
rw-r--r- 1 root root 32 Jan 1 2012 .nv_data.bak.md5
rw-r--r- 1 root root 1 Jul 19 2012 .nv_state
rw-r--r- 1 root root 152 Jul 19 2012 00000000.authtokcont
drwxr-xr-x 2 root root 4096 Jan 1 2012 FactoryApp
drwxrwxr-x 2 radio system 4096 Jul 19 2012 bluetooth
drwxr-xr-x 2 system system 4096 Jan 1 2012 carrier
drwxrwxr-x 3 drm system 4096 Jan 1 2012 drm
rw-r--r- 1 root root 6 Jul 19 2012 gyro_cal_data
rw-r--r- 1 root root 1100 Dec 31 2011 h2k.dat
drwxrwxr-x 2 radio system 4096 Jan 1 2012 imei
rw-r--r- 1 root root 4116 Jan 1 2012 nv.log
rw-r--r- 1 root root 2097152 Mar 11 09:58 nv_data.bin
rw-r--r- 1 root root 32 Mar 11 09:58 nv_data.bin.md5
drwxrwxr-x 2 radio system 4096 Jan 1 2012 wifi
rw-r--r- 1 root root 220 Jul 19 2012 wv.keys

RE: No network on Samsung GT-i9300 - Added by bagel bagel over 4 years ago

Is the ownership of nv_data.bak being radio:radio a clue that nv_data.bin ought to also be radio:radio and not root:root?

Also, it seems backing up all of /efs/ at this point would be wise?

Poking around the web, it seems uid 1001 is what people pass to chown to set ownership to radio, so would my next step be something like the following?

./adb shell busybox chown 1001:1001 /efs/nv_data.bin

Or, could it be I need an nv_core.something unhidden in /efs/?

I understand that /efs/ oddities (bad unlocking job?) might be beyond the scope of this forum, but solving the issue is germane to my running replicant and may help others run replicant too.

RE: No network on Samsung GT-i9300 (Solved) - Added by bagel bagel over 4 years ago

Changing ownership of nv_data.bin as suggested above solved it.

RE: No network on Samsung GT-i9300 (Solved) - Added by Paul Kocialkowski over 4 years ago

Is the ownership of nv_data.bak being radio:radio a clue that nv_data.bin ought to also be radio:radio and not root:root?

Right

Also, it seems backing up all of /efs/ at this point would be wise?

Sure

Poking around the web, it seems uid 1001 is what people pass to chown to set ownership to radio, so would my next step be something like the following?

That's a bit weird to use the uid directly, you could just use busybox's version of chown and use the user name directly.

Changing ownership of nv_data.bin as suggested above solved it.

Great!

RE: No network on Samsung GT-i9300 (Solved) - Added by Wolfgang Wiedmeyer over 2 years ago

A user contacted me about the same issue (n_data.bin owned by root), so the issue probably affects more users that have no network or the SIM card doesn't get recognized. I'm wondering if it's worth creating a section "Troubleshooting" in the wiki and collect issues like these if there are more.

    (1-8/8)