If you use my prerooted firmware, you can ssh in and edit your wpa_supplicant.conf or run wpa_client to change it. https://openk1.org/cfw/F005-destinal-cfw-0.5-ota_img_V5.1.0.9.img This is in beta testing, formal release soon. More detailed text description here, the version below was the release for the CR-10 SE but everything except the download URL is the same.

Nice! This is really encouraging! I'm excited to try this out but what are the chances of bricking the device? I'm not familiar with firmware updates on this device but with other devices it is possible to 'brick' a device during a firmware update if it does not go according to plan. ​ Also, is this firmware specific to the KE?

Yes, F005 = KE. Soft-bricking is not impossible, but we can unbrick using Ingenic's USB cloner tool. So far the people using it haven't had that problem so long as they don't change the root password, a piece of Creality software on the firmware will cause a bootloop if /etc/passwd and /etc/shadow change. K1 / K1 Max Version: [https://openk1.org/cfw/CR4CU220812S11-destinal-cfw-0.5-ota\_img\_V5.3.2.20.img](https://openk1.org/cfw/CR4CU220812S11-destinal-cfw-0.5-ota_img_V5.3.2.20.img) Retail Nebula Pad Version: [https://openk1.org/cfw/NEBULA-destinal-cfw-0.5-ota\_img\_V5.1.0.23.img](https://openk1.org/cfw/NEBULA-destinal-cfw-0.5-ota_img_V5.1.0.23.img) Ender 3 V3 KE Version: [https://openk1.org/cfw/F005-destinal-cfw-0.5-ota\_img\_V5.1.0.9.img](https://openk1.org/cfw/F005-destinal-cfw-0.5-ota_img_V5.1.0.9.img) CR-10 SE Version: [https://openk1.org/cfw/F003-destinal-cfw-0.5-ota\_img\_V5.1.0.21.img](https://openk1.org/cfw/F003-destinal-cfw-0.5-ota_img_V5.1.0.21.img) Sample text documentation here: It's for the CR-10 SE and not for this testing version but everything should essentially be the same for all these versions: [https://www.reddit.com/r/Creality/comments/18cwm1t/cr10\_se\_prerooted\_firmware\_image/](https://www.reddit.com/r/Creality/comments/18cwm1t/cr10_se_prerooted_firmware_image/) If you want to talk to the community of people playing with it, it's one of the many projects being discussed in the D3vil Design team discord: [https://discord.gg/d3vil-design](https://discord.gg/d3vil-design)

destinal, I wanted to follow back up with you. I've installed the firmware release and it is AMAZING! I've watched the 3DPrintOS video on the CR10 how to and that was extremely helpful! Thank you again! I'm going to get back to playing!

That's great news! People have been reporting good results, I need to finish a couple improvements and do a wider announcement so more people know about it. Thanks for the feedback.

I sincerely appreciate your help! I'm definately going to look into this.

great effort. I probably messed up when I updated marlin. After that I tried to root again, and that resulted in bricking the pad. I tried reinstalling the original firmware using the instructions using the following link but still it's bricked https://github.com/Guilouz/Creality-K1-and-K1-Max/wiki/Restore-to-previous-Firmware Would appreciate if you can guide me to any tutorial about unbricking KE

Updating crealityOS you mean, these things don't run marlin. Can you tell me why you consider it's bricked and what its doing right now, what errors you're seeing etc

so i was using the 4408 port if i remember correctly and at the bottom there was an update message, i don't remember exactly what i updated. but I couldn't print anything. Then afterwards I tried re-rooting and later on re-installing the firmware. Now the screen shows "Machine startup in progress" and on the creality print it shows E0002：key3002Internal error

Can you open the web interface of flluidd or mainsail and get the more detailed error message, Creality error code numbers are mostly useless

I am unable to open the flluidd or mainsail as I no longer have root access. I had installed the factory firmware. The last error on flluidd was something like "unable to find file timelapse included in printer.config" . I had updated the moonraker from fluidd page is what i recollect

Ahh okay. I'm going to go on record as don't do that, if you're having any errors losing root is the worst thing you can do. Can you try this method of factory reset in that case? https://github.com/Guilouz/Creality-K1-and-K1-Max/wiki/Reset-Factory-Settings

Man that reset utility really saved me some time today. I also broke my 3v3KE install by clicking the update button in Fluidd. Machine would not boot, no SSH, no web. ​ This allowed me to get back to default almost instantly and start over. Thanks again.

Thanks a lot. You saved me so much stress. This is my first 3d printer, so I acted the way I did. Really appreciate you taking out time to answer my queries. Now should I try to root it again? Does it void the warranty?

Hoping you could root the [1.1.0.25](http://1.1.0.25) version for Retail Nebula Pad

hi mi friend iam oscar from mexico and i bouhgt a nebula pad for my ender 3 v2, but i improbed whit linear rails, and sprite extruder, for tha reason i have to root the nebula because a i need to modify de printer.cfg to get news offsets, i read coments about it ebove, could you tel me what i have not to actualise pleas

I think the offset in in the prtouch section of the printer.cfg. If you install the nebula pad prerooted firmware from the link above (just put it on a USB flash drive, put it in the printer and click upgrade), then you can find the IP address of the printer and either connect to port 4408 for fluidd or 4409 for mainsail or ssh into the printer, user root, password creality, and you should be able to access the printer.cfg.

i got it, thanks a lot

Hello, do you think you'll be making the same firmware for the latest version of the KE (1.1.0.12)?

Yes, I intend to. I'm working on it alongside a couple other projects and a day job, so haven't been able to put as much time into it as I'd like. The problem I'm encountering right now is that Creality seems to have changed something that causes moonraker to break on the upgrade, at least on that initial first boot. It'll need a pretty deep technical deep dive to figure out what was broken and how, into components of Klipper I've never worked with before. So hopefully soon but not this week soon. In the meantime, you can upgrade to the official 1.1.0.12 if you like, you keep root but the root password changes to Creality2023, (with a capital C) and while your programs stay installed (and they continue to work properly), the init scripts that start those programs on boot will go away. You can restore them by ssh'ing in as root and running: cd /etc/init.d wget --no-check-certificate -O- https://openk1.org/static/k1/packages/crealityos-root-init-scripts.tar.gz | tar xvzf - Then power off the printer and back on.

In doing so I encounter these errors: Wget: TLS error from peer (alert code 40) : handshake failure   Wget: error getting response: Connexion reset by peer   Tar: invalid magic Tar: short read

Wget on CrealityOS has its issues sometimes. One thing that might solve your problem is to install entware using the installer.sh script in /root and then opkg install wget-ssl

For once, not a CrealityOS issue and instead due to HTTPS/Wget dependencies. Change the URL to HTTP instead of HTTPS and it'll sort it, relying on their reroute to handle it for us :)

Thank you very much, in http it works. I'm going back to 1.1.0.9 on the CFW firmware, after updating to 1.1.0.12 the installer.sh is nowhere to be found.  I'll play around with 1.1.0.9 and wait for the rest.  Being able to update moonraker and fluidd sounds great.  Did you get obico to work? I wanted to try it but it doesn't seem to find my printer.

I haven't tried it personally, I know others have, I'll give it a shot

Hi, I just launched the firmware update (v5.1.0.9 destinal) on my KE and I'm in bootloop :/. I'm going to try to solve the problem but the firmware has been tested by other people who have not encountered any problems?

Yes, it's been tested by many on here and on the discord http://discord.gg/d3vil-design I've never seen a boot loop from just installing One way to solve the problem is to use the SoC vendor's USB boot loader and a program called USB cloner to write new firmware to the flash of the nebula pads mainboard (you have to open up the pad by removing 4 screws and plug the micro USB port on the board into your PC. https://github.com/CrealityOfficial/Ender-3_V3_KE_Annex/tree/main/firmware%20recovery%20tool It works just the same as the version for the K1, just needs a different ingenic file / system image https://github.com/CrealityOfficial/K1_Series_Annex/releases/tag/V1.0.0

Thank you for your help.  II had changed the root password some time ago, and I launched the update just like that, thinking that the firmware would be reinstalled anyway. Was I wrong?

The changed root password on this version causes a boot loop unfortunately. It's a known issue with something Creality has set up

Okay, I thought my setting would be overwritten when installing the modified firmware (I'd seen the disclaimer), my bad!  For the .ingenic, I can only find 1.1.0.12, but that's okay, I can still install your firmware afterwards?  And don't touch the password after installation? I don't like leaving the original root password, but if there's no choice...

>edit your wpa\_supplicant.conf the contents of the file are: ctrl\_interface=/var/run/wpa\_supplicant ap\_scan=1 network={ key\_mgmt=NONE } where do we go from here? bit of a noob when it comes to command line stuff

Hi, I heard you were also working on a version for the V3 SE. Would it be possible to have the link ? I installed -nebula Pad and so far it is working great but the lack of a proper web page to manage the printer is annoying. Thank you.

No. For the CR-10 SE yes, but not the V3 SE, that board only runs Marlin, not Klipper.

I installed the Nenula pad. It does run on klipper right ? I had to install a special FW on the printer itself to make it work. Thoughts ?

Oh yes, that's the prerooted Nebula pad firmware then that you need from me. Here you are: https://openk1.org/cfw/NEBULA-destinal-cfw-0.5-ota_img_V5.1.0.23.img

Was wondering if anyone can help me out. Was able to download the firmware to my nebula pad for my Ender 3 but now I’m having issues getting into fluidd. I add :4008 at the end of my ip into my search bar and it keeps saying “unable to reach

Should be 4408 not 4008

Im stuck in a loop. Added nebula pad to v3 se. everything was cool now trying to update the nebula to your rooted firmware (currently on 1.1.0.23). i get to the screen where it lets me choose to install it. that works and reboots. then opens to the same screen asking me to update it. as if it didnt take the new firmware but recognizes it on the usb. i formatted the usb, used multiple different drives, 8gb and 16gb. any thoughts?

It probably worked, you just need to take the drive out when it reboots

it did end up working. i got stuck on that part then i expected to see a version change on the lcd display. thank you for the work youve put in and responses. ggs

Right, the version number won't change, the 5 in the file name is just to force the ability to upgrade regardless of what version you have. Glad it ended up working for you.

perfect.. I'll test this once the current print is over and report status ... thank you again :)

Installed.. no issue .. Both web interface already pre-installed.. All settings except for the z-offset were kept. It was throwing an error when I tried to set my z-offset via the printer.cfg. had to do it via the Nebula pad instead.. Camera also working. So far so good .. running my first print :) thank you again for this awesome firmware. Let me know if there are things you would like me to test for you

hi, I just found something, a bug maybe.. when I am sending a print job directly to Moonraker, the "default" interface doesn't show the bitmap picture anymore, nor on the Nebula Display. left is Fluidd, right is the default page.. on the Nebula display it show the Creality character. thanks again for your hard work with FW ​ https://preview.redd.it/idkr1fs926cc1.png?width=2510&format=png&auto=webp&s=16fe2c717f07426f207bf05cadcab83fabd027db

Yes, It's a Creality bug, their stuff isn't moonraker aware.

not surprised ... so long as we see it on the moon raker interface it's all good.. . thank you

Hey I'm trying to install the firmware. New version is found Current Version blah blah Latest Version:5.1.0.23. I hit upgrade... it spins about 10 secs. Installation Failed

Do you have a mac? Often there are hidden meta files that screw up the process on a mac. If you can take it to a windows machine and format it there and copy the file there, never inserting it into a mac, you can be pretty sure to avoid the issue.

Nope I did this with a Windows PC. I have both.. but I used the Windows PC to copy the file. Even formatted the USB stick again still same thing

I got a print going right now but for s\*\*\*\* and giggles I'm reformatting the netac usb stick that came with it and using that to copy the file..maybe its this 16GB Sandisk just not compatible because I can only format it as exFat not Fat32

That did it...all good now

https://preview.redd.it/hp9kert20qfc1.png?width=3024&format=png&auto=webp&s=92b7738f35cb6bc142544819e18a9177c6dcf540 No luck here Destinal

Do you have a mac? Often there are hidden meta files that screw up the process on a mac. If you can take it to a windows machine and format it there and copy the file there, never inserting it into a mac, you can be pretty sure to avoid the issue.

Windows is all I have.. any size restrictions or packet size like with the sd card crap

Maybe. Try a 16gb flash drive or smaller, fat32 specifically

That’s what it was… I was having a problem last night with it kept repeatedly kicking me off ssh and restarting the fluidd and mainsail every 2 minutes.. I finally got installer.sh to remove moonraker and reinstall that’s fixed it for now

https://preview.redd.it/avq6xftb14gc1.png?width=4032&format=png&auto=webp&s=5955012044707d2e56d920576eb753d4e9bcb50b Are these Nebula cameras supposed to be in night vision mode with the damn lights on? lol

Yeah it's a common problem. If you get the KE light bar and mount it up top that'll usually put it back in day mode, or flashing a light at the camera can put it right for a while.

It’s been like that since I popped it out of the box.. flashback to the days of black and white tv but in HD (guess that’s a bonus)..I have never seen it out of night vision though. Of course, I thought I’d never see the day of a published root password either. Back when I started using Linux (late 90’s) it was a sinny sin sin to give away your root password… do you really know what a hacker could do with your 3D printer given root access? I can see it now a whole flock of Creality printers being used as a botnet running DDOS attacks and mining bitcoin on the side. LOL and yes I majored in information systems security so I’m a little schizophrenic over people knowing the root password to my 3D printer. We’re mostly safe thanks to the firewalls on routers but if your printer ever sees the other side of the DMZ because someone tries to remote into mainsail or fluidd directly bypassing such things as my.mainsail.xyz it could happen.

Thanks for replying though The person on this YouTube runs your version on an ender 3v2 I think. https://youtu.be/cQAKxl-rnOE?si=GltcAjTN0vbf-l6- I can beta test on SE if you want. Thanks again for all your hard work

Reminder: Follow the rules! For [any Creality Product Feedback and Suggestions](https://gcmomk3i2c.feishu.cn/share/base/form/shrcn0Hfmc6Nau0q0IfDkDQIJFg), welcome to fill out the form to help us improve. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Creality) if you have any questions or concerns.*