ASUS RT-AX88U Firmware Update Failing

[mhandley92]

Hey all,

After doing tons of research, tests, and browsing this forum; I've decided to try and post to get a resolution for my router before I replace it.

Bought in 2021, has worked great but never been updated other than at purchase and switching to asuswrt-merlin 386.3. Tried to do a factory reset and firmware update 3 days ago because it would no longer allow me to login via the web gui. The update installs, completes, and then upon reboot it still shows 386.3. Since attempting, I am constantly losing packets between the firewall and endpoint. I work remote and can't even use teams calls, etc.

Things I've tried:
-I've tried many different firmware versions. Some from 2018, 386.4, 386.8, 388.1, 388.8, etc. All follow the same update with no error, goes to login page, still shows 386.3.
-I've tried different browsers.
-I've tried with the router fully disconnected from anything except the PC via lan port (no wan, no usb, nothing else connected).
-Factory resetting (WPS + Power, also from GUI)
-I attempted to turn on SSH. Seems to apply the setting, but does not listen on port 22, and doesn't accept connections.
-I attempted updating via rescue mode. (Unconnected power cable, held reset with paperclip, reconnected, Power LED slow blinking, Network adaptor IPv4 set IP and subnet mask). Utility just repeats that the router is not in rescue mode.

Is there any break glass method I can use to get this thing updated and back working?

 

[stephane_lunas]

I've got a similar problem, I cannot install the latest firmware and got stucked in 3004.388.9.2
I've also tried to restore the original Asus firmware for AX88U but when restore is done I'm back to 3004.388.9.2
My wifi connections are really slow and keep dissapearing every 2 or 3 minutes. It used to work fine but now it's just driving me mad.

When I click on update signatures for trent AV or search for an update in ASUS I also get an error. Please have a look at the screenshot

I've also tried the rescue router option but was not able to connect to the router. I've set my pc to 192.168.1.10 and 192.168.50.10 but none of them worked, after 30 secs, I get a timed out error message.
I would really appreciate if someone could help me to flash the router to latest firmware . Thanks in advance.

 

[zOi-br]

[Roteador sem fio] Como usar o modo de recuperação (restauração de firmware)? | Suporte Oficial | ASUS Brasil

Work for me.

 

[mhandley92]

I keep getting the error that the router is not in recovery mode. Nothing else is attached but my pc by lan port. The power is a steady slow blinking light. It's 100% in reacue mode.

My router is normally 192.168.50.1 so I am using 192.168.50.10 on the pc. No luck. Have tried other addresses as well.

 

[zOi-br]

I keep getting the error that the router is not in recovery mode. Nothing else is attached but my pc by lan port. The power is a steady slow blinking light. It's 100% in reacue mode.

My router is normally 192.168.50.1 so I am using 192.168.50.10 on the pc. No luck. Have tried other addresses as well.

Use the lan cable, go to the network card settings and put the specified ip on the site. Turn off the router, take a pointed object and insert it into the hole behind the router and hold it. Turn on the router and do not release the object that is in the hole, then only one light will start flashing slowly. Then you use the recovery software with the latest official asus update.

 

[zOi-br]

IP 192.168.1.10

^The IP has to be this one ^

 

[mhandley92]

*SOLVED*

For anyone that is having trouble getting your PC to view your router as being in Rescue Mode: Make sure you manually disable EVERY network adaptor other than ethernet, and disable the local Windows Firewall. I have Hyper-V services enabled (which created a vEthernet (Default Switch) adaptor and a few tailscale type services that create network adaptors. For Hyper-V, you have to fully disable the Hyper-V feature and restart. Disable the other network adaptors and wireless, so the PC only see's the ethernet connection to the router.

Then run the firmware restoration utility with the newest firmware. This is how I was able to get it resolved