Manole plz help me - GSM-Forum

SinghForHelp · 01-23-2010, 14:49

RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 0A70020AAA087D56CC55CEF748408C29BC534FBE
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 RAP 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,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
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: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026
Reading RAP NPC (0x168 bytes)

Begin Certificate Request ...
Connecting to server ...OK, Login ...
ERROR: No certificate found in the database !

Umair Rashid · 01-23-2010, 14:57

You might be trying to repair Superdongle key which is not possible with this button "Recover CERT"
Post your logs and problem for instant Help.

BR,
Umair

SinghForHelp · 01-23-2010, 15:03

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.11826, Date: 22-01-2010
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 0A70020AAA087D56CC55CEF748408C29BC534FBE
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 RAP 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,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
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: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026
Original Imei: 35196203214405
Original Product code: 0572571
Bluetooth ID: 00247DC18F52

Phone Type: RM-436 (Nokia 7210 Supernova)
SW Version: V 07.23 17-07-09 RM-436 (c) Nokia
Imei plain: 35196203214405-3
Product Code: 0514950
Language Pack:
- not available.

This phone have PM308 protected, SD security in not restorable.
- Avoid SW Downgrade & manual erase to this phone !

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!

Imei net: 351962032144053
Version: SIMLOCK SERVER
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

THIS IS MY PROBLAM

SinghForHelp · 01-23-2010, 15:05

WHEN I TRY TO auth pm THEN IT SAYS

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 115.187.16.2
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

t.technic · 01-23-2010, 16:50

may be your phone ever repaired with other tools,SDK become not detected by mx?? Ur procedure is right, but your lucky is not your hand. try with other tool bro,,

Umair Rashid · 01-23-2010, 16:54

. Do as follows .

Andra · 01-23-2010, 19:46

can u do SX-4 by mxkey server here ?
if phone already simlock / superdongle fix by another tool
u can't use that "button" at moment.
but coder already have some ways to make that work on future.

another ways u can use this tricks

Just in case if Recovery via Server doesn't work.......

br,

SinghForHelp · 01-24-2010, 16:26

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

This phone have PM308 protected, SD security in not restorable.
- Avoid SW Downgrade & manual erase to this phone !

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!

Imei net: 351962032144053
Version: SIMLOCK SERVER
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
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 0A70020AAA087D56CC55CEF748408C29BC534FBE
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 RAP 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,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
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: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026
Reading RAP NPC (0x168 bytes)
Original Product Code: 0572571
Reading RAP VARIANT (0x0 bytes)
Reading RAP CCC (0x160 bytes)
Product Code: 0581686
Product Code missmatch !
Reading RAP HWC (0xD4 bytes)
Product Code: 0566932
Product Code missmatch !

SinghForHelp · 01-24-2010, 16:28

what to do now. not solved sir

Umair Rashid · 01-24-2010, 16:30

Quote:

Originally Posted by musabhaiji

what to do now. not solved sir

Did you try what i recommended ?

SinghForHelp · 01-24-2010, 16:50

RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 0A70020AAA087D56CC55CEF748408C29BC534FBE
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 RAP 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,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
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: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026
Reading RAP NPC (0x168 bytes)
Original Product Code: 0572571
Reading RAP VARIANT (0x0 bytes)
Reading RAP CCC (0x160 bytes)
Product Code: 0581686
Product Code missmatch !
Reading RAP HWC (0xD4 bytes)
Product Code: 0566932
Product Code missmatch !

SinghForHelp · 01-24-2010, 16:54

yes i try. but sx4 is not done so how can pm will write.

