@noyb2025 

Hi,

to 1. For newer TP-Link models (AX and later) follow the instructions given under section "Method 2: Rescue an Archer AX Series Router" of this FAQ  https://www.tp-link.com/en/support/faq/1482/

to 2. There is no more TFTP recovery on newer TP-Link routers.

to 3. For recovery via the webpage the name of the file doesn't matter. (just avoid using symbols or non-english characters)

  @woozle Thanks for your reply.

I figured that there was no tftp request from the BE450 (tcpdump)

Thanks also for FAQ 1482.

FAQ 1482 (https://www.tp-link.com/en/support/faq/1482/) states:

"Hold the button for five seconds until only a single LED lights orange in the middle."

This does not work on a BE450.

Holding the Reset button (which requires some metal stick to press inside the notch),

1. all LEDs light up blue

2. the LED for Internet connection lights up orange (more so a blink)

3. the power LED blinks blue for approx. 10s

4. WiFI LEDs light up blue

5. Internet LED lights up orange for approx. 1s, changes to blue then

6. connection LED lights up blue

Connecting from 192.168.0.10 to http://192.168.0.1 brings up http://192.168.0.1/webpages/onboarding.html

I can manually try:

- 192.168.0.1/webpages/index.html -> blue clouds

- 192.168.0.1/index.html -> reroutes to 192.168.0.1/webpages/index.html#

- 192.168.0.1/webpages/rescue.html -> "No such file or directory"

- 192.168.0.1/rescue.html -> "No such file or directory"

No rescue page.

I retried this procedure:

- using WPS instead of Reset

- pressing Reset for 30s

- pressing Reset for 5s

- pressing Reset until the orange light went on

FAQ 1482 is WRONG (or does not apply to BE450).

Is there a human technician who has a BE450v1 at hand and can verify the rescure page? (and maybe let me know how to proceed)

  @Joseph-TP 

At the moment:

After multiple resets and booting up the router over night,

Power -> blue, sometimes blinking

2.4GHz -> blue

5 GHz -> blue

Internet -> orange, unstable

LAN -> blue, sometimes blinking

This looks like a bootloader-level recovery issue on some BE models the TFTP only triggers in a very short window, so timing + correct adapter setup matters more than IP guessing. Also make sure the PC NIC is directly wired with firewall off. It’s a bit like State filings where even small formatting/timing errors can stop the whole process from going through.

  @jackobjasson2 

Thanks for the reply.

@woozle claimed there is no TFTP request on the BE450, you claim there is a narrow window where there is. - What now? TFTP or no TFTP, that's the question.

From my tests, this particular BE450 certainly did not request any TFTP files.

After power on and release of the Reset pin, the router did some internal errand (blue LED blinking) for 10s.

Only then did it ARP into the network to query who was online (connected to the only LAN-port that was plugged in.

Why do I know?

I set up a Raspberry Pi that ran atftpd to serve any TFTP request.
it also ran tcpdump on eth0 with wlan0 being disabled.

eth0 was configured with systemd-network so that no NetworkManager could interfere.

to ensure the network being up and responsive all the time, router and Pi were connected via powered switch (passthrough).

This configuration was tested with an Archer C7 (only exception being IP address 192.168.0.66 as opposed to 192.168.0.10) and client TFTP requests (where the Pi could not assume anything but had to serve as soon as requested).

All worked well -> BE450 does not issue TFTP requests (neither slow nor fast).

What worries me way more is the contradicting statements I get from TP-Link support.

Therefore I returned the router to the vendor.