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

[piojofafner]

Add a key in that entry named 'Disabled', as boolean, set to true.

Thanks. Believe or not I was able to do it!

You spelled it wrong.
You have 'Disable'.
Should be 'Disabled'.

Read post #91. Carefully.

Yes I am so stupid. Thanks again for all your help!!!!

 

[RehabMan]

I ran the ConvertToAPFS false script

No idea what "script" you're referring to.

but when I reboot I don't find an option in the Clover user interface for "Boot macOS Install from" option.

Seems off-topic.
Open a separate thread.
Attach "Problem Reporting" files as per FAQ.

Also, attach output of "diskutil list" in Terminal.

 

[macnb]

If you see 'TRIM Support: Yes' in System Information.app (aka system profiler), then trim is enabled for that devcie and you have to trust that TRIM commands are being sent.

Which means TRIMFORCE command is not working since after running it to disable TRIM, system profiler still says Support = Yes.
Lot of beta testers had issues with TRIMFORCE and looks like it's not fixed in the released OS.

 

[erice]

Ciao.
Sorry, but remaining on HFS + J why should you leave Sierra for High Sierra?

 

[vulgo]

Which means TRIMFORCE command is not working since after running it to disable TRIM, system profiler still says Support = Yes.
Lot of beta testers had issues with TRIMFORCE and looks like it's not fixed in the released OS.

That command installs/uninstalls an injector kext named AppleDataSetManagement to /S/L/E

 

[vulgo]

Ciao.
Sorry, but remaining on HFS + J why should you leave Sierra for High Sierra?

Surely its asking for problems when the updates start landing.

 

[vulgo]

Probably. I'll just leave it alone for now and do a from scratch install later when Clover/Unibeast/Multibeast have been upgraded to reflect the file system changes. And it sounds like it would be smart to go with a conventional spinner drive at that time unless the trim issue is fixed.

With trim your mileage (and boot times) will probably vary considerably according to SSD firmware.

 

[RehabMan]

This one: /Applications/"Install macOS High Sierra.app"/Contents/Resources/startosinstall --converttoapfs NO --agreetolicense

Is "Script" not the correct term? Maybe "terminal command"? Why do you say it is off topic? It is exactly what this whole thread is about. When I run this terminal command and the machine reboots and I enter Clover, I see no "Boot macOS Install" option in Clover as per the instructions in the first post of this thread. On the other hand, after running the said terminal command and if I just allow the machine to reboot normally, I am back to the Sierra Desktop and the High Sierra installation has not happened.

Your issue is likely an incorrect Clover setup or a core storage disk setup.
Working with the installer is not covered here.
That is a separate guide:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

You need to open a separate thread and attach what was requested in my previous reply.

 

[RehabMan]

Which means TRIMFORCE command is not working since after running it to disable TRIM, system profiler still says Support = Yes.
Lot of beta testers had issues with TRIMFORCE and looks like it's not fixed in the released OS.

No change expected for NVMe disks.
No change expected until reboot.
If trimforce is not working for the expected scenario (SATA non-Apple SSD, after reboot), you should do a fresh install as it is likely you installed something else that has enabled trim.

 

[Henties]

Yes.
Full instructions are in post #1.

Sorry I missed that somehow. On the side I use vim, since the early 90's, and find the enhancements originally made to vi by Bram Moolenaar, quite useful. I use that command line editor with all my "...nix" based systems.