NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000p stopped working
so a little context, got this used so its not orginal. i dont have the box it came with nor any of the manuals. So i was playing video games and i noticed that my internet was slow and it wasnt c...
HOLY COW!!! IT FIXED IT!!!!
So this is how i ended up doing it
i took the downloaded file and moved it from my actual desktop to ThisPC> Local Disk (C:)> users> CarlJ> Desktop. and plased it there.
from there i followed this link https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP
and from there i followed the instructions and it flipping worked.
I just wanna say thank you guys so much for the help!! stay safe with Coiv-19
okay update, so i put the file in the folder by going to thispc>local disk>users>CarlJ>desktop and in the cmd prompt it comes up as this
HOLY COW!!! IT FIXED IT!!!!
So this is how i ended up doing it
i took the downloaded file and moved it from my actual desktop to ThisPC> Local Disk (C:)> users> CarlJ> Desktop. and plased it there.
from there i followed this link https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP
and from there i followed the instructions and it flipping worked.
I just wanna say thank you guys so much for the help!! stay safe with Coiv-19
> So this is how i ended up doing it [...]
Before I got dragged away by real life, I was about to suggest
forgetting your Desktop folder, which seems to be a source of endless
mystery, and copying/moving the firmware image file to some simpler
place, like, say, "C:\" or "C:\Users\CarlJ", and then giving the shell
some appropriate "cd <wherever>" command(s) to get the shell to look at
that simpler folder.But you seem to have found a way, not matter how strange it might
seem. No matter what, the key is to use "cd" commands to point the
shell at the folder where the file is. All you need to do is find that
folder.How your Desktop got into its current (confusing) state, is not clear
to me.It all boiled down to having the firmware file in the right place so that the TFTP command could find it.
In most cases this is a trivial task, but this was made harder by your quirky way of setting up Windows.
Fortunately, a little knowledge of "environment variables" in Windows can help to unravel that sort of labyrinth. But I would not be surprised if you encounter other strange Windows behaviour that causes you to scratch your head. But at least you got that one sorted out.
