NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
spopiela
Jul 06, 2019Guide
Latest R7000 firmware update breaks router . Unable to do a reset
Did latest update this morning. Router did not complete update. I can’t do a reset . Appears to be bricked. Is there a way to get back to initial factory firmware?
antinode
Jul 07, 2019Guru
> [...] The TFTP command returns an error message "can't read from local
> file" . [...]
Where did you put the firmware image file? Where are you? What was
your actual "The TFTP command"? Copy+paste is your friend.
spopiela
Jul 07, 2019Guide
I have unbricked the router. I was doing everything correct except that when I placed the router firmware file on the computer desktop and told the windows tftp executable to change to the desktop folder , it went to another desktop folder under Onedrive. The firmware file did not exist there and it gave me the error message of not being able to open the file. I only found the issue solution because the tftp2.exe routine that i also tried was showing the file location that it was going to for the file. Under CMD you see very little. It keeps the IT people employed. Just jesting.
Very interesting though, after I solved my router issue and set up all the settings, I ran into another problem. The router that I was fixing at home (R7000) was from another cottage location. I had to shut down my home router (R7800) to test the R7000 router. My home router would not boot up and get an IP address from Xfinity. I wasted 4 hours today on that problem and it's fixed. Thanks to everyone for their help with the R7000 Router firmware problem!!
Stan
- spopielaJul 07, 2019Guide
Oh! On the R7800 issue, always check if the issue is the modem or router. My router told me that it had no IP address from the modem. There was no resetting modem and router to correct this. After hours of many troubleshooting tries, I called Comcast( Xfinity) and a great technician connected me to a netgear tech. He asked me to connect the computer to the modem. We connected to Internet. I then reconnected to router and bingo was on the air on Internet. Where is the problem? I’m happy to have a way to fix my problem quickly. I think that there is an interface issue with the R7800 and my modem and/ or Xfinity. Life is too short to deal with this constantly.
Thanks for for all your help. I saved a few bucks on an another router.
- michaelkenwardJul 08, 2019Guru
spopiela wrote:
Oh! On the R7800 issue, always check if the issue is the modem or router. My router told me that it had no IP address from the modem.
You don't say what the modem is, but as long as it is not a modem/router this sounds like that oldie but goodie. Booting things in the wrong order.
Be sure to restart your network in this sequence:- Turn off and unplug modem.
- Turn off router and computers.
- Plug in and turn on modem. Wait 2 minutes for it to connect.
- Turn on the router and wait 2 minutes for it connect.
- Turn on computers and rest of network.
- michaelkenwardJul 08, 2019Guru
spopiela wrote:
I only found the issue solution because the tftp2.exe routine that i also tried was showing the file location that it was going to for the file. Under CMD you see very little.
This was explained earlier. (See above.)
There is an easy way to see if the firmware is available to TFTP. No need for an IT person.
At the CMD prompt, type DIR.
You will then see a list of what is in the active directory. If the firmware isn't there, it won't work without a bit of trickery.
It is useful, but not essential, to have the firmware in the working directory. You can include the directory in the tftp command.
If you are in CMD, just type tftp and it will show the commands that you can use and the possible modifiers.
So you can use something like:
tftp -i 192.168.1.1 put "E:\Downloads\Software\Netgear\[firmwarename]"
You may not need the quotes. They are only there to deal with any possible spaces in the path to the file.
- antinodeJul 09, 2019Guru
> https://community.netgear.com/t5/x/x/m-p/1714564
Note that the user in that (now closed) thread seemed to be trying to
send his firmware image file to his own computer (192.168.1.2) instead
of to his router (192.168.1.1), which would be enough to explain those
error messages:> [...] tftp -i 192.168.1.2 put R8500-V1.0.2.130_1.0.99.chk
> Timeout occurred
> Connect request failed