GL-RMQ1 firmware recovery?

KVM
1

I’m one of the Comet Q beta testers. I noticed the other day that 1.8.1 had been released as stable. Mine had 1.8.1 Beta on it, so I updated it via the web UI. The update seemed to get hung up, so I let it sit overnight. In the morning, it was still on the GL-iNet logo screen, so I removed and reapplied power (since there seemed to be no other option).

It appears to be stuck in a boot loop now. It shows the GL-iNet logo for about 15 seconds, flashes off for a moment, and repeats.

Is there a firmware recovery process for the GL-RMQ1? It doesn’t have the same ports as the other Comet models, so the existing instructions don’t really fit.

2

Hello @InvisiBill

Please use a standard 5V/3A to power on the Comet Q. Press and hold the reset button with a pin for 10 seconds, then check if it works properly.

4

Holding the reset button as it was powered on caused it to go into a slightly different loop. It would show the logo for a little over 10 seconds, then the screen would blank for 10 seconds, then it would repeat.

After removing power and reapplying, it returned to the original loop where it showed the logo for about 15 seconds, flashed off, then repeated.

5

May I know which beta version was running before the upgrade?

6

Hi,

I've sent you relevant tool and document on how to unbrick RMQ1. Please check the message and let us know if it works. Thank you

7

The instructions you sent worked. My Q is back up and running with 1.8.1 r3 now. Thanks!

1 Like
9

Today I noticed that 1.8.2 was available and decided to upgrade. Using the standard upgrade option in the web UI, I got similar (but slightly different) results.

The firmware downloaded and the upgrade process began. The Q’s screen changed to “Upgrading”, and the page in the browser said the process would take about 2 minutes. I left it there for 20 minutes, and it was still on the “Upgrading” screen, so I power-cycled it. The Q came back up normally, but it was still on 1.8.1.

For the second attempt, I manually downloaded the .swu file in my browser. In the Q’s web UI, I chose the Local Upgrade option and selected the .swu file I had downloaded. The file uploaded and the upgrade proceeded. After a minute or two, the page reloaded and the Q’s login screen came up. I logged back in and it was at 1.8.2 as expected.

I didn’t need to use the recovery process this time, but the standard web upgrade process did fail again. It’s a small sample size, but so far the “normal” upgrade process you would expect a user to follow has failed both times I’ve tried it.

10

Thanks for your feedback. Firmware v1.8.2 has optimized this problem. Please monitor the device to see if the problem persists after future firmware updates.