NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Ghostsquirrel74's avatar
Jun 10, 2019

R7000P Power light blinking red after firmware update

Hello!

 

I used the nighthawk app to update my firmware yesterday, after the reboot the power light started blinking red. I cannot see the SSID for either network for the router, nor can I access the router through ip in a web browser. I am unsure what to do at this point now, any help would be greatly appreciated. 

 

Thanks!

 

 

 

 

3 Replies

  • > I used the nighthawk app to update my firmware yesterday, [...]

     

       Using a web browser on a computer with a wired connection to the
    router might be more reliable.

     

    > [...] after the reboot the power light started blinking red. [...]

     

       You may be a candidate for the TFTP recovery scheme.  See, for
    example:

     

          https://community.netgear.com/t5/x/x/m-p/1622096

     

       To get the firmware kit, visit http://netgear.com/support , put in
    your model number, and look for Downloads.  (For older versions, under
    Firmware and Software Downloads, look for "View Previous Versions".)
    Find the kit(s).  Download the kit(s) you want.  Extract the files from
    the kit (if your web browser hasn't already done that for you.)

     

       Normally, then, you'd read the "Release Notes" file for instructions,
    but you'll be trying the TFTP recovery scheme instead of a normal
    update.  The User Manual for the device is in that same neighborhood,
    too (under Documentation).

    • Ghostsquirrel74's avatar
      Ghostsquirrel74
      Aspirant

      I have tried to do the TFTP Client reload multiple times now with no success. Is there anything else I can do?

      • antinode's avatar
        antinode
        Guru

        > I have tried to do the TFTP Client reload multiple times now with no
        > success.

         

           "tried" or "no success" is not a useful problem description.  It does
        not say what you did.  It does not say what happened when you did it.
        As usual, showing actual actions (commands) with their actual results
        (error messages, LED indicators, ...) can be more helpful than vague
        descriptions or interpretations.

         

           Which "the TFTP Client" did you use, on what type of computer?  What,
        exactly, did you do with it?  As documented, the TFTP firmware-load
        procedure has multiple steps, with multiple items of user-supplied data,
        and can be "tried" using multiple possible TFTP client programs.  That's
        too many variables for "tried" to be a useful problem description.

         

        > [...] Is there anything else I can do?

         

           A Web search for terms like:

         

              netgear  router  usb  serial  line


        should find details on a still more complex scheme, with even greater
        potential for problems.  I'd stick with the TFTP scheme (using a
        command-line TFTP client program supplied with your OS), at least until
        there's a better description of how the TFTP scheme was tried and
        failed.