5220; simlock data corrupted; is it possible to be repaired w/o ask2rpl? - GSM-Forum

ru_dee · 09-30-2009, 05:17

Hello,

got 5220 rm-411, contact service
damaged in security n simlock..
security area has been repaired, and is OK. one problem left, and that's its simlock

here's the log when i did BUS check

Code:

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM1 ID: 00000295
EM2 ID: 00000B22
PUBLIC ID: 0510010D8D9F02542966F8D924B3F95DEC13E515
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.fg [BB5 ALGORITHM] version: 1.33.1 revision: 0.0 size: 0x29878
 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: D93826B23E9B093BE4DD7304FBAA6778996AE60B
Original Imei: 35366201010036
Original Product code: 0563666
Bluetooth ID: 0021ABE46B60
 
Phone Type: RM-411 (Nokia 5220 XpressMusic)
SW Version: V 04.86 08-08-08 RM-411 (c) Nokia             
Imei plain: 35366201010036-0
Product Code: 0563666
VariantId: X
Language Pack:
- not available.

This phone have PM308 protected, SD security in not restorable.
Avoid manual erase to this phone !
 
SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST failed!
SECURITY_TEST failed!
 
TimeStamp: 2008-07-01T12:19:35Z
SW Version: 04.00
Variant Version: 001
ProductProfile: RM411_0563666_04.00_001.spr
Simlock: 0563666_simlock.bin
SIMLOCK_DATA corrupted!

and this is log after security (pm area 1 n 308) repaired

Code:

Phone Type: RM-411 (Nokia 5220 XpressMusic)
SW Version: V 04.86 08-08-08 RM-411 (c) Nokia             
Imei plain: 35366201010036-0
Product Code: 0563666
VariantId: X
Language Pack:
- not available.

This phone have PM308 protected, SD security in not restorable.
Avoid manual erase to this phone !
 
SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST failed!
SECURITY_TEST passed
 
TimeStamp: 2008-07-01T12:19:35Z
SW Version: 04.00
Variant Version: 001
ProductProfile: RM411_0563666_04.00_001.spr
Simlock: 0563666_simlock.bin
 
SIMLOCK_DATA corrupted!

tried already repairing simlock data using MX-key (option: repair SL; ticked PA_SL2; on tab imei and security), but no luck

here's the log

Code:

SIMLOCK_DATA corrupted!
 
 
Backup already exist.
Using device: UFS_USB V2.8 (c) SarasSoft 2007.
 
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
 
Error: Security block invalid or PM corrupted !

is there any other way to repair/ solve this problem w/o ask new rpl?

ru_dee · 09-30-2009, 06:09

pm n imei back-up were conducted after CS, i think it won't help -FYI the phone is PA_SL2, got pm308 protected-
restoring pm n imei back-up, then, will damage superdongle, and causing wd timer active

neo_2005 · 09-30-2009, 07:02

with other version not protected SD

ru_dee · 09-30-2009, 07:05

Quote:

Originally Posted by neo_2005

with other version not protected SD

u mean phone sw version or mobileX version?

Andra · 09-30-2009, 20:06

flash with unprotected frimware ,
and restore your backup .

br,

ru_dee · 10-01-2009, 03:12

Quote:

Originally Posted by MobileEx-Team

flash with unprotected frimware ,
and restore your backup .

br,

unprotected firmware? u mean flashing with other type/model firmware like rm-303, let's say v.7.0?

or else?

JHUNpanabO · 10-01-2009, 03:21

flash your phone another version....

ru_dee · 10-01-2009, 03:33

Quote:

Originally Posted by otelimrac

flash your phone another version....

upgraded already to firmware v.05.63, and didn't solve anything

ru_dee · 10-01-2009, 03:48

i flashed using rm-303 v.08.32, rpl n pm backed-up already.
i did full-erase, ticking safe erase, and automatically back-up rpl if possible, here's log

