Xbox 360:R-JTOP

The steps on this page are considered risky for your console, as there is a chance you can brick it. Please have someone else mod your console if you are not experienced in soldering!

The R-JTOP hack was the first open source modification that allows you to run unsigned code, mods, game backups, and homebrew on phat consoles. It works by glitching the CB fuse check when loading the old JTAGable CB, which allows JTAG (SMC Hack) to be performed like normal It works the same way as the R-JTAG+ hack and achieves the same result through a different method. This should only be used if your console doesn’t work well with RGH 1.2. It is useful, as it can be done more cheaply than an R-JTAG, but it is lesser used and therefore you will not receive much support if you run into issues. It’s recommended to take a look at the recommended exploit chart and see what hack is recommended for your console.

Note that R-JTOP does not support Slim/E motherboards.

Requirements

Below are the requirements to R-JTOP your Xbox 360. It’s recommended to read ahead and choose the NAND dumping method and R-JTOP specific wiring that’s right for you, as you will need a NAND programmer and potentially more equipment depending on which methods you choose.

To check that your console is exploitable, it must meet the following conditions. You must have:

1. A fat console (Xenon, Zephyr, Falcon, Opus, or Jasper model). You can look at the back of your console and check this chart to find out what model you have.
   • Xenons and Zephyrs do not have any reports of them working although the original announcement post said "some work".
   • If you have a Jasper, determine whether if there is Memory Unit built in. If it has 214MB of storage, it’s a 256MB NAND. If it has 451MB of storage, it is a 512MB NAND.
2. Your console on dashboard 15572 or higher. You can check this by navigating to Settings > Console Settings > Hover over System Info. Your dashboard version will be shown in the top right in the form 2.0.xxxxx.0, where xxxxx is your dashboard version.
   • If it is on a lower dashboard, you can update it to the latest.
3. Soldering experience. The Xbox 360 is not a good place to learn to solder. Regardless of which dumping method you choose, you will need a soldering iron, solder, and flux.

You will also need:

• A NAND reader that can program glitch chips (JR Programmer, NAND-X, or two Matrix USB NAND Flasher)
• A xc2c64a based glitch chip (CoolRunner 3, CoolRunner rev C/D, or Matrix Glitcher V1/V3) or the ability to compile the source for another chip
• J-Runner with Extras
• Equipment listed in the relevant R-JTOP specific wiring below

Reading your NAND

There are six different methods to making a dump of your NAND chip: xFlasher 360, Nand-X, JR Programmer, Matrix USB NAND Flasher, Picoflasher, or a LPT cable. While an LPT cable can be used, they cannot be used to flash glitch chips, so you will need one of the other devices anyway. It's also not recommended, as it's extremely slow and requires more work than other options. Consider the pros and cons below and choose the method that’s right for you. Once you have decided on a method, select the guide below and follow it to get a NAND dump, patch the dump, and write the dump to your motherboard. Once you’ve completed one of the pages below, continue to the next section.

Device	Pros	Cons
xFlasher 360	Reads NAND fast in 40 seconds to 4 minutes Can also program glitch chips Actively supported USB-C Uses signed drivers	*Most expensive flasher
PicoFlasher	Reads NAND fast in 1-8 minutes Super cheap Easy to find Uses signed drivers	Can't be used for programming glitch chips
Nand-X	Reads NAND in 2-8 minutes Can also program glitch chips	More expensive than most NAND flashers Not much cheaper than the xFlasher Requires unsigned drivers
JR Programmer	Reads NAND in 3-10 minutes Can also program glitch chips Cheap Easy to find	More expensive than PicoFlasher or Matrix Requires unsigned drivers
Matrix USB NAND Flasher	Reads NAND in 7-26 minutes Super cheap	Can’t be used for programming glitch chips unless you modify it Requires unsigned drivers
LPT Cable	Cheap Doesn't require unsigned drivers	Requires PC with a native parallel port and more equipment More difficult Can’t be used for programming glitch chips Takes 30-150 minutes to read NANDs

Programming the Glitch Chip

1. Plug the cable from your programmer into the chip programmer.
   • If you are using an xFlasher, ensure the switch is set to SPI
   • CoolRunner: Slide switch on the CoolRunner to "PRG".
2. Open J-Runner with Extras. Click "Program Timing File" in the upper left and select your console’s tab and the relevant radio button for R-JTOP.
3. Click "Program". When complete, unplug the cable from the glitch chip.
   • Coolrunner: Set the switch back to "NOR".

