Brume2 on 4.6 - Dead

Technical Support for Routers
1

Dear community,

I am reaching out for your help.

Yesterday, I updated my Brume2 to firmware 4.6 (keeping my configuration), as it was offered in the web GUI. Unfortunately, this update did not go well.

The router rebooted (presumably), and I was not able to connect to it anymore. No DHCP was working, and even a manual IP address setup did not work. There was no connectivity.

I tried a factory reset several times without any success. Again, no connectivity. Then I attempted the debrick procedure with firmwares 4.6, 4.5.16, and 4.4.6, but still no connectivity.

I tried to set up a USB console with "screen", but even this did not work.

So, it seems I must consider the Brume2 to be completely destroyed, which would be a huge bummer after a firmware online update...

Does anyone have any ideas?

Thanks in advance.

2

What exactly did you do to debrick? Debricking using U-boot?
Any messages during this process?

3

I downloaded the firmeware for the Brume2 from here: GL.iNet download center
and used this documentation for uploading the firmware: Debrick via Uboot - GL.iNet Router Docs 4

So, pressing the reset button on the Brume2 while plugging it in, waited that the LED went static, and accessed 192.168.1.1 via Browser. I did not upgrade the Uboot as mine is from 2022, which seems to be the current one.

I uploaded the firmware via the web interfade, which went bad on Linux (I always got an error message) but went well on MacOS. The web interface showed that the firmware was correct, I pressed "update" and after a while the router rebooted. But still no connecton possible on LAN (or even WAN).

4

Maybe email customer service to get replacement.

1 Like
5

You mean GL customer service? Do you have the email address maybe?

6

support@glinet.biz or Contact Us - GL.iNet

7

What was the resolution here? My Brume2 bricked yesterday after upgrading for 4.7...

8

Did you already try Debrick via Uboot?

9

Follow my instructions to recover the brume 2 and see if that helps.

1 Like
10

thanks @sumolx for your hint. I can at least debrick the Brume2 to use the openWRT snapshot now. Luci could be installed with SSH, so that the web interface could be used.

But if i try to flash any image from GL.iNet download center (incl. the latest 4.7.0) using Luci, i get the same result like using uboot before, i.e. stuck after rebooting, no IP is assigned.
Unfortunately your provided link for the 4.7.0 beta 9 is no more available, therefore i cannot try.

Currently if i want to use my Brume2, i need to stay with the openWRT snapshot image :sweat_smile:

11

With openwrt flashed try a factory config default erase then try to flash the GL firmware again via uboot.... that may have been the key step or maybe I just got lucky.... but I do know that if you try to flash the official using then openwrt GUi method it will report a CPU mismatch against official GL firmware which is strange.

1 Like
12

you really got lucky @sumolx. I tried a factory reset from the openWRT snapshot and apply uboot recovery after that with image for 4.7 and for 4.6.10 (provided by the support team). None of them worked :confused:

The warning about mismatch device is understandable, it compares the text of allowed device name and it's slightly different, i.e. between gl-mt2500 and mt2500-emmc but we know it's about the same device.