Tried to update to latest firmware (3.0.0.4.388_24231) after seeing there was an update available, via phone app first then via WebGUI, would get to 100% and say update failed. Router still worked at this point.

I attempted to update in recovery mode following Asus guidance, it failed there too except router now bricked. Tried repeatedly and kept failing. I can get a successful recovery message trying to apply the version I tried to update from (3.0.0.4.384.10177) and the original release (3.0.0.4.384.9261) but I can’t communicate with the router, doesn’t recognise any ethernet connection. The front RGB light flashing red. It only recognises the router exists in recovery mode but that’s not usable.

Router is 3 years old so expect I’ll get no help from Asus and don’t really want hassle with customer service.

Any tips or succumb to getting a new router?

I found a thread for AX86 and saw references to older release notes suggesting to not update to earlier new versions straight away, but there was no warning in the release note for 3.0.0.4.388_24231. Pretty annoyed. I’m a networking noob and only updated because I was prompted in the app, and thought I should for general security purpose. I only went into the app to assign my PS5 as a game device to reduce my ping!

Any help greatly appreciated.

  • RagnarLunchbox@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Oh, and another thing, make sure you dont have any security settings with your browser that can impede the CFE website on the router. Brave is good at breaking this sort of thing. Turn the router OFF for a full minute or two and disconnect power before you start the process of entering recovery mode, we need that NVRAM free of junk from the broken upload.

    If you miss getting the router into recovery mode on the first try due to timing, disconnect power and wait again before starting over. This sounds odd, but a lot of junk can stay in RAM for quite a while after power off, and youre last firmware is broken so we dont know how thats going to impact.

    • OtterSpotter2@alien.topOPB
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Thanks, if I could award you I would! Can see you’ve put a lot of effort and detail in

      I managed to use TFTP2, get a ping and Upgrading flash status with progress for about a minute, until it goes to erasing flash stage, then I can see in CMD the ping fails (that’s handy to see anyway), still with the Asus firmware (I don’t think I can use third party). Had a few attempts with different versions and all still failing.

      The TTL cable is maybe a step too far for me. Think the router may be going on eBay!

      Still thank you

  • TheEthyr@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I don’t own an Asus but I have recovered routers of other brands. It’s been years since I recovered a router so I haven’t kept up to date with the latest developments.

    I assume that the recovery process you tried was the Asus Rescue Mode. If not, it’s documented here.

    If that doesn’t work, many routers have a serial port that can be used to assist with the recovery. I found this post that lists the steps. It’s for a different Asus router but it will probably work on yours.

    As you’ll see, it’s quite involved and requires you to buy a special type of serial cable (called a TTL-level cable). The cable is readily available on Amazon from a number of places and is not that expensive. It’s certainly cheaper than buying a new router. You have to open the router to connect the cable to the serial port inside. Then follow the process to start a TFTP upload of firmware.

    Take a look, then decide if it’s something you are willing to try. You probably don’t have anything to lose other than a few $ for the serial cable.

    Good luck.

  • RagnarLunchbox@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I forgot to mention, theres actually a whole underworld of router hardware hackers out there (me included) who add custom firmware to these consumer devices - and thus never have these issues. Ever.

    A part of hacking router hardware means somtimes “alternative” ways uploading unbricking are needed, and the bwlow link is one such example. Asus routers looks like they all use a simple TFP recovery mode which wont specifically need the Asus recovery app, (which is prob rubbish anyway), you just need a TFP server and the right sequence and timing of upload.

    Here is a hacker’s recovery method for a similar model… Asus are likely all the same.

    https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1208723

    Manual unbricking should be faily straight forward if you pay attention to those steps. They should also map to what the recovery app is trying to do as well, jst without the flakiness.

    On a side note, these Asus models look like more security and stability hassles than they are worth OMG Asus firwares have broken so many motherboard and routers this year. Next time, buy somthing compatible with DDWRT (easy) or OpenWRT (adavnced) firmware. This always means avoiding routers with Broadcom based chipsets. Confirm future purchases with these links and play… you’ll never look back…

    https://openwrt.org/toh/start

    https://dd-wrt.com/support/router-database/