Jump to content

Broadcom Bluetooth 20702A

Xeon3D

By Xeon3D,
in OSx86 10.11 (El Capitan)

 Share
123 posts in this topic

Recommended Posts

s0niqu3
s0niqu3
Posted
Posted

Are you using this one as well?

			<dict>
				<key>Comment</key>
				<string>Handoff Fix</string>
				<key>Find</key>
				<data>
				SIX/dEdIiwc=
				</data>
				<key>Name</key>
				<string>IOBluetoothFamily</string>
				<key>Replace</key>
				<data>
				Qb4PAAAA60Q=
				</data>
			</dict>

 

Hi again, and yes, I'm using that patch too. That patch seems to enable everything (see my screenshots above, everything shows as supported in System Information) but the services just don't actually work, whereas they did both work on Yosemite with the old patch.

Link to comment
Share on other sites
mnfesq
mnfesq
Posted
Posted

I spoke too soon about my issues being resolved.  The first few reboots were great and the firmware was uploading and BT worked great.  Now, not so.  I'm back to the old firmware (4096) and BT is not connecting to my devices.  I still have continuity and handoff though.  For that, I had to exit iCloud on my phone and laptop, sign in again and, on my laptop, reboot.  Then, handoff/continuity worked for me in El Cap.

Link to comment
Share on other sites
s0niqu3
s0niqu3
Posted
Posted

I spoke too soon about my issues being resolved.  The first few reboots were great and the firmware was uploading and BT worked great.  Now, not so.  I'm back to the old firmware (4096) and BT is not connecting to my devices.  I still have continuity and handoff though.  For that, I had to exit iCloud on my phone and laptop, sign in again and, on my laptop, reboot.  Then, handoff/continuity worked for me in El Cap.

Thanks for the reply, man I feel dumb now for not trying this before... yes, signing out of iCloud on my desktop/hack and rebooting did the trick.

 

post-1089949-0-29160700-1442187905_thumb.png

 

EDIT: spoke too soon; Handoff is working again, but instant-hotspot fails every try, even after a couple reboots.

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

Note that 10.11 version of BrcmPatchRAM is available (BrcmPatchRAM2.kext): https://github.com/RehabMan/OS-X-BrcmPatchRAM

 

Install BrcmPatchRAM2.kext only on 10.11+.

Install BrcmPatchRAM.kext only on 10.10-.

Remove BrcmBluetoothInjector.kext if you're using either BrcmPatchRAM.kext or BrcmPatchRAM2.kext.

  • Like 2
Link to comment
Share on other sites
Andrw0380
Andrw0380
Posted
Posted

Thanks Rehabman your newest BrcmPatchRam2 is working awesome! The amber light on the Envy j-070 is now white without having to boot into Windows which is allowing bluetooth connections now. The one bug I noticed is some resuming from sleeps, cause the bluetooth to stop working and the amber light is orange. I do have my kexts in Clover/kexts/Other per the Envy thread still, but don't have any other kexts problems so just wanted to let you know.

  • Like 1
Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

Thanks Rehabman your newest BrcmPatchRam2 is working awesome! The amber light on the Envy j-070 is now white without having to boot into Windows which is allowing bluetooth connections now. The one bug I noticed is some resuming from sleeps, cause the bluetooth to stop working and the amber light is orange. I do have my kexts in Clover/kexts/Other per the Envy thread still, but don't have any other kexts problems so just wanted to let you know.

All kexts should be installed to /S/L/E.

Link to comment
Share on other sites
mnfesq
mnfesq
Posted
Posted

Thanks Rehabman your newest BrcmPatchRam2 is working awesome! The amber light on the Envy j-070 is now white without having to boot into Windows which is allowing bluetooth connections now. The one bug I noticed is some resuming from sleeps, cause the bluetooth to stop working and the amber light is orange. I do have my kexts in Clover/kexts/Other per the Envy thread still, but don't have any other kexts problems so just wanted to let you know.

 

That happens to me on rare occasion since using the BrcmPatchRam2.kext.  I have mine in L/E.  It has less permissions problems there than in Clover/Kexts/10.11.  But it certainly is a real pleasure to see that white LED light and to be able to connect to BT devices again.

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

