Is it just me or is SIP bugged.
1. disable SIP from recovery terminal csrutil disable
2. check status and it says disabled
3. boot to main system and check status and it says disabled
3. update Xcode and open it up and let it install components
4. check for SIP status on main system and it says enabled
5. boot to recover and check status and it says disabled
6. boot back to main system and it says enabled
7. boot to recovery and run csrutil disable even though it is already disabled
8. boot back to main system and check status and it says enabled
9. install os x on top of the one u already have
10. check status and it says disabled
11. open Xcode and it reinstalls components then same problem SIP enabled even though it is disabled
long story short
csrutil status shows disabled in recovery and enabled on main system
the heck is going on, is it a safety feature apple force enabling SIP on macs with Xcode installed or is it a bug which apple engineers aren't skilled enough to fix.
using 13 inch early 2011 MBP 10.11.2 and same problem occurring since 10.11
1. disable SIP from recovery terminal csrutil disable
2. check status and it says disabled
3. boot to main system and check status and it says disabled
3. update Xcode and open it up and let it install components
4. check for SIP status on main system and it says enabled
5. boot to recover and check status and it says disabled
6. boot back to main system and it says enabled
7. boot to recovery and run csrutil disable even though it is already disabled
8. boot back to main system and check status and it says enabled
9. install os x on top of the one u already have
10. check status and it says disabled
11. open Xcode and it reinstalls components then same problem SIP enabled even though it is disabled
long story short
csrutil status shows disabled in recovery and enabled on main system
the heck is going on, is it a safety feature apple force enabling SIP on macs with Xcode installed or is it a bug which apple engineers aren't skilled enough to fix.
using 13 inch early 2011 MBP 10.11.2 and same problem occurring since 10.11