NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
R6700v2 firmware update unsuccessful
I tried to update my firmware (from 1.2.0.74 to 1.2.0.76) this afternoon after noticing spotty internet on my wifi devices. I updated the router via the netgear app, however, the app never came back with a succesful message and has since been nonfunctional.
I have tried the command prompt TFTP method in addition to the TFTPd64 method while hard wired in to the router. I have gotten the 0 blocks retransmitted message on the proprietery software, waited 4+ minutes and the router is still flashing white on the power indicator light.
I am wired on a windows 10 computer.
What are my next steps?
5 Replies
I have not been able to ping the router using the default 192.168.1.1 or 192.168.0.1 ip addresses.
I have tried the TFTP schemes as outlined in the following:
https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP
https://kb.netgear.com/19841/Reinstall-the-firmware-on-a-router-without-the-setup-CD-recovery-tool
https://kb.netgear.com/000059633/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP-client
none of these have proven successful as of yet.
> [...] since been nonfunctional.
Which kind of "nonfunctional"? LED indicators?
> I have tried the command prompt TFTP method [...]
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 have not been able to ping the router using the default 192.168.1.1
> or 192.168.0.1 ip addresses.For an Rxxxx model, the default LAN IP address would be
"192.168.1.1".
"not able" is not a useful problem description. It does not say what
you did. It does not say what happened when you did it. See "As usual,
[...]", above.
> I have tried the TFTP schemes as outlined in the following: [...]I'd concentrate on: https://kb.netgear.com/000059634
Power LED indicator is either a solid stable orange, or blinking white depending on if a 30-30 reset was done recently.
connected laptop is the only device connected. modem has also been disconnected. laptop has
- IP address => 192.168.1.10
- Subnet mask => 255.255.255.0
- Default Gateway => 192.168.1.1
router turned off for 10 seconds. powering on with reset button held down for 10 flashing power led cycles, and then released.
command prompt executed.
Command prompt TFTP resulted in the following.
C:\Users\XXXXX\Desktop>tftp -i 192.168.1.1 put R6700v2-V1.2.0.76_1.0.1.img
tftp: can't read from local file 'R6700v2-V1.2.0.76_1.0.1.img'copied and pasted the file name from the desktop file icon, and added the .img as per item description.
Sending a ping to the default IP address resulted in the following.
Pinging 192.168.1.1 with 32 bytes of data
Request timed out.
Request timed out.
Request timed out.
Request timed out.Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)