Export translations

Settings

Group

Language

Format

Export for off-line translation

Export in native format

Export in CSV format

[[Category:Xbox 360]]
<languages/><div lang="en" dir="ltr" class="mw-content-ltr">
Over the years, Xbox 360 consoles have had several motherboard revisions. It is important to identify the motherboard revision to see what exploits are compatible and work best with your console. The steps for the mod itself will also vary depending on the motherboard. The easiest way is to look at the motherboard's PSU connector (phat) or required amperage (phat or Slim). [https://octal450.github.io/identify/ Octal450's identification wizard] is a useful & user friendly tool for identifying an Xbox 360 motherboard. You can view the '''[[Special:MyLanguage/Xbox_360:Buying_Guide|buying guide]]''' for more information on specific revisions and how to identify an Xbox 360's motherboard.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If your console is running dashboard/kernel '''2.0.7371''' or lower, it will have access to [[Special:MyLanguage/Xbox_360:JTAG|the JTAG exploit]]. However, some Jasper consoles manufactured with 7371 were patched against the JTAG exploit, in which case their CB needs to be checked after a NAND dump. Refurbished Xenon consoles with Elpis GPUs will also usually have a JTAG patched CB.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If your console's dashboard/kernel is ''above'' 2.0.7371 and/or has a patched CB, you can use [[Special:MyLanguage/Xbox_360:RGH|various Reset Glitch Hack methods]]. '''2.0.14699''' and lower on original consoles have access to RGH 1, but anything newer is also compatible with RGH 1.2, RGH 2 (non-Xenon), RGH 3, and EXT_CLK (Xenon/Zephyr). The newer RGH methods can also be used on 14699 and older dashboard versions.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
There is also [[Special:MyLanguage/Xbox_360:R-JTAG|R-JTAG]] which requires dashboard/kernel '''2.0.14719''' or higher, and [[Special:MyLanguage/Xbox_360:R-JTOP|R-JTOP]] which requires dashboard/kernel '''2.0.15572''' or higher. They are essentially RGH but instead of glitching the CPU directly into a custom bootloader and into a modified NAND, they glitch the LDV check of the bootloader to boot into a JTAGable bootloader, and into a JTAG NAND. There is usually no need to use these methods over normal RGH, as they require more steps for little benefit.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Any DVD drive in an original console can be flashed without soldering. However, the Lite-On DG-16D2S requires a probe tool to retreive the DVD key without modifying the console's motherboard. If the console was JTAGed or RGHed, the DVD key can be retreived from XeLL.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
All original consoles are also compatible with [[Special:MyLanguage/Xbox 360:Optical Drive Emulators (ODEs)|ODEs]], but you will need to extract the DVD key. Getting the DVD key is the same process as if you wanted to flash it.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
S consoles can use [[Special:MyLanguage/Xbox_360:RGH|most RGH methods]], but cannot use R-JTAG/JTOP or the original SMC JTAG exploit since the CB bootloader in Slim CPUs aren't compatible with JTAGable Phat bootloaders. They also cannot use RGH 1.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
DVD drives from S consoles are flashable if they came with a Lite-On DG-16D4S (usually came with Trinity and some early Corona consoles), but if they have a Hitachi DL10N (uncommon, but could come with any Slim motherboard) or DG-16D5S (usually Corona/Waitsburg slims) you need to buy an aftermarket DVD drive PCB and RGH the console to get the DVD key. The PCB in Lite-On drives also have some of the wires soldered to the PCB, but the Hitachi drives instead have ribbon cables for all connections so replacing the PCB for a Slim Hitachi drive is easier. 
*DG-16D4S drives with MXIC flash need a probe tool like the phat D2S, but uses a different type of probe tool. '''It must be a probe tool for a Slim 16D4S. Do not use a probe tool intended for a 16D2S and vise versa.'''
*Some DG-16D4S drives come with a "Windbond" flash chip [https://www.modchipcentral.com/store/images1/360identify/mtwin.jpg (example)] which requires the infamous Kamikaze mod in order to flash custom firmware. It involves drilling a specific area on the chip to unlock write permissions.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
All S consoles are compatible with [[Special:MyLanguage/Xbox 360:Optical Drive Emulators (ODEs)|ODE devices]], but you will need to extract the DVD key. If your console has a Lite-On DG-16D5S or Hitachi DL10N, the only way to get the DVD key is to RGH the console.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Stingray motherboards in the 360 E are similar to Corona/Waitsburg motherboards in 360 S, but with some features cut like the AV port and one of the USB ports. Thus, they also need [[:File:Full Postfix Guide.png|a postfix adapter]] like on Waitsburg Slims and have [[Special:MyLanguage/Xbox_360:RGH|the same RGH methods]] available.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
DVD drives in Xbox 360 E's are usually a DG-16D5S, which are not flashable and the DVD key cannot be extracted. The same applies to the Hitachi DL10N. It is possible to get the DVD key with RGH, but flashing requires a PCB replacement. S/E Hitachi drives don't have any wires soldered to the PCB, so PCB replacements for those will be easier.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Stringray Xbox 360 E's can use ODEs, but you will need to RGH the console to get the DVD key.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Winchester boards are not exploitable in any way. This includes RGH/JTAG, drive flashing, and ODEs.'''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Choosing what kind of hack to use ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
===[[Special:MyLanguage/Xbox_360:RGH|RGH]]/[[Special:MyLanguage/Xbox_360:JTAG|JTAG]]===
*Various Reset Glitch Hack or JTAG methods will fully unlock the console for homebrew, emulators, unencrypted game backups, region free DVD movies/games, running Linux, etc.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Hacks that fully unlock the console like RGH or JTAG require soldering, and there is no software alternative.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==== Which RGH/JTAG method should I use? ====
The below chart highlights the ''recommended'' hack to use on each console. [[Special:MyLanguage/Xbox 360:Exploit Chart|Exploit Chart]] has a more detailed chart that shows many more RGH methods.
{| class="wikitable"
!Dashboard
!Xenon
!Zephyr
!Falcon/Opus<sup>1</sup>
! Jasper
! Tonasket<sup>5</sup>
!Trinity
!Corona
!Winchester
|-
|≤7371<sup>2</sup>
|[[Special:MyLanguage/Xbox 360:JTAG|JTAG]]
|[[Special:MyLanguage/Xbox 360:JTAG|JTAG]]
|[[Special:MyLanguage/Xbox 360:JTAG|JTAG]]
|[[Special:MyLanguage/Xbox 360:JTAG|JTAG]]
| N/A
|N/A
|N/A
|N/A
|-
|>7371
|[[Special:MyLanguage/Xbox 360:RGH/EXT CLK|EXT_CLK]]<sup>3</sup>
|[[Special:MyLanguage/Xbox 360:RGH/EXT CLK|EXT_CLK]]
| [[Special:MyLanguage/Xbox 360:RGH/RGH1.2|RGH1.2]]
| [[Special:MyLanguage/Xbox 360:RGH/RGH1.2|RGH1.2]]
|[[Special:MyLanguage/Xbox 360:RGH/RGH1.2|RGH1.2]]
|[[Special:MyLanguage/Xbox 360:RGH/RGH1.2|RGH1.2]]<sup>4</sup> or [[Special:MyLanguage/Xbox 360:RGH/RGH3|RGH3]]<sup>4</sup>
|[[Special:MyLanguage/Xbox 360:RGH/RGH1.2|RGH1.2]]<sup>4</sup> or [[Special:MyLanguage/Xbox 360:RGH/RGH3|RGH3]]<sup>4</sup>
| N/A
|}
<sup>1</sup> Opus is just Falcon without HDMI, so they are grouped togeather.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<sup>2</sup> [[Special:MyLanguage/Xbox 360:Standard NAND#(Phat Only) Checking your CB if it's JTAGable|Must check CB via NAND dump]] to see if it is JTAGable. Most - but not all - consoles under 7371 and some on 7371 have an unpatched CB. This mainly effects Jasper systems, as some were manufactured with a patched CB when brand new.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<sup>3</sup> RGH is not currently working on Elpis Xenons with Samsung RAM. A solution is being investigated, but it works on all other Xenons with Infineon/Qimonda RAM.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<sup>4</sup> Requires scraping solder mask off of a tiny point (more difficult). [[Special:MyLanguage/Xbox 360:RGH/S-RGH|S-RGH]] is a viable alternative that has easier soldering.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<sup>5</sup> Most Tonasket consoles are more commonly known as Jaspers with Kronos GPUs. RGH methods are the same, but are never JTAG exploitable.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
===[[Special:MyLanguage/Xbox_360:Drive_Flashing|DVD Drive Flashing]]===
*An Xbox 360 with a DVD drive flashed with custom firmware will allow you to play retail game backups with burned DVDs, but will not allow access to homebrew, emulators, game mods, backups of digital games, or even a region unlock.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
*DVD drive flashing with a any phat or Slim DG-16D4S DVD drive does not require any soldering unlike JTAG or the Reset Glitch Hack.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
===[[Special:MyLanguage/Xbox_360:Optical_Drive_Emulators_(ODEs)|Optical Disc Emulator]]===
*The Xbox 360 had a few optical disc emulators released for it, such as the [[Special:MyLanguage/Xbox_360:XK3Y_ODE|XK3Y ODE]], [[Special:MyLanguage/Xbox_360:Wasabi360|Wasabi360]], and [[Special:MyLanguage/Xbox_360:Boxzii_(X360DOCK)|Boxzii]]. These devices allowed you to play .iso dumps of retail games through USB or eSATA storage.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
*ODEs have not been manufactured in a long time, and were expensive. Similarly to a flashed DVD drive, these didn't unlock the console for unsigned software and were only used for playing disc backups. They tend to not be very common on the used market either.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
===[[Special:MyLanguage/Xbox_360:KK_Exploit|King Kong Exploit]]===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{Note|This hack is not recommended as it is very limited and only for very old dashboards. It is just listed here for completeness.}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The King Kong Exploit used a modified copy of ''Peter Jackson's King Kong'' to allow the Xbox to boot into a Linux distribution. The KK exploit didn't allow access to homebrew outside of Linux.
*This exploit did not permanently modify the console's operating system, and the game had to be loaded every time you wanted to use Linux.
*Since the exploit relies on booting a modified game, the console either needed a DVD drive with modified firmware or a hotswap method in order to boot it.
*The King Kong Exploit only worked on consoles with a '''2.0.4532''' or '''2.0.4548''' kernel/dashboard, and there's no method to downgrade a retail Xbox 360 to a kernel vulnerable to the KK exploit due to the CPU's eFuses.
</div>

Export translations

Navigation menu

Search