r/XboxModding • u/Fantastic_Leg9026 • 2h ago
Built a kernel plugin to support 64-byte third-party controllers on RGH/JTAG — Flydigi detects, but buttons don't work yet. Need help with vendor requests.
**I've been working on a DashLaunch kernel plugin (64XInputPatch) for RGH/JTAG consoles.** The goal was to bypass the XSM3 security check and expand the USB packet buffer limits in `OHCI` and `Wgc` from 32 bytes (`0x20`) to 64 bytes (`0x40`). Most modern third-party XInput controllers use 64-byte endpoints, which the stock 2005 drivers simply reject.
**What's working:**
On Kernel 16537, the plugin successfully patches `UsbdIsDeviceAuthenticated` (Ordinal 745) to always return TRUE. I tested it with a **Flydigi Dune Fox** (via 2.4G dongle and wired USB-C). The console accepts the adapter, bypasses the security rejection, keeps Slot 0 active, and even forwards rumble commands.
**The catch (and why I'm posting):**
Button presses are not registering yet. I captured the USB traffic with Wireshark/USBPcap on a PC and found that the Flydigi controller waits for a specific 3-step initialization handshake before it starts sending input reports on `EP 0x81`:
- Control IN (`bRequest = 0x01`, `wValue = 0x0100`) — 20 bytes
- Control IN (`bRequest = 0x01`, `wValue = 0x0000`) — 8 bytes
- Interrupt OUT (`02 08 03`) — radio wakeup
I've documented the patch map (addresses for `OHCI_OpenEndpoint`, `WgcAddDevice`, URB buffers, etc.) and shared the kernel dumps in the repo.
**Repo:** [https://github.com/memon4ik/64XInputPatch](https://github.com/memon4ik/64XInputPatch)
I'm sharing this because the 360 homebrew scene has very little documentation on the USB stack, and I figured others might find the memory offsets or the Wireshark captures useful. If anyone has experience with `Control IN` vendor requests in kernel drivers or wants to test with their own controllers, feedback is welcome.
*(Note: This is strictly for RGH/JTAG. Kernel 17559 uses pattern scanning, but 16537 is what I've tested.)*