7210C Updating SIMLOCK...error 0x14 (ANSWERED) - GSM-Forum

jitmobile · 03-17-2011, 17:27

I RECEIVE 7210C IN DEAD CONDITION WHEN I FLASH IT. SET HANG ON AND SHOW NOKIA WITHOUT BACKLIGHT.
I ERASE USING MXKEY USING FLASH---ADVANCE---GET ADDRESS AND UNTICK SAFE ERASE ERASE THE PHONE.
AND FLASH IT WITH 7.23 VERSION. I RESTORE IMEI. SAME PROBLEM.

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.9169(08-01-2011), 1.0.0.15868(10-03-2011)
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 1800020C31D58A5670749837C7FC26A5BF3798C3
ASIC MODE ID: 00
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000,

030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002,

001C192101001002
FlashID0: 0089 8982 - 0000 0000 [Intel NU48F512,512 Mbits] type: NOR,CMT
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000,

030C192101023000, 0303192101033000, 030C192101033000, 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200,

000C192101002200, 0003192101012200, 000C192101012200, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002,

001C192101001002
CMT PAPUBKEYS HASH: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026
TransmissionMode: DDR&TX2
Original Imei: 355------------------- SHOW OK IMEI
Original Product code: 0581686
Bluetooth ID: 002669E97BD1

Phone Type: RM-436 (Nokia 7210 Supernova)
SW Version: V 07.23 17-07-09 RM-436 (c) Nokia
Imei plain: 355------------------- SHOW OK IMEI
Language Pack:
- not available.

SIMLOCK invalid!
SUPERDONGLE_KEY invalid!
- WD timer enabled, phone will reboot itself after 3 min.

Failed to read SP data

I UPDATE SPLOCK . SAME PROBLEM. PLS HELP ME.

Failed to read SP data

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.9169(08-01-2011), 1.0.0.15868(10-03-2011)

Product: V 07.23 17-07-09 RM-436 (c) Nokia

Using cached productData[1800020C31D58A5670749837C7FC26A5BF3798C3] ...
Calculating SIMLOCK using security server ...
SERVER->Served by MXKEY - BLADE X at host3, agent version 1.1 revision 0.6

Completed in 2.390 s

RPL saved to "C:\mobileEx\3.4\data\backup\BB5_RM-436_355231037742162_SIM.RPL"
Updating SIMLOCK...error 0x14

Reading Simlock info ...
Failed to read SP data

amit kanpur · 03-17-2011, 20:11

backup rpl, just in case.
Erase eeprom by get addr. do not tick safe erase. do erase.
- proceed to simlock repair.
- proceed to sd repair.
- last, write rfbb by any auth.

alamgarh · 03-17-2011, 20:16

backup rpl , just in case .
Erase eeprom by get addr. do not tick safe erase . do erase .
- proceed to simlock repair .
- proceed to sd repair .
- last , write rfbb by any auth .

gbluez · 03-17-2011, 20:48

@jitmobile:
do as jagritisharma and alamgarh advice.

jitmobile · 03-18-2011, 15:48

THANKS FOR REPLY I DO ALL THINGS BUT PROBLEM IS SAME.

backup rpl, just in case.
Erase eeprom by get addr. do not tick safe erase. do erase.
- proceed to simlock repair.
- proceed to sd repair.
- last, write rfbb by any auth.

EEPROM ERASE LOG.

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.9169(08-01-2011), 1.0.0.15868(10-03-2011)
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 1800020C31D58A5670749837C7FC26A5BF3798C3
ASIC MODE ID: 00
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000,

010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000,

030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101,

010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002,

001C192101001002
FlashID0: 0089 8982 - 0000 0000 [Intel NU48F512,512 Mbits] type: NOR,CMT
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size:

0x297E0
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000,

010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000,

030C192101023000, 0303192101033000, 030C192101033000, 0003192101002000,

000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200,

000C192101002200, 0003192101012200, 000C192101012200, 0103192101001101,

010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002,

001C192101001002
CMT PAPUBKEYS HASH: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026
TransmissionMode: DDR&TX2
Erase size: 256.00 KB
CMT NOR area [03FC0000-03FFFFFF] erased in 1.547 s

REPAIR SIMLOCK LOG.

Failed to read SP data

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.9169(08-01-2011), 1.0.0.15868(10-03-2011)

Product: V 07.23 17-07-09 RM-436 (c) Nokia

Using cached productData[1800020C31D58A5670749837C7FC26A5BF3798C3] ...
Calculating SIMLOCK using security server ...
SERVER->Served by MXKEY - BLADE X at host3, agent version 1.1 revision 0.6

