Xbox 360 KeyVault pairing myths (retail RGH vs devkit)
“Just pair the KV” is the most expensive five words in 360 Discord. Pairing means matching a vault to a CPU key / rebuild correctly — not laundering a kit image onto a Trinity and calling it an unban.
Retail RGH ≠ XDK
Studio kits and retail Slims are different machines. If you meant to stand up a retail RGH3 for Aurora / Live, you want a retail unshared KeyVault, not kit NAND folklore. Baseline: retail vs XDK · longer myth list: KV pairing myths.
What pairing actually is
Your CPU key decrypts. xeBuild / J-Runner stitches bootloaders with a kv.bin that belongs in that image. Wrong vault placement looks like “pairing failed” when you really dropped a random bin into the wrong slot. Dump hygiene: dump hygiene · identity map: kv.bin explained.
When to buy instead of invent
Banned retail vault, second console, or refuse to clone: purchase a checked unshared KV at unshared.shop. Kits remain useful for XBDM / unsigned workflows — XBDM notes — but they are not a KV store.