Jump to content
fantomas

[pre-release] macOS High Sierra

3,823 posts in this topic

Recommended Posts

thank you for info

but 0x3ff is no luck like 0x3e7

 

In find cecekpawon'post http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page-691?do=findComment&comment=2467180 And try this tool: csrstat. Give me your opinion on the results for csrutil status?

 

Under Sierra with 0x3e7

 

 

post-1110743-0-14698200-1504502020_thumb.png

Share this post


Link to post
Share on other sites
Advertisement

In find cecekpawon'post http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page-691?do=findComment&comment=2467180 And try this tool: csrstat. Give me your opinion on the results for csrutil status?

 

Under Sierra with 0x3e7

 

okay. good script. i don't know crsutil detail. i just checked system profiler's difference on each crsutil value.

i will check more

0x67 result

 

Sherlocksui-MacBook-Pro:~ sherlocks$ /Users/sherlocks/Downloads/csrstat 

System Integrity Protection status: disabled.

 

Configuration: (0x00000067)

Apple Internal...........: disabled

Kext Signing Restrictions: disabled

Task for PID Restrictions: disabled

Filesystem Protections...: disabled

Debugging Restrictions...: disabled

DTrace Restrictions......: disabled

NVRAM Protections........: disabled

Device Configuration.....: enabled

BaseSystem Verification..: enabled

Sherlocksui-MacBook-Pro:~ sherlocks$ 

Share this post


Link to post
Share on other sites

okay. good script. i don't know crsutil detail. i just checked system profiler's difference on each crsutil value.

i will check more

0x67 result

Strange: with this tool, crsutil detail show "Configuration: (0x000001e7) " with crs 0x3e7. While with 0x67 result "Configuration: (0x00000067)"

Share this post


Link to post
Share on other sites

