dokterdok / Continuity-Activation-Tool

An all-in-one tool to activate and diagnose macOS 10.10-12 Continuity on compatible Mac configurations.
MIT License
1.6k stars 150 forks source link

Unable To Enable Continuity And Kernel Panics After Running Tool #464

Open MikeDeezy100 opened 5 years ago

MikeDeezy100 commented 5 years ago

Have you tried these steps? Yes

Is there already an open topic for this issue? Not that I could find

Please include the following information.

Your Issue: After running the CAT tool and rebooting my Mac will reboot two or three times before macOS notifies me that a third party kernel extension is preventing my Mac from booting. When I look at the logs I see airport.brcm4360 is to blame. The only fix for the kernel panics during boot is to reinstall macOS from recovery.

Steps done to try to fix the issue: Running the tool using the commands listed including the -f flag with no success.

This is the output of the compatibility check.

--- 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: MacPro5,1 Verifying Mac board-id... OK. Short board id detected: Mac-F221BEC8 Verifying OS X version... Warning: This tool wasn't tested with OS X versions higher than 10.10. Detected OS version: 10.14.6 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... OK. Bluetooth 4.0 detected 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: v14 c4096 Verifying Login Item... OK. Login item for Auto Continuity Check is not set.

--- 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 ATTENTION: run in sandbox Verifying Wi-Fi whitelist status... OK. The whitelist is manually patched with your board-id as expected at the first location Checking legacy kext... OK. Not using legacy kext. Verifying BT4 dongles compatibility... OK. Compatibility with BT4 USB dongles is not enabled, this tool can fix this if a dongle is plugged in 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. --- Modifications check ---

robog0bo commented 5 years ago

I'm a little unclear as to whether this tool is still under development or even consideration for being updated to work under 10.14, or even 10.13. There are a few blogs and even comments around here suggesting @dokterdok is working on it, but I can't find anything official.

As to this issue. One global problem I see is the omission of instructions to move the tool out of the Downloads folder after unzipping to avoid them being sandboxed (there's a more official name for this but it escapes me). It looks like that's a possible contributor to your issue as indicated in the logs.

robog0bo commented 5 years ago

Oh I didn't notice @dokterdok has backed out of the project. So is @sysfloat still contributing?