Once you have reached the macOS desktop, you will need to mount your EFI partition to then copy over your EFI folder from your USB disk. Leave the USB plugged in as you will need to reboot from this a few times while macOS is installing Then you want to erase the drive and start the installation Once you have reached the installer, choose Disk Utility and then click on view and then show all devices It may look like it has frozen in some places, but boot from USB can be slow, so please be patient. Now, boot with your USB stick, the ist has verbose enabled so you can see what is going on. Your hack will not boot with CFG-Lock enabled)ĭVMT Pre-Allocated(iGPU Memory): 64MB or 128MB Thunderbolt(For initial install, as Thunderbolt can cause issues if not setup correctly)ĬFG Lock (MSR 0圎2 write protection)(This must be off, if you can't find the option then enable AppleXcpmCfgLock under Kernel -> Quirks. VT-d (can be enabled if you set DisableIoMapper to YES) You will want to make some changes here, if you can change these options: Once you have made those changes, save your ist and reboot your machine into your BIOS. This is currently set to MacBookPro13,1 which is for a Skylake laptop, read post 2 for configurations Then scroll further down until you find SystemProductName. (Making sure you have the correct kext in your kexts folder) Set csr-active-config to in your config.Building a CustoMac Hackintosh: Buyer's Guide.A SIP value which does not include the two flags above.csrutil disable -no-internal in Recovery.If you want to still have SIP disabled, use either: CSR_ALLOW_UNAUTHENTICATED_ROOT (Bit 11 = 0x800).CSR_ALLOW_APPLE_INTERNAL (Bit 4 = 0x10).Two bits in SIP specifically cause issues: Note: You do not need the -revsbvmm boot argument from RestrictEvents. More information is available on the Apple Secure Boot page (opens new window). If your SMBIOS does not have a T2 chip, then either Default or Disabled is ok. Hackintoshes which use a T2 SMBIOS MUST have OpenCore 0.7.4+ with SecureBootModel set to Default. non-T2 SMBIOS using j137 or iMacPro1,1 using j160). Starting with Monterey, updates are not delivered to T2 Macs which don't have Secure Boot enabled, and updates do not install properly if your SecureBootModel does not match your machine (ie. Monterey Beta 5+ issues (opens new window).If you still boot Big Sur or older, you can set the MinKernel field to 21.00.0 to prevent BlueToolFixup loading on older OSes.Needed for all non-native Bluetooth devices (Including Intel).BrcmPatchRAM2/3.kext + BrcmFirmwareData.kext for Broadcom. If you still boot Big Sur or older, you can instead set the MaxKernel field to 20.99.9 for your injector kext in your ist.BrcmBluetoothInjector.kext for Broadcom cards.IntelBluetoothInjector.kext for Intel cards.With the rewrite, injector kexts break bluetooth support in Monterey, though firmware uploader kexts are still needed. As of writing, many bluetooth devices do not work (legacy Broadcom and Intel). With Monterey, Apple has completely rewritten the bluetooth stack. Note that all cards have not been fixed yet, and that bluetooth support is being worked on still.ĭo not be suprised if your card does not work, and please be patient! For example, an 8-Core 5800X would have the new Replace value be:Ĭore Count => Hexadecimal Table Core Count Where is replaced with the physical core count of your CPU in hexadecimal. The patches which need to be edited are all named algrey - Force cpuid_cores_per_package, and you only need to change the Replace value. Haswell iGPUs are still supported in Montereyįor those on AMD CPUs, make sure to update your kernel patches (opens new window) for Monterey.ĭon't forget to update your patches as well with the core count of your CPU.
0 Comments
Leave a Reply. |