replacing dvd drive

[walter83]

I have one question thats on the back of my mind..

My unit has a Hitachi 59d, and I want to replace it with a hitachi 47d drive... I have keys and backups of all original firmware's..

My question is: When I modify the firmware on the new 47d drive with maximus 2.3r2 code, do I need to modify anything else due to different firmware rev's?

Dint fall update perform such a firmware check?

Do I need to make my new 47d report firmware as 59d to avoid issues?

Thanks...

 

[walter83]

It looks like Microsoft has implemented 'DVD DEVICE' and 'DVD VERSION' control in the new kernel, a bit similar to the Windows XP/VISTA device upgrade check!
Apparently Microsoft stores the original stock factory drive/version somewhere on the 360, and with the new Fall06 kernel it will give the user an E66 if it detects a drive model or firmware version change.

Can a new dvd drives firmware be updated to show old dvd drives ver??? Anyone???????

 

[hmelo]

Yes, it can. This can be done via hexediting your backup image and reflashing the sectors that contain this info or you can use maximus' firmware toolbox v3.0 to change the version. The later is your best option.

Caster.

 

[walter83]

Yes, it can. This can be done via hexediting your backup image and reflashing the sectors that contain this info or you can use maximus' firmware toolbox v3.0 to change the version. The later is your best option.

Caster.

Ohh YES! v3 of maximus firmware toolbox has the SPOOF FIRMWARE option!

Thanks!

 

[electrodeman]

Can someone explain why you need to spoof the old drives firmware version on the new drive?

 

[Textbook]

Can someone explain why you need to spoof the old drives firmware version on the new drive?

Because with the Fall Xbox Live Dashboard Update, a drive version check was implemented. If your current drive version differed from the original version stored, the Xbox 360 would give an error 66 and refuse to run.

 

[MatC]

Can someone explain why you need to spoof the old drives firmware version on the new drive?

Because with the Fall Xbox Live Dashboard Update, a drive version check was implemented. If your current drive version differed from the original version stored, the Xbox 360 would give an error 66 and refuse to run.

when flashing the patched bin to a new drive with the old drive's bin dvd key, doesn't it erase all traces of the new drives original key? it is afterall flashed with the original key in the firmware. Or is there somehow still traces of the original key of the new drive or ID or something. That's why i guess i don't understand spoofing and why it's necessary. I presume MS can kill the drives again with future updates because they can detect the spoof?

 

[Textbook]

The drive keys and drive versions strings are completely separate/different things. Your drive key is a lock to your motherboard alone, and it is a unique 32-character hexadecimal string.

The drive string is relatively simple, it shows up in your firmware as ms25 and 52ms (ms25 spelled backwards). These two entries can be hexedited to read ms28 and 82ms if say.. you were spoofing your firmware to MS28.