GL.iNet GL-X3000/ Spitz AX support

The build output is also

openwrt-mediatek-filogic-glinet_gl-x3000-bl31-uboot.fip

Is there an option to also flash the bootloader using this file?
Well, I cannot even find an official GL iNet doc that describes an update of the uboot for x3000.

Now that X3000 and XE3000 are supported in 24.10.0 : can one flash openwrt-24.10.0-mediatek-filogic-glinet_gl-xe3000-squashfs-sysupgrade.bin using CLI sysupgrade or LUCI Flash of even GL.iNet System upgrade? I ask because device is not yet updated in hardware support and snapshot only describes openwrt-24.10.0-mediatek-filogic-glinet_gl-xe3000-initramfs-kernel.bin U-boot method. On the other hand, I have several mediatek-filogic MT3000 which I always immediately flashed OpenWRT using LUCI Flash. Conversely is flashing openwrt-24.10.0-mediatek-filogic-glinet_gl-xe3000-initramfs-kernel.bin via U-boot method only way to install first time?

Another thing I wonder : currently on vendor firmware I update quectel module software using firehose. Is this possible under official 24.10.0 OpenWRT?

I's possible via uboot or ssh -> git-openwrt

    The bootloader can be replaced using the built-in web interface of the
    factory bootloader. Hold the reset button for five seconds while powering
    on the device and it will boot into a recovery http server.
    
    http://192.168.1.1/uboot.html and http://192.168.1.1/bl2.html can then
    be used to upload openwrt-mediatek-filogic-glinet_gl-x3000-bl31-uboot.fip
    and openwrt-mediatek-filogic-glinet_gl-x3000-preloader.bin respectively.
    
    Alternatively, from a root shell on the running system, unlock the boot
    partition with
    
      echo 0 >/sys/block/mmcblk0boot0/force_ro
    
    then write openwrt-mediatek-filogic-glinet_gl-x3000-bl31-uboot.fip to
    /dev/mmcblk0p4 and openwrt-mediatek-filogic-glinet_gl-x3000-preloader.bin
    to /dev/mmcblk0boot0.
2 Likes

@bass443

That commit looks very promising in that using the replaced bootloader would allow 5G module to work in PCIe mode, right?

Would you recommend this and have you compared with USB mode.

Bu the way when working in PCIe mode what tool to use for AT commands? Still some terminal emulator ?

While on 3000 topic? see my previous question? Does it have to be installed by stock U-Boot and if so which image? Or can we use sysupgrade imaje from stock with LUCI or CLI.

Thanks

You will not be able to install the sysupgrade image from Luci, as the target name changes between the GL.iNet firmware (glinet,x3000-emmc) and the OpenWrt one (glinet,gl-x3000).

So you have to:

  • Either install the OpenWrt image using the U-boot web interface, as described in the commit introducing the support of the device.
  • Or upgrade to the OpenWrt image using the CLI with the -F option of sysupgrade:
root@GL-X3000:/tmp# sysupgrade -F -v -n /tmp/openwrt-mediatek-filogic-glinet_gl-x3000-squashfs-sysupgrade.bin
Fri Oct 25 02:44:49 UTC 2024 upgrade: Device glinet,x3000-emmc not supported by this image
Fri Oct 25 02:44:49 UTC 2024 upgrade: Supported devices: glinet,gl-x3000
Image check failed but --force given - will update anyway!

In both cases, you have to use the squashfs-sysupgrade.bin file.

1 Like

As per my understanding you must switch to USB mode to leverage the 5G capabilities. Otherwise you have 4G only.

picocom /dev/ttyUSB2

You use picocom for executing AT commands.

Regarding installation, this is all very confusing. Right now, I am trying to collect all info and put it on the TOH wiki page for x3000.
The Stock UI also provides a link to Luci! Sweet
There you can also flash the sysupgrade image, but you can never flash the [squashfs-factory.bin]

If you think about buying this device: Check your 5G coverage (do some ping tests to check if it is "real 5G") and you will be happy. I would recommend that device.

1 Like

I was not able to get 5G in PCIe mode working, therefore i changed to USB mode. -> It's working, but with 330 MBit limitation.

Unfortunately PCIe kernel is not implemented.

1 Like

@bass443 @Frood42 @dohseven thanks a lot for expert advise and input!

you can set more than 1 supported device ...

add this to the makefile and | append-metadata

SUPPORTED_DEVICES:=glinet,gl-x3000 glinet,x3000-emmc

its an array, so technically you could set up to the limit of supported devices, just use a space between each entry, no comma

1 Like

damn :slight_smile: I was stupid enough to paste this command but the file of course was /tmp/openwrt-24.10.0-mediatek-filogic-glinet_gl-xe3000-squashfs-sysupgrade.bin

This left GL-XE3000 somewhat in a dead state and power off/on does not fix anything

But now if I go into uboot (pressing reset and power on and seeing internet flash few times and then wifi led on) and surf to 192.168.1.1 I do not see regular uboot interface but rather a LUCI login. However ... for username root, what password to use ? My previous one does not work. Or maybe anorther username/password combo.

If you see a LUCI interface, you are not in u-boot recovery mode.

I think that by defautl the root username has no password, but I'm not 100% sure

1 Like

@dohseven

thanks for kind reply ...

I tried empty and goodlife and sticker wifi password too.

Odd thing is I should see the regular well known uboot FIRMWARE UPGRADE page but I get LUCI on 192.168.1.1 ...

I also tried http://192.168.8.1/index.html but I always arrive at http://192.168.8.1/cgi-bin/luci/

Debrick page https://docs.gl-inet.com/router/en/3/tutorials/debrick/ mentions LAN should flash 5 times but here Internet flashes 5 times.

I will perhaps have to try harder.

UPDATE

somehow (I think perhaps by factory reset pressing reset 10 seconds) I got into regular uboot interface and all seems well.

I knew I could not brick GL.iNet :slight_smile:

1 Like

Thanks all here for kind help!

5G up and running IPv4/IPv6 download 330Mbps upload 100Mbps ...

I am impressed and happy :slight_smile:

1 Like