Updating your Firmware

Do not ever update an RGH/JTAG console using an original system update. This will install a default NAND and brick your device!

This guide will walk you through updating your Kernel/Dashboard to the latest version. Keeping your Kernel/Dashboard up to date ensures that you can run newer games in your console and give you the latest features implemented in the official dashboard. By following this guide, the latest Kernel/Dashboard will be patched to include DashLaunch (using your console information) and then flashed to your console. This process will not break an existing JTAG/RGH installation, even if the hack is dependent on a specific dashboard version.

A video demonstration of how to update your JTAG/RGH dashboard can be found on MrMario2011's channel.

Requirements

• A Windows PC
• A JTAG/RGH Xbox 360 - Identification Guide
  • If you're using Bad Update to install an RGH NAND for a console that has (or is going to have) a glitch chip or RGH3 wiring installed but still has the stock NAND, this guide can also apply to you, but it is strongly encouraged to also have a NAND flashing tool as a backup.
• A NAND dump (flashdmp.bin, nanddump1.bin, or nanddump2.bin file) and your CPU Key (FUSES.txt or cpukey.txt file) - Guide
• Simple 360 NAND Flasher.7z (Optional)
• J-Runner with Extras

Patching the NAND

Note regarding non-Corona consoles with RGH 3 wiring and retail NAND

Falcon, Jasper, Tonasket, & Trinity consoles with the RGH 3 exploit and unmodified retail NAND are incompatible, as the GPIO used for the POST wire is the one used by GPU_RST_N, a signal responsible for one of the RROD codes.

This isn't an issue for Corona/Waitsburg/Stingray consoles, as they have additional unused GPIOs that can be utilized without messing with GPU_RST_N.

You can use modified Freeboot NAND (as done when using Glitch2 RGH3), or wire in a switch to disconnect the POST wire for RGH 3.

For Trinity consoles, you also have the option to apply the following patch with J-Runner with Extras. Follow the directions in the included readme.txt file.

Instructions

1. In J-Runner, select "…" next to the Load Source field and choose your nanddump1.bin, nanddump2.bin, or flashdmp.bin file.
2. Select the appropriate radio button in the top right of the window:
   • JTAG - For JTAG, R-JTAG, or R-JTOP.
   • Glitch - For RGH1.
   • Glitch2 - For RGH1.2, RGH2, RGH3, EXT_CLK, Muffin/Mufas, or S-RGH.
   • Glitch2m - Same as Glitch2 but only used if your eFuses are in a non-bootable state. Rather than using the real eFuses from the console's CPU, it uses virtual eFuses stored on the NAND instead.
3. Put a check in the appropriate checkbox (if applicable) in the top right of the window:
   • If you are using JTAG, select JTAG and leave the R-JTAG checkbox disabled.
     • If you are using R-JTAG or R-JTOP, the R-JTAG checkbox would be enabled.
     • If you are not on a Xenon console, enable Aud_Clamp for either of these three modifications.
   • If you are using RGH1.2, S-RGH, EXT_CLK, or Project Mufas, enable SMC+
   • If you are using RGH2, you don't have to enable any options.
     • If you are using RGH2+ with a CR4, you can also enable CR4
     • If you are using RGH2 with an X360ACE on Zephyr/Falcon, enable SMC+ instead.
   • If you are using RGH3, select RGH3
   • If you have an Xbox 360 E Stingray motherboard, enable WB 2K
     • Many Stingray motherboards use Winbond W641GG2KB-14 RAM, which is incompatible with the older Corona bootloader used by default. This setting just installs a newer bootloader that's compatible with this RAM type, which was already installed on Corona/Waitsburg through system updates. This means that it can also still be enabled on Xbox 360 S Corona/Waitsburg motherboards, or Stingray boards with Samsung RAM, though it won't gain any benefits. You can leave this setting disabled if you know your board has Samsung RAM, but if you forgot or are unsure, then just enable the option to be safe.
   • If you have an Elpis motherboard, enable Elpis/Rhea
     • Many Elpis motherboards have Samsung RAM, which is incompatible with the Falcon bootloader that's used by default with Xenon Glitch2 images. This setting just installs an Elpis bootloader that's compatible with this RAM and GPU configuration, which was already installed on refurbished/remanufactured Elpis motherboards from the factory. This means it can still be used on Elpises with Infineon/Qimonda RAM, though it won't gain any benefits. You can leave this setting disabled if you know your board has Infineon/Qimonda RAM, but if you forgot or are unsure, then just enable the option to be safe.
