NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000 bricked after firmware update attempt
I have recently tried a firmware upgrade on my R7000, and it never got past the dreaded white blinking power light. I found other threads that referred to the tftp process, and tried a few things...
Thanks again.
Well I tried again from scratch, and got something to happen using the Windows 10 TFTP client.
It came up with a message saying that transfer was successful.
After a few minutes, the power light turned solid orange and stayed orange for about 10 minutes - I was about to pull everything apart again, when it suddenly turned solid white and the internet light came on.
I have checked and the firmware is back where it was before I believe, which is the same as the firmware version I used for the transfer via TFTP.
I am very hesitant to try the firmware update again.
Thanks you for your help :smileyhappy: Much appreciated.
Colin
> [...] I followed the instructions in this link [...]
> [...] I changed my IP address in properties to 192.168.1.1. [...]
Those two statements can't both be true.
"192.168.1.1" is the default address of the router. The address of
your computer must be compatible, but different. For example, as that
KB article suggests:
> xii. IP address => 192.168.1.10
> I then downloaded the tftpd64 software, [...]
Probably pointless. I'd stick with the command-line TFTP client
program which came with your OS, and forget any third-party TFTP
programs.
> [...] I changed the server interface to the Intel(R) Ethernet
> Connection (2)I219-V [...]
"changed"? "server"? What was it before? How many Ethernet
interfaces does this computer have? How many have a cable connected to
your router?
> [...] I did notice that in front of this description was a IP address
> of 169.254.227.39 - I was expecting it to be 192.168.1.1.
"169.254.x.y", is a self-assigned address, and is an indication of a
faulty configuration. My guess would be that you tried to set the
interface in the computer to "192.168.1.1", and that address was already
in use by the router. Windows noticed the conflict, ignored your
instruction, and did the best it could. (Which was not good enough.)
> [...] this time entering the 169.254.227.39 IP address in the host
> box, [...]
Still no good. "169.254.x.y" is not on the same subnet as
"192.168.1.1", which is where the router should be.
"192.168.1.1" is the default address of the router. The address of
your computer must be compatible, but different. For example, as that
KB article suggests:
> xii. IP address => 192.168.1.10
Read the instructions again, more carefully. Set the address of the
(active) interface in the computer to "192.168.1.10", as suggested.
With both the router and your computer on the same subnet
("192.168.1.*"), you should not get those "unreachable network"
complaints. (You may still have problems, but not that one.)
Thanks for the reply.
Apologies, let me clarify - in the network device IPv4 properties I set the IP address to 192.168.1.10, and the default gateway address to 192.168.1.1 (as per the instructions). The subnet mask is self populating.
I only tried the Tftp software because of the error message when using the Windows 10 TFTP client.
The default server interface in tftp software comes up as 127.0.0.1 Software Loopback Interface 1, so I changed it to the only other option, which was the Intel(R) option.
I have one cable connected to my router, which is the one connected to my desktop.
In the Tftp software, in the box called "Host" - is this the router IP address (192.168.1.1) or the PC IP address (192.168.1.10) ?
> The default server interface in tftp software [...]
That's in the third-party program (which I'd avoid)?
"127.0.0.1" is a software-only loopback interface. Don't fiddle with
it.> In the Tftp software, in the box called "Host" - is this the router IP
> address (192.168.1.1) or the PC IP address (192.168.1.10) ?As I said, I wouldn't use that program, but in any such program, the
address which you need to specify is the address of the target router,
"192.168.1.1". In order for that to have any chance of working, the
address of the Ethernet interface on your computer must be
"192.168.1.10" (or something very like it). If you're seeing
"169.254.x.y" anywhere, then you haven't done that interface
configuration properly.Thanks again.
Well I tried again from scratch, and got something to happen using the Windows 10 TFTP client.
It came up with a message saying that transfer was successful.
After a few minutes, the power light turned solid orange and stayed orange for about 10 minutes - I was about to pull everything apart again, when it suddenly turned solid white and the internet light came on.
I have checked and the firmware is back where it was before I believe, which is the same as the firmware version I used for the transfer via TFTP.
I am very hesitant to try the firmware update again.
Thanks you for your help :smileyhappy: Much appreciated.
Colin
> I have checked and the firmware is back where it was before I believe,
> which is the same as the firmware version I used for the transfer via
> TFTP.What could go wrong?
> I am very hesitant to try the firmware update again.
But now you know what to do when (what may be) the worst happens.
(The manual update method using a wired connection between computer and
router seems to be relatively reliable.)I know nothing, but reports here suggest that anything after
"1.0.9.42" (up through ".88") might do more harm than good.