| Registered User
Join Date: Mar 2007 Location: Bandung, Indonesia
Posts: 384
Member: 461468
Status: Offline Thanks Meter: 139 | Sx4 problem - superdongle key valid
Dear MXKEY Team,
I have SX4 more times but not sucessfull, please see the logs:
Version from phone: 07.20
Version from file: 07.20
Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.11446, Date: 25-11-2009
Rpl backup already exist.
Processing file: rm174__07.20.mcusw as MCU
[BB5,BB5 ALGORITHM] size: 14.55 MB
Supported RAP Ids: 0103192101001101, 010C192101001101
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 1AF0000838946E56F6F2211F8AF66CDCFF6CC4D6
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 191EC665DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported RAP Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
FlashID0: 00EC 2208 - 0000 6921 [Samsung K8F5615ETM,256 Mbits] type: NOR,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 1.40.0 revision: 0.0 size: 0x22C10
Supported RAP 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
RAP PAPUBKEYS HASH: D6D07E588DC4E06DEE7012A3C0ECC4E35D3CE263
Storing certificate ...OK
Total erase size: 16.37 MB
CMT NOR area [00000000-000006BF] erased in 0.407 s
CMT NOR area [000006C0-0001FFFF] erased in 0.078 s
CMT NOR area [00020000-0007FFFF] erased in 1.172 s
CMT NOR area [00080000-000DFFFF] erased in 0.140 s
CMT NOR area [00100000-001FFFFF] erased in 0.266 s
CMT NOR area [00200000-0031FFFF] erased in 3.453 s
CMT NOR area [00320000-0105FFFF] erased in 39.906 s
CMT NOR area [01060000-01067FFF] erased in 0.422 s
CMT NOR area [01068000-0107FFFF] erased in 0.063 s
Flash programming ...
CMT PAPUBKEYS: D6D07E588DC4E06DEE7012A3C0ECC4E35D3CE263 (Rap Certificate 31 v1) written.
Programming completed in 7 min 41.779 s
Processing file: rm174__07.20.ppm_x as PPM
[BB5,BB5 ALGORITHM] size: 4.27 MB
Supported RAP Ids: 0103192101001101, 010C192101001101
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 1AF0000838946E56F6F2211F8AF66CDCFF6CC4D6
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 191EC665DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported RAP Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
FlashID0: 00EC 2208 - 0000 6921 [Samsung K8F5615ETM,256 Mbits] type: NOR,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 1.40.0 revision: 0.0 size: 0x22C10
Supported RAP 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
RAP PAPUBKEYS HASH: D6D07E588DC4E06DEE7012A3C0ECC4E35D3CE263
Total erase size: 4.50 MB
CMT NOR area [01080000-014FFFFF] erased in 13.297 s
Flash programming ...
Programming completed in 2 min 17.531 s
Processing file: rm174__07.20.image_x as CNT
[BB5,BB5 ALGORITHM] page size: 64 K size: 6.63 MB
Supported RAP Ids: 0103192101001101, 010C192101001101
NOR page size in the phone is 128 K.
Formating FS: FILE2 ...
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 1AF0000838946E56F6F2211F8AF66CDCFF6CC4D6
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 191EC665DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported RAP Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
FlashID0: 00EC 2208 - 0000 6921 [Samsung K8F5615ETM,256 Mbits] type: NOR,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 1.40.0 revision: 0.0 size: 0x22C10
Supported RAP 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
RAP PAPUBKEYS HASH: D6D07E588DC4E06DEE7012A3C0ECC4E35D3CE263
Total erase size: 10.87 MB
CMT NOR area [01500000-01FDFFFF] erased in 32.875 s
Converting UCP blocks to 128 K.
Flash programming ...
Programming completed in 3 min 32.826 s
Flashing completed in 15 min 36.807 s
After Flash Processing ...
Updating Product Code OK.
Phone Type: RM-174 (Nokia 5200)
SW Version: V 07.20 23-10-08 RM-174 (c) Nokia.
Imei plain: 35865901336246-3
Product Code: 0535511
Language Pack:
- not available.
SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST passed
Imei net: 358659013362463
Version: SIMLOCK SERVER VERSION 63
Provider: Nokia Test, Country: Finland
Counter: 0/3, 0/10
CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000
BLOCK 1: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 2: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 3: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 4: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 5: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 6: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 7: 1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
Total time to process is 15 min 50.541 s
Connecting to server ...OK
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID), hello 114.120.170.176
SUPERDONGLE get challenge failed !
Connecting to server ...OK
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID), hello 114.120.170.176
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Connecting to server ...OK
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID), hello 114.120.170.176
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Connecting to server ...OK
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID), hello 114.120.170.176
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Connecting to server ...OK
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID), hello 114.120.170.176
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Connecting to server ...OK
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID), hello 114.120.170.176
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Connecting to server ...OK
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID), hello 114.120.170.176
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Connecting to server ...OK
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID), hello 114.120.170.176
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Connecting to server ...OK
Connecting to server ...OK
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID), hello 114.120.170.176
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Connecting to server ...OK
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID), hello 114.120.170.176
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Connecting to server ...OK
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID), hello 114.120.170.176
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Connecting to server ...OK
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID), hello 114.120.170.176
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Connecting to server ...OK
Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(ID), hello 114.120.170.176
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
|