X360sam 0.6, DOS-based key and version string copier for Samsung drives Options

[Exobex]

X360SAM 0.6 (build 06.11.09) by eXOBeX
======================================

---------------------------------------------------------------------
README PART 1 - THE TECHIE STUFF (if it confuses you, jump to part 2)
---------------------------------------------------------------------

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 and firmware version.

The key is copied using Sniperkilla's method (copying bytes $4000-$43FF from
the original file).

The drive version can come from one of three locations:-
1) The original firmware (same as the DVD key)
2) A separate firmware (Samsung or Hitachi)
3) Within X360SAM (you pick the version)

Usage: x360sam <original fw> <master hacked fw> <new fw> [<version fw> ¦ <version number>]
e.g.: x360sam orig.bin xtreme.bin hacked.bin
e.g.: x360sam orig.bin xtreme.bin hacked.bin was.bin
e.g.: x360sam orig.bin xtreme.bin hacked.bin ms25
e.g.: x360sam orig.bin xtreme.bin hacked.bin 0047

If selecting a separate firmware to copy the version string from, X360SAM will
look for (in this order):-
Hitachi or Samsung strings at $202e-$205d & $20bc-$20eb
Hitachi strings at $202e-$205d & $20ba-$20e9
Hitachi strings at $202a-$2059 & $20b6-$20e5

When selecting a Hitachi version held within X360SAM, the date codes for
0032, 0036, 0040, 0046, 0047, 0058, 0059 and 0078 are all known. I had to guess
the rest, so they're given the same date as the next highest version (e.g. 0027
will have the same date as 0032). For 0060 and higher, the date code from 0078
is used.

If 'ms' followed by 2 digits are used, a Samsung version string will be written.
If 4 digits are used, a Hitachi version string will be written.
Unless, of course, you've created files called 0059, ms28, etc. in which case
it'll try to use those!

If you don't select a version or a firmware to take one from, or if you give an
invalid version, or if you give the name of a "version firmware" that doesn't
exist, the version strings from the original firmware are used.

Note: it does not support long file names - use the short versions please!
This is an MS-DOS application, after all!

------------------------------
README PART 2 - THE EASY STUFF
------------------------------

Included with X360SAM.EXE are eight batch files:-

SAMREAD.BAT, SAMREADA.BAT, SAMREADB.BAT
To run this, type SAMREAD (or SAMREADA or SAMREADB) 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.
SAMREADA.BAT will use XTREM42A.BIN
SAMREADB.BAT will use XTREM42B.BIN
SAMREAD.BAT just calls SAMREADB.BAT anyway.
You can also specify a firmware version file or firmware version,
e.g. SAMREAD 1234567 61005 backups\61005\1234567\was.bin
or SAMREAD 1234567 61005 0059

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.

SAMREMOD.BAT, SAMREMOA.BAT, SAMREMOB.BAT
To run this, type SAMREMOD (or SAMREMOA or SAMREMOB) followed by the Xbox
serial number,
e.g. SAMREMOD 1234567 61005
This does the same as SAMREAD.BAT but without re-reading ORIG.BIN from the 360.
Useful if you've used X360SAM in the past, but now you want to flash a newer
firmware to the same drive.
SAMREMOA.BAT will use XTREM42A.BIN
SAMREMOB.BAT will use XTREM42B.BIN
SAMREMOD.BAT just calls SAMREMOB.BAT anyway.
You can also specify a firmware version file or firmware version,
e.g. SAMREMOD 1234567 61005 backups\61005\1234567\was.bin
or SAMREMOD 1234567 61005 0059

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 XTREM42A.BIN and XTREM42B.BIN in the SAMSUNG folder!

-------------------------------
README PART 3 - THE OTHER STUFF
-------------------------------

X360SAM was written in Turbo Pascal 5.5

Thanks go to:-
Commodore4Eva for his excellent work on the Xtreme firmware
DeViLs360 for the string-change idea
Geebee for his excellent flashing tutorial
Klutsh for making Samsung flashing even easier with his Xtreme Boot Maker
Iriez and the gang for providing "the usual places"
LUFCfan for most of the Hitachi drive ID strings used in V0.6
NU-NRG for testing DeViLs360's string-change idea
Sniperkilla for the expanded key range info
Textbook for helping the noobs on Xbox-Scene :-) and updating Geebee's tutorial
XanTium for always front-paging my new-version announcements!

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

