[ndsinister]

Hi,

I own a Netgear Nighthawk R7000P that had Kong's dd-wrt firmware from May 2018. Today I decided to update it to the latest so I downloaded dd-wrt.v24-K3_AC_ARM_R7000P.bin and installed it via the web gui.

Installation was successful but my 5Ghz wifi wasn't working. I followed a post from this forum where sombody recommended to execute `erase nvram && reboot`. Unfortunately I missed the part that said `from command line` (which apparently had a hidden meaning `from telnet/ssh ONLY`) and I executed it from the web gui.

Since then my router is stuck in a boot loop.
I'm able to get ping result but for a few seconds. Here's a snippet:

ping: sendto: No route to host
Request timeout for icmp_seq 1876
ping: sendto: No route to host
Request timeout for icmp_seq 1877
ping: sendto: No route to host
Request timeout for icmp_seq 1878
ping: sendto: No route to host
Request timeout for icmp_seq 1879
ping: sendto: No route to host
Request timeout for icmp_seq 1880
Request timeout for icmp_seq 1881
64 bytes from 192.168.1.1: icmp_seq=1882 ttl=100 time=0.926 ms
64 bytes from 192.168.1.1: icmp_seq=1883 ttl=100 time=1.153 ms
64 bytes from 192.168.1.1: icmp_seq=1884 ttl=100 time=0.691 ms
64 bytes from 192.168.1.1: icmp_seq=1885 ttl=100 time=0.718 ms
64 bytes from 192.168.1.1: icmp_seq=1886 ttl=100 time=0.610 ms
64 bytes from 192.168.1.1: icmp_seq=1887 ttl=100 time=0.756 ms
64 bytes from 192.168.1.1: icmp_seq=1888 ttl=100 time=0.562 ms
64 bytes from 192.168.1.1: icmp_seq=1889 ttl=100 time=0.555 ms
64 bytes from 192.168.1.1: icmp_seq=1890 ttl=100 time=0.536 ms
64 bytes from 192.168.1.1: icmp_seq=1891 ttl=100 time=0.780 ms
64 bytes from 192.168.1.1: icmp_seq=1892 ttl=100 time=0.552 ms
64 bytes from 192.168.1.1: icmp_seq=1893 ttl=100 time=0.758 ms
64 bytes from 192.168.1.1: icmp_seq=1894 ttl=100 time=0.769 ms
64 bytes from 192.168.1.1: icmp_seq=1895 ttl=100 time=0.747 ms
Request timeout for icmp_seq 1896
Request timeout for icmp_seq 1897
Request timeout for icmp_seq 1898
Request timeout for icmp_seq 1899
Request timeout for icmp_seq 1900
Request timeout for icmp_seq 1901
Request timeout for icmp_seq 1902
Request timeout for icmp_seq 1903
Request timeout for icmp_seq 1904
Request timeout for icmp_seq 1905
Request timeout for icmp_seq 1906
Request timeout for icmp_seq 1907
Request timeout for icmp_seq 1908

I followed the post of troubleshooting bricked router and was relieved to read that it may not be bricked due to ping response ttl 100. I tried to upload the firmware following the tftp guide for macos with the following commands pasted to tftp console while ping is successful:

connect 192.168.1.1
binary
rexmt 1
timeout 60
put dd-wrt.v24-K3_AC_ARM_R7000P.bin

but all I get (after 60 seconds) is "unreachable"
I tried a few times in different time windows and it shows the same error all the time.

When the router boots up, the power led is solid orange (no blinking) then a fter a few seconds the rightmost led lights up solid white (no blinking) and after a few seconds it turns off. Then few more seconds later and the power led goes off and right after that all the leds light up except the 2 rightmost ones for a couple of seconds and then the whole thing repeats.

I tried hard reset (WPS button) by following the instructions here: https://wiki.dd-wrt.com/wiki/index.php/Hard_reset_or_30/30/30#Hard_Reset_on_ARM_and_other_newer_routers but that didn't do anything. The power led didn't blink as written in the instructions...

I'd be glad for any help I can get.
(no jtag nor serial at my disposal)

[ndsinister]

OK. Finally managed to recover it after hours and hours of tries and googling the net.

Following https://forum.dd-wrt.com/phpBB2/download.php?id=42046
instructions and specifically NMRPFLASH tool saved my router.

[Per Yngve Berg]

This topic belongs in the Broadcom forum.

[Dr_K]

Congratulations on finding a fix for your situation on your own....especially on the same day you asked for help...?

That is usually the best way...that'll stick in your head for issues down the road


Though maybe next time do a little more reading before blindly running commands...

Not only as you later figured out that you should not run them through the webif/gui...

Also that command you ran, when followed by a reboot....will now write back most of the nvram variables from ram before the reboot...

Aparently in your router's case...not enough of them to successfully boot back up

The current command (from at least 04/18 ) is now "nvram erase"...

Good luck moving forward

[jtcsilva]