Post by: Exobex on August 29, 2006, 01:02:00 PM
It's a bit more colourful than the previous version, but that's not why it's released.
This one's FASTER. If you're running it from a floppy disk, you should find that the 1,024 drive head moves it used to require have been reduced to just SEVEN.
From the readme:-
X360SAM 0.3 (build 06.08.29) by eXOBeX
======================================
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 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.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
Post by: Textbook on August 29, 2006, 02:24:00 PM
ala xboxexpert-style , haha
Definitely awesome news, this is great stuff, and good to see it's finally the accepted Samsung hex method. Great update.
EDIT: Wonder how long it will take to reach XS-News this time ?
This post has been edited by Textbook: Aug 29 2006, 09:24 PM
Post by: Exobex on August 29, 2006, 02:24:00 PM
To see the topic that triggered this decision, click here.
This post has been edited by Exobex: Aug 29 2006, 09:34 PM
Post by: Exobex on August 29, 2006, 02:36:00 PM
QUOTE(Textbook @ Aug 29 2006, 09:31 PM) 
ala xboxexpert-style , haha
The look-and-feel is actually based on something I wrote back in 2000...
Post by: -FourDoor- on August 29, 2006, 03:58:00 PM
1. Make a bootable disk/usb and copy all of the contents of your X360sam 0.3 to the root of the usb/bootdisk. At this time, I will more than likely replace mtkflash.exe and mtkflash.typ with whatever copy is included in the the xtreme 3.2 package.
2. Copy "XTREME32.BIN" to the "SAMSUNG" folder *same from the usual places from the latest release discussed here: http://forums.xbox-scene.com/index.php?showtopic=543766*
3. Hook up samsung drive to pc and boot to usb drive/disk.
4. Type "SAMREAD 1234567 61005" where the #s will be replaced by my 360 serial #. This step will create a backup of my original firmware labeled "ORIG.BIN" and also create the new hacked firmware called "HACKED.BIN" using x360sam. *Just to confirm based on your .bat file the ORIG.BIN remains untouched and will be my virgin copy of my original firmware.
5. Type "SAMHACK 1234567 61005" where the #s will be replaced by my 360 serial #. This step will flash "HACKED.BIN" that contains the xtreme 3.2 firmware and my keys over to my samsung drive.
6. Power down pc and re-install drive into 360 in order to play both backups and originals.
7. Copy "ORIG.BIN" over to several different places to make backups of.
Do I have everything right?
Post by: Exobex on August 29, 2006, 04:12:00 PM
You'll need a version of MTKFLASH that works with your SATA chipset, if you have no luck with the ones included with X360SAM and XTREME32.BIN, search for Grim187's MTKFLASH post, he's very helpful when it comes to editing MTKFLASH.
Remember, for every noob who asks a seemingly daft question, there's another noob who's scared to ask, doesn't ask and bricks his drive. The moral of the story: don't apologise for asking, we were all noobs once! (IMG:style_emoticons/default/smile.gif)
This post has been edited by Exobex: Aug 29 2006, 11:16 PM
Post by: -FourDoor- on August 29, 2006, 04:43:00 PM
My SATA chipset is "ICH5" and I remember reading in another tutorial that it was supported to work with the sammy drive but was not aware that there were different versions of MTKFLASH floating around until you had noted that the x360sam version was modified. If I attempt to use the MTKFLASH file included with x360sam, what error should I be expecting to see if it is indeed incompatible? Is there a chance of bricking the drive if the file is incompatible?
And whoops, you're right. The connectivity kit is only for the power on the dvd drive. I still had the hdd conection in mind as I was recently copying videos off of the hdd for archive on my PC to free up disk space. So based off of your corrections:
1. Make a bootable disk/usb and copy all of the contents of your X360sam 0.3 to the root of the usb/bootdisk. Copying over a version of MTKFLASH may be necessary at this time if your SATA chipset is not supported with by the incuded MTKFLASH files.
2. Copy "XTREME32.BIN" to the "SAMSUNG" folder *same file from the usual places and from the latest release discussed here: http://forums.xbox-scene.com/index.php?showtopic=543766*
3. Hook up samsung drive to pc and boot to usb drive/disk. (SATA to motherboard and power to xecuter connectivity kit)
4. Type "SAMREAD 1234567 61005" where the #s will be replaced by my 360 serial #. This step will create a backup of my original firmware labeled "ORIG.BIN" and also create the new hacked firmware called "HACKED.BIN" using x360sam. The ORIG.BIN remains untouched and will be my virgin backup copy of my original firmware.
5. Power down and reboot PC back to the usb/disk.
6. Type "SAMHACK 1234567 61005" where the #s will be replaced by my 360 serial #. This step will flash "HACKED.BIN" that contains the xtreme 3.2 firmware and my keys over to my samsung drive.
7. Power down pc and re-install drive into 360 in order to play both backups and originals.
8. Copy "ORIG.BIN" over to several different places to make backups of.
Thanks in advance for the help and creating the tool.
Post by: Exobex on August 29, 2006, 05:06:00 PM
You may find it better to connect the SATA cable AFTER the PC has booted. I do, but you may get different results as you have a different chipset to me.
Anyway, bedtime (and I've just scoffed a load of cheese and necked a bottle of Jacob's Creek, so I should be in for an "interesting" night's sleep!)
Post by: xboxexpert on August 29, 2006, 11:12:00 PM
QUOTE(Textbook @ Aug 29 2006, 04:31 PM) 
(IMG:style_emoticons/default/biggrin.gif)
ala xboxexpert-style , haha
Definitely awesome news, this is great stuff, and good to see it's finally the accepted Samsung hex method. Great update.
EDIT: Wonder how long it will take to reach XS-News this time ?
(IMG:style_emoticons/default/grr.gif)
Post by: helfire on August 29, 2006, 11:37:00 PM
Post by: Exobex on August 30, 2006, 02:26:00 AM
Behind the spring-loaded flap on the faceplate
On the bottom (if you've removed the 360's plastic case)
Probably elsewhere as well.
If you're only ever going to work on one 360 (and not end up modding loads of them) you can just put any two numbers in. SAMHACK 1 1 will work quite happily. I recommend using the serial number though.
UPDATE
X360SAM now comes with FOUR batch files. The fourth one is SAMREMOD.BAT.
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 (and therefore already have an ORIG.BIN for that particular 360), but now you want to flash a newer firmware to the same drive - one based on XTREME32.BIN, for example.
Post by: wdew123 on August 30, 2006, 02:59:00 AM
QUOTE(Exobex @ Aug 30 2006, 06:31 AM)
Note: due to the ridiculous level of arrogance and elitism displayed on XboxHacker.net (together with what I feel to be an air of contempt towards Xbox Scene), the link to 0.3 has been withdrawn from their board and the 0.2 .rar file replaced with one containing a simple readme.txt file. Future releases will be announced on the Xbox Scene forums ONLY.
To see the topic that triggered this decision, click here.
man i see what you are saying it looks like they know everything at xboxhacker but most of them are just wannabes
Post by: sicknasty413 on August 30, 2006, 04:39:00 AM
QUOTE(xboxexpert @ Aug 30 2006, 01:19 AM)
(IMG:style_emoticons/default/laugh.gif) (IMG:style_emoticons/default/laugh.gif) (IMG:style_emoticons/default/laugh.gif) (IMG:style_emoticons/default/laugh.gif)
Awesome stuff man (IMG:style_emoticons/default/cool.gif)
Post by: ash1471 on August 30, 2006, 09:03:00 AM
This post has been edited by ash1471: Aug 30 2006, 04:04 PM
Post by: jtom617 on August 30, 2006, 09:05:00 AM
great version, just tested it out, works flawless, only thing i dislike are the commands. 
Post by: sinister slipknot on August 30, 2006, 09:26:00 AM
Post by: Exobex on August 30, 2006, 10:50:00 AM
QUOTE(ash1471 @ Aug 30 2006, 05:16 PM)
He is covering his own arse with that statement thats all. When ever you flash anything there is a risk....Birdy flashers for instance. This program is great I cant fault it one bit:)
Especially in a world where everyone's trying to sue everyone else for something or other. If X360SAM (and its supporting batch files) brick a drive, I'll be surprised and most certainly pissed off, but I won't be shelling out for a new 360. Unless it's one I'm flashing myself, of course!
Has anyone tried 0.3 on floppy disk yet?
Post by: Textbook on August 30, 2006, 11:04:00 AM
Post by: Textbook on August 30, 2006, 05:59:00 PM
I used a floppy disk. I was upgrading from 3.0 to 3.2. First of all, it was failing to make the Backups directory, because it is already included in the download and was already on the disk. Some noobs might get scared when they see "MKDIR BACKUPS FAILED" I knew it was nothing, and continued on. Everything worked fine and very quickly, great job Exobex. I sucessfully upgraded to 3.2 without booting back into Windows. Here are my timings:
Entire SAMREAD process (fw dump and X360SAM) : 2 minutes, 18 seconds
Entire SAMHACK process (fw write): 1 minute, 16 seconds
X360SAM alone (time started after fw dump reaches 100%) : 24.08 seconds
Very fast!
In all, takes less than five minutes to read, power cycle, and write. All in dos too.
A note: Do NOT use a floppy for multiple drives. Use 1 floppy per drive. I ran out of space on the second drive, during the X360SAM process. Received a "runtime error 101 at 0000:0A49." The orig.bin was fine, but the hacked.bin only got to 38,400 bytes. Floppies just don't have too much free space after putting the dos files on there.
All in all, a great update Exobex.
Post by: Exobex on August 30, 2006, 07:32:00 PM
QUOTE(violent_femme @ Aug 31 2006, 02:01 AM)
I tried using it and ended up being E65'ed. Performed emergency CPR on it.
Now I have successfully done it with a floppy to the point where it's not red lighting/E65ing me, but now it won't boot up originals or backups until i flash back to the orig.bin. It keeps giving me the "To play this disc, put it in an Xbox 360 console."
Any suggestions/tips/info would be greatly appreciated.
Is there plenty of free disk space on the floppy?
What's the chipset/motherboard you're using to flash?
What Xtreme firmware are you using? If using 3.2, it might be worth trying with 3.0 or 3.1.
What's the version of firmware already on the drive? You'll find this on a label on the top, e.g. ms25.
I've only had a similar problem twice. The first time was with KDX 1.5, the second with X360SAM 0.1 (which is why 0.2 was released, copying $4000-$43FF instead of $4000-$41FF as some drives seemed to have bigger keys). Didn't notice any E65 error, but did find that game discs booted to the video clip instead of the game.
Post by: Exobex on August 31, 2006, 06:19:00 AM
QUOTE(violent_femme @ Aug 31 2006, 12:29 PM)
Are there any methods to wipe clean what is on the drive and then to restore the ORIG.bin?
mtkflash /m w orig.bin
This will completely replace the firmware on the drive with ORIG.BIN.
Looks like I'm going to have to add a check to X360SAM that deletes the half-finished HACKED.BIN if it runs out of disk space, this will also pick up on disk read/write errors, important when using floppies!
Post by: Textbook on August 31, 2006, 06:56:00 AM
Post by: Textbook on August 31, 2006, 01:37:00 PM
A special thanks to l33 for putting this together, saving people time and making the floppy/USB preparation an easier process.
Auto XSAMDrive Thread (keep discussion in that thread, leave this one solely for X360SAM)
Readme and Download
Post by: Exobex on August 31, 2006, 02:54:00 PM
Version 0.4's been released!
New version, new thread.
Post by: ash1471 on August 31, 2006, 03:48:00 PM
QUOTE(Exobex @ Aug 31 2006, 10:01 PM)
Good lad!!!! Now the program is perfect not just amazing
