can't set PIN code on a MC7430

Kasper Holtze kasper at
Thu Dec 22 10:20:11 UTC 2016

Den 22-12-2016 kl. 10:47 skrev Bjørn Mork:
> Aleksander Morgado <aleksander at> writes:
>> On Wed, Dec 21, 2016 at 9:29 AM, Bjørn Mork <bjorn at> wrote:
>>> I don't now shit about these things, but I got the impression that you
>>> need "USIM" cards for anything non-2G.  And the MC74xx does not support
>>> 2G.
>>> Should at least be a simple theory to test with another card.
>> But Christophe is able to unlock the PIN via AT commands with the same
>> SIM card where QMI is failing, so now I wonder how to achieve the same
>> with QMI...
> Yes, I missed that at first. I have no idea what's going on then.  I
> cannot imagine what kind of extra magic the AT command interpreter has
> access to if it doesn't use the same QMI requests.
Just an idea - USIM/eUICC has more PIN options than a traditional SIM 
card. It has the option of multiple PIN codes, and the PIN code can be 
encrypted using a key. From the latest Gobi API (from Sierra):

  *  This structure contains the information about the pin parameters 
that need
  *  to be verified.
  *  \param  pinID
  *          - Indicates the PIN ID to be changed.
  *              - 1 - PIN1 (also called PIN)
  *              - 2 - PIN2
  *              - 3 - Universal PIN
  *              - 4 - Hidden key
  *  \param  oldPINLen
  *          - Length of the following elements i.e. old pin value.
  *          - Old PIN value.
  *          - This value is a sequence of ASCII characters.
  *  \param  pinLen
  *          - Length of the following elements i.e. new pin value.
  *  \param  pinVal[MAX_DESCRIPTION_LENGTH]
  *          - New PIN value.
  *          - This value is a sequence of ASCII characters.
typedef struct{
     BYTE pinID;
     BYTE oldPINLen;
     BYTE pinLen;
} changeUIMPIN;

So, the verify-pin-functions maybe needs to be updated in accordance 
with this?


More information about the libqmi-devel mailing list