macOS Catalina (OpenCore Build) Lenovo ThinkPad T450
COPIED FROM ECHOESPIRITS REPO (CREDIT HIM/HER) https://github.com/EchoEsprit/Hackintosh-Catalina-OpenCore-Lenovo-T450s-efi
- Intel 5th Generation Architecture (Broadwell)
- Intel HD Graphics 5500
- Intel Series 9 Chipset Family
- macOS Catalina Catalina
- OpenCore Based Configuration
- AirPort Extreme (Broadcom BCM94360CSAX & NGFF A/E Adapter) * Recommended Upgrade
- BETA BUILD!! Not all features may function like they do in my Clover Build#
Important Information For Usining OpenCore Instead Of Clover
-
OpenCore will not boot if CSM support is enabled in the BIOS!!! This can be confusing because usually CSM is required to successfully boot Clover but it needs to be disabled for OpenCore.
-
You must also remove the existing Clover configuration from your system as well in order for OpenCore to function properly. I suggest you back it up before hand as well as make a second USB installallation drive with the configuration and Clover in the EFI partition and do the same with an OpenCore drive as well.
PayPal
- If you like my work then please feel free to donate. Every little bit helps! jsa55u@icloud.com | Paypal.me/Sass86oh
#
iMessage (Contact me whenever for help)
- Jsass20@gmail.com (or Jsassu20@me.com)
#
Credits
- EchoEspirit - https://github.com/EchoEsprit/Hackintosh-Catalina-OpenCore-Lenovo-T450s-efi. His LenovoT450s OpenCore build is what I used as a base for this build as I'm still learning the ins and outs of proper building on OpenCore based systems since its a radically different approach compared with my previous venture into CLOVER based Hackintosh setups and whats required to build a successful one. Keep in mind the T450s is the same as the T450 in every important aspect in building a Hackintosh system so you can use this build of his as it is. The only thing that may need editing is the settings for proper battery reporting.
OpenCore Starter Guide From OCBuilder App
OpenCore Starter Guide 0.5.3
Updated 17th October
A brief guide to using the OpenCore boot-loader for hackintoshes
OpenCore is an alternative bootloader to CloverEFI or Chameleon. It is not only for Hackintosh and can also be used on real macs for purposes that require an emulated EFI. It also aims to have the ability to boot Windows and Linux without the need for using different acpi tables. It has a clean codebase and aims to stay closer to how a real mac bootloader functions. Kext injection has been greatly improved. While already functioning well,
OpenCore should be considered in Public Beta stage at this time and is intended to be used by experienced hackintosh users, developers, or users who are happy to recover a system which fails to boot or becomes broken in some way.
This guide may not always be able to keep up with every change to OpenCore, (currently OpenCore is in active development,and therefore a moving target) please keep that in mind when compiling the latest version of OpenCore. To be safe, use release versions of OpenCore rather than the latest commits. (0.0.4 Current Release)
This guide is intended to complement the excellent opencore “configuration.pdf” rather than be used instead of it. If you did not already do so, please read it now:
Full Documentation From Acidanthera GitHub
Current known issues
Refer to opencore bugtracker for current known bugs here
Opencore Pro’s
One average, OpenCore systems boot faster than those using Clover. OpenCore offers better overall security and better support for FileVault. OpenCore supports boot hotkey support via boot.efi - hold Option or ESC at startup to choose a boot device, Command+R to enter Recovery or Command+Option+P+R to reset NVRAM. OpenCore is designed with the future in mind, and uses modern methods to inject kernel extensions without breaking System Integrity Protection. BootCamp switching and boot device selection are supported by reading NVRAM variables set by Startup Disk just like a real mac. Furture development for AptioMemoryFix is directly tied to OpenCore, specifically being absorbed into OpenCore itself with the FwRuntimeVariable.efi being used as an extension. UEFI and Legacy boot modes are supported. OpenCore Must’s
Kernel extensions are loaded in the order specified in your config file, so you must load an extension’s dependencies before you load the extension itself. For example, Lilu must be loaded before WhateverGreen or VirtualSMC. ACPI patches and SSDTs are applied to all operating systems. Some systems require pure UEFI mode to boot. (This setting is commonly called “Windows 8/10 Mode” by motherboard manufacturers.) Issues can occur if NVMe devices are set up as SATA devices in the BIOS. Getting Started
Requirements:
OpenCorePkg (Recommend to build from scratch instead of using the prebuilt package as OpenCore is constantly being updated. As of writing we’re on Version 0.5.1 even though the current official release is 0.5.0). Easiest way to build is via the macbuild.tool or Use Pavo’s Opencore Builder App to Create the Entire EFI Folder (Requires Xcode Installed) Recommended BIOS settings:
Disable:
Fast Boot CFG Lock(MSR 0xE2 write protection) VT-d(can be enabled if you set DisableIoMapper to YES) CSM Thunderbolt Intel SGX Intel Platform Trust Enable:
VT-x Above 4G decoding Hyper Threading Execute Disable Bit EHCI/XHCI Hand-off OS type: Windows 8.1/10 EFI Drivers
For the majority of systems, you only need 3 .efi drivers to get up and running:
ApfsDriverLoader.efi Needed for seeing APFS volumes. VboxHfs.efi or HfsPlus.efi Needed for seeing HFS volumes. FwRuntimeServices.efi Replacement for AptioMemoryFix.efi, used for patching boot.efi for NVRAM fixes and better memory management. For extra functionality with OpenCore:
AppleGenericInput.efi Used for Apple Hot keys and FileVault support, some firmwares may not register all the keys while booting so this can be substituted with UsbKbDxe.efi. VirtualSmc.efi Used for proper FileVault support, cannot be used with FakeSMC For a full list of compatible drivers, see 11.2 Properties in the OpenCorePkg Docs
Kexts
Please refer to Kexts.md for a full list of supported kexts
SSDTs
So you see all those SSDTs in the AcpiSamples folder and wonder whether you need any of them. Well we’ll be going over a couple to see whether you need them. Do note you’ll need to compile these SSDTs with MaciASL and please read them before compiling. Some require you to adjust them for your specific system(ie: EC0 to H_EC for SSDT-EC-USBX)
SSDT-AWAC This is the 300 series RTC patch, needed for certain Z390 systems. SSDT-RTC0 Alternative to SSDT-AWAC when not compatible with your system. SSDT-EC-USBX Needed to setup USB power and such correctly, prefered option over renaming XHCI. This SSDT is meant for Skylake+ systems, please use SSDT-EC and SSDT-EHCx_OFF for older systems. SSDT-EC Needed to setup USB power correctly on pre-skylake systems. SSDT-EHCx_OFF Prefered alternative over renaming EHCI for setting up USB correctly on pre-skylake systems. SSDT-PLUG Sets PluginType, Clover altrenative would be under Acpi -> GenerateOptions -> PluginType. Do note that this SSDT is made for systems where AppleACPICPU attaches CPU0, though some systems have theirs starting at PR00 so adjust accordingly. SSDT-SBUS-MCHC Adds a SMbus device and fixes DeviceProperties injection via _DSM which is found in your DSDT table. Most can ignore. USB drive formatted as MacOS Journaled with GUID partition map. This is to test opencore without overwriting your working Clover. Knowledge of how a hackintosh works and what files yours requires. A previously setup and functioning hackintosh is assumed: which you are happy to potentially break. Time and patience. Without these, you are wasting your effort. *Sign out of all apple services until you are sure you have MLB and ROM sections of smbios set to match your previous Clover set up. Not doing so could cause said services to cease to function, or worst case block your machine.
InsanelyHack-Discord If you need any extra help join our discord.
Pavo’s OCBuilder Creates a Basic EFI Structure with Basic Kexts which are needed to Boot XCODE App is required
Creating the USB
Creating the USB is simple, format a USB stick (any size will suffice) as MacOS Journaled with GUID partition map.
Formatting the USB
Next, mount the EFI partition on the USB with either diskutil terminal command or Clover Configurator.
mountEFI
By default, the EFI partition will be empty.
EFI folder structure
To setup OpenCore’s folder structure, copy the files from OpenCorePkg so your EFI looks like the one below:
|--EFI | |--BOOT | | |--BOOTx64.efi | |--OC | | |--ACPI | | |--Drivers | | | |--ApfsDriverLoader.efi | | | |--AppleGenericInput.efi | | | |--AppleUiSupport.efi | | | |--FWRuntimeServices.efi | | | |--UsbKbDxe.efi | | | |--VBoxHfs.efi | | | |--VirtualSmc.efi (Filevault Only)) | | |--Kexts | | | |--AppleALC.kext | | | |--CPUFriend.kext | | | |--Lilu.kext | | | |--SMCBatteryManager.kext (Laptop) | | | |--SMCLightSensor.kext (Laptop) | | | |--SMCProcessor.kext | | | |--SMCSuperIO.kext | | | |--VirtualSMC.kext | | | |--WhateverGreen.kext | | |--OpenCore.efi | | |--Tools | | | |--CleanNvram.efi | | | |--Shell.efi | | | |--VerifyMsrE2.efi
Place necessary .efi drivers from AppleSupportPkg and AptioFixPkg into the drivers folder, then kexts/ACPI into their respective folders.
Setting up the config.plist
While sharing the name, the config.plist in OpenCore, is very different from Clover config.plist, they cannot be mixed and matched. It is also not recommended to duplicate every patch and option from your clover config.
First, duplicate the sample.plist, rename it to config.plist and open in your .plist editor of choice.
The config contains a number of sections:
ACPI: This is for loading, blocking and patching the ACPI. Booter UEFI modifications on Apple bootloader (boot.efi). DeviceProperties: This is where you’d inject PCI device properties or set Intel Framebuffer. Kernel: Where we tell OpenCore what kexts to load, what order to load and which to block. Misc: Settings for OpenCore’s boot loader itself. NVRAM: This is where we set certain NVRAM properties like boot flags and SIP. Platforminfo: This is where we setup your SMBIOS. UEFI: UEFI drivers and related options. We can delete #WARNING -1 and #WARNING -2 You did heed the warning didn’t you?
- ACPI
Add: Here you add your SSDTs or custom DSDT. (SSDT-EC.aml for example)
Block: Certain systems benefit from dropping some acpi tables, most modern desktops however require nothing in this section.
Patch: In OpenCore we should be keeping ACPI device renames to a minimum as they are often harmful and unnecessary. If your system absolutely needs something, you should add it in this section. Refer to configuration.pdf.
For those who need DSDT patches for things like XHC controllers can utilize the SSDT-EC-USBX.dsl or use similar Device Property patching like what’s seen with Framebuffer patching And to grab the location of such devices can use gfxutil.
Example, common device renames are handled now by WhateverGreen on-the-fly and in a safer way: GFX0 to IGPU HECI to IMEI Do NOT do these in the config.plist nor in DSDT/SSDT.
Do NOT rename EC0 to EC as this can cause an incompatible kext (AppleACPIEC) to load and cause strange issues at any time or a non bootable system. For those who utilize 300 series RTC patch can use the SSDT-AWAC.dsl.
Quirks:
FadtEnableReset: NO Enable reboot and shutdown on legacy hardware, not recommended unless needed NormalizeHeaders: NO Cleanup ACPI header fields, only relevant for macOS High Sierra 10.13 RebaseRegions: NO Attempt to heuristically relocate ACPI memory regions, not needed unless custom DSDT is used. ResetHwSig: NO Needed for hardware that fail to maintain hardware signature across the reboots and cause issues with waking from hibernation ResetLogoStatus: NO Workaround for OEM Windows logo not drawing on systems with BGRT tables.
- Booter
This section allows to apply different kinds of UEFI modifications on Apple bootloader (boot.efi). The modifications currently provide various patches and environment alterations for different firmwares. Some of these features were originally implemented as a part of AptioMemoryFix.efi, which is no longer maintained. NOTES:
Most up-to-date UEFI firmware (check your motherboard vendor website). Fast Boot and Hardware Fast Boot disabled in firmware settings if present. Above 4G Decoding or similar enabled in firmware settings if present. Note, that on some motherboards (notably ASUS WS-X299-PRO) this option causes adverse effects, and must be disabled. While no other motherboards with the same issue are known, consider this option to be first to check if you have erratic boot failures. DisableIoMapper quirk enabled, or VT-d disabled in firmware settings if present, or ACPI DMAR table dropped. No ‘slide‘ boot argument present in NVRAM or anywhere else. It is not necessary unless you cannot boot at all or see No slide values are usable! Use custom slide! message in the log. CFG Lock (MSR 0xE2 write protection) disabled in firmware settings if present. Cconsider patching it if you have enough skills and no option is available. See VerifyMsrE2 nots for more details. CSM (Compatibility Support Module) disabled in firmware settings if present. You may need to flash GOP ROM on NVIDIA 6xx/AMD 2xx or older. Use GopUpdate or AMD UEFI GOP MAKER in case you are not sure how. EHCI/XHCI Hand-off enabled in firmware settings only if boot stalls unless USB devices are disconnected. VT-x, Hyper Threading, Execute Disable Bit enabled in firmware settings if present. While it may not be required, sometimes you have to disable Thunderbolt support, Intel SGX, and Intel Platform Trust in firmware settings present. Booter Quirks
AvoidRuntimeDefrag: YES Fixes UEFI runtime services like date, time, NVRAM, power control, etc DevirtualiseMmio: NO Reduces Stolen Memory Footprint, expands options for Slide=N values but may not be ompatible with all boards. Generally useful for APTIO V firmwares(Broadwell+) DisableSingleUser: NO Disables use of Cmd+S and -s, this is closer to the behaviour of T2 based machines DisableVariableWrite: NO Needed for systems with non-functioning NVRAM like Z390 and such DiscardHibernateMap: NO Reuse original hibernate memory map, only needed for certain legacy hardware EnableSafeModeSlide: YES Allows for slide values to be used in Safemode EnableWriteUnprotector: YES Removes write protection from CR0 register during their execution ForceExitBootServices: NO Ensures ExitBootServices calls succeeds even when MemoryMap has changed, don’t use unless necessary) ProtectCsmRegion: NO Needed for fixing artifacts and sleep-wake issues, AvoidRuntimeDefrag resolves this already so avoid this quirk unless necessary ProvideCustomSlide: YES If there’s a conflicting slide value, this option forces macOS to use a pseudo-random value. Needed for those receiving Only N/256 slide values are usable! debug message SetupVirtualMap: YES Fixes SetVirtualAddresses calls to virtual addresses ShrinkMemoryMap: NO Needed for systems with large memory maps that don’t fit, don’t use unless necessary MmioWhiteList: Designed to be filled with plist dict values, describing addresses critical for particular firmware functioning when DevirtualiseMmio quirk is in use. See MmioWhitelist Properties section below. MmioWhitelist Properties
Exceptional MMIO address, which memory descriptor should be left virtualised (unchanged) by DevirtualiseMmio. This means that the firmware will be able to directly communicate with this memory region during operating system functioning, because the region this value is in will be assigned a virtual address. *The addresses written here must be part of the memory map, have EfiMemoryMappedIO type and EFI_MEMORY_RUNTIME attribute (highest bit) set. To find the list of the candidates the debug log can be used. Fixing Certain NVRAM Issues
AvoidRuntimeDefrag : Set to YES for Enabled NVRAM Reading.
EnableWriteUnprotector : Set to YES for Enabled NVRAM Writing.
NVRAM read tests should display the NVRAM information in the Hackin tool/NVRAM correctly. NVRAM write testing shall ensure that the starting disk was correctly. (Default name was must be Macintosh HD) Tested on Asus X299, Z370M-Plus II, and Gigabyte Z370 AORUS Gaming 5 and 7. This feature is based on an OpenCore 0.0.4 08082018 distribution and works with the FwRuntimeService.efi driver.
- DeviceProperties
Add: Sets device properties from a map.
This section is set up via Headkaze’s Intel Framebuffer Patching Guide and applies only one actual property to begin, which is the ig-platform-id. The way we get the proper value for this is to look at the ig-platform-id we intend to use, then swap the pairs of hex bytes.
If we think of our ig-plat as 0xAABBCCDD, our swapped version would look like DDCCBBAA
The two ig-platform-id’s we use are as follows:
0x3E9B0007 - this is used when the iGPU is used to drive a display 07009B3E when hex-swapped 0x3E920003 - this is used when the iGPU is only used for compute tasks and doesn’t drive a display 0300923E when hex-swapped Worth noting that for 10.12 -> 10.13.5, you would need to fake the iGPU to the same values in the Kaby Lake guide, as this was before native Coffee Lake iGPU showed up.
We also add 2 more properties, framebuffer-patch-enable and framebuffer-stolenmem. The first enables patching via WhateverGreen.kext, and the second sets the min stolen memory to 19MB. This is usually unnecessary, as this can be configured in BIOS.
I added another section as well that shows a fake device-id for the i3-8100’s UHD 630. This has a different device id than the UHD 630 found on the 8700k, for instance, (3e918086 vs 3e928086 ).
For this - we follow a similar procedure as our above ig-platform-id hex swapping - but this time, we only work with the first two pairs of hex bytes. If we think of our device id as 0xAABB0000, our swapped version would look like 0xBBAA0000. We don’t do anything with the last 2 pairs of hex bytes.
The device-id fake is set up like so:
0x3e920000 - this is the device id for the UHD 630 found on an 8700k 923e0000 when hex swapped Note: FakeID is only required for High Sierra, Mojave doesn’t require this
PciRoot(0x0)/Pci(0x1f,0x3) -> Layout-id
Applies AppleALC audio injection, you’ll need to do your own research on which codec your motherboard has and match it with AppleALC’s layout. AppleALC Supported Codecs. Keep in mind that some motherboards have different device locations, you can find yours by either examining the device tree in IOReg or using gfxutil. Please note that ADR for HDAS/HDEF is 0x001F0003 and Path = PciRoot(0x0)/Pci(0x1f,0x3), PciRoot(0x0)/Pci(0x1b,0x0) is for previous series
Do note that layout-id is a Data value meaning you will need to convert from Number to HEX so Layout=5 would be interpreted as <05000000> and Layout=11 would be <0B000000>
Fun Fact: The reason the byte order is swapped is due to Endianness, specifcally Little Endians that modern CPUs use for ordering bytes. The more you know!
Block: Removes device properties from map, for us we can ignore this
- Kernel
Add: Here we can specify kexts to inject from our EFI into the kernel kextcache. Order of kexts is important, they are loaded in this order. Plugins for other kexts should always come after the main kext. Lilu should be first, then Lilu plugins like WhateverGreen and VirtualSMC.
BundlePath Name of the kext ex: Lilu.kext Enabled Self explaitroy, either enables or diables the kext Executableath Path to the actual executable hidden within the kext, you can see what path you kext has by right clicking and selecting Show Package Contents. Generally they’ll be Contents/MacOS/Kext but some have kexts hiddin within under Plugin folder. Do note that Plist only kexts do not need this filled in. ex: Contents/MacOS/Lilu PlistPath Path to the info.plist hidden within the kext ex: Contents/Info.plist Emulate: Needed for spoofing unsupported CPUs like Pentiums and Celerons
CpuidMask: When set to Zero, original CPU bit will be used