My router seems to be stuck in some sort of loop. I tried reset and hard reset the hardware but had no luck. The router was used at my parents and stop working randomly within four month of use. By the time I got to the router I missed the warranty by 5 days, when I called the support the ran few trouble shooting steps with me and rudly told me to throw away the router.
I read quite a few forms online and found out I can connect the router via serial. Bellow is the output via serial it keeps repeating the process again and unable to kill the process using 'Cltr+C'. I tried TFTP client but the router doesn't even connect or provide IP.
Any help is appreciated :).
CFE for Foxconn Router R7000PLUS version: v1.0.5 Build Date: Wed Jan 24 22:20:51 CST 2018 Init Arena Init Devs. Boot up from NAND flash... Bootcode Boot partition size = 524288(0x80000) DDR Clock: 400 MHz Info: DDR frequency set from clkfreq=1000,*533* Warning: invalid DDR setting of 533 MHz ignored. DDR frequency will be set to 400 MHz. Warning: invalid CPU setting of 1000 MHz ignored. armclock frequency will be set to 800 MHz. Committing NVRAM...done
Waiting for reset button release...donDigital core power voltage set to 0.9375V Decompressing...done
Model: R7000P|Nighthawk AC2300 Smart WiFi Dual Band Gigabit Router
My R7000P was boot looping after moving it to a new location. I realized that I had plugged it in with the wrong power adapter. If it doesn’t have enough power to power on, it will just keep trying to restart.
Model: R7000P|Nighthawk AC2300 Smart WiFi Dual Band Gigabit Router
"called" _how_? _Whose_ "the support"? Netgear or some scam artists you found with a Web search?
> [...] I tried TFTP client [...]
The TFTP recovery scheme is a multi-step procedure which offers multiple opportunities for user input, hence user error. By itself, saying that you "tried" it doesn't say much. As usual, showing actual actions (commands) with their actual results (error messages, LED indicators, ...) can be more helpful than vague descriptions or interpretations. Especially when using a command-line program, copy+paste is your friend.
> [...] but the router doesn't even connect [...]
A vague description of what some device does _not_ do is less useful than a clear description of what _does_ happen.
> [...] or provide IP.
If the router as a whole is not working, then why would you expect its DHCP server to be working? A good part of the TFTP recovery procedure is configuring a computer with static IP parameters, specifically because DHCP is unavailable.
