@antinode I followed the old guide (linked below) from the netgear forums I did a 30-30-30 reset and have been non-stop pinging the router with a 2 (m)sec timeout... It looks like there is a 10(m)sec window for TFTP to connect, does that sound right?
Guide: https://community.netgear.com/t5/General-WiFi-Routers-Non/Guide-How-to-quot-unbrick-quot-your-WGR614...
ping command: ping -t -w 2 192.168.1.1
Ping results (timings vary each time):
Request timed out.
Reply from 192.168.1.1: bytes=32 time=3ms ttl=100
Reply from 192.168.1.1: bytes=32 time<1ms ttl=100
Reply from 192.168.1.1: bytes=32 time=1ms ttl=100
Reply from 192.168.1.1: bytes=32 time=1ms ttl=100
Request timed out.
Request timed out.
Request timed out. (20-30 times)
Reply from 192.168.1.1: bytes=32 time=1ms ttl=100
Reply from 192.168.1.1: bytes=32 time=1ms ttl=100
Reply from 192.168.1.1: bytes=32 time=1ms ttl=100
After the router resumes ping reponses the tftp window reports "Connect request failed"
Update: I did finally see the flashing power light... When I power on the device, let it boot fully and then press and hold the reset it either flashes on, bright on, on (repeating) or on, off, on (repeating) with the wireless led lit solid and blue.
I haven't been able to complete a tftp connection so far.
These modern browsers and their ability to detect a network connection update makes this process 10x more frustrating as they keep trying to detect the internet through the "new" connection and usually grab focus / open a new window or tab... Trying to stay with it though 😛
