My KC1 won’t go past the Language Selection Screen. After working fine, it stopped and went to the Language Selection Screen, and it won’t go past that screen even after turning it off and back on.
Ran into this exact thing a while back and wasted a chunk of time assuming it was a hardware problem before figuring out what was actually going on — figured I’d write it up in case it saves someone else here the same trouble.
My printer (K1 Max, S12 board / X2000E chip) would boot through the Creality logo, land on the language screen, and just stop — taps didn’t register, nothing. Error 0508 also popped up right before it locked. I checked the ribbon cable, reseated it, did a full power cycle — none of it changed anything, which is exactly the kind of result that makes you assume the screen itself is dead.
Turned out the screen was fine. The actual cause was /usr/data on the mainboard being completely full. When that partition has no room left, the touchscreen app can’t read or write the settings it needs and just hangs — which, from the outside, looks identical to a dead touchscreen. Nothing wrong with the display or the connector at all.
Here’s what got mine working again:
1. Open a serial console — you don’t need the touchscreen for this part. Wire a 3.3V USB-to-TTL adapter (I used an SH-U09C5) to the J1 header on the mainboard — GND / RX / TX from the center pin outward. Connect at 115200 baud and power the printer on while watching the terminal. If you see boot text scroll by and it lands on a login/shell prompt, the board itself is fine — you’re dealing with a stuck UI process, not a bricked board.
2. Check how full the partition actually is:
df -h /usr/data
Mine showed 100% used, zero bytes free.
3. Clean out what’s taking the space. Run du -sh /usr/data/* | sort -rh first to see what’s actually large on your board before deleting anything blind. For me it was old gcode files and timelapse images:
rm -rf /usr/data/printer_data/gcodes/*
rm -rf /usr/data/creality/userdata/delay_image/*
That freed up close to 6GB total — roughly 170 leftover gcode files (3.4GB), old firmware upgrade files (~400MB), and 2.3GB of timelapse delay images I didn’t need anymore.
4. Reboot. Mine passed the language screen immediately, the touchscreen responded normally again, and error 0508 hasn’t come back since.
Two things worth flagging before anyone tries this:
-
It only applies if the board is actually booting in the background — verify that with the serial console first. A J1 header that shows nothing at all during power-on points to a deeper hardware issue, and this fix won’t help with that.
-
Still worth ruling out the simple stuff first (cable fully seated, genuine power cycle) like raymond3dcorner suggested earlier in this thread — costs nothing and takes two minutes before pulling out a UART adapter.