Project

General

Profile

Actions

Issue #1455

closed

SIM card blocked with i9300 (Galaxy S3)

Added by Anonymous over 8 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Telephony and mobile data
Target version:
Start date:
11/22/2015
Due date:
% Done:

0%

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

Description

Hi.

I did too many times wrong PIN codes. So my SIM is blocked.
I am asked to enter the PUK code. On a paper I had with the SIM card, I have a code that I assume to be he PUK, after entering I am asked to choose a new PIN code and confirm.
I tried 0000, 1111, an other one that use not only the same number, and even the PUK code it self, but after confirming the PIN code, Replicant still tells me that the PIN card is blocked. I rebooted, take off the battery, etc, but I have still the problem.
I am running Replicant 4.2.0004 on a i9300 (Samsung Galaxy S3) with an encrypted partition, with a Prixtel simcard (a French operator).

It may be linked to bug #1017 ("Support STK commands (Sim Toolkit)"). https://redmine.replicant.us/issues/1017
I suppose that is linked to RIL_REQUEST_ENTER_SIM_PUK, RIL_REQUEST_ENTER_SIM_PIN2, RIL_REQUEST_ENTER_SIM_PUK2, RIL_REQUEST_CHANGE_SIM_PIN, and/or RIL_REQUEST_CHANGE_SIM_PIN2 (that have not be tested according to the wiki). https://redmine.replicant.us/projects/replicant/wiki/Samsung-RIL

Regards.

Actions #1

Updated by Paul Kocialkowski over 8 years ago

Those should work, indeed, but I haven't tested them. Could you send a log (feel free to email it privately to me) so that I can take a look at what exactly is going on when entering the PUK? See GettingLogs.

Actions #2

Updated by Anonymous over 8 years ago

I found later that the code on the paper I had with the SIM card was not the PUK code (so I locked my SIM card)... So it may worked, but Replicant should have told me that it was the wrong PUK code, I suppose that it is possible, or at least tell me that it did not arrive to unlock the SIM card (I saw this behaviour on a Nexus 4 of my friend with stock ROM). I will be careful to find the real PUK code with my future SIM card and test. Could you change the status in something like maybe that still enables me to add a note to tell if it works when I will have a new SIM-card?

Actions #3

Updated by Anonymous over 8 years ago

Nicola Spanti wrote:

I found later that the code on the paper I had with the SIM card was not the PUK code (so I locked my SIM card)... So it may work, but Replicant should have told me that it was the wrong PUK code, I suppose that it is possible, or at least tell me that it did not arrive to unlock the SIM card (I saw this behaviour on a Nexus 4 of my friend with stock ROM). I will be careful to find the real PUK code with my future SIM card and test. Could you change the status in something like maybe that still enables me to add a note to tell if it works when I will have a new SIM-card?

Actions #4

Updated by Denis 'GNUtoo' Carikli over 8 years ago

  • Category changed from 117 to Telephony and mobile data
  • Device Galaxy S 3 (I9300) added
Actions #5

Updated by Denis 'GNUtoo' Carikli over 5 years ago

  • Category changed from Telephony and mobile data to SIM card not recognized
Actions #6

Updated by Denis 'GNUtoo' Carikli over 5 years ago

  • Category changed from SIM card not recognized to Telephony and mobile data
Actions #7

Updated by Kurtis Hanna over 4 years ago

  • Status changed from New to Closed
  • Resolution set to wontfix

This issue has been closed because Replicant 4.2 is no longer supported or maintained.

Actions

Also available in: Atom PDF