"SUPERDONGLE_KEY invalid!" after flash phone !!! - GSM-Forum

msantar · 11-23-2009, 17:02

hello mx team,
i have Nokia 7210 Supernova. it was restart problem.
now i flash with V 06.51.
after flash SUPERDONGLE_KEY invalid!
i 100% sure before flash it was all ok.
now show this error

Phone Type: RM-436 (Nokia 7210 Supernova)
SW Version: V 06.51 23-03-09 RM-436 (c) Nokia
Imei plain: 3519xxxxxxxxxxxxx
Product Code: 0566806
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 invalid!
- WD timer enabled, phone will reboot itself after 3 min.
SIMLOCK_TEST passed
SECURITY_TEST passed

Imei net: 3519xxxxxxxxxx
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

i write backup rpl. which is mx-key saved b4 flash start.

this is very big problem to me set is auto off after few second.

need help please.

haji rahim · 11-23-2009, 17:14

Dear bro try to write backup with mexkey...
if you have pm or RPL;;;;

.:GSM International:. · 11-23-2009, 17:20

Quote:

Originally Posted by haji rahim

Dear bro try to write backup with mexkey...
if you have pm or RPL;;;;

Are you thick mate, or just plain stupid? Or, maybe you cant read, cos if you could you would see CLEARLY that he said he had WRITTEN BACKUP of phone that MxKey made!

msantar · 11-23-2009, 17:36

there are rpl. i write that but same

Rabatu · 11-23-2009, 17:50

that only means in its restarting state prior to flashing Superdongle Invalid was already there............getz? now you need new rpl since your back-up was already damaged

neilthirumuttam · 11-23-2009, 17:50

which version was the set before flashing ?
did u checked with product code or image dl option before flash ?

msantar · 11-23-2009, 17:56

if i write backup show this
RPL: "C:\mobileEx\3.2\data\backup\RPL\BB5_351xxxxxxxxxx x_BACK.rpl"
Imei: 3519xxxxxxxxxx
Restoring RF/BB DATA from backup ...
Updating RF ...OK
Updating BB ...OK
Updating WARRANTY ...OK
Updating PROD ...OK
Updating BT ...OK
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM1 ID: 00000295
EM2 ID: 00000B22
PUBLIC ID: 1E80001964497D562064127100B9CED19F42E410
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
NPC verified Ok.
Updating CMT NPC ...OK
Updating CMT CCC ...OK
Updating CMT HWC ...OK
Updating PRODUCTCODE (0566806)... OK
Updating PSN (DTC186745)... OK
Updating HWID (1000)... OK
Updating SIMLOCK...OK
Trying to update SUPERDONGLE_KEY ...error 0x0
Updating WMDRM_PD...OK
Certificate programmed successfully !

Phone Type: RM-436 (Nokia 7210 Supernova)
SW Version: V 07.23 17-07-09 RM-436 (c) Nokia
Imei plain: 3519xxxxxxxxxx-0
Product Code: 0566806
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 invalid!
- WD timer enabled, phone will reboot itself after 3 min.
SIMLOCK_TEST passed
SECURITY_TEST passed

TimeStamp: 2009-07-20T08:46:24Z
SW Version: 07.23
Variant Version: 012
ProductProfile: RM436_0566806_07.23_012.spr
Simlock: 0566806_simlock.bin

Imei net: 351xxxxxxxxxxxx
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

Riteshgpt60 · 11-23-2009, 18:00

You don't need to worry bro- SIMPLE, It was restart problem and now it is restarting only because of SUPERDONGLE KEY INVALID!
I can say that it was SUPERDONGLE KEY INVALID! before you flash.If not then you have to prove by posting scanlog before flash.
I flash many phones and did'nt ever encounter such kind of problem!

msantar · 11-23-2009, 18:02

when i write rpl back up
show superdongle data authentic
just look this

[/IMG]

thanks

msantar · 11-24-2009, 18:30

Quote:

Originally Posted by Riteshgpt60

You don't need to worry bro- SIMPLE, It was restart problem and now it is restarting only because of SUPERDONGLE KEY INVALID!
I can say that it was SUPERDONGLE KEY INVALID! before you flash.If not then you have to prove by posting scanlog before flash.
I flash many phones and did'nt ever encounter such kind of problem!

