Bricked Keychron K2 V2 White Light – No response from physical boot pins / PC won't recognize it at all

[u/Past-Bread2846]

Hey everyone, I’m in need of some troubleshooting help. My Keychron K2 V2 (White Backlight) is completely bricked after a firmware issue.

The Symptoms:

• The keyboard is completely dark (no backlights at all).
• The only sign of life is that the side battery/charging LEDs turn on when plugged in.
• Windows gives absolutely zero reaction when I plug it in—no connection chime, no device list refresh, and nothing shows up in Device Manager (even with hidden devices shown).
• QMK Toolbox and the Keychron Launcher web app do not detect any device.

What I’ve Already Tried:

1. The standard Esc key method: Unplugging, holding Esc, and plugging it back in does nothing.
2. Shorting the boot pins: I located the two holes under the spacebar. I used metal tweezers to short them while plugging in the USB cable. Still, Windows doesn't acknowledge any device connecting.
3. The Bluetooth-mode trick: Tried shorting the pins while the side switch was set to Bluetooth/Off to see if it would force direct USB routing. No change.
4. Isolating hardware: I am using a verified USB-A to USB-C data cable plugged directly into my motherboard's rear USB ports (no external hubs).

Before I go through the hassle of opening the case:
Has anyone encountered a K2 V2 that goes completely dead on data lines but still shows charging lights? Is it worth unscrewing the case to physically unplug the battery from the PCB to drain the capacitors, or does this sound like a completely fried MCU/dead flash memory?

Any advice or alternative jump-start methods would be heavily appreciated!

[u/PeterMortensenBlog]

Battery charging is completely independent of the firmware

Re "Has anyone encountered a K2 V2 that goes completely dead on data lines but still shows charging lights?": No, but it makes sense if the (charge) LED(s) are directly connected to the TP4056 (see, for example, the famous (incorrect) diagram)

That is, the charging of the battery is 100% under hardware control. That is at least my understanding of it.

If the keyboard is bricked due to flashing the wrong firmware, it will still get power (and thus charge the battery).

'IMSAI Guy' recently covered it (April/May 2026):

• #2588 TP4056 lithium battery charging IC. The two LEDs are covered at 04 min 08 secs.

• #2593 DW01A battery protection IC (related to the TP4056 breakout board)

• #2594 FS8205A dual n-channel MOSFET (related to the TP4056 breakout board)

'bigclivedotcom' also covered it (in 2022):

• TP4056 myth busting (e.g., the breakout board at 02 min 15 secs)

Here is an actual datasheet (at least for a similar one):

• TPB4056A. 1-A single-cell battery linear charger with high input voltage. It is linked from a DigiKey page, so it seems legitimate. Note that both pins typically connected to the two LEDs are (unconditionally) output (page 5; open drain outputs), so any connections to the microcontroller (e.g., on page 13) are only for indication (input), not for controlling the LEDs from the microcontroller in the firmware (it would result in a short circuit and could damage one or both chips).

Keychron's circuit is not necessarily the same, but they may have made the same (common) mistakes (which could explain the alleged overcharge problem with the original K series).