FORUMS

Analysis & Opinion

Top Forum Discussions

[Q] G2 won't connect to cell network after unlocking

9 posts
Thanks Meter: 0
 
By hmfic, Junior Member on 11th October 2010, 01:06 AM
Post Reply Subscribe to Thread Email Thread
14th October 2010, 02:17 AM |#21  
Senior Member
Thanks Meter: 430
 
More
logcat of radio from boot on
Attached you can find the logcats of radio from boot on.

The lc_radio.txt has been created with the PIN-input enabled, the other one with the PIN-input disabled.

Could somebody please do the same thing with a phone that still registers on a network? (of course it would be best with an unlocked phone, but also a normal T-Mobile registration would be interesting)

Thanks
Attached Files
File Type: txt lc_radio.txt - [Click for QR Code] (70.2 KB, 136 views)
File Type: txt lc_radio_nopin.txt - [Click for QR Code] (51.4 KB, 72 views)
 
 
14th October 2010, 07:59 AM |#22  
Member
Thanks Meter: 10
 
More
Mine too, now all the way from eBay to me and the unlock block network signal >.<

Already try flash original IMG but nothing change..
14th October 2010, 10:13 AM |#23  
jashsu's Avatar
Senior Member
Thanks Meter: 15
 
More
Quote:
Originally Posted by guhl99

Could somebody please do the same thing with a phone that still registers on a network? (of course it would be best with an unlocked phone, but also a normal T-Mobile registration would be interesting)


Here's a log of an unlocked G2 connecting to T-Mo US from init to a stable state. I edited out my personal data with tildes. An eleven tilde redaction indicates a phone number. Fifteen tilde redactions are IMEI. "310260~~~~~~~~~" are IMSI. Hope it helps.
Attached Files
File Type: txt lc_radio.txt - [Click for QR Code] (77.5 KB, 71 views)
14th October 2010, 12:44 PM |#24  
Senior Member
Flag Kalamata
Thanks Meter: 3
 
More
Quote:
Originally Posted by jashsu

Here's a log of an unlocked G2 connecting to T-Mo US from init to a stable state. I edited out my personal data with tildes. An eleven tilde redaction indicates a phone number. Fifteen tilde redactions are IMEI. "310260~~~~~~~~~" are IMSI. Hope it helps.

Does anybody know where the file holding info about cid and mcc mnc is located in android filesystem. Maybe this file corrupted after unlocking.
14th October 2010, 05:14 PM |#25  
Member
Thanks Meter: 10
 
More
Quote:
Originally Posted by gpou

Does anybody know where the file holding info about cid and mcc mnc is located in android filesystem. Maybe this file corrupted after unlocking.

I don't think is is about the corrupt file. Since after I unlock and lose cell connection I have find a complete ROM and flash it on top and nothing change. The phone still not function.

Right now I just hope that the solution is in some area we can touch or flash. Not deep down in some un-flashable or sign with some special key.
14th October 2010, 05:16 PM |#26  
jashsu's Avatar
Senior Member
Thanks Meter: 15
 
More
Quote:
Originally Posted by gpou

Does anybody know where the file holding info about cid and mcc mnc is located in android filesystem. Maybe this file corrupted after unlocking.

The CID information is probably held in the baseband's storage. MCC/MNC info is held in a variety of places, but the one you are missing is also likely in the baseband.

I'm wondering if it isn't a problem with your sim cards. Could you guys try using a T-mo US sim and checking logcat?
14th October 2010, 05:30 PM |#27  
Senior Member
Flag Kalamata
Thanks Meter: 3
 
More
Quote:
Originally Posted by jashsu

The CID information is probably held in the baseband's storage. MCC/MNC info is held in a variety of places, but the one you are missing is also likely in the baseband.

I'm wondering if it isn't a problem with your sim cards. Could you guys try using a T-mo US sim and checking logcat?

The logcat provided is with a T-mo sim.
Also after talking with the htc suport through their ticketing system they didnt help me at all. all they could do is offer me advices of how to hard reset my device.
Anyway the baseband files is in the filesystem??
Can we see or modify them through ADB?
14th October 2010, 05:53 PM |#28  
Senior Member
Flag Kalamata
Thanks Meter: 3
 
More
Quote:
Originally Posted by bluemoko

I don't think is is about the corrupt file. Since after I unlock and lose cell connection I have find a complete ROM and flash it on top and nothing change. The phone still not function.