see here logs.

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 115.187.16.2
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Writing PM from Node ...
Section: 1
Warning: failed to write 1 - 0 (12 bytes)
Warning: failed to write 1 - 2 (70 bytes)
Warning: failed to write 1 - 3 (70 bytes)
Warning: failed to write 1 - 4 (70 bytes)
Warning: failed to write 1 - 6 (276 bytes)
Warning: failed to write 1 - 7 (276 bytes)
Warning: failed to write 1 - 8 (276 bytes)
Warning: failed to write 1 - 10 (384 bytes)
Warning: failed to write 1 - 11 (384 bytes)
Warning: failed to write 1 - 12 (384 bytes)
Warning: failed to write 1 - 14 (384 bytes)
Warning: failed to write 1 - 15 (384 bytes)
Warning: failed to write 1 - 16 (384 bytes)
Warning: failed to write 1 - 17 (32 bytes)
Warning: failed to write 1 - 19 (16 bytes)
Section: 2
- Key: 0, size 440 bytes written.
Section: 4
- Key: 1, size 800 bytes written.
- Key: 3, size 10 bytes written.
- Key: 4, size 8 bytes written.
- Key: 5, size 8 bytes written.
- Key: 6, size 8 bytes written.
- Key: 9, size 5 bytes written.
- Key: 18, size 80 bytes written.
- Key: 19, size 4 bytes written.
- Key: 28, size 2 bytes written.
Section: 8
- Key: 0, size 2 bytes written.
- Key: 1, size 16 bytes written.
- Key: 2, size 16 bytes written.
- Key: 3, size 128 bytes written.
- Key: 4, size 128 bytes written.
- Key: 8, size 8 bytes written.
Section: 11
- Key: 0, size 4 bytes written.
- Key: 1, size 4 bytes written.
- Key: 2, size 4 bytes written.
- Key: 3, size 4 bytes written.
- Key: 5, size 6 bytes written.
- Key: 6, size 2 bytes written.
- Key: 14, size 2 bytes written.
- Key: 15, size 2 bytes written.
- Key: 16, size 2 bytes written.
- Key: 17, size 2 bytes written.
- Key: 18, size 16 bytes written.
- Key: 19, size 32 bytes written.
- Key: 20, size 32 bytes written.
- Key: 21, size 2 bytes written.
- Key: 22, size 2 bytes written.
- Key: 23, size 2 bytes written.
- Key: 24, size 2 bytes written.
- Key: 25, size 2 bytes written.
- Key: 26, size 2 bytes written.
- Key: 27, size 2 bytes written.
- Key: 28, size 2 bytes written.
- Key: 29, size 2 bytes written.
- Key: 30, size 2 bytes written.
- Key: 31, size 2 bytes written.
- Key: 32, size 2 bytes written.
- Key: 33, size 2 bytes written.
- Key: 34, size 2 bytes written.
- Key: 35, size 2 bytes written.
- Key: 36, size 2 bytes written.
- Key: 37, size 2 bytes written.
- Key: 38, size 2 bytes written.
- Key: 39, size 2 bytes written.
- Key: 40, size 2 bytes written.
- Key: 41, size 2 bytes written.
- Key: 42, size 2 bytes written.
- Key: 43, size 2 bytes written.
- Key: 44, size 2 bytes written.
- Key: 45, size 2 bytes written.
- Key: 46, size 2 bytes written.
- Key: 47, size 2 bytes written.
- Key: 48, size 2 bytes written.
- Key: 49, size 2 bytes written.
- Key: 50, size 2 bytes written.
- Key: 51, size 2 bytes written.
- Key: 52, size 2 bytes written.
- Key: 53, size 2 bytes written.
- Key: 54, size 2 bytes written.
- Key: 55, size 2 bytes written.
- Key: 56, size 2 bytes written.
- Key: 57, size 2 bytes written.
- Key: 58, size 2 bytes written.
- Key: 59, size 2 bytes written.
- Key: 60, size 2 bytes written.
- Key: 61, size 2 bytes written.
- Key: 62, size 2 bytes written.
- Key: 63, size 2 bytes written.
- Key: 64, size 2 bytes written.
- Key: 65, size 2 bytes written.
- Key: 66, size 4 bytes written.
- Key: 68, size 4 bytes written.
- Key: 69, size 4 bytes written.
- Key: 70, size 4 bytes written.
- Key: 71, size 4 bytes written.
- Key: 72, size 16 bytes written.
- Key: 73, size 4 bytes written.
- Key: 74, size 2 bytes written.
- Key: 75, size 13 bytes written.
Section: 31
- Key: 4, size 14 bytes written.
Section: 42
- Key: 0, size 2 bytes written.
- Key: 1, size 12 bytes written.
- Key: 2, size 36 bytes written.
- Key: 3, size 36 bytes written.
- Key: 4, size 36 bytes written.
- Key: 5, size 36 bytes written.
- Key: 6, size 36 bytes written.
- Key: 7, size 40 bytes written.
- Key: 8, size 40 bytes written.
- Key: 9, size 40 bytes written.
- Key: 10, size 40 bytes written.
- Key: 11, size 40 bytes written.
- Key: 12, size 40 bytes written.
- Key: 13, size 40 bytes written.
- Key: 14, size 40 bytes written.
Section: 50
- Key: 0, size 2 bytes written.
Section: 54
- Key: 0, size 2 bytes written.
Section: 66
- Key: 0, size 415 bytes written.
- Key: 1, size 240 bytes written.
- Key: 2, size 240 bytes written.
- Key: 5, size 240 bytes written.
- Key: 6, size 4 bytes written.
- Key: 7, size 4 bytes written.
- Key: 8, size 4 bytes written.
- Key: 9, size 4 bytes written.
- Key: 10, size 240 bytes written.
- Key: 11, size 240 bytes written.
- Key: 16, size 4 bytes written.
- Key: 18, size 4 bytes written.
- Key: 20, size 4 bytes written.
- Key: 22, size 4 bytes written.
- Key: 24, size 4 bytes written.
- Key: 26, size 4 bytes written.
- Key: 28, size 4 bytes written.
- Key: 30, size 4 bytes written.
Warning: failed to write 66 - 32 (4 bytes)
Warning: failed to write 66 - 54 (8 bytes)
Warning: failed to write 66 - 55 (8 bytes)
Warning: failed to write 66 - 56 (8 bytes)
Warning: failed to write 66 - 57 (8 bytes)
Warning: failed to write 66 - 71 (8 bytes)
Warning: failed to write 66 - 72 (8 bytes)
Warning: failed to write 66 - 74 (6144 bytes)
Warning: failed to write 66 - 75 (300 bytes)
Warning: failed to write 66 - 76 (60 bytes)
Warning: failed to write 66 - 85 (3 bytes)
Warning: failed to write 66 - 86 (3 bytes)
Warning: failed to write 66 - 87 (3 bytes)
Warning: failed to write 66 - 89 (4 bytes)
Warning: failed to write 66 - 90 (4 bytes)
- Key: 91, size 4 bytes written.
- Key: 92, size 4 bytes written.
Warning: failed to write 66 - 93 (4 bytes)
Warning: failed to write 66 - 94 (6 bytes)
Warning: failed to write 66 - 96 (4 bytes)
Warning: failed to write 66 - 103 (120 bytes)
Warning: failed to write 66 - 105 (30 bytes)
Warning: failed to write 66 - 107 (8 bytes)
Warning: failed to write 66 - 110 (7 bytes)
Section: 88
Warning: failed to write 88 - 0 (36 bytes)
Section: 96
Warning: failed to write 96 - 0 (2 bytes)
Warning: failed to write 96 - 1 (20 bytes)
Section: 107
Warning: failed to write 107 - 0 (21 bytes)
Warning: failed to write 107 - 1 (89 bytes)
Warning: failed to write 107 - 2 (69 bytes)
Warning: failed to write 107 - 3 (70 bytes)
Warning: failed to write 107 - 26 (12 bytes)
Section: 193
Warning: failed to write 193 - 2 (8 bytes)
Warning: failed to write 193 - 3 (32 bytes)
Warning: failed to write 193 - 4 (32 bytes)
Warning: failed to write 193 - 9 (64 bytes)
Section: 218
Warning: failed to write 218 - 0 (2 bytes)
Section: 238
Section: 309
Warning: failed to write 309 - 0 (4 bytes)
Warning: failed to write 309 - 1 (2 bytes)
Warning: failed to write 309 - 2 (12 bytes)
Warning: failed to write 309 - 4 (12 bytes)
Warning: failed to write 309 - 5 (12 bytes)
Warning: failed to write 309 - 7 (12 bytes)
Warning: failed to write 309 - 8 (12 bytes)
Warning: failed to write 309 - 17 (12 bytes)
Warning: failed to write 309 - 22 (12 bytes)
Section: 322
Section: 334
Section: 339
- Key: 0, size 511 bytes written.
- Key: 1, size 511 bytes written.
Section: 341
- Key: 3, size 4 bytes written.
- Key: 4, size 4414 bytes written.
Section: 354
- Key: 0, size 3 bytes written.
Section: 355
- Key: 1, size 2028 bytes written.
Section: 356
- Key: 0, size 2 bytes written.
Section: 362
- Key: 1, size 120 bytes written.
Completed in 23.093 s

