Netgear R7000 admin web interface failed to start after updating to latest 1.9 firmware

> I have no idea which firmware version I updated to [...]

   I doubt that it matters much.  Whichever version it was, it's hosed
now.

> * Failed to connect to 192.168.1.1 port 80: Connection refused

   Normally, "Connection refused" means that contact was made with the
target address, but nothing there was listening at the target port.  In
this case, the management web server appears not to be running.  The
usual explanation for that would be that the firmware is seriously
corrupt.

> [...] I supposed I could try rolling back my firmware to the previous
> version using tftp to update. That seems like it could be possible to
> brick it though so want to leave that as a last resort.

   That's what I'd try; it's pretty close to useless as-is.

> Is it possible the IP of the admin interface changed? [...]

   Conceivable, but "Connection refused" suggests otherwise.  If you
tried your test at a known-useless address (say, "192.168.1.57"), then
I'd expect some different error message.  _Somethings_ seem to be
listening at the default address, just not its httpd (port 80).

> [...] It was a 1.9.x_XX_XX_XX version [...]

   If I had to choose a 1.9.xxx, it'd be V1.0.9.42_10.2.44, and then I'd
work my way up from there.  Probably to the latest
(V1.0.11.116_10.2.100?), and not necessarily gradually.

   The next challenge would be getting the thing to be receptive to a
TFTP load when it's only stupid, not mostly dead.  If its Power LED were
flashing, then you might expect it to take a TFTP load without special
effort.  This way, you might need to play with the Reset button (to get
it into the mood), and/or with the timing of the TFTP-PUT command (to

catch it when it is).