Get started
One known way to put open firmware or software on this device, easiest first. Each one links to the project's own instructions.
Before you start- Back up your data and settings (and the stock firmware, when the guide says how).
- Check the exact model, hardware revision and firmware version against the guide: a close model may not work.
- Charge the battery or use a stable power supply; do not unplug during the install.
Install QMK over USB (bootloader unlock)
MediumNeeds a cable or the command line · QMK
- You need
- Computer with QMK Toolbox (or the qmk command line), USB cable
- Device opened
- No
- Brick risk
- Low
- Reversible
- Partly
Put the keyboard in bootloader mode (reset button or key combination, see its README), then flash a QMK build. Many of these keyboards ship with QMK already; a different original firmware may not be restorable.
No install report yet. · Report how it went
OpenDeviceDB links to each project's own instructions and tools; nothing is flashed from this site. Flashing is at your own risk and may void the warranty.
- ID
- hhkb/jp
- Category
- peripheral
- Vendor support
- Unknown
- usb
- 4848:0002
- chips
- atmega32u4
- Updated
- 2026-10-25
Being worked on
No live claim. If you start working on this device, claim it so nobody duplicates your work.
Interfaces
No interface documented yet.
Projects
| Project | Kind | Origin | License | Freedom |
|---|
| QMK hhkb/jp | firmware | community | GPL-2.0-or-later | Still non-free: bootloader · Cloud: noneQMK is free; the USB bootloader it is flashed through (atmel-dfu) is closed and stays. |
What "still non-free" and "cloud" mean
What stays proprietary or depends on the vendor's cloud once the project is in use, from the project's own documentation.
- vendor blobs
- proprietary files extracted from the stock firmware
- stock firmware
- the stock firmware stays on the device; the project only talks to it
- modem
- cellular modem firmware
- GPU
- graphics driver or firmware
- Wi-Fi
- Wi-Fi driver or firmware
- Bluetooth
- Bluetooth firmware
- camera
- camera driver or image processing
- sensors
- sensor hub or sensor drivers
- bootloader
- boot firmware
- other
- another proprietary part
- Cloud: none
- works fully locally
- Cloud: only at setup
- a vendor account is needed once, e.g. to obtain a local key
- Cloud: optional
- cloud features exist but are not needed
- Cloud: required
- does not work without the vendor's cloud
- Cloud: unknown
- not known
Verification
Not verified. A "verified on hardware" badge requires a replayable test (hardware-replay) run on a real device with a stated firmware version.
Provenance
AI assistance not stated.
Status and claims as of the build date (2026-10-25). Data licensed CC BY-SA 4.0; imported data keeps its upstream license.