miliuco Posted September 5 Share Posted September 5 (edited) Preface Sonoma required fewer changes to OpenCore and kexts than were necessary to install older systems such as Big Sur, which was a big challenge for developers. This time, minor changes allowed Sonoma to be installed almost immediately after the first beta version was released. Of course, there have been problems to work hard on, not all solved as of today. For now I will note the loss of Wi-Fi with Broadcom chipsets used in Mac models before 2017 and in Fenvi PCI-e cards, widely used in Hackintoshes. A fix has been provided by the OCLP team. Hardware Motherboard Gigabyte Z390 Aorus Elite CPU Intel i9-9900K GPUs: iGPU Intel UHD 630 / AMD Radeon RX 6600 XT Audio Realtek ALC1220 Ethernet Intel I219V7 Wi-Fi + BT Fenvi FV-T919 (BCM94360CD). BIOS settings (F10h version) CFG Lock: Disabled CSM: Disabled VT-d: Disabled Fast Boot: Disabled OS Type: Windows 8/10 WHQL Platform Power Management: Disabled XHCI Hand-Off: Enabled Network Stack: Disabled Wake on LAN: Disabled Secure Boot: Disabled Integrated Graphics: Enabled DVMT Pre-allocated: 256M o higher. What works well? dGPU AMD as main card iGPU in headless mode Shutdown, restart and sleep Ethernet Sound (also HDMI) USB ports (USB port map for this board) Bluetooth Fenvi T919. What's not working well? Fenvi T919 Wi-Fi: macOS Sonoma has dropped support for all Broadcom Wi-Fi present on Macs before 2017. Fenvi T919 and HB1200 have BCM4360 chipsets (not supported) so Wi-Fi does not work in Sonoma. Bluetooth works fine. This is a serious inconvenience because functions related to the Apple ecosystem (Airdrop, Continuity Camera, etc.) are also lost. A fix is proposed later. Installing macOS Sonoma I have updated macOS Ventura to Sonoma but creating USB boot media to install from scratch is another option for those who prefer to do it that way. It is advisable to have macOS 13.4 Ventura or later System Settings >> Software Update >> Beta Updates >> click on the info icon >> Disabled Choose macOS Sonoma 14.0 Or get the app from App Store. To create the USB installation media so you can install Sonoma from scratch: Get the complete installation package from Apple's servers. I use the app Download Full Installer (original by scriptingosx), main window shows all versions available for download from Big Sur to Sonoma. Spoiler The package is downloaded as InstallAssistant-14.0-build.number.pkg, double click on the package to generate Install macOS Sonoma.app in the Applications folder Format a USB stick of at least 16Gb with GUID partition scheme and Mac OS Plus (journaled) format, name it (e.g. USB) Open Terminal and run this command sudo /Applications/Install\ macOS\ Sonoma.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --no-interaction At the end, you can reboot from the USB device and begin Sonoma installation. OpenCore and EFI folder Update OpenCore and extensions to Sonoma compatible versions. OpenCore, at least version 0.9.4. Settings used with macOS Ventura may work with macOS Sonoma. Updating OpenCore and kexts, there are no significant changes to the config.plist file, which may be the same for both systems. For the update to be successful, 2 parameters in config.plist related to security must be adjusted: SecureBootModel=Default or x86legacy (Apple Secure Boot as Default sets the same model as in SMBIOS and x86legacy is designed for SMBIOS that lack T2 chip and virtual machines) SIP enabled (csr-active-config=00000000). It is advisable to have Gatekeeper enabled (sudo spctl –master-enable in Terminal). These security options can be changed after installation as they are not required out of updating macOS. Note: in last versions of Ventura, sudo spctl –master-enable (or disable) has been replaced by sudo spctl –global-enable (or disable). For now, both commands work fine. config.plist I get best results with iMac19.1 SMBIOS and the iGPU enabled in BIOS. These are the main details when configuring config.plist. ACPI ACPI: SSDT-EC-USBX.aml, SSDT-PLUG.aml and SSDT-PMC.aml. SSDT-AWAC.aml is not required on my system but, if in doubt, add it because it does not cause any harm if it is present without being needed ACPI >> Quirks: all = False Booter Booter >> Quirks: AvoidRuntimeDefrag, DevirtualiseMmio, ProtectUefiServices, ProvideCustomSlide, RebuildAppleMemoryMap, SetupVirtualMap and SyncRuntimePermissions = True Booter >> ResizeAppleGpuBars=-1 DeviceProperties >> Add PciRoot(0x0)/Pci(0x2,0x0) AAPL,ig-platform-id | Data | 0300913E device-id | Data | 9B3E0000 enable-metal | Data | 01000000 rps-control | Data | 01000000 PciRoot(0x0)/Pci(0x1.0x0)/Pci(0x0.0x0)/Pci(0x0.0x0)/Pci(0x0.0x0) unfairgva | Number | 6 PciRoot(0x0)/Pci(0x1F,0x3) layout-id | Data | 07000000 PciRoot(0x0)/Pci(0x14,0x0) acpi-wake-type | Data | 01 acpi-wake-gpe | Data | 6D Kernel Kernel > Add: Sonoma compatible kexts, Lilu.kext in the first place, UTBMap.kext specific for this motherboard Kernel >> Quirks: CustomSMBIOSGuid, DisableIoMapper, DisableIoMapperMapping, DisableLinkeditJettison, PanicNoKextDump and PowerTimeoutKernelPanic = True Kernel >> Quirks: SetApfsTrimTimeout = 0 Misc Misc >> Boot: HibernateMode=None, PickerAttributes=144, PickerVariant=Default, ShowPicker=True Misc >> Debug: AppleDebug, ApplePanic and DisableWatchDog = True, Target=3 Misc >> Security: AllowSetDefault=True, BlacklistAppleUpdate=True, ExposeSensitiveData=6, SecureBootModel=x86legacy or Default NVRAM WriteFlash=True Add >> 7C436110-AB2A-4BBB-A880-FE41995C9F82: boot-args >> agdpmod=pikera csr-active-config >> 00000000 run-efi-updater >> No Delete >> 7C436110-AB2A-4BBB-A880-FE41995C9F82: boot-args and csr-active-config PlatformInfo Generic >> iMac19.1 UpdateDataHub, UpdateNVRAM and UpdateSMBIOS = True UpdateSMBIOSMode >> Custom UEFI UEFI >> Quirks: EnableVectorAcceleration and RequestBootVarRouting = True UEFI >> Quirks >> ResizeGpuBars=-1. Notes about software updates There are 3 SMBIOS that I can use on my PC: iMac19,1 / iMacPro1,1 / MacPro7,1. My favorite is iMac19.1. Regarding the updates that are notified in Software Update and the size of the update (full or incremental package), there are some conditions to take into account. About obtaining Update notification iMac19.1 model (2019 iMac 27″) lacks a T2 security chip and, when using this SMBIOS model, you receive update notifications iMacPro1,1 (iMac Pro 27″, late 2017) and MacPro7,1 (Mac Pro 2019) models do have a T2 chip and, when using these SMBIOS models, you do not receive update notifications iMacPro1,1 and MacPro7,1 models receive update notifications if configured as vmm (virtual machine): revpatch=sbvmm in boot-args along with RestrictEvents.kext. About the size of the update (full or incremental) Systems where the OCLP root patch has not been applied or has been reverted: - iMac19,1 can get incremental updates - iMacPro1,1 and MacPro7,1 require revpatch=sbvmm in boot-args along with RestrictEvents.kext to get incremental updates, without this setting you get full update packages All systems that have the OCLP root patch applied receive full-size updates. In summary, using iMac19.1 you get update notifications but the updates are full size. After the system is updated, RestrictEvents.kext and the boot argument can be disabled because they are not required for normal Sonoma operation. Broadcom Wi-Fi stops working in Sonoma Apple has dropped support for Broadcom Wi-Fi chipset drivers used in pre-2017 Macs: Dependant of AirPortBrcmNIC.kext (IO80211FamilyLegacy.kext plugin) device-id pci12e4,43ba >> BCM43602 device-id pci12e4,43e3 >> BCM4350 device-id pci12e4,43a0 >> BCM4360 Dependant of AirPortBrcm4360.kext (IO80211Family.kext plugin) device-id pci12e4,4331 >> BCM94331 device-id pci12e4,4353 >> BCM943224. Many users including myself have used Fenvi T919 or Fenvi HB1200 PCI-express cards (Wi-Fi + Bluetooth combo) which have worked since at least High Sierra OOTB, without the need for additional drivers, automatically installed by macOS and recognized as Airdrop and Bluetooth by macOS. The 2 Fenvi cards have the BCM4360 Wi-Fi chipset so they have stopped working in Sonoma. Bluetooth works well, as in Ventura and earlier. I have already commented that this is a serious inconvenience because the features associated with the Apple ecosystem are lost: Airdrop, Continuity, iPhone camera... As extra information, Macs that can officially update to Sonoma have these Broadcom Wi-Fi: 2017 iMacPro1,1 / 2018/2019 MacBookAir8,x -> BCM4355 (pci14e4,43dc) 2018 MacMini8,1 / 2018/2019 MacBookPro15,x / 2019 iMac19,x / 2019 MacPro7,1 / 2019/2020 MacBookPro16,x / 2020 iMac20,x -> BCM4364 (pci14e4,4464) 2020 MacBookAir9.1 -> BCM4377b (pci14e4.4488). They are chipsets soldered on the board that are not sold loose on the market and we cannot got them to install a Wi-Fi compatible with Sonoma in our Hack. Get back Fenvi Wi-Fi in Sonoma OCLP developers have been working on this issue and have released a Sonoma-specific OCLP 0.6.9 beta that makes Wi-Fi work again like it did in Ventura. I know it is not the ideal situation, many of us want to have the system as similar as possible to a real Mac and OCLP has to apply root patches that force it to work by relaxing some macOS security rules. But what the OCLP team has achieved is a very big advance. You have the instructions in this post (look for the Hackintosh notes section): Early preview of macOS Sonoma support now available! To download the most recent version of this Sonoma-specific OCLP beta branch, look for the link with this text: Latest builds for the sonoma-development branch can be found below: Nightly.link: OpenCore-Patcher.app (Sonoma Development). Note: OCLP developers prefer that we download OCLP beta from the link they post, for this reason I do not put a direct link here. It is a way to take users to the original post so that it can be read, which is highly recommended. In summary, this is what to do: System Integrity Protection disabled: csr-active-config=03080000 AMFI disabled: boot-args = amfi=0x80 Secure Boot Model = Disabled Block com.apple.iokit.IOSkywalkFamily, setting MinKernel to 23.0.0 to ensure the patch is applied only in Sonoma Inject 3 extensions (Kexts folder and config.plist): IOSkywalk.kext, IO80211FamilyLegacy.kext and AirPortBrcmNIC.kext (IO80211FamilyLegacy.kext plugin) in this order, setting MinKernel to 23.0.0 to ensure they are injected only in Sonoma Reboot and apply OCLP root patch (Modern Wireless Network). My Wi-Fi is Fenvi T919 so I have tried this pre-release version of OCLP 0.6.9. I have followed the instructions TO THE LETTER and they have worked well. I have Wi-Fi and Airdrop in Sonoma. Please note that khronokernel instructions must be followed EXACTLY. In short, this version of OCLP 0.6.9 beta works, at least for me. Spoiler Don't forget to enable (Enabled=True) the 3 added extensions and the blocked extension. Important: com.apple.iokit.IOSkywalkFamily block must have Enabled=True and Strategy=Exclude. Otherwise, you may have kernel panic at boot. Incremental updates are lost with this configuration, updates can be notified from Software Update but the full installation package is downloaded and not the delta package that only contains changes from the previous version. To obtain incremental updates you have to revert the OCLP root patch and restart but you lose Wi-Fi, keep this in mind if you depend on it to have Internet access, in this case do not revert root patch before proceeding with the update. Note: After updating, you must ALWAYS reapply root patch since macOS overwrites the files modified by the patch, installing the original versions. Note: OCLP has added basic support for 3rd party Broadcom chipsets, not officially supported as never shipped in any official Mac but supported by AirportBrcmFixup, these chipsets are used in Hackintoshes: device-id pci12e4,4357 >> BCM43225 device-id pci12e4,43B1 >> BCM4352 device-id pci12e4,43B2 >> BCM4352 (2.4 GHz). AMFI and AMFIpass.kext AMFI (Apple Mobile File Integrity) was originally seen on iOS but migrated to macOS in 10.12 Sierra, possibly in 2012 when GateKeeper and digitally signed code were introduced. In short, it is a technology that blocks the execution of non signed code. It consists of 2 components: the /usr/libexec/amfid service run as root from /System/Library/LaunchDaemons/com.apple.MobileFileIntegrity.plist the extension /System/Library/Extensions/AppleMobileFileIntegrity.kext. AMFI must be enabled to grant third-party applications access to privacy-relevant services and/or peripherals, such as external cameras and microphones. But, with SIP and/or AMFI disabled (a necessary condition to apply OCLP root patches) the dialog box to grant access to those applications is not shown to the user so those peripherals simply cannot be used in applications like Zoom or MS Teams, for example. AMFI is usually enabled but it has already been seen that OCLP root patches require disabling AMFI and SIP in order to be applied. To avoid the problem of peripherals not working with third-party applications, the OCLP team has developed the AMFIPass.kext extension that allows AMFI to be enabled when the system must operate with AMFI and SIP disabled, such as when using OCLP or applying root patches. This fixes the permissions issue and OCLP can apply the patches as if AMFI were disabled. If macOS has previously given permissions to these third-party applications and then AMFI and/or SIP is disabled, these permissions are transferred and the new system maintains them. But in a clean installation they do not exist. This is the main problem that AMFIPass.kext tries to solve. Being able to root patch OCLP with AMFI enabled is just a positive side effect. In summary, when applying OCLP root patches you can act in 2 different ways: with boot argument amfi=0x80 without AMFIPass.kext. amfi=0x80 is a bitmask that disables AMFI completely. The value 0x80 is equivalent to AMFI_ALLOW_EVERYTHING with AMFIPass.kext removing amfi=0x80 and adding -amfipassbeta in boot args. The -amfipassbeta boot argument is provided by AMFIPass.kext to override kernel version checking, so that the extension is loaded regardless of the macOS version. This way AMFIPass can work on macOS beta for which the extension does not yet have support. I use AMFIPass.kext, removing amfi=0x80. If OCLP root patching fails due to this setting, I temporarily disable AMFI with the boot argument amfi=0x80, apply the patches, reboot, remove amfi=0x80, and reboot again. (credits to @cankiulascmnfye for much of the explanatory text on AMFI and AMFIPass.kext). EFI with OpenCore 0.9.5 iMac19,1 SMBIOS iGPU enabled in BIOS AMD as main card config.plist as base config, try this by default config-fenvi.plist if you have a Broadcom wifi card supported on Ventura but not on Sonoma (OCLP root patch also needed), it must be renamed to config.plist Add your own serial numbers (they are empty). EFI 0.9.5 Sonoma.zip Edited October 11 by miliuco 8 2 Link to comment Share on other sites More sharing options...
Max.1974 Posted September 5 Share Posted September 5 Very nice my friend!! 1 Link to comment Share on other sites More sharing options...
CloverLeaf Posted September 5 Share Posted September 5 Amazing! Thank you! 1 Link to comment Share on other sites More sharing options...
saCULar Posted September 8 Share Posted September 8 Kudos for this very nice post. saCUL 1 Link to comment Share on other sites More sharing options...
miliuco Posted September 14 Author Share Posted September 14 Added EFI with OpenCore 0.9.5 in the first post. 1 Link to comment Share on other sites More sharing options...
saCULar Posted October 3 Share Posted October 3 Used your EFI as a basis to install on Z390 Aorus Pro Wifi. Had to disable whatever green and had to move my display port cable around, but everything except wifi (unsupported BCM card) working. regards saCUL 1 Link to comment Share on other sites More sharing options...
scipionems Posted November 20 Share Posted November 20 Hi Miliuco, Thank you for this fantastic guide. I was able to install SONOMA 14,2 on my hackintosh similar to your, following your guide. It works quite everything, except wifi and bluetooth. I tried to follow your guide DISABLING completely SIP, resetting NVRAM and trying to patch using OCLP , but unfortunately OCLP give me this error message (see picture attached) and don't allow me to patch.... Have you any suggestions ?. Thank you 1 Link to comment Share on other sites More sharing options...
miliuco Posted November 21 Author Share Posted November 21 @scipionems SIP is wrong in your config.plist. Change SIP value to the recommended by OCLP. csr-active-config=03080000 2 Link to comment Share on other sites More sharing options...
scipionems Posted November 21 Share Posted November 21 (edited) 1 hour ago, miliuco said: @scipionems SIP is wrong in your config.plist. Change SIP value to the recommended by OCLP. csr-active-config=03080000 Hi Miliuco, thank you for the reply. Using 03080000, I was able to use OCLP and to patch the root... But unfortunately when I reboot the computer, my mackintosh go in loop.... starting and starting again... I have disabled from the EFI the AMFIPass.KEXT and the boot arg AMFIPASSBETA.... and I used only the boot arg AMFI=0X80 without the kext.... I was able to start again Sonoma , I tried to patch again with OCLP the root and rebooted my hack ... but wifi and bluetooth are still NOT working 😥 Probably for my kind of wifi I need some other kext.... Spoiler Edited November 21 by scipionems Link to comment Share on other sites More sharing options...
miliuco Posted November 21 Author Share Posted November 21 @scipionems Look for the chipset of the wifi, branch and model can help. To see if it’s included in the list of supported by OCLP. And show to me your config.plist. Link to comment Share on other sites More sharing options...
scipionems Posted November 21 Share Posted November 21 (edited) 2 hours ago, miliuco said: @scipionems Look for the chipset of the wifi, branch and model can help. To see if it’s included in the list of supported by OCLP. And show to me your config.plist. Hi Miliuco, thank you again. My chipset is Broadcom BCM94352Z , model DW1560.... branch DELL (I suppose).... I attach my EFI with config.plist EFI.zip Edited November 21 by scipionems Link to comment Share on other sites More sharing options...
miliuco Posted November 21 Author Share Posted November 21 @scipionems Config.plist looks fine, SIP value is ok. Your BCM94352Z chipset may be supported but I'm not sure. OCLP added more chipsets to the list: device-id pci12e4,4357 >> BCM43225 device-id pci12e4,43B1 >> BCM4352 device-id pci12e4,43B2 >> BCM4352 (2.4 GHz). I don't know if 4352 and 4352Z are the same chipset with slight differences. In any case, these chipsets also need AirportBrcmFixup, the kexts you currently have are not enough. Try adding AirportBrcmFixup (Kexts folder and config.plist, after AirPortBrcmNIC.kext), reboot and comment on the result. Important note on Readme.md Please pay attention In macOS 11+, class AirPortBrcm4360 has been completely removed. Using of injector kext with such class name and matched vendor-id:device-id blocks loading of original airport kext. To address this issue and keep compatibility with older systems injectors, AirPortBrcm4360 and AirPortBrcmNIC were removed from main Info.plist file. Instead, the two new kext injectors are deployed in PlugIns folder: AirPortBrcm4360_Injector.kext and AirPortBrcmNIC_Injector.kext. You have to block (or remove) AirPortBrcm4360_Injector.kext in 11+. In OpenCore you can specify MaxKernel 19.9.9 for AirPortBrcm4360_Injector.kext. According to this, You must block Sonoma from loading AirPortBrcm4360_Injector.kext and allow AirPortBrcmNIC_Injector.kext, e.g. (only wifi kexts): <?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>Kernel</key> <dict> <key>Add</key> <array> <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>IOSkywalkFamily.kext</string> <key>Comment</key> <string>IOSkywalkFamily</string> <key>Enabled</key> <false/> <key>ExecutablePath</key> <string>Contents/MacOS/IOSkywalkFamily</string> <key>MaxKernel</key> <string></string> <key>MinKernel</key> <string>23.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>IO80211FamilyLegacy.kext</string> <key>Comment</key> <string>IO80211FamilyLegacy</string> <key>Enabled</key> <false/> <key>ExecutablePath</key> <string>Contents/MacOS/IO80211FamilyLegacy</string> <key>MaxKernel</key> <string></string> <key>MinKernel</key> <string>23.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext</string> <key>Comment</key> <string>AirPortBrcmNIC</string> <key>Enabled</key> <false/> <key>ExecutablePath</key> <string>Contents/MacOS/AirPortBrcmNIC</string> <key>MaxKernel</key> <string></string> <key>MinKernel</key> <string>23.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>AirportBrcmFixup.kext</string> <key>Comment</key> <string>Broadcom Wifi Patch</string> <key>Enabled</key> <false/> <key>ExecutablePath</key> <string>Contents/MacOS/AirportBrcmFixup</string> <key>MaxKernel</key> <string></string> <key>MinKernel</key> <string>12.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext</string> <key>Comment</key> <string></string> <key>Enabled</key> <false/> <key>ExecutablePath</key> <string></string> <key>MaxKernel</key> <string></string> <key>MinKernel</key> <string>20.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcm4360_Injector.kext</string> <key>Comment</key> <string></string> <key>Enabled</key> <false/> <key>ExecutablePath</key> <string></string> <key>MaxKernel</key> <string>19.9.9</string> <key>MinKernel</key> <string></string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> </array> </dict> </dict> </plist> 1 Link to comment Share on other sites More sharing options...
Max.1974 Posted November 21 Share Posted November 21 (edited) Maybe you should try use compatible device properties in config.plist (exactly like print, not change for your device but extract from Hackintool and put parameters) And add this boot args: -lilubetaall -brcmfxbeta device-properties-BRCM4360-Compatible.plist.zip I saw your EFI maybe you need try this kexts, ons by one and try fix Bluetooth Exclude those was no necessary Edited November 21 by Max.1974 1 Link to comment Share on other sites More sharing options...
scipionems Posted November 21 Share Posted November 21 1 hour ago, miliuco said: @scipionems Config.plist looks fine, SIP value is ok. Your BCM94352Z chipset may be supported but I'm not sure. OCLP added more chipsets to the list: device-id pci12e4,4357 >> BCM43225 device-id pci12e4,43B1 >> BCM4352 device-id pci12e4,43B2 >> BCM4352 (2.4 GHz). I don't know if 4352 and 4352Z are the same chipset with slight differences. In any case, these chipsets also need AirportBrcmFixup, the kexts you currently have are not enough. Try adding AirportBrcmFixup (Kexts folder and config.plist, after AirPortBrcmNIC.kext), reboot and comment on the result. Important note on Readme.md Please pay attention In macOS 11+, class AirPortBrcm4360 has been completely removed. Using of injector kext with such class name and matched vendor-id:device-id blocks loading of original airport kext. To address this issue and keep compatibility with older systems injectors, AirPortBrcm4360 and AirPortBrcmNIC were removed from main Info.plist file. Instead, the two new kext injectors are deployed in PlugIns folder: AirPortBrcm4360_Injector.kext and AirPortBrcmNIC_Injector.kext. You have to block (or remove) AirPortBrcm4360_Injector.kext in 11+. In OpenCore you can specify MaxKernel 19.9.9 for AirPortBrcm4360_Injector.kext. According to this, You must block Sonoma from loading AirPortBrcm4360_Injector.kext and allow AirPortBrcmNIC_Injector.kext, e.g. (only wifi kexts): <?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>Kernel</key> <dict> <key>Add</key> <array> <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>IOSkywalkFamily.kext</string> <key>Comment</key> <string>IOSkywalkFamily</string> <key>Enabled</key> <false/> <key>ExecutablePath</key> <string>Contents/MacOS/IOSkywalkFamily</string> <key>MaxKernel</key> <string></string> <key>MinKernel</key> <string>23.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>IO80211FamilyLegacy.kext</string> <key>Comment</key> <string>IO80211FamilyLegacy</string> <key>Enabled</key> <false/> <key>ExecutablePath</key> <string>Contents/MacOS/IO80211FamilyLegacy</string> <key>MaxKernel</key> <string></string> <key>MinKernel</key> <string>23.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>IO80211FamilyLegacy.kext/Contents/PlugIns/AirPortBrcmNIC.kext</string> <key>Comment</key> <string>AirPortBrcmNIC</string> <key>Enabled</key> <false/> <key>ExecutablePath</key> <string>Contents/MacOS/AirPortBrcmNIC</string> <key>MaxKernel</key> <string></string> <key>MinKernel</key> <string>23.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>AirportBrcmFixup.kext</string> <key>Comment</key> <string>Broadcom Wifi Patch</string> <key>Enabled</key> <false/> <key>ExecutablePath</key> <string>Contents/MacOS/AirportBrcmFixup</string> <key>MaxKernel</key> <string></string> <key>MinKernel</key> <string>12.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcmNIC_Injector.kext</string> <key>Comment</key> <string></string> <key>Enabled</key> <false/> <key>ExecutablePath</key> <string></string> <key>MaxKernel</key> <string></string> <key>MinKernel</key> <string>20.0.0</string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> <dict> <key>Arch</key> <string>x86_64</string> <key>BundlePath</key> <string>AirportBrcmFixup.kext/Contents/PlugIns/AirPortBrcm4360_Injector.kext</string> <key>Comment</key> <string></string> <key>Enabled</key> <false/> <key>ExecutablePath</key> <string></string> <key>MaxKernel</key> <string>19.9.9</string> <key>MinKernel</key> <string></string> <key>PlistPath</key> <string>Contents/Info.plist</string> </dict> </array> </dict> </dict> </plist> Hi Miliuco, I added AirportBrcm4360Fixup in the kext folder, modified the config.plist, but unfortunately, after rebooting wifi and bluetooth are still NOT working 😥 Link to comment Share on other sites More sharing options...
Max.1974 Posted November 21 Share Posted November 21 4 minutes ago, scipionems said: Hi Miliuco, I added AirportBrcm4360Fixup in the kext folder, modified the config.plist, but unfortunately, after rebooting wifi and bluetooth are still NOT working 😥 How did you map your USB ports? Its necessary put Bluetooth Internal Link to comment Share on other sites More sharing options...
Max.1974 Posted November 21 Share Posted November 21 @scipionems try this EFI ResetNvram and backup yours Use only ONE EFI to set boot EFI-scip.zip 1 Link to comment Share on other sites More sharing options...
scipionems Posted November 21 Share Posted November 21 10 minutes ago, Max.1974 said: Maybe you should try use compatible device properties in config.plist (exactly like print, not change for your device but extract from Hackintool and put parameters) And add this boot args: -lilubetaall -brcmfxbeta device-properties-BRCM4360-Compatible.plist.zip 623 B · 1 download I saw your EFI maybe you need try this kexts, ons by one and try fix Bluetooth Exclude those was no necessary Hi Max.1974, I modified the config.plist device properties following your indication, but wifi and bluetooth still not working... I tried to add the kexts , but I am not able to boot... kernel panic....black screen... 😥 1 Link to comment Share on other sites More sharing options...
Max.1974 Posted November 21 Share Posted November 21 (edited) Try EFI that im upload above, reset Nvram Try change your USBports for Usbinjectall + XHCIunsupported and after test remap Can you extract your DSDT.aml with Hackintool ? Edited November 21 by Max.1974 Link to comment Share on other sites More sharing options...
Max.1974 Posted November 21 Share Posted November 21 (edited) Unfortnely OCLP cause crash on your config.plist, and I suggest you look for old EFI without OCLP modifications and do block Skywalk kext manually Config again your BIOS from Load Optimal Defaults and another thinks necessary like XHCI enable, update BIOS if needed, disable secure boot, disable 4g Above, disable Legacy ports...check if your wireless card is connected and fine with another OS, like Linux or Windows. Edited November 21 by Max.1974 Link to comment Share on other sites More sharing options...
makk Posted 9 hours ago Share Posted 9 hours ago Seems like Sonoma installs well @Max.1974 how was the install on Raptor Lake? I have Alder Lake 12600KF core i5 B660 board Gigabyte Link to comment Share on other sites More sharing options...
Recommended Posts