+CPIN: PH-NET PIN HILONC V2

:laughing: Hello,

I have 2 modules that started to respond to the AT+CPIN? command, +CPIN: PH-NET PIN.

From what I researched this means that the modules have become locked to a mobile network.

I’m almost sure that this happened with no user intervention!

AT+CPIN?

+CPIN: SIM PIN

OK
AT+CPIN="9352"

OK

AT+CPIN?

+CPIN: PH-NET PIN

OK

I tryed to upload the firmware, but not successful! Here is the log:

04/04/2016 17:03:54'925 HUAP HiloUpgrader starting... [RELEASE]
04/04/2016 17:03:54'925 HUAP HiloUpgrader version    : 5.0.4.0
04/04/2016 17:03:54'925 HUAP MobileHILO2 DLL version : 3.3.2.0
04/04/2016 17:03:54'979 HSET Serial Port count : 1
04/04/2016 17:03:54'979 HSET Serial Port list : COM1
04/04/2016 17:03:55'005 HSET UpdateMainMMI - Usable = 0x00 UnBusy = 0xFF
04/04/2016 17:03:55'050 HUAP Loader file OK : flash_nor_16bits_hwasic_evp_4901_2_rel_sc_0_6.hex
04/04/2016 17:03:55'053 HUAP Software    OK : \\zen\dev\software\HI2N_A_005_08_0020_p7035D.pac
04/04/2016 17:04:01'980 HSET UpdateMainMMI - Usable = 0x01 UnBusy = 0xFF
04/04/2016 17:04:11'736 HUAP Upgrade by user
04/04/2016 17:04:11'736 HUAP Loader file  : flash_nor_16bits_hwasic_evp_4901_2_rel_sc_0_6.hex
04/04/2016 17:04:11'736 HSET Main file : \\zen\dev\software\HI2N_A_005_08_0020_p7035D.pac
04/04/2016 17:04:11'739 PACF PAC file size : 3243706 bytes
04/04/2016 17:04:12'167 PACF CLA file size : 3183088 [0x003091F0] bytes (Data size : 3243704 bytes)
04/04/2016 17:04:12'175 PACF PARAM file size : 60608 [0x0000ECC0] bytes (Data size : 60612 bytes)
04/04/2016 17:04:12'178 PACF Checking software : 3183088 bytes
04/04/2016 17:04:12'186 PACF Get software version from CLA file  : SAGEMCOM Hi2N,A.005.08 [Offset : 0x003091F0]
04/04/2016 17:04:12'215 PACF Compute MD5 fingerprint of CLA file : 20EE71CD6CCD901B1C393E1B6EFA23B8
04/04/2016 17:04:12'216 HSET Software       : HI2N_A_005_08_0020_P7035D_HU.CLA
04/04/2016 17:04:12'216 HSET Parameter file : HI2N_A_005_08_0020_P7035D_HU.PARAM
04/04/2016 17:04:12'216 HSET DetectModule   : Enable
04/04/2016 17:04:12'230 MOD1 Step: Initialisation
04/04/2016 17:04:12'230 MOD1 Step: Detect module
04/04/2016 17:04:12'230 ATC1 Detect Module at COM1
04/04/2016 17:04:12'230 ATC1 Checking COM1 @ 115200 bauds
04/04/2016 17:04:12'430 ATC1 W (1) 00
04/04/2016 17:04:12'441 ATC1 W (3) 41 54 0D
04/04/2016 17:04:12'622 ATC1 R (9) 41 54 0D 0D 0A 4F 4B 0D 0A
04/04/2016 17:04:12'622 ATC1 W (8) 41 54 2B 43 47 4D 52 0D
04/04/2016 17:04:13'004 ATC1 R (40) 41 54 2B 43 47 4D 52 0D 0D 0A 53 41 47 45 4D 43 4F 4D 20 48 69 32 4E 2C 41 2E 30 30 35 2E 30 33 0D 0A 0D 0A 4F 4B 0D 0A
04/04/2016 17:04:13'005 MOD1 Found Speed    : 115200 bauds
04/04/2016 17:04:13'005 MOD1 Software version : SAGEMCOM Hi2N,A.005.03
04/04/2016 17:04:13'005 MOD1 Step: Generate SAV file
04/04/2016 17:04:13'006 DLL1 CFG : 04.00.00 - 13/01/2011 (Hilo V1/V2 management)
04/04/2016 17:04:13'107 DLL1 OpenSession COM1 @ AT:115200 bauds TAT:115200 bauds ...
04/04/2016 17:04:16'337 DLL1 TAT Session is opening (5) ...
04/04/2016 17:04:28'367 DLL1 Platform : [DEFAULT_PLATFORM] - Specific : [HiloV2_DV1.24]
04/04/2016 17:04:28'367 DLL1 HILO V2 MODULE READY FOR TAT REQUEST
04/04/2016 17:04:28'367 TAT1 STE software version : 3700001300020124
04/04/2016 17:04:28'367 DLL1 CTATRequest::ReadSerialNumber
04/04/2016 17:04:28'371 TAT1 HILO Serial Number : 1341316437
04/04/2016 17:04:28'381 DLL1 ReadSectionInfo ID:18 Size:0x0028 - Address:0xA802E474
04/04/2016 17:04:28'482 DLL1 CTATRequest::ReadMemory
04/04/2016 17:04:28'492 TAT1 Checking HILO module : 355278056345989
04/04/2016 17:04:28'502 DLL1 ReadSectionInfo ID:37 Size:0x0408 - Address:0xA802D8B0
04/04/2016 17:04:28'512 DLL1 ReadSectionInfo ID:37 Size:0x0408 - Address:0xA802D8B0
04/04/2016 17:04:28'613 DLL1 CTATRequest::ReadMemory
04/04/2016 17:04:28'708 TAT1 Checking HILO module : Invalid software key
04/04/2016 17:04:28'711 DLL1 TAT:CloseSession
04/04/2016 17:04:28'712 DLL1 CloseSession
04/04/2016 17:04:28'813 SAV1 Searching for a valid SAV file ...
04/04/2016 17:04:28'814 SAV1 Searching for a valid [SA_] file ...
04/04/2016 17:04:28'814 MOD1 Step: Generate SAV file: No SAV file and default Software Key
04/04/2016 17:04:28'814 DLL1 CloseSession
04/04/2016 17:04:28'814 HUM1 UserMessage [181] : Software key of the module is an Invalid Software Key!
04/04/2016 17:04:28'816 PACF Deleting temporary files...
04/04/2016 17:04:28'817 PACF   Delete file : HI2N_A_005_08_0020_P7035D_HU.PARAM
04/04/2016 17:04:28'830 PACF   Delete file : HI2N_A_005_08_0020_P7035D_HU.CLA
04/04/2016 17:04:42'076 HUAP HiloUpgrader closing
04/04/2016 17:04:42'077 HUAP ********************
04/04/2016 17:04:42'086 HLOG MD5 Fingerprint : 15EAF1B2D23C745EC737D57E0B292338

