What XeLL Reloaded is (and is not)
Recovery environment, CPU key print, HTTP dump. Not stealth, not Aurora, not Bad Update.
NAND is a database. Treat it like one.
XeLL Reloaded, PicoFlasher, J-Runner with Extras, xeBuild, Glitch2 / Glitch2m, and Simple 360 NAND Flasher all touch the same two secrets: a CPU key and a KeyVault. This journal is for RGH3 techs, JTAG museum pieces, and Bad Update 1.3 users who dump after XeUnshackle. You do not need to be buying a vault today to need a dump that is actually yours.
Xbox 360 KeyVault (kv.bin) explained
What an unshared KV is, why shared packs fail waves, and where checked stock lives.
NAND dump backup: the three files that matter
nand.bin, CPU key, board label — and why backing up also backs up kv.bin.
J-Runner with Extras in 2026
PicoFlasher, xeBuild, and the CPU key field versus the KeyVault slot.
CPU key, DVD key, and kv.bin
Three files Discord treats as synonyms. Pairing, sharing, and why offline boxes still care.
J-Runner with Extras and PicoFlasher in 2026
Raspberry Pi Pico, 4GB Corona SPI, xFlasher, NAND-X, writing XeLL to the first 50 blocks.
Dump hygiene: names, backups, Bad Update reads
How nand.bin(1) becomes a brick, and how XeUnshackle dumps still contain a vault.
DVD key vs CPU key vs kv.bin
Replacing a laser is not a vault swap. Drive firmware, discs, and dump hygiene.
Simple 360 NAND Flasher vs PicoFlasher
XeUnshackle software dumps versus a Raspberry Pi Pico on SPI / Corona 4GB.