You flashed — now prove it
A successful NAND write is only half the job. This post-swap checklist catches the usual “it boots but Live still hates me” problems before you tear the console down again.
Immediate checks
- Cold boot — Power off fully, then on. Confirm dash loads without repeated error loops.
- XeLL sanity — If you still use XeLL entry, confirm CPU key matches your notes for that board.
- KV identity — Re-dump or use your tool’s KV view to ensure the new serial is present (not the old banned one).
- Online test — Sign into Live / your stealth path the way you normally play. One clean session beats ten half-tests.
Still banned?
Confirm you actually wrote the new KV, that you are not loading an old dual-NAND slot, and that the file
you flashed is the one that validated clean. Then open
Support with order ID + serial if a replacement policy applies.
Hygiene after a good swap
- Archive the post-swap NAND next to the pre-swap backup.
- Delete casual copies of
kv.binfrom shared Discord channels or public drives. - Do not clone the new KV onto a second console “just to test.”
- If you use stealth services, update whatever side binds to console / KV identity so you are not mixing old and new profiles.
When to buy another KV
Fresh bans, clear partner hits that appeared after you went online, or a console you are handing to a different owner are all “buy new stock” moments. Use pack sizing if you maintain several boxes.
Helpful links
Tip: Keep order emails and My Files entries — support can resolve replacement cases much faster with that trail.