|
jungleflasher 1.66 hitachi 59 restore error
|
|
|
boer2030
Newbie
|
24. October 2009 @ 15:29 |
Link to this message
|
Hi,
I was wondering if someone could shed some light on my snag here. I have a hitachi 59dj drive and ixtreme 1.4. I'm trying to got up to 1.5 with jungleflasher 1.66 and everything goes smoothly up until the point where I need to restore the firmware to stock. jungleflasher reads the drive, puts it in mode B, assigns a drive letter, but when I click the button to restore the firmware to stock, it gives me the error "unlock failed." I've tried this probably 15 times all sorts of different ways, but it always gives me that error. What am I doing wrong here?
Thanks!
|
|
Advertisement
|
 |
|
|
|
qwert99
Senior Member
|
24. October 2009 @ 15:33 |
Link to this message
|
Have you done the device intro?
Firmware Toolbox seems to have more success for me in cases like this sometimes.
Also, make sure you are going to put 1.51 and not just 1.5 on there.
|
|
boer2030
Newbie
|
24. October 2009 @ 15:38 |
Link to this message
|
|
I did not do that. I just followed the guide for hitachis and didn't see that step. Is that on the MTK flash32 tab?
|
|
qwert99
Senior Member
|
24. October 2009 @ 15:41 |
Link to this message
|
Yeah, it's under the MTK tab.
Also, on the Hitachi tab, make sure you have the correct drive version radio button checked. You may want to try sending the unlock command yourself from the program, manually.
|
|
boer2030
Newbie
|
24. October 2009 @ 15:53 |
Link to this message
|
|
Thanks for the tip. I'll go try that. How do I do manual unlock? b/c I'm assuming the 78/79 unlock isn't applicable to 59 drive revision.
|
|
qwert99
Senior Member
|
24. October 2009 @ 15:56 |
Link to this message
|
Yeah, you're right. Sorry, I meant mode B, not unlock.
Definitely give Firmware Toolbox a try.
Remember that Hitachi drives are easily brickable, too.
|
|
boer2030
Newbie
|
24. October 2009 @ 17:03 |
Link to this message
|
Ok, that didn't work. The drive intro worked, but once I tried to restore in jungleflasher, it still gave me the same "unlock failed" error. I tried restore.bat in firmware toolbox and it doesn't work either. This is really weird. It was so easy going to 1.4, but for whatever reason it just doesn't want to revert back to the stock firmware. Does anyone know what may be going wrong here?
|
|
qwert99
Senior Member
|
24. October 2009 @ 17:32 |
Link to this message
|
Try using PortIO if you are using Win32, and vice versa.
Also, try the different transfer methods (Classic, mode select, RAM upload).
Not sure exactly what your problem is, just trying to help ya troubleshoot. These things can be a real pain in the ass sometimes.
|
|
boer2030
Newbie
|
24. October 2009 @ 17:35 |
Link to this message
|
|
I definitely appreciate it. I'm starting to lose hope on this. I may just keep 1.4 if I can't get it working by the end of the weekend.
|
|
qwert99
Senior Member
|
24. October 2009 @ 17:38 |
Link to this message
|
I am wondering if it is actually going into mode B, or the program just thinking it is in mode B. You may want to try the Slax CD method to ensure it is put into mode B and then try JF or FTB. I will warn you that JF seems to be more prone to crashing and freezing than FTB. That is a big no-no with Hitachi drives.
You may also need to make sure all of your VIA drivers are uninstalled. I've personally never had to take that step, but supposedly it is wise.
|
|
boer2030
Newbie
|
24. October 2009 @ 18:08 |
Link to this message
|
It's definitely in mode B. I made sure it was in mode B by ejecting the drive and confirming that the tray closes only after pressing the eject button twice.
My option for port I/O is greyed out, even though I installed it correctly. I think it's because I'm plugging the drive directly into my SATA controller.
Could you explain how to remove the VIA drivers? I wasn't aware that I installed them.
|
|
qwert99
Senior Member
|
24. October 2009 @ 18:13 |
Link to this message
|
PortIO should still be available, even if using an onboard SATA controller, I believe.
Sorry, I don't know the step-by-step for uninstalling the VIA drivers off of the top of my head. I imagine it involves opening up Device Manager and uninstalling from there. The steps have been written up here multiple times, however. So a search should reveal them.
|
|
boer2030
Newbie
|
25. October 2009 @ 19:38 |
Link to this message
|
I think I just screwed it royally. I tried to do a restore using restore.bat and then dumped it in firmware toolbox, copied key to 1.51 fw and flashed it with toolbox. Now the drive only wants to be a dvd player, which, from what i've read, means it has lost it's key. And if that's the case, I don't know where the original key is. I thought it would be dumped correct after the restore, but apparently not.
any thoughts on a solution?
|
|
qwert99
Senior Member
|
25. October 2009 @ 19:41 |
Link to this message
|
Use JF to 'load source' firmware. See what key it reports in the program. Just because you didn't flash it correctly doesn't mean it doesn't exist in your file.
As long as you have your dump file, you should be okay.
If your key shows up in your orig.bin (or whatever filename) file, then you can load your target firmware as the most recent iXtreme file. Then 'spoof source to target' and then 'Save to file'. Save the file as an original filename, and then use that file to reflash in Firmware Toolbox.
This message has been edited since posting. Last time this message was edited on 25. October 2009 @ 19:45
|
|
boer2030
Newbie
|
27. October 2009 @ 12:07 |
Link to this message
|
got it fixed up. fyi, jungleflasher is a POS. I used firmware toolbox and will continue to use it until jungleflasher decides to either work or allow me to control some advanced options.
I searched all over my computer for the original dumped firmware and I finally found it hidden away. Once I found that, I loaded in in toolbox, saved the key and dumped it once more, just to be thorough. I then did a differential flash (restore) and it scanned for differences. Toolbox recognized that all I needed was an updated key and flashed the key sector. Voila, 1.51 works perfectly now. Big sigh of relief as I thought I ruined it.
|
|
Advertisement
|
|
|
|
qwert99
Senior Member
|
27. October 2009 @ 12:12 |
Link to this message
|
Nice! Yeah, JF is pretty poorly coded. It does have a lot of features that increase ease of use, however, so it has its place. It's cost me more than one drive, though.
I am like you and I use Firmware Toolbox for the actual flashing. Much, much more reliable program, IMO.
Glad you got things sorted. I hope you still have some hair, and not all of it was pulled out.
|
