Nokia 5130c Only SUPERDONGL problem. will be fixed by Mxkey? - GSM-Forum

hussainafridi · 02-09-2010, 11:08

Nokia 5130c Only SUPERDONGL problem. will be fixed by Mxkey?
==================================

his is SL3 phone(Simlock2 format).
- Avoid SW Downgrade & 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 passed
SECURITY_TEST passed

TimeStamp: 2009-08-05T07:40:36Z
SW Version: 06.94
Variant Version: 010
ProductProfile: RM495_0571952_06.94_010.spr
Simlock: 0571952_simlock.bin

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

xannix_7575 · 02-09-2010, 11:22

1. open: service> imei & security> REPAIR SD(if DONE proced to atep 2)
2. open: PM> SUPER SD
3. tick LOAD FROM FILE (select PM 1 and 309 area only)
4. tick WRITE

when PM writing is DONE
to check if phone is OK, tick again BUS CHECK

GOOD LUCK

hussainafridi · 02-09-2010, 11:27

Good pm with 1 and 309 area needed ?
-----------------------

ngatijo · 02-09-2010, 11:31

good pm please..........

bk.gsm · 02-09-2010, 11:33

Quote:

Originally Posted by hussainafridi

Good pm with 1 and 309 area needed ?
-----------------------

Quote:

Originally Posted by ettykom

good pm please..........

here it's full good pm:

http://www.zshare.net/download/7233646573190e18/

b.r.

xannix_7575 · 02-09-2010, 11:37

Quote:

Originally Posted by hussainafridi

Good pm with 1 and 309 area needed ?
-----------------------

heres your PM with 1 and 309 only http://www.megaupload.com/?d=TS1KWBYD

and here http://rapidshare.com/files/34812952...5_5130.pm.html

MYUNLOCKING · 02-09-2010, 11:55

sl3 phones supported??

mukeshdurg · 02-09-2010, 12:12

Quote:

Originally Posted by mobileclinic_14

sl3 phones supported??

yes that is the corect information

hussainafridi · 02-09-2010, 12:17

So we wait for good answer. try or not for fixed this problem, ???????????????

bk.gsm · 02-09-2010, 12:39

Quote:

Originally Posted by hussainafridi

So we wait for good answer. try or not for fixed this problem, ???????????????

u can fix only SD data for that module but u can't fix sl data cuz it's PA SL3

but before repairing SD read all backup

b.r.

hussainafridi · 02-09-2010, 13:05

Yes don my problem, thanks @ xannix_7575 and @the scavenger

Phone Type: RM-495 (Nokia 5130c-2)
SW Version: V 06.94 21-07-09 RM-495 (c) Nokia
Imei plain: 35422303780449-9
Product Code: 0571952
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
SIMLOCK_TEST passed
SECURITY_TEST passed

TimeStamp: 2009-08-05T07:40:36Z
SW Version: 06.94
Variant Version: 010
ProductProfile: RM495_0571952_06.94_010.spr
Simlock: 0571952_simlock.bin

Imei net: 354223037804499
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
FULL FACTORY... OK
USER DATA... OK
LEAVE FACTORY... OK
SERVICE CENTER... OK
SOFTWARE UPGRADE... OK
PRODUCTION TUNING... OK
Reset User Code (to default:12345) ... OK
Completed in 5.875 s

