R7000-V1.0.9.32_10.2.34 update corrupt, cannot re-install even with recovery procedure

[Duran]

Hi there.

I recently launched a firmware update frmo the web interface (did it several times without any issue).

This time the process did not complete properly and the power led started flashing, indicating a "corrupt firmware"

I tried several things, from reboot to factory reset. Still doesn't work.

I then applied the recovery procedure sending the firmware by TFTP

https://kb.netgear.com/19841/Reinstall-the-firmware-on-a-router-without-the-setup-CD-recovery-tool

Still impossible to re-install. I get an "Error of type 50 occured".

Tried both V1.0.9.28_10.2.32 and V1.0.9.32_10.2.34

Same error message.

Can anyone please help me re-install a valid firmware on my R7000 ?

Many thnx

[antinode · Accepted solution]

> Yes I can ping 192.168.1.1 [...]

   That all sounds good.

> [...] The above discussed procedure (link) refers to a TFTP client for
> the mac which I downloaded. [...]

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

   I'd try the command-line TFTP client program.  At the very least, its
error messages might convey more useful information than "type 50".

[antinode]

> [...] I then applied the recovery procedure sending the firmware by
> TFTP [...]

   That's a very terse description of a multi-step procedure with many
variables.  One example (of many): Which file did you try to send to the
router?

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

[Duran]

Sorry for the missing details.

I connected with a cable form my mac.

I have been able to set a static ip address and the corresponding subnet mask.

The connection to the router worked properly (password) and the transfer started normally and lasted quite some time before I got the error message.

I tried both following files : R7000-V1.0.9.32,10.2.34.chk and R7000-V1.0.9.28,10.2.32.chk and it ended up the the "Error: An error of type 50 occurred" message.

Any suggestion?

[antinode]

> [...] I have been able to set a static ip address and the
> corresponding subnet mask. [...]

   What, exactly, did you set where?  Does a command like "ping
192.168.1.1" get a response from the router?

> The connection to the router worked properly (password) [...]

   What, exactly, does "The connection to the router" mean to you?  Were
you using some downloaded TFTP client program or the built-in
command-line TFTP client program?  

   "(password)"?  The first "T" in "TFTP" is for "Trivial".  So far as I
know, TFTP does not use a password.  That's part of "Trivial".

> I tried both following files : [...]

   A ".chk" file is the right type.

[Duran]

Yes I can ping 192.168.1.1 (set my own IP to 192.168.1.95 and subnet mask to 255.255.255.0)

The above discussed procedure (link) refers to a TFTP client for the mac which I downloaded.

To connect, you provide the IP, password (used the default factory password of the router, as I had done a factory reset) and a file to upload (see attached screenshot)

[antinode · Accepted solution]

> Yes I can ping 192.168.1.1 [...]

   That all sounds good.

> [...] The above discussed procedure (link) refers to a TFTP client for
> the mac which I downloaded. [...]

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

   I'd try the command-line TFTP client program.  At the very least, its
error messages might convey more useful information than "type 50".

[Duran]

Didnt' have time to try before the w-e but it worked out fine.

Many thanx and BR