What's new

Release Asuswrt-Merlin 3004.388.5 is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Upgraded through the 3004.388-5 Alpha's, Beta and now on the GA level. I do the Mesh units first as acheck the code is operational to the model, before doing the Router unit.
Thanks RMerlin for the time, energy and skills to deploy these updates. Without your support for ASUS Routers, myself and my friends/work mates, wouldn't have purchased as many ASUS Router products. ASUS branding then bleeds into purchasing Motherboards and Graphic cards too :)

On item of interest, after each of the 388-5 Alpha/Beta/GA updates on the GT-AXE1600, this message would be posted on browser panel after GUI invoked update.
View attachment 54633
With the first Alpha I just ignored, to avoid further disruption to the 50+ clients/devices at home. Then within 24-48hrs most of my seven Roost Water/Heat/Humidity units started dropping offline. If you manually re-connected them again, most dropped out again over 24-48hrs. Powered off/on the Router after the second Alpha and still no better. What did resolve the Roosts dropping out, was powering off/on the AXE16000 I have as a AiMesh unit.

All the Add-Ons (as per my signature) all working ok too on these levels.

BTW: I had to drop two Add-Ons in last few months: spdmerlin as caused random boots, scribe (forget why off top of my head). Diversion "Full" created issues with 'pixelserv' but Diverson "Lite" works a charm, key to disable 'type 65 blocking'.

“iOS 14 and newer, as well as a growing number of apps or devices use the type 65 query. Dnsmasq currently has no option to suppress or specifically handle these types of queries and therefore circumvent Diversion ad-blocking”

I mean I’ll keep using type 65 blocking since I have apple devices.

Now if only I can figure out what’s stopping my Microsoft updates from downloading. Have to use a VPN. Seems to be an issue on my buddy’s asus router also which is a stock router. Only similarity is using cloudflare dns. (Off topic)
 
Same here on AX86U

Dec 3 13:09:49 kernel: potentially unexpected fatal signal 11.
Dec 3 13:09:49 kernel: CPU: 0 PID: 2982 Comm: dnsmasq Tainted: P O 4.1.52 #2
Dec 3 13:09:49 (wan-event): 9188 Script not defined for wan-event: wan0-stopping
Dec 3 13:09:49 kernel: Hardware name: Broadcom-v8A (DT)
Dec 3 13:09:49 kernel: task: ffffffc02b9cea80 ti: ffffffc029494000 task.ti: ffffffc029494000
Dec 3 13:09:49 kernel: PC is at 0xf71bd654
Dec 3 13:09:49 kernel: LR is at 0x209ac
Dec 3 13:09:49 kernel: pc : [<00000000f71bd654>] lr : [<00000000000209ac>] pstate: 20010010
Dec 3 13:09:49 kernel: sp : 00000000ffb93ee8
Dec 3 13:09:49 kernel: x12: 0000000000000072
Dec 3 13:09:49 kernel: x11: 00000000000010f4 x10: 000000000009a70c
Dec 3 13:09:49 kernel: x9 : 00000000000010f8 x8 : 00000000ffffffff
Dec 3 13:09:49 kernel: x7 : 000000000009a70c x6 : 0000000000878f60
Dec 3 13:09:49 kernel: x5 : 00000000f726a5e8 x4 : 00000000ffb93d90
Dec 3 13:09:49 kernel: x3 : 0000000000000000 x2 : 0000000000000120
Are you running YazDHCP?
I kept getting dnsmasq fatal signal 11 running dnsmasq version 2.89 (the one in this release). It occurred right after reading the hostnames from YazDHCP.
For now I am running dnsmasq version 2.85 (from an older fw release).
I am hoping its fixed the next dnsmasq release. It’s been on 2.89 since Feb this past year.
 
This release is even more rock solid than either of the Alpha's or the Beta releases which were all pretty rock solid to start with.
Either that or I haven't any interference since applying the final, and the logs are for the most part clean, just the usual noise since rebooting after applying the firmware on the nodes, and router.

1701651832464.png


Checking in every so often, still pleasant bored 🤷‍♂️
 
Are you running YazDHCP?
I kept getting dnsmasq fatal signal 11 running dnsmasq version 2.89 (the one in this release). It occurred right after reading the hostnames from YazDHCP.
For now I am running dnsmasq version 2.85 (from an older fw release).
I am hoping its fixed the next dnsmasq release. It’s been on 2.89 since Feb this past year.
Had that issue as well, though since upgrading YazDHCP to v1.06, dnsmasq fatal signal 11 error have gone quiet.
 
All the Add-Ons (as per my signature) all working ok too on these levels.

BTW: I had to drop two Add-Ons in last few months: spdmerlin as caused random boots, scribe (forget why off top of my head). Diversion "Full" created issues with 'pixelserv' but Diverson "Lite" works a charm, key to disable 'type 65 blocking'.
I run spdmerlin on my AX88U for long time and no issues with all the latest firmware versions from Merlin - maybe it's an issue with your setup / incompatibility of add-ons?
 
Hello,

The firmware upgrade doesn't seem like it's working for me.

I've got an RT-AX86U (currently running 388.4 uploaded in last October, I believe).

I had downloaded the .zip file from sourceforge, verified sha256 through macos terminal and compared it with the asus-merlin download page.

I uploaded the pureubi.w file and numerous times I get this:
Screenshot 2023-12-04 at 02.47.57.png


Screenshot_2023-12-04_at_02_53_29.png


Sometimes the firmware upgrade asks me to manually reboot my router after the "unsuccessful" attempt (see first screenshot). Sometimes it doesn't.

I've logged out my router, cleared my browser, restarted my browser. I've redownloaded the sourceforge .zip file.

But the router webUI always shows the firmware version as 388.4

Anyone else having this issue?

