5130 problem IMEI plain is invalid

[shreedid123]

here is log plz solve my problem

Version from phone: 07.91
Version from file: 07.91
Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.11446, Date: 25-11-2009
Invalid imei plain, RPL backup skipped.
Processing file: rm495__07.91.mcusw as MCU
[BB5,BB5 ALGORITHM] size: 18.20 MB
Supported RAP Ids: 010C192101013000, 0103192101003000, 0303192101033000, 030C192101033000
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 10C0010F9F4F7F5616A89E6DE5E0BD224BF85853
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 is blank/erased.
Storing certificate ...OK
Total erase size: 21.00 MB
CMT NOR area [00000000-000006BF] erased in 0.547 s
CMT NOR area [000006C0-0001FFFF] erased in 0.078 s
CMT NOR area [00040000-000BFFFF] erased in 2.219 s
CMT NOR area [000C0000-0013FFFF] erased in 0.156 s
CMT NOR area [00140000-0137FFFF] erased in 1 min 6.968 s
CMT NOR area [01380000-0151FFFF] erased in 6.797 s
Flash programming ...
CMT PAPUBKEYS: 0C917F11196FDB7378C18EF7260698CA4489DCA0 (RAP Certificate 164 v.1) written.
Programming completed in 2 min 1.063 s
Processing file: rm495__07.91.ppm_mh as PPM
[BB5,BB5 ALGORITHM] size: 7.04 MB
Supported RAP Ids: 010C192101013000, 0103192101003000, 0303192101033000, 030C192101033000
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 10C0010F9F4F7F5616A89E6DE5E0BD224BF85853
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 is blank/erased.
Total erase size: 8.62 MB
CMT NOR area [01520000-01DBFFFF] erased in 25.500 s
Flash programming ...
Programming completed in 45.703 s
Processing file: rm495__07.91_v2.image_mh_red as CNT
[BB5,BB5 ALGORITHM] page size: 128 K size: 8.26 MB
Supported RAP Ids: 010C192101013000, 0103192101003000, 0303192101033000, 030C192101033000
NOR page size in the phone is 128 K.
Formating FS: FILE2 ...
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 10C0010F9F4F7F5616A89E6DE5E0BD224BF85853
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 is blank/erased.
Total erase size: 34.00 MB
CMT NOR area [01DC0000-0215FFFF] erased in 16.454 s
CMT NOR area [02160000-03FBFFFF] erased in 2 min 6.500 s
Converting UCP blocks to 128 K.
Flash programming ...
Programming completed in 52.578 s
Flashing completed in 8 min 30.422 s


Phone Type: RM-495 (Nokia 5130c-2)
SW Version: V 07.91 29-10-09 RM-495 (c) Nokia
Imei plain: 12345610654321-?
Product Code: 0515596
Language Pack:
- not available.
This phone have PM308 protected, SD security in not restorable.
- Avoid SW Downgrade & manual erase to this phone !

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


Imei plain is invalid !!!
SIMLOCK_DATA corrupted!
Total time to process is 8 min 59.500 s

[gbluez]

if you don't have original backup when it is still in good condition, you will need bb5 ask-rpl service.

br

[lokdid123]

Originally Posted by gbluez

if you don't have original backup when it is still in good condition, you will need bb5 ask-rpl service.

br

plz give me process to ask rpl services

[shreedid123]

Originally Posted by gbluez

if you don't have original backup when it is still in good condition, you will need bb5 ask-rpl service.

br

plz give me procedure for ask rpl

[abheejeet]

you don't have original backup when it is still in good condition, you will need bb5 ask-rpl service.

[imran78669]

Originally Posted by gbluez

if you don't have original backup when it is still in good condition, you will need bb5 ask-rpl service.

br

plz sir tell us how its work ask2rpl and which tool server is working?

[gbluez]

hello,
at the moment we don't have this bb5 ask to rpl service.

br

[enzawigroup]

Originally Posted by gbluez

hello,
at the moment we don't have this bb5 ask to rpl service.

br

i have the same prob
i flash my phone with mxkey and now the phone contact service and i have the org backup but same

when i upload in the phone i face this msg
Restoring RF/BB DATA from backup ...
Updating RF ...OK
Updating BB ...OK
Updating WARRANTY ...OK
Updating PROD ...OK
Updating BT ...OK
missing NPC data.

Updating PRODUCTCODE (0552130)... OK
Updating PSN (MXH150513)... OK
Updating HWID (1001)... OK
Updating SIMLOCK...OK
Trying to update SUPERDONGLE_KEY ...OK
Updating WMDRM_PD...OK
Certificate programmed successfully !

Phone Type: RM-233 (Nokia 8800e-1)
SW Version: V 05.20 12-11-07 RM-233 (c) Nokia
Imei plain: 12345610654321-?
Language Pack:
- not available.

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


Imei plain is invalid !!!
Imei net: 12345610654321?
Version: SIMLOCK SERVER
Provider: Nokia Test, Country: Finland
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 8000000000000002

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
Reading PMM area 0 - 384, please WAIT ...
Section: 1 - got 26 key(s)



and i have this back up file

i shared to u

plz help me
i love this tool


br

[Andra]

your backup dont have NCP data .

when i upload in the phone i face this msg
Restoring RF/BB DATA from backup ...
Updating RF ...OK
Updating BB ...OK
Updating WARRANTY ...OK
Updating PROD ...OK
Updating BT ...OK
missing NPC data.

