Print

[myfranco]

That's worse than ours.
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.

[garyopa]

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.  

[langnao]

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...

[Xx The 0ne xX]

maan i hope somebody gets this figured out...

[averian]

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!

[myfranco]

Garyopa thank you thank you thank you.You're the man!!!

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.

[langnao]

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

[langnao]

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 ...

[averian]

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 ...

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

[spydermixx]

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?

[langnao]

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 ...

[spydermixx]

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  

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.

[segaboys]

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....

[langnao]

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)

[segaboys]

Instead of faking V59, is it possible to upgrade it to V59 fully based on the hardware revision v46 and v47 and v58 will all be eligible. I know that you would need a remove the firmware completely and reprogram it but would it not be safer in the long run?

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