I have been building firmware for my RT3200 for a long time now. I built a snapshot from the latest git just now and went to flash it but was presented with this warning:
I used the same diffconfig that I always do:
Why am I seeing this warning?
The file is faulty.
It does not even say that it is for another router. Sounds like it is not a sysupgrade file at all.
What is the name of the file?
can you show the first lines of the diffconfig output from your build system?
I posted the entire diffconfig above but using the hidden text option. Here are the first few:
File name under
using the hidden text
I missed that. Too fancy for me
But you are right. It looks normal.
I wonder if the reason is that you are might be running the faulty versioned build.
"r0+21885-xxx". An early build from buildbot/auc ?
But your screenshot show the correct UBI... hmmm...
Might be best to revert to the initranfs recovery console and use that for flashing.
I can't remember the source of the current firmware... I thought I built it. What is your suggestion? Use an alternative method to use that same source file but not the sysupgrade part of luci?
% ls /scratch/union/bin/targets/mediatek/mt7622
openwrt-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery.itb gives this when I try using it from luci:
EDIT: I even get those warnings when I try using the
official 22.03.5 image:
Of course it gives, because that is wrong image.
That is the recovery image, not sysupgrade.
I proposed that you use the recovery console for flashing. You trigger recovery during boot and end up in the initramfs recovery console that is unique to the RT3200/E8450. You can then use that to completely overwrite the current run-time OpenWrt image.
the versinioning of your current image is so strange, that I guess that that image might be a reason for your problems.
There is no commit 629fef5ff6 in OpenWrt
How does one trigger recovery during boot? I am only aware of holding reset down for 10 sec which resets the configs to factory values. Thanks!
see here, wait for fast blink then hit reset several times.
I used the image I built and flashed with force mode and now everything seems normal. Thanks for the advice.
sysupgrade -F -i -v /tmp/openwrt-mediatek-mt7622-linksys_e8450-ubi-squashfs-sysupgrade.itb
Image check failed but --force given - will update anyway!
Keep config files over reflash (Y/n): Y
Edit config file list (y/N): N
Thu Jan 1 00:04:13 UTC 1970 upgrade: Saving config files...
Thu Jan 1 00:04:13 UTC 1970 upgrade: Commencing upgrade. Closing all shell sessions.
There are two images in the RT3200 UBI right? Could this be corresponding to the original dangowrt image? How can I tell which of the two images I am booted into?
No. It used normal versining, I think.
That is likely the "normal" OpenWrt failsafe mode.
I meant the RT3200-specific recovery console.
disconnect the device from power and reconnect it while holding down the RESET button until the orange Internet LED turn on.
This will reset all changes you may have made to the U-Boot environment and also wipes the rootfs_data overlay filesystem (ie. OpenWrt system is "reset to factory").
The device will then attempt to boot via TFTP and if no TFTP server replies, it will resort to the on-flash recovery image you have already been using to initially flash the sysupgrade image after the installer has run. From there you can flash a working firmware again.
Thanks for the advice... it seems that just running the force option did the trick.
There are two boot partitions with two images in the RT3200 UBI right? How can I tell which of the two images I am booted into?
ubus call system board
The version in either of those should match what you cloned/built.