Unable to switch partitions (i think) after failed OpenWrt update (Linksys MX5500)

I am using OpenWrt 25.12.2 on a Linksys MX5500. It works fine overall. However, the previous update did not go smoothly, causing the device to get stuck in the “wrong” partition.

After force rebooting it three times, it eventually returned to the previous installation on the other partition.

After that, I installed Advanced Reboot, but I am unable to switch between partitions.
Is something broken, or is this something that can be fixed?

Everything is working at the moment, but I have the impression that every update is now being installed on the same partition. How can I verify this?

Does anyone know how I can see on what partition I’m on, and if there is something wrong with a partition? It boots, so that works, but I can’t reboot to the other partition. they both give the same message as in the screenshot.

I’m I asking the wrong question, or to little info for someone to give me a push in the right direction? Or does really no one has a clue? :wink:

The only thing that comes to my mind, is to flash original linksys firmware, and start over with OpenWRT. But, i’m not sure if that’s possible without serial connection.

1 Like

just change to the mx5500 or scp file to your router in /tmp. this should bring you back to stock. works on MR5500 and MR7350

ssh in and

fw_printenv boot_part

Like pepermint's command hint implies, there are u-boot environment variables on flash, which control the boot partition selection. You can see all of them with fw_printenv.

I have experience with wrt3200acm dual boot, and there were actually several related variables controlling the boot, not just boot_part.

In your case, the "alternative" is shown for both partitions, likely meaning that the variable can't be read, and so neither is detected to be "current".

If the variables are damaged, you may need to reinitialise them.

when I try fw_printenv boot_part, it tells me;

root@Meterkast-Garage:~# fw_printenv boot_part
Cannot parse config file '/etc/fw_env.config': No such file or directory
Failed to find NVMEM device

On my other mx5500 it works, so something is broken.

root@Woonkamer-vlan:~# fw_printenv boot_part
boot_part=2

So I’m going for the oem firmware and then back to openwrt.

I did the

wget https://downloads.linksys.com/support/assets/firmware/FW_MR5500_1.1.2.209598_prod.img -O /tmp/FW_MR5500_1.1.2.209598_prod.img fw_printenv boot_part 
root@Meterkast-Garage:~# wget https://downloads.linksys.com/support/assets/firmware/FW_MR5500_1.1.2.209598_prod.img -O /
tmp/FW_MR5500_1.1.2.209598_prod.img fw_printenv boot_part
Downloading 'https://downloads.linksys.com/support/assets/firmware/FW_MR5500_1.1.2.209598_prod.img'
Connecting to 18.66.112.90:443
Writing to '/tmp/FW_MR5500_1.1.2.209598_prod.img'
/tmp/FW_MR5500_1.1.2 100% |*******************************| 41344k  0:00:00 ETA
Download completed (42336256 bytes)
Connecting to 18.66.112.90:443
Writing to '/tmp/FW_MR5500_1.1.2.209598_prod.img'
/tmp/FW_MR5500_1.1.2 100% |*******************************| 41344k  0:00:00 ETA
Download completed (42336256 bytes)
Connecting to 18.66.112.21:443
Writing to '/tmp/FW_MR5500_1.1.2.209598_prod.img'
/tmp/FW_MR5500_1.1.2 100% |*******************************| 41344k  0:00:00 ETA
Download completed (42336256 bytes)
root@Meterkast-Garage:~#

But not sure what to do next.

I used the command above, nothing seems te happen. When I reboot it goes back to openwrt (on the other partition :wink: )

See issue and solution here:

1 Like
mtd -e alt_kernel -n write /tmp/FW_MR5500_1.1.2.209598_prod.img

The output is;

The device is in the format of mtdX (eg: mtd4) or its label.

I didn’t try @georgem83 solution yet

@georgem83 his solution did trick for installing de OEM firmware.

Will try to force boot into it and install Openwrt from there.

Keep you posted.

Installed the OEM version, you have to config the whole thing :wink:

installed openwrt, everything is fine now.

thanks!

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