As subject, I'm hoping someone might be able to suggest a/the best way to update from v17 (specifically: LEDE Reboot 17.01.5) to what I see in the TOH is the current supported version for WNDR3700v4: 23.05.0
I hoped I might be able to just use the sysupgrade bin (I'm not trying to retain my existing settings), but it seems that v17 is probably a bit too old for that to work (which I guess is fair!).
Is there a way to upgrade from v17 to v23.05.0 directly? Should flash 23.05.0 having first reverted to stock (is there a preferred way to do that)?
Yes, sysupgrade -n blah.bin should do the job (-n = "discard old config"), but make sure to take a backup first so you can pick through your old settings and update things (sysupgrade -b backup.tar.gz --- scp router:backup.tar.gz workstation:...).
EDIT: Oops, I got a v2 in the link, should have been v4...
Hi.
I have this device. It runs well 23.05.2. Meanwhile I remember issues when updating in a previous version (probably 19.07 -> 21.02). So I would recommand that you update one version at a time. Each time not keeping settings. Just configure the device once it'll run 23.05.
I grabbed the file you linked, and figured I'd give it a go from the GUI Backup/Flash interface (I'm occasionally an optimist ), but it seems that just can't cope with newer images.
Does your reply suggest that maybe it's only validation in the web interface which doesn't like the new images, and if I transfer the file and run the sysupgrade -n file.bin via SSH, the sysupgrade method should be OK?
(i) I imagine "factory image" above refers to a 'flash from factory' OpenWrt image, rather than a Netgear factory image?
(ii) I don't see WNDR3700v4 as supported by the tool (here) but I guess that list might not be complete (and there are similar generation devices listed)?
Thanks again,
Rob.
p.s. Apologies for only now getting the hang of reply/quote in the new forum
Yes, I said 23.05 factory image so it's an OpenWrt factory image
It is. But each devices react differently to nmrpflash. Try different timings between launching the command and powering on the device. Also wait about 1min after the success message. Experience tells me that the flashing is still in progress even if the message is displayed, and rebooting too soon leads to a corrupted flash.
Just wanted to report back: nmrpflash from Win 10 with npcap 1.60 worked a treat. (I gave it a solid 180 seconds after sending the flashing before I rebooted.)
I installed npcap 1.60 (from the .exe installer, all releases available here).
Downloaded the win32 binary for nmrpflash from here and the '-factory' image for WNDR3700v4 from the repo here.
I set a static IP for the ethernet interface on the laptop (after flashing, the router will come up in 192.168.1.1, so 192.168.1.101 makes life slightly simpler), and followed the (simple) instructions for nmrpflash:
NOTE: Check these instructions yourself at the nmrpflash GitHub page. (I'm not responsible for something going wrong.)
i) Start with the router powered off.
ii) Execute with -L to find the target interface.
iii) Execute the flash command, when you see 'Waiting for Ethernet', power on the router.
iv) Following badulesia's advice - wait some extra time after 'Reboot your device' message (I gave it three minutes) before power cycling.
v) Give the router a few minutes to boot. Relax.
vi) Login (root, no pass) at 192.168.1.1.
vii) Do a little dance.
nmrpflash is an outstanding tool that saved my a$$ many times, especially for this device. For such a huge upgrade (17 to 23) it may be the best and fastest solution.
Many packages have changed since the initial release of 23.05.2. You may consider creating a custom build which will have up-to-date packages.
), but it seems that just can't cope with newer images.
