Print

[Exobex]

X360SAM (DOS-based key patcher for Samsung drives) 0.2

This one uses Sniperkilla's method of patching (copy $4000-$43FF from original firmware, the rest from the hacked firmware) as KDX 1.5 ballsed it up when I tried it on my own 360

The original X360SAM only copied $4000-$41FF of the key range.  This turned out to work for some drives, but not all.  Version 0.2 addresses this by copying $4000-$43FF instead.

From the readme:-

X360SAM is a small MSDOS application which will take your original Samsung
firmware plus a hacked firmware (such as XTREME.BIN) and will create a new
hacked firmware containing the correct DVD key.  This is done using
Sniperkilla's method (copying bytes $4000-$43FF from the original file).

Usage: x360sam <original fw> <master hacked fw> <new fw>
e.g.: x360sam orig.bin xtreme.bin hacked.bin

Note: it does not support long file names - use the short versions please!

Also included are three batch files:-

SAMREAD.BAT
To run this, type SAMREAD followed by the Xbox serial number,
e.g. SAMREAD 1234567 61005
This will create a folder especially for that Xbox, read the firmware from
the drive, storing it in the folder as ORIG.BIN.  It will then use X360SAM.EXE
to create a hacked version (called HACKED.BIN), storing it in the same folder.

SAMHACK.BAT
To run this, type SAMHACK followed by the Xbox serial number,
e.g. SAMHACK 1234567 61005
This flashes the HACKED.BIN file (created by SAMREAD.BAT) onto the drive.

SAMORIG.BAT
To run this, type SAMORIG followed by the Xbox serial number,
e.g. SAMORIG 1234567 61005
This flashes the ORIG.BIN file (created by SAMREAD.BAT) back onto the drive.

No need to boot Windows as part of the flash process!

You may need to replace MTKFLASH with your own version (the one included is
customised for VIA EPIA SP series Mini-ITX motherboards with PnP OS disabled).

Don't forget to put a copy of XTREME30.BIN in the SAMSUNG folder!

X360SAM was written in Turbo Pascal 5.5

*** USE AT YOUR OWN RISK - DON'T BLAME ME IF ANYTHING GOES WRONG ***

VERSION HISTORY
---------------
0.2 - Key area increased in size from $4000-$41FF to $4000-$43FF
      (release delayed, hence support for XTREME30.BIN which came out later)
0.1 - Initial release

[L337:XoDuS]

I'm assuming you made this for the new Xtreme 3.0 Firmware?

[KUNFUCHOPSTICKS]

i think you can just use mtkflasher for v3

[Exobex]

QUOTE(juavos @ Aug 7 2006, 02:46 AM)

does this work with the ms25 drives?  Thanks

Works on ms25 drives.
Works on ms28 drives with the switch fitted.

QUOTE(L337:XoDuS @ Aug 7 2006, 03:31 AM)

I'm assuming you made this for the new Xtreme 3.0 Firmware?

Works on XTREME.BIN.
Works on XTREME20.BIN.
I haven't tested it on XTREME30.BIN (wrote it on Saturday, ran it Saturday and Sunday, only discovered XTREME30.BIN last night) but see no reason why it shouldn't.  The only reason it was released last night and not Saturday morning was that I had no access to my website's FTP server.  So no, I didn't make it for Xtreme 3.0, but yes, it should work.  In fact, it should work on ANY Samsung firmware as long as the key remains in the same format and stored in the $4000-$43FF area, with no other changed code in the same area.

QUOTE(L337:XoDuS @ Aug 7 2006, 03:33 AM)

No kidding... he has it in the package, but I was wondering if this could patch the key into the xtreme30.bin properly unlike KDX does.

It uses a different method to KDX, basically the same as hexediting the file.
It copies $0000-$3FFF from the XTREME firmware.
It copies $4000-$43FF from the original firmware.
It copies $4400-$3FFFF from the XTREME firmware.
The resulting third file is an XTREME firmware especially for that particular Samsung, key and all.  X360SAM 0.1 worked fine on my Xbox (and two others) but didn't work on one I bought on Friday night, so I compared the files and realised that the key went past the $41FF mark (XTREME20 readme mentioned this but I thought it was a typo).  Increased the range copied from the original from $200 to $400 bytes, job done, worked a treat, X360SAM 0.2 was born!  Also worked on one I bought on Saturday, an ms28, once I found the soldering instructions on X-S (glad I didn't buy that one first!)

[Exobex]

I doubt the Hitachi keeps the key in the same format and the same location, so I'm afraid the answer's no.

[nibbles]

I really dont think this programme gets the recognition it deserves.  Ive done one samsung manually and one using this and i have to say this really made things much quicker and less tedious.  It shouldnt be haunted by the stigma of previous autoflashers because i really dont see how this could screw anything up.

[Exobex]

The only awkward bit is if you flash over a previous version, e.g. XTREME20.  Not because it'll balls it up (because it won't), but because you'll already have a firmware in that backup folder - it'll refuse to overwrite it!
The solution is to rename the files in the appropriate backup folder to .1st files, for example (for your 1st ever backup, geddit?).  This will then clear the way for the new flash.
I may bugger about with it to sort this, we'll see.

By the way, thanks for the compliment, it's nice to be appreciated!

[Exobex]

The link at the top of this topic will no longer work, as X360SAM 0.2 has been superseded.