meiyong Posted June 28, 2019 Share Posted June 28, 2019 On 2019/6/20 at 12:27 AM, thetwoangels said: It works very well, thanks for the great work you do and help us to the least we know how to continue to enjoy this great operating system. Successfully modified BrcmBluetoothInjector-Info.plist and BrcmPatchRAM2-Info.plist for BCM943602BAED Could you please upload your modified file? Mys is the same as yours. Thank you Link to comment Share on other sites More sharing options...
headkaze Posted June 28, 2019 Author Share Posted June 28, 2019 (edited) I've updated BrcmBluetoothInjector to include all the missing device-id's from BrcmPatchRAM2. - Added the following device-id's (vid:pid) to BrcmBluetoothInjector: 0489:e046, 0489:e04f, 0489:e052, 0489:e055, 0489:e059, 0489:e087, 0489:e096, 0489:e0a1, 04ca:2004, 04ca:2005, 04ca:2006, 04ca:2009, 04ca:200e, 04ca:2012, 04ca:2016, 04f2:b4a1, 0930:021e, 0930:021f, 0930:0225, 0930:0226, 0930:0229, 0a5c:2168, 0a5c:2169, 0a5c:216a, 0a5c:216c, 0a5c:216d, 0a5c:21d7, 0a5c:21e3, 0a5c:21f1, 0a5c:21f3, 0a5c:21f4, 0a5c:640b, 0a5c:6410, 0a5c:6412, 0a5c:6413, 0a5c:6414, 0a5c:6417, 0a5c:6418, 0a5c:7460, 0b05:17b5, 0bb4:0306, 105b:e065, 105b:e066, 13d3:3384, 13d3:3388, 13d3:3389, 13d3:3392, 13d3:3427, 13d3:3482, 13d3:3484, 13d3:3504, 13d3:3508, 145f:01a3, 413c:8197 - Already supported device-id's (vid:pid) in BrcmBluetoothInjector: 0489:e032, 0489:e042, 0489:e079, 0489:e07a, 04ca:2003, 04ca:200a, 04ca:200b, 04ca:200c, 04ca:200f, 050d:065a, 0930:0221, 0930:0223, 0a5c:216b, 0a5c:216e, 0a5c:216f, 0a5c:21de, 0a5c:21e1, 0a5c:21e6, 0a5c:21e8, 0a5c:21ec, 0a5c:21fb, 0a5c:21fd, 0b05:17cb, 0b05:17cf, 0b05:180a, 13d3:3404, 13d3:3411, 13d3:3413, 13d3:3418, 13d3:3435, 13d3:3456, 413c:8143 I've also created a Github fork of the project @ OS-X-BrcmPatchRAM Downloads are now available here Edited June 28, 2019 by headkaze Link to comment Share on other sites More sharing options...
sonicthehedgehog2 Posted June 28, 2019 Share Posted June 28, 2019 Hi Headkaze, I've just finished installing the new kexts and they work beautifully (For some strange reason I couldn't get the cp commands to work properly - error message about no such file or folder - so instead I used Kext Utility, rebooted and success). Many thanks for putting these together. 1 Link to comment Share on other sites More sharing options...
headkaze Posted June 28, 2019 Author Share Posted June 28, 2019 4 hours ago, meiyong said: Could you please upload your modified file? Mys is the same as yours. Thank you BrcmBluetoothInjector has been updated to include 0a5c:6410 1 Link to comment Share on other sites More sharing options...
headkaze Posted June 28, 2019 Author Share Posted June 28, 2019 (edited) On 6/19/2019 at 6:03 AM, fromdetroit7 said: headkaze, can you please add 21ff_0a5c as well? Attached are updated BrcmPatchRAM2-Info.plist and BrcmBluetoothInjector-Info.plist files (copy them over BrcmPatchRAM2.kext/Contents/Info.plist and BrcmBluetoothInjector.kext/Contents/Info.plist respectively). What I've done is add the firmware from 0a5c:21fd (BCM20702A1_001.002.014.1443.1463_v5559) for your 0a5c:21ff entry. Can you give it a try and let me know if it works. If it does I'll add it to the official release. BrcmBluetoothInjector-Info.zip Edited June 28, 2019 by headkaze Link to comment Share on other sites More sharing options...
LockDown Posted June 29, 2019 Share Posted June 29, 2019 @headkaze About your released over at github, that can be use in Highsierra too, or exclusively for catalina? Link to comment Share on other sites More sharing options...
meiyong Posted June 29, 2019 Share Posted June 29, 2019 11 hours ago, headkaze said: BrcmBluetoothInjector has been updated to include 0a5c:6410 thanks Link to comment Share on other sites More sharing options...
lanzaozijun Posted June 29, 2019 Share Posted June 29, 2019 0a5c:6412 1820A无法驱动 Link to comment Share on other sites More sharing options...
headkaze Posted June 29, 2019 Author Share Posted June 29, 2019 (edited) 5 hours ago, lanzaozijun said: 0a5c:6412 1820A无法驱动 What is the log output? Successful firmware upgrade should look like this: 2019-06-29 12:25:57.923689-0700 localhost kernel[0]: (kernel) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 19.0. 2019-06-29 12:25:57.940191-0700 localhost kernel[0]: (kernel) BrcmPatchRAM2: Unknown new Darwin version 19.0, using possible compatible personality. 2019-06-29 12:26:17.208045-0700 localhost kernel[0]: (kernel) BrcmPatchRAM: Loaded compressed embedded firmware for key "BCM20702A1_001.002.014.1443.1572_v5668". 2019-06-29 12:26:17.217894-0700 localhost kernel[0]: (kernel) BrcmPatchRAM: Decompressed firmware (29651 bytes --> 70012 bytes). 2019-06-29 12:26:17.218331-0700 localhost kernel[0]: (kernel) BrcmPatchRAM: Firmware is valid IntelHex firmware. 2019-06-29 12:26:17.218435-0700 localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:216f]: USB [184F32F341D4 v274] "BCM20702A0" by "Broadcom Corp" 2019-06-29 12:26:17.820577-0700 localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:216f]: Firmware upgrade completed successfully. 2019-06-29 12:26:18.135008-0700 localhost kernel[0]: (kernel) BrcmPatchRAM2: Processing time 21.599 seconds. 2019-06-29 12:26:18.151797-0700 localhost kernel[0]: (kernel) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 19.0. 2019-06-29 12:26:20.168330-0700 localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:216f]: BrcmPatchRAMResidency does not appear to be available. 2019-06-29 12:26:20.192004-0700 localhost kernel[0]: (kernel) BrcmPatchRAM2: uploadFirmware could not open the device! 2019-06-29 12:26:20.207301-0700 localhost kernel[0]: (kernel) BrcmPatchRAM2: Processing time 2.40 seconds. You can use Hackintool to capture log output if you're not sure how: Edited June 29, 2019 by headkaze 1 Link to comment Share on other sites More sharing options...
lanzaozijun Posted June 30, 2019 Share Posted June 30, 2019 (edited) 1820A Starting with mojave Bluetooth upload firmware should be a problem. To use the 5799 firmware only with a virtual machine. Please forgive me, English is not very good. 2019-06-30 15:14:20.620108+0800 localhost kernel[0]: (AirPortBrcmNIC) <AirPortBrcmNIC`osl_iolog_withtimestamp> ARPT: 17.291660: AirPort_Brcm43XX:probe:, this[0xda9645fceb7a4e9f] score[1400] 2019-06-30 15:14:20.649225+0800 localhost kernel[0]: (AirPortBrcmNIC) <AirPortBrcmNIC`osl_iolog_withtimestamp> ARPT: 17.320776: BRCM tunables: 2019-06-30 15:14:22.721362+0800 localhost kernel[0]: (IO80211Family) <IO80211Family`IO80211Controller::logDebug(char const*, ...)> AirPort_BrcmNIC::getSSIDData(): Get failure: APPLE80211_IOC_SSID: 6 2019-06-30 15:14:22.843428+0800 localhost kernel[0]: (kernel) BrcmPatchRAM: Loaded compressed embedded firmware for key "BCM4350C5_003.006.007.0095.1703_v5799". 2019-06-30 15:14:22.843589+0800 localhost kernel[0]: (kernel) BrcmPatchRAM: Decompressed firmware (5886 bytes --> 14872 bytes). 2019-06-30 15:14:22.843702+0800 localhost kernel[0]: (kernel) BrcmPatchRAM: Firmware is valid IntelHex firmware. 2019-06-30 15:14:22.843743+0800 localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:6412]: USB [ACE010953662 v274] "BCM2045A0" by "Broadcom Corp" 2019-06-30 15:14:23.112047+0800 localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:6412]: Firmware upgrade completed successfully. 2019-06-30 15:14:23.112064+0800 localhost kernel[0]: (kernel) BrcmPatchRAM2: Processing time 18.887 seconds. 2019-06-30 15:14:23.113930+0800 localhost kernel[0]: (kernel) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 19.0. 2019-06-30 15:14:25.115034+0800 localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:6412]: BrcmPatchRAMResidency does not appear to be available. 2019-06-30 15:14:25.115102+0800 localhost kernel[0]: (kernel) BrcmPatchRAM2: uploadFirmware could not open the device! 2019-06-30 15:14:25.115108+0800 localhost kernel[0]: (kernel) BrcmPatchRAM2: Processing time 2.1 seconds. 2019-06-30 15:14:25.120017+0800 localhost kernel[0]: (kernel) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 19.0. 2019-06-30 15:14:27.121157+0800 localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:6412]: BrcmPatchRAMResidency does not appear to be available. 2019-06-30 15:14:27.121224+0800 localhost kernel[0]: (kernel) BrcmPatchRAM2: uploadFirmware could not open the device! 2019-06-30 15:14:27.121231+0800 localhost kernel[0]: (kernel) BrcmPatchRAM2: Processing time 2.1 seconds. 2019-06-30 15:14:27.357586+0800 localhost kernel[0]: (IO80211Family) <IO80211Family`IO80211VirtualInterface::init(IO80211Controller*, ether_addr*, unsigned int, char const*)> IO80211VirtualInterface::AirPort_BrcmNIC_P2PInterface::init name <p2p0> role 1 2019-06-30 15:14:27.358190+0800 localhost kernel[0]: (IO80211Family) <IO80211Family`IO80211P2PInterface::init(IO80211Controller*, ether_addr*, unsigned int, char const*)> AirPort_BrcmNIC_P2PInterface::init <p2p> role 1 2019-06-30 15:14:28.158919+0800 localhost kernel[0]: (IO80211Family) <IO80211Family`IO80211VirtualInterface::init(IO80211Controller*, ether_addr*, unsigned int, char const*)> IO80211VirtualInterface::AirPort_BrcmNIC_P2PInterface::init name <awdl0> role 4 2019-06-30 15:14:28.158926+0800 localhost kernel[0]: (IO80211Family) <IO80211Family`IO80211P2PInterface::awdlAttachToBpf()> AirPort_BrcmNIC_P2PInterface::awdlAttachToBpf name <awdl0> role 4 successful attach to bpf type 147 2019-06-30 15:14:28.161245+0800 localhost kernel[0]: (IO80211Family) <IO80211Family`IO80211P2PInterface::init(IO80211Controller*, ether_addr*, unsigned int, char const*)> AirPort_BrcmNIC_P2PInterface::init <awdl> role 4 Edited July 1, 2019 by lanzaozijun Link to comment Share on other sites More sharing options...
Zhen-zen Posted June 30, 2019 Share Posted June 30, 2019 (edited) Hello, I just tried your fork on BCM94352Z with 0489:e07a BCM20702A0 but it didn't work. With Rehabman's fork, I use BrcmPatchRAM2 and merged BrcmFirmwareRepo with Injector plist. They are injected via OC, worked in Mojave but not in Catalina. After I replaced them with your build, they won't work in both macOS version. The BrcmPatchRAM2 is not loaded in Catalina, while both BrcmFirmwareData and Injector could load successfully and appeared in IOReg. I have also installed it with BrcmFirmwareRepo to LE but also no success. The kext is loaded in Mojave, but Bluetooth is not functional, shown as "Bluetooth: Not available" in menu bar. I have collected following log: Your build: 2019-06-30 15:33:45.386543-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: No firmware available for firmware key "BCM20702A1_001.002.014.1483.1651_v5747". 2019-06-30 15:33:45.386570-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: [0489:e07a]: USB ["MAC addr" v274] "BCM20702A0" by "Broadcom Corp" 2019-06-30 15:33:45.578595-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: No firmware available for firmware key "BCM20702A1_001.002.014.1483.1651_v5747". 2019-06-30 15:33:45.578620-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: [0489:e07a]: Firmware upgrade failed. 2019-06-30 15:33:45.578654-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: Processing time 10.154 seconds. 2019-06-30 15:33:45.578668-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 18.6. 2019-06-30 15:33:47.578759-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: [0489:e07a]: BrcmPatchRAMResidency does not appear to be available. 2019-06-30 15:33:47.954451-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Retrieved firmware "0489_e07a_v5747" from internal configuration. 2019-06-30 15:33:47.954936-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Decompressed firmware (29732 bytes --> 70201 bytes). 2019-06-30 15:33:47.955324-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Firmware is valid IntelHex firmware. 2019-06-30 15:33:47.955373-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: [0489:e07a]: USB ["MAC addr" v274] "BCM20702A0" by "Broadcom Corp" 2019-06-30 15:33:48.464769-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: [0489:e07a]: Firmware upgrade completed successfully. 2019-06-30 15:33:48.464805-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: Processing time 2.886 seconds. 2019-06-30 15:33:48.467898-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 18.6. 2019-06-30 15:33:50.468992-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: [0489:e07a]: BrcmPatchRAMResidency does not appear to be available. 2019-06-30 15:33:50.520840-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: No firmware available for firmware key "BCM20702A1_001.002.014.1483.1651_v5747". 2019-06-30 15:33:50.520906-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: [0489:e07a]: USB ["MAC addr" v274] "BCM20702A0" by "Broadcom Corp" 2019-06-30 15:33:50.544774-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: [0489:e07a]: Firmware upgrade not needed. 2019-06-30 15:33:50.544863-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: Processing time 2.76 seconds. 2019-06-30 15:33:50.544894-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 18.6. 2019-06-30 15:33:52.545020-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: [0489:e07a]: BrcmPatchRAMResidency does not appear to be available. 2019-06-30 15:33:52.545102-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: [0489:e07a]: USB ["MAC addr" v274] "BCM20702A0" by "Broadcom Corp" 2019-06-30 15:33:52.546949-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: [0489:e07a]: Firmware upgrade not needed. 2019-06-30 15:33:52.547047-0700 0x1b6 Default 0x0 0 0 kernel: (BrcmPatchRAM2) BrcmPatchRAM2: Processing time 2.2 seconds. Rehabman's build: 2019-06-30 15:42:13.196703-0700 0x1ba Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Retrieved firmware "0489_e07a_v5747" from internal configuration. 2019-06-30 15:42:13.197371-0700 0x1ba Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Decompressed firmware (29732 bytes --> 70201 bytes). 2019-06-30 15:42:13.197749-0700 0x1ba Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Firmware is valid IntelHex firmware. 2019-06-30 15:42:13.197772-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0489:e07a]: USB ["MAC addr" v274] "BCM20702A0" by "Broadcom Corp" 2019-06-30 15:42:13.256374-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0489:e07a]: Firmware upgrade not needed. 2019-06-30 15:42:13.258484-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0489:e07a]: Published new IOKit personality. 2019-06-30 15:42:13.260116-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Processing time 9.896 seconds. 2019-06-30 15:42:13.260127-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 18.6. 2019-06-30 15:42:13.436925-0700 0x1ba Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: No firmware available for firmware key "BCM20702A1_001.002.014.1483.1651_v5747". 2019-06-30 15:42:13.436955-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0489:e07a]: USB ["MAC addr" v274] "BCM20702A0" by "Broadcom Corp" 2019-06-30 15:42:13.438372-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0489:e07a]: Firmware upgrade not needed. 2019-06-30 15:42:13.440195-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0489:e07a]: Found existing IOKit personality "com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport". 2019-06-30 15:42:13.440202-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Processing time 0.180 seconds. 2019-06-30 15:42:13.445984-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 18.6. 2019-06-30 15:42:13.446022-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0489:e07a]: USB ["MAC addr" v274] "BCM20702A0" by "Broadcom Corp" 2019-06-30 15:42:13.447368-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0489:e07a]: Firmware upgrade not needed. 2019-06-30 15:42:13.448883-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0489:e07a]: Found existing IOKit personality "com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport". 2019-06-30 15:42:13.448890-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Processing time 0.2 seconds. 2019-06-30 15:42:13.448900-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 18.6. 2019-06-30 15:42:13.511535-0700 0x1ba Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: No firmware available for firmware key "BCM20702A1_001.002.014.1483.1651_v5747". 2019-06-30 15:42:13.511578-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0489:e07a]: USB ["MAC addr" v274] "BCM20702A0" by "Broadcom Corp" 2019-06-30 15:42:13.512381-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0489:e07a]: Firmware upgrade not needed. 2019-06-30 15:42:13.514346-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0489:e07a]: Found existing IOKit personality "com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport". 2019-06-30 15:42:13.514356-0700 0x1ba Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Processing time 0.65 seconds. Thank you. Update: I forgot to attribute the IOKitPersonalities to specify the ID, so the driver failed to load. After I merged the Injector to Repo kext, everything works again on Mojave. So the logs ahead could be ignored. However, the BrcmPatchRAM2 kext are still not loaded in Catalina, while that firmwarestore (with injector) one works and lead to 4096 firmware. I'm still investigating the issue. Edited July 2, 2019 by gongzhen Link to comment Share on other sites More sharing options...
onemanOSX Posted July 2, 2019 Share Posted July 2, 2019 (edited) No issues here using all three BRCM kexts in Catalina as per OP Edited July 2, 2019 by onemanOSX 1 Link to comment Share on other sites More sharing options...
headkaze Posted July 2, 2019 Author Share Posted July 2, 2019 On 6/30/2019 at 4:03 PM, gongzhen said: Update: I forgot to attribute the IOKitPersonalities to specify the ID, so the driver failed to load. After I merged the Injector to Repo kext, everything works again on Mojave. So the logs ahead could be ignored. However, the BrcmPatchRAM2 kext are still not loaded in Catalina, while that firmwarestore (with injector) one works and lead to 4096 firmware. I'm still investigating the issue. Going by your log it looks like you had multiple installs of the kexts. Make sure you only have them in one place. You shouldn't need to add 0489:e07a to IOKitPersonalities as it's already supported. What plist did you need to add it to? 4096 is indication of the firmware failing to be uploaded not success. On 6/29/2019 at 10:57 PM, lanzaozijun said: 1820A Starting with mojave Bluetooth upload firmware should be a problem. To use the 5799 firmware only with a virtual machine. Please forgive me, English is not very good. Your log shows the firmware was uploaded successfully. So is BrcmBluetoothInjector failing to load Apple's native driver? Are you sure you have the latest version from Github since 0a5c:6412 was only added in a recent update. 48 minutes ago, nytr0 said: When I try to load BrcmPatchRAM2 in Catalina dp2 with Opencore 0.0.3, I get "Invalid Parameter" and the kext won't load.. I have a DW1560 bluetooth 0a5c_216f. Should this be working or is a fix in the process? Or, could it be that i'm doing something wrong? Can you post the actual log where it shows "Invalid Parameter"? Link to comment Share on other sites More sharing options...
headkaze Posted July 2, 2019 Author Share Posted July 2, 2019 1 hour ago, nytr0 said: This is the opencore 0.0.3 log. I have the latest release of brcmpatchram2 from your github. opencore.log It looks like an issue with OC injecting the kext not with the kext itself. Probably best to try one of the OC forums here. 1 Link to comment Share on other sites More sharing options...
lanzaozijun Posted July 3, 2019 Share Posted July 3, 2019 10 hours ago, headkaze said: 按照你的日志,看起来你有多个安装的kexts。确保你只在一个地方。 您不需要将0489:e07a添加到IOKitPersonalities,因为它已经被支持。您需要将它添加到什么plist? 4096表示固件无法上传但未成功。 您的日志显示固件已成功上载。那么BrcmBluetoothInjector是否无法加载Apple的本机驱动程序?你确定你拥有Github的最新版本,因为0a5c:6412只是在最近的更新中添加的。 你能发布显示“无效参数”的实际日志吗? Confirm the latest github used. It is available to restart from win to mac Bluetooth... This phenomenon should start from 10.14. DW1820A Bluetooth has been bothering me. Link to comment Share on other sites More sharing options...
headkaze Posted July 3, 2019 Author Share Posted July 3, 2019 (edited) 5 hours ago, lanzaozijun said: Confirm the latest github used. It is available to restart from win to mac Bluetooth... This phenomenon should start from 10.14. DW1820A Bluetooth has been bothering me. Your log shows: [0a5c:6412]: Firmware upgrade completed successfully. So upload is successful but it seems BrcmBluetoothInjector fails to load the native driver (BroadcomBluetoothHostControllerUSBTransport) afterwards. Where are you installing the kexts? Edited July 3, 2019 by headkaze Link to comment Share on other sites More sharing options...
lanzaozijun Posted July 3, 2019 Share Posted July 3, 2019 (edited) 3小时前,headkaze说: 您的日志显示: 所以上传成功但似然BrcmBluetoothInjector之后无法加载本机驱动程序(BroadcomBluetoothHostControllerU SBTransport)。你在哪里安装kexts? C/k/o Edited July 3, 2019 by lanzaozijun Link to comment Share on other sites More sharing options...
sefki Posted July 14, 2019 Share Posted July 14, 2019 (edited) hi I'm running Catalina 19A501i on my new Dell XPS 7950. Everything works smooth except the communication with my Apple Watch. Handoff (and all other related stuff like clipboard, taking pictures..) with iPhone works great and fast but not at all with Apple Watch (handoff, unlock). Got the DW 1830, running your latest kexts, FW upload is successful. (thanks at this point for your great work!). Could it be firmware or kext related? Is someone aware of this kind of issues with DW1830? Edited July 14, 2019 by sefki Link to comment Share on other sites More sharing options...
dolgarrenan Posted July 16, 2019 Share Posted July 16, 2019 Hi there @headkaze I have mixed results with your method, at the end, in order to have the DW1820A work (0xa5c_6412) I have to boot into W10 or Linux, then it works. If I turn off the computer and cut the power (like a power cycle) when turns on again my Bluetooth doesn't work anymore.. Here is a screenshot of log (.kext are located at /CLOVER/Kext/Other y previously had them inside /Library/Extensions/) Link to comment Share on other sites More sharing options...
sonicthehedgehog2 Posted July 16, 2019 Share Posted July 16, 2019 On 7/14/2019 at 8:01 PM, sefki said: hi I'm running Catalina 19A501i on my new Dell XPS 7950. Everything works smooth except the communication with my Apple Watch. Handoff (and all other related stuff like clipboard, taking pictures..) with iPhone works great and fast but not at all with Apple Watch (handoff, unlock). Got the DW 1830, running your latest kexts, FW upload is successful. (thanks at this point for your great work!). Could it be firmware or kext related? Is someone aware of this kind of issues with DW1830? It may just be a case of lag. I have a Dell XPS 8500 with BCM94352. Handoff took about 2 days (no action taken by me other than installing kexts) before handoff started working with my iPAD and 3 days before it worked with my iPhone. Link to comment Share on other sites More sharing options...
headkaze Posted July 16, 2019 Author Share Posted July 16, 2019 6 hours ago, dolgarrenan said: Hi there @headkaze I have mixed results with your method, at the end, in order to have the DW1820A work (0xa5c_6412) I have to boot into W10 or Linux, then it works. If I turn off the computer and cut the power (like a power cycle) when turns on again my Bluetooth doesn't work anymore.. Here is a screenshot of log (.kext are located at /CLOVER/Kext/Other y previously had them inside /Library/Extensions/) You've posted a log of an unsuccessful firmware upload due to it already being uploaded (in your case most likely by Windows). You need to post the log showing the failed upload. Link to comment Share on other sites More sharing options...
sonicthehedgehog2 Posted July 17, 2019 Share Posted July 17, 2019 On 6/28/2019 at 8:37 PM, sonicthehedgehog2 said: Hi Headkaze, I've just finished installing the new kexts and they work beautifully (For some strange reason I couldn't get the cp commands to work properly - error message about no such file or folder - so instead I used Kext Utility, rebooted and success). Many thanks for putting these together. No longer working after update to 10.15 Beta (19A512f). System reports Firmware version as v14 c4096 using BCM94352HCM. When I have more time, I'll investigate further. Link to comment Share on other sites More sharing options...
dolgarrenan Posted July 17, 2019 Share Posted July 17, 2019 20 hours ago, headkaze said: You've posted a log of an unsuccessful firmware upload due to it already being uploaded (in your case most likely by Windows). You need to post the log showing the failed upload. Here is the log without firmware update from Windows. Here is the IOReg screen Funny because I try to manually edit BrcmPatchRAM2.plist in order to load latest Firmware in your repo (v6820) but it just doesn't work shows fw V4096.. I'll try your firmware with old set of .kext (RehabMan's) to see if any difference.. Link to comment Share on other sites More sharing options...
headkaze Posted July 18, 2019 Author Share Posted July 18, 2019 15 hours ago, dolgarrenan said: Here is the log without firmware update from Windows. The error code 0xe00002ed refers to an IO error communicating with the Bluetooth device. Have you ever had Bluetooth working on your Hackintosh? 15 hours ago, dolgarrenan said: Funny because I try to manually edit BrcmPatchRAM2.plist in order to load latest Firmware in your repo (v6820) but it just doesn't work shows fw V4096.. I'll try your firmware with old set of .kext (RehabMan's) to see if any difference.. You shouldn't need to edit any plist for your device (0a5c:6412) as it's already supported. It also has the latest firmware (12.0.1.1010). 2 Link to comment Share on other sites More sharing options...
dolgarrenan Posted July 18, 2019 Share Posted July 18, 2019 5 hours ago, headkaze said: The error code 0xe00002ed refers to an IO error communicating with the Bluetooth device. Have you ever had Bluetooth working on your Hackintosh? Indeed. I've had several cards installed in this same build and other similar builds (DW1560), right now is sort of working with your .kexts but it has to be right next to the antena, otherwise it won't work at all, as soon as i move the device away, there is choppy behaviour or connection loss... 5 hours ago, headkaze said: You shouldn't need to edit any plist for your device (0a5c:6412) as it's already supported. It also has the latest firmware (12.0.1.1010). I have looked over at the Dell website and the latest I could find is the 12.0.1.1105, which is the one I have loaded, but still it doesn't work as it should.. Perhaps moving to Catalina would make the difference?? I don't see why this kext wouldn't work under Mojave 10.14.6... Perhaps you've modified the BrcmBluetootInjector.kext in a way that only runs in Catalina?? I've looked everywhere and could not find the kext, I've even posted an issue at @RehabMan repo but have received no reply.. Unfortunately for me moving to Catalina is not an option yet (apps and whatnot) but I need this bluetooth functionality.. Here the .kext with the latest firmware, which by chance is v4689 as it is loaded by windows correctly. BrcmFirmwareRepo.kext.zip BrcmPatchRAM2.kext.zip Link to comment Share on other sites More sharing options...
Recommended Posts