openstick.de

Common Boot Problems & Solutions

A collection of the most common issues after flashing and how to fix them.

Stuck at Boot Logo
Cause: Wrong kernel/boot image for your device model.
Fix: Enter EDL mode and re-flash the boot partition with the correct image for your specific board.

Boot Loop (restarts every few seconds)
Cause: Corrupted root filesystem or missing init.
Fix: Re-flash the rootfs partition: No USB Device Detected on Host PC
Possible causes:

• Bad USB cable — try a different, shorter cable
• Wrong lk2nd version — make sure you flashed the correct lk2nd for your device
• Device is in EDL mode — check with

  Code: Select all

  lsusb

  for 05c6:9008
• USB port issue — try a different USB port (avoid USB 3.0 hubs)

Black Screen but SSH Works
Cause: Your device does not have a built-in display, or the display driver is not loaded.
This is normal for most devices. Only the MF800B-E LCD model has a built-in display. The device is working fine — just connect via SSH.

Kernel Panic on Boot
Cause: Device tree mismatch. The kernel cannot find the right DTB for your board.
Fix: Make sure the boot image includes the correct device tree for your specific device. Check which DTB files are supported: LTE Modem Not Found After Boot
Cause: Modem firmware not loaded or firmware partition corrupted.
Fix:

• Check if modem firmware is present:

  Code: Select all

  ls /lib/firmware/

• Restart ModemManager:

  Code: Select all

  sudo systemctl restart ModemManager

• Check dmesg for modem errors:

  Code: Select all

  dmesg | grep -i modem

WiFi Not Working
Cause: WiFi firmware not loaded.
Fix: The WCN3620 firmware files need to be present in the firmware directory.

If your problem is not listed here, post in this forum with your device model, what you did, and any error messages.