nokia 5130 contact service repair successfully

[MGT SOFTWARE]

For the first time i repaired 5130 which was very taff to me now is working ok

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.7687(12-02-2010), 1.0.0.12095(13-02-2010)
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 1CF0000A71D27D563A0A2AF739540E672F90FF1A
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 RAP 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,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
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: 0C917F11196FDB7378C18EF7260698CA4489DCA0
Original Imei: 35524603053621
Original Product code: 0572175
Bluetooth ID: 0025D034E0DD

Phone Type: RM-495 (Nokia 5130c-2)
SW Version: V 06.65 01-04-09 RM-495 (c) Nokia
Imei plain: 35524603053621-3
Product Code: 0571584
Language Pack:
- not available.

This phone have PM308 protected, SD security in not restorable.
This is SL3 phone(Simlock2 format).
- Avoid SW Downgrade & manual erase to this phone !

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 passed


Imei net: 355246030536213
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

[Master Software]

gooood work bro thanks for reporting...................

br

[ahsan bhi]

how can u solv this ???post log plzzzzz

[MGT SOFTWARE]

first step make full back up, and save,

secondly repair SD, sometime you may get error, do not worry,
go to the PMSolution for: "SECURITY_TEST failed!" and "warning: SD authorized but verify failed!"

If after repair SD and/or Simlock (Super Dongle RPL and Simlock RPL upload) you get "SECURITY_TEST failed!" and/or "warning: SD authorized but verify failed!".
This is comming usually because some PM fields and/or RPL sections are missing from your phone (e.g. DRM keys, CCC, ...).

Solution 1 (easy way, maybe not work all time, depends how phone was damaged):
- write full PM from SAME phone model C:\mobileEx\3.3\data\NOKIA BB5 PM Tested by Chevka
- unplug/replug phone from JAF/UFS box
- make Simlock RPL repair
- make SD RPL repair
- unplug/replug phone from JAF/UFS box
- make SUPER SX4 Auth then write PM1 and PM309

if still have problems, use Solution 2:

- backup RPL (NPC, CCC, HWC, ...), will call this ORIGINAL RPL
- backup RPL from another working phone (same model) with SAME product code
- edit this good RPL from another phone and remove NPC section (all lines who start with NPC_DATA_1 ... NPC_DATA_xx), will call this edited file CLONE RPL
- backup full PM from another working phone (same model) with SAME product code, will call this file CLONE PM
- full erase flash chip (use erase file regarding flash chip size)
- flash phone (CMT, APE, ...)
- upload CLONE RPL
- upload ORIGINAL RPL
- write full CLONE PM without fields 1,120,308,309
- unplug/replug phone from JAF/UFS box
- make Simlock RPL repair
- make SD RPL repair
- unplug/replug phone from JAF/UFS box
- make SUPER SX4 Auth then write PM1 and PM309

[nokiacareasr]

gooood work bro thanks for reporting...................

br

[Misbahullah]

nice solution but this can be a repaired phone log where are the first logs and procedure

[MGT SOFTWARE]

Originally Posted by falcon1975

hi
but how work it
can u repaly full post & how solution
thanks

next time i will arrange the video how to deal with good pm NOKIA BB5 PM Tested by Chevka is very useful pm , C:\mobileEx\3.3\data\NOKIA BB5 PM Tested by Chevka, if pm show fail warning, try to repair SD then again check factory reset , see if still security fail, if still security fail activate super dong, pm auth then write pm, check again , i think thats all, but remember do note erase the phone or press NPC button this is sl3 phone which till now no solution to repair simlock

[MGT SOFTWARE]

Originally Posted by Misbahullah

nice solution but this can be a repaired phone log where are the first logs and procedure

i was not aware with this solution i was trying to follow some instruction from the previous repaired BB5 sl2, but this work only for security fail not for simlock data corrupted

[alialjorany]

Originally Posted by MGT SOFTWARE

first step make full back up, and save,

secondly repair SD, sometime you may get error, do not worry,
go to the PMSolution for: "SECURITY_TEST failed!" and "warning: SD authorized but verify failed!"

