pio Posted June 4 Share Posted June 4 I've seen similar issues with the BCM94360 before. In my case, it was either related to USB power management or a messed-up USB mapping. It could also be a kext issue. Unfortunately, I can't really say much without seeing the EFI. The Google Drive link requires access, so I'm not able to download it and take a look. Ps: 셜록님 일단 윈도우 부팅되시면 윈도우쪽에서고 같은 증상있는지 먼저 확인해주세요. Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850853 Share on other sites More sharing options...
Mirone Posted June 5 Share Posted June 5 On 6/3/2026 at 1:08 PM, Sherlocks said: here is efi folder. I hope for a good result. https://drive.google.com/file/d/1NnGN_emKlL39BYpuJNkksdK2ZEFT9KAc/view?usp=drive_link You do not need the following kexts to enable Bluetooth on the BCM94360CD: BrcmBluetoothInjector.kext, BrcmFirmwareData.kext, BrcmPatchRAM.kext, BrcmPatchRAM2.kext, and BrcmPatchRAM3.kext. The only required kexts are: AMFIPass.kext, IO80211FamilyLegacy.kext, and IOSkywalkFamily.kext. For some variants, such as the BCM943602CS, you may also need AirportBrcmFixup.kext. In addition, you need to properly map your USB ports so that Sleep/Wake functions correctly. Make the necessary adjustments and test the kext again. 2 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850859 Share on other sites More sharing options...
Sherlocks Posted June 5 Share Posted June 5 (edited) 38 minutes ago, Mirone said: You do not need the following kexts to enable Bluetooth on the BCM94360CD: BrcmBluetoothInjector.kext, BrcmFirmwareData.kext, BrcmPatchRAM.kext, BrcmPatchRAM2.kext, and BrcmPatchRAM3.kext. The only required kexts are: AMFIPass.kext, IO80211FamilyLegacy.kext, and IOSkywalkFamily.kext. For some variants, such as the BCM943602CS, you may also need AirportBrcmFixup.kext. In addition, you need to properly map your USB ports so that Sleep/Wake functions correctly. Make the necessary adjustments and test the kext again. Yes i just test for brcm kext. Now disabled kext in attached config.plist. airportbrcmfixup too. I also remapped usb port from windows. https://github.com/perez987/USB-ports-map-for-macOS-with-USBToolBox But as result, both usbtoolbox and usbinjectall with ssdt is same.🥲 I prefer to use usbinjectall. So now i use it I will try to remap usb again 6 hours ago, pio said: I've seen similar issues with the BCM94360 before. In my case, it was either related to USB power management or a messed-up USB mapping. It could also be a kext issue. Unfortunately, I can't really say much without seeing the EFI. The Google Drive link requires access, so I'm not able to download it and take a look. Ps: 셜록님 일단 윈도우 부팅되시면 윈도우쪽에서고 같은 증상있는지 먼저 확인해주세요. Usb power management? SSDT-USBX? In windows 11, i don't have problem. Edited June 5 by Sherlocks 1 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850860 Share on other sites More sharing options...
pio Posted June 5 Share Posted June 5 13 hours ago, Sherlocks said: Yes i just test for brcm kext. Now disabled kext in attached config.plist. airportbrcmfixup too. I also remapped usb port from windows. https://github.com/perez987/USB-ports-map-for-macOS-with-USBToolBox But as result, both usbtoolbox and usbinjectall with ssdt is same.🥲 I prefer to use usbinjectall. So now i use it I will try to remap usb again Usb power management? SSDT-USBX? In windows 11, i don't have problem. I think there was some confusion here. I wasn’t talking about SSDT-USBX, just the USB header cable on the PCIe card. If USBToolBox and USBInjectAll both act the same, and it works fine in Windows, I'd still check the USB map in macOS. Worth trying a fresh remap on Tahoe just to rule it out. Also check if the Bluetooth USB device actually shows up after boot. Had a similar issue before and just unplugging/replugging the PCIe USB cable fixed it. P.S. 혹시 Tahoe로 오시면서 기본에 사용하시던 USB매핑 kext 수정하셧나요? Tahoe에서 USB 스택 쪽이 좀 바뀌면서 예전 방식 USB 매핑이 안 맞는 경우도 있는 것 같습니다. 1 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850869 Share on other sites More sharing options...
Mirone Posted June 5 Share Posted June 5 I'm working on a kext (BlueWakeFixup) based on BlueToolFixup, focused solely on fixing wake functionality for native Wi-Fi cards that don't require BlueToolFixup to enable Bluetooth. I need some time to finish and test it, which I currently don't have. @Sherlocks, add this boot argument: -btlfxnvramcheck Let's see whether the behavior changes or is affected. I would also try a new kext remapping, as @pio suggested. 4 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850871 Share on other sites More sharing options...
FirstCustomac Posted June 5 Share Posted June 5 2 hours ago, Mirone said: I'm working on a kext (BlueWakeFixup) based on BlueToolFixup, focused solely on fixing wake functionality for native Wi-Fi cards that don't require BlueToolFixup to enable Bluetooth. I need some time to finish and test it, which I currently don't have. This is great. I've had to reduce my memory clock speed down to 2666MHz on my Z390 to fix the Bluetooth(FVT919) issue since macOS 12. Anything higher, I lose Bluetooth on resume. Hopefully your kext can fix it! 1 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850874 Share on other sites More sharing options...
carlo_67 Posted June 5 Share Posted June 5 I found this card inside a 2012 MacBook Air, bcm943224pciebt2, which is old and native up to Catalina. I bought an M2 to mini PCI adapter and installed it in my AMD card. I'm using OCLP-Mod and these kexts: IOSkywalkFamily - IO80211FamilyLegacy + block. I also used the old AirportBrcmFixup, removing the AirPortBrcmNIC_Injector and AirPortBrcm4360_Injector.kext plugins, loading only the kext. In the device properties of the OC card, I set the Spoof Device-id. data A0430000 compatible string pci14e4,43a0 The bootarg and kext for BT are in the screenshot. I use it on my AMD and it works. Tahoe 26.5.1 Maybe it could be useful. 2 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850876 Share on other sites More sharing options...
carlo_67 Posted June 5 Share Posted June 5 On 3/10/2026 at 9:06 PM, Hnanoto said: Hello everyone! It’s Hnanoto Today I’m extremely excited to announce a massive architectural update to our Auxiliary Kexts project! We just released v1.1.0, turning o ur small injection kexts into full-fledged, autonomous hardware stabilizers for both Hackintoshes and Real Macs running modern macOS. If you ever suffer from random Wi-Fi drops, or your Bluetooth completely disappears from the menu bar after waking your PC from Sleep Mode, this project is for you! 🌟 Meet The Stabilizers: 1. AirPortUtility.kext (Network / Wi-Fi Guardian) Actively monitors IO80211Controller, AirPort_BrcmNIC, and itlwm instances. Auto-Recovery: If the network drops or becomes unresponsive, the built-in Watchdog safely issues a synchronous terminate() command to the crashed interface, instantly followed by a registerService() directly to the PCIe/USB provider bus. The Result: It simulates a physical "unplug and plug" hardware cycle at the kernel level. Your Wi-Fi comes back to life within 15 seconds, autonomously, without needing a system reboot. 2. BluetoothFileExchange.kext (Bluetooth Stabilizer) Focuses heavily on the Apple Virtual Bus, actively polling IOBluetoothHCIController and USB/UART transports. Serves as the ultimate "Sleep/Wake Guardian". If macOS loses communication with your Bluetooth module after sleep, this kext forces the system to reload the driver stack in the background automatically. 🛠️ What's new under the hood in v1.1.0? Zero Kernel Panics: We fully rewrote the XNU C++ service matching functions. The kexts no longer perform a double-free on IOKit dictionaries. It is now 100% memory-safe. True Self-Healing: Eradicated dummy logs. The kexts now execute real C++ termination and re-probing processes inside the kernel. 📦 How to get it? You can download the compiled .kext files ready for OpenCore and Clover directly from our GitHub Releases page! 👉GitHubhttps://github.com/hnanoto/Kexts_Auxiliares/releases/tag/v1.1.0 Drop them in your EFI folder (and add them to your config.plist if using OpenCore), snapshot, and reboot. Enjoy a panic-free and stable macOS experience! Let me know your feedback down below! Cheers, Hnanoto / @HackintoshAndBeyond This didn't work for me but I'm continuing to try anyway thanks 1 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850877 Share on other sites More sharing options...
Sherlocks Posted June 6 Share Posted June 6 11 hours ago, Mirone said: I'm working on a kext (BlueWakeFixup) based on BlueToolFixup, focused solely on fixing wake functionality for native Wi-Fi cards that don't require BlueToolFixup to enable Bluetooth. I need some time to finish and test it, which I currently don't have. @Sherlocks, add this boot argument: -btlfxnvramcheck Let's see whether the behavior changes or is affected. I would also try a new kext remapping, as @pio suggested. Okay. I will try it with your bluetoothfixup. 1 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850889 Share on other sites More sharing options...
Sherlocks Posted June 6 Share Posted June 6 15 hours ago, Mirone said: I'm working on a kext (BlueWakeFixup) based on BlueToolFixup, focused solely on fixing wake functionality for native Wi-Fi cards that don't require BlueToolFixup to enable Bluetooth. I need some time to finish and test it, which I currently don't have. @Sherlocks, add this boot argument: -btlfxnvramcheck Let's see whether the behavior changes or is affected. I would also try a new kext remapping, as @pio suggested. -btlfxnvramcheck, it is not working. i find info https://github.com/vluncasu/BCM94360-Sonoma-Fix i will test it. 1 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850891 Share on other sites More sharing options...
Mirone Posted June 6 Share Posted June 6 @Sherlocks, Could you send me your complete EFI folder? If you'd rather not post it here, feel free to send it to me via PM. Please also send me the USB kext you mapped using USBToolBox. I took a look at the GitHub repository you mentioned, and honestly, I didn't need to use many of the things listed there to get either my BCM4352 or BCM4360 working. Regarding the Bluetooth issue after sleep, I had already tried several approaches, including the BlueToolFixup boot arguments. In the end, I decided to analyze the bluetoothd daemon to address the problem directly, and so far the results have been very good on both Sonoma and Sequoia. Actually, I only noticed this behavior of Bluetooth remaining disabled after sleep with my BCM4352. On the BCM4360, Bluetooth was always enabled and working properly after waking from sleep. I haven't tested AirDrop, though. 18 hours ago, carlo_67 said: This didn't work for me but I'm continuing to try anyway thanks Have you tested the BlueToolFixup version I posted here? Do you have any issues with Bluetooth not being re-enabled after waking from sleep? 1 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850898 Share on other sites More sharing options...
Sherlocks Posted June 6 Share Posted June 6 1 hour ago, Mirone said: @Sherlocks, Could you send me your complete EFI folder? If you'd rather not post it here, feel free to send it to me via PM. Please also send me the USB kext you mapped using USBToolBox. I took a look at the GitHub repository you mentioned, and honestly, I didn't need to use many of the things listed there to get either my BCM4352 or BCM4360 working. Regarding the Bluetooth issue after sleep, I had already tried several approaches, including the BlueToolFixup boot arguments. In the end, I decided to analyze the bluetoothd daemon to address the problem directly, and so far the results have been very good on both Sonoma and Sequoia. Actually, I only noticed this behavior of Bluetooth remaining disabled after sleep with my BCM4352. On the BCM4360, Bluetooth was always enabled and working properly after waking from sleep. I haven't tested AirDrop, though. Have you tested the BlueToolFixup version I posted here? Do you have any issues with Bluetooth not being re-enabled after waking from sleep? please check pm here is usb in windows. now i don't have usb stick. sorry usb.json 2 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850899 Share on other sites More sharing options...
carlo_67 Posted June 7 Share Posted June 7 Il 06/06/2026 alle 09:59, Sherlocks ha detto: -btlfxnvramcheck, it is not working. i find info https://github.com/vluncasu/BCM94360-Sonoma-Fix i will test it. and the same one I indicated above, I only changed bootarg -brcmfx-as-apple It tells the kext (variant related to AirportBrcmFixup or BrcmPatchRAM) to mask the third-party Bluetooth controller, bpatchcfga= Stands for Bluetooth Patch Configuration (or similar firmware configuration string for BrcmPatchRAM). It tells the driver to apply a specific firmware patch directly to the following hardware ID. Hardware Identifier: (0x0a5c21e8) Represents the unique device IDs expressed in hexadecimal format: 0A5C: This is the Vendor ID and corresponds to Broadcom. 21E8: This is the Product ID and corresponds to the BCM20702A0 chip. and then use AirportBrcmFixup.kext, without loading the plugins, and when I wake up everything works normally 2 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850906 Share on other sites More sharing options...
Sherlocks Posted June 7 Share Posted June 7 4 hours ago, carlo_67 said: and the same one I indicated above, I only changed bootarg -brcmfx-as-apple It tells the kext (variant related to AirportBrcmFixup or BrcmPatchRAM) to mask the third-party Bluetooth controller, bpatchcfga= Stands for Bluetooth Patch Configuration (or similar firmware configuration string for BrcmPatchRAM). It tells the driver to apply a specific firmware patch directly to the following hardware ID. Hardware Identifier: (0x0a5c21e8) Represents the unique device IDs expressed in hexadecimal format: 0A5C: This is the Vendor ID and corresponds to Broadcom. 21E8: This is the Product ID and corresponds to the BCM20702A0 chip. and then use AirportBrcmFixup.kext, without loading the plugins, and when I wake up everything works normally Can you upload kext or config? 1 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850909 Share on other sites More sharing options...
carlo_67 Posted June 7 Share Posted June 7 @Sherlocks Here is my OC folder, I removed the serial numbers and resources folder, I hope it can be useful to you, NB: my platform is AMD so you will also find the patches I use there https://mega.nz/file/z9YGGKBK#hXqKqkCTVJf7iKx7kzIgDm0NmFFbgejSHtHgUt4WbKM 2 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850918 Share on other sites More sharing options...
Mirone Posted June 7 Share Posted June 7 @carlo_67, I tried your method but unfortunately it didn't work for my BCM4352. 1 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850920 Share on other sites More sharing options...
carlo_67 Posted June 8 Share Posted June 8 @Mirone put the correct device-id of your device 4352 (Key) Type. Value device-id Data. B1430000 compatible String pci14e4,43a0 1 Link to comment https://www.insanelymac.com/forum/topic/362501-release-hackintosh-and-beyond-auxiliary-kexts-v110-real-hardware-level-watchdogs-for-wi-fi-bluetooth/page/2/#findComment-2850933 Share on other sites More sharing options...
Recommended Posts