That happens to me on rare occasion since using the BrcmPatchRam2.kext.  I have mine in L/E.  It has less permissions problems there than in Clover/Kexts/10.11.  But it certainly is a real pleasure to see that white LED light and to be able to connect to BT devices again.

Try to record the logs (preferably debug logs) when it happens. Take note of the local time of the occurrence so the corresponding BrcmPatchRAM2 logs in system.log (if they exist) can be recognized. And ioreg (IORegistryExplorer v2.1).

Link to comment
Share on other sites
abdouoi
abdouoi
Posted
Posted

I've already tried that version but it doesn't work for me. Bluetooth is not available at all

No need to upload builds, which will just be obsolete as fixes are made).

 

It is available from bitbucket, linked from the README.

 

Always read the README.

 

Here is a link: https://github.com/RehabMan/OS-X-BrcmPatchRAM

Are the build on Bitbucket the latest one ?

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

I've already tried that version but it doesn't work for me. Bluetooth is not available at all

You probably installed it incorrectly or have other BT kexts installed which conflict.

 

Or you have a device which is not yet in the kext.

 

Also, many problems with BT are actually USB problems. If you don't have USB working correctly, BrcmPatchRAM will not help you.

 

Post ioreg (IORegistryExplorer v2.1).

 

Are the build on Bitbucket the latest one ?

They are close. Post ioreg for troubleshooting.

 

The latest version is currently on my own laptop, not yet pushed to github :-)

 

Note: To build this project, you need Xcode 7 with both 10.11 SDK and 10.6 SDK (from older versions of Xcode).

Link to comment
Share on other sites
abdouoi
abdouoi
Posted
Posted

You probably installed it incorrectly or have other BT kexts installed which conflict.

 

Or you have a device which is not yet in the kext.

 

Also, many problems with BT are actually USB problems. If you don't have USB working correctly, BrcmPatchRAM will not help you.

 

Post ioreg (IORegistryExplorer v2.1).

 

 

They are close. Post ioreg for troubleshooting.

 

The latest version is currently on my own laptop, not yet pushed to github :-)

 

Note: To build this project, you need Xcode 7 with both 10.11 SDK and 10.6 SDK (from older versions of Xcode).

I'm pretty sure it's the only BT kext. Here is my ioreg

ioreg.zip

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

I'm pretty sure it's the only BT kext. Here is my ioreg

Post output of:

grep -y brcmpatch /var/log/system.log
And:

sudo touch /System/Library/Extensions && sudo kextcache -u /
I don't think it is related, but you have a heck of a mess with your SSDTs loading from ACPI/patched...

 

From your bootlog:

9:918  0:000  Inserting SSDT-2-previous.aml from EFI\CLOVER\ACPI\patched ... Success
9:918  0:000  Inserting SSDT-previous.aml from EFI\CLOVER\ACPI\patched ... Success
9:918  0:000  Inserting SSDT-1-previous.aml from EFI\CLOVER\ACPI\patched ... Success
9:918  0:000  Inserting SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success
9:918  0:000  Inserting SSDT.aml from EFI\CLOVER\ACPI\patched ... Success
9:918  0:000  Inserting SSDT-2.aml from EFI\CLOVER\ACPI\patched ... Success
9:918  0:000  Inserting SSDT-3.aml from EFI\CLOVER\ACPI\patched ... Success
9:919  0:000  Inserting SSDT-4.aml from EFI\CLOVER\ACPI\patched ... Success
(bad order, probable duplicates, probably not the ones you expect to be used {first loaded wins}]
Link to comment
Share on other sites
abdouoi
abdouoi
Posted
Posted

Post output of:

grep -y brcmpatch /var/log/system.log
And:

sudo touch /System/Library/Extensions && sudo kextcache -u /
I don't think it is related, but you have a heck of a mess with your SSDTs loading from ACPI/patched...

 

From your bootlog:

