Reason why SX4 cant access? "Wrong response to SD verify request"

[daveiant]

option under
PHONE TEST > BB5 Certificate validation

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: 0566832
Reading RAP VARIANT (0x0 bytes)
Reading RAP CCC (0x160 bytes)
Product Code: 0566807
Product Code missmatch !
Reading RAP HWC (0xD4 bytes)
Product Code: 0566807
Product Code missmatch !

Original Product code: 0566832

MR. Manole plz help......

[cellcarekphb]

same problem
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 1FD00107165C7D56130A2D825CB664BF82D73C26
ASIC MODE ID: 00
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 9.11.1 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 8A31 [Intel NU48F512,512 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: 9.17.0 revision: 0.0 size: 0x22E90
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: 0566807
Product Code missmatch !
Reading RAP HWC (0xD4 bytes)
Product Code: 0572571
HWC seems to be valid
please help.

[daveiant]

another logs..
Using device: J.A.F, FW ver: 01.B1
Library version: 1.0.0.11985, Date: 03-02-2010
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 0BA0011948F67C568A89A0E1A4664FF59BC1769A
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: 35196203661091
Original Product code: 0566933
Bluetooth ID: 00247C39B5DC

Phone Type: RM-436 (Nokia 7210 Supernova)
SW Version: V 07.23 17-07-09 RM-436 (c) Nokia
Imei plain: 35196203661091-9
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: 351962036610919
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

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

[shahinahmed007]

Originally Posted by cellcarekphb

same problem
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 1FD00107165C7D56130A2D825CB664BF82D73C26
ASIC MODE ID: 00
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 9.11.1 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 8A31 [Intel NU48F512,512 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: 9.17.0 revision: 0.0 size: 0x22E90
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: 0566807
Product Code missmatch !
Reading RAP HWC (0xD4 bytes)
Product Code: 0572571
HWC seems to be valid
please help.

your ccc data damage. try this method-------
http://forum.gsmhosting.com/vbb/showthread.php?t=918108

[daveiant]

Originally Posted by shahinahmed007

your ccc data damage. try this method-------
http://forum.gsmhosting.com/vbb/showthread.php?t=918108

dnt thnk so.....i tried that solution, but still no luck...have any idea guyz ?

[bireun]

I think the server is not working well for SUPER SD AUTH.

[sunny_luthras99]

after sd calculations with sd.rpl sd becomes passed but security bocomes failed {Bad phones ack, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request}

this happens bcoz sd remains passed virtually in the phone
and pm auth need online connection when ever it goes online it reads the actual superdongle area of mobile and thats corrupted thats y pm auth failed

[.::Dr.Gsm::.]

Nokia N70

After Repair SD

No Super SD AUTH
No Pm Aurh

No RECOVER CERT

And Also TRy This

Solution for: "SECURITY_TEST failed!" and "warning: SD authorized but verify failed!"
If after repair SD and/or Simlock (Super Dongle RPL and Simlock RPL upload) you get "SECURITY_TEST failed!" and/or "warning: SD authorized but verify failed!".
This is comming usually because some PM fields and/or RPL sections are missing from your phone (e.g. DRM keys, CCC, ...).

Solution 1 (easy way, maybe not work all time, depends how phone was damaged):
- write full PM from SAME phone model (product number) WITHOUT fields 1, 308, 309 (and WITHOUT field 120 for SL20 based phones)
- unplug/replug phone from JAF/UFS box
- make Simlock RPL repair
- make SD RPL repair
- unplug/replug phone from JAF/UFS box
- make SUPER SX4 Auth then write PM1 and PM309

if still have problems, use Solution 2:

- backup RPL (NPC, CCC, HWC, ...), will call this ORIGINAL RPL
- backup RPL from another working phone (same model) with SAME product code
- edit this good RPL from another phone and remove NPC section (all lines who start with NPC_DATA_1 ... NPC_DATA_xx), will call this edited file CLONE RPL
- backup full PM from another working phone (same model) with SAME product code, will call this file CLONE PM
- full erase flash chip (use erase file regarding flash chip size)
- flash phone (CMT, APE, ...)
- upload CLONE RPL
- upload ORIGINAL RPL
- write full CLONE PM without fields 1,120,308,309
- unplug/replug phone from JAF/UFS box
- make Simlock RPL repair
- make SD RPL repair
- unplug/replug phone from JAF/UFS box
- make SUPER SX4 Auth then write PM1 and PM309

Manole

But Still Same

[Sniper_04]

http://www.gsmsandwich.com.ph/forum/...highlight=5220


check this forum............

100% tested