Yes, just like source code says...
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=4e7d58ebef92bdda8f582e0ef185cc2bc2d23897
Just updated, working great.
downgraded back to 24.10.1
I rebooted today and it would not mount ubi0_7 no matter what I did router would boot but the rootfs_data would be in read only mode
reflashing 24.10.1 resolved the issue, no sign of ubi errors in the log after
either the nand in my unit is going bad or something is bugging out on 24.10.2
If anyone's interested, the E8450 is available again at Woot for $19.99 ("Factory Reconditioned" with 90-day warranty).
Expires in ~4 days as of this post edit, or until sold out.
Here are unboxing pics of a similar order from February of this year.
4 Likes
It seems I've done too many things, originally did try to go from 22.03.xx to 24.10 with the Forum provided steps, but device did not come back online after the installer flash. Now trying to do the had steps, but fails already in step three:
MT7622> tftpboot factory.bin && mtd erase factory && mtd write factory $loadaddr 0 $filesize
Using ethernet@1b100000 device
TFTP from server 192.168.1.254; our IP address is 192.168.1.1
Filename 'factory.bin'.
Load address: 0x48000000
Loading: ####################################
11.1 MiB/s
done
Bytes transferred = 524288 (80000 hex)
MTD device factory not found, ret -19
Any help anyone?
Oh and the device boots from the Boot from the recovery just fine, but flashing anything does not seem to help
Looks like you have already updated U-Boot to the version which comes with 24.10. I recommend you to use mtk_uartboot to load U-Boot which came with OpenWrt 23.04 because only there the factory partition is defined. After writing the factory data, directly proceed and load the unsigned installer via TFTP and run it using bootm.
Tried with 23.05.5, tried 22.03.7, same result
MT7622> tftpboot factory.bin && mtd erase factory && mtd write factory $loadaddr 0 $filesize
Using ethernet@1b100000 device
TFTP from server 192.168.1.254; our IP address is 192.168.1.1
Filename 'factory.bin'.
Load address: 0x48000000
Loading: ####################################
6.6 MiB/s
done
Bytes transferred = 524288 (80000 hex)
MTD device factory not found, ret -19
MT7622> mtd list
List of MTD devices:
- spi-nand0
- device: snand@1100d000
- parent: root_driver
- driver: mtk-snand
- path: /snand@1100d000
- type: NAND flash
- block size: 0x20000 bytes
- min I/O: 0x800 bytes
- OOB size: 64 bytes
- OOB available: 28 bytes
- ECC strength: 4 bits
- ECC step size: 512 bytes
- bitflip threshold: 3 bits
- 0x000000000000-0x000008000000 : "spi-nand0"
- 0x000000000000-0x000000080000 : "bl2"
- 0x000000080000-0x000008000000 : "ubi"
Oh but using uboot for the mtk_uartboot gives me
- 0x000000000000-0x000008000000 : "spi-nand0"
- 0x000000000000-0x000000080000 : "bl2"
- 0x000000080000-0x0000001c0000 : "fip"
- 0x0000001c0000-0x0000002c0000 : "factory"
- 0x0000002c0000-0x000000300000 : "reserved"
- 0x000000300000-0x000008000000 : "ubi"
Stupid me
Okay somehow got it to reboot into the recovery partition unattended, I think. Version on the GUI now shows
OpenWrt 22.03.1 r19777-2853b6d652 / LuCI openwrt-22.03 branch git-22.245.77528-487e58a
And Model: Linksys E8450 (UBI)
Almost too scared to continue, but where do I look next 
Okay proceede with the 24.10 flash. System boots with the help of the bootmenu, but if I remove the serial, it does not boot. Am I toasted?
Edit:
Installed preloader and uboot from the 24.10.2 batch, the boot without the help of mtk_uartboot stops at
[ 2.610036] mt7530-mdio mdio-bus:1f lan2 (uninitialized): PHY [mt7530-0:01] driver [MediaTek MT7531 PHY] (irq=134)
[ 2.632295] mt7530-mdio mdio-bus:1f lan3 (uninitialized): PHY [mt7530-0:02] driver [MediaTek MT7531 PHY] (irq=135)
[ 2.654540] mt7530-mdio mdio-bus:1f lan4 (uninitialized): PHY [mt7530-0:03] driver [MediaTek MT7531 PHY] (irq=136)
[ 2.677027] mt7530-mdio mdio-bus:1f wan (uninitialized): PHY [mt7530-0:04] driver [MediaTek MT7531 PHY] (irq=137)
[ 2.688414] mtk_soc_eth 1b100000.ethernet eth0: entered promiscuous mode
[ 2.695205] DSA: tree 0 setup
[ 2.698663] clk: Disabling unused clocks
[ 2.703243] Waiting for root device /dev/fit0...
If I use mtk_uartboot, default boot selection works fine and system comes up fully funtional 24.10.2
Did you run the new v1.1.x installer?
After restoring your factory partition in U-Boot you will have to run the installer, that will convert the system to the new layout needed for 24.10.x or later. The procedure is documented on the device page in the wiki, sysupgrade gives you a warning when trying to update from 23.04.x to 24.10.x telling you to do so, and also in this thread this has been iterated over multiple times.
tl;dr: Start again with mtk_uartboot, flash again the factory paritition, and then load the installer via TFTP and launch it using bootm. Only then you can proceed and install OpenWrt 24.10.x using sysupgrade.
Okey, now I am in a state where unattended boot goes to recovery with version 24.10.1
If I select 3. Boot production system from flash.
from the boot menu, it goes to normal 24.10.2.
Can I fix it to boot to prodction and not to recovery by default?
The reason for the device booting into recovery mode by default is the presence of crash logs in the memory. Either view and delete them form /sys/fs/pstore/* or disconnect the device from power for a few seconds. That should subsequently make it boot into the production image.
Actually it seems the bootcmd was missing, I remember clearing it at some point when I was messing with the factory partition. I also cleared boot args if that matters.
However, boot is now ok, next grief seems to be that I have no wireless radios?
I can see from the boot log:
[ 9.715279] kmodloader: loading kernel modules from /etc/modules.d/*
[ 9.749059] Loading modules backported from Linux version v6.12.6-0-ge9d65b48ce1a
[ 9.756553] Backport generated by backports.git v6.1.110-1-35-g410656ef04d2
[ 9.833622] mt7622-wmac 18000000.wmac: Invalid MAC address, using random address c2:ba:fa:be:9e:f6
[ 9.843848] mt7622-wmac 18000000.wmac: registering led 'mt76-phy0'
[ 9.899458] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 9.922090] urngd: v1.0.2 started.
[ 9.925904] mt7915e 0000:01:00.0: assign IRQ: got 130
[ 9.931061] mt7915e 0000:01:00.0: enabling device (0000 -> 0002)
[ 9.937162] mt7915e 0000:01:00.0: enabling bus mastering
[ 9.989083] mt7622-wmac 18000000.wmac: HW/SW Version: 0x8a108a10, Build Time: 20190801210006a
[ 9.989083]
[ 10.089126] mtk-pcie 1a143000.pcie: msi#0 address_hi 0x0 address_lo 0x44f150c0
[ 10.125112] mt7622-wmac 18000000.wmac: N9 Firmware Version: _reserved_, Build Time: 20220630094834
[ 10.139942] mt7915e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20240429200716a
[ 10.139942]
[ 10.275830] mt7915e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20240429200752
[ 10.337401] mt7915e 0000:01:00.0: WA Firmware Version: DEV_000000, Build Time: 20240429200812
[ 10.453022] mt7915e 0000:01:00.0: eeprom load fail, use default bin
[ 10.459438] mt7915e 0000:01:00.0: Direct firmware load for mediatek/mt7915_eeprom.bin failed with error -2
[ 10.469103] mt7915e 0000:01:00.0: Falling back to sysfs fallback for: mediatek/mt7915_eeprom.bin
[ 10.486341] mt7915e: probe of 0000:01:00.0 failed with error -12
EDIT:
If I do the hard recovery to 23.05.5, wifi works fine, not sure where to go next to get to 24.10..
Has anyone managed to get to 24.10? I think I now have confidence to get back to 23.05, so if debugging is needed, fire away.
Hey Allā¦
Thanks very much for all your hard work getting this device supported.
I am having trouble with SQM in the download direction:
I have recently setup a linksys e8450 in a location with very low bandwidth, 1.5Mbit down and 0.5Mbit up. I have always used SQM in that location to help share the available bandwidth.
I have tried an openwrt-24.10-r20250307-080312 build and an openwrt-24.10-r20250723-204638 build, but it appears as though SQM is broken in the download direction?
I have all offloading and WED disabled. I am testing this now from my office with a high speed network on the WAN side.
I have SQM configured like this:
config queue 'wan'
option enabled '1'
option interface 'wan'
# 2aug25: only measure 1224 down
# dont forget to disable OFFLOADING and WED!
# 2aug25: sqm is broken, IFB does not collect all data from WAN, why?
option download '1101'
option upload '460'
option qdisc 'cake'
option ingress_ecn 'ECN'
option egress_ecn 'NOECN'
option linklayer 'ATM'
option overhead '44'
option verbosity '7'
option qdisc_advanced '1'
option squash_dscp '1'
option squash_ingress '1'
option debug_logging '1'
option script 'piece_of_cake.qos'
option qdisc_really_really_advanced '1'
option iqdisc_opts 'nat dual-dsthost'
option eqdisc_opts 'nat dual-srchost'
When using bwm-ng, it is easy to see that the download speed is not being restricted by the IFB like it should be, causing the modemās buffer to fill and latency to spike:
bwm-ng -t 1000 -I wan,ifb4wan
bwm-ng v0.6.3 (delay 1.000s);
input: /proc/net/dev; press 'ctrl-c' to end this
\ iface Rx Tx Total
==============================================================================
wan: 288.18 KB/s 14.34 KB/s 302.53 KB/s
ifb4wan: 130.27 KB/s 130.27 KB/s 260.54 KB/s
------------------------------------------------------------------------------
total: 418.46 KB/s 144.61 KB/s 563.07 KB/s
Note how the wan speed is way higher than the ifb4wan speed, they should be nearly identical right? The ifb4wan speed is correct, but the wan speed is too high.
Interestingly my test device only sees the correct 1.5Mbit during the download test.
I have tested SQM with the same build on X86 hardware and everything seems fine.
I have spent hours trying various SQM and network optionsā¦ I am at a loss, hopefully someone can give me a suggestion or pointer?
Thanks!
Just an update about the SQM problems I am havingā¦
I setup iperf between the test router and a few other devices. I used tcpdump to capture traffic in various places, then I opened the captures with wireshark.
I am no expert in wireshark, but the log is full of āTCP Dup Ackā entries, as well as āTCP Fast Retransmissionā entries. Could these retransmissions explain why the wan bandwidth is exceeding the ifb4wan bandwidth?
Everything looks fine with SQM disabled.
HI,
I have 2 RT3200 routers.
The first is on OpenWrt 23.05.5. Hardwired I get around 970Mb (1Gig line). Great.
The second one, I have upgraded to 24.10.2. The max I get is around 400Mb.
Both are configured the nearly exactly the same (vlan setup for Cityfibre UK ISP. https://www.ispreview.co.uk/talk/threads/openwrt-on-zen.39588/ )
The difference is that on the first one I have a wan6 Virtual dynamic interface (DHCPv6 client) and a guest network.
Software & Hardware offloading configured on both.
Maybe there i a setting I missed ?. Or could it be 24.10 is that much slower with this configuration. Could I backup settings from the 23.05 and restore it to the 24.10 router to to ensure settings are exactly the same (I donāt want to brick the router !)
Thanks
After reading more, could this be the issue ?:
The fix/workaround seems to be here
It states āThen apply this patch (note if ppoe lowlevel device is not vlan like eth0.1 it is not sufficient)ā My vlan is on base device āwanā - so I am guessing Iām ok trying this fix?
Hello Sir,
I think I may be in the same pithole now where you have been 
Initial update from 22.03 to install imaged already caused bricked device. With many attempts I got into 24.10.2 but no radios at all. Did try hard recovery to 24.10, does not work. Did hard recovery to 23.05.5, works fine, retried upgrade, does not boot. Another hard recovery to 25.05.5, all good. I put the case back on already but if you can share your adventures, maybe I dare to try once more
If you have succesfully recovered to 25.05.5 you are a great magician.
Regardless, once you have 24.10.2 running and did recovery by post from OW genious @grauerfuchs , than you are all set.
The reason why you think there is no radio is because you have not added any SSIDs. Until you add a ssid you get a generic device display in Luci wireless section for 2.4 and 5GHz. At least that was the case with me.
Try to upgrade with again (the procedure should be similar to 23.5.5) and let me know if this is a solution. If it is not, then you have made errors in recovery procedure with mac adresses. Only 2.4 generic wifi work.