Downgrading from snapshot to release (owut, OpenWrt One) SOLVED

I'm a total newbie to OpenWRT but am learning quickly. My hardware is the OpenWRT One router. I did what I thought was smart and upgraded the firmware via the Luci interface prior to building out the config. Oops, looks like I somehow managed to put a snapshot release on and of course lost my web interface. After figuring out how to get luci re-installed I want to get back to a stable release.... looking for advice before I --force anything.

root@router-main:~# owut upgrade -V 24.10.4
ASU-Server     https://sysupgrade.openwrt.org
Upstream       https://downloads.openwrt.org
Target         mediatek/filogic
Profile        openwrt_one
Package-arch   aarch64_cortex-a53
Version-from   SNAPSHOT r31608-017fc35b52 (kernel 6.12.55)
Version-to     24.10.4 r28959-29397011cc (kernel 6.6.110) DOWNGRADE
2 packages missing in target version, cannot upgrade
136 packages were downgraded
140 packages are out-of-date
ERROR: Update checks reveal package downgrades, re-run with '--force' to proceed

I ran again with -v and found the 2 packages missing:

apk-mbedtls                  3.0.0_pre20251007-r1                        missing to-version
kmod-usb-common              6.12.55-r1                                  missing to-version

So what's the best way to proceed to a stable supported firmware? Can I --force it or do I need to do something regarding the 2 missing packages first?

This is for a home network but I use it to work from home so it needs to be a production system for me. Should I consider just going into production with the snapshot version?

Thanks in advance, David

Try

owut check -V 24.10.4 -r apk-mbedtls,kmod-usb-common -a opkg --force

And see if anything looks wrong. If it seems ok, then change check to upgrade and see what happens...

Thank you for the quick suggestion! I'm having trouble interpreting the output and determining if this is any better:

root@router-main:~# owut check -V 24.10.4 -r apk-mbedtls,kmod-usb-common -a opkg --force
WARNING: Package 'kmod-usb-common' is a dependency, removal will have no effect on the build
ASU-Server     https://sysupgrade.openwrt.org
Upstream       https://downloads.openwrt.org
Target         mediatek/filogic
Profile        openwrt_one
Package-arch   aarch64_cortex-a53
Version-from   SNAPSHOT r31608-017fc35b52 (kernel 6.12.55)
Version-to     24.10.4 r28959-29397011cc (kernel 6.6.110) DOWNGRADE
1 packages missing in target version, cannot upgrade
136 packages were downgraded
139 packages are out-of-date
WARNING: There are 2 missing default packages, confirm this is expected before proceeding
ERROR: Checks reveal errors, do not upgrade

Snippets from the -v run gives more info:

fit-check-sign 2025.10-r1 missing to-version

Default package analysis:
  Default                      Provided-by
  kmod-nvme                    not installed
  kmod-phy-aquantia            not installed
  nftables                     nftables-json

There are currently package build failures for 24.10.4 aarch64_cortex-a53:
  Feed: packages
    syslog-ng                  Sun Oct 26 06:02:36 2025 - not installed
Failures don't affect this device, details at
  https://downloads.openwrt.org/releases/faillogs-24.10/aarch64_cortex-a53/

Okay so I added the fit-check-sign to the list of -r packages and perhaps this looks good enough to try?

root@router-main:~# owut check -V 24.10.4 -r apk-mbedtls,kmod-usb-common,fit-check-sign  -a opkg --force 
WARNING: Package 'kmod-usb-common' is a dependency, removal will have no effect on the build
ASU-Server     https://sysupgrade.openwrt.org
Upstream       https://downloads.openwrt.org
Target         mediatek/filogic
Profile        openwrt_one
Package-arch   aarch64_cortex-a53
Version-from   SNAPSHOT r31608-017fc35b52 (kernel 6.12.55)
Version-to     24.10.4 r28959-29397011cc (kernel 6.6.110) DOWNGRADE
136 packages were downgraded
138 packages are out-of-date
WARNING: There are 2 missing default packages, confirm this is expected before proceeding
WARNING: Checks reveal package downgrades, upgrade still possible with '--force'

Sounds good to me. If you do an owut download ... first, then you can also read through /tmp/firmware-manifest.json and see if anything looks strange.

Assuming that goes well, a simple owut install or sysupgrade /tmp/firmware.bin will finish the job and do the actual sysupgrade (both of those commands are equivalent, the only difference is that owut will re-verify the image against the build checksum again, which is sort of moot at this point).

Worked great, thank you. I'm happily on 24.10.4.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.