Post by: 6h05T_R1d3R on July 14, 2006, 08:56:00 AM
Post by: slinkys4evrh on July 15, 2006, 01:35:00 PM
Running the Hitachi in another 360
After restoring my Hitachi to the original FW-state I had a crazy thought of building an external DVD-drive to use with my other 360. My idea is to enclose the Hitachi drive in an external USB-casing so I can easily hook it ip to either my PC (USB) or my 360 (SATA). In case you´re wondering how I would hook this up to my 360 without having to open it all the time read my earlier posting about the SATA-extension I made.
However as you possibly know you can´t just use the DVD-drive from one 360 in another 360 because each 360 drives firmware has it´s own unique 16-bytes key embedded. So to get the Hitachi-drive running on another machine I had to do at least the following:
* Dump the unique 16-byte key from my other 360´s Samung-drive;
* Flash the Hitachi with the obtained key from the Samsung.
Step 1 - Getting the key from the Samsung-drive
I used my earlier build bootable USB stick to boot my PC using DOS. I then used mtkflash to dump the FW of my Samsung-drive:
mtkflash r /m samsung.bin
After rebooting my PC to windows I used Keydrive Xtractor 1.5 to grab the 16-byte key from the FW like this:
Please Note: DVD Key shown is faka data
Step 2 - Preparing the FW-bin from the Hitachi
After copying the DVD-Key to the clipboard I opened the original FW from my Hitachi (orig.bin) and pasted the DVD-Key from the clipboard to the DVD-Key field. I then saved the firmware as "hits.bin".
As you probably know by now the Hitachi-FW has to be encrypted before flashing. Using a tool made by Loser named FirmCrypt I created a "ready to flash FW" using the following command:
firmcrypt e hits.bin hitse.bin
So there it is: the encrypted firmware hitse.bin ready to get flashed.
Step 3 - Flashing the Hitachi with the new key
After putting my Hitachi drive in ModeB using the SlaxVM solution I flashed the sector containing the drives key from windows XP (i being the drive-letter):
flashsec47_win i hitse.bin 90004000 1000
Please note there´s no need to flash the Master Checksum since the key is in an area of the FW not included in the checksum-calculation.
Step 4 - Attach the Hitachi to the new 360
After plugging in the power and the sata-cable (which leads to the motherboard of the new 360) and inserting COD2 it was time to fire up the new 360. And as expected: it works like a charm (IMG:style_emoticons/default/smile.gif)
So there it is: My Hitachi drive works in a 360 it wasn´t "married" to before. At least this part won´t stop me from building my external DVD-drive! Still not sure if I go through with it.
This post has been edited by slinkys4evrh: Jul 15 2006, 08:38 PM
Post by: Garaputo on July 16, 2006, 06:48:00 PM
QUOTE(slinkys4evrh @ Jul 15 2006, 08:06 PM) 
Yeah I actually did that yesterday heres how:
Running the Hitachi in another 360
After restoring my Hitachi to the original FW-state I had a crazy thought of building an external DVD-drive to use with my other 360. My idea is to enclose the Hitachi drive in an external USB-casing so I can easily hook it ip to either my PC (USB) or my 360 (SATA). In case you´re wondering how I would hook this up to my 360 without having to open it all the time read my earlier posting about the SATA-extension I made.
However as you possibly know you can´t just use the DVD-drive from one 360 in another 360 because each 360 drives firmware has it´s own unique 16-bytes key embedded. So to get the Hitachi-drive running on another machine I had to do at least the following:
* Dump the unique 16-byte key from my other 360´s Samung-drive;
* Flash the Hitachi with the obtained key from the Samsung.
Step 1 - Getting the key from the Samsung-drive
I used my earlier build bootable USB stick to boot my PC using DOS. I then used mtkflash to dump the FW of my Samsung-drive:
mtkflash r /m samsung.bin
After rebooting my PC to windows I used Keydrive Xtractor 1.5 to grab the 16-byte key from the FW like this:
Please Note: DVD Key shown is faka data
Step 2 - Preparing the FW-bin from the Hitachi
After copying the DVD-Key to the clipboard I opened the original FW from my Hitachi (orig.bin) and pasted the DVD-Key from the clipboard to the DVD-Key field. I then saved the firmware as "hits.bin".
As you probably know by now the Hitachi-FW has to be encrypted before flashing. Using a tool made by Loser named FirmCrypt I created a "ready to flash FW" using the following command:
firmcrypt e hits.bin hitse.bin
So there it is: the encrypted firmware hitse.bin ready to get flashed.
Step 3 - Flashing the Hitachi with the new key
After putting my Hitachi drive in ModeB using the SlaxVM solution I flashed the sector containing the drives key from windows XP (i being the drive-letter):
flashsec47_win i hitse.bin 90004000 1000
Please note there´s no need to flash the Master Checksum since the key is in an area of the FW not included in the checksum-calculation.
Step 4 - Attach the Hitachi to the new 360
After plugging in the power and the sata-cable (which leads to the motherboard of the new 360) and inserting COD2 it was time to fire up the new 360. And as expected: it works like a charm (IMG:style_emoticons/default/smile.gif)
So there it is: My Hitachi drive works in a 360 it wasn´t "married" to before. At least this part won´t stop me from building my external DVD-drive! Still not sure if I go through with it.
(IMG:style_emoticons/default/biggrin.gif)
Post by: 6h05T_R1d3R on July 17, 2006, 07:37:00 AM
Post by: juavos on July 17, 2006, 11:21:00 AM
Post by: Millhouse on August 03, 2006, 02:30:00 AM
Sorry, but i dont know abou this step:
Step 3 - Flashing the Hitachi with the new key
After putting my Hitachi drive in ModeB using the SlaxVM solution I flashed the sector containing the drives key from windows XP (i being the drive-letter):
flashsec47_win i hitse.bin 90004000 1000
My english is not the best, and i dont know something about drive-letter, or so...
So wher to insert this comand line?
This post has been edited by Millhouse: Aug 3 2006, 09:34 AM
Post by: Millhouse on August 03, 2006, 03:05:00 AM
drive letter, i.e.: C: E: and so on...
stupid
But where to put in the comand line, ore where to get flahsec
This post has been edited by Millhouse: Aug 3 2006, 10:09 AM
Post by: Burnie on August 26, 2006, 11:21:00 AM
But once i have made my new file as step 2.
How do i or which batch file is it to write this file to the drive
Step 3 - Flashing the Hitachi with the new key
After putting my Hitachi drive in ModeB using the SlaxVM solution I flashed the sector containing the drives key from windows XP (i being the drive-letter):
flashsec47_win i hitse.bin 90004000 1000
bearing in mind this is a 46D
Can anyone help.
Im very dubious of doing this , i have just bricked my working flashed for 3 motnhs 47DJ drive.
Post by: Burnie on August 26, 2006, 11:36:00 AM
Im getting confused over the keys.
The drive that is bricked is the one from my machine ie the 47DJ. I have the original Keys.
I then have a 46D drive obviously with different key.
Why do i need to add the keys from my 47DJ into the 46D read firmware.
Cant i just flash the 46D with my orig,bin from the 47DJ drive. wont this 47DJ jeys then marry upto the 360 its going in.
Shit this is driving me mad
Im going round in circles.
Cheers Burnie
Post by: Burnie on August 26, 2006, 12:55:00 PM
Post by: Burnie on August 27, 2006, 05:52:00 AM
Im wanting to put my keys from my 47DJ firmware. into this 46D drive. Can someone plz explain which bat file, or which sector of the firware do i flash, I dont understand step 3 clearly. I can create the new file using kdx. I have the original firmware from the 46D drive so i will mod that one. add the new keys. then save using kdx. next step im lost. Once i have flashed the 46D with the changed keys. I will update it then to OPA 2.1. (not birdys as i have heard it fooks it)
Plz can someone help me.
Thanks
Burnie
Post by: Burnie on August 27, 2006, 08:22:00 AM
Ok I wanna do this on my 46D
flashsec47_win i hitse.bin 90004000 1000
What does this mean!!
Please note there´s no need to flash the Master Checksum since the key is in an area of the FW not included in the checksum-calculation.
Do i just modify xtreme.bat so its just this one line
flashsec47_win i hitse.bin 90004000 1000
.
Plz help me, Im wanting to start, but im worried that if i flash it wrong i will brick this drive too.
burnie
and what is this
90004000 1000
when i check the xtrme.bat its this flashsec47_win %1 xtrm-e.bin 9001c000 1000
@echo Flashing sector 90003000 (Custom Code)...
@echo.
I just dotn want to balls the flash up, I know how to do this, but i need the exact correct method, if someone would advise, i would appreciate it.
Post by: Burnie on August 27, 2006, 12:28:00 PM
Post by: Burnie on August 27, 2006, 02:07:00 PM
I have followed instructions set out here how to change keys on firmware. Flashed the drive ok with hitse.bin, after i had saved files and changed keys etc.
After restarting xbox, im not getting no joy, wont boot originals.
I have checked all keys. and my workings.
Do you think because when previously I put this 46D drive into my machine, and didnt change the key not knowing...It might have changed the keys on the 360 which have to match firmware on drive. Just seems weird how something so simple isnt grafting.
Any ideas
Burnie
Only thing different is this line in command line
90004000 1000
instead one i used
90003000 1000.
Is this why it aint working
Post by: ash1471 on August 27, 2006, 02:30:00 PM
QUOTE(Burnie @ Aug 27 2006, 08:38 PM) 
Hello.
I have followed instructions set out here how to change keys on firmware. Flashed the drive ok with hitse.bin, after i had saved files and changed keys etc.
After restarting xbox, im not getting no joy, wont boot originals.
I have checked all keys. and my workings.
Do you think because when previously I put this 46D drive into my machine, and didnt change the key not knowing...It might have changed the keys on the 360 which have to match firmware on drive. Just seems weird how something so simple isnt grafting.
Any ideas
Burnie
Only thing different is this line in command line
90004000 1000
instead one i used
90003000 1000.
Is this why it aint working
This will be exactly why its not working. As you have flashed the wrong sector of the firmware
Post by: cilo911 on September 01, 2006, 03:58:00 PM
how do i go about changing the key in this ver.
someone please help
thanx
Post by: ash1471 on September 01, 2006, 04:07:00 PM
QUOTE(cilo911 @ Sep 1 2006, 11:05 PM)
i'm using opa's v2.1 7in1 firmware and when it backs up the firmware it creates like 7 files now.bin was.bin key.bin 46_21.bin gdr46.bin. they r all in a folder together only 2 of them have keys was and now key.bin i cannot open in kdx
how do i go about changing the key in this ver.
someone please help
thanx
Hello send me your samsung orig.bin and your hitatchi was.bin and I will do the hexediting for you and send it back to you and then tell you what to do with it. Send me a pm and I will provide you with my email address for you to send the files
Post by: cilo911 on September 01, 2006, 04:32:00 PM
Post by: juavos on September 14, 2006, 05:55:00 PM
I may not have to do it because now my hitachi is flashed with the 2.1 so it has fast booting just like the samsung.
Post by: Buzzar on September 21, 2006, 03:29:00 PM
QUOTE(slinkys4evrh @ Jul 15 2006, 08:06 PM)
Yeah I actually did that yesterday heres how:
Running the Hitachi in another 360
After restoring my Hitachi to the original FW-state I had a crazy thought of building an external DVD-drive to use with my other 360. My idea is to enclose the Hitachi drive in an external USB-casing so I can easily hook it ip to either my PC (USB) or my 360 (SATA). In case you´re wondering how I would hook this up to my 360 without having to open it all the time read my earlier posting about the SATA-extension I made.
However as you possibly know you can´t just use the DVD-drive from one 360 in another 360 because each 360 drives firmware has it´s own unique 16-bytes key embedded. So to get the Hitachi-drive running on another machine I had to do at least the following:
* Dump the unique 16-byte key from my other 360´s Samung-drive;
* Flash the Hitachi with the obtained key from the Samsung.
Step 1 - Getting the key from the Samsung-drive
I used my earlier build bootable USB stick to boot my PC using DOS. I then used mtkflash to dump the FW of my Samsung-drive:
mtkflash r /m samsung.bin
After rebooting my PC to windows I used Keydrive Xtractor 1.5 to grab the 16-byte key from the FW like this:
Please Note: DVD Key shown is faka data
Step 2 - Preparing the FW-bin from the Hitachi
After copying the DVD-Key to the clipboard I opened the original FW from my Hitachi (orig.bin) and pasted the DVD-Key from the clipboard to the DVD-Key field. I then saved the firmware as "hits.bin".
As you probably know by now the Hitachi-FW has to be encrypted before flashing. Using a tool made by Loser named FirmCrypt I created a "ready to flash FW" using the following command:
firmcrypt e hits.bin hitse.bin
So there it is: the encrypted firmware hitse.bin ready to get flashed.
Step 3 - Flashing the Hitachi with the new key
After putting my Hitachi drive in ModeB using the SlaxVM solution I flashed the sector containing the drives key from windows XP (i being the drive-letter):
flashsec47_win i hitse.bin 90004000 1000
Please note there´s no need to flash the Master Checksum since the key is in an area of the FW not included in the checksum-calculation.
Step 4 - Attach the Hitachi to the new 360
After plugging in the power and the sata-cable (which leads to the motherboard of the new 360) and inserting COD2 it was time to fire up the new 360. And as expected: it works like a charm
So there it is: My Hitachi drive works in a 360 it wasn´t "married" to before. At least this part won´t stop me from building my external DVD-drive! Still not sure if I go through with it.
Post by: Seeker2002 on September 28, 2006, 02:49:00 PM
QUOTE(slinkys4evrh @ Jul 15 2006, 08:06 PM)
Yeah I actually did that yesterday heres how:
Running the Hitachi in another 360
After restoring my Hitachi to the original FW-state I had a crazy thought of building an external DVD-drive to use with my other 360. My idea is to enclose the Hitachi drive in an external USB-casing so I can easily hook it ip to either my PC (USB) or my 360 (SATA). In case you´re wondering how I would hook this up to my 360 without having to open it all the time read my earlier posting about the SATA-extension I made.
However as you possibly know you can´t just use the DVD-drive from one 360 in another 360 because each 360 drives firmware has it´s own unique 16-bytes key embedded. So to get the Hitachi-drive running on another machine I had to do at least the following:
* Dump the unique 16-byte key from my other 360´s Samung-drive;
* Flash the Hitachi with the obtained key from the Samsung.
Step 1 - Getting the key from the Samsung-drive
I used my earlier build bootable USB stick to boot my PC using DOS. I then used mtkflash to dump the FW of my Samsung-drive:
mtkflash r /m samsung.bin
After rebooting my PC to windows I used Keydrive Xtractor 1.5 to grab the 16-byte key from the FW like this:
Please Note: DVD Key shown is faka data
Step 2 - Preparing the FW-bin from the Hitachi
After copying the DVD-Key to the clipboard I opened the original FW from my Hitachi (orig.bin) and pasted the DVD-Key from the clipboard to the DVD-Key field. I then saved the firmware as "hits.bin".
As you probably know by now the Hitachi-FW has to be encrypted before flashing. Using a tool made by Loser named FirmCrypt I created a "ready to flash FW" using the following command:
firmcrypt e hits.bin hitse.bin
So there it is: the encrypted firmware hitse.bin ready to get flashed.
Step 3 - Flashing the Hitachi with the new key
After putting my Hitachi drive in ModeB using the SlaxVM solution I flashed the sector containing the drives key from windows XP (i being the drive-letter):
flashsec47_win i hitse.bin 90004000 1000
Please note there´s no need to flash the Master Checksum since the key is in an area of the FW not included in the checksum-calculation.
Step 4 - Attach the Hitachi to the new 360
After plugging in the power and the sata-cable (which leads to the motherboard of the new 360) and inserting COD2 it was time to fire up the new 360. And as expected: it works like a charm
So there it is: My Hitachi drive works in a 360 it wasn´t "married" to before. At least this part won´t stop me from building my external DVD-drive! Still not sure if I go through with it.
I'm trying to see if I'm understanding this right, for flashing a Hitachi 46D and not 47D as this example shows.
flashsec47_win i hitse.bin 90004000 1000
I Should replace the above like so correct?
flashsec46_win H hitse.bin 90004000 1000 <-- My drive letter is H.. but is this the right sector to flash the
H46D, and do I use Fashsec46_win instead of Flashsec47_win?
Or does it matter?Post by: Seeker2002 on September 29, 2006, 02:29:00 PM
Post by: davbere on September 29, 2006, 03:54:00 PM
QUOTE(Seeker2002 @ Sep 29 2006, 09:36 PM)
Anyone?
That is correct use flashsec46
Dont forget that the key/bin must first be encrypted
Post by: Millhouse on October 25, 2006, 03:41:00 PM
I translate it to german, get all files and all works fine.
Testet it on hitachi 47.
Mainboard was defekt. Insert the key from the new one and all works fine again.
Post by: diablofreak on November 20, 2006, 09:03:00 AM
Post by: rocky5 on November 20, 2006, 12:14:00 PM
1. I flashed the new drive with the Maximus-Garyopa XTRM-HITACHI v2.3 Stealth Rev2 firmware and it dint work i put the drive in the 360 and it wouldnt play games i only have originals but it wouldnt play them.
2. Now i know y it dint work i never put my original drives key in the new one dint know i was to do that.
3. What i want to know is can i just get a backup of the originals firmware and flash it to the new drive then flash the new drive with the 2.3 rev2 firmware.
Will this work on my xbox 360 after i do this because the drives are the same just different keys.