Issue with reconfiguring Keychron Q1 keyboard (ISO windows)

[Time2waste123]

Information

• None of the other issue templates apply

Description

Hi

I am attempting to reconfigure the Keychron Q1 keyboard (v1 or v2 not sure) with ISO layout for windows using QMK Toolbox - and after hours of troubleshooting I am at a loss.

I have tried to outline in detail below every step I have taken in the process - hope someone can help me figure it out. Please be detailed where possible, I am a novice :)

Thanks in advance!

---

GoaI: swap Delete and Insert keys

Step 1: Opened online QMK Configurator

Step 2: Selected keyboard (have tried with both v1 and v2 version of Q1 ISO keyboard)

Step 3: Swapped the insert and delete keys and downloaded .json. Have done this in both the windows and the Apple layers on the keyboard to be sure the change was made, my keyboard has 4 layers 2 for windows, and 2 for apple where second layer for each is the FN layer.

Step 4: have tried uploading the .json in QMK configurator to confirm the changes I made are registered and they are

Step 5: this is first sign something is not right, when using the “Test keys” function build into QMK configurator, the changes does not register, and Insert and delete are still in the wrong place despite the visual layout shows the keys are switched

Step 6: Press “Compile” button

Step 7: Press “Firmware” button (download of .bin)

Step 8: Have installed QMK toolbox

Step 9: Open QMK toolbox and upload bin file (fill in file location)

Step 10: Plug in keyboard while pressing Reset button to go to boot mode. QMK Toolbox writes in red font "Atmel DFU device has libusb0 driver assigned but should be WinUSB. Flashing may not succeed"

Step 11: Press Flash - QMK toolbox writes:
Dfu-programmer.exe atmega32u4 erase --force
Dfu programmer: no device present
Dfu-programmer.exe atmega32u4 erase --force "location of .bin file"
Dfu programmer: no device present
Dfu-programmer.exe atmega32u4 reset
Dfu programmer: no device present
Flash Complete

Step 12: The keyboard does not connect to laptop after flash, and I have to unplug and plug in again for keyboard to be recognized. The device goes back to looking the same in device manager as before and layout is still the original, no changes.

Step 13: I have tried to uninstall keyboard in Device Manager and install new ATmega32U4 drivers using QMK Driver Installer “install_connected_drivers.bat”, and repeated all above steps with no success.

[fauxpark]

Please don't post PDFs, just explain the issue here.

[lesshonor]

First off: If you bought a product from Keychron, customer support was included with that purchase price. You should absolutely reach out to them for instructions and assistance.

Even if you did not buy from Keychron you should still check their website for information such as the user manual. There are also Keychron-specific communities (Discord, subreddit...) which can provide more focused advice regarding their products. As an example: your keyboard may have come preconfigured for the VIA or Keychron Launcher remapping tools; should you flash firmware built with Configurator you will lose that functionality.

---

Based on the output from QMK Toolbox, you have a Q1v1. You cannot use firmware compiled for Q1v2 as it has entirely different hardware. When using Configurator, ensure you are compiling firmware for the correct keyboard.

Creating/saving a JSON file alone is not enough to change how your keyboard is programmed. You will need to compile the firmware and flash it.

Your attempt to flash the firmware via QMK Toolbox did not succeed, so nothing has been changed. You will need to replace the libusb0 driver with WinUSB before you can reprogram your keyboard. I am going to call out the final two sentences of that paragraph specifically:

Warning

Please ensure your keyboard is in bootloader mode and has libusb as the existing driver before attempting to use Zadig to replace the driver. If instead you see HidUsb you're not in bootloader mode and should not continue with driver replacement.

I would suggest joining Discord for realtime assistance with these kinds of questions.