DFUUtility

DFUUtility is a free, open-source native macOS utility for technicians who prepare, recover, restore, and inventory supported Apple devices. It provides a guided interface for Mac DFU, iPhone/iPad DFU, Apple firmware, and device identity workflows without requiring Git, Swift, Xcode, or direct use of Apple's command-line tools for normal operation.

Connect a device with a data-capable cable, choose the workflow, and follow the on-screen checks. DFUUtility keeps destructive actions explicit and shows the stage and progress reported by Apple Configurator while it works.

Community releases are ad-hoc signed. No paid Apple Developer account is required, but Community builds do not provide Developer ID publisher authentication or notarization.

Key capabilities

Mac

• Detect Normal, Recovery, and DFU targets and preserve the target ECID across transitions.
• Enter DFU using the bundled macvdmtool and standard macOS administrator authorization.
• Restore or Revive through Apple Configurator with real stage-local progress and operation logs.
• Verify the same target before reporting a successful DFU transition.

iPhone and iPad

• Discover mobile targets and retain product type and ECID metadata.
• Guide supported physical-button DFU sequences without sending device commands.
• Require same-ECID DFU enumeration before reporting success.
• Restore compatible validated IPSWs with destructive confirmation and live progress.
• Perform Recovery Restore on supported iPhone and iPad targets.

Firmware management

• Discover compatible Apple macOS, iOS, and iPadOS restore images.
• Resume downloads, validate integrity and archive structure, and reuse a platform-separated cache.
• Inspect storage, reveal files, resume partials, and confirm removal in Manage Downloads….
• Select a local IPSW without placing it under DFUUtility's cache management.
• Automatically assign an exact compatible validated cached IPSW to a newly discovered iPhone or iPad without selecting the device or starting an operation.

Technician workspace

• Work with multiple connected devices as independent sessions and run an explicitly selected Restore, Revive, or Restart batch sequentially.
• Capture read-only device identifiers, add an internal asset tag, generate an exact-serial QR code, and export CSV.
• Inspect Diagnostics and Host Readiness guidance for Apple Configurator, bundled tools, accessory authorization, and sanitized support reports.

Safety

• Explicit target selection when multiple devices are attached.
• Product compatibility and IPSW validation gates before Restore.
• Separate native destructive confirmation; Restore never begins from DFU detection alone.
• Demo and screenshot modes cannot invoke hardware operations.

Multiple devices

• Multiple connected devices are represented as independent sessions keyed by ECID where available, with UDID/serial used only to preserve non-destructive presentation state when ECID is unavailable.
• A device without ECID, UDID, or serial receives a new ephemeral session on rediscovery so another physical device cannot inherit its firmware or operation state; it remains unavailable for batch execution until an ECID is present.
• Use the checkboxes to build an explicit batch; Select All Restore-Ready selects only devices that currently satisfy Restore eligibility. Firmware remains assigned per device.
• Batch Restore, Revive, and Restart freeze the selected devices and firmware assignments, then run sequentially; every cfgutil command remains targeted to one ECID and destructive operations are never run in parallel.
• Firmware selection, validation, progress, reconnect verification, results, and logs remain per device. A failure is recorded and the next queued device continues; Stop After Current Device prevents new operations from starting without interrupting the active restore.
• Automatic Mac Enter DFU remains single-target because upstream macvdmtool dfu does not provide an unambiguous target selector.

Batch execution is intentionally sequential in this first implementation. Parallel destructive operations are not supported.

Screenshots

The gallery below uses the deterministic demo mode shipped with the project. All identities are fictional and the views show the same navigation and safety gates used by the app.

Restore & Revive	Device workspace

Firmware Library	Device Capture

Diagnostics / Host Readiness	Guided mobile DFU

Guided iPad DFU	Firmware chooser

Download progress	Manage Downloads

Restore progress	Completed Restore

About and licensing	Source-checkout update

All screenshots use deterministic fictional data; they contain no real device or user identifiers.

Requirements

• macOS 14 or newer.
• Apple Configurator from the Mac App Store for discovery, Restore, and Revive.
• A direct, data-capable USB connection. Charging-only cables and some hubs do not provide a usable restore transport.
• An Apple-silicon Mac host for automatic Mac DFU entry. Mac DFU port requirements are model-specific; follow Apple's guidance and the tested-hardware notes below.
• Administrator authorization only when entering a Mac into DFU. Mobile DFU uses physical button input.
• Internet access only when browsing or downloading firmware from Apple's catalogues.

DFUUtility does not claim universal Apple hardware support. Physical acceptance applies only to the products and workflows listed in HardwareAcceptance.json.

Installation

End-user installation

1. Open the latest DFUUtility GitHub Release.
2. Download the DFUUtility-<version>.zip asset.
3. Unzip it and move DFUUtility.app to /Applications.
4. Launch DFUUtility.

Community ZIPs are ad-hoc signed and are not notarized. macOS may show its standard confirmation for an app downloaded from the internet.

Quick Terminal install

To download, verify, and install the latest stable published release without piping a network response directly into a shell, paste this block into Terminal:

(
  workdir="$(mktemp -d)" &&
  trap 'rm -rf "$workdir"' EXIT &&
  curl --proto '=https' --tlsv1.2 -fsSL \
    https://raw.githubusercontent.com/thehallifax/DFUUtility/main/scripts/install-release.sh \
    -o "$workdir/install-release.sh" &&
  /bin/sh "$workdir/install-release.sh"
)

Quit DFUUtility before running the installer. It installs /Applications/DFUUtility.app without changing macOS security settings or requesting administrator privileges. If /Applications is not writable, it stops with instructions to use the GitHub Release ZIP instead. The manual ZIP steps above remain the simplest alternative.

This installer uses the published distribution artifact, not the current source branch. The installed app therefore uses DFUUtility → Check for Updates… for future releases.

Updating

For a packaged installation, choose DFUUtility → Check for Updates…. Updates are always explicit:

Check for Updates… → Download Update → Install Update

DFUUtility verifies the published release metadata, download size, SHA-256, archive structure, bundle identity/version/resources, and structural code signature before offering installation. The replacement is transactional and the app relaunches only after the installed destination has been verified. The production binary updater lifecycle was accepted for 0.10.9 → 0.10.10; Community artifacts remain ad-hoc signed and not notarized.

Developer/source installation

Developers can build a source installation from a persistent clean Git clone:

git clone https://github.com/thehallifax/DFUUtility.git
cd DFUUtility
scripts/install-local.sh

Open /Applications/DFUUtility.app. To uninstall the local build, run scripts/uninstall-local.sh.

The normal installer builds, packages, verifies, and installs the app with concise progress output. It does not run the repository test suite, so full Xcode is not required merely to install DFUUtility when the selected Command Line Tools can compile the release app. Contributors with a newer Swift/Xcode toolchain that includes Swift Testing can validate before installation explicitly:

scripts/install-local.sh --test

For complete build, packaging, and verification output, use verbose mode. The flags can be combined in either order:

scripts/install-local.sh --verbose
scripts/install-local.sh --test --verbose

Source-checkout updates

For a source installation, DFUUtility → Check for Updates… checks the original clean Git checkout. Update Now safely fast-forwards that checkout, rebuilds and verifies the app locally, installs it, and relaunches it. The original checkout must still exist, remain on main, and have no local changes.

Distribution bundles use GitHub Release metadata instead, even if an older source-install registration remains on the machine. Installation provenance keeps these workflows separate.

The installer records the canonical source location in the user's DFUUtility application-support folder; no developer path is embedded in the app. Update progress and failures are recorded in ~/Library/Logs/DFUUtility/update.log. A failed build or verification leaves the existing installed app available.

If updates report Source checkout unavailable, the original clone may have moved, been deleted, or been replaced with an extracted source archive. Follow the Installation instructions above using a persistent Git clone, then reinstall from that clone. View Update Log retains the technical reason. DFUUtility does not repair or overwrite a checkout automatically.

Manual updating remains available as a fallback:

cd /path/to/DFUUtility
scripts/update.sh

The updater checks GitHub for newer source, refuses to overwrite local changes, and fast-forwards the main branch without creating a merge commit. When an update is available, it reuses the existing installer to build, verify, and replace /Applications/DFUUtility.app; the installer moves the previous application to Trash.

