> For the complete documentation index, see [llms.txt](https://guide.cronuszen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.cronuszen.com/frequently-asked-questions/troubleshooting.md).

# Troubleshooting

Find your symptom below and open it. If a fix points to a procedure, that procedure is at the bottom of this page.

### <i class="fa-triangle-exclamation">:triangle-exclamation:</i> Symptoms <a href="#symptoms" id="symptoms"></a>

<details>

<summary><strong>Firmware Version Incompatible</strong></summary>

This message appears when your Cronus Zen™ firmware or your Zen Studio version is outdated.

**Fix**

1. Update the firmware — see Update Firmware
2. Update Zen Studio
3. Reconnect the Zen and restart Zen Studio

</details>

<details>

<summary><strong>Error E3, E3001, or E3002</strong></summary>

These codes mean the firmware is corrupted or missing. They typically occur when:

* firmware installation was interrupted
* the device lost power during an update
* firmware files became corrupted

**Fix:** Bootloader recovery

</details>

<details>

<summary><strong>Stack or Bytecode error</strong></summary>

Indicates corrupted memory, an invalid script, or a failed programming process. Typically caused by:

* interrupting programming
* power loss during flashing
* a corrupted GamePack or script

**Fix:** Hard reset, then reinstall your scripts.

{% hint style="info" %}
If the error comes back immediately after installing one particular script, that script is corrupted or incompatible.
{% endhint %}

</details>

<details>

<summary><strong>Freezing or abnormal behaviour</strong></summary>

If the Zen freezes, behaves abnormally, or shows error codes, a hard reset restores it to factory condition.

**Fix:** Hard reset

</details>

***

### <i class="fa-screwdriver-wrench">:screwdriver-wrench:</i> Procedures <a href="#procedures" id="procedures"></a>

<details>

<summary><strong>Bootloader recovery</strong></summary>

**Enter Bootloader Mode**

{% stepper %}
{% step %}

#### Find the reset button

The **blue reset button** is underneath the Cronus Zen™.
{% endstep %}

{% step %}

#### Hold it and connect

Press and hold the reset button firmly. While holding, connect the Zen to your PC using the **CONSOLE/PC USB** port.
{% endstep %}

{% step %}

#### Confirm recovery mode

The screen shows **Zen Bootloader**.
{% endstep %}
{% endstepper %}

**Reinstall the firmware**

Open [firmware.modcentral.ca](https://firmware.modcentral.ca/) in Google Chrome or Microsoft Edge, and follow the on-screen instructions.

{% hint style="warning" %}
If the update fails, the cause is usually insufficient USB power. Connect the **PROG USB** port on the right side of the Zen as well, then retry with both ports connected.
{% endhint %}

</details>

<details>

<summary><strong>Hard reset</strong></summary>

{% hint style="danger" %}
A hard reset erases every script stored on the Zen.
{% endhint %}

**Step 1 — Hardware reset**

{% stepper %}
{% step %}

#### Disconnect everything

Remove all cables from the Zen so it has no power.
{% endstep %}

{% step %}

#### Hold P1 + P2

Press and hold both large blue buttons beside the OLED.
{% endstep %}

{% step %}

#### Connect while holding

Connect the Zen using the **CONSOLE/PC USB** port and keep holding for at least 4 seconds.

The RGB LEDs flash **red → green → blue**.
{% endstep %}

{% step %}

#### Release

Let go once the logo appears on the OLED screen.
{% endstep %}
{% endstepper %}

**Step 2 — Factory reset in Zen Studio**

{% stepper %}
{% step %}

#### Connect via PROG USB

Connect the Zen to your PC using the **PROG USB** port.
{% endstep %}

{% step %}

#### Run the factory reset

Open **Zen Studio → Device** tab and click **Factory Reset** in the bottom-right. Confirm — the Zen reboots to its default state.
{% endstep %}
{% endstepper %}

**Step 3 — After the reset**

The Zen is now empty. Reinstall the latest firmware, then reinstall your scripts.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guide.cronuszen.com/frequently-asked-questions/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.