Mieze Posted October 15, 2019 Share Posted October 15, 2019 As BT depends on working USB ports, check your USB configuration. Link to comment Share on other sites More sharing options...
silencer51 Posted October 15, 2019 Share Posted October 15, 2019 Just wanted to chime in and give thanks to Mieze for the best BT solution for Dell 1830 I've seen so far. This card overall is a nightmare, further solidifying my disdain for Broadcom chips. While wifi works great OOB on Mac OS, BT has been a pain in the butt, while in Windows the wifi driver is outdated and overall horrible (connection drop outs, disconnects etc. and latest version from 2017 causes a random BSOD). I really wish we had more options for compatible cards apart from Apple Airport ones (which due to the necessary adapter in most cases don't fit in laptops). Also, for the member above with issues with webcam and BT, its your USB port mapping that's the problem. Use the script here to create a custom SSDT with all your USB ports mapped: https://www.reddit.com/r/hackintosh/comments/9wkuc6/script_to_create_ssdtuiacamlinjector_kext/ 1 Link to comment Share on other sites More sharing options...
LockDown Posted October 16, 2019 Share Posted October 16, 2019 Hi @Mieze is this still correct for your v2.3.0d2? BrcmPatchRAM: for 10.10 or earlier BrcmPatchRAM2: for 10.11 - 10.14 BrcmPatchRAM3: for 10.15 Link to comment Share on other sites More sharing options...
Mieze Posted October 16, 2019 Share Posted October 16, 2019 @ellaosx Yes, but BrcmPatchRAM3 has also been successfully tested under Mojave! 2 Link to comment Share on other sites More sharing options...
SchillerX Posted October 16, 2019 Share Posted October 16, 2019 @Mieze Hi, I'm having trouble with BT, sometimes it works and sometimes it doesn't (I get this the most)... I activate BT in my DW1830 with the following steps... I hope this helps: macOS Catalina 10.15 latest supplemental update applied (15th Oct). DW1830 (BT: [0a5c:6410] BCM2045A0). HP EliteBook 840 G4, in BIOS the Wireless button is unlocked as a reference, since I've pin-taped my DW1830 it only affects BT. My USB ports are working as intended, already validated and limited using SSDT method, thanks to: https://www.reddit.com/r/hackintosh/comments/9wkuc6/script_to_create_ssdtuiacamlinjector_kext/ kexts installed: Version 2.3.0d3 ➜ Extensions pwd /Library/Extensions ➜ Extensions ls | grep Brcm AirportBrcmFixup.kextBrcmBluetoothInjector.kext BrcmFirmwareRepo.kext BrcmPatchRAM3.kext Here's what I did: Power on my laptop and BT was not available. Checked logs and noted this: (BrcmPatchRAM3) BrcmPatchRAM: uploadFirmware could not open the device! Manually loaded kext: sudo kextutil -v 5 /Library/Extensions/BrcmPatchRAM3.kext Checked logs: 2019-10-16 13:48:41.131161-0500 0x74 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000125.256635 BCM2045A0@14300000: IOUSBHostDevice::removePowerChild: BrcmPatchRAM3@(null) 2019-10-16 13:49:35.769191-0500 0x38b0 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Version 2.3.0d3 starting on OS X Darwin 19.0. 2019-10-16 13:49:35.869966-0500 0x38b0 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: USB [441CA8E34E56 v274] "BCM2045A0" by "Broadcom Corp" 2019-10-16 13:52:14.819821-0500 0x19d Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Not responding - Delaying next read. 2019-10-16 13:52:14.820466-0500 0x38b0 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: device request failed ("0xe00002d8 (UNDEFINED)" 0xe00002d8). 2019-10-16 13:52:14.820474-0500 0x38b0 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Firmware upgrade failed. 2019-10-16 13:52:14.820816-0500 0x38b0 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 159.51 seconds. Pressed the BT on/off switch in my laptop. Manually loaded BrcmPatchRAM3.kext. Still no BT. Pressed the BT on/off switch again. Loaded BrcmPatchRAM3.kext again, then checked logs. 2019-10-16 13:52:37.917573-0500 0x9559 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Version 2.3.0d3 starting on OS X Darwin 19.0. 2019-10-16 13:52:38.018334-0500 0x9559 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: USB [441CA8E34E56 v274] "BCM2045A0" by "Broadcom Corp" 2019-10-16 13:52:38.941107-0500 0x9559 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Firmware upgrade completed successfully. 2019-10-16 13:52:38.941126-0500 0x9559 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 1.23 seconds. BT becomes available and can pair with my devices. There's something weird about the on/off switch but idk if the physical button has something to do in my scenario, I see addPowerChild and removePowerChild methods in the logs, I'm guessing those are trying to do the same as if I pressed the button. Logs: ➜ Release uptime 13:53 up 7 mins, 4 users, load averages: 2.47 7.86 5.64 ➜ Release log show --predicate 'processID==0' --last 7m | grep BrcmPatch 2019-10-16 13:47:00.418078-0500 0x515 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Version 2.3.0d3 starting on OS X Darwin 19.0. 2019-10-16 13:47:01.113682-0500 0x515 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Loaded firmware "BCM20703A1_001.001.005.0214.0422_v4518.zhx" from resources. 2019-10-16 13:47:01.114364-0500 0x515 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Decompressed firmware (43444 bytes --> 109080 bytes). 2019-10-16 13:47:01.114990-0500 0x515 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Firmware is valid IntelHex firmware. 2019-10-16 13:47:01.115023-0500 0x515 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000026.422594 BCM2045A0@14300000: IOUSBHostDevice::addPowerChild: BrcmPatchRAM3@(null) 2019-10-16 13:47:01.116185-0500 0x19d Default 0x0 0 0 kernel: (IOUSBHostFamily) 000026.423756 BCM2045A0@14300000: IOUSBHostDevice::powerStateDidChangeToGated: BrcmPatchRAM3@(null) will permit idling 2019-10-16 13:47:01.216650-0500 0x515 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: uploadFirmware could not open the device! 2019-10-16 13:47:01.216654-0500 0x515 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.101 seconds. 2019-10-16 13:48:41.131161-0500 0x74 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000125.256635 BCM2045A0@14300000: IOUSBHostDevice::removePowerChild: BrcmPatchRAM3@(null) 2019-10-16 13:49:35.769191-0500 0x38b0 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Version 2.3.0d3 starting on OS X Darwin 19.0. 2019-10-16 13:49:35.869966-0500 0x38b0 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: USB [441CA8E34E56 v274] "BCM2045A0" by "Broadcom Corp" 2019-10-16 13:52:14.819821-0500 0x19d Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Not responding - Delaying next read. 2019-10-16 13:52:14.820466-0500 0x38b0 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: device request failed ("0xe00002d8 (UNDEFINED)" 0xe00002d8). 2019-10-16 13:52:14.820474-0500 0x38b0 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Firmware upgrade failed. 2019-10-16 13:52:14.820816-0500 0x38b0 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 159.51 seconds. 2019-10-16 13:52:37.917573-0500 0x9559 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Version 2.3.0d3 starting on OS X Darwin 19.0. 2019-10-16 13:52:38.018334-0500 0x9559 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: USB [441CA8E34E56 v274] "BCM2045A0" by "Broadcom Corp" 2019-10-16 13:52:38.941107-0500 0x9559 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Firmware upgrade completed successfully. 2019-10-16 13:52:38.941126-0500 0x9559 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 1.23 seconds. Regards! Alex Link to comment Share on other sites More sharing options...
Mieze Posted October 16, 2019 Share Posted October 16, 2019 (edited) This is a power management issue because firmware updates fail, when the device is power cycled by the BIOS. Use the debug builds of the kexts in order to collect more data. By the way, it's quite normal that firmware updates fail after wakeup on some notebooks, including my own, but the upgrade will be retried until it succeeds. It's not unusual that it takes 3 or 4 attempts until BT is back again. Edited October 16, 2019 by Mieze 1 Link to comment Share on other sites More sharing options...
SchillerX Posted October 16, 2019 Share Posted October 16, 2019 (edited) 2 hours ago, Mieze said: This is a power management issue because firmware updates fail, when the device is power cycled by the BIOS. Use the debug builds of the kexts in order to collect more data. Thanks for your answer @Mieze Boot macOS Catalina (Cold or warm it doesn't really matter). Pressed the Wireless button 4 times (every 5 secs), in the last (4th) I get BT working. Here's the log: ➜ Debug uptime 17:09 up 3 mins, 4 users, load averages: 14.40 11.25 4.96 ➜ Debug log show --predicate 'processID==0' --last 3m | grep BrcmPatch 2019-10-16 17:07:02.095206-0500 0x4ad Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: init 2019-10-16 17:07:02.095217-0500 0x4ad Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: probe 2019-10-16 17:07:02.095219-0500 0x4ad Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Version 2.3.0d3 starting on OS X Darwin 19.0. 2019-10-16 17:07:02.095228-0500 0x4ad Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Device doesn't support handshake. 2019-10-16 17:07:02.161523-0500 0x4ab Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Firmware store start 2019-10-16 17:07:02.161834-0500 0x4ad Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: getFirmware 2019-10-16 17:07:02.161837-0500 0x4ad Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: loadFirmware 2019-10-16 17:07:02.163593-0500 0x4ad Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource: 00000000 2019-10-16 17:07:02.408676-0500 0x25f Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2019-10-16 17:07:02.408741-0500 0x4ad Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource: 00000000 2019-10-16 17:07:02.507235-0500 0x25f Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource Callback: dc008006. 2019-10-16 17:07:02.507276-0500 0x4ad Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource: 00000000 2019-10-16 17:07:02.535763-0500 0x25f Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource Callback: 43444 bytes of data. 2019-10-16 17:07:02.535795-0500 0x4ad Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Loaded firmware "BCM20703A1_001.001.005.0214.0422_v4518.zhx" from resources. 2019-10-16 17:07:02.536415-0500 0x4ad Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Decompressed firmware (43444 bytes --> 109080 bytes). 2019-10-16 17:07:02.537165-0500 0x4ad Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Firmware is valid IntelHex firmware. 2019-10-16 17:07:02.537182-0500 0x4ad Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: start 2019-10-16 17:07:02.537194-0500 0x4ad Default 0x0 0 0 kernel: (IOUSBHostFamily) 000022.836810 BCM920703 Bluetooth 4.1@14300000: IOUSBHostDevice::addPowerChild: BrcmPatchRAM3@(null) 2019-10-16 17:07:02.537587-0500 0x82 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-16 17:07:02.538111-0500 0x82 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000022.837728 BCM920703 Bluetooth 4.1@14300000: IOUSBHostDevice::powerStateDidChangeToGated: BrcmPatchRAM3@(null) will permit idling 2019-10-16 17:07:02.638538-0500 0x4ad Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: uploadFirmware could not open the device! 2019-10-16 17:07:02.638542-0500 0x4ad Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.101 seconds. 2019-10-16 17:07:04.245826-0500 0x53b Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0 2019-10-16 17:07:04.246070-0500 0x53b Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-16 17:08:38.644176-0500 0x6f Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: stop 2019-10-16 17:08:38.644236-0500 0x74 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000119.072593 BCM920703 Bluetooth 4.1@14300000: IOUSBHostDevice::removePowerChild: BrcmPatchRAM3@(null) 2019-10-16 17:08:38.644320-0500 0x6f Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: free 2019-10-16 17:08:47.181544-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: init 2019-10-16 17:08:47.181558-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: probe 2019-10-16 17:08:47.181562-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Version 2.3.0d3 starting on OS X Darwin 19.0. 2019-10-16 17:08:47.181572-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Device doesn't support handshake. 2019-10-16 17:08:47.181578-0500 0x2800 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: getFirmware 2019-10-16 17:08:47.181581-0500 0x2800 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Retrieved cached firmware for "BCM20703A1_001.001.005.0214.0422_v4518". 2019-10-16 17:08:47.181643-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: start 2019-10-16 17:08:47.181694-0500 0x82 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-16 17:08:47.281847-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: USB [441CA8E34E56 v274] "BCM920703 Bluetooth 4.1" by "Broadcom Corp" 2019-10-16 17:08:47.281853-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Available composite configurations: 1. 2019-10-16 17:08:47.283777-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Set device configuration to configuration index 0 successfully. 2019-10-16 17:08:47.283782-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: USBDeviceShim::findFirstInterface 2019-10-16 17:08:47.283785-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: getValidatedInterface returns <private> 2019-10-16 17:08:47.283789-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Interface 0 (class ff, subclass 01, protocol 01) located. 2019-10-16 17:08:47.284034-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: set configuration and interface opened 2019-10-16 17:08:47.284037-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: findPipe: direction = 1, type = 3 2019-10-16 17:08:47.284039-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3 2019-10-16 17:08:47.284040-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: found matching endpoint 2019-10-16 17:08:47.284267-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: findPipe: direction = 0, type = 2 2019-10-16 17:08:47.284270-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3 2019-10-16 17:08:47.284272-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 2 2019-10-16 17:08:47.284275-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 0, epType = 2 2019-10-16 17:08:47.284277-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: found matching endpoint 2019-10-16 17:08:47.284519-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: got pipes 2019-10-16 17:08:47.284522-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: State "Unknown" --> "Initialize". 2019-10-16 17:08:59.610580-0500 0x53b Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Not responding - Delaying next read. 2019-10-16 17:08:59.610820-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: State "Initialize" --> "Initialize". 2019-10-16 17:08:59.611089-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: device request failed ("0xe00002d8 (UNDEFINED)" 0xe00002d8). 2019-10-16 17:08:59.611095-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: HCI_VSC_READ_VERBOSE_CONFIG failed, aborting. 2019-10-16 17:08:59.611099-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: State "Initialize" --> "Update aborted". 2019-10-16 17:08:59.611103-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Firmware upgrade failed. 2019-10-16 17:08:59.611426-0500 0x2800 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 12.429 seconds. 2019-10-16 17:08:59.611537-0500 0x6f Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: stop 2019-10-16 17:08:59.611935-0500 0x6f Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: free 2019-10-16 17:09:10.922756-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: init 2019-10-16 17:09:10.922769-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: probe 2019-10-16 17:09:10.922773-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Version 2.3.0d3 starting on OS X Darwin 19.0. 2019-10-16 17:09:10.922783-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Device doesn't support handshake. 2019-10-16 17:09:10.922790-0500 0x3048 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: getFirmware 2019-10-16 17:09:10.922793-0500 0x3048 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Retrieved cached firmware for "BCM20703A1_001.001.005.0214.0422_v4518". 2019-10-16 17:09:10.922843-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: start 2019-10-16 17:09:10.922899-0500 0x53b Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1 2019-10-16 17:09:11.022985-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: USB [441CA8E34E56 v274] "BCM920703 Bluetooth 4.1" by "Broadcom Corp" 2019-10-16 17:09:11.022991-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Available composite configurations: 1. 2019-10-16 17:09:11.024944-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Set device configuration to configuration index 0 successfully. 2019-10-16 17:09:11.024950-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: USBDeviceShim::findFirstInterface 2019-10-16 17:09:11.024954-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: getValidatedInterface returns <private> 2019-10-16 17:09:11.024959-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Interface 0 (class ff, subclass 01, protocol 01) located. 2019-10-16 17:09:11.024975-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: set configuration and interface opened 2019-10-16 17:09:11.024978-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: findPipe: direction = 1, type = 3 2019-10-16 17:09:11.024981-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3 2019-10-16 17:09:11.024983-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: found matching endpoint 2019-10-16 17:09:11.025236-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: findPipe: direction = 0, type = 2 2019-10-16 17:09:11.025238-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3 2019-10-16 17:09:11.025240-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 2 2019-10-16 17:09:11.025242-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 0, epType = 2 2019-10-16 17:09:11.025244-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: found matching endpoint 2019-10-16 17:09:11.025479-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: got pipes 2019-10-16 17:09:11.025482-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: State "Unknown" --> "Initialize". 2019-10-16 17:09:11.042889-0500 0x15b Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: READ VERBOSE CONFIG complete (status: 0x00, length: 10 bytes). 2019-10-16 17:09:11.042895-0500 0x15b Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Firmware version: v4518. 2019-10-16 17:09:11.042905-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: State "Initialize" --> "Update not needed". 2019-10-16 17:09:11.042910-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6410]: Firmware upgrade not needed. 2019-10-16 17:09:11.042951-0500 0x3048 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.120 seconds. Edited October 16, 2019 by SchillerX Link to comment Share on other sites More sharing options...
Mieze Posted October 16, 2019 Share Posted October 16, 2019 (edited) I disabled the wireless button in BIOS setup because I realized that macOS doesn't cope well with it because there is no such button on real Macs. EDIT: Pin-taping devices may cause trouble as the BIOS will assume that the device isn't present and may fail to power it properly on boot/wakeup but I know the problems with WIFI whitelisting on HP and Lenovo notebooks. Edited October 16, 2019 by Mieze 2 Link to comment Share on other sites More sharing options...
vanquybn Posted October 17, 2019 Share Posted October 17, 2019 I have just tested all version in this topic. All of them does not work for me if i put following ket in to L/E: BrcmBluetoothInjector.kext BrcmFirmwareRepo.kext BrcmPatchRAM3.kext However it work if it use following way: Put BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext into L/E and BrcmPatchRAM3.kext into clover Or put BrcmBluetoothInjector.kext, BrcmFirmwareData.kext, BrcmPatchRAM3.kext into clover 1 Link to comment Share on other sites More sharing options...
headkaze Posted October 17, 2019 Author Share Posted October 17, 2019 We have moved to https://github.com/acidanthera/BrcmPatchRAM Thanks to vit9696 and Mieze! 1 1 Link to comment Share on other sites More sharing options...
bronxteck Posted October 18, 2019 Share Posted October 18, 2019 (edited) Hi @headkaze I see they merged the changes but the last release over at git is from July 16 2018 will they be making a release version soon? Edited October 18, 2019 by bronxteck 1 Link to comment Share on other sites More sharing options...
XploRa_1 Posted October 18, 2019 Share Posted October 18, 2019 On 10/17/2019 at 5:09 AM, vanquybn said: Or put BrcmBluetoothInjector.kext, BrcmFirmwareData.kext, BrcmPatchRAM3.kext into clover Thanks, this works for me too. Link to comment Share on other sites More sharing options...
XploRa_1 Posted October 18, 2019 Share Posted October 18, 2019 The Logitech Triathlon M720 is very difficult to get paired, but this just worked without problems. Link to comment Share on other sites More sharing options...
headkaze Posted October 18, 2019 Author Share Posted October 18, 2019 12 hours ago, bronxteck said: Hi @headkaze I see they merged the changes but the last release over at git is from July 16 2018 will they be making a release version soon? Yeah sorry I didn't realize there was no binary up yet. Please use Mieze's links for now. Link to comment Share on other sites More sharing options...
Mieze Posted October 18, 2019 Share Posted October 18, 2019 Here are binaries of the latest build which I'm using for test purposes. Please use this as an intermediate solution as long as there is no official release. BrcmPatchRAM-2019-10-17.zip 4 Link to comment Share on other sites More sharing options...
bronxteck Posted October 18, 2019 Share Posted October 18, 2019 Thank you Mieze and Headkaze. Link to comment Share on other sites More sharing options...
PepsiColaNYC Posted October 19, 2019 Share Posted October 19, 2019 This is really great, thanks so much for making this work so well. On Catalina, I had a DW1560 with working WiFi but wasn't able to get the Bluetooth working correctly. However, I suspect a USB configuration issue, rather than an issue with these kexts. I returned the DW1560. Now I have a Broadcom 20702A3-based USB BT dongle. I installed the kexts as instructed in /L/E, and confirm updated firmware v14 c5860 after a cold boot. However, things are not yet working 100%: Bluetooth shows a disabled icon and "unavailable" after boot, even with v14 c5860 firmware correctly installed. If I unplug and replug the dongle, Bluetooth then becomes available. Could this be a USB configuration issue? Even when Bluetooth is working, Airdrop / handoff / continuity don't. System Report shows Handoff Supported as "No". I tried the "10.11.dp1+ BT4LE-Handoff-Hotspot, credit RehabMan based on Dokterdok original" patch but it does not seem to have made a difference. Link to comment Share on other sites More sharing options...
Mieze Posted October 19, 2019 Share Posted October 19, 2019 @PepsiColaNYC Why are you asking us? Ask your kernel logs! You'll find the answer there! 2 Link to comment Share on other sites More sharing options...
drewmu Posted October 19, 2019 Share Posted October 19, 2019 Help, please? I have an Azurewave (4352HMB) [13d3:3404] that worked prior to the upgrade to Catalina. I followed the instructions and am using BrcmPatchRAM3, BrcmBluetoothInjector, and BcrmFirmwareData, all injected via Clover the the kext/other folder. Bluetooth shows up but does not detect any devices. System info shows the firmware is not loaded (4096 v14). Not sure what is going on... here is the log: 2019-10-19 11:22:13.606532-0400 0x65 Default 0x0 0 0 kernel: Refusing new kext com.no-one.BrcmFirmwareStore, v2.2.12: already have prelinked v2.2.7. 2019-10-19 11:22:27.739426-0400 0x504 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Version 2.2.7 starting on OS X Darwin 19.0. 2019-10-19 11:22:27.739429-0400 0x504 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Unknown new Darwin version 19.0, using possible compatible personality. 2019-10-19 11:22:27.740969-0400 0x504 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Published new IOKit personality for BrcmFirmwareStore. 2019-10-19 11:22:27.766544-0400 0x504 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Published new IOKit personality for BrcmPatchRAMResidency. 2019-10-19 11:22:28.297817-0400 0x28a Error 0x0 74 0 kextd: (IOKit) [com.apple.kext:kextlog] Kext with invalid signature (-67062) allowed: <OSKext 0x600000a0cc60 [0x7fff8e4cfb00]> { URL = "file:///Library/Extensions/BrcmFirmwareRepo.kext/", ID = "com.no-one.BrcmFirmwareStore" } 2019-10-19 11:22:28.509771-0400 0x504 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Loaded firmware "BCM20702A1_001.002.014.1443.1479_v5575.zhx" from resources. 2019-10-19 11:22:28.510153-0400 0x504 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Decompressed firmware (29713 bytes --> 70105 bytes). 2019-10-19 11:22:28.510514-0400 0x504 Default 0x0 0 0 kernel: (BrcmFirmwareRepo) BrcmPatchRAM: Firmware is valid IntelHex firmware. 2019-10-19 11:22:28.510534-0400 0x504 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: uploadFirmware could not open the device! 2019-10-19 11:22:28.511450-0400 0x504 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [13d3:3404]: Found existing IOKit personality "com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport". 2019-10-19 11:22:28.511456-0400 0x504 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Processing time 0.772 seconds. 2019-10-19 11:22:28.514241-0400 0x504 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Version 2.2.7 starting on OS X Darwin 19.0. 2019-10-19 11:22:28.514264-0400 0x504 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: uploadFirmware could not open the device! 2019-10-19 11:22:28.515080-0400 0x504 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [13d3:3404]: Found existing IOKit personality "com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport". 2019-10-19 11:22:28.515086-0400 0x504 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Processing time 0.0 seconds. 2019-10-19 11:22:54.937210-0400 0xc06 Default 0x359e 385 0 AdvancedBlocking: (libswiftFoundation.dylib) The extension received a message (getAdvancedBlockingData) from a script injected into (https://www.insanelymac.com/forum/topic/339175-brcmpatchram2-for-1015-catalina-broadcom-bluetooth-firmware-upload/?page=8) with userInfo ([:]) 2019-10-19 11:29:29.111662-0400 0x3b06 Default 0xf4f0 1620 0 AdvancedBlocking: (libswiftFoundation.dylib) The extension received a message (getAdvancedBlockingData) from a script injected into (https://github.com/acidanthera/BrcmPatchRAM) with userInfo ([:]) 1 Link to comment Share on other sites More sharing options...
AlbertoSONIC Posted October 19, 2019 Share Posted October 19, 2019 Could somebody upload the binaries? Every download link I've found on this thread gives me 404... Thanks! Link to comment Share on other sites More sharing options...
Mieze Posted October 19, 2019 Share Posted October 19, 2019 @AlbertoSONIC You are one click away from it, just have to download! Link to comment Share on other sites More sharing options...
AlbertoSONIC Posted October 19, 2019 Share Posted October 19, 2019 (edited) 10 minutes ago, Mieze said: @AlbertoSONIC You are one click away from it, just have to download! From where? Releases on github are pretty old... EDIT: nvm, found it! Edited October 19, 2019 by AlbertoSONIC 2 Link to comment Share on other sites More sharing options...
pantherstoner12 Posted October 20, 2019 Share Posted October 20, 2019 @Mieze Thanks for your great work. Is it possible for you to add AR3012 [0489:e036] support? I am running the High Sierra. Link to comment Share on other sites More sharing options...
tonymoses Posted October 21, 2019 Share Posted October 21, 2019 Mieze在2019/10/19的AM1点54分说: 这是我用作测试目的的最新版本的二进制文件。如果没有正式版本,则替换为中间解决方案。 BrcmPatchRAM-2019-10-17.zip Hello, I am 94352hmb, after updating 2.5, Bluetooth can not find the device? Link to comment Share on other sites More sharing options...
Mieze Posted October 21, 2019 Share Posted October 21, 2019 7 hours ago, tonymoses said: Hello, I am 94352hmb, after updating 2.5, Bluetooth can not find the device? You might want to look at your kernel logs! Link to comment Share on other sites More sharing options...
Recommended Posts