AX58U (AX3000) unable to update firmware in 386.1 beta unless factory default.

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

chchia

Occasional Visitor
Hi Merlin, thanks for the great firmware.

i have an AX3000 using AX58U firmware, after 386.1 alpha 3, every upgrade of firmware i will need to factory default the AX3000, otherwise the flashing will just failed without any error. please refer to picture below, from beta 1 to beta 2, it show please wait, Applying Settings, and AX3000 will be reboot without any upgrade of firmware.

I have another AC68U and it upgraded correctly to beta2.

is there anyway that i can upgrade AX3000 without the need of factory default? as i need to connect the AiMesh again after upgrade.

1608008512455.png


1608008753031.png
 

chchia

Occasional Visitor
after perform factory reset to default, the upgrade will be able to complete correctly.
 

Attachments

  • factory reset.png
    factory reset.png
    26.4 KB · Views: 37

RMerlin

Asuswrt-Merlin dev
Reboot without any USB disk plugged in to ensure you have enough free RAM to perform the upgrade.
 

Bulls729

Occasional Visitor
I posted about this same issue on Dec 8

Beta - Asuswrt-Merlin 386.1 Beta is now available | Page 18 | SmallNetBuilder Forums (snbforums.com)

"Have an interesting issue. I have an AX3000 and had been using the 58U FWs without issue until Alpha 3. I was unable to get Alpha 3 to A4 using the web interface, the router would just reboot without being updated. I had to use the FW Restore Utility to get it to upgrade. Once again, it’s doing the same thing unable to upgrade via the web interface from Alpha 4 to the Beta versions."

I did not have any USB devices plugged in.
 

John Fitzgerald

Senior Member
i dont use any USB devices. only aimesh system, with about 10 devices. not using any ATMT.

Wipe the JFFS partition and try again. (put a check in the box & scroll down to click APPLY, then reboot)
 

Theliel

Regular Contributor
Exactly the same here, performing a factory reset was necessary. In my case, I had a USB inserted, but neither formatting the JFFS partition nor disconnecting the pendrive. The web interface was not even trying to load the new image.

About new beta2 (after factory resetting and upgrading to beta2), QoS still doesn't work (before configuring anything else). The traffic is correctly identified, but nothing more else, there is no graph or count or anything. I don't know if it will be related, but despite using AiProtect too, and enabling QoS, HW acceleration appears enabled in all cases: "HW Archer: Enabled - Flow Cache: Enabled". Previously (the code base), Runner was disabled by QoS. I don't know if the new code by Asus allows to use now QoS / AiProtect with HW acceleration, but anyway, QoS still don't work here.

Thank
 

John Fitzgerald

Senior Member
Exactly the same here, performing a factory reset was necessary. In my case, I had a USB inserted, but neither formatting the JFFS partition nor disconnecting the pendrive. The web interface was not even trying to load the new image.

About new beta2 (after factory resetting and upgrading to beta2), QoS still doesn't work (before configuring anything else). The traffic is correctly identified, but nothing more else, there is no graph or count or anything. I don't know if it will be related, but despite using AiProtect too, and enabling QoS, HW acceleration appears enabled in all cases: "HW Archer: Enabled - Flow Cache: Enabled". Previously (the code base), Runner was disabled by QoS. I don't know if the new code by Asus allows to use now QoS / AiProtect with HW acceleration, but anyway, QoS still don't work here.

Thank

What CFE/Bootloader Version are the newer ones using?

If these are new out of the box( @chchia ) perhaps it would be best to load the newest stock firmware first, then do a factory reset, then do a Merlin firmware switch, then another factory reset and see how that lands.

Stock 384? ---> Stock 386
Stock 386 ---> Merlin 386
 
Last edited:

cmillar6

Senior Member
have an AX3000 using AX58U firmware, after 386.1 alpha 3, every upgrade of firmware i will need to factory default the AX3000, otherwise the flashing will just failed without any error. please refer to picture below, from beta 1 to beta 2, it show please wait, Applying Settings, and AX3000 will be reboot without any upgrade of firmware.

I had the exact same problem with the AX58u firmware going between alpha's. Merlin identified the issue with the AX58u firmware missing some component for hardware acceleration which for me was the cause of the reboots when flashing. This should have been addressed in Beta 1. Try formatting your JFFS partition at next boot and you should be able to flash normally again.
 

Theliel

Regular Contributor
I had the exact same problem with the AX58u firmware going between alpha's. Merlin identified the issue with the AX58u firmware missing some component for hardware acceleration which for me was the cause of the reboots when flashing. This should have been addressed in Beta 1. Try formatting your JFFS partition at next boot and you should be able to flash normally again.

please read, I'd the same issue from beta1 to beta2. Router was not rebooted in this case, also formatting JFFS didn't help. Maybe its only a coincidence, who know... for the next beta I will tell what happens.

And about CFE, my ax58u is on 0.0.0.5
 

chchia

Occasional Visitor
just to report that, 386.1 b3 solved this problem, i donot need to factory reset before apply update to AX3000.

i did not perform format jjffs nor disable AI Protection, i dont have USB devices.

thank your Merlin!
 

det721

Part of the Furniture
Strange never had any of these issues on my AX58U alpha's or any beta's all flashed with no problems.
 

John Fitzgerald

Senior Member
just to report that, 386.1 b3 solved this problem, i donot need to factory reset before apply update to AX3000.

i did not perform format jjffs nor disable AI Protection, i dont have USB devices.

thank your Merlin!

So you never ever have performed a JFFS format? (the size of this space has been adjusted with different firmware and has been a source of problems)
 

JWoo

Senior Member
Strange never had any of these issues on my AX58U alpha's or any beta's all flashed with no problems.
Also have an RT-AX58U and have flashed freely between 384 and 386 based ROMS without issue.
My NVRAM shows:
bl_version=0.0.0.5
boardrev=0x1101
boardtype=0x08a3
Would be interesting to see if anyone has a different BL or board rev that may be causing this.
 

John Fitzgerald

Senior Member
Also have an RT-AX58U and have flashed freely between 384 and 386 based ROMS without issue.
My NVRAM shows:
bl_version=0.0.0.5
boardrev=0x1101
boardtype=0x08a3
Would be interesting to see if anyone has a different BL or board rev that may be causing this.

I have the same as you.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

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