Rooted Max and CFS

Flagship K Series Creality Flagship K1 Max
1

Like so many of us, i want to add the CFS to my K1M but am still waiting for the upgrade kit ro become available. Anyway, i i want to root the machine, but i keep getting conflicting info about its compatibility with the CFS. So…can anybody tell me 100% one way or another if the CFS will work with a rooted machine ?

2 Likes
2

It does. I did it yesterday.

1 Like
3

Hi, could you please explain how you did it?
Or an link we’re WE can find a description.
Thank’s Chris

1 Like
4
1 Like
5

Here is the translated version of the post, ready to be copied and shared on English-speaking forums like Reddit (r/klippers, r/crealityk1) or GitHub discussions:

Title: Warning: Don’t waste your time trying to disable CFS purges on the Creality Hi (Locked-down system)

Hi everyone. I’m writing this post to save you the hours of life and frustration I just lost fighting this printer’s firmware.

I have a Creality Hi with the CFS multi-color system. My only goal was something that should be simple in Klipper: disabling or modifying the purges during CFS filament changes so I could manage the waste directly from the slicer (using a purge tower or flushing into infill) and avoid wasting so much material.

It turns out this machine runs a highly restrictive version based on Tina Linux (Hi_Klipper) and is completely locked down. Here is a breakdown of everything I tried and how the machine blocked me at every step, so you don’t have to repeat my odyssey:

  • Attempt 1: Editing G-code and the slicer. The first thing I tried was intercepting and cleaning up the purges by directly modifying the .gcode files and tweaking the toolchange scripts in the slicer. Total failure: the Creality Hi firmware ignores this and injects its own forced purge routine for the CFS directly from the board, overriding whatever you send.

  • Attempt 2: Modifying internal logic (box.py). I tried messing directly with the Python script (box.py) that handles CFS communication. I logged in via WinSCP and edited it to try to nullify the purge command from the source code (even battling Windows formatting and line break errors), but it was useless.

  • Attempt 3: Guilouz’s Helper Script. Looking for real root access, I tried using the well-known Helper Script. It fails as soon as it starts. It throws the error /usr/data/helper-script/helper.sh: line 28: git: not found. Creality removed git and wget from the OS so we can’t download anything from GitHub.

  • Attempt 4: Installing Entware to recover Git. By editing the helper.sh file, I commented out the update line to bypass the Git check and force the blue menu to open. I managed to install Entware (which in theory gives us the opkg command to install packages). The script says “installed successfully”, but…

  • Attempt 5: Automatic route wiping. Upon restarting the SSH session, the opkg command returns not found. The machine wipes or blocks the /opt folder (where Entware goes) on every reboot. There is no way to leave packages persistently installed.

  • Attempt 6: Brute-forcing Fluidd and tricking Nginx. I tried to push the web interface manually. We created folders in /usr/data/fluidd (the only partition that doesn’t get wiped), made symbolic links (ln -s) to bypass the protected /usr/share/ partition, and modified nginx.conf.

  • The final result (and the biggest waste of time): I managed to hack the system to get full access to Fluidd… but I already had access to Fluidd from the start! The real problem is that, even with full access to the interface and the .cfg files, the CFS purge macros are completely obfuscated or locked inside Creality’s environment. They are nowhere to be found in any cfs_macros.cfg or printer.cfg where you could just add a # and comment them out.

Conclusion: Guys, as of today, if you have a Creality Hi with a CFS, the system is locked from the root. Don’t waste your time fighting the Git error, or forcing Entware, or messing with Python scripts. Until Creality releases a truly open firmware for the CFS module, we are stuck with the massive factory purges.

6

I disagree, there has been a nice discussion on K1 reddit group and I reduced filament change to 1min and poop to a minor qty.

7

Do you by chance have the link to the post you’re referencing?

8

I think this one.

https://www.reddit.com/r/crealityk1/comments/1q2uo9r/free_your_build_plate_new_purge_chute_nozzle/

1 Like