sure, server problem ( Super SD Auth error ) - GSM-Forum

dharyadi · 05-06-2010, 19:38

I dont know why this problem come back again.
please check, i know how to repair fone, but after new release 3.4 this problem come. i am trying today from morning till tonigh still error.

1. repair simlock OK
2. repair Super Dongle OK
3. Super Dongle Auth Always Error

1st super SD Auth

Quote:

Using device: POTATO BOX, FW ver: 01.B1
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

Product: V 05.00 27-04-07 RM-174 (c) Nokia.

Using cached productData[23300211D3680058B02EA2905C15383BDBD49EF0] ...

Authenticating to SUPERDONGLE using security server ...
SERVER->Served by MXKEY - BLADE X at host2, agent version 1.0 revision 1.5

Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

REPAIR SIMLOCK

Quote:

Imei net: 356300016253654
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

Using device: POTATO BOX, FW ver: 01.B1
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

Product: V 05.00 27-04-07 RM-174 (c) Nokia.

Using cached productData[23300211D3680058B02EA2905C15383BDBD49EF0] ...

Calculating SIMLOCK using security server ...
SERVER->Served by MXKEY - BLADE X at host2, agent version 1.0 revision 1.5

Completed in 7.765 s

RPL saved to "E:\mobileEx\3.4\data\backup\BB5_RM-174_356300016253654_SIM.RPL"
Updating SIMLOCK...OK

Reading Simlock info ...
Imei net: 356300016253654
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

REPAIR SD

Quote:

Using device: POTATO BOX, FW ver: 01.B1
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

Product: V 05.00 27-04-07 RM-174 (c) Nokia.

Using cached productData[23300211D3680058B02EA2905C15383BDBD49EF0] ...

Calculating SUPERDONGLE using security server ...
SERVER->Served by MXKEY - BLADE X at host2, agent version 1.0 revision 1.5

Completed in 7.656 s

RPL saved to "E:\mobileEx\3.4\data\backup\BB5_RM-174_356300016253654_SD.RPL"
Updating SUPERDONGLE_KEY ...OK

2nd SUPER SD AUTH ( still problem)

Quote:

Using device: POTATO BOX, FW ver: 01.B1
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

Product: V 05.00 27-04-07 RM-174 (c) Nokia.

Using cached productData[23300211D3680058B02EA2905C15383BDBD49EF0] ...

Authenticating to SUPERDONGLE using security server ...
SERVER->Served by MXKEY - BLADE X at host2, agent version 1.0 revision 1.5

Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

BB5 CERTIFICATE VALIDATION

Quote:

RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 23300211D3680058B02EA2905C15383BDBD49EF0
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
TransmissionMode: 16Bit
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
Reading RAP NPC (0x168 bytes)
Original Product Code: 0535401
Reading RAP VARIANT (0x0 bytes)
Reading RAP CCC (0x160 bytes)
Product Code: 0535401
CCC seems to be valid
Reading RAP HWC (0xD4 bytes)
Product Code: 0535401
HWC seems to be valid

hope fix it asap.

WAJID PNR · 05-06-2010, 19:42

i did 2,3 mobile it ok change sx server then try,
i got good result
try again

Kethey · 05-06-2010, 19:50

Quote:

Originally Posted by dharyadi

I dont know why this problem come back again.
please check, i know how to repair fone, but after new release 3.4 this problem come. i am trying today from morning till tonigh still error.

1. repair simlock OK
2. repair Super Dongle OK
3. Super Dongle Auth Always Error

1st super SD Auth

REPAIR SIMLOCK

REPAIR SD

2nd SUPER SD AUTH ( still problem)

BB5 CERTIFICATE VALIDATION

hope fix it asap.

Me too has same problem. May be it is server problem

dharyadi · 05-06-2010, 19:55

Quote:

Originally Posted by ktkwajid

i did 2,3 mobile it ok change sx server then try,
i got good result
try again

I am tire today.
take rest and trying again tommorow..

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

Product: V 07.20 23-10-08 RM-174 (c) Nokia.

Using cached productData[23300211D3680058B02EA2905C15383BDBD49EF0] ...

Authenticating to SUPERDONGLE using security server ...
SERVER->Served by MXKEY - BLADE X at host3, agent version 1.0 revision 1.5

Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

dharyadi · 05-06-2010, 20:15

last try tonigh............................................ ..

Quote:

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

Product: V 07.20 23-10-08 RM-174 (c) Nokia.

Using cached productData[23300211D3680058B02EA2905C15383BDBD49EF0] ...

Authenticating to SUPERDONGLE using security server ...
SERVER->Served by MXKEY - BLADE X at host1, agent version 1.0 revision 1.5

Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

============================================

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

Product: V 07.20 23-10-08 RM-174 (c) Nokia.

Using cached productData[23300211D3680058B02EA2905C15383BDBD49EF0] ...

