5130c contact service not done............ (ANSWERED)

[Shantobhai]

5130c contact service not done............i can do that pls tell me any easy

solution........................

Here is all log

Bus check
.......................................

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.9169(08-01-2011), 1.0.0.15596(08-01-2011)
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 0AD0001637407D566CBB95C89A1D3CE4B2431C35
ASIC MODE ID: 00
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
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 8982 - 0000 0000 [Intel NU48F512,512 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: 0C917F11196FDB7378C18EF7260698CA4489DCA0
TransmissionMode: DDR&TX2
Original Imei: 35524603457114
Original Product code: 0576625
Bluetooth ID: 0025D0904B2E

Phone Type: RM-495 (Nokia 5130c-2)
SW Version: V 06.65 01-04-09 RM-495 (c) Nokia
Imei plain: 35524603457114-1
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!

After supar sd auth
......................................

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.9169(08-01-2011), 1.0.0.15596(08-01-2011)
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 0AD0001637407D566CBB95C89A1D3CE4B2431C35
ASIC MODE ID: 00
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
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 8982 - 0000 0000 [Intel NU48F512,512 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: 0C917F11196FDB7378C18EF7260698CA4489DCA0
TransmissionMode: DDR&TX2
Original Imei: 35524603457114
Original Product code: 0576625
Bluetooth ID: 0025D0904B2E

Phone Type: RM-495 (Nokia 5130c-2)
SW Version: V 07.97 13-09-10 RM-495 (c) Nokia
Imei plain: 35524603457114-1
Product Code: 0576625
Language Pack:
- not available.

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


SIMLOCK_DATA corrupted!

Repair sp losk
..................................

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.9169(08-01-2011), 1.0.0.15596(08-01-2011)

Product: V 06.65 01-04-09 RM-495 (c) Nokia

SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F

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

Completed in 12.375 s

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

Reading Simlock info ...
SIMLOCK_DATA corrupted!

Read phone id
.................................................. ........


Backup saved to "BB5_35524603457114_SIMLOCK.back"
Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.9169(08-01-2011), 1.0.0.15596(08-01-2011)

Product: V 07.97 13-09-10 RM-495 (c) Nokia

ERROR: Missing SP BLOCK or PM corrupted !

Now some body help me................................................ ............

[rockindheeraj]

simlock data cannot be repaired at the moment because it is sl3.

[gbluez]

All SL3 phones with damaged simlock can be fixed by using it's original backup.
And if you don't have it, your only solution is buy nokia rpl.
you can contact Fast Unlocking to buy one.

BR

[gsm_future]

i have simple and working idea for sl3 simlock data corrupted solution..............change pcb

[Shantobhai]

Originally Posted by gbluez

All SL3 phones with damaged simlock can be fixed by using it's original backup.
And if you don't have it, your only solution is buy nokia rpl.
you can contact Fast Unlocking to buy one.

BR

I have only original backup rpl but whean i write rpl bacup not sole same

condition contact service

[OTIENOJULIUS]

wait for new update in future,sl3 sd repair will be available

[gbluez]

Originally Posted by Shantobhai

I have only original backup rpl but whean i write rpl bacup not sole same

condition contact service

paste here your logs when you are restoring your rpl backup.


BR