Jump to content
228 posts in this topic

Recommended Posts

No need to update my HackBookPro16,2 since I had already applied the 26.2 RC update.  Just want to report that this hack continues to work perfectly.  I'm beginning to like Tahoe.  Feels good to know that this hack is going to be a solid laptop with the latest macOS for another year.  I'll reluctantly buy a new Mac in 2027 when I need Xcode support with macOS 27.

 

Screenshot2025-12-12at2_02_15PM.png.d36f32c208346d30465ebd5b19215894.png

 

EDIT: Same with my HackMini8,1s - outstanding, low-cost desktops that still run the latest macOS.   Much thanks to the OC and CLOVER devs who continue to make this possible.

 

EDIT2: To ease the burden of macOS Tahoe on my lightly-powered graphics, I enable the following in System Settings > Accessibility:

  • Display > Reduce Transparency
  • Motion > Reduce Motion
Edited by deeveedee
  • Like 5

Painless OTA update to macOS 26.2 (25C56) with WhateverGreen.kext 1.7.1d7 after reverting the OCLP 3.0.0 Nightly modern Wi-Fi and modern Audio root patches, removing boot-arg "amfi=0x80" and reenabling AMFIPass.kext. 

 

image.png.132ae2dce5bf0937ac4a128e8b2e8560.png

 

During the post installation, I added again boot-arg "amfi=0x80", disabled AMFIPass.kext and reapplied the OCLP 3.0.0 Nightly modern Wi-Fi and modern Audio root patches.

 

Everything works as expected.

 

image.png.ee542cb0e64c2dcdc511507bc963dd42.png

 

image.png.fb4445c573f4d7a3a82d72c19fce7615.png

 

image.thumb.png.cbff29d4bfb63e24aa87da3713cb6f35.png

 

Helpful links:

a.) EFI-Folder distribution

b.) Experimental Fork of OCLP 3.0.0 Nightly

c.) X299 Guidelines

Edited by KGP-iMacPro
  • Like 7
1 hour ago, KGP-iMacPro said:

...reenabling AMFIPass.kext...

 

...disabled AMFIPass.kext ...

 

Congrats on the upgrade!  Not trying to offend or challenge your expertise - just genuinely curious... Why re-enable and then disable AMFIPass.kext - especially if you're using amfi=0x80 for Experimental OCLP?

  • Like 2
8 hours ago, deeveedee said:

 

Congrats on the upgrade!  Not trying to offend or challenge your expertise - just genuinely curious... Why re-enable and then disable AMFIPass.kext - especially if you're using amfi=0x80 for Experimental OCLP?

 

I removed amfi=0x80 and enabled AMFIPass.kext only for the OTA update, as a precaution to avoid possible conflicts with amfi=0x80 during the update and for system consistency (com.apple.iokit.IOSkywalkFamily replacement). Honestly, I could have left AMFIPass.kext disabled, but I simply used the second EFI for Sequoia (OCLP 2.4.1), which is currently configured this way and does not differ in anything else. Before the OTA update, I anyway reverted the experimental OCLP 3.0.0 Nightly patches to allow the OTA update instead of the full installer. After completing the OTA update, and before reinstalling the experimental OCLP OCLP 3.0.0 Nightly patches, I booted again using the EFI for Tahoe, with amfi=0x80 and AMFIPass.kext disabled. I hope this unusual explanation satisfies your curiosity. 🙂

Edited by KGP-iMacPro
  • Like 4

Just for the sake of completeness and as there is no dedicated thread. 

 

Also flawless OTA update to Sequoia 15.7.3 (24G419)

 

image.png.7ca35b77ebee04bef8e22f5f82dc6e76.png

 

Wi-Fi works as expected using OCLP 2.4.1. However under 15.7.2 and 15.7.3, there are minor connectivity issues of IntelLucy 1.1.5, occasionally not connecting to Ethernet directly after boot, with or without AppleVTD enabled. At some point, however it always successfully connects to Ethernet and stays connected. I will mention this issue in the dedicated thread.

 

image.png.8c99bc0ca6395138afa0ee0d0411666c.png

 

Under Tahoe, IntelLucy 1.1.5 works flawlessly. 

 

If the post is inadequate in this thread, I ask the moderation to move it to the correct place. 

 

Edited by KGP-iMacPro
  • Like 2
11 hours ago, KGP-iMacPro said:

I hope this unusual explanation satisfies your curiosity. 🙂

 

In addition to the joy of collaboration with others in this forum and the thrill of victory over a difficult hack, the thing I like most about hackintoshing is learning something new.  I will definitely add this to my repertoire.  Thank you.  An old dog like me still hopes to learn something new every day. :)

Edited by deeveedee
  • Like 7

