GSM Shop GSM Shop
GSM-Forum  

Welcome to the GSM-Forum forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.

Registration is fast, simple and absolutely free so please - Click to REGISTER!

If you have any problems with the registration process or your account login, please contact contact us .

Go Back   GSM-Forum > Product Support Sections > No More Supported Solutions (Dead Products) > No More Supported H/W Products > Saras Boxes > HWK
Reload this Page 6500c Problem flashing - Need Urgent Help :confused:
Register FAQDonate Forum Rules Root any Device ★iPhone Unlock★ ★ Direct Codes ★ Direct Unlock Source


 
 
LinkBack Thread Tools Display Modes
Old 07-14-2009, 09:38   #1 (permalink)
Registered User
 
Join Date: Nov 2001
Location: Mosta
Age: 53
Posts: 233
Member: 7641
Status: Offline
Thanks Meter: 26
6500c Problem flashing - Need Urgent Help :confused:

I get nokia 6500c v8.30 in working condition, some minor software problem,
reflash will help, and I need to change lang pack to.

Now dead nokia !!!!!

HWK or JAF can't flash higher version then 6.61 for 6500c !
What's the problem,,, me, loader or something else ?

I try with ver: (both boxes - HWK and JAF)
4.80, 4.84, 6.61 - Successfully, but can't turn on.
8.30, 9.45, 9.48 - Not possible to flash. After erase, error on 1% flashing.

Few min before, I flash and unlock another one 6500c v4.80->v4.84
with no problems.

Please Mr. Odia, or somebody else, help me to solve this problem.
 
Old 07-14-2009, 09:43   #2 (permalink)
Freak Poster
 
howell's Avatar
 
Join Date: Feb 2008
Location: Angeles City
Posts: 365
Member: 697643
Status: Offline
Thanks Meter: 68
what is the history of your phone sir? wet unit?
 
Old 07-14-2009, 09:54   #3 (permalink)
Registered User
 
Join Date: Nov 2001
Location: Mosta
Age: 53
Posts: 233
Member: 7641
Status: Offline
Thanks Meter: 26
No suspicious history for this phone. I'm not alone with flashing problem for 8.30, 9.45 or 9.48 version.

Before flashing was in working condition !

What can be wrong ? Loader or some new protection or ..... ?
 
Old 07-14-2009, 13:38   #4 (permalink)
Registered User
 
Join Date: Nov 2001
Location: Mosta
Age: 53
Posts: 233
Member: 7641
Status: Offline
Thanks Meter: 26
Few words about this 6500c versions from other forums.

Code:
Nokia SL3 based - Facts & Fiction 

--------------------------------------------------------------------------------

For some time we noticed the new BB5 phones with software version higher
than 50.00.

But I would like start from the beginning, when Nokia Company introduced on
the market BB5 phones with new security system SIMLOCK was impossible to
unlock. For long time we waited to update our software to be able to fully
service these phones - SIM-Lock too. 
At this time almost any type of lock on BB5 type with SL2 is possible to
unlock. Right now Nokia have completely changed the firmware in the
handsets with SL3 Security Zone.
At the moment any attempt to downgrade or unlock the handset ends from
damage security zone. The most common symptoms are:

* Contact Service
* damaged IMEI - 12345678901?
* white blinking
* NOKIA logo freeze
* Security 'Failed to Read'
* dead handset

Called by Nokia, new idea - Protected Application PA_SL3 (SimLockx; x=2,
x+3) that protects the functions which are executed by special applications.
Security zone formatted by 'ProtectedApp_SL' application isn't compatible
with PA_SL2 application and vice versa yet - totally modyfied EEprom in
flash. 

All currently manufactured phones have the SL3 structure and I am sure that
it will be more in the future. In addition, Nokia complete rebuilding system of
RPL counting by the RPL server.

What mobiles are SL3 right now ?

based on different CPU types, but new MCU SW security SimLock3 - 'SL3'
(T-Mobile & Orange)

* 5310 MCU v58.58, v59.42 (RM-303)
* 6300 MCU v57.20 (RM-217)
* 6500c MCU v59.45 (RM-265)
* 6500s MCU v59.60 (RM-240)
* ... (more in future)

After downgrade phone coming to dead. But after restore oryginal MCU SW
phone will alive.
But how to restore original MCU SW ?
Last edited by djanib; 07-14-2009 at 13:43.
 
Old 07-14-2009, 15:11   #5 (permalink)
No Life Poster
 
[Shadab_M]'s Avatar
 
Join Date: Mar 2006
Location: .: India :. Heaven on Earth
Posts: 2,496
Member: 238812
Status: Offline
Sonork: 100.1602669
Thanks Meter: 1,443
Bro!

