Is anyone able to perform sysupgrade with this command and upgrade on the same partition?
sysupgrade -s -v -i openwrt-sysupgrade.bin
I tried it but it overwrite the other partition with Linksys firmware.
Before
| Partition | Status | Firmware |
| 01 | Alternative | Linksys |
| 02 | Current | OpenWrt 25.12.4 |
After
| Partition | Status | Firmware |
| 01 | Current | OpenWrt 25.12.5 |
| 02 | Alternative | OpenWrt 25.12.4 |
How about Attended Sysupgrade from the UI? Has anyone tried that?
My situation is the same as yours. I once tested it at OpenWrt 24.10（MX5300 and WHW03v2）, and it still flashed into another partition.
The MR9000 wasn't supported with OWRT 24.x. I upgraded mine within snapshot with owut -upgrade and eventually downgraded it to 25.12.5 with owut --upgrade -V 25.12.5. YMMV. Make sure you follow the instructions to increase the kernel size before bricking your device.
That link does not exist.
It looks like the page hasn't been promoted since the MR9000 has achieved supported status. Can you try this link? If that doesn't work, just look it up in the Table of Hardware.
Anyone has solved this problem? Flashing on the same partition that you are running on?
As per sysupgrade command help
-s option => stay on current partition (for dual firmware devices)
My experience was that if you perform sysupgrade -n openwrt-sysupgrade.img on the same version of OpenWrt firmware as you already have, it will indeed flash to the other partition. If you sysupgrade to a different version, that should stay in the same partition.
In your case though, it appears to be not the case. I am wondering if there maybe a bug or something in the upgrade mechanism triggering this.
I have 3 WHW03v2, 1 MX5300 and 1 MR9000. According to my test results, whether it is the same version or the new version, the -s parameter is always invalid, and each firmware will be flashed into another partition. There is no problem with the operation of these newly flashed firmware.
I just checked the Wiki page for sysupgrade command, there is no option -s in that page (you can run the command sysupgrade --help to check if this option exists in your system). I think this option was probably added in more recent versions of OpenWrt (24.10.x or later).
Maybe we need to start some debugging on how this relatively new option works correctly.
root@MR9000:~# sysupgrade --help
Usage: /sbin/sysupgrade [<upgrade-option>...] <image file or URL>
/sbin/sysupgrade [-q] [-i] [-c] [-u] [-o] [-k] [-P] <backup-command> <file>
upgrade-option:
-f <config> restore configuration from .tar.gz (file or url)
-i interactive mode
-c attempt to preserve all changed files in /etc/
-o attempt to preserve all changed files in /, except those
from packages but including changed confs.
-u skip from backup files that are equal to those in /rom
-n do not save configuration over reflash
-p do not attempt to restore the partition table after flash.
-k include in backup a list of current installed packages at
/etc/backup/installed_packages.txt
-s stay on current partition (for dual firmware devices)
-P create provisioning partition to keep sensitive data across
factory resets.
-T | --test
Verify image and config .tar.gz but do not actually flash.
-F | --force
Flash image even if image checks fail, this is dangerous!
--ignore-minor-compat-version
Flash image even if the minor compat version is incompatible.
-q less verbose
-v more verbose
-h | --help display this help
backup-command:
-b | --create-backup <file>
create .tar.gz of files specified in sysupgrade.conf
then exit. Does not flash an image. If file is '-',
i.e. stdout, verbosity is set to 0 (i.e. quiet).
-r | --restore-backup <file>
restore a .tar.gz created with sysupgrade -b
then exit. Does not flash an image. If file is '-',
the archive is read from stdin.
-l | --list-backup
list the files that would be backed up when calling
sysupgrade -b. Does not create a backup file.
Hello all... first timer here.
Thanks to all involved in getting this device officially supported.
I actually bought the device today after lots of reading, with the goal of moving it to OpenWrt.
Unfortunately, I can't get to the 22.03.5 firmware from @sshel 's site... so I'm wondering if anyone can help me locate the file.
Maybe bad timing on my part and the site is down?
Thanks in advance!
If you can't get an old version to work so you can set the kernsize variable you can revert to the serial port method. I bought a serial-to-USB from Amazon for $15; taking the router apart, making the change, and screwing it back together took about 15 minutes. Add a bit more to flash the image and reboot the router.
So far the MR9000 has been flawless for apartment mesh use.
Thanks for the quick reply. 
But yeah... I should have specified that I was hoping to avoid buying an adapter or opening the box... even if it could be fun. But before hitting up Amazon, I thought I'd check here to see if it was a site-being-down issue and/or if anyone could point me to another location.
Seems @sshel 's website is having capacity problem. I have re-uploaded a mirror of 22.03.5 factory.bin image from there to Google Drive. You can find it here.
Thank you @wfgriffin88 !
The site was up yesterday and I was able to get the file I wanted, but forgot to update here. Good to have it somewhere else for the next person who comes along, though.
Unfortunately, the second hand MR9000 I picked up seems to have power issues, so I didn't actually get to use it.
Appreciate the help.
No problem. Maybe try another 12V x 2A AC power adapter and see if you can get the router working again. Good luck!
Any luck with sysupgrade -s option?
It would be really nice and perfect to keep the Linksys firmware on one partition(as a backup) and keep upgrading on the other partition with sysupgrade when a new release is out.
Any thoughts?