E50 not accepting RPL Backup MX-Key TEam Help[SOLVED] - GSM-Forum

romeoluv56 · 02-19-2010, 11:54

Mx-Key Team

Phone came to me for a upgradation, while flashing in between i got the error

Error BSI/RX2 ..........

than i flash this phone in JAF it flashed perfectly (Now this is whose problem Mx-Key or Cable, because same cable worked in JAF.)

After that i tried to restore my backed up rpl and its not accepting

can you telll me why ?

here is the log file

Scan Log with 1234.... imei

Quote:

Phone Type: RM-170 (Nokia E50)
SW Version: V 4.41.41 28-06-07 RM-170 (c) Nokia.
Imei plain: 12345610654321-?
Product Code: 0535572
ApeCoreSw: V 07.36.0.0 07-09-2007 RM-170 (c) Nokia
ApeVariant: V 07.36.0.0 07-09-2007 RM-170 03 (c) Nokia
Language Pack:
- not available.

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

Imei plain is invalid !!!
Imei net: 12345610654321?
Version: SIMLOCK SERVER VERSION 63
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

Imei Restore Log

Quote:

RPL: "C:\mobileEx\3.3\data\backup\BB5_35189501138997_BA CK.rpl"
Imei: 35189501138997
Restoring RF/BB DATA from backup ...
Updating RF ...OK
Updating BB ...OK
Updating WARRANTY ...OK
Updating PROD ...OK
Updating BT ...OK
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000352
PUBLIC ID: 2EE0011541310058BC482F11A69EE9237B5BAACB
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 191EC665DFAAF68F
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: 00EC 22FE - 0000 8D21 [Samsung K8S5615ETA,256 Mbits] type: NOR,RAP
FlashID1: 00EC 0030 - 0000 0011 [Samsung K5W1G13ACM-DJ60,1 Gbits] type: ONENAND,RAP
ALG [35]: BB5 ALGORITHM
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: 378E6A71B6975E4F03868F793B3BCC7502219779
NPC verified Ok.
Updating CMT NPC ...OK
Updating CMT VARIANT ...OK
Updating PRODUCTCODE (0535572)... OK
Updating PSN (SJF724073)... OK
Updating HWID (5101)... OK
Updating LOCK ...OK
Certificate programmed successfully !

Phone Type: RM-170 (Nokia E50)
SW Version: V 4.41.41 28-06-07 RM-170 (c) Nokia.
Imei plain: 12345610654321-?
Product Code: 0535572
Language Pack:
- not available.

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

Imei plain is invalid !!!
Imei net: 12345610654321?
Version: SIMLOCK SERVER VERSION 63
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

Please help me its really very urgent, Customer is waiting to collect his handset

Please do the need full

alamgarh · 02-19-2010, 12:01

Quote:

Originally Posted by romeoluv56

Mx-Key Team

Phone came to me for a upgradation, while flashing in between i got the error

Error BSI/RX2 ..........

than i flash this phone in JAF it flashed perfectly (Now this is whose problem Mx-Key or Cable, because same cable worked in JAF.)

After that i tried to restore my backed up rpl and its not accepting

can you telll me why ?

here is the log file

Scan Log with 1234.... imei

Imei Restore Log

Please help me its really very urgent, Customer is waiting to collect his handset

Please do the need full

dont restore it just write rpl and give it backup rpl then all will be ok.

romeoluv56 · 02-19-2010, 12:15

i tried that also but not working

romeoluv56 · 02-19-2010, 15:16

Mx team please help its very urgent

kidgz · 02-19-2010, 15:25

try to use bck_rpl on JAF progdata

not on the MXkey back up

prince_arsalan · 02-19-2010, 15:29

Bro Full Erase Your Phone..............
Flash With The Same Product Code On The Back Of Your Phone............
Than Try Restoring Rpl Again..............
Repair Sd..............
Make Super Sd Auth And Write Modified P.m...............

Note: If Problem Still Remains For Sure Your Rpl Back Up Is Not Valid...........

romeoluv56 · 02-19-2010, 15:42

but the phone was in working mode and it came for upgratation, and i have take backup in Mx-key before proceeding to upgrade.

Mohsin-* · 02-19-2010, 15:48

full erase phone
flash with same product code (back on phone sticker)
restore rpl
make simlock repair
make sd repair and write pm with super sd auth

post result

miklaus35 · 02-19-2010, 15:56

If you flash with Jaf, try to restore Crt_Backup.rpl with Jaf. May be the rpl backup with Mx-Key was wrong.

Rabatu · 02-19-2010, 16:10

hope it's ok to give link

complete procedure
http://www.tapgsm.com.ph/showthread....&highlight=E50

or

1. After all back-up, do this open Mxkey go Advance, get Address, uncheck eeprom and tick Erase.

2. Now Flash it with E50-2 or RM-171 not E50-1 or RM-170 this is to have a Restored IMEI DATA not 123456? after this is the result. if you scan it's in RM-170 but log shows RM-171 (why we flash with RM-171? since i personally tried all tricks with restore imei and write PM but no success, only this way will restore in Mxkey tool)

(Now flash with E50-1 or RM-170 and tick Downgrade
check this. check flashfiles i used also. without sim this version will work but with simcard this version is stupid!)

3. so best is use this lower version....tested working! check log SW Version. DL in JAf server
RM170p_06271.C01
RM170p_06271.L31
RM170_APAC2.U03

4. then Fullfactory and format

this time phone is perfectly working!!!

hope this can help you....ENJOY!

pls post feedback if success since this solution is tested

hasnain · 02-19-2010, 18:22

there is something wrong with red fields

[CERT_PROG_DATA_OUT_CMT]
PRODUCTCODE=0557631
PSN=SHG437010
HWID=4120
NPC_DATA_1=CBFC673F0000415000000000000000000000000 00000000000000000303535303830354300000000
NPC_DATA_2=0000000000000000000000009143E09402C8614 761A42B00646F7242000000000B500109E8740058
NPC_DATA_3=C150CCB77307A23628480A369C5EA53A1F6DBD7 DF955715E780159991B4B6EA42F631E8EC0E2B55A
NPC_DATA_4=F3D1C1126720E9DA99B2D575000000000000000 000000000000000000400000047534D0000000000
NPC_DATA_5=3365890361729655FFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFF42545F4944000000
NPC_DATA_6=1F88F49A1C00000000000000000000000000000 0000000000000000000000000574C414E5F494400
NPC_DATA_7=EF9309D41C00000000000000000000000000000 0000000000000000000000000434F4D5F53430000
NPC_DATA_8=5E6A81E61E2D6CBD5471777F84DCDC43F321409 8811F7D5B1DC3A4C5CD13873C880671913638D4D6
NPC_DATA_9=C0DC0108ADD462C1886880D25D69D6DF40C2466 6FC15542C335C3687000C65CAB253884BC7BF50E9
NPC_DATA_10=2C5B6F375C9E39CE29D7DFD5D6C7D916E3925F 340048216C61100538A1BA18B15542F7A58580746B
NPC_DATA_11=90E6F0BFD61693A41EFEF2F56E63C461E6A46B 496384363C86816E8542950A3C2241E35781EACBF5
checksum=-1

just remove red field and only write NPC field like this

[CERT_PROG_DATA_OUT_CMT]
NPC_DATA_1=CBFC673F0000415000000000000000000000000 00000000000000000303535303830354300000000
NPC_DATA_2=0000000000000000000000009143E09402C8614 761A42B00646F7242000000000B500109E8740058
NPC_DATA_3=C150CCB77307A23628480A369C5EA53A1F6DBD7 DF955715E780159991B4B6EA42F631E8EC0E2B55A
NPC_DATA_4=F3D1C1126720E9DA99B2D575000000000000000 000000000000000000400000047534D0000000000
NPC_DATA_5=3365890361729655FFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFF42545F4944000000
NPC_DATA_6=1F88F49A1C00000000000000000000000000000 0000000000000000000000000574C414E5F494400
NPC_DATA_7=EF9309D41C00000000000000000000000000000 0000000000000000000000000434F4D5F53430000
NPC_DATA_8=5E6A81E61E2D6CBD5471777F84DCDC43F321409 8811F7D5B1DC3A4C5CD13873C880671913638D4D6
NPC_DATA_9=C0DC0108ADD462C1886880D25D69D6DF40C2466 6FC15542C335C3687000C65CAB253884BC7BF50E9
NPC_DATA_10=2C5B6F375C9E39CE29D7DFD5D6C7D916E3925F 340048216C61100538A1BA18B15542F7A58580746B
NPC_DATA_11=90E6F0BFD61693A41EFEF2F56E63C461E6A46B 496384363C86816E8542950A3C2241E35781EACBF5
checksum=-1

check this process and post result

Alim Hape · 02-19-2010, 19:11

Hi,

Please do 'BUS Check' then see if 'Original Imei' is not empty, it means that write RPL procedure is OK.
If Original Imei is OK, but Imei plain reseted(12345...) it means phones have a bad firmware.

Best way to restorethe original fw is do 'Image DL' based by 'Original Product code' which is also shown when doing Bus check.
And thats it.

BR.
ALIM

romeoluv56 · 02-20-2010, 15:42

thanks i'll try and let you know by the log

romeoluv56 · 02-20-2010, 16:26

Thanks bro alim problem solved just updating with Product Code thanks for MX-Key here is the log file

Quote:

Imei: 35189501138997
Restoring RF/BB DATA from backup ...
Updating RF ...OK
Updating BB ...OK
Updating WARRANTY ...OK
Updating PROD ...OK
Updating BT ...OK
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000352
PUBLIC ID: 2EE0011541310058BC482F11A69EE9237B5BAACB
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 191EC665DFAAF68F
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: 00EC 22FE - 0000 8D21 [Samsung K8S5615ETA,256 Mbits] type: NOR,RAP
FlashID1: 00EC 0030 - 0000 0011 [Samsung K5W1G13ACM-DJ60,1 Gbits] type: ONENAND,RAP
ALG [35]: BB5 ALGORITHM
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: 378E6A71B6975E4F03868F793B3BCC7502219779
NPC verified Ok.
Updating CMT NPC ...OK
Updating CMT VARIANT ...OK
Updating PRODUCTCODE (0535572)... OK
Updating PSN (SJF724073)... OK
Updating HWID (5101)... OK
Updating LOCK ...OK
Certificate programmed successfully !

Phone Type: RM-170 (Nokia E50)
SW Version: V 4.41.41 28-06-07 RM-170 (c) Nokia.
Imei plain: 35189501138997-8
Product Code: 0535572
Language Pack:
- not available.

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

Imei net: 351895011389978
Version: SIMLOCK SERVER VERSION 63
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

Quote:

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.7705(18-02-2010), 1.0.0.12217(18-02-2010)
RAP Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101001101 [RAPGSM ver: 1.1]
EM0 ID: 00000232
EM1 ID: 00000352
PUBLIC ID: 2EE0011541310058BC482F11A69EE9237B5BAACB
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 191EC665DFAAF68F
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: 00EC 22FE - 0000 8D21 [Samsung K8S5615ETA,256 Mbits] type: NOR,RAP
FlashID1: 00EC 0030 - 0000 0011 [Samsung K5W1G13ACM-DJ60,1 Gbits] type: ONENAND,RAP
ALG [35]: BB5 ALGORITHM
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: 378E6A71B6975E4F03868F793B3BCC7502219779
Original Imei: 35189501138997
Original Product code: 0535572
Bluetooth ID: 00188D6E7555

Phone Type: RM-170 (Nokia E50)
SW Version: V 4.41.41 28-06-07 RM-170 (c) Nokia.
Imei plain: 35189501138997-8
Product Code: 0535572
Language Pack:
- not available.

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

Imei net: 351895011389978
Version: SIMLOCK SERVER VERSION 63
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

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
mx key team help me how to get log txt of mx key	sanjayvikas	MXKEY Nokia Flasher and Unlocker (by Alim Hape)	0	01-22-2010 12:48
help me plz uesr and passeword!!!!!!!!!!! MX-KEY TEAM HELP	>>the boos<<	MXKEY Nokia Flasher and Unlocker (by Alim Hape)	1	01-16-2010 17:17
mx key team help om this error..	stacey-ann	MXKEY Nokia Flasher and Unlocker (by Alim Hape)	0	11-03-2009 08:35
MX-KEY team help all users plzzzzzzzzzzzz	rana_jee	MXKEY Nokia Flasher and Unlocker (by Alim Hape)	7	11-02-2009 13:34
mx key team help me	shama	MXKEY Nokia Flasher and Unlocker (by Alim Hape)	1	08-09-2009 13:39

02-19-2010, 12:15	#3 (permalink)
romeoluv56 Freak Poster Join Date: Nov 2009 Posts: 361 Member: 1170910 Status: Offline Thanks Meter: 76	i tried that also but not working

02-19-2010, 15:16	#4 (permalink)
romeoluv56 Freak Poster Join Date: Nov 2009 Posts: 361 Member: 1170910 Status: Offline Thanks Meter: 76	Mx team please help its very urgent

02-19-2010, 15:25	#5 (permalink)
kidgz Freak Poster Join Date: Jul 2007 Location: Circuitcorner Posts: 463 Member: 551599 Status: Offline Thanks Meter: 139	try to use bck_rpl on JAF progdata not on the MXkey back up

02-19-2010, 15:29	#6 (permalink)
prince_arsalan Freak Poster Join Date: Oct 2007 Posts: 405 Member: 618626 Status: Offline Sonork: 100.1592779 Thanks Meter: 61	Bro Full Erase Your Phone.............. Flash With The Same Product Code On The Back Of Your Phone............ Than Try Restoring Rpl Again.............. Repair Sd.............. Make Super Sd Auth And Write Modified P.m............... Note: If Problem Still Remains For Sure Your Rpl Back Up Is Not Valid...........

02-19-2010, 15:42	#7 (permalink)
romeoluv56 Freak Poster Join Date: Nov 2009 Posts: 361 Member: 1170910 Status: Offline Thanks Meter: 76	but the phone was in working mode and it came for upgratation, and i have take backup in Mx-key before proceeding to upgrade.

02-19-2010, 15:48	#8 (permalink)
Mohsin-* No Life Poster Join Date: Dec 2006 Location: Pakistan/UAE/WorldWide Posts: 8,288 Member: 417298 Status: Offline Sonork: 100.1578269 Thanks Meter: 18,268	full erase phone flash with same product code (back on phone sticker) restore rpl make simlock repair make sd repair and write pm with super sd auth post result

02-19-2010, 15:56	#9 (permalink)
miklaus35 Junior Member Join Date: Dec 2009 Posts: 28 Member: 1175310 Status: Offline Thanks Meter: 3	If you flash with Jaf, try to restore Crt_Backup.rpl with Jaf. May be the rpl backup with Mx-Key was wrong.

02-19-2010, 16:10	#10 (permalink)
Rabatu No Life Poster Join Date: Apr 2009 Posts: 602 Member: 1009679 Status: Offline Thanks Meter: 166	hope it's ok to give link complete procedure http://www.tapgsm.com.ph/showthread....&highlight=E50 or 1. After all back-up, do this open Mxkey go Advance, get Address, uncheck eeprom and tick Erase. 2. Now Flash it with E50-2 or RM-171 not E50-1 or RM-170 this is to have a Restored IMEI DATA not 123456? after this is the result. if you scan it's in RM-170 but log shows RM-171 (why we flash with RM-171? since i personally tried all tricks with restore imei and write PM but no success, only this way will restore in Mxkey tool) (Now flash with E50-1 or RM-170 and tick Downgrade check this. check flashfiles i used also. without sim this version will work but with simcard this version is stupid!) 3. so best is use this lower version....tested working! check log SW Version. DL in JAf server RM170p_06271.C01 RM170p_06271.L31 RM170_APAC2.U03 4. then Fullfactory and format this time phone is perfectly working!!! hope this can help you....ENJOY! pls post feedback if success since this solution is tested

02-19-2010, 18:22	#11 (permalink)
hasnain No Life Poster Join Date: Apr 2006 Location: Pakistan Posts: 4,239 Member: 265626 Status: Offline Sonork: 100.1591486 Thanks Meter: 2,982	there is something wrong with red fields [CERT_PROG_DATA_OUT_CMT] PRODUCTCODE=0557631 PSN=SHG437010 HWID=4120 NPC_DATA_1=CBFC673F0000415000000000000000000000000 00000000000000000303535303830354300000000 NPC_DATA_2=0000000000000000000000009143E09402C8614 761A42B00646F7242000000000B500109E8740058 NPC_DATA_3=C150CCB77307A23628480A369C5EA53A1F6DBD7 DF955715E780159991B4B6EA42F631E8EC0E2B55A NPC_DATA_4=F3D1C1126720E9DA99B2D575000000000000000 000000000000000000400000047534D0000000000 NPC_DATA_5=3365890361729655FFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFF42545F4944000000 NPC_DATA_6=1F88F49A1C00000000000000000000000000000 0000000000000000000000000574C414E5F494400 NPC_DATA_7=EF9309D41C00000000000000000000000000000 0000000000000000000000000434F4D5F53430000 NPC_DATA_8=5E6A81E61E2D6CBD5471777F84DCDC43F321409 8811F7D5B1DC3A4C5CD13873C880671913638D4D6 NPC_DATA_9=C0DC0108ADD462C1886880D25D69D6DF40C2466 6FC15542C335C3687000C65CAB253884BC7BF50E9 NPC_DATA_10=2C5B6F375C9E39CE29D7DFD5D6C7D916E3925F 340048216C61100538A1BA18B15542F7A58580746B NPC_DATA_11=90E6F0BFD61693A41EFEF2F56E63C461E6A46B 496384363C86816E8542950A3C2241E35781EACBF5 checksum=-1 just remove red field and only write NPC field like this [CERT_PROG_DATA_OUT_CMT] NPC_DATA_1=CBFC673F0000415000000000000000000000000 00000000000000000303535303830354300000000 NPC_DATA_2=0000000000000000000000009143E09402C8614 761A42B00646F7242000000000B500109E8740058 NPC_DATA_3=C150CCB77307A23628480A369C5EA53A1F6DBD7 DF955715E780159991B4B6EA42F631E8EC0E2B55A NPC_DATA_4=F3D1C1126720E9DA99B2D575000000000000000 000000000000000000400000047534D0000000000 NPC_DATA_5=3365890361729655FFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFF42545F4944000000 NPC_DATA_6=1F88F49A1C00000000000000000000000000000 0000000000000000000000000574C414E5F494400 NPC_DATA_7=EF9309D41C00000000000000000000000000000 0000000000000000000000000434F4D5F53430000 NPC_DATA_8=5E6A81E61E2D6CBD5471777F84DCDC43F321409 8811F7D5B1DC3A4C5CD13873C880671913638D4D6 NPC_DATA_9=C0DC0108ADD462C1886880D25D69D6DF40C2466 6FC15542C335C3687000C65CAB253884BC7BF50E9 NPC_DATA_10=2C5B6F375C9E39CE29D7DFD5D6C7D916E3925F 340048216C61100538A1BA18B15542F7A58580746B NPC_DATA_11=90E6F0BFD61693A41EFEF2F56E63C461E6A46B 496384363C86816E8542950A3C2241E35781EACBF5 checksum=-1 check this process and post result

02-19-2010, 19:11	#12 (permalink)
Alim Hape No Life Poster Join Date: Nov 2003 Location: 00000000h Age: 42 Posts: 590 Member: 43548 Status: Offline Thanks Meter: 2,192	Hi, Please do 'BUS Check' then see if 'Original Imei' is not empty, it means that write RPL procedure is OK. If Original Imei is OK, but Imei plain reseted(12345...) it means phones have a bad firmware. Best way to restorethe original fw is do 'Image DL' based by 'Original Product code' which is also shown when doing Bus check. And thats it. BR. ALIM

02-20-2010, 15:42	#13 (permalink)
romeoluv56 Freak Poster Join Date: Nov 2009 Posts: 361 Member: 1170910 Status: Offline Thanks Meter: 76	thanks i'll try and let you know by the log