Airport Extreme branding is not needed anymore, it can be injected by ProbookARPT.kext.
Note for future ProBook Installer...
- Broadcom related entries (both WiFi and BT) should be removed from ProBookARPT.kext
- AirPort Extreme patch should be removed from config.plist
- Use FakePCIID.kext FakePCIID_BCM94352Z_as_BCM94360CS2.kext
- Use BrcmPatchRAM.kext
Airport Extreme branding is not needed anymore, it can be injected by ProbookARPT.kext.
PBI CE removed AirportExtreme patch while ago, and Airport Extreme can be injected by ProBookARPT.kext. What is the advantage of the FakePCIID compared to injector kext?
BrcmPatchRAM is already in tool, under "Broadcom Bluetooth", do you mean I should install it by default to all laptops?
OK! Thanks again. Proceeding with the process you described.
Remove any existing bluetooth firmware uploader you have (BTFirmwareUploader.kext, old version of BrcmPatchRAM.kext).
Remove ProBookARPT.kext.
Install latest FakePCIID.kext and FakePCIID_BCM94352Z_as_BCM94360CS2.kext: https://github.com/RehabMan/OS-X-Fake-PCI-ID
Remove any config.plist patch you have for AirPort Extreme branding.
Install latest BrcmPatchRAM.kext: https://github.com/RehabMan/OS-X-BrcmPatchRAM
Final config for BT/WiFi:
- BrcmPatchRAM: firmware uploader
- handoff patch in config.plistRep
- FakePCIID kexts: AirPort Extreme branding for WiFi
- 5ghz patch in config.plist
Report back on results.
OK, but please try to use quoted replies. It makes it easier to follow the conversation, especially in a busy thread like this one.
FakePCIID fakes configRead32 calls for PCI config data.
FYI: ProbookARPT.kext *is* an injector kext.
Yes I know, FakePCIID is more complete than just FakeID/Injector (as shown in HD4400/HD4600), but I don't see any practical advantage in using FakePCIID compared to ProbookARPT in Wifi. Both have stable wifi, has Airport Extreme branding, and do not support 5Ghz channel without patch.