NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Latest Update Bricked My R8000 Router
The latest firmware update (R8000-V1.0.4.52_10.1.67) bricked my router! I am using the R8000 Nighthawk X6 AC3200 Smart WiFi Router. I utilized the web interface to update the firmware via a wired ...
There is more severe, recovery reset, that you could try:
- Press reset for 30 seconds
- Keep pressing reset while removing power
- Keep pressing reset for another 30 seconds while apply power
If it works, you may be able to use the usual method to flash the firmware again.
Download the latest firmware for your device – or an older version if that is what you want – and read the Release Notes for how to install it.
If that fails, you are into TFTP country.
How to upload firmware to a NETGEAR router using Windows TFTP | Answer | NETGEAR SupportThis also explains how to tell Windows to use TFTP on your PC.
This isn't the easiest operation, so if you are forced to use it, you could try a web search to find videos that guide you through the process.
The good news is that TFTP has rescued many a dead device.
Tried the TFTP method and I still can't figure out a way to unbrick it. Tried the 30/30/30 method and that doesn't work either. Mine was also bricked by the new firmware update.
Here is the error I get in CMD:
C:\Users\zohnw\Desktop>tftp -i 192.168.1.10 put R8000-V1.0.4.52_10.1.67.chk
Connect request failed
> Tried the TFTP method [...]
First, as a general rule, start your own thread for your own
(different) problem.
The TFTP recovery scheme is a multi-step procedure which offers
multiple opportunities for user input, hence user error. By itself,
saying that you "Tried" it doesn't say much. Especially when using a
command-line program, copy+paste is your friend.
> C:\Users\zohnw\Desktop>tftp -i 192.168.1.10 put R8000-V1.0.4.52_10.1.67.chk
> Connect request failed
The IP address there should be that of the router, "192.168.1.1", not
that of your computer, "192.168.1.10". Otherwise it looks ok.
Your computer probably isn't running a TFTP server, so specifying
that ".10" address should explain the problem. (Only one way to find
out.) Reading more carefully whichever instructions you're trying to
follow might be helpful.