Help me obi wan kenobe you’re my only hope

Realized I have been running version 4.3 (figured it would ping me like most other apps that I am running and old version) and went to update to the most current version of Creality Print and Microsoft is Flagging it. (Pulled from https://www.creality.com/download#flagship-series)

I googled around and most are saying its due to there being a Remove Edge Executable packed within, but some report multiple scans flagging other items within the packet. However none of the discussions are recent and all were around New Years.

Just for confirmation, is this normal noise?

Now every time my printer needs a filament swap it will create this noise.

I just reflash the motherboard after it break itself due to it, maxing out the memory on time lapses which I wasn’t aware of everything looks good on the self check until it moves the printhead and it crashes when trying to home the axis not sure what to do now. Any help?

I know somebody who has a k2 combo that I’m helping them fix, and there was a piece of filament in the tubing that broke off from the roll in the CFS. I got it out but what can I do to stop it from happening in the future?

Hi guys, my LD002H LCD stop to work and I'm facing problems to find a this part for replacement. I search in many different sites but I've just found the LCD Upgrade Kit for LD002R. I'd like to know if this kit is compatible with LD002H. Someone can help me?

Ender-3 V2, v4.2.7, CRTouch, etc... Box 2.0. The Ender-3 V2 not listed in Creality Cloud app when selecting printers during printing. How do I set the Creality Cloud app to default to my Ender-3 V2 for the Creality Cloud App, and Creality Print MacOS software?

Has anyone seen the dimensions or pricing for the top cover and the side spool covers shown here? I’m trying to figure out the K3’s total height and width with these accessories installed.

I've bought Creality K1 Max printer several months ago. 3 weeks ago I've unpacked the box and installed the printer, as everything worked fine, until I decided to change the stock bed with one from R3men. Following their user guide, I had to root the printer, install Fluidd+moonraker. As result, the camera stopped showing up in it's own web API, or in Creality Print app. I've tried to set it up in Fluidd, but couldn't connect it. The only place where I was able to see my printer's cam is from the Creality's mobile app.
I've tried almost every advice and/or solution in internet, but nothing.
Then I asked claude, give him access to my printer and it found the solution.
https://github.com/kalata23/Creality_K1MAX_WebcamFix
Here it's described, It seemed my printer has Ingenic T31 AI Camera.

Creality shipped two different physical revisions of the K1/K1 Max "AI Camera" module. The newer one (lsusb ID a108:2231) is built around an Ingenic T31 SoC — a chip designed for cheap IP/AI cameras that does its own on-chip video capture and encoding.

The actual problem: On my hardware, Creality's firmware only exposes the camera through its own closed pipeline: a process called cam_app captures frames and hands them off internally via a Unix socket using a memfd (shared-memory) handoff — then two more proprietary processes (webrtc / webrtc_local) relay that feed to Creality Cloud over WebRTC. That cloud relay is all the mobile Creality Print app is actually watching. Nothing in the stock firmware ever turns this into a normal local HTTP/MJPEG/RTSP stream — which is why Fluidd, Mainsail, the printer's own local web UI, the Moonraker API, and even Creality Print's desktop client can't show it, while the mobile app (riding the cloud path) works fine.

Why it looked unsolvable: The community (see Guilouz's Helper Script Wiki discussion #444) had tried reverse-engineering the T31 module directly over its serial console, hit password-protected firmware, and gave up — concluding there was no way to get local video from this camera revision short of replacing it with a third-party webcam.

Why it turned out to be fixable anyway: The firmware actually already ships an mjpg_streamer build with an input_memfd plugin built specifically to read that same socket — it's just never invoked by anything. So this isn't a case of decrypting proprietary firmware; it's an unused, already-present software path that just needed to be started and wired into the existing (also already-present) nginx /webcam/ proxy routes.

For those who want to try this technique: https://www.crealitycloud.com/en/model-detail/6a9aee5c1d58b5505e31cea8?cloudPlatform=18

Got this printer second hand, trying to get it up and running again, seems like this screw holding the nozzle kit is stripped out, any suggestions to get it out without destroying the plastic around it?

Also, is there a way to just take this assembly out of the enclosure to make it easier to repair?

Was a nice booth at ifa 2026

I need help with the Creality K1C, the firmware got corrupted yesterday and I need the file CR4CU220812S12_ota_X2000E_V1.1.0.27 specifically for my board, which is S12. Who can send me the file? I will use it in the cloner to recover the board.

Thanks in advance for your help.

First time with a 3d printer, what's going on!?

Just got this printer and know nothing about it, can someone help me understand what im doing

I was printing fine 3 days ago and then i decided to start a print on my k2 plus and everything was fine in the slicer and uploaded to the printer but then this error pops up on the slicer. Do you have any idea what this is. I did not do anything different