Hitachi f/w 47 via JF issue.

[petrieslastword]

Here's the specifics of my issue.

I'm using the CK3 and a via card that I've used for all 3 other drive brands, and attempting to flash a friend's Hitachi drive. I place both the orig and ixtreme files into the firmware folder of JF 1.62 beta, and from there click over to the Hitachi area. My drive it detected fine, so from there, use the CK3 to open the drive, and then power it off. I then click send mode-b, and send the signal, then powering the drive on. It gives me the following:

........
Drive, answers normal Windows Inquiry 12 0 0 0 24 0
0000: 05 80 00 32 5B 00 00 00 - 48 4C 2D 44 54 2D 53 54 ...2[...HL-DT-ST
0010: 44 56 44 2D 52 4F 4D 20 - 47 44 52 33 31 32 30 4C DVD-ROM GDR3120L
0020: 30 30 34 37 0047

Mode-B Done!

From there, I then click flash Ixtreme as per the tutorial on the site I was using, and I get the following:

Flashing Hacked f/w to Hitachi 0046/0047 by Ram Upload Method via WIN32 API
UnLocked!
Dumping Flash:Ram Upload Dump Failed

I've gone through the video on the site again and again trying to figure out where I might be going wrong, but I can't seem to find where I mis-step. Does anyone have a clue?

*Just thought about this as a possibility: the light on my CK3 is red, which I believed to mean it is in mode B. Is this correct? Switching it didn't seem to help, but I just wanted to give as much detail as possible.*

[dalecheesy]

Nope just leave the modeB off on the ck3 (led blue). You might have to try changing it to mode select or classic in the transfer method.

[petrieslastword]

Nope just leave the modeB off on the ck3 (led blue). You might have to try changing it to mode select or classic in the transfer method.

It actually isn't even giving me the option for classic in the transfer method, and I've tried the mode select as well to no avail.

Scratch that, when I try with mode select, I get these 2 messages after trying twice:

Flashing Hacked f/w to Hitachi 0046/0047 by Mode Select Method via WIN32 API
UnLocked!
Dumping Flash:Upload buffer failed
Flashing Hacked f/w to Hitachi 0046/0047 by Mode Select Method via WIN32 API
Enable Execute Failed

[HAZ3]

you are better off using firmware toolbox. another member here posted a good tutorial on how to use it to dump/flash via that method via text, the same one i used. very concise & to the point & helped me flash it successfully

[petrieslastword]

you are better off using firmware toolbox. another member here posted a good tutorial on how to use it to dump/flash via that method via text, the same one i used. very concise & to the point & helped me flash it successfully

Any chance you could link me to the tutorial you used? I've never been able to quite wrap my head around using firmware toolbox.

[Shootsteel]

Use Ram upload for this issue....many times I have done this and no problems at all.

[HAZ3]

Use Ram upload for this issue....many times I have done this and no problems at all.

never heard of this method. curious to see how this works though

[HAZ3]

you are better off using firmware toolbox. another member here posted a good tutorial on how to use it to dump/flash via that method via text, the same one i used. very concise & to the point & helped me flash it successfully

Any chance you could link me to the tutorial you used? I've never been able to quite wrap my head around using firmware toolbox.

i"ll try looking for it when i have a chance.

here you go buddy. make sure you buy me a hamburger when i see you around

viewtopic.php?f=63&t=5882" onclick="window.open(this.href);return false;

[petrieslastword]

I'm at a loss. When I try to run 360FwTb, I get the error message:
Run-time error '339':

Component 'MSCOMCTL.OCX' or one of its dependencies not correctly registered: a file is missing or invalid


Why won't this work...ergh!

Nevermind, got past this point. See post below.

[petrieslastword]

I've tried that tutorial using firmware toolbox, and I'm having a similar problem. I get to the point where I am to read the drive and detect differences, but then it cannot read from drive. If I switck to classic mode, it can get past that part, but then I get the following when I click to flash:

Cannot communicate with drive. Make sure it is visible on windows.

My drive is visible on windows though, so I have no idea what else I could do.

*edit* Another forum claimed I need to use the following drivers:

http://drivers.softpedia.com/progDownlo ... 16737.html" onclick="window.open(this.href);return false;

But I can't for the life of me figure out how to install them from these files. How would one get rid of the drivers I had and replace them with these on the 32 bit Vista? Could this even be the problem?

[dalecheesy]

Use Ram upload for this issue....many times I have done this and no problems at all.

never heard of this method. curious to see how this works though

You were using this method in your first post.

And the drivers you linked might be worth a shot (just unrar it and click on the setup.exe and follow the prompts) but try another sata cable first or a different port. I use the internal port on the card nearest the front of the tower for all drives.

[Shootsteel]

[quote]Use Ram upload for this issue....many times I have done this and no problems at all.[/quote]

In JF choose the Ram Upload method manually....it will not do this automatic you have to choose this option....the hit 47 is bothersome ....funny everyone worries about the 79 but it's the lower ones that can really be a pain in the rump. Whenever they refuse to surrender I choose the Ram upload method and it works like a champ. As a side note whenever I am flashing a hit or any other drive I make sure that I save the bin files before I try to flash. JF is set up to flash the HIT use JF IMO.

[petrieslastword]

I'm not sure if I'm getting closer. I'm at the point where when I switch ports, the drive is willing to start the "flash ixtreme" process. I get the following:

Flashing Hacked f/w to Hitachi 0046/0047 by Ram Upload Method via WIN32 API
UnLocked!
Dumping Flash:................................
Hitachi Dump file saved to C:\Users\Justin\Desktop\JungleFlasher v0.1.62 Beta\firmware\Hit-OFW.bin
Loading Hitachi Dump to Source Buffer

C:\Users\Justin\Desktop\JungleFlasher v0.1.62 Beta

From there, the program never moves on.

I've tried using firmware toolbox but when I do so using this port, the program cannot see the drive.

[HAZ3]

ok, here's the deal. first of all i need your set up: are u using a ck3 kit? are u sure you are in mode b? (red color on led) are you installing the proper drivers for via 6421 card? are u using the sata port closest to mobo (usually the one pointing to the hdd is the one that works others are meh) if you answered y to all then folllow the tutorial i provided you with for firmware toolbox & you should be ready to roll. if u r going to use jungleflasher, good luck as ur going to have to put up with more stuff especially for the old drives. i know for a fact if you stick to the method i followed in that tutorial you will be ok w/o error however don't bypass anything. trust me, it will work. just dont give up.