E52, 6303i can't be flashed, can't generate SHA file - GSM-Forum

PSG · 10-11-2011, 15:42

my hti updated to 0.24 with mxkey:

System:
» OS version: 6.1.7600.16850(x86)
Main:
» mobileEx.exe, version: 3.4.0.9170, date: 7-10-2011
» mobileEx.lib, version: 1.0.0.12920, date: 08-10-2011
Modules:
» alc.mx, library version: 1.0.0.17, module version: 1.01, date: 23-12-2010
» bb.mx, library version: 1.0.0.850, module version: 1.05, date: 03-10-2011
» ccs.mx, library version: 1.0.0.1288, module version: 1.02, date: 07-11-2010
» htc.mx, library version: 1.0.0.320, module version: 1.03, date: 07-11-2010
» huw.mx, library version: 1.0.0.109, module version: 1.02, date: 06-05-2010
» nk.mx, library version: 1.0.0.19045, module version: 1.22, date: 08-10-2011
» qcd.mx, library version: 1.0.0.1994, module version: 1.02, date: 01-10-2011
» siem.mx, library version: 1.0.0.293, module version: 1.01 B, date: 06-05-2010
» vcom.mx, library version: 1.0.0.1326, module version: 1.04, date: 23-06-2010
» voda.mx, library version: 1.0.0.43, module version: 1.00, date: 06-05-2010
» zte.mx, library version: 1.0.0.23, module version: 1.00, date: 20-11-2010
Loaded Drivers:
» Nokia NMWCD, version: 7.1.32.70, date: 6-27-2011
» MXKEY TEAM WinUSB, version: 3.5.0.0, date: 9-6-2011

PROBLEMS:

1. nokia conect drivers are too old becasue i can't flash via USB E52 or 6303i. i used nokia phoenix Phoenix Service Software 2011.38.003.46817 and flashed via USB no problem but before in mxkey i've got error on second boot

2. i can't get SHA file for E52 via USb or FBUS when option verify secure data is checked (without option checked i can get sha file but i don't know is it worth to calc it. i will not do it myself i have to pay for it.

3. i have same problems with 6303i rm-638 read via usb not possible (old loaders in mxkey, can't even flash via mxkey) read via fbus same problem as with E52.
both E52 and 6303i are working OK, no reboots period, no probem with watch dog.

Request:
1. first of all you should update nokia drivers, aktual is USB Cable Driver version: 7.1.45.0 but mxkey used: 7.1.32.70 which are too old to flash via USB different E52 and 6303i
2. how to be sure generated SHA file is OK?

SCAN via FBUS:

Phone type: RM-469 (Nokia E52-1)
SW version: V ICPR82_10w22.10 03-01-11 RM-469 (c) Nokia
Imei plain: 359327034XXXXXXX
Product code: 0593004
Battery voltage: 4839 mV, current: 112 mA
ApeCoreSw: 054.003
Language Pack:
- not available.

Detected as PA_SL3 phone.
- 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: 3593270XXXXXXX
Version: SIMLOCK SERVER
Provider: Idea (Polska Telefonia Komórkowa Centertel Sp. Z.o.o) , Country: Poland
Counter: 0/3, 0/10

CONFIG_DATA: 2600300000000000
PROFILE_BITS: 8000000000000000

BLOCK1: 1=CLOSED(MCCMNC), DATA=26003F [Poland-Idea (Polska Telefonia Komórkowa Centertel Sp. Z.o.o) ]

BUS CHECK via FBUS:

MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 0], SN: C08552ED
Using device: HTI, FW ver: 00.24, SN: 0000C7C1
Connection status: UHCI:HUB:USB 2.00 (Full-speed)
Driver: WinUSB, ver: 3.5.0.0 , NTMP ver: 6.1.7600.16385
Module ver: 1.0.0.19045(08-10-2011), Library ver: 1.0.0.12920(08-10-2011)
CMT Data :
SYSTEM ASIC ID: 000000030000022600010007600C192102011104 [RAPUYAMA ver: 1.1]
EM0 ID: 00001040
EM1 ID: 00001030
PUBLIC ID: 1CC00003E76C03445E77820FBD5ED61D464D4704
ASIC MODE ID: 00
ROOT KEY HASH: 25B977A055BE9B5DEC0C38A2A279C695
ROM ID: 3E273BF637BE26FA
SecondaryBoot: RAPUv11_2nd.fg [BB5] version: 11.24.0 revision: 3.0 size: 0x3B40
Supported Ids: 4003192102001104, 400C192102001104, 6003192102001104, 600C192102001104, 6003192102011104, 600C192102011104, 6003192102021104, 600C192102021104, 6003192102031104, 600C192102031104
eBB5ProtocolType: NEW
TransmissionMode: DDR&TX2
Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT
Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT
Storage2: 0020 0040 - 0000 0031 [ST NAND KAT00F00RA] type: FLASH,NOR, asic:CMT
Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT
Storage4: 0020 0040 - 0000 0031 [ST NAND KAT00F00RA] type: FLASH,MuxOneNAND, asic:CMT
Suggested algorithm: XSR 1.6
Algorithm: RAPUv11_XSR17_alg.fg [XSR 1.6] version: 11.24.0 revision: 3.0 size: 0xC6B13
Supported Ids: 4003192102001104, 400C192102001104, 6003192102001104, 600C192102001104, 6003192102011104, 600C192102011104, 6003192102021104, 600C192102021104, 6003192102031104, 600C192102031104
TransmissionMode: DDR&TX2
FUR: Adding Asic CMT as client OK
CMT PAPUBKEYS HASH: 85F252E351E225CAFC4DFBC8041EABD2823E3500
Original Imei: 359327XXXXXXX
Original Product code: 0591462
Bluetooth ID: A87B39D43920
SIMLOCK PA identifier:
[0] PA_SIMLOC30

Phone type: RM-469 (Nokia E52-1)
SW version: V ICPR82_10w22.10 03-01-11 RM-469 (c) Nokia
Imei plain: 35932703XXXXXXX
Product code: 0593004
Battery voltage: 4839 mV, current: 54 mA
ApeCoreSw: 054.003
Language Pack:
- not available.

Detected as PA_SL3 phone.
- 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: 35932703XXXXXX
Version: SIMLOCK SERVER
Provider: Idea (Polska Telefonia Komórkowa Centertel Sp. Z.o.o) , Country: Poland
Counter: 0/3, 0/10

CONFIG_DATA: 2600300000000000
PROFILE_BITS: 8000000000000000

BLOCK1: 1=CLOSED(MCCMNC), DATA=26003F [Poland-Idea (Polska Telefonia Komórkowa Centertel Sp. Z.o.o) ]

SL3 logger via FBUS with checked ON verify secure data (without it i can get sha file)

MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 0], SN: C08552ED
Using device: HTI, FW ver: 00.24, SN: 0000C7C1
Connection status: UHCI:HUB:USB 2.00 (Full-speed)
Driver: WinUSB, ver: 3.5.0.0 , NTMP ver: 6.1.7600.16385
Module ver: 1.0.0.19045(08-10-2011), Library ver: 1.0.0.12920(08-10-2011)

Phone type: RM-469 (Nokia E52-1)
SW version: V ICPR82_10w22.10 03-01-11 RM-469 (c) Nokia
ApeCoreSw: 054.003

SYSTEM ASIC ID: 000000030000022600010007600C192102011104 [RAPUYAMA ver: 1.1]
ROOT KEY HASH: 25B977A055BE9B5DEC0C38A2A279C695
ROM ID: 3E273BF637BE26FA
SecondaryBoot: RAPUv11_2nd.fg [BB5] version: 11.10.0 revision: 3.0 size: 0x3B40
Supported Ids: 4003192102001104, 400C192102001104, 6003192102001104, 600C192102001104, 6003192102011104, 600C192102011104, 6003192102021104, 600C192102021104, 6003192102031104, 600C192102031104
eBB5ProtocolType: NEW
PUBLIC ID: 1CC00003E76C03445E77820FBD5ED61D464D4704
PRIVATE ID: BB2F47D3CDC1189CF885C4DEDD2AC855463A8085
SEC ROM CRC: 37BE26FA
Restarting phone ...

Verifying secure data ...Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted !
failed
:

PSG · 10-11-2011, 17:07

E52 working ok, no problem. how is that possible SL3 SHA file read via fbus from same phone could have different HASH?

[IMEI]
3593270XXXXXXX
[TARGET_HASH]
66406567D9BA05A88EB0FA5D1A725854A786F9BE

or

[IMEI]
3593270XXXXXXX
[TARGET_HASH]
CC0FD55249F07DE18C6FF0EDF4397240B96CB501

or

[IMEI]
3593270XXXXXXXXX
[TARGET_HASH]
26517A32AF60AA68B4468EED4332F734D014EACC

what is this sh it ?

PSG · 10-12-2011, 12:40

why i can't get same code? i get several times same HASH but after some time HASH different.
phone work ok, i checked on 6303i, and 6700c and same problem with checked option verify data i can't get SHA file, with unchecked option i get sometimes different HASH.
i read via usb and Fbus to check

10-11-2011, 15:42	#1 (permalink)
PSG No Life Poster Join Date: May 2003 Location: POLAND Posts: 1,262 Member: 27761 Status: Offline Thanks Meter: 55	E52, 6303i can't generate SHA file my hti updated to 0.24 with mxkey: System: » OS version: 6.1.7600.16850(x86) Main: » mobileEx.exe, version: 3.4.0.9170, date: 7-10-2011 » mobileEx.lib, version: 1.0.0.12920, date: 08-10-2011 Modules: » alc.mx, library version: 1.0.0.17, module version: 1.01, date: 23-12-2010 » bb.mx, library version: 1.0.0.850, module version: 1.05, date: 03-10-2011 » ccs.mx, library version: 1.0.0.1288, module version: 1.02, date: 07-11-2010 » htc.mx, library version: 1.0.0.320, module version: 1.03, date: 07-11-2010 » huw.mx, library version: 1.0.0.109, module version: 1.02, date: 06-05-2010 » nk.mx, library version: 1.0.0.19045, module version: 1.22, date: 08-10-2011 » qcd.mx, library version: 1.0.0.1994, module version: 1.02, date: 01-10-2011 » siem.mx, library version: 1.0.0.293, module version: 1.01 B, date: 06-05-2010 » vcom.mx, library version: 1.0.0.1326, module version: 1.04, date: 23-06-2010 » voda.mx, library version: 1.0.0.43, module version: 1.00, date: 06-05-2010 » zte.mx, library version: 1.0.0.23, module version: 1.00, date: 20-11-2010 Loaded Drivers: » Nokia NMWCD, version: 7.1.32.70, date: 6-27-2011 » MXKEY TEAM WinUSB, version: 3.5.0.0, date: 9-6-2011 PROBLEMS: 1. nokia conect drivers are too old becasue i can't flash via USB E52 or 6303i. i used nokia phoenix Phoenix Service Software 2011.38.003.46817 and flashed via USB no problem but before in mxkey i've got error on second boot 2. i can't get SHA file for E52 via USb or FBUS when option verify secure data is checked (without option checked i can get sha file but i don't know is it worth to calc it. i will not do it myself i have to pay for it. 3. i have same problems with 6303i rm-638 read via usb not possible (old loaders in mxkey, can't even flash via mxkey) read via fbus same problem as with E52. both E52 and 6303i are working OK, no reboots period, no probem with watch dog. Request: 1. first of all you should update nokia drivers, aktual is USB Cable Driver version: 7.1.45.0 but mxkey used: 7.1.32.70 which are too old to flash via USB different E52 and 6303i 2. how to be sure generated SHA file is OK? SCAN via FBUS: Phone type: RM-469 (Nokia E52-1) SW version: V ICPR82_10w22.10 03-01-11 RM-469 (c) Nokia Imei plain: 359327034XXXXXXX Product code: 0593004 Battery voltage: 4839 mV, current: 112 mA ApeCoreSw: 054.003 Language Pack: - not available. Detected as PA_SL3 phone. - 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: 3593270XXXXXXX Version: SIMLOCK SERVER Provider: Idea (Polska Telefonia Komórkowa Centertel Sp. Z.o.o) , Country: Poland Counter: 0/3, 0/10 CONFIG_DATA: 2600300000000000 PROFILE_BITS: 8000000000000000 BLOCK1: 1=CLOSED(MCCMNC), DATA=26003F [Poland-Idea (Polska Telefonia Komórkowa Centertel Sp. Z.o.o) ] BUS CHECK via FBUS: MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 0], SN: C08552ED Using device: HTI, FW ver: 00.24, SN: 0000C7C1 Connection status: UHCI:HUB:USB 2.00 (Full-speed) Driver: WinUSB, ver: 3.5.0.0 , NTMP ver: 6.1.7600.16385 Module ver: 1.0.0.19045(08-10-2011), Library ver: 1.0.0.12920(08-10-2011) CMT Data : SYSTEM ASIC ID: 000000030000022600010007600C192102011104 [RAPUYAMA ver: 1.1] EM0 ID: 00001040 EM1 ID: 00001030 PUBLIC ID: 1CC00003E76C03445E77820FBD5ED61D464D4704 ASIC MODE ID: 00 ROOT KEY HASH: 25B977A055BE9B5DEC0C38A2A279C695 ROM ID: 3E273BF637BE26FA SecondaryBoot: RAPUv11_2nd.fg [BB5] version: 11.24.0 revision: 3.0 size: 0x3B40 Supported Ids: 4003192102001104, 400C192102001104, 6003192102001104, 600C192102001104, 6003192102011104, 600C192102011104, 6003192102021104, 600C192102021104, 6003192102031104, 600C192102031104 eBB5ProtocolType: NEW TransmissionMode: DDR&TX2 Storage0: 0000 0000 - 0000 0000 type: RAM, asic:CMT Storage1: FFFF 0000 - 0000 0000 type: MMC, asic:CMT Storage2: 0020 0040 - 0000 0031 [ST NAND KAT00F00RA] type: FLASH,NOR, asic:CMT Storage3: 0000 0001 - 0000 0000 [unused/removed] type: FLASH,NOR, asic:CMT Storage4: 0020 0040 - 0000 0031 [ST NAND KAT00F00RA] type: FLASH,MuxOneNAND, asic:CMT Suggested algorithm: XSR 1.6 Algorithm: RAPUv11_XSR17_alg.fg [XSR 1.6] version: 11.24.0 revision: 3.0 size: 0xC6B13 Supported Ids: 4003192102001104, 400C192102001104, 6003192102001104, 600C192102001104, 6003192102011104, 600C192102011104, 6003192102021104, 600C192102021104, 6003192102031104, 600C192102031104 TransmissionMode: DDR&TX2 FUR: Adding Asic CMT as client OK CMT PAPUBKEYS HASH: 85F252E351E225CAFC4DFBC8041EABD2823E3500 Original Imei: 359327XXXXXXX Original Product code: 0591462 Bluetooth ID: A87B39D43920 SIMLOCK PA identifier: [0] PA_SIMLOC30 Phone type: RM-469 (Nokia E52-1) SW version: V ICPR82_10w22.10 03-01-11 RM-469 (c) Nokia Imei plain: 35932703XXXXXXX Product code: 0593004 Battery voltage: 4839 mV, current: 54 mA ApeCoreSw: 054.003 Language Pack: - not available. Detected as PA_SL3 phone. - 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: 35932703XXXXXX Version: SIMLOCK SERVER Provider: Idea (Polska Telefonia Komórkowa Centertel Sp. Z.o.o) , Country: Poland Counter: 0/3, 0/10 CONFIG_DATA: 2600300000000000 PROFILE_BITS: 8000000000000000 BLOCK1: 1=CLOSED(MCCMNC), DATA=26003F [Poland-Idea (Polska Telefonia Komórkowa Centertel Sp. Z.o.o) ] SL3 logger via FBUS with checked ON verify secure data (without it i can get sha file) MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 0], SN: C08552ED Using device: HTI, FW ver: 00.24, SN: 0000C7C1 Connection status: UHCI:HUB:USB 2.00 (Full-speed) Driver: WinUSB, ver: 3.5.0.0 , NTMP ver: 6.1.7600.16385 Module ver: 1.0.0.19045(08-10-2011), Library ver: 1.0.0.12920(08-10-2011) Phone type: RM-469 (Nokia E52-1) SW version: V ICPR82_10w22.10 03-01-11 RM-469 (c) Nokia ApeCoreSw: 054.003 SYSTEM ASIC ID: 000000030000022600010007600C192102011104 [RAPUYAMA ver: 1.1] ROOT KEY HASH: 25B977A055BE9B5DEC0C38A2A279C695 ROM ID: 3E273BF637BE26FA SecondaryBoot: RAPUv11_2nd.fg [BB5] version: 11.10.0 revision: 3.0 size: 0x3B40 Supported Ids: 4003192102001104, 400C192102001104, 6003192102001104, 600C192102001104, 6003192102011104, 600C192102011104, 6003192102021104, 600C192102021104, 6003192102031104, 600C192102031104 eBB5ProtocolType: NEW PUBLIC ID: 1CC00003E76C03445E77820FBD5ED61D464D4704 PRIVATE ID: BB2F47D3CDC1189CF885C4DEDD2AC855463A8085 SEC ROM CRC: 37BE26FA Restarting phone ... Verifying secure data ...Bad phones ack on step1, probably SUPERDONGLE_KEY corrupted ! failed : Last edited by PSG; 10-11-2011 at 15:48.

10-11-2011, 17:07	#2 (permalink)
PSG No Life Poster Join Date: May 2003 Location: POLAND Posts: 1,262 Member: 27761 Status: Offline Thanks Meter: 55	E52 working ok, no problem. how is that possible SL3 SHA file read via fbus from same phone could have different HASH? [IMEI] 3593270XXXXXXX [TARGET_HASH] 66406567D9BA05A88EB0FA5D1A725854A786F9BE or [IMEI] 3593270XXXXXXX [TARGET_HASH] CC0FD55249F07DE18C6FF0EDF4397240B96CB501 or [IMEI] 3593270XXXXXXXXX [TARGET_HASH] 26517A32AF60AA68B4468EED4332F734D014EACC what is this sh it ? Last edited by PSG; 10-11-2011 at 17:12.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Successfully Unlocked / Flashed Phones By hwk	..::: Naveed :::..	HWK	4765	01-16-2021 08:54
Thread for reporting damaged files on support area	FractalizeR	HWK	37	08-30-2017 12:29
e52 only vibrate???????? ##	rasheedc007	MXKEY Nokia Flasher and Unlocker (by Alim Hape)	12	06-30-2012 15:19
Synchronize task ended: Some files didnt passed verification, please retry ! ##	jorco_max11	MXKEY Nokia Flasher and Unlocker (by Alim Hape)	9	10-28-2011 07:35
Solution for Updating HTI Flasher / Synchronize Files ##	adnan_taeki	MXKEY Nokia Flasher and Unlocker (by Alim Hape)	2	10-11-2011 02:19

10-12-2011, 12:40	#3 (permalink)
PSG No Life Poster Join Date: May 2003 Location: POLAND Posts: 1,262 Member: 27761 Status: Offline Thanks Meter: 55	why i can't get same code? i get several times same HASH but after some time HASH different. phone work ok, i checked on 6303i, and 6700c and same problem with checked option verify data i can't get SHA file, with unchecked option i get sometimes different HASH. i read via usb and Fbus to check