Nokia 5300 super dongle corrupted

[Unicom]

Hi, I was trying to fix sd corrupted, and I got this ok(Calculating SUPERDONGLE using security server ...
SERVER->Served by MXKEY - BLADE X at host2, agent version 1.1 revision 0.0

Completed in 6.625 s

RPL saved to "C:\mobileEx\3.4\data\backup\BB5_RM-146_3530950289XXXXX_SD.RPL"
Updating SUPERDONGLE_KEY ...OK)

And after that when I try to super dongle authorization to write pm it showing
(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.00 19-08-08 RM-146 (c) Nokia.

Using cached productData[19600216C7317B5657C6EA7D787B8A9E3F4FB384] ...

Authenticating to SUPERDONGLE using security server ...
Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request)
Please help me to fix.
Thnks

[UNLOCK PARK ® SUPPORT]

Try and try u will done

Br
Mahadi

[jagdish puri]

first open mxkey option ,server . sllect blade server #2 in (slect server )
then do this job .

first backup rpl full
then reset npc
then write good pm file ( you can read it from any working same modle )
then restore imei
then repair SD, Repair simlock, SD AU
after all write pm area 1and 309 only .( not with pm auth )
post result

[nepoleanl]

your solution here

http://forum.gsmhosting.com/vbb/f550...5/#post5890501

[Unicom]

Originally Posted by jagdish puri

first open mxkey option ,server . sllect blade server #2 in (slect server )
then do this job .

first backup rpl full
then reset npc
then write good pm file ( you can read it from any working same modle )
then restore imei
then repair SD, Repair simlock, SD AU
after all write pm area 1and 309 only .( not with pm auth )
post result

Hi, Thanks for the answer, Yes I have done the exact way you said, But when I go to SD AU I am getting the msg: 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-146 (c) Nokia.

Using cached productData[19600216C7317B5657C6EA7D787B8A9E3F4FB384] ...

Authenticating to SUPERDONGLE using security server ...
Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
Wrong response to SD verify request
Please help.
Thnks