Seems ive bricked my flint 2 (and both beryls) for good. Have never had uboot fail on 3 devices but i have 3 pretty useless routers and no idea what to do. Anyone wanna walk me thru a flash using a pico and some jumper cables or do i need a cheap usb to ttl cable (they should be identical but im no expert clearly or id have stopped after i bricked two routers using the reset button with 24.10.0 after the wifi stopped workingš¬
By default, Wi-Fi does not work. You need to connect with a cable and make settings. If the LED lights up (blinks), then the bootloader is alive.
Im not so new to openwrt. Ik wifi is off by default. But i had it working and then it just stoped. Normally id just hold the reset button or worst case unbrick it with uboot. I never had this happen tho
It seems like there was a press release on "beryl" that there is an error in the bootloader and it is necessary to update it urgently, otherwise the NAND will die. It seems like this is a warranty case and should be replaced if this happened, but this did not happen on Flint 2.
Try to restore by holding RESET, connecting the power supply, in general, according to the instructions.
The led lights up but luci isnāt accessible at 192.168.1.1 or glās stock 192.168.8.1 either. And ssh worked initially the first time i held the reset button on my flint and used my old ssh password, but then i ran into the wifi issue again after a few hours, reset and then ended up where i an now. With 3 useless routers and the xe300 puli which is too slow to do anything withā¦. And i dont think that will run any recent vanilla openwrt builds anyway so was afraid of installing itā¦ then id have 4 open source bricks, instead of 3 and one proprietary pos i dont trust enough to wanna use lol
And the button holding while inserting the power cable trick doesnt seem to help. Ive been trying for an entire day until deciding id finally make an account here and ask for helpā¦but now i think its time to consider reaching out to glinet or popping one of these open to flash externally. Been looking to do that to my thinkpad so i have a lot of stuff i can use to flash plus i got a sweet new soldering station because i have a shopping problem.
Because it doesn't work the way you imagine. Press and hold until it stops blinking and lights up with a steady light ~10s. Then assign the computer's network card a static IP of 192.168.1.2 and a mask of 255.255.255.0, then go to the router's bootloader at 192.168.1.1, and then it will be hard not to figure it out.
Flash stock firmware or file blah.blah-sysupgrade.itb
I was wondering: Does the MT6000 with OpenWRT 24.10 still have WiFi problems when using the same SSID for the 2.4 and 5GHz band?
In the past, the WiFi connection would produce a lot of packet loss and reconnecting would become impossible or the download / upload speed would drastically get reduced.
Read the detailed changelog.
1 Like
Thanks a lot. The patch
for the identical problem
was therefore added to the latest OpenWRT version 24.10.1. I'm looking forward to try it out.
2 Likes
I use same SSID/pw for 2.4 and 5.1 and no issue. I also tweak AQL limits for slightly lower wifi latency. 24.10.1 is fantastic so far. (Then again so was .0 had a 67-day uptime with tons of added services before flashing .1 yesterday.)
1 Like
Ill try on the flint again with my computers ip changed. I used to change it when debricking because thats what is shown in the video from glinet but I stopped bothering with that step when i realized my browser would take me to luci regardless if I just went to 192.168.1.1 in my browser either way. Im hoping that extra step does the trick for the flint but i think the beryl is done for. It wont even blink rapidly when i plug it in with the button held for any period of timeā¦ just a really slow dim steady flashing that i imagine is router talk for āim doneā¦ put me out of my miseryā
Edit: it doesnt flash rapidly it flashes blue slowly for about 15 seconds then turns white and 192.168.1.1 is still not accessibleā¦
Topic about GL.iNet GL-MT6000
I don't know what's going on with other routers, as I've never seen them.
Either way I just wanted to make people aware that its not a problem exclusive to the flint and whatever i did made all my gliās seemingly beyond uboots help. Ive concluded all I did differently was install a pretty limited number of new packages on them and update some packages that werent broken (linux wasnt given me enough curveballs this week and it was time to spice things upš¤·). I tried getting wireguard and my dns settings dialed in perfect on one of them and the other i tried turning into an onion router. Had high hopes of hardening the OSā¦ bricks=hardā> success! Now that ive learned one tough lesson about messing with things i dont 100% completely understand the ramifications of before diving in head first, does anyone happen to have advice on flashing the flint over a serial connection or am I on my own for this one? Besides reading a lot about externally flashing coreboot and frequently needing to figure out how to fix hardware i broke while āfinetuning stuffā im admittedly in over my headā¦. Might be time to try opnsense on a corebooted x86 and leave the openwrt routers alone as dumb APās since they seem to be better if I just dont touch emā¦
What's more likely?
That 3-4 routers died in one second, or that you did something wrong?
What's more likely?
That you lost your keys, or that aliens stole them from you?
1 Like
Hey i didnt exactly deny fault here lol. āNow that ive learned one lessonāā¦ānot enough curveballsā¦spice things upā etcā¦ but whats done is done. Learning always best cemented via experience vs warnings imo. Any experiencial knowledge flashing a brick back to life to share instead of harping stupid decicion to ignore the warnings about unnecessary willy nilly opkg use?
Hi,
Here is saying:
1. Network ā Firewall ā Software Flow Offloading: enable
2. Network ā Firewall ā Hardware Flow Offloading: enable
3. Save and Apply
It seems I don't have this option to enable both:
They switched it to a dropdown in 24.10, which makes more sense since itās really one or the other technique you canāt do both at the same time. Iāll update the doc page when I have time later this weekend.
3 Likes
Hi,
Here is saying:
- Setup the Admin Web Interface to listen on
192.168.1.1at port8080. (Changing the web interface port is optional)
But doing this, I cannot access LuCi nor AdGuard Home.
I suspect that LuCi is also listening at the same port, so it's better to keep AdGuard Home on the standard port 3000
I know it's an optional. But this optional should be followed by a comment that LuCi is listening on the same port 
Could it be that there still is a significant WiFi range and performance difference between:
the stock firmware (MTK drivers) and the OpenWRT mt76 drivers in favor of the MTK drivers, even when using the same channel and bandwidth and maximum TX power?