NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CCNE37
Oct 09, 2019Luminary
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...
- Oct 10, 2019
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
antinode
Oct 10, 2019Guru
> 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.
CCNE37
Oct 10, 2019Luminary
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
- antinodeOct 10, 2019Guru
> 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.
- CCNE37Oct 10, 2019Luminary
Thanks. I was using a wired connection to desktop originally when things went pear-shaped. I initiated the update through the Netgear R7000 login page.
No thanks - I think I will stay where I am for now. My R7000 has been pretty bulletproof for the last 4 years with maybe 1 reconnection / reset per month at most.
I am over fiddling :smileyhappy:
- antinodeOct 10, 2019Guru
> [...] I initiated the update through the Netgear R7000 login page.
I'll assume that that means ADVANCED > Administration > Firmware
Update, but there are two options at that point: "Check for new version
from the Internet" or "Locate and select the upgrade file on your hard
disk". I generally use the latter.> I am over fiddling [...]
Just when you were getting better at it...
- CCNE37Oct 10, 2019Luminary
Yes it was through Advanced etc. I am pretty sure I clicked the first option, not the latter.
I will bear that in mind for next time - if there is a next time.
Thanks again.