Scout Lite ESP32-C5 Marauder wardrive board for Flipper Zero troubleshooting

ESP32 Marauder Wardrive Not Working? 8 Fixes (GPS, SD, Memory, Crash) 2026

PINGEQUA Lab · ESP32 Marauder troubleshooting · 8 min read · Updated 2026-08-03

ESP32 Marauder wardrive not working can mean four completely different things: the app won't start, GPS never gets a fix, the SD card stays empty, or the whole board crashes mid-scan. This is a diagnostic hub — find your symptom below, then jump to the deeper fix if one exists.

Quick answer First figure out which stage fails: app won't start (check GPS baudrate on ESP32-C5, issue #1268), GPS won't fix (needs open sky, ~30s-2min cold start), SD stays empty (needs ≤32GB FAT32), or it crashes (known memory/white-screen bugs in v1.10.1–1.14.x). Match your symptom to a fix below.

8 Fixes for ESP32 Marauder Wardrive Problems

Fix #1: Wardrive Won't Start / ESP32-C5 "Scanning Does Not Start"

On ESP32-C5 hardware, the wardrive app can fail to launch entirely, with boot logs showing Could not detect GPS baudrate followed by GPS Not Found — documented in issue #1268 (2026-05-07, firmware 1.12.1). This is a chain failure, not a cosmetic warning: the C5 build of wardrive waits for a valid GPS baudrate handshake before it will start scanning at all, so a GPS module that never responds blocks the entire app, not just location logging.

Confirm the GPS module has power and a clear connection, then power-cycle outdoors under open sky and give it up to two minutes to complete a cold start before assuming the sensor is dead. If baudrate detection keeps failing across repeated power cycles, that points to a wiring or module fault rather than a Marauder software bug — fix #2 below covers narrowing that down.

Fix #2: GPS Not Found or No GPS Fix

A GPS module that's detected but never returns a location fix — and sometimes stops being detected at all after a soft reset — is one of the longest-running wardrive complaints on record (issue #338, 2023-09-21; the reporter's own words were "Very confusing lol"). Outdoors with open sky, a cold start typically takes 30 seconds to 2 minutes per Marauder's official wardrive wiki; indoors or under any cover, it will not fix at all, which is often mistaken for a hardware failure.

We cover the full GPS fix troubleshooting flow — antenna orientation, cold-start timing, wiring checks — separately: GPS detected but no fix →

Fix #3: No Records Written to SD Card

If GPS has a fix and scanning is clearly running but the log file stays empty or zero bytes, check the card before touching any firmware setting. Marauder's official FAQ requires SD cards ≤32GB, formatted FAT32 — exFAT or cards over 32GB will mount without error but silently fail to log. SD initialization and mount failures unrelated to card size are also tracked separately in issues #227 and #95.

We keep a running list of cards confirmed to work for wardriving in a dedicated guide: Best microSD card for ESP32 Marauder wardriving →

Fix #4: "Deauth Does Nothing" — It's Probably Working

The most common false negative in Marauder troubleshooting isn't a bug — it's the read-out. A deauthed client typically auto-reconnects within seconds, so checking a router's connected-device list a minute later shows the target back online and looks like the attack failed. Flipper forum staff (user jmr) confirmed in June 2023 that a deauth attack can succeed even when the device reappears in the AP's client list shortly after, because most clients reconnect automatically and immediately.

To actually confirm a deauth frame was sent, you need a separate monitor-mode capture device watching for deauth/disassoc frames in the air — the router's admin page cannot tell you this. That said, not every "does nothing" report is a false negative: some ESP32-C5 DevKit units have logged genuine deauth failures on firmware 1.11.1 (issue #1216), so a monitor-mode check is also how you rule that in or out. This article does not cover how to run deauth attacks — only how to verify one landed, for authorized testing on your own equipment.

Fix #5: Memory Hits 95% Mid-Scan

On v7 hardware running firmware 1.10.1, users reported wardrive's memory usage climbing to roughly 95% before a single access point had even been logged (issue #1087, 2026-01-28). At that level the app becomes unstable and can freeze or silently drop scans. No user-side fix is documented in the issue beyond restarting the scan and keeping sessions short — treat repeated 95%+ spikes on that firmware version as a known leak rather than something to chase in your own GPS or SD setup.

Fix #6: White-Screen Freeze After Exiting Wardrive

A separate crash pattern shows up specifically after exiting wardrive, not during scanning: the screen goes white and locks up. Issue #1343 (2026-06-30) traces this to accumulated log volume — testers reproduced it consistently around 20 files / 15.7MB of wardrive logs already sitting on the SD card. If you're hitting this, clearing old wardrive log files off the card before starting a new session is the only workaround reported so far.

