Opkg upgrade kills my routers

Hello Forum,

yesterday I wanted to install the latest updates to my OpenWrt router (a Fritzbox 4040). During the updates process the FB was dying. No way to get it back to life.
Today I tried the updates on another hardware, a FB 7412 - same issue. Machine dead.
Last status on the console was:

Upgrading busybox on root from 1.33.1-1 to 1.33.1-4...
Downloading https://downloads.openwrt.org/releases/21.02.0-rc1/packages/mips_24kc/base/busybox_1.33.1-4_mips_24kc.ipk
Upgrading netifd on root from 2021-01-09-c00c8335-1 to 2021-05-26-899c2a45-1...
Downloading https://downloads.openwrt.org/releases/21.02.0-rc1/packages/mips_24kc/base/netifd_2021-05-26-899c2a45-1_mips_24kc.ipk
Installing libubox20210516 (2021-05-16-b14c4688-1) to root...
Downloading https://downloads.openwrt.org/releases/21.02.0-rc1/packages/mips_24kc/base/libubox20210516_2021-05-16-b14c4688-1_mips_24kc.ipk

Is there any chance to get the routes back to life ?

Thanks in advice

Please read:

The TOH page for FB 4040 links to guides for debricking and factory reset. Did you try these?

only flash a release candidate OpenWrt version to routers to help stabilizing this future release and if you are ready to run into problems on these devices where you run that release candidate. Release candidates are built for testing, not for production.

The current stable release is still 19.07.7.

1 Like

Busybox alone is a sure way to break your router... See the first link shared in the post above about running a system-wide opkg upgrade.

@odrt The point of release candidates is wider testing. I have been running 21.02 in 'production' for months and it works very well. However, recently there has been a lot of netifd refactoring, and upgrading from one 21.02 build to another seems to be broken now, as was the case at some point with master as well.

So if you want to install a 21.02 snapshot build, you should be wiping your settings (basically /etc/config/network needs to be rewritten, which will happen if you wipe settings during sysupgrade). The migration path is broken ATM, and that's holding back the RC2 as you can read in the mailing list message.

@Rocky I edited your generic topic title to reflect what's actually happening.

I wrote the same:

thanks so far. So I will try to get them back to life