Skip to content
JehuAlvPublic

About

Pad8Lab - custom firmware for 8BitDo controllers. Flash controller profiles for Bluetooth rumble and native Xbox (XInput) support on Windows 11; the Ultimate 2C Wireless is supported today.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

12 stars

Watchers

0 watching

Forks

Pad8Lab — custom firmware for 8BitDo controllers

Pad8Lab flashes custom firmware profiles onto 8BitDo controllers. The first supported model is the 8BitDo Ultimate 2C Wireless, which becomes a native Xbox controller with real rumble over Bluetooth on Windows 11: no drivers, no dongle and no virtual pad.

Out of the box, over Bluetooth, the Ultimate 2C Wireless is a plain HID gamepad on Windows: it does not rumble, and many games do not recognise it. This app flashes 8BitDo's own firmware with two small tweaks, so the controller presents itself as an Xbox Series X|S pad and vibrates over Bluetooth. The change lives inside the controller, so after one flash it works on any Windows PC.

Support is profile-based: only the Ultimate 2C Wireless is registered today, and a new controller means a new profile, not a rewrite of the flashing core.

Use at your own risk. Flashing modified firmware probably voids the controller's warranty. It is reversible (your backup restores the original firmware), but it is not risk-free. Read the disclaimer before you start. This project is not affiliated with or endorsed by 8BitDo.

Download the latest release — a self-contained Windows x64 .exe, no .NET runtime or Python needed.

Screenshots

The guided setup: connect the cable, back up, install the tweaks and reconnect

What the app does, the controller state and what to do with the SmartScreen warning

What it does for the Ultimate 2C Wireless

Feature What it changes
Native Xbox over Bluetooth The controller reports as an Xbox Series X|S pad (045e:0b13), so Windows and games see it as a real Xbox controller through XInput.
Rumble over Bluetooth Games can make it vibrate over Bluetooth, which the stock firmware does not allow. Both motors work.
Fewer Bluetooth interruptions The Bluetooth connection interval is tuned so the pad stays responsive.

Everything else stays as it was. The tweaks only touch the firmware's application area; the bootloader, the calibration and the Bluetooth pairings are never modified.

Why the flashing is needed

The tweaks are small edits to the firmware that runs inside the controller. That is why, once flashed, the controller works on any Windows PC — you only need this tool once. The stock firmware simply has no code path that accepts rumble commands over Bluetooth.

Requirements

  • 8BitDo Ultimate 2C Wireless controller (the PC SKU with the 2.4 GHz dongle) on firmware 1.09.
  • Windows 11 (x64).
  • A USB-C data cable for the one-time flash. Bluetooth cannot flash the controller.
  • To run the released app, nothing else: it is a single self-contained .exe.
  • To build it, the .NET 10 SDK. The app and the flashing core are written in 100% C#/.NET.

How to use

  1. Back up. Connect the controller by cable and press Back up controller. The backup is the safety net: it contains your unit's bootloader check, calibration and Bluetooth keys, and the app refuses to write anything without one.
  2. Check. Press Check (no write) to see what would change.
  3. Install the tweaks. Tick the disclaimer box and press Install. The app puts the controller into update mode, writes the changes, verifies them and restarts it.
  4. Reconnect. Unplug the cable. Remove the controller in Settings → Bluetooth & devices and pair it again, so Windows re-reads the new description.
  5. Play. Turn the controller on over Bluetooth. Windows shows it as an Xbox controller and games can make it vibrate.

To go back, restore your backup the same way. The app puts back the newest backup that still holds the original firmware, so restoring also undoes the tweaks.

Recovery

The bootloader is never written, so a failed or interrupted write is always recoverable:

Turn the controller fully off, hold L1 + R1, and plug in the USB cable. It starts in update mode (the LED blinks white). From there you can restore your backup. This works only over USB.

Windows says "Windows protected your PC"

The app is free and open source, and the .exe is not signed with a paid code-signing certificate. SmartScreen treats every unsigned app from a new publisher as unknown, so the first time you run it Windows may show Windows protected your PC with an Unknown publisher note. That warning is about the missing signature and the download count, not about what the app does.

To run it, press More info, then Run anyway.

To check that the file is the one published here, compare its SHA-256 with the value in SHA256SUMS.txt from the same release:

Get-FileHash .\Pad8Lab-1.2.0-win-x64.exe -Algorithm SHA256

Only a code-signing certificate (OV or EV) removes that warning for everyone; a self-signed certificate does not help. The app is open source, so the code that runs is the code in this repository.

Making the warning go away

For your own copy: remove the internet tag that Windows puts on downloaded files. Right-click the .exe, open Properties, tick Unblock, then OK. In PowerShell the same thing is:

Unblock-File .\Pad8Lab-1.2.0-win-x64.exe

SmartScreen only checks files that carry that tag, so this copy opens without the prompt. It does not change the file's contents and it does not help anyone else.

For everyone who downloads it: sign the executable. Only a certificate from a certificate authority removes the prompt at the source:

  • EV certificate: trusted from the first download.
  • OV certificate: the prompt fades as the file builds reputation.
  • Azure Trusted Signing: Microsoft's subscription signing service.

All of them verify your identity, so none is free. A self-signed or test certificate keeps the publisher unknown.

