Print

[uradodah]

QUOTE(TeeVee @ Mar 7 2009, 11:05 PM)

First I'll start off saying I'm using USB Connectivity kit v2...I do not have sata on motherboard.

Had some issues getting drive to show up in windows...found out if I unplug usb then plug it back in when in modeb it will show up in windows. Now in JungleFlasher -- that's another story. It appears on the right hand side (when Hitachi tab is selected) but nothing appears under port properties on left...The hitachi drive does not appear under any of the ports....only appears on the pulldown menu on the right side of screen.

I figure to get into modeb i must send modeb command but how do i do that if I cant see drive info in port properties...help! Please!

Did you get this issue resolved yet?  I don't know if I can help, but I'll try.  

I literally just got done flashing my Hitachi 47 drive using Jungle Flasher.  The only difference is I used an internal SATA connection.  It took me a while to get the flashing process fully completed but I eventually figured it out.

First, and I could definitely be wrong on this so proceed with caution, since your drive is showing up in Windows - and also showing up on the right side in Jungle Flasher - I think you can proceed with flashing the drive using the Win API option instead of Port IO.  If I understand correctly, the Port Properties section on the left side would be applicable if you wanted to use the Port IO method to flash.  However, the Win API method should still work since the drive *is* being recognized by both Windows and J. Flasher.

Does that make sense?  Again, I could be wrong.  However, if I am wrong, when you go to flash the drive it just won't work because it won't be able to connect to the drive at all.  Therefore, you wouldn't be hurting anything.

Additionally, have you flashed the drive before now?  Were you already using iXtreme 1.4 or a different version of the previously hacked firmware?  If so, you should already have a back-up of your original (stock) firmware so even if you screw up, you can still fix it...as long as you have the drive's key.

I'm not sure how you got it in ModeB but many people commonly forget that you can easily put it in ModeB if you're already using hacked firmware...doesn't matter which version.  Turn on the 360 and open the DVD drive.  Leave the drive door open and unplug the system WITHOUT closing the drive's door.  It must remain open when you unplug it.  Then, plug the 360 back into the wall and power it back on.  Close the drive's door if it doesn't do it automatically and, viola, it *should* be in ModeB...and recognizable by Windows.  

Now - as if this post isn't long enough already, I ran into some problems getting J. Flasher to properly flash my drive at first.  Windows (Vista) recognized my drive - only after I put it into ModeB and hooked the drive up to my PC prior to turning it on.  The driver auto-installed and I was good to go.  Even though I followed the manual installation instructions for PortIO - and successfully installed the driver - it still didn't work.  I could see the PortIO device in Device Manager but J. Flasher just would *not* work unless I used the Win API setting.  Now - I could still see my drive in the top left corner (Port Properties) but all attempts to flash my drive failed.

After I switched to Win API and started the process of restoring the original (stock) firmware, I STILL had problems.  I started to worry. After thinking for awhile, and kicking the dog a few times (not really), I decided to hit the 'Query' button under the drive's name in the top right corner.  Once I did that, the 'Drive answers normal Windows inquiry' message showed up - with a bunch of numbers following it - *as noted in the screenshot at the top of page 46 in the J. Flasher beta tutorial PDF.  

That seemed to be the magic solution.  Using my own logic - and many people would tell you I'm f-ed up so, again, be careful - since I had already put the drive into ModeB WITHOUT doing so through J. Flasher, I don't think it properly queried the drive to begin with.  Once I queried the drive, I was able to restore and re-flash the new 1.51 firmware without any issues.  Total process took only 2 minutes once I hit the 'Query' button.

So - I tell you all of this in case the 'Query' button might help you as well...maybe someone else out there too.  You're putting the drive into ModeB without using J. Flasher - just like I did - so this may help resolve any issues you run into.

Let me know if this was of *any* help to you.  I hope so...I can't get the last 10 minutes of my life back.

[TeeVee]

Since the drive showed up on the right side I decided to go ahead and try and dump firmware...
"dumped drive and "read To Source"
Asked me if I wanted to save...I said Yes.
The I chose "Flash iXtreme" and "Flas Hacked Firmware" I got this message:

Loading Hitachi Dump file
Inquiry string found
Identify string found
DVD key found @ 0x4F00 key is "my key here"
Firmware is Hitachi OSIG: HL-DT-STDVD-ROM GDR3120L0047
Firmware type is: Stock
Flashing Hacked f/w to Hitachi 0046/0047 by Mode Select Method via WIN32 API
UnLock Failed

Xbox is still workling so I didn't brick it...just don't know what it means..scared to try it again...
Seems my computer does not like JungleFlasher...freezes up every once in a while and I have to reboot...scared that will happen during a write!

[uradodah]

QUOTE(TeeVee @ Mar 8 2009, 03:39 AM)

Since the drive showed up on the right side I decided to go ahead and try and dump firmware...
"dumped drive and "read To Source"
Asked me if I wanted to save...I said Yes.
The I chose "Flash iXtreme" and "Flas Hacked Firmware" I got this message:

Loading Hitachi Dump file
Inquiry string found
Identify string found
DVD key found @ 0x4F00 key is "my key here"
Firmware is Hitachi OSIG: HL-DT-STDVD-ROM GDR3120L0047
Firmware type is: Stock
Flashing Hacked f/w to Hitachi 0046/0047 by Mode Select Method via WIN32 API
UnLock Failed

Xbox is still workling so I didn't brick it...just don't know what it means..scared to try it again...
Seems my computer does not like JungleFlasher...freezes up every once in a while and I have to reboot...scared that will happen during a write!

Don't be concerned, my computer didn't like J. Flasher too much either.  I just chalked it up to a Vista problem.  Are you using Vista by chance?  If so, make sure to right-click J. Flasher's .exe file, select Properties and go to the Compatibility tab.  Change it to XP SP2 and click Ok.  From there, right-click on J. Flasher's .exe again and select 'Run as Administrator'.  That seemed to help J. Flasher work a bit more smoothly.

Of course, if you're not using Vista, forget what I just said.  

Anyway, once you opened J. Flasher and selected the Hitachi tab, did you select the 'Query' Button?  If so, did you see the message I mentioned in my last post?

Again, my flashes failed too - until I did that.  They didn't fail as quickly as yours but they failed none-the-less.

Try the 'Query' button - if you haven't already - and let me know what happens.

[TeeVee]

Yup, Vista. I did not run as admin..maybe that's the problem. I did press query at one point or another and got message query received.
Worried if I screw around too much it's going to brick drive!

[uradodah]

QUOTE(TeeVee @ Mar 8 2009, 04:01 AM)

Yup, Vista. I did not run as admin..maybe that's the problem. I did press query at one point or another and got message query received.
Worried if I screw around too much it's going to brick drive!

Nah...you're good.  As long as you have the original f/w (stock) saved - including the drive's key - it can be restored.  Where people run into problems is when they don't back up the stock f/w and key...or they lose it.

I'm thinking outside the box here so take this suggestion/idea with a grain of salt.  Would booting Vista in Safe Mode possibly work?  Since your drive is being recognized by Vista, it might be possible to try running J. Flasher in Safe Mode to see if there was a conflict happening somewhere.

Just a thought...

Also, because it can't hurt, even though you're already in ModeB, try hitting the 'Send Mode-B' button in J. Flasher to see what happens.  Hit the 'Open' and 'Close' buttons too...just to see if the 360 drive reacts to them.

One last thing I forgot to mention when I flashed successfully...

After hitting the 'Query' button, I tried the 'Open' and 'Close' buttons too.  The drive opened fine and closed fine too.  However, instead of staying closed, it opened again and stayed that way.  You might recall that it's actually a good sign...a sign of it being in ModeB.  Textbook's old flashing tutorial PDF referenced that as a good sign...

Anyway, my previous attempts to flash WERE NOT with the drive's door open.  So - I said, 'Heck, I'll give it a try with the drive open.'  Again, viola!  Everything worked perfectly.

I say, try to open/close and then leave the door open when trying to flash first.  Then, if that doesn't work, try booting your PC in Safe Mode.

Finally, I'm assuming you're running J. Flasher in compatibility mode too.  Keep running it as Admin. going forward.

Let me know if one of these 2 ideas work.

[TeeVee]

Thanks for the suggestions..going to give this a shot again.

Quick question though. If I follow the JungleFlasher Tutorial, does it restore Firmware back to original if I follow the steps? The way I see it it says to dump, then flash hacked firmware...don't see the step in there to restore. Only after the tutorial does it mention anything about restoring. Do I need to skip to end of tutorial, restore then begin tutorial? Sorry may be a dumb question but confused about the order of steps in the tutorial.

[Bazdoctor]

QUOTE(TeeVee @ Mar 9 2009, 03:29 AM)

Thanks for the suggestions..going to give this a shot again.

Quick question though. If I follow the JungleFlasher Tutorial, does it restore Firmware back to original if I follow the steps? The way I see it it says to dump, then flash hacked firmware...don't see the step in there to restore. Only after the tutorial does it mention anything about restoring. Do I need to skip to end of tutorial, restore then begin tutorial? Sorry may be a dumb question but confused about the order of steps in the tutorial.

There is no original Lite on FW. If you have a bad flash or a freeze, erase the drive and start again, try dosflash. People have reported erasing there drives multiple times with no complications. Just make sure you have a good key etc.

[hardie]

Sorry Bazdoctor his query is regarding a Hitachi47 not a liteon

[Traviss63]

TeeVee you don't need to restore, that is for people who have previously modded their Hitachi with older, obsolete firmware. When Uradodah says "don't worry since you have the key"  he means if you fuck up you can still REPLACE the drive since you have you original key. It is very easy to fuck up with Hitachis so use care and common sense!


Good Luck!  

[TeeVee]

Traviss63, so even if I have iXtreme 1.4...still don't restore...just follow exact tutorial?

[Traviss63]

iXtreme 1.4 is old and now that 1.51 is released 1.4 is obsolete. So yes you do need to use the restore function.
I am currently doing the same to a 59 and I can relate the experience when I'm done...just give me a few minutes.

[TeeVee]

Great, let me know!

[Traviss63]

Tried the restore function but I got this from JF...

JungleFlasher 0.1.51 Beta

Session Started Sun Mar 08 08:36:03 2009




This is a 32 bit process running on a 32 bit CPU

Found 4 I/O Ports.

Found 2 Com Ports.

Found 6 windows drives.

Found 3 CD/DVD drives.





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 35 39                                       0059            



Mode-B Done!

Restoring Stock f/w to Hitachi 0058/0059 by Mode Select Method over Port IO

UnLocked!

Dumping Flash:...................Execute Failed

[TeeVee]

Hmmmm.

Well I didn't get  the message:

QUOTE

Drive, answers normal Windows Inquiry 12 0 0 0 24 0

But drive does show up in Windows and right side of Jungle Flasher. If it shows up in Windows I'm assumig it's in modeb?

Haven't gone further cuz I'm worried. Like you getting all sorts of mysterious error messages.

[TeeVee]

Well definately modeb. Too bad JungleFlasher never sees it under port properties.

I also tried running in Safe mode...got the error "No COM ports found during enumeration"

Guess flashing in Safe Mode is not an option.