Step 01
Confirm Bluetooth mode and enter pairing mode deliberately.
Keychron’s current V Max troubleshooting directs users to select Bluetooth mode and hold Fn + 1/2/3 for about 4–6 seconds. Use one profile at a time. The host should discover the device as Keychron V6 Max.
Step 02
Delete the stale host record and pair again.
If the keyboard was previously paired, remove the old Keychron entry from Windows, macOS, Linux, iOS, or Android, toggle Bluetooth off and back on, and start a fresh pairing sequence. This changes the host state without modifying keyboard firmware.
Step 03
Test another profile and another host.
Try profile 2 or 3, then try a phone or second computer. If the keyboard pairs elsewhere, the keyboard’s Bluetooth radio is functioning and the first host becomes the main suspect. If no profile pairs with any host, continue with battery/reset/support steps.
Step 04
Charge the keyboard and power-cycle it.
Keychron’s V6 Max specification lists a 4000 mAh rechargeable battery. Charge it with a normal supported USB source, then switch the keyboard off and back to Bluetooth mode. Do not interpret a lit RGB backlight as proof that the battery state is adequate for stable wireless operation.
Step 05
Use Keychron’s exact V6 Max reset/firmware path only if pairing still fails.
Keychron maintains separate keyboard, Bluetooth, and receiver firmware. Match the firmware to the exact V6 Max layout/version. Keychron’s Bluetooth firmware page explicitly warns not to flash a working keyboard because the process can damage it. If you reach this step, follow the current V6 Max user guide or Keychron support rather than a firmware file copied from another model.
Decision
Do you need a replacement keyboard?
If another profile or host works, solve the pairing/host Bluetooth issue.
If Bluetooth fails but 2.4 GHz and wired modes work, collect firmware versions and contact Keychron before replacing the board.
If the keyboard cannot pair to multiple known-good hosts after Keychron’s documented reset/support procedure, a radio or board fault becomes more plausible.
Sources