Code:

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Rpl backup already exist.
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM1 ID: 00000295
EM2 ID: 00000B22
PUBLIC ID: 0510010D8D9F02542966F8D924B3F95DEC13E515
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.fg [BB5 ALGORITHM] version: 1.33.1 revision: 0.0 size: 0x29878
 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: D93826B23E9B093BE4DD7304FBAA6778996AE60B
Total erase size: 63.75 MB
CMT NOR area [00000000-03FBFFFF] erased in 3 min 16.094 s

flashed w/ rm-303 firmware; mcu n ppm only

Code:

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Processing file: rm303__08.32.mcusw as MCU 
 [BB5,BB5 ALGORITHM]  size: 17.05 MB
 Supported RAP Ids: 010C192101013000, 0103192101003000, 030C192101033000
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM1 ID: 00000295
EM2 ID: 00000B22
PUBLIC ID: 0510010D8D9F02542966F8D924B3F95DEC13E515
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: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 
ExtDEVC: FFFF 0000 - 0000 0000
 Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 1.33.1 revision: 0.0 size: 0x29878
 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: 18.00 MB
CMT NOR area [00000000-000006BF] erased in 0.063 s
CMT NOR area [000006C0-0001FFFF] erased in 0.078 s
CMT NOR area [00040000-000BFFFF] erased in 0.156 s
CMT NOR area [000C0000-0013FFFF] erased in 0.156 s
CMT NOR area [00140000-010DFFFF] erased in 3.609 s
CMT NOR area [010E0000-0121FFFF] erased in 0.312 s
Flash programming ...
Selecting first PAPUB block with matching CMT RootKey
CMT PAPUBKEYS, RAP Certificate 90 v1 written.
Programming completed in 1 min 52.078 s
Processing file: rm303__08.32.ppm_t as PPM 
 [BB5,BB5 ALGORITHM]  size: 6.05 MB
 Supported RAP Ids: 010C192101013000, 0103192101003000, 030C192101033000
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM1 ID: 00000295
EM2 ID: 00000B22
PUBLIC ID: 0510010D8D9F02542966F8D924B3F95DEC13E515
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.fg [BB5 ALGORITHM] version: 1.33.1 revision: 0.0 size: 0x29878
 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: 3E96DE4212587183E5E16BB2C79692A53C19875D
Total erase size: 6.50 MB
CMT NOR area [01220000-0189FFFF] erased in 1.531 s
Flash programming ...
Programming completed in 38.453 s
Flashing completed in 3 min 21.579 s
 
 
Phone Type: RM-303 (Nokia 5310 XpressMusic)
SW Version: V 08.32 23-07-08 RM-303 (c) Nokia             
Imei plain: 12345610654321-?
Product Code: 0563666
VariantId: T
Language Pack:
- not available.

SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST passed
 
 
Imei plain is invalid !!!
SIMLOCK_DATA corrupted!
Total time to process is 3 min 31.078 s

it successed turning simlock test from 'failed' to 'pass'
and warning 'pm 308 protected and not restorable' dissappear.

but when i restore pm n rpl backed-up, phone won't enter local mode

here's log

Code:

restoring pm

SIMLOCK invalid!
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST passed
 
 
Imei plain is invalid !!!
SIMLOCK_DATA corrupted!
Phone authenticated to SUPERDONGLE already.
Writing PM from Node ...
Section: 1
 - Key: 0, size 12 bytes written.
 - Key: 2, size 70 bytes written.
 - Key: 3, size 70 bytes written.
 - Key: 4, size 70 bytes written.
 - Key: 6, size 276 bytes written.
 - Key: 7, size 276 bytes written.
 - Key: 8, size 276 bytes written.
 - Key: 10, size 384 bytes written.
 - Key: 11, size 384 bytes written.
 - Key: 12, size 384 bytes written.
 - Key: 14, size 384 bytes written.
 - Key: 15, size 384 bytes written.
 - Key: 16, size 384 bytes written.
 - Key: 17, size 32 bytes written.
 - Key: 19, size 16 bytes written.
Section: 2
 - Key: 0, size 440 bytes written.
