XiaoMi-Pro-Hackintosh: OpenCore EFI for Xiaomi NoteBook Pro 15.6

Which Xiaomi NoteBook Pro models this EFI actually covers

This project is a set of prebuilt EFI folders for running macOS on the Xiaomi NoteBook Pro 15.6 inch. It is not a general hackintosh toolkit and it does not target other Xiaomi laptops. The README splits supported machines into two groups.

The first group is TM1701 and TM1707, the 15.6 inch models with MX150 or GTX graphics, an Intel Core i5-8250U or i7-8550U, Samsung DDR4 2400MHz memory, a Samsung PM961 NVMe SSD (PM981 is struck through in the table), Intel UHD Graphics 620, a BOE NV156FHM-N61 1920x1080 panel, Realtek ALC298 audio with layout-id 30 or 99, an Intel Wireless-AC 8265 card, an ETD2303 trackpad and a Realtek RTS5129 or RTS5250S SD card reader.

The second group is TM1905 and TM1963, the MX250 or MX350 models with a Core i5-10210U or i7-10510U, DDR4 2666MHz memory, an Intel SSD 660P Series drive, the same UHD 620 integrated graphics, an LQ156M1JW01 SHP14C3 panel, Realtek ALC256 audio with layout-id 69, an Intel Wireless-AC 9462 card, an ELAN2303 trackpad and a Realtek RTS5129 reader.

The audience is narrow by design: people who already own one of those four model numbers. If your machine is a different Xiaomi laptop, the ACPI patches and kext selection here will not match your hardware, and nothing in the README suggests otherwise.

How the EFI, ACPI patches and kexts fit together

The repository is organised as a bootloader payload rather than an application. The top level holds ACPI, ALCPlugFix, BIOS, CLOVER, ColorProfile, Docs, Kexts, OC, Patches and Scripts, plus a makefile.sh build script.

OC is the OpenCore EFI tree and CLOVER is the older Clover tree. Both are shipped because the two bootloaders have different macOS ceilings and different quirks. The README states that OpenCore supports macOS 10.15 through macOS 26 on both hardware groups, while Clover supports macOS 10.15 through macOS 15. Version 1.5.9 is called out as the last EFI release supporting macOS High Sierra and Mojave.

The ACPI folder holds the SSDT patches. Two are named in the README with their purpose: SSDT-DDGPU disables the discrete graphics card because macOS does not support Optimus, and SSDT-USB disables the fingerprint sensor. Both are described as power-saving measures, not fixes. The Kexts folder carries the driver set, and Patches holds the binary patches that the bootloader applies.

The BIOS folder and ALCPlugFix point at the two things you must handle outside the EFI: firmware settings and the audio jack. The README does not document the individual BIOS options in the excerpt available, so treat the BIOS folder as the reference rather than guessing at settings.

One cross-bootloader constraint is explicit. After using OpenCore you should clean NVRAM before switching to Clover: press Space on the OpenCore boot page, select the Reset NVRAM entry, reboot, then use Clover. The same instruction appears in reverse for going from Clover to OpenCore.

First-time installation and upgrade path

The README's installation section has four steps: identify your model, first-time installation, build, and upgrade. Model identification matters because the two hardware groups use different audio layout-ids and different trackpad and Wi-Fi chips.

If you want to build the EFI yourself rather than download a release, the repository ships a makefile.sh at the top level. The README documents a build step, but the available excerpt does not list its flags, so run it from the repository root and read the script before executing it:

./makefile.sh

The releases page is the other route. The most recent tagged release is v1.8.9 (XiaoMi NoteBook Pro EFI v1.8.9), published on 2025-06-15, preceded by v1.8.8 on 2025-04-08 and v1.8.7 on 2024-12-16. Downloading a release gives you the EFI folder without running the build script.

On the CML machines (TM1905 and TM1963), the README warns that hibernation can trigger serious boot problems and points to issues #661 and #694. The stated fix is to disable hibernation:

sudo pmset -a hibernatemode 0

The README also refers readers to Docs/README_CML.txt for the CML machines. After the first boot, expect the HDMI quirk described in Current Status: on first plug-in the display may not come up, and you have to re-plug the cable or close the lid for about five seconds and reopen it.

Wi-Fi and Bluetooth are the weakest part of the support matrix

Intel Wi-Fi is listed as working with low performance. That phrasing is the honest summary of the whole wireless situation. The README states that IO80211 does not support macOS Sequoia and above, and directs users to itlwm plus HeliPort instead. macOS 11 through 14 is described as the recommended range. On macOS versions below 11, if Intel Wi-Fi does not work, you need to rebuild the kextcache and restart.

The README offers two fallbacks: buy a USB Wi-Fi dongle, or replace the card with a supported wireless card. Neither is a software fix, and both cost money or a teardown.

