Flashed *-ubi-squashfs-sysupgrade.itb, router is non-responsive, power light blinking white

[apiskors]

I have a brand new Belkin RT3200 router that I bought c. a year ago, and finally took out of the box today. It had the original 1.0 firmware. On my Linux computer (Ubuntu 22.04.3 LTS), I used git to clone the owrt-ubi-installer project, and then ran build_installer.sh. That generated several files in the "dl" directory. The two important files seem to be:

openwrt-23.05.0-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery.itb
openwrt-23.05.0-mediatek-mt7622-linksys_e8450-ubi-squashfs-sysupgrade.itb

Next I followed the instructions here:

https://github.com/dangowrt/owrt-ubi-installer/tree/main#installing-openwrt

I first used the stock Belkin interface to upload the 1st file above, *-ubi-initramfs-recovery.itb. That seemed to work fine, the router rebooted into the OpenWRT recovery.

Next in the OpenWRT recovery, I used http://192.168.1.1/cgi-bin/luci/admin/system/flash to "Flash new firmware image", and gave it the 2nd file above, *-ubi-squashfs-sysupgrade.itb. That did NOT work fine. The router's power light is now blinking white, all other lights are off, all ethernet ports appear to be off.

What should I do to fix this? Thanks in advance for any help and advice!

[dangowrt]

The two important files seem to be:

openwrt-23.05.0-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery.itb
openwrt-23.05.0-mediatek-mt7622-linksys_e8450-ubi-squashfs-sysupgrade.itb

That's not the installer. If there aren't also the files
openwrt-23.05.0-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer.itb
openwrt-23.05.0-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer_signed.itb

then something went wrong in your attempt to run the build script.

Flashing the openwrt-23.05.0-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery.itb (which is what I assume you did) will not result in an installation of the new bootchain, only the image with the word installer in it's name does that. When running V1.0 stock firmware, the correct file would have been openwrt-23.05.0-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer.itb.

Now your subsequent attempt to flash openwrt-23.05.0-mediatek-mt7622-linksys_e8450-ubi-squashfs-sysupgrade.itb resulted in havoc (as the new bootchain is not present and conversion to UBI had never been carried out) which can only be recovered by connecting the serial console.

This has happened to multiple users before who did not read the filename and flashed the wrong file, e.g. here #63

[apiskors]

Ah. Thanks for the quick response! Well, I ordered a USB-to-TTL serial cable, looks like I'll have to learn to use it, and study your #63...

build_installer.sh emitted lots of output... Re-running it now, I see the problem:

+ find /tmp/tmp.HSCvhn6Lau/initrd/ -mindepth 1 -execdir touch -hcd @1698717834 '{}' +
find: The relative path ‘~/bin’ is included in the PATH environment variable, which is insecure in combination with the -execdir action of find.  Please remove that entry from $PATH

That's not the script's fault, ~/bin is in my PATH. Running it like this fixed things:

export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin ; ./build_installer.sh 

Now I see it actually built a bunch of *.itb files like you said it should:

openwrt-23.05.0-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer.itb
openwrt-23.05.0-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer_signed.itb
openwrt-23.05.0-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery.itb
openwrt-23.05.0-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery_signed.itb
openwrt-23.05.0-mediatek-mt7622-linksys_e8450-ubi-squashfs-sysupgrade.itb