

(again, make a backup of the original, copy the IO80211Family.kext to your desktop, do the edits there and copy it back to S/L/E) - again, you need to be in terminal to repair the permissions to the file, then rebuild your kext cache (or use kext utility to do this work for you) Once you search all the way down to "mac-phi-state", you're done. There's actually two sections that your board-id must be in.

That's the file you need to hex edit and look for mac- (board ID's) and change one of the existing values in each section to your board ID (zero filled with 0's to the right - so it would look like Mac-F221BEC800000000 Presuming you have a Broadcom card for this next bit.įor the IO80211Family.kext, the whitelisting is in the /Contents/PlugIns/AirPortBrcm4360.kext/Contents/MacOS/AirPortBrcm4360 module. In terminal as well - so you can fix the ownership and permissions on the file: (/System/Library/Frameworks/amework/Versions/A/Resources)

Not sure if you need the specifics, but I'll put them here in case others do.įor the ist, you need to copy it somewhere else (make a backup of the original) - if you look at the file, you'll see the sections for the systems that DO support Continuity don't even have a "ContinuitySupport" section - so, just delete those bits for your card. Pretty sure you can re-enable SIP once you've completed them. (CAT also says they were whitelisting in IOBluetoothfamily.kext, but I haven't been able to find where they were doing that). The two bits I needed to change for everything to work were the amework and whitelisting in the IO80211Family.kext for my board ID. So far.Ĭlick to expand.I have a similar setup in that my MBP 17" 4,1 has a replacement BT/WIFI. They continue to work after a re-start, too. Then, the other Continuity features all seemed to start working. The call would pop up on my iMac and I'd answer it on my iMac. The thing that seemed to trigger it to start working on this machine, for both Beta and Master, was to make a phone call to my iPhone from a different phone. I forget exactly what it said.īut anyway, Continuity still wouldn't work, so I'd try logging out and in iCloud on my iMac and my iPhone, but still no change. But if I then ran (1) Activate Continuity, it would tell me that it was already active but that it was making changes to correct something. I tried different things within the tools including running (2) System Diagnostic, which would tell me that everything was ok and Continuity was already activated. I ended up loading Sierra on two different drives to test and play with Continuity Activation Tool, and I was able to get Continuity to work with Sierra using both Beta and Master versions. I don't have a Watch so can't touch on that. I have Continuity features working on my upgraded (BT/WIFI card) 2011 iMac on Sierra, including the new copy/paste.
