Project

General

Profile

Issue #1840

My SIM is locked and still doesn't work after unlocking it on lineageos

Added by ariel enter almost 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
Telephony and mobile data
Target version:
Start date:
10/15/2017
Due date:
% Done:

0%

Estimated time:
Resolution:
Device:
Galaxy S 2 (I9100)
Grant:

Description

I was trying to use a TL-WN722N with RepWifi in my galaxy s2 when it rebooted by it self.

After rebooting the following message appeared:

"SIM network unlock PIN"

I tried to unlock it but it kept saying "SIM network unlock unsuccessful". I read in here [[https://redmine.replicant.us/boards/9/topics/7467]] that replicant some times has trouble unlocking SIMs, so I follow the suggestion of trying on LineageOS and it worked. I got the "SIM network unlock successful".

Unfortunately, even after unlocking the SIM, the notification area showed that I didn't have service yet, and every time that I reboot the cell phone I had to unlock the SIM again.

I'm sending my "adb logcat -b radio" logs, both from LineageOS and Replicant encrypted.

I'm also publishing some of the files content where the word "error" is percent and that, "I pretty sure", won't give away sensitive info and it may help others.

E use-Rlog/RLOG-RIL: error: Failed to clear address for rmnet0: Cannot assign requested address
E use-Rlog/RLOG-RIL: BTADDR_PATH_NEW open error(w).
E use-Rlog/RLOG-RIL: checkDbgFlag error. (from DBG_FLAG_MNT_FILENAME)
E use-Rlog/RLOG-RIL: fail to change radio directory permission, error : Operation not permitted
E TelephonyComponentFactory: Error loading TelephonyComponentFactory
D RilRequest: [3648]< GET_HARDWARE_CONFIG error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret=
D RilRequest: [3650]< RIL_REQUEST_CDMA_SET_SUBSCRIPTION_SOURCE error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret=
D RilRequest: [3651]< RIL_REQUEST_SET_CELL_INFO_LIST_RATE error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret=
D RilRequest: [3652]< SCREEN_STATE error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret=
D RilRequest: [3653]< RIL_REQUEST_START_LCE error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret=
W CarrierConfigManager: Error getting config for subId -1 ICarrierConfigLoader is null
D RilRequest: [3654]< SIGNAL_STRENGTH error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret=
D RilRequest: [3655]< SET_SUPP_SVC_NOTIFICATION error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret=
D RilRequest: [3656]< RIL_REQUEST_SET_TTY_MODE error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret=
D RilRequest: [3661]< RIL_REQUEST_START_LCE error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret=
D RilRequest: [3671]< RIL_REQUEST_IMS_REGISTRATION_STATE error: com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED ret=
D UiccCard: Error in SIM access with exceptioncom.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED
D RilRequest: [3682]< RIL_REQUEST_REPORT_STK_SERVICE_IS_RUNNING error: com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED ret=
D UiccPkcs15: error: com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED
D RilRequest: [3688]< RIL_REQUEST_ALLOW_DATA error: com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED ret=
D RilRequest: [3710]< ENTER_NETWORK_DEPERSONALIZATION error: com.android.internal.telephony.CommandException: PASSWORD_INCORRECT ret=
E use-Rlog/RLOG-RIL: error: Failed to clear address for rmnet0: Cannot assign requested address
E use-Rlog/RLOG-RIL: error: Failed to clear address for rmnet1: Cannot assign requested address
E use-Rlog/RLOG-RIL: error: Failed to clear address for rmnet2: Cannot assign requested address
W CarrierConfigManager: Error getting config for subId -1 ICarrierConfigLoader is null
E PhoneBase: Error! registerForCallWaiting() in PhoneBase should not be called, CDMAPhone inactive.
E PhoneBase: Error! unregisterForCallWaiting() in PhoneBase should not be called, CDMAPhone inactive.
D RilRequest: [3700]< OPERATOR error: com.android.internal.telephony.CommandException: GENERIC_FAILURE ret=
E GsmSST  : [GsmSST] RIL implementation has returned an error where it must succeedcom.android.internal.telephony.CommandException: GENERIC_FAILURE
D RilRequest: [3712]< OEM_HOOK_RAW error: com.android.internal.telephony.CommandException: GENERIC_FAILURE ret=

Thank you.


Files

lineageos.log.gpg (41.1 KB) lineageos.log.gpg ariel enter, 10/15/2017 12:58 AM
replicant.log.gpg (30.2 KB) replicant.log.gpg ariel enter, 10/15/2017 12:58 AM

Related issues

Related to Replicant - Feature #2098: Support SIM network unlockNew07/30/2020

Actions
Related to Replicant - Feature #2101: Document/implement the Replicant way of SIM unlockNew07/30/2020

Actions
#1

Updated by ariel enter almost 3 years ago

I should have said "when suddenly my cell phone rebooted by it self". I mean, it wasn't a regular reboot, it just shut down immediately like if the power had been disconnected. I have read that battery drain can cause some troubles with losing some important files or permissions changes. I fear these reboots are something similar. I haven't done any back up of my EFS, although I see that I can still get mi IMEI. I got a little worry.

I encrypted the files with the KEY_IDs of all active developers as suggested here [[https://redmine.replicant.us/projects/replicant/wiki/GettingLogs]]

Also, the sudden reboots when using TL-WN722N and RepWifi happened to me some other times in the past, but I thought it was normal since, RepWifi seemed to have troubles detecting the device until I manually shut my cell phone down and turn it back on, although, some times this didn't work either and some times I lose the wifi signal all along which made me believe that it may had something to do with my otg cable quality. I regret my decision of trying again after that. Hopefully is nothing horrible and something can be done D:

#2

Updated by Wolfgang Wiedmeyer almost 3 years ago

Your network operator cannot be identified. The modem sends 33403 as operator code, but this code doesn't exist. 334030 does exist (see Wikipedia). It's for Movistar in Mexico.

I only did a quick look and there may be more issues.

#3

Updated by ariel enter almost 3 years ago

Wolfgang Wiedmeyer wrote:

Your network operator cannot be identified. The modem sends 33403 as operator code, but this code doesn't exist. 334030 does exist (see Wikipedia). It's for Movistar in Mexico.

I only did a quick look and there may be more issues.

Thanks very much Wolfgang. This cellphone was originally lock to use Movistar only. When I bought it, it was unlocked by the seller. Could it be that is locked again for Movistar only? I'll try to get a hold on a Movistar SIM and try it out and let you know if it works.

The SIM I'm trying to use is for Telcel. I remember the word Telcel is present in both logs but I don't know what it means. But I'm guessing that since the modem is not requesting the right code, probably because it became locked again, that's the reason it can not use that operator instead, even though is the right Telcel SIM.

#4

Updated by ariel enter almost 3 years ago

YES! the SIM from Movistar did work. Now I need to find a way to unlock it again xD

If some one could tell me of a way to do so using free software I'll be very thankful. There is a lot of places here in my city that do the job, but I would rather do it my self if I could, since I'm not sure if I can trust them considering that they most probably use proprietary software or whether they could inject malware through the process.

First thing I'll make a backup of my EFS.

Thank you very much Wolfgang Wiedmeyer. I surely will donate to the project and hope to keep doing it in the future. Thank you.

#5

Updated by ariel enter almost 3 years ago

It appears that I can not close the Issue. I wanted to close it because I feel that the original problem is already solved, and unlock the phone is a different case. I'll post in the forum instead for that, since I think is a general issue. I'll search also for instructions where they could be using free software. Once again Thanks for every thing.

#6

Updated by Fil Bergamo almost 3 years ago

  • Status changed from New to Closed

ariel enter wrote:

It appears that I can not close the Issue. I wanted to close it because I feel that the original problem is already solved, and unlock the phone is a different case. I'll post in the forum instead for that, since I think is a general issue. I'll search also for instructions where they could be using free software. Once again Thanks for every thing.

Closed the Issue.

#7

Updated by dl lud about 2 months ago

#8

Updated by dl lud about 2 months ago

  • Related to Feature #2101: Document/implement the Replicant way of SIM unlock added

Also available in: Atom PDF