2026 comparison · 18 min read
Bad Update 1.3 vs RGH3 on Corona, Trinity, and Winchester
Two different communities now use the word “modded 360.” One means a Trinity or Corona with RGH3, xeBuild NAND, Dashlaunch 3.21 in flash, and Aurora on an internal SATA drive. The other means a Winchester E that never opened, dashboard 17559, a USB stick, Rock Band Blitz, and grimdoomer’s Bad Update hypervisor exploit — in 1.3 form, theoretically near-instant — then XeUnshackle so unsigned XEX and plugins exist until you power off.
Those people are all 360 modders. A KeyVault, CPU key, and NAND backup belong to both groups. Persistent glitch does not. This article is the board-level split I wish search results led with.
What Bad Update is
Bad Update is a software-only hypervisor exploit. It does not reprogram SPI flash as a persistent hack. It does not install RGH3. When the console reboots, you are retail again. Official writeups stress dashboard 17559. Bad Update 1.3 (August 2026) dropped the Tony Hawk’s American Wasteland trigger in favor of Rock Band Blitz, added bootanim recovery for people who replaced the boot animation XEX with an unsigned file, and aimed at reliability that older 30%-over-twenty-minutes builds did not have.
Post-exploit loaders matter. XeUnshackle applies HV/kernel patches similar in spirit to an RGH xeBuild patch set, then loads a Dashlaunch-like launch.xex from the USB session. FreeMyXe is the other name people search; the important warning from ConsoleMods-style docs is: do not install Dashlaunch to NAND on a retail Bad Update box. That is a brick recipe. XeUnshackle already carries the session loader.
What RGH3 is
Reset Glitch Hack 3 uses the SMC on compatible boards so you do not need an Ace V3, Coolrunner Rev C, or Matrix glitcher. Wiring is still soldering: CPU_RST, POST, a diode, a resistor, board-specific points. The reward is persistence. Cold boot, XeLL or dash, Aurora, launch.ini plugins, stealth xex, xbdm.xex for Neighborhood — without launching Rock Band Blitz every afternoon.
RGH3 does not run on Winchester. It does run on many Trinity and Corona boards and on a lot of Jaspers. RGH1.2 with a discrete chip is the older persistent method still living on Phats. JTAG and R-JTOP are kernel-era stories for dashboards that have not been 17559 for a decade. I mention them so searchers landing from “JTAG 360” know they are not interchangeable with Bad Update.
Who should pick which
| Goal | Prefer |
|---|---|
| Winchester / 360 E unsigned code | Bad Update + XeUnshackle |
| Trinity/Corona daily Aurora, stealth, FTP | RGH3 |
| No soldering, try homebrew this weekend | Bad Update 1.3 |
| Sell a “modded” console that boots hacked cold | RGH3 (honest listing) |
| Keep warranty-ish retail NAND intact | Bad Update (still a ToS issue, but no glitch wires) |
| Live play with a stealth plugin every day | RGH3 + identity hygiene |
Why kv.bin shows up in a Bad Update article
Because the exploit does not invent a new console. Your KeyVault is still in NAND. If you dump with Simple 360 NAND Flasher after XeUnshackle, if you later RGH3 the same Trinity, if you dual-boot a second Slim with a copied dump, identity is the through-line. Modders who only wanted GOD backups still leak serials when they share nand.bin in Discord.
I do not treat KV shops as only for banned Live accounts. Anyone cloning a dump, commissioning an RGH3, or parking a Winchester until a persistent hack exists should know whether the vault in that image is unique. That is dump hygiene. It is also how the rest of this site talks about Corona 4GB.
Dashboard 17559 is not optional trivia
Bad Update public builds target 17559. RGH3 boxes often sit on the same kernel so Dashlaunch 3.21 and modern Aurora builds match. If your friend’s “exploit USB” fails, ask the dash version before you ask the board. NXE settings, System Info, or a NAND read will tell you. Updating a Winchester to 17559 to run Bad Update is a different risk conversation than updating an RGH3 Trinity through Dashlaunch’s update helpers — do not mix those how-tos.
Marketplace closure and the remaining Live stack confuse newcomers. Offline backups, original Xbox titles, and Kinect experiments do not require Live. Stealth and KV quality only enter when the console talks to Microsoft’s servers. Plenty of Corona Notes readers never sign in. They still need the board chart.
Continue with Corona 4GB dump mechanics or the RGH3 first-boot checklist.