Okay, then I think its better to wait until the process is more mature.
After flasing the openwrt sysupgrade in GL-Inet GUI under 192.168.8.1, Luci is not working (neither 192.168.8.1 nor 192.168.1.1). How can I fix that?
Btw, I can do ssh root@192.168.1.1 into openwrt.
I see there are separate files for the bootloader/uboot and the kernel on the download page, but based on what you said previously, it seems that flashing a factory image will change the OEM uboot. Is that correct?
So from what I understand, we can flash a sysupgrade from either the GL.iNet main WebUI firmware update page, or from recovery, and the OEM uboot will be left alone.
I too am just trying to stop people bricking their routers, so if there is an easy way to brick them, I want to warn people.
No flashing the factory image via uboot will cause it to fail to boot aka.
To use the Factory image you must flash the OpenWRT Uboot (Risky and requires the TFTP server to be setup and UART)
Which is why it would be safer to simply flash the sysupgrade image via the supplied uboot from GL-iNet.
When i tried to flash via the GL-iNet GUI the sysupgrade it failed to accept the firmware hence had to go into recovery mode to then flash the sysupgrade image for the first time, then after that you can use LUCI.
That would be because this is a snapshot build, which usually do not have Luci installed.
If you ssh in and do 'opkg update' then 'opkg install luci', then reboot, you should be ok. Or go to the firmware selector page and do a custom build with luci added in to the package list. I would probably also recommend adding luci-app-attendedsysupgrade as that will prove useful for upgrading.
phqzgunsfjror
Is there somebody who already uses the OpenWrt uboot and can kindly share a manual how to do it with the TFTP?
I have not done this, so take everything I say with a grain of salt, and be warned there are dragons there.
I think you would need a UART serial cable connected to GND, TX, RX (not V+/VCC) and a terminal app configured correctly. I think like with many routers you would need to hit the correct key (or key combo, perhaps CTRL+C) to interrupt boot and get a shell prompt, then run the TFTP server.
There are videos of similar (but not the same!) scenario;
This one is likely to be close, but not exactly the same.
If you look through the code in the git commit, you see the OpenWRT uboot menu options;
++bootmenu_title= *** U-Boot Boot Menu for GL-iNet GL-MT6000 ***
++bootmenu_0=Startup system (Default).=run boot_system
++bootmenu_1=Load Firmware via TFTP then write to eMMC.=run boot_tftp_firmware ; run bootmenu_confirm_return
++bootmenu_2=Load BL31+U-Boot FIP via TFTP then write to eMMC.=run boot_tftp_write_fip ; run bootmenu_confirm_return
++bootmenu_3=mLoad BL2 preloader via TFTP then write to eMMC.=run boot_tftp_write_bl2 ; run bootmenu_confirm_return
++bootmenu_4=Reboot.=reset
++bootmenu_5=Reset all settings to factory defaults.=run reset_factory ; reset
Just to be clear, the videos above are the hard way to do any of this. The text based uboot recovery is not the method I would recommend, I was just answering someone's question.
As stated by @solidus1983, the easier way is to only use sysupgrade
1) Remove Power from the router
2) Press and Hold the reset button
3) Apply power whilst still holding the reset button
4) After 5 seconds head to http://192.168.1.1
5) Flash OpenWRT https://downloads.openwrt.org/snapshots/targets/mediatek/filogic/openwrt-mediatek-filogic-glinet_gl-mt6000-squashfs-sysupgrade.bin
Upgrading after simply use the same file type via LUCI on each upgrade.
I was loking at the specifications of the installed GL software and it looks like hardware offloading is supported. Does the snapshot openwrt support that .
Does anyone had opportunity to compare the performace and stability of installed factory GL firmware with openwrt?. Would be useful to know any thoughts before bricking/debricking
My Flint 2 will apparently be delivered today by FedEx, had to pay them import tax and fees. For NL that was €28,09 on top of the €102,90, should hopefully still be worth the money....
GL.inet can do better job by maintaining their page properly updated for new releases, but, can confirm that this information was there when I ordered my as early bird:
Products without the "EU local delivery" tag are shipped from outside the EU and are subject to shipping costs & TAX & longer delivery time.
Recieved my GL-MT6000 (Flint 2) yesterday. Wasn't charged import taxes in the US, Fedex just dropped it off and left.
Unboxed it, but didn't power it up yet. I'm very impressed with the small size and overall build quality. Between the compact size and grey/black body it just look greats. A little smaller than my current WRT32X, which is wonderful considering it should have much more performance.
Looking forward to getting into this and the MediaTek / Filogic target as a whole.
Received mine as well today. Just booted up and checked the interface, which is basically the same as the interface of my GL-MT1300 Beryl travel router.
I'll fiddle around with it a bit and will try to flash Vanilla Openwrt to replace my current main router (Netgear R7800).
Bit reluctant still as there are only snapshots so far, I might wait with the replacement until the snapshot is a bit more mature or GL-MT6000 is added to 23.05.x....
Yea thinking the same, going to keep my WRT32X as my main for a little while since it's rock solid. Once the main snapshot moves Filogic to kernel 6.1, I'm going to move it over for main router testing. Really excited about the upgrade though. OpenWrt 24.0x is going to be great
Btw I paid $110 total. Noticed they just moved their price up to $160, so great timing with the preorders everyone!
I for one am now glad for the http firmware recovery service in the GL.iNet Uboot after I got cocky with dependencies and flashed a bad custom SNAPSHOT build last night. It was otherwise working great but I've swapped my Belkin RT3200 back in as my primary for now. The MT6000 is noticably faster to use but the RT3200 hardly sweats with my 500/20 connection and qosify, wireguard, adblock, etc. all running. Wireless range and connection quality are the biggest practical improvement I've noticed.
Any idea what it'll take for GL-MT6000 support to be added to STABLE? I ran SNAPSHOT with the RT3200 for almost 2 years but hopefully we won't have to wait that long for this one.