Fix #7: Upload to WiGLE Fails

Marauder v1.14.0 (2026-07-22) added the first direct-from-device upload path to WiGLE and WDGWars, along with direct-upload support on the ESP32-C5 DevKit. In practice, issue #1409 (2026-07-30) shows v7 hardware on 1.14.0 throwing "could not connect" / "upload failed" errors, and in some cases the device reboots mid-upload. If direct upload keeps failing, the reliable fallback is pulling the log file off the SD card and uploading it through WiGLE's own web uploader instead of the on-device path.

Full steps for both paths: Upload wardrive data to WiGLE from Flipper Zero →

Fix #8: Firmware Version Mismatch

Marauder v1.14.0 (2026-07-22) and v1.14.1 (2026-08-01, installer-manifest update only, no functional changes) are the current releases. Before assuming your symptom matches a forum thread or this guide, confirm which build you're actually running from the Marauder menu — the GPS baudrate stall in fix #1 was logged on 1.12.1, while the no-fix report in fix #2 predates it by nearly two years. GPS-related complaints span multiple firmware generations, not one bad release, so check version-specific GitHub issues before filing a new bug or reflashing.

An honest 2026 note: Most of what's above is a Marauder firmware bug, not a defect specific to one board. GPS baudrate stalls, memory spikes, white-screen freezes, and WiGLE upload failures are all logged against Marauder itself, and they can show up on any hardware running the same firmware — including our own Scout Lite, which ships with stock ESP32 Marauder. Hardware can only remove failure sources that live in the wiring: a hardwired GPS module removes pin-mapping and loose-jumper failures, and a spec-correct onboard SD slot removes card-compatibility failures. It cannot patch a firmware-level memory leak or a WiGLE upload bug — those only get fixed upstream, in a Marauder release, on any board.

Cut Two Failure Sources Before You Even Open the App

Scout Lite hardwires a Quectel L86-M33 GPS and a board-level microSD to Flipper Zero's GPIO — no jumper wires to loosen, no SD compatibility guesswork, and it ships preloaded with ESP32 Marauder so wardriving works out of the box. The firmware-layer bugs above still apply; the wiring-layer ones don't.

Get the Scout Lite →
Read the setup guide →

FAQ

Why is my ESP32 Marauder wardrive not working?
The most common causes are GPS baudrate detection failing on ESP32-C5 boot (issue #1268), a GPS module that's detected but never gets a location fix (issue #338), or firmware bugs like the v1.10.1 memory spike to 95% (issue #1087). Confirm which stage fails first — app won't start, GPS won't fix, or SD won't log — then match it to the specific fix above.
Why is my Marauder wardrive not saving records to the SD card?
Check the card format first: Marauder requires ≤32GB and FAT32 per the official FAQ — exFAT or cards over 32GB will mount but fail to log silently. SD init/mount failures are also tracked in issues #227 and #95. If the card checks out, the white-screen freeze in issue #1343 (tied to roughly 20 files/15.7MB of accumulated logs) can also interrupt writes.
Is my deauth actually working if nothing seems to happen?
Probably yes. Clients typically auto-reconnect within seconds, so a router's device list showing the target back online minutes later doesn't mean the attack failed — Flipper forum staff confirmed this in 2023. Verifying a deauth actually landed requires a separate monitor-mode device watching for the deauth frames in the air, not the AP's admin dashboard.
Does the Scout Lite fix these ESP32 Marauder wardrive bugs?
Partially. Scout Lite's hardwired GPS and onboard microSD eliminate wiring and card-compatibility failure points, but it runs the same ESP32 Marauder firmware as any other board, so firmware-layer bugs — GPS baudrate stalls, memory spikes, white-screen freezes, WiGLE upload errors — can still occur and get fixed the same way: through upstream Marauder firmware updates.

Sources & further reading (verified 2026-08-03): Issue #1268 — C5 scanning does not start, Issue #338 — GPS detected but no fix, Issue #1216 — C5 DevKit deauth not working, Marauder official FAQ (SD card requirements), Issue #227 and Issue #95 — SD mount failures, Flipper forum — "Marauder don't do anything" (staff reply, 2023-06), Marauder wardrive wiki, Issue #1087 — memory hits 95%, Issue #1343 — white-screen freeze, Issue #1409 — WiGLE upload fails, Marauder v1.14.0 release notes, Marauder v1.14.1 release notes.

For authorized security testing and education only. Test only networks and devices you own or have explicit written permission to test. You are responsible for compliance with all applicable laws and radio regulations (e.g. FCC Part 15 in the US). "Flipper Zero" and "ESP32 Marauder" are referenced for compatibility and comparison; PINGEQUA is independent and not affiliated with or endorsed by their respective owners.

Back to blog