Smoothy update 26.1 to 26.2 on my Z390 machine 😊 In fact, always stuck at user login screen after entering session password. Wait and see...

I'm a nice boy. Please Santa Klaus bring me an Intel Ultra 9 285K with mobo etc  or Ryzen 9 9950X3D with top mobo, etc.... 😇

Edited by Matgen84
  • Like 1
  • Haha 1
46 minutes ago, Matgen84 said:

Smoothy update 26.1 to 26.2 on my Z390 machine 😊 In fact, always stuck at user login screen after entering session password. Wait and see...

I'm a nice boy. Please Santa Klaus bring me an Intel Ultra 9 285K with mobo etc  or Ryzen 9 9950X3D with top mobo, etc.... 😇

 

How about your gatekeeper status?

Still app moved after update?

31 minutes ago, Sherlocks said:

 

How about your gatekeeper status?

Still app moved after update?

 

I had disabled GateKeeper via Terminal command: sudo spctl --master-disable under macOS 26.1.
My Z390 machine is always stuck, so I  don't know if there are relocated Items. 🥲

6 hours ago, Slice said:

Sorry but the link to 22.11.2025 so it is 26.1 version.

HI Slice

 

It's strange : in 093-37361.English.dist content (part of below) it's really 26.2 (25C56)

 

Tahoe 26.2 25C56 (093-37361) English.dist
https://swcdn.apple.com/content/downloads/11/14/093-37361-A_NX0SMZC0LI/9slwkknt5xciy7bhd9ux9utct03e07j6qp/093-37361.English.dist
093-37361.English.dist content (part of)
...
    <auxinfo>
        <dict>
            <key>BUILD</key>
            <string>25C56</string>
            <key>VERSION</key>
            <string>26.2</string>
        </dict>
    </auxinfo>
...
 

 

In this Tahoe 26.2 installer "Content/SharedSupport/SharedSupport.dmg/com_apple_MobileAsset_MobileSoftwareUpdate_MacUpdateBrain/

com_apple_MobileAsset_MobileSoftwareUpdate_MacUpdateBrain.xml  content (part of) is

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>AssetType</key>
    <string>com.apple.MobileAsset.MobileSoftwareUpdate.MacUpdateBrain</string>
    <key>Assets</key>
    <array>
        <dict>
            <key>Build</key>
            <string>25C56</string>
            <key>OSVersion</key>
            <string>26.2</string>
            <key>TrainName</key>
            <string>CheerC</string>
            <key>_CompatibilityVersion</key>
            <integer>20</integer>
            <key>_CompressionAlgorithm</key>
            <string>zip</string>
            <key>_ContentVersion</key>
...

Regards

 

  • Like 2

I installed my newly ordered BCM943602CS (Only Mac) (0x14E4 0x43BA) Wifi/Bt card into my computer. When I disabled Bluetoolfixup kext to update OTA, I noticed that the BCM943602CS card does not need Bluetoolfixup kext to activate the bluetooth feature.

I also using my Broadcom BCM4350 (Win&Mac) 0x14E4 0x43A3 Wifi/Bt card plugged in in the other pci slot of my device. Mac naturally saw the BCM943602CS card and started using it. When I switch to the Windows operating system, it sees my BCM4350 Wifi/Bt card, so I started to use wifi and bluetooth cards on both windows and macs in this way.

 

Transactions;

1. Bluetoolfixup.kext has been disabled. (BCM943602CS card also works without using this kext. BCM4350 card needs this time.)

2. OCLP 3.0 patch is withdrawn.

3. The update was completed without any problems.

4. I did not activate the bluetoolfixup kextin because I used the BCM943602CS card.

5. With the OCLP 3.0 patch, AppleALC and Wifi became active again.

 

image.thumb.png.24d334da14bccabeea7e9d85731dc6af.png

 

image.png.deae3d9e172658bc1a00052ad3d7ea3f.png

Edited by HyperX7
  • Like 7

@KGP-iMacPro

OT:

As you know, DFI was originally a scriptingosx repo that stopped receiving updates and has been archived for some time. In my fork, and since I really liked the app, I continued updating it.

Six months ago, @matxpa added a large number of improvements to the code; it was probably the biggest leap forward in 2025. This is acknowledged in the credits.
He has far superior programming skills to mine and has followed modifying the app, but not publicly.
For my part, with the help of @chris1111, Copilot, and some other users, I've taken a different approach: simpler main window and options/preferences, adding improvements step by step (at least they are improvements to me). And it's available on GitHub, as you know.

This is the story of these three versions of DFI, one obsolete, one public and one private, although I'm sure @matxpa's code has enough interesting features to learn SwiftUI with.

 

Edited by miliuco
Typo
  • Like 7
  • Thanks 1
×
×
  • Create New...