Section: 4
 - Key: 1, size 800 bytes written.
 - Key: 3, size 10 bytes written.
 - Key: 4, size 8 bytes written.
 - Key: 5, size 8 bytes written.
 - Key: 6, size 8 bytes written.
 - Key: 9, size 5 bytes written.
 - Key: 18, size 80 bytes written.
 - Key: 19, size 4 bytes written.
 - Key: 28, size 2 bytes written.
Section: 8
 - Key: 0, size 2 bytes written.
 - Key: 1, size 16 bytes written.
 - Key: 2, size 16 bytes written.
 - Key: 3, size 128 bytes written.
 - Key: 4, size 128 bytes written.
 - Key: 8, size 8 bytes written.
 - Key: 9, size 8 bytes written.
Warning: failed to write 8 - 10 (24 bytes)
Section: 11
 - Key: 0, size 4 bytes written.
 - Key: 1, size 4 bytes written.
 - Key: 2, size 4 bytes written.
 - Key: 3, size 4 bytes written.
 - Key: 5, size 6 bytes written.
 - Key: 6, size 2 bytes written.
 - Key: 14, size 2 bytes written.
 - Key: 15, size 2 bytes written.
 - Key: 16, size 2 bytes written.
 - Key: 17, size 2 bytes written.
 - Key: 18, size 16 bytes written.
 - Key: 19, size 32 bytes written.
 - Key: 20, size 32 bytes written.
 - Key: 21, size 2 bytes written.
 - Key: 22, size 2 bytes written.
 - Key: 23, size 2 bytes written.
 - Key: 24, size 2 bytes written.
 - Key: 25, size 2 bytes written.
 - Key: 26, size 2 bytes written.
 - Key: 27, size 2 bytes written.
 - Key: 28, size 2 bytes written.
 - Key: 29, size 2 bytes written.
 - Key: 30, size 2 bytes written.
 - Key: 31, size 2 bytes written.
 - Key: 32, size 2 bytes written.
 - Key: 33, size 2 bytes written.
 - Key: 34, size 2 bytes written.
 - Key: 35, size 2 bytes written.
 - Key: 36, size 2 bytes written.
 - Key: 37, size 2 bytes written.
 - Key: 38, size 2 bytes written.
 - Key: 39, size 2 bytes written.
 - Key: 40, size 2 bytes written.
 - Key: 41, size 2 bytes written.
 - Key: 42, size 2 bytes written.
 - Key: 43, size 2 bytes written.
 - Key: 44, size 2 bytes written.
 - Key: 45, size 2 bytes written.
 - Key: 46, size 2 bytes written.
 - Key: 47, size 2 bytes written.
 - Key: 48, size 2 bytes written.
 - Key: 49, size 2 bytes written.
 - Key: 50, size 2 bytes written.
 - Key: 51, size 2 bytes written.
 - Key: 52, size 2 bytes written.
 - Key: 53, size 2 bytes written.
 - Key: 54, size 2 bytes written.
 - Key: 55, size 2 bytes written.
 - Key: 56, size 2 bytes written.
 - Key: 57, size 2 bytes written.
 - Key: 58, size 2 bytes written.
 - Key: 59, size 2 bytes written.
 - Key: 60, size 2 bytes written.
 - Key: 61, size 2 bytes written.
 - Key: 62, size 2 bytes written.
 - Key: 63, size 2 bytes written.
 - Key: 64, size 2 bytes written.
 - Key: 65, size 2 bytes written.
 - Key: 66, size 4 bytes written.
 - Key: 68, size 4 bytes written.
 - Key: 69, size 4 bytes written.
 - Key: 70, size 4 bytes written.
 - Key: 71, size 4 bytes written.
 - Key: 72, size 16 bytes written.
 - Key: 73, size 4 bytes written.
 - Key: 74, size 2 bytes written.
 - Key: 75, size 13 bytes written.
Section: 12
 - Key: 0, size 102 bytes written.
