Apex 5 Marauder WarDrive Not Working? You Probably Have Ver.1 (2026)
Partager
PINGEQUA Lab · Flipper Wardriving · 7 min read · Updated 2026-08-03
The Apex 5 sells two hardware versions on one product page — and only the version most buyers never notice they didn't pick supports Marauder's WarDrive mode out of the box.
Why your Apex 5 won't wardrive: Ver.1 vs Ver.2 (Marauder WarDrive support)
The Apex 5 is an ESP32-C5-based expansion module for the Flipper Zero from Honey Honey Team (Australia), combining dual-band 2.4/5 GHz Wi-Fi 6, two Sub-GHz radios (433/868 MHz), an nRF24 radio, and GPS on one board. (CNX Software, 2026-02-11)
What that CNX Software launch coverage doesn't tell you: the Apex 5 has shipped in two distinct versions under one listing. Per the maker's own GitHub README:
Batch 2 (branded "Ver.2" in the current listing) has been available since 2026-04-12, per the same README's changelog. But — and this is the part that trips buyers up — the maker never pulled Ver.1 from sale. Both versions are still offered side by side on the same Tindie product page, at the same rough price point (currently $79, down from the $99 launch price reported by CNX Software in February 2026). If you didn't specifically select Ver.2 at checkout, or you bought before April 2026, there's a real chance you're holding a Ver.1 unit that was never going to run WarDrive — no matter what firmware you flash.
How to tell which version you have — before you buy, and after
Before you buy: The Tindie listing includes a version selector (alongside case-colour options) where Ver.1 and Ver.2 are picked separately — read it, don't assume the "current" listing only sells the newest hardware. The maker also publishes a feature comparison chart referenced in the README; check it for the exact line items before adding to cart.
After you already own one: the fastest check is the Marauder app itself.
- Open the Marauder companion app on your Flipper. If there's no WarDrive menu entry at all, you have a Ver.1 unit.
- If you're feeding it GPS today, check whether it worked "out of the box" through the Marauder app, or whether you had to manually swap UART pin configuration to get a GPS lock. Per the maker's README, that manual UART step is a Ver.1-specific requirement — Ver.2 wires GPS through automatically.
What Ver.1 can and can't do (GPS via manual UART swap; no out-of-box WarDrive)
Ver.1 is not GPS-less — it physically includes a GPS module, same as Ver.2. The difference, per the maker's own documentation, is integration:
- Ver.1: GPS exists on the board, but using it requires manually reconfiguring the UART wiring/settings yourself. There is no WarDrive mode in the Marauder menu on Ver.1 units.
- Ver.2: GPS is wired through the Marauder app automatically — "no configuration changes" needed — and WarDrive mode is present in the menu.
That's a meaningful distinction for anyone diagnosing "my Apex 5 won't wardrive": it's not that GPS logging is impossible on Ver.1, it's that the maker never exposed the WarDrive workflow for that hardware revision, and getting raw GPS data working at all is a manual, undocumented-in-detail exercise rather than a menu option.
Scan vs attack: wardriving only needs passive dual-band scan + GPS
It's worth separating two very different capabilities that get lumped together on C5 boards: attack features (deauth, 5 GHz offense) and wardriving, which is just passive AP scanning tagged with GPS coordinates and uploaded to something like WiGLE. Wardriving never needs deauth or any active/attack capability — it needs a working scan loop and a GPS fix.
That distinction matters here because the Apex 5's underlying ESP32-C5 radio is fully capable of passive dual-band (2.4/5 GHz) scanning — the C5 chip natively supports 802.11ax on both bands without a dual-chip workaround. (CNX Software, 2026-02-11) Where 5 GHz gets shaky on C5-class boards in 2026 is on the attack side (deauth reliability), not passive scanning — see our dedicated breakdown for the details. (Can the Flipper Zero Wardrive on 5 GHz?)
So a Ver.1 Apex 5's missing WarDrive menu isn't a radio limitation — the hardware can scan dual-band fine. It's purely that the maker didn't ship the WarDrive workflow (menu, logging, GPS auto-wiring) on that revision.
Options that wardrive out of the box today (buy Ver.2; Flipper + GPS; pre-assembled Scout Lite)
If you want Flipper Zero wardriving working today, without chasing UART pinouts:
- Buy Ver.2 specifically — if you want to stay on the Apex 5 / Marauder-on-C5 path, double-check the version selector on the listing before checkout, per the section above.
- Flipper Zero + a separate GPS-capable Wi-Fi board — a general-purpose 2.4 GHz board like PINGEQUA's ESP32-S2 Devboard ($29.99) has no onboard GPS and isn't built for wardriving on its own; a dual-band board like 5Ghost (BW16, $39.99+) also ships without onboard GPS. Neither is the wrong product — they're built for scanning, capture, and Evil Portal work, not GPS-tagged logging.
- A pre-assembled, GPS-onboard unit — PINGEQUA's Scout Lite ($64.98) is built specifically for this: ESP32-C5, Wi-Fi 6 dual-band (2.4/5 GHz), an onboard L86 GPS, and pre-flashed ESP32 Marauder, ready to log to WiGLE without checking a version chart or touching a UART pin. It's the one board in the PINGEQUA lineup with onboard GPS — the ESP32-S2 Devboard and 5Ghost cover general Wi-Fi testing, Scout Lite covers wardriving.
Skip the version chart — Scout Lite just wardrives
Scout Lite is the one PINGEQUA board with onboard GPS — ESP32-C5 dual-band Wi-Fi 6 + onboard L86 GPS, pre-flashed with ESP32 Marauder, ready to log to WiGLE out of the box. $64.98.
Scout Lite for Flipper Zero →Already stuck with a Ver.1? Your paths forward
If you already bought an Apex 5 and it turns out to be a Ver.1:
- Attempt the manual GPS UART reconfiguration yourself if you're comfortable following the maker's documentation — this may get you a raw GPS fix, though it won't unlock the Ver.2 WarDrive menu itself, since that's a firmware/menu feature tied to the newer revision.
- Buy a Ver.2 unit separately if you want to stay within the Apex 5 ecosystem for its Sub-GHz and nRF24 features while adding proper WarDrive support.
- Add a dedicated wardriving device and keep your Apex 5 for what it already does well (Sub-GHz, nRF24, dual-band scanning) — Scout Lite is built for exactly this handoff, with no version to double-check. For the full head-to-head on price, GPS, and setup effort, see our Scout Lite vs Apex 5 comparison.
FAQ
Why won't Marauder WarDrive show up on my Apex 5?
How do I know if I have Apex 5 Ver.1 or Ver.2?
Does Apex 5 Ver.1 support wardriving at all?
When did Apex 5 Ver.2 come out?
Does the Apex 5 support 5 GHz wardriving?
What Flipper Zero wardriving device works out of the box without version confusion?
Related reading: For the full price, GPS, and setup trade-off, see our Scout Lite vs Apex 5 comparison, or if Marauder itself is misbehaving rather than a Ver.1/Ver.2 mismatch, check our ESP32 Marauder WarDrive troubleshooting guide. For where 5 GHz actually stands on C5-class hardware in 2026 — including why the ESP32-C5 single chip enables dual-band wardriving and a no-soldering, no-PC wardriving setup — see Can the Flipper Zero Wardrive on 5 GHz?
Sources & further reading: Apex 5 launch coverage — CNX Software (2026-02-11); hardware/version specs and WarDrive support — Honey Honey Team GitHub README; pricing and batch availability — Apex 5 Tindie listing (HoneyHoneyTrading). Verified August 2026.
For authorized security testing and education only. Test only devices and networks you own or have explicit written permission to test. You are responsible for compliance with local law and radio regulations. "Flipper Zero", "ESP32 Marauder", "Apex 5" and other names are referenced for compatibility; PINGEQUA is independent and not affiliated with or endorsed by their owners.