CAT2.0 unsuccessful on MacBookPro5,2 (Early 2009) w/ USB dongle

[sejmann]

Hey -- thanks for building this tool!

Dongle is an ORICO BTA-402. on OSX 10.10.1. The Early 2009 MBP 17 had separate airport and bluetooth modules, the airport card seemingly non-pci/non-upgradable. Initial CAT install appeared successful, but after reboot, no dice. Attempted reinstall, reboot, still no dice. Only anomaly in diagnostics is "unknown bluetooth features" detected, code 5, which sounded benign. Any ideas? Much appreciated. (Edit: Also logged out of iCloud, rebooted, logged in again, rebooted, to no avail. I'm skeptical my Airport card can support Handoff -- I've never seen airdrop work, even mac to mac, even though it claims to support it. It definitely doesn't work mac<->iOS.)

Attached images of CAT Diagnostics, WIFI/Bluetooth/System Info.

CAT Diag:

CAT Re-Install:

Bluetooth:

Wifi:

System:

[dokterdok]

Hi @sejmann, The output indicates two things:

• legacy Wi-Fi drivers are in use which should not be the case, as they prevent some Continuity features from working.
• a compatibility issue with your dongle which is from the CSR brand. CSR-based dongles currently aren't well supported by CAT. During the beta phase, roughly 50% of them worked, others didn't.

Could you please confirm if your system diagnostic output was made after the reboot? If not - could you please re-take a screenshot or do a copy/paste? Thanks

[wjteale]

I have Macbook Pro 17" 2009. Using a belkin USB Dongle. Product ID: 0x065a Vendor ID: 0x050d (Belkin Corporation) Version: 1.12 Serial Number: 5CF3706136A9 Speed: Up to 12 Mb/sec Manufacturer: Broadcom Corp Location ID: 0x04100000 / 2 Current Available (mA): 500 Current Required (mA): 100

Tried to activate a few times. Nothing happens. Doesn't seem to read or recognize the Dongle. Help

[dokterdok]

@wjteale please copy/paste the CAT system diagnostic output or take a screenshot

[wjteale]

Here you go ....

Last login: Wed Dec 17 21:04:57 on ttys000 Williams-MacBook-Pro-3:~ root# /Users/William/Downloads/Continuity-Activation-Tool-master/Continuity\ Activation\ Tool.app/Contents/Resources/contitool.sh ; exit;

You must run this script with admin privileges, please enter your password.

--- OS X Continuity Activation Tool 2.0.0 --- by dokterdok

Select an option:

1) Activate Continuity 3) Uninstall 2) System Diagnostic 4) Quit

? 2

--- OS X Continuity Activation Tool 2.0.0 --- by dokterdok

--- Initiating system compatiblity check ---

--- Hardware/OS checks --- Verifying Continuity status... OK. OS X reports Continuity as inactive Verifying Mac model reference... OK. Known compatible Mac Model detected: MacBookPro5,2 Verifying Mac board-id... OK. Short board id detected: Mac-F2268EC8 Verifying OS X version... OK. Mac OS X 10.10.1 (14B25) detected Verifying Wi-Fi hardware... OK. A Broadcom AirPort card is active, and uses the legacy Brcm4331 kext. This tool can fix this. Verifying AWDL status... OK. No AWDL is active, but the hardware seems to be able to support it. This tool can try to fix this. Verifying Bluetooth hardware... OK. The internal Bluetooth card is active Verifying Bluetooth version... NOT OK. Your hardware doesn't support Bluetooth 4.0, necessary for Continuity. Current LMP Version=4, expected 6. Verifying Bluetooth features... OK. Bluetooth features are currently not compatible with Continuity. This tool can try to fix this. Verifying Bluetooth firmware... OK. Bluetooth firmware version: v208 c523

--- Modifications check --- Verifying OS kext protection... OK. Kext developer mode is not active. This tool can fix this. Verifying kexts readability... OK. Wi-Fi and Bluetooth kexts were found and could be read Verifying Bluetooth blacklist status... OK. Your Mac model is not blacklisted Verifying Wi-Fi whitelist status... OK. Your board-id is not yet whitelisted. This tool can fix this. Verifying old Wi-Fi kext presence... OK. Legacy Brcm4331 Wi-Fi driver is present. This tool can fix this. Verifying legacy Wi-Fi card patch... OK. The legacy Wi-Fi patch is not present. This tool can fix this. Verifying BT4 dongles compatibility... OK. Compatibility with BT4 USB dongles is not enabled, this tool can fix this if a dongle is plugged in