Completed in 10.234 s

RPL saved to "C:\mobileEx\3.4\data\backup\BB5_RM-436_355-------------------_SIM.RPL"
Updating SIMLOCK...error 0x14

Reading Simlock info ...
Failed to read SP data

SCAN LOG HERE.

Phone Type: RM-436 (Nokia 7210 Supernova)
SW Version: V 07.23 17-07-09 RM-436 (c) Nokia
Imei plain: 355------------------- SHOW OK IMEI
Language Pack:
- not available.

SIMLOCK invalid!
SUPERDONGLE_KEY[MX] seems to be valid

Failed to read SP data

PLS HELP ME.

net.tarik · 03-18-2011, 15:50

bro,
post self test log.

..::KASHIF::.. · 03-18-2011, 16:27

br rehot pcb bord & conct cabel sol 100%

thanks

br
..::KASHIF::..

net.tarik · 03-18-2011, 16:39

Quote:

Originally Posted by el-polaco

Only way is buy rpl and write.
This Phone is sl3 and simlock is damage (no backup/no solution)

b/r

polaco

This Phone is sl3

jitmobile · 03-18-2011, 16:44

i do all things ex. full erase untick safe erase. and erase with 64 mb erase file. flash with latest 7.23 version. after this i restore imei using SERVICE- IMEI & SECURITY - IMEI REBUILD - RESTORE IMEI.

I THINK THAT PROBLEM IS START WHEN I RESTORE IMEI. I ALSO HAVE ONLY RAP NPC AND APE NPC I FULL ERASE PHONE AND ONLY WRITE NPC DATA BUT PROBLEM IS SAME FINALLY I SAW THAT PROBLEM IS Failed to read SP data IN LAST LINE OF THIS LOG. I ALSO WRITE FULL MODIFIED PM AND DO REPAIR SD. REPAIR SIMLOCK, INIT SIMLOCK, WRITE RFBB BUT PROBLEM NOT SOLVED.

HERE IS LOG OF SERVICE- IMEI & SECURITY - IMEI REBUILD - RESTORE IMEI. (((( Updating SIMLOCK...error 0x14 ))))

RPL: "C:\mobileEx\3.4\data\backup\BB5_355-------------------_BACK.rpl"
Imei: 355------------------- SHOW OK IMEI
Restoring RF/BB DATA from backup ...
Updating RF ...OK
Updating BB ...OK
Updating PROD ...OK
Updating BT ...OK
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 1800020C31D58A5670749837C7FC26A5BF3798C3
ASIC MODE ID: 00
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
FlashID0: 0089 8982 - 0000 0000 [Intel NU48F512,512 Mbits] type: NOR,CMT
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
CMT PAPUBKEYS HASH: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026
TransmissionMode: DDR&TX2
Updating CMT NPC ...OK
Updating CMT CCC ...OK
Updating CMT HWC ...OK
Updating PRODUCTCODE (0566807)... OK
Updating PSN (DTC424093)... OK
Updating HWID (1000)... OK
Updating SIMLOCK...error 0x14
Updating SUPERDONGLE_KEY ...OK
Updating CMLA_KEY...OK
Updating WMDRM_PD...OK

Phone Type: RM-436 (Nokia 7210 Supernova)
SW Version: V 07.23 17-07-09 RM-436 (c) Nokia
Imei plain: 355------------------- SHOW OK IMEI
Product Code: 0566807
Language Pack:
- not available.

SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid

Failed to read SP data

jawad_anis · 03-18-2011, 16:46

Quote:

Originally Posted by jitmobile

I RECEIVE 7210C IN DEAD CONDITION WHEN I FLASH IT. SET HANG ON AND SHOW NOKIA WITHOUT BACKLIGHT.
I ERASE USING MXKEY USING FLASH---ADVANCE---GET ADDRESS AND UNTICK SAFE ERASE ERASE THE PHONE.
AND FLASH IT WITH 7.23 VERSION. I RESTORE IMEI. SAME PROBLEM.

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.9169(08-01-2011), 1.0.0.15868(10-03-2011)
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 1800020C31D58A5670749837C7FC26A5BF3798C3
ASIC MODE ID: 00
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000,

030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002,

001C192101001002
FlashID0: 0089 8982 - 0000 0000 [Intel NU48F512,512 Mbits] type: NOR,CMT
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000,

030C192101023000, 0303192101033000, 030C192101033000, 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200,

000C192101002200, 0003192101012200, 000C192101012200, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002,

001C192101001002
CMT PAPUBKEYS HASH: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026
TransmissionMode: DDR&TX2
Original Imei: 355------------------- SHOW OK IMEI
Original Product code: 0581686
Bluetooth ID: 002669E97BD1

