All Activity

Once OCLP is updated for Tahoe, it should be good too.

Updated for 2025.

Restoring support for dropped GPUs in macOS Tahoe. Tahoe did not drop additional GPUs. As such, the same patches that applied to Ventura, Sonoma and Sequoia can be expected to apply to Tahoe. OCLP will require updating for Tahoe. Meantime, for Skylake iGPUs, the same good old patches cab ne applied to obtain full graphics acceleration in Tahoe, i.e. fake KBL graphics.

Updated following the release of macOS Tahoe 1st beta.

kext for macos tahoe, without use bootarg beta WhateverGreen-1.7.0-RELEASE.zipVirtualSMC-1.3.7-RELEASE.zipRestrictEvents-1.1.6-RELEASE.zipNVMeFix-1.1.3-RELEASE.zipLilu-1.7.1-RELEASE.zipFeatureUnlock-1.1.8-RELEASE.zipDebugEnhancer-1.1.1-RELEASE.zipCryptexFixup-1.0.5-RELEASE.zipCPUFriend-1.3.0-RELEASE.zipAppleALC-1.9.5-RELEASE.zipECEnabler-1.0.6-RELEASE.zipNootRX-1.0.0-RELEASE.zipIntelBTPatcher.kext.zipBlueToolFixup.kext.zipRealtekCardReaderFriend_1.0.4__RELEASE.zipHibernationFixup-1.5.4-RELEASE.zip

List of dropped platforms for this last Intel-compatible macOS version extends to 8th gen. Coffee Lake Macs and 10th gen. Ice Lake MacBookAir9,1. Surprisingly, good news again for Skylake platforms, given that KBL graphics drivers are again retained. As such, SKL graphics remain supported through the same patches used for Ventura, Sonoma and Sequoia. On the wireless front, OCLP patcher will need to be updated for Tahoe so that legacy Broadcom cards are supported again. Users will notice a very different graphics design, from the Finder's bar to the shape & look of the Windows and the file icons. And kexts for USB ports mapping won't work but patched ACPI table SSDT-UIAC does so use that meantime. It can easily be generated with tools such as Hackintool for instance. Installation on my Skylake Latitude E7270 was fairly straightforward once I had the right commit of Clover r5162: from Sequoia, I updated Clover to attached version revised to boot Tahoe, changed my Clover config's SMBIOS to MBP16,2 (necessary), disabled the BlockSkywalk kernel & kext patch (necessary) and updated Lilu & Plugins and other kexts to the versions provided by @Lorys89 here and at InsanelyMac (to avoid using boot arg -lilubetaall). I then rebooted Sequoia, downloaded the Tahoe beta installation package (though software update) and launched the installation targeting a dedicated Tahoe volume (previously created in Disk Utility). That was it and, after a couple of reboots, I was offered the Tahoe setup screens and reached the Tahoe desktop. Resources: Tahoe beta 1 installation package can be downloaded here. Clover_r5162.pkg.zip E7270_Clover_Pack_Tahoe_26.0.b1.zip Working from the onset: graphics acceleration with same KBL settings as in Ventura/Sonoma/Sequoia brightness control HDMI output mini-DP output touchscreen touchpad audio (incl. DP/HDMI audio) LAN Apple (Broadcom) BCM94360CS2 Bluetooth USB ports SD card reader full CPU power management sleep & wake (having disabled hibernation) Not working: Apple (Broadcom) BCM94360CS2 wireless, as per Sonoma and Sequoia. We'll have to wait for the OCLP patcher to be updated for Tahoe. Meantime, it's important not to boot with the BlockSkywalk kernel & kext patch and/or with AMFI prevention or Tahoe will KP/fail to boot. Some bugs here and there. Graphics not entirely stable.

WWDC Keynote, June 9th, 2025. Apple unveiled macOS 26 Tahoe. As usual, 1st beta version was immediately made available to developers and 1st public beta will be available in July with a final release in the fall. The major novelty is Liquid Glass that replaces Aqua. And the version numbering, of course, which Apple will now unify across the board (macOS, iOS, etc.). As expected, this is the very last macOS version to support Intel platforms; it will therefore put the final nail in the coffin of Hackintoshing on Intel platforms; after nearly 20 years, it will have been a good run! Tahoe drops support for all systems older than 9th gen. Coffee Lake, 10th gen. Comet Lake/Ice Lake and Cascade Lake platforms, i.e. those 8th gen. Coffee Lake MacMini8,1/MacBookPro15,x/iMac19,x and Skylake iMacPro1,1 that had remained supported in Sequoia. Surprisingly, 10th gen. Ice Lake MacBookAir9,1 laptops appear dropped too but, given that 2020 ICL-based MBP16,2 remain supported, those last Intel MBA should nevertheless be able to run Tahoe too -to be confirmed-. Minimum Intel platform requirements are therefore: iMac20,x (10th gen. Comet Lake) MacBookPro16,1 (9th gen. Coffee Lake) MacBookPro16,2 (10th gen. Ice Lake) MacPro7,1 (Cascade Lake) View full article

I somehow ended up on the BrcmPatchRAM.kext release page again and saw the change log for version 2.7.0 saying, "Improved performance on macOS 15+ by disabling incompatible patches". That got me wondering if my card was affected. I replaced BrcmPatchRam.kext with version 2.6.9 and reset NVRAM, and my Bluetooth back. Not too sure if it’s supposed to show up as a third-party dongle, though, but at least it works. AirDrop remains limited as it started from Monterey: it only works reliably from my iPhone to my Mac. If I want to send something from my Mac to my iPhone, I actually need another iPhone nearby, set to discover others for AirDrop to work both ways.

Check whether Bluetooth is enabled or not in your BIOS settings. Could be disabled given that the MAC address of your module is not detected. No other Wifi/BT device in your E6440 that could interfere, right?

BlueToolFixup replaces BrcmBluetoothInjector for macOS 12+. According to their docu, BlueToolFixup also supports 413c:8143 devices. Both bluetooth* NVRAM properties are from the same page. Others suggested it worked for them with DW1560 cards so I thought to give it a go, but it's doesn't work for me.

Hello, it's been some time since I last used a non-Apple Wifi/BT card but I noticed the 2 following elements in your OC config file. You don't inject the Bluetooth injector kext, having limited this to macOS Big Sur (20.9.9). Are you certain you don't need it? The BT chip used on the DW1550 is clearly present in the injector: <key>413c_8143</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport</string> <key>IOClass</key> <string>BroadcomBluetoothHostControllerUSBTransport</string> <key>IOProbeScore</key> <integer>3000</integer> <key>IOProviderClass</key> <string>IOUSBHostDevice</string> <key>idProduct</key> <integer>33091</integer> <key>idVendor</key> <integer>16700</integer> </dict> What does this NVRAM property do?

Hi, I'm trying to get Bluetooth (DW1550) working on macOS Sequoia 15.5 on my E6440. I followed Wifi in Sonoma & later: Patching for legacy Broadcom wireless cards and got WiFi working. However, BT shows up in system information but won't allow me to toggle it on from the menu bar. EFI.zip For context: - Install macOS using system product name MacBookPro15,2 - After initial device setup, reboot and reset NVRAM - Boot using system product name MacBookPro11,1 - Run OCLP to fix graphics and networks Any idea what I'm missing?

Released May 12th, 2025. Build 24F74. Bug fixes and security update. Safe to install on our Hackintosh platforms. Also released at the same time: macOS Sonoma Security Update 14.7.6 (Build 23H626) macOS Ventura Security Update 13.7.6 (Build 22H625) View full article

Not a guide! -> moved to support section. A zipped copy of your OpenCore EFI folder with indication of the OpenCore version you use would be useful.

Hi, I am trying to install Monterey on a X1 Carbon 7th Gen model 20R1 with a i7-10710 processor, but stuck at EXITBS:START. I have tried with a USB boot disk created by following the guide on Dortania, and also tried with the EFI for Lenovo X1C8 posted on this site (similar spec to my X1C7) to no avail. Any suggestion is appreciated. I have included the X1C8 config file as reference. config.plist.zip

yes, I have two disks, but the second disk is not visible in Mac OS, I still couldn't patch it, it is not displayed in BIOS, I tried to swap them, tried to see it through Windows and through Ubuntu, the same result everywhere. Most likely you are right and the disk itself is out of order, I will try to update the firmware on it. thanks for your help

Is the disk visible in BIOS Setup? DU should show all disks, no matter the partitioning/contents. Maybe your SSD has gone faulty and that's what caused the OpenCore error rather than the other way round. I take it that your E6430 is fitted with 2 disks: one in the usual SATA slot and the other in the modular bay, right? If so, maybe you can try to swap them around to check things out. Then, it'll depend on which one carried the bootstrap of course. If I remember correctly, disks fitted into the modular bay required a patch of some sort to be seen in OS X/macOS.

The Ventura partition is on an SSD drive that is not visible in the disk utility. OCLP suggested updating the version, then an error occurred and the message eject disk, after that the SSD drive is not visible. At the same time, I tried to update Ventura and there was also an update error. Thanks for any help

Where is your macOS Ventura partition supposed to be? On the internal disk labelled ST500LM021-1KJM52? What is shown/listed when you select that disk? It would also be most useful if you could list what you did in terms of actions re: "updating OCLP". Was it just the config file you modified or did you update your OpenCore and/or OCLP version?

Good day. Accidentally started updating oclp on config.plist mac os x Ventura, oclp gave an error and after rebooting I no longer see my ssd with mac os x Ventura through disk utility and have no access to it, what can I do about it?

Released March 31st, 2025. Build 24E248 Bug fixes and security update. Safe to install on our Hackintosh platforms. Also released at the same time: macOS Sonoma Security Update 14.7.5 (Build 23H527) macOS Ventura Security Update 13.7.5 (Build 22H527) View full article