emad2007 · 01-24-2010, 17:33

MX-KEY is the BEST NOKIA TOOL

SinghForHelp · 01-24-2010, 17:35

please solv my problam

kharisma · 01-24-2010, 17:40

Just in case if Recovery via Server doesn't work.......

01-23-2010, 14:49	#1 (permalink)
SinghForHelp Freak Poster Join Date: Feb 2007 Location: In Your Heart Posts: 496 Member: 451538 Status: Offline Thanks Meter: 98	Manole plz help me RAP Data : SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x] EM0 ID: 00000295 EM1 ID: 00000B22 PUBLIC ID: 0A70020AAA087D56CC55CEF748408C29BC534FBE 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 RAP 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,RAP ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 ExtDEVC: FFFF 0000 - 0000 0000 Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0 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: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026 Reading RAP NPC (0x168 bytes) Begin Certificate Request ... Connecting to server ...OK, Login ... ERROR: No certificate found in the database !

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
plz help me	lloydgsm	FuriousGold	3	03-29-2010 20:08
plz help me	lloydgsm	SETool2	6	03-29-2010 13:10
manole plz help me	rana_jee	MXKEY Nokia Flasher and Unlocker (by Alim Hape)	0	03-14-2010 09:58
mr MANOLE .plz help me ( Security test Faild )	city-gsm	MXKEY Nokia Flasher and Unlocker (by Alim Hape)	6	02-07-2010 12:53
to MANOLE plz help me as fast as you can	ufs-4	BB5 RPL	6	03-21-2008 16:11