VERSION HISTORY
---------------
0.6 - Two extra options:-
1: either specify a Hitachi (XXXX) or Samsung (msXX) version to get the
appropriate version string.
2: specify a WAS.BIN (or equivalent .BIN file), X360SAM will
take the version number from there (Samsung or Hitachi).
Version string copying range expanded, now copies $202e-$205d/$20bc-$20eb
from Samsung and either $202e-$205d/$20ba-$20e9 or $202a-$2059/$20b6-$20e5
from Hitachi (all strings are 48 bytes).
0.5 - Now copies the version strings at $202e-$205d and $20bc-$20db from the
original firmware, so the hacked firmware reports the original version.
If the firmware version isn't ms-anything, stops with an error.
0.4 - Added I/O error checking, if X360SAM encounters a disk error (because
it's full, for example) it'll delete the partly-created file and halt
with ERRORLEVEL 1 which is now picked up by the batch files.
0.3 - Read/write block size increased to reduce operating time on floppy
drives, logo added, SAMREAD.BAT altered to accommodate XTREME32.BIN.
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, features 256K filesize check and $4000-$41FF key size.

[bhind69]

didn't the last version automatically detect from your original firmware if it was ms25 or 28? Why do you need to specify?

Or am i totally off base.

[Exobex]

didn't the last version automatically detect from your original firmware if it was ms25 or 28? Why do you need to specify?

Or am i totally off base.

You CAN specify, but you don't HAVE TO specify. If you don't specify, it grabs it from the original firmware just like 0.5 does.
This new version offers help for people who have their key but not their original firmware to grab a version from, or people who have replaced a Hitachi drive with a Samsung (won't extract Hitachi keys though, just version strings).

My Samsung (originally running ms25) was quite happily claiming to be a Hitachi with 0078 firmware earlier this evening!

This post has been edited by Exobex: Nov 9 2006, 11:15 PM

[jbaltz69]

Nicely done sir. Thanks!

[port443]

You CAN specify, but you don't HAVE TO specify. If you don't specify, it grabs it from the original firmware just like 0.5 does.
This new version offers help for people who have their key but not their original firmware to grab a version from, or people who have replaced a Hitachi drive with a Samsung (won't extract Hitachi keys though, just version strings).

My Samsung (originally running ms25) was quite happily claiming to be a Hitachi with 0078 firmware earlier this evening!

It is safer to use Xtreme4.2 Update files because the firmwares have been changed to ALTER the responses to certain commands NOT just the ascii text.

[CsL]

"SAMHACK.BAT
To run this, type SAMHACK followed by the Xbox serial number"

Where can I find this serial number? On the X360-case? Or can I find it inside the Xbox, too? Because I don't have the original case :/

Edit

KK, found it, Dashboard - Sys Info - Line 1 :)

This post has been edited by CsL: Nov 10 2006, 06:23 AM

[pizza-man]

use any serial number its for ur own reference
incase it needs to be flashed back to orig

This post has been edited by pizza-man: Nov 10 2006, 06:26 AM

[jbaltz69]

Yeah, you can put whatever the hell you want there. Just for reference.

[hookland]

escuse me, but with x360sam 0.6 is possible flash the hitachi 0078 drive?????

[fredfunk]

nice 1 Exobex

[Textbook]

escuse me, but with x360sam 0.6 is possible flash the hitachi 0078 drive?????

X360SAM is for Samsungs only.

[teddykiller1]

At the risk of sounding thick , i already have the 4.0a on my sammy, can u just flash over the top of it with this new version and 4.2? or do i have to go back to the original FW and then reflash?

sorry if i sounding stoopid just want to be sure .

[ProdigyXP]

At the risk of sounding thick , i already have the 4.0a on my sammy, can u just flash over the top of it with this new version and 4.2? or do i have to go back to the original FW and then reflash?

sorry if i sounding stoopid just want to be sure .

With Samsung drives, you don't need to revert back to original firmware in order to flash a newer firmware. Just flash over the current one.

[Exobex]

It is safer to use Xtreme4.2 Update files because the firmwares have been changed to ALTER the responses to certain commands NOT just the ascii text.

Then use whichever you prefer.

I'll take a closer look to see what else is changed in C4E's edited ones, it shouldn't be too difficult to implement in the next version.

This post has been edited by Exobex: Nov 10 2006, 12:48 PM

[Exobex]

At the risk of sounding thick , i already have the 4.0a on my sammy, can u just flash over the top of it with this new version and 4.2? or do i have to go back to the original FW and then reflash?

sorry if i sounding stoopid just want to be sure .

To expand on ProdigyXP's reply, with the Hitachis only parts of the firmware get overwritten, what you don't want is some mutant firmware with bits of old and new hacks in there.

In the case of the Samsungs, the whole flash gets overwritten in one hit, so any old hacks get wiped out anyway.