Print

[Gazcoigne]

bump coz some people were looking for the tutorial perhaps a mod should add it to the list of tuts!!!!

if any1 agrees please post to support

[tedstevens]

thank you for the guide, your effort is appreciated

so i followed the steps outlined in the guide, got the orig key, dumped the new firmware, inserted the key, encrypted it, flashed it

when i boot up, the middle LED is always blinking as if its in mode b. i put an orignial in the drive, i hear the drive spinning up but the xbox still says "opening" as if i ejected the drive. when i put a backup in the drive, the drive does not spin up (expected, it has non "fixed" firmware)

ill read up a bit more, and find look for that error guide to see what this means, but any other help in the meantime would be great

[lawdawg0931]

@Kramer987

I have several of Textbooks tutorials also (excellent help), but you mentioned Garyopa's stuff is updated frequently also. Can you please point me to a tutorial on v2.2 if you know of one. I have looked & cannot find anything other than the '7 in 1'. Thanks in advance

[tedstevens]

QUOTE(lawdawg0931 @ Oct 24 2006, 11:13 PM)

@Kramer987

I have several of Textbooks tutorials also (excellent help), but you mentioned Garyopa's stuff is updated frequently also. Can you please point me to a tutorial on v2.2 if you know of one. I have looked & cannot find anything other than the '7 in 1'. Thanks in advance (IMG:style_emoticons/default/uhh.gif)

ive used  the 7in1 v2.1 on my hitachi 46dh and it worked great- i didnt try v2.2 for 2 reasons: i dont want to revert back to and old fw and screw anything up AND my xbox 360 died! again! god damn MS repaired my 360 and it lasted 3 weeks before dying again

so try the 7in1 2.1 if you dont mind not having stealth FW because the included readme is very simple

[Gazcoigne]

QUOTE(tedstevens @ Oct 24 2006, 09:28 PM)

thank you for the guide, your effort is appreciated

so i followed the steps outlined in the guide, got the orig key, dumped the new firmware, inserted the key, encrypted it, flashed it

when i boot up, the middle LED is always blinking as if its in mode b. i put an orignial in the drive, i hear the drive spinning up but the xbox still says "opening" as if i ejected the drive. when i put a backup in the drive, the drive does not spin up (expected, it has non "fixed" firmware)

ill read up a bit more, and find look for that error guide to see what this means, but any other help in the meantime would be great

how are you getting the drive into modeb? sounds to me like you have used the cross wire method and held it too long. ive had some ppl pm me about continuous modeb, and i dont really know what you can do about it. does the drive constantly eject? i think ur laser may be damaged also, as it spins for originals, but not for backups, due to the difference in reflectivity.

[Gazcoigne]

another bump as i have seen more posts asking how this is done

MODS ADD THIS TUT!!!

[mattyv]

I agree, this is a great tut and is very helpful. The one question that I have, is the 90004000 1000 address where the key is on ALL versions of Hitachi drives (78 excluded) or just FW rev 47 ??

[Gazcoigne]

yes this key location is the same for all hitachi drive models, even the newer 78 revision.

[bigkevt]

hi m8
i`m stuck
i`ve got a copy of the dead firmware drive , a copy of the new firmware drive , i take the key from the dead drive and insert it into the new drive , then flash it back ? , cause this isnt happening for me, when i try to flash back it says , deviceIOcontrol<> failed 0
failed to initiate modeb <sense: 05/20/00>
the firmware from the dead drive is from the birdy flasher. and the firmware for the new drive is from the garyopa flasher , but when i dump the firmware with memdump that does dump a 256kb bin file, when i run it through 360 firmware toolbox i get an error firmware version not supported or not a valid firmware file,
can i just flash the whole dead firmware onto the new drive , if so what do i use

[OriginalCompGeek]

I don't have the power to add your tut to the tutorial thread, but I edited your original post with the most recent PDF link.

I'll see if I can get this added for you.  Good work.

[Textbook]

QUOTE(OriginalCompGeek @ Oct 31 2006, 07:45 PM)

I don't have the power to add your tut to the tutorial thread, but I edited your original post with the most recent PDF link.

I'll see if I can get this added for you.  Good work.

Yay  

[bigkevt]

bump

QUOTE(bigkevt @ Nov 1 2006, 02:36 AM)

hi m8
i`m stuck
i`ve got a copy of the dead firmware drive , a copy of the new firmware drive , i take the key from the dead drive and insert it into the new drive , then flash it back ? , cause this isnt happening for me, when i try to flash back it says , deviceIOcontrol<> failed 0
failed to initiate modeb <sense: 05/20/00>
the firmware from the dead drive is from the birdy flasher. and the firmware for the new drive is from the garyopa flasher , but when i dump the firmware with memdump that does dump a 256kb bin file, when i run it through 360 firmware toolbox i get an error firmware version not supported or not a valid firmware file,
can i just flash the whole dead firmware onto the new drive , if so what do i use

[Gazcoigne]

QUOTE(bigkevt @ Nov 1 2006, 12:36 AM)

hi m8
i`m stuck
i`ve got a copy of the dead firmware drive , a copy of the new firmware drive , i take the key from the dead drive and insert it into the new drive , then flash it back ? , cause this isnt happening for me, when i try to flash back it says , deviceIOcontrol<> failed 0
failed to initiate modeb <sense: 05/20/00>
the firmware from the dead drive is from the birdy flasher. and the firmware for the new drive is from the garyopa flasher , but when i dump the firmware with memdump that does dump a 256kb bin file, when i run it through 360 firmware toolbox i get an error firmware version not supported or not a valid firmware file,
can i just flash the whole dead firmware onto the new drive , if so what do i use

no you cannot simply flash the full image, if you read my tut you would know why.

strange that the fw toolbox isnt reading the fw correctly it would lead me to believe that it is a bad dump possibly, as the fw toolbox should read it perfectly. are you using v20 of the toolbox? try hexing the fw and see if it is valid. if it is all FFFFFFFF then it is no good.

from that error it seems your new drive is not in modeb, how are you putting the drives into modeb?

[bigkevt]

i`m thinking that my original firmware on new drive is now corrupt but i have a copy of the first read that i`m 100% sure is correct , i think i need to put this back on , how do i do this , then i will run through your process again , i`m using the 2 wire trick to get it into modeb that works everytime, if i can dump the firmware using memdump then i must be in modeb ?

[Gazcoigne]

yes u have got modeb if you are able to see the drive in windows and read/flash to it, so thats not the problem.

however the fact u have got a bad firmware from it is worrying. the fw cant be corrupt on the drive as u have not been able to flash it yet. and for it to work the fw has to be ok and intact, you will only be changing the key in it and you wont be able to replace it. perhaps the dump itself was corrupted and not the actual fw on the drive.

try to dump it again and see what you get, or run an opa release on it to flash it to 2.3 and use one of the dumped fw files in the key change process i outline in my tutorial.