I've bricked my ASUS RT-AX53U

Dear community, I need help. I destroyed my ASUS RT-AX53U.

I tried a self-compiled OpenWRT image with my own settings and packages, flashed it, and now it's dead. The router boots up, the ON/OFF light flashes, Ethernet on the router is accessible for about 2-3 seconds, and then it's dead, probably a kernel panic or some kind of loop. Wi-Fi doesn't even activate.

I've read the documentation on debricking, but I'm stuck. Failsafe mode doesn't work for me, or maybe I'm just too stupid :frowning:

I really don't know what to do.

Best regards,

Beowulf

Read the "Installation with TFTP / ASUS Firmware Restoration utility" chapter on the page you posted ?

3 Likes

You can always restore to OEM FW and try again
https://www.asus.com/support/faq/1000814/

Probably you removed some ubus or netif compiling. Just dont do it again?

Doesn't work for me because I can't maintain an Ethernet connection.

The ASUS firmware tool is very unreliable (EDIT: for me). I don't have a native Windows 10/11 host, but I have a virtual machine that passes through the physical Ethernet port of my host.

Unfortunately, the ASUS program is incredibly unstable (EDIT: for me). It loads, sends the file up to about 30-50% and then drops the connection again.

I have actually only selected my router, a few packages that should be included in the image by default and added security during the compilation. In addition, my network configuration and other settings that I would otherwise make manually are imported straight away.

I'm sure I could physically repair the router on the serial port, but I've never done that before.

But can't I put my router into some kind of recovery? Is this not included in self-compiled images or am I doing something wrong?

Are you blaming the tool for running Win in a VM ?

There's however
https://github.com/jnissin/arescue.

If inaccessible means secure, mission accomplished ,)

It's not very hard.
It's also described on the page you linked to earlier.

No, no, I used this tool back when I was still a pure Windows user. Maybe it's just the router that isn't quite keeping up. It's also several years old now.

I agree, it's great, no attack surface from the Internet and not even physical! The thing is now a little plastic tank.

Hopefully I won't have to go that far, because then I'll have to get the materials. Let's see...

I have tried, but nothing happens. Nothing happens, as if I didn't have all these modes. Maybe I'll put the router aside for now, let my thoughts rest for a few hours and then get back to it with renewed vigor.

I'd try the Linux version of the recovery tool, before shelving it.
It's really only a shell for ifconfig and tftp (client), you can probably do it yourself by following the link on the GitHub page.

LAN1 should respond in failsafe and recovery. Are you sure you tried all ports?

Do not us a VM for this. atftp in linux should work to send asus trx firmware.

(https://chrishardie.com/2013/02/asus-router-firmware-windows-mac-linux/)

2 Likes

Works with Windows 7 too, your assumption is completely wrong.

I will try it, thanks for the link.

No, I haven't tried all the LAN ports. But I will try today.

I am not making any special assumptions, perhaps the tool is not working properly on my Windows hosts because I have heavily customized my systems and the tool has become unstable as a result of it.

I can only speak for my experience, and I have always had problems with the ASUS flash tool.

It's probably 99% something in my setup.

So the ball is with you, uncustomize your "systems" to make them work.

General note on flashing via tftp:
If you have a dumb unmanaged desk switch, put it between the router and your PC, to avoid carrier up and down events.

1 Like

Didn't work. I got myself a fresh Windows 11 laptop, unmodified, from a friend, and this firmware tool still doesn't work. It seems that when I touch computer systems, they burst into flames internally.

At least I was able to put the router into recovery mode (or something similar) by turning it off completely, holding down the RESET button, and turning it back on. Now I have a stable Ethernet connection, but the router is not responding to pings. I also tried the arescue tool and TFTP manually, but nothing works.

$ tftp

(to) 192.168.1.1

tftp> binary

tftp> put RT-AX53U_3.0.0.4_386_69155-g0a07ff2.trx

Transfer timed out.

I'm slowly starting to feel that my own image has ruined a lot of things, and that the router can only be saved by physical intervention.

How is that happening? There are multiple "recovery" modes. The tftp is to power on with reset pushed for 15s into boot.

Both failsafe and recovery should respond.

AFAIK, Asus recovery software will always complete to 100% and your unit will reboot. It can take 5-15minutes for this entire process.

If you are absolutely sure you did everything correctly, serial is your only option now.

It is blurry lines, OpenWrt cannot brick OEM bootloader stone dead, you have to really enter the tftp mode carefully.

I can't get the router to work and feel like I'm severely disabled.