NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000 bricked during firmware update to 1.0.9.18
While updating the firmware to the latest version (1.0.9.18). The router stopped responding and now I am unable to access it or reload firmware. The power button is white and flashing. I have tried t...
I have successfully recovered my router, with the help of an old post by ghoffman (along with many other): under the thread "[SOLVED] Steps for debrick unresponsive R7000 (softbricked)"
The steps as written:
5.confirm the cfe is waiting for firmware by 'ping 192.168.1.1' a 'ttl=100' response is what you are looking for
6. use 'tftp -i 192.168.1.1 put factory.trx' to upload you newly created image
7. wait 2-3 minute for a couple reboots.This is how I implemented these steps:
1. Open the command window and change the directory to my desktop (this is where the dowloaded firmware is located)
2. Type the command: ping 192.168.1.1 a ttl=100
3. Open a second command window and type: tftp -i 192.168.1.1 put 1.0.9.18.chk
4. Turn on the router (no need to hold reset button).
5. Start the ping comand in the first window.
6. When the ttl response = 100, start the tftp command in the second window.
7. This took a few minutes. When it is complete the router reset.
There are many other steps that are needed to get to this point, but these are the critical steps that I needed to get my pc to connect to the router and load the firmware.
Thank you for all the responses.
All great pieces of advice, but, unfortunately all are too late. The router is not having anything to do with the outside world. I have no connection to the router via a browser. I even tried to reset the router to default settings, but I still cannot access it using a browser.
Check to see if NG has a recovery mode to load the FW back on fully. Might contact NG support and ask about this.
> [...] now I am unable to access it or reload firmware.
"unable" is not a useful problem description. It does not say what
you did. It does not say 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.
> The power button is white and flashing.
That sounds receptive (to TFTP).
> I have tried tftp through windows, but I get "connect request failed"
> as a response after about a minute.
Plenty of details missing from that. Which "tftp through windows"?
Did you configure the Windows system with a suitable static IP address
(and related parameters)? What was the actual TFTP command? Are you
following some well-defined TFTP procedure, or just fiddling around?
One such:
https://kb.netgear.com/22688/
I know nothing, but some reports here suggest that, on Windows, the
built-in command-line TFTP client works better than the "tftp2.exe"
program shown there.
> [...] I still cannot access it using a browser.
An actual error message would beat "cannot access", but if the power
LED is flashing, then I'd expect a web browser to have little chance.
Check to see if NG has a recovery mode to load the FW back on fully.
Recovery mode doesn't quite get that far, which would be nice, but there is a more thorough reset that does more than the usual "pinhole" trick.
Turn off the device > insert something into reset pinhole > turn device on and wait (about 30 seconds) for the power LED to start fast flashing.
Here's a variation on the theme:
- Press reset for 30 seconds
- Keep pressing reset while removing power
- Keep pressing reset for another 30 seconds while apply power
I have used this to do "major surgery" on a router's firmware.
