Jump to content

BrcmPatchRAM2 for 10.15 Catalina (Broadcom bluetooth firmware upload)

headkaze

By headkaze,
in LAN and Wireless

 Share
432 posts in this topic

Recommended Posts

Gusu7
Gusu7
Posted
Posted
6 hours ago, Gusu7 said:

after upgrading to 10.15.1, the bluetooth failed again, the firmware version turns to 4096 again... 

Please kindly help, what should I do, because I tried to use Hackintool to install the 3 kexts again, but it's not working.

 


kextcache -arch x86_64 -local-root -all-loaded -kernel /System/Library/Kernels/kernel -prelinked-kernel /Library/Apple/System/Library/PrelinkedKernels/prelinkedkernel -volume-root / /Library/Extensions /AppleInternal/Library/Extensions /Library/Apple/System/Library/Extensions /System/Library/Extensions
Kext with invalid signature (-67062) allowed: <OSKext 0x7fecd9e126a0 [0x7fff84c04d10]> { URL = "file:///Library/Extensions/BrcmBluetoothInjector.kext/", ID = "org.rehabman.injector.BrcmBluetoothInjector" }
Kext with invalid signature (-67062) allowed: <OSKext 0x7fecd9e22e60 [0x7fff84c04d10]> { URL = "file:///Library/Extensions/BrcmFirmwareRepo.kext/", ID = "com.no-one.BrcmFirmwareStore" }
Kext with invalid signature (-67062) allowed: <OSKext 0x7fecd9c01150 [0x7fff84c04d10]> { URL = "file:///Library/Extensions/BrcmFirmwareData.kext/", ID = "com.no-one.BrcmFirmwareStore" }
Kext with invalid signature (-67062) allowed: <OSKext 0x7fba7942d060 [0x7fff84c04d10]> { URL = "file:///Library/Extensions/BrcmFirmwareData.kext/", ID = "com.no-one.BrcmFirmwareStore" }
Kext with invalid signature (-67062) allowed: <OSKext 0x7fba794396c0 [0x7fff84c04d10]> { URL = "file:///Library/Extensions/BrcmBluetoothInjector.kext/", ID = "org.rehabman.injector.BrcmBluetoothInjector" }
Kext with invalid signature (-67062) allowed: <OSKext 0x7fba79442180 [0x7fff84c04d10]> { URL = "file:///Library/Extensions/BrcmPatchRAM3.kext/", ID = "com.no-one.BrcmPatchRAM3" }
Kext with invalid signature (-67062) allowed: <OSKext 0x7fba79443de0 [0x7fff84c04d10]> { URL = "file:///Library/Extensions/BrcmFirmwareRepo.kext/", ID = "com.no-one.BrcmFirmwareStore" }
 

Link to comment
Share on other sites
onemanOSX
onemanOSX
Posted
Posted
16 hours ago, Gusu7 said:

after upgrading to 10.15.1, the bluetooth failed again, the firmware version turns to 4096 again... 

Please kindly help, what should I do, because I tried to use Hackintool to install the 3 kexts again, but it's not working.

 No problem here. I dont install 3rd party kexts in S/L/E or L/E but only C/K/O

Link to comment
Share on other sites
TheMaciner
TheMaciner
Posted
Posted

Thank you all for being a helpful forum!

My BT works only as intended after wake up from deep sleep. with miezes kexts. I have a 20702A3 chipset working in my latitude. Its weird that the usbport.kext things are not as easy to make as in Mojave. something changed again. 

Link to comment
Share on other sites
brookheather
brookheather
Posted
Posted (edited)
On 10/30/2019 at 3:01 PM, kolodzieski said:

10.15.1 seems to have fixed, or at least changed the bluetooth stack. My Magic Mouse 2 is working great now. 

Same here - my Logitech MX Anywhere 2 Mouse is now working with BT since I upgraded to 10.15.1.

Edited by brookheather
Link to comment
Share on other sites
k0nrad
k0nrad
Posted
Posted (edited)

The [413c:8143] Dell DW1550 (4352/20702 combo) card does not seem to support the handshake mechanism – to answer the question in line 67. :-) 

(BrcmPatchRAM3) BrcmPatchRAM: init
(BrcmPatchRAM3) BrcmPatchRAM: probe
(BrcmPatchRAM3) BrcmPatchRAM: Version 2.5.0 starting on OS X Darwin 19.0.
(BrcmPatchRAM3) BrcmPatchRAM: Device doesn't support handshake.

Also the firmware upload fails in the first place. 

