Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Nothing...

Thanks for the help anyway ;)

Hmm. There is one small thing I did differently. When I installed CAT the first time I didn't back up the Kext so when my wifi wouldn't work I replaced it with the kext I had copied from when I was running Yosemite, this made my wifi work again. I then proceeded to use the CAT.
 
I'm struggling cannot seem to get it to work, the option just does not appear in settings... has it working no problem in Yosemite....
 
I've experienced lag on Magic Mouse + Mac Mini 2011 + El Cap Public Beta 1. Solved only after removing CAT 2.1.

Any help?
 
Updating to El Capitan Public Beta 2 required running the CAT program again. Handoff and Continuity are now working.
Tried for the first time on DP4, it is not working for me on a mid-2010 15" MBP w/ an Asus BT400.

After running your modded CAT, I get no wifi and (sometimes) no bluetooth. I tried the "original" CAT on Yosemite and it worked, so I copied over the patched IO80211Family.kext to El Capitan, re-created kext caches and now your modded CAT says "No changes were applied, your system seems to be already OK for Continuity". However, continuity does not get enabled.
AirDrop, however, now works to and from iOS devices.

If you need any help/testing, I'll gladly help. Thanks for all your efforts!
 
Tried for the first time on DP4, it is not working for me on a mid-2010 15" MBP w/ an Asus BT400.

After running your modded CAT, I get no wifi and (sometimes) no bluetooth. I tried the "original" CAT on Yosemite and it worked, so I copied over the patched IO80211Family.kext to El Capitan, re-created kext caches and now your modded CAT says "No changes were applied, your system seems to be already OK for Continuity". However, continuity does not get enabled.
AirDrop, however, now works to and from iOS devices.

If you need any help/testing, I'll gladly help. Thanks for all your efforts!
Thank you for sharing your experience.

The modded CAT I was speaking of was made by sysfloat and is referenced in post #77.

https://forums.macrumors.com/thread...pitan-is-working.1890715/page-4#post-21502588
 
hi, sorry for the English language, I am French. With El Capitan public beta 1 or beta 2, I have great downturn and disconnections of the Magic Mouse to the point that El Capitan is almost unusable. I uninstall CAT and everything returns to normal.
 
Had great success with (and donated to) CAT, right up through El Cap PB1 with iOS 9 B1. Since upgrading to El Cap PB2 and iOS 9 B2, and reinstalling CAT 2.1, through a couple sign-outs of iCloud, I seem to have lost my Handoff & Continuity in both directions. Running CAT app shows app installed properly, AirDrop is working fine, and System Diagnostic on Bluetooth panel shows all as it should be on my mid 2013 MacBook Air. Any suggestions to bring it back...? Thanks in advance...
 
Hi, today i just installed the fifht beta of El Capitan, but trying to use the modded CAD it's returns me a lot of errors and when I restart my computer just crashes and don't boot, I have a mac book pro early 2011.
When are we going to have a compatible version with the Capitan Beta 5?
 
Hi, today i just installed the fifht beta of El Capitan, but trying to use the modded CAD it's returns me a lot of errors and when I restart my computer just crashes and don't boot, I have a mac book pro early 2011.
When are we going to have a compatible version with the Capitan Beta 5?
Which CAT did you use?
 
Hi, today i just installed the fifht beta of El Capitan, but trying to use the modded CAD it's returns me a lot of errors and when I restart my computer just crashes and don't boot, I have a mac book pro early 2011.
When are we going to have a compatible version with the Capitan Beta 5?