Bluetooth has its own caveats. Intel Bluetooth does not support some Bluetooth devices, though on macOS 12 and later it supports more Bluetooth 4.x devices. The README points to a wiki page titled Work-Around-with-Bluetooth and to three external projects, IOBluetoothFixup, IntelBluetoothFamily and OpenFirmwareManager, from the AppleBluetooth organisation. Those are third-party kexts maintained outside this repository, so their compatibility is not something this project controls.

There is also a Clover-specific trap: r5127 does not support Intel Wi-Fi on macOS versions below Big Sur because of incomplete ForceKextsToLoad functionality. Only v1.4.7 supports Intel Wi-Fi on those older releases, or you can add IO80211Family.kext to the kext folder yourself. If you are on Clover and an older macOS, that is a hard constraint, not a configuration detail.

What does not work, and what that means for buying decisions

The discrete graphics card does not work. macOS does not support Optimus, so the MX150, MX250 or MX350 is disabled by SSDT-DDGPU and the machine runs on Intel UHD Graphics 620. Anyone hoping to use the NVIDIA chip for rendering, gaming or compute is on the wrong platform, and the project's answer is to turn the chip off rather than drive it.

The fingerprint sensor does not work and is disabled by SSDT-USB. Audio is the newest casualty: the README states audio will not work starting with macOS 26.0 beta 2 (25A5295e) because AppleHDA was dropped, and users need OpenCore-Legacy-Patcher to restore it. That is a meaningful regression for anyone tracking the newest macOS releases, and it means the macOS 26 support claim comes with an audio asterisk.

Ethernet may not work on macOS 10.15 and later, tracked in issue #256. The Realtek USB SD card reader works only in some setups, and the README points to RealtekCardReader's FAQ plus the RealtekCardReader and RealtekCardReaderFriend kexts, or a VMware-based workaround documented in another project's wiki.

The pattern is consistent: the essential laptop functions work, and every peripheral that depends on a vendor driver is either disabled, degraded or delegated to a third-party project. If your workflow depends on the SD reader, wired Ethernet, or Bluetooth audio across a range of devices, this EFI is the wrong tool and a supported Mac or a different laptop is the honest answer.

OpenCore also has a limited theme, per the README, and some users report trouble updating to Windows 11 (issue #665). Dual-boot plans should account for that.

OpenCore versus Clover, and where Dortania's guides fit

The real alternative is not another EFI pack. It is building your own OpenCore configuration following the Dortania documentation, which the README itself links for post-install security and FileVault guidance. The difference in approach is ownership: this project hands you a prebuilt EFI tuned for four specific model numbers, while Dortania's guides walk you through generating ACPI patches, selecting kexts and configuring the config.plist for your exact hardware.

If your machine matches TM1701, TM1707, TM1905 or TM1963, the prebuilt route saves the ACPI work, and the project has already decided which devices to disable. If your machine is close but not identical, the prebuilt route is a liability, because you inherit someone else's device decisions without the reasoning. The README does not document rollback, and it does not provide a per-patch explanation of why each SSDT exists beyond the two named disabling patches.

Within the project itself, the OpenCore and Clover trees are the two choices. OpenCore reaches macOS 26 and is the one the README treats as current; Clover stops at macOS 15 and carries the r5127 Wi-Fi limitation on older macOS versions. Unless you have a specific reason to stay on Clover, OpenCore is the branch with headroom.

Licence, maintenance and upgrade cost

The repository is licensed under 0BSD, a permissive licence that imposes no conditions on use, modification or redistribution. That matters here because EFI folders bundle third-party kexts, and those kexts carry their own licences which 0BSD does not override. Check the Kexts folder contents against their upstream projects before redistributing a modified EFI.

The repository is not archived, and the last push was on 2026-06-19. The most recent tagged release, v1.8.9, dates from 2025-06-15. That gap between the last push and the last release is worth noting: commits continue, but tagged EFI releases arrive less often, so if you build from the main branch you are running untagged code.

Upgrade cost is dominated by macOS, not by this project. Each macOS release has changed the wireless situation: IO80211 stopped supporting Sequoia and above, and macOS 26.0 beta 2 dropped AppleHDA and broke audio. Every one of those transitions is a potential rework of kexts and patches, and some of the fixes live in other repositories. Budget time for that, and read the Current Status section before upgrading rather than after.

Editorial conclusion

Adopt this if you own a TM1701, TM1707, TM1905 or TM1963 Xiaomi NoteBook Pro 15.6 and want a prebuilt OpenCore EFI instead of building one from the Dortania guides. Do not adopt it if you expect working Intel Wi-Fi at usable speed, Bluetooth audio for every device, or the MX150/MX250/MX350 discrete GPU, because the README states none of those work as they would on supported hardware. Before flashing anything, verify your exact model number and SSD, since the README lists PM961 as supported and strikes through PM981, and check the Current Status section for the macOS release you plan to run.

Frequently asked questions

Official sources

1. daliansky/XiaoMi-Pro-Hackintosh on GitHub
2. Issues
3. License: 0BSD
4. README
5. Releases