Release ASUS TUF-AX6000 Firmware version 3.0.0.4.388_33965 (2025/10/23)

[denis]

I'm sorry, I don't understand that sentence. What are wi-fi only lan connections?

That means I have all devices connected wireless.
Considering your question I'm advising you against fiddle with OpenWRT.
Stick with the original firmware.
No offence.

 

[kp333]

When using version 33965, I experienced intermittent image loading delays or web page loading failures. After changing to version 33427, these symptoms have disappeared at all. It seems that ASUS has no intention of fixing it even after almost a year. All routers that use MT7986a, such as 59u or ax4200, have the same symptoms

 

[denis]

When using version 33965, I experienced intermittent image loading delays or web page loading failures. After changing to version 33427, these symptoms have disappeared at all. It seems that ASUS has no intention of fixing it even after almost a year. All routers that use MT7986a, such as 59u or ax4200, have the same symptoms

I don't think Asus is not wanting to fix,think that they have no clue what is causing it..... finding out it takes time and cost money, for them is cheaper to release another hardware router with different chipset than fix the broken ones with latest firmware.....

 

[dparakatis]

Hi,
I’m sharing this in case it helps other users troubleshoot a similar issue with the ASUS TUF AX4200 v2, which seems a similar issue with other same family routers (ie AX-6000).
After introducing a TUF AX4200 v2 into an existing, previously stable AiMesh network, we started experiencing random Wi-Fi lags / client stalls.
The situation was temporarily fixed by turning off & on the WiFi of the device. After 2-5 mins, same issue appeared.

The stock/out of the box firmware version had been immediately upgraded to 3.0.0.4.388_33965 (as per usual practice when out of the box new equipment).
Testing an older firmware version — specifically 3.0.0.4.388_33506 — resolved the problem completely in this case.

You may check my complete input on this in ASUS forum :

https://rog-forum.asus.com/t5/gaming-routers/tuf-ax4200-v2-random-wi-fi-lag-in-aimesh-resolved-by-downgrading/m-p/1137474#M11237

 

[kp333]

I don't think Asus is not wanting to fix,think that they have no clue what is causing it..... finding out it takes time and cost money, for them is cheaper to release another hardware router with different chipset than fix the broken ones with latest firmware.....

Yeah, they don't seem to know the cause. It happened in 2025 and it's still the same even after a year :'(

 

[kp333]

Hi,
I’m sharing this in case it helps other users troubleshoot a similar issue with the ASUS TUF AX4200 v2, which seems a similar issue with other same family routers (ie AX-6000).
After introducing a TUF AX4200 v2 into an existing, previously stable AiMesh network, we started experiencing random Wi-Fi lags / client stalls.
The situation was temporarily fixed by turning off & on the WiFi of the device. After 2-5 mins, same issue appeared.

The stock/out of the box firmware version had been immediately upgraded to 3.0.0.4.388_33965 (as per usual practice when out of the box new equipment).
Testing an older firmware version — specifically 3.0.0.4.388_33506 — resolved the problem completely in this case.

You may check my complete input on this in ASUS forum :

https://rog-forum.asus.com/t5/gaming-routers/tuf-ax4200-v2-random-wi-fi-lag-in-aimesh-resolved-by-downgrading/m-p/1137474#M11237

4200v2 cpu is MK7986A ?

 

[asal]

Following up on ugdp3's post in the RT-AX59U thread, I’ve found information suggesting that the "broken" builds might be due to a specific buggy MediaTek driver/firmware version.

According to this GitHub resource, the 20231229 version (which may be the same as the 20231228 version currently used by ASUS) is known to cause lag and stutter. The developer recommends switching to 20240823 for stability.

Considering that intermediate versions also have known security vulnerabilities, updating to the 20240823 build is essential. These firmware variants mentioned in the above GitHub repo seem to align with the commit logs found in MediaTek’s official open-source repository:
https://git01.mediatek.com/plugins/...kage/kernel/mt76/src/firmware/mt7986_wo_0.bin

Hopefully, ASUS will find this and update the MediaTek SoC driver/firmware to the proper stable version in the next release...

 

[kp333]

Following up on ugdp3's post in the RT-AX59U thread, I’ve found information suggesting that the "broken" builds might be due to a specific buggy MediaTek driver/firmware version.

According to this GitHub resource, the 20231229 version (which may be the same as the 20231228 version currently used by ASUS) is known to cause lag and stutter. The developer recommends switching to 20240823 for stability.

Considering that intermediate versions also have known security vulnerabilities, updating to the 20240823 build is essential. These firmware variants mentioned in the above GitHub repo seem to align with the commit logs found in MediaTek’s official open-source repository:
https://git01.mediatek.com/plugins/...kage/kernel/mt76/src/firmware/mt7986_wo_0.bin

Hopefully, ASUS will find this and update the MediaTek SoC driver/firmware to the proper stable version in the next release...

I also checked that post but it is very frustrating because Asus is not interested at all (they are not even aware of the problem) :'(

 

[fruitcornbread]

@asal Based on the "mt_wifi.ko" file found in the trx/lib/modules/ for official TUF-AX6000 firmware:

• TUF-AX6000_3.0.0.4_388_33965-g895dddb.trx = Kernel 5.4.246 Mediatek wifi driver 7.6.7.2 build 20240626
• TUF-AX6000_3.0.0.4_388_33950-g847b78e.trx = Kernel 5.4.246 Mediatek wifi driver 7.6.7.2 build 20240626
• TUF-AX6000_3.0.0.4_388_33911-gf36c0bb.trx = Kernel 5.4.246 Mediatek wifi driver 7.6.7.2 build 20231228
• TUF-AX6000_3.0.0.4_388_33903-gf5cd6c5.trx = Kernel 5.4.246 Mediatek wifi driver 7.6.7.2 build 20231228
• TUF-AX6000_3.0.0.4_388_33427-gc525e4e.trx = Kernel 5.4.225 Mediatek wifi driver 7.6.7.0 build 20230814

@dparakatis FYI, TUF-AX4200's beta firmware that were uploaded on ASUS' webstorage in 2024 / 2025:

• TUF-AX4200_3.0.0.4_388_33957-ge8b1967_downgrade_sdk_to_v7670.trx = Kernel 5.4.246 Mediatek wifi driver 7.6.7.0 build 20230814
• TUF-AX4200_9.0.0.4_388_33914-gc99eb3d_test1.trx = Kernel 5.4.246 Mediatek wifi driver 7.6.7.0 build 20230814
• TUF-AX4200_9.0.0.4_388_33512-g0a64af8.trx = Kernel 5.4.225 Mediatek wifi driver 7.6.7.0 build 20230814
• TUF-AX4200_9.0.0.4_388_33507-g4deef75_iot.trx = Kernel 5.4.225 Mediatek wifi driver 7.6.7.0 build 20230814

1. Almost all the beta firmware were based on Mediatek wifi driver 7.6.7.0 and build 20230814 which is the same as official TUF-AX4200_3.0.0.4.388_33506 with the exception of TUF-AX4200_9.0.0.4_388_33964-gd52d0ef.trx = Kernel 5.4.246 Mediatek wifi driver 7.6.7.2 build 20240626.
2. There was one more beta firmware TUF-AX4200_9.0.0.4.388_33912 that Ask1 had mentioned back in May 2025, but the download link no longer works so I can't check it. However, I assume it's based on Kernel 5.4.246 Mediatek wifi driver 7.6.7.0 build 20230814 as well.

As there are no release notes for these beta firmware and they are not released typically to the public so I would update at your own discretion.

TUF-AX4200 official firmware driver / build:

• TUF-AX4200_3.0.0.4_388_33965-g895dddb.trx = Kernel 5.4.246 Mediatek wifi driver 7.6.7.2 build 20240626
• TUF-AX4200_3.0.0.4_388_33950-g847b78e.trx = Kernel 5.4.246 Mediatek wifi driver 7.6.7.2 build 20240626
• TUF-AX4200_3.0.0.4_388_33920-gbb1345b.trx = Kernel 5.4.246 Mediatek wifi driver 7.6.7.2 build 20240626
• TUF-AX4200_3.0.0.4_388_33903-gf5cd6c5.trx = Kernel 5.4.225 Mediatek wifi driver 7.6.7.2 build 20231228
• TUF-AX4200_3.0.0.4_388_33506-gb8edbc3.trx = Kernel 5.4.225 Mediatek wifi driver 7.6.7.0 build 20230814

RT-AX59U official firmware driver / build:

• RT-AX59U_3.0.0.4_388_33965-g895dddb.trx = Kernel 5.4.246 Mediatek wifi driver 7.6.7.2 build 20240626
• RT-AX59U_3.0.0.4_388_33950-g847b78e.trx = Kernel 5.4.246 Mediatek wifi driver 7.6.7.2 build 20240626
• RT-AX59U_3.0.0.4_388_33911-gf36c0bb.trx = Kernel 5.4.246 Mediatek wifi driver 7.6.7.2 build 20231228
• RT-AX59U_3.0.0.4_388_33903-gf5cd6c5.trx = Kernel 5.4.246 Mediatek wifi driver 7.6.7.2 build 20231228
• RT-AX59U_3.0.0.4_388_33407-g30d8d49.trx = Kernel 5.4.225 Mediatek wifi driver 7.6.7.0 build 20230814

Edit: added kernel info.
Edit 2: added RT-AX59U official firmware info

 

[Unhappy ASUS user]

@fruitcornbread
Hi, Asus support sent me the beta firmware TUF-AX4200_3.0.0.4_388_33957-ge8b1967_downgrade_sdk_to_v7670.trx to try, as you yourself write this firmware should work because they rolled back the driver, but this firmware does not work, the same problems occur, the last working firmware is FW_TUF_AX4200_300438833506.
It's strange, but the problem must be something else, for example, modified security that is not compatible with the chip design. Maybe that's why ASUS is making a dead bug, because the problem cannot be fixed.

 

[denis]

