NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R6400V2 failed firmware
Ok all,
I was recently (today) upgrading my frimware for the R6400v2 through the router's web portal. While uploading the firmware, it failed. No idea why it failed, but it did.
Suddenly, I lost all internet.
I went to my router and saw all lights off except for the power LED light. It was blinking an amber color.
Now, I went through some guides and people having the same problem, but I couldn't find exactly what was wrong. I was going to follow the guides to upload the firmware through a TFTP, but my computer no longer has an ethernet port (macbook pro, late 2013 model). I could go out and get the thunderport to ethernet adaptor, but that will take almost a week to get in this current 'rona eviornment. Also, the TFTP program suggested for mac users is a 32bit, and I run OS Sierra which has compeltely shifted to 64bit, meaning no 32bit programs will open on this computer. I do run Parallells, and can access network connectivity through Windows, but again, no ethernet port, and quite some time to get the cable.
So I thought, I'll factory resent and just go through the struggle of reconnecting all my smart devices to the new networks. However, when attempting to factory reset, it does nothing! The power LED continues to blink amber and it does not appear to be resetting.
Does anyone have any idea what's going on here? And how can I fix it?
Thanks in advance!
> [...] what appears to be a cycle [...]
In some cases, the router can get into a (failing) boot loop, which
might mean that if it's ever receptive to a TFTP load, then you might
need to catch it at the right time. Some experimentation may be needed.> [...] (see attached).
You're running the "tftp" program, and then giving _it_ a command to
run the "tftp" program.> [...] But the "$" int he above is what confuses me.
What was on the line before what you posted? That "$" was supposed
to represent (abbreviated) the prompt from your shell (which, as your
"ping" picture showed, is pretty long, but does end in "$ ").So, the actual command should look like:
<blah-blah-blah> $ tftp 192.168.1.1of which you type only: tftp 192.168.1.1
The "tftp" program uses a "tftp> " prompt, and you type whatever
appears after that in the example.> [...] I'm sorry, I'm a bit novice at this. [...]
I noticed. Just bask in the education. Wheee.
> [...] I already did the /usr/bin/tftp bit to access the tftp.
That was what the "tftp 192.168.1.1" command was for. You could,
instead, do:$ tftp
tftp> connect 192.168.1.1which would be equivalent to (but more work than):
$ tftp 192.168.1.1
The "put fred.img" command assumes that your firmware image file (use
its actual name) is in the shell's current directory. Otherwise, you'd
need to specify an appropriate path to it (like the one (partially)
shown in your Tftpd64 screen shot, but with a Mac/unix syntax instead of
a PC\Windows syntax). For some shell navigation basics, see, for
example:
18 Replies
> [...] I was going to follow the guides to upload the firmware through
> a TFTP, but my computer no longer has an ethernet port (macbook pro,
> late 2013 model). [...]You need older/better junk. Or a USB-Ethernet adapter. Or a
better-equipped friend.> [...] the TFTP program suggested for mac users is a 32bit, [...]
There's no need for any third-party TFTP client program. The
command-line programs which come with any popular OS generally provide
better error messages, too. See, for example:https://community.netgear.com/t5/x/x/m-p/1622096#M102004
> [...] factory reset, it does nothing! The power LED continues to blink
> amber [...]The flashing Power indicator means that the firmware is corrupt, and,
without working firmware, even basic router features like a settings
reset can't work.The TFTP recovery procedure is the usual tool for loading firmware
into a (mostly) helpless device.> "The command-line programs which come with any popular OS generally provide better error messages, too."
The link you provided me has links which provide instructions on using the TFTP programs, but you mentioned bening able to use the command-line programs with my OS. Do you have a guide for just that?
Also, I followed the guide using the TFTP thrid part program on Windows and I keep getting a "Server Stops the Transfer Errpr #2: Access" message. Any ideas? I followed the guide every step.
UPDATE:
I was able to move past the error message on the TFPT thing, but it seems to be getting stuck on the put (I've attached screenshot and will explain further in post). I've read the timing can be finicky with when to push Put, so I just want to confirm:
- Unplug all port connections from router except this PC.
- Turn router OFF for 10 seconds and then turn it back ON.
- Watch the Power LED. It will start with an orange color and then start flashing.
- Press PUT button on the Tftpd64 utility to perform the firmware upload.
- Nothing by the laptop is plugged into teh router.
- I turn off the power for 10 seconds, then turn it back on
- All the lights light up, then just the 1st port lights in a solid dull pink, then all lights light up, then just the power led light and the 1st port light illuminate solid (amber for Power, white for 1st port). Then, the power light will begin to blink amber while the 1st port light remains white.
- At the moment the power light begins to blick amber, I press the Put button
Then, as I mentioned above with where I'm gettign stuck, according to the instructions, I am suppose to "see a pop up saying that '0 block retransmitted'. If not, you may need to repeat above." I do not, so I repeat above and nothing changes.
Instead, what I am seeing is no pop up, but "block #0" appear above the progress bar on the TFTP64 window (see attached screenshot).
Am I doing something wrong at this point?
As per the isntructions, I've created a static IP with the below info:
- IP address => 192.168.1.10
- Subnet mask => 255.255.255.0
- Default Gateway => 192.168.1.1