Section: 13
 - Key: 1, size 2 bytes written.
 - Key: 3, size 2 bytes written.
 - Key: 8, size 2 bytes written.
 - Key: 11, size 48 bytes written.
 - Key: 12, size 4 bytes written.
 - Key: 15, size 886 bytes written.
 - Key: 16, size 2 bytes written.
 - Key: 19, size 8 bytes written.
 - Key: 25, size 2 bytes written.
 - Key: 37, size 4 bytes written.
 - Key: 42, size 4 bytes written.
 - Key: 43, size 4 bytes written.
 - Key: 45, size 4 bytes written.
 - Key: 46, size 4 bytes written.
 - Key: 48, size 4 bytes written.
 - Key: 52, size 2 bytes written.
 - Key: 53, size 4 bytes written.
 - Key: 54, size 4 bytes written.
 - Key: 58, size 2 bytes written.
 - Key: 60, size 4 bytes written.
 - Key: 61, size 4 bytes written.
 - Key: 63, size 4 bytes written.
 - Key: 64, size 4 bytes written.
 - Key: 66, size 4 bytes written.
 - Key: 67, size 4 bytes written.
 - Key: 71, size 4 bytes written.
 - Key: 72, size 4 bytes written.
 - Key: 74, size 4 bytes written.
 - Key: 75, size 2 bytes written.
 - Key: 76, size 2 bytes written.
 - Key: 77, size 2 bytes written.
 - Key: 83, size 2 bytes written.
 - Key: 85, size 4 bytes written.
 - Key: 86, size 4 bytes written.
 - Key: 87, size 2 bytes written.
 - Key: 89, size 4 bytes written.
 - Key: 90, size 4 bytes written.
 - Key: 91, size 2 bytes written.
 - Key: 93, size 4 bytes written.
 - Key: 94, size 4 bytes written.
 - Key: 95, size 2 bytes written.
 - Key: 97, size 4 bytes written.
 - Key: 98, size 4 bytes written.
 - Key: 99, size 2 bytes written.
 - Key: 100, size 4 bytes written.
 - Key: 101, size 2 bytes written.
 - Key: 103, size 4 bytes written.
 - Key: 104, size 4 bytes written.
 - Key: 105, size 4 bytes written.
 - Key: 106, size 4 bytes written.
 - Key: 107, size 4 bytes written.
 - Key: 108, size 2 bytes written.
 - Key: 109, size 4 bytes written.
 - Key: 110, size 4 bytes written.
 - Key: 111, size 4 bytes written.
 - Key: 112, size 2 bytes written.
 - Key: 113, size 4 bytes written.
 - Key: 114, size 4 bytes written.
 - Key: 118, size 4 bytes written.
 - Key: 119, size 4 bytes written.
 - Key: 123, size 8 bytes written.
 - Key: 129, size 4 bytes written.
 - Key: 130, size 4 bytes written.
 - Key: 133, size 2 bytes written.
 - Key: 135, size 2 bytes written.
 - Key: 138, size 4 bytes written.
 - Key: 139, size 4 bytes written.
 - Key: 144, size 4 bytes written.
 - Key: 145, size 8 bytes written.
 - Key: 146, size 4 bytes written.
 - Key: 147, size 4 bytes written.
 - Key: 159, size 2 bytes written.
 - Key: 160, size 2 bytes written.
 - Key: 167, size 8 bytes written.
 - Key: 168, size 4 bytes written.
 - Key: 177, size 4 bytes written.
 - Key: 178, size 2 bytes written.
 - Key: 190, size 4 bytes written.
 - Key: 191, size 2 bytes written.
 - Key: 193, size 4 bytes written.
 - Key: 196, size 10 bytes written.
Section: 31
 - Key: 4, size 14 bytes written.
Section: 42
 - Key: 0, size 2 bytes written.
 - Key: 1, size 12 bytes written.
 - Key: 2, size 36 bytes written.
 - Key: 3, size 36 bytes written.
 - Key: 4, size 36 bytes written.
 - Key: 5, size 36 bytes written.
 - Key: 6, size 36 bytes written.
 - Key: 7, size 40 bytes written.
 - Key: 8, size 40 bytes written.
 - Key: 9, size 40 bytes written.
 - Key: 10, size 40 bytes written.
 - Key: 11, size 40 bytes written.
 - Key: 12, size 40 bytes written.
 - Key: 13, size 40 bytes written.
 - Key: 14, size 40 bytes written.