9:918  0:000  Inserting SSDT-2-previous.aml from EFI\CLOVER\ACPI\patched ... Success
9:918  0:000  Inserting SSDT-previous.aml from EFI\CLOVER\ACPI\patched ... Success
9:918  0:000  Inserting SSDT-1-previous.aml from EFI\CLOVER\ACPI\patched ... Success
9:918  0:000  Inserting SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success
9:918  0:000  Inserting SSDT.aml from EFI\CLOVER\ACPI\patched ... Success
9:918  0:000  Inserting SSDT-2.aml from EFI\CLOVER\ACPI\patched ... Success
9:918  0:000  Inserting SSDT-3.aml from EFI\CLOVER\ACPI\patched ... Success
9:919  0:000  Inserting SSDT-4.aml from EFI\CLOVER\ACPI\patched ... Success
(bad order, probable duplicates, probably not the ones you expect to be used {first loaded wins}]

thanks for notifying me about the SSDT. here is the output 

Last login: Sat Sep 19 23:28:48 on console

MBPdeg33k1ns1d3:~ g33k1ns1d3$ grep -y brcmpatch /var/log/system.log

MBPdeg33k1ns1d3:~ g33k1ns1d3$ sudo touch /System/Library/Extensions && sudo kextcache -u /

Password:

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Trackpad.kext

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Mouse.kext

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Keyboard.kext

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Controller.kext

kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext VoodooHDA.kext

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RealtekRTL8111.kext

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext LPCSensors.kext

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext GPUSensors.kext

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext CPUSensors.kext

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPISensors.kext

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmPatchRAM2.kext

kext file:///System/Library/Extensions/AppleHDADisabler.kext/ is in hash exception list, allowing to load

kext file:///System/Library/Extensions/AHCIPortInjector.kext/ is in hash exception list, allowing to load

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext

Invalid signature -67030 for kext <OSKext 0x7fc7ce8b18e0 [0x7fff7a2aa890]> { URL = "VoodooHDA.kext/ -- file:///System/Library/Extensions/", ID = "org.voodoo.driver.VoodooHDA" }

 

MBPdeg33k1ns1d3:~ g33k1ns1d3$ 

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

...

MBPdeg33k1ns1d3:~ g33k1ns1d3$ grep -y brcmpatch /var/log/system.log

I don't get it. The ioreg shows BrcmFirmwareStore resident, but no output in system.log from BrcmPatchRAM?

 

Doesn't make any sense.

Link to comment
Share on other sites
abdouoi
abdouoi
Posted
Posted

I don't get it. The ioreg shows BrcmFirmwareStore resident, but no output in system.log from BrcmPatchRAM?

 

Doesn't make any sense.

I've cleaned up my SSDTs and rebooted. Here is the output 

Last login: Sun Sep 20 00:36:10 on ttys000

MBPdeg33k1ns1d3:~ g33k1ns1d3$ grep -y brcmpatch /var/log/system.log

Sep 20 00:15:53 localhost kernel[0]: BrcmPatchRAM2: Version 2.0.1 starting on OS X Darwin 15.0.

Sep 20 00:15:53 localhost kernel[0]: BrcmPatchRAM2: Published new IOKit personality for BrcmFirmwareStore.

Sep 20 00:15:53 localhost kernel[0]: BrcmPatchRAM2: Retrieved firmware for firmware key "BCM20702A1_001.002.014.1443.1479_v5575".

Sep 20 00:15:53 localhost kernel[0]: BrcmPatchRAM2: Decompressed firmware (29776 bytes --> 70105 bytes).

Sep 20 00:15:53 localhost kernel[0]: BrcmPatchRAM2: Firmware is valid IntelHex firmware.

Sep 20 00:15:53 localhost kernel[0]: BrcmPatchRAM2: [13d3:3404]: USB [240A64B58EC5 v274] "BCM20702A0" by "Broadcom Corp"

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: [13d3:3404]: Firmware upgrade completed successfully.

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: [13d3:3404]: Found existing IOKit personality "com.apple.driver.AppleUSBMergeNub".

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: Processing time 0.651 seconds.

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: Version 2.0.1 starting on OS X Darwin 15.0.

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: [13d3:3404]: USB [240A64B58EC5 v274] "BCM20702A0" by "Broadcom Corp"

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: [13d3:3404]: Firmware upgrade not needed.

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: [13d3:3404]: Found existing IOKit personality "com.apple.driver.AppleUSBMergeNub".

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: Processing time 0.16 seconds.

MBPdeg33k1ns1d3:~ g33k1ns1d3$ 

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

I've cleaned up my SSDTs and rebooted. Here is the output 

