e66 on Hitachi firmware update

[Han Cholo]

So I just got an e66 error on a hit 79 drive I was flashing.

I was really surprised to see that. I've done quite a few of these without a problem.
I was using jungleflasher, went through the usual steps...modeB,...unlockCD....
Dumped the drive
Restored to stock
flashed ixtreme

Everything verified just fine, then when I go to test it e66....

I tried to restore it back to stock, and no luck.

Luckily I got a good dump of the firmware, so I guess I can just use firmware toolbox and flash that bad boy with the original firmware.

Sucks that I can't flash that drive though... I wonder what that's all about...

[technoe]

It happens sometimes. It could be an error during the transfer, which sometimes does read as verified. As long as you can get it to work with the toolbox it'll be all good. Let us know how it goes.

[Han Cholo]

Yeah for sure. I'm gonna take a crack at it tomorrow. I'll post up my results, shouldn't be a problem bringing it back. Just wish I knew why I couldn't update the firmware. I tried it like 3 times. It won't take.

[sadalius]

Hitachi's are notorious for problems like that. I had a 78FK just the other day that gave me such problems. I fought with it for an hour before it finally gave it up and submitted to the flash. It's not like that with all of them, just one every so often. I think it's something with those drives.

[Han Cholo]

So do you think I should just keep trying to flash it? I did it a few times, and everything registered fine. Everything verified just like normal, but when I tested it... I still get that e66.

Update:

So I had a chance to play with that drive just now. I loaded the original firmware that I dumped from it, and for whatever reason it was spoofed as a v78. This drive is a 79. So apparently when Jungleflasher would auto-load my firmware it was flashing it with v78 firmware which is why I was getting e66.

So once I realized that , it was an easy fix. I just returned that bad boy to stock. I loaded some original hit79 firmware in my target, and spoofed the key in, then just spoofed that drive back to a 79. What confuses me is how the drive didn't have error e66 before when it was spoofed as a 78. Since that drive is the original drive for that console.