|
|
 |
|
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 |
02-08-2010, 11:51
| #1 (permalink) | |||
| No Life Poster   Join Date: Oct 2005 Location: Ubá--Brazil Age: 34
Posts: 916
Member: 194078 Status: Offline Sonork: no have Thanks Meter: 209  | E63-RM450 SECURITY_TEST failed! Even with these various server updates the MXkey so far not managed to solve my problem. I have written a full PM, only the area 1 and 309, as did also Writing HWC (Hardware) Certificate and CCC (Common Certification Certificate) and also without success! go down the logs of the device and some prints LOG: Quote:
Quote:
Quote:
Last edited by daroas; 02-08-2010 at 11:56. Reason: Update | |||
| The Following User Says Thank You to daroas For This Useful Post: |
|
02-09-2010, 11:07
| #2 (permalink) | |
| No Life Poster  Join Date: Feb 2005 Location: AD
Posts: 4,665
Member: 976728 Status: Offline Sonork: 1589709 Thanks Meter: 4,775 | there is 3 ways to repair that 1.[MXKEY - INFO] !!! NEW magic button inside mxkey !!! 2.Just in case if Recovery via Server doesn't work....... 3.[MXKEY - SERVER UPDATE] Solved "SECURITY_TEST failed!" after SD repair on PM auth use "Super SD Auth" Failed write HWC Quote:
ex : Code: [CERT_PROG_DATA_OUT_CMT] CCC_DATA_1=4343434302004150010000009138E0949B95CC491B5033000AAA9C00000060010000000080827947 CCC_DATA_2=00000000000000000000000000000000000000000000000000000000000000003035383237393543 CCC_DATA_3=803800470000000000000000030000000F0000008100000000000000000000000000000000000000 CCC_DATA_4=00000000000000000000000000000000000000000000000000000000000000000000000000000000 CCC_DATA_5=00000000000000000000000000000000000000000000000000000000000000000000000000000000 CCC_DATA_6=0000000000000000000000000000000000000000000000006CF146355A227E59DA0576F0B632FF5E CCC_DATA_7=C43B78757EB5006482AA42C7BE4BE334A881630075A32EE42B0FC9E3E409216E1B4E995841DB59C1 CCC_DATA_8=D64FC7CE33283AEC9AB63423FB806C38EA5E6216CA455A6F098E7BDD3E5ABCBC165B4161941FA3B5 CCC_DATA_9=F47BDA0E33495A2BA6CBC683B60264D7FA16160A659C0E4312627D1752C1FC93FFFFFFFFFFFFFFFF CCC_DATA_10=FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF CCC_DATA_11=FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF CCC_DATA_12=FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF CCC_DATA_13=FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF HWC_DATA_1=43485743050041500100000006120298F412D2490B890400646F7242000000000000000000000000 HWC_DATA_2=000000009B95CC490A100209DD750052013ADE0055F5D81C2D8D942F303538323739354300000000 HWC_DATA_3=000000007A46CC58ED5C646B513264D61923938D852EBCF635A52580C0B550256351A133C064D29C HWC_DATA_4=04F97268ED2AE83E5745B180BE374E0BFE9322D947AF6CA18D5BE8FD7B7144532C9FA3A0D8014EEC HWC_DATA_5=A6C3948ED5F2704B7189C7C4E427B44B28EA0230DD31C8B19412E23279B600CD4ED6407A2361431E HWC_DATA_6=96B033E4784AB192DFC2ACACFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF HWC_DATA_7=FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF Code: [CERT_PROG_DATA_OUT_CMT] CCC_DATA_1=4343434302004150010000009138E0949B95CC491B5033000AAA9C00000060010000000080827947 CCC_DATA_2=00000000000000000000000000000000000000000000000000000000000000003035383237393543 CCC_DATA_3=803800470000000000000000030000000F0000008100000000000000000000000000000000000000 CCC_DATA_4=00000000000000000000000000000000000000000000000000000000000000000000000000000000 CCC_DATA_5=00000000000000000000000000000000000000000000000000000000000000000000000000000000 CCC_DATA_6=0000000000000000000000000000000000000000000000006CF146355A227E59DA0576F0B632FF5E CCC_DATA_7=C43B78757EB5006482AA42C7BE4BE334A881630075A32EE42B0FC9E3E409216E1B4E995841DB59C1 CCC_DATA_8=D64FC7CE33283AEC9AB63423FB806C38EA5E6216CA455A6F098E7BDD3E5ABCBC165B4161941FA3B5 CCC_DATA_9=F47BDA0E33495A2BA6CBC683B60264D7FA16160A659C0E4312627D1752C1FC93FFFFFFFFFFFFFFFF HWC_DATA_1=43485743050041500100000006120298F412D2490B890400646F7242000000000000000000000000 HWC_DATA_2=000000009B95CC490A100209DD750052013ADE0055F5D81C2D8D942F303538323739354300000000 HWC_DATA_3=000000007A46CC58ED5C646B513264D61923938D852EBCF635A52580C0B550256351A133C064D29C HWC_DATA_4=04F97268ED2AE83E5745B180BE374E0BFE9322D947AF6CA18D5BE8FD7B7144532C9FA3A0D8014EEC HWC_DATA_5=A6C3948ED5F2704B7189C7C4E427B44B28EA0230DD31C8B19412E23279B600CD4ED6407A2361431E HWC_DATA_6=96B033E4784AB192DFC2ACACFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF br, | |
|
02-09-2010, 17:23
| #3 (permalink) |
| No Life Poster Join Date: Oct 2005 Location: Ubá--Brazil Age: 34
Posts: 916
Member: 194078 Status: Offline Sonork: no have Thanks Meter: 209 | Option 1: Hi,after click in Recover CERT have this log: RAP Data : SYSTEM ASIC ID: 000000010000022600010006400C192101031103 [RAPIDO3G ver: 1.13] EM0 ID: 00000296 EM1 ID: 00000B22 PUBLIC ID: 07900109167E0052E3C949DB323E622E40506345 ASIC MODE ID: 00 ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C ROM ID: 4B9B75103E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 1.37.1 revision: 0.0 size: 0x3B80 Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105 FlashID0: 00EC 0040 - 0080 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: ONENAND,RAP ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 ExtDEVC: FFFF 0000 - 0000 0000 Algorithm: RAPIDOv11_algo.fg [XSR 1.5] version: 1.40.0 revision: 0.0 size: 0x27520 Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105 RAP PAPUBKEYS HASH: D9C25399C696B8549EDCDB1497A950B3A20DDFB6 Reading RAP NPC (0x190 bytes) Begin Certificate Request ... Connecting to server ...OK, Login ... ERROR: No certificate found in the database ! ----------------------------------------------- After click in BB5 Cert Validation: RAP Data : SYSTEM ASIC ID: 000000010000022600010006400C192101031103 [RAPIDO3G ver: 1.13] EM0 ID: 00000296 EM1 ID: 00000B22 PUBLIC ID: 07900109167E0052E3C949DB323E622E40506345 ASIC MODE ID: 00 ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C ROM ID: 4B9B75103E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 1.37.1 revision: 0.0 size: 0x3B80 Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105 FlashID0: 00EC 0040 - 0080 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: ONENAND,RAP ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 ExtDEVC: FFFF 0000 - 0000 0000 Algorithm: RAPIDOv11_algo.fg [XSR 1.5] version: 1.40.0 revision: 0.0 size: 0x27520 Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105 RAP PAPUBKEYS HASH: D9C25399C696B8549EDCDB1497A950B3A20DDFB6 Reading RAP NPC (0x190 bytes) Original Product Code: 0578484 Reading RAP VARIANT (0x0 bytes) Reading RAP CCC (0x160 bytes) Product Code: 0582795 Product Code missmatch ! Reading RAP HWC (0xD4 bytes) Product Code: 0578484 HWC seems to be valid --------------------------------------------- Options 2: After Click in BB5 Secure Storage Validation : SIMLOCK seems to be valid SUPERDONGLE_KEY seems to be valid SIMLOCK_TEST passed SECURITY_TEST failed! ------------------------ After click in BB5 Certivicate Validation again: RAP Data : SYSTEM ASIC ID: 000000010000022600010006400C192101031103 [RAPIDO3G ver: 1.13] EM0 ID: 00000296 EM1 ID: 00000B22 PUBLIC ID: 07900109167E0052E3C949DB323E622E40506345 ASIC MODE ID: 00 ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C ROM ID: 4B9B75103E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 1.37.1 revision: 0.0 size: 0x3B80 Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105 FlashID0: 00EC 0040 - 0080 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: ONENAND,RAP ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 ExtDEVC: FFFF 0000 - 0000 0000 Algorithm: RAPIDOv11_algo.fg [XSR 1.5] version: 1.40.0 revision: 0.0 size: 0x27520 Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105 RAP PAPUBKEYS HASH: D9C25399C696B8549EDCDB1497A950B3A20DDFB6 Reading RAP NPC (0x190 bytes) Original Product Code: 0578484 Reading RAP VARIANT (0x0 bytes) Reading RAP CCC (0x160 bytes) Product Code: 0582795 Product Code missmatch ! Reading RAP HWC (0xD4 bytes) Product Code: 0578484 HWC seems to be valid ----------------------------- After click in Recover CERT again: RAP Data : SYSTEM ASIC ID: 000000010000022600010006400C192101031103 [RAPIDO3G ver: 1.13] EM0 ID: 00000296 EM1 ID: 00000B22 PUBLIC ID: 07900109167E0052E3C949DB323E622E40506345 ASIC MODE ID: 00 ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C ROM ID: 4B9B75103E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 1.37.1 revision: 0.0 size: 0x3B80 Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105 FlashID0: 00EC 0040 - 0080 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: ONENAND,RAP ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 ExtDEVC: FFFF 0000 - 0000 0000 Algorithm: RAPIDOv11_algo.fg [XSR 1.5] version: 1.40.0 revision: 0.0 size: 0x27520 Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105 RAP PAPUBKEYS HASH: D9C25399C696B8549EDCDB1497A950B3A20DDFB6 Reading RAP NPC (0x190 bytes) Begin Certificate Request ... Connecting to server ...OK, Login ... ERROR: No certificate found in the database ! ------------------------------- After SX4 On Line-PM AUTH: 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 189.107.147.205 Bad phones ack, probably SUPERDONGLE_KEY corrupted ! Wrong response to SD verify request -------------------------------------- 3 option: The third choice was made when it came out this update on the server, but also without success! I'm not programad, but I believe the only way to solve this problem will be to add the E63 RM-450 was added as other models in the server upgrade as this link If possible add this model and the reference (RM450) to see if that solves my problem. I'm having a bit of urgency. If possible help me! Very tankhs!! |
| The Following User Says Thank You to daroas For This Useful Post: |
|
02-09-2010, 17:33
| #4 (permalink) | |
| No Life Poster Join Date: Oct 2005 Location: Ubá--Brazil Age: 34
Posts: 916
Member: 194078 Status: Offline Sonork: no have Thanks Meter: 209 | others log's: After click in Super SD Auth and write Full PM: Using device: UFS_USB V2.8 (c) SarasSoft 2007. Library version: 1.0.0.11985, Date: 03-02-2010 Product: V ICPR71_08w44.1 30-10-08 RM-450 (c) Nokia ApeCoreSw: 100.21.110 SYSTEM ASIC ID: 000000010000022600010006400C192101031103 [RAPIDO3G ver: 1.13] ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C ROM ID: 4B9B75103E691FF8 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  !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 80 bytes written. - Key: 3, size 10 bytes written. - Key: 4, size 8 bytes written. - Key: 5, size 8 bytes written. - Key: 9, size 5 bytes written. - Key: 26, size 132 bytes written. - Key: 28, size 2 bytes written. Section: 8 - Key: 0, size 12 bytes written. - Key: 1, size 12 bytes written. Warning: failed to write 8 - 2 (128 bytes) Warning: failed to write 8 - 3 (128 bytes) - Key: 4, size 8 bytes written. - Key: 6, size 4 bytes written. - Key: 7, size 8 bytes written. - Key: 8, size 8 bytes written. - Key: 9, size 16 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 1 bytes written. - Key: 7, size 2 bytes written. - Key: 8, size 2 bytes written. - Key: 9, size 2 bytes written. - Key: 10, size 2 bytes written. - Key: 11, size 2 bytes written. - Key: 12, size 1 bytes written. - Key: 13, size 1 bytes written. - Key: 14, size 1 bytes written. - Key: 15, size 1 bytes written. - Key: 16, size 1 bytes written. - Key: 17, size 1 bytes written. - Key: 18, size 1 bytes written. - Key: 19, size 2 bytes written. - Key: 20, size 2 bytes written. - Key: 21, size 1 bytes written. - Key: 22, size 1 bytes written. - Key: 23, size 4 bytes written. - Key: 24, size 4 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 1 bytes written. - Key: 30, size 1 bytes written. - Key: 31, size 1 bytes written. - Key: 32, size 1 bytes written. - Key: 33, size 1 bytes written. - Key: 34, size 1 bytes written. - Key: 35, size 1 bytes written. - Key: 36, size 1 bytes written. - Key: 37, size 1 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 4 bytes written. - Key: 44, size 4 bytes written. - Key: 45, size 4 bytes written. - Key: 46, size 1 bytes written. - Key: 47, size 16 bytes written. - Key: 48, size 2 bytes written. - Key: 49, size 2 bytes written. - Key: 50, size 20 bytes written. - Key: 51, size 10 bytes written. - Key: 52, size 2 bytes written. - Key: 53, size 20 bytes written. - Key: 54, size 10 bytes written. - Key: 55, size 1 bytes written. - Key: 56, size 1 bytes written. - Key: 57, size 1 bytes written. - Key: 58, size 1 bytes written. - Key: 59, size 1 bytes written. - Key: 60, size 1 bytes written. - Key: 61, size 1 bytes written. - Key: 62, size 1 bytes written. - Key: 63, size 1 bytes written. - Key: 64, size 1 bytes written. - Key: 65, size 1 bytes written. - Key: 66, size 32 bytes written. - Key: 67, size 32 bytes written. - Key: 68, size 2 bytes written. - Key: 69, size 2 bytes written. - Key: 70, size 2 bytes written. - Key: 71, size 2 bytes written. - Key: 72, size 2 bytes written. - Key: 73, size 2 bytes written. - Key: 74, size 2 bytes written. - Key: 75, size 2 bytes written. - Key: 76, size 2 bytes written. - Key: 77, size 2 bytes written. - Key: 78, size 2 bytes written. - Key: 79, size 2 bytes written. - Key: 80, size 2 bytes written. - Key: 81, size 2 bytes written. - Key: 82, size 2 bytes written. - Key: 83, size 2 bytes written. - Key: 84, size 2 bytes written. - Key: 85, size 2 bytes written. - Key: 86, size 2 bytes written. - Key: 87, size 2 bytes written. - Key: 88, size 2 bytes written. - Key: 89, size 2 bytes written. - Key: 90, size 2 bytes written. - Key: 91, size 2 bytes written. - Key: 92, size 2 bytes written. - Key: 93, size 2 bytes written. - Key: 94, size 2 bytes written. - Key: 95, size 2 bytes written. - Key: 96, size 2 bytes written. - Key: 97, size 2 bytes written. - Key: 98, size 2 bytes written. - Key: 99, size 2 bytes written. - Key: 100, size 2 bytes written. - Key: 101, size 2 bytes written. - Key: 102, size 2 bytes written. - Key: 103, size 2 bytes written. - Key: 104, size 2 bytes written. - Key: 105, size 2 bytes written. - Key: 106, size 2 bytes written. - Key: 107, size 2 bytes written. - Key: 108, size 2 bytes written. - Key: 109, size 2 bytes written. - Key: 110, size 2 bytes written. - Key: 111, size 2 bytes written. - Key: 112, size 2 bytes written. - Key: 113, size 2 bytes written. - Key: 114, size 2 bytes written. - Key: 115, size 2 bytes written. - Key: 116, size 4 bytes written. - Key: 117, size 4 bytes written. - Key: 118, size 1 bytes written. - Key: 119, size 4 bytes written. - Key: 120, size 4 bytes written. - Key: 121, size 4 bytes written. - Key: 122, size 4 bytes written. - Key: 123, size 16 bytes written. - Key: 124, size 4 bytes written. - Key: 125, size 2 bytes written. - Key: 126, size 2 bytes written. - Key: 127, size 1436 bytes written. Section: 12 - Key: 0, size 102 bytes written. Section: 26 - Key: 0, size 16 bytes written. - Key: 1, size 68 bytes written. Section: 29 - Key: 2, size 8 bytes written. Section: 31 - Key: 4, size 20 bytes written. Section: 44 - Key: 0, size 1 bytes written. Section: 50 - Key: 0, size 2 bytes written. Section: 54 - Key: 0, size 2 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 79 bytes written. - Key: 2, size 79 bytes written. - Key: 3, size 70 bytes written. - Key: 25, size 132 bytes written. - Key: 26, size 12 bytes written. Section: 117 - Key: 5, size 10 bytes written. - Key: 6, size 8 bytes written. - Key: 8, size 42 bytes written. - 120 skipped Section: 193 - Key: 2, size 8 bytes written. - Key: 3, size 32 bytes written. Warning: failed to write 193 - 4 (32 bytes) - Key: 9, size 64 bytes written. Section: 208 - Key: 1, size 4 bytes written. Section: 217 - Key: 0, size 32 bytes written. Section: 239 - Key: 0, size 2 bytes written. - Key: 1, size 2629 bytes written. - 308 skipped 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. Warning: failed to write 309 - 5 (12 bytes) Warning: failed to write 309 - 7 (12 bytes) Warning: failed to write 309 - 8 (12 bytes) Warning: failed to write 309 - 17 (12 bytes) Warning: failed to write 309 - 22 (12 bytes) Section: 313 Warning: failed to write 313 - 0 (615 bytes) Section: 322 Warning: failed to write 322 - 0 (1 bytes) Section: 334 Warning: failed to write 334 - 0 (1 bytes) Section: 341 Warning: failed to write 341 - 0 (1 bytes) Warning: failed to write 341 - 3 (4 bytes) Warning: failed to write 341 - 4 (4514 bytes) Section: 354 Warning: failed to write 354 - 0 (18 bytes) Section: 356 Warning: failed to write 356 - 0 (2 bytes) Warning: failed to write 356 - 1 (8 bytes) Completed in 45.438 s And writhe the PM 1 and 309: 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. - 120 skipped - 308 skipped 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. - Key: 22, size 12 bytes written. Completed in 15.422 s The archive.rpl has the HWC: Quote:
| |
|
02-10-2010, 22:00
| #7 (permalink) |
| Insane Poster  Join Date: Aug 2005 Age: 52
Posts: 64
Member: 172811 Status: Offline Thanks Meter: 135 | i have the same problem as yours! and i worked 3 days to solve it. Phone Type: RM-450 (Nokia E63) SW Version: V ICPR71_09w22 29-05-09 RM-450 (c) Nokia Imei plain: 35931802129495-7 Product Code: 0578484 ApeCoreSw: 200.21.012 ApeVariant: 200.21.012, ApeTest: RM437ENO874571920.a01 Language Pack: - not available. SIMLOCK seems to be valid SUPERDONGLE_KEY seems to be valid SIMLOCK_TEST passed SECURITY_TEST passed Imei net: 359318021294957 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 RAP Data : SYSTEM ASIC ID: 000000010000022600010006400C192101031103 [RAPIDO3G ver: 1.13] EM0 ID: 00000296 EM1 ID: 00000B22 PUBLIC ID: 10300210DB878B520C13910807BFDB0B3FD33F32 ASIC MODE ID: 00 ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C ROM ID: 4B9B75103E691FF8 SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 1.37.1 revision: 0.0 size: 0x3B80 Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105 FlashID0: 00EC 0040 - 0080 0121 [Samsung 2Gb DDP OneNAND,2 Gbits] type: ONENAND,RAP ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000 ExtDEVC: FFFF 0000 - 0000 0000 Algorithm: RAPIDOv11_algo.fg [XSR 1.5] version: 1.40.0 revision: 0.0 size: 0x27520 Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105 RAP PAPUBKEYS HASH: D9C25399C696B8549EDCDB1497A950B3A20DDFB6 Reading RAP NPC (0x190 bytes) Original Product Code: 0575296 Reading RAP VARIANT (0x0 bytes) Reading RAP CCC (0x160 bytes) Product Code: 0575296 CCC seems to be valid Reading RAP HWC (0xD4 bytes) Product Code: 0575296 HWC seems to be valid it is the result now after the repair (i could not post the error after it work fine now cause i did not copy it) the chance is we have the same productcode and the same error ,but i have few backup before it get test failed. just backup rpl ccc and another rpl hwc. replace my ccc data with yours . CCC_DATA_1=4343434302004150010000009138E0942057784 9DB1F91000AAA9C00000060010000000000F37947 CCC_DATA_2=000000000000000000000000000000000000000 00000000000000000000000003035373532393643 CCC_DATA_3=F09A00470000000000000000030000000F00000 01100000000000000000000000000000000000000 CCC_DATA_4=000000000000000000000000000000000000000 00000000000000000000000000000000000000000 CCC_DATA_5=000000000000000000000000000000000000000 00000000000000000000000000000000000000000 CCC_DATA_6=000000000000000000000000000000000000000 000000000009189DE34127C3336EA288D0202C0FC CCC_DATA_7=27979BCF8BC71D77917978460319CADB8AFEF16 29D76C54DA27A3D2C6644237348B620D30DC42F85 CCC_DATA_8=D9476859E8CF453276DD9DC1A1F7AFBF36705A3 59FE66FB4299E741262FFBA0A05945382F2DD9746 CCC_DATA_9=E35921A0F3606A110D63261BB88E64B2F3C9D7C FC5708287E851AF6D6E127209 and hwc data with yours . HWC_DATA_1=434857430500415001000000542202982D37DD4 A9A8E0200646F7242000000000000000000000000 HWC_DATA_2=000000000000000010300210DB878B520C13910 807BFDB0B3FD33F32303537353239364300000000 HWC_DATA_3=000000000A25C1899FBA09E38CB370DF08602FA 9B4CCDD65C11DA53DFAF7C91E2B081C38909B7F40 HWC_DATA_4=3E5962525ABA48F01E38F935862D4002CC9C559 B12728A8DC939FACD2E4ABD9AFBE2A499F7631AF7 HWC_DATA_5=3C9A1F5556C82640419BCB399ED88644B46DB3C EF9170AB13EEEA05F26E44A4DD604DABCF89B2DE3 HWC_DATA_6=D0F14691FDA56A359542C0DC .. work fine for me. |
| The Following 3 Users Say Thank You to woolfgang For This Useful Post: |
|
02-21-2010, 11:22
| #9 (permalink) | |
| No Life Poster  Join Date: Jun 2006 Location: Bangladesh
Posts: 2,545
Member: 303373 Status: Offline Sonork: 100.1584377 Thanks Meter: 1,241 | Quote:
| |
| The Following 3 Users Say Thank You to ashraf_bcs For This Useful Post: |
|
05-29-2010, 07:46
| #10 (permalink) |
| Registered User Join Date: Feb 2005 Location: Turkiye :islam
Posts: 2,911
Member: 115596 Status: Offline Sonork: [email protected] Thanks Meter: 1,127 | here is this................. RM-450.pm here is this................. RM-450.pm  |
|
05-29-2010, 08:42
| #11 (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.. |
|
05-30-2010, 06:30
| #12 (permalink) | |
| Insane Poster Join Date: Jan 2003 Location: semarang Age: 46
Posts: 89
Member: 20038 Status: Offline Thanks Meter: 19 |  Quote:
tested and my phone work again... | |
|
| Bookmarks |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| E63-3 RM-450 security_test failed | fernandesx | MXKEY Nokia Flasher and Unlocker (by Alim Hape) | 0 | 02-06-2010 16:59 |
| Any Buddy repair SIMLOCK invalid!, SIMLOCK_TEST failed! or SECURITY_TEST failed! | mohit_kripalu01 | MXKEY Nokia Flasher and Unlocker (by Alim Hape) | 2 | 02-06-2010 11:36 |
| SECURITY_TEST failed!" and "warning: SD authorized but verify failed solution | ..::Rizwan::.. | MXKEY Nokia Flasher and Unlocker (by Alim Hape) | 2 | 02-03-2010 15:58 |
| SIMLOCK invalid!, SIMLOCK_TEST failed!, SECURITY_TEST failed! | Raven21 | MXKEY Nokia Flasher and Unlocker (by Alim Hape) | 7 | 01-27-2010 08:15 |
|
|
Linear Mode
