This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
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."
"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.
"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.
Re: De-bricking EX6200V2 after failed firmware update
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.
