Good morning,
I tried several times to reinstall the firmware of my BRUME 2 via u-boot, however after the successful update the router does not restart, and I remain stuck on this page
Thank you for your help
remove 192.168.1.2 from the lan configuration and access the 192.168.8.1 page normally
1 Like
Could you please post the output of ipconfig /all using cmd.exe on your PC?
Carte Ethernet Ethernet :
Suffixe DNS propre Ă la connexion. . . :
Description. . . . . . . . . . . . . . : Realtek PCIe FE Family Controller
Adresse physique . . . . . . . . . . . : 18-67-B0-40-99-ED
DHCP activé. . . . . . . . . . . . . . : Oui
Configuration automatique activée. . . : Oui
Adresse IPv6 de liaison locale. . . . .: fe80::e00a:1714:bbb9:ec37%4(préféré)
Adresse d’autoconfiguration IPv4 . . . : 169.254.234.222(préféré)
Masque de sous-réseau. . . . . . . . . : 255.255.0.0
Passerelle par défaut. . . . . . . . . :
IAID DHCPv6 . . . . . . . . . . . : 102262704
DUID de client DHCPv6. . . . . . . . : 00-01-00-01-25-24-FC-8A-18-67-B0-40-99-ED
NetBIOS sur Tcpip. . . . . . . . . . . : Activé
It seems that your PC did not get a IP from the right network.
Try to unplug the PC from the router and plug it again into the LAN socket. Maybe power cycle the router as well.
thank you, but after reconnecting or restarting it still does not work and the LED on my router remains frozen in blue
She looks like she’s bricked if power cycling it & ipconfig /renew then ipconfig /flushdns didn’t push a 192.168.8.0/24 to your Windows box.
Otherwise it’s time to file a RMA request, methinks.
Hmm sometimes you also have to release dhcp.
ipconfig /release and then followed by ipconfig /renew this essentially force a dhcp request.
Make sure your network configuration is no more set to static mode.
If all does not work, and uboot procedure also not i think you should RMA it. 
That’s not needed. DHCP lease will be cleared automatically when the link is down.
I would try to uboot process once more. After it’s done, disconnect the device from power and LAN.
1 Like
It could have been still caching stale DNS; that’s a Chromium browser in OP’s screenshot.
@matou : try U-boot again… but using Incognito Mode.
I answered you over your ticket. Please check your email box.
hello I have a same issue on my MT2500.
is there anything to try like tftp firmware writing?
so it just requesting RMA is only way I can do, please?
I found that when I trying to firmware load using Uboot,
MT2500 request “openwrt-gl-mt2500.bin” using TFTP port from my PC. it it normal behavior, right?
what file is the “openwrt-gl-mt2500.bin” in openwrt-mt2500-4.5.0-0123-1706007069.bin?
A similar problem! Are there any solutions?
can you write to support at glinet.biz?
1 Like
Ran into the same problem after starting an update via the web GUI.
I can access and flash the firmware again via uboot, but attempting to connect to http://192.168.8.1 afterwards fails.
Both, with the network adapter assigned the address 192.168.8.2 manually and set to DHCP. The client will not get an IP address from the Brume 2. It will only self-assign a 169.254.xxx.xxx address.
What can be done?
hmm are you using windows 11?
please set it in windows to dhcp for now, If the usual ipconfig /renew doesn't work, you might suffer from a windows 11 network bug.
can you navigate to: system settings -> network and there reset settings?
If you restart the pc you can check if it works again.
For some reason microsoft broke it in their latest service update, meaning nothing respond to your network port, also the network identifying does not start.
Often if the leds show normal operation then it might not be bricked 
Try this method instead of /renew
ipconfig /release
ipconfig /renew
I tried for me that didn't fix.
thats why i'd say it is a bug in windows.
It randomly happens when changing settings or changing cables which has the potention to kill something in windows to not work properly as expected, only the reset settings solved it for me.
Hello,
thank you for the reply. I'm on macOS, though. And I tried to connect to the Brume gateway after the uboot reset with two independent macOS devices.
I had to recover a AR300 (Shadow) last year via uboot and that worked flawlessly.
Any further ideas?