So you want to JTAG your xbox360? (POST 248 FOR xeBuild/16197 TUT)

Better solutions exist for multi-disc games.

For trouble-free use, I highly recommend a hard drive. The great thing about the JTAG is you don't need an official one, any 2.5" SATA hard drive will do, 20gb, 500gb, 1TB - whatever. You can pick up the enclosure for it from ebay or DealExtreme for $10.

To get going on trying a USB method you need to do the following:

Format the drive to FAT32, put your files onto the hard drive in their own folders, also put on Freestyle Dash into it's own folder (e.g. USB:\Freestyle). Get the Live CD version of XexMenu. Burn the ISO to a CD and put this into the DVD drive of the console. Run the application and from here you can run other XEX files (programs) such as Freestyle Dash. To get the best usability you should run DashLaunch which is an app that will launch applications on boot (e.g. Freestyle Dash) so you don't always have to go into XeXMenu. Be sure to set up your launch.ini file properly, read the README with DashLaunch.

If you got it working, when you have your USB hard drive connected and turn on the console it should auto-launch FSD. In FSD you can set up drive paths for FSD to search for Homebrew, Games, Emulators etc so set it up properly and then use away. Note that if the drive is formatted FAT32 you cannot use it for saving games or other xbox data. It is possible to use the dashboard to format the hard drive into XBFS format but that only uses a maximum of 16GB. Then you can format the rest of the drive as FAT32 using a PC. This dual-format drive can save games (on the XBFS partition) and store files for Freestyle Dash on the FAT32 partition. There are a few caveats I can think of, they might have workarounds though - since the USB drive isn't following standard xbox hard drive file structure I have no idea where you put Title Updates or DLC. These usually go in a specific folder on the hard drive, and I'm not even sure if the console looks on USB storage for TU/DLC. Freestyle Dash v2.0 might take care of the TUs for you though, but you could be out of luck on DLC.

Anyway, that's enough to get you going.

Xbox 360 game DVDs are DVD dual layers roughly 8GB big. The max single file a FAT table can handle is 4GB. This is why you cannot copy them onto the hard drive.

Apart from explaining why it isn't working, telling you you're going about this the wrong way because there are no ISO launchers for the JTAG, and suggesting you read the last post of page 3 again in closer detail, it is against the rules to offer any help in relation to ISO files, or getting backups to run

For $65USD you can pick up a 500GB 2.5" SATA drive and an enclosure from DX, I highly recommend a bigger drive for the JTAG

Dashboard version 2.0.yyyyy.0 where yyyyy is not greater than 7371, but your dash is, so justryan is correct, no JTAG for you

EnterNow wrote: »

To reflect this, do we need to keep using the 'custom freeboot' to inject the aud_clamp smd? Or can I use my 12625 dump done with fbbuild as a reference for BP tool, negating the need to redo the smd fix? I seriously don't want to go soldering again this time either...

I can't be certain that the BestPig tool decrypts the SMC from the provided nand file or has it's own Jasper SMC that it uses. Without being certain, I'd recommend just using custom freeBOOT and throwing in the SMC manually. That being said, it's something that can be fixed quite easily if you forget to click 'custom freeBOOT', and the SMC that I provided is just a bugfixed SMC so the only thing it should have any effect on is stuff like the console rebooting if you leave the play & charge kit. It's not an absolutely vital step, but definitely a recommended one

@justryan: No offence taken, this time around I did wait for Bestpig to update his tool - I was pretty busy when fbBuild v0.31 came around. Sometimes the simpler solution is the better way to go

Firstly, the Bestpig toolbox generated file needs to be called updflash.bin. Are you sure the USB stick is detected? It needs to be FAT32 formatted, not NTFS. The file needs to be located in the drive root, not in a folder.

When Xell is booting if it detects the USB drive and can access it you should see several lines of text where it searches for named files:

Searching for updslot0.bin...
Searching for updslot1.bin...
Searching for updpatch.bin...
Searching for updflash.bin. File found.
If you do not want your console to update then turn the POWER OFF now

If you get to the part of Xell where it's just sitting there and you're looking at an IP address then obviously it isn't working - it's most likely an issue with your USB stick. Either try another USB slot or just use Flash360 to flash updflash.bin instead of Xell.