01-23-2010, 14:57	#2 (permalink)
Umair Rashid No Life Poster Join Date: Dec 2006 Location: Rawalpindi, Pakistan Posts: 2,292 Member: 421117 Status: Offline Sonork: +92 346 5544377 (PHONE) Thanks Meter: 2,522	You might be trying to repair Superdongle key which is not possible with this button "Recover CERT" Post your logs and problem for instant Help. BR, Umair

01-23-2010, 15:03	#3 (permalink)
SinghForHelp Freak Poster Join Date: Feb 2007 Location: In Your Heart Posts: 496 Member: 451538 Status: Offline Thanks Meter: 98	Using device: UFS_USB V2.8 (c) SarasSoft 2007. Library version: 1.0.0.11826, Date: 22-01-2010 RAP Data : SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x] EM0 ID: 00000295 EM1 ID: 00000B22 PUBLIC ID: 0A70020AAA087D56CC55CEF748408C29BC534FBE 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 RAP 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,RAP ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 ExtDEVC: FFFF 0000 - 0000 0000 Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0 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: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026 Original Imei: 35196203214405 Original Product code: 0572571 Bluetooth ID: 00247DC18F52 Phone Type: RM-436 (Nokia 7210 Supernova) SW Version: V 07.23 17-07-09 RM-436 (c) Nokia Imei plain: 35196203214405-3 Product Code: 0514950 Language Pack: - not available. This phone have PM308 protected, SD security in not restorable. - Avoid SW Downgrade & manual erase to this phone ! SIMLOCK seems to be valid SUPERDONGLE_KEY seems to be valid SIMLOCK_TEST passed SECURITY_TEST failed! Imei net: 351962032144053 Version: SIMLOCK SERVER 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 THIS IS MY PROBLAM

01-23-2010, 15:05	#4 (permalink)
SinghForHelp Freak Poster Join Date: Feb 2007 Location: In Your Heart Posts: 496 Member: 451538 Status: Offline Thanks Meter: 98	WHEN I TRY TO auth pm THEN IT SAYS 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 115.187.16.2 Bad phones ack, probably SUPERDONGLE_KEY corrupted ! Wrong response to SD verify request

01-23-2010, 16:50	#5 (permalink)
t.technic Registered User Join Date: Nov 2008 Location: tepian brantas,east java.Ina Posts: 101 Member: 892591 Status: Offline Thanks Meter: 42	may be your phone ever repaired with other tools,SDK become not detected by mx?? Ur procedure is right, but your lucky is not your hand. try with other tool bro,,

01-23-2010, 16:54	#6 (permalink)
Umair Rashid No Life Poster Join Date: Dec 2006 Location: Rawalpindi, Pakistan Posts: 2,292 Member: 421117 Status: Offline Sonork: +92 346 5544377 (PHONE) Thanks Meter: 2,522	. Do as follows .

