An OpenCore EFI configured for my personal Raptor Lake Refresh (Intel 14th Generation) system.
This Hackintosh is currently a fluke - I don't have much of an idea of how or why this hack even works.
After I changed an unknown BIOS setting or something in config.plist, it randomly decided to boot into the macOS Installer instead of kernel panicking. I was so relieved and surprised that I ended up regaining faith in God and started praying - like literally...
"Thank You God for such a blessed day!"
Because of my lack of knowledge on completely unsupported systems with OpenCore (I only have experience with supported configurations such as an Intel Core i7-10700KF as an example), I will not be providing in-depth explanations here before I conduct a further investigation.
| Component | Name | Key Information | Hackintosh Notes | Hardware Comments |
|---|---|---|---|---|
| 🌍 Motherboard | ASUS TUF Gaming B760M-Plus | B760 Chipset, ALC897, RTL8125 | Lovely motherboard! 😍 | |
| 🧠 Processor | Intel Core i9-14900KF | 24 Cores (8P + 16E), 32 Threads | Raptor Lake is not natively supported. Advanced configuration required. | Really powerful - Outperforms M2 Ultra and M3 Max even with non-native support! 💪🏻 |
| 👀 Graphics | AMD Radeon RX 6900 XT Gaming Z Trio 16GB | MSI XTXH Variant | Only XTX is supported in macOS - XTXH is not. The device ID has to be spoofed. | Very powerful graphics - Outperforms above. 🤓 |
| 💭 Memory | Corsair Dominator Titanium RGB 64GB | DDR5 6400MHz, 4x16GB Configuration, Intel XMP | macOS does not recognise that it is DDR5 - this is purely cosmetic and doesnt affect anything. Also, you won't be able to control RGB from macOS. | Lovely colours with RGB! 🌈 |
| 💾 Storage | WD_BLACK SN850X 2TB with Heatsink | NVMe SSD, WD In-house controller | I'm not sure if this requires NVMeFix.kext as Apple and Western Digital go well together. | Really fast - up to 7,300MB/s. 🏃🏻💨 |
| 🛜 Wireless | Fenvi T-919 | Broadcom BCM94360CD | Has native support in macOS up to Ventura | Just a regular card 👍🏻 |
| Component | Name | Key Information | Hackintosh Notes | Hardware Comments |
|---|---|---|---|---|
| ❄️ CPU Cooler | Corsair iCUE H100i ELITE LCD XT | AIO Liquid Cooler, 65.57 CFM, 240mm Radiator | You will not be able to control it from within macOS. Set your settings in Windows and leave it alone. | Keeps the CPU very cool. Idles ranging from 26℃ to 29℃. ☃️ |
| 🪭 Case Fans | Corsair iCUE AR120 Digital RGB | 59 CFM, 120mm | This is controlled by the Corsair iCUE Commander Core XT, so you won't be able to control it either from macOS. | They look pretty in the case and circulate air optimally. 🧊 |
| ⛑️ Case | Asus Prime AP201 | microATX, Mini Tower | Really easy to work with, given its small size. 👏🏻 | |
| ⚡️ Power Supply | Corsair HX1000 Platinum | 1000W, Fully modular | Really efficient and powerful. 🔌 |
- Fast Boot
- Secure Boot
- Secure Boot Mode: Standard
- Secure Boot State: Setup
- Key management will turn off with these Secure Boot settings, however, this is required.
- Compatibility Support Module (CSM)
- Discrete Thunderbolt Support
- UEFI Variable Protection
- This doesn't have to stay disabled - only for Post-Install Configuration.
- VT-d and VT-x (The
DisableIoMapperquirk does not have to be enabled. In fact, disabling VT-d or enablingDisableIoMapperactually causes issues.)- A long time ago (almost a decade ago), when Hackintoshes were a new thing, someone said that VT-d should be disabled. This is no longer the case however and macOS actually requires it! This false piece of information has stayed with the community, however.
- Above 4G Decoding
- Resize BAR Support will become available - turn it on too.
- Hyper-Threading
- XHCI Handoff
- OS Type: Other OS
- Contrary to what the OpenCore Install Guide says, we will set this to "Other OS" to disable Microsoft Secure Boot which isn't required for macOS.
- Intel XMP
- Intel XMP does not cause issues. This can be enabled to enhance the performance of your hack.
- ASUS AI Tweaker (BIOS Automatic Overclocking)
- For some reason, people believe that overclocking can cause issues. Whilst this may be true on supported systems where power is managed properly, we do not care because we're doing enough spoofing with the CPU already and we need CPUFriend to handle our power management nevertheless. So, maximum performance it will be!
- Where exactly is the AI in this lol? It's just a BIOS... I don't expect it to have any AI features. How would you as a BIOS Vendor even implement that, and furthermore, how would American Megatrends implement it lol?
To be documented.
To be documented.
- CPUFriend
- Apple Industry Standard ProcessorType
- PlatformInfo > Generic > ProcessorType
- CFG Lock
- Spoofing the Processor Name and Type
- NVRAM >> Add >> 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102
To be further documented.
| Name | Type | Value |
|---|---|---|
| device-id | Data | BF730000 |
| model | String | AMD Radeon RX 6900 XT |
In TylerLyczak's Guide for fixing RX 6900 XT support, the model string he set was Radeon RX 6900 XT (XTXH). However, I believe that his model name didn't adhere to Apple's way of product naming.
I watched MKBHD's MacPro7,1 Unboxing Video and I found out that Apple tends not to include advanced information such as the GPU variant (in our case, (XTXH). Apple is always for simplicity. So I made it AMD Radeon RX 6900 XT as that is how Apple would present it.
As you can see, Apple only includes the product name and no advanced information. The amount of VRAM is automatically appended by macOS, so we do NOT set this manually in the device model string.
I've also applied the same naming convention to the processor name, see below.
Remember, this is PURELY COSMETIC! So naming here doesn't matter much. I'm just going for the ultimate Apple experience.
| Name | Type | Value |
|---|---|---|
| revcpu | Number (Integer) | 1 |
| revcpuname | String | 24-Core Intel Core i9 |
Please note: It is recommended to not go over 20 characters for revcpuname. However, I do not think that it matters that much. I've gone over by 1 character to display 24-Core Intel Core i9 and it still displays everything fine without issues.
As you can see here, I've applied the same naming convention to the CPU name as well. I've seen many configurations set the CPU name to be the full product name or a weird mix of everything combined. e.g. Intel Core i9-14900KF or even 24-Core Intel i9-14900KF. I have an issue with both because the presentation of information is very un-Apple-like. Apple tends to go for simplicity and displays only the important information such as core count and the short product name. I especially have an issue with the latter, 24-Core Intel i9-14900KF, because it just seems cursed not to say "Intel Core". Although Intel processors are not Apple's hardware, they are still respectful and display the full trademark name. Woo! Therefore, I have applied the same naming as Apple would have done.
| Name | Type | Value |
|---|---|---|
| ProcessorType | Number | 3841 |
I initially did not know that ProcessorType had to be set manually in order to apply a custom CPU name. Or, more specifically and more likely, because I have an unsupported Raptor Lake Refresh CPU, OpenCore was failing to determine a ProcessorType so it defaulted to 0x00, AppleProcessorTypeUnknown which I assume does not support CPU renaming. Hence, macOS was showing "3.18GHz Unknown" regardless of the CPU name I was attempting to set. The unknown will always be unknown!
❗️ Be careful when modifying your BIOS directly. It can severely break your system!
ℹ️ UEFI Variable Protection must be disabled in the BIOS.
After that, instructions from the OpenCore Post-Install Guide can be followed as-is.
In my case, VarOffset was 0x44. This meant that I had to use the following command in the Modified GRUB Shell:
setup_var_cv CpuSetup 0x44 0x01 0x00
The command above writes one byte of information, 0x00, to offset 0x44 in CpuSetup.
The contents of this GitHub repository adhere to the Numelon Standardisation Convention.