To restore original MCU SW means - Flash with the same flash file Version, which was in phone before you tried to flash it.

But, for better help, please provide flashing log.

One more thing, before flashing this phone with higher version, goto UFSX tab of DCTxBB5 and Uncheck 1331 Option.

Try this and post result!

Br,
Shadab Ahmad
 
Old 07-14-2009, 17:05   #6 (permalink)
Registered User
 
Join Date: Nov 2001
Location: Mosta
Age: 53
Posts: 233
Member: 7641
Status: Offline
Thanks Meter: 26
Problem solved.

Nokia flashed with JAF as "dead USB" and working ok.

In any case, I will post here errors received with HWK and JAF usig FBUS cable, with or without 1331 checked .

With FBUS I can flash version 6.61 or lower (4.80, 4.84) but this can't help to power on nokia, because
it is downgradeing procedure SL3 type phone. Read "CODE" section in my previous post.

My main problem is, "Why I can't flash with FBUS 8.30 or 9.45 or 9.48 with HWK or with JAF ?"

Here is JAF Dead USB revive:
Code:
14:07:2009  17:18 -> Phone prepared OK!
14:07:2009  17:18 -> Waiting for the phone to boot...
14:07:2009  17:18 -> Searching for phone...
14:07:2009  17:18 -> Status byte: 8000
14:07:2009  17:18 -> Selecting CMT flash...
14:07:2009  17:18 -> Result: 0000
14:07:2009  17:18 -> Phone is in flash mode...
14:07:2009  17:18 -> CMT blocks: 2043, APE blocks: 0
14:07:2009  17:18 -> Erasing cmt...
14:07:2009  17:18 -> Processing C:\Program Files\Nokia\Phoenix\Products\RM-265\rm265__08.30.mcusw...
14:07:2009  17:18 -> Erasing cmt zone 00000000 - 0001FFFF ... 14:07:2009  17:18 -> Erase result: 0000
14:07:2009  17:18 -> Erasing cmt zone 00040000 - 000BFFFF ... 14:07:2009  17:18 -> Erase result: 0000
14:07:2009  17:18 -> Erasing cmt zone 000C0000 - 0013FFFF ... 14:07:2009  17:18 -> Erase result: 0000
14:07:2009  17:18 -> Erasing cmt zone 013C0000 - 0153FFFF ... 14:07:2009  17:18 -> Erase result: 0000
14:07:2009  17:18 -> Erasing cmt zone 00140000 - 013BFFFF ... 14:07:2009  17:18 -> Erase result: 0000
14:07:2009  17:18 -> Processing C:\Program Files\Nokia\Phoenix\Products\RM-265\rm265__08.30.ppm_d...
14:07:2009  17:18 -> Erasing cmt zone 01540000 - 01BBFFFF ... 14:07:2009  17:19 -> Erase result: 0000
14:07:2009  17:19 -> Processing C:\Program Files\Nokia\Phoenix\Products\RM-265\rm265__08.30_ISM_002.image_telecom_ba_bronze...
14:07:2009  17:19 -> Erasing cmt zone 01EC0000 - 03F9FFFF ... 14:07:2009  17:19 -> Erase result: 0000
14:07:2009  17:19 -> Erasing cmt zone 01BC0000 - 01EBFFFF ... 14:07:2009  17:19 -> Erase result: 0000
14:07:2009  17:19 -> Send CMT CFG...
14:07:2009  17:19 -> Writing cmt...
14:07:2009  17:19 -> Processing C:\Program Files\Nokia\Phoenix\Products\RM-265\rm265__08.30.mcusw...
14:07:2009  17:19 -> Sending CMT HASH for NOLO
14:07:2009  17:19 -> Sending CMT HASH for KEYS
14:07:2009  17:19 -> Sending CMT HASH for PRIMAPP
14:07:2009  17:19 -> Sending CMT HASH for PASUBTOC
14:07:2009  17:19 -> cmt->PAPUB_CERTIFICATE_DATA_BB5 block detected, sending... 
14:07:2009  17:19 -> Sending CMT HASH for UPDAPP
14:07:2009  17:19 -> Sending CMT HASH for DSP0
14:07:2009  17:19 -> Sending CMT HASH for MCUSW
14:07:2009  17:21 -> Processing C:\Program Files\Nokia\Phoenix\Products\RM-265\rm265__08.30.ppm_d...
14:07:2009  17:21 -> Processing C:\Program Files\Nokia\Phoenix\Products\RM-265\rm265__08.30_ISM_002.image_telecom_ba_bronze...
14:07:2009  17:23 -> Rebooting...
14:07:2009  17:23 -> Finishing CMT session...
14:07:2009  17:23 -> Restarting CMT...
14:07:2009  17:24 -> Pooling phone...
14:07:2009  17:24 -> Phone not found...
14:07:2009  17:25 -> Second try...
14:07:2009  17:25 -> MCUSW: V 08.30
03-07-08
RM-265
(c) Nokia            
14:07:2009  17:25 -> APESW: (null)
14:07:2009  17:25 -> VariantSW: (null)
14:07:2009  17:25 -> Prodcode: 0565774
14:07:2009  17:25 -> Done!
JAF Error flashing FBUS interface:
Code:
14:07:2009  05:13 -> JAF version 1.98.64
Detected PKEY: xxxxxxxx
14:07:2009  05:13 -> Card life counter: xx.xx%
14:07:2009  05:13 -> P-key nokia module version xx.xx
14:07:2009  05:13 -> Detected  version: 01.B1, Driver version: 0, Library version: 0
14:07:2009  05:13 -> JAF DCT4/BB5 LOADERS DIR: C:\Program Files\ODEON\JAF\Flash\
14:07:2009  05:13 -> JAF DCT4/BB5 PRODUCT DIR: C:\Program Files\Nokia\Phoenix\Products\
14:07:2009  05:13 -> JAF USB LOADERS DIR: C:\Program Files\ODEON\JAF\FlashUSB\
14:07:2009  05:13 -> JAF DCT3/DCTL LOADERS DIR: C:\Program Files\ODEON\JAF\Flash3\
14:07:2009  05:13 -> USB Cable Driver version: 7.0.2.0
14:07:2009  05:14 -> Changing mode...14:07:2009  05:14 -> Done!
14:07:2009  05:14 -> FILES SET FOR FLASHING:
14:07:2009  05:14 -> MCU Flash file: NONE
14:07:2009  05:14 -> PPM Flash file: NONE
14:07:2009  05:14 -> CNT Flash file: NONE
14:07:2009  05:14 -> APE Variant file: NONE
14:07:2009  05:14 -> Phone Type: 
14:07:2009  05:14 -> FILES SET FOR FLASHING:
14:07:2009  05:14 -> MCU Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-265\rm265__08.30.mcusw
14:07:2009  05:14 -> PPM Flash file: NONE
14:07:2009  05:14 -> CNT Flash file: NONE
14:07:2009  05:14 -> APE Variant file: NONE
14:07:2009  05:14 -> Phone Type: 
14:07:2009  05:14 -> FILES SET FOR FLASHING:
14:07:2009  05:14 -> MCU Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-265\rm265__08.30.mcusw
14:07:2009  05:14 -> PPM Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-265\rm265__08.30.ppm_d
14:07:2009  05:14 -> CNT Flash file: NONE
14:07:2009  05:14 -> APE Variant file: NONE
14:07:2009  05:14 -> Languages in ppm: English,German,Slovak,Slovene,Serbian,Hungarian,Czech,Croatian
14:07:2009  05:14 -> Phone Type: 
14:07:2009  05:14 -> FILES SET FOR FLASHING:
14:07:2009  05:14 -> MCU Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-265\rm265__08.30.mcusw
14:07:2009  05:14 -> PPM Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-265\rm265__08.30.ppm_d
14:07:2009  05:14 -> CNT Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-265\rm265__08.30_ISM_002.image_telecom_ba_bronze
14:07:2009  05:14 -> APE Variant file: NONE
14:07:2009  05:14 -> Languages in ppm: English,German,Slovak,Slovene,Serbian,Hungarian,Czech,Croatian
14:07:2009  05:14 -> Manual mode selected, version can't be checked!
14:07:2009  05:14 -> Booting phone...
14:07:2009  05:14 -> FAST PHONE detected!
14:07:2009  05:14 -> 
CMT Boot Data:
14:07:2009  05:14 -> Asic ID: 14:07:2009  05:14 -> 000000010000022600010006010C192101003000
14:07:2009  05:14 -> Asic Mode ID: 14:07:2009  05:14 -> 00
14:07:2009  05:14 -> Asic EM ID: 14:07:2009  05:14 -> 00000B22
14:07:2009  05:14 -> Asic Public ID: 14:07:2009  05:14 -> 0FB000164A9402540D0136BFB0F281BFCCF435A9
14:07:2009  05:14 -> HASH: 14:07:2009  05:14 -> BAF3A9C3DBFA8454937DB77F2B8852B100000000
14:07:2009  05:14 -> ROM ID: 14:07:2009  05:14 -> 273F6D55DFAAF68F
14:07:2009  05:14 -> CMT Boot File: C:\Program Files\ODEON\JAF\Flash\UFS\rap3gv3_2nd.fg
14:07:2009  05:14 -> Loader version: 01.10.0214:07:2009  05:14 ->  -> Revision: 0000
14:07:2009  05:14 -> Patching CMT boot step1...
14:07:2009  05:14 -> Patching CMT boot step2...
14:07:2009  05:14 -> Patching CMT boot step3...
14:07:2009  05:14 -> CMT Boot Ready
14:07:2009  05:14 -> CMT Flash ID: 14:07:2009  05:14 -> 220C00EC14:07:2009  05:14 ->  <=> SAMSUNG (SEC) -> K5G1257ATM
14:07:2009  05:14 -> CMT Flash Data: 14:07:2009  05:14 -> 00000000000000000000000000000000
14:07:2009  05:14 -> Error finding cmd loader...
14:07:2009  05:14 -> Error loading cmt loader...
I lost log but I will repeate flashing MCU with HWK just to show this error.
HWK Error flashing FBUS interface:
Code:
Detected: V 08.30 03-07-08 RM-265 (c) Nokia            
1ST BOOT  : C0,07 [Rm-265] [2.0.8.5]
RAPx ID   : 000000010000022600010006010C192101003000
EM 1 ID   : 00000295
EM 2 ID   : 00000B22
RAPx PBID : 0FB000164A9402540D0136BFB0F281BFCCF435A9
RAPx MODE : 00
RAPx HASH : BAF3A9C3DBFA8454937DB77F2B8852B1
RAPx ROID : 273F6D55DFAAF68F
CMT 1ST Boot OK
CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1
CMT FLID0 : 00EC220C-00008921, Sam K8F1215ETM
CMT FLCNT : 00000000000000000000000000000000000000
CMT MCID0 : FFFF0000-00000000
CMT 2ND Boot OK
CMT ALGO  : RAP3Gv3_algo_xsr15.fg, Ver: 1.40.0
CMT KSIG0 : D0D8948DEF333BF18141EF4C3D0FB1B002EB5D88
CMT VPP   : Internal
DUAL LINE : True
CMT ALG Boot OK
IMAGE : rm265__08.30.mcusw
CMT NOR Erase Area: 0x00000000-0001FFFF
CMT NOR Erase Area: 0x00040000-000BFFFF
CMT NOR Erase Area: 0x000C0000-0013FFFF
CMT NOR Erase Area: 0x013C0000-0153FFFF
CMT NOR Erase Area: 0x00140000-013BFFFF
CMT FLASH ERASE OK, Time: 00:55
DATA_BLK_ERROR at: 0x000A0400, 00
ERR: CMT FLASH WRITE D_BLK 000000000000000910000000B172, LN: 0x008580, Time: 00:08
Process Failed, Repowering Mobile
Problem is solved, but I want to know why this,,,, loader or something else ?
 
Old 07-15-2009, 23:13   #7 (permalink)
No Life Poster
 
Join Date: Nov 2008
Location: Hate stupidity
Posts: 1,907
Member: 904530
Status: Offline
Thanks Meter: 517
Enable Ext. VPP option
and use 9V battery to have 9v voltage on Vpp pin
and all will be Ok and much faster

1ST BOOT : C0,07 [Rm-265] [2.0.8.5]
RAPx ID : 000000010000022600010006010C192101003000
EM 1 ID : 00000295
EM 2 ID : 00000B22
RAPx PBID : 29400106BF257C56694236B183F9C767FF0750DE
RAPx MODE : 00
RAPx HASH : BAF3A9C3DBFA8454937DB77F2B8852B1
RAPx ROID : 273F6D55DFAAF68F
CMT 1ST Boot OK
CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1
CMT FLID0 : 00EC220C-00008921, Sam K8F1215ETM
CMT FLCNT : 00000000000000000000000000000000000000
CMT MCID0 : FFFF0000-00000000
CMT 2ND Boot OK
CMT ALGO : RAP3Gv3_algo_xsr15.fg, Ver: 1.40.0
CMT KSIG0 : 238ABB2E0343011DC42EE92433FF027210669E1C
CMT VPP : External
DUAL LINE : True
CMT ALG Boot OK
IMAGE : rm265__59.45.mcusw
CMT NOR Erase Area: 0x00000000-0001FFFF
CMT NOR Erase Area: 0x00040000-000BFFFF
CMT NOR Erase Area: 0x000C0000-0013FFFF
CMT NOR Erase Area: 0x013C0000-0153FFFF
CMT NOR Erase Area: 0x00140000-013BFFFF
CMT FLASH ERASE OK, Time: 00:46
Written: 8 Certificate(s)
CMT FLASH WRITE OK, Time: 01:38
1ST BOOT : C0,07 [Rm-265] [2.0.8.5]
RAPx ID : 000000010000022600010006010C192101003000
EM 1 ID : 00000295
EM 2 ID : 00000B22
RAPx PBID : 29400106BF257C56694236B183F9C767FF0750DE
RAPx MODE : 00
RAPx HASH : BAF3A9C3DBFA8454937DB77F2B8852B1
RAPx ROID : 273F6D55DFAAF68F
CMT 1ST Boot OK
CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1
CMT FLID0 : 00EC220C-00008921, Sam K8F1215ETM
CMT FLCNT : 00000000000000000000000000000000000000
CMT MCID0 : FFFF0000-00000000
CMT 2ND Boot OK
CMT ALGO : RAP3Gv3_algo_xsr15.fg, Ver: 1.40.0
CMT ISM Conf OK
CMT KSIG0 : 238ABB2E0343011DC42EE92433FF027210669E1C
CMT VPP : External
DUAL LINE : True
CMT ALG Boot OK
IMAGE : rm265__59.45_ism_001.image_c_uk_vg_uk_payt_black_v 2
CMT NOR Erase Area: 0x01EC0000-03F9FFFF
CMT NOR Erase Area: 0x01BC0000-01EBFFFF
CNT FLASH ERASE OK, Time: 00:40
CNT FLASH WRITE OK, Time: 00:58
1ST BOOT : C0,07 [Rm-265] [2.0.8.5]
RAPx ID : 000000010000022600010006010C192101003000
EM 1 ID : 00000295
EM 2 ID : 00000B22
RAPx PBID : 29400106BF257C56694236B183F9C767FF0750DE
RAPx MODE : 00
RAPx HASH : BAF3A9C3DBFA8454937DB77F2B8852B1
RAPx ROID : 273F6D55DFAAF68F
CMT 1ST Boot OK
CMT 2ND Bt: RAP3Gv3_2nd.fg, Ver: 9.11.1
CMT FLID0 : 00EC220C-00008921, Sam K8F1215ETM
CMT FLCNT : 00000000000000000000000000000000000000
CMT MCID0 : FFFF0000-00000000
CMT 2ND Boot OK
CMT ALGO : RAP3Gv3_algo_xsr15.fg, Ver: 1.40.0
CMT KSIG0 : 238ABB2E0343011DC42EE92433FF027210669E1C
CMT VPP : External
DUAL LINE : True
CMT ALG Boot OK
IMAGE : rm265__59.45.ppm_cvf
CMT NOR Erase Area: 0x01540000-01BBFFFF
PPM FLASH ERASE OK, Time: 00:14
PPM FLASH WRITE OK, Time: 00:32
Flashing Completed, Rebooting Mobile
 