-A
 
Hello,

The firmware upgrade doesn't seem like it's working for me.

I've got an RT-AX86U (currently running 388.4 uploaded in last October, I believe).

I had downloaded the .zip file from sourceforge, verified sha256 through macos terminal and compared it with the asus-merlin download page.

...
You should please read from page 2 of this thread...
 
Hello,

The firmware upgrade doesn't seem like it's working for me.

I've got an RT-AX86U (currently running 388.4 uploaded in last October, I believe).

I had downloaded the .zip file from sourceforge, verified sha256 through macos terminal and compared it with the asus-merlin download page.

I uploaded the pureubi.w file and numerous times I get this:
View attachment 54653

View attachment 54655

Sometimes the firmware upgrade asks me to manually reboot my router after the "unsuccessful" attempt (see first screenshot). Sometimes it doesn't.

I've logged out my router, cleared my browser, restarted my browser. I've redownloaded the sourceforge .zip file.

But the router webUI always shows the firmware version as 388.4

Anyone else having this issue?

-A

Try it connected via Ethernet from the router you wish to upgrade if you’re attempting this over wifi. Especially if you’re using a mesh network. About my only suggestion. At worst you could try removing any usb, factory resetting the router then attempt to flash the updated firmware.
 
Um, yeah... I did read through the thread, but I didn't think I got a clear answer from someone who successfully broke through the same problem as me.

Second, I do not USBs on my router, but I do have mesh. And I have tried to upload via ethernet a few times earlier (I forgot to mention).

And, I don't know what "dirty flash" means.**

**edited: ok, i looked it up. going to try it now. 🤞
 
Last edited:
Um, yeah... I did read through the thread, but I didn't think I got a clear answer from someone who successfully broke through the same problem as me.

Second, I do not USBs on my router, but I do have mesh. And I have tried to upload via ethernet a few times earlier (I forgot to mention).

And, I don't know what "dirty flash" means.**

**edited: ok, i looked it up. going to try it now. 🤞

Yeah dirty flash or dirty upgrade just means it was done without prior wiping the device back to factory defaults. Honestly most of the time factory resetting the device before upgrading firmware is not needed, but it eliminates the possibility of some issues arising from addon packages or custom configurations.

In bug testing you want a clean slate to focus on what the firmware itself is doing opposed to what issues addon packages might additionally cause. Addon packages should reasonably be taken care of by their respective developers after the firmware is released and stable. Most developers don’t support live (released) development during beta testing because things often change and would cause a support nightmare. Even though this firmware is released and for the most part considered stable, addon packages likely haven’t been updated since 388.4
 
Last edited:
Hello,

The firmware upgrade doesn't seem like it's working for me.

I've got an RT-AX86U (currently running 388.4 uploaded in last October, I believe).

I had downloaded the .zip file from sourceforge, verified sha256 through macos terminal and compared it with the asus-merlin download page.

I uploaded the pureubi.w file and numerous times I get this:
View attachment 54653

View attachment 54655

Sometimes the firmware upgrade asks me to manually reboot my router after the "unsuccessful" attempt (see first screenshot). Sometimes it doesn't.

I've logged out my router, cleared my browser, restarted my browser. I've redownloaded the sourceforge .zip file.

But the router webUI always shows the firmware version as 388.4

Anyone else having this issue?

-A
Have you accidentally downloaded the firmware for the pro model, or the RT-AX88U perhaps?
 
Dirty upgrade from 388.4_beta3 and no errors or problems as always.
Thank you, wizard.
 
“iOS 14 and newer, as well as a growing number of apps or devices use the type 65 query. Dnsmasq currently has no option to suppress or specifically handle these types of queries and therefore circumvent Diversion ad-blocking”

I mean I’ll keep using type 65 blocking since I have apple devices.

Now if only I can figure out what’s stopping my Microsoft updates from downloading. Have to use a VPN. Seems to be an issue on my buddy’s asus router also which is a stock router. Only similarity is using cloudflare dns. (Off topic)
Only reason I had to disable the "type 65" was because of YouTube's Cast or Airplay device selection. With "type 65" enabled our Apple iOS 16/17 and iPadOS 16/17 units went from instantaneous device selection, to 45-60 second (or longer) selection.
 
Did you download the correct firmware? There is another RT-AX86U Pro beside RT-AX86U.

Did you mount any USB drive from the router? Try unmount the USB drive before running the upgrade.


Hello,

The firmware upgrade doesn't seem like it's working for me.

I've got an RT-AX86U (currently running 388.4 uploaded in last October, I believe).

I had downloaded the .zip file from sourceforge, verified sha256 through macos terminal and compared it with the asus-merlin download page.

I uploaded the pureubi.w file and numerous times I get this:
View attachment 54653

View attachment 54655

Sometimes the firmware upgrade asks me to manually reboot my router after the "unsuccessful" attempt (see first screenshot). Sometimes it doesn't.

I've logged out my router, cleared my browser, restarted my browser. I've redownloaded the sourceforge .zip file.

But the router webUI always shows the firmware version as 388.4

Anyone else having this issue?

-A
 
forgot to unmount usb drives, but still went like a charm. 388.5 running flawlessly after dirty upgrade from 388.4 for 24 hours now. Thanks very much Merlin
 
Thank you for your response!

Tried redownloading the package from Onedrive (downloaded frm sourceforge yesterday) power cycling and other browsers (Edge and also a fresh install of Firefox), to no prevail. It keeps stating, that the firmware upgrade was unsuccessful and reverts to previous firmware.

Any help is very much appreciated, thanks!
 
What router model? What firmware is the 'previous firmware'? Are you using any USB drives? Are you using a PC to do these updates?

We need more information than, 'it's failing to upgrade'.
 
Status
Not open for further replies.

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top