Hi all,

I’m running into a blocking issue with a TP-Link Omada ER707-M2 and I’m hoping for confirmation or guidance from TP-Link staff or other users.

Context:
- ISP: Delta (Netherlands)
- ISP modem/router: Nokia XS-2426G-B
- Bridge mode is not available on the ISP device
- Intended setup: ISP modem → ER707-M2 (DMZ) → Omada network

Problem:
The ER707-M2 contains old firmware (v1.0.2).
I am running Omada Controller 5.14.x, which no longer supports legacy gateway agents.

As a result:
- The ER707 appears as “Pending” in Omada
- Adoption always fails
- Standalone web UI is accessible but upgrading to a compatible firmware is not possible

This creates a firmware deadlock:
- Omada cannot adopt the gateway because the agent is too old
- The gateway cannot be upgraded to a newer firmware via Omada

What I already tried:
- Multiple factory resets
- Standalone configuration
- Fully isolated setup (direct PC ↔ ER707, no ISP modem)
- Attempted firmware upgrade via web UI
- Attempted TFTP recovery using ER707-M2 firmware v1.2.3:
  - Static IP on PC (192.168.0.66)
  - Correct firmware filename (er707.bin)
  - Direct LAN connection
  - Firewall and VPN adapters disabled
  - Reset button held during power-on (15–30 seconds)

(- Adoption attempts with the ER707 connected to the LAN via an Omada switch, not directly in front of or behind the ISP router)

TFTP issue:

- The ER707 never sends a TFTP read request.

- No request is observed on the TFTP server, even in a fully isolated environment.

(First time I tried this though, but I surely followed all steps with full focus and attention). 

Additional note:

- The default LAN IP of the ER707 overlaps with my ISP router’s LAN IP which complicates initial access but this does not seem to be the root cause.

The issue persists even when completely isolated.

Questions:
1. Is this a known issue with early ER707-M2 firmware batches?
2. Is there any alternative recovery method besides TFTP?
3. Should this unit be considered non-recoverable and eligible for RMA?

The device has been lying around for around 25 months but it has never been put into production and is effectively new.

In parallel: I have also contacted the reseller to ask whether this can be resolved via warranty or goodwill but I wanted to check here as well whether this is a known issue and whether there is any official recovery path for this situation.

The rest of my Omada setup (APs, switches and controller) has been running fine so far (really great, actually).
Hopefully I can get this ER707 up and running soon, as I’m planning to further extend my network with additional switches, cameras and NVRs, including dedicated IoT and camera/ surveillance VLANs in the near future.
 

Thanks in advance for any insights.

Kind regards