NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Firmeware upgrade does not coplete
I just attempted to upgrade the firmware in my router, but after 45 minutes, it was still not complete. The power LED is still blkinking.
I tried to power cycle it, but to no avail. It will not boot.
How do I get around this problem?
I went out and bought a Linksys to replace the "broken" Netgear.
8 Replies
> I tried to power cycle it, but to no avail. It will not boot.
What does the Power LED do now? You may be a candidate for the TFTP
recovery scheme. See, for example:
https://community.netgear.com/t5/x/x/m-p/1533866#M87578The power light is still flashing. I can't use the tftp hack because I cannot access the router at all. It does not boot either the new or the old image. So, I can't http to it. It's not coming up at all.
Thanks for the suggestion though.
There is support material, including a manual, for the R7000 somewhere at the end of this link:
>>>> R7000 | Product | Support | NETGEAR <<<<
If the regular "factory reset" does not work, try getting it into "recovery mode":
- Press reset for 30 seconds
- Keep pressing reset while removing power
- Keep pressing reset for another 30 seconds while apply power
If that works you should see a flashing white power LED. You may then be able to load the new firmware.
Neither, router reset, nor recovery mode suggested works. It seems like the firmware got wiped out during the upgrade. I cannot get a response from it at all. ping 192.162.1.1 times out, http://routerlogin.net also times out.
It seems like what I have right now is a very light weight door stopper.
> [...] I can't use the tftp hack because I cannot access the router at
> all. It does not boot either the new or the old image. So, I can't
> http to it. It's not coming up at all.
Read the TFTP instructions again? You don't need to "http to it".
The whole idea of the TFTP recovery scheme is that it can work when
normal (HTTP) access does not work.
> [...] I cannot get a response from it at all. ping 192.162.1.1 times
> out, http://routerlogin.net also times out.
How is your (unspecified) computer configured when you do that "ping"
test? If the router is not operating normally, then you'd need to
configure the computer with a suitable static IP address, as explained
in the Netgear TFTP KB article.
If the router is not operating normally, then any
"[www.]routerlogin.{com|net}" name can be expected to fail.
Hi jserpa,
Contact support to better isolate the issue for possible hardware problem.
Regards,
Blanca
Community TeamI went out and bought a Linksys to replace the "broken" Netgear.
