Xbox 360 hardware desk · updated August 2026

Identify the board before you talk RGH3, PicoFlasher, or Bad Update.

Corona, Trinity, Jasper, Falcon, and Winchester are not the same job. This desk logs how to tell them apart, why Corona 4GB dumps are a different object than 16MB NAND, and how dashboard 17559 homebrew still sits on top of a KeyVault, CPU key, and kv.bin whether you soldered RGH3 or only ran Bad Update 1.3.

RGH3Bad Update 1.3PicoFlasher Corona 4GBTrinity SlimWinchester E J-Runner with Extras17559XeUnshackle

Why this exists

Most 360 modding searches in 2026 are not “how do I solder POST_OUT.” They are “will Bad Update work on my Winchester,” “is RGH3 worth it on a Trinity if Bad Update 1.3 is instant,” and “why did PicoFlasher read a 16MB image off a 4GB Corona.” Those questions share a motherboard. They also share a console identity. Homebrew, Aurora, XeXMenu, stealth, and Live all assume you know which silicon you have and that the NAND you keep actually belongs to that CPU.

I write for anyone in the 360 scene: people about to RGH3 a Jasper, people who will only ever use Rock Band Blitz + Bad Update on an E model, people cloning HDDs with FATXplorer, and people who already have Dashlaunch 3.21 and just want the board chart. A KeyVault is not only an “unban product.” It is the identity blob inside every dump you should already be backing up.

Guide · 18 min · August 2026

Bad Update 1.3 vs RGH3 on Corona, Trinity, and Winchester

Non-persistent hypervisor exploit versus a soldered Reset Glitch Hack. What dashboard 17559, XeUnshackle, FreeMyXe, and a Winchester E can and cannot do — and why kv.bin still exists on every path.

Phat · Oct 2026

Jasper Xbox 360 RGH

Identify Jasper first — Coolrunner/Ace V3 territory, not Slim RGH3 fashion.