How to update ExpressLRS
RADIO // FIELD_REPORT

How to update ExpressLRS

Published
Updated
Read time4 min read

ExpressLRS updates are normal maintenance. What breaks binds is updating the radio (TX) and forgetting the craft receiver (RX), or the reverse, so the two are on different major versions and no longer talk. Treat every flash as a paired job: TX and RX on a compatible release, binding phrase saved, sticks checked before the field.

Basics first if you are new: what is ExpressLRS.

Before you flash anything

How to update ExpressLRS: Before you flash anything

Pre-flash checklist:
□ Write down binding phrase / UID notes
□ Note current TX and RX firmware versions (Lua / Configurator)
□ Charge the radio and a craft pack; a power cut mid-flash can leave a device unbootable
□ Props off; remove props if the craft might arm on first power
□ Know whether your RX is serial (UART, its own chip) or SPI (built into the AIO)

The binding phrase keeps an ELRS fleet together. Lose it and you are rebinding every craft. Keep it in a private note on your phone.

Bench tip: many spare USB cables are charge-only. Use a known data cable before you blame the bootloader.

Update order that prevents bind pain

StepWhatWhy
1Update TX (radio internal / external module)Radio is the reference
2Update each RX to the same major versionA major-version mismatch (2.x vs 3.x) will not bind
3Revisit Lua bind / phraseConfirm still set
4Stick end-points in BetaflightCatch inverted / dead channels early

Use the official ExpressLRS Configurator and the Lua script for your hardware, not random forks. Internal modules (Pocket, Boxer, Zorro) and external modules (Happymodel, BetaFPV and others) each have their own targets; pick the exact one for your hardware.

Typical radio (EdgeTX) flow:
1. Backup models if you are nervous
2. Flash TX via Configurator (WiFi / USB / passthrough as supported)
3. Open ELRS Lua - confirm version string
4. Flash each serial RX (WiFi, or Betaflight passthrough over the UART)
5. Power cycle both ends

After the update

Re-bind if the update requires it, then verify before freestyle:

  1. Radio shows telemetry / LQ if you expect it.
  2. Betaflight Receiver tab: sticks move cleanly - how to bind ELRS.
  3. Modes still land on the right aux channels (ARM especially).
  4. Short range check outdoors before gaps - ELRS link budget and setup checklist.
CheckPass looks like
BindCraft responds without random failsafes at 10 m
SticksThrottle / yaw / pitch / roll correct axes
ARM switchOnly arms when you intend - how to arm
FailsafeDisarm / drop per your model setup when TX off

Failure modes

How to update ExpressLRS: Failure modes

MistakeResult
TX on 3.x, RX left on 2.xWill not bind
Wrong Configurator targetBoot loops / no RF
Flashing RX while phrase wrong“Updated” but never binds your TX
Skipping stick checkFirst field pack flies inverted
Updating at the fieldFlat batteries, bad Wi-Fi, half-finished flashes

Many whoop BNFs use an SPI ELRS receiver built into the AIO. Its ELRS code is part of Betaflight, so the ExpressLRS Configurator cannot update it: you update it by flashing Betaflight. Betaflight 4.4 or newer is needed for ELRS 3.x; 4.3 only speaks 2.x (ExpressLRS SPI receiver docs). Save a CLI diff all before flashing. Some older Mobula6/Mobula7 batches shipped on Betaflight 4.3, which is why they will not bind to a 3.x radio out of the box.

Version compatibility (practical rule)

Keep the whole fleet on the same major version when you can. If you must mix, read the ExpressLRS release notes for that pair. “It bound once” is not a version strategy. When in doubt, update TX and every craft you will fly that weekend in one sitting.

India field notes

Update at home on Wi-Fi you control, not at the field. Carry a known-good USB data cable in your bag (away from the packs). After monsoon storage, reseat module antennas before blaming firmware for weak link quality.

Dry practice while you wait for a flash to finish: /sim.

Bench

ELRS radios and whoop BNFs: the Bench. Match radio + BNF protocol in Grind Lab before you buy a second craft that cannot share the phrase.

See also

Discussion

Comments aren't open on this post yet. Share it with your build group, or start a thread on X.