# XiaoXinPro-13-hackintosh: a Hackintosh EFI for the Lenovo XiaoXin Pro 13

> This repository is a prebuilt EFI folder and configuration set for running macOS on the 2019 and 2020 Intel versions of the Lenovo XiaoXin Pro 13, with notes on the CPUID spoofing, BIOS changes and SSD models that the setup depends on. It suits an owner of that specific laptop who wants a working configuration rather than a general guide.

**daliansky/XiaoXinPro-13-hackintosh** — Lenovo XiaoXin Pro 13 2019 Hackintosh

- Repository: https://github.com/daliansky/XiaoXinPro-13-hackintosh
- Stars: 899 · Forks: 137
- Language: C++
- License: not declared
- Published: 2026-10-20 · Updated: 2026-10-20 · Language: en
- Canonical page: https://hysenlabs.com/projects/daliansky-xiaoxinpro-13-hackintosh

## One laptop, one EFI, and a list of the parts that matter

The scope is deliberately narrow. This is an EFI folder and configuration set for the Lenovo XiaoXin Pro 13 2019 and 2020, and the applicability line is explicit: the 2019 and 2020 models of the XiaoXin Pro 13 in the Intel version. The configuration table lists what the machine has, and it doubles as a compatibility list. The processor is a Core i5-10210U or i7-10710U, the memory is 16GB soldered and not replaceable, the display is a 13.3 inch IPS panel at 2560x1600, the graphics are Intel HD Graphics CFL CRB, which is the UHD620, and the audio is Realtek ALC257. The network card is listed with several alternatives, the original AX201 alongside Intel cards, the BCM94360Z4 four antenna card, and a card taken from a white Apple machine, each of which links to its own wiki page. The official BIOS is not shipped with the repository but is pointed at by a Lenovo support search for the XiaoXin Pro 13 Intel, with the IML platform version named. A repository structured this way is not a general hackintosh guide. It is a specific answer to a specific machine, which is exactly what makes it useful and exactly what limits it.

## Some CPUs need a spoofed CPUID before macOS will install

The first technical hurdle is the one most likely to stop a new user, and it is documented with a warning marker. Some i5 processors and the i7-10710U have a CPUID of 0x0A0660, and those units need a spoofed CPUID, with 0x0806EC and 0x0806EB given as the values to use, and a wiki page explaining how to check the CPUID on the machine. The reason this matters is that macOS matches its kernel extensions against a list of supported processor identifiers, and a CPUID that is not on that list produces an installation that fails or a system that will not boot. Spoofing the identifier is the standard workaround, and the documentation is careful to say that the values are for the affected units rather than for every machine. The second prerequisite is a firmware change. The documentation says you need the DVMT change and CFG Lock enabled, again with a link to a wiki page and a reference to a test BIOS. Both of these are non-negotiable steps before anything else, and both are things a reader will otherwise discover by trial and error.

## The SSD model decides whether the install works at all

The storage section is the most useful piece of accumulated knowledge in the repository, because it is a compatibility matrix of specific part numbers with a binary verdict. The laptop has a PCIe x4 slot that can take a mix of drives, and the known models are listed as usable or not usable under macOS. Usable are the UMIS drives, which is Yimeng's AH530, the INTEL drives, which is the Intel 760P, and the WD BLACK drives, which is the SN 730. Not usable are the SK Hynix drives, with the specific part named as SK HYNIX SKHynix_HFS512GD9TNI-L2A0B, and the Samsung drives, with the part named as SAMSUNG MZVLB512HBJQ-000L2, described as the PM981a. The documentation is careful about the limits of its own list, noting that for any other model the list neither says it is usable nor says it is not. And the advice for the two unusable models is direct: if your drive is one of those, replacing it with another model is strongly recommended for a better experience of macOS. There is also a linked spreadsheet about the power consumption of the drive on this machine, which is the kind of detail that only appears after someone measured it. The practical effect is that a buyer of a used XiaoXin Pro 13 should check the drive model before anything else.

## Both Clover and OpenCore are shipped, and the switch has a procedure

The EFI directory contains a Clover boot method and an OpenCore boot method, and the documentation says both currently work, with the caveat that the OpenCore route requires you to add Windows boot yourself, with a linked document for adding a multi system entry. The switching instructions are specific, and they read like a fix for a common failure. To move from Clover to OpenCore, for example, you set OpenCore as the boot method first, then on the first reboot you choose reset nvram, which clears the previous boot settings, and then you set the corresponding EFI to boot. The reason the order matters is that the two bootloaders write to the same NVRAM, so a stale Clover entry can point at an EFI partition that no longer holds what the firmware expects. The repository also ships a Changelog.md at the root, which the README links for the details of the sound card ID, and the release history shows a line of tagged versions with v3.1.1 from 2023-06-11, v3.1.0 from 2023-04-16 and v3.0.9 from 2023-02-28, though the last push was on 2026-10-19, so the branch is receiving work that has not produced a new tag.

## ACPI patches are applied at runtime with hotpatch

The ACPI handling is the part of the configuration that shows real engineering rather than a copied config file. Other ACPI patches that fix various problems are applied with the hotpatch method, with the files located under the /ACPI/patched directory inside the EFI. The USB customisation is also done with the ACPI approach, described as being done in preparation for using OpenCore. A hotpatch setup means the patched tables are loaded from disk at boot rather than being baked into a compiled binary, so a user can add or remove a patch by editing a file rather than by recompiling an SSDT. That is a meaningful difference for a configuration that people follow from a wiki, because it is the difference between a step that requires a toolchain and a step that requires a text editor. The repository root makes the ACPI theme visible too, with an archive containing the sound card extraction and the SSDT ACPI files, and separate plist configuration files for the BCM wireless and Bluetooth driver list with ASPM and for the Intel wireless and Bluetooth driver list, which are alternatives to the stock AX201 setup for anyone who has swapped the card.