i am 100% sure it was all ok b4 flash, if i know it happean really i saved the log 4 proof.
really mx key damage this phone.
i think no way without new rpl.

adelkaha25 · 11-24-2009, 19:30

if the software of MXkey show phone authentificated to superdongle message after writting RPL bakup that mean your superdongle key in this time is correct (RPL backup of mxkey contain simlock data).
try to make info after wrriting RPL backup and post log here

can you tel us what do you do after writting RPL backup?

msantar · 11-25-2009, 18:35

Quote:

Originally Posted by adelkaha25

if the software of MXkey show phone authentificated to superdongle message after writting RPL bakup that mean your superdongle key in this time is correct (RPL backup of mxkey contain simlock data).
try to make info after wrriting RPL backup and post log here

can you tel us what do you do after writting RPL backup?

so why not show superdongle data valid?
i try to write pm via sx4 authentic show superdongle data corrupt???

if u have solution plz share.

Rabatu · 11-25-2009, 19:01

try reset NPC then write your back-up PM then restore your back-up RPL

i've been using MXKEY for several months especially in BB5 flashing. Doing some experiment destroying erasing all Flash Data and restoring all again with full success. Mxkey is very reliable when it comes with BB5.

imagine again your phone keeps on restarting not because of HW problem but because of SW related problem...something corrupted there in which we never exactly knew which area. so Only possible if it was downgraded things like that.

adelkaha25 · 11-25-2009, 20:30

Quote:

Originally Posted by msantar

so why not show superdongle data valid?
i try to write pm via sx4 authentic show superdongle data corrupt???

if u have solution plz share.

i have an experience with 7210 supernova RM-436 the way to solve this problem is to flash the set with his original firmware and restore your backup that's the solution i have to suggest for your problem.

bood luck

Riteshgpt60 · 11-26-2009, 03:13

Ok if you are sure ,then try to do what adelkaha25 had said!

11-23-2009, 17:02	#1 (permalink)
msantar Banned Join Date: Dec 2006 Location: inside of infinity best tool Posts: 1,142 Member: 411831 Status: Offline Thanks Meter: 215	"SUPERDONGLE_KEY invalid!" after flash phone !!! hello mx team, i have Nokia 7210 Supernova. it was restart problem. now i flash with V 06.51. after flash SUPERDONGLE_KEY invalid! i 100% sure before flash it was all ok. now show this error Phone Type: RM-436 (Nokia 7210 Supernova) SW Version: V 06.51 23-03-09 RM-436 (c) Nokia Imei plain: 3519xxxxxxxxxxxxx Product Code: 0566806 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 invalid! - WD timer enabled, phone will reboot itself after 3 min. SIMLOCK_TEST passed SECURITY_TEST passed Imei net: 3519xxxxxxxxxx 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 i write backup rpl. which is mx-key saved b4 flash start. this is very big problem to me set is auto off after few second. need help please.

11-23-2009, 18:02	#9 (permalink)
msantar Banned Join Date: Dec 2006 Location: inside of infinity best tool Posts: 1,142 Member: 411831 Status: Offline Thanks Meter: 215	superdongle data authentic when i write rpl back up show superdongle data authentic just look this [/IMG] thanks

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
AP75 invalid PPF after flashing	ceedee	Infinity-Box	9	01-22-2008 08:16
C62 : Why after flash phone power on but all "?????"	bestncheap	MT-BOX	9	01-25-2006 13:37
7650 "bluetooth sysem error!" after flash	trustunna	Twisterflasher	5	12-09-2004 09:15

11-23-2009, 17:14	#2 (permalink)
haji rahim No Life Poster Join Date: Mar 2008 Location: RMS- CLUB Posts: 3,364 Member: 723410 Status: Offline Sonork: 📱 100.1592732 Thanks Meter: 3,374	Dear bro try to write backup with mexkey... if you have pm or RPL;;;;

11-23-2009, 17:36	#4 (permalink)
msantar Banned Join Date: Dec 2006 Location: inside of infinity best tool Posts: 1,142 Member: 411831 Status: Offline Thanks Meter: 215	there are rpl. i write that but same

