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

Forum Discussion

mhmoran's avatar
mhmoran
Aspirant
Feb 02, 2025

AX1800 firm fails and bricks

Got a hand-me-down RAX15 ( ax1800 ) that probably had not had the firmware updated since 2020. The Android app identified it and asked for an update.  The update failed with an unprovided message,  effectively bricking the device.

The KB provides directions for using TFTP from Windows, but the device NEVER gives the signal to start the TFTP. 

Has anyone successfully manually updated an RAX15?

6 Replies


  • mhmoran wrote:

    Got a hand-me-down RAX15 ( ax1800 ) that probably had not had the firmware updated since 2020. The Android app identified it and asked for an update.  The update failed with an unprovided message,  effectively bricking the device.


    First check if the thing really is "bricked". What do the LEDs look like after the router boots? The power LED is the important one.

     

    How did you try the update? The app us generally pathetic. Wired and manual is best.

     

    How do I manually upgrade firmware to my NETGEAR router? | Answer | NETGEAR Support

     


    The KB provides directions for using TFTP from Windows, but the device NEVER gives the signal to start the TFTP. 


     

    TFTP is a picky process. It needs careful management and several attempts. It isn't the only option. There are a few videos out there that may help. Here's one:

     

     

    Different device. same process.

     

     


    Just another user with time on their hands.

    • mhmoran's avatar
      mhmoran
      Aspirant

      ||> mhmoran wrote:
      |> Got a hand-me-down RAX15 ( ax1800 ) that probably had not had the firmware/>

      |> updated since 2020. The Android app identified it and asked for an update. The

      |> update failed with an unprovided message, effectively bricking the device.


      Well, in my case the definition of bricked is the lights are on, but nothing responds. It is not issuing DHCP addresses, no traffic is moving ( wired or wireless - traffic scanners see nothing from it ), and finally, the internet port doesn't light when connected to the broadband modem.

       

      |> How did you try the update? The app us generally pathetic. Wired and manual is

      |> best.

       

      Unfortunately, I let the Android version of the app to the upgrade.  I told me that the update failed and asked if I wanted to send in a crash report.  I sent it in.

       

      The manual attempt was made by trying to follow the cited article

       

      |>  How do I manually upgrade firmware to my NETGEAR Router? | Answer | NETGEAR Support 

       

      The problem I'm having is that the directions is the article do NOT match what I'm seeing ( or their definition of blinking is different  from mine ).  Specifically, it says to start the TFTP transfer when the power light is blinking
      From the article:
                9.  Wait for the Power LED to light orange and start flashing.

              10. When the Power LED is flashing, return to the Command Prompt app and  press Enter to execute the tftp command and initiate the firmware upload. 

      The problem I'm having is that the Power LED  NEVER flashes.  It goes from solid
      orange to solid white, and shortly thereafter the Internet light goes orange, followed by the WIiFi light going white.  Even though port 1 is connected between a Windows matching and the router, the port light stays dark.

       

      Thanks for the link to the video.  I watched it, it says the same thing as the original article .. power light flashing to be able to connect.  I never get a flashing power light.


      • mhmoran wrote:


        Well, in my case the definition of bricked is the lights are on, but nothing responds. It is not issuing DHCP addresses, no traffic is moving ( wired or wireless - traffic scanners see nothing from it ), and finally, the internet port doesn't light when connected to the broadband modem.

        The "bricked" label is widely abused, partly because it has no real technical meaning. No surprise then that your definition is at odds with the more widely used notion of busted firmware.

         

        What do the lights actually look like? What colour is the power LED and what is it doing? Flashing or solid?

         


        The problem I'm having is that the Power LED  NEVER flashes.  It goes from solid
        orange to solid white, and shortly thereafter the Internet light goes orange, followed by the WIiFi light going white.  Even though port 1 is connected between a Windows matching and the router, the port light stays dark.

         


        If it is "solid white" it isn't bricked in the sense that the firmware shows no sign of being damaged.

         

        Step back and explain what you are doing. What is the router connected to? What do you mean by " port 1 is connected between a Windows matching and the router"? Machine?

         

        You can get odd behaviour of you try adding another router to your existing router. If you can plug it into a PC with nothing else in there, what happens when you try to use a web browser and the graphical user interface (GUI)?

         

        The bottom line may be that this is a dead router. But there are a few things that you can try to pin that down.


        Just another user with time on their hands.

  • I'd agree with michaelkenward on the bricking. What makes you think its bricked? 

    What are all the led's on it doing? (color, blinking, solid, etc)