UEFI Firmware Update failing

I have had a firmware update problem. It keeps failing to update and a IEFI module shows as an error. Ive tried to removing all USB-C devices, unplugging it, making sure the power is drained and retrying it. The update reboots to the logi and update bar and after a few minutes a blie box pops up saying formware update failed.

dmaynor@project-2501:/$ fwupdmgr get-history

NVIDIA NVIDIA_DGX_Spark

├─Embedded Controller:

│ │ Device ID: 8c948e1db381648c8893897e4d09b7b153309991

│ │ Previous version: 0x02004b03

│ │ Update State: Success

│ │ Last modified: 2026-03-01 17:45

│ │ GUID: 3d13c989-e6a8-4ead-95ee-921f09868f65

│ │ Device Flags: • Internal device

│ │ • Updatable

│ │ • System requires external power source

│ │ • Supported on remote server

│ │ • Needs a reboot after installation

│ │ • Reported to remote server

│ │ • Device is usable for the duration of the update

│ │ • Signed Payload

│ │

│ └─DGX Spark EC FW Embedded Controller Update:

│ New version: 0x02004e12

│ Remote ID: lvfs

│ Release ID: 135056

│ Summary: DGX Spark Embedded Controller Firmware Update

│ License: Proprietary

│ Size: 519.3 kB

│ Created: 2026-01-13

│ Urgency: High

│ Vendor: NVIDIA

│ Duration: 30 seconds

│ Release Flags: • Trusted metadata

│ Description:

│ This update improves the performance and stability of the Embedded Controller in DGX Spark

│ Checksum: 55f0d41a5a93b39bb6a0afa3765b6b746ddcc667f4e9047972f02f2d57cc1073

├─UEFI Device Firmware:

│ │ Device ID: 0681fd3882fb4fdca996e412ec249365f6e85838

│ │ Previous version: 0x02009418

│ │ Update State: Success

│ │ Last modified: 2026-03-30 02:06

│ │ GUID: b488217b-3895-4fc0-b1bf-ab7005a2d45a

│ │ Device Flags: • Internal device

│ │ • Updatable

│ │ • System requires external power source

│ │ • Supported on remote server

│ │ • Needs a reboot after installation

│ │ • Device is usable for the duration of the update

│ │ • Signed Payload

│ │

│ └─DGX Spark SoC FW System Update:

│ New version: 0x0200941a

│ Remote ID: lvfs

│ Release ID: 136978

│ Summary: DGX Spark SoC Firmware Update

│ License: Proprietary

│ Size: 30.4 MB

│ Created: 2026-02-24

│ Urgency: High

│ Tested by NVIDIA:

│ Tested: 2026-03-02

│ Distribution: ubuntu 24.04

│ Old version: 0x02009009

│ Version[fwupd]: 1.9.33

│ Vendor: NVIDIA

│ Duration: 30 seconds

│ Release Flags: • Trusted metadata

│ • Tested by trusted vendor

│ Description:

│ This update improves the performance and stability of the System-on-Chip Firmware including UEFI and GPU in DGX Spark

│ Checksum: d4b05b4b9455d4c139361ce3ff521b2cad53e7de90d9637f2f76419231081a2b

└─UEFI Device Firmware:

│ Device ID: a6c6b7f79c96a1cc84d9612d804675e0c3d879c4

│ Previous version: 0x00000001

│ Update State: Failed

│ Update Error: failed to update to 0: error-unsuccessful

│ Last modified: 2026-03-30 03:01

│ GUID: dd1a238a-5f8e-46bd-9401-a88da99c5a96

│ Device Flags: • Internal device

│ • Updatable

│ • System requires external power source

│ • Supported on remote server

│ • Needs a reboot after installation

│ • Device is usable for the duration of the update

│ • Signed Payload

└─DGX Spark USB-C PD FW Controller Update:

    New version:      0x00000507

    Remote ID:        lvfs

    Release ID:       133185

    Summary:          DGX Spark USB-C Power Delivery Controller Firmware Update

    License:          Proprietary

    Size:             1.1 MB

    Created:          2025-12-04

    Urgency:          High

    Vendor:           NVIDIA

    Duration:         30 seconds

    Release Flags:    • Trusted metadata

                      • Is upgrade

    Description:      

    This update improves the performance and stability of the USB Power Delivery Controller in DGX Spark for USB-C Ports

    Checksum:         575ee2e586119a941c83659b6d73b47ffe761a64bb783668803a3625beceeb6f

dmaynor@project-2501:/$

