Closed atharvaunde closed 3 years ago
Did that and added the BlueToolFix kext but still no luck.
You'll likely need a build of BluetoolFixup from the latest source code. The patch for Beta10+ has not been included in the official release.
Its showing like this in Hackintool
I have the same problem too. Bluetooth hardware information CANNOT corrently display on the Hackintool.
You'll likely need a build of BluetoolFixup from the latest source code. The patch for Beta10+ has not been included in the official release.
I built from the source only, as per this page https://openintelwireless.github.io/IntelBluetoothFirmware/Advanced.html#build-from-source and made changes as per OP of following issue https://github.com/OpenIntelWireless/IntelBluetoothFirmware/issues/347#issue-1026235946
(Fixed)I also cannot get it working.. applied the patches to both, intelbluetoothfirmware and bluetoolfixup. and it still not working.. Intel AX200
(UPDATE) The power in my house went off, and when I turned the computer on again it was working, with the latest patches. I guess it needed a cold boot, because I only rebooted then.
Thanks a lot for the patch!!
I don't think it is ideal but if you're facing the same issues (has applied the latest patches, and bluetooth is still not working) try pulling the AC plug off, wait a few seconds then turn the computer on again.
For what its worth, if you have the right kext in place, and bluetooth used to work in Big Sur or Cat, the other probable cause is your choice of SMBIOS
My original SMBIOS was MacBookPro16,3 which did not work. I've changed to MacBookPro15,2, and bluetooth now works as expected in Monterey, barring other airdrop bugs.
Those who are still facing issues can give this a try, but of course, pick the right smbios that is suitable for your hardware.
This build of BlueToolFixup.kext has no issue with my AX201's bluetooth
For what its worth, if you have the right kext in place, and bluetooth used to work in Big Sur or Cat, the other probable cause is your choice of SMBIOS
My original SMBIOS was MacBookPro16,3 which did not work. I've changed to MacBookPro15,2, and bluetooth now works as expected in Monterey, barring other airdrop bugs.
Those who are still facing issues can give this a try, but of course, pick the right smbios that is suitable for your hardware.
Thanks!! it work for me
Thanks add bluetoolfixup 2.6.1 ,delete intelbluetoothinjector,SMBIOS changed to MacBookPro15,2 My Monterey AX200 Bluetooth can run
Add bluetoolfixup and add the beta kext of 'Monterey Beta 10 Workaround'. My AC9560 can use bluetooth again. But handoff still cannot work.
Add bluetoolfixup and add the beta kext of 'Monterey Beta 10 Workaround'. My AC9560 can use bluetooth again. But handoff still cannot work.
Beta kext? U mean one by building with source code and changing that line in the file before building?
For what its worth, if you have the right kext in place, and bluetooth used to work in Big Sur or Cat, the other probable cause is your choice of SMBIOS
My original SMBIOS was MacBookPro16,3 which did not work. I've changed to MacBookPro15,2, and bluetooth now works as expected in Monterey, barring other airdrop bugs.
Those who are still facing issues can give this a try, but of course, pick the right smbios that is suitable for your hardware.
Same happened with me, my SMBIOS was MacBookPro16,3. After changing it to MacBookPro15,2 Bluetooth started working fine on Monterey!
ventura 13.5 beta no me funciona
Description Hello Folks, I just upgraded my Open core from Big Sur to Monterey 12.0.1 and Bluetooth started breaking down. As per the site,
Make sure IntelBluetoothFirmware.kext v1.1.3 or newer is used. -> Am already having the latest version from the site
Exclude the injection of IntelBluetoothInjector.kext for macOS Monterey from the Bootloader's config -> I have deleted that kext from the EFI Folder
Include BlueToolFixup.kext from acidanthera/BrcmPatchRAM(opens new window) -> I have added BlueToolFixup.kext from the given link and added same to config.plist..
Still, my Bluetooth is not working, positive thing is the toggle is working but not discovering any device. Is it expected behavior considering the Monterey is very new or am missing out on something?
Do I need to add all other kexts from BRCMPatch or only BlueToolFixup is sufficient?
Environment
Screenshots