CR4CU220812S12 ingenic firmware file

Flagship K Series Creality Flagship K1 Max
1

So, I apparently f’ed up the OS on my K1 Max enough that it won’t boot. Just shows Creality on the screen and that is it. Can’t login via SSH or any method. factory-reset file on a usb stick does not work. Hopefully I can find the fabled ingenic file for this mainboard and use usbcloner to revive it. Unless anyone else has other recommendations.

1 Like
2

Hi, I’ve encountered the same issue. However, it happened after I connected the CFS-C. I couldn’t find the firmware file. Should I contact customer support?

3

https://github.com/CrealityOfficial/K1_Series_Klipper/releases

https://guilouz.github.io/Creality-Helper-Script-Wiki/firmwares/firmware-recovery-k1/

4

Hello, thanks for the links. I tried flashing it, but now I see an image of a mountain. Any ideas on what I can do?

5

So, to restore a printer with an inverted mountain display, you need to copy a full dump from another board and load it onto your faulty board. But that’s not all! After that, you need to follow the instructions in the link above, and perform a restore using cloner version 2.18, as well as firmware version 1.3.2.1.

6

Hey Mate,

Thanks for posting an update.

I have a Ender 3 v3 that screen fully stopped working after the power went out mid print.

I have followed the steps and loaded on the s11 firmware but now im seeing the mountain….

Im a bit confused what you mean by a “full dump” and then a restore….

If you could help me out that would be much appreciated :slight_smile:

7

HELLO,
I have exactly the same problem with my K1 Max device (CR4CU220812S12 motherboard).
I’ve been trying to fix it using USB Cloner for two days. My current situation is as follows:
:white_check_mark: USB Cloner successfully connected :white_check_mark: Ingenic USB Boot Device driver installed :white_check_mark: DDR recognized: W97BV6MK_LPDDR2, type: 2, frequency: 400MHz
:white_check_mark: Phase 1 firmware is running :cross_mark: PHASE 2 INITIAL ERROR — eMMC cannot be initialized
The problem is that the S11 spl.bin file has different parameters than the eMMC initialization parameters required by the S12 board. There is no publicly available .ingenic file for the S12. If anyone has a working K1 Max or K1C device with a CR4CU220812S12 motherboard and SSH access, please run this command:
dd if=/dev/mmcblk0boot0 of=/tmp/spl_dump.bin bs=512 count=256
Then download the file from /tmp/spl_dump.bin and share it here or via Google Drive.
This spl.bin dump will allow all of us whose S12 motherboards have become unusable to recover our printers. You will be helping many people!
Thank you very much.

8

I have tested using this method on a S11 board and have no issues, but when trying this on multiple S12 boards all attempts have failed.

9

The spl.bin is located here. https://github.com/swilsonnc/ACEPROK1Max

Hopefully that works for you.

10

My K1C also has the board ending in S12 and it became unusable. The LCD screen has stripes when turned on and seems to be frozen (you can’t see anything on it). I already changed the cable and it’s still the same.
I’m a layman on the subject (I only do 3D modeling and printing) and I don’t understand anything about programming. When I use Ingenic S11, I noticed this appears in the cloner:
QuaZipFile::atEnd(): file is not open
I used cloner version 2.5.18.
When I use another version, it gives a fatal error and data.

11
12

1 Like
13

Привет, в архиве нет файла unboot и sn_mac

14

Wanted to share something in case it saves someone else the days I just spent on this.

Like a few people in this thread, my board froze on the “checking language” screen throwing error 0508, and my first assumption was the same as everyone else’s — dead firmware, need the S12 .ingenic file Creality still hasn’t published. I went down the exact same road: USB Cloner connected fine, board detected as X2000E, config set to x2000e_sfc_nand_ota_lpddr2_linux.cfg… and then hit the same wall as murat_karakoç and Tony_09 — no official S12 recovery file exists anywhere.

Before you assume it’s the missing firmware file, check disk usage. In my case error 0508 had nothing to do with the bootloader or firmware at all — /usr/data was simply 100% full (mine was at 6.5GB used, mostly accumulated gcode files and timelapse delay images) and the board couldn’t finish booting into userspace because of it.

How I found this out, in case it’s useful to anyone stuck at the same screen:

  • Wired a USB-to-TTL adapter (any 3.3V one works — I used an SH-U09C5) to the J1 header. Pinout from the center pin outward is GND / RX / TX, 3.3V logic.

  • Opened a terminal at 115200 baud (PuTTY on Windows) and power cycled the board while watching the boot log.

  • Mine actually came up on its own while I was watching the serial output — the freeze wasn’t total, it was hanging on something disk-related.

  • Once I had a shell, df -h /usr/data confirmed it — 100% used.

  • Cleared it out:

  rm -f /usr/data/printer_data/logs/*
  rm -f /usr/data/creality/userdata/log/*
  rm -f /usr/data/creality/userdata/delay_image/*
  rm -rf /usr/data/creality/upgrade/*
  • Rebooted and it came up completely normally — no firmware flashing needed.

This obviously won’t help everyone in this thread — if you get zero serial output at all when you power cycle, that’s a genuinely dead bootloader and you still need the real .ingenic file. But if you can see it boot (or partially boot) over UART, it’s worth ruling out a full disk before spending more time chasing a file Creality hasn’t released.