01-23-2010, 19:46	#7 (permalink)
Andra No Life Poster Join Date: Feb 2005 Location: AD Posts: 4,665 Member: 976728 Status: Offline Sonork: 1589709 Thanks Meter: 4,775	can u do SX-4 by mxkey server here ? if phone already simlock / superdongle fix by another tool u can't use that "button" at moment. but coder already have some ways to make that work on future. another ways u can use this tricks Just in case if Recovery via Server doesn't work....... br,

01-24-2010, 16:26	#8 (permalink)
SinghForHelp Freak Poster Join Date: Feb 2007 Location: In Your Heart Posts: 496 Member: 451538 Status: Offline Thanks Meter: 98	Phone Type: RM-436 (Nokia 7210 Supernova) SW Version: V 07.23 17-07-09 RM-436 (c) Nokia Imei plain: 35196203214405-3 Product Code: 0566807 Language Pack: - not available. This phone have PM308 protected, SD security in not restorable. - Avoid SW Downgrade & manual erase to this phone ! SIMLOCK seems to be valid SUPERDONGLE_KEY seems to be valid SIMLOCK_TEST passed SECURITY_TEST failed! Imei net: 351962032144053 Version: SIMLOCK SERVER 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 RAP Data : SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x] EM0 ID: 00000295 EM1 ID: 00000B22 PUBLIC ID: 0A70020AAA087D56CC55CEF748408C29BC534FBE 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 RAP 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,RAP ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 ExtDEVC: FFFF 0000 - 0000 0000 Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0 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: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026 Reading RAP NPC (0x168 bytes) Original Product Code: 0572571 Reading RAP VARIANT (0x0 bytes) Reading RAP CCC (0x160 bytes) Product Code: 0581686 Product Code missmatch ! Reading RAP HWC (0xD4 bytes) Product Code: 0566932 Product Code missmatch !

01-24-2010, 16:28	#9 (permalink)
SinghForHelp Freak Poster Join Date: Feb 2007 Location: In Your Heart Posts: 496 Member: 451538 Status: Offline Thanks Meter: 98	what to do now. not solved sir

01-24-2010, 16:50	#11 (permalink)
SinghForHelp Freak Poster Join Date: Feb 2007 Location: In Your Heart Posts: 496 Member: 451538 Status: Offline Thanks Meter: 98	RAP Data : SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x] EM0 ID: 00000295 EM1 ID: 00000B22 PUBLIC ID: 0A70020AAA087D56CC55CEF748408C29BC534FBE 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 RAP 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,RAP ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 ExtDEVC: FFFF 0000 - 0000 0000 Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0 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: F1DCA5EA5203CD30A64D4D95ABCD621F4AB23026 Reading RAP NPC (0x168 bytes) Original Product Code: 0572571 Reading RAP VARIANT (0x0 bytes) Reading RAP CCC (0x160 bytes) Product Code: 0581686 Product Code missmatch ! Reading RAP HWC (0xD4 bytes) Product Code: 0566932 Product Code missmatch !