Press any key to go back to the main menu...

The USB Belkin is 4.0

[NeoTeo]

I get the same as wjteale

[dokterdok]

@wjteale your system has the internal bluetooth set as active. Unplug the dongle, replug it, and retry the activation directly after. You should normally not see a "plugin your dongle now" prompt at the beginning of the activation, as it autodetects your dongle. At the end of the activation, before you reboot, copy/paste the activation output in a txt file.
If you continue to have issues please post the copy/activation output + a description.

[wjteale]

Ok. Thank you. Deactivated bluetooth on Mac. Unplugged Dongle. Plugged it in and retried activation. No go. Tried again and almost did both simultaneously. Worked. I see the dongle is now working. I signed out and back in to my icloud account. But in System/preferences I don't have option to turn on Handoff.

Last login: Wed Dec 17 22:42:19 on ttys000 Williams-MBP-3:~ root# /Users/William/Downloads/Continuity-Activation-Tool-master/Continuity\ Activation\ Tool.app/Contents/Resources/contitool.sh ; exit; You must run this script with admin privileges, please enter your password.

--- OS X Continuity Activation Tool 2.0.0 --- by dokterdok

Select an option:

1) Activate Continuity 3) Uninstall 2) System Diagnostic 4) Quit

? 1

--- OS X Continuity Activation Tool 2.0.0 --- by dokterdok

If you want to activate Continuity using a USB Bluetooth 4.0 dongle, then plug-it in now. The script will continue once it's detected.

--- OS X Continuity Activation Tool 2.0.0 --- by dokterdok

--- Initiating system compatibility check ---

Verifying Mac model reference... OK Verifying Mac board-id... OK Verifying OS X version... OK Verifying Wi-Fi hardware... OK Verifying Bluetooth version... OK Verifying Bluetooth features... OK Verifying kexts readability... OK Verifying Bluetooth blacklist status... OK Verifying Wi-Fi whitelist status... OK Verifying legacy Wi-Fi card patch... OK Verifying old Wi-Fi kext presence... OK

--- Initiating Continuity mod ---

Disabling OS kext protection... OK Fixing disk permissions... OK Backing up original drivers... OK. Wi-Fi and Bluetooth kexts were backed up in '/Users/William/KextsBackupBeforePatch' Skipping blacklist patch... OK Patching whitelist................ OK Cleaning up old Wi-Fi kext... OK Applying legacy Wi-Fi card patch... OK Verifying BT4 dongle patch status... OK Setting HCI switch behavior... OK Patching Bluetooth feature flags... OK Skipping legacy Wi-Fi cards patch... OK Applying correct permissions... OK Updating kext caches... OK Updating system caches... OK Backing up patched drivers... OK. Wi-Fi and Bluetooth kexts were backed up in '/Users/William/KextsBackupAfterPatch'

ALMOST DONE! After rebooting: 1) Make sure that both your Mac and iOS device have Bluetooth turned on, and are on the same Wi-Fi network. 2) On OS X go to SYSTEM PREFERENCES> GENERAL> and ENABLE HANDOFF. 3) On iOS go to SETTINGS> GENERAL> HANDOFF & SUGGESTED APPS> and ENABLE HANDOFF. 4) On OS X, sign out and then sign in again to your iCloud account. Troubleshooting: support.apple.com/kb/TS5458

Thanks to Lem3ssie, UncleSchnitty, Skvo, toleda, TealShark, Manic Harmonic, rob3r7o and the many beta testers for their support.

Press any key to reboot or CTRL-C to cancel...

I will now reboot system and see. Hopes this also helped NeoTeo. Thank you ... Will get back to you after reboot

[NeoTeo]

Although I have a Mac Pro I get a similar issue. It's as though it only looks at the built in BT.

[wjteale]

NeoTeo follow instructions David gave me.

[NeoTeo]

I did, several times, with no luck.

[sejmann]

@dokterdok Yes, I can confirm the screenshots were post install/reboot. I also just uninstalled CAT, rebooted, reinstalled, rebooted. I took additional screen shots of each step, however they remain identical. Diagnostic still show legacy Broadcom kext in use. I'm happy to buy/try another BT dongle, but I have no idea what's up with my broadcom kext. I'm not sure what I'm looking for, but I see both AppleAirPortBrcm43224.kext and AirPortBrcm4360.kext inside /S/L/E/IO80211Family, both with with recent modification dates.