(BrcmFirmwareRepo) BrcmPatchRAM: Firmware store start
(BrcmFirmwareRepo) BrcmPatchRAM: getFirmware
(BrcmFirmwareRepo) BrcmPatchRAM: loadFirmware
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource: 00000000
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource Callback: dc008006.
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource: 00000000
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource Callback: dc008006.
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource: 00000000
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource Callback: 29701 bytes of data.
(BrcmFirmwareRepo) BrcmPatchRAM: Loaded firmware "BCM20702A1_001.002.014.1443.1449_v5545.zhx" from resources.
(BrcmFirmwareRepo) BrcmPatchRAM: Decompressed firmware (29701 bytes --> 70101 bytes).
(BrcmFirmwareRepo) BrcmPatchRAM: Firmware is valid IntelHex firmware.
(BrcmPatchRAM3) BrcmPatchRAM: start
(BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
(BrcmPatchRAM3) BrcmPatchRAM: uploadFirmware could not open the device!
(BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.103 seconds.

It then succeeds after sleep/wake. 

(BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0
(BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
(BrcmPatchRAM3) BrcmPatchRAM: stop
(BrcmPatchRAM3) BrcmPatchRAM: free
(BrcmPatchRAM3) BrcmPatchRAM: init
(BrcmPatchRAM3) BrcmPatchRAM: probe
(BrcmPatchRAM3) BrcmPatchRAM: Version 2.5.0 starting on OS X Darwin 19.0.
(BrcmPatchRAM3) BrcmPatchRAM: Device doesn't support handshake.
(BrcmFirmwareRepo) BrcmPatchRAM: getFirmware
(BrcmFirmwareRepo) BrcmPatchRAM: Retrieved cached firmware for "BCM20702A1_001.002.014.1443.1449_v5545".
(BrcmPatchRAM3) BrcmPatchRAM: start
(BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: USB [B8EE65335CE4 v274] "BCM20702A0" by "Broadcom Corp"
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: Available composite configurations: 1.
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: Set device configuration to configuration index 0 successfully.
(BrcmPatchRAM3) BrcmPatchRAM: USBDeviceShim::findFirstInterface
(BrcmPatchRAM3) BrcmPatchRAM: getValidatedInterface returns <private>
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: Interface 0 (class ff, subclass 01, protocol 01) located.
(BrcmPatchRAM3) BrcmPatchRAM: set configuration and interface opened
(BrcmPatchRAM3) BrcmPatchRAM: findPipe: direction = 1, type = 3
(BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3
(BrcmPatchRAM3) BrcmPatchRAM: found matching endpoint
(BrcmPatchRAM3) BrcmPatchRAM: findPipe: direction = 0, type = 2
(BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3
(BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 2
(BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 0, epType = 2
(BrcmPatchRAM3) BrcmPatchRAM: found matching endpoint
(BrcmPatchRAM3) BrcmPatchRAM: got pipes
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: State "Unknown" --> "Initialize".
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: READ VERBOSE CONFIG complete (status: 0x00, length: 10 bytes).
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: Firmware version: v4096.
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: State "Initialize" --> "Firmware version".
(BrcmFirmwareRepo) BrcmPatchRAM: getFirmware
(BrcmFirmwareRepo) BrcmPatchRAM: Retrieved cached firmware for "BCM20702A1_001.002.014.1443.1449_v5545".
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: DOWNLOAD MINIDRIVER complete (status: 0x00, length: 4 bytes).
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: State "Firmware version" --> "Mini-driver complete".
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: END OF RECORD complete (status: 0x00, length: 4 bytes).
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: State "Instruction write" --> "Firmware written".
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: RESET complete (status: 0x00, length: 4 bytes).
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: State "Firmware written" --> "Reset complete".
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: Device reset.
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: Device status 0x00000003.
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: State "Reset complete" --> "Update complete".
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: Firmware upgrade completed successfully.
(BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.623 seconds.

The setPowerState: which = 0x0 command seems to do the trick, as it is issued only after wake. Or does it have something to do with the power state notifications (see line 198ff)?!

 

Clover r5098 / macOS 10.15.1 / BrcmBluetoothInjector.kext+BrcmFirmwareRepo.kext+BrcmPatchRAM3.kext 2.5.0 installed to /L/E

brcmpatchram3.log

Edited by k0nrad
Made the code in the post more readable and attached a log file with time stamps.
Link to comment
Share on other sites
rottenpants
rottenpants
Posted
Posted (edited)
On 11/4/2019 at 9:29 AM, k0nrad said:

The [413c:8143] Dell DW1550 (4352/20702 combo) card does not seem to support the handshake mechanism – to answer the question in line 67. :-) 


(BrcmPatchRAM3) BrcmPatchRAM: init
(BrcmPatchRAM3) BrcmPatchRAM: probe
(BrcmPatchRAM3) BrcmPatchRAM: Version 2.5.0 starting on OS X Darwin 19.0.
(BrcmPatchRAM3) BrcmPatchRAM: Device doesn't support handshake.

Also the firmware upload fails in the first place. 


(BrcmFirmwareRepo) BrcmPatchRAM: Firmware store start
(BrcmFirmwareRepo) BrcmPatchRAM: getFirmware
(BrcmFirmwareRepo) BrcmPatchRAM: loadFirmware
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource: 00000000
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource Callback: dc008006.
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource: 00000000
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource Callback: dc008006.
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource: 00000000
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource Callback: 29701 bytes of data.
(BrcmFirmwareRepo) BrcmPatchRAM: Loaded firmware "BCM20702A1_001.002.014.1443.1449_v5545.zhx" from resources.
(BrcmFirmwareRepo) BrcmPatchRAM: Decompressed firmware (29701 bytes --> 70101 bytes).
(BrcmFirmwareRepo) BrcmPatchRAM: Firmware is valid IntelHex firmware.
(BrcmPatchRAM3) BrcmPatchRAM: start
(BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
(BrcmPatchRAM3) BrcmPatchRAM: uploadFirmware could not open the device!
(BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.103 seconds.

It then succeeds after sleep/wake.

The setPowerState: which = 0x0 command seems to do the trick, as it is issued only after wake. Or does it have something to do with the power state notifications (see line 198ff)?!

 

Clover r5098 / macOS 10.15.1 / BrcmBluetoothInjector.kext+BrcmFirmwareRepo.kext+BrcmPatchRAM3.kext 2.5.0 installed to /L/E

brcmpatchram3.log

 

Exactly my problem as well, even if I try to open BT in system preferences it doesn't even open. Tested on 2 laptops and BT only works after sleep/wake (DW1560).

 

bt.png

  

(kernel) BrcmPatchRAM: Version 2.5.0 starting on OS X Darwin 19.0.
(kernel) BrcmPatchRAM: Loaded firmware "BCM20702A1_001.002.014.1443.1572_v5668.zhx" from resources.
(kernel) BrcmPatchRAM: Decompressed firmware (29651 bytes --> 70012 bytes).
(kernel) BrcmPatchRAM: Firmware is valid IntelHex firmware.
(kernel) BrcmPatchRAM: uploadFirmware could not open the device!
(kernel) BrcmPatchRAM: Processing time 0.101 seconds.
Edited by rottenpants
Link to comment
Share on other sites
xtraa
xtraa
Posted
Posted (edited)

Strange...

 

the firmware is updated, but I still have no Handoff or Instant Hotspot.

 

- my BT device is supported according to Rehabmans readme

- dropped kexts BrcmFirmwareData and BrcmPatchRAM3 in /Others

- applied Handoff-Patch in cfg plist as shown in Rehabman's readme

- USB ports are fine, like sorted and working

- cat /var/log/system.log | grep -i brcm[fp] gives no errors

But my hackintosh still says nein and nein :lol:

 

Hmm, I think I am missing something...

 

2101082585_Bildschirmfoto2019-11-06um22_04_27.png.7623bd975b7903b20178ac79a6673889.png

 

 

 

 

Edited by xtraa
Link to comment
Share on other sites
xtraa
xtraa
Posted
Posted

Thank you for the hint!

 

Unfortunately, after installing it (and also disabling the kext-patch in Clover), it still does not work. kextstat shows me that it's loaded, but it still shows it as unsupported. Maybe I need internal WiFi for it to work? Because I'm on a desktop with an ethernet connection only.

Link to comment
Share on other sites
k0nrad
k0nrad
Posted
Posted

https://support.apple.com/guide/mac-help/mchl732d3c0a/mac

 

Quote

To use Handoff, your devices must meet Continuity system requirements. They must also have Wi-Fi, Bluetooth and Handoff turned on in System Preferences (on your Mac) and in Settings (on your iOS and iPadOS devices). You must be signed in with the same Apple ID on all your devices.

 

  • Like 1
  • Thanks 1
Link to comment
Share on other sites
Hologos
Hologos
Posted
Posted (edited)
On 10/12/2019 at 12:09 AM, Mieze said:

Here is version 2.3.0d3 in which I optimized a few details and fixed some possible weaknesses of earlier versions. It's working 100% stable on my test machines and I consider it to be ready for productive use.

 

Have fun!

 

Mieze :cat:

 

BrcmPatchRAM3-V2.3.0d3.zip

 

Hi @Mieze, I just found out that v2.5 breaks the "Call from iPhone" feature. Can you confirm that? Last working version for me is the v2.3.0d3. I'm using DW1560.

Edited by Hologos
Link to comment
Share on other sites
Mieze
Mieze
Posted
Posted
On 11/8/2019 at 11:01 AM, Hologos said:

just found out that v2.5 breaks the "Call from iPhone" feature. Can you confirm that? Last working version for me is the v2.3.0d3. I'm using DW1560.

As version 2.5.0 includes updated firmware files for all supported devices, it might be a firmware related problem. Can anybody confirm this issue with version 2.5 using a DW1560?

 

Mieze

Link to comment
Share on other sites
xXiGeniusXx
xXiGeniusXx
Posted
Posted

As of version 2.5 I'm still getting random disconnection and a reboot (kernel panic I guess) some time after the disconnection!

Tried installing in the S/L/E and my hack froze when I tried connecting to my bluetooth speaker! Removed the S/L/E and reverted back to boot loader solution and now my hack won't even recognize my bluetooth dongle and bluetooth preferences pane is gone from Settings!

 

This is very frustrating can someone come up with a working patch here?

I also don't know how to get a log from the console for this! any pointers appreciated.

Thank you.

Link to comment
Share on other sites
xXiGeniusXx
xXiGeniusXx
Posted
Posted (edited)

Here's my chip's firmware hex extracted from the latest available driver according to instructions on Github page, it's listed as a "[0a5c:21ec] Inateck Bluetooth (20702A1)" but it's actually a Orico BTA 408 .

I was hoping someone could build custom kext for me, I tried but instructions seemed too complicated!

 

Thanks! 

BCM20702A1_001.002.014.1315.1419.hex

Edited by xXiGeniusXx
Link to comment
Share on other sites
headkaze
headkaze
Posted
  • Author
Posted
4 hours ago, xXiGeniusXx said:

Here's my chip's firmware hex extracted from the latest available driver according to instructions on Github page, it's listed as a "[0a5c:21ec] Inateck Bluetooth (20702A1)" but it's actually a Orico BTA 408 .

I was hoping someone could build custom kext for me, I tried but instructions seemed too complicated!

 

Thanks! 

BCM20702A1_001.002.014.1315.1419.hex

The name is not so important (it's just the same rebranded hardware) it's the VID:PID that counts. Your hardware is already supported and BrcmPatchRAM3 has a newer version of the firmware you link to above anyway.

Link to comment
Share on other sites
Michelinu
Michelinu
Posted
Posted (edited)

Hi, I'm currently running macOS Catalina 10.15.1. I'm using an Asus ROG Strix Z390-I with DW1820A (model 0VW3T3).

Wi-Fi was working OOB, BT didn't.

 

By installing BrcmFirmwareData+BrcmBluetoothInjector+BrcmPatchRAM3 kexts, now BT works but only for Continuity/Handoff. Other BT devices are detected but it doesn't connect.

1238994802_Schermata2019-11-11alle19_01_01.png.f05ec5ee91eb910ff128eaf059cc2779.png

1539222359_Schermata2019-11-11alle19_08_14.thumb.png.7341910536eae31b3eb2172d11face38.png

 

 

This I what happens during boot.

1160651279_Schermata2019-11-11alle19_42_09.png.eff07778dd03fd7cb8a454f37fe0b315.png

 

 


I also noticed that if I boot Windows and then I reboot in macOS, firmware is upgraded to 5799 and BT works.

 

Can you help me?
Thank you :)

Edited by Michelinu
Link to comment
Share on other sites
k0nrad
k0nrad
Posted
Posted
On 11/4/2019 at 10:29 AM, k0nrad said:

The [413c:8143] Dell DW1550 (4352/20702 combo) card does not seem to support the handshake mechanism – to answer the question in line 67. :-) 


(BrcmPatchRAM3) BrcmPatchRAM: init
(BrcmPatchRAM3) BrcmPatchRAM: probe
(BrcmPatchRAM3) BrcmPatchRAM: Version 2.5.0 starting on OS X Darwin 19.0.
(BrcmPatchRAM3) BrcmPatchRAM: Device doesn't support handshake.

Also the firmware upload fails in the first place. 


(BrcmFirmwareRepo) BrcmPatchRAM: Firmware store start
(BrcmFirmwareRepo) BrcmPatchRAM: getFirmware
(BrcmFirmwareRepo) BrcmPatchRAM: loadFirmware
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource: 00000000
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource Callback: dc008006.
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource: 00000000
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource Callback: dc008006.
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource: 00000000
(BrcmFirmwareRepo) BrcmPatchRAM: OSKextRequestResource Callback: 29701 bytes of data.
(BrcmFirmwareRepo) BrcmPatchRAM: Loaded firmware "BCM20702A1_001.002.014.1443.1449_v5545.zhx" from resources.
(BrcmFirmwareRepo) BrcmPatchRAM: Decompressed firmware (29701 bytes --> 70101 bytes).
(BrcmFirmwareRepo) BrcmPatchRAM: Firmware is valid IntelHex firmware.
(BrcmPatchRAM3) BrcmPatchRAM: start
(BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
(BrcmPatchRAM3) BrcmPatchRAM: uploadFirmware could not open the device!
(BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.103 seconds.

It then succeeds after sleep/wake. 


(BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x0
(BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
(BrcmPatchRAM3) BrcmPatchRAM: stop
(BrcmPatchRAM3) BrcmPatchRAM: free
(BrcmPatchRAM3) BrcmPatchRAM: init
(BrcmPatchRAM3) BrcmPatchRAM: probe
(BrcmPatchRAM3) BrcmPatchRAM: Version 2.5.0 starting on OS X Darwin 19.0.
(BrcmPatchRAM3) BrcmPatchRAM: Device doesn't support handshake.
(BrcmFirmwareRepo) BrcmPatchRAM: getFirmware
(BrcmFirmwareRepo) BrcmPatchRAM: Retrieved cached firmware for "BCM20702A1_001.002.014.1443.1449_v5545".
(BrcmPatchRAM3) BrcmPatchRAM: start
(BrcmPatchRAM3) BrcmPatchRAM: setPowerState: which = 0x1
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: USB [B8EE65335CE4 v274] "BCM20702A0" by "Broadcom Corp"
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: Available composite configurations: 1.
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: Set device configuration to configuration index 0 successfully.
(BrcmPatchRAM3) BrcmPatchRAM: USBDeviceShim::findFirstInterface
(BrcmPatchRAM3) BrcmPatchRAM: getValidatedInterface returns <private>
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: Interface 0 (class ff, subclass 01, protocol 01) located.
(BrcmPatchRAM3) BrcmPatchRAM: set configuration and interface opened
(BrcmPatchRAM3) BrcmPatchRAM: findPipe: direction = 1, type = 3
(BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3
(BrcmPatchRAM3) BrcmPatchRAM: found matching endpoint
(BrcmPatchRAM3) BrcmPatchRAM: findPipe: direction = 0, type = 2
(BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 3
(BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 1, epType = 2
(BrcmPatchRAM3) BrcmPatchRAM: endpoint found: epDirection = 0, epType = 2
(BrcmPatchRAM3) BrcmPatchRAM: found matching endpoint
(BrcmPatchRAM3) BrcmPatchRAM: got pipes
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: State "Unknown" --> "Initialize".
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: READ VERBOSE CONFIG complete (status: 0x00, length: 10 bytes).
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: Firmware version: v4096.
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: State "Initialize" --> "Firmware version".
(BrcmFirmwareRepo) BrcmPatchRAM: getFirmware
(BrcmFirmwareRepo) BrcmPatchRAM: Retrieved cached firmware for "BCM20702A1_001.002.014.1443.1449_v5545".
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: DOWNLOAD MINIDRIVER complete (status: 0x00, length: 4 bytes).
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: State "Firmware version" --> "Mini-driver complete".
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: END OF RECORD complete (status: 0x00, length: 4 bytes).
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: State "Instruction write" --> "Firmware written".
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: RESET complete (status: 0x00, length: 4 bytes).
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: State "Firmware written" --> "Reset complete".
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: Device reset.
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: Device status 0x00000003.
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: State "Reset complete" --> "Update complete".
(BrcmPatchRAM3) BrcmPatchRAM: [413c:8143]: Firmware upgrade completed successfully.
(BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.623 seconds.

The setPowerState: which = 0x0 command seems to do the trick, as it is issued only after wake. Or does it have something to do with the power state notifications (see line 198ff)?!

 

Clover r5098 / macOS 10.15.1 / BrcmBluetoothInjector.kext+BrcmFirmwareRepo.kext+BrcmPatchRAM3.kext 2.5.0 installed to /L/E

brcmpatchram3.log

 

Fixed my problem by using the "old" RehabMan method to create a custom SSDT for USBInjectAll.kext instead of the USBPorts.kext created by Hackintool. As a benefit several other problems and lags also disappeared. Nice! :-)

  • Like 1
  • Thanks 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...