You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CC2: how to revert from Cosmos to stock Elegoo firmware (A/B slot, toolhead/bed MCU) #460
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:
Does the CC2 install write only the inactive A/B slot, or both slots / other partitions?
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?
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?
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:
The updated will always write to the non-active slot so this will change with every time you update.
If you revert with the button on the GUI then all the firmware on the external MCUs are also flashed back to stock.
I wouldn't recommend changing u-boot or u-boot variables manually unless you know what you are doing.
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.
@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?
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.
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
/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
@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.
Sharing what worked for me on a CC2 with CANVAS, in case it helps others:
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.
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.
Activity
jamesturton commentedon Nov 1, 2026
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:
Hope this helps!
JohnDS1 commentedon Nov 3, 2026
@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?
jamesturton commentedon Nov 3, 2026
Are you using CC1 or CC2? Did you have
elegoo_canvas = Trueincosmos.confbefore 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.
JohnDS1 commentedon Nov 3, 2026
@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.conffile, then revert back to stock?jamesturton commentedon Nov 4, 2026
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.
JohnDS1 commentedon Nov 4, 2026
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
JohnDS1 commentedon Nov 5, 2026
@jamesturton is there anyway I can get the stock firmware back on the Canvas unit?
jamesturton commentedon Nov 5, 2026
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.
JohnDS1 commentedon Nov 5, 2026
@jamesturton thanks for your help.
I have returned to the Cosmos firmware now.
jamesturton commentedon Nov 6, 2026
Try running these commands over SSH please and post the output here
JohnDS1 commentedon Nov 6, 2026
@jamesturton
No output for this command ^
jamesturton commentedon Nov 6, 2026
Sorry please try
JohnDS1 commentedon Nov 6, 2026
@jamesturton
jamesturton commentedon Nov 6, 2026
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 /etcJohnDS1 commentedon Nov 6, 2026
@jamesturton
jamesturton commentedon Nov 6, 2026
/etc/canvas.veris still there. Can you try deleting it again withrm /etc/canvas.verand checking it's been removed before trying to start the klipper-firmware-canvas againJohnDS1 commentedon Nov 6, 2026
@jamesturton I removed the file and verified it was removed and then started klipper-firmware-canvas
jamesturton commentedon Nov 6, 2026
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
JohnDS1 commentedon Nov 6, 2026
@jamesturton sorry, now it worked!
jamesturton commentedon Nov 6, 2026
Great! Looks like that worked. Can you now restart the printer and check it looks ok
JohnDS1 commentedon Nov 6, 2026
Thanks you, it is now back to working!
jamesturton commentedon Nov 6, 2026
Great to hear!
samfrosnew-lab commentedon Nov 13, 2026
Sharing what worked for me on a CC2 with CANVAS, in case it helps others:
switch-to-oc-patchedleft the CANVAS unresponsive on stock firmware. What fixed it: reinstall COSMOS, setelegoo_canvas = Trueincosmos.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.So for anyone reverting with a CANVAS: make sure
elegoo_canvas = Trueis set and the CANVAS is working in COSMOS before you switch back, and register the machine in Elegoo Matrix afterwards.samfrosnew-lab commentedon Nov 13, 2026
Two more details from my revert on the CC2, which I confirmed on my own printer and could not find in the docs:
ELEGOO.txtplugged in during the revert. This is the file COSMOS wrote to the drive when it was installed.It would be great to have both points added to the uninstall section of the COSMOS install page.
suchmememanyskill commentedon Nov 13, 2026
This does nothing
samfrosnew-lab commentedon Nov 13, 2026
It worked for me, since it wouldn't allow the firmware to be downloaded.