## What works, what does not, and why sleep cannot be fixed

The working list is specific. The graphics, power management, Bluetooth, display brightness adjustment, the original AX201 wireless card, which is noted as drivable under macOS as of 08-02-2020, and the touchpad, dated 02-17-2020, with a note that the touchpad can be turned off in OpenCore with the FN+F6 combination. The not-working list has two entries and one of them is the interesting one. Sleep is struck through, meaning it was once listed as broken and is now described as simulated rather than real, with the wake method in OpenCore given as the power button. The explanation for why is a detailed panel in the documentation and it is worth reading in full. The machine has no S3 sleep, and the text argues that a modern standby state of S0 does not really exist as a distinct sleep, that S0 sleep is in substance the idle state of D0, and that the machine has no S3 sleep because no relevant hardware was designed for it. The presence of S3 in the ACPI is what makes macOS attempt a sleep that then fails for lack of the hardware, and the text notes that this does not affect Windows. The microphone is a separate story: the entry for the broken microphone is struck through, and the working list notes MIC as fixed as of 2026-10, with links to community audio projects.

## Troubleshooting guidance, and where to get help

The documentation ends with a support section that is unusually concrete about what a good bug report looks like. It strongly recommends reading the wiki first, then troubleshooting on your own with steps such as rebuilding the cache and restarting, and then providing the hardware information for the XiaoXin Pro 13, for example a screenshot from a hardware identification tool, a detailed description of the operations performed, and logs or full screenshots. That list is a good model for what to gather before asking, and it applies to any hackintosh problem rather than only this one. There are three QQ groups listed, one for general XiaoXin Pro hackintosh use, one for a technical group, and one specifically for Insyde BIOS research, which is the firmware vendor behind the laptop and the component responsible for the DVMT and CFG Lock work. The installation section also carries a practical warning that is easy to miss: during installation the touchpad may not be driven, and using a USB stick to install macOS occupies the only USB port, so it is recommended to buy a USB hub before starting so a mouse can be plugged in to select the installation options. The rest of the support resources point to a macOS image download page and to a separate system information collection tool shipped as a zip in the repository root.

## Conclusion

This repository is a good fit for someone who owns a 2019 or 2020 Intel XiaoXin Pro 13 and wants a configuration that has already been worked out, since the EFI, the patched ACPI files and the release history are all in one place and the hardware-specific pitfalls are documented rather than left to be rediscovered. It is the wrong tool for a different laptop, for a newer Apple Silicon machine, or for anyone who needs macOS with working sleep, because the documentation is explicit that the machine has no S3 sleep hardware and that sleep is only simulated. Before starting, check the CPUID of your processor against the list, because some i5 and i7-10710U units need a spoofed CPUID, and confirm your SSD model against the compatibility list, since several common models are marked as unusable. The licence is not identified for the repository, and the last push was on 2026-10-19.

## FAQ

### Which laptops does the XiaoXinPro-13-hackintosh EFI support?

The 2019 and 2020 models of the Lenovo XiaoXin Pro 13 in the Intel version, with a Core i5-10210U or i7-10710U processor, 16GB of soldered memory, Intel UHD620 graphics, a 13.3 inch 2560x1600 display and a Realtek ALC257 sound card.

### Which SSD models work with macOS on the XiaoXin Pro 13?

The known usable models are UMIS drives such as the Yimeng AH530, INTEL drives such as the Intel 760P, and WD BLACK drives such as the SN 730. SK Hynix drives and Samsung drives, including the PM981a, are listed as not usable, and the documentation strongly recommends replacing those two models. For any other model the list says neither that it works nor that it does not.

### Do I need to change the BIOS before installing macOS on this laptop?

Yes. The documentation says you need the DVMT change and CFG Lock enabled, with a link to a test BIOS, and it also gives the Secure Boot steps: enter the BIOS with Fn+F2, check whether Secure Boot is enabled under Information, disable it under Security if it is, and save with Fn+F10. Some processors also need a spoofed CPUID, with 0x0806EC and 0x0806EB given as values to use.

### Can the XiaoXin Pro 13 sleep under macOS?

Not properly. The documentation explains that the machine has no S3 sleep because no relevant hardware was designed for it, that the S0 state is in substance the idle state of D0, and that the presence of S3 in the ACPI is what makes macOS attempt a sleep that then fails for lack of hardware. Sleep is struck through in the list of known problems, and wake in OpenCore is done with the power button.

### Does the repository provide both Clover and OpenCore boot files?

Yes, the EFI directory contains both a Clover boot method and an OpenCore boot method, and the documentation says both currently work. The OpenCore route requires you to add Windows boot yourself, and the switch procedure is to set OpenCore first, choose reset nvram on the first reboot, then set the corresponding EFI to boot.

## Sources

- [daliansky/XiaoXinPro-13-hackintosh on GitHub](https://github.com/daliansky/XiaoXinPro-13-hackintosh)
- [Issues](https://github.com/daliansky/XiaoXinPro-13-hackintosh/issues)
- [README](https://github.com/daliansky/XiaoXinPro-13-hackintosh/blob/master/README.md)
- [Releases](https://github.com/daliansky/XiaoXinPro-13-hackintosh/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/daliansky-xiaoxinpro-13-hackintosh
