Jump to content
142 posts in this topic

Recommended Posts

10 minutes ago, calmesal said:

OK got it. Thanks for the reply, I already got the 3.0.0 but want the lates 3.1.2.

 

The English translation linked above is for OCLP-Mod 3.1.2. Please just have a proper look to it, unveil the hidden content in the post and give it a try!  

Edited by KGP-iMacPro
  • Like 2
  • Sad 1

Booted by OpenCore 1.0.7 can enable BCM43602CS's  WiFi at Macos 14.x/15.x/26.3, but it can not enable its Bluetooth controller in my ASUS H97M-E Hackintosh.

No such an issue if booted by Clover 5163. My config.plist of OC is posted here for your reference.

Screenshot 2026-01-01 at 10.02.24.png

config.plist

Edited by jsl
  • Like 1

@jsl I took a quick look at your config.plist and here's what I noticed:

  • There are additional NVRAM variables that help bluetooth functionality on hacks and OCLP-patched Macs.  See the attached config-bluetooth.plist

I stopped looking after finding those issues.  Test and report your results.

 

 

EDIT: I noticed a couple of other things in your config.plist (not related to Bluetooth):

  • you have boot-arg revpatch=sbvmm and "NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > revpatch (String, sbvmm)" in your config.plist.  This won't affect bluetooth (or anything else), but you only need one or the other.
  • you have "Booter > Patch > Skip Board ID Check" and boot-arg -no_compat_check.  You only need one of them (your preference).

config-Bluetooth.plist.zip

Edited by deeveedee
  • Like 4
3 hours ago, deeveedee said:

@jsl I took a quick look at your config.plist and here's what I noticed:

  • There are additional NVRAM variables that help bluetooth functionality on hacks and OCLP-patched Macs.  See the attached config-bluetooth.plist

I stopped looking after finding those issues.  Test and report your results.

 

 

EDIT: I noticed a couple of other things in your config.plist (not related to Bluetooth):

  • you have boot-arg revpatch=sbvmm and "NVRAM > Add > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > revpatch (String, sbvmm)" in your config.plist.  This won't affect bluetooth (or anything else), but you only need one or the other.
  • you have "Booter > Patch > Skip Board ID Check" and boot-arg -no_compat_check.  You only need one of them (your preference).

config-Bluetooth.plist.zip 2.72 kB · 4 downloads

Thanks for your kind help and advice.

I have followed your advice to modify my config.plist, but it did not work to solve my previous problem.

This error did not occur at Macos 11.x/12.x/13.x !

Screenshot 2026-01-04 at 10.05.14.png

Screenshot 2026-01-04 at 10.05.30.png

Screenshot 2026-01-04 at 10.14.05 AM.png

Edited by jsl
  • Like 3
  • Thanks 1
9 hours ago, jsl said:

Thanks for your kind help and advice.

I have followed your advice to modify my config.plist, but it did not work to solve my previous problem.

This error did not occur at Macos 11.x/12.x/13.x !

Screenshot 2026-01-04 at 10.05.14.png

Screenshot 2026-01-04 at 10.05.30.png

Screenshot 2026-01-04 at 10.14.05 AM.png

I don't think this is a software issue. I have a very similar Wi-Fi/Bluetooth card, but its Bluetooth part always worked automatically out of the box. I looked at your configuration, and it's correct, except for the outdated keys, which have no effect since the Ventura. And this thread is about the Tahoe 26, so you should probably ask in the OpenCore setup thread. In the case of Ventura, I would recommend rolling back root patches. 

Снимок экрана 2026-01-04 at 13.29.33.jpg
For .MB: ASUS H97M-E| CPU: i7-4770K (3.5 GHz)| GPU: Intel HD 4600/AMD RX-6600 XT| the highest version of Mac OS, VentureBeat. Tahoe can be installed, but it will require some creative thinking.

Edited by MakAsrock
  • Like 1
3 hours ago, fantomas said:

@jsl

 

Hi,

 

Why do we see a macOS Ventura screenshot in macOS Tahoe beta topic?

The Macos Ventura screenshot showed normal Bluetooth controller was found & connected.

But it's abnormal at Tahoe beta, 14. x and 15.x of my ASUS H97M-E hackintoshs. 

Edited by jsl
  • Like 2
36 minutes ago, jsl said:

The Macos Ventura screenshot showed normal Bluetooth controller was found & connected.

But it's abnormal at Tahoe beta, 14. x and 15.x of my hackintoshs. 

On my old Asus Z77-A (Ivy Bridge)  +i7-3770K +16 GB DDR-3 + RX580 Hackintosh, the same adapter worked fine with Mac OS 14.x and 15.x, but I wasn't satisfied with the overall performance of that hack. My Son is currently playing computer games on Windows 10 with external USB Wi-Fi/Bluetooth dongle.

You have the next generation and everything should work no worse. But you still won't get satisfaction.
UDATE:
I think I figured out what's going on: You need to make a new UTBMap.kext and everything should work.