The repository ships no signing tool: releases are published unsigned. If you sign your own build with signtool.exe or another tool, the signature changes the file, so recalculate its SHA-256 and update the release.

Project layout

src/Pad8Lab.Core/           the flashing core, 100% C# (HID, protocols, tweaks, backup, patch, restore)
src/Pad8Lab.Core/Firmware/  flash layout, firmware catalogs, tweak blobs
src/Pad8Lab.Core/Hid/       Win32 HID discovery and transport
src/Pad8Lab.Core/Ops/       backup, probe, plan, patch and restore
src/Pad8Lab.Core/Profiles/  per-model profiles; only registered profiles appear in the app
src/Pad8Lab.Core/Protocol/  app and bootloader protocols
src/Pad8Lab/                the WPF desktop app (Setup and About tabs)
tests/Pad8Lab.Core.Tests/   unit tests for the parts that need no controller
tests/ParityCheck/          proves the C# builder matches the validated reference image
tests/HardwareCheck/        runs devices, backup and check from the console
docs/                       screenshots and architecture notes
.github/                    CI workflow, issue forms and the pull request template

Pad8Lab.Core uses Win32 HID calls directly, with no external packages. Read the architecture notes for how the layers fit together.

Adding another controller model

The core is built around ControllerProfile: model identity, flash layout, firmware targets, update protocol and tweak catalog. ProfileRegistry.Default is the only place that decides which models the app supports, and today it registers only the Ultimate 2C Wireless.

src/Pad8Lab.Core/Profiles/TemplateProfile.cs is a non-registered worked example with placeholder values. It is compiled but never shown in the GUI, so it cannot be selected by users. Read the profiles guide before adding a model.

Build and run

git clone https://github.com/JehuAlv/Pad8Lab
cd Pad8Lab

dotnet build src/Pad8Lab/Pad8Lab.csproj -c Release
dotnet run --project src/Pad8Lab/Pad8Lab.csproj

Run the tests

The unit tests cover the parts that need no hardware: the layout checks, the profile registry, the HID mode matching, the tweak table and the plan ranges. They run on every push in CI.

dotnet test tests/Pad8Lab.Core.Tests/Pad8Lab.Core.Tests.csproj -c Release

Run it headless

The same core is available from the command line, which is handy for checking a controller without the window:

dotnet run --project tests/HardwareCheck/HardwareCheck.csproj -- devices
dotnet run --project tests/HardwareCheck/HardwareCheck.csproj -- backup
dotnet run --project tests/HardwareCheck/HardwareCheck.csproj -- check
dotnet run --project tests/HardwareCheck/HardwareCheck.csproj -- restore-check

devices, check and restore-check never write; backup only reads the controller and saves the file.

Verify the port

The tweaks were ported from the original Python toolkit and validated byte for byte before release. Point the parity test at a full backup of a stock 1.09 controller:

dotnet run --project tests/ParityCheck/ParityCheck.csproj -c Release -- controller-*.bin

It rebuilds the firmware from the backup and checks the size, the SHA-256, the recognised tweaks and the stock hash. If you also pass an image produced by the original core, it compares every byte.

Contributing

Read CONTRIBUTING.md for the build, test and release commands, and docs/ARCHITECTURE.md for how the layers fit together. Security problems go through SECURITY.md, never a public issue. The project follows the Contributor Covenant.

Safety and disclaimer

  • Warranty: installing modified firmware probably voids the controller's warranty.
  • Reversible: the bootloader is never touched, so recovery is always possible over USB.
  • Tested on one unit: the tweaks were validated on one Ultimate 2C Wireless. Edge cases may exist.
  • Reported risk: making the motors run during an active Bluetooth link has been reported to hang the controller in one instance; the toolkit author ran both motors at full strength for 30 seconds without reproducing it. This is a behaviour risk, not a brick risk.
  • See DISCLAIMER.md for the full text and SAFEGUARDS.md for every check the app makes before writing.

Credits

This project stands on other people's work. See CREDITS.md for the full list.

  • Carlos Browne F. — carlosbrownef-source/8bitdo-ultimate-2c-toolkit (GPL-3.0-or-later): the U2C Firmware Toolkit, its flashing core, the bt_xbox and bt_rumble tweaks and all the reverse engineering behind them. The C# core in this repository is a port of that work.
  • jgus-org/8bitdo-2c-re-flake (MIT): reverse engineering of the update and bootloader protocols and the flash layout.
  • xpadneo, supercypok/ultimate2c-ring, Crazyawk/8bitdo-ultimate2c-macos-rumble, vomba/8bitdo-ultimate-2c-apple, MoridaDE/8bitdo-2c-battery-tray: descriptor and technique references.

License

GPL-3.0-or-later. See LICENSE.

Not affiliated with or endorsed by 8BitDo.


Keywords: 8BitDo Ultimate 2C Wireless, Bluetooth rumble, convert to XInput, Xbox controller on Windows 11, native XInput, gamepad rumble fix, HID, firmware tweak.

About

Pad8Lab - custom firmware for 8BitDo controllers. Flash controller profiles for Bluetooth rumble and native Xbox (XInput) support on Windows 11; the Ultimate 2C Wireless is supported today.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

12 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages