3110 SECURITY_TEST failed?

[Nabeel khan]

Can any one help me i have nokia 3110 and i can not solve this problem i do every thing (repair sim lock,spdata,nd pm 1 and 309 with sx4 but same problem(Phone Type: RM-237 (Nokia 3110c)
SW Version: V 07.30 07-05-09 RM-237 (c) Nokia.
Imei plain: 35606103615094-6
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY[MX] seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!


Imei net: 356061036150946
Version: SIMLOCK SERVER VERSION 63
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
)

[shakir hashmi]

try this br.100% work
1 update splock
2 repair sd
3 super sd auth
4 load from file
5 pm 1 to 309
6 writem pm

[Nabeel khan]

i alrady do this my bro

[shakir hashmi]

br. use another pm file and post result

[bipugunjan]

write rpl without npc. like bandchenge rpl then pmm auth 1&9 pm write.I hoppe solved problem 100%.

[Nabeel khan]

thankssssssss sir my problem is solve use modifing pm only 1 and 309

[mahir ashab]

br, scurity test fail. only one method that write modify pm 1 & 309. if not solve, no way. no result if use others way. 100 times tested me. each & every method i already aplied more and more time. but no result. i have one 3110c CONTACT SERVICE FOR SCURITY TEST FAILED.

thanks

[shakir hashmi]

Originally Posted by mahir ashab

br, scurity test fail. only one method that write modify pm 1 & 309. if not solve, no way. no result if use others way. 100 times tested me. each & every method i already aplied more and more time. but no result. i have one 3110c CONTACT SERVICE FOR SCURITY TEST FAILED.

thanks

post ur mx key log here

[dreams_bd]

1. open your backup rpl with notpad
2. COPY HWC ,CCC DATA on working phone and past your backup rpl where HWC,CCC data then write modified rpl
3. update sp data (unlock phone)
if no work
do sx4 write 1-309 field
then scan phone
if no work then unlock
it will be ok

br,
dreams_bd

[md jawad]

Originally Posted by bipugunjan

write rpl without npc. like bandchenge rpl then pmm auth 1&9 pm write.I hoppe solved problem 100%.

where do i get pm plz help

[cellsclinic]

here is pm file get it sir

[md jawad]

Writing PM from Node ...
Section: 1
Warning: failed to write 1 - 0 (114 bytes)
Warning: failed to write 1 - 2 (98 bytes)
Warning: failed to write 1 - 4 (110 bytes)
Warning: failed to write 1 - 6 (98 bytes)
Warning: failed to write 1 - 8 (110 bytes)
Warning: failed to write 1 - 13 (98 bytes)
Warning: failed to write 1 - 16 (86 bytes)
Warning: failed to write 1 - 18 (86 bytes)
Warning: failed to write 1 - 20 (86 bytes)
Warning: failed to write 1 - 25 (4 bytes)
Warning: failed to write 1 - 29 (6 bytes)
Warning: failed to write 1 - 34 (80 bytes)
Section: 309
Warning: failed to write 309 - 0 (4 bytes)
Warning: failed to write 309 - 1 (2 bytes)
Warning: failed to write 309 - 2 (12 bytes)
Warning: failed to write 309 - 4 (12 bytes)
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)
Completed in 1.563 s

[Jayrus]

Originally Posted by Nabeel khan

Can any one help me i have nokia 3110 and i can not solve this problem i do every thing (repair sim lock,spdata,nd pm 1 and 309 with sx4 but same problem(Phone Type: RM-237 (Nokia 3110c)
SW Version: V 07.30 07-05-09 RM-237 (c) Nokia.
Imei plain: 35606103615094-6
Language Pack:
- not available.

SIMLOCK seems to be valid
SUPERDONGLE_KEY[MX] seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST failed!




Imei net: 356061036150946
Version: SIMLOCK SERVER VERSION 63
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
)

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

We solved some bugs on server side at first SX4 Auth when phones had bad PM uploaded (e.g. PM308 from another phone, empty PM308, ...)
Now all SD repair should work well.

Here is general repair procedure.
It will repair any phone (SL1, SL2) with any kind of damaged PM, except phones with RPL NPC damaged (IMEI 123456....).
It will repair ONLY SD (not Simlock) for supported hashes "pure SL3" based phones.

1. write full PM from SAME phone model (not care if contains fields 1, 120, 308, 309)
2. make Simlock RPL repair
3. make SD RPL repair
4. make SUPER SX4 Auth then write PM1 and PM309 from SAME phone model
5. eventualy (if phone had bad RPL written by other people) write RPL CCC, HWC, VARIANT from SAME phone model, can get from here:


RapidShare: 1-CLICK Web hosting - Easy Filehosting

[RACUN DUNIA]

Originally Posted by md jawad

Writing PM from Node ...
Section: 1
Warning: failed to write 1 - 0 (114 bytes)
Warning: failed to write 1 - 2 (98 bytes)
Warning: failed to write 1 - 4 (110 bytes)
Warning: failed to write 1 - 6 (98 bytes)
Warning: failed to write 1 - 8 (110 bytes)
Warning: failed to write 1 - 13 (98 bytes)
Warning: failed to write 1 - 16 (86 bytes)
Warning: failed to write 1 - 18 (86 bytes)
Warning: failed to write 1 - 20 (86 bytes)
Warning: failed to write 1 - 25 (4 bytes)
Warning: failed to write 1 - 29 (6 bytes)
Warning: failed to write 1 - 34 (80 bytes)
Section: 309
Warning: failed to write 309 - 0 (4 bytes)
Warning: failed to write 309 - 1 (2 bytes)
Warning: failed to write 309 - 2 (12 bytes)
Warning: failed to write 309 - 4 (12 bytes)
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)
Completed in 1.563 s

conesion error bro....

[DOSTI]

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.9100(23-12-2010), 1.0.0.15151(24-12-2010)
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 1E30010BC2787E56E7BAC42747F3C47C5C7692B0
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 191EC665DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 1.30.0 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
FlashID0: 0089 8981 - 0000 0000 [Intel NU48F256,256 Mbits] type: NOR,CMT
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo_131.fg [BB5 ALGORITHM] version: 1.31.0 revision: 0.0 size: 0x297E0
Supported 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
CMT PAPUBKEYS HASH: C0E691EA16A7593A9BB28832D7312A39F7ED668D
TransmissionMode: DDR&TX2
Original Imei: 35196303325990
Original Product code: 0581523
Bluetooth ID: 00247D6DA051

Phone Type: RM-237 (Nokia 3110c)
SW Version: V 07.30 07-05-09 RM-237 (c) Nokia.
Imei plain: 35196303325990-8
Product Code: 0514950
Language Pack:
- not available.

SIMLOCK invalid!
SUPERDONGLE_KEY[MX] seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST failed!
SECURITY_TEST passed


Imei net: 351963033259908
Version: SIMLOCK SERVER VERSION 63
Counter: 0/3, 0/10

CONFIG_DATA: FFFFFFFFFFFFFFFF
PROFILE_BITS: FFFFFFFFFFFFFFFF

BLOCK 1: 1=CORRUPTED






than

i try to this

353780005379471
352524003412528
First method:

1 - taking full Backup IMEI & Security -> Backup RPL (All Section)
2 - Full Erase
3 - Full Flash
4 - Restore only NPC Backup Part
5 - Repair SIMlock with MXKey
6 - Repair Superdongle with MXKey
7 - Super SD Auth, and finally write Full PM(without Field 308-120)
(If required Recover Cert)

The second method:

1 - taking full Backup IMEI & Security -> Backup RPL (All Section)
2 - Full Erase
3 - Full Flash
4 - Restore only NPC Backup Part
5 - Lock the by phone by IMEI & Security -> Lock To Provider (MCC+MNC value is not important)
6 - Repair SIMlock with MXKey
7 - Repair Superdongle with MXKey
8 - Super SD Auth, and finally write Full PM(without Field 308-120)
(If required Recover Cert)


Third method:

1 - taking full Backup IMEI & Security -> Backup RPL (All Section)
2 - Erase Eeprom Section: Flashing-> Advance-> GetAddress, Disable Safe Erase. Enable Eeprom Part only, Click Erase.
3 - Locke the phone by IMEI & Security -> Lock To Provider (MCC+MNC value is not important)
4 - Repair SIMlock with MXKey
5 - Repair Superdongle with MXKey
6 - Super SD Auth, and finally write Full PM(without Field 308-120)
[B](If required Recover Cert)
__________________





but problem is same pls help meeeeeeeeeeeee