Phone Type: RM-436 (Nokia 7210 Supernova)
SW Version: V 07.23 17-07-09 RM-436 (c) Nokia
Imei plain: 355------------------- SHOW OK IMEI
Language Pack:
- not available.

SIMLOCK invalid!
SUPERDONGLE_KEY invalid!
- WD timer enabled, phone will reboot itself after 3 min.

Failed to read SP data

I UPDATE SPLOCK . SAME PROBLEM. PLS HELP ME.

Failed to read SP data

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.9169(08-01-2011), 1.0.0.15868(10-03-2011)

Product: V 07.23 17-07-09 RM-436 (c) Nokia

Using cached productData[1800020C31D58A5670749837C7FC26A5BF3798C3] ...
Calculating SIMLOCK using security server ...
SERVER->Served by MXKEY - BLADE X at host3, agent version 1.1 revision 0.6

Completed in 2.390 s

RPL saved to "C:\mobileEx\3.4\data\backup\BB5_RM-436_355231037742162_SIM.RPL"
Updating SIMLOCK...error 0x14

Reading Simlock info ...
Failed to read SP data

http://forum.gsmhosting.com/vbb/f550...5/#post5383535

jitmobile · 03-18-2011, 17:00

I READ THE THREAD BUT HERE PROBLEM IS Failed to read SP data NOT SIMLOCK DATA CORRUPTED.

IF ANYONE HAVE SOLUTION PLS POST HERE.

net.tarik · 03-18-2011, 17:24

why not you post self test log?

jitmobile · 03-19-2011, 09:30

here is selftest log picture link

2shared - download selftest2.jpg

pls see this and give a solution using HWK And MXKEY.

gbluez · 03-20-2011, 02:33

once again, do this way
if end up with self test failed, perform recover certificate.

@el-polaco:
this is an SL2 phones with 9DDB hash, it's kind of old security.
mxkey can handled this long time ago, free of charge.

BR

2net@jay · 03-20-2011, 04:52

make repair simlock with create simlock rpl checked..

then write ccc.hwc without npc rpl..

auth sd and write pm.. rfbb from server checked also..

03-17-2011, 17:27	#1 (permalink)
jitmobile Junior Member Join Date: Feb 2005 Age: 48 Posts: 36 Member: 113442 Status: Offline Thanks Meter: 9	7210C Updating SIMLOCK...error 0x14 (ANSWERED) I RECEIVE 7210C IN DEAD CONDITION WHEN I FLASH IT. SET HANG ON AND SHOW NOKIA WITHOUT BACKLIGHT. I ERASE USING MXKEY USING FLASH---ADVANCE---GET ADDRESS AND UNTICK SAFE ERASE ERASE THE PHONE. AND FLASH IT WITH 7.23 VERSION. I RESTORE IMEI. SAME PROBLEM. Using device: UFS_USB V2.8 (c) SarasSoft 2007. Library version: 1.0.0.9169(08-01-2011), 1.0.0.15868(10-03-2011) CMT Data : SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x] EM0 ID: 00000296 EM1 ID: 00000B22 PUBLIC ID: 1800020C31D58A5670749837C7FC26A5BF3798C3 ASIC MODE ID: 00 ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723 ROM ID: 273F6D55DFAAF68F SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00 Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002 FlashID0: 0089 8982 - 0000 0000 [Intel NU48F512,512 Mbits] type: NOR,CMT ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 TransmissionMode: 16Bit Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0 Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002 CMT PAPUBKEYS HASH: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026 TransmissionMode: DDR&TX2 Original Imei: 355------------------- SHOW OK IMEI Original Product code: 0581686 Bluetooth ID: 002669E97BD1 Phone Type: RM-436 (Nokia 7210 Supernova) SW Version: V 07.23 17-07-09 RM-436 (c) Nokia Imei plain: 355------------------- SHOW OK IMEI Language Pack: - not available. SIMLOCK invalid! SUPERDONGLE_KEY invalid! - WD timer enabled, phone will reboot itself after 3 min. Failed to read SP data I UPDATE SPLOCK . SAME PROBLEM. PLS HELP ME. Failed to read SP data Using device: UFS_USB V2.8 (c) SarasSoft 2007. Library version: 1.0.0.9169(08-01-2011), 1.0.0.15868(10-03-2011) Product: V 07.23 17-07-09 RM-436 (c) Nokia Using cached productData[1800020C31D58A5670749837C7FC26A5BF3798C3] ... Calculating SIMLOCK using security server ... SERVER->Served by MXKEY - BLADE X at host3, agent version 1.1 revision 0.6 Completed in 2.390 s RPL saved to "C:\mobileEx\3.4\data\backup\BB5_RM-436_355231037742162_SIM.RPL" Updating SIMLOCK...error 0x14 Reading Simlock info ... Failed to read SP data

