Backup first, flash second
Every KV swap rewrites console identity data. If you skip a NAND backup, a bad flash or a wrong file can leave you without a working image and without the original KV you started with. This checklist is the minimum we recommend before you touch Flash360, XeLL, or any NAND tool.
Non-negotiable:
Keep at least two copies of the pre-mod dump (USB + PC or cloud). Label them with console nickname,
date, and CPU key.
What to capture
- Full NAND dump from the console you are about to modify.
- CPU key from XeLL / your existing notes (required for many repair paths).
- Original KV extract if your toolset can pull the 16 KB block separately.
- Dashboard / fuse notes if you already documented them for that board.
Suggested workflow
- Boot XeLL (eject-hold power-on on a properly wired RGH/JTAG console) and write down the CPU key.
- Dump NAND to a known-good USB stick with Flash360, XeLL, or your preferred flasher.
- Copy the dump to your PC immediately; verify the file size looks sane for that motherboard.
- Only then download a new KV from the shop and follow the KV swap guide.
- After a successful Live test, archive the “known good” post-swap dump separately from the original.
Common mistakes
- Flashing a KV into the wrong console’s dump.
- Overwriting the only backup with the modified image.
- Using a corrupt USB stick and assuming the dump succeeded.
- Skipping validation of the new KV before writing NAND.
Validate before you write
Drop the purchased file into the online KV validator (or call the API) so you know ban status and partner hits before you spend time flashing. Packs return per-file results — check every entry in a 2 / 3 / 7 ZIP.
Related:
Unshared vs shared
·
After-swap checklist