I messed up some VLAN configs on my R7000 and did a reset using the reset button. I held for around 30 seconds as I have in the past but this time the router didn't come back up with 192.168.1.1 accessible
When I ping the router from my laptop connected via ethernet, and turn it on, I do see around 25 pings go through with a TTL of 100, which I saw means the bootloader is responding. It then goes back to "Request timeout" 've since tried a 30-30-30 hard reset to no avail. Based on what I've read in the stickies, this doesn't mean it's bricked but I should try TFTP flashing..
Unfortunately this doesn't seem to do anything (I start the tftp command when the pings start going through, but it times out. I also tried with a TFTP Client GUI for MacOS and this also didn't transfer past 0 bytes.
I don't think I'm as knowledgable as most when it comes to DD-WRT but am really trying to learn. Appreciate any advice for how I can get back to a working DD-WRT router or if I'm stuffed and I've bricked it?
Find "Serial". There should be 4 hits on page one and the 2nd is going to show you what you want.
As for the 30-30-30 method,
that has been obsolete for arm based routers since the early days (couple years now) and is common knowledge on the forums.
The best way to reset an arm router is via the command line.
Again, thats covered in the R7000 sticky.
""erase nvram && reboot"
minus the "" & it will reset the arm router & reboot it to a clean config. _________________ Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode
Thanks guys, I'll look at the serial recovery. My understanding from the Announcement thread was that because I could still ping it during bootup it meant it wasn't bricked, so I assumed the TFTP should have worked. Quite a lot of Announcements/ stickys to trawl through and some conflicting information so just wanted to get the confirmation.
Joined: 03 Jan 2017 Posts: 49 Location: Lindau, Germany
Posted: Tue Feb 27, 2018 17:51 Post subject: Re: May have buggered my R7000 during reset..
windyboi wrote:
Based on what I've read in the stickies, this doesn't mean it's bricked but I should try TFTP flashing..
Unfortunately this doesn't seem to do anything (I start the tftp command when the pings start going through, but it times out. I also tried with a TFTP Client GUI for MacOS and this also didn't transfer past 0 bytes.
I had a similar issue with my R7000 Router: I could ping it for a few seconds then the boot process proceeded until the router froze.
During this short period the router assigns itself the IP 192.168.1.1 and tries to download a vmlinuz file via tftp from the IP address 192.168.1.2. To use this feature you have to install a tftp server which has a vmlinuz file available. This file is loaded by the router and executed as firmware. You can then log in to the router and erase the NVRAM.
As I did that I was wondering that the firmware was not flashed (after reset the original dd-wrt firmware was still available).
But be careful: When I did this with the vmlinuz file from the link above even the MAC addresses (and maybe other variables) where erased which never occurred when erasing nvram under dd-wrt.
So from my point of view a serial recovery is a better choice than living with corrupted MAC addresses (or re-creating the MAC addresses manually, what I did).
But then after rebooting router I am in exact same problem (ping 192.168.1.1 only works for first 20 pings). Looks like the firmware didn't update.
On the plus side, I guess I now have access to the CFE> command line. I tried to "erase nvram" as someone above said but was told this was an "invalid command". Anything else I am able to do to recover my R7000? Shall I try TFTPing Kongs latest .chk instead of this R7000 zip?
Joined: 03 Jan 2017 Posts: 49 Location: Lindau, Germany
Posted: Mon Mar 05, 2018 6:28 Post subject:
windyboi wrote:
I did the exact steps listed here
I tried to "erase nvram" as someone above said but was told this was an "invalid command". Anything else I am able to do to recover my R7000? Shall I try TFTPing Kongs latest .chk instead of this R7000 zip?
As I remember correctly the following command worked:
Lol
Yeah the zip file won't do the router any good.
I followed the exact steps that have been linked from the R7000 kong sticky which you told me to go to and follow. Step 9 shows to configure the TFTP Client as follows:
Is this incorrect then?
You've also told me to run erase nvram && reboot but this shows me "Invalid command"
