Just got the printer today. Ran a benchy, then decided I would calibrate E steps. Was going through the menu and miss clicked something I didn’t want it to do, pressed the stop button
Now the printer won’t boot. Been trying all sorts of things the last 2 hours to get it to boot with no luck.
Try pushing or holding the stop button…it might be jammed.
From what you posted, you probably should have just let the process continue or flipped the power switch…hitting the emergency stop is a last resort.
Have tried that. I didn’t realize it functioned like a E stop. Essentially cutting power to the machine, which I know can corrupt software.
The only other option I can think of is you’ll have to re-flash the firmware.
After the install, do the calibrations…then do the OTA update & do the calibrations again.
EDIT: According to the instructions, the printer has to be booted first before you insert the USB drive.
So unless someone has another option, you might have to wait a few days for Sovol to reply.
I don’t think that’s going to work with that file because it doesn’t have the correct filename. The firmware upgrade logic from usb is looking for files named “SV08mini_Update_Package*.deb” so something starting with “SV08 zero” isn’t going to trigger the upgrade process. Not really sure what Sovol messed up with that package anyway because it doesn’t even contain 1.4.1 but 1.4.0 instead. 1.4.1 was some days later released as SV08mini_Update_Package-04-19-1.4.1.deb.
The current latest firmware is available from https://www.comgrow.com/files/printer/SV08mini_Update_Package-05-20_1-4-7.deb
So the files for the Zero are on the Comgrow site..??
Sovol needs to fix that.
It gets better.
Goto www.comgrow.com and click “Return to home”
I went to pull the SD card so I could flash it and it doesn’t have one so yeah, I was pretty certain this board is bricked.
Definitely a fantastic experience with my first printer 
Did you configure network access to it before you got it to that state?
If you can get the printer to connect to a network, wired or wireless, then you could try to ssh in and see in what state it is. If it’s only the klipper firmware that’s in some inconsistent state then reinstalling the firmware package (or some different version that’s currently in) will flash the klipper firmware and overwrite whatever is corrupted.
It doesn’t use an SD Card, it should have come with a USB Drive.
Voron mobos have an SD card for the firmware.
No I didn’t, but it does have the Ethernet port and I have a laptop. Is it possible to get into it via Ethernet without it configured?
Do you have a router with ethernet ports? The Zero expects to get assigned an IP address from a DHCP host. A direct PC <> Zero you’ll have to figure out the default IP then configure an IP on the laptop to the same IP range.
A couple notes that might help.
The Zero uses the same mainboard as the SV08. Lots more google hits for the older machine.
That mainboard contains 3 complete functional units.
It’s probably easier to try the usb upgrade method then first because it’s there starting from the first firmware and isn’t going to change anything if the Linux OS is somehow not even starting (which I don’t think is likely).
If any of these steps results in something unexpected, stop there and ask here.
I tried it 3 separate times with no changes. The flash drive only has the .dev file on it. I usually gave it at least an hour before trying again.
At which point does the printer boot get stuck?
Do the fans start running? If yes, which ones?
Does the display backlight power on?
Is anything shown on the display?
Screen says ‘system booting’. The tool head led is lit, and the mobo cooling fan is on. This is the state it’s in right after turning it on and nothing changes status.
Ok, I have at least one more idea. It could be possible that you managed to activate the OTA update with the “going through the menu and miss clicked something I didn’t want it to do”. The OTA update has the annoying feature that it will directly start the upgrade if there’s one without asking the user. Since you did have a new printer, it’s pretty much guaranteed to come with an older than the latest firmware so the upgrade would have started and you either may have succeeded in interrupting it or it may have failed.
Sovol recently introduced a feature in the new firmware packages that the klipper firmware doesn’t anymore get upgraded unless it has changed. However, the possible issue is that it doesn’t query this information from the firmware itself but from the menu.cfg file which gets installed before the firmware upgrade. So if the firmware upgrade fails, the menu.cfg will still point to the latest firmware and trying to reinstall the package isn’t going to do anything.
The assumption is that due to either the OTA update or the manual tries, you now have at least partially version 1.4.7 installed. I know that 1.4.6 has a misconfiguration so we’ll not try to roll back to that one. 1.4.2 was the previous release before 1.4.6 so let’s try that → follow the same instructions above but use the following url instead: https://www.comgrow.com/files/printer/SV08mini_Update_Package-04-22_1-4-2.deb
Hope that helps. The display not being totally blank and the fans starting at least suggest the system isn’t totally bricked.
If that doesn’t help then connect any screen to the HDMI port and see what it outputs during power on. It may provide a clue what the issue is. Getting network connectivity and then SSH in to force the firmware upgrade would also still be a possibility.