How to Safely Use the x99 dmg 3 Hackintosh Image

The filename x99 dmg 3 is one of the most downloaded in legacy X99 Hackintosh circles. This disk image, typically 8–12 GB in compressed form, claims to contain a ready-to-install copy of macOS 10.12 Sierra, 10.13 High Sierra, or 10.14 Mojave alongside a preconfigured boot environment for Haswell-E and Broadwell-E systems. The archive is often distributed via file‑sharing platforms and may originate from several anonymous community builds. Before attaching it to your system, you need to understand exactly what the image contains, what risks it carries, and how to extract only the components you really need without compromising your data.

What the DMG Typically Contains

Most releases of x99 dmg 3 are constructed around a genuine macOS installer app (Install macOS Sierra.app, Install macOS High Sierra.app, etc.) combined with a prepackaged EFI partition. The EFI partition is the part you care about — it holds the bootloader configuration, kernel extensions (kexts), and ACPI patches that make macOS boot on X99 hardware. Common contents include:

Bootloader — either Clover (v2.4k or later, sometimes older v2.3k) or OpenCore (0.5.x–0.6.x). The bootloader’s config.plist is pre‑tuned for generic X99 boards, often with a one‑size‑fits‑all approach.
Kexts — Lilu, WhateverGreen, AppleALC, FakeSMC (or VirtualSMC), IntelMausiEthernet (or AppleIntelE1000e), USBInjectAll, and possibly specific GPU enablers like NvidiaWebDriver for High Sierra/Mojave.
ACPI patches — SSDTs that are critical for X99: SSDT-UNC (uncore frequency), SSDT-EC (embedded controller emulation), and SSDT-XCPM (XNU CPU Power Management). Some packs also include board‑specific SSDTs for USB port mapping or for disabling unused PCI devices.
Drivers — UEFI drivers such as ApfsDriverLoader, HFSPlus.efi, and sometimes NvmExpressDxe for NVMe support.

The actual macOS installer inside the DMG is typically unmodified vanilla files, but the EFI partition is a custom assembly that may not match your specific motherboard or GPU.

Risks of Using a Prebuilt DMG Blindly

Several documented problems arise from relying on such images without inspection:

Malicious code — The DMG could contain scripts or kexts that modify system files, install persistent kernel backdoors, or exfiltrate serial numbers from your own hardware.
Stale kexts — A DMG built in 2018 may carry Lilu 1.2.0 and WhateverGreen 1.1.0, which lack fixes for newer GPU revisions or for macOS security patches released later. Running outdated kexts on a fresh install will cause kernel panics on wake, broken iGPU support, or unstable Ethernet.
Wrong ACPI tables — The SSDTs inside the image were likely dumped from a specific board (e.g., ASUS X99‑A or Gigabyte X99‑UD4). Applying those tables on a different model (e.g., MSI X99A SLI Plus) can cause boot loops, missing CPU cores, or instant sleep‑panic. A common symptom is an ACPI error 3327 (as discussed in our earlier guide on Ivy Bridge and Haswell systems, similar principles apply).
USB port mapping — X99 systems often have many USB 3.0 ports that require a custom SSDT-UIAC or a USBInjectAll with port limit patches. The DMG’s prebuilt mapping will almost certainly leave some ports dead or cause wake issues.

How to Inspect the DMG Safely

Never double‑click the DMG in Finder or run any script inside it. Use the command line to mount it read‑only and examine the contents:

Verify file integrity — Run shasum -a 256 x99 dmg 3.dmg and compare the checksum against published values from trusted community sources (e.g., tonymacx86 or InsanelyMac posts that publish the SHA‑256 of their releases). If no matching checksum exists, treat the file with extreme suspicion.
Mount read‑only — hdiutil attach -readonly x99 dmg 3.dmg. This mounts the image but prevents any write operations. The mounted volume will appear under /Volumes.
Browse the EFI partition — Inside the volume you’ll see a folder named EFI (or efi). Open it and inspect the CLOVER or OC folder. Look for a config.plist and open it in a text editor or a tool like Clover Configurator. Pay attention to:

ACPI -> Drop Tables — Are any OEM SSDTs being dropped? That setting is board‑specific.
KextsToPatch — Are there binary patches that disable SIP or modify kernel internals? Flag any patch that does not target a known bug.
SMBIOS — Which Mac model is being used? For X99, iMacPro1,1 or MacPro6,1 are typical; a MacBookPro entry will cause wrong power management.

Check the ACPI folder — Look for SSDT.aml files. Open them with a tool like iASL (available via MacRanger). Verify their content matches your CPU topology (e.g., Haswell‑E vs Broadwell‑E use different SSDT-XCPM).

Verifying Compatibility with Your Specific Board

Even if the image looks clean, it may still be unsuitable for your hardware. The most reliable approach is to use the DMG only as a source for the macOS installer app, then build your own EFI folder from scratch using known‑good references. You can find detailed kext and ACPI guidance for Broadwell‑E systems in the Broadwell-E Hackintosh on High Sierra: Required Kexts, ACPI Patches, and Bootloader Config post. For resolving sleep and wake quirks on X99, refer to Fixing Sleep/Wake Issues on Legacy Hackintosh Builds (Sierra & High Sierra).

If you decide to use the EFI partition from the DMG as a starting point, strip it down to the bare essentials before booting:

Delete all SSDT-xxx.aml files except SSDT-UNC, SSDT-EC, and SSDT-XCPM. Add a board‑specific SSDT-UIAC for your USB ports.
Replace all kexts with fresh copies from the official GitHub releases. Remove any kext that is not strictly required for your setup (e.g., NoTouchID, VoodooPS2 if you use a standard USB keyboard).
Reset the config.plist to a vanilla template and apply only the patches that your hardware actually needs — start with a minimal config.plist and add features incrementally.

Safe Extraction Workflow

Here is a step‑by‑step procedure that avoids writing anything to your main system drive:

Insert a USB flash drive (8 GB or larger) and format it as a single FAT32 partition with GUID Partition Map.
Mount the x99 dmg 3 image read‑only (hdiutil attach -readonly).
Copy the EFI folder from the mounted image to the USB drive. Do not copy any other files or run any installer.
Unmount the DMG (hdiutil detach /Volumes/name_of_volume).
On the USB drive, examine and trim the EFI folder as described above. Replace kexts with current versions.
Disconnect all internal SATA/NVMe drives except the one you intend to install macOS on. This prevents the installer from overwriting your existing boot loader.
Enter BIOS: enable XHCI hand‑off, disable CSM, set SATA mode to AHCI, and — if your board supports it — set CFG‑Lock to disabled or allocate 1–2 MB for it.
Boot from the USB drive. The bootloader should present the installer entry.

Before you start the installer, boot from the USB and watch for any panic messages. If you see one, check the ACPI error code — a common one is 3327, which the linked guide covers. Also verify that your BIOS has CFG-Lock disabled; many X99 boards ship with it enabled, causing immediate kernel panics. Spending ten minutes on these checks now beats spending hours recovering a corrupted install later.