This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
My R8500 seems to have crashed today, and is now stuck in a reboot loop. I was working (connected to the router via wifi), and the network dropped. I got up to see what the issue was and could see the router was rebooting. After watching it stuggle for a while, I tried:
* Power cycling the router (via both the power button, and unplugging from the wall)
None have seemed to have had any effect. Everytime, the lights flash on, the power light goes amber, more flashing lights, then they all go off and it starts over.
Following the tfto guide, I was able to connect to the router (confirmed via ping), but every time I tried to transfer the file, it timed out.
I am runing the stock firmware, V1.0.2.26_1.0.41, and that is the version I have been trying to flash with tftp.
Thanks for the tip, but holding the reset button while booting doesn't seem to do anything.
If I set my computer up with a static ip, I can ping the router part way through the boot process. TTL is 100. Here's a sample of the ping output:
From 192.168.1.75 icmp_seq=744 Destination Host Unreachable
From 192.168.1.75 icmp_seq=745 Destination Host Unreachable
64 bytes from 192.168.1.1: icmp_seq=746 ttl=100 time=3007 ms
64 bytes from 192.168.1.1: icmp_seq=747 ttl=100 time=1999 ms
64 bytes from 192.168.1.1: icmp_seq=749 ttl=100 time=1.69 ms
64 bytes from 192.168.1.1: icmp_seq=750 ttl=100 time=1.65 ms
64 bytes from 192.168.1.1: icmp_seq=751 ttl=100 time=1.67 ms
64 bytes from 192.168.1.1: icmp_seq=752 ttl=100 time=1.70 ms
From 192.168.1.75 icmp_seq=785 Destination Host Unreachable
From 192.168.1.75 icmp_seq=786 Destination Host Unreachable
i also have the dreaded reboot loop. I'm using a CP2102 USB TTL board V3.0 to use putty and tftpd64 (windows10). Tried everything I could find online. I feel equipped with the right tools...but so far no go.
@GeekSkill@ & @rlaroch1 Kindly register your devices and let me know once done so I can forward you to our support team.
I couldn't register this R8500 serial # 4DG159760239A as it was already registered by someone on the Netgear staff. I guess he didn't want to deal with this nonfunctional device. I found it on eBay.
This R8500: cannot invoke reset mode via reset button. Boot cycle is only partial and loops 8 times before finally stopping. No access to gui.
I can get the device in TFTP mode (blinking amber power) via puTTY/serial interface. TFTPd64 "appears" to load and program the firmware but reboots to its same reboot loop state. My best guess the installed FW file is not only corrupt but a file type other than .chk
I made a rather startling discovery: I cannot tftpd firmware because I don't know the stored password: every try says 'unauthorized password'. I tried every default including 'password'. As previously stated the reset button has no effect on restoring defaults: be it 5 seconds, 30 seconds or a hard reset. So there's my roadblock. If anyone has a suggestion I'd LOVE to hear it!
Let's back off little bit. Can you ping the router? I many times used tftp to debrick routers and never
aI was asked password. You mean when you start excecuting tftp command, you get password question?
Hi thanks for trying to help! No problem pinging router. Only tftp/tftp2 gives that. Tftp64 doesn't and goes through the motions like it's actually upgrading the firmware. Putty tells me its programming then auto reboots, only to do a partial boot and then repeat over and over. Again I suspect instead of a chk file somebody loaded a third party file (bin or whatever). I'm in uncharted territory but at least it's alive. I refuse to give up!
Can you log in to the router by it's ip address? Netgear routers all use 12V DC wall wart. None handy for you?
No I can't. After it's done with all of its boot cycles it's in a state of unusefullness. No GUI, no wireless. It's a miracle I can connect via LAN. And if it wasn't for the serial interface I couldn't invoke a blinking Amber power light. I can't seem to telnet into it. If I could I'd try 'MTD -erase linux' : apparently from what I've read it's not possible to replace open source firmware with stock firmware if you're not in the GUI. Because this is a newish model router I can only get info on older routers. Again, uncharted territory ha ha.
@ChrisRogers91 wrote: FWIW, when the support team contacted me (OP), they said it was a hardware issue, and shipped me a new unit (just arrived today).
Best,
Chris
Lucky you. I bought this device as is with known issues so I can only dream. It's worse than I expected but I'm determined to find a way. #fun