03-18-2011, 15:48	#5 (permalink)
jitmobile Junior Member Join Date: Feb 2005 Age: 48 Posts: 36 Member: 113442 Status: Offline Thanks Meter: 9	Thnx but problem not solved THANKS FOR REPLY I DO ALL THINGS BUT PROBLEM IS SAME. backup rpl, just in case. Erase eeprom by get addr. do not tick safe erase. do erase. - proceed to simlock repair. - proceed to sd repair. - last, write rfbb by any auth. EEPROM ERASE LOG. Using device: UFS_USB V2.8 (c) SarasSoft 2007. Library version: 1.0.0.9169(08-01-2011), 1.0.0.15868(10-03-2011) CMT Data : SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x] EM0 ID: 00000296 EM1 ID: 00000B22 PUBLIC ID: 1800020C31D58A5670749837C7FC26A5BF3798C3 ASIC MODE ID: 00 ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723 ROM ID: 273F6D55DFAAF68F SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00 Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002 FlashID0: 0089 8982 - 0000 0000 [Intel NU48F512,512 Mbits] type: NOR,CMT ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 TransmissionMode: 16Bit Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0 Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002 CMT PAPUBKEYS HASH: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026 TransmissionMode: DDR&TX2 Erase size: 256.00 KB CMT NOR area [03FC0000-03FFFFFF] erased in 1.547 s REPAIR SIMLOCK LOG. Failed to read SP data Using device: UFS_USB V2.8 (c) SarasSoft 2007. Library version: 1.0.0.9169(08-01-2011), 1.0.0.15868(10-03-2011) Product: V 07.23 17-07-09 RM-436 (c) Nokia Using cached productData[1800020C31D58A5670749837C7FC26A5BF3798C3] ... Calculating SIMLOCK using security server ... SERVER->Served by MXKEY - BLADE X at host3, agent version 1.1 revision 0.6 Completed in 10.234 s RPL saved to "C:\mobileEx\3.4\data\backup\BB5_RM-436_355-------------------_SIM.RPL" Updating SIMLOCK...error 0x14 Reading Simlock info ... Failed to read SP data SCAN LOG HERE. Phone Type: RM-436 (Nokia 7210 Supernova) SW Version: V 07.23 17-07-09 RM-436 (c) Nokia Imei plain: 355------------------- SHOW OK IMEI Language Pack: - not available. SIMLOCK invalid! SUPERDONGLE_KEY[MX] seems to be valid Failed to read SP data PLS HELP ME.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
where to find a working program all they have some errors ??	fondas	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	2	12-12-2012 13:26
SimLock Level 4 counter	HitMan	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	0	11-12-1999 00:17
The multiple errors of Winlock ... ???	Genata	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	0	09-20-1999 19:12
error (1002) simlock3.dll winopen	fondas	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	0	08-28-1999 15:57

03-17-2011, 20:11	#2 (permalink)
amit kanpur No Life Poster Join Date: May 2009 Location: kanpur Age: 35 Posts: 2,443 Member: 1033905 Status: Offline Sonork: amitsharma Thanks Meter: 892	backup rpl, just in case. Erase eeprom by get addr. do not tick safe erase. do erase. - proceed to simlock repair. - proceed to sd repair. - last, write rfbb by any auth.

03-17-2011, 20:16	#3 (permalink)
alamgarh No Life Poster Join Date: Sep 2006 Location: Allah is Greatest Posts: 4,822 Member: 358694 Status: Offline Sonork: 100.1597323 Thanks Meter: 994	backup rpl , just in case . Erase eeprom by get addr. do not tick safe erase . do erase . - proceed to simlock repair . - proceed to sd repair . - last , write rfbb by any auth .

03-17-2011, 20:48	#4 (permalink)
gbluez No Life Poster Join Date: Jul 2004 Posts: 11,049 Member: 73565 Status: Offline Thanks Meter: 5,062	@jitmobile: do as jagritisharma and alamgarh advice.

03-18-2011, 15:50	#6 (permalink)
net.tarik No Life Poster Join Date: Jun 2010 Location: Green Forest Posts: 1,125 Member: 1316000 Status: Offline Sonork: 100.1624093 Thanks Meter: 348	bro, post self test log.

