WORKSPACE/Overview
Not connected
PLUG IN. EXPLORE. BUILD.

Your device. One zombie rig.

A clear view of your Flipper, with the tools you need close at hand.

CONNECTIONREADY WHEN YOU ARE

Let’s connect your Flipper.

Use a USB data cable. Keep the Wi-Fi board attached and close qFlipper before connecting.

You choose which USB port this hub can access.
SESSION AT A GLANCELOCAL
Detected interfaceWaiting for device
Supported commands—
Received data0 B
Current operationIdle

Connect first. Discovery reads the device’s help output.

GOT THE WI-FI BOARD?

Two interfaces. One hub.

Start with the Flipper console. For Wi-Fi analysis, switch to a compatible board through the USB/UART bridge.

EVERYDAY TOOLS

Start with the essentials

DEVICE TOOLKIT

A place for every task.

Controls unlock after the connected device advertises a matching command.

Storage inspector

List folders, inspect a path, or read a small text file on your Flipper.

Output appears in the session terminal. Use qFlipper for file transfer and backups.

WI-FI LAB

See your wireless environment.

Beacon discovery and retained device lists, powered by compatible Marauder firmware.

A stock Wi-Fi board is a debugger.

Scanning requires compatible firmware on the board. A USB connection to the Flipper alone does not establish a Marauder connection.

Wireless workflow

2.4 GHz · OFFICIAL S2 BOARD
  1. 01
    Connect & identify

    Open the USB/UART bridge on Flipper, select the board profile, and discover its commands.

  2. 02
    Listen for access points

    Start nearby access point discovery. Live output goes to the session terminal.

  3. 03
    Stop & review

    Stop the scan, display the access point list, then export your session.

For deeper workflows, use the advanced console with your installed firmware’s help. Output formats and available commands vary by firmware.

ADVANCED WORKSPACE

Work directly with your device.

Send individual serial commands, save shortcuts, and inspect the full response.

Command composer

NO DEVICE

Commands go to the selected serial device, not Windows. Use Up/Down in the command box for session history. Stop any active tool before starting another.

Your shortcuts

Available commands

Recognized from the last help response. The full firmware help remains in your terminal.

Connect and identify a device to populate this list.
Flipper CLI reference ↗Marauder CLI reference ↗
GET CONNECTED

The right cable. The right interface.

Start here if your Wi-Fi module’s firmware is unknown.

01

Start with your Flipper

  1. Open this hub directly in Microsoft Edge or Chrome on Windows 10/11.
  2. With Flipper powered off, seat the Wi-Fi board correctly on its GPIO pins. Power on the Flipper.
  3. Connect a USB data cable to the Flipper’s USB-C port. Close qFlipper and other serial terminals.
  4. Select Flipper Zero · USB console, then Connect USB device. Choose its COM port.
  5. Click Identify & discover tools. The console reads help and enables recognized tools.
02

Identify your Wi-Fi board

Reading the Flipper’s identity does not reveal the board’s firmware.

The official board normally comes with Black Magic / CMSIS-DAP debugging firmware. This does not provide Marauder Wi-Fi commands.

If you connect USB directly to a stock board, its ports may be a GDB debug interface and a UART log interface. Start with Unknown board · listen only; silent output does not prove which firmware is installed.

Official board documentation ↗Compatible firmware & hardware guide ↗

This hub does not flash or replace firmware. Use the exact board’s setup instructions before changing firmware.

03

Connect Marauder via Flipper

  1. Use a board with a Marauder build for that specific hardware.
  2. Disconnect this hub’s current session.
  3. On Flipper, open GPIO → USB-UART Bridge. Set UART to USART / channel 0 and baud to 115200. Menu names may vary.
  4. Keep the USB cable in the Flipper. Choose the USB CDC channel assigned to the bridge. If using an additional CDC interface, Windows may show a second COM port.
  5. Select Wi-Fi board · Marauder via UART, connect to the bridge port, then identify.

If you see the Flipper greeting instead of Marauder help, you selected its console port. Disconnect and select the bridge port. Exit the bridge on Flipper to return to normal CLI mode.

04

When a connection fails

No device in the picker

Try a known data cable, another USB port, and Device Manager → Ports. qFlipper can help diagnose Flipper USB drivers.

Access denied / port is busy

Quit qFlipper, Flipper Lab, IDE serial monitors and other hub tabs. Only one client can own a serial port at a time.

Connected, but no reply

Check the port, baud rate, bridge mode and board firmware. A stock debug endpoint is not a command console. Try listen-only mode without sending commands.

Tool is unavailable

Refresh discovery and inspect the complete help response. Different firmware versions expose different commands. A manual command can be entered in the advanced console.

I need screen mirroring or firmware updates

Use qFlipper or Flipper Lab for those functions. Disconnect this hub first. This version is a serial tools hub, not an RPC screen viewer or firmware installer.

qFlipper ↗Flipper Lab ↗
Session terminalNo active connection
Welcome to your workbench.
Connect a USB device to begin, or explore the clearly labeled demo.
ReadyRX 0 B · TX 0 B