-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System Diagnostics makes changes to the system #1
Comments
Thanks for the report. There are two issues mentioned in your post. |
V1.0.2 now lets me cancel before it makes any changes. I guess bug #1 is officially fixed! |
I'm afraid I haven't fixed this yet. Running diagnostics in v1.0.2 still enables kext-dev-mode in the boot-args (although without changing any other nvram settings, unlike v1.0.0), even when hitting ctrl-c. The patch is in the pipeline for the next release. |
This has been fixed in hte latest v.1.1.0. |
* Fixed: OS X version check typo corrected, which affected execution on case sensitive file systems ([#97](#97 )) * Fixed: rare ioreg crash issue ([#100](#1 00)) * Fixed: running the script from the command line no longer kills Terminal when quitting ([#101](#101 )) * Fixed: the ```-f | --forceHack``` command line option now correctly skips the Wi-Fi card device-id(s) injection check and Bluetooth blacklist check * Fixed: CAT utilities are now correctly detected when running the tool from the command line * Fixed: disk permissions repair is no longer silently skipped in some cases when forcing the activation
Closing. |
When I ran the diagnostic I was expecting for the tool just to check my compatibility with the tweak and report to me what changes were needed to make it work.
However, the utility made me reboot my system and changing some settings (boot-args, I suppose). This change made my graphic switch glitch an I ended up needing t do a NVRAM reset to solve the issue.
I'm running Yosemite on a MacBookPro6,2.
The text was updated successfully, but these errors were encountered: