[pre-release] macOS Tahoe 26.6

[MaLd0n]

[Max.1974]

Nice  congrats!!  

[kgp]

Small follow-up regarding the AX210 Bluetooth BCM_4350C2 fallback state:

 

I was able to recover my AX210 Bluetooth side under macOS 26.5.2 after it had remained stuck in the persistent BCM_4350C2 / Address NULL / State Off state.

 

The interesting part is that the BCM_4350C2 state was still visible even after disabling IntelBluetoothFirmware, IntelBTPatcher, BlueToolFixup and AirportItlwm, and even after physically disconnecting the AX210 Bluetooth USB cable. With only Lilu loaded and no Intel 0x8087 USB Bluetooth device present anymore, System Information still showed the stale BCM_4350C2 / UART / Address NULL Bluetooth controller. At that point, this could no longer have been the real AX210 USB Bluetooth device, but looked more like a persistent macOS IOBluetooth ghost controller.

 

The recovery path that finally worked was:

 

1. Temporarily reinstall BCM943602CDP.

2. Boot the native Broadcom/OCLP EFI.

3. Let macOS initialize a real Broadcom Bluetooth controller.

4. Shut down and remove power.

5. Switch back to AX210.

6. Boot again with IntelBluetoothFirmware 2.5.1, IntelBTPatcher 2.5.1 and BlueToolFixup 2.7.2.

 

After that, AX210 Bluetooth came back as THIRD_PARTY_DONGLE again:

 

Address: 20:BD:1D:D8:94:32

State: On

Chipset: THIRD_PARTY_DONGLE

Firmware Version: v12490 c12490

Transport: USB

 

Magic Keyboard and Magic Mouse are connected again.

 

So this is not a code fix, but at least in my case temporarily initializing a real Broadcom Bluetooth controller cleared the persistent BCM_4350C2 ghost controller state, while NVRAM reset, deleting Bluetooth preferences and long complete power-off alone did not.

Edited 1 hour ago by kgp