RT-AX86U bricked after update Version 3.0.0.4.386.48377

[tomeradio]

Here you go

 

[John Fitzgerald]

404 page error for download (Driver & Tool), Pulled?
One page/Tab has the new firmware listed, the other (Bios & Firmware) does not, no consistency.

 

[ducatinus]

Here you go

Some got lucky Again. I had a simple standard home-use setup, no fancy settings or tweaks.
Lessons learned: don't do a OTA app update but use ethernet and the webGUI

 

[ducatinus]

404 page error for download (Driver & Tool), Pulled?
One page/Tab has the new firmware listed, the other (Bios & Firmware) does not, no consistency.

View attachment 40779View attachment 40780View attachment 40779View attachment 40780

Yes, it was pulled this morning......think they where smart to do that because bricked routers with no change at fixing is bad publicity

 

[John Fitzgerald]

Yes, it was pulled this morning......think they where smart to do that because bricked routers with no change at fixing is bad publicity

Most of the CVE fixes were not for this model, based on: https://nvd.nist.gov/vuln/detail/CVE-2022-23970

 

[tomeradio]

some update guys,
you were all right about this firmware bricking ax86u/s.
I think this update is not even for the AX86U model, I think ASUS is messed up big time!
So I checked right now the system log file, and I was shocked I found that the AX86U was about to die if I wasn't checked the log file today.
there was so many kernel errors like dozens of messages spammed every second all night from yesterday (like every sec 24/7)
thank god I reverted back and manually re-flashed the router with the previous firmware.

 

[john385]

Some got lucky Again. I had a simple standard home-use setup, no fancy settings or tweaks.
Lessons learned: don't do a OTA app update but use ethernet and the webGUI

Mine was bricked after an ethernet update, not OTA, so it doesnt matter.
Seems this is a major bungle on ASUS’s part.
My router is in RMA process, returned it to the store this morning. :/

 

[Jbennett360]

some update guys,
you were all right about this firmware bricking ax86u/s.
I think this update is not even for the AX86U model, I think ASUS is messed up big time!
So I checked right now the system log file, and I was shocked I found that the AX86U was about to die if I wasn't checked the log file today.
there was so many kernel errors like dozens of messages spammed every second all night from yesterday (like every sec 24/7)
thank god I reverted back and manually re-flashed the router with the previous firmware.

How do you know it was about to die?

 

[ImpalerV]

I think the issue is with OTA. Myself and others that downloaded the file haven't had issues in this and other thread it seems or are there people that got bricked using manual update?

 

[Jbennett360]

I think the issue is with OTA. Myself and others that downloaded the file haven't had issues in this and other thread it seems or are there people that got bricked using manual update?

Has anyone done OTA (Via the app?) on the AX86U and had no issues?

It's looking like that's the culprit at the minute.

 

[tomeradio]

I think the issue is with OTA. Myself and others that downloaded the file haven't had issues in this and other thread it seems or are there people that got bricked using manual update?

I don’t know, but after i saw the system log is spamming kernel errors every sec for all night it kinda freak me out so I manually downloaded and flashed the previous version..
also first i tried to reboot router and mesh system to see if the errors are gone but then the AX86U not finding the aimesh nodes so i went and flashed the previous firmware.

 

[SeriousFamily]

Clicked the update button in the GUI, straight over the top of the previous version. no problems here.

ASUS RT-AX86U 5700 - purchased this item on 8 Aug 2021 - https://www.amazon.co.uk/gp/product/B08CBCR6BB/?tag=smallncom-21​

​

	0 days 21 hour(s) 3 minute(s) 32 seconds

 

[tomeradio]

How do you know it was about to die?

I don’t know, but after i saw the system log is spamming kernel errors every sec for all night it kinda freaked me out so I went and manually downloaded and flashed the previous version..
also first i tried to reboot router and mesh system to see if the errors are gone but then the AX86U not finding the aimesh nodes so i went and flashed the previous firmware.

 

[bbunge]

Sorry that some had problems with this update. I was able to do a successful flash, from an Ethernet connected PC, and manual configure. The router seemed to be working as it should but I was having issues with the WEB GUI when I changed a setting. Firefox was wanting to resend the data. I have not seen that before. Having saved the settings from the prior Merlin 386.5_2 I was able to easily go back.
Having some health issues I feel there are some advantages, for family protection, to have Auto Update enabled should something happen to me. Having passed the three score and fifteen mark today I have lived longer than all the male members of my fathers family since they came over in 1893.

 

[tomeradio]

Sorry that some had problems with this update. I was able to do a successful flash, from an Ethernet connected PC, and manual configure. The router seemed to be working as it should but I was having issues with the WEB GUI when I changed a setting. Firefox was wanting to resend the data. I have not seen that before. Having saved the settings from the prior Merlin 386.5_2 I was able to easily go back.
Having some health issues I feel there are some advantages, for family protection, to have Auto Update enabled should something happen to me. Having passed the three score and fifteen mark today I have lived longer than all the male members of my fathers family since they came over in 1893.

I had the exact same behavior on Firefox with this firmware.
(also came from Merlin 386.5_2)

 

[ColinTaylor]

Having passed the three score and fifteen mark today ...

Happy Birthday, and may you have many more.

 

[xander73]

My RT-AX86U brickage was over a lagged ethernet connection using Microsoft Edge going from 3.0.0.4.386.46061 to 3.0.0.4.386.48377...
As mentioned earlier, I had had a similar brickage with the ASUSWRT 386 RC3-2 public beta firmware - https://www.snbforums.com/threads/asuswrt-386-rc3-2-public-beta.75355/post-721622
Interesting how the RT-AX86U model was dropped from the RC3-3 public beta...

 

[OzarkEdge]

I notice that 48377 can still be found on the US website:

OE

 

[Kudzu]

Anyone successfully recover from this bad flash? My rt-ax86u is out of warranty and so not RMA'able as far as I know. I didn't try the update and don't have the problem but I'm wondering, how does one switch between the alternate boot and image partitions on this router? Seems like it has them, see below.

I've seen posts that say to repeatably reset the router right after boot and eventually it will switch. Is that how its done and would this address this bad flash situation?

mtd0
Name:                           rootfs
Type:                           nand
Eraseblock size:                131072 bytes, 128.0 KiB
Amount of eraseblocks:          760 (99614720 bytes, 95.0 MiB)


mtd1
Name:                           rootfs_update
Type:                           nand
Eraseblock size:                131072 bytes, 128.0 KiB
Amount of eraseblocks:          760 (99614720 bytes, 95.0 MiB)

mtd4
Name:                           image
Type:                           nand
Eraseblock size:                131072 bytes, 128.0 KiB
Amount of eraseblocks:          760 (99614720 bytes, 95.0 MiB)

mtd5
Name:                           image_update
Type:                           nand
Eraseblock size:                131072 bytes, 128.0 KiB
Amount of eraseblocks:          760 (99614720 bytes, 95.0 MiB)

 

[tomeradio]

I notice that 48377 can still be found on the US website:

View attachment 40785

OE

It can be found, but it can’t be downloaded.