Is there anything that can be done to recover the modules?

What could have happened to make the modules behave like this?

Thanks.

Hi,
When some issue happens during the firmware upgrade, then PH-NET PIN may happen.
During the upgrade, for some reason (For example, sudden power off), the module failed to restore parameters from the .SAV file. So some important settings are missing, for example IMEI, Security key and RF settings. So module will be forbidden to register to network.
So please try to find back the .SAV file for this module. The file name of the .SAV should include the same Serial number as the module.

-Alex

The GSM module is integrated in a product, and only I can do upgrades. So I’m 99% sure that there was not any upgrade attempt, by the end user. That being said, I don’t have any SAV file to restore (is it possible to create this file, using the IMEI and serial number on the label?).

However, the end user used a SIM card with wrong PIN, but the SIM card itself was not locked.

This issue has happened in two devices, and whatever went wrong, went wrong twice.

Can the mobile network issue ant kind of command to put the module in the PH-NET PIN condition?

Thanks.

hi,
You can find the file in C:\Program Files\HiloUpgrader\SAV. The file name of the .SAV should include the same Serial number as the module. You can do force download of the firmware if you have .SAV file of the corresponding module.

Also check if these sims are working in any other devices such as mobile phone. So that we can conclude issue with SIM card or with the HiLo module.

-Alex

Hi,

As I posted,I don’t have any .SAV file, as there was not any firmware upgrade.

Without the .SAV file is there any way to fix this?

The SIM works in other devices.

Thanks.

Hi,
In this case, i will suggest you to contact Sierra technical support team. You can seek help from your reseller/distributor for this.

-Alex

xgon,
Did you fix your module without the .SAV file?
Does Sierra support team give any tool to restore IMEI or Serial Numer?