This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Re: How to unbrick the Nighthawk R7000 using OS X and TFTP
HI,
thanks youve saved me a lot of headache, after my router suddenly appeared with an unportected LEDE wifi, and was unreachable on all regular addresses. Dont asl, I dont know how this happened.... must have been an interuption of the cable modem setup in the dorm...
all in all I used your guide succesfully to return to the original firmware.
1 addition to be made though: I needed to powerdown the router, and hold the pin, pressing the restore factory settings during powerup, all the way to the green power led blinking.
After that, I uploaded the firmware in 2 seconds !
Might want to add that for reference for other users.
Thanks again1
Model: WNDR3700v1|N600 Wireless Dual Band Gigabit Router
Re: How to unbrick the Nighthawk R7000 using OS X and TFTP
Forgot to add to my reply yesterday, 2019-11-03 05:50 PM, the key that helped me:
pinging the ip address (step 3 of kryptonix's original post). Leaving the ping running, I learned there was a pattern of connectivity and that eventually the connection stabalized. Once stabalized--like 10 minutes after the hold-reset-button-down-while-powering-on step (steps 7 through 9 in kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP )--I was able to do the TFTP transfer.
Re: How to unbrick the Nighthawk R7000 using OS X and TFTP
> Moonweasel , I have the same error. [...]
"same" as _what_?
> [...] Did you figure out how to fix this?
"this"? _What_?
Rather than starting your own thread for your own problem, you've joined a many-months-old thread with thirty-odd postings. Pronouns and other vague references are approximately useless here.
Hi @kryptonix thanks for your step by step instructions, but that did not work for my device, my Macbook is late 2011 and has an ethernet port so i can connect the router throuh the cable , however i have tried the steps thrugh my terminal which showing ttl-64 (not 100) like urs, when i have typed the command tftp>EX6120-V1.0.0.40_1.0.30.chk after a while it replied Request timed out.what elase can i do?
thanks
Model: EX6120|AC1200 Dual Band WiFi Range Extender
> [...] when i have typed the command tftp>EX6120-V1.0.0.40_1.0.30.chk > [...]
Presumably, there was a "put" command in there?
> [...] after a while it replied Request timed out.
With my weak psychic powers, I can't see what else you did, but "Request timed out" suggests that no one is listening at the (invisible) IP address which you gave to the TFTP client program.
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. Especially when using a command-line program, copy+paste is your friend.
> [...] i can connect the router [...]
> Model: EX6120|AC1200 Dual Band WiFi Range Extender
That's your target/failing device? That's not a router.
I don't know that TFTP is supposed to work with an extender, or, if it did, what the extender's default IP address would be. And you're connected to it how?
> [...] what elase can i do?
Start your own thread for your own problem in some more appropriate forum?
hi thanks for your intellect description, let me write down a little in details i have uploaded exactly what it happend on my macbook please have a look and provide me a solution, i have followed all the steps you stated. in the ping tab i have got ttl=64 and after tftp>binary i didnt get any OCTET
thanks
Model: EX6120|AC1200 Dual Band WiFi Range Extender
Re: How to unbrick the Nighthawk R7000 using OS X and TFTP
> [...] 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>
Re: How to unbrick the Nighthawk R7000 using OS X and TFTP
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
Re: How to unbrick the Nighthawk R7000 using OS X and TFTP
> 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):
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.
Re: How to unbrick the Nighthawk R7000 using OS X and TFTP
> Thank you, I can ping it but my transfer times out. Any ideas > appreciated.
Instead of posting a terse/useless problem description in multiple years-old threads, you might get better results if you started your own thread for your own problem, and included a few details, such as what your router does, what you did, and what happened when you did it.