03-18-2011, 16:27	#7 (permalink)
..::KASHIF::.. No Life Poster Join Date: Apr 2010 Location: United Arab Emirates ( DUBAI ) Posts: 2,018 Member: 1294044 Status: Offline Thanks Meter: 1,269	br rehot pcb bord & conct cabel sol 100% thanks br ..::KASHIF::..

03-18-2011, 16:44	#9 (permalink)
jitmobile Junior Member Join Date: Feb 2005 Age: 48 Posts: 36 Member: 113442 Status: Offline Thanks Meter: 9	i do all things ex. full erase untick safe erase. and erase with 64 mb erase file. flash with latest 7.23 version. after this i restore imei using SERVICE- IMEI & SECURITY - IMEI REBUILD - RESTORE IMEI. I THINK THAT PROBLEM IS START WHEN I RESTORE IMEI. I ALSO HAVE ONLY RAP NPC AND APE NPC I FULL ERASE PHONE AND ONLY WRITE NPC DATA BUT PROBLEM IS SAME FINALLY I SAW THAT PROBLEM IS Failed to read SP data IN LAST LINE OF THIS LOG. I ALSO WRITE FULL MODIFIED PM AND DO REPAIR SD. REPAIR SIMLOCK, INIT SIMLOCK, WRITE RFBB BUT PROBLEM NOT SOLVED. HERE IS LOG OF SERVICE- IMEI & SECURITY - IMEI REBUILD - RESTORE IMEI. (((( Updating SIMLOCK...error 0x14 )))) RPL: "C:\mobileEx\3.4\data\backup\BB5_355-------------------_BACK.rpl" Imei: 355------------------- SHOW OK IMEI Restoring RF/BB DATA from backup ... Updating RF ...OK Updating BB ...OK Updating PROD ...OK Updating BT ...OK CMT Data : SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x] EM0 ID: 00000296 EM1 ID: 00000B22 PUBLIC ID: 1800020C31D58A5670749837C7FC26A5BF3798C3 ASIC MODE ID: 00 ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723 ROM ID: 273F6D55DFAAF68F SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00 Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002 FlashID0: 0089 8982 - 0000 0000 [Intel NU48F512,512 Mbits] type: NOR,CMT ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 TransmissionMode: 16Bit Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0 Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002 CMT PAPUBKEYS HASH: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026 TransmissionMode: DDR&TX2 Updating CMT NPC ...OK Updating CMT CCC ...OK Updating CMT HWC ...OK Updating PRODUCTCODE (0566807)... OK Updating PSN (DTC424093)... OK Updating HWID (1000)... OK Updating SIMLOCK...error 0x14 Updating SUPERDONGLE_KEY ...OK Updating CMLA_KEY...OK Updating WMDRM_PD...OK Phone Type: RM-436 (Nokia 7210 Supernova) SW Version: V 07.23 17-07-09 RM-436 (c) Nokia Imei plain: 355------------------- SHOW OK IMEI Product Code: 0566807 Language Pack: - not available. SIMLOCK invalid! SUPERDONGLE_KEY seems to be valid Failed to read SP data

03-18-2011, 17:00	#11 (permalink)
jitmobile Junior Member Join Date: Feb 2005 Age: 48 Posts: 36 Member: 113442 Status: Offline Thanks Meter: 9	I READ THE THREAD BUT HERE PROBLEM IS Failed to read SP data NOT SIMLOCK DATA CORRUPTED. IF ANYONE HAVE SOLUTION PLS POST HERE.

03-18-2011, 17:24	#12 (permalink)
net.tarik No Life Poster Join Date: Jun 2010 Location: Green Forest Posts: 1,125 Member: 1316000 Status: Offline Sonork: 100.1624093 Thanks Meter: 348	why not you post self test log?

03-19-2011, 09:30	#13 (permalink)
jitmobile Junior Member Join Date: Feb 2005 Age: 48 Posts: 36 Member: 113442 Status: Offline Thanks Meter: 9	here is selftest log picture link 2shared - download selftest2.jpg pls see this and give a solution using HWK And MXKEY.

03-20-2011, 02:33	#14 (permalink)
gbluez No Life Poster Join Date: Jul 2004 Posts: 11,049 Member: 73565 Status: Offline Thanks Meter: 5,062	once again, do this way if end up with self test failed, perform recover certificate. @el-polaco: this is an SL2 phones with 9DDB hash, it's kind of old security. mxkey can handled this long time ago, free of charge. BR

03-20-2011, 04:52	#15 (permalink)
2net@jay Freak Poster Join Date: Jun 2006 Location: Marikina City Posts: 162 Member: 293270 Status: Offline Thanks Meter: 43	make repair simlock with create simlock rpl checked.. then write ccc.hwc without npc rpl.. auth sd and write pm.. rfbb from server checked also..