NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Netgear X6 R8000 flashing power light after attempted update
Hello! I have spent the last 3 hours trying to figure out how to fix my wifi router. We went to watch a movie, it wasn't loading great, went to the netgear app and saw an upgrade was available. Sta...
> [...] went to the netgear app and saw an upgrade was available.
> Started the upgrade [...]
Many people around here might advise you to shun any Netgear-supplied
app, and use a computer with a wired connection when doing a firmware
update.
> [...] I've been trying to update the firmware using the tftp methods.
> [...]
That's a little vague.
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. As usual, showing actual
actions (commands) with their actual results (error messages, LED
indicators, ...) can be more helpful than vague descriptions or
interpretations. Especially when using a command-line program,
copy+paste is your friend.
> I tried downloading one [...]
Again, a little vague, but seem to have fetched a proper R8000 kit,
and you might have extracted its contents onto your Desktop.
> [...] I tried using the one on windows (after enabling the option).
> [...]
Ok. I prefer that Windows built-in command-line TFTP client program
to any third-party program which you'd need to download.
> On the software I downloaded [...]
I'd avoid it. If for no other reason, the built-in command-line TFTP
client program tends to provide better error messages.
> [...] I followed the steps to set the static IP address and gateway to
> 192.168.1.1, [...]
Read the instructions again? In the router's mostly-dead mode, its
LAN IP address should be "192.168.1.1". Your computer's address should
be set to something similar but different, like, say, "192.168.1.10".
(The gateway address doesn't really matter, but "192.168.1.1" should be
fine for that.)
> disable the wireless [...]
Shouldn't matter. Won't get used.
> C:\Users\Jessica\Desktop>tftp -i 192.168.0.1 put R8000-V1.0.4.68_10.1.75chk
> tftp: can't read from local file 'R8000-V1.0.4.68_10.1.75chk'
Two problems there. First: "192.168.0.1" should be the router's LAN
IP address, "192.168.1.1". ("192.168.0.1" might be right for some DSL
modem+router, but a mostly-dead R8000 should default to "192.168.1.1".)
Second, "R8000-V1.0.4.68_10.1.75chk" should have been
"R8000-V1.0.4.68_10.1.75.chk". The last dot is significant, and that
would be what caused the "can't read" error (assuming that the file's on
your desktop, which should be where that prompt
("C:\Users\Jessica\Desktop>") says that your TFTP program is looking).
> I'm also not able to ping the IP address, it says destination host
> unreachable.
Regarding "not able", see "As usual, [...]", above. Specifying a
wrong address (anyplace) could account for that, too.
You seem to be headed in the right general direction, but with a few
deviations from the true path. Reread, retry. What could go wrong?
Thanks for the reply antinode! I didn't know that its not recommended to use the App, I definitely wont do that in the future. I'm not very good at software/firmware stuff. By not very good I mean I don't know anything about it haha. I spent 3 hours last night researching and trying everything I came across. I've never "pinged" anything, used the command screen, done anything with the IP address or even heard of gateway address. So I apologize if my descriptions arent what you needed. If you're willing/able to help just let me know what you need and I'll supply it.
Sorry to be vague on the TFTP part, I did add a link to the bottom to the two different things I tried, I hope that helped. When you say showing actual commands, do you mean photos of the command screen? I can do that, I did copy and past one of the message I got. I got several as I tried about 15 different times. Next time I'll show them all. I did actually catch that .chk mistake and fixed that.
Can you help me understand what you mean by by the computers IP address vs the routers? I'm at work on my ipad, not the computer so I can't remember exactly(or show pictures at this time) what all the labels were but what I can remember is I went to settings, internet, Ethernet, properties, the something 4 protocol (or something like that), properties, and saw 3 places to put xxx.xxx.xxx.x. In the top one I tried 192.168.1.1 and I also tried 192.268.0.1 in the top spot. The middle spot defaulted to 255.255.255.x (cant remember that last number) and in the bottom I put the same as the top. Are you saying that I need to put 192.168.1.10 on top and 192.168.1.1 in the bottom? If so, which do I type into the command screen?
Also, when it says "desktop" does that mean I need to pin it to the desktop? It was in my downloads folder, could that have been the issue?
Thanks for all your feedback! I'll definitely be trying again tonight when I get home.
> [...] the something 4 protocol (or something like that), [...]
IPv4. https://en.wikipedia.org/wiki/IPv4
> [...] properties, and saw 3 places to put xxx.xxx.xxx.x. In the top
> one I tried 192.168.1.1 and I also tried 192.268.0.1 in the top spot.
> [...]Wrong.
> [...] The middle spot defaulted to 255.255.255.x (cant remember that
> last number) [...]"255.255.255.0" would be the usual.
> [...] and in the bottom I put the same as the top. [...]
Wrong.
> [...] Are you saying that I need to put 192.168.1.10 on top and
> 192.168.1.1 in the bottom? [...]Yup. The top one is the address of the computer's Ethernet
interface. The bottom one is its gateway address. (That would normally
be the router's LAN address, but, in its current crippled condition, the
router can't do any routing, anyway, so that one matters little.)> [...] If so, which do I type into the command screen?
Pretty much what that Netgear KB article says (adjusted for your file
name), the router's (default) address:tftp -i 192.168.1.1 put R8000-V1.0.4.68_10.1.75.chk
> Also, when it says "desktop" does that mean I need to pin it to the
> desktop? It was in my downloads folder, could that have been the issue?That (among other things) would also have caused a "can't read"
error.
You don't need to "pin" anything, but you probably want to _place_ it
there.The Command Prompt shell keeps a current directory ("folder") in its
mind, and the TFTP program inherits it. When you start the Command
Prompt shell (CMD.EXE), it normally uses your home directory as its
current directory. In your case, that was "C:\Users\Jessica". Also, by
default, it displays that current directory in its prompt, hence:
C:\Users\Jessica>Then, you apparently gave it a CD command like:
cd Desktop
which changed its current directory ("CD" -- get it?), and it adjusted
its prompt accordingly:
C:\Users\Jessica\Desktop>
So, when you then gave the TFTP program a simple (relative) file name
("R8000-V1.0.4.68_10.1.75.chk"), it would look for that file in its
current directory. That'd be fine, if you put that file on your
Desktop. If you put it into your Downloads folder
("C:\Users\Jessica\Downloads"), then you'd want to tell the Command
Prompt shell to use _that_ as is current directory. For example:C:\Users\Jessica>cd Downloads
As usual, many things are possible. You might, for example, specify
a complete (absolute) path to the file in the TFTP command, and such a
command would work regardless of the shell's current directory:tftp -i 192.168.1.1 put C:\Users\Jessica\Downloads\R8000-V1.0.4.68_10.1.75.chk
Using the CD command allows you to get a head start
("C:\Users\Jessica"), and to specify the rest of the path to the
directory in a bite-sized piece, making the ultimate TFTP command easier
to type.
Either way, it doesn't really matter where the file is, only that you
specify its actual location in your TFTP command, whether that's an
absolute path (independent of the shell's current directory) like
"C:\Users\Jessica\Downloads\R8000-V1.0.4.68_10.1.75.chk", or a relative
path like "R8000-V1.0.4.68_10.1.75.chk", which is implicitly based on
the shell's current directory.Clearer, or just more confusing detail?
> Can you help me understand what you mean by by the computers IP
> address vs the routers? [...]Every gizmo (computer, router, ...) on your network has an IP
address. It's analogous to a telephone number. If you want to push a
firmware image file to your router, then you need to specify the
router's address, not your own (your computer's).Strictly speaking, a _gizmo_, doesn't have an address, a network
_interface_ has one. If the gizmo has only one network interface, then
you can get sloppy, and refer to the address of the computer, when you
really mean the address of the Ethernet interface in the computer.It matters if a gizmo has multiple network interfaces. Your computer
might have, for example, a wireless interface and an Ethernet interface.
Or, your router, which has a WAN/Internet interface (for communication
with your ISP) and a LAN interface (for communication with the gizmos on
your LAN). That "192.168.1.1" is its default _LAN_ address.
In order to communicate with the router, the Ethernet interface of
your computer needs a similar but different address (like
"192.168.1.10").Your ISP normally deals with your router's WAN/Internet interface,
exclusively, because it must be compatible with their stuff, and you
can't be trusted. For this TFTP stuff, the router's too crippled to do
anything with its WAN/Internet side, anyway.