BL4K3Y

It sounds like an issue with bad blocks to me. What are you using to build the 16197 image?

If it's a 9199 freeBOOT image, it's probably an older version of XeLLous. Try renaming the NAND file to "updflash.bin" (minus the quotes). Failing that, use Trancy's NAND Flasher 360 as I mentioned above.

Which version of XeLL is the console currently running? If you can boot the console to the dashboard, use Trancy's NAND Flasher 360 to update or use a hardware flasher (NAND-X, JR-Programmer etc).

Set the date and time through Console Settings using the Metro dashboard (hold RB as the console boots up). Your console should automatically set the date and time when it detects an internet connection.

What does your launch.ini say? If livestrong = true, your console will not be able to connect to the internet. Ensure liveblock = true and livestrong = false.

That's because F3 is now using LiNK - you can find settings for it under the "Settings" tab. You also need DashLaunch 3.04 installed with Pingpatch and DevLink enabled (refer to DashLaunch "info_launch.ini" for more details). I suggest you read JPizzle's tutorial.

What are you trying to do?

Did you run the HDD Compatibility Partition Fixer and FTP the XBOX1 Compatibility folder across to the HDDX partition (use the files in the nov2007 archive)? It should be noted that not all XBOX 1 titles are compatible. I did however manage to play the PAL release of GTA: San Andreas so it might be worth trying to purchase a PAL version of the game. The "hacked" XBOX1 emulator files do add "extra" compatibility, but it still isn't 100%.

If your JTAG/RGH console is running kernel version 16197 and you have DashLaunch 3.04 installed, enable DevLink and Pingpatch - this will allow you to use LiNK. I'm sure Swizzy's latest version of XeBuild GUI uses DashLaunch 3.04.

Without having DashLaunch installed, DevLink and Pingpatch cannot be enabled. If you updated to kernel version 16202, DashLaunch will not work because a new version is required. In which case, you should revert back to 16197 (no games require 16202 anyway) and install DashLaunch 3.04.

Enable UPnP on the router and reboot/reset it. I'm not a moderator here, but I would have thought that this is an issue of it's own and nothing to do with XeBuild .

You can do that or Clear Data/DB from within FSD/F3 (it's in the General Settings section I think).

If you want GoD containers to show up in the original dashboard (NXE/Metro), they MUST reside in the Content0000000000000000 folder (this is the default GoD directory). You can place them on a USB hard drive and launch them from FSD/F3 as instructed above though (you still need to set a path and the scan depth).

You're kidding, right? You do realise that what you just asked for = piracy? Stuff like FSD and XeBuild isn't developed with piracy in mind - XeBuild builds modified images allowing us to run homebrew code on our consoles and FSD is a dashboard replacement - piracy was never the intention. I wrote this tutorial to explain how to install Avatar and Kinect data on a JTAG/RGH system.

Certainly not. XBL on a JTAG/RGH system will most likely never be done.

Thread updated with some additional information. Thanks to Martin C for amending the original thread over on Team Xecuter forums.

That is an excellent tutorial, but why did you take photos for step 4? Print screen works wonders .

Read the J-Runner PDF or maybe follow this tutorial. Both J-Runner and Swizzy's XeBuild GUI are great applications.

That explains it. The link in my tutorial will download the latest available system update. I suggest you update your console's JTAG/RGH image to 16197 using J-Runner, XeBuild GUI etc., and then follow this tutorial.

Which JTAG/RGH kernel is your console currently running? I'm sure DashLaunch now prevents you from applying a system update newer than the current kernel version.

As JQE said, partition the HDD - a 2TB partition should be more than enough storage space. I mean, how many retail games can one person own ? Lol.

That is correct and F3 is FreeStyle 3 .

Run the DashLaunch 3.04 installer to install it on your console. Let F3 handle your multiple-disc games. Note that some games aren't really multiple discs as such, they are often DLC which must be placed in the Content/0000000000000000/Title ID/00000002 directory on the internal HDD. The directory structure for letting F3 handle the swap is as follows: GameName > Disc 1 > Disc 1 Files and GameName > Disc 2 > Disc 2 Files (GoD or extracted). When the relevant disc is required, F3 will automatically select and load it - remember to move the "duplicate" game entry to "No Section" (Press Y, select Move Game and select No Section then rename GameName Disc 1 to GameName). Note that if DashLaunch Disk Swapper is enabled, you will have issues - use one OR the other!

I don't think the boot screen can be modified - I believe it is hard-coded into F3. However, I'm sure boot screen modification could be made possible in a future release .

This is NOT for updating your JTAG/RGH dashboard/kernel, this is for installing Avatar/Kinect data ONLY. To change the dashboard/kernel version of your JTAG/RGH console, you build a new image with J-Runner or similar. Before you proceed, ensure you have an internal hard drive connected with enough space for the update (I think somewhere around 128MB is required). Also, ensure that you have DashLaunch installed and configured. So, you have a JTAG or RGH system, but no Avatars or Kinect? This small tutorial will help you install them (ensure your Kinect hardware is connected before you begin or you will be prompted to update again once you connect it!). Step 1 Download the USB system update from here (remember to check that the system update you download matches your JTAG/RGH kernel version - go to System Settings>Console Settings>System Info and read where it says Dashboard: 2.0.XXXXX.0, where X = your current dashboard/kernel version). Step 2 Extract the $systemupdate folder from the archive with 7-Zip or similar and rename it to $$ystemUpdate. Step 3 Transfer the $$ystemUpdate folder (the one you renamed in Step 2) to the root of a FAT32-formatted USB stick (I recommend 512MB+). Step 4 Connect your USB stick to your console, power it on and accept the update when prompted. There are different messages shown based on what the system update is going to apply. If you see this: Do NOT accept the update because this is telling you that the system is going to attempt a complete update which alters bootloaders and it will also burn eFUSEs. If you see this: It is fine to proceed with the update. This is the system telling you that additional components are missing. The console will reboot once the update has installed successfully and you should now see Avatars and have Kinect installed (don't forget to configure it!). If the console doesn't do anything, ensure that: The update folder is named correctly.The system update you are applying matches the JTAG/RGH dashboard/kernel version your console is currently running (see Step 1).You inserted the USB stick before booting the console (FSD can block the system update).If, after all this is attempted, the console still won't update, go into FSD and then into the File Manager, look for a SysExt: folder and delete what you can (don't forget to enable File Manager Advanced Mode in General Settings first). Reboot the console and you'll be told that there are corrupted files - reboot the console to resolve this. Do this with the USB stick connected and your console should prompt you to accept the update. I find that if I boot the console to NXE/Metro (hold RB after powering the console on) and THEN insert the USB stick, the update prompt shows up.