Arco Unleashed v1.1.4 (Bookworm 6.18.30)
Latest build — 2026-08-25 (v1.1.4). Five things an owner will notice.
(1) The console is readable again. Phrozen's firmware narrates itself constantly — the serial link
being re-initialised before every send, each 16-byte AMS frame printed byte by byte, the firmware version
one field per line. All of it scrolled the welcome banner away within seconds of a print starting. Of 357
console lines from a real print, six now show, and those six are the banner and actual commands. A jam
report and a missing AMS still come through: the patterns are built around keeping them.
(2) One dialog for the AMS. Which slot each tool pulls from, and the refeed switch, in a single
place — AMS_SETUP in the Macros panel. Picking the same slot for two tools is allowed: that is how
you print a four-colour file from two loaded spools. And the old AMS on / off switch is gone — the
unit enumerates as a USB device and the printer follows it by itself, so there is no longer a setting
that can disagree with the hardware.
(3) The printer shows what is plugged in. AMS and USB Stick each get a line under
Miscellaneous, green when connected and red when not. They are indicators, not buttons — clicking
one does nothing, on purpose. Fluidd shows the same two in its Runout sensors card.
Fluidd ships that card switched off, so a fresh printer now switches it on by itself; on a
dashboard you have already arranged it is left alone, and the setup menu still offers it
(w → s).
(4) A print that starts with nothing loaded is stopped. The toolhead filament sensor is visible to
the web interface for the first time, and a job that begins with an empty toolhead is paused instead
of laying down air for hours. A print running without runout protection now says so in the console rather
than staying quiet about it — and it waits until printing has actually begun, so it no longer speaks up
while the bed mesh is still probing and the start G-code has not set the mode yet.
(5) An update from the web interface now finishes the job. Installing an update from Mainsail
or Fluidd is a plain git pull, so anything that needed root — a service, a boot hook, the theme —
was left unapplied without a word. On a printer flashed from an older image that could stay true
indefinitely: every file present, nothing switched on, and no message saying so. An update now
arms the remaining work and applies it at the next start, by itself.
Arco Unleashed — Full Image (pre-built, flash & run)
A complete Debian Bookworm + Klipper image for the Phrozen Arco. Includes the Klipper stack,
the arco-unleashed kit (setup menu, AMS auto-mode, Mainsail theme) and the Arco configuration.
No proprietary Phrozen software is included — you supply Phrozen's official Arco_FW_V*.zip on a
USB stick at first boot.
📦 What to download
| Asset | You need it for |
|---|---|
Arco-Unleashed-USB.zip |
everything — the image, its checksums, the self-flash tool and all guides. Extract it to the top level of a FAT32 USB stick. |
collect_data_arco.sh |
Step 0 below — grab it on its own so you can run it before downloading the big archive. |
Arco-Reflash-to-Buster-USB.zip |
only if you ever want to go back to stock Phrozen Buster. |
The image is no longer offered as a separate download — it lives inside Arco-Unleashed-USB.zip
together with its .sha256 and .rawsize, so there is one thing to fetch and nothing to mismatch.
Before you flash — collect data from your running printer (required)
Some data the Arco needs is not in Phrozen's Arco_FW_V*.zip (phrozen_master + ~/hdlDat) —
without it the AMS detection hangs and the display misbehaves. Grab it from your still-running
original printer: download collect_data_arco.sh from this release, put it on a FAT32 USB
stick, plug that into your original Arco, SSH in, then:
bash ~/printer_data/gcodes/USB/collect_data_arco.sh ~/printer_data/gcodes/USB(If the stick auto-mounts elsewhere, run lsblk and use that path.) This writes
arco-phrozen-ams.tar.gz onto the stick — keep it there for the install below.
Two ways to flash
Path A — easy direct flash (self-flash, no teardown). The running printer overwrites its own eMMC.
Proven end-to-end on hardware, but one shot, no net.
- Extract
Arco-Unleashed-USB.ziponto the root of a FAT32 stick. Add Phrozen's official
Arco_FW_V*.zipand your collectedarco-phrozen-ams.tar.gznext to it. - Plug it into the printer, SSH in as
mks. The stick auto-mounts at~/printer_data/gcodes/USB(stock
printer and Unleashed). If that folder is empty, mount it to that same path yourself —
sudo mkdir -p /home/mks/printer_data/gcodes/USB && sudo mount /dev/sda1 /home/mks/printer_data/gcodes/USB
(lsblkshows the partition). Then:cd ~/printer_data/gcodes/USB # where the stick auto-mounts sh prepare_unleashed_self_flash.sh # unpacks the tool to ~/selfflash sudo bash ~/selfflash/install-unleashed.sh # inspect only — changes nothing sudo bash ~/selfflash/install-unleashed.sh --arm # verify, confirm, arm, reboot
- Leave the stick plugged in. The display shows three named steps (check → write → verify), the
printer reboots itself, seeds its WiFi from the stick and installs Phrozen's parts from it.
If something goes wrong before the write begins — image missing, checksum mismatch, or the flasher
hangs — pull the USB stick and power-cycle. With no image on the stick the flasher stands down and
your existing system boots normally. Once the write has begun, only path B recovers the printer.
Path B — eMMC replacement / recovery. The proven route, and how you recover from a failed path A.
- Extract
Arco-Unleashed_bookworm_6.18.30.img.gzout ofArco-Unleashed-USB.zip— that file is
what balenaEtcher writes. - eMMC out → USB adapter → flash it with balenaEtcher → eMMC back in.
- Put Phrozen's official
Arco_FW_V*.zipand the collectedarco-phrozen-ams.tar.gzon a
FAT32 USB stick. First boot: Wi-Fi portal → the display then installs Phrozen's parts from it.
If the printer never comes online after the flash
Wait ~90 seconds first — that is how long it tries the seeded Wi-Fi before raising its own
Arco-Unleashed-Setup hotspot for your phone. If neither appears, put a wifi-seed.txt on the
stick with three lines (SSID=, PSK=, COUNTRY=) and power-cycle: the first boot re-runs on every
power-cycle until Phrozen's firmware is installed, so it picks the file up and joins your network. Full
details in the QUICKSTART inside the archive — worth knowing, because a printer in that state has no
network, so the guides on the stick are the only ones you can open.
Afterwards (either path): SSH in as mks, set your own password, flash the MCUs and re-calibrate.
Only the toolhead F103 needs a hands-on button step, and only once — the MANUAL explains why.
See the README / QUICKSTART for the full procedure.