As I understand the procedure for El Cap and Sierra, you have to boot into recovery, disable sip, reboot, and run CAT, which then reboots again. Everything went fine for me until AFTER I ran CAT, when it went into re-boot loop and hung there. I had to boot back into recovery and then start the TM restore. Still running a HDD, so still a couple of hours to go. What a PITA. ???? Did I do something wrong?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Modded Continuity Activation Tool (BTLE cards) with El Capitan is working
- Thread starter Apple_Robert
- Start date
- Sort by reaction score
I need help please. Something is corrupted. I successfully completed a total TM restore back to El Cap 10.11.6. HOwever, I wanted to get completely rid of CAT 2.2.3, so I ran it, and chose uninstall. When it rebooted, I am back to the boot loop, and am having to do a restore again. I think it has to be something to do with erroneous Kext files, but am not sure how to fix it. I just want to get back to "normal", make a clean backup, and then try the NEWEST version of CAT. Thanks in advance, and sorry for the trouble. Tom
Restore your 10.11.6 backup
Download the 10.11.6 update (regular or combo, whichever you prefer) from Apple and install https://support.apple.com/downloads/macos
You will now be back to stock 10.11.6
No prob.
An SSD will def be an upgrade. I did it on my late 2011 MBP, boot time is 20 seconds.
All right, I admit I have a problem. Having spent hours successfully restoring, and then completely reinstalling El Cap, I then installed an SSD and upgraded to 16gb of memory. Of course the memory was defective, and gave me numerous total crashes over several days until I pulled it, went back to stock, and then replaced with substitute memory. Now, after all that, my early mbp15" is running perfect, yet I feel compelled to try again to get CAT to run. I can not stand to leave things alone or quit while I am ahead. So, please confirm - boot into recovery, disable sip, reboot, run CAT 2.3 which will then reboot again? This is where my machine went nuts last time and got hung in the boot loop. Obviously anxious, but I miss all of the features that CAT allowed me to use while I was in Yosemite. Any thoughts? Surely y'all have done this successfully. Don't know why mine hung up last time.
Does anyone have a copy of CAT v2.3 they can upload? I was trying out v2.4b on my MBP and it doesn't seem to be working that well. I thought I had a copy of v2.3 but apparently not.
Edit: Nevermind. I found a copy.
Edit: Nevermind. I found a copy.
Last edited:
So who here has a MBP with the alt BT card installed and using an iPhone w/ iOS 10? Is Handoff/Airdrop working for you? The only time either one of those works is if I open the BT Preferences pane, then Handoff will show on my mac. Same with Handoff. As soon as I close BT Preferences, Handoff won't work. Could it be something in iOS 10? Both my work and personal phones won't work. I know this is a Mac thread, but I just wanted to see if anyone else is having the same probs.
If someone could hand me a clue-by-four I'd appreciate it. I have a cMP 5,1 (late 2012). I've installed the Apple Broadcom BCM94360CD that I ordered via OSXWifi. Continuity works fine (phone calls etc) but Handoff does not.
Do I still have to use the CAT tool in order to get Handoff to work, even tho this is apple equipment? I can't figure that part out even after reading this thread.
Do I still have to use the CAT tool in order to get Handoff to work, even tho this is apple equipment? I can't figure that part out even after reading this thread.
I have the same question. In my case it's a MP 4,1 (early 2009) with firmware updated to 5,1. Currently on OS X 10.11.6, intend to upgrade to Sierra.
I installed the OSXWifi card and all looks good in system profiler. (4.0 ox6). But no luck on Handoff at all. All settings are as they should be (enabled handoff on both devices, signed out and in to icloud, toggled bluetooth/wifi, reset pram on Mac, deleted com.apple.bluetooth.plist file).
So is it required to use the CAT tool? I thought that this OSXWifi hardware was supposed to work out of the box? I would rather not be patching kext files every system upgrade if not necessary.
Well i never used the OSXWifi cards, but even if its original apple, its still not 'designed' for your system. THEREfore you need to run CAT to enable handoff. You probably also need to disable SIP to allow CAT to run correctly.
Hmmm… I apprecaite this response, but I'm really not sure how accurate this is. The chipset of what they sell should be "native", and there are lots of people who seem to have ordered this kit and report success with handoff, without mentioning needing to run CAT. But if you're right, does that mean it has to be run at every system upgrade?
I'll tell you this, I bought an apple card, and every update I rerun CAT to enable handoff and continuity.
I dont know how much more 'Native' it gets than straight from apple.
The problem is the hardware (hardware number) is coded to tell the OS that the system doesnt support continuity.
CAT removs that code and tells the OS that it Does have the hardware to run it, and 'turns it on'.
I dont know how much more 'Native' it gets than straight from apple.
The problem is the hardware (hardware number) is coded to tell the OS that the system doesnt support continuity.
CAT removs that code and tells the OS that it Does have the hardware to run it, and 'turns it on'.
Last edited:
Best thing to do would be to make a backup of your system (preferably a bootable clone) and then run CAT. If it works, cool. If not, and your system gets screwed up, just clone the image back to your drive and continue like nothing happened.
Thanks. That's huge info for those of us trying to read thru this whole thread. Maybe instread of removing mention from OP you can state that it is no longer required and explain why.
Well, I just ran CAT 2.3 on El Cap 10.11.6. It said only that continuity was already active but it still was going to patch something anyway. SIP was disabled and I then rebooted into recovery mode and re-enabled SIP and rebooted.
So far Handoff is still not working.
And according to the CAT wiki compatibility list it says that a "software patch" (eg CAT) is not required for my hardware (MacPro 2009 with wifi/bluetooth card "BCM94360CD + adapter"). So I'm again totally confused.
And yet after "patching" it reports this in diagnostic:
how can I verify if anything was really patched? Where are the backups of the original system files copied exactly?
Any other ideas what may be wrong? (note as above i've already logged out/in/off/on icloud/wifi/bluetooth).
I finally succeed in getting Handoff to work. All it seems to have involved was purging the system kext cache and rebooting. I wrote up my entire upgrade experience on my blog, and that part is at the end.
This is a great article. Thanks for writing it.
EDIT: Clearing the kext caches described here: http://superuser.com/questions/251113/safe-to-delete-system-library-caches-com-apple-kext-caches seems to have done the trick!
Last edited:
Do you need to disable SIP for this to work? Ok, just checked, my SIP was disabled all the time.
Installed CAT on late 2008 macbook 13 5,1. The install went fine but after reboot, macbook is not starting. Get some terminal panic screen. I am using GMYLE dongle.
Is there anything I could do about it?
Installed CAT on late 2008 macbook 13 5,1. The install went fine but after reboot, macbook is not starting. Get some terminal panic screen. I am using GMYLE dongle.
Is there anything I could do about it?
Last edited:
At this point you'd need to have a recovery disk or bootable install media for OSX. You can also try to go into recovery mode and re-install the OS.
https://support.apple.com/en-us/HT201314
Hi, thanks! I've already restored the macbook using recovery partition and time machine. The point is that I've purchased the dongle for continuity to work, and the CAT now is not working. And I dont know how to get it working now, since I've already tried installing it twice, and both of the times my machine ended up dead upon reboot.
This is the exact same error that I get. But I dont have VirtualBox installed. Does it mean that I have to install clean OS and see if that helps? If yes, then how do I find out which software is causing the problem? Is there any other application that is known to give this issue other than VB?My macbook won't boot past this