Brume2 devices bricked

[bbnsn]

I performed a proactive reboot on my 2 Brume2 devices yesterday via the web UI during network maintenance. After restart they just stayed inoperable with a blue LED. No amount of power disconnections or resets made a difference. I checked online and found out about the Critical Notification for Brume2, requiring a uboot upgrade. I followed the instructions, and for both devices despite receiving "Upgrade Successful" messages (with confirmed MD5 after upload) when the Brume2's restarted after upgrade they were completely dead. No power LED, no response to anything I seem to do. Just. Dead.

Contacted support but it seems Murphys Law applies yet again and there is nobody online at GL.iNet due to Labor Day holiday, so no support for 5 days and I can't even order a replacement if I wanted to. sigh

Has anyone found a way to un-brick a Brume2 after uboot-upgrade-success-but-not-a-success? (clearly a desperation post )

[alzhao]

Did you use Firefox for uboot update? If yes then it is dead.

Only way is to exchange. You can order replacement via Amazon first and return this one.

[bbnsn]

hi there nope no Firefox around these parts ... will progress with RMA as advised

[alzhao]

What browser did you use then?

[mkdr]

At this point, Glinet should really look into why all these Brume 2 brick with a high chance for the Uboot upgrade. That is totally not normal. Seems the upgrade procedure is somehow flawed.

[alzhao]

We have identified the reason. Firefox update uboot will brick it, unless you have a different case.

[mkdr]

Some people however claim, they used Chromium browser. Also here is an example of someone who cant even upgrade anymore:

Brume2 possibly bricked

From what I have readed here and there, I suspect this is what it looks like if the brick happen if the emmc is already teared before the upgrade, meaning no other upgrade is possible, it will be in some sort of read only mode from what I have seen in posts, this then also happens on normal firmware right? it is a different brick than the ones who did managed to upgrade and it failed which results in a cold brick, this is the brick what this firmware and u-boot is supposed to fix, very sad unfo…

Then I also found posts of people on Amazon Germany in reviews, who said this:

Translation:

"I have two devices. One is in use, and the other occasionally comes with me to hotels. Today, after an update, one of them no longer boots. I take the second one out of my bag—and it won’t boot either. Both are suddenly dead with just a blue LED. I then tried to restore both devices using the manufacturer’s recovery instructions (YouTube). On both devices, the attempt fails with a “failed” message. Great. Two Brume2 devices suddenly broken out of nowhere. Very disappointing!!!!"

This seems to become more and more dramatic. Eventually mostly all Brume 2 will fail and most customers wont receive an email from Glinet because theyre not registered.

Maybe Glinet should put a warning on their front web page / store, also inform dealers like Amazon about this mess.

[alzhao]

Thanks for the links.

The Chromium update failed message, may not relate to the brick as firefox. The firefox update uboot will be successful in the web page but then write wrong data to the device. While the video shows cannot update.

Uboot Ethernet driver does has compatibility issues and sometimes need to try a different computer.