Update 1: I've ordered a BCM20702 dongle, which I'll try in a few days. Still struggling to understand the contradictory state of my airport drivers -- updated, but still somehow legacy.

Update 2: Not sure how this is possible. sudo find /System -name '4331' returns nothing sudo find / -name "Brcm4331" only finds the copy your script put in KextsBackupBeforePatch kextstat|egrep -i Airport , however, still returns: 51 0 0xffffff7f81d52000 0x1f3000 0x1f3000 com.apple.driver.AirPort.Brcm4331 (800.20.24) <50 43 12 7 5 4 3 1> Does that mean my kext cache wasn't rebuilt?

Update 3: It seems so. /System/Library/Caches/com.apple.kext.caches/Startup/loadedkextmt.plist still contains: and kernelcache hasn't been updated since Dec 2.

And sudo kextcache -system-prelinked-kernel returns:

So, it seems, among other issues, my IOBluetoothFamily.kext is corrupt, perhaps from my prior attempts to get Continuity working? About to try "contitool --uninstallWithRecovery" to see if I can start from a clean slate.

Update 4: Yep, that was it. Okay, kernel cache is now updating properly, and Handoff is reported as supported. However my BT dongle now no longer works at all. Hmm.

[dokterdok]

@sejmann , nice detailed report. Indeed CAT requires fresh, unmodified drivers to work correctly. You can get a clean slate easily by renaming the KextsBackupBeforePatch folder, and run the uninstaller. OS X recovery disk drivers will then be reinstalled.

However : the BTLE functionality you lost after patching is because CAT isn't compatible with your dongle apparently. I've had mixed reports when using CSR dongles with CAT, try using a Broadcom-based BT4.0 dongle if you can for now.

[wjteale]

After many attempts it seems now that I should have handoff. My preference panel now shows the option. I have clicked handoff on all my devices. I also clicked on OS X system/General/Handoff - enabled. Airdrop seems to be working now. But handoff does not work. This is the diagnostics report I receive now. If there is anything I have missed could you let me know. Again ... Many Thanks

--- OS X Continuity Activation Tool 2.0.0 --- by dokterdok

--- Initiating system compatiblity check ---

--- Hardware/OS checks --- Verifying Continuity status... OK. OS X reports Continuity as active Verifying Mac model reference... OK. Known compatible Mac Model detected: MacBookPro5,2 Verifying Mac board-id... OK. Short board id detected: Mac-F2268EC8 Verifying OS X version... OK. Mac OS X 10.10.1 (14B25) detected Verifying Wi-Fi hardware... OK. A Broadcom AirPort card is active, and is using the Continuity compatible Brcm4360 kext Verifying AWDL status... OK. An AWDL interface is up, Wi-Fi is ready for Continuity Verifying Bluetooth hardware... OK. 3rd party Bluetooth hardware detected Verifying Bluetooth version... OK. Bluetooth 4.0 detected Verifying Bluetooth features... OK. Bluetooth features are Continuity compliant Verifying Bluetooth firmware... OK. Bluetooth firmware version: v14 c4096

--- Modifications check --- Verifying OS kext protection... OK. Kext developer mode is already active Verifying kexts readability... OK. Wi-Fi and Bluetooth kexts were found and could be read Verifying Bluetooth blacklist status... OK. Your Mac model is not blacklisted Verifying Wi-Fi whitelist status... OK. The whitelist is correctly patched with your board-id Verifying old Wi-Fi kext presence... OK. Legacy Wi-Fi driver Brcm4331 was already removed Verifying legacy Wi-Fi card patch... OK. The patch is already done. Old Broadcom Wi-Fi cards may work. Verifying BT4 dongles compatibility... OK. The patch that enables BT4 USB dongles compatibility has already been applied

Press any key to go back to the main menu...

[wjteale]

This is my macbook pro ( Bluetooth ) system report now. I am not sure if Dongle is overriding internal bluetooth or not.

