NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
kryptonix
Sep 26, 2018Guide
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 me using a MacBook instead of a W10/8/7 operating system. Below you will find a step by step aproach using OS X and what has worked for me.
Prerequisites:
- Default network cable (Cat5/5e/6)
- USB to Network dongle for MacBook pro's (starting 2015/2016 and up)
Example: https://www.apple.com/nl/shop/product/HJKF2ZM/A/belkin-usb-c-naar-gigabit-ethernet-adapter?fnode=58
- Downloaded stable/latest firmware version unpacked your desktop, use a mobile hotspot if you need to download after the brick
https://www.netgear.com/support/product/r7000.aspx#download
- Admin rights on the MacBook
- Keep your router close to you to see results using the lights on the router
Situation to start from:
Somewhere my router bricked during a firmware upgrade. The crash happend whille installing and the router was showing a blinking white light when the router was reset and rebooted. The router was still operating and showing white and orange light on the LAN ports so I knew I should be able to acces the router. I was not able to acces the router via Safari using 192.168.1.1 of www.routerlogin.net.
If you experience this above situatie this has worked for me to unbrick the router;
Step 1:
Remove any other network cables (including the WAN cable) from the router except the cable that is directly connected to your laptop. I used port 1 to conenct to my laptop, it should not matter but I just like to use the first port.
Step 2:
Open up your network preferences and use the admin rights to unlock your configuration settings.
When you connected your USB network adapter and cable you will see that your MacBook will self-assign an ip-address which probably will start 192.169.*.* or 169.*.*.* and an exclamation mark that there is no internet connection. It will look roughly like this.
In the red dropdown is where we are going to make some changes: Clicking on it opens up the following choices:
At this point we will be starting to assign a manual ipadres to our Mac to we need to choose Manual (Handmatig). When you choose manual you have to fill in the following data
IP-adres:
192.168.1.10
Subnetmask:
255.255.255.0
Router:
Leave empty.
The result will be that the USB Network dongle will directly connect with the router and if succesful it should will also state that it's connected. The reason why do manually assign an ip-adres to make sure that your Mac doesn't get the same ip-adres as the host/router. If everything went ok you will get the following screen:
Status: Connected (Verbonden)
Apple USB Ether wil get the assigned ip-adres that you have given in, in this case 192.168.1.10
Step 3:
We will first check if we are able to ping the router in the network to and to see the status of the router. We quickly check if our router is still blinking. If it is open up your terminal os OSX, use cmd + space and type terminal and press enter) this will open the following screen:
Default color white background and black text
First we define where we are, normally you are in your home directory. type the following command:
ls
You will see an overview of you home folder including a directory desktop. We will navigate towards that directory using the following commando:
cd Desktop
Now you press cmd + t to open a new terminal tab. This will make it easier to ping and use commando's. Use the second tab to ping the router and see the results use the following:
ping 192.168.1.1
If succesful the results will look like this:
The orange part is where you need to look to see if the router is in the right state to upload the firmware manually. ttl=100 is the state that worked for me.
Step 4:
If you haven't done it already you unpack the zip file to your desktop and move the R7000-V1.0.*.**_**.*.*.chk on the desktop where the asterix state the version you want to put on the router. When writing this article the latest version is: R7000-V1.0.9.34_10.2.36.chk
Confirm you see the file in the desktop directory using terminal ls command in the desktop directory, in terminal you are already in your desktop directory so only using ls should work.
Step 5
Go to terminal and see if the router is still up on the ping tab and check te status of the ping. When the router is still up we will start the manual upload of the firmware
In terminal type the following code:
tftp
You will see that your computername and user are gone and will be replaced by tftp. First we are going to connect to our router using the following :
connect 192.168.1.1
When succesful nothing happens and you will be shown a new tftp line. To make sure we have the right settings to upload the file you use the following command:
status
This will display the current status of the router:
To use the transfer we need to set the mode to binary otherwise it will not accept the file. This is where I struggled for more then a two hours to find this. Changing the mode to binary every step after that worked. To change the mode type:
binary
You can if the change worked by using status, when succesful you will see mode: octet.
Now we will upload the file to the router by using the following commando:
put R7000-V1.0.9.34_10.2.36.chk
Remember to replace all the version number to the version you are uploading.
This will take some time, when I was uploading it took me around the 110 seconds to complete. You will get a notification when it's done. From this point you will see your router rebooting and a lot of lights flashing and starting your router. It may take up to roughly 7 minutes to fully reboot and install etc.
By some reason all my settings where still intact and everything was up and running on the router. Then connect the WAN cable and the other cables and login in to your router using Safari to see if everything is ok, just to be sure everything is working again and clear some caches etc reboot the router.
When your router is working again in terminal just use:
quit
I hope this guide will help you in the future when using a Mac because the steps are actually different then using a Windows operated machine. The put -l 192.168.1.1 R7000-V1.0.9.34_10.2.36.chk by example will not work when you use a Mac.
Cheers
Kryptonix
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.
74 Replies
Sort By
- moonweaselAspirant
This post was helpful in my quest, since like you mentioned, the TFTP commands listed in all the Windows unbricking guides don't work in macOS Terminal.
For me the method still does not work, because in Step 3, ping returns mostly
Request timeout for icmp_seq xx
without the
ttl=100
- myerswMaster
Very nice writeup. Should help the MAC only folks out there. I have both in my case and have used both to recover a router. The one Netgear writeup for recovery using tftp suggests using a tftp client that you download. It was created in 2012 and when you download and try to install you get a message that it will not work with the current OS. ;)
Your method does not make use of that. MAC's in my exerience are not as user friendly when trying to recover a router, especially if having to go the serial connection route. With windows I do not have to drop to a terminal window, but do with MAC.
- NaiveAspirantMoonweasel , I have the same error. Did you figure out how to fix this?
> 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.
- waymer66AspirantI have followed the instructions to the letter, as outlined in the first post:
Ran a cable from the computer directly to the first LAN port.
Opened System Preferences/Network and keyed in the following:
Configure IPv4: Manually
IP Address: 192.168.1.10
Subnet Mask: 255.255.255.0
Router: (left blank)
I opened up the terminal and commanded it to the desktop. I opened another window in the terminal and entered “ping 192.168.1.1”.
I get the message Request timeout for icmp_seq (number).
What am I doing wrong or is this proof that the router is toast? Thanks.> What am I doing wrong or is this proof that the router is toast?
It's evidence that the router is not responding as expected. But
you've joined a years-old discussion and provided little information
about your own situation. Starting your own thread for your own problem
might make more sense.> Model: R7000P|Nighthawk AC2300 Smart WiFi Dual Band Gigabit Router
Is that your model? Connected to what?
LED indicators? Any other symptoms? Have you done a settings reset?
- MollmonroeAspirant
Hello,
I am having similar issues with my router. Could you explain what exactly is to be plugged in at the beginning? I keep getting server/route errors when running commands.
Just a ethernet cord should be connected from LAN port to the adapter on the Mac? Should an ethernet cord also be plugged into the ethernet connection in the wall and the power adapter for the router?
I apologize as I am confused about the instructions and how the connection will show up as connected without internet connection.
- moonweaselAspirant
Actually the ethernet cable goes from the computer into one of the four WAN ports. No other network cables should be connected to the router (just power)
Then in the Network Preferences on your Mac, turn off the WiFi, select the Ethernet connection, and change the TCP/IP settings to Manual, and set the following:
IPv4 address: 192.168.0.2
Subnet mask: 255.255.255.0
Router: leave blank
Then you should be able to ping the router by opening a Terminal window and entering "ping 192.168.0.1" (without quotes)
> I am having similar issues with my router. [...]
You should start your own thread, and provide your own details there.
What, for example, is your "my router"?
> [...] I keep getting server/route errors when running commands.
Not a useful problem description. It does not say what you did. It
does not say what happened when you did it. As usual, showing actual
actions (commands, ...) with their actual results (error messages, LED
indicators, ...) can be more helpful than vague descriptions or
interpretations. Copy+paste is your friend.
> Just a ethernet cord should be connected from LAN port to the adapter
> on the Mac? [...]
For data lines, yes. Assuming that "the adapter" is an Ethernet
adapter of some kind. (What's your "the Mac"?)
> [...] Should an ethernet cord also be plugged into the ethernet
> connection in the wall and the power adapter for the router?
Yeah, you need to supply power to your "the router". Once you've
downloaded the firmware kit to your computer, you don't need any kind of
Internet connection to use the TFTP recovery scheme. The non-psychics
in your audience don't know what's behind your "the wall", but, whatever
it might be, you shouldn't need it for this.
https://community.netgear.com/t5/x/x/m-p/1622096
> Actually the ethernet cable goes from the computer into one of the
> four WAN ports. [...]
Not really. These routers have one WAN/Internet Ethernet port, and
multiple (typically four) LAN Ethernet ports.
> [...] set the following:
> IPv4 address: 192.168.0.2
Not really. As explained in those Netgear KB articles cited above,
you do need to Configure IPv4 Manually, but the default LAN IP address
of an R7000 should be "192.168.1.1", so you should set your computer's
Ethernet interface to a similar but different address, like, say,
"192.168.1.10".
- MisterCoinsAspirant
Thank you kryptonix for this amazingly detailed and helpful write-up. I was in the same spot after my R7000 bricked during a firmware update.
I tried a few diffrerenrt methods, but your step by step description was head and shoulders above anything else out there. You're a legend in our household. - ColombaAspirantThis absolutely worked for me. Thank you so much.
Everything was going as you clearly stated right up to "put R7000....." . The file could not be found. The file is on my desktop, it is unzipped. What am I doing wrong? Help.
- myerswMaster
If you are following directions and using windows tftp you need to be in the directory where the firmware is stored. Otherwise the tftp client cannot find it. So make sure directory you are in has the file.
I am using a Mac - not Windows. Am I missing something? I checked for the file as instructed by checking the desktop files in the terminal app.
- MariusthvdbAspirant
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
- myerswMaster
Thanks for the info.
Glad things are good again. It is a pain to have to do a tftp.
Make sure of two things.
1. Make sure the auto update is turned OFF.
2. Only update the firmware via a PC/MAC Ethernet connected to router and do a manual update.
- westonagreeneAspirant
Thank you! This got my bricked RBS40 Orbi Satellite running!
I bought it off ebay and it came this way. So glad it's not in the trash--thanks to you.
For those searching the web for a similar woe:
Symptoms: ring was blinking white for about 30 seconds, then suddenly amber, milliseconds, green, black; repeat.
This article combined with the following is what I relied on: https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP
I found it reading these articles:
https://community.netgear.com/t5/Orbi/Solution-to-fix-Orbi-Satellite-flashing-white-forever-failed/m-p/1588079#M33357
https://community.netgear.com/t5/Orbi/RBK40-Satellite-RBS40-Flashing-White-then-after-25s-rapidly/m-p/1505028#M23516
https://community.netgear.com/t5/Orbi/Orbi-RBR50-satellite-pulsing-white/m-p/1733449- westonagreeneAspirant
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.
- FiddlededeeInitiate
kryptonix I signed up for this community just so I could thank you for saving my evening sir. The binary instruction saved it all. Thank you.
- Glad to help out, that’s where this community is for;)
- Rickrob00Aspirant
Had this same issue on a nighthawk x6s ac4000, and this was the only thing that worked. Thanks to Kryptonix!