Section: 50
 - Key: 0, size 2 bytes written.
Section: 54
 - Key: 0, size 2 bytes written.
Section: 66
 - Key: 0, size 524 bytes written.
 - Key: 1, size 240 bytes written.
 - Key: 2, size 240 bytes written.
 - Key: 5, size 240 bytes written.
 - Key: 6, size 4 bytes written.
 - Key: 7, size 4 bytes written.
 - Key: 8, size 4 bytes written.
 - Key: 9, size 4 bytes written.
 - Key: 10, size 240 bytes written.
 - Key: 11, size 240 bytes written.
 - Key: 16, size 4 bytes written.
 - Key: 18, size 4 bytes written.
 - Key: 20, size 4 bytes written.
 - Key: 22, size 4 bytes written.
 - Key: 24, size 4 bytes written.
 - Key: 26, size 4 bytes written.
 - Key: 28, size 4 bytes written.
 - Key: 30, size 4 bytes written.
 - Key: 32, size 4 bytes written.
 - Key: 34, size 4 bytes written.
 - Key: 37, size 4 bytes written.
 - Key: 38, size 4 bytes written.
 - Key: 98, size 4 bytes written.
 - Key: 100, size 4 bytes written.
 - Key: 101, size 4 bytes written.
 - Key: 106, size 4 bytes written.
 - Key: 108, size 4 bytes written.
 - Key: 109, size 4 bytes written.
 - Key: 110, size 4 bytes written.
 - Key: 133, size 7 bytes written.
 - Key: 134, size 7 bytes written.
 - Key: 135, size 7 bytes written.
Section: 96
 - Key: 0, size 2 bytes written.
Section: 107
 - Key: 0, size 21 bytes written.
 - Key: 1, size 89 bytes written.
 - Key: 2, size 69 bytes written.
 - Key: 3, size 70 bytes written.
 - Key: 25, size 132 bytes written.
 - Key: 26, size 12 bytes written.
Section: 116
 - Key: 0, size 2 bytes written.
 - Key: 1, size 12 bytes written.
 - Key: 2, size 36 bytes written.
 - Key: 3, size 36 bytes written.
 - Key: 4, size 36 bytes written.
 - Key: 5, size 36 bytes written.
 - Key: 6, size 36 bytes written.
 - Key: 7, size 40 bytes written.
 - Key: 8, size 40 bytes written.
 - Key: 9, size 40 bytes written.
 - Key: 10, size 40 bytes written.
 - Key: 11, size 40 bytes written.
 - Key: 12, size 40 bytes written.
 - Key: 13, size 40 bytes written.
 - Key: 14, size 40 bytes written.
 - Key: 15, size 40 bytes written.
 - Key: 16, size 40 bytes written.
Section: 120
 - Key: 0, size 944 bytes written.
 - Key: 1, size 80 bytes written.
 - Key: 2, size 20 bytes written.
 - Key: 3, size 112 bytes written.
Section: 153
 - Key: 0, size 68 bytes written.
 - Key: 1, size 68 bytes written.
 - Key: 2, size 68 bytes written.
 - Key: 3, size 68 bytes written.
 - Key: 4, size 68 bytes written.
 - Key: 5, size 68 bytes written.
Section: 193
 - Key: 2, size 8 bytes written.
 - Key: 3, size 32 bytes written.
 - Key: 4, size 32 bytes written.
 - Key: 9, size 64 bytes written.
Section: 217
 - Key: 0, size 32 bytes written.
Section: 218
 - Key: 0, size 2 bytes written.
