The video on that page does not seem to want to work for me, using either Brave or Chrome, so I am going by the instructions on that page.
I can connect to the box, using just my machine, and do get a web page, showing Firmware version 1.2.00, and a page asking me to accept the Terms, etc.
I click "Next," and get told that the WAN cable is not connected. There is NO Cancel button on that page. I click Next, and get taken back to the Terms page and Next from there goes back to the "No WAN" page.
First things first, try an old version of Firefox from around 2020-2021. There should be portable versions available for most computing platforms. Many of the stock firmwares for this device and others used old coding techniques that violate security standards of modern browsers, leading to âforgetfulnessâ and loops like this. It most often presents as an unending circle of successful login which will immediately drop back to the login prompt.
Sadly, different operating systems and computer configurations can sometimes make finding the perfect older version difficult. If youâre running Linux, you might actually do better trying to run an appimage-packaged version (or even the Windows version via WINE) to avoid issues with conflicting dependencies. If youâre running Windows, a âportableâ version of Firefox ESR around version 78 might be a safe option.
Worst case, you can always open the case, connect to the routerâs serial console, and use the U-Boot (bootloader) menu to instruct the router to install the OpenWRT UBI installer as its firmware image. The only downsides to that method are that it takes a bit of extra work, and you need a 3.3v serial to USB adapter. It also voids your warranty, but installing OpenWRT via any means will likely count toward that.
I was able to get through the Wizard by doing the above.
From GitHUB, I had downloaded the three files shown:
openwrt-mediatek-filogic-asus_zenwifi-bt8-ubootmod-initramfs-recovery-installer.trx
openwrt-mediatek-filogic-asus_zenwifi-bt8-ubootmod-initramfs-recovery.itb
openwrt-mediatek-filogic-asus_zenwifi-bt8-ubootmod-squashfs-sysupgrade.itb
Following the instructions, I went to Administration->FirmwareUpgrade and selected:
openwrt-mediatek-filogic-asus_zenwifi-bt8-ubootmod-initramfs-recovery-installer.trx
And was told that the Image File was Incorrect.
I also tried uploading the other two files, and was told the same thing.
Is it time to give up and try to find another router that can do Gigabit on the LAN side and will actually load OpenWRT?
The first file is the UBI installer. That is the one you need to load first. That one will reboot a couple of times before it finishes. When it is done (solid blue power LED), connect to the new web page with your regular browser and install the -sysupgrade.itb file. That will leave you on OpenWRT 24.10.0. Alternatively, you can use the above linked file with -installer- in the name and then the most up-to-date sysupgrade file from the OpenWRT firmware selector for the e8450 (make sure you chooser the UBI version) and that will give you a working 24.10.4 install. Do not forget to install a sysupgrade file after loading the installer file. The installer file alone will only configure your device with a recovery environment. It does not include a full firmware.
Well, I tried the new "recovery" file, openwrt-24.10.0-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer.itb, and, just for fun also tried openwrt-24.10.4-mediatek-mt7622-linksys_e8450-ubi-squashfs-sysupgrade.itb and both time was told, again, that the "Image File is Incorrect."
Is there any point in trying to build the software from source, or should I send this back and try something else?
All I need is a box that will connect to WAN and provide multiple 1+GB LAN ports.
This file includes the digital signature, so it will work for the versions of stock firmware that require it (1.2.00.273012 or newer).
I do not recommend building OpenWRT from source unless you are looking to get into development testing. Home-built versions will receive little to no support from the community because there are far, far too many ways it could break or differ from the official builds in ways that people have no way to identify.
If you havenât done so yet, you may want to log into the device via SSH and take a backup of the âfactoryâ UBI volume and/or the boot_backup data. Although the e8450 can be recovered from nearly any sort of flash corruption, the âfactoryâ volume is unique to each individual device.
The configuration archives tend to contain a lot of device-specific (and sometimes even version-specific) settings. Device/interface names differ between different devices, so restoring a configuration from a completely different piece of hardware will frequently soft-brick a device and require a fail-safe reload. Even across major OpenWRT versions, there can be quirks and breakages when restoring configurations.
Thank you. I also had an old backup from five years ago or so, when I was using OpenWRT last, and was using the configuration files ( things like port forwards ) to remind myself of what my network wanted, when I was building the Netgear, but thought that I could use the Netgear backup to just jump-start this e8450, but I was obviously wrong.
Yes, I will make such a backup.
I am slowly re-learning OpenWRT. I used it for years, but then used commodity routers for a few years, and had forgotten much of what I used to know.