Print

[caster420]

QUOTE(Tal1481 @ Feb 9 2007, 10:37 AM)

PS If any 1 can wirte me a guide with explicit steps - I am willing 2 pay £10 into a paypal account - not a lot of money but at elast it's a gesture ;-)

No need for that.  I have already started a tutorial for this purpose and will finish it up tonight.  It will show a couple different methods (complete hexedit, fwtb, samtool).

Caster.

[Tal1481]

Thank u, thank u, THANK U!

[OriginalCompGeek]

QUOTE(vinikun @ Feb 8 2007, 03:26 PM)

Ok, I was a total idiot when I got my ms25 samsung to replace my hitachi 0047. Here's what I did and why I think it's not working when I try to reflash it / even use it in my 360 (get the Play DVD for every disc I put in the drive):

1. Took the "was.bin" from my hitachi flash.
2. Used the batch file for making the Xtreme 5.2 firmware with was.bin renamed to orig.bin in the same directory.
3. Proceeded to take that firmware and flash it to my new samsung.
4. Flashed fine, put it in my 360 and booted the system up. Tray kept on obnoxiously opening, but I got it to close once in a while.
5. Whenever it did close, it would give me the "Play DVD" option and then it would tell me "put this disc in a compatible xbox 360 system" or some junk.
6. So then I realized the key was probably wrong in the firmware and after reading online, all I had to do was take the xtreme firmware relating to my 47 and replace the key from my old firmware.
7. I tried reflashing the samsung drive knowing this (which now shows up as a hitachi in my bios), but it will always hang after I select my drive in MTKFlash.

Did I brick my samsung?

You needed to take the key.bin hex and put it in FW toolbox.  Try using an Enable0800 disc, you will need that for 5.2

QUOTE(caster420 @ Feb 8 2007, 04:23 PM)

Well, i happen to know you are incorrect.  After the fall update, people began getting E66 when using a firmware that didnt report as a higher version than their original drive version.  Go back and read up on it.  Maybe you dont have the most current kernel/dash on your 360.  This is the reason for there being 28(+/-) firmwares in the current xtreme 5.2 pack, each with different version strings for the appropriate firmware.

Quote from GaryOPA:

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

End Quote.

Caster.

I wrote the major help threads for E66, it's more random than anything.  Again, never had a problem.  It's not gonna just "happen."

QUOTE(slimgrip @ Feb 9 2007, 06:06 AM)

Quick noobish Q??

What did you open the key.bin with to copy the key to paste into fwtoolbox?
I cant open the key.bin in fw toolbox as its only 1kb & gives an error.
If i open it in a hex editor its in hexadecimal format whereas fwtoolbox keys are alphanumeric

Slim

You need to open the Xtreme FW file in FW toolbox and insert the hex code from your key.bin.

[caster420]

Yes, it is almost finished.  I need to do some editing/formatting and you will see it.  Once i get home from work, i'll finish it and post - couple more hours.

Caster.

[slimgrip]

Sorted

I put the hitachi key into an original ms28 firmware, then ran the tool in xtreme5.2 to create a firmware spoofed as a v47.
Worked a treat

Slim