Yes. If you want to move to current snapshot builds instead of using older snapshots or releases you can just force-flash the v1.1.3 installer.
2 Likes
@daniel Please consider removing Installer v1.1.0, v1.1.1 and v1.1.2 files (which contain the buggy BL2 TF-A) from https://github.com/dangowrt/owrt-ubi-installer/releases page so that people don't accidentally download and use those installer versions. Thank you.
1 Like
To be clear this with the bl2 v2.10 won't work with the current v23x release, just snapshots?
1 Like
Thank you to @Daniel and others who kept working on this, and to you @lostpuppy for the clear instructions in the Github Gist.
The freezer trick only went so far, lol, and I was getting much better at the serial connection to rewrite the flash, but
Now, I believe I can put all the screws back in!
Thanks again to all who persevered . 
3 Likes
Yes, exactly. For v23.05.x you should stick with bl2 from TF-A v2.4 (aka 1.0.2 installer). Scroll up in this thread to find out if your current bl2 is affected by the problem and if so, how to fix the issue.
1 Like
To fix the Apple issues, try setting DTIM Interval to 3 on the wireless interfaces.
My router is servicing almost entirely iOS and Macs. Works fine .
mt76 driver is not really polished for 23.05 or earlier. Lots of bug fixes have gone into snapshots since 23.05 have branched off.
My mistake in the migration to the new unified apsoc_common framework 
2 Likes
Many many thanks for this! It was tremendously helpful for me on two [of four] of my OKD prone, but not yet failed RT3200s. 
1 Like
@daniel removed files from github,and im struggling to find bl2_preload.bin (used some from thread,also trying recover bricked unit which had 6.1 kernel snapshot ,bl31-uboot.fip from current snapshot shows "no valid mac address found" and "cant get kernel image",unable to get in uboot menu.Is it possible to boot via uartboot installer.itb to recover and reflash?
1 Like
I just ran into this problem overnight while running the new fix instructions, thankfully had an old one downloaded. The one currently available/downloadable does not have an option for U-Boot Console at the bottom of menu; the one I previously downloaded to fix my first OKD does... I can send it to you if desired.
Successfully followed these instructions overnight while injecting some of my own (like, instead of using wget to download a vanilla firmware image, at that stage where the router successfully reboots, I went into Luci and did an Attended Sysupgrade instead, then installed the kmod-mtd-rw package and proceeded with the mtd block rewrites).
Hoping I won't have to open the RT3200's case ever again after this!
A big THANK YOU to everyone here for working diligently to track down and fix this pesky problem.
I was running an old build of OpenWrt with 2.4 firmware. I just ran https://github.com/dangowrt/owrt-ubi-installer 's sysupgrade build from within OpenWrt. Am I in trouble?
edit: yep, this is not powering on anymore.
edit2: 2.0mm pitch... I need wires looks like.
Yes, you are in a bit of trouble. The content of the factory partition which you most likely wiped now should still be in a file in the boot_backup UBI volume, try grabbing it out of there using 23.05.x recovery image. Then run the actual installer to move to snapshots.
I've removed the confusing sysupgrade and recovery files to make all this more clear which is the file people should download and flash.
I used that sysupgrade file as the README implied it was different than the standard one. Additionally unless I missed it, the instructions were all for upgrading from stock firmware.
Oh well. Cable arrives Tuesday. Unless I can find it in a local shop.
BL2 TF-A
bl2-for-mtk_uartboot.bin
EDIT:
https://downloads.openwrt.org/snapshots/targets/mediatek/mt7622/mt7622-ram-1ddr-bl2.bin
When running:
sysupgrade -v openwrt-mediatek-mt7622-linksys_e8450-ubi-squashfs-sysupgrade.itb
I get the following error message:
Fri Aug 16 08:17:05 +03 2024 upgrade: The device is supported, but this image is incompatible for sysupgrade based on the image version (1.0->2.0).
Fri Aug 16 08:17:05 +03 2024 upgrade: SPI-NAND flash layout changes require bootloader update. Please run the UBI installer version 1.1.0+ (unsigned) first.
Image check failed.
Here's my device information:
-----------------------------------------------------
OpenWrt 23.05.4, r24012-d8dd03c46f
-----------------------------------------------------
root@OpenWrt:~# cat /etc/os-release
NAME="OpenWrt"
VERSION="23.05.4"
ID="openwrt"
ID_LIKE="lede openwrt"
PRETTY_NAME="OpenWrt 23.05.4"
VERSION_ID="23.05.4"
HOME_URL="https://openwrt.org/"
BUG_URL="https://bugs.openwrt.org/"
SUPPORT_URL="https://forum.openwrt.org/"
BUILD_ID="r24012-d8dd03c46f"
OPENWRT_BOARD="mediatek/mt7622"
OPENWRT_ARCH="aarch64_cortex-a53"
OPENWRT_TAINTS=""
OPENWRT_DEVICE_MANUFACTURER="OpenWrt"
OPENWRT_DEVICE_MANUFACTURER_URL="https://openwrt.org/"
OPENWRT_DEVICE_PRODUCT="Generic"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="OpenWrt 23.05.4 r24012-d8dd03c46f"
root@OpenWrt:~# grep "(release)" /dev/mtd0ro
v2.9(release):OpenWrt v2023-07-24-00ac6db3-2 (mt7622-snand-1ddr)
v2.9(release):OpenWrt v2023-07-24-00ac6db3-2 (mt7622-snand-1ddr)
v2.9(release):OpenWrt v2023-07-24-00ac6db3-2 (mt7622-snand-1ddr)
v2.9(release):OpenWrt v2023-07-24-00ac6db3-2 (mt7622-snand-1ddr)
Kindly advise what I need to do to overcome this error. Thank you.
i have four devices with three different states:
a) bl2 v2.4 v2021-05-06-d2c75b21-3
fip
factory
ubi:
ubootenv
ubootenv2
recovery
boot_backup
fit
rootfs_data
b) bl2 v2.9 v2023-07-24-00ac6db3-2
fip
factory
ubi:
ubootenv
ubootenv2
recovery
boot_backup
fit
rootfs_data
c) bl2 v2.9.0 v2023-10-13-0ea67d76-1
ubi:
fip
factory
ubootenv
ubootenv2
recovery
fit
boot_backup
rootfs_data
What is the recommended way of updating them with current master and the fixed bl2?
With all four, if you don't have it, you probably want to take a backup of the factory partition to ensure you'll always be able to recover even from the worst case situation. A and B will have it listed right from luci in the mtdblock section. C requires a bit more work over SSH to find and retrieve it from UBI.
a: This device is not at risk of OKD. You can remain on the release version if you wish and not have to perform any steps at this time, or you can use the OpenWRT UBI installer 1.1.3 if you truly feel you have a need to move to snapshot.
b: This router is at risk of OKD. You can replace only the BL2 (preloader) with the one provided with OpenWRT release 22.03.7 (this can be done over SSH or via U-Boot console), or you can run the OpenWRT UBI installer 1.1.3 if you feel you need to move to snapshot.
c: This router is at risk of OKD and is already running snapshot. Download the preloader (bl2) currently available from the OpenWRT firmware selector for e8450 UBI with version SNAPSHOT and flash that file to the router either from the U-Boot console or with the SSH instructions posted by Lostpuppy (in this thread).
1 Like
If you're on the stable firmware, you can't follow the complete set of instructions in that document, as it was designed for updating OKD-affected snapshot to patched snapshot. Bypassing the warning would brick your router.
For routers running stable / Release 23.05.4 or older:
What you want is the BL2 (preloader) from 22.03.7, not the one from snapshot. The process to write the bl2 does apply, however:
opkg update
opkg install kmod-mtd-rw
cd /tmp
wget https://downloads.openwrt.org/releases/22.03.7/targets/mediatek/mt7622/openwrt-22.03.7-mediatek-mt7622-linksys_e8450-ubi-preloader.bin
# load the kernel module
insmod mtd-rw.ko i_want_a_brick=1
# redundantly write bl2 into the first 4 blocks
mtd -p 0x0 write openwrt-22.03.7-mediatek-mt7622-linksys_e8450-ubi-preloader.bin /dev/mtd0
mtd -p 0x20000 write openwrt-22.03.7-mediatek-mt7622-linksys_e8450-ubi-preloader.bin /dev/mtd0
mtd -p 0x40000 write openwrt-22.03.7-mediatek-mt7622-linksys_e8450-ubi-preloader.bin /dev/mtd0
mtd -p 0x60000 write openwrt-22.03.7-mediatek-mt7622-linksys_e8450-ubi-preloader.bin /dev/mtd0
sync
1 Like