K1 max stuck on language selection (touchscreen not working)

Flagship K Series Creality Flagship K1 Max
1

I need help, When I turn on my printer it goes to the language selection and no matter what I press it doesn’t register, I thought maybe it froze so l left there for a good while but still it’s stuck

2

I have the same problem. What did you do? Have you been helped?

3

Same Problem with me as well

4

Double check the cable connection to ensure with the solid connection. The cable is fully insert to the connector. Sometime loose cable or belt cable will cause the screen not responding. Also check is there any physical damage on the ribbon cable.

If the cable connection is good. Try to do a power cycle on the printer. Unplug the power cord for 2 min and reconnect the power cord after. See is the able to pass the language selection.

If problem still persists please contact cs@creality.com for further assistance. Get your printer model number, serial number and proof of purchase on your email. It can help to speed up the process.

5

Mine is with the same issue! how can I solve?

6

Same problem here! anyone can solve it?

7

Chiming in here because I hit this exact symptom — stuck on the language selection screen, screen completely unresponsive to touch — and it turned out to have nothing to do with the touchscreen itself.

Mine’s a K1 Max with the S12 board (Ingenic X2000E). It would boot through the Creality logo, land on language selection, and just sit there no matter what I tapped — plus error 0508 flashing up before it locked. Ribbon cable was fine, power cycling didn’t help. Natural assumption at that point is a dying screen or a bad connector.

It wasn’t the screen — /usr/data was completely full. The touchscreen UI hangs trying to read/write settings it can’t get to when the partition is out of space, and a hung UI looks exactly like an unresponsive touchscreen. It isn’t a hardware fault at all.

How I confirmed it and fixed it, in case it saves someone else the same runaround:

  1. Get a serial console — you don’t need the touchscreen for this part. I used a cheap 3.3V USB-to-TTL adapter (SH-U09C5) wired to the J1 header on the mainboard (GND / RX / TX from the center pin outward), opened a terminal at 115200 baud, and power-cycled the printer while watching it. If you see boot text scroll by and it reaches a login/shell prompt, your board is not bricked — you’re looking at a software hang, not dead hardware.

  2. Check disk space:

   df -h /usr/data

Mine came back 100% full, 0 bytes available.

  1. Clear the usual space hogs. For me it was accumulated gcode files and timelapse frames:
   rm -rf /usr/data/printer_data/gcodes/*
   rm -rf /usr/data/creality/userdata/delay_image/*

Worth checking what’s actually eating your space first with du -sh /usr/data/* | sort -rh rather than deleting blind. In my case that cleared roughly 6GB — about 170 old gcode files (3.4GB), leftover firmware upgrade files (~400MB), and 2.3GB of timelapse delay images.

  1. Reboot. Mine came straight up past the language screen, touchscreen fully responsive again, error 0508 gone for good.

A couple of caveats so nobody goes down the wrong path:

  • This is specifically for boards that are still booting normally in the background — confirm that with the serial console before doing anything else. If J1 gives you nothing at all during power-on, that’s a different and more serious problem than this fix addresses.

  • Definitely still worth checking the basics raymond3dcorner mentioned above (ribbon cable fully seated, genuine power cycle) first — cheap to rule out before pulling out a UART adapter.

8

Can you explain/show pictures of connecting the adapter?