r7000 bricked after update

[Bart83]

Hello,

While updating the firmware to the latest version. The router stopped responding and now I am unable to access it or reload firmware. The power button is white and flashing. What can i do? update en then is broken thats not correct.

[Bart83 · Accepted solution]

Thank you, He is working:D

[jbae843123]

I'm sorry to hear that...

I updated to version 64 a couple of weeks ago, and I noticed many issues, but it did not brick my router.

When I just checked the release note of version 64, it had "Last modified" of 3/26/2019, instead of 1/??/2019.

Maybe they re-released the firmware under the same version number, and it was a bad one?

To fix the issue, try factory reset? or check this link out.

https://community.netgear.com/t5/Nighthawk-WiFi-Routers/SOLVED-Steps-for-debrick-unresponsive-R7000-...

I hope everything works out

[Bart83 · Accepted solution]

Thank you, He is working:D

[michaelkenward]

A more recent explanation of the process is here:

How to upload firmware to a NETGEAR router using Windows TFTP | Answer | NETGEAR Support

[buster_petaluma]

Got an email recommending update. I used the Netgear App to update. Click, Download,Install. Easy. But, the power light blinked constantly white. waited 35 minutes for the hair-ball to clear. Didn't. All devices are dark. No internet, ROUTER BRICKED. Mac OSX environment.

Tried every idea I had, tried ideas online and here (had to use my phone).

Had to go buy a new router (imperiative that I get back in business now). Not happy having to replace my 2 yr old R7000. Hopefully the new AC3000P lasts longer.

[antinode]

> [...] Tried every idea I had, tried ideas online and here (had to use
> my phone). [...]

   Think for a moment about how little useful unformation that
non-description conveys to the non-psychics in your audience.

> [...] But, the power light blinked constantly white. [...]

   You may be a candidate for the TFTP recovery scheme.  See, for
example:

      https://community.netgear.com/t5/x/x/m-p/1622096

> [...] waited 35 minutes [...]

   I wouldn't expect time to cure a flashing power indicator.

> Mac OSX environment.

   The Mac-specific details are covered in that cited thread (and links
therefrom).

> Had to go buy a new router [...]

   Rehabilitating the old one as a spare might be useful someday, then.

[buster_petaluma]

Rehabilitating the dead R7000 is not possible. It will not communicate with my devices/computers.

It does not even send out a network signal - it can not be "seen". It does not show up in Networks list. It is just dead/bricked.

Hope no one else experiences this.

[michaelkenward]

---

@buster_petaluma wrote:

Rehabilitating the dead R7000 is not possible. It will not communicate with my devices/computers.

It does not even send out a network signal - it can not be "seen". It does not show up in Networks list. It is just dead/bricked.

Hope no one else experiences this.

---

I see no evidence in your messages that you are following the correct procedure for TFTP.

What is this "network signal" that you expect to see?

No, it won't show up in a Networks list, whatever that means. The fact that you are even looking there suggests that you are not following the instructions:

How to upload firmware to a NETGEAR router using Windows TFTP | Answer | NETGEAR Support

Go through things slowly, one a step at a time and tell people where it isn't working for you and what error messages you see.

You might also do better to start a new discussion rather than hitching a ride on the end of one started by someone who has fixed their problem. They have marked this is SOLVED so it is unlikely that anyone from Netgear will see your message. They are too busy firefighting new challenges.

[antinode]

> Rehabilitating the dead R7000 is not possible. [...]

   "I couldn't do it, so it's impossible."

   I'd guess that ranting in multiple old threads won't help much more
than ranting in one old thread.

> Hope no one else experiences this.

   I agree.  Trying to deal with a completely useless problem
description (scattered across multiple threads) certainly _is_ trying.

[buster_petaluma]

Thanks for the snarky response. Not helpful, at all

[antinode]

> Thanks for the snarky response. [...]

   You're welcome.

> [...] Not helpful, at all

   So, just like "Tried every idea I had" and "is not possible", then?

   As usual, showing actual actions with their actual results (error
messages, LED indicators, ...) can be more helpful than vague
descriptions or interpretations.  Or repetitive, broadcast rants.