README.md

Снимок экрана 2026-01-04 at 14.17.59.jpg

Edited by MakAsrock
  • Like 1

Hello everyone, I managed to stabilize everything using USBToolbox + UTBMap by doing the mapping in Windows, and after testing, I extracted it with HT and replaced the kexts with USBPorts + SSDTs, and used the USBMap injector. It turned out very good.

  • Like 4
11 hours ago, jsl said:

Thanks for your kind help and advice.

I have followed your advice to modify my config.plist, but it did not work to solve my previous problem.

This error did not occur at Macos 11.x/12.x/13.x !

 

Thanks for testing. MakAsrock's theory that the Bluetooth problem is USB-related is sound, since the problem for you started with Tahoe.  Did you modify your USBPorts.kext for Tahoe?  If you don't solve this, please post your full EFI (at least config.plist, OC/Kexts and OC/ACPI).

 

EDIT: I made some other notes about your config.plist:

  • ACPI > Add > Item 7: SSDT-UIAC is not necessary unless you are using USBInjectAll.kext (which is disabled in your config.plist).  This SSDT does nothing without USBInjectAll.kext, so if you disable USBInjectAll.kext, you can disable SSDT-UIAC as well.
  • Kernel > Add > Item 10 & 11: Why do you have MaxKernel = 21.99.99 for BrcmFirmwareData.kext and BrcmPatchRAM3.kext?  Is this not needed for BCM43602CS?  (I just purchased my BCM43602CS and haven't tried it yet, so I have no experience with this card)
Edited by deeveedee
  • Like 2
2 hours ago, deeveedee said:

 

Thanks for testing. MakAsrock's theory that the Bluetooth problem is USB-related is sound, since the problem for you started with Tahoe.  Did you modify your USBPorts.kext for Tahoe?  If you don't solve this, please post your full EFI (at least config.plist, OC/Kexts and OC/ACPI).

 

EDIT: I made some other notes about your config.plist:

  • ACPI > Add > Item 7: SSDT-UIAC is not necessary unless you are using USBInjectAll.kext (which is disabled in your config.plist).  This SSDT does nothing without USBInjectAll.kext, so if you disable USBInjectAll.kext, you can disable SSDT-UIAC as well.
  • Kernel > Add > Item 10 & 11: Why do you have MaxKernel = 21.99.99 for BrcmFirmwareData.kext and BrcmPatchRAM3.kext?  Is this not needed for BCM43602CS?  (I just purchased my BCM43602CS and haven't tried it yet, so I have no experience with this card)

Only on the Tahoe 26 I Did modify UTBMap to get the internal USB port to work, which is connected to the cable from the FENVI FV-HB1200 PCIe adapter (Broadcom BCM43xx) for Bluetooth audio output. I just thought it was self-evident to those who read the FAQ. I haven't tried editing SSDT-UIAC before. I was missing ports before, although it worked on the Sequoia. If you try it and let me know the results, I'd be very grateful.

And attached is my current config:  

Config.plist

Edited by MakAsrock
  • Like 2
11 hours ago, maly70 said:

what is 26.3 beta(a)... is it the same as beta version(25D5087f)?

Thank you for your time mates

This Background Security Improvement is for testing purposes only and does not contain any security fixes.

 

image.png.1acfb8b711edeedb3bce73854527d266.png

image.png

  • Like 3

Very fast incremental upgrade to Tahoe 26.3 Beta 2.  Happy to have at least another year of flawless hack performance with macOS Tahoe.

  • Open Core 1.0.6
  • WhateverGreen 1.7.0 (need to temporarily add boot-arg -wegnoegpu to perform the update and then remove the boot-arg after the update)
  • Temporarily disable BluetoolFixup.kext to enable incremental update, then enable BluetoolFixup.kext after update
  • VoodooHDA.kext 3.0.3 with SIP csr-active-config = <01000000>
  • IntelMausiEthernet 3.0.3 working perfectly with AppleVTD enabled
  • No root patches

Incremental Update

Spoiler

Screenshot2026-01-12at2_55_18PM.png.1294d8af2f47a551589d84d3837b979f.png

 

Screenshot2026-01-12at3_25_34PM.png.f2aa6e3be62055f8e7a02754ad268295.png

 

EDIT: Similar easy update for my HackBookPro16,2 (HP EliteBook 850 G7).  Using VoodooHDA.kext and Intel itlwm with csr-active-config = <01000000> (no root patches).

Spoiler

Screenshot2026-01-12at3_46_49PM.png.74a9d2e3077c0967a07475ae9adcf0f8.png

 

EDIT2: After a "settling" period following the update on my HackBookPro16,2 (only Intel IGPU graphics), I am impressed with the overall responsiveness of Tahoe on this hack.  I continue to enable System Settings "Accessibility > Motion > Reduce Motion" and "Accessibility > Display > Reduce Transparency"

Edited by deeveedee
  • Like 7
Guest
This topic is now closed to further replies.
×
×
  • Create New...