Hey! We’ll fix your Eero firmware update loop and get the network stable again (no more “stuck updating”, random reboots, or “update failed”). Quick questions so we don’t guess:
• Which Eero model(s) do you have (eero, eero Pro, eero 6/6+, Pro 6E, Max 7, etc.) and how many nodes in the mesh Wi-Fi?
• Is the “main” unit a gateway eero connected to the modem by Ethernet, or do you have another router in front (possible double NAT)?
• What exactly happens: the app shows Updating eeroOS forever, the network drops during update, the gateway keeps restarting, or the update says “failed” then tries again?
• Any ISP setup like PPPoE, modem/router combo, or bridge mode changes recently?
Once we know that, we’ll do the fastest path: stabilize internet → power cycle in the right order → retry update → soft/hard reset only if needed.

Yep — that’s a classic eero stuck updating pattern. An eeroOS update loop usually comes from one of these:
• The gateway loses internet mid-download (ISP hiccup, modem issue, flaky Ethernet) → update fails → retries.
• Power or overheating causes the gateway to reboot while applying firmware (especially in tight cabinets).
• App/session problems (phone hops Wi-Fi/cellular, VPN enabled) causing “update failed” even if the nodes are trying.
• Network topology conflicts: another router in front, “smart” firewall, or a modem/router combo not truly in bridge mode → intermittent WAN during update.

We’ll go step-by-step and keep it safe: first stabilize the gateway’s WAN, then make the update succeed once — not endlessly retry.

Perfect — we’ll start with the fast wins that fix most Eero firmware update loop cases.

Step 1 — Make the update environment “clean” (2 minutes)
1) On your phone: turn VPN OFF temporarily and disable any “Private DNS” / ad blockers for the update.
2) Keep the phone on the same network and close/reopen the eero app so it refreshes the update session.

Step 2 — Power cycle in the correct order (this matters)
1) Unplug the modem/router combo power for 60 seconds.
2) Unplug the gateway eero power for 60 seconds.
3) Plug the modem/router back in first and wait until it’s fully online (solid “internet” light).
4) Plug the gateway eero back in and wait 5–10 minutes (it may flash while re-establishing WAN and downloading eeroOS).

This clears stuck WAN sessions and fixes “update failed” loops caused by shaky internet or a stale modem lease.

Good question — for an eero update stuck situation, we want the gateway eero stable first. Nodes will follow once the gateway is on the correct firmware.

Step 3 — Confirm the gateway’s WAN is solid before retry
• Check the Ethernet cable from modem/router → gateway eero. If you have a spare, swap it (bad cables cause random WAN drops during firmware download).
• If your modem/router has multiple LAN ports, try a different port.
• Make sure the gateway is not in a hot/closed spot (overheating can trigger reboots right when firmware applies).

Step 4 — Retry update once, then leave it alone
In the eero app, tap Retry update and then don’t force-close the app repeatedly. Let it run 10–15 minutes. The LED may flash while the eeroOS firmware installs. Constant app-refreshing can make it look “stuck” when it’s actually applying the update.

Yes — an ISP modem/router combo can absolutely contribute. Double NAT by itself doesn’t always break updates, but “router features” sometimes do: firewall filtering, parental controls, or unstable WAN renewals.

Step 5 — Reduce topology conflicts (quick checks)
• If the ISP device is a router, see if it supports bridge mode. Bridge mode often makes the gateway eero the only router (cleaner WAN, fewer random drops).
• If you can’t bridge it, at least disable “smart security” filtering temporarily and ensure the gateway eero is on a normal LAN port (not guest/VLAN).

Step 6 — Do a safe “soft reset” on the gateway eero
A soft reset refreshes the gateway’s internal state without wiping your whole network like a factory reset.
• Press and hold the reset button on the gateway eero until the LED changes (then release).
• Let it reboot fully, then try the update again from the eero app.

If the LED went red, that often indicates loss of internet/WAN at that moment — which lines up with an update loop caused by unstable WAN.

Totally fair — and you’re right to avoid a full wipe unless needed.

Soft reset vs hard reset (important)
• Soft reset: designed to recover from glitches (like a stuck update) and typically keeps your network configuration intact.
• Hard reset / factory reset: wipes the eero and you’d set up the network again (last resort).

Step 7 — If the loop continues, isolate the update to the gateway
Sometimes a node with a weak connection causes the mesh to destabilize during firmware rollout. Quick test:
1) Unplug power from the two non-gateway nodes.
2) Leave only the gateway eero online (connected to modem).
3) Retry the firmware update and let it finish.
4) After the gateway is stable, plug nodes back in one at a time so they update cleanly and rejoin the mesh Wi-Fi.

Exactly — once the gateway is updated, the next most common issue is a single node struggling to rejoin and apply the same eeroOS firmware.

Step 8 — Bring that node close for a clean update
• Plug the problem node in near the gateway (same room) to improve signal during the update handshake.
• If you use Ethernet backhaul, confirm the cable/switch is working; a flaky switch port can cause “online/offline” flapping.

Step 9 — Soft reset the node if it won’t settle
• Do a soft reset on that node (reset button until LED changes, then release).
• Give it time to rejoin and download the update from the gateway.

Once it’s stable, move it back to its normal spot. If it only fails in its original location, it’s a placement/signal issue rather than a firmware problem.

Yes — a few tweaks make eero firmware updates far less stressful:

Prevent the next Eero firmware update loop
• Keep the gateway on a stable outlet (avoid loose power strips) and in a cool, open area (heat = reboots during updates).
• If you use an ISP modem/router combo, consider enabling bridge mode so the gateway eero is the only router (fewer WAN resets and fewer “update failed” errors).
• Avoid running updates while using a VPN or aggressive DNS filtering on the management phone.
• If one node is far away, consider better placement or wired backhaul — weak links are the #1 reason a single node stalls during firmware rollout.
• When the app prompts for an update, do it when you can leave the network alone for 15–20 minutes (no constant power cycling).

If it ever starts looping again, the fastest fix is the same: stabilize WAN → update gateway alone → then nodes one-by-one.

Summary: To fix an Eero firmware update loop, first stabilize the internet (modem → gateway power cycle, swap Ethernet), then retry the update once. If it keeps failing, soft reset the gateway and update the gateway eero alone (unplug nodes). After the gateway is updated, bring nodes online one-by-one (move a stuck node closer and soft reset if needed). Not sure if your ISP modem/router needs bridge mode or if you’re dealing with double NAT? Open the chat and an expert will guide you step by step.