Install SigRoam Wardriving on your Flipper Zero
Install the SigRoam Wardriving app onto your Flipper Zero from this page, over the Flipper's own RPC protocol. No qFlipper and no SD-card removal. The Flipper has no Wi-Fi radio. This app is the control head: Dashboard, Probe firmware, Upload, Rank, Raw log, Settings and About. Scanning, GNSS and the WiGLE CSV stay on the attached board.
The version in the installer is the current SigRoam Wardriving release. You need Chrome, Edge or Firefox 151+ on a desktop computer and a USB-C data cable.
This is an early release, not a product-v1.0 field-readiness claim. SigRoam does not provide deauthentication or handshake capture. Survey capture is passive. WiGLE upload uses an ordinary Wi-Fi connection after scanning stops, so a receive-only survey does not mean the board never transmits.
What this release supports
| Scanner on the GPIO header | What you get |
|---|---|
| Scout Lite running SigRoam scanner firmware v0.6 | Passive 2.4 GHz and 5 GHz, BLE, GNSS, a sealed WiGLE CSV on the Scout Lite microSD, and an upload attempt after you stop |
| Scout Lite running factory ESP32 Marauder | This dashboard over Marauder's serial protocol. Marauder writes its own CSV and uses its own upload. SigRoam's sealed-session upload does not apply |
| Other boards that speak Marauder serial on Flipper pins 13 and 14 | The app may connect. Those boards have not all been bench-tested here |
Scout Lite is the verified reference board for the SigRoam scanner firmware. GNSS and a microSD card are required for a located WiGLE CSV. An ESP32-C5 covers 2.4 GHz and 5 GHz with one radio, not two radios at once.
v0.6.1 adds one fix on top of the v0.6 app: on battery, opening SigRoam turns on pin 1's 5 V so the scanner powers up. USB power is unchanged.
Flash the scanner from the Scout Lite page. Do not flash this .fap onto the ESP32.
Which Flipper firmware is compatible?
| Flipper firmware | This release |
|---|---|
| Official, and Momentum that reports API 87 | Supported. This page installs sigroam-0.6.1.fap from the current release, an Official SDK API-87 build, as /ext/apps/GPIO/sigroam.fap |
| Unleashed (API 88) | Not in this release. There is no Unleashed file. If the loader says the API does not match, do not continue |
v0.6 shipped a separate sigroam-0.6-unleashed.fap. v0.6.1 does not. If sigroam-0.6.fap or sigroam-0.6-unleashed.fap is still in Apps → GPIO, delete it so the menu does not show two copies.
After install, set Settings → System → Log Device to Off. The system log otherwise occupies serial pins 13 and 14. Open Apps → GPIO → SigRoam Wardriving.
How does browser app-installation work?
Connect the Flipper over USB and click Connect. The page opens an RPC session, reads your firmware version, then writes sigroam.fap to /ext/apps/GPIO/ on the SD card. Your Flipper Zero firmware is not changed.
Which browsers can talk to a Flipper Zero?
| Browser | Supported |
|---|---|
| Chrome / Edge (desktop) | ✅ Yes |
| Chrome (Android) | ✅ Yes |
| Firefox 151+ (desktop) | ✅ Yes — first use adds a permission add-on |
| Safari (macOS / iOS) | ❌ No |
| Firefox (Android) | ❌ No |
Browser access uses the Web Serial API. Safari and every browser on iOS are out; see Web Serial is not supported.
Troubleshooting
| Symptom | Fix |
|---|---|
| No Flipper in the port picker | Follow No serial port detected, then pick the STMicroelectronics Virtual COM Port. |
| "RPC session" stalls or times out | Close qFlipper, the Flipper mobile app, and lab.flipper.net; see Failed to open serial port. |
| App installs but won't open | The file is built for API 87. Unleashed (API 88) will refuse it. Do not bypass the mismatch warning. |
| Two SigRoam entries in the menu | Delete older sigroam-0.6.fap or sigroam-0.6-unleashed.fap files from the SD card's apps/GPIO folder. This page writes sigroam.fap. |
| Connect fails immediately | Unplug and replug the cable, then reload the page. On Linux you may need permission for the serial device (dialout group). |
About this installer
This page installs an application onto a Flipper Zero you own, using the device's documented Protobuf RPC protocol over Web Serial. No firmware is modified. SigRoam Wardriving is GPL-3.0 — see the sigroam-wardriving repository.
Frequently asked questions
What does SigRoam Wardriving do?
It is the Flipper control head for a survey. The menu is Dashboard, Probe firmware, Upload, Rank, Raw log, Settings and About. The attached board scans, receives GNSS and stores the WiGLE CSV. The Flipper has no Wi-Fi radio. This is an early release, not a product-v1.0 claim.
Which scanner firmware does it support?
On a Scout Lite running SigRoam scanner firmware v0.6, you get passive 2.4/5 GHz, BLE, GNSS, a sealed CSV on the Scout card, and an upload attempt after you stop. Factory Marauder on the same board uses this app as a dashboard only; its CSV and upload stay on Marauder's own workflow. Other Marauder-serial boards on Flipper pins 13/14 are not all bench-tested.
Which Flipper firmware can load it?
The current release is an Official SDK build, API 87, for Official firmware and compatible Momentum. Unleashed is API 88 and is not in this release. If the loader warns that the API does not match, do not continue. Delete any older sigroam-0.6.fap or sigroam-0.6-unleashed.fap left in Apps → GPIO so two copies do not both appear.
Does it change my Flipper firmware?
No. It writes /ext/apps/GPIO/sigroam.fap on the SD card over the Flipper RPC protocol. Open it from Apps → GPIO → SigRoam Wardriving. Set Settings → System → Log Device to Off so the system log does not occupy pins 13/14.
Which browsers can install it?
Chrome or Edge on desktop, Chrome on Android, or Firefox 151+ on desktop. It uses the Web Serial API; in Firefox the first connection also adds a permission add-on. Safari and every browser on iOS cannot flash.
WARNING
For educational and lawful use only. Comply with all applicable laws in your jurisdiction.