How to correctly upgrade from 1.1.3 to 1.1.4

[crackerfly]

Hello～ How to correctly upgrade from 1.1.3 to 1.1.4？

I used ”openwrt-24.10.0-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer.itb “ and the update failed.

[dangowrt]

You cannot update v1.1.x by re-running the installer. The only way is currently to individually update:

• ARM TrustedFirmware-A bl2
• U-Boot and ARM TrustedFirmware-A bl31 (fip)
• OpenWrt recovery image (from the OpenWrt 24.10.0 release or newer)

You can do this using a TFTP server and the U-Boot menu when connecting to the internal 3.3V-level TTL serial port.

If you do not want to open the device it's more tricky:
Or you force-boot into recovery mode and start with replacing recovery image to the one of the 24.10.0 or newer release. You will have to delete the recovery and rootfs_data UBI volumes (ubirmvol), then re-create the recovery volume with the updated new size of the image you intend to write (ubimkvol), then write the downloaded recovery image to that new volume (ubiupdatevol).

Then reboot without clearing pstore, so you end up in the now updated recovery image. There you can install kmod-mtd-rw and load it using insmod mtd-rw i_want_a_brick=1, which will allow you to subsequently update the bl2/preloader.
Last but not least remove (ubirmvol) and recreate the static fip volume (ubimkvol) and write it (ubiupdatevol).

Note that there are no (as in zero) advantages of updating U-Boot or even bl2, and it's really just an unnecessary risk. I do not recommend anyone to do that.

Updating the recovery image to that of an official 24.10.x or later release does have the benefit that you will be able to (temporarily, in ram) install packages, esp. kernel modules.

[crackerfly]

You cannot update v1.1.x by re-running the installer. The only way is currently to individually update:

• ARM TrustedFirmware-A bl2
• U-Boot and ARM TrustedFirmware-A bl31 (fip)
• OpenWrt recovery image (from the OpenWrt 24.10.0 release or newer)

You can do this using a TFTP server and the U-Boot menu when connecting to the internal 3.3V-level TTL serial port.

If you do not want to open the device it's more tricky: Or you force-boot into recovery mode and start with replacing recovery image to the one of the 24.10.0 or newer release. You will have to delete the recovery and rootfs_data UBI volumes (ubirmvol), then re-create the recovery volume with the updated new size of the image you intend to write (ubimkvol), then write the downloaded recovery image to that new volume (ubiupdatevol).

Then reboot without clearing pstore, so you end up in the now updated recovery image. There you can install kmod-mtd-rw and load it using insmod mtd-rw i_want_a_brick=1, which will allow you to subsequently update the bl2/preloader. Last but not least remove (ubirmvol) and recreate the static fip volume (ubimkvol) and write it (ubiupdatevol).

Note that there are no (as in zero) advantages of updating U-Boot or even bl2, and it's really just an unnecessary risk. I do not recommend anyone to do that.

Updating the recovery image to that of an official 24.10.x or later release does have the benefit that you will be able to (temporarily, in ram) install packages, esp. kernel modules.

Oh my God! It's so complicated. Thank you for your guidance...