|
|
 |
|
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please - Click to REGISTER! If you have any problems with the registration process or your account login, please contact contact us . |
| |||||||
| Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source |
 |
| | LinkBack | Thread Tools | Display Modes |
05-30-2010, 04:00
| #1 (permalink) |
| Freak Poster   Join Date: Dec 2009 Location: ifixedcellution.blogspot.com
Posts: 361
Member: 1190236 Status: Offline Sonork: 100.1589642 Thanks Meter: 233 | 7210c cs security test failed hard to revived. . . log's of super sd auth: Code: 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.23 17-07-09 RM-436 (c) Nokia Using cached productData[04100214A53A7D563BADDD5837299291ED38D576] ... Authenticating to SUPERDONGLE using security server ... Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted ! Wrong response to SD verify request |
|
05-30-2010, 04:31
| #2 (permalink) |
| No Life Poster   Join Date: Jan 2008 Location: Kabul Afghanistan
Posts: 1,101
Member: 687312 Status: Offline Thanks Meter: 290 | Yes Mate I also have same problem and waiting for Super SD Auth after SD repair since 2 weeks but don't know why MX-team ignore this problem and don't fix this bugs in new update. WBR |
|
05-30-2010, 05:18
| #4 (permalink) | |
| Freak Poster Join Date: Dec 2009 Location: ifixedcellution.blogspot.com
Posts: 361
Member: 1190236 Status: Offline Sonork: 100.1589642 Thanks Meter: 233 | Quote:
and npc data are all ok. a very weird problem like this it is the bug's of latest update's..? | |
|
05-30-2010, 05:33
| #5 (permalink) | |
| Freak Poster Join Date: Jul 2008 Location: tangub
Posts: 177
Member: 823842 Status: Offline Thanks Meter: 33 | Quote:
im also encountered that same problem.................. | |
|
05-30-2010, 06:03
| #6 (permalink) | |
| Freak Poster Join Date: Jul 2009 Location: INDIA
Posts: 117
Member: 1079615 Status: Offline Thanks Meter: 23 | 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.23 17-07-09 RM-436 (c) Nokia Using cached productData[2380010A2AAF7C56500E7ABF22B6A03E46D1E976] ... Authenticating to SUPERDONGLE using security server ... Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted ! Wrong response to SD verify request today is the 5th day i m also trying continusly but not get success pls help mx team,,, thanks | |
|
05-30-2010, 07:48
| #9 (permalink) |
| Freak Poster Join Date: May 2010 Location: Pakistan Age: 47
Posts: 295
Member: 1295798 Status: Offline Sonork: brista786 Thanks Meter: 97 | use this metohed i hope ur problem will be solved Phone logs when Scanned in Mx-key: Phone Type: RM-240 (Nokia 6500s-1) SW Version: V 10.00 06-03-09 RM-240 (c) Nokia Imei plain: 35765901674649-9 Language Pack: - not available. SIMLOCK invalid! SUPERDONGLE_KEY invalid! - WD timer enabled, phone will reboot itself after 3 min. SIMLOCK_TEST failed! SECURITY_TEST passed SIMLOCK_DATA corrupted! PROCEDURE TO FOLLOW 1.Repair SD 2.SUPER SD Auth 3.PM Write 4.Repair SIMLOCK Step by Step: 1. Repair SD. Under IMEI & Security tab click IMEI Rebuild and click "Repair SD". Wait until mx-key finishes it's job.. Sample Log: Using device: J.A.F, FW ver: 01.B1 Library version: 1.0.0.11985, Date: 03-02-2010 Product: V 10.00 06-03-09 RM-240 (c) Nokia SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0] ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 ROM ID: 273F6D55DFAAF68F Sending SecondaryBoot ...OK Sending PreLoader ...OK Sending CustomLoader ...OK Calculating SUPERDONGLE using security server ... Connecting to server[main.mxkey.biz] ...OK, secure login ... Completed in 4.906 s RPL saved to "C:\mobileEx\3.3\data\backup\BB5_RM-240_357659016746499_SD.RPL" Updating SUPERDONGLE_KEY ...OK After repairing SUPERDONGLE_KEY, SECURITY_TEST has been damaged. see status: Phone Type: RM-240 (Nokia 6500s-1) SW Version: V 10.00 06-03-09 RM-240 (c) Nokia Imei plain: 35765901674649-9 Language Pack: - not available. SIMLOCK invalid! SUPERDONGLE_KEY seems to be valid SIMLOCK_TEST failed! SECURITY_TEST failed! SIMLOCK_DATA corrupted! proceed to next steps to restore SECURITY_TEST. 2. SUPER SD Auth. Under PM tab click "SUPER SD Auth". Again wait for mx-key to finish.. Sample Log: Using device: J.A.F, FW ver: 01.B1 Library version: 1.0.0.11985, Date: 03-02-2010 Product: V 10.00 06-03-09 RM-240 (c) Nokia SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0] ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 ROM ID: 273F6D55DFAAF68F Sending SecondaryBoot ...OK Sending PreLoader ...OK Sending CustomLoader ...OK Restarting phone ... Connecting to server[main.mxkey.biz] ...OK, secure login ... Authenticating to SUPERDONGLE using security server ... SUPERDONGLE authorized ! After the unit has been authorized, you can now write pm fields 1 and 309.. For my case, i use a complete pm file but chose to skip simlock area. 3. Write good pm file. Still under PM tab..Locate "Load from file" then click it.. a folder will pop-up asking you to choose the pm file you would like to write.. pick the file then click "Open". Wait for mx-key to finish. Sample Log: Completed in 7.828 s Writing PM from Node ... Section: 1 - Key: 0, size 114 bytes written. - Key: 2, size 98 bytes written. - Key: 4, size 110 bytes written. - Key: 6, size 98 bytes written. - Key: 8, size 110 bytes written. - Key: 13, size 98 bytes written. - Key: 16, size 98 bytes written. - Key: 18, size 98 bytes written. - Key: 20, size 98 bytes written. - Key: 22, size 16 bytes written. - Key: 23, size 4 bytes written. - Key: 24, size 84 bytes written. - Key: 25, size 4 bytes written. - Key: 26, size 110 bytes written. - Key: 28, size 98 bytes written. - Key: 29, size 10 bytes written. - Key: 31, size 98 bytes written. - Key: 33, size 36 bytes written. - Key: 34, size 80 bytes written. - Key: 40, size 16 bytes written. - Key: 41, size 182 bytes written. - Key: 42, size 4 bytes written. - Key: 43, size 36 bytes written. - Key: 44, size 182 bytes written. Section: 2 - Key: 0, size 448 bytes written. Section: 4 - Key: 1, size 48 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: 1, size 12 bytes written. - Key: 7, 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: 4, size 1 bytes written. - Key: 5, size 6 bytes written. - Key: 6, size 2 bytes written. - Key: 7, size 1 bytes written. - Key: 8, size 1 bytes written. - Key: 9, size 1 bytes written. - Key: 10, size 1 bytes written. - Key: 11, size 1 bytes written. - Key: 12, size 1 bytes written. - Key: 13, size 1 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 4 bytes written. - Key: 66, size 1 bytes written. - Key: 67, 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 16 bytes written. - Key: 72, size 4 bytes written. - Key: 73, size 2 bytes written. - Key: 74, size 13 bytes written. Section: 31 - Key: 4, size 16 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 2050 bytes written. - Key: 1, size 240 bytes written. - Key: 2, size 240 bytes written. - Key: 3, size 1 bytes written. - Key: 4, size 1 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: 12, size 1 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. - Key: 32, size 4 bytes written. - Key: 34, size 4 bytes written. - Key: 57, size 8 bytes written. - Key: 58, size 8 bytes written. - Key: 59, size 8 bytes written. - Key: 60, size 8 bytes written. - Key: 61, size 8 bytes written. - Key: 75, size 8 bytes written. - Key: 76, size 8 bytes written. - Key: 78, size 6144 bytes written. - Key: 79, size 300 bytes written. - Key: 80, size 60 bytes written. - Key: 91, size 3 bytes written. - Key: 92, size 3 bytes written. - Key: 93, size 3 bytes written. - Key: 94, size 3 bytes written. - Key: 95, size 3 bytes written. - Key: 96, size 3 bytes written. - Key: 98, size 4 bytes written. - Key: 99, size 4 bytes written. - Key: 100, size 4 bytes written. - Key: 101, size 4 bytes written. - Key: 102, size 4 bytes written. - Key: 103, size 6 bytes written. - Key: 105, size 4 bytes written. - Key: 106, size 4 bytes written. - Key: 107, size 4 bytes written. - Key: 116, size 120 bytes written. - Key: 118, size 30 bytes written. - Key: 119, size 1 bytes written. - Key: 120, size 8 bytes written. Section: 88 - Key: 0, size 36 bytes written. Section: 96 - Key: 0, size 24 bytes written. Section: 107 - Key: 0, size 21 bytes written. - Key: 1, size 89 bytes written. - Key: 2, size 69 bytes written. - Key: 3, size 70 bytes written. - Key: 26, size 12 bytes written. - 120 skipped Section: 122 - Key: 0, size 2 bytes written. Section: 193 - Key: 2, size 8 bytes written. - Key: 3, size 32 bytes written. - Key: 4, size 32 bytes written. - Key: 9, size 64 bytes written. Section: 208 - Key: 1, size 4 bytes written. Section: 218 - Key: 0, size 2 bytes written. Section: 238 - Key: 1, size 1 bytes written. Section: 309 - Key: 0, size 4 bytes written. - Key: 1, size 2 bytes written. - Key: 2, size 12 bytes written. - Key: 4, size 12 bytes written. - Key: 5, size 12 bytes written. - Key: 7, size 12 bytes written. - Key: 8, size 12 bytes written. - Key: 17, size 12 bytes written. Section: 322 - Key: 0, size 1 bytes written. Section: 334 - Key: 0, size 1 bytes written. Section: 339 - Key: 0, size 511 bytes written. - Key: 1, size 511 bytes written. Section: 341 - Key: 0, size 1 bytes written. - Key: 3, size 4 bytes written. - Key: 4, size 4296 bytes written. Section: 354 - Key: 0, size 3 bytes written. Section: 356 - Key: 0, size 2 bytes written. - Key: 1, size 8 bytes written. Section: 362 - Key: 0, size 1 bytes written. - Key: 1, size 120 bytes written. Completed in 9.594 s after pm write, check the status of the unit.. Phone Type: RM-240 (Nokia 6500s-1) SW Version: V 10.00 06-03-09 RM-240 (c) Nokia Imei plain: 35765901674649-9 Product Code: 0543754 Language Pack: - not available. SIMLOCK invalid! SUPERDONGLE_KEY seems to be valid SIMLOCK_TEST failed! SECURITY_TEST passed SIMLOCK_DATA corrupted! SECURITY_TEST has been restored.. Proceed to next step to repair SIMLOCK. 4.Repair SIMLOCK. Under "IMEI & SECURITY" click Simlock locate and click "Repair SIMLOCK" in Options menu. Also click "Make SIMLOCK RPL" then then click "Update SpLock". Wait for mx-key to finish. Sample Log: Library version: 1.0.0.11985, Date: 03-02-2010 Product: V 10.00 06-03-09 RM-240 (c) Nokia SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0] ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1 ROM ID: 273F6D55DFAAF68F Sending SecondaryBoot ...OK Sending PreLoader ...OK Sending CustomLoader ...OK Calculating SIMLOCK using security server ... Connecting to server[main.mxkey.biz] ...OK, secure login ... Completed in 4.672 s RPL saved to "C:\mobileEx\3.3\data\backup\BB5_RM-240_357659016746499_SIM.RPL" Updating SIMLOCK...OK Reading Simlock info ... Imei net: 357659016746499 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 After all procedure's are done, scan the unit again to check it's status.. Phone Type: RM-240 (Nokia 6500s-1) SW Version: V 10.00 06-03-09 RM-240 (c) Nokia Imei plain: 35765901674649-9 Product Code: 0543754 Language Pack: - not available. SIMLOCK seems to be valid SUPERDONGLE_KEY seems to be valid SIMLOCK_TEST passed SECURITY_TEST passed Imei net: 357659016746499 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 Unit successfully repaired.. thanks to Mx-key team.. |
| The Following User Says Thank You to True Man For This Useful Post: |
|
05-30-2010, 07:53
| #10 (permalink) |
| Freak Poster  Join Date: Nov 2009 Location: INDIA
Posts: 251
Member: 1170625 Status: Offline Sonork: 100.1616527 Thanks Meter: 94 |  server error plz help me epair sd successfull operation but, can't perform super sd auth log's of super sd auth: Code: 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.23 17-07-09 RM-436 (c) Nokia Using cached productData[04100214A53A7D563BADDD5837299291ED38D576] ... Authenticating to SUPERDONGLE using security server ... Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted ! Wrong response to SD verify request mxkey team, pls help. i will try in may more times but server is not ok mxkey team, plz correct our srever prob plz |
|
05-30-2010, 07:57
| #11 (permalink) |
| No Life Poster  Join Date: Apr 2006 Location: INDIA Age: 38
Posts: 5,596
Member: 269044 Status: Offline Sonork: 100.1590584 Thanks Meter: 3,949 | MX-KEY SUPER SX4 AUTH SERVER IS UNDER MAINTENCE. PLS BE PATIENCE IT WILL SOON BE ONLINE AND U CAN DO ALL UR OPERATION. WBR sahil2000ind |
|
05-30-2010, 08:07
| #12 (permalink) | |
| No Life Poster  Join Date: Dec 2007 Location: Bangladesh Age: 41
Posts: 1,657
Member: 648647 Status: Offline Sonork: 100.1603328 Thanks Meter: 967 | Quote:
Super dongle not working pls mx key teammmmmmmmmmmm do some thing. | |
|
| Bookmarks |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| news headlines to gsm phone | mos | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 7 | 05-22-2016 11:42 |
| How to add a language in 51xx/61xx | tati | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 8 | 05-21-2013 19:20 |
| 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 |
| How to upload a new firmware... | Brand | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 8 | 06-08-2012 18:29 |
| Copy from one 6110 to another | Leif Nielsen | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 1 | 06-10-1999 22:36 |
|
|
Linear Mode
