GSM Shop GSM Shop
GSM-Forum  

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 .

Go Back   GSM-Forum > Product Support Sections > No More Supported Solutions (Dead Products) > No More Supported H/W Products > MXKEY (by Alim Hape) > MXKEY Nokia Flasher and Unlocker (by Alim Hape)
Reload this Page nokia n76 sucussfully phonestartup failure solved .security test fail solved
Register FAQDonate Forum Rules Root any Device ★iPhone Unlock★ ★ Direct Codes ★ Direct Unlock Source


Closed Thread
 
LinkBack Thread Tools Display Modes
Old 01-23-2010, 07:39   #1 (permalink)
Freak Poster
 
Join Date: Aug 2008
Posts: 379
Member: 838176
Status: Offline
Thanks Meter: 57
nokia n76 sucussfully phonestartup failure solved .security test fail solved

Phone Type: RM-135 (Nokia N76)
SW Version: V 06wk41v46 06-11-07 RM-135 (c) Nokia
Imei plain: 35395401015579-5
Product Code: 0550409
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!


Imei net: 353954010155795
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: 000000010000022600010006400C192101011103 [RAPIDO3G ver: 1.11]
EM0 ID: 00000295
EM1 ID: 00000B21
PUBLIC ID: 07800008524E0058B945F69E6FAFD9EE44DF2D2F
ASIC MODE ID: 00
ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C
ROM ID: F2C6EBADC86E6189
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 0030 - 0060 0121 [Samsung K5W1G13ACM-DJ60,1 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: 500F1CC61F6C1F570D3EF99F62B9AA86C53B2049
Reading RAP NPC (0x168 bytes)

Begin Certificate Request ...
Connecting to server ...OK, Login ...
Query done with status: OK
Updating PRODUCTCODE (0550414)... OK
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101011103 [RAPIDO3G ver: 1.11]
EM0 ID: 00000295
EM1 ID: 00000B21
PUBLIC ID: 07800008524E0058B945F69E6FAFD9EE44DF2D2F
ASIC MODE ID: 00
ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C
ROM ID: F2C6EBADC86E6189
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 0030 - 0060 0121 [Samsung K5W1G13ACM-DJ60,1 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: 500F1CC61F6C1F570D3EF99F62B9AA86C53B2049
Updating CMT NPC ...OK
Updating CMT CCC ...OK
Updating CMT HWC ...OK
Certificate programmed successfully !

---------------------------


Phone Type: RM-135 (Nokia N76)
SW Version: V 06wk41v46 06-11-07 RM-135 (c) Nokia
Imei plain: 35395401015579-5
Product Code: 0550409
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!


Imei net: 353954010155795
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: 000000010000022600010006400C192101011103 [RAPIDO3G ver: 1.11]
EM0 ID: 00000295
EM1 ID: 00000B21
PUBLIC ID: 07800008524E0058B945F69E6FAFD9EE44DF2D2F
ASIC MODE ID: 00
ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C
ROM ID: F2C6EBADC86E6189
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 0030 - 0060 0121 [Samsung K5W1G13ACM-DJ60,1 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: 500F1CC61F6C1F570D3EF99F62B9AA86C53B2049
Reading RAP NPC (0x168 bytes)

Begin Certificate Request ...
Connecting to server ...OK, Login ...
Query done with status: OK
Updating PRODUCTCODE (0550414)... OK
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101011103 [RAPIDO3G ver: 1.11]
EM0 ID: 00000295
EM1 ID: 00000B21
PUBLIC ID: 07800008524E0058B945F69E6FAFD9EE44DF2D2F
ASIC MODE ID: 00
ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C
ROM ID: F2C6EBADC86E6189
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 0030 - 0060 0121 [Samsung K5W1G13ACM-DJ60,1 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: 500F1CC61F6C1F570D3EF99F62B9AA86C53B2049
Updating CMT NPC ...OK
Updating CMT CCC ...OK
Updating CMT HWC ...OK
Certificate programmed successfully


Phone Type: RM-135 (Nokia N76)
SW Version: V 06wk41v46 06-11-07 RM-135 (c) Nokia
Imei plain: 35395401015579-5
Product Code: 0550414
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST passed


Imei net: 353954010155795
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
 
Old 01-23-2010, 08:24   #2 (permalink)
Junior Member
 
Join Date: Oct 2009
Location: I live vietnam
Age: 35
Posts: 30
Member: 1139204
Status: Offline
Thanks Meter: 4
hello!

I want to information repair n76

thask!!!!!!!!!!!!!!!!!!!!!!
 
Old 01-23-2010, 08:36   #3 (permalink)
Freak Poster
 
armanhosting's Avatar
 
Join Date: Dec 2006
Location: gsmworld of moderetso .
Posts: 368
Member: 410890
Status: Offline
Thanks Meter: 88
so you used the magic button to recover certificate....but you try in 2 times........

you repair it without using pmm auth?????
 
Old 01-23-2010, 09:02   #4 (permalink)
Freak Poster
 
Join Date: Aug 2008
Posts: 379
Member: 838176
Status: Offline
Thanks Meter: 57
yes,without using pmm auth,only one timerecover certificate.
 
Old 06-28-2010, 12:48   #5 (permalink)
Banned
 
Join Date: Dec 2009
Location: india
Posts: 90
Member: 1178099
Status: Offline
Sonork: 143
Thanks Meter: 3
[/I][/B]Writing PM from Node ...
Section: 1
- Key: 0, size 114 bytes written.
- Key: 1, size 4 bytes written.
- Key: 2, size 98 bytes written.
- Key: 4, size 110 bytes written.
- Key: 5, size 4 bytes written.
- Key: 6, size 98 bytes written.
Warning: failed to write 1 - 8 (110 bytes)
- Key: 13, size 98 bytes written.
- Key: 15, size 4 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: 27, size 4 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: 44, size 182 bytes written.
Section: 2
- Key: 0, size 440 bytes written.
Section: 4
- Key: 3, size 10 bytes written.
- Key: 4, size 8 bytes written.
- Key: 5, size 8 bytes written.
- Key: 9, size 5 bytes written.
Section: 8
- Key: 0, size 12 bytes written.
- Key: 1, size 12 bytes written.
- Key: 2, size 128 bytes written.
- Key: 3, size 128 bytes written.
- Key: 4, size 8 bytes written.
- Key: 6, size 4 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 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 1437 bytes written.
Section: 12
- Key: 0, size 102 bytes written.
Section: 31
- Key: 2, size 8 bytes written.
- 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.
- Key: 2, size 24 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.
Section: 117
- Key: 0, size 4 bytes written.
- Key: 1, size 3 bytes written.
- Key: 2, size 6 bytes written.
- Key: 3, size 1 bytes written.
- Key: 4, size 9 bytes written.
- Key: 5, size 10 bytes written.
- Key: 6, size 8 bytes written.
- Key: 8, size 42 bytes written.
- Key: 13, size 3 bytes written.
- Key: 14, size 3 bytes written.
- Key: 19, size 40 bytes written.
Section: 193
- Key: 2, size 8 bytes written.
- Key: 3, size 32 bytes written.
- Key: 4, size 32 bytes written.
- Key: 7, size 1 bytes written.
- 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.
- Key: 2, size 2629 bytes written.
- Key: 3, size 2629 bytes written.
- Key: 4, size 2629 bytes written.
- Key: 5, size 2629 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.
- Key: 22, size 12 bytes written.
Section: 322
- Key: 0, size 1 bytes written.
Section: 334
- Key: 0, size 1 bytes written.
Section: 341
- Key: 0, size 1 bytes written.
- Key: 3, size 4 bytes written.
- Key: 4, size 4402 bytes written.
Section: 354
- Key: 0, size 23 bytes written.
Section: 356
- Key: 0, size 2 bytes written.
- Key: 1, size 8 bytes written.
Completed in 18.875
pls hlp me what is the promblam?
 
Old 06-28-2010, 12:54   #6 (permalink)
Moderator
 
...:::::NP™:::::...'s Avatar
 
Join Date: Nov 2009
Location: €urope
Age: 41
Posts: 11,041
Member: 1162626
Status: Offline
Sonork: 100.1591727 QQ:2337938173
Thanks Meter: 11,110
Which Mx-key Server is Stablise Connection is ok. Only that time is Possible Pm Authoriser , Super Sd Authoriser is Success Full.............
 
Old 06-28-2010, 13:00   #7 (permalink)
Banned
 
Join Date: Dec 2009
Location: india
Posts: 90
Member: 1178099
Status: Offline
Sonork: 143
Thanks Meter: 3
Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8929(24-06-2010), 1.0.0.14574(24-06-2010)
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101011103 [RAPIDO3G ver: 1.11]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 1970000DB8540058A3B9C54C8B1E72184601E235
ASIC MODE ID: 00
ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C
ROM ID: F2C6EBADC86E6189
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 0030 - 0060 0121 [Samsung K5W1G13ACM-DJ60,1 Gbits] type: MuxOneNAND,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
TransmissionMode: 16Bit
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: 500F1CC61F6C1F570D3EF99F62B9AA86C53B2049
TransmissionMode: DDR&TX2
Original Imei: 35626201113967
Original Product code: 0543089
Bluetooth ID: 001BAFA0486F

Phone Type: RM-135 (Nokia N76)
SW Version: V 06wk41v46 06-11-07 RM-135 (c) Nokia
Imei plain: 35626201113967-8
Product Code: 0550409
Language Pack:
- not available.

SIMLOCK invalid!
SUPERDONGLE_KEY[MX] seems to be valid
WMDRM_PD seems to be valid


SIMLOCK_DATA corrupted!

what i can do sr pls help me
 
Old 02-14-2011, 06:55   #8 (permalink)
No Life Poster
 
MUTUAL's Avatar
 
Join Date: Jul 2005
Location: Auckland
Posts: 4,547
Member: 160928
Status: Offline
Thanks Meter: 338
Quote:
Originally Posted by manish_jain View Post
Phone Type: RM-135 (Nokia N76)
SW Version: V 06wk41v46 06-11-07 RM-135 (c) Nokia
Imei plain: 35395401015579-5
Product Code: 0550409
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!


Imei net: 353954010155795
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: 000000010000022600010006400C192101011103 [RAPIDO3G ver: 1.11]
EM0 ID: 00000295
EM1 ID: 00000B21
PUBLIC ID: 07800008524E0058B945F69E6FAFD9EE44DF2D2F
ASIC MODE ID: 00
ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C
ROM ID: F2C6EBADC86E6189
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 0030 - 0060 0121 [Samsung K5W1G13ACM-DJ60,1 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: 500F1CC61F6C1F570D3EF99F62B9AA86C53B2049
Reading RAP NPC (0x168 bytes)

Begin Certificate Request ...
Connecting to server ...OK, Login ...
Query done with status: OK
Updating PRODUCTCODE (0550414)... OK
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101011103 [RAPIDO3G ver: 1.11]
EM0 ID: 00000295
EM1 ID: 00000B21
PUBLIC ID: 07800008524E0058B945F69E6FAFD9EE44DF2D2F
ASIC MODE ID: 00
ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C
ROM ID: F2C6EBADC86E6189
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 0030 - 0060 0121 [Samsung K5W1G13ACM-DJ60,1 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: 500F1CC61F6C1F570D3EF99F62B9AA86C53B2049
Updating CMT NPC ...OK
Updating CMT CCC ...OK
Updating CMT HWC ...OK
Certificate programmed successfully !

---------------------------


Phone Type: RM-135 (Nokia N76)
SW Version: V 06wk41v46 06-11-07 RM-135 (c) Nokia
Imei plain: 35395401015579-5
Product Code: 0550409
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!


Imei net: 353954010155795
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: 000000010000022600010006400C192101011103 [RAPIDO3G ver: 1.11]
EM0 ID: 00000295
EM1 ID: 00000B21
PUBLIC ID: 07800008524E0058B945F69E6FAFD9EE44DF2D2F
ASIC MODE ID: 00
ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C
ROM ID: F2C6EBADC86E6189
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 0030 - 0060 0121 [Samsung K5W1G13ACM-DJ60,1 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: 500F1CC61F6C1F570D3EF99F62B9AA86C53B2049
Reading RAP NPC (0x168 bytes)

Begin Certificate Request ...
Connecting to server ...OK, Login ...
Query done with status: OK
Updating PRODUCTCODE (0550414)... OK
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101011103 [RAPIDO3G ver: 1.11]
EM0 ID: 00000295
EM1 ID: 00000B21
PUBLIC ID: 07800008524E0058B945F69E6FAFD9EE44DF2D2F
ASIC MODE ID: 00
ROOT KEY HASH: 9A28E119033B91D14D22838C86D0D53C
ROM ID: F2C6EBADC86E6189
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 0030 - 0060 0121 [Samsung K5W1G13ACM-DJ60,1 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: 500F1CC61F6C1F570D3EF99F62B9AA86C53B2049
Updating CMT NPC ...OK
Updating CMT CCC ...OK
Updating CMT HWC ...OK
Certificate programmed successfully


Phone Type: RM-135 (Nokia N76)
SW Version: V 06wk41v46 06-11-07 RM-135 (c) Nokia
Imei plain: 35395401015579-5
Product Code: 0550414
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST passed


Imei net: 353954010155795
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
salam
can u plz explain me how u fix ur phone cuz i can not able to fix phone strat up failed if u can expalin me step by step i will be really thank ful
 
Closed Thread

Bookmarks

« Previous Thread | Next Thread »

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Similar Threads
Thread Thread Starter Forum Replies Last Post
3120c rm-346 "CS" security test failed [solved (server update)] i-Fixed MXKEY Nokia Flasher and Unlocker (by Alim Hape) 12 03-11-2011 15:02
mxkey can't solve security-test failed. mobilezone1997 MXKEY Nokia Flasher and Unlocker (by Alim Hape) 6 11-08-2010 14:53
How can i solve Security Test Fail, after unlock by Mx-key powerplay83 MXKEY Nokia Flasher and Unlocker (by Alim Hape) 9 03-25-2010 14:39
Help with Nokia 3500 with security test failed? [ Solved ] geovanny78 Cyclonebox 2 02-18-2010 00:27
7210c CONTACT SAERVICE security test failed [ Solved ] jermaineyork Cyclonebox 4 02-04-2010 06:35

 



All times are GMT +1. The time now is 17:56.

Contact Us - GSM-Forum - Archive - Top


Powered by Searchlight © 2024 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -
Page generated in 0.26145 seconds with 9 queries

SEO by vBSEO