TP-Link BE450 factory firmware

I want to flash OpenWrt to a TP-Link Archer BE450.
The hardware table says this is possible. However, the ToH download section provides only an initramfs kernel image (falsely claiming to be factory) and a sysupgrade image.
Neither can be uploaded from the TP-Link firmware update page.
Reason: initramfs is not a valid firmware format, sysupgrade is only recognized by OpenWrt.

There is no device specific wiki page to explain installation steps from scratch.

The download firmware page has a creation procedure for a customized firmware. But this breaks and does not provide any downloadable files.

Question:
Is there a way to convert initramfs to a factory image, that the original TP-Link firmware accepts to upload and that will run OpenWrt after a reboot?

Thanks

Not how it's done.

is possible via uart i has a tp link too he work very well

Thanks (I came across this post in my research) but it is neither helpful nor a solution to my problem.

Why:

  1. you have to open the router to get access to the board
  2. you need to attach some sort of terminal to the UART
  3. you need to attach a tftpd via ethernet and set up the initramfs
  4. even then, the router is not functioning according to spec (10Gb requires additional manipulation)

The page is a beautiful description of how to fiddle with hardware (if one is interested in that).

I’m not.

I check with the OpenWrt page. If it says, it works, I expect it works. I get the router.

If there are questions or reminders or warnings, I refrain.

Back to my problem:

I have a TP-Link BE450 running TP-Link software.

I want to upgrade to OpenWrt (https://firmware-selector.openwrt.org/?version=25.12.2 → useful for first installation, https://openwrt.org/toh/start → search for BE450, no limitations, https://openwrt.org/toh/views/toh_extended_all → there is a link to a factory image 25.12.1).

I download the factory image but this cannot be installed. Its not in the right format to upload to the router.

So my question was and still is:
How can I make such an image, if the image on the OpenWrt website does not fulfill its intended purpose.

This question is still unanswered.

btw: If you do not have a BE450v1 and you have not upgraded the router to OpenWrt 25.12.x via firmware flash, please do not reply. It does not address the issue. But thanks for trying to help.

You had to crack open the case.
I’m not doing this because there must be a simpler way (firmware flash).

have fun not running openwrt.

feel free to post it when you find it.

start buying lottery tickets, you'll be a millionaire before a person fulfilling this requirement will come along.

@frollic (I reply, because I still consider this forum to be credible)

Re: to my statement of opening the router → “have fun not running openwrt”
I have several TP-Link routers running OpenWrt. All in common, that I flashed them (without opening the case) with factory firmware, configured and operated them.

I also want the BE450 running on OpenWrt.

Re: there must be a simpler way → “feel free to post it when you find it”

Brilliant idea, if I find out how. I will also give credit to those who have contributed to the solution.

Re: you have not upgraded … → “start buying lottery tickets…”

Maybe my post needs explaining:

Before I post to a forum, I do my (thorough) research. As much as I appreciate when people try to help, I consider this forum being populated by people who know more that I about the topic. All I ask is: Don’t give me arbitrary information when I need specific advice.

Now to your response:

From your profile (impressive) you seem quite competent regarding OpenWrt (you even have a Guru badge).
However: your list of devices does NOT include TP-Link BE450. So you are not competent regarding the TP-Link BE450. At most, you could draw from analogy.
In May 2022 you had issues with your EM7455 (like I have issues with my BE450). From following the thread, your arguments and proceedings where remarkably factual. In May 2023 you have solved all your problems. With a little help from several others.

What happened between May 2023 and April 2026 that the quality of your contributions did degrade to an insulting level.

@frollic:

Regarding https://forum.openwrt.org/t/em7455-cant-get-it-to-work-on-21-02-3/128742:

In this thread you seem to have access to system logs.
How did you get access to them? Did you open the case and connected to the console or did you find a way to tap into it via ethernet ports?

Useful hints welcome.

cool, any of them a BE450 ?

you received the (currently) only valid response on how to install openwrt, you didn't want to accept it, that's fine, until you do, have fun not running openwrt.

same issue, not the same device though - Adding Support for FR365 v1.2.

@frollic:

Re 1

Mostly old Archer C7 (v2, v5 meshed together), before that WR84x and WR86x, Netgear WRND3700.
No BE450 so far.

Re 2

On Mar 22 you stated that the text on the web page that shows whether OpenWrt can in fact be installed is boilerplate text. Frustrating but reasonable and as it turned out, factual (you just rendered the ToH of OpenWrt useless).

I followed a link to flash TP-Link using ssh and curl (https://github.com/chill1Penguin/er605v2_openwrt_install).
BE450 does not provide ssh. So if I really wanted to get access, I had to open the case.

Going a little further down, I read the reply of slh - quite interesting.

Concluding: I made a mistake by posting my question in the first place.
Should have contacted Dirk Buchwalder in the first place.

so you're comparing apples and oranges ?

that's not why I posted the link to the FR365 thread, but I guess it doesn't matter.
the relevant part was the outcome, it's basically the same question as yours.

your mistake was not accepting the info you received about serial port install.

I'm sure Dirk only posted the most cumbersome way of getting openwrt installed on the BE450.

As @frollic wrote, it depends of the actual device if it’s possible to flash them via the stock firmware or not.

The TP-Link upgrade logic is hidden in a pre-compiled binary (I don’t remember the actual file name)

Adding a factory image recipe to the image.mk is simple, but without knowing how the stock upgrade process works it would make no sense.

That’s why the only way to flash the device atm the moment is using UART as described in the commit message.

Since this is a volunteers project, feel free to de-compile the upgrade binary to get to know the logic behind it.