Modded Continuity Activation Tool (BTLE cards) with El Capitan is working

Discussion in 'OS X El Capitan (10.11)' started by BasicGreatGuy, Jun 8, 2015.

  1. BasicGreatGuy, Jun 8, 2015
    Last edited: Sep 17, 2015

    BasicGreatGuy Contributor

    BasicGreatGuy

    Joined:
    Sep 21, 2012
    Location:
    In the middle of several books.
    #1
    Edited to add: CAT is now working. The latest sysfloat CAT can be found here.

    If anyone has trouble getting CAT to work, (via error messages etc) please post your Mac model, model card or dongle.

    Make sure you have a recent backup before going through the process, just in case something untoward happens.

    Thanks to Scoobie for working to help debug the older CAT problem with Handoff, and to Sysfloat for keeping CAT abilities alive for us and refining the install process.
     
  2. iamMacPerson macrumors 68030

    iamMacPerson

    Joined:
    Jun 12, 2011
    Location:
    AZ/10.0.1.1
    #2
    What about machines that didn't need the tool, but instead needed a hardware upgrade like the Mac Pro towers? I'm curious.

    EDIT: Dammit. This means even if I get the hardware upgrade for my MacBook, I'm still f*ed. Thanks Apple.
     
  3. BasicGreatGuy thread starter Contributor

    BasicGreatGuy

    Joined:
    Sep 21, 2012
    Location:
    In the middle of several books.
    #3
    I have read on here as well as on another site, (Trim Enabler) that no third party Kext signing (read: changing) will be allowed. If your upgrade doesn't call for the Kext to change, you may be ok.
     
  4. Zorn macrumors 6502a

    Zorn

    Joined:
    Feb 14, 2006
    Location:
    Ohio
    #4
    Netkas has said if you run with boot args kext-dev-mode=1 and rootless=0 , the system works just like Yosemite. This shouldn't be an issue.
     
  5. BasicGreatGuy thread starter Contributor

    BasicGreatGuy

    Joined:
    Sep 21, 2012
    Location:
    In the middle of several books.
    #5
    How does one go about checking that?
     
  6. macintoshmac macrumors 65816

    macintoshmac

    Joined:
    May 13, 2010
    #6
    Are we really going to be running in rootless=0 for some kext? What's the point of going the mac way if we will compromise on the secure foundation itself?
     
  7. LewisChapman macrumors 6502a

    LewisChapman

    Joined:
    Jan 10, 2015
    Location:
    UK
    #7
    I can confirm that CAT doesn't work with 10.11. Here is the text I receive when performing a 'System Diagnostic' within CAT (apologies for not attaching a screenshot, I am receiving a 'Plug-in failure' message within Safari):

    --- 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: MacBookPro8,1

    Verifying Mac board-id... OK. Long board id detected: Mac-94245B3640C91C81

    Verifying OS X version... Warning: This tool wasn't tested with OS X versions higher than 10.10. Detected OS version: 10.11

    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... /Applications/Continuity Activation Tool.app/Contents/Resources/contitool.sh: line 357: [: 6

    6: integer expression expected

    NOT OK. Your hardware doesn't support Bluetooth 4.0, necessary for Continuity. Current LMP Version=6

    6, expected 6.

    Verifying Bluetooth features... WARNING. Unknown Bluetooth features have been detected (code:15

    15). This tool can try to fix this.

    Verifying Bluetooth firmware... OK. Bluetooth firmware version: v149 c5831



    --- 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. Warning: Blacklist not found in the Bluetooth drivers. An OS X update might have made this hack useless.

    However, your Mac model shouldn't need to be removed from that blacklist.

    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... WARNING. Unpatchable drivers found. They are either already patched or don't support CAT.

    Press any key to go back to the main menu...
     
  8. SlCKB0Y macrumors 68040

    SlCKB0Y

    Joined:
    Feb 25, 2012
    Location:
    Sydney, Australia
    #8
    We've lived through 10 versions of OS X without enforced kext signing and 11 without root protection and now suddenly its a massive security issue to disable these "features"? o_O
     
  9. LewisChapman macrumors 6502a

    LewisChapman

    Joined:
    Jan 10, 2015
    Location:
    UK
    #9
    I agree with you completely here. People seem to think that Apple are trying to 'protect' us with these features however I think they exist more so to encourage us to buy the new product by limiting our upgrade options.
     
  10. Jarman74 macrumors regular

    Jarman74

    Joined:
    Mar 22, 2009
    #10
    El Crappytan.
     
  11. BasicGreatGuy thread starter Contributor

    BasicGreatGuy

    Joined:
    Sep 21, 2012
    Location:
    In the middle of several books.
    #11
    Would it be possible to turn off the Rootless system file protection, use the Continuity Activation Tool, and turn Rootless protection back on? If so, how would one go about it?
     
  12. MichaelDT macrumors member

    Joined:
    Aug 18, 2012
    #12
    Well interestingly, on my install on DP 1 bluetooth and continuity are working out of the box. I have a 2011 iMac with an upgraded n/bt 4.0 airport card in the wifi slot. Perhaps apple decided to remove the whitelist/blacklist. I'm sure it was an oversight and in a later preview I'll find it nuked.
     
  13. abcdefg12345 macrumors regular

    abcdefg12345

    Joined:
    Jul 10, 2013
    #13
    i tried rootless = 0 in terminal then i ran the activation tool still didn't work

    looks like the only thing apple worked on improving in el crappytan is blocking users from getting new features on older hardware.:rolleyes:
     
  14. vopol macrumors newbie

    Joined:
    Jun 10, 2015
    #14
    i've type in terminal sudo nvram boot-args="rootless=0" than delete IO80211Family.kext and IOBluetoothFamily.kext from System/Library/Extensions, make sure that this "kext" were copy in Library/Extensions, after that i run CAT and it work's for me. MBP 13" late 2011
     
  15. BasicGreatGuy thread starter Contributor

    BasicGreatGuy

    Joined:
    Sep 21, 2012
    Location:
    In the middle of several books.
    #15
    Did you turn rootless back on afterward? If so, what command did you use? It is my understanding, that if rootless is off, there is no more automatic disk repair with updates.
     
  16. vopol macrumors newbie

    Joined:
    Jun 10, 2015
    #16
    No, i didn't turn rootless back
     
  17. Dwalls90 macrumors 601

    Dwalls90

    Joined:
    Feb 5, 2009
    #17
    Why not wait for the GM? This tool came out after Yosemite launched, so perhaps they have excluded it from the beta as it's not a core service and it's being rethought.
     
  18. till213 Suspended

    Joined:
    Jul 1, 2011
    #18
    By the way that is a bad way of setting boot arguments! You are also overwritting any existing boot arguments that might be set already!

    Better check the existing settings first, then append your desired settings (such as rootless=0).

    In order to enable rootless simply omit that option the next time you set your boot arguments.

    As for the question about whether you need to keep "rootless" disabled after having done your kernel extension modifications: I cannot tell from my own experience, but according to a discussion about "Trim enabler and El Capitain" it is okay to re-enable "rootless", after the corresponding Apple kext has been "patched" (by Trim Enabler).
     
  19. abcdefg12345 macrumors regular

    abcdefg12345

    Joined:
    Jul 10, 2013
    #19
    i did as u suggested i ran the command sudo nvram boot-args="rootless=0" in terminal then deleted IO80211Family.kext and IOBluetoothFamily.kext from System/Library/Extensions and ran the tool still got the error

    Screen Shot 2015-06-11 at 12.34.47 AM.png

    running this tool on early 2011 MBP with the hardware upgrade which is still working on Yosemite partition
     
  20. BasicGreatGuy thread starter Contributor

    BasicGreatGuy

    Joined:
    Sep 21, 2012
    Location:
    In the middle of several books.
    #20
    I got the same message. For some reason, I couldn't find the two kext files noted, even though I used Spotlight to search in the Extensions folder.

    I miss my Airdrop ability.

    * Side note - I was able to get MacID working after turning off rootless, rebooting, installing MacID, and then turned rootless back on. That was one of my other heavily used apps that I am glad to get back.
     
  21. r4ndy macrumors newbie

    Joined:
    Jun 10, 2015
    #21
    It is still possible to unlock Continuity manually.
    Just follow the tutorial here but instead of running sudo nvram boot-args="kext-dev-mode=1" run
    sudo nvram boot-args="kext-dev-mode=1 rootless=0". After a verifying everything works fine after a reboot you can reenable rootless by running sudo nvram boot-args="kext-dev-mode=1".
     
  22. venom466 macrumors member

    venom466

    Joined:
    Aug 4, 2014
    Location:
    Italy
    #22
    yeah! it works on MBA mid 2011

    [​IMG]
     
  23. crjackson2134 macrumors 68020

    crjackson2134

    Joined:
    Mar 6, 2013
    Location:
    Charlotte, NC
    #23
    Having upgraded my Mac Pro hardware back in Mavericks, continuity and handoff work just fine in both Yosemite and Cappy.
     
  24. BasicGreatGuy thread starter Contributor

    BasicGreatGuy

    Joined:
    Sep 21, 2012
    Location:
    In the middle of several books.
    #24
    I am confused starting with the part about opening the kext file with OXeD app.
     
  25. LewisChapman macrumors 6502a

    LewisChapman

    Joined:
    Jan 10, 2015
    Location:
    UK
    #25
    I do apologise if I'm being a bit dull here, a lot of this language is above me. I just run the (brilliant) CAT and it has always worked for my MBP 2011.

    Since TRIM can be enabled in El Cap natively, does that not suggest that we have a good chance at permanently enabling continuity on older devices by taking advantage of this method?
     

Share This Page