billal930 · 02-09-2010, 13:08

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.11985, Date: 03-02-2010
APE Data :
SYSTEM ASIC ID: 17100701 [OMAP1710 ver: 1.1]
ASIC MODE ID: 00
PUBLIC ID: F042C4012258B474E505C08E8E81323025D86C4E
ROOT KEY HASH: 2C05369F57CC3C4CF9E783E83D9B512B00000000
ROM ID: AB5E4ADB27A06946
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006000C192101002200 [RAP3G ver: PA 2.2]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 1F800107746B5D514513253695A3E241BC36CB82
ASIC MODE ID: 00
ROOT KEY HASH: E9EFF4BFAA5393217CA6B17755FC3E14
ROM ID: F28A211FCEA7B19D
SecondaryBoot: rap3gv2_2nd.fg [BB5] version: 1.21.0 revision: 0.0 size: 0x3D00
Supported RAP Ids: 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200
FlashID0: 00EC 2250 - 0000 0121 [Samsung K8S6415ETB,64 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.40.0 revision: 0.0 size: 0x22C10
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: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D
SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500
Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
FlashID0: 0098 0036 - 00A5 00C0 [Toshiba 512 DDP NAND,512 Mbits] type: NAND,APE
ALG [35]: OMAP1610 GBBM-1.8.1 ALG
ExtBUSC: 0002 0000 0006 0000 0000 0000 0000 0000
Algorithm: h3_sam_nand_gbbm.fg [OMAP1610 GBBM-1.8.1 ALG] version: 1.33.0 revision: 0.0 size: 0xA908
Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
APE PAPUBKEYS HASH: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D
Original Imei: 35696301667219
Original Product code: 0524110
Bluetooth ID: 001C9A473753

Phone Type: RM-84 (Nokia N70)
SW Version: V 05wk07v48.1 28-08-07 RM-84 (c) Nokia.
Imei plain: 35696301667219-7
Product Code: 0524086
ApeCoreSw: V 5.0737.3.0.1 13-09-07 RM-84 (C)Nokia
ApeVariant: V 5.0737.3.0.1-29.01 13-09-07 RM-84 (c)Nokia.
Language Pack:
- not available.

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

Imei net: 356963016672197
Version: SIMLOCK SERVER VERSION 58
Counter: 0/3, 0/10

CONFIG_DATA: FFFFFFFFFFFFFFFF
PROFILE_BITS: FFFFFFFFFFFFFFFF

BLOCK 1: 1=CORRUPTED

how can i do

Muhammadasif655 · 02-09-2010, 13:20

Quote:

Originally Posted by billal930

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.11985, Date: 03-02-2010
APE Data :
SYSTEM ASIC ID: 17100701 [OMAP1710 ver: 1.1]
ASIC MODE ID: 00
PUBLIC ID: F042C4012258B474E505C08E8E81323025D86C4E
ROOT KEY HASH: 2C05369F57CC3C4CF9E783E83D9B512B00000000
ROM ID: AB5E4ADB27A06946
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006000C192101002200 [RAP3G ver: PA 2.2]
EM0 ID: 00000232
EM1 ID: 00000353
PUBLIC ID: 1F800107746B5D514513253695A3E241BC36CB82
ASIC MODE ID: 00
ROOT KEY HASH: E9EFF4BFAA5393217CA6B17755FC3E14
ROM ID: F28A211FCEA7B19D
SecondaryBoot: rap3gv2_2nd.fg [BB5] version: 1.21.0 revision: 0.0 size: 0x3D00
Supported RAP Ids: 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200
FlashID0: 00EC 2250 - 0000 0121 [Samsung K8S6415ETB,64 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.40.0 revision: 0.0 size: 0x22C10
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: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D
SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500
Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
FlashID0: 0098 0036 - 00A5 00C0 [Toshiba 512 DDP NAND,512 Mbits] type: NAND,APE
ALG [35]: OMAP1610 GBBM-1.8.1 ALG
ExtBUSC: 0002 0000 0006 0000 0000 0000 0000 0000
Algorithm: h3_sam_nand_gbbm.fg [OMAP1610 GBBM-1.8.1 ALG] version: 1.33.0 revision: 0.0 size: 0xA908
Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708
APE PAPUBKEYS HASH: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D
Original Imei: 35696301667219
Original Product code: 0524110
Bluetooth ID: 001C9A473753

Phone Type: RM-84 (Nokia N70)
SW Version: V 05wk07v48.1 28-08-07 RM-84 (c) Nokia.
Imei plain: 35696301667219-7
Product Code: 0524086
ApeCoreSw: V 5.0737.3.0.1 13-09-07 RM-84 (C)Nokia
ApeVariant: V 5.0737.3.0.1-29.01 13-09-07 RM-84 (c)Nokia.
Language Pack:
- not available.

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

Imei net: 356963016672197
Version: SIMLOCK SERVER VERSION 58
Counter: 0/3, 0/10

CONFIG_DATA: FFFFFFFFFFFFFFFF
PROFILE_BITS: FFFFFFFFFFFFFFFF

BLOCK 1: 1=CORRUPTED

how can i do

fuly flash with latest virsion

your problem will be solved

neo_2005 · 02-09-2010, 13:31

5130c / sl3 can repair with magic mx-key
but,

only this can repair

PHP Code:

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

before backup rpl dan simlock (easy backup)

Code:

SIMLOCK seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST passed

after sd_k repair,

Code:

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

and

Code:

CONFIG_DATA: FFFFFFFFFFFFFFFF
PROFILE_BITS: FFFFFFFFFFFFFFFF

BLOCK 1: 1=CORRUPTED

restore backup rpl & simlock.

Code:

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

then super-SD dan write pm (modif ur pm).
done.

if before,

Code:

 SIMLOCK invalid!

REPAIR 1ST , now with other tools.

raselopu · 02-09-2010, 13:39

billal930 >>>>>>>>> You just Repair SL in IMEI & Security.

02-09-2010, 11:08	#1 (permalink)
hussainafridi No Life Poster Join Date: Jan 2008 Location: peshawar Posts: 1,172 Member: 668816 Status: Offline Sonork: no Thanks Meter: 182	Nokia 5130c Only SUPERDONGL problem. will be fixed by Mxkey? Nokia 5130c Only SUPERDONGL problem. will be fixed by Mxkey? ================================== his is SL3 phone(Simlock2 format). - Avoid SW Downgrade & 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 passed SECURITY_TEST passed TimeStamp: 2009-08-05T07:40:36Z SW Version: 06.94 Variant Version: 010 ProductProfile: RM495_0571952_06.94_010.spr Simlock: 0571952_simlock.bin Imei net: 354223037804499 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

02-09-2010, 11:22	#2 (permalink)
xannix_7575 Freak Poster Join Date: Aug 2008 Location: PhiIippines Posts: 377 Member: 847117 Status: Offline Thanks Meter: 71	1. open: service> imei & security> REPAIR SD(if DONE proced to atep 2) 2. open: PM> SUPER SD 3. tick LOAD FROM FILE (select PM 1 and 309 area only) 4. tick WRITE when PM writing is DONE to check if phone is OK, tick again BUS CHECK GOOD LUCK Last edited by xannix_7575; 02-09-2010 at 11:27.

02-09-2010, 13:31	#14 (permalink)
neo_2005 Freak Poster Join Date: May 2004 Location: Silent Mode Age: 39 Posts: 448 Member: 65656 Status: Offline Thanks Meter: 91	5130c / sl3 can repair with magic mx-key but, only this can repair PHP Code: `SIMLOCK seems to be valid SUPERDONGLE_KEY invalid! - WD timer enabled, phone will reboot itself after 3 min. SIMLOCK_TEST passed SECURITY_TEST passed` before backup rpl dan simlock (easy backup) Code: SIMLOCK seems to be valid SIMLOCK_TEST passed SECURITY_TEST passed after sd_k repair, Code: SIMLOCK seems to be valid SUPERDONGLE_KEY seems to be valid SIMLOCK_TEST passed SECURITY_TEST failed! and Code: CONFIG_DATA: FFFFFFFFFFFFFFFF PROFILE_BITS: FFFFFFFFFFFFFFFF BLOCK 1: 1=CORRUPTED restore backup rpl & simlock. Code: SIMLOCK seems to be valid SUPERDONGLE_KEY seems to be valid SIMLOCK_TEST passed SECURITY_TEST passed then super-SD dan write pm (modif ur pm). done. if before, Code: SIMLOCK invalid! REPAIR 1ST , now with other tools.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
nokia 6124c-1 rm-422 by vodafone cant be unlocked by mxkey (ANSWERED)	med26	MXKEY Nokia Flasher and Unlocker (by Alim Hape)	3	07-17-2011 21:37
Do you think will be nice if MXKEY will make ATF as supported interface ?	MANOLE	Advance-Box	229	11-28-2010 12:10
- Stop Complaing - Server Will Be Fixed -	Kevbodian	Dongle Problems (USB-Smart)	23	09-04-2006 01:42
When will be fixed bug?!?	systemworm	JAF Xtras	5	07-30-2006 07:29
When IT WIll BE FIXED...............:-(	.::BHATTI::.	FuriouS II	0	12-29-2005 17:02

02-09-2010, 11:27	#3 (permalink)
hussainafridi No Life Poster Join Date: Jan 2008 Location: peshawar Posts: 1,172 Member: 668816 Status: Offline Sonork: no Thanks Meter: 182	Good pm with 1 and 309 area needed ? -----------------------

02-09-2010, 11:31	#4 (permalink)
ngatijo Junior Member Join Date: Mar 2006 Location: Ngemut Penthil Posts: 9 Member: 241467 Status: Offline Thanks Meter: 0	good pm please..........

02-09-2010, 11:55	#7 (permalink)
MYUNLOCKING No Life Poster Join Date: Apr 2008 Location: karachi .. Age: 38 Posts: 3,442 Member: 749969 Status: Offline Sonork: 100.1581886 Thanks Meter: 771	sl3 phones supported??

02-09-2010, 12:17	#9 (permalink)
hussainafridi No Life Poster Join Date: Jan 2008 Location: peshawar Posts: 1,172 Member: 668816 Status: Offline Sonork: no Thanks Meter: 182	So we wait for good answer. try or not for fixed this problem, ???????????????

02-09-2010, 13:05	#11 (permalink)
hussainafridi No Life Poster Join Date: Jan 2008 Location: peshawar Posts: 1,172 Member: 668816 Status: Offline Sonork: no Thanks Meter: 182	Yes don my problem, thanks @ xannix_7575 and @the scavenger Phone Type: RM-495 (Nokia 5130c-2) SW Version: V 06.94 21-07-09 RM-495 (c) Nokia Imei plain: 35422303780449-9 Product Code: 0571952 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 SIMLOCK_TEST passed SECURITY_TEST passed TimeStamp: 2009-08-05T07:40:36Z SW Version: 06.94 Variant Version: 010 ProductProfile: RM495_0571952_06.94_010.spr Simlock: 0571952_simlock.bin Imei net: 354223037804499 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 FULL FACTORY... OK USER DATA... OK LEAVE FACTORY... OK SERVICE CENTER... OK SOFTWARE UPGRADE... OK PRODUCTION TUNING... OK Reset User Code (to default:12345) ... OK Completed in 5.875 s

02-09-2010, 13:08	#12 (permalink)
billal930 Freak Poster Join Date: Jan 2007 Location: DREAM HOME Posts: 307 Member: 429744 Status: Offline Thanks Meter: 93	Using device: UFS_USB V2.8 (c) SarasSoft 2007. Library version: 1.0.0.11985, Date: 03-02-2010 APE Data : SYSTEM ASIC ID: 17100701 [OMAP1710 ver: 1.1] ASIC MODE ID: 00 PUBLIC ID: F042C4012258B474E505C08E8E81323025D86C4E ROOT KEY HASH: 2C05369F57CC3C4CF9E783E83D9B512B00000000 ROM ID: AB5E4ADB27A06946 RAP Data : SYSTEM ASIC ID: 000000010000022600010006000C192101002200 [RAP3G ver: PA 2.2] EM0 ID: 00000232 EM1 ID: 00000353 PUBLIC ID: 1F800107746B5D514513253695A3E241BC36CB82 ASIC MODE ID: 00 ROOT KEY HASH: E9EFF4BFAA5393217CA6B17755FC3E14 ROM ID: F28A211FCEA7B19D SecondaryBoot: rap3gv2_2nd.fg [BB5] version: 1.21.0 revision: 0.0 size: 0x3D00 Supported RAP Ids: 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200 FlashID0: 00EC 2250 - 0000 0121 [Samsung K8S6415ETB,64 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.40.0 revision: 0.0 size: 0x22C10 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: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D SecondaryBoot: helen3_2nd.fg [BB5] version: 1.35.0 revision: 0.0 size: 0x3500 Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708 FlashID0: 0098 0036 - 00A5 00C0 [Toshiba 512 DDP NAND,512 Mbits] type: NAND,APE ALG [35]: OMAP1610 GBBM-1.8.1 ALG ExtBUSC: 0002 0000 0006 0000 0000 0000 0000 0000 Algorithm: h3_sam_nand_gbbm.fg [OMAP1610 GBBM-1.8.1 ALG] version: 1.33.0 revision: 0.0 size: 0xA908 Supported APE Ids: 17100700, 17100701, 17100702, 17100703, 17100704, 17100708 APE PAPUBKEYS HASH: 0F72BF9DE5D6711B3B1133EBCAB5914FA419C78D Original Imei: 35696301667219 Original Product code: 0524110 Bluetooth ID: 001C9A473753 Phone Type: RM-84 (Nokia N70) SW Version: V 05wk07v48.1 28-08-07 RM-84 (c) Nokia. Imei plain: 35696301667219-7 Product Code: 0524086 ApeCoreSw: V 5.0737.3.0.1 13-09-07 RM-84 (C)Nokia ApeVariant: V 5.0737.3.0.1-29.01 13-09-07 RM-84 (c)Nokia. Language Pack: - not available. SIMLOCK seems to be valid SUPERDONGLE_KEY seems to be valid SIMLOCK_TEST passed SECURITY_TEST failed! Imei net: 356963016672197 Version: SIMLOCK SERVER VERSION 58 Counter: 0/3, 0/10 CONFIG_DATA: FFFFFFFFFFFFFFFF PROFILE_BITS: FFFFFFFFFFFFFFFF BLOCK 1: 1=CORRUPTED how can i do

02-09-2010, 13:39	#15 (permalink)
raselopu No Life Poster Join Date: Apr 2007 Location: Motalib Plaza,Dhaka,Bangladesh Age: 39 Posts: 806 Member: 485407 Status: Offline Sonork: 100.1580486 Thanks Meter: 183	billal930 >>>>>>>>> You just Repair SL in IMEI & Security.