Last login: Sun Sep 20 00:36:10 on ttys000[/size]

MBPdeg33k1ns1d3:~ g33k1ns1d3$ grep -y brcmpatch /var/log/system.log

Sep 20 00:15:53 localhost kernel[0]: BrcmPatchRAM2: Version 2.0.1 starting on OS X Darwin 15.0.

Sep 20 00:15:53 localhost kernel[0]: BrcmPatchRAM2: Published new IOKit personality for BrcmFirmwareStore.

Sep 20 00:15:53 localhost kernel[0]: BrcmPatchRAM2: Retrieved firmware for firmware key "BCM20702A1_001.002.014.1443.1479_v5575".

Sep 20 00:15:53 localhost kernel[0]: BrcmPatchRAM2: Decompressed firmware (29776 bytes --> 70105 bytes).

Sep 20 00:15:53 localhost kernel[0]: BrcmPatchRAM2: Firmware is valid IntelHex firmware.

Sep 20 00:15:53 localhost kernel[0]: BrcmPatchRAM2: [13d3:3404]: USB [240A64B58EC5 v274] "BCM20702A0" by "Broadcom Corp"

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: [13d3:3404]: Firmware upgrade completed successfully.

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: [13d3:3404]: Found existing IOKit personality "com.apple.driver.AppleUSBMergeNub".

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: Processing time 0.651 seconds.

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: Version 2.0.1 starting on OS X Darwin 15.0.

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: [13d3:3404]: USB [240A64B58EC5 v274] "BCM20702A0" by "Broadcom Corp"

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: [13d3:3404]: Firmware upgrade not needed.

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: [13d3:3404]: Found existing IOKit personality "com.apple.driver.AppleUSBMergeNub".

Sep 20 00:15:54 localhost kernel[0]: BrcmPatchRAM2: Processing time 0.16 seconds.

MBPdeg33k1ns1d3:~ g33k1ns1d3$

Where is the com.apple.driver.AppleUSBMergeNub personality for 13d3:3404 coming from?

 

Seems likely something you added... and it is interfering with correct operation of BrcmPatchRAM2.kext.

 

Make sure no other BT solutions are installed, no other personalities registered for this 13d3:3404 device.

I've seen people stuffing weird things into their FakeSMC, for example.

Link to comment
Share on other sites
abdouoi
abdouoi
Posted
Posted

Where is the com.apple.driver.AppleUSBMergeNub personality for 13d3:3404 coming from?

 

Seems likely something you added... and it is interfering with correct operation of BrcmPatchRAM2.kext.

 

Make sure no other BT solutions are installed, no other personalities registered for this 13d3:3404 device.

I've seen people stuffing weird things into their FakeSMC, for example.

I know I have it in my wifi injector kext

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

I know I have it in my wifi injector kext

It needs to be removed for BrcmPatchRAM to work.

 

Strange that no WiFi injector shows in the kextcache output, nor Clover bootlog.

 

Note that this "WiFi injector" kext is probably not needed. You should probably be using FakePCIID.kext+FakePCIID_BCM94352Z_as_BCM94360CS2.kext instead.

 

It takes care of the WiFi device personality (for all known compatible BCM WiFi) and Airport branding.

Link to comment
Share on other sites
abdouoi
abdouoi
Posted
Posted

It needs to be removed for BrcmPatchRAM to work.

 

Strange that no WiFi injector shows in the kextcache output, nor Clover bootlog.

 

Note that this "WiFi injector" kext is probably not needed. You should probably be using FakePCIID.kext+FakePCIID_BCM94352Z_as_BCM94360CS2.kext instead.

 

It takes care of the WiFi device personality (for all known compatible BCM WiFi) and Airport branding.

 

Followed your instructions and now everything is working, wifi + bluetooth! Thanks!  :thumbsup_anim:

It needs to be removed for BrcmPatchRAM to work.

 

Strange that no WiFi injector shows in the kextcache output, nor Clover bootlog.

 

Note that this "WiFi injector" kext is probably not needed. You should probably be using FakePCIID.kext+FakePCIID_BCM94352Z_as_BCM94360CS2.kext instead.

 

It takes care of the WiFi device personality (for all known compatible BCM WiFi) and Airport branding.

 

Do you know how to make handoff and instant hotspot work ?

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