NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
How to unbrick the Nighthawk R7000 using OS X and TFTP
Hi,
After spending a night on unbricking my R7000 and how I struggled to work with all the manuals out there but none of them actually worked. I thought I should share what actually worked for ...
HOLY COW IT WORKED!!!
nmrpflash worked!!! Switching to a Static IP address and turning my Wifi off did the trick!!
Also, recommend using -vvv to double check when it works. Took me two tries to nail the timing because the router has to finish restarting for the packet transfer to begin before the command times out.
> [...] i have followed all the steps you stated. [...]
Not very well.
> tftp> connect 192.168.1.10
"192.168.1.10" is (or should be) the address of your computer. Your
computer is not running a TFTP server, so you get a time-out when you
try to talk to it that way.
You want to connect to the router/other-device at _its_ default IP
address (which, I gather, is that same as for a router: "192.168.1.1").
For example (without the wasted time/steps):
$ tftp 192.168.1.1
tftp> binary
tftp> put <your_file_name_here>
I have completed all the process until
PUT firmware.chk
and keep getting "transfer timed out" message.. (see attached image)
> I have completed all the process until [...]
Not a useful description of what you did. _Which_ "the process",
exactly?> [...] (see attached image)
Copy+paste of the plain text would be more helpful than a picture of
the plain text, and your picture does not show the initial commands.
However:Connected to 192.168.1.10
suggests that you didn't read the previous post:
Thanks for the quick reply.
A little bit of backgroud with my problem.. I updated firware to ExpressVPN and after that event I am not able to access the router admin settings. Neither Netgear nor ExpressVPN. As a result, I want to delete the new ExpressVPN firmware and replace with Netgear.
I know expressVPN is 3rd party and Netgear cannot provide support. But I've learned my lesson and what I want is to return to original settings.
Regarding your instructions, new IP address of the router is 192.168.132.140, which I used for the transfer firmware commmand and did not work
> A little bit of backgroud with my problem.. [...]
That would have justified starting a new thread for your different
problem, rather than joining this old, largely unrelated one.> [...] I updated firware to ExpressVPN [...]
You might have tried. It might have worked. What are the LEDs on
the thing doing now?> [...] new IP address of the router is 192.168.132.140, [...]
Says who? I know nothing, but, as I read the instructions,
installing ExpressVPN on an R7000 should leave it listening at
"192.168.0.1" (which, note, is not what the default would be with
Netgear firmware on an R7000):https://www.expressvpn.com/support/vpn-setup/app-for-routers-netgear/
If the router firmware really is scrambled, and it's scrambled
Netgear firmware, then I'd look for it at "192.168.1.1". If it's
scrambled ExpressVPN firmware, then I'd look for it at "192.168.0.1".
Anything like "192.168.132.140" _might_ make some sense if the
ExpressVPN firmware is _not_ scrambled, but what do I know?> [...] which I used for the transfer firmware commmand and did not work
Regarding "did not work", look (way back) in this thread for "Not a
useful problem description [...]".VPNs (about which I know approximately nothing) tend to involve new
(virtual) networks, which may involve different, unexpected
addresses/subnets. Some confusion may be inevitable.