11-23-2009, 17:50	#5 (permalink)
Rabatu No Life Poster Join Date: Apr 2009 Posts: 602 Member: 1009679 Status: Offline Thanks Meter: 166	that only means in its restarting state prior to flashing Superdongle Invalid was already there............getz? now you need new rpl since your back-up was already damaged

11-23-2009, 17:50	#6 (permalink)
neilthirumuttam No Life Poster Join Date: Sep 2002 Location: KERALA, india Age: 56 Posts: 1,237 Member: 15903 Status: Offline Sonork: 100.1583162 Thanks Meter: 1,046	which version was the set before flashing ? did u checked with product code or image dl option before flash ?

11-23-2009, 17:56	#7 (permalink)
msantar Banned Join Date: Dec 2006 Location: inside of infinity best tool Posts: 1,142 Member: 411831 Status: Offline Thanks Meter: 215	if i write backup show this RPL: "C:\mobileEx\3.2\data\backup\RPL\BB5_351xxxxxxxxxx x_BACK.rpl" Imei: 3519xxxxxxxxxx Restoring RF/BB DATA from backup ... Updating RF ...OK Updating BB ...OK Updating WARRANTY ...OK Updating PROD ...OK Updating BT ...OK RAP Data : SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x] EM1 ID: 00000295 EM2 ID: 00000B22 PUBLIC ID: 1E80001964497D562064127100B9CED19F42E410 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 NPC verified Ok. Updating CMT NPC ...OK Updating CMT CCC ...OK Updating CMT HWC ...OK Updating PRODUCTCODE (0566806)... OK Updating PSN (DTC186745)... OK Updating HWID (1000)... OK Updating SIMLOCK...OK Trying to update SUPERDONGLE_KEY ...error 0x0 Updating WMDRM_PD...OK Certificate programmed successfully ! Phone Type: RM-436 (Nokia 7210 Supernova) SW Version: V 07.23 17-07-09 RM-436 (c) Nokia Imei plain: 3519xxxxxxxxxx-0 Product Code: 0566806 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 invalid! - WD timer enabled, phone will reboot itself after 3 min. SIMLOCK_TEST passed SECURITY_TEST passed TimeStamp: 2009-07-20T08:46:24Z SW Version: 07.23 Variant Version: 012 ProductProfile: RM436_0566806_07.23_012.spr Simlock: 0566806_simlock.bin Imei net: 351xxxxxxxxxxxx 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

11-23-2009, 18:00	#8 (permalink)
Riteshgpt60 No Life Poster Join Date: Jul 2009 Location: India Posts: 2,857 Member: 1086393 Status: Offline Thanks Meter: 771	You don't need to worry bro- SIMPLE, It was restart problem and now it is restarting only because of SUPERDONGLE KEY INVALID! I can say that it was SUPERDONGLE KEY INVALID! before you flash.If not then you have to prove by posting scanlog before flash. I flash many phones and did'nt ever encounter such kind of problem!

11-24-2009, 19:30	#11 (permalink)
adelkaha25 No Life Poster Join Date: Feb 2009 Location: Algeria-Cne Age: 47 Posts: 1,059 Member: 973866 Status: Offline Sonork: 1603443 Thanks Meter: 297	if the software of MXkey show phone authentificated to superdongle message after writting RPL bakup that mean your superdongle key in this time is correct (RPL backup of mxkey contain simlock data). try to make info after wrriting RPL backup and post log here can you tel us what do you do after writting RPL backup?

11-25-2009, 19:01	#13 (permalink)
Rabatu No Life Poster Join Date: Apr 2009 Posts: 602 Member: 1009679 Status: Offline Thanks Meter: 166	try reset NPC then write your back-up PM then restore your back-up RPL i've been using MXKEY for several months especially in BB5 flashing. Doing some experiment destroying erasing all Flash Data and restoring all again with full success. Mxkey is very reliable when it comes with BB5. imagine again your phone keeps on restarting not because of HW problem but because of SW related problem...something corrupted there in which we never exactly knew which area. so Only possible if it was downgraded things like that.

11-26-2009, 03:13	#15 (permalink)
Riteshgpt60 No Life Poster Join Date: Jul 2009 Location: India Posts: 2,857 Member: 1086393 Status: Offline Thanks Meter: 771	Ok if you are sure ,then try to do what adelkaha25 had said!