Old 07-29-2009, 16:26   #8 (permalink)
Junior Member
 
Join Date: Apr 2007
Posts: 9
Member: 491001
Status: Offline
Sonork: IGGY01
Thanks Meter: 1
6500c v8.30 issue
I too am getting the same issue when trying to upgrade 6500c to v8.30.

The post mentions applying 9V battery to Ext vpp pin. Is there a special cable available for this and/or how do you go about this?

Is a new version of HWK imminent to resolve?
 
Old 07-29-2009, 19:40   #9 (permalink)
No Life Poster
 
ranagaurav's Avatar
 
Join Date: Nov 2008
Location: gsm hosting
Posts: 5,609
Member: 907098
Status: Offline
Sonork: 100.1601140
Thanks Meter: 705
yes maney time i see that fbus flashing is not sucsees but usb flashing is ok
 
 

Bookmarks

« Previous Thread | Next Thread »

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Similar Threads
Thread Thread Starter Forum Replies Last Post
e2100b problem unlocking need urgent help 00aa NSPRO 1 08-23-2009 17:20
***** flash problem need urgent help plz karouk FuriousGold 2 08-22-2007 09:14
w550i flashing problem need urgently help manish665 Cruiser Suite 4 06-23-2007 12:21
T 630 flash need urgently help Unlocker AL Twisterflasher 5 03-07-2005 17:33
C300 flash needed urgently .... help mar0der Motorola ODM 2 06-05-2003 06:37

 



All times are GMT +1. The time now is 15:58.

Contact Us - GSM-Forum - Archive - Top


Powered by Searchlight © 2024 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -
Page generated in 0.23226 seconds with 9 queries

SEO by vBSEO