update from App Store not working, I update my r`MBP than clone again and applied clover etc.

working good...is there NVIDIA drivers for this beta?

post-474300-0-54188700-1504533131_thumb.png

Share this post


Link to post
Share on other sites

thanks sandro I was hoping I wouldn't have to fix dsdt and ssdts.  I did disable gpu with DSDT reg fix but don't think thats enough.will have another go later cheers!

Please, niknod could teach me how to disable the Nvidia card through SSDT. You could send me your patched SSDT. As you know I had the same problem as you with MacOS High Sierra update beta 8 (WindowServer)
 
Thank you
 
P.D.:
 
I extend my request to any other member who can help me
 
 
 

Share this post


Link to post
Share on other sites

Strange: with this tool, crsutil detail show "Configuration: (0x000001e7) " with crs 0x3e7. While with 0x67 result "Configuration: (0x00000067)"

 

i tested all. in script, some parts shown wrong info that you mentioned
0x3FF
all flags are disabled. just shown System Integrity Protection status: enabled on system profile, actually disabled all csr flags, script also shown enabled with "Custom Configuration"
 
0x3e7
except CSR_ALLOW_KERNEL_DEBUGGER, CSR_ALLOW_APPLE_INTERNAL, all flags are disabled.
 
i don't exactly know role of each flags. just if 0x67 crsactive config, system profiler recoginzed "SIP: disabled".
At high Sierra, the value 0x67 does not seem to be a big problem. because The 0x67 value contains the flags we need most.
as result, i think that useful values is 0x3FF to avoid any situation in future

Share this post


Link to post
Share on other sites

 

i tested all. in script, some parts shown wrong info that you mentioned
0x3FF
all flags are disabled. just shown System Integrity Protection status: enabled on system profile, actually disabled all csr flags, script also shown enabled with "Custom Configuration"
 
0x3e7
except CSR_ALLOW_KERNEL_DEBUGGER, CSR_ALLOW_APPLE_INTERNAL, all flags are disabled.
 
i don't exactly know role of each flags. just if 0x67 crsactive config, system profiler recoginzed "SIP: disabled".
At high Sierra, the value 0x67 does not seem to be a big problem. because The 0x67 value contains the flags we need most.
as result, i think that useful values is 0x3FF to avoid any situation in future

 

ThanKs. I will follow your advice

Share this post


Link to post
Share on other sites

 

Please, niknod could teach me how to disable the Nvidia card through SSDT. You could send me your patched SSDT. As you know I had the same problem as you with MacOS High Sierra update beta 8 (WindowServer)
 
Thank you
 
P.D.:
 
I extend my request to any other member who can help me
 
 
 

 

ok Wellcome here my 3 ssdts that did the trick.but don't think they will for you as different laptop good luck!

Wellcome.zip

Share this post


Link to post
Share on other sites

Anyone noticing slow boot speeds? My Computer has Sierra on a ssd and High Sierra on a Samsung 960 NVMe m.2 and booting the Sierra drive I get to the login in about 8 seconds. The High Sierra boot process takes almost 30 seconds to get to the login screen. I thought by now that High Sierra  (using DP9) that my boot time would be at least equal to or faster than the Sierra ssd. I get reads of 3000mb/s on the High Sierra drive vs 460mb/s on Sierra drive. 

Share this post


Link to post
Share on other sites

ok Wellcome here my 3 ssdts that did the trick.but don't think they will for you as different laptop good luck!

Ok.Thank you.I'll try to do the complete procedure that is more complicated and you will report

regards

Share this post


Link to post
Share on other sites

 

i tested all. in script, some parts shown wrong info that you mentioned
0x3FF
all flags are disabled. just shown System Integrity Protection status: enabled on system profile, actually disabled all csr flags, script also shown enabled with "Custom Configuration"
 
0x3e7
except CSR_ALLOW_KERNEL_DEBUGGER, CSR_ALLOW_APPLE_INTERNAL, all flags are disabled.
 
i don't exactly know role of each flags. just if 0x67 crsactive config, system profiler recoginzed "SIP: disabled".
At high Sierra, the value 0x67 does not seem to be a big problem. because The 0x67 value contains the flags we need most.
as result, i think that useful values is 0x3FF to avoid any situation in future

 

from PMheart reply

Share this post


Link to post
Share on other sites

Anyone noticing slow boot speeds? My Computer has Sierra on a ssd and High Sierra on a Samsung 960 NVMe m.2 and booting the Sierra drive I get to the login in about 8 seconds. The High Sierra boot process takes almost 30 seconds to get to the login screen. I thought by now that High Sierra  (using DP9) that my boot time would be at least equal to or faster than the Sierra ssd. I get reads of 3000mb/s on the High Sierra drive vs 460mb/s on Sierra drive. 

 

 

Update DP9 succeed  :)  As Beta 7, Beta 8, Beta 9 not allowed Hot-swap (Hot-Plug) internal hard drive on my system.

Nobody has an answer, a tip, a suggestion for these problems, which are also my problems?

Thanks in advance.

Share this post


Link to post
Share on other sites

interesting hot plug works for me beta 9

Share this post


Link to post
Share on other sites

okay. good script. i don't know crsutil detail. i just checked system profiler's difference on each crsutil value.

i will check more

0x67 result

Shanes-iMac:~ shane$ /Users/shane/Downloads/csrstat 
System Integrity Protection status: disabled.
 
Configuration: (0x00000067)
Apple Internal...........: disabled
Kext Signing Restrictions: disabled
Task for PID Restrictions: disabled
Filesystem Protections...: disabled
Debugging Restrictions...: enabled
DTrace Restrictions......: disabled
NVRAM Protections........: disabled
Device Configuration.....: enabled
BaseSystem Verification..: enabled
Shanes-iMac:~ shane$ 

Share this post


Link to post
Share on other sites

Nobody has an answer, a tip, a suggestion for these problems, which are also my problems?

Thanks in advance.

 

I found no solutions for this problem. Despite search and search on several forum.

 

Sorry for my bad english

interesting hot plug works for me beta 9

 

Can you share your EFI folder, Bios settings? I see you have an Ozmosis Bios patched, mine is not.

 

Thanks

 

Sorry for my bad english

Share this post


Link to post
Share on other sites

Wellcome

 NVOP   5b810e50 43415003 0040084c 43544c10141f5f49 4e490070 005c2f05 5f53425f50434930 52503035 50585358 5f41445214400d ----> 5b810e50 43415003 0040084c 43544c1014235f49 4e490070 005c2f05 5f53425f50434930 52503035 50585358 5f4144525f4f4646 14400d

Disable nvidia
I do not speak English
Edited by Allan
Translated

Share this post


Link to post
Share on other sites

Matgen84 there is no ozmosis support on this mobo as its a 100 series board. x99/100/200 have no support so i am using clover on this rig. i have hot plug enabled on my sata 4 port in bios for hot plug

Share this post


Link to post
Share on other sites

Matgen84 there is no ozmosis support on this mobo as its a 100 series board. x99/100/200 have no support so i am using clover on this rig. i have hot plug enabled on my sata 4 port in bios for hot plug

 

Sorry for my mistake: I've read Osmozis in your "interest" under your avatar. Like you, I have hot plug enabled on my 6 sata port in Bios. Hot Plug work like a charm under Sierra and under High Sierra up to Developer Beta 6. Since Beta 7, don't work as I say before. 

Share this post


Link to post
Share on other sites

 

i saw. also i calculated each parts. what she said is right.

crsactiveconfig is as users prefer. some users want to disable all flags, other users don't want to disable all flags.

 

at least crsactiveconfig 0x67 or over, no problem. i now used 0x67. In my case, do not need to disable all flags.

Share this post


Link to post
Share on other sites

fusion71au, on 30 Aug 2017 - 12:51 AM, said:

snapback.png

 

Thank. I try but don't work...

 

Edit: Asmedia1061-Asmedia1062 with with AHCIPortInjector.kext. Since beta 7 and of course with Beta 8, I can no longer use the hot-plugging of internal hard drives. I can't insert HDD when High Sierra is running. Does anyone even have same problem? Hot-pluggging HDD work like a charm under Sierra.

 

 

According to kextstat, the kexts loading on my system related to AHCI are

fusion71aus-iMac:~ fusion71au$ kextstat | grep AHCI
   64    3 0xffffff7f81f3f000 0x1a000    0x1a000    com.apple.iokit.IOAHCIFamily (288) F3AC999A-975D-3D01-82D4-8ACCB4A885B1 <5 4 3 1>
   65    0 0xffffff7f82b6b000 0x14000    0x14000    com.apple.driver.AppleAHCIPort (328) 440D7F9B-DE37-375D-AFE0-EABC372B001E <64 12 5 4 3 1>
   78    0 0xffffff7f81f69000 0x27000    0x27000    com.apple.iokit.IOAHCIBlockStorage (301.1.2) 81611BFF-AE58-3937-A337-1731E734B3C2 <64 27 6 5 4 3 1>
   85    0 0xffffff7f81f5c000 0xd000     0xd000     com.apple.iokit.IOAHCISerialATAPI (267) BA23AC56-7AB4-3898-A468-B18B1550E039 <64 28 5 4 3 1>
 
Maybe try downgrading both AppleAHCIPort and IOAHCIFamily kexts to versions before DB7 (after making backups of current kexts).  Attached are AHCI kexts from High Sierra PB1_17A291m.  Note IOAHCIBlockStorage and IOAHCISerialATAPI are Plugin kexts inside IOAHCIFamily.kext.  
 
Don't forget to set correct kext permissions and rebuild caches (sudo touch /System/Library/Extensions && sudo kextcache -u /).  Can check kexts are loadable with kextutil -tn command eg
fusion71aus-iMac:~ fusion71au$ sudo kextutil -tn /System/Library/Extensions/AppleAHCIPort.kext
Password:
/System/Library/Extensions/AppleAHCIPort.kext appears to be loadable (including linkage for on-disk libraries).
 
Good Luck!

AHCI kexts from PB1_17A291m.zip

Share this post


Link to post
Share on other sites

 

According to kextstat, the kexts loading on my system related to AHCI are

fusion71aus-iMac:~ fusion71au$ kextstat | grep AHCI
   64    3 0xffffff7f81f3f000 0x1a000    0x1a000    com.apple.iokit.IOAHCIFamily (288) F3AC999A-975D-3D01-82D4-8ACCB4A885B1 <5 4 3 1>
   65    0 0xffffff7f82b6b000 0x14000    0x14000    com.apple.driver.AppleAHCIPort (328) 440D7F9B-DE37-375D-AFE0-EABC372B001E <64 12 5 4 3 1>
   78    0 0xffffff7f81f69000 0x27000    0x27000    com.apple.iokit.IOAHCIBlockStorage (301.1.2) 81611BFF-AE58-3937-A337-1731E734B3C2 <64 27 6 5 4 3 1>
   85    0 0xffffff7f81f5c000 0xd000     0xd000     com.apple.iokit.IOAHCISerialATAPI (267) BA23AC56-7AB4-3898-A468-B18B1550E039 <64 28 5 4 3 1>
 
Maybe try downgrading both AppleAHCIPort and IOAHCIFamily kexts to versions before DB7 (after making backups of current kexts).  Attached are AHCI kexts from High Sierra PB1_17A291m.  Note IOAHCIBlockStorage and IOAHCISerialATAPI are Plugin kexts inside IOAHCIFamily.kext.  
 
Don't forget to set correct kext permissions and rebuild caches (sudo touch /System/Library/Extensions && sudo kextcache -u /).  Can check kexts are loadable with kextutil -tn command eg
fusion71aus-iMac:~ fusion71au$ sudo kextutil -tn /System/Library/Extensions/AppleAHCIPort.kext
Password:
/System/Library/Extensions/AppleAHCIPort.kext appears to be loadable (including linkage for on-disk libraries).
 
Good Luck!

 

 

Thanks. I try this.

 

I've forgotten:  I use under Sierra and High Sierra, AHCIPortInjector.kext (Fabio version 2016) in EFI/CLOVER/KEXT and I can Hot-Plugging. It does the job now only in Sierra.

 

 

Update: with only AppleAHCIPort version 328 instead of version 329 in S/L/E and AHCIPortInjector.kext (Fabio version 2016) in EFI/CLOVER/KEXT Hot-Plug work again under High Sierra.

 

I don't know why? these two versions, both of which date back to 2016, appear to be identical. Should I do the same manipulation for the release?

Share this post


Link to post
Share on other sites

Just an experience: I reverted back to HFS+ because Clover lost track of my APFS partion for two times now: once boot error, the other time the drive simply didn't show up. Both times out of nowhere, just after a regular shutdown. I had to reinstall DP9-update each time to get Clover recognize the drive again, using different apfs.efi's didn't make any difference. So I stay on HFS+ until the new file system proves itself reliable within the next months. 

Share this post


Link to post
Share on other sites

 

According to kextstat, the kexts loading on my system related to AHCI are

fusion71aus-iMac:~ fusion71au$ kextstat | grep AHCI
   64    3 0xffffff7f81f3f000 0x1a000    0x1a000    com.apple.iokit.IOAHCIFamily (288) F3AC999A-975D-3D01-82D4-8ACCB4A885B1 <5 4 3 1>
   65    0 0xffffff7f82b6b000 0x14000    0x14000    com.apple.driver.AppleAHCIPort (328) 440D7F9B-DE37-375D-AFE0-EABC372B001E <64 12 5 4 3 1>
   78    0 0xffffff7f81f69000 0x27000    0x27000    com.apple.iokit.IOAHCIBlockStorage (301.1.2) 81611BFF-AE58-3937-A337-1731E734B3C2 <64 27 6 5 4 3 1>
   85    0 0xffffff7f81f5c000 0xd000     0xd000     com.apple.iokit.IOAHCISerialATAPI (267) BA23AC56-7AB4-3898-A468-B18B1550E039 <64 28 5 4 3 1>
 
Maybe try downgrading both AppleAHCIPort and IOAHCIFamily kexts to versions before DB7 (after making backups of current kexts).  Attached are AHCI kexts from High Sierra PB1_17A291m.  Note IOAHCIBlockStorage and IOAHCISerialATAPI are Plugin kexts inside IOAHCIFamily.kext.  
 
Don't forget to set correct kext permissions and rebuild caches (sudo touch /System/Library/Extensions && sudo kextcache -u /).  Can check kexts are loadable with kextutil -tn command eg
fusion71aus-iMac:~ fusion71au$ sudo kextutil -tn /System/Library/Extensions/AppleAHCIPort.kext
Password:
/System/Library/Extensions/AppleAHCIPort.kext appears to be loadable (including linkage for on-disk libraries).
 
Good Luck!

 

 

Thanks first of all to the suggestion.
The hot plug now works; but trim activation no longer works.
???

 

Thanks first of all to the suggestion.
The hot plug now works; but trim activation no longer works.
???

 

 

AppleDataSetManagement.kext

  Dependency Resolution Failures:

  Kexts already loaded for these libraries have no OSBundleCompatibleVersion: com.apple.iokit.IOAHCIBlockStorage

Share this post


Link to post
Share on other sites

Update: with only AppleAHCIPort version 328 instead of version 329 in S/L/E and AHCIPortInjector.kext (Fabio version 2016) in EFI/CLOVER/KEXT Hot-Plug work again under High Sierra.

 

I don't know why? these two versions, both of which date back to 2016, appear to be identical. Should I do the same manipulation for the release?

 

When you compare the MD5 values of the binaries inside AppleAHCIPort kexts v328 vs v329, you will find that they are different...

 

post-846696-0-67621900-1504646291_thumb.png

 

 

We will have to wait for the final release before knowing if regressing the kext still works  :).  It seems v329 is still buggy on quite a few older hardwares eg

 

 

Thanks first of all to the suggestion.
The hot plug now works; but trim activation no longer works.

 

 

  1. Downgrade only AppleAHCIPort v329 to v328 (restore original IOAHCIFamily with IOAHCIBlockStorage kext in /S/L/E, repair permissions & rebuild kext cache etc)
  2. Enable Trim with Clover KextsToPatch....

 

 

 

		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>TRIM Enabler</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				AEFQUExFIFNTRAA=
				</data>
				<key>Name</key>
				<string>IOAHCIBlockStorage</string>
				<key>Replace</key>
				<data>
				AAAAAAAAAAAAAAA=
				</data>
			</dict>

post-846696-0-69216800-1504647204_thumb.png

 

 

 

Share this post


Link to post
Share on other sites

When you compare the MD5 values of the binaries inside AppleAHCIPort kexts v328 vs v329, you will find that they are different...

 

 

 

We will have to wait for the final release before knowing if regressing the kext still works  :).  It seems v329 is still buggy on quite a few older hardwares eg

 

 

 

  1. Downgrade only AppleAHCIPort v329 to v328 (restore original IOAHCIFamily with IOAHCIBlockStorage kext in /S/L/E, repair permissions & rebuild kext cache etc)
  2. Enable Trim with Clover KextsToPatch....

 

 

 

		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>TRIM Enabler</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				AEFQUExFIFNTRAA=
				</data>
				<key>Name</key>
				<string>IOAHCIBlockStorage</string>
				<key>Replace</key>
				<data>
				AAAAAAAAAAAAAAA=
				</data>
			</dict>

attachicon.gifTrim with Clover Kexts to Patch.png

 

 

 

Thanks @Fusion71au

 

Wait and see the final release.  :)

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • By chris1111
      Here my theme of OC 
       
      ### Dark version Selector Low

      Resources-Dark-S-Low.zip
       
      ### Dark version Selector Top

      Resources-Dark-S-Top.zip
       
      ### Dark version Selector GreenLight

      Resources-Dark-S-Green-Light.zip
       
      ### Light version Selector Low

      Resources-Light-S-Low.zip
       
      ### Light version Selector Top

      Resources-Light-S-Top.zip
       
       
      ### OC-Grey

      OC-Grey.zip
       
      ### OC-Blue

      OC-Blue.zip
       
      ### OC-White

      OC-White.zip
       
      ### OC-Blues

      OC-Blues.zip
    • By jrbros1
      Hi there,
       
      So I have my Windows computer, used a USB with Clover setup to boot into Mojave OS that I installed on the SD card in the computer. The world was a great place and all was well!

      Then I did the steps to partition the pc system to now include the additional drive that I would put Clover on. Here's where I messed up: Instead of directly copying over the full Clover folder into the EFI folder of the new drive (which just had the Boot & Microsoft folders in it), I replaced the EFI's boot folder with Clover's boot folder. So the EFI folder now contains a Microsoft folder, a Clover folder, and Clover's Boot folder only.

      Now, I only can access the Clover boot up menu, the macOS, but no Windows at all. Even if I go into BIOS and pick Windows Boot Manager or Partition 1 for the start up, I get a black screen for both. I can still access the macOS as well as Shell, but I don't know what that does other than displaying all of the yellow text fly by..

      Is there a kind soul out there that can help me get Windows back to boot? Keep in mind I'm a bit of a newbie here so laying out the common-sense steps would be helpful!

      Thank you in advance!
    • By EmriBG
      Hello everyone,
      I found a guide on how to install Catalina on Lenovo M920q, everything works well but the installation is freezing up.
      The USB bootable drive is a recovery one with internet based installation. The internet is working well on the pre-installation setup (I tested it, when you can use the utilities).
      The installation is freezing whether I am installing the macOS or not.
      I've attached my EFI partition so you can check if there's anything to add.
      Will realy appreciate any kind of help (quit noob to the whole thing).
      Thanks in advance and stay safe!
       
      NOTE: I did followed up the troubleshooting guide of OpenCore installation forum and the answer was to add the  NullCPUPowerManagement.kext to the kexts and configure it on the .plist file.
      This is the original EFI folder: EFI.zip
      Thats the one with the NullCPUPowerManagement.kext added: EFI.zip
       
       
       
       
    • By PropoFlexWX4
      This new case will be arriving for me tomorrow.
       
      It's the model M25-W White Version.
       
       
      It has an integrated 7.1 sound card.
      Which means the machine will effectively have 2 sound cards...
       
      Unfortunately I couldn't find any info on the card's model.  
       
      Does anyone have experience with Hackintoshing on non-standard audio configurations like this?
       
       
    • By fusion71au
      Making a High Sierra USB Installer Entirely From Scratch in Windows
      This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ).  @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet...
       

      Pre-Requisites
      8GB or larger USB drive.  Edit: Recommend 16GB or larger for macOS Catalina 10.16 Boot Disk Utility v2.1.2017rev021b from @CVAD TransMac (free 15 day trial) Paragon Hard Disk Manager Free Download Installer Files Directly from Apple
      1)  Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist (Hint - search page for "InstallESD" to find its URL and others nearby)

      to a folder named "SharedSupport" on your Windows NTFS drive.  A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...

      2)  Rename InstallESDDmg.pkg to InstallESD.dmg
      3)  Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)...
      Note:  You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.
      Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition
      1.  Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition
      2.  Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder
      3.  Restore 4.hfs to USB second partition with BDU --->  2nd partition becomes bootable "OS X Base System"
      Paragon Hard Disk Manager to extend HFS Partition to its Full Extent
      Open Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed.  Don't forget to apply the changes at the end...
      Transmac to Copy "SharedSupport" folder to OS X Base System
      1.  Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder.  Right click anywhere in the empty space on the RHS pane and select "Copy Here"...
      2.  In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"...
       
      Clover Settings
      Clover configuration is required now.  The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky.  If not, the hackintosh-vanilla-desktop-guide has some good explanations on the various settings available and also offers sample configuration files based on CPU type.  Also, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad.
      The location of the important configuration files for Clover are summarized below
      config.plist--->EFI/CLOVER folder DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist) Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here.  You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work. If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI. If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware).  In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine.  Reboot the system to the USB installer to install High Sierra ...
      What happens if we don't have access to TransMac or Paragon Hard Disk Manager?
      Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app.  In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)...
      -bash-3.2# cd / -bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/ -bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/  
      ...then start installation with the startosinstall utility...
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app  
      The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume.  Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)...
      cd "/Volumes/Macintosh HD" chmod +x startosinstall.command ./startosinstall.command Updated Download Links for macOS Mojave 10.14.6_18G103
      Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      Note: In Mojave, Apple has removed the --converttoapfs NO and --applicationpath arguments from the startosinstall utility....
       
      eg to use startosinstall for the above section "What happens if we don't have access to TransMac or Paragon Hard Disk Manager?", the syntax is now
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD  
      This basically means that for Mojave, the default installation will always convert the target volume to the apfs file system.
       
      Updated Download Links for macOS Catalina 10.15.6_19G73
      Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      startosinstall.command.zip
      InstallInfo.plist_edited_10.13.6.zip
      InstallInfo.plist_edited_10.14.6.zip
      InstallInfo.plist_edited_10.15.6.zip
×