From last 2-3 year I upgrage my WNDR4700 not so often, but after long long time when I apply "wndr4700-squashfs-sysupgrade" It wont reboot, And green power led keeps on blinking.
this happen 3-4 times with me, what am I doing wrong.
Since debricking need to install stock > then new openwrt,
last rom was some 19.7
new is 23.xyz
or direct jumping is not allowed ?
Did the system warn you about the upgrade (requiring you to "force" the process), or did it allow without question?
And did you keep your settings or did you allow them to reset to defaults when you performed the upgrade?
No, it did not.
I have saved configuration. Since I know from past experiences that sysupgrade failed restore completely.
No you did not... what? Force the upgrade? reset to defaults? keep settings?
Probably best if you tell us what you did do, and what, if any, messages you saw in the process.
Yes there was msg, will is as usuall
listed like
file name
md5
etc etc
but nothing noticeable
This is certainly a problem. Keeping settings is not supported when you are upgrading across more than 1 version.
Hopefully you can recover from this using failsafe mode.
https://openwrt.org/docs/guide-user/troubleshooting/failsafe_and_factory_reset
Assuming you can regain access this way, you'll need to reset your router to defaults and then reconfigure from scratch. Once you get in, you'll issue the following command to reset to defaults:
firstboot -y && reboot
got this,
C:\Users\kdm>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=128
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Reply from 192.168.1.1: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
C:\Users\kdm>
but hard to get promt.
C:\Users\kdm>ssh 192.168.1.1
ssh: connect to host 192.168.1.1 port 22: Connection timed out
so I chose debrick with stock (https://kb.netgear.com/000059633/How-do-I-upload-firmware-to-my-NETGEAR-router-using-a-TFTP-client-on-Microsoft-Windows) > install new openwrt
but this time I will try to push
https://mirror-03.infra.openwrt.org/releases/24.10.0-rc7/targets/apm821xx/nand/openwrt-24.10.0-rc7-apm821xx-nand-netgear_wndr4700-squashfs-factory.img
You should use 24.10.0 (official release) instead of the release candidate.
The wndr4700 will require a change in the boot command to get it to work with new releases. Unfortunately that can only be done using serial / UART. See the following post with details on the procedure:
unbricking using stock
192.168.1.1
Debricked ok
v24 squashfs-sysupgrade failed
v23 squashfs-sysupgrade failed
also tesed:
| openwrt-24.10.0-apm821xx-nand-netgear_wndr4700-squashfs-factory | not working | uging tftp put | |
|---|---|---|---|
| openwrt-21.02.7-apm821xx-nand-netgear_wndr4700-squashfs-factory | working | uging tftp put | |
| openwrt-19.07.9-apm821xx-nand-netgear_wndr4700-squashfs-factory | working | uging tftp put |
and 21 -> 23 caused
squashfs-sysupgrade 23 boot loop
boots loop every 30 +/-2sec
now stucked? after updateing from 21 to 23 .
Stuck in bootloop (30s) what to do? any help? without serial would be appriciated ?
Any upgrade to 22.03 or newer will need a new boot command that does require serial unfortunately. In theory it would be possible to set uboot environment from a running system but this only works if the exact location where the environment is saved is known and defined properly.
Oops, but how to unbrick now?
It's in bootloop (~30s)?
Woked. Unbricked
https://github.com/jclehner/nmrpflash and https://npcap.com/dist/npcap-1.75.exe helped
C:\c>nmrpflash.exe -L
net15 192.168.1.10 d4:xx:yy:34:bf:77 (Ethernet)
C:\c>nmrpflash.exe -i net15 -f openwrt-21.02.7-apm821xx-nand-netgear_wndr4700-squashfs-factory-tftp-put-ready.img
Advertising NMRP server on net15 ... |
No response after 60 seconds.
Bailing out.
Reboot WNDR4700 and press and hold reset button
C:\c>nmrpflash.exe -i net15 -f openwrt-21.02.7-apm821xx-nand-netgear_wndr4700-squashfs-factory-tftp-put-ready.img
Waiting for Ethernet connection (Ctrl-C to skip).
Warning: IP address marked as deprecated.
Advertising NMRP server on net15 ... -
Received configuration request from 20:e5:2a:55:be:18.
Sending configuration: 10.164.183.253/24.
Received upload request: filename 'firmware'.
Uploading openwrt-21.02.7-apm821xx-nand-netgear_wndr4700-squashfs-factory-tftp-put-ready.img ... OK (9437313 b)
Waiting for remote to respond.
Remote finished. Closing connection.
Reboot your device now.
refrence1:https://community.netgear.com/t5/Nighthawk-Wi-Fi-5-AC-Routers/Router-seems-to-be-stuck-in-boot-loop/td-p/2082818
refrence2:https://github.com/jclehner/nmrpflash
I have absolutely no WNDR4700 (nor apm821xx target) expertise, so nothing concrete to offer to you...
But your device seems to need some modifications before the newest OpenWrt can be applied.
E.g. this commit from @chunkeey seems to indicate need for serial connection:
You might look into other device-specific commits too: https://github.com/search?q=repo%3Aopenwrt%2Fopenwrt+wndr4700&type=commits&s=committer-date&o=desc