Developer Install From Stock

First install from stock

Developer / advanced testing documentation. Full detail: docs/DEVELOPER_INSTALL_FROM_STOCK.md — this page is a summary.

These procedures expose raw firmware images, partitions, A/B boot slots, and SSH/root access. Not a supported consumer installer.

Prerequisite (out of scope for this project): root/SSH access on a stock printer. Every user of this project already has a standing method to obtain this on stock Creality firmware — NebulaOS does not document how to acquire it, matching the convention of sibling Creality K1/KE mod projects.

Evidence gap, stated plainly: no run in this project's own qualification archive begins from a printer whose custom slot (mmcblk0p6/p8) has literally never been written before. The documented sequence below is expected to work unchanged on a genuinely virgin slot 2, but that specific end-to-end case has not been verified. NOT_PROVEN.

Sequence:

1. Build (./build.sh) or obtain artifacts — see Build From Source.
2. scp the artifacts to the printer, staged under /usr/data (not /tmp — tmpfs, can run out of space).
3. sha256sum the transferred files against build-manifest.txt.
4. scripts/flash-spare-slot.sh --check-only — validates slot mapping, active slot, target slot, live-target collision, image sizes, and manifest hashes before touching anything.
5. Run the real flash. It always targets slot 2 only and refuses if target == active slot.
6. Flip the OTA marker forward from stock's own tool: sh -c '. /etc/ota_bin/ota_local_method.sh; local_set_next_boot_device'
7. Reboot. Watch S00revert-safety → S04/S5x service bring-up → S99confirm-good.

See A/B Slot Model for exactly what each of those init stages does and why.