Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BlueToolFixup.kext breaks macOS incremental OTA Updates #2433

Open
TonyC5 opened this issue Oct 16, 2024 · 0 comments
Open

BlueToolFixup.kext breaks macOS incremental OTA Updates #2433

TonyC5 opened this issue Oct 16, 2024 · 0 comments

Comments

@TonyC5
Copy link

TonyC5 commented Oct 16, 2024

When BlueToolFixup.kext is injected via OC, incremental OTA macOS updates fail and revert to a download of the full macOS installer. A work-around is to temporarily disable Kernel > Add > BlueToolFixup.kext in OC config.plist, perform the macOS OTA update and then re-enable BlueToolFixup.kext after the macOS incremental update completes.

If BluetoolFixup.kext is left enabled during the entire macOS update process, the macOS update completes successfully with the full macOS installer (after failing with the incremental macOS installer).

I am currently testing this with release versions of Open Core 1.0.2, Lilu.kext 1.6.9 and BlueToolFixup.kext 2.6.9 with both macOS Sonoma and Sequoia.

I am using BlueToolFixup.kext with Intel BlueTooth (Open Wireless Project Bluetooth version 2.5.0 kexts), but have seen reports by others indicating that this BlueToolFixup.kext / macOS OTA issue occurs when using BlueToolFixup.kext with Brcm chipsets.

Note that only BlueToolFixup.kext needs to be disabled / re-enabled. The other Bluetooth kexts can remain enabled during the incremental macOS update.

My System Specs

  • Wi-Fi/Bluetooth m.2 card: Intel 9560NGW
  • SMBIOS macMini8,1
  • BlueToolFixup.kext 2.6.9 (Release)
  • IntelBluetoothFirmware.kext and IntelBTPatcher.kext 2.5.0
  • Lilu.kext 1.6.9 (Release)
  • RestrictEvents.kext 1.1.5 (Release) with revpatch=sbvmm
  • Open Core 1.0.2 (Release)
  • csr-active-config = 0x0 (SIP fully enabled)

I am not using any Wi-Fi (no Wi-Fi kexts).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants