⚠️ Important: Dasharo v1.0.0 Update Temporarily Disabled for NovaCustom V540TU & V560TU

[BeataZdunczyk]

We have received two reports from users who experienced a brick when updating firmware from v0.9.0 to v1.0.0: https://novacustom.com/forum/d/422-error-updating-firmware/25.

We are collecting details and tracking progress in this issue: #1613.

As a precaution, the update to v1.0.0 has been temporarily disabled until we identify the root cause of the issue. We take this very seriously and are committed to ensuring the safety of all firmware updates.

So far, we have not been able to reproduce the problem, but we are continuing to test additional scenarios. If you have experienced any issues with the firmware update, please contact us via Matrix or leave a comment in the GH issue.

In the meantime, we are implementing safeguards in DTS that will abort a firmware update if any warnings appear. This will help prevent users from applying an update when something is wrong and reduce the risk of bricking.

We are actively investigating this issue and will provide updates as soon as the update to v1.0.0 is safe to restore.

We apologize for the inconvenience and appreciate your patience.
— The Dasharo Team

[BeataZdunczyk]

Update on v1.0.0 Firmware for MTL iGPU Laptops

✅ Root cause fixed (Automatic FUM update starts on every TTY) → Only one update workflow can run at a time
✅ Updates safely restored
🔒 New safeguards against failed BIOS config migration, FMAP warnings, and end-of-flash failures
🛠️ Improved log sending instructions
📦 Dasharo Tools Suite v2.7.1 released with these fixes → Release notes

We are happy to share that the issue reported with firmware updates from v0.9.0 to v1.0.0 on Dasharo firmware for MTL iGPU laptops has been identified and fixed. The update has now been safely restored.

Root cause

The main issue was tracked down to #1603. Updates were automatically triggered on all TTYs when DTS was booted via FUM, which could result in multiple update processes running in parallel. Since users only saw one process, they could unknowingly interrupt another one still in progress, leading to a potential brick.

Fix

To prevent this, DTS now ensures that only one update workflow is active. When DTS is launched, users are asked to choose:

This ensures visibility and prevents multiple parallel updates.

Additional safeguards

Several new safety measures and usability improvements have also been added:

• Failed BIOS configuration migration → users are asked whether they want to continue (continuing resets all BIOS settings to defaults).
• FMAP warnings (caused by flashrom not being able to read firmware from flash) → update is stopped automatically instead of continuing.
• Flash write failures at the end of the process → clear message instructs users not to reboot at this stage, since rebooting could cause a brick depending on what was written.
• Improved log sending messages and path visibility → clearer messages when sending logs, plus a visible path to the archive containing all logs sent to 3mdeb, allowing users to copy or view them manually.

Tools update

👉 All fixes are included in the latest Dasharo Tools Suite v2.7.1: Release notes

We sincerely thank the community for reporting these issues and for your patience while we worked on the fix. Firmware updates are now safe, with additional safeguards to prevent bricks and improve user control.

— The Dasharo Team