If you are using an X360ACE, you can follow flashing instructions here

R-JTOP Specific Wiring

The wiring for R-JTOP is the same as the wiring for the JTAG hack. Choose the guide that pertains to you:

Xenon Method

• This is the only method for Xenon motherboards. Do not use it if you have a non-Xenon motherboard.

Boxxdr Method

• This method is for Zephyr, Opus, Falcon, or Jasper motherboards. This method may disable 5.1 audio output.

Boxxdr Method + Open Tray

• Use this method if the Boxxdr method doesn’t boot, you receive E79 errors, or you have issues with HDMI. This method may cause your DVD drive to eject on bootup. Also, your console will reboot instead of shutting down if you turn off the console while a controller is charging via USB.

Glitch Chip Wiring

The wiring for R-JTOP is the same as the wiring for RGH 1.2.

Coolrunner Rev C or D

• A - PLL
• B - STBY_CLK (only if not using oscillator)
• C - POST
• D - RST

=== Coolrunner 3 Lite ===*A - PLL

• B - STBY_CLK (only if not using oscillator)
• C - POST
• D - RST

Matrix Glitcher

• A - RST
• B - POST
• C - STBY_CLK (only if not using oscillator)
• F - PLL

Squirt

• Squirt BGA 1.2: Disable the onboard 670pf and/or 480pf caps by removing R7 and R8
• Squirt Reloaded 2.X: remove R2 and connect STBY_CLK
• Pinout follows written labels
• Don't use POST or RST tuners

X360ACE

• C - POST
• D - RST
• E - STBY_CLK (only if not using oscillator version)
• F - PLL (22K ohm resistor required)
• Remember to remove the diode and connect 1.8V
• Note that the X360 ACE requires you to compile timing files for it

Creating an XeBuild Image

You should now be able to turn on your Xbox 360 and boot into XeLL and see your CPU key. With that CPU key, we can build an XeBuild image, which is a NAND dump built specifically for your console. Ensure that you have written down your CPU key and have powered off your console.

1. Open J-Runner and select "…" next to the Load Source field and select your nanddump1.bin if not already selected. In the upper right corner of the window, select the dashboard version you chose for the patched dump that you wrote to the motherboard and make sure that the JTAG radio button is selected, the R-JTAG box has a check in it, and if you have a non-Xenon console, the Aud_Clamp box has a check in it.
2. Select the "Create Image" button in the top left of the window. It may prompt you for your motherboard model, select it and click OK. It will build your image and save it to a numbered folder within the J-Runner directory as updflash.bin.
   • If you get an error during this step, see the troubleshooting section below.
3. Copy updflash.bin to a FAT32 formatted USB storage device and plug it into your powered-off console. Turn on your console and it will boot into XeLL and begin flashing your NAND. Once it has finished, it will power off your console. Turn it back on, and it should boot to the Microsoft dashboard, which is an indication that you’ve successfully hacked your console. You’re now free to install XEXmenu (instructions in section below).

You may want to leave your Xbox 360 disassembled so that you can:

• ...disable the eFuse-blowing circuit so that you can't accidentally install official updates on your console.
• ...check what it's running temperatures are so that you can judge whether it'd be a good idea to use cooling mods to avoid overheating issues. This is recommended for all fat consoles, particularly Xenons.

Installing XeXMenu

1. Plug a flash drive into your Xbox 360 and navigate to Console Settings > Storage. Select the flash drive and allow it to format the flash drive as a system drive.
2. Extract the CODE9999 folder from the XeXMenu 1.2 rar to your Desktop.
3. Plug the flash drive into your PC. Open Xplorer360 and select Drive > Open > Harddrive or Memcard. On the left-hand side, select Partition 3, then right-click the Content folder, select "New Folder", and name it 0000000000000000 (16 zeroes). Open the new folder, then drag the CODE9999 folder into it.
4. Select Drive > Close, then close Xplorer360. Safely eject your flash drive and plug it into your Xbox 360. Navigate to the Demos section of your dashboard, and it should list XeXMenu there. Select it to launch it.
   • You can install XeXMenu to your hard drive by going to Console Settings > Storage, and copying it from your flash drive to the hard drive.

From here, you can install any homebrew or mods that you want. See this page for a list of recommended modifications and applications to install.