高通SIMLOCK研究
2024-04-23 22:15:54
目录
1、设置策略
2、开启SIMLOCK功能
3、解除SIMLOCK功能
4、换一种策略
参考资料：
高通SIMLOCK的机制已经很成熟了，通过阅读参考资料可以对该功能有个基本的了解，但对于没做过的人可能还是不清楚如何使能该功能，以验证或研究相关功能。本文只是简单介绍如何开启SIMLOCK功能，及效果验证。
高通modem不需要修改任何代码，通过QXDM的DIAG command就可开启、验证SIMLOCK的相关功能。
1、设置策略
命令：UIMDIAG_SIMLOCK_SET_POLICY_CMD
只有该命令执行后才能真正开启SIMLOCK功能。
具体的DIAG命令：
send_data 0x80 0x21 0x60 0xea 0x00 0x00 0x13
SIMLOCK_SLOT_POLICY_SAME_ON_ALL_SLOTS
颜色标出的部分是所有卡槽使用相同的策略。
日志：
[0003] STRING 07:20:39.795000 Automation send_data 0x80 0x21 0x60 0xea 0x00 0x00 0x13
[0003] STRING 07:20:39.795000 Automation SendRawRequest 0x80 0x21 0x60 0xea 0x00 0x00 0x13
[0003] STRING 07:20:39.795000 Automation Subsys TX item
[0003] STRING 07:20:39.795000 Automation 0x80 21 60 ea 00 00 13
[0003] STRING 07:20:39.795000 Automation Subsys RX item
[0003] STRING 07:20:39.795000 Automation 0x80 21 60 ea 00 00 00 00 33 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ……
[ 21/ 2] MSG 07:21:31.119695 User Identity Module/High[ simlock_modem_lib.c 186] Queue of SIMLOCK command: SIMLOCK_SET_SIMLOCK_POLICY_MSG status 0x0
[ 21/ 1] MSG 07:21:31.276759 User Identity Module/Medium[ simlock.c 510] simlock_set_simlock_policy slot_policy: 0x0, sub_policy: 0x02、开启SIMLOCK功能
开启SIMLOCK功能的命令有多种，这里只执行一个。
命令：UIMDIAG_SIMLOCK_CK_LOCK_CMD
具体的DIAG命令：
send_data 0x80 0x21 0x62 0xea 0x01 0x00 0x00 0x00 0x0A 0x00 0x00 0x00 0xA0 0x86 0x01 0x00 0x08 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x01 0x34 0x36 0x30 0x02 0x30 0x31 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
这里只是把设备锁定在46001的网络上。
日志：
通过日志可以看出开启SIMLOCK功能后，卡1 52003的卡及卡2 20404的卡都被锁住了：
[0003] STRING 07:21:10.107000 Automation send_data 0x80 0x21 0x62 0xea 0x01 0x00 0x00 0x00 0x0A 0x00 0x00 0x00 0xA0 0x86 0x01 0x00 0x08 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x01 0x34 0x36 0x30 0x02 0x30 0x31 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[0003] STRING 07:21:10.107000 Automation SendRawRequest 0x80 0x21 0x62 0xea 0x01 0x00 0x00 0x00 0x0A 0x00 0x00 0x00 0xA0 0x86 0x01 0x00 0x08 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x01 0x34 0x36 0x30 0x02 0x30 0x31 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[0003] STRING 07:21:10.107000 Automation Subsys TX item
[0003] STRING 07:21:10.107000 Automation 0x80 21 62 ea 01 00 00 00 0a 00 00 00 a0 86 01 00 08 30 31 32 33 34 35 36 37 01 34 36 30 02 30 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[0003] STRING 07:21:10.123000 Automation Subsys RX item
[0003] STRING 07:21:10.123000 Automation 0x80 21 62 ea 00 00 00 00 34 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ……
[ 21/ 2] MSG 07:22:01.436260 User Identity Module/High[ simlock_modem_lib.c 505] Queue of SIMLOCK command: SIMLOCK_SET_LOCK_CK_MSG status 0x0
[ 21/ 1] MSG 07:22:01.436274 User Identity Module/Medium[ simlock.c 1078] simlock_set_lock_ck for category: 0x0
[ 21/ 1] MSG 07:22:01.461963 User Identity Module/Medium[ simlock_util.c 599] simlock_util_check_code_data
[ 21/ 1] MSG 07:22:01.461971 User Identity Module/Medium[simlock_category_conflicts.c 1287] simlock_category_verify_codes_for_conflicts
[ 21/ 1] MSG 07:22:01.461992 User Identity Module/Medium[ simlock_crypto.c 241] simlock_crypto_run_pbkdf2_algorithm, iteration_cnt: 0x186a0, password_data_len: 0x8, salt_data_len: 0x10, key_data_len: 0x20
[ 21/ 1] MSG 07:22:01.462011 User Identity Module/Medium[ simlock_crypto.c 290] pwd[0-3]:0x30, 0x31, 0x32, 0x33
[ 21/ 1] MSG 07:22:01.462016 User Identity Module/Medium[ simlock_crypto.c 292] pwd[4-7]:0x34, 0x35, 0x36, 0x37
[ 21/ 1] MSG 07:22:01.462021 User Identity Module/Medium[ simlock_crypto.c 302] dk_block_num: 0x1
[ 21/ 0] MSG 07:22:07.470645 User Identity Module/Low [ simlock_category.c 1885] From req - mcc[0]: 0x34, mcc[1]: 0x36, mcc[2]: 0x30, mnc[0]: 0x30, mnc[1]: 0x31, mnc[2]: 0x0
[ 21/ 1] MSG 07:22:07.470651 User Identity Module/Medium[ simlock_category.c 1254] simlock_category_write_lock_data
[ 21/ 1] MSG 07:22:07.485700 User Identity Module/Medium[ simlock_config.c 1924] simlock_config_update_and_write_category_status
[ 21/ 2] MSG 07:22:07.515132 User Identity Module/High[ mmgsdi_simlock.c 2031] processing SIM Lock event, evt_type: 0x4, status: 0x0
[ 21/ 2] MSG 07:22:07.515146 User Identity Module/High[ simlock_modem_lib.c 971] Queue of SIMLOCK command: SIMLOCK_GET_STATUS_MSG status 0x0
[ 21/ 2] MSG 07:22:07.737450 User Identity Module/High[ simlock_modem_lib.c 1153] Queue of SIMLOCK command: SIMLOCK_RUN_ALGORITHM_MSG status 0x0
[ 21/ 2] MSG 07:22:07.759763 User Identity Module/High[ simlock_3gpp.c 1979] category 0x0 enabled
[ 21/ 0] MSG 07:22:07.774337 User Identity Module/Low [ simlock_3gpp.c 1101] run_algo_nw: From sim - mcc[0],mcc[1],mcc[2]: 0x35,0x32,0x30; mnc[0],mnc[1],mnc[2]: 0x30,0x33,0x0
[ 21/ 1] MSG 07:22:07.774343 User Identity Module/Medium[ simlock_3gpp.c 1173] nw code in list type: 0x0
[ 21/ 2] MSG 07:22:07.774363 User Identity Module/High[ simlock_3gpp.c 1979] category 0x0 enabled
[ 21/ 0] MSG 07:22:07.789042 User Identity Module/Low [ simlock_3gpp.c 1101] run_algo_nw: From sim - mcc[0],mcc[1],mcc[2]: 0x32,0x30,0x34; mnc[0],mnc[1],mnc[2]: 0x30,0x34,0x0
[ 21/ 2] MSG 07:22:07.789214 User Identity Module/High[ mmgsdi.c 8618] Received event: 0x13 in mmgsdi_evt_cb
[ 21/ 2] MSG 07:22:07.789218 User Identity Module/High[ mmgsdi.c 8848] MMGSDI_PERSO_EVT, feature: 0x0, status: 0x2
[ 21/ 2] MSG 07:22:07.789241 User Identity Module/High[ mmgsdi.c 8618] Received event: 0x13 in mmgsdi_evt_cb
[ 21/ 2] MSG 07:22:07.789244 User Identity Module/High[ mmgsdi.c 8848] MMGSDI_PERSO_EVT, feature: 0x0, status: 0x2 at+cfun=0，at+cfun=1 抓日志：
[ 21/ 2] MSG 07:52:51.830716 User Identity Module/High[ mmgsdi.c 8656] MMGSDI_SESSION_CHANGED_EVT, app: 0x3, slot: 0x2, activated: 0x1, session_type: 0x2
[ 21/ 2] MSG 07:52:52.358633 User Identity Module/High[ mmgsdi.c 8656] MMGSDI_SESSION_CHANGED_EVT, app: 0x3, slot: 0x1, activated: 0x1, session_type: 0x0
[ 21/ 2] MSG 07:52:52.396315 User Identity Module/High[ mmgsdi.c 8806] MMGSDI_PIN1_EVT, status: 0x3, slot: 0x1
[ 21/ 2] MSG 07:52:52.498373 User Identity Module/High[ simlock_modem_lib.c 1153] Queue of SIMLOCK command: SIMLOCK_RUN_ALGORITHM_MSG status 0x0
[ 21/ 1] MSG 07:52:52.524675 User Identity Module/Medium[ simlock_3gpp.c 1868] simlock_3gpp_run_algorithm
[ 21/ 2] MSG 07:52:52.524701 User Identity Module/High[ simlock_3gpp.c 1979] category 0x0 enabled
[ 21/ 0] MSG 07:52:52.541836 User Identity Module/Low [ simlock_3gpp.c 1101] run_algo_nw: From sim - mcc[0],mcc[1],mcc[2]: 0x35,0x32,0x30; mnc[0],mnc[1],mnc[2]: 0x30,0x33,0x0
[ 21/ 1] MSG 07:52:52.541836 User Identity Module/Medium[ simlock_3gpp.c 1173] nw code in list type: 0x0
[ 21/ 1] MSG 07:52:52.541862 User Identity Module/Medium[ simlock_policy.c 756] simlock_apply_config_policy: slot_policy=0x0, sub_policy=0x0
[ 21/ 2] MSG 07:52:52.541888 User Identity Module/High[ mmgsdi_simlock.c 1621] mmgsdi_simlock_process_run_algo_resp
[ 21/ 2] MSG 07:52:52.542018 User Identity Module/High[ mmgsdi.c 8618] Received event: 0x13 in mmgsdi_evt_cb
[ 21/ 2] MSG 07:52:52.542018 User Identity Module/High[ mmgsdi.c 8848] MMGSDI_PERSO_EVT, feature: 0x0, status: 0x2
[ 21/ 2] MSG 07:52:53.988793 User Identity Module/High[ mmgsdi.c 8806] MMGSDI_PIN1_EVT, status: 0x2, slot: 0x2
[ 21/ 2] MSG 07:52:54.078246 User Identity Module/High[ simlock_modem_lib.c 1153] Queue of SIMLOCK command: SIMLOCK_RUN_ALGORITHM_MSG status 0x0
[ 21/ 1] MSG 07:52:54.103715 User Identity Module/Medium[ simlock_3gpp.c 1868] simlock_3gpp_run_algorithm
[ 21/ 2] MSG 07:52:54.103741 User Identity Module/High[ simlock_3gpp.c 1979] category 0x0 enabled
[ 21/ 0] MSG 07:52:54.120434 User Identity Module/Low [ simlock_3gpp.c 1101] run_algo_nw: From sim - mcc[0],mcc[1],mcc[2]: 0x35,0x32,0x30; mnc[0],mnc[1],mnc[2]: 0x30,0x33,0x0
[ 21/ 1] MSG 07:52:54.120434 User Identity Module/Medium[ simlock_3gpp.c 1173] nw code in list type: 0x0
[ 21/ 1] MSG 07:52:54.120460 User Identity Module/Medium[ simlock_3gpp.c 1868] simlock_3gpp_run_algorithm
[ 21/ 2] MSG 07:52:54.120460 User Identity Module/High[ simlock_3gpp.c 1979] category 0x0 enabled
[ 21/ 0] MSG 07:52:54.137413 User Identity Module/Low [ simlock_3gpp.c 1101] run_algo_nw: From sim - mcc[0],mcc[1],mcc[2]: 0x32,0x30,0x34; mnc[0],mnc[1],mnc[2]: 0x30,0x34,0x0
[ 21/ 1] MSG 07:52:54.137413 User Identity Module/Medium[ simlock_3gpp.c 1173] nw code in list type: 0x0
[ 21/ 1] MSG 07:52:54.137439 User Identity Module/Medium[ simlock_policy.c 756] simlock_apply_config_policy: slot_policy=0x0, sub_policy=0x0
[ 21/ 2] MSG 07:52:54.137465 User Identity Module/High[ mmgsdi_simlock.c 1621] mmgsdi_simlock_process_run_algo_resp
[ 21/ 2] MSG 07:52:54.137569 User Identity Module/High[ mmgsdi.c 8618] Received event: 0x13 in mmgsdi_evt_cb
[ 21/ 2] MSG 07:52:54.137595 User Identity Module/High[ mmgsdi.c 8848] MMGSDI_PERSO_EVT, feature: 0x0, status: 0x2
[ 21/ 2] MSG 07:52:54.137778 User Identity Module/High[ mmgsdi.c 8618] Received event: 0x13 in mmgsdi_evt_cb
[ 21/ 2] MSG 07:52:54.137778 User Identity Module/High[ mmgsdi.c 8848] MMGSDI_PERSO_EVT, feature: 0x0, status: 0x2卡1插入匹配的46001的卡：
通过日志可以看出卡146001的卡在白名单里，可以到ready；而卡2 20404的卡依然在锁定状态：
[ 21/ 2] MSG 08:07:36.761556 User Identity Module/High[ simlock_modem_lib.c 971] Queue of SIMLOCK command: SIMLOCK_GET_STATUS_MSG status 0x0
[ 21/ 2] MSG 08:07:38.362578 User Identity Module/High[ mmgsdi.c 8618] Received event: 0xd in mmgsdi_evt_cb
[ 21/ 2] MSG 08:07:38.362578 User Identity Module/High[ mmgsdi.c 8656] MMGSDI_SESSION_CHANGED_EVT, app: 0x3, slot: 0x1, activated: 0x1, session_type: 0x0
[ 21/ 2] MSG 08:07:40.189928 User Identity Module/High[ simlock_modem_lib.c 1153] Queue of SIMLOCK command: SIMLOCK_RUN_ALGORITHM_MSG status 0x0
[ 21/ 1] MSG 08:07:40.209694 User Identity Module/Medium[ simlock_3gpp.c 1868] simlock_3gpp_run_algorithm
[ 21/ 2] MSG 08:07:40.209720 User Identity Module/High[ simlock_3gpp.c 1979] category 0x0 enabled
[ 21/ 0] MSG 08:07:40.223105 User Identity Module/Low [ simlock_3gpp.c 1101] run_algo_nw: From sim - mcc[0],mcc[1],mcc[2]: 0x34,0x36,0x30; mnc[0],mnc[1],mnc[2]: 0x30,0x31,0x0
[ 21/ 1] MSG 08:07:40.223105 User Identity Module/Medium[ simlock_3gpp.c 1173] nw code in list type: 0x1
[ 21/ 1] MSG 08:07:40.223105 User Identity Module/Medium[ simlock_3gpp.c 1868] simlock_3gpp_run_algorithm
[ 21/ 2] MSG 08:07:40.223132 User Identity Module/High[ simlock_3gpp.c 1979] category 0x0 enabled
[ 21/ 0] MSG 08:07:40.236595 User Identity Module/Low [ simlock_3gpp.c 1101] run_algo_nw: From sim - mcc[0],mcc[1],mcc[2]: 0x32,0x30,0x34; mnc[0],mnc[1],mnc[2]: 0x30,0x34,0x0
[ 21/ 1] MSG 08:07:40.236595 User Identity Module/Medium[ simlock_3gpp.c 1173] nw code in list type: 0x0
[ 21/ 2] MSG 08:07:40.236621 User Identity Module/High[ mmgsdi_simlock.c 1621] mmgsdi_simlock_process_run_algo_resp
[ 21/ 2] MSG 08:07:40.236725 User Identity Module/High[ mmgsdi.c 8618] Received event: 0x13 in mmgsdi_evt_cb
[ 21/ 2] MSG 08:07:40.236725 User Identity Module/High[ mmgsdi.c 8848] MMGSDI_PERSO_EVT, feature: 0x7fffffff, status: 0x1
[ 21/ 2] MSG 08:07:40.236882 User Identity Module/High[ mmgsdi.c 8618] Received event: 0x13 in mmgsdi_evt_cb
[ 21/ 2] MSG 08:07:40.236882 User Identity Module/High[ mmgsdi.c 8848] MMGSDI_PERSO_EVT, feature: 0x0, status: 0x2
[ 21/ 2] MSG 08:07:41.656803 User Identity Module/High[ mmgsdi.c 8879] MMGSDI_SUBSCRIPTION_READY_EVT, app: 0x3, slot: 0x13、解除SIMLOCK功能
命令：UIMDIAG_SIMLOCK_UNLOCK_CMD
具体的DIAG命令：
send_data 0x80 0x21 0x63 0xea 0x01 0x00 0x08 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37
日志：
[0003] STRING 08:14:32.202000 Automation send_data 0x80 0x21 0x63 0xea 0x01 0x00 0x08 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37
[0003] STRING 08:14:32.204000 Automation SendRawRequest 0x80 0x21 0x63 0xea 0x01 0x00 0x08 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37
[0003] STRING 08:14:32.211000 Automation Subsys TX item
[0003] STRING 08:14:32.212000 Automation 0x80 21 63 ea 01 00 08 30 31 32 33 34 35 36 37
[0003] STRING 08:14:32.212000 Automation Subsys RX item
[0003] STRING 08:14:32.213000 Automation 0x80 21 63 ea 00 00 00 00 18 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00……
[ 21/ 2] MSG 08:16:00.020617 User Identity Module/High[ simlock_modem_lib.c 777] Queue of SIMLOCK command: SIMLOCK_SET_UNLOCK_MSG status 0x0
[ 21/ 1] MSG 08:16:00.145145 User Identity Module/Medium[ simlock.c 2276] simlock_unlock_device for category: 0x0
[ 21/ 1] MSG 08:16:00.175198 User Identity Module/Medium[ simlock.c 2138] num_codes: 0x1
[ 21/ 1] MSG 08:16:00.175201 User Identity Module/Medium[ simlock_crypto.c 241] simlock_crypto_run_pbkdf2_algorithm, iteration_cnt: 0x186a0, password_data_len: 0x8, salt_data_len: 0x10, key_data_len: 0x20
[ 21/ 1] MSG 08:16:00.175208 User Identity Module/Medium[ simlock_crypto.c 290] pwd[0-3]:0x30, 0x31, 0x32, 0x33
[ 21/ 1] MSG 08:16:00.175210 User Identity Module/Medium[ simlock_crypto.c 292] pwd[4-7]:0x34, 0x35, 0x36, 0x37
[ 21/ 1] MSG 08:16:00.175212 User Identity Module/Medium[ simlock_crypto.c 302] dk_block_num: 0x1
[ 21/ 1] MSG 08:16:04.538157 User Identity Module/Medium[ simlock.c 2182] key data matched
[ 21/ 1] MSG 08:16:04.538160 User Identity Module/Medium[ simlock_config.c 1924] simlock_config_update_and_write_category_status
[ 21/ 1] MSG 08:16:04.569446 User Identity Module/Medium[ simlock_category.c 1254] simlock_category_write_lock_data
[ 21/ 2] MSG 08:16:04.616197 User Identity Module/High[ mmgsdi_simlock.c 2031] processing SIM Lock event, evt_type: 0x0, status: 0x04、换一种策略
换策略要在关闭所以SIMLOCK功能后才可以。
UIMDIAG_SIMLOCK_SET_POLICY_CMD
send_data 0x80 0x21 0x60 0xea 0x01 0x00 0x13
SIMLOCK_SLOT_POLICY_UNIQUE_FOR_EACH_SLOT
每种卡槽使用不同的策略
UIMDIAG_SIMLOCK_CK_LOCK_CMD
send_data 0x80 0x21 0x62 0xea 0x01 0x00 0x00 0x00 0x0A 0x00 0x00 0x00 0xA0 0x86 0x01 0x00 0x08 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x01 0x34 0x36 0x30 0x02 0x30 0x31 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
把设备锁定在46001的网络上，这个命令只发了一次。
日志：
[0003] STRING 08:28:52.555000 Automation send_data 0x80 0x21 0x60 0xea 0x01 0x00 0x13
[0003] STRING 08:28:52.556000 Automation SendRawRequest 0x80 0x21 0x60 0xea 0x01 0x00 0x13
[0003] STRING 08:28:52.561000 Automation Subsys TX item
[0003] STRING 08:28:52.562000 Automation 0x80 21 60 ea 01 00 13
[0003] STRING 08:28:52.562000 Automation Subsys RX item
[0003] STRING 08:28:52.562000 Automation 0x80 21 60 ea 00 00 00 00 c8 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ……
[ 21/ 2] MSG 08:29:44.960548 User Identity Module/High[ simlock_modem_lib.c 186] Queue of SIMLOCK command: SIMLOCK_SET_SIMLOCK_POLICY_MSG status 0x0
[ 21/ 1] MSG 08:29:44.960562 User Identity Module/Medium[ simlock.c 510] simlock_set_simlock_policy slot_policy: 0x1, sub_policy: 0x0
[ 21/ 2] MSG 08:29:44.986393 User Identity Module/High[ simlock_config.c 1837] slot_policy: 0x1, sub_policy: 0x0
[0003] STRING 08:29:25.388000 Automation send_data 0x80 0x21 0x62 0xea 0x01 0x00 0x00 0x00 0x0A 0x00 0x00 0x00 0xA0 0x86 0x01 0x00 0x08 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x01 0x34 0x36 0x30 0x02 0x30 0x31 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[0003] STRING 08:29:25.388000 Automation SendRawRequest 0x80 0x21 0x62 0xea 0x01 0x00 0x00 0x00 0x0A 0x00 0x00 0x00 0xA0 0x86 0x01 0x00 0x08 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x01 0x34 0x36 0x30 0x02 0x30 0x31 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[0003] STRING 08:29:25.392000 Automation Subsys TX item
[0003] STRING 08:29:25.392000 Automation 0x80 21 62 ea 01 00 00 00 0a 00 00 00 a0 86 01 00 08 30 31 32 33 34 35 36 37 01 34 36 30 02 30 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[0003] STRING 08:29:25.393000 Automation Subsys RX item
[0003] STRING 08:29:25.393000 Automation 0x80 21 62 ea 00 00 00 00 c9 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ……
[ 21/ 2] MSG 08:30:17.792266 User Identity Module/High[ simlock_modem_lib.c 505] Queue of SIMLOCK command: SIMLOCK_SET_LOCK_CK_MSG status 0x0
[ 21/ 1] MSG 08:30:17.792266 User Identity Module/Medium[ simlock.c 1078] simlock_set_lock_ck for category: 0x0
[ 21/ 1] MSG 08:30:17.813985 User Identity Module/Medium[ simlock_util.c 599] simlock_util_check_code_data
[ 21/ 1] MSG 08:30:17.813985 User Identity Module/Medium[simlock_category_conflicts.c 1287] simlock_category_verify_codes_for_conflicts
[ 21/ 1] MSG 08:30:17.813985 User Identity Module/Medium[ simlock_crypto.c 241] simlock_crypto_run_pbkdf2_algorithm, iteration_cnt: 0x186a0, password_data_len: 0x8, salt_data_len: 0x10, key_data_len: 0x20
[ 21/ 1] MSG 08:30:17.814011 User Identity Module/Medium[ simlock_crypto.c 290] pwd[0-3]:0x30, 0x31, 0x32, 0x33
[ 21/ 1] MSG 08:30:17.814011 User Identity Module/Medium[ simlock_crypto.c 292] pwd[4-7]:0x34, 0x35, 0x36, 0x37
[ 21/ 1] MSG 08:30:17.814011 User Identity Module/Medium[ simlock_crypto.c 302] dk_block_num: 0x1
[ 21/ 1] MSG 08:30:22.507214 User Identity Module/Medium[ simlock_category.c 1254] simlock_category_write_lock_data
[ 21/ 1] MSG 08:30:22.530677 User Identity Module/Medium[ simlock_config.c 1924] simlock_config_update_and_write_category_status
[ 21/ 2] MSG 08:30:22.561406 User Identity Module/High[ mmgsdi_simlock.c 2031] processing SIM Lock event, evt_type: 0x4, status: 0x0 at+cfun=0，at+cfun=1 抓日志：
通过日志可以看出，卡1 52003的卡被锁定了；卡2是20404的卡没有被锁定，已经ready了。因为卡1卡2的策略不同，难道是只开启了一次SIMLOCK功能，默认就在卡1上生效？
[ 21/ 2] MSG 08:44:43.225490 User Identity Module/High[ mmgsdi.c 8656] MMGSDI_SESSION_CHANGED_EVT, app: 0x3, slot: 0x2, activated: 0x1, session_type: 0x2
[ 21/ 2] MSG 08:44:43.777001 User Identity Module/High[ mmgsdi.c 8656] MMGSDI_SESSION_CHANGED_EVT, app: 0x3, slot: 0x1, activated: 0x1, session_type: 0x0
[ 21/ 2] MSG 08:44:43.988120 User Identity Module/High[ simlock_modem_lib.c 1153] Queue of SIMLOCK command: SIMLOCK_RUN_ALGORITHM_MSG status 0x0
[ 21/ 1] MSG 08:44:44.008433 User Identity Module/Medium[ simlock_3gpp.c 1868] simlock_3gpp_run_algorithm
[ 21/ 2] MSG 08:44:44.008459 User Identity Module/High[ simlock_3gpp.c 1979] category 0x0 enabled
[ 21/ 0] MSG 08:44:44.021350 User Identity Module/Low [ simlock_3gpp.c 1101] run_algo_nw: From sim - mcc[0],mcc[1],mcc[2]: 0x35,0x32,0x30; mnc[0],mnc[1],mnc[2]: 0x30,0x33,0x0
[ 21/ 1] MSG 08:44:44.021376 User Identity Module/Medium[ simlock_3gpp.c 1173] nw code in list type: 0x0
[ 21/ 1] MSG 08:44:44.021376 User Identity Module/Medium[ simlock_policy.c 756] simlock_apply_config_policy: slot_policy=0x1, sub_policy=0x0
[ 21/ 2] MSG 08:44:44.021376 User Identity Module/High[ simlocklib.c 280] simlock process message, status: 0x0
[ 21/ 2] MSG 08:44:44.021402 User Identity Module/High[ mmgsdi_simlock.c 1621] mmgsdi_simlock_process_run_algo_resp
[ 21/ 2] MSG 08:44:44.021480 User Identity Module/High[ mmgsdi.c 8618] Received event: 0x13 in mmgsdi_evt_cb
[ 21/ 2] MSG 08:44:44.021480 User Identity Module/High[ mmgsdi.c 8848] MMGSDI_PERSO_EVT, feature: 0x0, status: 0x2
[ 21/ 2] MSG 08:44:45.517370 User Identity Module/High[ mmgsdi.c 8618] Received event: 0x13 in mmgsdi_evt_cb
[ 21/ 2] MSG 08:44:45.517370 User Identity Module/High[ mmgsdi.c 8848] MMGSDI_PERSO_EVT, feature: 0x7fffffff, status: 0x1
[ 21/ 2] MSG 08:44:45.665782 User Identity Module/High[ mmgsdi.c 8879] MMGSDI_SUBSCRIPTION_READY_EVT, app: 0x3, slot: 0x2
参考资料：
80-nm328-7_f_simlock_hck_based_engine_overview.pdf
80-VL005-1_UIM Diagnostic (UIM DIAG).pdf
高通SIMLOCK研究相关推荐
- 高通UEFI研究[三]
QTI针对UEFI规范使用TianocoreEDK2实现. 它是一种开放源代码实施,可从www.tianocore.org/edk2/获得. TianoCore EDK II提供了现代,适用于UEFI ...
- 英特尔、高通等多家科技巨头禁止员工与华为交流！
整理 | 伍杏玲 出品 | 程序人生(ID:coder_life) 刚在 6 月 2 日,IEEE 才发表声明恢复华为的评审权限:经美国商务部就出口管制条例在 IEEE 出版活动中的适用性做出的说明, ...
- 高通：人工智能不一定都靠“云” 终端也能拥有强大能力
在IT界,继移动互联网之后,人工智能浪潮也已经开始掀起.人们开始越来越关注人工智能技术即将给生活带来的改变.凭借这股浪潮,人工智能有望成为未来10年乃至更长时间内产业发展的焦点技术.国内外巨头们也都加 ...
- 高通人工智能前瞻性布局 发力终端人工智能
人工智能的最大愿景,是以无处不在的终端侧人工智能对云端人工智能实现补充.在我们预想中的世界里,人工智能将使终端.机器.汽车和万物都变得更加智能,简化并丰富我们的日常生活.具有极强创新研发能力的高通正在 ...
- 高通专利组合范围广 专利授权涉及多领域专利
众所周知,在高通在全球通信行业始终有着举足轻重的地位.拥有大量核心标准必要专利技术.并且,在整个移动通信行业发展的过程中,高通一直充当着关键技术研发和创新的引擎,而且通过专利授权让整个行业中的参与者都 ...
- Google、高通都在研究的芯片架构，是他们对抗ARM的武器
作者 | 张智伟 出品 | AI科技大本营(公众号ID:rgznai100) 据美国媒体 TheInfomation 报道,Google.高通.英伟达等 80 多家科技公司陆续开始研究一个名叫 RIS ...
- 高通CVPR神研究：视频处理计算量降低78%，教卷积层自己“挑像素”，卡成PPT的视频纵享丝滑...
萧箫 发自 凹非寺 量子位 报道 | 公众号 QbitAI 图像领域,已经限制不住AI算法大牛们的身手了. 现在,随着视频产业火热发展,相关算法也正成为计算机视觉研究的新潮流. 毕竟日常生活中,无论是 ...
- 高斯滤波器是低通还是高通_经典模拟滤波器仍值得研究吗？
对于大多数的电路和系统来说,使用电感器.电容器和电阻器的模拟滤波器至关重要.无论是被动还是主动设计,透过具有高难度数学的理论结构.实际的「应用说明」(application note)设计与物料清单( ...
- 高通发布《5G经济》研究:将催生12万亿美元市场
美国高通公司旗下子公司高通技术公司与多位产业界研究专家共同发表了一项名为<5G经济>(The5GEconomy)的研究.<5G经济>的研究成果基于对全球3500多个企业决策者. ...
最新文章
- [转载] CSS模块化【封装-继承-多态】
- 已调信号波形是怎样的_【鼎阳硬件智库原创 | 测试测量】初识任意波形发生器...
- Android自定义控件系列
- 《云计算》学习笔记3——Google的云计算原理与应用(分布式锁服务——Chubby)
- 应用层（知识架构图）
- java 声明静态类,为什么你不能在Java中将类声明为静态？
- query.exec报QSqlQuery::exec: database not open
- Robbin关于App class loader的总结(转帖)
- 深度学习专项课程精炼图笔记！必备收藏 | 原力计划
- 多线程学习-时间改变事件
- 如何在ubuntu上安装make 3.81
- 新兴IT企业特斯拉（八）——自动辅助驾驶
- 普通人的电脑离***远吗
- 贝尔曼方程基于全期望公式的前期推导
- python 方法加强@ pytho中@ python@
- 《算法图解》学习笔记（七）：狄克斯特拉算法（附代码）
- Unix环境高级编程-高级IO
- DCS概念简述——以教学用ABB HT 600控制系统/WinCS为例
- m4s格式转换mp3_M4A格式怎么转换成MP3
- jquery遍历节点的方法