If after repair SD and/or Simlock (Super Dongle RPL and Simlock RPL upload) you get "SECURITY_TEST failed!" and/or "warning: SD authorized but verify failed!".
This is comming usually because some PM fields and/or RPL sections are missing from your phone (e.g. DRM keys, CCC, ...).

Solution 1 (easy way, maybe not work all time, depends how phone was damaged):
- write full PM from SAME phone model C:\mobileEx\3.3\data\NOKIA BB5 PM Tested by Chevka
- unplug/replug phone from JAF/UFS box
- make Simlock RPL repair
- make SD RPL repair
- unplug/replug phone from JAF/UFS box
- make SUPER SX4 Auth then write PM1 and PM309

if still have problems, use Solution 2:

- backup RPL (NPC, CCC, HWC, ...), will call this ORIGINAL RPL
- backup RPL from another working phone (same model) with SAME product code
- edit this good RPL from another phone and remove NPC section (all lines who start with NPC_DATA_1 ... NPC_DATA_xx), will call this edited file CLONE RPL
- backup full PM from another working phone (same model) with SAME product code, will call this file CLONE PM
- full erase flash chip (use erase file regarding flash chip size)
- flash phone (CMT, APE, ...)
- upload CLONE RPL
- upload ORIGINAL RPL
- write full CLONE PM without fields 1,120,308,309
- unplug/replug phone from JAF/UFS box
- make Simlock RPL repair
- make SD RPL repair
- unplug/replug phone from JAF/UFS box
- make SUPER SX4 Auth then write PM1 and PM309

is that possible ???????????

[anand_panwar]

can u help me 5130 c/s my id anand_panwar28@yahoo.co.in

[Master Software]

Originally Posted by alialjorany

is that possible ???????????

i think mayb possible but simoock data crupted not possible

[dilipnachna]

Originally Posted by Master Software

i think mayb possible but simoock data crupted not possible

yes u r right bro.....................

[vmf1990]

Thank u i repaired 5130 security failed with the 1st method

Originally Posted by MGT SOFTWARE

first step make full back up, and save,

secondly repair SD, sometime you may get error, do not worry,
go to the PMSolution for: "SECURITY_TEST failed!" and "warning: SD authorized but verify failed!"

If after repair SD and/or Simlock (Super Dongle RPL and Simlock RPL upload) you get "SECURITY_TEST failed!" and/or "warning: SD authorized but verify failed!".
This is comming usually because some PM fields and/or RPL sections are missing from your phone (e.g. DRM keys, CCC, ...).

Solution 1 (easy way, maybe not work all time, depends how phone was damaged):
- write full PM from SAME phone model C:\mobileEx\3.3\data\NOKIA BB5 PM Tested by Chevka
- unplug/replug phone from JAF/UFS box
- make Simlock RPL repair
- make SD RPL repair
- unplug/replug phone from JAF/UFS box
- make SUPER SX4 Auth then write PM1 and PM309

if still have problems, use Solution 2:

- backup RPL (NPC, CCC, HWC, ...), will call this ORIGINAL RPL
- backup RPL from another working phone (same model) with SAME product code
- edit this good RPL from another phone and remove NPC section (all lines who start with NPC_DATA_1 ... NPC_DATA_xx), will call this edited file CLONE RPL
- backup full PM from another working phone (same model) with SAME product code, will call this file CLONE PM
- full erase flash chip (use erase file regarding flash chip size)
- flash phone (CMT, APE, ...)
- upload CLONE RPL
- upload ORIGINAL RPL
- write full CLONE PM without fields 1,120,308,309
- unplug/replug phone from JAF/UFS box
- make Simlock RPL repair
- make SD RPL repair
- unplug/replug phone from JAF/UFS box
- make SUPER SX4 Auth then write PM1 and PM309

is there any possibility that we make backup first aND THEN TRY TO UNLOCK...........

[safaraa]

Originally Posted by vmf1990

Thank u i repaired 5130 security failed with the 1st method
is there any possibility that we make backup first aND THEN TRY TO UNLOCK...........

You can get the unlock code here ************.com : Unlock your mobile phone for free at free of cost....And also get the unlock instruction in then same site.....

[spkumar]

mic and speaker not working pls solution