Print

[langnao]

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

[langnao]

One more thing to add. Even if you had successfully fixed the problem with modifying the model no, it will complicated things in future flash. As Garyopa flashing script will detect the drive being the "new" model and thus use the respective flashing program. Therefore 59FLASH.EXE will be used to flash a 47 drive. You need to account for this and change accordingly ...

[fat]

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?

[langnao]

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

[myfranco]

Langnao you found quite good things.That would help.
In any case it's a good progess and needs to be confirmed(with mosifications as well)

[langnao]

For 59 to 47, dump out the firmware and make a backup copy in case something went wrong and need to restore original.

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

[myfranco]

Langnao we need 47>59 to avoid the error first.However,do you encrypt the firmware or not.As far as i know , we need to encrypt the firmware to flash some sectors.Those adresses might be different in that case.

[myfranco]

Another thing . How do we know which sector to be flashed when it's encrypted?

[langnao]

From the dump, the drive model is just pure text string and don't think it is encrypted. I believe 0x3000 of the firmware to flush will translate to 90003000 (??) when using the respective flash command. For this case, this is the xtreme custom code.

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?

[myfranco]

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

[langnao]

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

[myfranco]

Langnao it's not a problem.If this system works then we can change it back while flashing with new fw(e.g. gayopa 2.4).
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.

[northernmonkey]

My xbox360 was a hitachi originally ... the drive was swapped out for a ms25 samsung, the samsung had the key injected and booted no problem ... xtreme 4.2a was used ... i then did the update to dash 2.0.4532.0 and now get E66 error code as expected as it is a swapped drive!

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)

[myfranco]

I'm sure there are people who replaced broken hitachis with older ones but still no answer.I'm not sure how you can do it since it's samsung-hitachi related problem.
In this topic we are trying to change some sectors in hitachi fw and it seems that yours is more complicated.

[segaboys]

Well, here is one sad story for you:-

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