Contribute
Register

[Guide] Avoid APFS conversion on High Sierra update or fresh install

There are
 

Attachments

  • Screen Shot 2017-10-12 at 17.51.50.png
    Screen Shot 2017-10-12 at 17.51.50.png
    140.1 KB · Views: 202
Figured it out
disabled SIP and now I can use the --mount argument
don't know why it doesn't work with SIP enabled
 
Figured it out
disabled SIP and now I can use the --mount argument
don't know why it doesn't work with SIP enabled

No such thing as --mount... perhaps you mean --volume.

SIP should never be enabled on a hack anyway.
It probably has to do with NVRAM access. And it might change depending on 'sudo' or lack thereof.
The startosinstall probably has to write the target volume into NVRAM for use when the system reboots into the installer.
 
Yes, meant --volume
 
SIP should never be enabled on a hack anyway.
Why not?
It's working very nice so far
Plus I don't need fixes for apps/drivers by 3rd parties which install kexts in /Library/Extensions.
Just approve them in gatekeeper.
 

It is not possible to predict when the system may decide to rebuild kernel cache.

If you rebuild kernel cache and you happen to have unsigned/invalid signature kexts in /L/E or /S/L/E (such as FakeSMC.kext), they will be excluded from kernel cache and your system will not boot.

Therefore, you should keep SIP disabled at all times.
 
Hello RehabMan, where I can found the .plist from my "Install macOS High Sierra.app"?
I see that you have the last version 17A405.

Inside "Install macOS High Sierra.app", you find Contents/SharedSupport/BaseSystem.dmg.
If you mount BaseSystem.dmg, you find System/Library/CoreServices/SystemVersion.plist.
Inside the plist is the build/version info.
 
Back
Top