NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
fire_ash
May 10, 2017Aspirant
R7000 AC1900 Unresponsive After Firmware Upgrade
Hello All, Unfortunately, now I have the reason to ask for help. I have recently logged in into my router, which was functioning without any problem since the purchase, to discover that the FW U...
- May 10, 2017
I haven't tried myself, but here is a prior post. https://community.netgear.com/t5/Nighthawk-WiFi-Routers/SOLVED-Steps-for-debrick-unresponsive-R7000-softbricked/td-p/414034
If you look at openrouter.com, there are plenty of people who brick their router by mistake when flashing to open source firmware, so they also have steps on trying to recover. I think it is possible to do it w/o using a serial USB cable, but I have never had to try it myself. Maybe also try the hard reset (stick a paper-clip in the hole for 6 seconds).
Good luck!
fire_ash
May 10, 2017Aspirant
AhnFire, Thank you! Having adjusted slightly your referenced solution, it did work (download FW -> tftp to router -> voila)! Interestingly all the settings remained unchanged, so I didn't have to re-set anything. Must have been interrupted firmware load, which interestingly completely ignores hard reset :/
Anyway, big thanks for help.
michaelkenward
May 11, 2017Guru - Experienced User
fire_ash wrote:Interestingly all the settings remained unchanged, so I didn't have to re-set anything.
If a firmware flash does take, then it is often a good idea to reset to factory defaults. Especially of you see any post-flash problems. In this way you don't carry over settings that are not compatible with the new firmware.
In future, this might be useful:
How to upload firmware to a NETGEAR router using TFTP | Answer | NETGEAR Support
No need to resort to possibly dodgy third party trickery.
- fire_ashMay 13, 2017Aspirant
Thanks Michael.
Actually, I did try mentioned by you method, but the tftp utility was always returning error half way through upgrade. At the same time, when I used standard win utility, it worked. Odd.