Troubleshooting

Find your symptom below and work through the list from the top.

🔌 Computer doesn't see the keyboard

1. Try another cable — many USB cables are charge-only.
2. Try another port, ideally directly on the computer rather than through a dock.
3. Wireless: check the power switch and battery, and switch to the right Bluetooth profile.

🧰 Remapping tool won't connect

Still nothing? The firmware may not support that tool — see the Remapping overview for alternatives.

⌨️ Some keys don't work

1. Use Vial's Matrix tester or an online key tester to tell a hardware problem from a keymap problem.
2. One dead key: on hot-swap boards the switch may be loose or have a bent pin — pull it and check.
3. A whole row or column dead: likely a solder joint or controller issue — contact the maker.
4. Check you're not stuck on another layer: unplug and replug to return to layer 0.

⇆ One split half doesn't respond

🔀 Wrong keys / changes don't apply

• Edited the wrong layer: check which layer you changed in the tool.
• Stuck on a layer: TG / TO without a way back — replug to return to layer 0, then add a return key on that layer.
• ZMK: after editing in Studio, flashed .keymap changes don't apply until you Restore Stock Settings in Studio.
• RMK: still the old keymap after flashing a new default — see clear_layout in Edit keyboard.toml.
• QMK / VIA: to wipe the keymap stored in EEPROM, press a QK_CLEAR_EEPROM (EE_CLR) key, or re-import your backup after flashing.

🔥 Flashing failed

• No USB drive / Toolbox sees nothing: the keyboard isn't in bootloader mode. Try another method (double-tap reset, hold BOOT while plugging in) — see Flash firmware.
• GitHub Actions build failed: open the failed run to read the error — usually a config syntax mistake; revert the last change.
• Keyboard dead after flashing: probably the wrong file (model, controller or side). Re-enter the bootloader and flash the right one.

→ Contact us