Kernel binary patches to enable native AMD CPU support on macOS.
- Enables macOS to run on AMD CPUs on the fly.
- Enables iMessage, Siri, FaceTime, Continuity etc.
- Stable compared to custom XNU kernel.
- No 32-bit support (OPEMU) in 10.14 and lower
Family | Codename | Example |
---|---|---|
15h | Bulldozer | FX Series |
16h | Jaguar | A Series |
17h | Zen | Ryzen, Threadripper, Athlon 2xxGE |
- High Sierra 10.13.6 (17G65, 17G66, 17G8030, 17G8037)
- Mojave 10.14.6 (18G84, 18G87, 18G95, 18G103)
- Catalina 10.15.0 (19A583, 19A602)
- Download macOS High Sierra, Mojave or Catalina from the App Store.
- Plug in an empty USB drive.
- Run one of the below commands in your Terminal to prepare the bootable macOS USB.
NOTE: Make sure to replace 'MyVolumeName' with your actual USB volume name in the below commands.
## High Sierra
sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolumeName
## Mojave
sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolumeName
## Catalina
sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolumeName
- Install Clover on your USB drive.
- Place the
config.plist
provided, according to your CPU family (i.e15h_16h
or17h
) in your USB EFI Clover folderEFI/EFI/CLOVER/
and edit it as per your needs. Note: If your are making your own Clover config, usepatches.plist
and merge the patches manually. - Place the required kext according to your system in your USB EFI kexts folder
EFI/EFI/CLOVER/kexts/Other/
.
- For 15h_16h CPU family users on macOS Mojave:
- Upon booting to macOS Mojave for first time, the system will reboot after the Data & Privacy screen. To fix this issue follow the procedure mentioned here under UPDATE-2 heading.
- On macOS Mojave certain webpages will crash upon loading (eg. brew.sh, facebook.com). To fix this issue follow the procedure mentioned here under UPDATE-5 heading.
- To boot 10.15 two things needs to be taken care of:
- If you have an EC device with ID
PNP0C09
in your DSDT then macOS might get stuck while booting at the initial stage. To fix that you need to make sure your EC device is disabled by making it return statusZero
. You can use a custom SSDT-EC0.aml to do that and if you want to see how it works then refer here.
-or-
You can change the ID of the EC device. Use this ACPI patch:Comment Find Replace PNP0C09 to PNPFFFF 41D00C09 41D0FFFF
- If using SMBIOS
MacPro6,1
,MacPro7,1
, oriMacPro1,1
,AppleIntelMCEReporter.kext
might panic. To prevent that you need to either use a different SMBIOS model or use a disabler kext from here.
- If you have an EC device with ID