I'm reaching out because I don't know what to do! I had loaded with DDWRT nearly a year ago and it was working great! That until about the past 2 weeks or so, where it's lost connection with my TV, so I've had to just restart the device (hitting the power off button, then power back on). However - yesterday - I seem to have done a restart OF DEATH - as when I restarted the router, it never came back on.
Problem: when I turn on the router, a few white/orange lights across the board flash briefly, which is replaced by the power button remaining a solid orange color. A few seconds later, the light below the 5GHz label lights up white, and my router doesn't progress past that point. I've tried power cycling, as well as doing a 30/30/30 reset with the reset button in the back. However, to no avail did this resolve my problems. I even tried the ARM 30/30/30 but that didn't work. I also can't connect to the device when I connect directly to it with my computer. I'm at a loss for how to further troubleshoot. Does anyone have any ideas? Any help would be greatly appreciated!
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Wed Jul 21, 2021 0:59 Post subject:
Ok, topic says R7500, link says R7000. Which is it? In either case, you don't do a 30-30-30 whatsoever. There are only a couple of methods to reset and none of them involve a 30-30-30. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
I am trying to remember how to recover it specifically. I am sure there is a forum thread link in the references sticky at the top of the Atheros forum; But I would try to boot it up normally and then press and hold the reset for ~7-10 seconds and see if it resets. Outside of that, you should be able to recover via TFTP by pressing reset button and powering up until the power light gives indication that it is ready to receive the firmware file. Normally, this would require stock firmware image but I believe you should be able to use the factory-to-ddwrt.img file as well.
Thanks for the links kernel-panic69 - I unfortunately wasn't able to reset it to fix the problem, and I can't find the IP address of the access point in order to authenticate. It assigns me a bogus IP (one that I don't ever remember setting as the netmask/subnet combo for the AP, and there isn't a default gateway ever assigned. I'm connected to the router via an ethernet cord but no luck. Any nudges you can provide would greatly be appreciated - as I've hit a dead end googling for answers, which makes me think I'm not thinking through the problem appropriately
I'm connected to the router via an ethernet cord but no luck. Any nudges you can provide would greatly be appreciated - as I've hit a dead end googling for answers, which makes me think I'm not thinking through the problem appropriately
My personal experience with sat receivers, settop boxes, routers and repeaters and more:
You should check the power supply and main board dc power electrolytic capacitors. Increasing failures or hangups without changing firmware or settings are mainly based on problems with the DC power (or overheating on high powered devices). All other hardware failures mostly render a device from complete working to unusable in one step. A reboot cannot fix any such hardware failure.
I don't own that hardware, maybe one owner already knows howto check and replace or is able to offer some pictures of relevant capacitors. If you don't have any repair / solder experience you should look for repair cafe in your range.
Thanks for the links blkt. Any idea on how to identify my Router IP? It gives me a random IP with a random subnet (and a massive netmask of 255.255.0.0). When I manually assign it to 192.168.1.1 I get request timeouts pinging the host. I've even tried 192.168.3.1 which is what the old access point used to be set to, but no luck.
Winner winner chicken dinner! Not sure why, but purely booting into TFTP mode seems to have fixed the problem itself! Thanks for the recommendation blkt!!