Live · identity · 2026-10-11
Xbox 360 ban wave “unban”: buy a KeyVault, not another stealth xex
Search traffic after a wave always splits into two piles: people reinstalling stealth, and people who need a new KeyVault. Only one of those piles fixes a burned serial.
What a ban wave hits
Waves cluster shared identities. If your kv.bin lived in a public pack, your console can fail Live even when Dashlaunch, Aurora, and the glitch chip look perfect. Longer background: ban waves and shared KeyVaults.
Stealth is not an unban
XBLStealth-class plugins and proto servers hide or reshape how a glitched box presents. They do not rewrite Microsoft’s memory of a serial that already circulated. If the vault is burned, you replace kv.bin. Primer: what stealth is actually doing.
Account ban vs console ban
Gamertag / Gold problems are not the same as a console identity ban. Profiles ride on top of the vault. Mixing those diagnoses wastes weekends. See profiles, Gold, and KV.
The practical unban path
- Keep the original NAND dump and CPU key.
- Confirm the failure is identity (Live / KV), not a bad Dashlaunch liveblock line.
- Install a checked unshared KeyVault — not a Discord zip.
- Rebuild, flash, verify, then reintroduce stealth if you still need it.
Checked stock: unshared.shop. Walkthrough: KV change / unban article.