NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Andre_BR
Nov 05, 2018Aspirant
Night Hawk R7000 upgrade failure
I have a Netgear Nighthawk R7000 (v1) and tried to upgrade the firmware, after receiving a notification in the Web UI, from V1.0.9.34_10.2.36 to the latest one, V1.0.9.42_10.2.44. I've used the web i...
- Nov 05, 2018
> [...] the power LED kept blinking alternating blank and amber [...]
You seem to be a candidate for the TFTP recovery scheme. See, for
example:
https://community.netgear.com/t5/x/x/m-p/1622096
> [...] I've followed the process described at [...]
> [...] when I rebooted, and then started the TFTP upgrade process, it
> failed [...]
Not a useful description of what you did, or what happened when you
did it. As usual, showing actual actions with their actual results
(error messages, LED indicators, ...) can be more helpful than vague
descriptions or interpretations.
Andre_BR
Nov 05, 2018Aspirant
Hi, thank you for the prompt response.
I've tried to describe what I've done, with references to the step-by-step guides I've followed, assuming copy and pasting what was there was not needed. I suppose I was wrong, so I am trying something different in this post.
This is the sequence of events, following what was suggested at the link you've recommended (https://community.netgear.com/t5/x/x/m-p/1622096, which points to https://kb.netgear.com/000059633/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP-client, so, I've followed the instructions in this link):
1) Downloaded and installed Mac TFTP client from http://download.cnet.com/MacTFTP-Client/3000-18508_4-5707.html
2) Booted netgear device pressing the reset button and waited 5 minutes;
3) Connected the notebook to the netgear device;
4) Configured static IP on my macbook:
- IP address: 192.168.1.10
- Netmask: 255.255.255.0
- Gateway: 192.168.1.1
5) unplugged any other connections from netgear, besides macbook;
6) Pinged the netgear ip address 192.168.1.1, with success:
$ ping -c5 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=100 time=1.325 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=100 time=1.323 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=100 time=1.054 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=100 time=1.022 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=100 time=1.012 ms
--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.012/1.147/1.325/0.145 ms
7) Opened the TFTP client and filled the fields with:
- Address: 192.168.1.1
- Password: password
- File: (selected the firmware file R7000-V1.0.9.42_10.2.44.chk, unzipped from downloaded file from netgear.com - md5 = 2bfd8e25bbcbc7ffa11374425a1d9a8a)
8) Turned netgear off and waited 10 seconds;
9) Waited the power led transition from amber to a flashing white color;
10) Pressed the button send on the TFTP client;
11) Starting the transmission of the file (63,025 blocks / 32.3MB) and waited;
12) The upload process finished successfully after ~80 minutes
13) After some time (~1min), the power led turned to a solid amber color and stayed this way for a long time
14) Tried to ping 192.168.1.1 had 100% packet loss
15) Changed interface configuration to DHCP, and it got IP 192.168.2.2
16) Tried to ping 192.168.2.1 (default gateway) and got 0% packet loss
17) The power led changed to blank
18) Web UI became accessible again with the same configuration I had before (I guess I did something wrong in the reset process)
19) Firmware version updated to V1.0.9.42_10.2.44
It is working fine now. I hope this description help others,
Thanks
antinode
Nov 05, 2018Guru
> 1) Downloaded and installed Mac TFTP client from [...]
My recommendation was to use the Mac's built-in command-line TFTP
client program. Details like that make a description like "the TFTP
upgrade process" less informative than one might think.
> 7) Opened the TFTP client and filled the fields with:
> - Address: 192.168.1.1
> - Password: password
So far as I know, TFTP doesn't use a password. I have no idea what
that TFTP client program does with any password, which is just one of
the reasons for my recommendation to use the Mac's built-in command-line
TFTP client program.
Otherwise, your procedure looks ok.
> [...] It is working fine now. [...]
Good news. Thanks for the report.