[Guide] Airport - PCIe Half Mini v2

[RehabMan]

can someone kindly assist me to get my BCM94360CD to run BT? WiFi is working fine.
Info: 0a5c_22be

Tried installing the latest repo, patchram2, nonpatchram2 in S>L>E and still not working.
has removed them from path already.

0a5c_22be used to be supported in BrcmPatchRAM, but no longer...
It was removed from the Win8/Win10 drivers, and since BrcmPatchRAM is based on those drivers, also removed.
You can find the firmware in older versions of BrcmPatchRAM and integrate it back into the kext (editing the Info.plist, placing the firmware file in Resources, etc).

 

[tokyanru]

i tried using BrcmBluetoothInjector.kext. Bluetooth were fired up but it seems like bluetooth is unable to scan anything.
is it working/semi-working?

 

[RehabMan]

i tried using BrcmBluetoothInjector.kext. Bluetooth were fired up but it seems like bluetooth is unable to scan anything.
is it working/semi-working?

BrcmBluetoothInjector.kext does not have the ability to upload firmware.

 

[michael_pro]

Try:
Post #1
BCM94352 5 GHz/BT Handoff (10.10 and newer)
2. Patches (Select one)

1. 10.10.3 and newer, 5GHz

1. Binary patch: AirPortBrcm4360

1. US/FCC the-darkvoid #981​

2. ROW: Sebinouse #1162

1. [Guide] Airport - PCIe Half Mini v2 - Page 117
​

find: 41 83 FC FF 74 2C 48
replace:
US: 55 53/repl: 66 C7 06 55 53 EB 2B
GB: 47 42/repl: 66 C7 06 47 42 EB 2B
DE: 44 45/repl: 66 C7 06 44 45 EB 2B
FR: 46 52/repl: 66 C7 06 46 52 EB 2B

Edit - 5.14.15: fixed GB/DE typos

Hi Toleda , based on the information above i tried to edit the 10.12-BCM94352-5GHz-US-FCC-darkvoid to GB

from 81 F9 52 AA 00 00 66 90
to 81 F9 47 42 00 00 66 90 ( i also tried 81 F9 52 47 42 00 66 90)

still shows up as US FCC in About>System Report> WiFi

what did i do wrong

 

[nicholasM]

still shows up as US FCC in About>System Report> WiFi

Try resetting your Network Configuration; navigate to:

/Library/Preferences/SystemConfiguration/

And delete these two files:

NetworkInterfaces.plist
preferences.plist

Reboot and check if it's changed.

 

[michael_pro]

Try resetting your Network Configuration; navigate to:

/Library/Preferences/SystemConfiguration/

And delete these two files:

NetworkInterfaces.plist
preferences.plist

Reboot and check if it's changed.

thanks i ended up using the 10.11-BCM94352-CC=#a-Ramalama patch

 

[tokyanru]

0a5c_22be used to be supported in BrcmPatchRAM, but no longer...
It was removed from the Win8/Win10 drivers, and since BrcmPatchRAM is based on those drivers, also removed.
You can find the firmware in older versions of BrcmPatchRAM and integrate it back into the kext (editing the Info.plist, placing the firmware file in Resources, etc).

Tried the below, bluetooth is able to show in system report, but unable to detect any device to pair. Any suggestions on what went wrong?
-Added 0a5c_22be folder + .zhx into firmware folder.
-Added 0a5c_22be key into BrcmPatchRAM2-Info.plist
-Build and install BrcmPatchRAM2 + BrcmFirmwareRepo.kext into S/L/E
-Restart

 

[RehabMan]

Tried the below, bluetooth is able to show in system report, but unable to detect any device to pair. Any suggestions on what went wrong?
-Added 0a5c_22be folder + .zhx into firmware folder.
-Added 0a5c_22be key into BrcmPatchRAM2-Info.plist
-Build and install BrcmPatchRAM2 + BrcmFirmwareRepo.kext into S/L/E
-Restart

Check system logs to be certain firmware loaded. Compare with firmware used by Windows. Test hardware on Windows to be certain it is installed correctly (eg. antennas connected/etc).

 

[fminus]

Do you recommend the DW 1560 or the DW1830? I see much love for the 1560, but not much for the 1830. It seems better on paper.

 

[RehabMan]

Do you recommend the DW 1560 or the DW1830? I see much love for the 1560, but not much for the 1830. It seems better on paper.

DW1560 is BCM94352Z
DW1830 is BCM943602BAED

Both are supported M.2/NGFF 2230 cards.

The BCM94360 is more natively supported (requires less patching) than the BCM94352.