ZWA-2 stuck in bootloader after update from v1.0 to v1.1.0 in Home Assistant

Issue in Home Assistant on linux doing the update from v1.0 to v1.1.0 of the ZWA-2

I wondering if there is a step by step on how to finish/repair my ZWA-2 that is in bootloader mode?

6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/config.sh
[15:36:17] INFO: Both 'network_key' and 's0_legacy_key' are set and match. All ok.
[15:36:17] INFO: RF region set to Automatic: USA
[15:36:17] INFO: Setting RF region to (USA)
[15:36:17] INFO: Soft-reset set to automatic
[15:36:17] INFO: Virtual Machine detected, disabling soft-reset
cont-init: info: /etc/cont-init.d/config.sh exited 0
cont-init: info: running /etc/cont-init.d/structure.sh
cont-init: info: /etc/cont-init.d/structure.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun zwave_js (no readiness notification)
s6-rc: info: service legacy-services successfully started
[15:36:17] INFO: Successfully send discovery information to Home Assistant.
2025-08-30 15:36:18.350 DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                 ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                   ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                  ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                 ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                 ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2025-08-30 15:36:18.352 DRIVER   version 15.12.0
2025-08-30 15:36:18.352 DRIVER   
2025-08-30 15:36:19.611 DRIVER   Controller is in bootloader, attempting to recover...
2025-08-30 15:36:20.615 DRIVER   Failed to recover from bootloader. Please flash a new firmware to continue...
Error in driver ZWaveError: Failed to recover from bootloader. Please flash a new firmware to continue... (ZW0100)
    at Driver.destroyWithMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:3775:17)
    at Immediate.<anonymous> (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1662:18) {
  code: 100,
  context: undefined,
  transactionSource: undefined
}
Shutting down
[19:36:20] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Thanks for your help

Below is firmware to reflash

Did you get nvm backup
Before you tried update?

Hi tmjpugh,

No backup, it’s my first Z-Wave integration :sweat_smile:
Thanks to point the location of the firmware, but I need the command line to complete the upgrade.

I hope someone will have a solution.

Same problem
I think they had flash method

I guess in zwavejsui there is advanced action that will allow you to flash bootloader

Install this add-on.