BL4K3Y

Give QuickBoot a try. It will create an NXE shortcut to a XEX file.

I don't understand why people are in such a rush to update their JTAG/RGH kernel. For what it's worth, kernel version 16747 and DashLaunch 3.12 are still perfectly fine.

Every FIFA game is XBOX Live only. You can not play XBL-only games over system link.

That's no big deal. You can simply install/transfer them again from their original games discs .

Yes - format/configure your 2TB hard drive and you're all set. A FAT32 hard drive can't be accessed in NXE/Metro unless it has been formatted/configured first.

Almost . It needs formatting/configuring, but apart from that, there is nothing you need to do.

You can use XZP Tool to extract and re-package skin files.

The HDD signature check is removed in JTAG/RGH images which means you can use any size hard drive you like. A 5400RPM drive is perfectly fine as read/write times are fine and the HDD will run quiet. I have a 2.5" 500GB Seagate hard drive in my RGH console.

Build an image with "noremap" enabled and write it to the console with RawFlash. If this fails, you will need a hardware flasher (you can buy one or you can make your own).

Your console looks like a Jasper (look at the Southbridge chip). Use XeBuild's Update Mode (UPDSERV) and the build type will be detected for you.

Good point, but as far as I know, it won't transfer the data to any other device (IntMU/USB).

You don't ever accept an official system update when you are using a JTAG/RGH console. You need to apply the correct update to match your console's current kernel version. For example, if your JTAG/RGH console is on 16747, you can apply the 16747 update to install Avatar/Kinect data. It is also worth mentioning that XeBuild's Update Mode will send the data to your console's internal hard drive (HDD1) if the correct $SystemUpdate folder is present.

Is it an internal hard drive or an external USB hard drive?

You need to point the Default line in Launch.ini to FSD's Default.xex. You can do this manually or set the path using the DashLaunch Installer. For example: Default = Hdd:\FSD\Default.xex.

Replace the files in your FSD folder with clean FSD3 rev775 files.

XeBuild's update mode makes updating your console's kernel version a piece of cake! It updates your console using LAN, so not only is it easier than ever, it is also a quick process. The only thing you need to do is enable/launch UPDSERV on your console, execute one command and XeBuild will do the rest.

Pay attention to what Swizzy said about there being an "old" Flash Config for 16MB Jasper boards. If you see Flash Config 0x01198010, you must use the "jaspersb" image type when building your image. I believe his GUI will select the correct radio button when you load your NAND image as the source .

To build a retail NAND image from files, you need the console's CPU key, the original KV, the SMC Config (original if possible) and a clean/stock SMC. You also need FCRT from a slim console or it will refuse to boot any games, even if you build and write a valid retail NAND image. You also need to make sure the CB and LDV match what CPU fuses say or the console will show RROD error code 0022.

Is the "clicking" sound coming from the HDD?

Which version of XeLL has the NAND got on it at the moment? Build a new image for your console (JTAG/Glitch), rename it to updflash.bin and put it on the root of a FAT32-formatted USB stick. Boot your console to XeLL with the USB stick connected and tell us what happens. For future reference, DO NOT modify/delete ANY files from the Flash:\ partition unless you know what you are doing. In fact, disable the Advanced File Manager view in FSD and then you won't be tempted to mess with any files there .

Did you put the 16747 $SystemUpdate folder in the XeBuild\16747 folder?

Why don't you use XeBuild's Update Mode (UPDSERV) to update your console to 16747 and let it transfer the system update data to your console? Read this great tutorial (thanks JPizzle!) and remember to replace 16537 files with 16747.

Put the DashLaunch v3.12 installer on a USB stick and launch it with XeXMenu or FSD. Your first USB device will be seen as USB0 and the second as USB1.

Removing a path in FSD will only remove it's entry from the database - your games will still be present on the HDD. When you use the function to copy a game disc to your console's hard drive, you can play the game without the disc in the drive (that function basically extracts the contents of the disc to the hard drive). You shouldn't confuse that with mandatory game installs because those are different.

Yeah, I just found out myself .