Please run the Field Diagnostic and share the result bundle with me: NVIDIA DGX Spark Field Diagnostics | NVIDIA

Unpacking onediag…

Removing Nvidia drivers and services…

Stopping ‘docker.service’, but its triggering units are still active:

docker.socket

Stopping ‘systemd-udevd.service’, but its triggering units are still active:

systemd-udevd-control.socket, systemd-udevd-kernel.socket

Installing MODS driver…

Starting OneDiag…

******************************************************************

* *

* DGX FIELD DIAGNOSTIC *

* *

******************************************************************

Version r9.257.3

Python /opt/nvidia/dgx-spark-fieldiag/dgx/python/python-3.10.7-glibc-2.17-aarch64/bin/python3

Build Date Fri, 19 Dec 2025

Start time Mon, 30 Mar 2026 21:11:27

Est. Completion time Tue, 31 Mar 2026 00:13:57

Logs /opt/nvidia/dgx-spark-fieldiag/dgx/logs-20260330-211108

Inforom logs /opt/nvidia/dgx-spark-fieldiag/dgx/logs-20260330-211108/inforom

Product NVIDIA_DGX_Spark

Product Version A.7

Family DGX Spark

SKU 0000

Serial Number xxxxxxxxxxxxxxx

Testing GpuStress OK [ 3:19s ]

Testing C2CStress OK [ 0:06s ]

Testing CpuStress1 OK [ 0:08s ]

Testing CpuStress2 OK [ 10:00s ]

Testing PowerStress OK [ 8:11s ]

Testing ThermalStress OK [ 0:42s ]

Testing FioSSD OK [ 0:11s ]

Testing MemStress OK [ 7:07s ]

Exit Code | Virtual Id | Test | Subtest | Component | Component Id | Notes

===========================================================================================

MODS-000000000000 | GpuStress | custommods | | GPU | | OK

MODS-000000000000 | C2CStress | custommods | | C2C | | OK

MODS-000000000000 | CpuStress1 | custommods | | CPU | | OK

DGX-000000000000 | CpuStress2 | cpustress | | CPU | | OK

MODS-000000000000 | PowerStress | custommods | | Power | | OK

MODS-000000000000 | ThermalStress | custommods | | Thermal | | OK

DGX-000000000000 | FioSSD | custom | | SSD | | OK

DGX-000000000000 | MemStress | custom | | Memory | | OK

####### #### ###### ######

######## ###### ######## ########

## ## ## ## ## # ## #

## ## ## ## ### ###

######## ######## #### ####

####### ######## ### ###

## ## ## # ## # ##

## ## ## ######## ########

## ## ## ###### ######

Final Result: PASS

End time: Mon, 30 Mar 2026 21:41:15 [ 29:48s elapsed ]

Copying logs…

Thanks for trying that.

Can you also share with me your firmware versions?
Please tell me the output of fwupdmgr get-devices
as well as a screenshot of your BIOS reporting your device firmware.

I believe I had this exact issue on the spark I have at work. The issue is that the installed version cannot bridge to the current version attempting to be installed.
On my machine at home I didn’t encounter this because I had reformatted it from an updated OS image, so that’s the easiest more surefire solution.
I did manage to fix the one at work over SSH but I don’t remember the specifics. But I basically had to manually download a slightly less old firmware version (I believe 304) and update manually as a stepping stone.

dmaynor@project-2501:~$ fwupdmgr get-devices

NVIDIA NVIDIA_DGX_Spark

├─Embedded Controller:

│ Device ID: 8c948e1db381648c8893897e4d09b7b153309991

│ Summary: UEFI System Resource Table device (Updated via capsule-on-disk)

│ Current version: 0x02004e12

│ Minimum Version: 0x02003400

│ Vendor: NVIDIA (DMI:American Megatrends International, LLC.)

│ Update State: Success

│ GUID: 3d13c989-e6a8-4ead-95ee-921f09868f65

│ Device Flags: • Internal device

│ • Updatable

│ • System requires external power source

│ • Supported on remote server

│ • Needs a reboot after installation

│ • Device is usable for the duration of the update

│ • Signed Payload

│ Device Requests: • Message

├─MZALC4T0HBL1-00B07:

│ Device ID: 7de5ffdca08fa52d95fd4bb42aa5d07a4b35d2dd

│ Summary: NVM Express solid state drive

│ Current version: NXHB202Q

│ Vendor: Samsung (NVME:0x144D)

│ Serial Number: S8C2NG0YA18234

│ GUIDs: 35abf34a-7ed8-51b2-ba1b-edef527d47e6 ← NVME\VEN_144D&DEV_A810

