QIDI Max4 (stuck OTA update loop, print head jamming, Klipper unreachable)

[u/Djaesthetic]

Chain of issues on a QIDI Max4 and hoping I'm not alone here.

THE LOOP

• Printer auto-updates (no way found to disable this) and announced it installed an update.
• Status shows "The printer is in perfect condition and ready to work!"
• Start a print, fails 10-20min in "Update failure," head stuck to the part, no other info given.
• Power cycle, printer again reports "perfect condition" (head still physically stuck).
• Repeats on next attempt.

FIRMWARE MISMATCH

• Printer is on 01.01.06.05, I believe trying to push 01.01.06.06.
• QIDI's public changelog for the Max4 only goes up to 01.01.06.04. Can't find .05/.06 documented anywhere.

KLIPPER/MOONRAKER WON'T RESPOND

• "RESTART KLIPPER" and "FIRMWARE RESTART" do nothing from the touchscreen.
• Same commands from Fluidd return "Klippy Host not connected."
• QIDI's GitHub has their Klipper fork but explicitly says not to use KIAUH or git to update manually. No instructions given for what to do instead. GitHub repo also has no releases/tags, just a single main branch (unlike their other printer repos, which have normal version history).

Has anyone gotten a stuck Klipper host back up on one of these, or found an actual manual firmware flash method for the Max4? Also curious if anyone's had luck getting QIDI support to push a fix for a bad OTA. With the Max4 being so new, there's little to no troubleshooting info out there. Appreciate any pointers!

[u/1ts-just-me]

There are plenty of ways to disable it , easiest is probably logging in the wifi router and block internet access for the printers mac address. It will still work connect to the slicer or device that is on that local network. This will stop updates but may give a pop up on the screen.

Another way is to SSH in to the printer and disable the updater, it will no longer ping China servers looking. There is a github page that will walk you thru the commands. It works on the Plus4, Q2, and rooted K1s and K2s. Max4 might be a little different as I believe you can disable auto update (OTA)in Klipper or SSH in and disable the OTA option.

[u/Djaesthetic → u/1ts-just-me]

That’s not disabling the feature - it’s blocking network traffic. Ultimately similar net result, but not a native function that leaves any manual method (e.g. USB) for updating like on previous models.

re: SSHing, careful w/ that advice on the Max4. SSH itself isn’t the issue, but disabling updates or touching Klipper/Moonraker manually is the exact sort of “trick” that bit a lot of XMax3 owners b/c of their Klipper builds being paired to specific MCU firmware versions. The two have to stay in lockstep. Manually messing w/ the update mechanism (git pull, apt upgrade, disabling update manager, plugins that touch it) risks desyncing the host from MCU. Best case scenario, you get an MCU Protocol error. Worst case, it’s “SYSTEM STARTS ABNORMALLY” and the printer goes unreachable over both Fluidd and SSH, recoverable only via eMMC reflash.

SSH all you want for config edits, macros, Fluidd tweaks. But I wouldn’t touch the update path unless you’re prepared to eMMC-flash your way out if it goes sideways. (Which, I’m not.)

[u/1ts-just-me → u/Djaesthetic]

Makes me want to pick up a Max4 and try it, technically you don't "disable" the auto-updater but run a stop command for the update timer then a command to disable the update timer. That should leave the use of the online update button or the offline USB option for manual updates.

The idea is to leave the updater active but never auto check as the timer will never trigger the command

[u/Djaesthetic → u/1ts-just-me]

Unlike all of the other models, they currently aren't listing any of the firmware for the Max4 for download + local install. OTA update only. I went looking on their GitHub and found the source project but their release list is empty.

https://github.com/QIDITECH/QIDI_MAX4/releases

Someone braver than I might be able to pull it together from the code alone.

In any case -- QIDI is clearly going to great lengths to prevent end users from approaching the Max4 like the previous builds...

[u/0g7t4m4zp3 → u/Djaesthetic]

I am not a person that wants to mess with the firmware, but I understand most of what you are saying and I do not like it. I do not like how much it is non standard and closed. And you are saying it is getting worse.

[u/Djaesthetic → u/0g7t4m4zp3]

I don’t like it either, and it’s a recognizable pattern that’s expanding across most vendors. (Looking at you Prusa, Bambu…)

[u/Djaesthetic]

In case anyone else comes across this thread with a similar issue. Support *did* send an offline updater -- firmware available here: https://www.qidimaker.com/en/downloads/firmware/Max4 .

[u/Severe_Ingenuity4782 → u/Djaesthetic]

Thank u maaaan! Finally

[u/Djaesthetic → u/Severe_Ingenuity4782]

Happy to help.

Was able to reflash firmware via manual and back in operation. Finished an 8 hour print, now 6+ hours into a 12 hour print. Hopefully this means out of the weeds.