Orbi WiFi 7 RBE973
Reply

Night Hawk R7000 upgrade failure

Andre_BR
Aspirant

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 interface to perform this process, as I always do.


After doing that, the device has never completed the process, and the power LED kept blinking alternating blank and amber colors for more than 10 minutes.


I've waited a little longer, and after 15 minutes I've tried to reboot, which failed, then I've tried to turn it off, wait +10s, and the turn it back on, pressing reset button.


It didn't really bring it back to life, then I've followed the process described at https://kb.netgear.com/27477/How-to-resolve-amber-LEDs-or-a-blinking-power-LED-on-NETGEAR-routers and https://kb.netgear.com/19841/Reinstall-the-firmware-on-a-router-without-the-setup-CD-recovery-tool

 

I could ping the device, but, when I rebooted, and then started the TFTP upgrade process, it failed (I've configured 4 attempts and it failed 4 times).

 

The device was working fine until I've tried the upgrade... Does anyone has another hint on how to try to bring it back to life again?

 

Thanks

Model: R7000|AC1900 Smart WIFI Router
Message 1 of 8

Accepted Solutions
antinode
Guru

Re: Night Hawk R7000 upgrade failure

> [...] 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.

View solution in original post

Message 2 of 8

All Replies
antinode
Guru

Re: Night Hawk R7000 upgrade failure

> [...] 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.

Message 2 of 8
Andre_BR
Aspirant

Re: Night Hawk R7000 upgrade failure

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)

😎 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

 

Model: R7000|Nighthawk AC1900 Dual Band WiFi Router
Message 3 of 8
antinode
Guru

Re: Night Hawk R7000 upgrade failure

> 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.

Message 4 of 8
markharris2000
Initiate

Re: Night Hawk R7000 upgrade failure

I too somehow bricked my R7000/AC1900 with the latest firmware updated. It was lifeless for hours, and I re-powered it.  Now, I see the unit power, Amber on for 45 seconds or so, and then the power led blinks WHITE continuously.  No PING (192.168.1.1) works, 30/30/30 reset doesn't change anything. Still just a blinking WHITE LED.  Am I lost?

Model: R7000|Nighthawk AC1900 Dual Band WiFi Router
Message 5 of 8
antinode
Guru

Re: Night Hawk R7000 upgrade failure

> [...] No PING (192.168.1.1) works, [...]

   I don't know what that means.  Are you offering any (plain-language)
clues as to what you did, and/or what happened when you did it?

> [...] Am I lost?

   I don't know.  Did you read any of the discussion which you've
joined?

Message 6 of 8
markharris2000
Initiate

Re: Night Hawk R7000 upgrade failure

Here's the full story to help anyone provide some insight into what my next steps might be.

 

1. I had a R7000/AC1900 running for about a year running 1.0.9.34. It was working fine. I have it connected to a ARRIS cable modem with a 1 gig uplink, and connected downstream to two 16-port switches, using gig connections. The router was left in its default settings from the factory, with router address of 192.168.1.1

 

2. I received an email from Netgear awhile back suggesting that there was a security concern and I should upgrade to 1.0.9.42. 

 

3. So I went to the NETGEAR website and downloaded the CHK file to my PC.

 

4. My PC is a Windows machine, runnning Version 10, April 2018 build (official). The PC is attached via hardwire to the Gigabit switch and was assigned a static address of 192.168.1.30 and is using a subnet mask of 255.255.255.0  I am using the COMCAST specified DNS entry of 75.75.75.75

 

5. For the past year, this PC has been successfully accessing the internet, with download speeds of 300Meg and Upload of 12Meg

 

6. From the PC, I logged into the router via the CHROME browser to access the R7000's Firmware update screen and pointed to the 1.0.9.42 CHK file and told it to Upgrade. It never came back and my internet was no longer reachable.

 

7. I left it for 2 hours and then I repowered the router itself. The single LED on the left, the POWER LED, is now blinking WHITE which seems to say the firmware is corrupted (according to the Netgear KB here: https://kb.netgear.com/23991/What-are-the-LEDs-and-ports-on-the-front-panel-of-my-Nighthawk-router-c...)

 

7. I plugged a laptop into the cable modem itself and able to establish and confirm successful connection to the internet, which it was, but the R7000 router was now definately offline.

 

8. I went back to my PC (with a static 192.168.1.30 address) which is still hardwired to the switch which is hardwired to the R7000 router and tried to access the router, which was now NOT reachable. I tried the EDGE browser and CHROME browsers by entering "192.168.1.1" into the address bar. Both failed as unreachable. The Router POWER LED is still blinking WHITE

 

9. On the PC, I opened a CMD box, and got the familiar "DOS-Box" window with the "C:User>" prompt.

 

10. I typed "Ping 192.168.1.1" and recieved the notices "Request Timed Out." over and over.

 

11. I also tried typing "tftp -i 192.168.1.1 put 1.0.9.42.chk" and get the "Connect request failed" message

 

12. I typed "Ping 192.168.1.30" (the PC's own address), to confirm the network stack on the PC was operational and got the four success messages. And I even typed "Ping 192.168.1.22" which was the IP address of my HP Printer hardwired to the same switch and received four correct/successful Bytes=32 Time=4ms TTL=64 messages.

 

13. I tried to factory RESET the box. I put a paper clip into the RESET hole and heard the click, held it for 30 seconds, then while holding it removed power and left it unplugged for 30 seconds, and then reapplied power and kept holding the paper clip for another 30 seconds. (Paperclip was pressed for a total of 90 seconds). The box repowered, POWER LED stayed amber for perhaps 30-40 seconds, and then started BLINKING WHITE again.

 

13. Finally I tried opening a CMD box again on my PC and at the "C:User>" prompt, tried "PING 192.168.1.1" from my PC which is still hardwired to the switch which is hardwired to the router and my PC still has a static address of 192.168.1.30. Router is still not reachable and I get "Request Timeout" messages.

 

Does anyone have any suggestion on what I may be able to do now with what appears to be corrupted firmware and no communication to the outside world? I would prefer not to open the box. (I saw one thread about opening the box and using a serial USB cable to access the LINUX console to manually start the TFTPD, but this is unfamiliar territory for me which I would rather avoid if possible).

Model: R7000|Nighthawk AC1900 Dual Band WiFi Router
Message 7 of 8
antinode
Guru

Re: Night Hawk R7000 upgrade failure

> Here's the full story [...]

   That all looks reasonable (and thorough) to me.

> 10. I typed "Ping 192.168.1.1" and recieved the notices "Request Timed
> Out." over and over.

   That's not good.  And if that's true, then I'd expect TFTP to be
doomed.

> [...] The box repowered, POWER LED stayed amber for perhaps 30-40
> seconds, and then started BLINKING WHITE again.

   Does "ping" (or TFTP) do any better/worse during the amber phase
versus the flashing-white phase?

   You might also try this stuff with the R7000 connected to nothing
except (its power adapter and) the Windows system.

Message 8 of 8
Discussion stats
  • 7 replies
  • 4089 views
  • 1 kudo
  • 3 in conversation
Announcements

Orbi 770 Series