Authenticating to SUPERDONGLE using security server ...
SERVER->Served by MXKEY - BLADE X at host2, agent version 1.0 revision 1.5

Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

============================================

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

Product: V 07.20 23-10-08 RM-174 (c) Nokia.

Using cached productData[23300211D3680058B02EA2905C15383BDBD49EF0] ...

Authenticating to SUPERDONGLE using security server ...
SERVER->Served by MXKEY - BLADE X at host3, agent version 1.0 revision 1.5

Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

==================================================

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

Product: V 07.20 23-10-08 RM-174 (c) Nokia.

Using cached productData[23300211D3680058B02EA2905C15383BDBD49EF0] ...

Authenticating to SUPERDONGLE using security server ...
SERVER->Served by MXKEY - BLADE X at host4, agent version 1.0 revision 1.5

Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

MOURAD™ · 05-06-2010, 20:22

Authenticating to SUPERDONGLE using security server ...
SERVER->Served by MXKEY - BLADE X at host2, agent version 1.0 revision 1.5

Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

hope mx team fix this problem ASAP.

**UNLOCK PARK ®** · 05-06-2010, 20:42

Quote:

Originally Posted by ktkwajid

i did 2,3 mobile it ok change sx server then try,
i got good result
try again

how to change sx4 server

MOURAD™ · 05-06-2010, 21:04

Quote:

Originally Posted by gsm_yousuf

how to change sx4 server

Bro,

**UNLOCK PARK ®** · 05-06-2010, 21:17

Quote:

Originally Posted by Mrd07

Bro,

Thanks but not working

Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

MOURAD™ · 05-06-2010, 21:26

Quote:

Thanks but not working

Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

look this.......................

dharyadi · 05-07-2010, 03:36

WHERE THE PROBLEM.??????????????

PMM AUTH

Quote:

SERVER->Served by MXKEY - BLADE X at host4, agent version 1.0 revision 1.5

Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...Connection timed out
Connecting to server[main.mxkey.biz] ...Connection timed out
Connecting to server[main.mxkey.biz] ...Connection timed out

SUPER SD AUTH

Quote:

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

Product: V 07.20 23-10-08 RM-174 (c) Nokia.

Using cached productData[23300211D3680058B02EA2905C15383BDBD49EF0] ...

Authenticating to SUPERDONGLE using security server ...
SERVER->Served by MXKEY - BLADE X at host4, agent version 1.0 revision 1.5

Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

CONNECTION TO main.mxkey.biz

Quote:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DIJEE>ping main.mxkey.biz

Pinging main.mxkey.biz [202.122.12.178] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 202.122.12.178:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\DIJEE>tracert main.mxkey.biz

Tracing route to main.mxkey.biz [202.122.12.178]
over a maximum of 30 hops:

1 880 ms 899 ms 659 ms 10.208.17.75
2 715 ms 659 ms 742 ms 10.208.19.73
3 843 ms 719 ms 719 ms 10.159.33.140
4 839 ms 678 ms 700 ms 10.159.33.140
5 1026 ms 857 ms 761 ms 10.159.33.146
6 801 ms 678 ms 797 ms 10.208.17.68
7 696 ms 779 ms 797 ms 114.4.16.26
8 792 ms 880 ms 779 ms 202.152.164.222
9 796 ms 797 ms 839 ms giga-0-0.openixp.net [218.100.27.129]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

CONNECTION TO HOST4.MXKEY.BIZ

Quote:

C:\Documents and Settings\DIJEE>ping host4.mxkey.biz

Pinging host4.mxkey.biz [193.37.152.121] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 193.37.152.121:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\DIJEE>tracert host4.mxkey.biz

Tracing route to host4.mxkey.biz [193.37.152.121]
over a maximum of 30 hops:

1 1639 ms 1397 ms 1379 ms 10.208.17.75
2 1396 ms 1079 ms 941 ms 10.208.19.73
3 1060 ms 1079 ms 1217 ms 10.159.33.140
4 1198 ms 1517 ms 1259 ms 10.159.33.140
5 1018 ms 1180 ms 1398 ms 10.159.33.146
6 1317 ms 1259 ms 1199 ms 10.208.17.68
7 1162 ms 898 ms 1038 ms 114.4.16.26
8 999 ms 1278 ms 1259 ms 202.93.41.230
9 1377 ms 978 ms 1360 ms so-4-1-2.edge2.LosAngeles1.Level3.net [4.71.134.
49]
10 1219 ms 936 ms 1161 ms ae-73-70.ebr3.LosAngeles1.Level3.net [4.69.144.1
16]
11 1754 ms 1601 ms 1355 ms ae-4-4.ebr4.Washington1.Level3.net [4.69.132.82]

