Ender 3 S1 - firmware update issues - downgrade screen firware needed I think

Ender Series Creality Ender-3 S
1

Hi all, I have a Ender 3 S1 that I bought secondhand about 2 months ago. I was getting some uneven surfaces on long diagonal prints so figured I should try updating the firmware after researching and finding V1.0.6_C has some resonance compensation features added or improved.

The firmware on my printer was on v1.0.5_C and I identified that I have the F1 chip.

Essentially before know and figuring out the different chip versions etc I downloaded the the latest version V3.2.0_Nine_C_F401 and opened the folder. . . then figuring out that I have the F1 chip i also downloaded the V1.0.6_C update. . . then in my confusion I accidentally installed the dcboot.bin file from V3.2.0_Nine_C_F401 on the screen which seemed to go fine. Then realizing my mistake, i installed the private folder from v1.0.6_C update. This also seems to have installed fine but the screen is not showing anything. I’m thinking the dcboot.bin file is the issue as its the wrong boot loader or something. But I can’t seem to find a dcboot.bin file for v1.0.6_c or find a way to uninstall the dcboot file.

So I updated the firmware of the main board to 1.0.6_c thinking that would help but the screen still seems to be blank.

I do get a beep when i push the main button on the screen. So there is some life in it.

So I think i’m needing to essentially downgrade the dcboot file from V3.2.0_Nine_C to v1.0.6_C? Is this correct and how would I do this as there is no dcboot file in the v1.0.6_C firmware folder that you down load from creality? Or do I update the whole screen to V3.2.0_Nine_C_F401 and leave the main board at v1.0.6_C?

Thanks in advance!

Tristan.

Correction - SWV3.1.9_Two_C_F401 is actually the version I have downloaded and installed the dcboot.bin file onto the screen - not the V3.2.0_Nine_C_F401 i mentioned above. . . not sure where my head was at yesterday. . . panic stations probably. . .

Here is a link to a video and some pics of the situation from today. It’s a Dropbox link
https://www.dropbox.com/scl/fo/c3hzqkvo5wk46a1vbmxcs/APSLMFM0ASWVbKoxKKI_TQU?rlkey=suzpj0zk5xggd1rw346h80gio&st=tj7vzn1d&dl=0

Thanks again.

Tristan

2

Hi there,

An update from my side. Thought I’d share it in case someone else has this issue.

The other day I actually managed to resolve the issue pretty much. I ended up completing the install of V3.1.9_Two_C_F401 on the screen as previously I only installed the dcboot.bin file before realizing my mistake. Once I had finished the installation of V3.1.9_Two_C_F401 on the screen, the screen worked again, yet wasn’t able to read data from the main board as the main board was running V1.0.6_C. So I then installed the “private” folder for V1.0.6_C onto the screen and it now seems to be working. Although the :'s within the times etc on the screens aren’t aligned properly for some reason.

So currently the main board seems to be on V1.0.6_C and the screen is mostly running the “private” folder of V1.0.6_C. And things seem to be running ok again.

Hope this is helpful!