NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
De-bricking EX6200V2 after failed firmware update
So out of the blue I decided to update my EX6200V2 firmware and for some reason the range extender died after the post-flash reboot. I tried resetting it but it doesn't work and I also tried to the tftp guide here (https://kb.netgear.com/000059633/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP-client) but I can't get the tftp to connect. It seems that the extendered has not entered TFTP mode, but it can't start the normal firmware either. When the extender boot, LEDs would blink signaling that it is initializing but it would end up with constant amber light on the "Device to Extender" LED, which, according to the manual, signals "The extender firmware is updating."
Any suggestion how I can restore it?
> [...] tried to the tftp guide here [...]
I'd use the command-line TFTP client program which comes with your
computer's OS. I'd expect better error messages that way, at least.https://community.netgear.com/t5/x/x/m-p/1622096#M102004
(For Windows: https://kb.netgear.com/000059634/ )
> [...] I can't get the tftp to connect. [...]
"can't" 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 (commands) with their actual results (error
messages, LED indicators, ...) can be more helpful than vague
descriptions or interpretations.
The TFTP recovery scheme is a multi-step procedure which offers
multiple opportunities for user input, hence user error. By itself,
saying that you tried it doesn't say much. Especially when using a
command-line program, copy+paste is your friend.For example, I know nothing, but I wouldn't bet that an extender
would have the same default-when-crippled LAN IP address as a router.
("192.168.1.250", perhaps?) Timing of the "put" command in the
reset/start-up sequence might matter, too.
2 Replies
> [...] tried to the tftp guide here [...]
I'd use the command-line TFTP client program which comes with your
computer's OS. I'd expect better error messages that way, at least.https://community.netgear.com/t5/x/x/m-p/1622096#M102004
(For Windows: https://kb.netgear.com/000059634/ )
> [...] I can't get the tftp to connect. [...]
"can't" 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 (commands) with their actual results (error
messages, LED indicators, ...) can be more helpful than vague
descriptions or interpretations.
The TFTP recovery scheme is a multi-step procedure which offers
multiple opportunities for user input, hence user error. By itself,
saying that you tried it doesn't say much. Especially when using a
command-line program, copy+paste is your friend.For example, I know nothing, but I wouldn't bet that an extender
would have the same default-when-crippled LAN IP address as a router.
("192.168.1.250", perhaps?) Timing of the "put" command in the
reset/start-up sequence might matter, too.Thanks so much. This guide you sent is much better. The guide I found didn't mention the fact that I need to hold RESET when booting to force the extender into recovery mode for TFTP flash. I have now restored it.