Post by: spydermixx on November 03, 2006, 12:45:00 AM
I am under the impression that restoring the drive (hitachi) still results in an E66 (at least for me). If anyone in the same or similar position has fixed theirs since the update I'd love to hear how!
Post by: Mongolive on November 03, 2006, 12:50:00 AM
http://forums.xbox-scene.com/index.php?showtopic=559755
http://forums.xbox-scene.com/index.php?showtopic=559639
Post by: spydermixx on November 03, 2006, 01:10:00 PM
Post by: fat on November 03, 2006, 01:54:00 PM
I have also tried every combination of firmwares with the same results E66!!
my original dvd was a hitachy 59 but now y have a samsung.
I also tried a hitachy 47 (not 59) with mi original key with no luck
i think i need the same model and number hitachi 59dj to fix it
sorry for my english I am spanish.
Post by: Looouky on November 03, 2006, 02:03:00 PM
http://forums.xbox-scene.com/index.php?showtopic=559651
This post has been edited by Looouky: Nov 3 2006, 10:03 PM
Post by: spydermixx on November 03, 2006, 03:37:00 PM
Post by: fat on November 03, 2006, 03:46:00 PM
there is no way to reset the updatet dashboard.
Post by: myfranco on November 03, 2006, 04:02:00 PM
When i check original.bin i can see HL-DT-STDVD-ROM GDR3120L0047 in the line 3D482
What if we make the fw and then change 0047 to 0059 with 47flash.exe (the same way we insert the key)? As i had a 59dj drive which is bricked now , the dashboard would get the drive information and will return with correct code.
Is it possible?
This post has been edited by myfranco: Nov 4 2006, 12:02 AM
Post by: Looouky on November 03, 2006, 05:33:00 PM
Post by: spydermixx on November 04, 2006, 12:31:00 AM
what suprises me, is im seeing people are successfully swapping drive makes after E66 errors, i just cant work out whats going wrong with ours.
Post by: myfranco on November 04, 2006, 04:41:00 AM
I sent P.M. to Garyopa asked that.I'm waiting for answer.There must be a fix for replaced or downgraded drives.
Post by: langnao on November 04, 2006, 07:24:00 AM
Post by: myfranco on November 04, 2006, 08:07:00 AM
Would be piece of cake for Garyopa.
Post by: fat on November 04, 2006, 09:23:00 AM
Will I brick the drive? if dont
how do I use Flashsec to Write the whole firmware ?
Post by: myfranco on November 04, 2006, 10:41:00 AM
What we need is to flash a certain area which reports the correct code back to the dashboard.I found that gdr3120l0046 and 0047 are in the same adress($3D482) but 0059 is in a different adress.I have no idea if that sector is reporting the fw version back to the dash.It's just a guess.
Post by: langnao on November 04, 2006, 12:10:00 PM
QUOTE(myfranco @ Nov 5 2006, 01:48 AM) 
I think flashing the whole firmware would not be possible.(At least not with the present flasher)
What we need is to flash a certain area which reports the correct code back to the dashboard.I found that gdr3120l0046 and 0047 are in the same adress($3D482) but 0059 is in a different adress.I have no idea if that sector is reporting the fw version back to the dash.It's just a guess.
Yap, actually there are 2 portion in the whole firmware dump where it shows the drive model. First part 0x202E and the second part around 0x3D482 that you had mentioned. The first portion is the same for both 47 and 59 model but the second part, the address differs ...
My take is, if you wanna modify, just modify the model no and the date. It has to be based on your firmware. Thus one has to do a dump of the present firmware and modify accordingly and then flash back that portion. We are only touching the string portion and thus should not affect any of the rest of the code.
E.g. for the firmware of an original 47 model, after doing a dump, 'dump.bin', to change to 59 :
Hex edit 0x2030 to enter the reverse of the model (e.g u wanna change to 59) -> '95'. Hex edit 0x20D4 -> '59'. 0x20DE -> '06/01/24' (this is the date for 59).
Hex edit 0x3D49E -> '59', 0x3D4A8 -> '06/01/24' and 0x3D51C -> '95'
The instructions to flash will be (I think):
47flash %1 dump.bin 90002030 2
47flash %1 dump.bin 900020D4 2
47flash %1 dump.bin 900020DE 8
47flash %1 dump.bin 9003D49E 2
47flash %1 dump.bin 9003D4A8 8
47flash %1 dump.bin 9003D51C 2
where %1 is the drive letter
The modification has to be based on the firmware dumped out of the drive and the risk is, this is pretty much experimenting and I don't think a newbie can do it ...
Post by: langnao on November 04, 2006, 12:47:00 PM
Post by: fat on November 04, 2006, 12:26:00 PM
QUOTE(myfranco @ Nov 4 2006, 06:48 PM) 
I think flashing the whole firmware would not be possible.(At least not with the present flasher)
What we need is to flash a certain area which reports the correct code back to the dashboard.I found that gdr3120l0046 and 0047 are in the same adress($3D482) but 0059 is in a different adress.I have no idea if that sector is reporting the fw version back to the dash.It's just a guess.
the whole firmware can be flashed with flashsec command, but i dont remember the adress of the command.
there was a post some time ago pointing how to do it . but i cant found that post.
I am willing to brick the drive just for the cause. (but I think it can work, because the 2 drives are the same but
with different rom version.
am i wrong?
Post by: langnao on November 04, 2006, 12:43:00 PM
QUOTE(fat @ Nov 5 2006, 03:33 AM)
the whole firmware can be flashed with flashsec command, but i dont remember the adress of the command.
there was a post some time ago pointing how to do it . but i cant found that post.
I am willing to brick the drive just for the cause. (but I think it can work, because the 2 drives are the same but
with different rom version.
am i wrong?
Don't do that, you will brick your drive.
If this can be done, there won't be a need to detect the version of the drive and flash accordingly to the different firmware which was included in the fwpack ....
Post by: myfranco on November 04, 2006, 01:56:00 PM
In any case it's a good progess and needs to be confirmed(with mosifications as well)
Post by: langnao on November 04, 2006, 08:51:00 PM
The address to hex edit:
0x2030 -> 74
0x20D4 -> 47
0x20DE -> 05/07/27
0x3D4BA -> 47
0x3D4C4 -> 05/07/27
0x3D538 -> 74
59flash %1 dump.bin 90002030 2
59flash %1 dump.bin 900020D4 2
59flash %1 dump.bin 900020DE 8
59flash %1 dump.bin 9003D4BA 2
59flash %1 dump.bin 9003D4C4 8
59flash %1 dump.bin 9003D538 2
Post by: myfranco on November 05, 2006, 01:03:00 AM
Post by: myfranco on November 05, 2006, 03:52:00 AM
Post by: langnao on November 05, 2006, 04:40:00 AM
The best way is to try just the first line then do a memdump back to compare if it is corrent ... Any help from Garyopa?
Post by: myfranco on November 05, 2006, 05:22:00 AM
We need to be sure about 90003000? thingy.However , if we slip one byte over , I don't want to think what may happen
Post by: langnao on November 05, 2006, 07:13:00 AM
QUOTE(myfranco @ Nov 5 2006, 08:29 PM)
You may be right but if it's different than what we think,the drive could be bricked.I sent P.M. to Gayopa and started a topic no answer yet.He must be busy.Soon or later,he will solve this problem.
We need to be sure about 90003000? thingy.However , if we slip one byte over , I don't want to think what may happen
But seriously, if this solves the problem, it creates more problem later. For future update, you have to either change the drive model back to original or modify the flashing script so that the correct drive version will be detected. BTW, the 'GETHITV.EXE' that is used to detected the drive version based on the firmware, only check the first portion of the firmware (2 portion of the firmware that indicates the drive model)....
Post by: myfranco on November 05, 2006, 09:07:00 AM
The problem is there is no confirmation yet.I still don't know if 9003000 thingy bricks the drive or not.
Thank you for your contribution anyway.We keep doing this.
Post by: northernmonkey on November 05, 2006, 12:09:00 PM
I have tried using the Hitachi key with Xtreme 4.2a .... I get error E66 (only after dash update)
I have tried using the Hitachi key with Xtreme 3.3 as it was a MS25 drive but still E66
I have tried using the Hitachi key on a original MS25 fw (from a different xbox again) ... still E66
I still have a full backup of the 59b Hitachi fw (the orginal drive from this xbox360) I have 'A' ms25 firmware release but from a different system completley I do not have the original ms25 fw that belongs to the drive Im trying to install!
I have done cleared the cache, I have tried the system resest too in system info but it doesnt appear to do anything.
Is there a way around this? A Fix for someone who has replaced a Hitachi with a Samsung?
Or perhaps someone out there is in the simular position Im in .. but opposite way around .. needs a samsung back in there machine and wants to swap for a 59b hitachi? (or any hitachi if its compatible)
Post by: myfranco on November 05, 2006, 03:15:00 PM
In this topic we are trying to change some sectors in hitachi fw and it seems that yours is more complicated.
Post by: segaboys on November 05, 2006, 03:09:00 PM
I had a XBOX 360 with a Hitachi 47D firmware DVD Drive.
The Hitachi Bricked before I could retrieve the unique Key....... (Long story)
I then bought a new XBOX 360 motherboard (Manufactured Jun/Jul 2005)
I do not know what DVD Drive was originally bundled with the MotherBoard
I bought a V32CE Hitachi DVD Drive which was a pre-release DVD Drive (As I found out later)
I had to upgrade the V32 Firmware to V40 to get it to play original games
I could then Patch the firmware and everything worked sweetly
Then the Fall update..... ERROR66
How screwed am I?????
Post by: myfranco on November 05, 2006, 04:17:00 PM
If it was a hitachi married with that motherboard,could be v59 or v78.
If we find out how this one is fixed , you can also do that.
Post by: garyopa on November 05, 2006, 06:24:00 PM
to reply back as v59 which will help those that have "downgraded" to
an older Hitachi from their original Hitachi version.
The E66 error appears it seems only on those units which people have
used on Live and Upgraded the dashboard since stock version, and
then afterwards have swapped their DVD drive or replaced it with an
older "version build" then what they had before in their system, and
applied the newer "fall update".
This idea of patching the Hitachi firmware will not currently help
those that have switched from a Samsung drive to an Hitachi,
or vice-versa, only for those that have downgraded their Hitachi.
You need to change the following locations:
starting at >2030 (2 bytes) backwards version becomes "95"
starting at >20D4 (2 bytes) forewards version becomes "59"
starting at >20DE (8 bytes) ver. build date becomes "06/01/24"
and the same change again at:
starting at >3D49E (2 bytes) forewards version becomes "59"
starting at >3D4A8 (8 bytes) ver. build date becomes "06/01/24"
starting at >3D51C (2 bytes) backwards version becomes "95"
And then you need to "encrypt" the hex-edited firmware before flashing:
firm e upped.bin upped-e.bin <---- Encrypt the "upped" firmware
And finally you need to "flash" the changed sectors:
47flash H upped-e.bin 90002000 1000 <---- Flash the first changed sector
47flash H upped-e.bin 9003D000 1000 <---- Flash the second changed sector
NOTE: The following changes currently have only been tested
on the NON-STEALTH versions of firmware, if you are trying to
do this on a STEALTHed firmware you MAY also need to first
UN-STEALTH your firmware by doing the following:
firm e orig.bin orig-e.bin <---- Encrypt the untouched original firmware
47flash H orig-e.bin 90033000 1000 <--- Flash back the READ part, to unstealth the firmware
P.S.: In the above examples and commands, replace the "H" with your CORRECT drive letter.
AGAIN I MUST WARN YOU PLEASE READ THRU EVERYTHING FIRST, AND ONLY TRY THIS IF YOU ARE
SURE OF WHAT YOU ARE DOING AND UNDERSTAND ALL THE RISKS (BRICKING YOUR DRIVE) IN DOING SO.
Post by: langnao on November 05, 2006, 07:15:00 PM
QUOTE(garyopa @ Nov 6 2006, 08:55 AM) 
In theory you should be able to patch the v40, v46, v47, v58 firmwares
to reply back as v59 which will help those that have "downgraded" to
an older Hitachi from their original Hitachi version.
The E66 error appears it seems only on those units which people have
used on Live and Upgraded the dashboard since stock version, and
then afterwards have swapped their DVD drive or replaced it with an
older "version build" then what they had before in their system, and
applied the newer "fall update".
This idea of patching the Hitachi firmware will not currently help
those that have switched from a Samsung drive to an Hitachi,
or vice-versa, only for those that have downgraded their Hitachi.
You need to change the following locations:
starting at >2030 (2 bytes) backwards version becomes "95"
starting at >20D4 (2 bytes) forewards version becomes "59"
starting at >20DE (8 bytes) ver. build date becomes "06/01/24"
and the same change again at:
starting at >3D49E (2 bytes) forewards version becomes "59"
starting at >3D4A8 (8 bytes) ver. build date becomes "06/01/24"
starting at >3D51C (2 bytes) backwards version becomes "95"
And then you need to "encrypt" the hex-edited firmware before flashing:
firm e upped.bin upped-e.bin <---- Encrypt the "upped" firmware
And finally you need to "flash" the changed sectors:
47flash H upped-e.bin 90002000 1000 <---- Flash the first changed sector
47flash H upped-e.bin 9003D000 1000 <---- Flash the second changed sector
NOTE: The following changes currently have only been tested
on the NON-STEALTH versions of firmware, if you are trying to
do this on a STEALTHed firmware you MAY also need to first
UN-STEALTH your firmware by doing the following:
firm e orig.bin orig-e.bin <---- Encrypt the untouched original firmware
47flash H orig-e.bin 90033000 1000 <--- Flash back the READ part, to unstealth the firmware
P.S.: In the above examples and commands, replace the "H" with your CORRECT drive letter.
AGAIN I MUST WARN YOU PLEASE READ THRU EVERYTHING FIRST, AND ONLY TRY THIS IF YOU ARE
SURE OF WHAT YOU ARE DOING AND UNDERSTAND ALL THE RISKS (BRICKING YOUR DRIVE) IN DOING SO.
gary replies.... Thanks man ... (IMG:style_emoticons/default/smile.gif)
myfranco, I think you could can consider doing a restore first to put the firmware back to original state (without stealth, etc).
Then implement the changes as what garyopa had mentioned before running the flash23s.bat script. However, now to the script, your drive will be '59' and thus u need to modify flash23s.bat to run the correct flashing program. Just replace all 59flash under the :FLASH5X to be 47flash.
All the best and waits your good news...
Post by: Xx The 0ne xX on November 05, 2006, 08:00:00 PM
Post by: averian on November 05, 2006, 08:04:00 PM
Story: Refurb Xbox with Samsung ms25 swapped in place of its original Hitachi 47DJ 3 months ago. Not even the stock original firmware would work on the Samsung ms25 after the update (e66).
THE FIX: Manual hexedit of Samsung ms25 firmware to replace mentions of TS-H943 with equivalent code from original Hitachi 47DJ firmware. (starts around $2020, be diligent here as there are some slight differences, use the Samsung's syntax). Now original edited Samsung firmware works, as should any edited xtreme firmware without any e66 error!
Post by: myfranco on November 05, 2006, 08:05:00 PM
I'll try this later.It's 5 A.M. here in Turkey and i don't feel i can do this without an error.I'll have a good sleep than will do it.
Again Thank you so much.
Post by: langnao on November 05, 2006, 08:50:00 PM
QUOTE(averian @ Nov 6 2006, 10:35 AM)
Hey guys...I have your fix for those that swapped original Hitachi's for replacement Samsungs.
Story: Refurb Xbox with Samsung ms25 swapped in place of its original Hitachi 47DJ 3 months ago. Not even the stock original firmware would work on the Samsung ms25 after the update (e66).
THE FIX: Manual hexedit of Samsung ms25 firmware to replace mentions of TS-H943 with equivalent code from original Hitachi 47DJ firmware. (starts around $2020, be diligent here as there are some slight differences, use the Samsung's syntax). Now original edited Samsung firmware works, as should any edited xtreme firmware without any e66 error!
cool... replacing hitachi drive model string onto samsung drive ... But what about the manufacturing date? Seems to me samsung drive does not have that.
Can see that '0074 LHD--TTSVD-DOR MDG3R21L0' from a hitachi drive can fit into 'sm52 STTSocprVD-DOR MSTH-49A3' of a sumsung, exactly 32bytes. The second part, non-inverted one not so obvious cos of the date part on the hitachi firmware ...
Ha, pretty risky business here since one could mess up some byte on the samsung firmware and possibly brick it in the process ...
This post has been edited by langnao: Nov 6 2006, 04:51 AM
Post by: langnao on November 05, 2006, 09:24:00 PM
QUOTE(averian @ Nov 6 2006, 10:35 AM)
Hey guys...I have your fix for those that swapped original Hitachi's for replacement Samsungs.
Story: Refurb Xbox with Samsung ms25 swapped in place of its original Hitachi 47DJ 3 months ago. Not even the stock original firmware would work on the Samsung ms25 after the update (e66).
THE FIX: Manual hexedit of Samsung ms25 firmware to replace mentions of TS-H943 with equivalent code from original Hitachi 47DJ firmware. (starts around $2020, be diligent here as there are some slight differences, use the Samsung's syntax). Now original edited Samsung firmware works, as should any edited xtreme firmware without any e66 error!
Care to provide more info?
Eg. To replace samsung MS25 with hitachi 47 model, copy from 0x202E - 0x204D from hitachi firmware to 0x202E - 0x204D of samsung firmware? Copy 0x20BA - 0x20EA from hitachi firmware to 0x20BC - 0x20EC?
This info will be useful for those who had swapped original hitachi drive with samsung ...
Post by: averian on November 05, 2006, 11:17:00 PM
QUOTE
cool... replacing hitachi drive model string onto samsung drive ... But what about the manufacturing date? Seems to me samsung drive does not have that.
Can see that '0074 LHD--TTSVD-DOR MDG3R21L0' from a hitachi drive can fit into 'sm52 STTSocprVD-DOR MSTH-49A3' of a sumsung, exactly 32bytes. The second part, non-inverted one not so obvious cos of the date part on the hitachi firmware ...
Ha, pretty risky business here since one could mess up some byte on the samsung firmware and possibly brick it in the process ...
Can see that '0074 LHD--TTSVD-DOR MDG3R21L0' from a hitachi drive can fit into 'sm52 STTSocprVD-DOR MSTH-49A3' of a sumsung, exactly 32bytes. The second part, non-inverted one not so obvious cos of the date part on the hitachi firmware ...
Ha, pretty risky business here since one could mess up some byte on the samsung firmware and possibly brick it in the process ...
If a byte is wrong on the Samsung firmware, just reflash it...I had to in experimenting, no bricks. Easiest answer in manually hexediting is just to follow the syntax of the Samsung firmware, not the syntax of the Hitachi firmware. IE, since the Samsung has no manufacturing date, don't copy that.
Details of mine, though unchecked on others are:
copy 0x202e - 0x204d from Hitachi 47DJ to Samsung 0x202e - 0x204d
copy 0x20b3 - 0x20d5 from Hitachi 47DJ to Samsung 0x20b5 - 0x20d7
Post by: spydermixx on November 06, 2006, 01:48:00 AM
QUOTE(averian @ Nov 6 2006, 02:35 AM)
Hey guys...I have your fix for those that swapped original Hitachi's for replacement Samsungs.
Story: Refurb Xbox with Samsung ms25 swapped in place of its original Hitachi 47DJ 3 months ago. Not even the stock original firmware would work on the Samsung ms25 after the update (e66).
THE FIX: Manual hexedit of Samsung ms25 firmware to replace mentions of TS-H943 with equivalent code from original Hitachi 47DJ firmware. (starts around $2020, be diligent here as there are some slight differences, use the Samsung's syntax). Now original edited Samsung firmware works, as should any edited xtreme firmware without any e66 error!
quick question for you averian, im in the same situation as you (i think) only the other way around (swapped mobos and have one now that orignally came with a samsung or so im led to believe). my question is what command line did you use to flash the modified fw?
Post by: langnao on November 06, 2006, 02:20:00 AM
QUOTE(averian @ Nov 6 2006, 01:48 PM)
If a byte is wrong on the Samsung firmware, just reflash it...I had to in experimenting, no bricks. Easiest answer in manually hexediting is just to follow the syntax of the Samsung firmware, not the syntax of the Hitachi firmware. IE, since the Samsung has no manufacturing date, don't copy that.
Details of mine, though unchecked on others are:
copy 0x202e - 0x204d from Hitachi 47DJ to Samsung 0x202e - 0x204d
copy 0x20b3 - 0x20d5 from Hitachi 47DJ to Samsung 0x20b5 - 0x20d7
the first part is straight forward 'copy 0x202e - 0x204d from Hitachi 47DJ to Samsung 0x202e - 0x204d'
the second part I think from copy 0x20b6 - 0x20d5 from Hitachi to Samsung 0x20b8 - 0x20d7 will be much better since it is exactly 32bytes like the first part. But shouldn't matter much as the extra few bytes that you had included happen to be the same on Samsung ...
Cool, I wonder whether the reverse will work, from Samsung to Hitachi? I think so in theory....
QUOTE(spydermixx @ Nov 6 2006, 04:55 PM)
quick question for you averian, im in the same situation as you (i think) only the other way around (swapped mobos and have one now that orignally came with a samsung or so im led to believe). my question is what command line did you use to flash the modified fw?
spydermixx, yours a bit more complicated cos hitachi firmware is encrypted and each modification you have to follow what garyopa had highlighted. But in theory it should work. But your combination is pretty limited, either a MS25 or MS28 (or maybe an older model)...
BTW, flashing a samsung drive is much easier than hitachi which u only modified a portion of the firmware. You really run out of all other options? What is your present hitachi drive model?
Awaiting myfranco results ...
Post by: spydermixx on November 06, 2006, 02:39:00 AM
i just about nearly slapped myself when i realised to flash the hitachi with samsung info id need to know sectors to flash. the worst part is i can only contemplate the replacement mobo originally came with a samsung drive as the seller is somewhat unresponsive and I have had to go by his auction history on ebay to find what other replacement parts he sold.
what i might do is when i come home from work and have more time is to try "upgrading" my hitachi to a 59 to see if that sorts it. im not holding out much hope for it though to be perfectly honest.
Post by: segaboys on November 06, 2006, 04:42:00 AM
I am in the same situation as you, actually probably worse....
I have a replacement MB which I think had a samsung drive but not sure...
I have already upgraded my V32CE to V40
I will now edit it to make it appear as a V59 courtesy of GaryOpa's method.
If that does not work I would assume its a motherboard married to a Samsung Drive
To clear up some things in my head... Does the following work?
copy 0x202e - 0x204d from Hitachi 47DJ to Samsung 0x202e - 0x204d
copy 0x20b3 - 0x20d5 from Hitachi 47DJ to Samsung 0x20b5 - 0x20d7
On my edited V40/V59 Hitachi
0x202e - 0x204d equals "0095 LHD--TTSVD-DOR MDG3R21L0"
0x20b3 - 0x20d5 equals "..2[...HL-DT-STDVD-ROM GDR3120L0059"
I think 0x20b3 - 0x20d5 probably should be 0x20ba - 0x20d6 which equals "HL-DT-STDVD-ROM GDR3120L00590"
Is it possible for someone to post what appears on a Samsung at the following addresses as I am at work and dont' have access to any samsung firmware?
Samsung 0x202e - 0x204d
Samsung 0x20b5 - 0x20d7
Thanks in advance....
Post by: langnao on November 06, 2006, 05:38:00 AM
QUOTE(segaboys @ Nov 6 2006, 07:13 PM)
spydermixx,
I am in the same situation as you, actually probably worse....
I have a replacement MB which I think had a samsung drive but not sure...
I have already upgraded my V32CE to V40
I will now edit it to make it appear as a V59 courtesy of GaryOpa's method.
If that does not work I would assume its a motherboard married to a Samsung Drive
To clear up some things in my head... Does the following work?
copy 0x202e - 0x204d from Hitachi 47DJ to Samsung 0x202e - 0x204d
copy 0x20b3 - 0x20d5 from Hitachi 47DJ to Samsung 0x20b5 - 0x20d7
On my edited V40/V59 Hitachi
0x202e - 0x204d equals "0095 LHD--TTSVD-DOR MDG3R21L0"
0x20b3 - 0x20d5 equals "..2[...HL-DT-STDVD-ROM GDR3120L0059"
I think 0x20b3 - 0x20d5 probably should be 0x20ba - 0x20d6 which equals "HL-DT-STDVD-ROM GDR3120L00590"
Is it possible for someone to post what appears on a Samsung at the following addresses as I am at work and dont' have access to any samsung firmware?
Samsung 0x202e - 0x204d
Samsung 0x20b5 - 0x20d7
Thanks in advance....
Yap if going to '59' doesn't work for u, most probably you are having a samsung drive originally.
It works for averian but his is modifying samsung to show hitachi model.
The first part is pretty must the same but the second part, I think,
hitach 0x20b6 - 0x20d5 to samsung 0x20b8 - 0x20d7
will be must better choice since it is 32byes like the first part.
averian copied a bit more for the hitachi at 0x20b3, 0x20b4 and 0x20b5 which happens to be '80 00 32'. On the samsung 0x20b5, 0x20b6 and 0x20b7 also happens to be '80 00 32'. Thus I think 32 bytes are enough ...
For MS25:
Samsung 0x202e - 0x204d :
sm52 STTSocprVD-DOR MSTH-49A3 (ASCII)
736D353220202020535454536F63707256442D444F52204D5354482D34394133 (in hex)
Samsung 0x20b5 - 0x20d7 :
..2[...TSSTcorpDVD-ROM TS-H943Ams25 (ASCII)
8000325B00000054535354636F72704456442D524F4D2054532D48393433416D733235 (hex)
Post by: segaboys on November 06, 2006, 05:42:00 AM
This is the info I have been able to dig up based on hardware revisions.
Hardware Rev: 01 = v10 and v27
Hardware Rev: 02 = v32 and v36 and v40
Hardware Rev: 03 = v46 and v47 and v58 and v59
Cheers
Post by: langnao on November 06, 2006, 05:49:00 AM
QUOTE(spydermixx @ Nov 6 2006, 05:46 PM)
right now i have a hitachi 46dh. I should be getting a sammy drive in the next few weeks from the BST part of the forums but being a fairly impatient person I would prefer to fix the hitachi so it works sooner rather than later (IMG:style_emoticons/default/biggrin.gif)
i just about nearly slapped myself when i realised to flash the hitachi with samsung info id need to know sectors to flash. the worst part is i can only contemplate the replacement mobo originally came with a samsung drive as the seller is somewhat unresponsive and I have had to go by his auction history on ebay to find what other replacement parts he sold.
what i might do is when i come home from work and have more time is to try "upgrading" my hitachi to a 59 to see if that sorts it. im not holding out much hope for it though to be perfectly honest.
Best is to restore the firmware to original state where it is unstealth and do the respective modification. Then encrypt and then flash sector 9002000 & 9003D000, both sector where the drive model appears.
The troublesome part is applying back garyopa firmware. As you had changed the drive model, the original back script will not work. You had to modified the script. There are a number of ways to do it. Either you modify the respective firmwares in the FWPACK or you enter those commands to change the drive model yourself and run the modified flashing script that contains only the flashing routines for your specific drive model (minus off the checking of the drive model)
Post by: myfranco on November 06, 2006, 06:10:00 AM
From what i understood to avoid E66 error , this is what we need to do:
1-Assuming we have a flashed v32 , v46 , v47 with stealth , we first un-stealth the firmware
2-firm e orig.bin orig-e.bin <---- Encrypt the untouched original firmware
47flash Driveletter orig-e.bin 90033000 1000 <--- Flash back the READ part, to unstealth the firmware
3-Restore the drive to its original Firmware.We have now the original firmware without any modification.
4-We flash the drive with Garyopa 2.3.Until this point we have a working drive but giving E66 error
5-Hexediting the original firmware :
starting at >2030 (2 bytes) backwards version becomes "95"
starting at >20D4 (2 bytes) forewards version becomes "59"
starting at >20DE (8 bytes) ver. build date becomes "06/01/24"
The second part of the firmware:
starting at >3D49E (2 bytes) forewards version becomes "59"
starting at >3D4A8 (8 bytes) ver. build date becomes "06/01/24"
starting at >3D51C (2 bytes) backwards version becomes "95
6-After hexediting we encrypt the firmware:
firm e orig.bin orig-e.bin and rename to fake59.bin
7- 47flash H fake59.bin 90002000 1000 <---- Flash the first changed sector
47flash H fake59.bin 9003D000 1000 <---- Flash the second changed sector
That is how it has to be ,right?
To me ,we need to flash the drive before changing v32,v46,v47 to v59.Since we don't touch any flashed sector during the modification,that would not have any effect on the firmware.
Flashing the drive after the modifications might have different effects,i think.
@Langnao why flashing the drive before modifications? We can flash the drive first then we can make those modifications.In that case,there won't be any need to change Garyopa's flashing script.
This post has been edited by myfranco: Nov 6 2006, 02:27 PM
Post by: langnao on November 06, 2006, 06:27:00 AM
QUOTE(myfranco @ Nov 6 2006, 08:41 PM)
----------Hitachi v32,v46,v47 to Hitachi v59 to avoid E66 Error----------------
From what i understood to avoid E66 error , this is what we need to do:
1-Assuming we have a flashed v32 , v46 , v47 with stealth , we first un-stealth the firmware
2-firm e orig.bin orig-e.bin <---- Encrypt the untouched original firmware
47flash Driveletter orig-e.bin 90033000 1000 <--- Flash back the READ part, to unstealth the firmware
3-Restore the drive to its original Firmware.We have now the original firmware without any modification.
4-We flash the drive with Garyopa 2.3.Until this point we have a working drive but giving E66 error
5-Hexediting the original firmware :
starting at >2030 (2 bytes) backwards version becomes "95"
starting at >20D4 (2 bytes) forewards version becomes "59"
starting at >20DE (8 bytes) ver. build date becomes "06/01/24"
The second part of the firmware:
starting at >3D49E (2 bytes) forewards version becomes "59"
starting at >3D4A8 (8 bytes) ver. build date becomes "06/01/24"
starting at >3D51C (2 bytes) backwards version becomes "95
6-After hexediting we encrypt the firmware:
firm e orig.bin orig-e.bin and rename to fake59.bin
7- 47flash H fake59.bin 90002000 1000 <---- Flash the first changed sector
47flash H fake59.bin 9003D000 1000 <---- Flash the second changed sector
That is how it has to be ,right?
To me ,we need to flash the drive before changing v32,v46,v47 to v59.Since we don't touch any flashed sector during the modification,that would not have any effect on the firmware.
Flashing the drive after the modifications might have different effects,i think.
@Langnao why flashing the drive before modifications? We can flash the drive first then we can make those modifications.In that case,there won't be any need to change Garyopa's flashing script.
Running the restore.bat will restore everything back to original which include unstealth ,etc. garyopa mentioned that the method recommended was tested on unstealth firmware and thus it is better to unstealth it. Based on your steps, step 2, you unstealth the drive then step 4 u run the script to flash the drive which will stealth it again. Also, each time before running the modified firmware, it is better to run the restore.bat which will restore everything to default cos u only unstealth in step 2, but other things like Security Sector Read, Media Detect, etc was still there ...
This post has been edited by langnao: Nov 6 2006, 02:29 PM
Post by: myfranco on November 06, 2006, 06:32:00 AM
And actually,after the step 2 and 3 ,we would have original firmware.After step 4 we need to un-stealth it again.
When i mean original.bin , i mean the very first original.bin
This post has been edited by myfranco: Nov 6 2006, 02:35 PM
Post by: langnao on November 06, 2006, 06:43:00 AM
E.g if your drive is 47, modified the 2 files 47_23.BIN and 47_23S.BIN accordingly to reflect the new drive. Assuming you are running flash23s.bat cos if you are running flash16s.bat, you have to modify the 47_16.BIN and 47_16S.BIN instead.
Then open flash23s.bat, go and find under :FLASH47, just below it, enter these 2 lines,
47flash %1 xtrm-e.bin 90002000 1000
47flash %1 xtrm-e.bin 9003D000 1000
Everything is pretty much intact. Not much modification to flash23s.bat script. The script first check for the version of your drive from the firmware dump of your drive. It will detect as 47(assume). Then it proceed to prepare the mod. firmware to flash for your drive. Since we had modified the firmware in the FWPACK.RAR to reflect the new drive model, these steps are automated. It will proceed to the script portion for 47 and starts flashing. The first 2 lines are the command to modified the drive model, then it will proceed with the rest of the modification ...
Post by: myfranco on November 06, 2006, 06:52:00 AM
What i want to know is can we make the FW stealth after everything is finished?
Garyopa mentioned that must be un-stealth to do those mods.In that case , after restoring , flashing , un-stealthing and modifing we can stealt the firmware.Would there be any problem with that?
Post by: langnao on November 06, 2006, 07:00:00 AM
QUOTE(myfranco @ Nov 6 2006, 09:03 PM)
Yeah you're right.After flashing the drive we better un-stealth it again so that it won't be any problem.
And actually,after the step 2 and 3 ,we would have original firmware.After step 4 we need to un-stealth it again.
When i mean original.bin , i mean the very first original.bin
Another way if you don't have to redo everything, remove steps 3 & 4. And then ended with stealth the firmware back after you had completed everything. Thus in summary, first you unstealth as in step 2. Then you proceed to step 5 where you do all the necessary changes to change the drive model and then step 6 where you encrypt the changes and then step 7 where u flash back to drive. Then you have to stealth back the drive. But to stealth the drive, you need to prepare the respective firmware that comes with the FWPACK.RAR and alot of the steps that were listed in the flash23s.bat ...
QUOTE(myfranco @ Nov 6 2006, 09:23 PM)
@Langnao that's pretty automated.Good thinking.
What i want to know is can we make the FW stealth after everything is finished?
Garyopa mentioned that must be un-stealth to do those mods.In that case , after restoring , flashing , un-stealthing and modifing we can stealt the firmware.Would there be any problem with that?
That's why the first method is better cos when running garyopa script, after the 9 modifications, eg Xtreme Custom Code, Master Checksum ,etc. It ended with doing FW STEALTH DATA/CODE and FW STEALTH HACK ...
The only troublesome part is modifying the firmware in FWPACK.RAR.
Post by: myfranco on November 06, 2006, 07:08:00 AM
firm e garyopaFW.bin garyopaFW-e.bin (gave the name just to show which fw to be flashed)
47flash H garyopaFW-e.bin 90033000 1000 now the FW in the drive must be stealth
Is that so ? or do i need another thing to stealth it?
OR:
47flash H garyopaFW-e.bin 90005000 1000 FW STEALTH DATA/CODE
47flash H garyopaFW-e.bin 90033000 1000 FW STEALTH HACK
which of them?
And one more thing. I believe we are confused about this modification(to make it look like v59) for this modification we can use original.bin because those sectors are not flashed with garyopa , untouched.
Restoring the drive , flashing with Garyopa , un stealthing ,modifing the original fw to v59 , flashing v59 sectors to the drive then stealthing would be enough.In that case ,the last command must be this:
47flash H garyopaFW-e.bin 90005000 1000 FW STEALTH DATA/CODE
47flash H garyopaFW-e.bin 90033000 1000 FW STEALTH HACK
This post has been edited by myfranco: Nov 6 2006, 03:19 PM
Post by: langnao on November 06, 2006, 07:19:00 AM
QUOTE(myfranco @ Nov 6 2006, 09:39 PM)
Ok i got it.When everything is done , we would have a modified and non stealth firmware which DOES NOT give E66 error.However,the firmware would be non stealth right?
firm e garyopaFW.bin garyopaFW-e.bin (gave the name just to show which fw to be flashed)
47flash H garyopaFW-e.bin 90033000 1000 now the FW in the drive must be stealth
Is that so ? or do i need another thing to stealth it?
OR:
47flash H garyopaFW-e.bin 90005000 1000 FW STEALTH DATA/CODE
47flash H garyopaFW-e.bin 90033000 1000 FW STEALTH HACK
which of them?
No need to do 90005000 (FW STEALTH DATA/CODE) since it was not undone as only 90033000 FW STEALTH HACK was undone.
After you had completed everything, you will have to use 47_23S.bin, encrypt it and then flash the stealth portion back.
Eg.
firm e 47_23S.bin xtrm-es.bin
47flash %1 xtrm-es.bin 90033000 1000
You run all these yourself, you don't have any error checking like those in garyopa script thus hopefully all goes well ...
Post by: myfranco on November 06, 2006, 07:29:00 AM
Thank you for your contribution.I'll think everything than will flash it.
Post by: segaboys on November 06, 2006, 07:45:00 AM
I have a V32 drive upgrade to V40
Which of the following do I use...
46FLASH.EXE
47FLASH.EXE
59FLASH.EXE
Thanks
Post by: langnao on November 06, 2006, 07:57:00 AM
QUOTE(segaboys @ Nov 6 2006, 10:16 PM)
How do you know which version of Flash to use?
I have a V32 drive upgrade to V40
Which of the following do I use...
46FLASH.EXE
47FLASH.EXE
59FLASH.EXE
Thanks
V40 goes to :FLASH4X of the script which is using 46FLASH.EXE to flash ...
Post by: Bluenose on November 06, 2006, 07:53:00 AM
QUOTE(langnao @ Nov 6 2006, 02:09 PM)
Yap if going to '59' doesn't work for u, most probably you are having a samsung drive originally.
It works for averian but his is modifying samsung to show hitachi model.
The first part is pretty must the same but the second part, I think,
hitach 0x20b6 - 0x20d5 to samsung 0x20b8 - 0x20d7
will be must better choice since it is 32byes like the first part.
averian copied a bit more for the hitachi at 0x20b3, 0x20b4 and 0x20b5 which happens to be '80 00 32'. On the samsung 0x20b5, 0x20b6 and 0x20b7 also happens to be '80 00 32'. Thus I think 32 bytes are enough ...
For MS25:
Samsung 0x202e - 0x204d :
sm52 STTSocprVD-DOR MSTH-49A3 (ASCII)
736D353220202020535454536F63707256442D444F52204D5354482D34394133 (in hex)
Samsung 0x20b5 - 0x20d7 :
..2[...TSSTcorpDVD-ROM TS-H943Ams25 (ASCII)
8000325B00000054535354636F72704456442D524F4D2054532D48393433416D733235 (hex)
I can confirm that this method worked for me. I have a samsung ms25 flashed to x42a working in box that had a hitachi 59dj that gave me e66 with the samsung (tried every fw possible). I just hex edited the same lines from averian's post (thanks) with the ones from my orignal hitachi.bin into my x42a.bin. I checked the bin with 360fwtoolbox and my key was all fffffffffffffff's so this might be something to look out for. I have been on live and everything seems ok.
Post by: averian on November 06, 2006, 11:15:00 AM
copy 0x202e - 0x204d from Hitachi 47DJ to Samsung 0x202e - 0x204d
copy 0x20b6 - 0x20d5 from Hitachi 47DJ to Samsung 0x20b8 - 0x20d7
Post by: myfranco on November 06, 2006, 11:26:00 AM
Story : Hitachi v59 got bricked with Birdy Flasher then we bought a Hitachi v47 , flashed and injected the key.It worked fine.After the fall update 360 was giving E66 Error since it was married with a hitachi v59 but there was v47 at that moment.
Solution :
1 - Flashed back to original Firmware (used restore.bat command in Garyopa 2.3 )
2 - Flashed with Garyopa 2.3 (thank you to Garyopa)
3 - Unstealthed the firmware with the encrypted original.bin :
47flash H orig-e.bin 90033000 1000 --->this is the very first original firmware.
4 - Hexedited original.bin and changed v47 information to v59 to make Xbox 360 return with the correct code:
QUOTE
starting at >2030 (2 bytes) backwards version becomes "95"
starting at >20D4 (2 bytes) forewards version becomes "59"
starting at >20DE (8 bytes) ver. build date becomes "06/01/24"
and the same change again at:
starting at >3D49E (2 bytes) forewards version becomes "59"
starting at >3D4A8 (8 bytes) ver. build date becomes "06/01/24"
starting at >3D51C (2 bytes) backwards version becomes "95" taken from Garyopa
starting at >20D4 (2 bytes) forewards version becomes "59"
starting at >20DE (8 bytes) ver. build date becomes "06/01/24"
and the same change again at:
starting at >3D49E (2 bytes) forewards version becomes "59"
starting at >3D4A8 (8 bytes) ver. build date becomes "06/01/24"
starting at >3D51C (2 bytes) backwards version becomes "95" taken from Garyopa
saved the bin file as fake59 then encrypted with Firmware Toolbox 1.2
5 - Again with Garyopa's X-LG folder:
47flash.exe H fake59.bin 90002000 1000 <---- Flash the first changed sector
47flash.exe H fake59.bin 9003D000 1000 <---- Flash the second changed sector
(Where H is the drive letter)
Turned 360 off.Plugged all the cable and played Splinter Cell Double Agent (IMG:style_emoticons/default/biggrin.gif)
I want to thank to Garyopa and Langnao for their great contribution.
I believe this solution be a sticky topic since all these people who swapped hitachi to hitachi or hitachi to samsung or vice versa would need it in case they get E66 error
This post has been edited by myfranco: Nov 6 2006, 07:28 PM
Post by: segaboys on November 06, 2006, 12:57:00 PM
Last question before you go back to playing,
What would the steps be if I wanted flash my Hitachi V40 to fake itself as a Samsung, thats the Drive my Motherboard is married to.
I now have a Hitachi and no Samsung
Post by: myfranco on November 06, 2006, 12:27:00 PM
QUOTE(segaboys @ Nov 6 2006, 09:28 PM)
well done myfranco!!!!
Last question before you go back to playing,
What would the steps be if I wanted flash my Hitachi V40 to fake itself as a Samsung, thats the Drive my Motherboard is married to.
I now have a Hitachi and no Samsung
Honestly i don't know what to do for samsung since i tried to fake v47 for v59 hitachi.However,in the previous posts there were some explanations.I'll have a look for samsung,try if it fits than i try to help you ok?
Post by: segaboys on November 06, 2006, 01:09:00 PM
Samsung 0x202e - 0x204d :
sm52 STTSocprVD-DOR MSTH-49A3 (ASCII)
736D353220202020535454536F63707256442D444F52204D5354482D34394133 (in hex)
Samsung 0x20b5 - 0x20d7 :
..2[...TSSTcorpDVD-ROM TS-H943Ams25 (ASCII)
8000325B00000054535354636F72704456442D524F4D2054532D48393433416D733235 (hex)
Would the following command update the description in the firmware?
46flash.exe H fake-sam.bin 90002000 1000 <---- Flash the first changed sector
46flash.exe H fake-sam.bin 9003D000 1000 <---- Flash the second changed sector
And in theory would I be able to change it back?
Thanks
Post by: myfranco on November 06, 2006, 02:33:00 PM
QUOTE
If I changed the descriptions as below and create a fake-sam-e.bin
Samsung 0x202e - 0x204d :
sm52 STTSocprVD-DOR MSTH-49A3 (ASCII)
736D353220202020535454536F63707256442D444F52204D5354482D34394133 (in hex)
Samsung 0x20b5 - 0x20d7 :
..2[...TSSTcorpDVD-ROM TS-H943Ams25 (ASCII)
8000325B00000054535354636F72704456442D524F4D2054532D48393433416D733235 (hex)
Samsung 0x202e - 0x204d :
sm52 STTSocprVD-DOR MSTH-49A3 (ASCII)
736D353220202020535454536F63707256442D444F52204D5354482D34394133 (in hex)
Samsung 0x20b5 - 0x20d7 :
..2[...TSSTcorpDVD-ROM TS-H943Ams25 (ASCII)
8000325B00000054535354636F72704456442D524F4D2054532D48393433416D733235 (hex)
Segaboys i believe you should change those info in the hitachi firmware than you should encrypt it.Finally you can flash with 46flash.exe
But the first part is a bit complicated
Post by: SCSI on November 06, 2006, 02:44:00 PM
This post has been edited by SCSI: Nov 6 2006, 10:46 PM
Post by: spydermixx on November 06, 2006, 03:06:00 PM
Post by: segaboys on November 06, 2006, 03:29:00 PM
Samsung 0x202e - 0x204d :
sm52 STTSocprVD-DOR MSTH-49A3 (ASCII)
736D353220202020535454536F63707256442D444F52204D5354482D34394133 (in hex)
Samsung 0x20b5 - 0x20d7 :
..2[...TSSTcorpDVD-ROM TS-H943Ams25 (ASCII)
8000325B00000054535354636F72704456442D524F4D2054532D48393433416D733235 (hex)
DOES not work.... must be something extra cos the above fits in sweetly...
When I open the firmware in firmware tools it still comes up as a Hitachi firmware....
Windows detects my Hitachi as a Samsung Drive now....
Also just noticed, if you remove the SATA cable then XBOX boots up to dash (missed that one)
Plug in SATA while on and you get Error 66
Plan to roll back and try again....
Post by: langnao on November 06, 2006, 04:05:00 PM
QUOTE(myfranco @ Nov 7 2006, 01:57 AM)
OK I'VE DONE IT !!!!
Story : Hitachi v59 got bricked with Birdy Flasher then we bought a Hitachi v47 , flashed and injected the key.It worked fine.After the fall update 360 was giving E66 Error since it was married with a hitachi v59 but there was v47 at that moment.
Solution :
1 - Flashed back to original Firmware (used restore.bat command in Garyopa 2.3 )
2 - Flashed with Garyopa 2.3 (thank you to Garyopa)
3 - Unstealthed the firmware with the encrypted original.bin :
47flash H orig-e.bin 90033000 1000 --->this is the very first original firmware.
4 - Hexedited original.bin and changed v47 information to v59 to make Xbox 360 return with the correct code:
saved the bin file as fake59 then encrypted with Firmware Toolbox 1.2
5 - Again with Garyopa's X-LG folder:
47flash.exe H fake59.bin 90002000 1000 <---- Flash the first changed sector
47flash.exe H fake59.bin 9003D000 1000 <---- Flash the second changed sector
(Where H is the drive letter)
Turned 360 off.Plugged all the cable and played Splinter Cell Double Agent (IMG:style_emoticons/default/biggrin.gif)
I want to thank to Garyopa and Langnao for their great contribution.
I believe this solution be a sticky topic since all these people who swapped hitachi to hitachi or hitachi to samsung or vice versa would need it in case they get E66 error
Glad it works out for u .... Thanks to all, garyopa, averian for contributing.
Just one question, u don't plan to stealth back the firmware?
Something happened similar to me. Was helping my brother to flash to 2.3 and the process hang after completing the 9 steps at 'Checking flashed version'. Pack up the box and forgetten to manually run the last 2 steps of stealth the firmware. Too lazy to open up again and probably waiting for the next release. Everything fine just unstealth that's all ... (IMG:style_emoticons/default/smile.gif)
QUOTE(segaboys @ Nov 7 2006, 06:00 AM)
Samsung ----> Hitachi
Samsung 0x202e - 0x204d :
sm52 STTSocprVD-DOR MSTH-49A3 (ASCII)
736D353220202020535454536F63707256442D444F52204D5354482D34394133 (in hex)
Samsung 0x20b5 - 0x20d7 :
..2[...TSSTcorpDVD-ROM TS-H943Ams25 (ASCII)
8000325B00000054535354636F72704456442D524F4D2054532D48393433416D733235 (hex)
DOES not work.... must be something extra cos the above fits in sweetly...
When I open the firmware in firmware tools it still comes up as a Hitachi firmware....
Windows detects my Hitachi as a Samsung Drive now....
Also just noticed, if you remove the SATA cable then XBOX boots up to dash (missed that one)
Plug in SATA while on and you get Error 66
Plan to roll back and try again....
Maybe try a MS28 as in your original drive could be a MS28 thus setting to MS25 will still fail ? ...
Post by: myfranco on November 06, 2006, 03:33:00 PM
QUOTE
3D49E (2 bytes) forewards version becomes "59"
3D4A8 (8 bytes) ver. build date becomes "06/01/24"
3D51C (2 bytes) backwards version becomes "95" taken from Garyopa
3D4A8 (8 bytes) ver. build date becomes "06/01/24"
3D51C (2 bytes) backwards version becomes "95" taken from Garyopa
I hope it fits well in there too.
@Langnao you're right , i haven't done it on purpose.That machine would never be on live so i just left it unstealthed.I was afraid of breaking something
Post by: segaboys on November 06, 2006, 03:46:00 PM
QUOTE(myfranco @ Nov 6 2006, 10:40 PM)
@segaboy what about the second part of the fimware
I hope it fits well in there too.
@Langnao you're right , i haven't done it on purpose.That machine would never be on live so i just left it unstealthed.I was afraid of breaking something
Yes I saw that, I have just rolled back....
I started replacing in the second section but they dont seem to match in size... also I cant encrypt the firmware anymore with the extra changes so something must be wrong...
Will keep messing
Does the Firmware toolkit do specific firmware checks so I can't encrypt a faked Samsung/Hitachi firmware
I am a bit of a Noob and would like to know the follwing...
When you flashing specific lines on the hitachi firmware, how do you know which section?
Eg. 46flash H orig-e.bin 90033000 1000
how do you calculate 90033000 1000
Is there a cmd I can use to dump the firmware I just modified, to check that I have patched it correctly?
Figured that one out :-) memdump ... checked for full command in the bat file.
Thanks again for all the help.
Post by: garyopa on November 06, 2006, 04:01:00 PM
QUOTE(segaboys @ Nov 6 2006, 05:53 PM)
Yes I saw that, I have just rolled back....
I started replacing in the second section but they dont seem to match in size... also I cant encrypt the firmware anymore with the extra changes so something must be wrong...
Does the Firmware toolkit do specific firmware checks so I can't encrypt a faked Samsung/Hitachi firmware
Use the old command prompt "firmcrypt" named "firm.exe" in our package to "encrypt" the faked firmwares.
Post by: myfranco on November 06, 2006, 04:45:00 PM
To encrypt the firmware , put your bin file in X-LG(garyopa's flashing folder).Say your bin file is segaboy.bin:
Firm.exe e segaboy.bin encrypted.bin
"e" is for encrypting.
To decrypt:
Firm.exe d segaboy.bin encrypted.bin (Shorter filenames is better)
To know which sector to flash ,there must be 8 digits.Say we flash 2030, you type
"9002030" but if it's more than 4 digits where you need to flash(like 3d000) you type
"9003d000" in any case that 9000 thingy must be totally 8 digits.Keep in mind it must be always encrytped.
To dump original.bin or let's say whatever you flashed
memdump %1 12200 8 8000 firmware.bin where %1 is the drive letter of hitachi.
In your situation , i believe you flashed one part but not the second part.Open an untouched hitachi bin file(verifying it's your version for hitachi) , encrypt it then flash the first part to its original state.After that you can modify another hitachi fw and you can flash those sectors you need to.
I have no idea what to do for the second part but i'll have a look and help you as much as i can.
Post by: segaboys on November 06, 2006, 04:56:00 PM
GAMEOVERReplacing it in both places bricks the drive!!!!!!!!!
USB Connectivity kit will not find drive
Error 66 has changed to Error 65
Verified firmware before I rebooted to make sure changes were made....
Can't say I learnt anything new :-(
Post by: garyopa on November 06, 2006, 05:37:00 PM
QUOTE(segaboys @ Nov 6 2006, 07:03 PM)
Replacing it in both places bricks the drive!!!!!!!!!
USB Connectivity kit will not find drive
Error 66 has changed to Error 65
Verified firmware before I rebooted to make sure changes were made....
Can't say I learnt anything new :-(
Hmm, you are sure you replaced the strings right and encrypted the firmware,
and flashed the two correct sectors?
Also the strings must match in both halves or the drive itself will be not bootup
correctly.
Also was this on a "Xtreme" version of firmware or your "Original" firmware,
in both cases you must also make sure the "checksum" is set to all ZERO's,
or the drive will boot-up into RECOVER mode and will not operate correctly.
Post by: langnao on November 06, 2006, 06:17:00 PM
0x3D480 - 0x3D49F
0x3D51A - 0x3D539
Post by: myfranco on November 06, 2006, 06:51:00 PM
Post by: langnao on November 06, 2006, 08:12:00 PM
QUOTE(myfranco @ Nov 7 2006, 09:22 AM)
It's sad.I hope you have someone in your area to get it fixed.
Maybe he can use the swapping method to try to flash the hitachi drive again?
Anyway, too bad, else we can confirm if it works for hitachi-samsung swap ...
In future firmware flashing, you will have to edit the flashing script cos it will detect your drive as 59 and use 59flash.exe but it should be 47flash.exe for your case. No need to change the drive model anymore cos the flashing script does not affect it ...
Post by: myfranco on November 06, 2006, 08:39:00 PM
I have no idea or no knowledge to say that will work or not but undoing those two sectors makes me feel safe.
I don't want to see another bricked drive because this was already a replacement
Post by: langnao on November 06, 2006, 10:02:00 PM
QUOTE(myfranco @ Nov 7 2006, 11:10 AM)
From what you're saying Langnao , v47>v59 hitachi can now be flashed as a v59 and nothing would happen.
I have no idea or no knowledge to say that will work or not but undoing those two sectors makes me feel safe.
I don't want to see another bricked drive because this was already a replacement (IMG:style_emoticons/default/smile.gif)
No. You are still using the 47 firmware. But because you have changed the drive model to '59'. The next new firmware release, if u just run the default flashing batch file, you will have problem cos it will detect your drive as 59 (which it is not) and will branch to the 59 flashing procedure using '59flash.exe' which is not correct. You still need to use the '47flash.exe' portion of the script. One way is to revert back the drive model to 47 and flash with new release then redo everything again. This is quite troublesome and error prone. Any way is to modified the batch script replacing all the 59flash.exe lines with 47flash.exe. So when u run the script, it detects as drive '59' branch to the 59 portion of the script but the actual flashing will be using 47flash.exe command.
This aside, the 2 changes that you made just change the drive model and it is pretty safe. Hitachi flashing is just patching certain portion of the firmware. You had done it right, subsequent flashing, you don't have to do it again, unless u undo it. But I am sure garyopa restore.bat script will not undo it ...
Anyway, when the next firmware release appears, just take note and maybe create a new thread and we can discuss about it ...
This post has been edited by langnao: Nov 7 2006, 06:08 AM
Post by: myfranco on November 07, 2006, 05:00:00 AM
This Xbox 360 belongs to a good friend of mine and he bought it from USA. In Turkey xbox 360 is not sold officially like Xbox(first). That is why we don't have a repair service nor warranty here. He won't flash it because he has no idea even about opening the case so that i'm not worried.
When we have a problem with the machine we are on our own
There is a very good contribution in Xbox-scene and i believe this solution will help people very much.I'm thinking of prepairing a good tutorial from beginning to the end about this solution.
Post by: langnao on November 07, 2006, 06:51:00 AM
QUOTE(myfranco @ Nov 7 2006, 07:31 PM)
@Langnao you're right.Before flashing this drive again , i need to undo those two sectors .After that, I flash the drive and redo the patch. That won't be a problem unless i don't forget it.
This Xbox 360 belongs to a good friend of mine and he bought it from USA. In Turkey xbox 360 is not sold officially like Xbox(first). That is why we don't have a repair service nor warranty here. He won't flash it because he has no idea even about opening the case so that i'm not worried.
When we have a problem with the machine we are on our own (IMG:style_emoticons/default/smile.gif)
There is a very good contribution in Xbox-scene and i believe this solution will help people very much.I'm thinking of prepairing a good tutorial from beginning to the end about this solution.
Yah, I think a lot of us make the assumption that xbox360 is widely available. I think MS should work harder to distribute to more areas (IMG:style_emoticons/default/smile.gif)
So far we know changing model within Hitachi firmware works. Changing model within samsung firmware works. Injecting Hitachi drive model to samsung firmware works. Only left injecting samsung drive model to hitachi firmware to be verified working. Alas a waste ...
Post by: myfranco on November 07, 2006, 09:51:00 AM
However, Sony has no problem with it. Even if there is just a repair service, i think they earn lots of money
Post by: Pres on November 07, 2006, 10:57:00 AM
My scenario quoted from another post.
QUOTE(Pres @ Nov 3 2006, 09:17 AM)
I have a premium manufactured in late May 2006 which originally came with a TS-H943 ms25 Ver.A.
I never modified the FW only dumped it as a precaution when the tools became available. The drive started to act up after the warranty was no longer. (go figure) It slowly started not reading disks and eventually quit reading disks. (again as I said never modified) So I aquired a Hitachi 3120 46 DG put my key in and ran OPA 2.1 all is fine. Never planned on modifying my drive but was a little ticked that my 360 lasted 4 months so to speak it was my way of saying f*** you too MS. I have been using the Hitachi for awhile now and never no probs. I do not go on live with it nor have I ever with it. (did with original ms25) I dont care to update my dash but I know it will be released on a game disk in the future and I will be forced into it. What would seem like my best option to get the update when that time comes. The ms25 still registers in the 360 just wont read, so should I place the ms25 in it update then switch back to the Hitachi or update with Hitachi?
Have you guys made any more improvement on your situation. Looking forward to what you come up with.
Post by: myfranco on November 07, 2006, 11:22:00 AM
Those adresses are known in hitachi.I want to try if i can implement samsung info into hitachi firmware but will be just experimental.
Post by: Pres on November 07, 2006, 11:35:00 AM
Post by: myfranco on November 07, 2006, 12:35:00 PM
You're right it's all experimental
Post by: langnao on November 07, 2006, 07:24:00 PM
We don't know exactly what are the steps carried out by segaboys. Modifying hitachi firmware is more complicated as compared to samsung. The whole encrypting thingy, unstealth before changes and after doing, stealth it back ,etc. Thus there are many possible areas of failure ...
Based on the posting, he managed to change the first portion of the firmware but brick his drive when changing the second portion.
First part of hitachi firmware:
0x202e - 0x204d
0x20b6 - 0x20d5
Second part of hitachi firmware:
0x3d480 - 0x3d49f
0x3d51a - 0x3d539
I checked thru. The byte values are the same for first part and second part. Thus I don't see why changing the first part is okay whereas the second part got problem. We really need segaboys to feedback what he had actually done and whether he copied the code correctly?
Thus:
0x202e - 0x204d of samsung firmware copied to 0x202e - 0x204d of hitachi
0x20b8 - 0x20d7 of samsung copied to 0x20b6 - 0x20d5 of hitachi
0x20b8 - 0x20d7 of samsung copied to 0x3d480 - 0x3d49f of hitachi
0x202e - 0x204d of samsung copied to 0x3d51a - 0x3d539 of hitachi
We don't have a way to test it out and just waiting for some desperate brave soul to try ...
myfranco will not try it out cos his set is working now and no point for him to try too as his original drive is a hitachi 59, changing it to samsung doesn't make sense and will not work and thus will not contribute to the result.
Post by: segaboys on November 08, 2006, 04:00:00 AM
I realised what I did wrong, don't know if it will fix it though....
After faking a V59 hitachi on my V40 and finding out it did not work, I rolled back to the original using Restore.bat
I then did not patch the firmware with Garyopa 2.3, I did all the work on an original firmware
However the changes I made are as follows:-
Original Hitachi V40:-
0004 LHD--TTSVD-DORMDG3R21L0
HL-DT-STDVD-ROM GDR3120L0040
00002028 0000 0000 0000 3030 3034 2020 2020 4C48 442D 2D54 5453 5644 2D44 4F52
00002044 204D 4447 3352 3231 4C30 2020 2020 2020 2020 2020 2020 2020 2020 0000
00002060 0000 000F 0000 0002 0002 0600 0000 0000 0000 0000 0000 0000 0000 0000
0000207C 0700 0700 0300 7800 7800 7800 7800 0000 0000 0000 0000 0000 0000 0000
00002098 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0700 0580
000020B4 0032 5B00 0000 484C 2D44 542D 5354 4456 442D 524F 4D20 4744 5233 3132
000020D0 304C 3030 3430 3042 4D42 4220 2020 3035 2F30 372F 3133 2020 2020 0100
000020EC FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
Faked Samsung:-
sm82 STTSocprVD-DORMSTH-49A3
TSSTcorpDVD-ROM TS-H943Ams28
00002028 0000 0000 0000 736D 3832 2020 2020 5354 5453 6F63 7072 5644 2D44 4F52
00002044 204D 5354 482D 3439 4133 2020 2020 2020 2020 2020 2020 2020 2020 0000
00002060 0000 000F 0000 0002 0002 0600 0000 0000 0000 0000 0000 0000 0000 0000
0000207C 0700 0700 0300 7800 7800 7800 7800 0000 0000 0000 0000 0000 0000 0000
00002098 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0700 0580
000020B4 0032 5B00 0000 5453 5354 636F 7270 4456 442D 524F 4D20 5453 2D48 3934
000020D0 3341 6D73 3238 3042 4D42 4220 2020 3035 2F30 372F 3133 2020 2020 0100
000020EC FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
Original Hitachi V40:-
HL-DT-STDVD-ROM GDR3120L0040
0004 LHD--TTSVD-DORMDG3R21L0
0003D470 FC45 0290 2C46 0290 0000 0000 0580 0032 5B00 0000 484C 2D44 542D 5354
0003D48C 4456 442D 524F 4D20 4744 5233 3132 304C 3030 3430 3042 4D42 4220 2020
0003D4A8 3035 2F30 372F 3133 2020 2000 0100 0000 0000 0000 0000 0000 0000 0000
0003D4C4 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0400
0003D4E0 0200 0600 0100 0500 0300 0700 C085 0000 0000 0000 0000 0000 0000 0000
0003D4FC 0000 0000 2020 2020 2020 2020 2020 2020 2020 2020 2020 2020 0000 0000
0003D518 0000 3030 3034 2020 2020 4C48 442D 2D54 5453 5644 2D44 4F52 204D 4447
0003D534 3352 3231 4C30 2020 2020 2020 2020 2020 2020 2020 2020 0000 0000 000F
0003D550 0000 0002 0002 0600 0000 0000 0000 0000 0000 0000 0000 0000 0000 0700
Faked Samsung:-
TSSTcorpDVD-ROM TS-H943Ams28
sm82 STTSocprVD-DORMSTH-49A3
0003D470 FC45 0290 2C46 0290 0000 0000 0580 0032 5B00 0000 5453 5354 636F 7270
0003D48C 4456 442D 524F 4D20 5453 2D48 3934 3341 6D73 3238 3042 4D42 4220 2020
0003D4A8 3035 2F30 372F 3133 2020 2000 0100 0000 0000 0000 0000 0000 0000 0000
0003D4C4 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0400
0003D4E0 0200 0600 0100 0500 0300 0700 C085 0000 0000 0000 0000 0000 0000 0000
0003D4FC 0000 0000 2020 2020 2020 2020 2020 2020 2020 2020 2020 2020 0000 0000
0003D518 0000 736D 3832 2020 2020 5354 5453 6F63 7072 5644 2D44 4F52 204D 5354
0003D534 482D 3439 4133 2020 2020 2020 2020 2020 2020 2020 2020 0000 0000 000F
0003D550 0000 0002 0002 0600 0000 0000 0000 0000 0000 0000 0000 0000 0000 0700
Reference Samsung:-
sm82 STTSocprVD-DORMSTH-49A3
TSSTcorpDVD-ROM TS-H943Ams28
00002028 0000 0000 0000 736D 3832 2020 2020 5354 5453 6F63 7072 5644 2D44 4F52
00002044 204D 5354 482D 3439 4133 2020 2020 2020 2020 2020 2020 2020 2020 0000
00002060 0000 000B 0000 0002 0002 0600 0000 0000 0000 0000 0000 0000 0000 0000
0000207C 0000 0700 0300 7800 7800 E300 7800 0000 0000 0000 0000 0000 0000 0000
00002098 0200 0800 0800 0000 0000 0000 0000 0000 0000 0000 0000 0000 3F00 0000
000020B4 0580 0032 5B00 0000 5453 5354 636F 7270 4456 442D 524F 4D20 5453 2D48
000020D0 3934 3341 6D73 3238 2020 2000 0000 0000 0000 0000 0000 0000 0000 0000
000020EC 0000 1600 03A0 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
Now all I need to do is get my bricked Hitachi fixed :-(
Post by: langnao on November 08, 2006, 07:35:00 AM
You mentioned about changing to 59 first before u did the replacement with samsung model? You followed exactly the steps of myfranco? Unstealth first then change? Then?
Post by: segaboys on November 08, 2006, 09:02:00 AM
I then rolled it back to original V40 firmware.
I did not patch the firmware, I did it to an original V40 firmware so I did not need to un-stealth.
Forgot to patch the firmware with GaryOPA so that could be why it bricked!!!!
This post has been edited by segaboys: Nov 8 2006, 05:03 PM
Post by: myfranco on November 08, 2006, 06:23:00 PM
I can't understand why hitachi got bricked that way.
Post by: myfranco on November 08, 2006, 08:02:00 PM
Post by: langnao on November 08, 2006, 10:04:00 PM
QUOTE(myfranco @ Nov 9 2006, 10:33 AM)
Sorry i missed a part of your post.That second part bricked your drive obviously.
The first part & second is exactly the same in codes. Thus unless something else screw up along the way ...
Best is get a hitachi drive and test it ... (IMG:style_emoticons/default/smile.gif)
Post by: myfranco on November 08, 2006, 10:24:00 PM
This post has been edited by myfranco: Nov 9 2006, 06:28 AM
Post by: langnao on November 08, 2006, 10:33:00 PM
QUOTE(myfranco @ Nov 9 2006, 12:55 PM)
I think the second part Langnao.I haven't seen any code on samsung fw there.
To me just the first part is enough.As i mentioned that 360 was a friend' and i can't test it now.Otherwise,i would return the second part to its original state and try it (IMG:style_emoticons/default/smile.gif)
Based on what segaboys had posted on those hex codes, it is correct but just don't know what went wrong alone the way. Anyway garyopa mentioned the need to change both parts inorder for it to work. segaboys mentioned that changing the first part, Windows already detect it as a samsung drive. Even 360fwtoolbox only read the first part to determine what firmware it is. But I think changing both sides are correct. Drive + shipment will cost me close to ~$150... Too expensive for experimental purpose ... (IMG:style_emoticons/default/smile.gif)
Post by: BlackOmega on November 09, 2006, 12:51:00 AM
Ppl who had a hitachi drive can't use a samsung drive?
I about to buy a samsung drive for my 360 (my hitachi bricked), should I cancel the order and try to find a hitachi drive instead?
omg, I almost done dealing with the seller, about to get the info for the deposit ...
Post by: spydermixx on November 09, 2006, 12:55:00 AM
QUOTE(BlackOmega @ Nov 9 2006, 07:22 AM)
Say, after reading the entire topic I still confused.
Ppl who had a hitachi drive can't use a samsung drive?
I about to buy a samsung drive for my 360 (my hitachi bricked), should I cancel the order and try to find a hitachi drive instead?
omg, I almost done dealing with the seller, about to get the info for the deposit ...
no this can be done, it takes a little work. see averians previous post to see how he did it. the people with problems are those switching from samsung to hitachi.
Post by: segaboys on November 09, 2006, 02:29:00 AM
Really want to get playing games again :-(
Post by: langnao on November 09, 2006, 06:04:00 AM
QUOTE(BlackOmega @ Nov 9 2006, 03:22 PM)
Say, after reading the entire topic I still confused.
Ppl who had a hitachi drive can't use a samsung drive?
I about to buy a samsung drive for my 360 (my hitachi bricked), should I cancel the order and try to find a hitachi drive instead?
omg, I almost done dealing with the seller, about to get the info for the deposit ...
So far, the success stories are those changing from hitachi to hitachi, samsung to samsung and hitachi to samsung ...
QUOTE(segaboys @ Nov 9 2006, 05:00 PM)
Where can you get Samsung Drives from?
Really want to get playing games again :-(
do you have any friends that have a samsung drive? Maybe can use the swapping method to "save" your hitachi drive ...
Post by: Pres on November 09, 2006, 07:17:00 AM
(IMG:http://speednetllc.com/ispep1012/pictures/ftb.jpg)
Post by: noonlight on November 09, 2006, 07:33:00 AM
QUOTE(Pres @ Nov 9 2006, 01:48 PM)
I tinkered with the editing when the fix was found for the Samsung E66 error. Everything I did then matches the same changes as described here. Firmware ToolBox recognizes it but slightly different from what it should be. It also shows that the key is no longer there which is understandable considering the Hitachi key starts at 0x4f00 and the Samsung starts at 0x40ec, so that doesnt bother me. It is the extra characters shown behind the ms25 of the rom version that bothers me.
(IMG:http://speednetllc.com/ispep1012/pictures/ftb.jpg)
Am i right in thinking you have switched from a samsung to a hitachi drive on your 360 and then faked your hitachi firmware to be samsung? if so have you flashed this to the drive, and did this work?
If so could you let me know how you did it?
Post by: Pres on November 09, 2006, 07:40:00 AM
Post by: noonlight on November 09, 2006, 07:51:00 AM
Post by: langnao on November 09, 2006, 08:02:00 AM
QUOTE(Pres @ Nov 9 2006, 10:11 PM)
I have done the hex work to make it show as a Samsung drive but, unfortunetly I have not been brave enough to flash it as the Hitachi is my only working drive at the moment. So no Hitachi no 360. If you are interested in learning how, look back a few posts as it is explained throughout here. I would suggest segaboys post as it is more laid out.
Can't advise you whether it is working or not cos this is the only missing puzzle now. firmware toolbox is only mean to read either a hitachi/samsung firmware and not a mixture. The thingy in the bracket normally reflects the xtreme version when u use it to open an xtreme firmware (not original). My take is, from the modification, toolbox detects it as not original firmware and while trying to read which version of xtreme firmware but it can't as it can't recognize it and thus those "funny" characters ...
If you really wanna try, better restore everything back to default (if u have applied the mod. firmware), then applied those changes and flash that 2 sectors...
Maybe segaboys can provide u with more info.
Again, if you tried a hitachi - samsung firmware hacking, if you used toolbox to open, you will also see "garbage" in the brackets. But this is proven to work by averian ...
Thus you can't use toolbox to verify since now the firmware is a "mix" ...
However, do everything at your own risks ....
Post by: Pres on November 09, 2006, 08:03:00 AM
(IMG:http://speednetllc.com/ispep1012/pictures/Hitachi-ms25.jpg)
Post by: langnao on November 09, 2006, 08:06:00 AM
QUOTE(Pres @ Nov 9 2006, 10:34 PM)
I might be a bit off here but would changing the f/w version and first part of each identifier be enough. It may be possible that all it is looking at is the f/w revision only therefor seeing ms25 regardless of manufacturer and model may be enough to fool it. Just a thought as it would seem flashing only these parts would be alot less likely to brick a drive. What do you guys think.
Read my previous post, averian got it working for hitachi - samsung and if you repeat what he had done, toolbox also reports "garbage" within the brackets ...
Don't really know but most probably it will not work. They might be doing a full string compare ...
Furthermore, segaboys reported bricking the drive only after changing the second part thou we missed out the exact details. He had successfully changed the first part and toolbox only check the first part ...
Post by: Pres on November 09, 2006, 08:16:00 AM
QUOTE(langnao @ Nov 9 2006, 09:37 AM)
Read my previous post, averian got it working for hitachi - samsung and if you repeat what he had done, toolbox also reports "garbage" within the brackets ...
I see what you mean now about the brackets. I did not open multiple f/w to realize that the brackets are normal. I used the xtreme 4.2 update to convert a ms25 to Hitachi and the brackets are there also which would confirm that it does not mess with the functionality of the Samsung f/w. So it might definetly be possible on the Hitachi.
segaboys, would it be at all possible for a step by step layout of the procedures you took so that we may identify more accurately what step was the failure.
Post by: segaboys on November 09, 2006, 08:24:00 AM
Post by: langnao on November 10, 2006, 07:51:00 AM
QUOTE(Pres @ Nov 9 2006, 10:47 PM)
I see what you mean now about the brackets. I did not open multiple f/w to realize that the brackets are normal. I used the xtreme 4.2 update to convert a ms25 to Hitachi and the brackets are there also which would confirm that it does not mess with the functionality of the Samsung f/w. So it might definetly be possible on the Hitachi.
segaboys, would it be at all possible for a step by step layout of the procedures you took so that we may identify more accurately what step was the failure.
Had you taken the "plunge" or still waiting for segaboys info.?
Post by: Pres on November 10, 2006, 02:35:00 PM
QUOTE(langnao @ Nov 10 2006, 09:22 AM)
Had you taken the "plunge" or still waiting for segaboys info.?
I havent as of yet. The Hitachi is all I have to play my games at the moment and since I have not done the fall update yet there is no reason for me to jump right in. I was hoping to review segaboy's info in hopes that whatever bricked his drive is or was a simple error.
Post by: langnao on November 10, 2006, 06:00:00 PM
QUOTE(Pres @ Nov 11 2006, 05:06 AM)
I havent as of yet. The Hitachi is all I have to play my games at the moment and since I have not done the fall update yet there is no reason for me to jump right in. I was hoping to review segaboy's info in hopes that whatever bricked his drive is or was a simple error.
Or maybe until someone else had done it. Perhaps can seek some help from garyopa if he is not very busy with the next xtreme release?
Post by: Pres on November 10, 2006, 06:04:00 PM
QUOTE(langnao @ Nov 10 2006, 07:31 PM)
Or maybe until someone else had done it. Perhaps can seek some help from garyopa if he is not very busy with the next xtreme release?
Thats for sure! If I had another working drive I would go for it just for the learning experience. Garyopa's help is always welcomed.
Post by: langnao on November 10, 2006, 06:15:00 PM
QUOTE(Pres @ Nov 11 2006, 08:35 AM)
Thats for sure! If I had another working drive I would go for it just for the learning experience. Garyopa's help is always welcomed.
I think he read this forum else he would not had replied to this thread ...
Anyway, had u checked out xboxhacker.net? Maybe someone had already done it successfully ...
Post by: Pres on November 10, 2006, 07:00:00 PM
QUOTE(langnao @ Nov 10 2006, 07:46 PM)
I think he read this forum else he would not had replied to this thread ...
Anyway, had u checked out xboxhacker.net? Maybe someone had already done it successfully ...
No I have not looked around there yet. I will give it a shot and see what I can come up with.
Post by: hugheso on November 11, 2006, 04:32:00 AM
Post by: langnao on November 11, 2006, 05:12:00 AM
QUOTE(hugheso @ Nov 11 2006, 07:03 PM)
Hi everyone! I am in the same boat as myfranco was in. I bricked my v59 with birdy and replaced it with a v47. Everything went fine till the fall update. The only thing is I dont know how to hexedit these files or what they mean! Could somebody please help me? I have hex editor but dont have a clue what tio change
Let myfranco helps u then ...
But r u sure you want to do this? Cos this changes require running commands at DOS and pretty much everything is manually key in. Since you are not even sure about hex edit, it is pretty much risky to do it yourself ...
Post by: hugheso on November 11, 2006, 07:54:00 AM
Post by: langnao on November 11, 2006, 09:56:00 PM
QUOTE(hugheso @ Nov 11 2006, 10:25 PM)
Well who could i do it for me??? I have all the firmware files for the backup. Could i sent them to someone to do it for me? Or is it better to fait for a new firmware release and hopefully that will fix it?
Can you even run a hex editor program and change some values?
Post by: hugheso on November 12, 2006, 05:58:00 AM
Post by: langnao on November 12, 2006, 06:09:00 AM
QUOTE(hugheso @ Nov 12 2006, 08:29 PM)
No not really. I have had hex editor on but there are that many different values i wouldn't know what to change. Is there a guide somewhere which will show me how to use it properly?
What to change was already mentioned in previous thread.
Take the 'was.bin', change accordingly what was mentioned.
Assuming your drive already modded. with xtreme 2.3
Unstealth your drive firmware.
Encrypt the modified 'was.bin' and flashed your drive firmware
Stealth back the drive firmware.
Post by: hugheso on November 12, 2006, 06:55:00 AM
Post by: langnao on November 12, 2006, 07:14:00 AM
QUOTE(hugheso @ Nov 12 2006, 09:26 PM)
YEAH!!! I did it!!! I just got the courage to do it myself and it was self explanitary really! I would like to thank everyone for there help in doing this! In my eyes you are all legends!!!
So you did 'stealth' back the firmware after the changes? Ha, I guess it is not so difficult afterall ...
Post by: myfranco on November 12, 2006, 08:24:00 AM
You did good hugheso
Post by: morbis242 on November 13, 2006, 09:49:00 AM
...but no MS28 to copy from. Where can I find one or at least the drive info at 2020 and 3D49E?
Thanks.
Morbis
Post by: hugheso on November 13, 2006, 10:26:00 AM
Many Thanks again! i know who to call if i need anymore help in the future
Post by: Exobex on November 13, 2006, 11:25:00 AM
QUOTE(morbis242 @ Nov 13 2006, 04:20 PM)
I have an HLG 46DH drive I'm trying to get to work in my 360. The original drive is an MS28. I unfortunately applied the Fall update and now need to trick the 360 into thinking it's a MS28. I have an MS25 firmware to copy from:
...but no MS28 to copy from. Where can I find one or at least the drive info at 2020 and 3D49E?
Thanks.
Morbis
The updated Xtreme 4.2 pack has one of each, you can pick from there.
Post by: morbis242 on November 13, 2006, 11:34:00 AM
QUOTE(Exobex @ Nov 13 2006, 12:56 PM)
The updated Xtreme 4.2 pack has one of each, you can pick from there.
It has MS25, but no MS28. The hacked firmware is MS28, but I was looking for a clean version.
Post by: langnao on November 13, 2006, 04:03:00 PM
QUOTE(morbis242 @ Nov 14 2006, 02:05 AM)
It has MS25, but no MS28. The hacked firmware is MS28, but I was looking for a clean version.
Had you read thru this thread? What you are going to do has not been tested and we are waiting for people to test this out ...
Generally:
1) After flashing with lastest garyopa 2.3 firmware
2) Unstealth the firmware
3) Apply the respective changes
4) Stealth back the firmware
This will take care of the checksum thingy mentioned by garyopa in the other thread that you had started ...
Lastly, before you do anything make sure you are very clear about it and it helps to list down the exact steps so that we can help to check before you proceed ...
Will list down the hex value of MS25 on the respective sectos ...
Post by: langnao on November 13, 2006, 06:58:00 PM
1) now.bin
2) 46.bin
3) 46_23.bin
4) 46_23S.bin
46.bin, 46_23.bin & 46_23S.bin can be found in the RAR file 'FWPACK.RAR'
1) Hex edit 46_23.bin file and change the following ...
Replace 0x202E - 0x204D with 736D383220202020535454536F63707256442D444F52204D5354482D34394133
Replace 0x20B6 - 0x20D5 with 5B00000054535354636F72704456442D524F4D2054532D48393433416D733238
Replace 0x3D480 - 0x3D49F with 5B00000054535354636F72704456442D524F4D2054532D48393433416D733238
Replace 0x3D51A - 0x3D539 736D383220202020535454536F63707256442D444F52204D5354482D34394133
Save the file as 46_23m.bin
2) Ensure the the hitachi drive had been flashed with xtreme 2.3 firmware using flash23s.bat script
3) Unstealth the firmware
firm 46.bin 46-e.bin
46flash %1 46-e.bin 90033000 1000
4) Flash the drive with the changes
firm 46_23m.bin 46_23m-e.bin
46flash %1 46_23m-e.bin 90002000 1000
46flash %1 46_23m-e.bin 9003D000 1000
5) Stealth the firmware
firm 46_23S.bin 46_23S-e.bin
46flash %1 46_23S-e.bin 90033000 1000
6) Dump the changes
memdump %1 12200 8 8000 mod.bin
7) Compare mod.bin with now.bin and make sure the only changes are those made in Step 1
Lastly, do it at your own risks ..
Post by: myfranco on November 14, 2006, 06:00:00 PM
I checked those sectors compared with Langnao's last post and it matches.Edited with xvi32 hex editor encrypted it and we will the results tomorrow.When it's done i would send the result here.
Post by: Pres on November 14, 2006, 06:23:00 PM
Post by: langnao on November 14, 2006, 06:57:00 PM
QUOTE(myfranco @ Nov 15 2006, 08:31 AM)
Guys , we are working on a hitachi drive now to show it as if it's samsung ms28(xbox 360 was married to ms28)
I checked those sectors compared with Langnao's last post and it matches.Edited with xvi32 hex editor encrypted it and we will the results tomorrow.When it's done i would send the result here.
Good luck, just remember the checksum thingy that garyopa mentioned
Changes to the drive model have to be done at least after the drive has been flashed with xtreme 2.3 else just changing the drive model alone with the rest as original will screw up things since the checksum was not changed ...
Post by: myfranco on November 15, 2006, 07:57:00 AM
Hope everything goes fine.
Post by: langnao on November 15, 2006, 11:12:00 AM
QUOTE(myfranco @ Nov 15 2006, 10:28 PM)
Thanks Langnao ,that's what we are going to do.We will restore the drive then flash with Garyopa 2.3 , unstealth ,patch those sectors then stealth back.
Hope everything goes fine.
Yap, all the best. Hope this fills up the "last piece of the puzzle" ...
Post by: myfranco on November 15, 2006, 01:50:00 PM
WE DID IT!!!!!!
Trying to show a hitachi drive as if it's samsung is done!!!
I will post the solution in a very short time
Post by: Pres on November 15, 2006, 02:08:00 PM
Post by: myfranco on November 15, 2006, 04:25:00 PM
This time , I want to share my experience on how to change Hitachi v47(version doesn't matter actually) to Samsung ms28.
Story : A friend of mine has a Xbox 360 married to Samsung Ms28 dvd drive.For some reasons , he put a hitachi v47 on the console and after the fall update , 360 was giving E66 error.We needed to cheat the console as if there is a Samsung drive in it.
Solution : First thing first , If you have an old firmware on your Xbox 360 , you need to update to the newest firmware (Garyopa 2.3 revision 2) . Your drive must be firmwared to begin this trick.Use flash23s.bat in the Garyopa's folder.When everything is done , you can step to next process.Make sure you have both Garyopa 2.3 rev1 and rev2.
-What we need:
QUOTE
1. Your original.bin file
2. Garyopa's firmware(2.3 rev2)
3. Firmware toolbox 1.2 or 2.0
4. Hex Editor (preferably xvi32)
5. Courage
2. Garyopa's firmware(2.3 rev2)
3. Firmware toolbox 1.2 or 2.0
4. Hex Editor (preferably xvi32)
5. Courage
First of all we have to unstealth the firmware.Get your original.bin file and by using Firmware Toolbox encrypt it.Rename it to step1.bin.Copy step1.bin into Garyopa's folder.Navigate to "X-LG" and use:
QUOTE
For v46 46flash.exe
For v47 47flash.exe
For v59 59flash.exe
For v47 47flash.exe
For v59 59flash.exe
As our drive was a v47 and the drive letter was "H" , In the command prompt i wrote:
QUOTE
47flash.exe H step1.bin 90033000 1000
If it returns with an error use other revision of Garyopa 2.3 (rev2 didn't work for us so we stepped back to rev1)
Your drive is unstealth now.From now on , we have to change some bytes of the original.bin file.Be sure your original.bin file is NOT encrypted.Change the name to step2.bin.Open xvi32.exe or any other hex editor.Open step2.bin (Hex editing was taken from Langnao)
QUOTE
Hex edit step2.bin file and change the following ...
Replace 0x202E - 0x204D with 736D383220202020535454536F63707256442D444F52204D5354482D34394133
Replace 0x20B6 - 0x20D5 with 5B00000054535354636F72704456442D524F4D2054532D48393433416D733238
Replace 0x3D480 - 0x3D49F with 5B00000054535354636F72704456442D524F4D2054532D48393433416D733238
Replace 0x3D51A - 0x3D539 with 736D383220202020535454536F63707256442D444F52204D5354482D34394133
Replace 0x202E - 0x204D with 736D383220202020535454536F63707256442D444F52204D5354482D34394133
Replace 0x20B6 - 0x20D5 with 5B00000054535354636F72704456442D524F4D2054532D48393433416D733238
Replace 0x3D480 - 0x3D49F with 5B00000054535354636F72704456442D524F4D2054532D48393433416D733238
Replace 0x3D51A - 0x3D539 with 736D383220202020535454536F63707256442D444F52204D5354482D34394133
and save the file.To make sure check with Firmware toolbox.It must be a samsung ms28 firmware now.(Well , it looks so).If you have a ms25 drive , you can change ms28 and sm82 to ms25 and sm52 respectively.
Now , we need to encrypt step2.bin but Firmware toolbox can't do it anymore.Since the firmware looks like a samsung firmware, there won't be any option to encrypt it.We will use Garyopa's firmware folder.The name of the exe is firm.exe.Put step2.bin in the Garyopa's folder and give this command:
QUOTE
Firm.exe e step2.bin step3.bin
Your encrypted bin file is step3.bin now.After this you use these commands :
QUOTE
47flash H step3.bin 90002000 1000
47flash H step3.bin 9003D000 1000
47flash H step3.bin 9003D000 1000
And finally we stealth the firmware.From Garyopa's folder find fwpack.rar. Get 47_23S.bin and encrypt it.Change the name to step4 and put it into Garyopa's folder :
QUOTE
47flash H step4.bin 90033000 1000
If everything went fine your drive is ok now.
Check this :
- Your bin file has to be always encrypted.The only time you use your original.bin file (NOT ENCRYPTED) is when hex editing.
- Make sure you updated the firmware to Garyopa 2.3 rev2 or rev1 before you do anything on these page.
- File names are important.I recommend using the same type of filenames or same names given here.This prevents you getting confused.
- For drive letter i used "H" .If your drive letter is different than tihs change it accordingly.
- If you're not sure if it works or not , we did exactly what's written here and Xbox 360 is working like charm.
Thank to Garyopa , Langnao for their great contribution.Thank to everyone in this topic to beat Microsoft one more time
Post by: myfranco on November 15, 2006, 05:06:00 PM
Post by: langnao on November 15, 2006, 06:06:00 PM
QUOTE(myfranco @ Nov 16 2006, 07:37 AM)
I think both hitachi<>hitachi and hitachi>samsung solutions should be moved to E66 section.That might help other people too.
Nice ...
With your test of confirmation, now the swapping of drives of different models in any combination has been proven to work. Thanks. The "last piece of the puzzle" has been completed ...
This E66 issue is no longer an issue any more ...
If segaboys had done this a bit later, things will be different. But anyway, thanks for the contribution from everyone esp. garyopa & myfranco.
Post by: spydermixx on November 17, 2006, 12:21:00 AM
Post by: langnao on November 17, 2006, 12:29:00 AM
QUOTE(spydermixx @ Nov 17 2006, 03:28 PM)
lol, im away for a few days and what do i miss? great job guys, all i need now is some free time from work to do this myself! well done
ha, the starter of the thread have yet to fix it ...
Anyway, myfranco instructions are pretty clear and straight forward to follow ...
Post by: segaboys on November 20, 2006, 07:06:00 AM
I had given up and bought a second XBOX.....
Will be fixing my other....
I must be a addict... I needed my 360 fix
Post by: langnao on November 20, 2006, 09:03:00 AM
QUOTE(segaboys @ Nov 20 2006, 10:13 PM)
Great News....
I had given up and bought a second XBOX.....
Will be fixing my other....
I must be a addict... I needed my 360 fix
You fix the other then you have 2 boxes. One mod. and one unmod. Best of both worlds ...
Post by: davbere on November 20, 2006, 10:22:00 AM
Can I just modify the text manually ?
like change 47 to 59 and 74 to 95 ?
Post by: langnao on November 20, 2006, 10:48:00 AM
But take note, there are 2 parts where u need to change cos the whole firmware, there are 2 portions that refers to the model no. That's y when u flash, u flash 2 portion of the sector at 90002000 & 9003D000. The flashing steps are the same as mentioned above just that instead of replacing with the samsung model string, u just change the drive model accordingly.
myfranco had done it already in his postings. Maybe u can read that ...
Post by: davbere on November 20, 2006, 11:04:00 AM
QUOTE(langnao @ Nov 20 2006, 06:19 PM)
Yap. If you just wanna change the version of hitachi drive. Just replace the drive model no. accordingly. Like 47 to 59 and 74 to 95.
But take note, there are 2 parts where u need to change cos the whole firmware, there are 2 portions that refers to the model no. That's y when u flash, u flash 2 portion of the sector at 90002000 & 9003D000. The flashing steps are the same as mentioned above just that instead of replacing with the samsung model string, u just change the drive model accordingly.
myfranco had done it already in his postings. Maybe u can read that ...
Thanks for the reply.
I have read this thread several times now.
I dont need to do this yet... I am just trying to prepare myself and understand this clearly.
Quote from GaryOpa:
5-Hexediting the original firmware :
starting at >2030 (2 bytes) backwards version becomes "95"
starting at >20D4 (2 bytes) forewards version becomes "59"
starting at >20DE (8 bytes) ver. build date becomes "06/01/24"
The second part of the firmware:
starting at >3D49E (2 bytes) forewards version becomes "59"
starting at >3D4A8 (8 bytes) ver. build date becomes "06/01/24"
starting at >3D51C (2 bytes) backwards version becomes "95
End Quote
To me it almost sounds like moving the bytes backwards and forwards at the specified locations is what changes the Drive version. I just want to be clear on this.
Thanks all you guys for your contributions.
Post by: langnao on November 20, 2006, 06:03:00 PM
Yap.
Changing drive model is much easier as compared to reflect samsung drive model. Lesser hex values to change ...
Post by: myfranco on November 21, 2006, 05:34:00 PM
May Garyopa help us please
Post by: langnao on November 21, 2006, 06:50:00 PM
QUOTE(myfranco @ Nov 22 2006, 08:41 AM)
I think we can make a batch file for those who want it to be auto.
May Garyopa help us please
Then u will have alot more postings on all the problems of chaging drive model and drive swapping ...
Post by: myfranco on November 22, 2006, 06:11:00 AM
I'll try to do that tomorrow to see how it works.
Post by: Gazcoigne on November 29, 2006, 06:19:00 AM
with your permission i would like to add this to my tutorial, and try to get it pinned as this will be essential reading for many 360 users.
kick ass!!
Post by: langnao on November 29, 2006, 07:21:00 AM
QUOTE(Gazcoigne @ Nov 29 2006, 09:26 PM)
congratulations guys top job!! nice teamwork and thinking outside the box.
with your permission i would like to add this to my tutorial, and try to get it pinned as this will be essential reading for many 360 users.
kick ass!!
That will be great help to those who swapped their drives. I m sure myfranco will be glad that his detailed steps be included in a full tutorial.
You will probably have to take care of 4 combinations, samsung - samsung, samsung - hitachi, hitachi - samsung & hitachi - hitachi
Post by: Gazcoigne on November 29, 2006, 09:08:00 AM
QUOTE(langnao @ Nov 29 2006, 01:52 PM)
That will be great help to those who swapped their drives. I m sure myfranco will be glad that his detailed steps be included in a full tutorial.
You will probably have to take care of 4 combinations, samsung - samsung, samsung - hitachi, hitachi - samsung & hitachi - hitachi
yeah my original tutorial covers the method of inserting the key into a hitachi, as that was the only tut that was missing when i wrote it. since then there has been a lot of stuff happening in the 360 scene with the fall update etc so now i think i will simply extend the tutorial to cover the whole process of replacing any type drive in the console. i will begin work on it v soon all being well.
Post by: langnao on November 29, 2006, 09:56:00 AM
QUOTE(Gazcoigne @ Nov 30 2006, 12:15 AM)
yeah my original tutorial covers the method of inserting the key into a hitachi, as that was the only tut that was missing when i wrote it. since then there has been a lot of stuff happening in the 360 scene with the fall update etc so now i think i will simply extend the tutorial to cover the whole process of replacing any type drive in the console. i will begin work on it v soon all being well.
I m waiting for the reply of LEXS from another thread http://forums.xbox-scene.com/index.php?showtopic=567148
Apparantly, his firmware is a bit "weird" compared to the rest on the drive model portion. If this was indeed his original dump, then the changing of the drive model will not be purely on a specific address but more on finding the correct string and replace it. This will impact your tutorial ...
Post by: langnao on November 29, 2006, 06:45:00 PM
Anyway, this confirm the steps drafted by myfranco and thus it is safe to include into the Gazcoigne's tutorial.
Post by: myfranco on November 29, 2006, 08:22:00 PM
Langnao we don't see each other that much since we fixed the problem and started playing games
Post by: langnao on November 29, 2006, 11:05:00 PM
QUOTE(myfranco @ Nov 30 2006, 11:29 AM)
@Gazcoigne if you want to add to your tutorial ,it will be a great idea.However, if you want a full tutorial with easy step by step explanation and pictures , i am in. Just tell me how you want to do it.
Langnao we don't see each other that much since we fixed the problem and started playing games
Yah, not to mention work commitment, etc. But still check the forum regularly but after sometime you will notice things start to be repetitive. Looking for more 'unusual' stuff ...
Post by: Papique on December 04, 2006, 09:17:00 AM
My Hitachi 47DJ died, so I bought an Samsung MS25 TS-H943... To get it running in my Xbox I must flash it with my Hitachi Original firmware, and then, to don't get E66, I must do this:
copy 0x202e - 0x204d from Hitachi 47DJ to Samsung 0x202e - 0x204d
copy 0x20b6 - 0x20d5 from Hitachi 47DJ to Samsung 0x20b8 - 0x20d7
That's correctly?
Thanks!
Ps: which lines of my Hitachi I must copy to insert the key in the MS25? (It's 4000-4200?)
Post by: langnao on December 04, 2006, 09:33:00 AM
QUOTE(Papique @ Dec 4 2006, 11:48 PM)
Well, let me see if I understood it right...
My Hitachi 47DJ died, so I bought an Samsung MS25 TS-H943... To get it running in my Xbox I must flash it with my Hitachi Original firmware, and then, to don't get E66, I must do this:
copy 0x202e - 0x204d from Hitachi 47DJ to Samsung 0x202e - 0x204d
copy 0x20b6 - 0x20d5 from Hitachi 47DJ to Samsung 0x20b8 - 0x20d7
That's correctly?
Thanks!
Ps: which lines of my Hitachi I must copy to insert the key in the MS25? (It's 4000-4200?)
If your original drive is hitach 47DJ and your replacement drive is samsung MS25, you just have to use the firmware package 'xtreme 42 Update' and run either 'Make X42a.bin Report as HT47' (for 42a) or 'Make X42b.bin Report as HT47' (for 42b) to allow the samsung drive reports its model as hitachi 47. It is very much easier ...
The Make link requires 'orig.bin' to be present and this orig.bin must contain the correct key. Since the samsung is your replacement drive, you must dump out the firmware then inject the key from hitach (which is your original drive) into the firmware and save as 'orig.bin'. After that, run the respective 'Make' link that I had mentioned above.
Post by: Papique on December 04, 2006, 10:51:00 AM
One last question that I forgot to ask: If I do that, and install Extreme V4.2b, can I use xbox live or not? There are any firmware that I can use to don't get E66 in Xbox Live with my swapped MS25? Thanks!
Post by: holyniht on December 05, 2006, 03:39:00 AM
Post by: holyniht on December 05, 2006, 04:12:00 AM
QUOTE(holyniht @ Dec 5 2006, 05:10 AM)
excellent tute, but im stuck, im trying to create the step2.bin. I opened step1.bin in 360firmware toolbox saved it as un encreypted, ive over written the mentioned address and my file is always one kb larger thus, it wont reopen in 360toolbox. im using the xvi32 hex editor and its in overwrite mode. ive even typed each bit manually and i always get a larger file. can anyone help?
**Edit**
Found out the problem, xvi32 for sum reason was padding the file. used another hex editor and i got it all 2 work on one go. now my hitachi 47 works on a ms25 mobo. much credit to all that worked hard on this. you guys are geniueses.
Post by: langnao on December 05, 2006, 04:26:00 AM
QUOTE(holyniht @ Dec 5 2006, 06:10 PM)
excellent tute, but im stuck, im trying to create the step2.bin. I opened step1.bin in 360firmware toolbox saved it as un encreypted, ive over written the mentioned address and my file is always one kb larger thus, it wont reopen in 360toolbox. im using the xvi32 hex editor and its in overwrite mode. ive even typed each bit manually and i always get a larger file. can anyone help?
U just rename your original.bin to step2.bin and then use your hex editor edit accordingly and save it.
Post by: droideka on December 05, 2006, 07:02:00 AM
i had a 47dj(wich died, not bricked) and now i bought a new 46 with my key allready injected(the guy just did that to me), but im worried am i going to get the error 66(he says i wont)?
If i do can please someone, and i would be very thankful, please tell me what are the steps to change a 46 to appear as a 47 and then flash it with garyopas package?
Ive read almost all the thread but nothing appeard for this particular case... i have the skill to flash a drive without hassel but this is a bit too much for me...
drive is in original state with my key injected
Please, please can anybody help?
Post by: langnao on December 05, 2006, 06:54:00 AM
QUOTE(droideka @ Dec 5 2006, 09:33 PM)
Hello, i hope someone can help me as i am very confused right now.
i had a 47dj(wich died, not bricked) and now i bought a new 46 with my key allready injected(the guy just did that to me), but im worried am i going to get the error 66(he says i wont)?
If i do can please someone, and i would be very thankful, please tell me what are the steps to change a 46 to appear as a 47 and then flash it with garyopas package?
Ive read almost all the thread but nothing appeard for this particular case... i have the skill to flash a drive without hassel but this is a bit too much for me...
drive is in original state with my key injected
Please, please can anybody help?
The steps are already here in this thread. Just some modification at the editing of the firmware part. Instead of editing the firmware to show the model as MS28, just edit it to reflect as 47 which is easier since it is just drive model change. Of course the flashing part has to be done using 46Flash.exe instead. It was mentioned in the steps ...
A reminder to those who had done the firmware modification especially for hitachi drive. For garyopa next xtreme firmware releases, you can't just run the restore.bat and flash with the new firmware. You had change the drive model and thus the script will use the 'wrong' flashing executable. You can either, undo the drive model changed or modify the restore and flashing script. Do take note of this issue ...
Post by: holyniht on December 05, 2006, 03:59:00 PM
47flash e orig.bin 90002000 1000
47flash e orig.bin 9003D000 1000
Would i have to unstealth my drive 1st , flash, restealth, then restore?
or i could i just flash orig, then do garyopa restore, upgrade firm, then flash step 3 bin back @ those locations?
Post by: langnao on December 05, 2006, 05:19:00 PM
For me, I would prefer to modify the respective scripts, easier ...
Post by: holyniht on December 05, 2006, 09:06:00 PM
Post by: langnao on December 05, 2006, 11:44:00 PM
QUOTE(holyniht @ Dec 6 2006, 11:37 AM)
i would like to edit the script aswell, but what exactly do i edit, thats what i dont know
Wait for garyopa new firmware and we will see. Basically, edit to remove the checking of drive model and just direct to the flashing portion for your drive keeping the rest of the script e.g error checking routines untouched ...
Post by: myfranco on December 10, 2006, 10:46:00 AM
Post by: Dark_Neo on December 10, 2006, 11:42:00 AM
I noticed when comparing the modded firmware (which is just the drives original firmware with the key + values changes) to the firmware from the motherboards original drive the second drive details bit is not at the same offset, is this normal?
Post by: myfranco on December 10, 2006, 06:43:00 PM
Post by: langnao on December 10, 2006, 07:32:00 PM
Anyway, do a dump of the present firmware and check what is wrong. May be able to fix ...
Post by: Dark_Neo on December 11, 2006, 04:04:00 PM
Here's the diff (don't think there would be a problem posting this, it's only arbitary bytes):
CODE
Different between:
First file: "v59-faked-with-key.bin"
Second file: "original-new-key.bin"
------------------------------------------------------------------------
00002030 | 39 35 | 00002030 | 36 34 |
------------------------------------------------------------------------
000020D0 | 35 39 | 000020D0 | 34 36 |
000020D8 | 36 | 000020D8 | 35 |
000020E0 | 31 34 | 000020E0 | 37 37 |
------------------------------------------------------------------------
0003D498 | 35 39 | 0003D498 | 34 36 |
------------------------------------------------------------------------
0003D4A8 | 36 31 34 | 0003D4A8 | 35 37 37 |
------------------------------------------------------------------------
0003D518 | 39 35 | 0003D518 | 36 34 |
------------------------------------------------------------------------
First file: "v59-faked-with-key.bin"
Second file: "original-new-key.bin"
------------------------------------------------------------------------
00002030 | 39 35 | 00002030 | 36 34 |
------------------------------------------------------------------------
000020D0 | 35 39 | 000020D0 | 34 36 |
000020D8 | 36 | 000020D8 | 35 |
000020E0 | 31 34 | 000020E0 | 37 37 |
------------------------------------------------------------------------
0003D498 | 35 39 | 0003D498 | 34 36 |
------------------------------------------------------------------------
0003D4A8 | 36 31 34 | 0003D4A8 | 35 37 37 |
------------------------------------------------------------------------
0003D518 | 39 35 | 0003D518 | 36 34 |
------------------------------------------------------------------------
Oh and in the original v46 firmware the second HL-DT-STDVD-ROM starts at 0x0003D484 but in the v59 firmware from the motherboards original drive it starts at 0x0003D4A0.
Post by: Dark_Neo on December 12, 2006, 01:31:00 PM
Post by: myfranco on December 12, 2006, 05:40:00 PM
You better send it to someone who can reprogramme since there is nothing left for that hitachi.
Can you tell us what you have done after you flashed the hacked firmware?
Post by: rca1 on December 12, 2006, 05:57:00 PM
Post by: majik655 on December 12, 2006, 05:53:00 PM
QUOTE(rca1 @ Dec 12 2006, 04:28 PM)
1st time poster long time reader. Anyways I got a good one for you. I have a 360 v59 drive bricked. Got the replacment v32 drive with v40 fw and e66 with fall update. I sent the drive back and got it fixed to look like a v78. I got the drive installed and e66 still. Do you think the drive has to say v59 and no other type of FW revision?
yeah it must say 59 as that is what your original firmware was. anything else there will not be original.
Post by: langnao on December 12, 2006, 06:59:00 PM
QUOTE(Dark_Neo @ Dec 12 2006, 06:35 AM)
I'm using UltraEdit to hex edit the files, and I've never had any problems with it before. I can't dump the firmware, it's not being detected by Slax any more to get it into modeb, any suggestions on that? I have 2 original firmware files, one before I started any sort of modding, and the second before I tried getting the drive working with the new motherboard (after a restore) there's quite a few differences between those files. Also a compare between the second original and the modded one shows only the changes that should have been made.
Here's the diff (don't think there would be a problem posting this, it's only arbitary bytes):
CODE
Different between:
First file: "v59-faked-with-key.bin"
Second file: "original-new-key.bin"
------------------------------------------------------------------------
00002030 | 39 35 | 00002030 | 36 34 |
------------------------------------------------------------------------
000020D0 | 35 39 | 000020D0 | 34 36 |
000020D8 | 36 | 000020D8 | 35 |
000020E0 | 31 34 | 000020E0 | 37 37 |
------------------------------------------------------------------------
0003D498 | 35 39 | 0003D498 | 34 36 |
------------------------------------------------------------------------
0003D4A8 | 36 31 34 | 0003D4A8 | 35 37 37 |
------------------------------------------------------------------------
0003D518 | 39 35 | 0003D518 | 36 34 |
------------------------------------------------------------------------
First file: "v59-faked-with-key.bin"
Second file: "original-new-key.bin"
------------------------------------------------------------------------
00002030 | 39 35 | 00002030 | 36 34 |
------------------------------------------------------------------------
000020D0 | 35 39 | 000020D0 | 34 36 |
000020D8 | 36 | 000020D8 | 35 |
000020E0 | 31 34 | 000020E0 | 37 37 |
------------------------------------------------------------------------
0003D498 | 35 39 | 0003D498 | 34 36 |
------------------------------------------------------------------------
0003D4A8 | 36 31 34 | 0003D4A8 | 35 37 37 |
------------------------------------------------------------------------
0003D518 | 39 35 | 0003D518 | 36 34 |
------------------------------------------------------------------------
Oh and in the original v46 firmware the second HL-DT-STDVD-ROM starts at 0x0003D484 but in the v59 firmware from the motherboards original drive it starts at 0x0003D4A0.
Based on your earlier post, is it correct to say that your original drive is 59 and now you wanna replace it with 46? Or vice versa?
Yes, the second portion of drive model for 59 is at 0x003D4A0. Thus if you wanna change, you should follow it at this address. What you had shown above is correct for changing a 46 to 'look' like a 59 (modifying the 46 firmware)
Before you implemented the change, was the firmware flashed with xtreme 2.3? You need to do this else you will have problem with the checksum.
Post by: rca1 on December 12, 2006, 07:05:00 PM
Post by: Dark_Neo on December 16, 2006, 01:26:00 PM
Anyway the 46 is off being repaired atm, but I've got my hands on a v47 which I'd like to try, can anyone give me a diff between an unmodded v47 and a v47 faked as a v59?
BTW where is the checksum located? Is it at 0x0003E7FC? If so I'm sure the checksum was zeroed out on the firmware, hence the problem. Is there a way to recalculate the checksum on a firmware? (I don't want to use any modded code, just need to fake it as a v59)
Post by: Druggedpolak on December 19, 2006, 01:39:00 PM
I have a v78 and would like to use my old 47dh in it.
What I am wondering is this part
QUOTE
5-Hexediting the original firmware :
starting at >2030 (2 bytes) backwards version becomes "95"
starting at >20D4 (2 bytes) forewards version becomes "59"
starting at >20DE (8 bytes) ver. build date becomes "06/01/24"
The second part of the firmware:
starting at >3D49E (2 bytes) forewards version becomes "59"
starting at >3D4A8 (8 bytes) ver. build date becomes "06/01/24"
starting at >3D51C (2 bytes) backwards version becomes "95
starting at >2030 (2 bytes) backwards version becomes "95"
starting at >20D4 (2 bytes) forewards version becomes "59"
starting at >20DE (8 bytes) ver. build date becomes "06/01/24"
The second part of the firmware:
starting at >3D49E (2 bytes) forewards version becomes "59"
starting at >3D4A8 (8 bytes) ver. build date becomes "06/01/24"
starting at >3D51C (2 bytes) backwards version becomes "95
Does anyone with a v78 know the backwards, forewards, and build date for it?
Is there anyone who can show me what these are if I Hex edit it and show these addresses?
Thanks a bunch
Post by: myfranco on December 19, 2006, 03:12:00 PM
Post by: Druggedpolak on December 19, 2006, 02:42:00 PM
That saves me a lot of trouble.
Toolbox 3.0 just keeps getting better and better lol