Beryl 7 (GL-MT3600BE) 4.9.0 Beta 3 failed to update feedback

Router
1

Hi everyone,

I’ve tried on to two different occasions to update my Beryl 7 from 4.9.0 beta 2 to 4.9.0 beta 3. On both occasions after manually uploading the firmware file to the Beryl 7 router the file uploads successfully but it never updates the router. Instead the router appears to become unresponsive and requires a power cycle after 10 minutes to return the router to an operational state. After each failed attempt the router is still on 4.9.0 Beta 2.

Regards

John

5

Hi,

We were unable to reproduce the issue during our local testing of the system upgrade.
Could you please try upgrading the firmware via U-Boot and check whether the issue still occurs?
You can refer to this guide for the U-Boot upgrade process:

6

Hi Charles2,

Will do I’ll post my findings here.

Thanks

John

7

Hi Charles2,

I thought I’d try one more time doing the manual update via the GUI and the upgrade worked perfectly, thanks for your advice.

Regards

John

8

I had this also with the GL UI trying to upgrade from Beta1. Over wired or wireless. Upgrade works fine if you upgrade via Luci

9

There’s a new version of the firmware again today dated 7/7/2026, I’ll give that a spin when I get home from work.

10

I successfully updated to the new released version of the firmware last night and got a slightly different experience during the firmware update process. The updated loaded and I received a message at the top of the screen that the process was talking a long time, I’m not sure of the exact wording as it only appeared for a few seconds. After the verification of the file completed I then clicked on the install button. I didn’t see the normal count down timer instead the computer screen became unresponsive and I assumed the firmware update was underway. To keep track of the router I started a ping trace to its IP address noting it had gone unresponsive, so I assumed the update was in progress. After a few minutes the router’s login screen appeared and I logged in successfully, upon checking the firmware it had indeed updated to the new release 1 version of 4.9.0. This isn’t the normal path these updates take from my experience and it was hard to know what was going on while the computer screen was blank and unresponsive. I hope the engineering team can replicate this and resolve it for future beta and production releases of the firmware.