NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Netgear NIghthawk R8000 Bricked after update
Hello everyone, yesterday i decided to go ahead and update my router after I saw the notification for the update, I decided to go an update it and it starts to flash colours and not update, so after 15 minutes of watching this loop I decidd to check the wiki and saw somehthing about TFTP, I decided to start working, the tftp wasn't working so I assumed that I was doing something wrong, so I decided to set-up a ping command to see if the router was connecting, and it seems like the router is reachable for only 5 or so seconds then it stops working, i noticed if I press the reset button at startup it loops and the router is reachable 5 seconds at a time but I am still unable to upload the firmware as I keep on getting a time-out any suggestions of what I can do?
Try nmrpflash:
https://github.com/jclehner/nmrpflash
3 Replies
Try nmrpflash:
https://github.com/jclehner/nmrpflashSo I tried that and when nmrp said I should reboot the device the power switch was blinking amber and when I rebooted it I was still greeted with red amber on power it just boots up with all leds on then goes to this any help?
tftp and nmrpflash are sensitive to timings. You have to execute the command when its in the window of accessibility. Sometimes you have to try it a few times.
.
are you on windows? if so, follow this guide
https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP
just make sure you enable tftp
https://www.thewindowsclub.com/enable-tftp-windows-10
and here's a video walk through using a tftp client. Use the built in one for windows 10 though. the video is more of an example of how its done.
https://www.youtube.com/watch?v=R9DLrLQrpaw
and if that doesn't work, you can try nmrpflash again
https://github.com/jclehner/nmrpflashagain, you might have to try several times.
The R8000 has had some firmware issues with users that were on the .50 firmware versions. You used to have to send it in to get it repaired but this user figured out how to get it to take.