│ 095ba8dd-3778-52b4-9f32-02a67c210ce5 ← NVME\VEN_144D&DEV_A810&SUBSYS_144DA801

│ 93768061-87bf-5c78-b9ea-5b7a6301012b ← SAMSUNG MZALC4T0HBL1-00B07

│ Device Flags: • Internal device

│ • Updatable

│ • System requires external power source

│ • Needs a reboot after installation

│ • Device is usable for the duration of the update

│ • Signed Payload

├─UEFI Device Firmware:

│ Device ID: 0681fd3882fb4fdca996e412ec249365f6e85838

│ Summary: UEFI System Resource Table device (Updated via capsule-on-disk)

│ Current version: 0x0200941a

│ Minimum Version: 0x02007300

│ Vendor: NVIDIA (DMI:American Megatrends International, LLC.)

│ Update State: Success

│ GUID: b488217b-3895-4fc0-b1bf-ab7005a2d45a

│ Device Flags: • Internal device

│ • Updatable

│ • System requires external power source

│ • Supported on remote server

│ • Needs a reboot after installation

│ • Device is usable for the duration of the update

│ • Signed Payload

│ Device Requests: • Message

├─UEFI Device Firmware:

│ Device ID: a6c6b7f79c96a1cc84d9612d804675e0c3d879c4

│ Summary: UEFI System Resource Table device (Updated via capsule-on-disk)

│ Current version: 0x00000001

│ Minimum Version: 0x00000400

│ Vendor: NVIDIA (DMI:American Megatrends International, LLC.)

│ Update State: Failed

│ Update Error: failed to update to 0: error-unsuccessful

│ GUID: dd1a238a-5f8e-46bd-9401-a88da99c5a96

│ Device Flags: • Internal device

│ • Updatable

│ • System requires external power source

│ • Supported on remote server

│ • Needs a reboot after installation

│ • Device is usable for the duration of the update

│ • Signed Payload

│ Device Requests: • Message

└─UEFI dbx:

  Device ID:          362301da643102b9f38477387e2193e57abaa590

  Summary:            UEFI revocation database

  Current version:    20230501

  Minimum Version:    20230501

  Vendor:             UEFI:Microsoft

  Install Duration:   1 second

  GUIDs:              10ec82f4-ff64-5362-9e5d-688febf5dbb0 ← UEFI\\CRT_3CD3F0309EDAE228767A976DD40D9F4AFFC4FBD5218F2E8CC3C9DD97E8AC6F9D&ARCH_AA64

                      67d35028-ca5b-5834-834a-f97380381082 ← UEFI\\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_AA64

  Device Flags:       • Internal device

                      • Updatable

                      • Needs a reboot after installation

                      • Device is usable for the duration of the update

                      • Only version upgrades are allowed

                      • Signed Payload

Thank you, it seems fwupdmgr is reporting a bad PD firmware version of 0x00000001. This may have happened to due to an initial failed or interrupted FW update.
We need the Type 45 table to know what is actually installed, can you provide the output of sudo dmidecode -t 45 | egrep -A4 "EC|PD|UEFI|FLASH"

dmaynor@spark-261f:~$ sudo dmidecode -t 45 | egrep -A4 “EC|PD|UEFI|FLASH”

[sudo] password for dmaynor:

Firmware Component Name: FLASH

Firmware Version: SBP:R:2.148.26

Firmware ID: Not Specified

Release Date: Not Specified

Manufacturer: Not Specified

--

Firmware Component Name: UEFI

Firmware Version: R:1.107.26

Firmware ID: Not Specified

Release Date: Not Specified

Manufacturer: Not Specified

--

Firmware Component Name: EC Firmware

Firmware Version: 2.78.24

Firmware ID: Not Specified

Release Date: Not Specified

Manufacturer: Not Specified

--

Firmware Component Name: PD Firmware

Firmware Version: PD0 FW1: 5.7, FW2: 5.7

Firmware ID: Not Specified

Release Date: Not Specified

Manufacturer: Not Specified

Lowest Supported Firmware Version: Not Specified

--

Firmware Component Name: PD Firmware

Firmware Version: PD1 FW1: 0.0, FW2: 0.0

Firmware ID: Not Specified

Release Date: Not Specified

Manufacturer: Not Specified

Lowest Supported Firmware Version: Not Specified

dmaynor@spark-261f:~$

Your PD banks are still showing invalid FW version 0.0 which is preventing the update.
Please contact consumer support to request an RMA.