Post by: Exobex on August 31, 2006, 02:50:00 PM
If for any reason X360SAM cannot complete its job (due to a disk read/write error or the disk being full) it will delete the part-made file and stop with an error message. It will also now set the DOS ERRORLEVEL according to why it's stopped:
0 = completed successfully
1 = aborted (disk error, required files missing, unwanted files present)
2 = "usage" screen displayed (not enough/too many parameters given)
The SAMREAD.BAT and SAMREMOD.BAT files now detect this errorlevel setting and act accordingly.
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 four 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.
SAMREMOD.BAT
To run this, type SAMREMOD 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.
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 XTREME32.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.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
This post has been edited by Exobex: Aug 31 2006, 10:00 PM
Post by: Wlnb0nD on August 31, 2006, 02:56:00 PM
keep 'em coming
Post by: ash1471 on August 31, 2006, 03:52:00 PM
Post by: -FourDoor- on August 31, 2006, 05:31:00 PM
Post by: xboxexpert on August 31, 2006, 10:57:00 PM
Post by: Zydroid on August 31, 2006, 11:28:00 PM
Post by: vintage_guitar on August 31, 2006, 11:41:00 PM
This post has been edited by vintage_guitar: Sep 1 2006, 06:46 AM
Post by: Exobex on September 01, 2006, 04:41:00 AM
QUOTE(Zydroid @ Sep 1 2006, 06:35 AM) 
Very nice tool, however one thing I would like to see is it display the key, just like the dos KDX version did that was pretty darn usefull. Maybe in the next update??
I don't know the structure of the key, and neither does X360SAM - it just copies the whole block without arsing about with it, which is why it works so well - it keeps things simple. If I start arsing with the key, X360SAM will end up going down the KDX route. If I don't decipher the key correctly, people will start using the wrongly-deciphered key and start bricking drives with it.
In its raw form, the key area is 1,024 bytes in size. To display this on-screen in hex requires 2,048 characters - that's 26 lines on an 80-column display, going off the page unless you're in 43 or 50 line mode, and too much to write down anyway.
QUOTE(vintage_guitar @ Sep 1 2006, 06:48 AM)
oGm DisC ChekciNg gj man.. seriously. this spam is getting old to increase post count..where is this hitachi FW
Today's post has been brought to you by the letters W, T and F.
Post by: Textbook on September 01, 2006, 05:17:00 AM
QUOTE(vintage_guitar @ Sep 1 2006, 01:48 AM)
oGm DisC ChekciNg gj man.. seriously. this spam is getting old to increase post count..where is this hitachi FW
QUOTE(Exobex @ Sep 1 2006, 06:48 AM)
Today's post has been brought to you by the letters W, T and F.
I was asking myself the same question.
Nice update Exobex, and I agree with the key display.
Post by: -FourDoor- on September 01, 2006, 12:07:00 PM
Thanks again Exobex!!! (IMG:style_emoticons/default/biggrin.gif)
Post by: biggy7 on September 01, 2006, 01:22:00 PM
now when i reboot and try thr SAMHACK command, it says hacked.bin doesnt exist and aborts!
ive had a look at the usb flash drive and the hacked.bin is in the backups folder along with the orig.bin
any help guys?
Post by: Zydroid on September 01, 2006, 01:29:00 PM
QUOTE(Exobex @ Sep 1 2006, 11:48 AM)
I don't know the structure of the key, and neither does X360SAM - it just copies the whole block without arsing about with it, which is why it works so well - it keeps things simple. If I start arsing with the key, X360SAM will end up going down the KDX route. If I don't decipher the key correctly, people will start using the wrongly-deciphered key and start bricking drives with it.
In its raw form, the key area is 1,024 bytes in size. To display this on-screen in hex requires 2,048 characters - that's 26 lines on an 80-column display, going off the page unless you're in 43 or 50 line mode, and too much to write down anyway.
Actually I was thinking was like the dos app kdx42.exe and displaying the key which would be just 47 chars including spaces example:
key: 71 72 47 63 F2 F7 BE 73 AF CC DC 1B 94 CF 55 43
rather than 2,048 characters on 26 lines, now that would be confusing.
Post by: ash1471 on September 01, 2006, 01:31:00 PM
QUOTE(biggy7 @ Sep 1 2006, 08:29 PM)
just trying this now, have done the SAMREAD bit and it dumps the firmware and modifies it to make hacked.bin.
now when i reboot and try thr SAMHACK command, it says hacked.bin doesnt exist and aborts!
ive had a look at the usb flash drive and the hacked.bin is in the backups folder along with the orig.bin
any help guys?
Have you put a copy of xtreme32.bin in the SAMSUNG folder??
Post by: biggy7 on September 01, 2006, 01:35:00 PM
QUOTE(ash1471 @ Sep 1 2006, 08:38 PM)
Have you put a copy of xtreme32.bin in the SAMSUNG folder??
yep, thats in the samung folder aswell. when you do samread doesnt it do the key extraction then? it did all that, made 2 files, orig.bin and hacked.bin in DIR: BACKUPS/1234567/12345 (numbers used as an example)
do you think i should just flash manually now with the hacked.bin and mtkflash on the flash drive?
Post by: ash1471 on September 01, 2006, 01:43:00 PM
QUOTE(biggy7 @ Sep 1 2006, 08:42 PM)
yep, thats in the samung folder aswell. when you do samread doesnt it do the key extraction then? it did all that, made 2 files, orig.bin and hacked.bin in DIR: BACKUPS/1234567/12345 (numbers used as an example)
do you think i should just flash manually now with the hacked.bin and mtkflash on the flash drive?
I would delete the 2 files it made in the backups folder and try again with samread just incase the hacked.bin is not correct. Its better wasting 5 mins than having a brick.