4. Go in the Patches tab and enable any desired options. Commonly used ones will be listed below (except for WB 2K Buffer, as it is mentioned earlier).
   • noinitmu will disable the ability for the console to initialize the internal memory unit's usable storage during the boot process. This is useful for Corona/Waitsburg/Stingray consoles, as it prevents any accidental writes to the eMMC by a significant amount.
     • This patch also applies to big block 256/512 MB NANDs that can be used on Jaspers, Tonaskets, and Trinities, but since the big block NANDs tend to have perfectly fine reliability, using this option is more of a preference (like if the desired console only has one storage device connected (such as an internal HDD), and you want to avoid having to deal with storage device selection pop-ups in games)
     • Noinitmu is not supported with retail NAND images; only JTAG/Glitch/Glitch2/Glitch2m Freeboot images.
   • Key Fix addresses minor issue with how Corona Glitch2 images are made by XeBuild, where a second copy of one of the CPU's secret keys isn't actually created with the Freeboot patches. While it doesn't normally cause an issue in the majority of games, this patch will fix the infinite loading bug that can occur on RGH Corona/Waitsburg/Stingray motherboards in rhythm games developed by Harmonix or Neversoft, like the Rock Band, Guitar Hero, or Dance Central series of games.
   • UsbDSec will remove the console's security restrictions of XInput peripherals, allowing you to use various controllers or controller adapters as long as they output the XInput protocol. This is also mentioned in the Using Modern Controllers page.
   • XL HDD and XL USB enable the ability to use USB/SATA storage larger than 2 TB, with the caveat that they have to be formatted in a special way with FATXplorer.
     • Note that XL patches will also disable the ability to use non-XL formatted storage! This is explained further on the FATXplorer website.
5. Select your desired kernel version in the drop-down menu. The latest dashboard (17559) will be the default selection in J-Runner.
6. Select the Create XeBuild button and wait for it to finish. It will be located in J-Runner's output folder, and you can click the Show Working Folder button in order to quickly get to it.

Flashing your Patched NAND

Method 1: XeLL

1. Copy updflash.bin into the root of the USB drive and plug it in.
2. Boot XeLL by either turning on the console with its eject button (RGH/JTAG) or XellLaunch
3. If everything went fine, you would get a message saying it was successful, and you should shut down the console.
4. Boot your console and verify that everything works. Make sure you are in the latest kernel version.

Method 2: Simple 360 NAND Flasher

1. Unzip 360 NAND Flasher to your Xbox 360's internal hard drive or a USB drive.
2. Copy updflash.bin to the directory of 360 NAND Flasher's executable.
3. Run the application in your desired dashboard. (e.g. Aurora, Freestyle, XeXMenu, etc.)
4. Press the A button and then press START. The program will flash the new NAND image and automatically reboot the console when finished.
5. Verify that everything works. Make sure you are in the latest kernel version.

Installing the Avatar Data

If you're using a stealth server or a stock console, manually installing the avatar data from a USB drive is not required and can just be downloaded from the internet with the console itself. However, downloading the update from the internet directly with the console can be slow even with an Ethernet connection, so it could still be preferable to install it from a USB drive instead.

You will also need a System Drive set up for the console, if it doesn't have any form of internal storage (either HDD or internal memory unit).

1. On your PC, download the latest system update from Xbox.com
   • (mirror)
2. Extract the update and copy $SystemUpdate to your USB storage device. This can also be put on a System Drive.
   • You might need to change $SystemUpdate to $$ystemUpdate to bypass DashLaunch's update blocker if you have RGH/JTAG.
3. Plug the storage device into your Xbox. This seems to work best when in the original dashboard.
4. If you see THIS, press yes. If you see THIS, DO NOT ACCEPT, AS YOU WILL BRICK AN RGH/JTAG CONSOLE.
   • If you're just updating a stock console, then you don't have to worry about the pop-up message, since you are using the standard update process anyway. However, note that the second one will blow the CPU's fuses for the newer dashboard.
5. The Xbox 360 will install missing data and then reboot. Verify the installation by going to the original dashboard and checking that your avatar has skin and does not look like a generic white character anymore.