i come from the land of shitbox cars, so i did check those fuses, and the front screen is disconnected so even if the button was stuck it no longer can send an input.
i did have the drive connected. so the same firmware flash i did earlier but with the toolhead board not connected?
no. Power cycle just the tool head by unplugging the 24v power.
That way Linux is booted and ssh is live when the toolboard boots
Some archaic microcontrollers would only go into “programming” mode for a brief time after power up. None of those had CAN but why not try
got the same ‘no device detected on canbus’ error
I got nothing more
My guess is the bootloader on your toolhead MCU is corrupted. That is exceedingly rare. Microcontrollers are INTENTIONLY hard to “reprogram” and built from the ground up to tolerate “rough conditions” like unintentional resets.
Without knowing what bootloader Sovol chose (there are many, which is why Klipper needs to know the bootloader offset to compile firmware) there isn’t anything I can do for you.
Writing the bootloader usually requires a hardware interface other than USB or CAN. Even if you had the programmer you don’t have the bootloader code.
1 Like
I contacted customer support last night since it seems I’ve exhausted all options to fix it myself.
I want to thank you and everyone in this thread for being extremely patient and helpful. This is my first printer, and while it sucks that it’s broken, I’ve learned a lot in this process of attempting to fix it.
It’s also encouraging since I plan on using this printer to help me build a Voron 2.4 in a few months. I’m good with hardware and assembly but software is my weak spot.
It will boot just fine without the original LCD, I don’t have mine plugged in at all, just using a touch screen.
Did customer support have any solution for you?
They asked if I turned it off and on after I told them I SSHed in and tried to reflash the firmware but I get a CANBUS Error 
I’ve now had to tell them a 3rd time that I SSHd into the printer, attempted to reflash the firmware, and get a can bus error.
To say I’m frustrated that they don’t read what I’m sending them is an understatement.
I hope you can get your support query escalated to some more technical tier of support (if Sovol has such). In the worst case, you current contact is just browsing some support manual which doesn’t cover situations where the customer is able to SSH into the device and get a more detailed error message than the “stuck at ‘system booting’” description of the issue you’d likely otherwise have provided them.
1 Like
I hope so as well. It feels like I’m emailing a bot, not a human.
@sovol3d Please review this thread and expedite the support process.
Try the Unofficial Sovol Discord, there are a lot of smart people over there.
They are now sending me a new eMMC and mobo.
Fingers crossed that works.
If they are sending the main MB not the toolhead one I’m afraid that won’t be the case. That the toolhead MCU processor type showed up in Mainsail makes me think CAN is okay on the mainboard and the CAN transceiver in the toolhead is okay too. I still think it is a toolhead MCU bootloader problem.
They are sending both the toolhead and eMMC board. I didn’t word that correctly