Right now I just hope that the solution is in some area we can touch or flash. Not deep down in some un-flashable or sign with some special key.

Apparently the problem is a corrupted baseband file. I believe that tha firmware we have just hasn't that files
14th October 2010, 06:08 PM |#29  
jashsu's Avatar
Senior Member
Thanks Meter: 15
 
More
Quote:
Originally Posted by gpou

The logcat provided is with a T-mo sim.
Also after talking with the htc suport through their ticketing system they didnt help me at all. all they could do is offer me advices of how to hard reset my device.
Anyway the baseband files is in the filesystem??
Can we see or modify them through ADB?

It is not in the Linux filesystem at all. All the stuff pertaining to the radio (including the storage of settings like CID and subsidy lock) are controlled and stored by the baseband processor and baseband software (collectively known as the "radio").
14th October 2010, 06:09 PM |#30  
Senior Member
Flag Kalamata
Thanks Meter: 3
 
More
Quote:
Originally Posted by jashsu

It is not in the Linux filesystem at all. All the stuff pertaining to the radio (including the storage of settings like CID and subsidy lock) are controlled and stored by the baseband processor and baseband software (collectively known as the "radio").

So unless we get a new radio update its difficult to do something
14th October 2010, 07:31 PM |#31  
jashsu's Avatar
Senior Member
Thanks Meter: 15
 
More
Here is a comparison of where our two radio logs diverge (I'm referencing your no-sim log):

http://gist.github.com/626698

Short snippets:

My successful radio association
Code:
D/RILJ    ( 1549): [0004]< BASEBAND_VERSION 12.22.60.09bU_26.02.01.15_M2
D/HTC_RIL ( 1359): (t=1287044490)<< ~~~~~~~~~~~~~~~01\r\n0\r
D/HTC_RIL ( 1359): (t=1287044490)>> AT+CGSN\r
D/RILJ    ( 1549): [0005]< GET_IMEI 
D/HTC_RIL ( 1359): (t=1287044490)<< ~~~~~~~~~~~~~~~01\r\n0\r
D/HTC_RIL ( 1359): (t=1287044490)>> AT+CPMS="SM","SM","SM"\r
D/RILJ    ( 1549): [0006]< GET_IMEISV 
D/HTC_RIL ( 1359): (t=1287044490)<< +CPMS: 11,30,11,30,11,30\r\n0\r
D/RILJ    ( 1549): [0007]> OPERATOR
D/HTC_RIL ( 1359): (t=1287044490)>> AT+CPIN?\r
D/HTC_RIL ( 1359): (t=1287044490)<< +CPIN: READY\r\n0\r
D/HTC_RIL ( 1359): ril_func_get_imsi():called
D/HTC_RIL ( 1359): ril_func_chk_pb_state_until_ready():called
D/HTC_RIL ( 1359): (t=1287044490)>> AT+CIMI\r
D/HTC_RIL ( 1359): ril_func_get_curr_operator_name():called
D/HTC_RIL ( 1359): (t=1287044490)<< 310260~~~~~~~~~\r\n0\r
D/HTC_RIL ( 1359): ril_func_get_msisdn():called
D/HTC_RIL ( 1359): (t=1287044490)>> AT+CRSM=192,28480,0,0,0\r
D/RILJ    ( 1549): [0008]> GPRS_REGISTRATION_STATE
D/HTC_RIL ( 1359): ril_func_get_gprs_reg_state():called
D/RILJ    ( 1549): [0009]> REGISTRATION_STATE
D/HTC_RIL ( 1359): ril_func_get_gsm_cdma_reg_state():called
D/RILJ    ( 1549): [0010]> QUERY_NETWORK_SELECTION_MODE
D/HTC_RIL ( 1359): ril_func_get_network_select_mode():called
D/RILJ    ( 1549): [0011]> GET_CURRENT_CALLS
D/HTC_RIL ( 1359): ril_func_get_call_list():called
D/GSM     ( 1549): Baseband version: 12.22.60.09bU_26.02.01.15_M2
D/HTC_RIL ( 1359): (t=1287044490)<< +CRSM: 144,0,000000786F40040011F5550102011E\r\n0\r
D/HTC_RIL ( 1359): (t=1287044490)>> AT+CRSM=178,28480,1,4,30\r
D/HTC_RIL ( 1359): (t=1287044490)<< +CRSM: 144,0,4D736973646E31FFFFFFFFFFFFFFFFFF078~~~~~~~~~~~F7FFFFFFFFFFFF\r\n0\r
D/HTC_RIL ( 1359): (t=1287044490)>> AT+CPBS="SM"\r
D/HTC_RIL ( 1359): (t=1287044490)<< 0\r
D/HTC_RIL ( 1359): (t=1287044490)>> AT+CPBS?\r
D/HTC_RIL ( 1359): (t=1287044490)<< +CPBS: "SM",15,250\r\n0\r
E/HTC_RIL ( 1359): cust_table_create():failed to open customized operator name table
D/HTC_RIL ( 1359): ril_func_chk_eons():called
D/HTC_RIL ( 1359): ril_func_chk_cphs_ons():called
D/RILB    ( 1549): Notifying: SIM ready
D/RILJ    ( 1549): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED SIM_READY
D/RILJ    ( 1549): [0012]> OPERATOR
D/RILJ    ( 1549): [0013]> GPRS_REGISTRATION_STATE
Failed radio association
Code:
D/RILJ    ( 1535): [0004]< BASEBAND_VERSION 12.22.60.09bU_26.02.01.15_M2
D/HTC_RIL ( 1359): (t=1287010699)<< ~~~~~~~~~~~~~~~01\r\n0\r
D/HTC_RIL ( 1359): (t=1287010699)>> AT+CGSN\r
D/RILJ    ( 1535): [0005]< GET_IMEI 
D/HTC_RIL ( 1359): (t=1287010699)<< ~~~~~~~~~~~~~~~01\r\n0\r
D/HTC_RIL ( 1359): (t=1287010699)>> AT+CPMS="SM","SM","SM"\r
D/RILJ    ( 1535): [0006]< GET_IMEISV 
D/HTC_RIL ( 1359): (t=1287010699)<< +CMS ERROR: 500\r
D/HTC_RIL ( 1359): req_rsp_pair_retry_default():(0, 0x00000000) 1-th retries
D/HTC_RIL ( 1359): (t=1287010699)>> AT+CPIN?\r
D/HTC_RIL ( 1359): (t=1287010699)<< +CPIN: READY\r\n0\r
D/HTC_RIL ( 1359): ril_func_get_imsi():called
D/HTC_RIL ( 1359): ril_func_chk_pb_state_until_ready():called
D/HTC_RIL ( 1359): (t=1287010699)>> AT+CIMI\r
D/HTC_RIL ( 1359): (t=1287010699)<< +CME ERROR: 14\r
D/HTC_RIL ( 1359): req_rsp_pair_retry_default():(0, 0x00000000) 1-th retries
D/HTC_RIL ( 1359): (t=1287010699)>> AT+CPBS="SM"\r
D/HTC_RIL ( 1359): (t=1287010699)<< 0\r
D/HTC_RIL ( 1359): (t=1287010699)>> AT+CPBS?\r
D/HTC_RIL ( 1359): (t=1287010699)<< 0\r
D/HTC_RIL ( 1359): req_rsp_pair_retry_default():(0, 0x00000000) 1-th retries
D/STK     ( 1535): StkService: ril message arrived
D/STK     ( 1535): CommandParamsFactory: process SelectItem
D/RILJ    ( 1535): [0007]> OPERATOR
D/HTC_RIL ( 1359): ril_func_get_curr_operator_name():called
D/RILJ    ( 1535): [0007]< OPERATOR error: com.android.internal.telephony.CommandException: OP_NOT_ALLOWED_BEFORE_REG_NW
D/RILJ    ( 1535): [0008]> GPRS_REGISTRATION_STATE
D/HTC_RIL ( 1359): ril_func_get_gprs_reg_state():called
D/HTC_RIL ( 1359): (t=1287010699)>> AT+CGREG?\r
D/HTC_RIL ( 1359): (t=1287010699)<< +CGREG: 1,0\r\n0\r
D/RILJ    ( 1535): [0009]> REGISTRATION_STATE
D/RILJ    ( 1535): [0008]< GPRS_REGISTRATION_STATE {0, null, null, 0}
D/HTC_RIL ( 1359): ril_func_get_gsm_cdma_reg_state():called
D/HTC_RIL ( 1359): (t=1287010699)>> AT+CREG?\r
D/RILJ    ( 1535): [0010]> QUERY_NETWORK_SELECTION_MODE
D/HTC_RIL ( 1359): (t=1287010699)<< +CREG: 2,0\r\n0\r
D/HTC_RIL ( 1359): ril_func_get_network_select_mode():called
D/HTC_RIL ( 1359): (t=1287010699)>> AT+COPS=3,2;+COPS?\r
D/RILJ    ( 1535): [0009]< REGISTRATION_STATE {0, null, null, 0, null, null, null, null, null, null, null, null, null, null, null}
D/HTC_RIL ( 1359): (t=1287010699)<< +CME ERROR: 30\r
D/RILJ    ( 1535): [0011]> GET_CURRENT_CALLS
D/HTC_RIL ( 1359): get_nwsel_mode_rsp_handler():fail to get network select mode!
D/RILJ    ( 1535): [0010]< QUERY_NETWORK_SELECTION_MODE error: com.android.internal.telephony.CommandException: OP_NOT_ALLOWED_BEFORE_REG_NW
D/HTC_RIL ( 1359): ril_func_get_call_list():called
D/HTC_RIL ( 1359): (t=1287010699)>> AT+CLCC\r
D/HTC_RIL ( 1359): (t=1287010699)<< 0\r
D/RILJ    ( 1535): [0011]< GET_CURRENT_CALLS  
D/GSM     ( 1535): Baseband version: 12.22.60.09bU_26.02.01.15_M2
D/STK     ( 1535): StkService: SET_UP_MENU
D/STK     ( 1535): StkService: TERMINAL RESPONSE: 810301250082028281830100
D/RILJ    ( 1535): [0012]> REQUEST_STK_SEND_TERMINAL_RESPONSE
D/HTC_RIL ( 1359): ril_func_stk_send_terminal_response():called
D/HTC_RIL ( 1359): (t=1287010699)>> AT+GTKR=810301250082028281830100\r
D/HTC_RIL ( 1359): (t=1287010699)<< 0\r
D/RILJ    ( 1535): [0012]< REQUEST_STK_SEND_TERMINAL_RESPONSE 
E/GSM     ( 1535): Wrong network type: 0
E/GSM     ( 1535): Wrong network type: 0
D/GSM     ( 1535): Poll ServiceState done:  oldSS=[3 home null null null  Unknown CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false] newSS=[1 home null null null  Unknown CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false] oldGprs=1 newGprs=1 oldType=unknown newType=unknown
D/HTC_RIL ( 1359): (t=1287010699)%% +GTKI: \r\n
D/RILJ    ( 1535): [UNSL]< UNSOL_STK_SESSION_END
D/STK     ( 1535): StkService: ril message arrived
D/STK     ( 1535): StkService: SESSION END
D/HTC_RIL ( 1359): (t=1287010700)>> AT+CPMS="SM","SM","SM"\r
D/HTC_RIL ( 1359): (t=1287010700)<< +CMS ERROR: 500\r
D/HTC_RIL ( 1359): req_rsp_pair_retry_default():(0, 0x00000000) 2-th retries
D/HTC_RIL ( 1359): (t=1287010700)>> AT+CIMI\r
D/HTC_RIL ( 1359): (t=1287010700)<< +CME ERROR: 14\r
D/HTC_RIL ( 1359): req_rsp_pair_retry_default():(0, 0x00000000) 2-th retries
D/HTC_RIL ( 1359): (t=1287010700)>> AT+CPBS="SM"\r
D/HTC_RIL ( 1359): (t=1287010700)<< 0\r
D/HTC_RIL ( 1359): (t=1287010700)>> AT+CPBS?\r
D/HTC_RIL ( 1359): (t=1287010700)<< 0\r
D/HTC_RIL ( 1359): req_rsp_pair_retry_default():(0, 0x00000000) 2-th retries
D/HTC_RIL ( 1359): (t=1287010701)%% +CREG: 3\r\n
D/HTC_RIL ( 1359): (t=1287010701)%% +CGREG: 3\r\n
D/HTC_RIL ( 1359): (t=1287010701)>> AT+UPSC\r
D/RILJ    ( 1535): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
One thing I noticed is your log has a lot of STK (sim toolkit) entries, particularly unsolicited STK messages. Is this a brand new t-mo sim you are using? Was it ever activated on the t-mo network?
Last edited by jashsu; 14th October 2010 at 07:42 PM.

Read More
Post Reply Subscribe to Thread

Quick Reply
Message:
Options
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes