nokia 6500c dead fix bug (ANSWERED)

[sajohaker]

MXKEY Serial: [MxKey HTI FLASHER INTERFACE 3] - C0805BF9
Using device: HTI BOX, FW ver: 00.08
Driver: FTDIBUS, ver: 2.8.14.0 , NTMP ver: 2.8.12.0
Module ver: 1.0.0.17309(31-05-2011), Library ver: 1.0.0.10695(31-05-2011)
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 1DA00107F14D025499F2197ADC0C43C88936B9A6
ASIC MODE ID: 00
ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: rap3gv3_2nd.fg [BB5] version: 10.6.0 revision: 0.0 size: 0x3C40
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
FlashID0: 00EC 220C - 0000 8921 [Samsung K8F1215ETM,512 Mbits] type: NOR,CMT
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
TransmissionMode: 16Bit
Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM] version: 10.28.0 revision: 0.0 size: 0x23220
Supported 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
CMT PAPUBKEYS HASH: D0D8948DEF333BF18141EF4C3D0FB1B002EB5D88
TransmissionMode: DDR&TX2
Processing MCU file: rm265__06.61.mcusw
[BB5,BB5 ALGORITHM] size: 18.11 MB
Supported Ids: 0103192101003000, 010C192101003000, 030C192101023000
Erase size: 21.12 MB
CMT NOR area [00000000-0001FFFF]
CMT NOR area [00040000-000BFFFF]
CMT NOR area [000C0000-0013FFFF]
CMT NOR area [013C0000-0153FFFF]
CMT NOR area [00140000-013BFFFF]
erased in 57.703 s
Flash programming ...
CMT NOLO block sent
CMT KEYS block sent
CMT PRIMAPP block sent
CMT PASUBTOC block sent
CMT PAPUBKEYS: D0D8948DEF333BF18141EF4C3D0FB1B002EB5D88 (RAP Certificate 87 v1) sent
CMT UPDAPP block sent
CMT DSP0 block sent
CMT MCUSW block sent
Programming completed in 1 min 52.016 s
Processing PPM file: rm265__09.48.ppm_d
[BB5,BB5 ALGORITHM] size: 5.59 MB
Supported Ids: 0103192101003000, 010C192101003000, 030C192101023000
Erase size: 6.50 MB
CMT NOR area [01540000-01BBFFFF]
erased in 15.766 s
Flash programming ...
Programming completed in 27.375 s
Processing CNT file: rm265__09.48_ISM_007.image_d_silver
[BB5,XSR 1.5] page size: 128 K size: 10.84 MB
Supported Ids: 0103192101003000, 010C192101003000
Storing certificate [NPC, CCC, HWC, R&D] ...OK
Erase size: 35.87 MB
CMT NOR area [01EC0000-03F9FFFF]
CMT NOR area [01BC0000-01EBFFFF]
erased in 1 min 54.125 s
Flash programming ...
Programming completed in 47.031 s
Total time for flashing process(boot+erase+write) was 6 min 24.844 s

Phone Type: RM-265 (Nokia 6500c)
SW Version: V 06.61 26-03-08 RM-265 (c) Nokia
Imei plain: 35866701325748-4
Product Code: 0558041
Battery voltage: 4821 mV, current: 71 mA
Language Pack:
- not available.

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: 358667013257484
Version: SIMLOCK SERVER
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 8000000000000006

BLOCK1: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK2: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK3: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK4: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK5: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK6: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN
BLOCK7: 1=OPEN, 2=OPEN, 3=OPEN, 4=OPEN, 5=OPEN

when turn on only the nokia logo appears and automatically shuts down .. I tried the same usb no result....
same version i flashed with ub phone alive..

please fix bug...

[gbluez]

hi,
negative as bugs. i personally tested with other rap3gv3 phones. same hash no problem.
with UB you flashed higher version, that's why it's good.

RM-265 v06.61 is old enough

BR

[sajohaker]

Originally Posted by gbluez

hi,
negative as bugs. i personally tested with other rap3gv3 phones. same hash no problem.
with UB you flashed higher version, that's why it's good.

RM-265 v06.61 is old enough

BR

I marked in mx..

rm265__09.48.mcusw
rm265__09.48.ppm_d
rm265__09.48_ISM_007.image_d_silver

but mx flashed v06.61.mcusw
I do not know why

otherwise the only fbus MX-BOX is going to end.
on the same cable tried to hwk ATF ub no result.flashing error..
My opinion is that the more time the bug will be removed with very good tools for fbus flashing

[gbluez]

hi,
your market configuration is messed up, no matter what file you load into it, it will use the file setting from market .ini.

on good working files config should be like this, right after you select such market:

Phone Type: RM-265
TimeStamp: 2008-11-26T15:51:06Z
SW Version: 09.45
Variant Version: 006
ProductProfile: RM265_0560650_09.45_006.spr
Simlock: 0560650_simlock.bin
Language Pack:
English,Chinese Simpl,Chinese Trad,Bahasa Indonesia

it is suggested to not have multiple version inside product folder. one highest version is better.

please delete your rm-265 folder, reinstall phone data package, or create new one by scan and image dl.

BR