Your ELRS receiver is stuck on 2.x firmware while your transmitter module runs 3.5.1 — and now they won’t bind. The binding phrase is correct, the model match is off, and you’ve been staring at a solid red LED for 20 minutes. ExpressLRS 3.x introduced a major protocol change that breaks backward compatibility with 2.x. Here’s how to flash everything to 3.x, including the Backpack, without bricking anything.
The ELRS Protocol Break: Why 3.x Won’t Talk to 2.x
ExpressLRS 3.0 introduced FLRC modulation for faster telemetry and dynamic power improvements, but the packet format changed at the RF level. A 2.x receiver literally cannot decode 3.x packets — not just a config issue. Every device in your chain (TX module, RX, Backpack) must be on the same major version.
The April 2026 stable release (3.5.x) adds Gemini X dual-band support, native Backpack VTX control, and improved 900MHz LORA performance. If you’re still on 2.x, you’re leaving significant range and reliability on the table.
Step-by-Step: Flashing ELRS 3.x to All Devices
Step 1: Identify Your Hardware Target
Before downloading any firmware, know your exact hardware:
- **TX module:** Radiomaster Ranger, Happymodel ES24TX, Namimno Flash, BetaFPV Micro/Nano — check the label on the module
- **RX:** EP1/EP2, RP1/RP2/RP3, ER series, PP — printed on the board silkscreen
- **Backpack:** Built into many TX modules since 2023 — if your module has a USB-C port and a secondary antenna, it has a Backpack
Use the ELRS Configurator — the web-based tool auto-detects targets when you connect via WiFi.
Step 2: Flash the TX Module via WiFi
- Power on your radio with the ELRS module inserted
- Wait 60 seconds — if the module doesn’t connect to a receiver, it enters WiFi AP mode (LED flashes rapidly)
- Connect your phone/laptop to the “ExpressLRS TX” WiFi network (password: “expresslrs”)
- Browse to `http://10.0.0.1`
- Under “Update Firmware,” select the latest 3.x build for your target
- Click “Flash” — the page refreshes within 30 seconds when done
Critical: After flashing, the module may take 45-60 seconds to reboot. The LED goes solid for several seconds, then enters WiFi mode again. Wait. Don’t power-cycle mid-boot — that’s how you corrupt the bootloader.
Step 3: Flash the Receiver via WiFi
- Power the receiver (plug in a USB or a battery to your quad)
- Wait 60 seconds for WiFi AP mode
- Connect to “ExpressLRS RX” WiFi
- Browse to `http://10.0.0.1`
- Flash the matching 3.x firmware (same major version as the TX module)
- After flash completes, the RX reboots automatically
Receiver recovery — if WiFi mode doesn’t activate: Power-cycle the RX three times rapidly (on-off-on-off-on, each cycle under 2 seconds). The LED goes into a double-flash pattern indicating forced WiFi mode.
Step 4: Flash the Backpack
The Backpack streams VRx data (RSSI, LQ, mode) to your goggles OSD and enables wireless VTX control. Flashing it is the step most pilots skip — then wonder why their OSD shows no data.
- Connect the TX module via USB-C to your computer
- In ELRS Configurator, select “Backpack” as the device type
- Choose the matching target (usually auto-detected via USB)
- Select UART or USB flashing depending on your module
- Flash and verify — the Backpack LED blinks green when operational
Parameter Comparison: ELRS 2.x vs 3.x
| Feature | ELRS 2.x | ELRS 3.x (3.5+) |
|---|---|---|
| ——— | ——— | —————– |
| Packet rate | 500Hz max | 1000Hz (FLRC mode) |
| Telemetry ratio | Fixed | Dynamic (Std/1:128) |
| Model match | Basic ID | Cryptographic model match |
| Backpack protocol | VRx only | VRx + VTX control + fan control |
| Dynamic power | Basic LQ-based | AI-adaptive (learns from environment) |
| Binding phrase | Plain text | Hashed (stored in config only) |
| Gemini X support | No | Yes (2.4GHz + 900MHz dual-band) |
| WiFi flash file size | ~400KB | ~600KB |
| OTA update from TX | Manual | Auto-prompt on version mismatch |
| Regulatory domains | FCC/EU | FCC/EU/ISM (auto-detect) |
What Most Pilots Get Wrong
Mistake 1: Flashing the TX module but not the RX.
The #1 support request on the ELRS Discord: “Flashed my TX to 3.5, now nothing binds.” You must flash both TX module and every receiver to the same major version. An RP1 on 2.5.2 will never bind to a Ranger on 3.5.1.
Mistake 2: Skipping the Backpack flash.
Without updating the Backpack to 3.x, your goggles show “NO DATA” instead of LQ and RSSI. The Backpack uses a separate firmware binary that must stay in sync with the TX module version. If the TX module is on 3.5.1 and the Backpack is on 2.x, they communicate in different languages.
Mistake 3: Using the wrong flashing method for the hardware.
New ELRS receivers (RP4TD, ER8, PP) use EdgeTX passthrough via the flight controller USB port — NOT WiFi. Plugging in a battery won’t enter WiFi mode on these units. Follow the target-specific flashing docs at expresslrs.org or you’ll spend an hour wondering why the WiFi network never appears.
Mistake 4: Reusing a binding phrase from 2.x without re-entering it.
After flashing to 3.x, the binding phrase storage format changed. Your old phrase “MyDrone123” won’t survive the flash. Re-enter it in the Web UI before rebooting, or you’ll be bound to nothing and think the flash failed.
Mistake 5: Powering the RX from a USB port that can’t supply enough current.
Some USB ports (especially on laptops in power-save mode) drop to 100mA output. An ELRS RX in WiFi mode draws 300-400mA. If the WiFi network appears for 3 seconds and disappears, the USB port is browning out. Use a powered USB hub or plug the RX into the flight controller and power with a LiPo.
⚠️ **Regulatory Notice:** The flight recommendations in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. Always verify local laws regarding flight altitude, no-fly zones, remote ID requirements, and registration before flying. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities. ELRS dynamic power levels and frequency bands are regulated — ensure your module is set to the correct regulatory domain (FCC, EU_CE_2400, etc.) for your region.
As we detailed in our ExpressLRS Gemini X setup guide, the 3.5.x firmware is required for dual-band Gemini X operation. Flashing to 3.5 unlocks simultaneous 2.4GHz and 900MHz links for redundancy that no single-band system can match.
If you run into trouble with the flight controller firmware side of things, revisit our guide on flashing Betaflight firmware — ELRS passthrough depends on a correctly configured Betaflight UART, and a driver failure on the FC side manifests as an ELRS flash failure.
For reliable ELRS hardware, we recommend the Happymodel EP1 Dual TCXO receiver — it’s the gold standard for 2.4GHz with temperature-compensated oscillator and WiFi flash support out of the box. Available now at uavmodel.