Contribute
Register

Broadcom WiFi/Bluetooth [Guide]

Edhawk

Moderator
Joined
Aug 2, 2013
Messages
4,167
Motherboard
Asus TUF Z390 Gaming
CPU
i5-8500
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
Mobile Phone
  1. iOS
The AirPortBrcm4360_Injector.kext stopped working in Big Sur. You need to remove or disable this kext when running macOS Big Sur or newer.
 

Edhawk

Moderator
Joined
Aug 2, 2013
Messages
4,167
Motherboard
Asus TUF Z390 Gaming
CPU
i5-8500
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
Mobile Phone
  1. iOS
Have you tried using the BlueToolFixup.kext to fix your Bluetooth issues in Monterey - BlueToolFixup
 

Edhawk

Moderator
Joined
Aug 2, 2013
Messages
4,167
Motherboard
Asus TUF Z390 Gaming
CPU
i5-8500
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
Mobile Phone
  1. iOS
No I didn't mean for you to delete both lines, as you will need the AirPortBrcmNIC_Injector.kext in Monterey.

What you need to do is add a MaxKernel entry to your config.plist, so AirportBrcm4360_Injector.kext is not used in any version of macOS newer than Catalina.

This is how the AirportBrcmFixup.kext and the two injectors are set in my config.plist.

Screenshot 2022-02-27 at 17.23.41.png

Under the AirPortBrcm4360_Injector.kext entry I have set the MaxKernel to 19.9.9. This prevents the system using the AirportBrcm4360_injector.kext when running Big Sur or newer.

So no need to delete the kext.

See this section of the AirPortBrcmFixup readme - AirportBrcmFixup
 

Edhawk

Moderator
Joined
Aug 2, 2013
Messages
4,167
Motherboard
Asus TUF Z390 Gaming
CPU
i5-8500
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
Mobile Phone
  1. iOS
To fix bluetooth issues in Monterey you need the BlueToolFixup.kext, did you read the information on the link I provided?
 
Joined
Aug 30, 2018
Messages
1,466
Motherboard
Asus ROG Strix Z390 I-Gaming
CPU
i7-8700K
Graphics
Vega 64
Mac
  1. MacBook
Classic Mac
  1. 512K
  2. iMac
Mobile Phone
  1. iOS
To fix bluetooth issues in Monterey you need the BlueToolFixup.kext, did you read the information on the link I provided?

I read those instructions a few times, but like everything I read at 2:00 AM in the morning, I probably glossed over it.
Thanks to your help!

My last issue is I lost access to my boot camp partition. My also system takes forever to boot up and it seems to be caused by this error:

tzinit: New update not compatible or older version: 2020a.1.0 vs 2020a.1.0: No such file or directory

Any idea where I should post for help on that one? A search on Tonymac doesn't turn up anything.

Thanks again!
 

Edhawk

Moderator
Joined
Aug 2, 2013
Messages
4,167
Motherboard
Asus TUF Z390 Gaming
CPU
i5-8500
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
Mobile Phone
  1. iOS
Which version of OpenCore are you using, as you are running Monterey I assume it is OC 0.7.4 or newer.
Do you still have a Bootcamp folder in your OC folder, or are you using the newer method for running BootCamp with OpenCore?

The way to fix the tzinit error seems to be to reinstall macOS using the macOS Recovery partition. That was the fix offered on Apple's Support forums, as listed in this post - https://discussions.apple.com/thread/251585186
 
Joined
Aug 30, 2018
Messages
1,466
Motherboard
Asus ROG Strix Z390 I-Gaming
CPU
i7-8700K
Graphics
Vega 64
Mac
  1. MacBook
Classic Mac
  1. 512K
  2. iMac
Mobile Phone
  1. iOS
Which version of OpenCore are you using, as you are running Monterey I assume it is OC 0.7.4 or newer.
Do you still have a Bootcamp folder in your OC folder, or are you using the newer method for running BootCamp with OpenCore?

The way to fix the tzinit error seems to be to reinstall macOS using the macOS Recovery partition. That was the fix offered on Apple's Support forums, as listed in this post - https://discussions.apple.com/thread/251585186
No Boot Camp folder and OC 0.7.8 . Used to work fine before, now no love. I assume I'm using the 'new' method because I can boot to Windows from OC? I have ALMOST been exclusively using Parallels to run Windows MOST of the time. I want the option to boot to Windows directly even once in a while for specific things.

Windows is on it's own ssd. I did copy in the Bootx64.efi folder in the Boot folder. Could that have caused it? At some point a few versions ago I started to have to choose which volume I wanted to boot Windows from, Any ideas on that? I suspect I have an extra EFI somewhere.

I did see the Apple article but I was hoping it didn't apply or there was a a less scary way of doing it. What does TZINIT do anyway?

Should this be moved to another thread?

Thanks again.
 
Last edited:

Edhawk

Moderator
Joined
Aug 2, 2013
Messages
4,167
Motherboard
Asus TUF Z390 Gaming
CPU
i5-8500
Graphics
RX 580
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
Mobile Phone
  1. iOS
tzinit Initiates something, not sure what.

That was the only fix I could find, well one that made sense. The rest were similar but not as conclusive about the outcome.

BootCamp was removed some time ago, year or more, around the release of OC 0.6.6, IIRC. So not so new!

Do you mean you copied in the BOOTx64.efi and BOOT folder from an older version of OC, to the new 0.7.8 setup? If Yes, you need to replace the BOOT Folder with the OC 0.7.8 version attached below.

As the BOOTx64.efi, OpenCore.efi and OpenRuntime.efi all need to match, based in the version of OC you are using. These are the core elements for OC.
 

Attachments

  • BOOT.zip
    7.7 KB · Views: 37
Last edited:
Top