Loss of Motion and Connectivity After Firmware Update

I am currently experiencing an issue with my Snapmaker 2.0 A250 and would greatly appreciate any guidance or insight from the community.

I have owned this machine for nearly six years, and it has been consistently reliable until recently. The unit had not been used for approximately two months due to a relocation to a new studio space. After reassembling the machine, I updated it to the latest firmware and installed the most recent version of Luban.

Following these updates, the machine no longer moves on any axis.

Troubleshooting steps and observations made:

  • Rebooted the device

  • Performed a factory reset

  • Installed an older firmware version

    • With the older firmware (tested 1.13 thru 1.14), the print head and linear modules respond, but the X and Y axes appear to be inverted at times
  • Reinstalled the latest firmware

    • After updating again, the machine locks in place on all axes immediately upon startup

Additional results:

  • The machine correctly detects different tool heads and appears to initialize normally

  • The calibration option intermittently disappears from the touchscreen interface

  • Snapmaker Luban no longer maintains a stable connection:

    • Wi-Fi briefly connects, then disconnects immediately

    • The machine’s display continues to show an active connection

  • Reinstalled Luban and rebooted my PC

  • Tested across multiple systems (two Windows 11 machines and one Windows 10 machine) with identical results. Different routers were also tested.

  • Attempted connection via USB (mini-B-USB, per my research, I don’t think USB C works)

    • No connection is detected on any device

At this stage, I am uncertain whether this issue is related to firmware, configuration, communication failure, or a hardware fault that may have coincidentally appeared after the update.

I would appreciate any recommendations on further diagnostic steps, or insight from anyone who may have encountered a similar issue.

This machine has been very reliable for me, and I had planned to begin a large prototyping project, so I am hoping to resolve this as soon as possible.

I may be slow to respond, but I will follow up within 48 hours. Thank you for your time and assistance.

How is it about your free space on the touchscreen?
Try to delete files, this could be necessary for each toolhead, and try to update without any toolhead.
Is there a screen which prompts " update successfully installed"?

Thanks for the fast reply!

I checked the available storage on the touchscreen, and there is currently nothing stored on the device aside from a default folder labeled “workspace,” which I have already removed. I typically rely on external storage or Snapmaker Luban for file management and monitoring, so the internal storage has seen minimal use.

At this time, the system reports approximately 4117 MB used out of 4795 MB total, despite no visible files being stored.

For each firmware installation and update I have performed, the machine has consistently displayed a confirmation message indicating that the update was successfully completed.

One additional observation I had not included earlier, the FDM toolhead is partially responsive. It is able to heat the nozzle, but it does not engage the filament drive at all. During factory reset procedures that require toolhead setup, the nozzle heats continuously without extrusion, which has led to a noticeable burning smell from the filament.

If your suggestion is referring specifically to the Snapmaker 2.0 OS rather than the firmware updates, I would appreciate any clarification on how to properly revert or manually reinstall the OS, as I am not currently familiar with that process.

I will also set aside some time to attempt a firmware update without any toolheads attached and will provide an update once I have completed that test.

This could be the issue.

Even if you print with Luban over WiFi, the gcode would be transferred to the touchscreen and stored there.

Try to connect every single toolhead in unpowered state, power on and delete the files.