Firmware Rebuild fails

[SteffenAuer]

I followed the instructions in the recent 7.0 Progress Report for updating the firmware image after installation. So:

1. Ensured I was on 6.19. Output of uname:

   Linux smba14 6.19.13-400.asahi.fc43.aarch64+16k #1 SMP PREEMPT_DYNAMIC Mon Apr 20 15:18:52 UTC 2026 aarch64 GNU/Linux
   

2. Reboot into recoveryOS, launch terminal
3. Run curl https://alx.sh | bash and select v
4. Immediately after, the script fails with an exception. I've attached the full installer.log below.

    04-30 15:37 root         ERROR    Exception caught
    Traceback (most recent call last):
      File "/System/Volumes/Data/private/tmp/asahi-install/main.py", line 1149, in <module>
        InstallerMain(installer_version).main()
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
      File "/System/Volumes/Data/private/tmp/asahi-install/main.py", line 946, in main
        while self.main_loop():
              ~~~~~~~~~~~~~~^^
      File "/System/Volumes/Data/private/tmp/asahi-install/main.py", line 1124, in main_loop
        return self.action_rebuild_vendorfw(oses_vendorfw)
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
      File "/System/Volumes/Data/private/tmp/asahi-install/main.py", line 467, in action_rebuild_vendorfw
        k, v = var.split('=')
        ^^^^
    ValueError: not enough values to unpack (expected 2, got 1)
   

installer.log

[SteffenAuer]

A colleague updated his firmware blob using the same mechanism without issues. I realized it could be because my root partition is LUKS encrypted? 🤔 Are there steps I should execute to unlock the partition (btrfs subvol) before the installer runs and point it somehow to the mapper dev or can this be handled in the installer itself? Or is it impossible to work with an encrypted root partition for the purpose of the firmware rebuild?
Clarification on this would be appreciated 🙏