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

Forum Discussion

SebastianH's avatar
SebastianH
Aspirant
Jul 31, 2021

Bricked R6400 won't let me interrupt loop from putty

Hi,

 

My R6400 wifi router keeps looping in startup. (It happened after a power cycle from all my gear)

Using a CP2102 USB-UART cable and Putty i managed to see what was going on inside the router.

Usually you can break this router startup into CFE-prompt and do a tftp session to recover firmware.

But now it is impossible to break the loop in Putty. I'm not sure what to do next.

Attached is the output from my putty session.

(another strange behaviour: The router will not startup connected with the PC-USB_UART cable/First i have to power on Router and after that connect the USB to the PC etc)

Maybe someone of this community understands whats going on and can help me?

Thanks for your time!

 

Regards,

Sebastian

 

5 Replies

    • SebastianH's avatar
      SebastianH
      Aspirant
      Hi Oliver, thanks for your reply!

      I’m familiar with the firmware flashing procedure. Thanks for the link. The problem is I can’t get the device into flashing mode. The LEDs are blinking in a certain sequence corresponding with the boot phase which seems to be infinite and I cannot interrupt (using Putty). Unfortunately i can’t attach a video with the blinking LEDs sequence. Any chance this can be resolved? Or is the device really bricked?

      Regards,
      Sebastian
      • antinode's avatar
        antinode
        Guru

        > [...] it is impossible to break the loop in Putty. [...]

         

           You know this because you did everything possible in PuTTY?  I'd
        expect that to take a _very_ long time.

         

        > [...] I cannot interrupt (using Putty).

         

           "impossible" or "cannot" 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.

         

           You _might_ actually know what you're doing, but that's not obvious
        from your problem description.

    • olympos1625's avatar
      olympos1625
      NETGEAR Employee Retired

      Hi SebastianH,

       

      Thank you for all the information that you have provided. It seems that the router got bricked for some reason. How long do you have the device? Please DM us the serial number of the router.

       

      Please do not hesitate to let me know if you need further assistance. 

       

      Regards,

       

      Oliver

      Community Team