xboxscene.org forums

Pages: 1 [2]

Author Topic: X360sam 0.3  (Read 95 times)

sinister slipknot

  • Archived User
  • Hero Member
  • *
  • Posts: 643
X360sam 0.3
« Reply #15 on: August 30, 2006, 09:26:00 AM »

I like how a program aimed at making something easier says 'use at your own risk'
Logged

Exobex

  • Archived User
  • Hero Member
  • *
  • Posts: 1093
X360sam 0.3
« Reply #16 on: August 30, 2006, 10:50:00 AM »

QUOTE(ash1471 @ Aug 30 2006, 05:16 PM) View Post

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?
Logged

Textbook

  • Archived User
  • Hero Member
  • *
  • Posts: 1203
X360sam 0.3
« Reply #17 on: August 30, 2006, 11:04:00 AM »

I'll see if I can try it tonight exobex.  Actually, it will be the first time using X360SAM at all.
Logged

Textbook

  • Archived User
  • Hero Member
  • *
  • Posts: 1203
X360sam 0.3
« Reply #18 on: August 30, 2006, 05:59:00 PM »

My X360SAM experience:

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

Exobex

  • Archived User
  • Hero Member
  • *
  • Posts: 1093
X360sam 0.3
« Reply #19 on: August 30, 2006, 07:32:00 PM »

QUOTE(violent_femme @ Aug 31 2006, 02:01 AM) View Post

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

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

Exobex

  • Archived User
  • Hero Member
  • *
  • Posts: 1093
X360sam 0.3
« Reply #20 on: August 31, 2006, 06:19:00 AM »

QUOTE(violent_femme @ Aug 31 2006, 12:29 PM) View Post
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!
Logged

Textbook

  • Archived User
  • Hero Member
  • *
  • Posts: 1203
X360sam 0.3
« Reply #21 on: August 31, 2006, 06:56:00 AM »

I agree with the disk space check update, that would be nice.  Violent_femme, you can use the "bad flash recovery method" to try and repair the samsung with your orig.bin.
Logged

Textbook

  • Archived User
  • Hero Member
  • *
  • Posts: 1203
X360sam 0.3
« Reply #22 on: August 31, 2006, 01:37:00 PM »

I helped l33 on IRC in the #fw channel last week. In return, he helped me back and gave something back to the scene. He put together Auto XSAMDrive, a small program for preparing a floppy disk or USB pen drive with X360SAM. This helps when flashing the Samsung drive with the Xtreme firmware. Previously, you had to download the HP USB Formatting Tool, download separate DOS files, install the program, run it, and format your drive, then copy the necessary files over. This program will do all of that automatically.

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
Logged

Exobex

  • Archived User
  • Hero Member
  • *
  • Posts: 1093
X360sam 0.3
« Reply #23 on: August 31, 2006, 02:54:00 PM »

I'm going to annoy you now, then...

Version 0.4's been released! laugh.gif
New version, new thread.
Logged

ash1471

  • Archived User
  • Full Member
  • *
  • Posts: 226
X360sam 0.3
« Reply #24 on: August 31, 2006, 03:48:00 PM »

QUOTE(Exobex @ Aug 31 2006, 10:01 PM) View Post

I'm going to annoy you now, then...

Version 0.4's been released! laugh.gif
New version, new thread.


Good lad!!!! Now the program is perfect not just amazing smile.gif
Logged
Pages: 1 [2]