Section: 301
 - Key: 0, size 2 bytes written.
 - Key: 1, size 12 bytes written.
 - Key: 2, size 36 bytes written.
 - Key: 3, size 36 bytes written.
 - Key: 4, size 36 bytes written.
 - Key: 5, size 36 bytes written.
 - Key: 6, size 36 bytes written.
 - Key: 7, size 40 bytes written.
 - Key: 8, size 40 bytes written.
 - Key: 9, size 40 bytes written.
 - Key: 10, size 40 bytes written.
 - Key: 11, size 40 bytes written.
 - Key: 12, size 40 bytes written.
 - Key: 13, size 40 bytes written.
 - Key: 14, size 40 bytes written.
 - Key: 15, size 40 bytes written.
 - Key: 16, size 40 bytes written.
Section: 308
Warning: failed to write 308 - 1 (8192 bytes)
Warning: failed to write 308 - 5 (10 bytes)
 - Key: 9, size 40 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.
 - Key: 8, size 12 bytes written.
 - Key: 17, size 12 bytes written.
 - Key: 22, size 12 bytes written.
Section: 322
Section: 341
 - Key: 3, size 4 bytes written.
 - Key: 4, size 4418 bytes written.
Section: 354
 - Key: 0, size 3 bytes written.
Section: 355
 - Key: 1, size 2028 bytes written.
Section: 356
 - Key: 0, size 2 bytes written.
Section: 362
 - Key: 1, size 120 bytes written.
Completed in 1 min 1.188 s
==================================
restoring rpl


Imei: 35366201010036
Updating PRODUCTCODE (0563666)... OK
Updating PSN (DTB727192)... OK
Updating HWID (1000)... OK
Updating SIMLOCK...OK
Updating SIMLOCK_KEY...error 0x1
Updating SUPERDONGLE_KEY from backup ...OK
Updating WMDRM_PD...OK
Updating WARRANTY ...OK
Updating PROD ...OK
Updating BT ...OK
Restoring RF/BB DATA from backup ...
Updating RF ...OK
Updating BB ...OK
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM1 ID: 00000295
EM2 ID: 00000B22
PUBLIC ID: 0510010D8D9F02542966F8D924B3F95DEC13E515
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.fg [BB5 ALGORITHM] version: 1.33.1 revision: 0.0 size: 0x29878
 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: 3E96DE4212587183E5E16BB2C79692A53C19875D

----
PAPUBKEYS from phone is NOT same as on certificate, rpl does not seems to be valid for this phone. Do you want to continue? pressed 'yes'
----
NPC verify error, RAP PAPUPKEYS not match or empty!
Updating CMT  NPC ...OK
Updating CMT  CCC ...OK
Updating CMT  HWC ...OK
Certificate programmed successfully !


PAPUBKEYS from phone is NOT same as on certificate, rpl does not seems to be valid for this phone. Do you want to continue?

any idea what to do next?

utuh · 10-01-2009, 21:24

Code:

SIMLOCK invalid!  <<< maybe its mean empty
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST passed

SIMLOCK_DATA corrupted!

if simlock invalid ,can not repair with this method (currently still have to calculate RPL)

Code:

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


SIMLOCK_DATA corrupted!

if simlock valid and simlock test failed, you can do repair with this method

CMIIW

ru_dee · 10-02-2009, 06:00

Quote:

Originally Posted by utuh

Code:

SIMLOCK invalid!  <<< maybe its mean empty
SUPERDONGLE_KEY seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST passed

SIMLOCK_DATA corrupted!

if simlock invalid ,can not repair with this method (currently still have to calculate RPL)

Code:

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


SIMLOCK_DATA corrupted!

if simlock valid and simlock test failed, you can do repair with this method

CMIIW

thank u Sir, that's what i've been searching, then there's no sucha trick/way yet, to solve this problem w/o ask2rpl

there's way to fix 'simlock invalid' using other tools, but only for rapido cpu, isn't it?

andr3_jc · 10-08-2009, 09:16

ny body can help me plz...urgent.i have 5220(rm-411)contact service.can solved without rpl??any body have solution plz...

this log

Phone Type: RM-411 (Nokia 5220 XpressMusic)
SW Version: V 06.51 23-03-09 RM-411 (c) Nokia
Imei plain: 35366201517644-9
Product Code: 0563611
VariantId: X
Language Pack:
- not available.