12 3734 ms 1301 ms 1079 ms ae-74-74.csw2.Washington1.Level3.net [4.69.134.1
82]
13 3434 ms * 1797 ms ae-72-72.ebr2.Washington1.Level3.net [4.69.134.1
49]
14 3656 ms 1522 ms 1355 ms ae-42-42.ebr2.Frankfurt1.Level3.net [4.69.137.53
]
15 3416 ms 1739 ms 1499 ms ae-82-82.csw3.Frankfurt1.Level3.net [4.69.140.26
]
16 3452 ms 1380 ms 1780 ms ae-81-81.ebr1.Frankfurt1.Level3.net [4.69.140.9]

17 * * 2697 ms ae-4-4.car1.Munich1.Level3.net [4.69.134.1]
18 * * * Request timed out.
19 3055 ms * * ten9-1.r2.muc2.m-online.net [212.18.7.157]
20 * * 2917 ms ten9-1.r2.muc2.m-online.net [212.18.7.157]
21 * 1622 ms 1477 ms gw01.giga-hosting.biz [93.104.204.34]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

dharyadi · 05-07-2010, 05:05

change internet service provider, error still same.

..::Nihal::.. · 05-07-2010, 05:53

Why is MX-KEY team not replying to these threads........

cel_phon · 05-07-2010, 06:45

yes - new server installed and need alteration timely as per users response

problems pointed-out by users are being solved - all processes are in pipe line

dharyadi · 05-07-2010, 08:20

as i see, agent version already update, but still no work for me.

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010)

Product: V 07.20 23-10-08 RM-174 (c) Nokia.

Using cached productData[23300211D3680058B02EA2905C15383BDBD49EF0] ...

Authenticating to SUPERDONGLE using security server ...
SERVER->Served by MXKEY - BLADE X at host4, agent version 1.0 revision 1.6

Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
SERVER->Served by MXKEY - BLADE X at host4, agent version 1.0 revision 1.6

Scanning local SX4 Card ...
No SX4 Card found.
Authenticating using security server ...
Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(CN), hello 182.0.141.238
Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request

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
error (1002) simlock3.dll winopen	fondas	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	0	08-28-1999 15:57
HELP: Problem with 5110	Xabi	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	1	07-16-1999 00:44

05-06-2010, 19:42	#2 (permalink)
WAJID PNR No Life Poster Join Date: Nov 2007 Location: Dubai. Posts: 1,063 Member: 625961 Status: Offline Sonork: 100.1590447 Thanks Meter: 1,285	i did 2,3 mobile it ok change sx server then try, i got good result try again

05-06-2010, 20:22	#6 (permalink)
MOURAD™ No Life Poster Join Date: Mar 2007 Location: Guangzhou-China Posts: 1,289 Member: 468587 Status: Offline Sonork: 100.1612429 Thanks Meter: 681	Authenticating to SUPERDONGLE using security server ... SERVER->Served by MXKEY - BLADE X at host2, agent version 1.0 revision 1.5 Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted ! Wrong response to SD verify request hope mx team fix this problem ASAP.

05-07-2010, 05:05	#12 (permalink)
dharyadi No Life Poster Join Date: Oct 2006 Age: 45 Posts: 687 Member: 369678 Status: Offline Thanks Meter: 192	change internet service provider, error still same.

05-07-2010, 05:53	#13 (permalink)
..::Nihal::.. Freak Poster Join Date: Apr 2010 Location: In ThE HeaRT Of GSMHoStInG Posts: 166 Member: 1275013 Status: Offline Thanks Meter: 64	Why is MX-KEY team not replying to these threads........

05-07-2010, 06:45	#14 (permalink)
cel_phon No Life Poster Join Date: Jan 2009 Location: M_B_Din-PK Posts: 3,979 Member: 950201 Status: Offline Thanks Meter: 1,928	yes - new server installed and need alteration timely as per users response problems pointed-out by users are being solved - all processes are in pipe line

05-07-2010, 08:20	#15 (permalink)
dharyadi No Life Poster Join Date: Oct 2006 Age: 45 Posts: 687 Member: 369678 Status: Offline Thanks Meter: 192	as i see, agent version already update, but still no work for me. Using device: UFS_USB V2.8 (c) SarasSoft 2007. Library version: 1.0.0.8336(03-05-2010), 1.0.0.12955(03-05-2010) Product: V 07.20 23-10-08 RM-174 (c) Nokia. Using cached productData[23300211D3680058B02EA2905C15383BDBD49EF0] ... Authenticating to SUPERDONGLE using security server ... SERVER->Served by MXKEY - BLADE X at host4, agent version 1.0 revision 1.6 Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted ! Wrong response to SD verify request SERVER->Served by MXKEY - BLADE X at host4, agent version 1.0 revision 1.6 Scanning local SX4 Card ... No SX4 Card found. Authenticating using security server ... Connecting to server[main.mxkey.biz] ...MXKEY-SX4 ver 2.5(CN), hello 182.0.141.238 Bad phones ack, probably SUPERDONGLE_KEY corrupted ! Wrong response to SD verify request