Closed abgen27 closed 4 years ago
Yeah, I've been running into this as well, I need to keep it disabled to work. cc @w0lfschild is there a way that I can change how this is setup to not require csrutil
to stay disabled on Catalina? Does all of MacForge need it to stay disabled, or is it just SpacesRenamer?
So you need to have at least:
csrutil enable --without debug --without fs
I think this might also be required:
sudo defaults write /Library/Preferences/com.apple.security.libraryvalidation.plist DisableLibraryValidation -bool true
You do not want:
sudo nvram boot-args="amfi_get_out_of_my_way=1"
You can get rid of the above with:
sudo nvram boot-args=""
Updated post
Thanks for the guidance @w0lfschild. I tried all of your instructions, and it appears that SpacesRenamer is working now. Note that only the first line of code you suggested (csrutil enable --without debug --without fs
) worked.
See screenshots below for the error messages I received for the other two codes you suggested (I tried all variations).
Thanks for your help. Amar
@abgen27
Since you're trying to run the command in recovery mode you automatically have root powers so you would run the commands without sudo, but that command can just be run on a normal boot with sudo.
Marking this as resolved, will update the README with this.
Versions
I am able to get spaces-renamer to work during the initial install following all steps outlined in the read-me. However, when I reboot my Mac and reenable csrutil it stops functioning. I've done this twice and same result.
Attempt #1: on restart I did csrutil enable Attempt #2: I tried to follow the instructions on MacForge under the 'System' tab csrutil enable --without fs --without nvram --without debug; nvram boot-args="amfi_get_out_of_my_way=1" but same result. In fac, I got an error message in the recovery terminal stating that nvram wasn't a recognized term (forget exact wording)
Can someone please help me understand what I'm doing wrong?