scripts/update.sh --check    # Check without pulling, building, or installing
scripts/update.sh --verbose  # Show complete installer output
scripts/update.sh --test     # Run the repository tests before installation

The flags may be combined. In-app and shell updates are intended for clean end-user clones. Contributors with local changes or feature branches should manage their Git checkout manually; the updater never stashes, resets, cleans, switches branches, or discards work.

Using DFUUtility

Select and prepare a device

Connect the target with a data-capable cable. With one device, DFUUtility selects it for the detail workspace; with multiple devices, select the target explicitly. The Firmware Library can also be browsed before any device is connected.

Choose and validate firmware

For a connected target, use Choose Firmware… or Change Version… to see exact ProductType-compatible releases, or choose a local IPSW. Downloaded images are validated before they become Restore-ready. The independent Firmware Library can browse macOS, iOS, and iPadOS, download images, validate them, and open Manage Downloads… without changing a device's selection.

Enter DFU

Mac entry is initiated by DFUUtility on an Apple-silicon host. Supported iPhone/iPad entry follows the guided physical-button assistant; the assistant does not press buttons or send an unverified device command for you.

Restore, Revive, and Recovery Restore

Choose Revive where the current device state supports it. Restore is a separate, explicitly confirmed destructive action and requires a validated compatible IPSW. Supported mobile Recovery targets use the same exact-device Restore path and checks. Progress is stage-local and comes from Apple Configurator; DFUUtility does not invent an overall percentage.

Multiple devices and capture

Use Restore & Revive to select devices and run a sequential batch. Each operation is explicitly targeted and remains per-device. Use Device Capture for read-only identifiers, asset tags, serial-number QR codes, and CSV export; capture never changes batch selection or device state.

If Mac Enter DFU reports that the final VDM reply was not received, the target may already have transitioned. Wait briefly and click Refresh. If it remains absent, reconnect the cable. USB-C/DFU port behavior varies by model, so consult Apple's model-specific DFU-port guidance rather than assuming every MacBook uses the same port.

On the physically tested Mac17,6, automatic DFU entry required the rightmost USB-C port on the left side. After transition, the already-DFU target enumerated immediately when the cable was moved to the other left-side USB-C port. This is an observation for that tested machine, not a universal M4/M5-era port map.

Restore erases the target device. Back up recoverable data first. Restore does not bypass Activation Lock, ownership, enrollment, or setup requirements. Revive is not a backup and offers no data-preservation guarantee.

Dedicated DFU workstations

On an Apple-silicon Mac laptop, macOS may require approval before a newly connected wired accessory can communicate. DFUUtility cannot reliably read or change this policy. For a trusted technician workstation, review System Settings → Privacy & Security → Accessories → Allow accessories to connect. Automatically allow when unlocked can reduce repeated prompts while retaining protection when the Mac is locked. Always allow reduces prompts further but allows new wired accessories without individual approval, so reserve it for a physically controlled dedicated bench rather than a normal personal Mac.

During Mac DFU entry, approve “Allow accessory to connect?” if macOS presents it. If macvdmtool reports a missing final reply after the confirmed unlock/DBMa stage, DFUUtility checks for the same ECID in DFU for up to 30 seconds. This allows time for manual accessory approval and enumeration; it never retries the DFU command. Without positive same-device evidence, the transition remains unverified. Host accessory approval is separate from mobile trust/pairing and model-specific DFU-port selection.

See Dedicated DFU host setup for cable, model-specific DFU-port, security, MDM, and trust/pairing distinctions.

Tested hardware

Device	Product	Detection	Guided DFU	Restore/Revive
MacBook Air M2	Mac14,2	Normal/DFU: PASS	GUI same-ECID DFU: PASS	Restore and Revive: PASS
Newer Apple Silicon MacBook	Mac17,6	Normal/DFU: PASS	Automatic DFU: PASS; tested port-change caveat	Restore, progress, and restart: PASS
iPhone 6	iPhone7,2	Normal/Recovery/DFU: PASS	Same-ECID DFU: PASS	End-to-end Restore: PASS
iPhone 15	iPhone15,4	Recovery: PASS	—	iOS 27.0 / 24A437 Restore: PASS
iPad (7th generation) Wi-Fi	iPad7,11	Normal/Recovery/DFU: PASS	Same-ECID DFU: PASS	Recovery-mode Restore: PASS; progress/restart verification pending

For iPad7,11, compatible iPadOS discovery, GUI download, IPSW validation, and Recovery-mode GUI Restore passed on real hardware. Live Restore progress, restart verification, and full end-to-end acceptance remain pending. The authoritative, deliberately scoped record is Config/HardwareAcceptance.json.

An iPhone15,4 Recovery Restore using iOS 27.0 / 24A437 also passed exact-ECID targeting, firmware download/validation, Restore readiness, and Restore execution. Historical firmware acceptance remains untested.

Two simultaneously connected iPad12,1 Recovery targets also passed the explicitly selected, ECID-targeted sequential Restore workflow. A subsequently connected replacement iPad12,1 automatically received the exact validated cached iPadOS 26.6.1 / 23G83 asset and became Restore-ready while remaining unselected until explicit user action.

Older Lightning troubleshooting

If an older Lightning device repeatedly lands in Recovery with direct USB-C to Lightning, try USB-A to Lightning through a USB-C adapter or hub. This helped the tested iPhone 6; it is troubleshooting guidance, not a universal requirement. Testing has not established that USB-A is required for the iPad.

Firmware cache

Managed downloads live under ~/Library/Caches/DFUUtility/IPSW/, separated by platform. Manage Downloads… shows total storage, validation state and failure detail, and offers Reveal, Resume, and confirmed Remove actions. Operation logs live under ~/Library/Logs/DFUUtility/ and are available through View Log.

Diagnostics… shows detailed local information for troubleshooting. Copy Sanitized Diagnostics and Save Sanitized Diagnostics… create a shareable report that omits full device identifiers, usernames, and local filesystem paths.

CLI

swift build -c release
.build/release/dfuctl doctor
.build/release/dfuctl status
.build/release/dfuctl ipsw list
.build/release/dfuctl ipsw cache

Explicit hardware commands are .build/release/dfuctl dfu, .build/release/dfuctl revive, and .build/release/dfuctl restore /path/to/Restore.ipsw. Restore is destructive. The CLI's safe privilege behavior is documented in Privileged helper architecture.

Build and test from source

swift build
swift test
swift build -c release
scripts/package-app.sh release
scripts/verify-app.sh .build/app/DFUUtility.app

Run swift run DFUUtility --demo for a hardware-inert demo. scripts/release-check.sh performs builds, tests, read-only CLI smoke checks, packaging, metadata, license, signature, acceptance, screenshot, and ZIP checks; it never enters DFU, restores, revives, authorizes, or downloads firmware.

Security and privilege model

Community builds invoke only the bundled macvdmtool dfu operation through macOS's standard administrator UI. DFUUtility never reads or stores a password and does not use interactive sudo, setuid, or a custom password dialog. A future Developer ID distribution can use the embedded SMAppService privileged helper with matching Team-ID signatures, hardened runtime, and notarization. See Signing and distribution.

Apple Configurator's cfgutil remains required for device discovery, Restore, and Revive. Mobile DFU requires physical button input and is hardware validated only for the products listed above.

Contributing

See CONTRIBUTING.md for focused development and privacy-safe issue reporting. Read the 0.10.10 release notes, 0.9.0 release notes, and 0.10.0 binary updater notes for key milestones. The accepted updater workflow is documented in Binary update architecture. Browse the complete GitHub Release history for all published artifacts.

License

DFUUtility is licensed under the Apache License 2.0.

Third-party software

DFUUtility bundles upstream Asahi Linux macvdmtool at commit b22ae51eb43a0e1daa21d41616ac899f28e7bf8a. macvdmtool remains Copyright 2021 The Asahi Linux Contributors and Apache-2.0 licensed; DFUUtility does not claim ownership or relicense it. Its upstream source, attribution, license, and revision record are preserved and included in packaged apps.