your PM have IMEI but not have NPC data.

solution is by generate BB5 RPL.

br,

[Bruno Rafael]

how to generete rpl by mxkey ( bb5 and bb5+)?

[Andra]

we dont have yet RPL BB5 calculation server.

br,

[Bruno Rafael]

Originally Posted by MobileEx-Team

we dont have yet RPL BB5 calculation server.

br,

ok.tankx.and.how to repair SL DATA Corrupted in n85 by mxkey?

[Andra]

and that to,
we not supported yet.

br,

[Bruno Rafael]

and creat rpl from pm??

[Andra]

create RPL from PM

on this link
write by alex

Of course you can! is just a bit of pratice needed.
Sample with the mobile of Phoneboutique

RM-328
(c) Nokia
HW version: 1304
PCI version:
RFIC version:
DSP version:
APE SW Core version: 03.06
APE Variant version: 05.01
APE Test version: rm328_ENO_x_2008wk23v0.30
Retu version: 15
Tahvo version: 22
APE HW version: 256
APE ADSP SW version: 256
Production serial number: KQA520847
Product code: 0566909
Module code:
Basic production code: 0548720
Flash code:
Order number:
Product specific data:
Long production SN: 0
ATO:
Default SN type:
IMEI plain: 352921022689872
IMEI spare to net: 3A 25 29 01 22 86 89 07
IMEI SV to net: 33 25 29 01 22 86 89 27 F4
LOCK STATUS:
CONFIG KEY: 0000000000000000
PROVIDER KEY: 0000000000000000
Provider: Unknown provider
Key Code count: 0, FBUS Code count: 0


It has the Simlock to 0000 which means the mobile has corrupted PM

He gave me the PM (I need only the 120 part in this case) and the infos
Just look for any logs with the same product code (You can use google)
I found this log

Product code: 0566909
Original IMEI: 352921-02-********
Production serial: KRA796793
HW Version: 1304
DSP Version: ICPR72_08w20
LCD Version:
APE ADSP Version: 256
SIMLock service: SIMLOCK SERVER [01000B07091C]
Profile bits: 8000000000000000
Simlock config: 2342000000000000
Invalid codes entered: 0 / 0
Block: 1; Lock: 1; State: Closed; Data: 23420F
Block: 2; Lock: 1; State: Closed; Data: 23594F
Reading PM...
Input power: 11.93V OK.

Where I can see it is 2 lines, 2 provviders locked Hutchinson.

I use the PM120 utility by oOXTCOo to generate the PM120 line 1 with these infos and i get this

[120]
0=800000000000000023420000000000000018020000000000 0028000001FFFFFF003C000001FFFFFF000000007FFF6F07FF FFFFFFF800005003000502000000007FFF6F07FFFFFFFFF800 00530300050223420F23594FFFFF

which is different, as you can see, from the one in the PM posted by phonesboutique

Hoping the PM120 1, 2 and 3 fields are OK (Normally they are not touched by the free solutions) I merge these 3 fields with the calculated fields 0 in a file and I get this PM 120

[120]
0=800000000000000023420000000000000018020000000000 0028000001FFFFFF003C000001FFFFFF000000007FFF6F07FF FFFFFFF800005003000502000000007FFF6F07FFFFFFFFF800 00530300050223420F23594FFFFF
1=D9F42AC46F5D177419A45084D504C94A3C4D00F9030F909D 9FFF525A0CE56ACE2F1008652B5506D58902BD5A5339C909DE E0954806E663F2F7C3C0766C4561E5296C9E9A49D72F75DB65 9391DC1DBCD9
2=04EBD9B852D0DCEC318EDCBA5E0833A836482FA3
3=000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000

Using the function create RPL from PM of Cyclone I make from it a plain RPL like this

[CERT_PROG_DATA_OUT_CMT]
SIMLOCK_DATA_1=A6A057DAB4FF11711C918A9F073AE002A0C 70BE88000000000000000234200000000000000180200
SIMLOCK_DATA_2=000000000028000001FFFFFF003C000001F FFFFF000000007FFF6F07FFFFFFFFF800005003000502
SIMLOCK_DATA_3=000000007FFF6F07FFFFFFFFF8000053030 0050223420F23594FFFFF
SIMLOCK_KEY_DATA_1=D9F42AC46F5D177419A45084D504C94 A3C4D00F9030F909D9FFF525A0CE56ACE2F1008652B5506D5
SIMLOCK_KEY_DATA_2=8902BD5A5339C909DEE0954806E663F 2F7C3C0766C4561E5296C9E9A49D72F75DB659391DC1DBCD9
SIMLOCK_KEY_DATA_3=04EBD9B852D0DCEC318EDCBA5E0833A 836482FA3

Which if I write in the mobiles, with plain rpl thicked, should Fix the simlock.

Now, considering the mobile of phonesboutique doesn't give error in reading the simlock, before writing the RPL i would write only the PM 120 line 0 in the mobile

so, using write PM i would write this PM in the mobile

http://rapidshare.com/files/29561599...21022689872.pm

Doing this the mobile should be already out of the contact service

if instead was with error in reading the simlock data I would write this plain RPL

http://rapidshare.com/files/29561645...1022689872.RPL

as writing the RPL in the mobile would sync as well the PM 308 and fixing the simlock corrupted.

obviously all this will work if the fields 1, 2 and 3 of the PM are still the original

BR

Alex

br,