Linksys WRT32X Upgrade issue

[Chrisofthewhites]

Hi,
I took out an old Linksys WRT32X to start using again, it was on OpenWrt 18.06.0 I was unable to install 24.10.0 via the web interface sysupupgrade I got the error:
"The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform."

I had the keep configeration unticked as it's a big jump in versions.
I then restarted in the factory firmware partition and installed the factory firmware version of the 24.10.0 thinking it would just overwrite whatever was on the second partition, but it just restarted to factory firmware. I tried forcing a restart to the second partition by powering it off when booting three times, but that didn't work either.
Anybody any ideas?
Thanks

[hnyman]

There is a kernel size change, forcing the need of factory image flash, so that the new kernel size gets initialized.

Note that there is no special "factory partition" and normal partition. Both are functionally identical. Both factory image flash and sysupgrade image flash always write to the other partition, and switch boot to that.

If you have a working system, either OEM firmware or openwrt, you need to flash the openwrt factory image of 24.10.1. if flashing from openwrt, you need to force it. Boot should then change to the other partition with 24.10.1.
And you can't restore settings, due to the DSA change in meanwhile.

[Chrisofthewhites]

Thanks, I'm going into the OEM firwmare and flashing the factory image of 24.10.1. It seems to complete but afterwards it won't boot into that partition, normally it should automatically restart and boot to openwrt but it doesn't. The OEM firmware just loads up again. I tried to give it three failed boots in the hope that that would work but that didn't work either.

[hnyman]

@Chrisofthewhites

flashing the factory image of 24.10.1. It seems to complete but afterwards it won't boot into that partition

Not owning wrt32x (but just the sister wrt3200acm with different flash size), I haven't tested anything with wrt32x myself, but anyhow, two ideas for you:

• boot partition selection (and also flashing) is controlled by two u-boot variables that can get mixed. You might try flashing from OEM again a second OEM image and hope that the boot variables get corrected. And then try 24.10.1 again
• alternatively, try flashing the older 23.05.5 factory image (or the current main/master development snapshot)

[hnyman]

Reference to "mixed variables" that I talked about:

Rebooting Linksys WRT3200ACM leads to the router reverting to 'default' settings

That is the u-boot env, which is common to both partitions. Only these two lines should change in sysupgrade: They should be bootcmd="run altnandboot" boot_part=2 Hmm... Now, when I look at your data, I notice that there are mixed values. There should be either boot_part 1 + bootcmd "run nandboot", or boot_part 2 + bootcmd "run altnandboot" You have somewhat illegal combination of boot_part 1 and altnandboot. That will likely straighten up when you do the next OpenWrt sysupgrade, …

and other less than funny example of variables after manual editing...
(discussion of 5-10 messages)

Linksys Wrt32X issue

That sysupgrade from SSH looks normal, upto the moment when network connectivity is broken (normal). One possibility is that there is something wrong with the boot commands in u-boot. If you run the command fw_printenv from SSH console, what u-boot variables you see? The boot commands in use should be visible. Please copy them from your terminal here as text, instead of taking a photo.

[Chrisofthewhites]

Thanks for the tips however it didn't seem to solve, I tried flashing to both but it always restarts to the same partition. Maybe I'll jsut use it in the OEM firmware, keep life simple!