Just had the same problem. The cause of this seems to be the IOBluetoothFamily.kext. I wasn't able to boot even after reinstalling the kext that I made before running the tool nor using the recovery disk one.
I will investigate further tomorrow.
For anyone that's unable to boot:
1. Hold CMD + R and turn or your mac.
(2). Mount your locked drive using disk utility if it's FielVault protected.
3. Open Terminal (main screen - Utility - Terminal)
4. type: "rm -rf '/Volumes/YOURVOLUMENAME/System/Library/Extensions/IOBluetoothFamily.kext'" (YOURVOLUMENAME should be Macintosh HD by default, check disk utility if you're not sure.)
5. type: "kextcache -update-volume /Volumes/YOURVOLUMENAME"
6. you should now be able to boot. bluetooth won't be available though.

Could anyone please send me the original IOBluetoothFamily.kext file via pm?
 
Just had the same problem. The cause of this seems to be the IOBluetoothFamily.kext. I wasn't able to boot even after reinstalling the kext that I made before running the tool nor using the recovery disk one.
I will investigate further tomorrow.
For anyone that's unable to boot:
1. Hold CMD + R and turn or your mac.
(2). Mount your locked drive using disk utility if it's FielVault protected.
3. Open Terminal (main screen - Utility - Terminal)
4. type: "rm -rf '/Volumes/YOURVOLUMENAME/System/Library/Extensions/IOBluetoothFamily.kext'" (YOURVOLUMENAME should be Macintosh HD by default, check disk utility if you're not sure.)
5. type: "kextcache -update-volume /Volumes/YOURVOLUMENAME"
6. you should now be able to boot. bluetooth won't be available though.

Could anyone please send me the original IOBluetoothFamily.kext file via pm?

I've got my backup here, hope I'll be usefull https://www.dropbox.com/sh/mz2jmifa0d6b5mx/AAA3otKsV_2CWzPEIZjQ2sS8a?dl=0
 
So that's weird.. wasn't able to boot today even though I removed IOBluetoothFamily.kext. After removing every bluetooth related kext I was able to boot again.
I then installed the bluetooth kexts from the recovery image.
My mac booted fine but bluetooth still wasn't available..
I then installed my backup of IOBluetoothFamily.kext and everything worked fine again. I ran CAT 2.1 rebooted and Continuity works fine too.
I'm not sure whether my other bluetooth kexts were broken or something else happend?
It's also pretty interesting that the recovery image files are different then mine.
file name - my file size - recovery image file size
AppleBluetoothMultitouch.kext - 158KB - 158KB
AppleBluetoothRemote.kext - 336KB - missing (too new?)
IOBluetoothFamily.kext - 4.1MB - 1.6MB (huh?)
AppleMIDIBluetoothDriver.plugin - 314KB - 123KB
Any feedback would be greatly appreciated..

TL;DR: Had to reinstall all bluetooth kexts from recovery image. CAT 2.1 still works though!

P.S.: I updated the readme on github with some instructions to fix your mac if you run into booting problems.
 
CAT 2.1 beta (Sysfloat modded) does not work with El Capitan PB 3.


p: /System/Library/Extensions/IOBluetoothFamily.kext/: unable to copy extended attributes to /Applications/KextsBackupBeforePatch/IOBluetoothFamily.kext: Operation not permitted

cp: /System/Library/Extensions/IO80211Family.kext/: unable to copy extended attributes to /Applications/KextsBackupBeforePatch/IO80211Family.kext: Operation not permitted

OK. Wi-Fi and Bluetooth kexts were backed up in '/Applications/KextsBackupBeforePatch'

Patching whitelist................. OK

Cleaning up old Wi-Fi kext... OK

Applying legacy Wi-Fi card patch... OK

Updating kext caches... OK

I got the same errors regardless of whether or not SIP was turned on.

After several attempts of install, Airdrop is now working. Still working on getting handoff to kick in.
 
Last edited:
Mine seems to apply fine, but when i reboot it doesnt show any 'handoff' check boxes.
I did put the Kexts from beforepatch in the /extensions/ folder before hand and used the 2.1 beta
 
How to force it to work with pb3 (result: bluetooth - OK; wi-fi - exist)? On pb1 and pb2 worked well.
What version I must to use: original 2.1 or modded?

MBA mid 2011
 
How to force it to work with pb3 (result: bluetooth - OK; wi-fi - exist)? On pb1 and pb2 worked well.
What version I must to use: original 2.1 or modded?

MBA mid 2011

this works fine!!!

Many thanks sysfloat ;)

Yeah this is normal, you still had the rootless=0 boot-args set in the NVRAM, they should stay set until Apple decides they no longer allow it.


Here's my new updated tool with a few new features and bug fixes.
Please make a backup of all your files and keep in mind that this tool is in a beta stage, on a beta OS. This also still doesn't work with dognles (see the readme on github).
Please post or PM me any working models.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.