r7000p firmware failure

[66forest]

I tried to update my R7000P firmware version 1.3.1.64 via the Netgear rounter management website. It didn't work

and now the router does nothing except blink one amber light.

I tried resetting the router. Nothing changed.

I then tried to download the firmware directly from the netgear website and update using

the Windows TFTP per Netgear's recommendation. I unzipped the file and all I see are release notes

and a file called R7000P-V1.3.1.64_10.1.36.chk. Is this file the correct one or is it too damaged?

[antinode]

> [...] the router does nothing except blink one amber light.

   _Which_ "one amber light"?  Power?

> [...] using the Windows TFTP per Netgear's recommendation.

   Probably a reasonable course, but a pointer to the actual
instructions which you are following might be good, too.

> [...] I unzipped the file and all I see are release notes and a file
> called R7000P-V1.3.1.64_10.1.36.chk. [...]

   That's what I'd expect.

> [...] Is this file the correct one or is it too damaged?

   It's probably fine, but if you ask _Windows_ to open it (by, say,
double-clicking on it, instead of following the actual TFTP recovery
instructions), then you can expect to get some misleading/useless error
messages about it.

[IrvSp]

The .chk is the f/w file you should point TFTP to, usually the .chk file is in the same folder as TFTP is as well.

Did you do that? If so, what happened? Any error?

[66forest]

Thanks for the reply. My replies to your questions are in italics.

---

@antinode wrote:

> [...] the router does nothing except blink one amber light.

   _Which_ "one amber light"?  Power?

yes.

> [...] using the Windows TFTP per Netgear's recommendation.

   Probably a reasonable course, but a pointer to the actual
instructions which you are following might be good, too.

Here's what I used.

https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP

The installation using this method also failed.

> [...] I unzipped the file and all I see are release notes and a file
> called R7000P-V1.3.1.64_10.1.36.chk. [...]

   That's what I'd expect.

> [...] Is this file the correct one or is it too damaged?

   It's probably fine, but if you ask _Windows_ to open it (by, say,
double-clicking on it, instead of following the actual TFTP recovery
instructions), then you can expect to get some misleading/useless error
messages about it.

---

[66forest]

---

@IrvSp wrote:

The .chk is the f/w file you should point TFTP to, usually the .chk file is in the same folder as TFTP is as well.

Did you do that? If so, what happened? Any error?

Thanks for the reply. Yes, this method failed. I used method described in this article.

https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP

---

[antinode]

> The installation using this method also failed.

   "failed" 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.