Apple Bluetooth Software Version: 4.3.1f2 15015 Hardware, Features, and Settings: Name: William’s MacBook Pro (3) Address:
Bluetooth Low Energy Supported: Yes Handoff Supported: Yes Instant Hotspot Supported: Yes Manufacturer: Broadcom Transport: USB Chipset: 20702A3 Firmware Version: v14 c4096 Bluetooth Power: On Discoverable: On Connectable: Yes Auto Seek Pointing: On Remote wake: On Vendor ID: 0x050D Product ID: 0x065A HCI Version: 0x6 HCI Revision: 0x1000 LMP Version: 0x6 LMP Subversion: 0x220E Device Type (Major): Computer Device Type (Complete): Mac Portable Composite Class Of Device: 0x38010C Device Class (Major): 0x01 Device Class (Minor): 0x03 Service Class: 0x1C0 Auto Seek Keyboard: On Devices (Paired, Configured, etc.): William’s keyboard: Address: E8-06-88-4B-65-B8 Major Type: Peripheral Minor Type: Keyboard Services: Apple Wireless Keyboard Paired: Yes Configured: Yes Connected: Yes Manufacturer: Apple (0x3, 0x31C) Battery Level: 100% Firmware Version: 0x0050 Vendor ID: 0x05AC Product ID: 0x0239 Class of Device: 0x05 0x10 0x2540 AFH: On AFH Map: 500E4FDFFFFFFFF5F RSSI: -51 Role: Master Connection Mode: Sniff Mode Interval: 12.5 ms Host Connectable: Yes EDR Supported: No eSCO Supported: No SSP Supported: No JAMBOX by Jawbone: Address: 00-21-3C-8F-56-E0 Major Type: Audio Minor Type: Headset Services: Hands-Free unit, SPP Dev, Headset Paired: No Configured: Yes Connected: No Manufacturer: Cambridge Silicon Radio (0x5, 0x1A67) Class of Device: 0x04 0x01 0x240404 EDR Supported: Yes eSCO Supported: Yes SSP Supported: Yes William’s mouse: Address: D4-9A-20-4D-0E-1B Major Type: Peripheral Minor Type: Mouse Services: Apple Wireless Mouse Paired: No Configured: Yes Connected: No Manufacturer: Apple (0x3, 0x31C) Firmware Version: 0x0084 Vendor ID: 0x05AC Product ID: 0x030D Class of Device: 0x05 0x20 0x2580 Host Connectable: Yes EDR Supported: No eSCO Supported: No SSP Supported: No Services: Bluetooth File Transfer: When receiving items: Accept all without warning State: Disabled Bluetooth File Exchange: When other items are accepted: Save to location When receiving items: Accept all without warning State: Disabled Bluetooth Internet Sharing: State: Disabled Incoming Serial Ports: Bluetooth-Incoming-Port: RFCOMM Channel: 3 Requires Authentication: No Outgoing Serial Ports: Bluetooth-Modem: Address:
RFCOMM Channel: 0 Requires Authentication: No JAMBOXbyJawbone-SPPDev: Address: 00-21-3C-8F-56-E0 RFCOMM Channel: 1 Requires Authentication: No

[sejmann]

@wjteale Yeah, your BTLE dongle is definitely working, rather than the internal. You can tell both by the first line, "Bluetooth Low Energy Supported: Yes" and by the "LMP Version: 0x6" which would be "LMP Version: 0x4" if you were using the internal bluetooth module on our laptop. Also, the CAT diagnostics indicate it detected it properly. As to why handoff isn't working, I'll have to leave that to @dokterdok. =)

Out of curiosity, if you have multiple iOS devices running iOS 8, like both an iPad and an iPhone, can they handoff between each other? (For instance, after starting to compose an email on your iPhone, and then looking at your iPads lock screen for a little handoff icon in the lower left?)

[dokterdok]

@wjteale

Verifying Continuity status... OK. OS X reports Continuity as active

This looks good. If you don't have Handoff working at this stage it's because the handshake hasn't happened yet between your iOS and OS X devices. To force it:

1. Make sure you are on the same Wi-Fi on your Mac and iOS device, and that Handoff is enabled in the System Preferences / General and on your iOS device. Bluetooth should be on.
2. Log out iCloud on OS X
3. Log out iCloud on iOS (optional, only if you have the iOS 8.2 beta)
4. Log in iCloud on OS X
5. Log in iCloud on iOS (optional, only if you have the iOS 8.2 beta)
6. Try handoff and be patient: the handshake can take a few long minutes to happen

On 18 December 2014 at 14:05, wjteale notifications@github.com wrote:

This is my macbook pro ( Bluetooth ) system report now. I am not sure if Dongle is overriding internal bluetooth or not.

Apple Bluetooth Software Version: 4.3.1f2 15015 Hardware, Features, and Settings: Name: William's MacBook Pro (3) Address:

Bluetooth Low Energy Supported: Yes Handoff Supported: Yes Instant Hotspot Supported: Yes Manufacturer: Broadcom Transport: USB Chipset: 20702A3 Firmware Version: v14 c4096 Bluetooth Power: On Discoverable: On Connectable: Yes Auto Seek Pointing: On Remote wake: On Vendor ID: 0x050D Product ID: 0x065A HCI Version: 0x6 HCI Revision: 0x1000 LMP Version: 0x6 LMP Subversion: 0x220E Device Type (Major): Computer Device Type (Complete): Mac Portable Composite Class Of Device: 0x38010C Device Class (Major): 0x01 Device Class (Minor): 0x03 Service Class: 0x1C0 Auto Seek Keyboard: On Devices (Paired, Configured, etc.): William's keyboard: Address: E8-06-88-4B-65-B8 Major Type: Peripheral Minor Type: Keyboard Services: Apple Wireless Keyboard Paired: Yes Configured: Yes Connected: Yes Manufacturer: Apple (0x3, 0x31C) Battery Level: 100% Firmware Version: 0x0050 Vendor ID: 0x05AC Product ID: 0x0239 Class of Device: 0x05 0x10 0x2540 AFH: On AFH Map: 500E4FDFFFFFFFF5F RSSI: -51 Role: Master Connection Mode: Sniff Mode Interval: 12.5 ms Host Connectable: Yes EDR Supported: No eSCO Supported: No SSP Supported: No JAMBOX by Jawbone: Address: 00-21-3C-8F-56-E0 Major Type: Audio Minor Type: Headset Services: Hands-Free unit, SPP Dev, Headset Paired: No Configured: Yes Connected: No Manufacturer: Cambridge Silicon Radio (0x5, 0x1A67) Class of Device: 0x04 0x01 0x240404 EDR Supported: Yes eSCO Supported: Yes SSP Supported: Yes William's mouse: Address: D4-9A-20-4D-0E-1B Major Type: Peripheral Minor Type: Mouse Services: Apple Wireless Mouse Paired: No Configured: Yes Connected: No Manufacturer: Apple (0x3, 0x31C) Firmware Version: 0x0084 Vendor ID: 0x05AC Product ID: 0x030D Class of Device: 0x05 0x20 0x2580 Host Connectable: Yes EDR Supported: No eSCO Supported: No SSP Supported: No Services: Bluetooth File Transfer: When receiving items: Accept all without warning State: Disabled Bluetooth File Exchange: When other items are accepted: Save to location When receiving items: Accept all without warning State: Disabled Bluetooth Internet Sharing: State: Disabled Incoming Serial Ports: Bluetooth-Incoming-Port: RFCOMM Channel: 3 Requires Authentication: No Outgoing Serial Ports: Bluetooth-Modem: Address:

RFCOMM Channel: 0 Requires Authentication: No JAMBOXbyJawbone-SPPDev: Address: 00-21-3C-8F-56-E0 RFCOMM Channel: 1 Requires Authentication: No

Reply to this email directly or view it on GitHub https://github.com/dokterdok/Continuity-Activation-Tool/issues/85#issuecomment-67482905 .

[wjteale]

Thank you David. Signed out and in of icloud on all devices. Seems to be working fine now from both IPad and Iphone to Macbook .... But still not from Macbook to Ipad or Iphone. Will be patient. Donation definitely on the way. Thank you again

[sejmann]

@dokterdok Yeah, okay, thank you. I'll try again tomorrow with a Broadcom dongle. I appreciate your help. =)

Interestingly, the CSR BT dongle spontaneously activated after a few reboots/removals/insertions, and CAT now reports "OK. OS X reports Continuity as active". But you're right, the CRS config is apparently finicky. BT 2.0 connections work, but BTLE doesn't seem to work quite right (Authy connect between mac and iPhone doesn't work, for instance), but airdrop on my mac can see my phone, though can't send anything, and my phone can't see my mac at all. (Err, though I'm not sure if airdrop uses BT, or Wifi or both.) Handoff doesn't work at all. Oh well, I'll try again tomorrow with the Broadcom. Thanks!

[sejmann]

David, thank you! Tried the new Broadcom BTLE Dongle, and Continuity is working perfectly, both ways. Brilliant job pulling this all together so well, and bending over backwards to help us all. Not sure about the others, but as far as concerns me, you can close out this issue.

[dokterdok]

@wjteale One way handoff is unfortunately a common issue with Continuity even with new Macs, you'll find many similar reports on the Apple Support Communities for example. No perfect solution has been identified yet - it usually starts to work eventually, or you can try these steps again. That's what I usually do when I have that issue during my tests.

Many thanks to all for your reports. I'm closing the issue.