NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Frimware corrupted during update
My NightHawk R7000 failed while updating the firmware. Now the power light blinks white (firmware corrupted) and I cannot access the router.
I have cabled the router directly to my computer and changed the computer's IPv4 settings to
IP: 192.168.1.10
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.1
The IP address 192.168.1.1 cannot be pinged from the computer. I even tried the suggestion to run 'ping 192.168.1.1 -t' in one command prompt window, have the 'tftp 192.168.1.1 put R7000-V1.0.9.88_10.2.88.chk' command in a second command window ready to execute while powering on the router and holding down the reset button.
The only ping response I received was 'PING: transmit failed. General failure.' so I could never execute the tftp command.
Are there any other options for rebuilding the corrupted firmware, or at least getting the router to respond to an IP address?
CWood wrote:
....I've come to a realization that it is a 'crap shoot' as to whether it can ever be resolved
I reckon that is an accurate scientific description of the TFTP process.
But persistence can pay off.
Netgear's instructions could do with an update. For example, enabling the native TFTP client in Windows is better than faffing around with extra software.
I'd do all this with a single wired connection between a PC and the router. That seems to be what you are doing.
It can also help to track down a video to take you through the process.
2 Replies
I have spent way more time than the cost of a new router trying to fix this. After reading all of the other posts on this topic and trying their suggestions I've come to a realization that it is a 'crap shoot' as to whether it can ever be resolved and I don't want to throw any more good time after a bad router.
I've tried the '10 second regular factory reset' and the '30 second recovery reset' and still the power light blinks white and I cannot access the router using the IP settings from my first post.
I like the router and will probably replace it with the same thing but I won't be doing any suggested firmware updates in the future. (I did this one from a wired connection and still had problems.)
CWood wrote:
....I've come to a realization that it is a 'crap shoot' as to whether it can ever be resolved
I reckon that is an accurate scientific description of the TFTP process.
But persistence can pay off.
Netgear's instructions could do with an update. For example, enabling the native TFTP client in Windows is better than faffing around with extra software.
I'd do all this with a single wired connection between a PC and the router. That seems to be what you are doing.
It can also help to track down a video to take you through the process.