This phone have PM308 protected, SD security in not restorable.
Avoid manual erase to this phone !

SIMLOCK seems to be valid
SUPERDONGLE_KEY invalid!
WD timer enabled, phone will reboot itself after 3 min.
SIMLOCK_TEST failed!
SECURITY_TEST passed

and this is backup

ashraf_bcs · 10-08-2009, 09:27

Quote:

Originally Posted by andr3_jc

ny body can help me plz...urgent.i have 5220(rm-411)contact service.can solved without rpl??any body have solution plz...

this log

Phone Type: RM-411 (Nokia 5220 XpressMusic)
SW Version: V 06.51 23-03-09 RM-411 (c) Nokia
Imei plain: 35366201517644-9
Product Code: 0563611
VariantId: X
Language Pack:
- not available.

This phone have PM308 protected, SD security in not restorable.
Avoid manual erase to this phone !

SIMLOCK seems to be valid
SUPERDONGLE_KEY invalid!
WD timer enabled, phone will reboot itself after 3 min.
SIMLOCK_TEST failed!
SECURITY_TEST passed

and this is backup

It looks SUPERDONGLE_KEY invalid!.I think no way to revive it without new rpl.Actualy no device can back up SUPERDONGLE_KEY data yet.

Riteshgpt60 · 10-08-2009, 11:12

Quote:

Originally Posted by MobileEx-Team

flash with unprotected frimware ,
and restore your backup .

br,

Unprotected firmware? what it means sir?

10-01-2009, 21:24	#10 (permalink)
utuh Freak Poster Join Date: Jul 2006 Location: indonesia Posts: 303 Member: 310458 Status: Offline Thanks Meter: 94	Code: SIMLOCK invalid! <<< maybe its mean empty SUPERDONGLE_KEY seems to be valid SIMLOCK_TEST passed SECURITY_TEST passed SIMLOCK_DATA corrupted! if simlock invalid ,can not repair with this method (currently still have to calculate RPL) Code: SIMLOCK seems to be valid SUPERDONGLE_KEY seems to be valid SIMLOCK_TEST failed! SECURITY_TEST failed! SIMLOCK_DATA corrupted! if simlock valid and simlock test failed, you can do repair with this method CMIIW

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Is it possible to gdfs repair w200i with SE Ultimatr Unlocker,	tuhingr	Cruiser Suite	2	09-26-2008 09:13
is it possible to download ring tones on a800 with data cable	acronus	Samsung Media, Games, Ringtones	5	02-07-2006 06:09
Benq A500. Is it possible to be unlocked ?	doctormike	FuriouS II	0	08-18-2005 20:01
Is it possible to be from a battery?	stefanovmm	Hardware Repair by brands	6	11-30-2004 03:57
Is it possible to remove SIMLOCK on NEC DB 2000?	Bogi	Various	0	06-23-2002 17:36

09-30-2009, 06:09	#2 (permalink)
ru_dee Freak Poster Join Date: Nov 2008 Location: ina 4 sure Posts: 156 Member: 911645 Status: Offline Thanks Meter: 19	pm n imei back-up were conducted after CS, i think it won't help -FYI the phone is PA_SL2, got pm308 protected- restoring pm n imei back-up, then, will damage superdongle, and causing wd timer active

09-30-2009, 07:02	#3 (permalink)
neo_2005 Freak Poster Join Date: May 2004 Location: Silent Mode Age: 39 Posts: 448 Member: 65656 Status: Offline Thanks Meter: 91	with other version not protected SD

09-30-2009, 20:06	#5 (permalink)
Andra No Life Poster Join Date: Feb 2005 Location: AD Posts: 4,665 Member: 976728 Status: Offline Sonork: 1589709 Thanks Meter: 4,775	flash with unprotected frimware , and restore your backup . br,

10-01-2009, 03:21	#7 (permalink)
JHUNpanabO Freak Poster Join Date: Apr 2006 Location: PH-unlocktoys Posts: 497 Member: 265729 Status: Offline Thanks Meter: 144	flash your phone another version....