01-24-2010, 16:54	#12 (permalink)
SinghForHelp Freak Poster Join Date: Feb 2007 Location: In Your Heart Posts: 496 Member: 451538 Status: Offline Thanks Meter: 98	yes i try. but sx4 is not done so how can pm will write. see here logs. 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 115.187.16.2 Bad phones ack, probably SUPERDONGLE_KEY corrupted ! Wrong response to SD verify request Writing PM from Node ... Section: 1 Warning: failed to write 1 - 0 (12 bytes) Warning: failed to write 1 - 2 (70 bytes) Warning: failed to write 1 - 3 (70 bytes) Warning: failed to write 1 - 4 (70 bytes) Warning: failed to write 1 - 6 (276 bytes) Warning: failed to write 1 - 7 (276 bytes) Warning: failed to write 1 - 8 (276 bytes) Warning: failed to write 1 - 10 (384 bytes) Warning: failed to write 1 - 11 (384 bytes) Warning: failed to write 1 - 12 (384 bytes) Warning: failed to write 1 - 14 (384 bytes) Warning: failed to write 1 - 15 (384 bytes) Warning: failed to write 1 - 16 (384 bytes) Warning: failed to write 1 - 17 (32 bytes) Warning: failed to write 1 - 19 (16 bytes) Section: 2 - Key: 0, size 440 bytes written. Section: 4 - Key: 1, size 800 bytes written. - Key: 3, size 10 bytes written. - Key: 4, size 8 bytes written. - Key: 5, size 8 bytes written. - Key: 6, size 8 bytes written. - Key: 9, size 5 bytes written. - Key: 18, size 80 bytes written. - Key: 19, size 4 bytes written. - Key: 28, size 2 bytes written. Section: 8 - Key: 0, size 2 bytes written. - Key: 1, size 16 bytes written. - Key: 2, size 16 bytes written. - Key: 3, size 128 bytes written. - Key: 4, size 128 bytes written. - Key: 8, size 8 bytes written. Section: 11 - Key: 0, size 4 bytes written. - Key: 1, size 4 bytes written. - Key: 2, size 4 bytes written. - Key: 3, size 4 bytes written. - Key: 5, size 6 bytes written. - Key: 6, size 2 bytes written. - Key: 14, size 2 bytes written. - Key: 15, size 2 bytes written. - Key: 16, size 2 bytes written. - Key: 17, size 2 bytes written. - Key: 18, size 16 bytes written. - Key: 19, size 32 bytes written. - Key: 20, size 32 bytes written. - Key: 21, size 2 bytes written. - Key: 22, size 2 bytes written. - Key: 23, size 2 bytes written. - Key: 24, size 2 bytes written. - Key: 25, size 2 bytes written. - Key: 26, size 2 bytes written. - Key: 27, size 2 bytes written. - Key: 28, size 2 bytes written. - Key: 29, size 2 bytes written. - Key: 30, size 2 bytes written. - Key: 31, size 2 bytes written. - Key: 32, size 2 bytes written. - Key: 33, size 2 bytes written. - Key: 34, size 2 bytes written. - Key: 35, size 2 bytes written. - Key: 36, size 2 bytes written. - Key: 37, size 2 bytes written. - Key: 38, size 2 bytes written. - Key: 39, size 2 bytes written. - Key: 40, size 2 bytes written. - Key: 41, size 2 bytes written. - Key: 42, size 2 bytes written. - Key: 43, size 2 bytes written. - Key: 44, size 2 bytes written. - Key: 45, size 2 bytes written. - Key: 46, size 2 bytes written. - Key: 47, size 2 bytes written. - Key: 48, size 2 bytes written. - Key: 49, size 2 bytes written. - Key: 50, size 2 bytes written. - Key: 51, size 2 bytes written. - Key: 52, size 2 bytes written. - Key: 53, size 2 bytes written. - Key: 54, size 2 bytes written. - Key: 55, size 2 bytes written. - Key: 56, size 2 bytes written. - Key: 57, size 2 bytes written. - Key: 58, size 2 bytes written. - Key: 59, size 2 bytes written. - Key: 60, size 2 bytes written. - Key: 61, size 2 bytes written. - Key: 62, size 2 bytes written. - Key: 63, size 2 bytes written. - Key: 64, size 2 bytes written. - Key: 65, size 2 bytes written. - Key: 66, size 4 bytes written. - Key: 68, size 4 bytes written. - Key: 69, size 4 bytes written. - Key: 70, size 4 bytes written. - Key: 71, size 4 bytes written. - Key: 72, size 16 bytes written. - Key: 73, size 4 bytes written. - Key: 74, size 2 bytes written. - Key: 75, size 13 bytes written. Section: 31 - Key: 4, size 14 bytes written. Section: 42 - Key: 0, size 2 bytes written. - Key: 1, size 12 bytes written. - Key: 2, size 36 bytes written. - Key: 3, size 36 bytes written. - Key: 4, size 36 bytes written. - Key: 5, size 36 bytes written. - Key: 6, size 36 bytes written. - Key: 7, size 40 bytes written. - Key: 8, size 40 bytes written. - Key: 9, size 40 bytes written. - Key: 10, size 40 bytes written. - Key: 11, size 40 bytes written. - Key: 12, size 40 bytes written. - Key: 13, size 40 bytes written. - Key: 14, size 40 bytes written. Section: 50 - Key: 0, size 2 bytes written. Section: 54 - Key: 0, size 2 bytes written. Section: 66 - Key: 0, size 415 bytes written. - Key: 1, size 240 bytes written. - Key: 2, size 240 bytes written. - Key: 5, size 240 bytes written. - Key: 6, size 4 bytes written. - Key: 7, size 4 bytes written. - Key: 8, size 4 bytes written. - Key: 9, size 4 bytes written. - Key: 10, size 240 bytes written. - Key: 11, size 240 bytes written. - Key: 16, size 4 bytes written. - Key: 18, size 4 bytes written. - Key: 20, size 4 bytes written. - Key: 22, size 4 bytes written. - Key: 24, size 4 bytes written. - Key: 26, size 4 bytes written. - Key: 28, size 4 bytes written. - Key: 30, size 4 bytes written. Warning: failed to write 66 - 32 (4 bytes) Warning: failed to write 66 - 54 (8 bytes) Warning: failed to write 66 - 55 (8 bytes) Warning: failed to write 66 - 56 (8 bytes) Warning: failed to write 66 - 57 (8 bytes) Warning: failed to write 66 - 71 (8 bytes) Warning: failed to write 66 - 72 (8 bytes) Warning: failed to write 66 - 74 (6144 bytes) Warning: failed to write 66 - 75 (300 bytes) Warning: failed to write 66 - 76 (60 bytes) Warning: failed to write 66 - 85 (3 bytes) Warning: failed to write 66 - 86 (3 bytes) Warning: failed to write 66 - 87 (3 bytes) Warning: failed to write 66 - 89 (4 bytes) Warning: failed to write 66 - 90 (4 bytes) - Key: 91, size 4 bytes written. - Key: 92, size 4 bytes written. Warning: failed to write 66 - 93 (4 bytes) Warning: failed to write 66 - 94 (6 bytes) Warning: failed to write 66 - 96 (4 bytes) Warning: failed to write 66 - 103 (120 bytes) Warning: failed to write 66 - 105 (30 bytes) Warning: failed to write 66 - 107 (8 bytes) Warning: failed to write 66 - 110 (7 bytes) Section: 88 Warning: failed to write 88 - 0 (36 bytes) Section: 96 Warning: failed to write 96 - 0 (2 bytes) Warning: failed to write 96 - 1 (20 bytes) Section: 107 Warning: failed to write 107 - 0 (21 bytes) Warning: failed to write 107 - 1 (89 bytes) Warning: failed to write 107 - 2 (69 bytes) Warning: failed to write 107 - 3 (70 bytes) Warning: failed to write 107 - 26 (12 bytes) Section: 193 Warning: failed to write 193 - 2 (8 bytes) Warning: failed to write 193 - 3 (32 bytes) Warning: failed to write 193 - 4 (32 bytes) Warning: failed to write 193 - 9 (64 bytes) Section: 218 Warning: failed to write 218 - 0 (2 bytes) Section: 238 Section: 309 Warning: failed to write 309 - 0 (4 bytes) Warning: failed to write 309 - 1 (2 bytes) Warning: failed to write 309 - 2 (12 bytes) Warning: failed to write 309 - 4 (12 bytes) Warning: failed to write 309 - 5 (12 bytes) Warning: failed to write 309 - 7 (12 bytes) Warning: failed to write 309 - 8 (12 bytes) Warning: failed to write 309 - 17 (12 bytes) Warning: failed to write 309 - 22 (12 bytes) Section: 322 Section: 334 Section: 339 - Key: 0, size 511 bytes written. - Key: 1, size 511 bytes written. Section: 341 - Key: 3, size 4 bytes written. - Key: 4, size 4414 bytes written. Section: 354 - Key: 0, size 3 bytes written. Section: 355 - Key: 1, size 2028 bytes written. Section: 356 - Key: 0, size 2 bytes written. Section: 362 - Key: 1, size 120 bytes written. Completed in 23.093 s

01-24-2010, 17:33	#13 (permalink)
emad2007 Freak Poster Join Date: Jan 2007 Location: MX-KEY is the BEST NOKIA TOOL Posts: 104 Member: 440570 Status: Offline Thanks Meter: 9	MX-KEY is the BEST NOKIA TOOL

01-24-2010, 17:35	#14 (permalink)
SinghForHelp Freak Poster Join Date: Feb 2007 Location: In Your Heart Posts: 496 Member: 451538 Status: Offline Thanks Meter: 98	please solv my problam

01-24-2010, 17:40	#15 (permalink)
kharisma Major Poster Join Date: Oct 2008 Location: MX-KEY is the BEST NOKIA TOOL Posts: 43 Member: 883736 Status: Offline Sonork: kharisma_phone Thanks Meter: 5	Just in case if Recovery via Server doesn't work.......