Spitz AX GL-X3000 - No longer boots

Even PCIE mode works and the speed is x3 ! Check out my guide for installing vanilla openwrt on x3000.

@ywp it seems to be working fine in stock openwrt. You seem to have a recent pattern of this happening with the GLInet firmware only.

Sounds for me like the factory partition is corrupt which hold some important stuff for the GL config (like hostname and encryption key)

Do you have any recommendations for getting some 5G connection status like the stock firmware? Like if it’s 5G NSA, SA, LTE, strength, etc? I use my Spitz as a modem only behind an OpenMPTCPRouter. Don’t need anything else GLI.Net has bundled in, really, but I’m not familiar with stock OpenWrts modem management.

Would be great if there was a way to wipe this partition from stock OpenWRT. I'd rather not go through the RMA process and be without of my modem.

There is, but I would not recommend nor support it.
So maybe you need to talk to @bruce or support about it.

I am looking for the same capabilities, better modem management and monitoring with vanilla OpenWrt, I also use the Spitz as a modem, with an MT6000 as a router running vanilla OpenWrt 23.05.4

4.3.0 and 4.4.10 Fail to Start Properly?
Can I see your partition?
cat /proc/mtd

4.4.10 isn't listed for downloads from what I can tell.

root@OpenWrt:~# cat /proc/mtd
dev:    size   erasesize  name
root@OpenWrt:~#

/prod/mtd is empty

4.3.0 Are you sure can't get up?
Have you changed the mode of the module?
Did you do anything else?

ls /dev/ ---press tab

root@OpenWrt:~# ls /dev/
bus/          full          log           loop2         loop6         mmcblk0boot1  mmcblk0p4     mmcblk0rpmb   ppp           sda           stdout        ttyS10        ttyS14        ttyS4         ttyS8         ttyUSB2       watchdog
cdc-wdm0      gpiochip0     loop-control  loop3         loop7         mmcblk0p1     mmcblk0p5     net/          ptmx          shm/          tty           ttyS11        ttyS15        ttyS5         ttyS9         ttyUSB3       watchdog0
console       hwrng         loop0         loop4         mmcblk0       mmcblk0p2     mmcblk0p6     null          pts/          stderr        ttyS0         ttyS12        ttyS2         ttyS6         ttyUSB0       ubi_ctrl      zero
fd/           kmsg          loop1         loop5         mmcblk0boot0  mmcblk0p3     mmcblk0p7     port          random        stdin         ttyS1         ttyS13        ttyS3         ttyS7         ttyUSB1       urandom

I made zero modifications outside of the basic steps @SpitzAX3000 posted to get OpenWRT working.

The steps I took yesterday:

  1. Router stopped working
  2. I tried to reboot it
  3. I tried to reset it to factory defaults. I guess that didn't work
  4. I got it into UBoot mode, I tried to flash 4.4.9, didn't work. Tried probably 3-4 times.
  5. I flashed OpenWRT, same upload process, it worked immediately.
  6. I tried to flash 4.4.9 again, it didn't work. I tried 4.3.0 three times, it didn't work.
  7. I flashed OpenWRT again, and now I'm trying to use it.
opkg update
opkg install minicom
minicom -D /dev/ttyUSB2
Ctrl + a   --press E
AT+QCFG="data_interface"
AT+QCFG="pcie/mode"

Take a look AT the results of these two AT instructions

To be clear, "didn't work", when referencing 4.3 and 4.4.9, meant it would not boot. I was unable to get a DHCP IP, use a static IP, see any activity, etc.

Welcome to minicom 2.9

OPTIONS:
Port /dev/ttyUSB2

Press CTRL-A Z for help on special keys

AT+QCFG="data_interface"
AT+QCFG="data_interface"
+QCFG: "data_interface",0,0

OK
AT+QCFG="pcie/mode"
AT+QCFG="pcie/mode"
+QCFG: "pcie/mode",0

OK
AT+QCFG="data_interface",1,0

Try 4.4.9 or 4.3.0 again?

I ran that command and then tried 4.3.0 again, twice. No dice. I do have a USB-UART adapter if there's anything to gain from looking at the serial console doing this. Otherwise I was suggested by email support to perform my own "forward return" by buying a new unit on AliExpress, and returning this one in its box, since its under warranty, but I don't want to be without it for what I would assume to be months.

Do you know which AT instructions you have executed?
thank you

Before it crashed? I hadn't run any AT instructions in probably 6-12 months since getting it set up initially. After it crashed? The only commands I ran were the ones listed in How-To: Installing Vanilla OpenWRT on GL X3000

echo -e "AT+QCFG=\"usbnet\",0\r\n" > /dev/ttyUSB2
echo -e "AT+QCFG=\"data_interface\",0,0\r\n" > /dev/ttyUSB2

After that, the only commands I've run were your commands to try and debug it, and then I reran those commands once I re-flashed OpenWRT this morning, to keep my system usable.

Can you get the logs of the serial port?

Mines doing the same thing now after going to newest firmware. Any fix for this?

What kind of problem?
Keep rebooting?