flipper-zero

Flipper Zero — multi-protocol handheld for sub-GHz, NFC, RFID, infrared and iButton

Vendor: Flipper Devices

Status: supported — the identifiers and setup recipe are believed correct.

Not maintainer-verified: nobody on this project has run this hardware yet. The two facts are recorded separately on purpose (D-027) — a correct recipe and a tested device are different claims.

What it is

A handheld multi-tool for short-range wireless protocols: sub-GHz radio, 125 kHz RFID, 13.56 MHz NFC, infrared, iButton and GPIO, with a screen and its own firmware.

What you can do with it

Read, store and replay the short-range protocols above, and use it as a general-purpose hardware interface over GPIO. Like the Marauder firmware, some of what its firmware can do transmits rather than listens; that is a property of firmware supplied by upstream and running on the device. Operating those features against systems you do not own or are not authorised to test is a separate matter from installing a flashing tool.

Setup

Join dialout and plugdev, then log out and back in — group membership does not apply to an existing session. Attach the device; it appears as /dev/ttyACM0 (this entry emits no symlink — see the NO SYMLINK note). qFlipper is the normal desktop route and is packaged on all four targets (qflipper 1.3.3, 2026-08-28); dfu-util covers firmware recovery from DFU.

Known problems

Its DFU mode presents the generic STM32 bootloader identifier, so a rule matching it would also match unrelated STM32 boards — see the identification gap above. ModemManager grabs the serial port for around twenty seconds on many desktops, which looks exactly like a dead device; qFlipper's shipped udev rule tags it with ENV{ID_MM_DEVICE_IGNORE}="1" so ModemManager leaves it alone.

How it identifies itself

USB id	What	Confirmed	Node
0483:5740	Flipper Zero — normal mode, presenting a USB serial port	yes	serial
0483:5741	Flipper Zero — U2F security-key mode	yes	hid

⚠ 0483:5740 is not unique to this device (generic_function_name; also used by: STM32 projects shipping the reference USB CDC descriptors). usb.ids names 0483:5740 "Virtual COM Port" -- a function, not a product. It is STMicroelectronics' reference VCP identifier and is reused by a wide range of STM32-based projects that never changed it. Confirmed as the Flipper's serial mode by qflipper's own rule; not confirmed as belonging to the Flipper alone, which is a different claim.

⚠ 0483:5741 is not unique to this device (generic_function_name; also used by: ). Adjacent to 0483:5740 in STMicroelectronics' range and named by no product string in usb.ids. Treated as ambiguous on the same basis as its neighbour rather than assumed unique because it happens to be less widely documented -- absence of evidence about reuse is not evidence of uniqueness.

What is not yet known

One identifier from Debian's rule is deliberately NOT carried above: 0483:df11, the device's DFU mode. It is STMicroelectronics' generic STM32 bootloader identifier, shared by every STM32 board in DFU — including, as the same sweep found, the TYT MD-UV380 radio in dmrconfig's rule. A udev symlink on it would name an unrelated device /dev/flipper. The normal and U2F identifiers are carried, and they are ambiguous too: 0483:5740 is usb.ids' "Virtual COM Port", ST's reference identifier, reused by a wide range of STM32 projects that never changed it. So this entry emits no symlink at all. What would fix that is one ATTRS{product} string, which the device almost certainly supplies and nobody here has read -- run scripts/identify-device.sh flipper-zero and it turns three ambiguous identifiers into one safe rule.

Who can close it: nobody on this project owns one — an operator who does can close it with one lsusb (how).

Access and permissions

Group membership required: dialout, plugdev — added at install, applies at next login.

Firmware modes

• dfu — tooling: dfu-util qFlipper is the normal route and handles the mode switch itself. dfu-util is the recovery path when the device will not boot far enough for qFlipper to reach it. Firmware comes from upstream; nothing here builds or supplies it.

Software that makes it useful

dfu-util, qflipper

Upstream: https://flipperzero.one/