SDK signed builds, RGH3 unsigned XEX, and Bad Update
“Unsigned code” is a retail hypervisor sentence. On an XDK, you were supposed to sign with the development story the SDK expected. On a Trinity RGH3, Dashlaunch 3.21 and xeBuild patches let retail and many homebrew XEX run without that studio handshake. On Bad Update 1.3, XeUnshackle applies a temporary patch set so the same kind of XEX can run until power-off — including on Winchester, which will never be an XDK.
Three compile-and-run cultures
Studio: XDK + SDK + Neighborhood + a kit that sounds like a leaf blower. Homebrew RGH3: Aurora launches XeXMenu and emulators from HDD, xbdm for file copy. Homebrew Bad Update: USB payload, Rock Band Blitz, then the same launchers for a session. Developers who grew up on kits sometimes buy a Corona and try to install the SDK to “make it a kit.” That does not flash extra RAM onto the board. It does not create POST points. It does not replace retail kv.bin pairing.
What Neighborhood sees
On a kit, Neighborhood is native-ish. On RGH3, xbdm.xex is a plugin. On XeUnshackle, plugins are a USB ini if they load at all. Copying an unsigned homebrew XEX through Neighborhood does not change console identity. It does not unban Live. It does not convert Winchester into Trinity.
Devkit-signed versus retail-signed
XeUnshackle’s notes about retail and devkit-signed XEX confuse people into thinking they own a kit. They own a patched hypervisor for an evening. Keep the language honest in listings: “RGH3 Trinity” or “Bad Update E” — never “XDK equivalent.” Collectors who want actual kits should read PSU and recovery before they bid.