Hello everyone. I was trying to install Tomato on my R8000 when it become inaccessible after a firmware upgrade. I installed the tomato-R8000-1.28.ARM--140-initial-64K.chk without issue and then updated it to tomato-R8000-ARM--140-AIO-64K.trx when it stopped working. When the router is plugged into WAN (going to an eero system, not my ISP), it boots with the lights going: 1, 2, 3, 4 white, then the rest dimly light up white, then all the lights light up with both white and amber, then it settles to an amber power light. When my computer is plugged into one of the LAN ports, ipconfig shows:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Autoconfiguration IPv4 Address. . : 169.254.78.90
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
I tried changing the IPv4 settings to:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
but when I try to ping the router the request just times out.
I really don't know where to go from here. I tried the 30-30-30 reset but got nowhere. I also tried just holding the reset button down for 15 seconds and that only seems to inconsistently trigger a reboot and doesn't help with the problem at all. When it is plugged into WAN, I don't see it connected to my eero's at all.
I don't have time to wait for a USB-TTL cable to recover it, so if this is solveable without that, I would greatly appreciate the help.
You could certainly solve it with usb ttl, but first try to fix it wirelessly if u can access it.
Hi, i had the same issue, did you fix it?
Nope. You probably need to connect to the serial port inside. I never tried that and I still haven't fixed it.
Had exactly this isssue, you can attempt to fix it with nmrpflash by jclehner on Github.