Skip to content

CC2: how to revert from Cosmos to stock Elegoo firmware (A/B slot, toolhead/bed MCU) #460

Open

Description

@BorjaLL

Before installing 26.10.1 on my CC2 I would like to know the way back to stock. The install page only documents "Switch to OC Patched", which has no CC2 build, and warns that flashing an official .swu directly skips downgrading the toolhead/bed and bricks.

My unit: stock 01.03.02.36 running from slot B (boot_partition=bootB), slot A holds 01.03.01.89. I have a full dd image of mmcblk0 taken over SSH and the ELEGOO.txt file.

Questions:

  1. Does the CC2 install write only the inactive A/B slot, or both slots / other partitions?
  2. Does it reflash the toolhead and bed MCUs on the CC2? If so, is there a supported way to put Elegoo's MCU firmware back?
  3. Would switching U-Boot back to the stock slot (or restoring the eMMC image via FEL) plus that MCU step give a working stock printer, or is there a planned "switch to stock" for CC2?

Thanks for the CC2 port.

Activity

  1. jamesturton commented on Nov 1, 2026

    @jamesturton
    Collaborator

    Hi!

    Sorry we haven't finished the documentation for CCW yet, but you can revert to stock using the button in the GUI. You can see how it looks from this PR here #455 (sorry the pictures are all rotated). To answer you specific questions:

    1. The updated will always write to the non-active slot so this will change with every time you update.
    2. If you revert with the button on the GUI then all the firmware on the external MCUs are also flashed back to stock.
    3. I wouldn't recommend changing u-boot or u-boot variables manually unless you know what you are doing.

    Hope this helps!

  2. JohnDS1 commented on Nov 3, 2026

    @JohnDS1

    @jamesturton I reverted back to stock now and now CANVAS is not recognized (Canvas unit does have 2 red lights). How do I fix this?

  3. jamesturton commented on Nov 3, 2026

    @jamesturton
    Collaborator

    2. @jamesturton I reverted back to stock now and now CANVAS is not recognized (Canvas unit does have 2 red lights). How do I fix this?

    Are you using CC1 or CC2? Did you have elegoo_canvas = True in cosmos.conf before you reverted?
    There are very very little tools in the stock firmware to be able to flash the firmware back, so my suggestion would be to go back to using Cosmos, check Canvas is connected and working and then downgrade again.

  4. JohnDS1 commented on Nov 3, 2026

    @JohnDS1

    @jamesturton Canvas was working before a reverted back to stock because of a temperature sensor issue I had. That's when Canvas stopped working. Now I also tried Open Centauri firmware where the temperature sensor issue is resolver or working as expected, but canvas still doesn't work.

    Do you recommend I go back to Cosmos, edit the cosmos.conf file, then revert back to stock?

  5. jamesturton commented on Nov 4, 2026

    @jamesturton
    Collaborator

    Open Centauri firmware

    Does this mean you are using CC1 as we dont have patched firmware for CC2? Sorry I'm not really following.

    Either way, returning to Cosmos will be the easiest way to flash the stock firmware back to the Canvas unit.

  6. JohnDS1 commented on Nov 4, 2026

    @JohnDS1

    My apologies for the confusion. I researched some more and now noticed that the patched firmware is no longer going to be updated in favour of cosmos.

    The firmware I installed on my CC2 is: https://github.com/Neme77/centauri-carbon-2-community/tree/develop

  7. JohnDS1 commented on Nov 5, 2026

    @JohnDS1

    @jamesturton is there anyway I can get the stock firmware back on the Canvas unit?

  8. jamesturton commented on Nov 5, 2026

    @jamesturton
    Collaborator

    Like I said in my last comment, the easiest way to recover is by returning to Cosmos as there were have all the tooling for updating the MCUs. Once you have flashed Cosmos again please let me know and I can help guide you through re-flashing the Canvas unit.

  9. JohnDS1 commented on Nov 5, 2026

    @JohnDS1

    @jamesturton thanks for your help.

    I have returned to the Cosmos firmware now.

  10. jamesturton commented on Nov 6, 2026

    @jamesturton
    Collaborator

    Try running these commands over SSH please and post the output here

    service klipper stop
    rm /etc/canvas.ver
    service klipper-firmware-canvas start
    
  11. JohnDS1 commented on Nov 6, 2026

    @JohnDS1

    @jamesturton

    root@centauri-carbon-2:~# service klipper stop
    Stopping klipper...
    stopped process in pidfile '/var/run/klipper.pid' (pid 436)
    
    root@centauri-carbon-2:~# rm /etc/canvas.ver 
    

    No output for this command ^

    root@centauri-carbon-2:~# service klipper-firmware-canvas restart
    Usage: /etc/init.d/klipper-firmware-canvas {start|status}
    
  12. jamesturton commented on Nov 6, 2026

    @jamesturton
    Collaborator

    Sorry please try

    service klipper-firmware-canvas start
    
  13. JohnDS1 commented on Nov 6, 2026

    @JohnDS1

    @jamesturton

    root@centauri-carbon-2:~# service klipper-firmware-canvas start
    Starting klipper-firmware-canvas...
    Firmware is already up to date.
    
  14. jamesturton commented on Nov 6, 2026

    @jamesturton
    Collaborator

    I don't really understand this. Removing the version file should cause the service script to try re-flashing the canvas. Can you check what exists in /etc with ls -ls /etc

  15. JohnDS1 commented on Nov 6, 2026

    @JohnDS1

    @jamesturton

    root@centauri-carbon-2:~# ls -ls /etc/
         4 -rw-r--r--    1 root     root            45 Nov  5 18:54 bed.ver
         2 -rw-r--r--    1 root     root          2472 Mar  9  2018 busybox.links.nosuid
         0 -rw-r--r--    1 root     root            91 Mar  9  2018 busybox.links.suid
         0 drwxr-xr-x    3 root     root            31 Mar  9  2018 ca-certificates
         5 -rw-r--r--    1 root     root          4903 Mar  9  2018 ca-certificates.conf
         4 -rw-r--r--    1 root     root            45 Nov  6 08:34 canvas.ver
         0 -rw-r--r--    1 root     root             0 Nov  6  2026 centauri-carbon-2-detected
         2 -rw-r--r--    1 root     root          1676 Mar  9  2018 chrony.conf
         0 drwxr-xr-x    3 root     root            70 Mar  9  2018 dbus-1
         0 drwxr-xr-x    3 root     root            89 Mar  9  2018 default
         0 drwxr-xr-x    2 root     root             3 Mar  9  2018 depmod.d
         4 drwxr-xr-x    1 root     root          4096 Nov  6  2026 dropbear
         2 -rw-r--r--    1 root     root          1936 Mar  9  2018 ethertypes
         0 drwxr-xr-x    3 root     root            47 Mar  9  2018 fonts
         1 -rw-r--r--    1 root     root           740 Mar  9  2018 fstab
         0 -rw-r--r--    1 root     root            75 Mar  9  2018 fw_env.config
         1 -rw-r--r--    1 root     root           523 Mar  9  2018 group
         4 -rw-r--r--    1 root     root             9 Nov  5 18:54 grumpyscreen-config.ver
         0 -r--------    1 root     root           438 Mar  9  2018 gshadow
         0 -rw-r--r--    1 root     root            26 Mar  9  2018 host.conf
         0 -rw-r--r--    1 root     root            18 Mar  9  2018 hostname
         0 -rw-r--r--    1 root     root           242 Mar  9  2018 hosts
         0 -rw-r--r--    1 root     root            22 Mar  9  2018 hwrevision
         0 drwxr-xr-x    2 root     root           910 Mar  9  2018 init.d
         1 -rw-r--r--    1 root     root          1110 Mar  9  2018 inittab
         0 drwxr-xr-x    2 root     root             3 Mar  9  2018 inittab.d
         0 -rw-r--r--    1 root     root           112 Mar  9  2018 issue
         0 -rw-r--r--    1 root     root            32 Mar  9  2018 issue.net
         8 drwxr-xr-x    1 root     root          4096 Nov  5 18:54 klipper
         4 -rw-r--r--    1 root     root             8 Nov  5 18:54 klipper-config.ver
         5 -rw-r--r--    1 root     root          5521 Mar  9  2018 ld.so.cache
         0 -rw-r--r--    1 root     root            33 Mar  9  2018 ld.so.conf
         0 drwxr-xr-x    2 root     root            44 Mar  9  2018 libnl
        13 -rw-r--r--    1 root     root         13498 Mar  9  2018 login.defs
         0 -rw-r--r--    1 root     root           121 Mar  9  2018 logrotate-dmesg.conf
         0 drwxr-xr-x    2 root     root            38 Mar  9  2018 modprobe.d
         0 -rw-r--r--    1 root     root           494 Mar  9  2018 motd
         0 lrwxrwxrwx    1 root     root            12 Mar  9  2018 mtab -> /proc/mounts
         0 drwxr-xr-x    6 root     root           106 Mar  9  2018 network
         0 -rw-r--r--    1 root     root           487 Mar  9  2018 nsswitch.conf
         0 lrwxrwxrwx    1 root     root            21 Mar  9  2018 os-release -> ../usr/lib/os-release
         1 -rw-r--r--    1 root     root           825 Mar  9  2018 passwd
         2 -rw-r--r--    1 root     root          1943 Mar  9  2018 profile
         3 -rw-r--r--    1 root     root          3144 Mar  9  2018 protocols
         0 drwxr-xr-x    2 root     root           493 Mar  9  2018 rc0.d
         0 drwxr-xr-x    2 root     root           400 Mar  9  2018 rc1.d
         0 drwxr-xr-x    2 root     root           439 Mar  9  2018 rc2.d
         0 drwxr-xr-x    2 root     root           439 Mar  9  2018 rc3.d
         0 drwxr-xr-x    2 root     root           422 Mar  9  2018 rc4.d
         0 drwxr-xr-x    2 root     root           439 Mar  9  2018 rc5.d
         0 drwxr-xr-x    2 root     root           495 Mar  9  2018 rc6.d
         0 drwxr-xr-x    2 root     root           419 Mar  9  2018 rcS.d
         0 lrwxrwxrwx    1 root     root            20 Mar  9  2018 resolv.conf -> /var/run/resolv.conf
         1 -rw-r--r--    1 root     root           911 Mar  9  2018 rpc
         2 -r--------    1 root     root          1866 Mar  9  2018 securetty
        13 -rw-r--r--    1 root     root         12990 Mar  9  2018 services
         0 -r--------    1 root     root           505 Mar  9  2018 shadow
         0 -rw-r--r--    1 root     root            42 Mar  9  2018 shells
         0 drwxr-xr-x    2 root     root            46 Mar  9  2018 skel
         0 drwxr-xr-x    5 root     root            83 Mar  9  2018 ssl
         0 -rw-r--r--    1 root     root            90 Mar  9  2018 swupdate.cfg
         0 -rw-r--r--    1 root     root           451 Mar  9  2018 swupdate_public.pem
         1 -rw-r--r--    1 root     root           651 Mar  9  2018 syslog-startup.conf
         0 -rw-r--r--    1 root     root            69 Mar  9  2018 syslog.conf
         0 drwxr-xr-x   10 root     root            87 Mar  9  2018 terminfo
         4 -rw-r--r--    1 root     root            15 Nov  6 08:33 timestamp
         4 -rw-r--r--    1 root     root            45 Nov  5 18:54 toolhead.ver
         0 drwxr-xr-x    4 root     root            77 Mar  9  2018 udev
         0 drwxr-xr-x    2 root     root            32 Mar  9  2018 udhcpc.d
         0 -rw-r--r--    1 root     root            15 Mar  9  2018 version
         0 lrwxrwxrwx    1 root     root            18 Nov  6 08:34 webui -> /var/www/mainsail/
         4 -rwxr-xr-x    1 root     root           104 Nov  6  2026 wpa_supplicant.conf
         1 -rw-r--r--    1 root     root           681 Mar  9  2018 xattr.conf
    
  16. jamesturton commented on Nov 6, 2026

    @jamesturton
    Collaborator

    /etc/canvas.ver is still there. Can you try deleting it again with rm /etc/canvas.ver and checking it's been removed before trying to start the klipper-firmware-canvas again

  17. JohnDS1 commented on Nov 6, 2026

    @JohnDS1

    @jamesturton I removed the file and verified it was removed and then started klipper-firmware-canvas

    root@centauri-carbon-2:~# service klipper-firmware-canvas start
    Starting klipper-firmware-canvas...
    Firmware version mismatch or not installed, flashing firmware...
    
    thread 'main' (3027) panicked at src/main.rs:111:10:
    Failed to open port: Error { kind: NoDevice, description: "Unable to acquire exclusive lock on serial port" }
    note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
    Firmware flash failed, version not updated.
    
  18. jamesturton commented on Nov 6, 2026

    @jamesturton
    Collaborator

    Ohh you have klipper running again. Did you restart since the last attempt?

    Try running these three commands again #460 (comment) I have now updated my comment to be correct

  19. JohnDS1 commented on Nov 6, 2026

    @JohnDS1

    @jamesturton sorry, now it worked!

    root@centauri-carbon-2:~# service klipper-firmware-canvas start
    Starting klipper-firmware-canvas...
    Firmware version mismatch or not installed, flashing firmware...
    Waiting up to 20s for the CC2 bootloader on /dev/ttyS1...
    Erased 43008 bytes
    Sending block 1/84
    Sending block 2/84
    Sending block 3/84
    Sending block 4/84
    Sending block 5/84
    Sending block 6/84
    Sending block 7/84
    Sending block 8/84
    Sending block 9/84
    Sending block 10/84
    Sending block 11/84
    Sending block 12/84
    Sending block 13/84
    Sending block 14/84
    Sending block 15/84
    Sending block 16/84
    Sending block 17/84
    Sending block 18/84
    Sending block 19/84
    Sending block 20/84
    Sending block 21/84
    Sending block 22/84
    Sending block 23/84
    Sending block 24/84
    Sending block 25/84
    Sending block 26/84
    Sending block 27/84
    Sending block 28/84
    Sending block 29/84
    Sending block 30/84
    Sending block 31/84
    Sending block 32/84
    Sending block 33/84
    Sending block 34/84
    Sending block 35/84
    Sending block 36/84
    Sending block 37/84
    Sending block 38/84
    Sending block 39/84
    Sending block 40/84
    Sending block 41/84
    Sending block 42/84
    Sending block 43/84
    Sending block 44/84
    Sending block 45/84
    Sending block 46/84
    Sending block 47/84
    Sending block 48/84
    Sending block 49/84
    Sending block 50/84
    Sending block 51/84
    Sending block 52/84
    Sending block 53/84
    Sending block 54/84
    Sending block 55/84
    Sending block 56/84
    Sending block 57/84
    Sending block 58/84
    Sending block 59/84
    Sending block 60/84
    Sending block 61/84
    Sending block 62/84
    Sending block 63/84
    Sending block 64/84
    Sending block 65/84
    Sending block 66/84
    Sending block 67/84
    Sending block 68/84
    Sending block 69/84
    Sending block 70/84
    Sending block 71/84
    Sending block 72/84
    Sending block 73/84
    Sending block 74/84
    Sending block 75/84
    Sending block 76/84
    Sending block 77/84
    Sending block 78/84
    Sending block 79/84
    Sending block 80/84
    Sending block 81/84
    Sending block 82/84
    Sending block 83/84
    Sending block 84/84
    Firmware flashed and version recorded.
    
  20. jamesturton commented on Nov 6, 2026

    @jamesturton
    Collaborator

    Great! Looks like that worked. Can you now restart the printer and check it looks ok

  21. JohnDS1 commented on Nov 6, 2026

    @JohnDS1

    Thanks you, it is now back to working!

  22. jamesturton commented on Nov 6, 2026

    @jamesturton
    Collaborator

    Great to hear!

  23. samfrosnew-lab commented on Nov 13, 2026

    @samfrosnew-lab

    Sharing what worked for me on a CC2 with CANVAS, in case it helps others:

    1. CANVAS dead after reverting (no lights at all). My first revert with switch-to-oc-patched left the CANVAS unresponsive on stock firmware. What fixed it: reinstall COSMOS, set elegoo_canvas = True in cosmos.conf, reboot (the CANVAS board got flashed automatically on that boot), confirm the CANVAS works in COSMOS, then revert again. After the second revert the CANVAS worked on stock.
    2. Stock firmware would not update after reverting. The fix was to register the printer in Elegoo Matrix. After registering, the system update ran without errors.

    So for anyone reverting with a CANVAS: make sure elegoo_canvas = True is set and the CANVAS is working in COSMOS before you switch back, and register the machine in Elegoo Matrix afterwards.

  24. samfrosnew-lab commented on Nov 13, 2026

    @samfrosnew-lab

    Two more details from my revert on the CC2, which I confirmed on my own printer and could not find in the docs:

    1. Keep the USB drive with ELEGOO.txt plugged in during the revert. This is the file COSMOS wrote to the drive when it was installed.
    2. Revert from the printer itself (the "Switch to Stock" button on the screen), not by flashing a firmware file from USB.

    It would be great to have both points added to the uninstall section of the COSMOS install page.

  25. suchmememanyskill commented on Nov 13, 2026

    @suchmememanyskill
    Contributor

    Keep the USB drive with ELEGOO.txt plugged in during the revert. This is the file COSMOS wrote to the drive when it was installed.

    This does nothing

  26. samfrosnew-lab commented on Nov 13, 2026

    @samfrosnew-lab

    It worked for me, since it wouldn't allow the firmware to be downloaded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions