I flashed this file to the router through the Web GUI
Right after the flash uploads the router reboots, the power light turns orange and then around 10 seconds later all the port lights flash indicating a reboot.
I waited about 10 minutes and the router was still in boot loop mode.
I assigned my ethernet interface a static 192.168.1.2 address and issued a ping 192.168.1.1 command in terminal. Pinging will show show activity for about 4 packets. Then port lights on the router will flash and the router will reboot.
I downloaded the original firmware R7800-V126.96.36.199.img from the Netgear website then I activate the tftp command prompt. I issue the commands:
connect 192.168.1.1 binary rexmt 1 timeout 60
I put the router into recovery mode by holding down the reset button and power cycling the device. Once the power led flashes white it takes about 10-15 more seconds until I see steady ping activity on my computer.
I tell tftp put R7800-V188.8.131.52.img. A few seconds later tftp tells me the file has sent and the router starts to reboot. However the router will start going into boot loops again. I check on it 30 minutes later, do a power cycle and it will still boot loop.
My question is, what's going on? Are the boot loops normal when doing a firmware upggrade? Is there any indicator I should see that the firmware is actually being processed after upload? Should I wait longer than 30 minutes? I have tried older firmware files from the netgear page, lede factory.img files, and the img files from www.desipro.de/ddwrt/K3-AC-IPQ806X/NetgearFW/ . All of them give me the same boot loop result.
Though serial may be the ultimate solution, r7800 has uboot which is pretty resilient. I usually try everything I can to avoid opening up the sucker. So try tftp each of these 3 latest img firmwares and see which may work.
I had the exact same issue with a R7500 v1.
It was also boot looping after flashing the factory to ddwrt file. I tried the one in the regular folder (K3-AC-IPQ806X) and the one in the Test folder on Kong's website. And flashed dd-wrt via the netgear interface and a second time via tftp. The results were the same, boot looping.
I did not try that build. The problem is that the factory to ddwrt img puts it into a boot loop and therefore you never get to installing a new build of dd-wrt. Is there a way to skip the initial factory to ddwrt image?
I have been successful before to get it to work for my r7800 that I use at work. No need for serial recovery.
- Flash to factory fw
- Enable telnet in 192.168.1.1/debug.htm
- Via telnet: mtd erase kernel, rootfs, netgear, firmware; reboot.
- Flash factory fw again via tftp
- Flash to ddwrt via BS/Kong factory-ddwrt fw.
tl;dr: this router is just screwed up. i think it's overheating.
I last left it plugged into my Mac and I gave up for the night after TFTP flashing the oldest Netgear firmware ( 184.108.40.206 ) for the umpteeth time.
After reading all the suggestions this afternoon I decide to bring it down to where my Windows desktop computer is to try a different tftp client. When I plugged it in to the outlet, to my fustrating surprise the power light started flashing white and it magically booted into the Netgear firmware. WTF.
Being the masochist that I am I decide to see what would happen if I upgraded the Netgear firmware to the current version (220.127.116.11) through the Web GUI. Again it boot loops. I then tried to TFTP flash the firmware file again and again it boot loops.
I then decide to unplug it, wait a moment and turn it on again. After about 5 minutes I turn it on and it boots into the firmware no problem.
I leave it turned on (but not configured) while running other errands and when I come back about 20-30 minutes later I find the router boot looping again.
I'm guessing there was nothing wrong with the flashing process. Something is overheating and causing the boot loops. It's odd because it's barely been turned on for any length of time. It feels warm but not abnormally hot.
I'm going to attempt to return this. Thanks guys for all your helpful suggestions.
The boot-loop is probably caused by bad hardware. Most likely a bad spot in the Flash Memory.
I lost my 7800 due to a bad flash chip. It had run fine for a year and then went poof during an update.
Solution? Gave it to my son to play with and went to all R9000's. He managed to erase the wrong partition and relegated it to door stop. _________________ Segment 1 R9000 10Gb LAN, 1Gb ISP BS
Test Bed R9000 10Gb LAN
Wired AP 1 R9000 10Gb LAN
Wired AP 2 R9000 1Gb LAN
Wired AP 3 R9000 1Gb LAN
Test Bed R7800 1Gb LAN OpenWRT Kong
download1.dd-wrt.com/dd-wrtv2/downloads/betas/ (Brain Slayer)