Hello!
I have a r6400v2 that became unresponsive. No wifi signal or anything. I was able to plug in a ethernet cord and ping it. It would reply when I set up my static ip to 192.168.1.1 and default gateway to 192.168.1.1. I tried tftp firmware but all I got was a blinking orange power LED (plugged in ethernet would blink orange aswell).
This happened after I flashed DD-WRT and it worked, but once I tried updating DD-WRT it reboot and never responded. No routerlogin and 192.161.1.1 on ethernet since there was no wifi. Anytips on getting it to work? I tried tftp windows, tftp2, and tftpd64 with DD-WRT firmware and stock firmware. All seem to just blink orange still.
Try this to load on a Netgear firmware.
https://github.com/jclehner/nmrpflash
Best of luck.
Right now there is an issue with DD-WRT and this router. Basically, because the build identifies it as a 7000P router it messes everything up. It's not just a cosmetic problem, it creates a huge mess in the background because the 7000P has different memory addressing. As far as DD-WRT is concerned it thinks that it really IS installed on a 7000P and treats it as such. This install only works one time, going from factory to DD-WRT because it carries over settings from the original stock firmware. As soon as DD-WRT is installed over DD-WRT it goes down the drain. Your only option is to use nmrpflash or connect through a serial connection. I restored mine through a serial connection and it sits on the shelf until this identification problem is fixed. There have been tickets submitted but to my knowledge it hasn't been fixed yet...
Yeah, the "official" DD-WRT image is borked. It kinda works, but as soon as you make changes, everything goes to shit. Best stick with Netgear firmware for now, if it's "mission critical"
I managed to get back to factory firmware with some help. Hopefully we'll get a version that doesn't identify as 7000P. Hold off until that's fact. Took me lots of searching and tinkering just to get the stock firmware back on track.
The new Kong build (still in the testing phase) has it corrected, and the new versions coming out from "brainslayer" are supposed to have the fix as well. Hold tight.
Thanks for the update. I don't mind playing with the test versions. I've already cracked open the case after owning it for 6 hours :)
http://desipro.de/ddwrt/K3-AC-Arm/TEST/
(the V2 version is for board ID ending in 20... the V2OTP is for board ID ending in 30)