3110c update simlock error need soluation

[naushad09]

3110 FLASHING LOG.......


RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 14B002105E9B7B56C6DEA975FE77BCB75F011CA6
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 RAP 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,RAP
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 RAP 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
RAP PAPUBKEYS HASH: C0E691EA16A7593A9BB28832D7312A39F7ED668D
TransmissionMode: DDR&TX2
Original Imei: 35683302886672
Original Product code: 0550573
Bluetooth ID: 0022FDF86C8F

Phone Type: RM-237 (Nokia 3110c)
SW Version: V 07.21 05-11-08 RM-237 (c) Nokia.
Imei plain: 35683302886672-5
Product Code: 0550573
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: 356833028866725
Version: SIMLOCK SERVER VERSION 63
Counter: 0/3, 0/10

CONFIG_DATA: FFFFFFFFFFFFFFFF
PROFILE_BITS: FFFFFFFFFFFFFFFF

BLOCK 1: 1=CORRUPTED


PLZ HELP ME URGENT

[shashankmobile]

Repair sd > Update Simlock > write pm 1 or 309 area by pm auth.
Simple.






Br.
Shashank

[naushad09]

REPAIER SD...........LOG

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)

Product: V 07.21 05-11-08 RM-237 (c) Nokia.

Using cached productData[14B002105E9B7B56C6DEA975FE77BCB75F011CA6] ...

Calculating SUPERDONGLE using security server ...
SERVER->Served by MXKEY - BLADE X at host1, agent version 1.1 revision 0.1
[CR2]BB5 remaining credit: 18

Completed in 2.844 s

RPL saved to "C:\mobileEx\3.4\data\backup\BB5_RM-237_356833028866725_SD.RPL"
Updating SUPERDONGLE_KEY ...OK



.................................


REPAIER SIMLOCK....LOG


mei net: 356833028866725
Version: SIMLOCK SERVER VERSION 63
Counter: 0/3, 0/10

CONFIG_DATA: FFFFFFFFFFFFFFFF
PROFILE_BITS: FFFFFFFFFFFFFFFF

BLOCK 1: 1=CORRUPTED

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)

Product: V 07.21 05-11-08 RM-237 (c) Nokia.

Using cached productData[14B002105E9B7B56C6DEA975FE77BCB75F011CA6] ...

Calculating SIMLOCK using security server ...
SERVER->Served by MXKEY - BLADE X at host1, agent version 1.1 revision 0.1
[CR2]BB5 remaining credit: 17

Completed in 3.781 s

RPL saved to "C:\mobileEx\3.4\data\backup\BB5_RM-237_356833028866725_SIM.RPL"
Updating SIMLOCK...error 0x1

Reading Simlock info ...
Imei net: 356833028866725
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




writem pm....


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 86 bytes written.
- Key: 18, size 86 bytes written.
- Key: 20, size 86 bytes written.
- Key: 25, size 4 bytes written.
- Key: 29, size 6 bytes written.
- Key: 34, size 80 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.
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 2.937 s

[naushad09]

Andra sir need soluation..............plzzzzz

[shashankmobile]

write pm by pm auth or post here proper log.




Br.
Shashank

[naushad09]

Scanning local SX4 Card ...
No SX4 Card found.
SERVER->Served by MXKEY - BLADE X at host1, agent version 1.1 revision 0.1

Authenticating using [MX] security server ...
Connecting to server[main.mxkey.biz] ...MXKEY SX4CARD - ID, hello 120.88.39.138
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 86 bytes written.
- Key: 18, size 86 bytes written.
- Key: 20, size 86 bytes written.
- Key: 25, size 4 bytes written.
- Key: 29, size 6 bytes written.
- Key: 34, size 80 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.
Warning: failed to write 309 - 8 (12 bytes)
Warning: failed to write 309 - 17 (12 bytes)
- Key: 22, size 12 bytes written.
Completed in 2.797 s

[abdullah sheikh]

Originally Posted by shashankmobile

Repair sd > Update Simlock > write pm 1 or 309 area by pm auth.
Simple.






Br.
Shashank

BROTHER I LL GIVE YOU A COMPLETE SOLUTION FOLLOW MY ALL INSTRUCATION



First you are repair sd like this ;






AND THEN PEPAIR SIM LOCK LIKE THIS WRITE CHECK ON PEPAIR SIM LOCK AND MAKE SIM LOCK RPL AND THEN CLICK ON PEPAIR SIM LOCK LIKE THIS


Uploaded with ImageShack.us


YOUR HAND SET WILL B 1000% OK TESTED BY ME DNT FORGET PRESS THANKX

[Andra]

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

your phone only need to REPAIR SIMLOCK
then do PMM Auth + write PM (1) and (309)


br,