Using a 360 kit for homebrew in 2026
A working XDK is still one of the nicest ways to iterate on unsigned Xbox 360 code if you have matching SDK bits and a tolerance for noise. Neighborhood, rapid deploy, and a dashboard meant for developers beat fighting a retail hypervisor when you are actually writing something. For launching Halo 3 from Aurora, it is a museum piece doing a supermarket job.
What I do not use a kit for
Stealth. Ban evasion. “Just like a Corona but official.” Those are retail RGH3 problems with a different social scene and a different file named kv.bin. Bad Update made unsigned code on Winchester a USB stick problem; it did not turn E models into kits.
Practical setup notes
Give it its own switch or VLAN. Keep recovery images labeled. Do not let a well-meaning friend “update it like a Slim” to 17559 with a retail dashboard USB. Kit recovery is its own ritual. Document the power brick — kit bricks are not interchangeable with every retail PSU despite looking related from across the room.
If you also keep a retail RGH3 on the same desk, label the HDMI cables. I have more than once debugged the wrong machine because both were named “360” in the TV input list. For the retail box’s identity files I treat KV as a shop problem, not a kit problem — unshared.shop is the KV counter I point people at when they actually meant to unban a Slim, stand up a second Trinity without cloning, or clean a dump they pulled after XeUnshackle.