Xbox 360 NAND dump backup: the three files that matter
Before you “just try a rebuild,” freeze a copy of reality. A useful Xbox 360 NAND dump backup is not one mysterious nand.bin on the Desktop. It is a dated folder with the image, the CPU key, and a note about which board you read.
What to capture
- Full NAND image — PicoFlasher / J-Runner with Extras for RGH3, or Simple 360 NAND Flasher after XeUnshackle on Bad Update.
- CPU key — from XeLL Reloaded or tool metadata, in a
.txtnext to the dump. - Board label — Trinity, Corona 16MB, Corona 4GB, Jasper, Winchester. Size mismatches brick weekends.
Naming that survives a month: dump hygiene. Tooling: J-Runner + PicoFlasher.
Where the KeyVault lives in that dump
Inside every retail image is a KeyVault (kv.bin). Backing up NAND is backing up identity. If that vault is already shared or banned, your backup is still precious — it is the rollback — but the Live fix is a new unshared vault, not a second copy of the same serial. Primer: Xbox 360 KeyVault explained.
When the original identity is burned, keep the dated original dump read-only and buy a checked unshared KV from unshared.shop before you rebuild. Do not overwrite the only clean read.
Bad Update dumps count too
XeUnshackle does not invent a new console. The file you saved “just in case” still contains kv.bin. Do not mail that zip to five friends. Related: Simple 360 NAND Flasher.