I don't think Asus is not wanting to fix,think that they have no clue what is causing it.....so finding out it takes time and cost money, so for them is cheaper to release another hardware router with different chipset than fix the broken ones with latest firmware.....

It is nothing to do with the wireless driver,Asus technicians should understand that. Why I'm definitely sure because with all old/latest firmware openwrt this issue never happens. And the security patch is latest on their firmware.

@fruitcornbread
Hi, Asus support sent me the beta firmware TUF-AX4200_3.0.0.4_388_33957-ge8b1967_downgrade_sdk_to_v7670.trx to try, as you yourself write this firmware should work because they rolled back the driver, but this firmware does not work, the same problems occur, the last working firmware is FW_TUF_AX4200_300438833506.
It's strange, but the problem must be something else, for example, modified security that is not compatible with the chip design. Maybe that's why ASUS is making a dead bug, because the problem cannot be fixed.

 

[UltrashRicco]

It is nothing to do with the wireless driver,Asus technicians should understand that. Why I'm definitely sure because with all old/latest firmware openwrt this issue never happens. And the security patch is latest on their firmware.

It DOES seem to be related to the Mediatek wireless driver/firmware v7.6.7.2 between build 20231228 and build 20240823 according to @asal

According to this GitHub resource, the 20231229 version (which may be the same as the 20231228 version currently used by ASUS) is known to cause lag and stutter. The developer recommends switching to 20240823 for stability.
[...]
Hopefully, ASUS will find this and update the MediaTek SoC driver/firmware to the proper stable version in the next release...

I guess there is no way to unpack the ASUS FW package or get the source code, and build a new version with the latest driver, plus it may very well break other things.

I understand that it is hard to justify dedicating time and effort to "legacy" products, but the inconvenience here is not minor, especially with ASUS shipping their routers with automatic updates enabled, likily resulting in most of the users suffering from the issue...

This gives ASUS a bad image, but the fact that they are unable/unwilling to fix it is even worse.
I most likely won't purchase a product from Asus again, and certainly not consumer-grade network equipment.

I am not affected by the issue after disabling IPV6 (not a good workaround though), and going back to FW v3.0.0.4_388_33427 is still another (bad) option.

I need to overcome the procrastination and give OpenWRT another shot.
I guess not everything is easily doable from the GUI, so learning network command line commands is key here.
One limitation I have with the current ASUS FW/GUI is the limited firewall features, especially I cannot control/forward outbound traffic at all, if I understand correctly. (I want to force ALL outbound DNS traffic through my PiHole on a specific local IP address).

 

[denis]

It DOES seem to be related to the Mediatek wireless driver/firmware v7.6.7.2 between build 20231228 and build 20240823 according to @asal

I guess there is no way to unpack the ASUS FW package or get the source code, and build a new version with the latest driver, plus it may very well break other things.

I understand that it is hard to justify dedicating time and effort to "legacy" products, but the inconvenience here is not minor, especially with ASUS shipping their routers with automatic updates enabled, likily resulting in most of the users suffering from the issue...

This gives ASUS a bad image, but the fact that they are unable/unwilling to fix it is even worse.
I most likely won't purchase a product from Asus again, and certainly not consumer-grade network equipment.

I am not affected by the issue after disabling IPV6 (not a good workaround though), and going back to FW v3.0.0.4_388_33427 is still another (bad) option.

I need to overcome the procrastination and give OpenWRT another shot.
I guess not everything is easily doable from the GUI, so learning network command line commands is key here.
One limitation I have with the current ASUS FW/GUI is the limited firewall features, especially I cannot control/forward outbound traffic at all, if I understand correctly. (I want to force ALL outbound DNS traffic through my PiHole on a specific local IP address).

According to

It DOES seem to be related to the Mediatek wireless driver/firmware v7.6.7.2 between build 20231228 and build 20240823 according to @asal

I guess there is no way to unpack the ASUS FW package or get the source code, and build a new version with the latest driver, plus it may very well break other things.

I understand that it is hard to justify dedicating time and effort to "legacy" products, but the inconvenience here is not minor, especially with ASUS shipping their routers with automatic updates enabled, likily resulting in most of the users suffering from the issue...

This gives ASUS a bad image, but the fact that they are unable/unwilling to fix it is even worse.
I most likely won't purchase a product from Asus again, and certainly not consumer-grade network equipment.

I am not affected by the issue after disabling IPV6 (not a good workaround though), and going back to FW v3.0.0.4_388_33427 is still another (bad) option.

I need to overcome the procrastination and give OpenWRT another shot.
I guess not everything is easily doable from the GUI, so learning network command line commands is key here.
One limitation I have with the current ASUS FW/GUI is the limited firewall features, especially I cannot control/forward outbound traffic at all, if I understand correctly. (I want to force ALL outbound DNS traffic through my PiHole on a specific local IP address).

According to "Unhappy ASUS user" who tested the latest firmware with wi-fi drivers prior to the issue.And,it is still behaving the same.That why I'm thinking is got nothing to do with wi-fi drivers.A thumb up for ASUS for trying to find a fix for the issue.