Jump to content
fusion71au

Making a bootable High Sierra USB Installer Entirely From Scratch in Windows or Linux Mint (without access to Mac or App Store Installer.app)

34 posts in this topic

Recommended Posts

Advertisement

Making a High Sierra USB Installer Entirely From Scratch in Linux Mint

Prerequisites

  1. 8GB or larger USB drive
  2. Linux Mint (virtualized is also OK, tested with Mint 17.3 & 18.1) and the following installed packages:  hfsplus, hfsprogs, gparted, gdisk, p7zip and dmg2img...
 

post-846696-0-68450600-1511427218_thumb.png

Download Installer Files Directly from Apple and Clover from SourceForge 
1)  Open terminal, create SharedSupport folder in ~/Downloads

mkdir ~/Downloads/SharedSupport

2)  Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...

  1. BaseSystem.dmg
  2. BaseSystem.chunklist
  3. InstallInfo.plist
  4. InstallESDDmg.pkg
  5. AppleDiagnostics.dmg
  6. AppleDiagnostics.chunklist

(Hint - search page for "InstallESD" to find its URL and others nearby)
 into ~/Downloads/SharedSupport.  A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...
 3) Rename InstallESDDmg.pkg to InstallESD.dmg

mv ~/Downloads/SharedSupport/InstallESDDmg.pkg ~/Downloads/SharedSupport/InstallESD.dmg

4)  Edit InstallInfo.plist with a 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 post#1)...

post-846696-0-14287300-1511472961_thumb.png

post-846696-0-64042000-1511427524_thumb.png

Note:  You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.

5)  If you don't already have Clover installed, download the latest Clover.iso from SourceForge.  Extract the EFI folder to ~/Downloads...

 

 

post-846696-0-89018000-1511427846_thumb.png

post-846696-0-74647300-1511427861_thumb.png

post-846696-0-29546900-1511427875_thumb.png

post-846696-0-58876200-1511427891_thumb.png

 

6)  Determine the size of the "OS X Base System" HFS partition by listing contents of BaseSystem.dmg with 7z l command.  Here, 4.hfs=2008506368 bytes=1915.5 MB (1024x1024 bytes per MB) or 3922864 sectors (512 bytes per sector)...

 

 

 

fusion71au@fusion71au-VirtualBox ~ $ 7z l ~/Downloads/SharedSupport/BaseSystem.dmg

7-Zip [64] 9.20  Copyright © 1999-2010 Igor Pavlov  2010-11-18
p7zip Version 9.20 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,1 CPU)

Listing archive: ~/Downloads/SharedSupport/BaseSystem.dmg

--
Path = ~/Downloads/SharedSupport/BaseSystem.dmg
Type = Dmg
Method = copy[16]-13636K zero2[202]-593M zlib[503]-1436M-455M
Blocks = 721

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
                    .....          512           30  0.MBR
                    .....          512           75  1.Primary GPT Header
                    .....        16384          116  2.Primary GPT Table
                    .....         3072            0  3.free
                    .....   2008506368    491582140  4.hfs
                    .....    134221312            0  5.free
                    .....        16384          116  6.Backup GPT Table
                    .....          512           76  7.Backup GPT Header
------------------- ----- ------------ ------------  ------------------------
                            2142765056    491582553  8 files, 0 folders

 

Prepare USB with GParted and Restore OS X Base System with dmg2img
 1)  Open GParted.  In this example, I have an 8GB installer disk, /dev/sdb, initialized as GPT from Device Menu... 

 

 

post-846696-0-58757000-1511427995_thumb.png

post-846696-0-20950400-1511428025_thumb.png

 

2)  Create the following 2 new partitions 
Part 1 200MB FAT32 labelled EFI
Part 2 5817MB HFS+ labelled Installer_App
Leave 2174MB free for OS X Base System restore (=1916+129+129 MB of loader space before and after to keep Apple's Disk Utility happy)

 

 

post-846696-0-34917400-1511428083_thumb.png

post-846696-0-05940600-1511428101_thumb.png

post-846696-0-70312800-1511560664_thumb.png

post-846696-0-99292300-1511680514_thumb.png

 

3)  Use gdisk to set correct partition type, name and attributes for the EFI System Partition and create new sdb3 for OS X Base System...

 

 

fusion71au@fusion71au-VirtualBox ~ $ sudo gdisk /dev/sdb
[sudo] password for fusion71au:
GPT fdisk (gdisk) version 0.8.8

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): t
Partition number (1-3): 1
Current type is 'Microsoft basic data'
Hex code or GUID (L to show codes, Enter = 8300): EF00
Changed type of partition to 'EFI System'
 
Command (? for help): c
Partition number (1-3): 1
Enter name: EFI
 
Command (? for help): x
 
Expert command (? for help): a
Partition number (1-3): 1
Known attributes are:
0: system partition
1: hide from EFI
2: legacy BIOS bootable
60: read-only
62: hidden
63: do not automount
 
Attribute value is 0000000000000000. Set fields are:
  No fields set
 
Toggle which attribute field (0-63, 64 or <Enter> to exit): 0
Have enabled the 'system partition' attribute.
Attribute value is 0000000000000001. Set fields are:
0 (system partition)
 
Toggle which attribute field (0-63, 64 or <Enter> to exit):  
 
Expert command (? for help): m

Command (? for help): n
Partition number (3-128, default 3): 3
First sector (34-16777182, default = 12324864) or {+-}size{KMGTP}: +129M <--- For Disk Utility loader space
Last sector (12589056-16777182, default = 16777182) or {+-}size{KMGTP}: 16511920 <--- Equals 12589056+3922864 sectors for Base System
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): AF00
Changed type of partition to 'Apple HFS/HFS+'

Command (? for help): p
Disk /dev/sdb: 16777216 sectors, 8.0 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 10D5C66B-C765-5247-9DF4-358C0FEB2208
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 16777182
Partitions will be aligned on 2048-sector boundaries
Total free space is 531468 sectors (259.5 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          411647   200.0 MiB   EF00  
   2          411648        12324863   5.7 GiB     AF00  
   3        12589056        16511920   1.9 GiB     AF00  Apple HFS/HFS+

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.

 

4)  Open Terminal, type lsblk to show the system's attached disks, partitions and their mount points...

 

 


fusion71au@fusion71au-VirtualBox ~ $ lsblk
 
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0    50G  0 disk  
├─sda1   8:1    0   200M  0 part  
├─sda2   8:2    0   350M  0 part /boot
├─sda3   8:3    0    15G  0 part /
├─sda4   8:4    0  32.5G  0 part /home
└─sda5   8:5    0     2G  0 part [SWAP]
sdb      8:16   0     8G  0 disk  
├─sdb1   8:17   0   200M  0 part   
├─sdb2   8:18   0   5.7G  0 part
├─sdb3   8:19   0   1.9G  0 part
sr0     11:0    1  1024M  0 rom   

 

5)  Change directory to access the SharedSupport files in ~/Downloads

cd ~/Downloads/SharedSupport

6)  Type dmg2img -l BaseSystem.dmg to list the "partitions" in the compressed disk image file "BaseSystem.dmg"...

 

 


fusion71au@fusion71au-VirtualBox ~/Downloads/SharedSupport $ dmg2img -l BaseSystem.dmg
 
dmg2img v1.6.5 (c) vu1tur (to@vu1tur.eu.org)
 
BaseSystem.dmg --> (partition list)
 
partition 0: Protective Master Boot Record (MBR : 0)
partition 1: GPT Header (Primary GPT Header : 1)
partition 2: GPT Partition Data (Primary GPT Table : 2)
partition 3:  (Apple_Free : 3)
partition 4: disk image (Apple_HFS : 4)
partition 5:  (Apple_Free : 5)
partition 6: GPT Partition Data (Backup GPT Table : 6)
partition 7: GPT Header (Backup GPT Header : 7)

 

7)  Use the command sudo dmg2img -v -i BaseSystem.dmg -p 4 -o /dev/sdb3 to write the 4.hfs image to your "OS X Base System" volume ie sdb3 partition.

 

 


fusion71au@fusion71au-VirtualBox ~/Downloads/SharedSupport $ sudo dmg2img -v -i BaseSystem.dmg -p 4 -o /dev/sdb3
[sudo] password for fusion71au:  
 
dmg2img v1.6.5 (c) vu1tur (to@vu1tur.eu.org)
 
BaseSystem.dmg --> /dev/sdb3
 
reading property list, 52391 bytes from address 491582553 ...
partition 0: begin=203, size=430, decoded=284
partition 1: begin=948, size=430, decoded=284
partition 2: begin=1695, size=430, decoded=284
partition 3: begin=2424, size=430, decoded=284
partition 4: begin=3137, size=42778, decoded=28804
partition 5: begin=46198, size=430, decoded=284
partition 6: begin=46926, size=430, decoded=284
partition 7: begin=47671, size=430, decoded=284
 
decompressing:
opening partition 4 ...       [715] 100.00%  ok
 
Archive successfully decompressed as /dev/sdb3
 
You should be able to mount the image [as root] by:
 
modprobe hfsplus
mount -t hfsplus -o loop /dev/sdb3 /mnt

 

8)  Create mounting folders in /media/your_username 

sudo mkdir /media/fusion71au/EFI
sudo mkdir /media/fusion71au/Installer_App  

9)  Mount the Installer_App volume (corresponding to sdb2) and copy the SharedSupport folder to its root ...

sudo mount /dev/sdb2 /media/fusion71au/Installer_App  
sudo cp -R ~/Downloads/SharedSupport /media/fusion71au/Installer_App/

 10)  Mount the EFI partition, sdb1, and copy the EFI folder containing Clover into it...

sudo mount /dev/sdb1 /media/fusion71au/EFI
sudo cp -R ~/Downloads/EFI /media/fusion71au/EFI/

Clover Settings

Clover configuration is required now.  The default config.plist (in the EFI partition, /EFI/Clover folder of the USB) maybe sufficient to boot your machine if you’re lucky.  If not, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with a text editor.

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.  You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work.
  • If legacy booting, you need to install legacy boot sectors on the drive (boot0af, boot1f32 and boot6).  There is an automated install for this here by @StarBrilliant
  • 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.

Hint:  For newbs, you don't necessarily need Clover to boot the installer in a VMware virtual machine.  Just attach the installer (without Clover) to a macOS guest running on a VMware Windows host (patched with @Donk's unlocker program - to create the VM guest, see my VMware guide).

Boot to OS X Base System, build "Install macOS High Sierra.app" then startosinstall in Terminal

1)  Unmount sdb1 & sdb2,

 sudo umount /dev/sdb1
 sudo umount /dev/sdb2

then reboot your system to the USB Installer using the system's boot device selection key eg F12 for Gigabyte motherboards, F8 for ASUS motherboards, F11 for ASrock motherboards ...

 

post-846696-0-82338900-1511429981_thumb.png

2)  Launch Disk Utility from the macOS Utilities main screen and prepare the target hard disk to install High Sierra eg "Macintosh HD", erase/formatted as HFS+j.  Hint - click View Menu to Show All Devices...

 

 

post-846696-0-92478900-1512120265_thumb.png

post-846696-0-33292400-1512120286_thumb.png

post-846696-0-90999200-1512120301_thumb.png

 

3)  Launch terminal from the macOS Utilities main screen, Utilities Menu...

 

post-846696-0-57863800-1512423901_thumb.png

4)  Type the following commands to assemble the full "Install macOS High Sierra.app" on the Installer_App volume...

-bash-3.2# cd /
-bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Installer_App/
-bash-3.2# mv /Volumes/Installer_App/SharedSupport /Volumes/Installer_App/Install\ macOS\ High\ Sierra.app/Contents/

Terminal Hints:

  • Type the first few characters of a path, then press <Tab> key ---> rest of the path will autocomplete.
  • Pressing the <up> arrow key will duplicate the previous command entered into terminal.

5)  Start installation with the startosinstall utility in Terminal...

-bash-3.2# /Volumes/Installer_App/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Installer_App/Install\ macOS\ High\ Sierra.app

where "Macintosh HD" is the target volume to install High Sierra in this example...

 

post-846696-0-92831600-1511471083_thumb.png

Steps 4 and 5 can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on the "Installer_App" partition of the USB and launch the startosinstall utility targeting the "Macintosh HD" volume.  Copy/download to Installer_App volume, then run in terminal...

cd /Volumes/Installer_App
chmod +x startosinstall.command
./startosinstall.command

startosinstall.command.zip

Edited by fusion71au
update download links for 10.13.6

Share this post


Link to post
Share on other sites

 

 

Making a High Sierra USB Installer Entirely From Scratch in Linux Mint

 

Prerequisites

  1. 8GB or larger USB drive
  2. Linux Mint (virtualized is also OK, tested with Mint 17.3 & 18.1) and the following installed packages:  hfsplus, hfsprogs, gparted, gdisk and dmg2img...

 

 

 

 

Download Installer Files Directly from Apple and Clover from SourceForge
 
1)  Open terminal, create SharedSupport folder in ~/Downloads

mkdir ~/Downloads/SharedSupport

 
2)  Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...

  1. BaseSystem.dmg
  2. BaseSystem.chunklist
  3. InstallInfo.plist
  4. InstallESDDmg.pkg
  5. AppleDiagnostics.dmg
  6. AppleDiagnostics.chunklist

(Hint - search page for "InstallESD" to find its URL and others nearby)
 
into ~/Downloads/SharedSupport.  A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...
 
3) Rename InstallESDDmg.pkg to InstallESD.dmg

mv ~/Downloads/SharedSupport/InstallESDDmg.pkg ~/Downloads/SharedSupport/InstallESD.dmg

4)  Edit InstallInfo.plist with a 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 post#1)...

 

attachicon.gifEdit InstallInfo.plist.png

5)  If you don't already have Clover installed, download the latest Clover.iso from SourceForge.  Extract the EFI folder to ~/Downloads...
 

 

 

 

 

 

Prepare USB with GParted and Restore OS X Base System with dmg2img
 
1)  Open GParted.  In this example, I have a 8GB installer disk, initialized as GPT from Device Menu... 

 

 

 

2)  Create the following 3 new partitions
 
Part 1 200MB FAT32 labelled EFI
Part 2 5812MB HFS+ labelled Installer_App
Part 3 1921MB HFS+ labelled "OS X Base System" should have 129MB free "loader" space before and after it so Apple's Disk Utility is happy...

 

 

 

3)  Use gdisk to set correct partition type, name and attributes for the EFI System Partition ...

 

 

 

fusion71au@fusion71au-VirtualBox ~ $ sudo gdisk /dev/sdb
GPT fdisk (gdisk) version 0.8.8
 
Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present
 
Found valid GPT with protective MBR; using GPT.
 
Command (? for help): v
 
No problems found. 266173 free sectors (130.0 MiB) available in 2
segments, the largest of which is 264159 (129.0 MiB) in size.
 
Command (? for help): t
Partition number (1-3): 1
Current type is 'Microsoft basic data'
Hex code or GUID (L to show codes, Enter = 8300): EF00
Changed type of partition to 'EFI System'
 
Command (? for help): c
Partition number (1-3): 1
Enter name: EFI
 
Command (? for help): x
 
Expert command (? for help): a
Partition number (1-3): 1
Known attributes are:
0: system partition
1: hide from EFI
2: legacy BIOS bootable
60: read-only
62: hidden
63: do not automount
 
Attribute value is 0000000000000000. Set fields are:
  No fields set
 
Toggle which attribute field (0-63, 64 or <Enter> to exit): 0
Have enabled the 'system partition' attribute.
Attribute value is 0000000000000001. Set fields are:
0 (system partition)
 
Toggle which attribute field (0-63, 64 or <Enter> to exit):  
 
Expert command (? for help): m
 
Command (? for help): p
Disk /dev/sdb: 16777216 sectors, 8.0 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): ED6532BB-14E1-4E3C-92FF-14E1C5F1B0A8
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 16777182
Partitions will be aligned on 2048-sector boundaries
Total free space is 266173 sectors (130.0 MiB)
 
Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          411647   200.0 MiB   EF00  EFI
   2          411648        12578815   5.8 GiB     AF00   
   3        12578816        16513023   1.9 GiB     AF00   
 
Command (? for help): w
 
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
 
Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.

 

 

 

4)  Open Terminal, type lsblk to show the system's attached disks, partitions and their mount points...
 

 

fusion71au@fusion71au-VirtualBox ~ $ lsblk
 
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0    50G  0 disk  
├─sda1   8:1    0   200M  0 part  
├─sda2   8:2    0   350M  0 part /boot
├─sda3   8:3    0    15G  0 part /
├─sda4   8:4    0  32.5G  0 part /home
└─sda5   8:5    0     2G  0 part [SWAP]
sdb      8:16   0     8G  0 disk  
├─sdb1   8:17   0   200M  0 part   
├─sdb2   8:18   0   5.7G  0 part
├─sdb3   8:19   0   1.9G  0 part
sr0     11:0    1  1024M  0 rom   

 

 

5)  Change directory to access the SharedSupport files in ~/Downloads

cd ~/Downloads/SharedSupport

6)  Type dmg2img -l BaseSystem.dmg to list the "partitions" in the compressed disk image file "BaseSystem.dmg"...

 

 

fusion71au@fusion71au-VirtualBox ~/Downloads/SharedSupport $ dmg2img -l BaseSystem.dmg
 
dmg2img v1.6.5 (c) vu1tur (to@vu1tur.eu.org)
 
BaseSystem.dmg --> (partition list)
 
partition 0: Protective Master Boot Record (MBR : 0)
partition 1: GPT Header (Primary GPT Header : 1)
partition 2: GPT Partition Data (Primary GPT Table : 2)
partition 3:  (Apple_Free : 3)
partition 4: disk image (Apple_HFS : 4)
partition 5:  (Apple_Free : 5)
partition 6: GPT Partition Data (Backup GPT Table : 6)
partition 7: GPT Header (Backup GPT Header : 7)

 

 

7)  Use the command sudo dmg2img -v -i BaseSystem.dmg -p 4 -o /dev/sdb3 to write the 4.hfs image to your "OS X Base System" volume ie sdb3 partition.

 

 

 

fusion71au@fusion71au-VirtualBox ~/Downloads/SharedSupport $ sudo dmg2img -v -i BaseSystem.dmg -p 4 -o /dev/sdb3
[sudo] password for fusion71au:  
 
dmg2img v1.6.5 (c) vu1tur (to@vu1tur.eu.org)
 
BaseSystem.dmg --> /dev/sdb3
 
reading property list, 52391 bytes from address 491582553 ...
partition 0: begin=203, size=430, decoded=284
partition 1: begin=948, size=430, decoded=284
partition 2: begin=1695, size=430, decoded=284
partition 3: begin=2424, size=430, decoded=284
partition 4: begin=3137, size=42778, decoded=28804
partition 5: begin=46198, size=430, decoded=284
partition 6: begin=46926, size=430, decoded=284
partition 7: begin=47671, size=430, decoded=284
 
decompressing:
opening partition 4 ...       [715] 100.00%  ok
 
Archive successfully decompressed as /dev/sdb3
 
You should be able to mount the image [as root] by:
 
modprobe hfsplus
mount -t hfsplus -o loop /dev/sdb3 /mnt

 

 

8)  Create mounting folders in /media/your_username 

sudo mkdir /media/fusion71au/EFI
sudo mkdir /media/fusion71au/Installer_App  

9)  Mount the Installer_App volume (corresponding to sdb2) and copy the SharedSupport folder to its root ...

sudo mount /dev/sdb2 /media/fusion71au/Installer_App  
sudo cp -R ~/Downloads/SharedSupport /media/fusion71au/Installer_App/

 
10)  Mount the EFI partition, sdb1, and copy the EFI folder containing Clover into it...

sudo mount /dev/sdb1 /media/fusion71au/EFI
sudo cp -R ~/Downloads/EFI /media/fusion71au/EFI/

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, 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.  You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work.

 

 

 

Boot to OS X Base System, build "Install macOS High Sierra.app" then startosinstall in Terminal

 

1)  Unmount sdb1 & sdb2,

 sudo umount /dev/sdb1
 sudo umount /dev/sdb2

     then reboot your system....

 

 

2)  Launch terminal from macOS Utilities Menu

 

 

 

3)  Type the following commands to assemble the full "Install macOS High Sierra.app" on the Installer_App volume...

-bash-3.2# cd /
-bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Installer_App/
-bash-3.2# mv /Volumes/Installer_App/SharedSupport /Volumes/Installer_App/Install\ macOS\ High\ Sierra.app/Contents/

Terminal Hints:

  • Type the first few characters of a path, then press <Tab> key ---> rest of the path will autocomplete.
  • Pressing the <up> arrow key will duplicate the previous command entered into terminal.

 
4)  Start installation with the startosinstall utility...

-bash-3.2# /Volumes/Installer_App/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Installer_App/Install\ macOS\ High\ Sierra.app

where "Macintosh HD" is the target volume to install High Sierra in this example.
 
 

 

 

 

Interesting, thanks @fusion72au.. :)

Share this post


Link to post
Share on other sites

@ice_pdb,

 

Yes, its possible to create a GPT formatted installer disk with dmg2img for Windows, Win32 Disk Imager, Paragon Partition Manager and gdisk instead of MBR using @CVAD's Boot Disk Utility.

 

 

Procedure
1) Convert BaseSystem.dmg to BaseSystem.img with dmg2img.exe:
       In command prompt, type

dmg2img BaseSystem.dmg BaseSystem.img

post-846696-0-46272200-1511498323_thumb.png

 

 

2) Open BaseSystem.img in Win32 Disk Imager ---> write to USB drive

 

 

 

post-846696-0-21962000-1511498373_thumb.png

 

 

3) Launch Paragon PM and

  • move HFS+ OS X Base System volume to the right so 200MB free space created at the start of the drive
  • create new 200MB FAT32 partition at the start of the drive, labelled EFI
  • extend HFS+ OS X Base System volume to right (but leave approx 130MB free space at end)

 

 

post-846696-0-33760200-1511498477_thumb.png

post-846696-0-62595800-1511499192_thumb.png

post-846696-0-22740600-1511498504_thumb.png

post-846696-0-98770300-1511498525_thumb.png

 

 

 

4) Set correct name, type and partition attribute for EFI System Partition with gdisk in command prompt window.

 


H:\gdisk>gdisk64 7:   <--- This is the disk number given to the usb drive by the system.  Find out by opening "Disk Management".
GPT fdisk (gdisk) version 1.0.0

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): p
Disk 7:: 7827456 sectors, 3.7 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): ED6532BB-14E1-4E3C-92FF-14E1C5F1B0A8
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7827422
Partitions will be aligned on 2048-sector boundaries
Total free space is 272317 sectors (133.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          413695   201.0 MiB   0700  Basic data partition
   2          413696         7557119   3.4 GiB     AF00  disk image

Command (? for help): c
Partition number (1-2): 1
Enter name: EFI

Command (? for help): t
Partition number (1-2): 1
Current type is 'Microsoft basic data'
Hex code or GUID (L to show codes, Enter = 700): EF00
Changed type of partition to 'EFI System'

Command (? for help): x

Expert command (? for help): a
Partition number (1-2): 1
Known attributes are:
0: system partition
1: hide from EFI
2: legacy BIOS bootable
60: read-only
62: hidden
63: do not automount

Attribute value is 0000000000000000. Set fields are:
  No fields set

Toggle which attribute field (0-63, 64 or <Enter> to exit): 0
Have enabled the 'system partition' attribute.
Attribute value is 0000000000000001. Set fields are:
0 (system partition)

Toggle which attribute field (0-63, 64 or <Enter> to exit):

Expert command (? for help): p
Disk 7:: 7827456 sectors, 3.7 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): ED6532BB-14E1-4E3C-92FF-14E1C5F1B0A8
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7827422
Partitions will be aligned on 2048-sector boundaries
Total free space is 272317 sectors (133.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          413695   201.0 MiB   EF00  EFI
   2          413696         7557119   3.4 GiB     AF00  disk image

Expert command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to \\.\physicaldrive7.
Disk synchronization succeeded! The computer should now use the new
partition table.

Expert command (? for help): m

Command (? for help): q

 


 

Final result ...

post-846696-0-20349600-1511498895_thumb.png

5) Open TransMac to copy downloaded files in /SharedSupport folder from NTFS Windows drive to /Install macOS High Sierra.app/Contents on "OS X Base System" HFS volume

6) Install Clover in Windows - see guide here :).  

 

Post#1 is for UEFI systems  ---> only need to copy CLOVER folder into /EFI on the EFI System Partition + replace /EFI/BOOT/BOOTX64.efi with Clover's BOOTX64.efi.  

 

Post#3 for legacy BIOS systems ---> need to also install boot sectors (boot0af, boot1f32 in MBR/PBR with Bootice Program) and boot6 or boot7 in the root / of the EFI partition.

 

Note: the MBR installer made with @CVAD's Boot Disk Utility already has legacy boot sectors for Clover installed ---> should work with BOTH legacy and UEFI systems.

Share this post


Link to post
Share on other sites

 

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 :whistle:).  @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...

 

attachicon.gifApple SW Catalog URLs Pike's Universum.png

Pre-Requisites

  1. 8GB or larger USB drive
  2. Boot Disk Utility v2.1.2017rev021b from @CVAD
  3. TransMac (free 15 day trial)
  4. 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...

  1. BaseSystem.dmg
  2. BaseSystem.chunklist
  3. InstallInfo.plist
  4. InstallESDDmg.pkg
  5. AppleDiagnostics.dmg
  6. AppleDiagnostics.chunklist

(Hint - search page for "InstallESD" to find its URL and others nearby)

attachicon.gifApple SW Catalog Find InstallESD in browser.png

 

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...

 

attachicon.gifApple SW Catalog List of Download Manager Downloads.png

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)...

 

 

 

 

 

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, 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

 

I tried it and it all went well. I made a image from the usb and it successfully booted a virtual box vm. After Installer did copied files to the drive it went for a reboot. after that I booted it with clover, Installer showed up again to continue installation but suddenly showed this error:

macOS could not be installed on your computer

The path /System/Installation/Packages/OSInstall.mpkg appears to be missing or damaged.

Quit the installer to restart your computer and try again.

 

any idea what I should do?

Share this post


Link to post
Share on other sites
The path /System/Installation/Packages/OSInstall.mpkg appears to be missing or damaged.

Quit the installer to restart your computer and try again.

 

any idea what I should do?

 

First, verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.

 

Eg for "Install macOS High Sierra.app" 10.13.2_17C88, SHA1 in Terminal...

fusion71aus-iMac:~ fusion71au$ shasum /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/InstallESD.dmg 
49e336085247331ea6033ebd3598a827caa6596e  /Applications/Install macOS High Sierra.app/Contents/SharedSupport/InstallESD.dmg
fusion71aus-iMac:~ fusion71au$ shasum /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/BaseSystem.dmg 
209d6a382026115a30c79f0825aec1b7a4cdb2dd  /Applications/Install macOS High Sierra.app/Contents/SharedSupport/BaseSystem.dmg

The OSInstall.mpkg error can sometimes be due to "stale data" in /macOS Install Data (time stamp/IAEndDate in OSInstallAttr.plist too old).  Easiest to erase target drive and start again...

 

If using VirtualBox, follow instructions exactly as per post#75.

 

If using VMware, follow instructions as per post#41.

Share this post


Link to post
Share on other sites
On 4/13/2018 at 1:22 AM, justmex said:

there are a couple links for each file, are they the same files? thanks

One of them is the chunklist and the other is a dmg file so they are different. 

Share this post


Link to post
Share on other sites
21 hours ago, roon83 said:

One of them is the chunklist and the other is a dmg file so they are different. 

no, no, when you do a search on the xml to Apple's files there are two links for each of the sox files, are they redundancy links?

Share this post


Link to post
Share on other sites

Thank you so much for this great effort. My os stopped booting. So I have followed the steps as stated above. except the step below. All i want to do is use the installer created above to install my mac os. My question is Do i need to do the clover settings below? 2. I tried installing with all the steps above, so i attached the usb to my system and I was greeted with OS X Base System and EFI Boot... I choose egi boot... then clover came up ..it was trying to install , then my mac made 3 sounds continously, i gues it wasnt working ,lol) so i restarted the mac and I choose OS Xbase system...that also was installing suddenly it failed.

 

How do i install high sierra with all the steps I have done above... and do i need clover setting below. If i need it, how can i apply it, thanks

 

On 12/26/2017 at 6:57 AM, dindu5678 said:

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, 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.

 

Share this post


Link to post
Share on other sites

Comparing these two files from the Apple Catalog...

 

http://swcdn.apple.com/content/downloads/07/20/091-95774/awldiototubemmsbocipx0ic9lj2kcu0pt/InstallInfo.plist
http://swcdn.apple.com/content/downloads/29/03/091-94326/45lbgwa82gbgt7zbgeqlaurw2t9zxl8ku7/InstallInfo.plist

 

I noticed different version numbers: 10.13.6.0.0.1532145923 and 10.13.6.0.0.1530695593

 

Are they both release versions?

 

Share this post


Link to post
Share on other sites
14 hours ago, CrazyTeeka said:

Comparing these two files from the Apple Catalog...

 


http://swcdn.apple.com/content/downloads/07/20/091-95774/awldiototubemmsbocipx0ic9lj2kcu0pt/InstallInfo.plist

http://swcdn.apple.com/content/downloads/29/03/091-94326/45lbgwa82gbgt7zbgeqlaurw2t9zxl8ku7/InstallInfo.plist

 

I noticed different version numbers: 10.13.6.0.0.1532145923 and 10.13.6.0.0.1530695593

 

Are they both release versions?

 

 

Yes, both are release versions of High Sierra 10.13.6:

 

http://swcdn.apple.com/content/downloads/29/03/091-94326...---> corresponds to build 10.13.6.17G65

http://swcdn.apple.com/content/downloads/07/20/091-95774...---> corresponds to build 10.13.6.17G2208 (with latest security update).

 

Edited by fusion71au

Share this post


Link to post
Share on other sites
8 hours ago, Manash420 said:

@fusion71au How to identify the macOs version of baseSystem.dmg and  InstallESD.dmg from the apple catalogue?

 

Download, then open the corresponding English.dist file in a text editor.  

 

Eg BaseSystem.dmg and InstallESDDmg.pkg for Mojave Beta11_18A389 have the following URLs...

 

http://swcdn.apple.com/content/downloads/42/45/091-62771/dsx32mbizk8mo8nx84umbwp5iknyxpgyxc/BaseSystem.dmg

http://swcdn.apple.com/content/downloads/42/45/091-62771/dsx32mbizk8mo8nx84umbwp5iknyxpgyxc/InstallESDDmg.pkg

 

Corresponding English.dist file URL is

https://swdist.apple.com/content/downloads/42/45/091-62771/dsx32mbizk8mo8nx84umbwp5iknyxpgyxc/091-62771.English.dist

 

Opening this file in text editor shows this ...

 

English_dist.png.b5e0584855107650a2ed77b5ab32d095.png

Share this post


Link to post
Share on other sites

I know this thread is old, but is there any way to fix the frozen boot screen? When I boot from the usb, it shows a frozen clover boot utility screen and i cant move around to select anything. 

Share this post


Link to post
Share on other sites

The diversion was first reported by Rockstar Games on 25 October 2011.[55] They discharged its introduction trailer multi week later,[56] with an official public statement recognizing its setting.[57] Journalists noticed that the declaration  gta 6 mobile

Share this post


Link to post
Share on other sites

Tq for this nice guide. I want to create usb for el capitan 10.11.6. I try to search the catalog for el capitan 10.11.6 but i did not find the the link. Can u help me? Thank u

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Shogun
      Hi,

      I'm trying to get a clean install of High Sierra, but didn't manage to get too far... stuck on pre-installer with some errors.

      General flow that i've tried, following relevant guides and some success stories:
      1. Used [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] to create bootable usb drive.
      2. Tried to use different options, UEFI boot mode, Legacy boot mode, with and without Clover configuration...

      In legacy mode it restarts after last error, while in uefi it hangs on kextd stall...

      Screens with error and clover folder/config attached.

      Motherboard: ASUS P8P67 EVO
      CPU: i7 2600K (not overlocked)
      Graphics: Sapphire Pulse Radeon RX 580 8GB
      Memory: Kingston 16 GB (2x8gb) 1333MHz
      Storage: SSD Samsung 860 EVO 500GB + Samsung 860 EVO 1TB

      Are this components compatible with High Sierra? From what i see on other threads, people got it working somehow.
      Should i use Legacy boot mode as of advice from [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] or is possible to get it working with UEFI? Which one is better?

      How to get rid of "Unsupported CPU for reporter"?

      Any help would be highly appreciated. I'm desperate on wasting time to get it working. 

      Thanks!


      CLOVER.zip
      config.plist
    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By JackRabbitSlim
      Hi everyone,
      This is my first hackintosh. To be completely honest there's still a lot I'm trying to figure out... And considering I can't even get the installer to begin, seems like there's something I'm just not understanding. Any help would be greatly appreciated!!
       
      I've specced the machine based on a multiple successful builds I've seen in various vanilla forums.
      I've set the recommended BIOS, double-checked, but can't even get to an installer screen despite following a Vanilla guide from a popular hackintosh youtuber.
      (Not sure if her links can be mentioned, posted etc... Just playing it safe since this is my 1st post...)
       
       
       
      THE BUILD:

      Gigabyte Z390 Designare
      i9 9900k
      Sapphire Radeon RX580 Pulse - 8 GB
      G.Skill TridentZ 3200 - 64 GB
      Samsung EVO 840 (This is a scrap drive. Planned on using it to get the build running first, then cloning my MP 5,1 HS image after.)
      Other Stuff: Bluetooth, USB, iGPU, etc not important yet... Current goal is just to get the machine booting... I'll focus on WIFI/BT etc after...
       
      I've tried multiple SMBIOS profiles, (listed below). All of them prevent me from even booting the installer with the message below.
      At this point I'm wondering if the issue is HS related, or if there's a step that, although obvious to some, isn't obvious to me and overlooking somehow.
       
      Message returned when attempting to boot the installer. (Pic attached):
       
      This version of Mac OS X is not supported on this platform!
      Reason: Mac-AA95B1DDAB278B95
       
      I also get an error when I click update in Clover saying: Package is incompatible with this version of OS X and may fail to install
      ^ Seems like this indicates I've missed a step or done something wrong?
       
      Here's a list of the complete steps I've taken so far:
       
      Double-checked BIOS settings according to each build.
      Built a vanilla installer based on the video I mentioned above, steps listed below... (I've done this twice now, confirming I followed the steps in the guide.)
       
      Vanilla Installer Steps:
      Wiped and formatted my thumb drive with GUID Partition, HFS Extended (Journaled) Used terminal to create a bootable installer from a 10.13.6 installer I downloaded last june/july. Installed Clover Bootloader onto the Install macOS High Sierra partition of the thumb drive, and ticked: Clover for UEFI booting only, Install Clover into the ESP, VBox HFS-64, APFSDriverLoader-64, AptioMemoryFix-64 (leaving everything else unticked.)  
      Clover Configurator Steps:
      Mounted the Thumb Drive's EFI folder, opened C.C. and "downloaded" Lilu, WhateverGreen, & FakeSMC to the Other folder, & installed sensors. Deleted the default plist and manually created one using the Coffee Lake 'sample plist' from r/Vanilla Hackintosh Desktop Guide. Copy plist to the mounted EFI folder.  
      Open the plist with CC and did the following:
      Confirmed the following flags were set in CC's Boot section - Verbose (-v), dart=0, debug=0x100, & keepsyms=1 Tried 5 different SMBIOS profiles - iMac 18,1 ,  iMac 18,3 ,  iMac 19,1 , iMacPro 1,1 , and MacBookPro 15,1.  
      All result in the same Mac OS X is not supported on this platform message. The one suggestion I've found so far that seemed like it might work was to add the boot argument:
       -no_compat_check
       
      Same results, installer won't start and I get the same message...
       
      Seems like there must be something I've missed or I've done something wrong... I've spent the weekend searching, reading, etc, no luck so far...
       
      A few questions:
       
      I made the installer on my MacBook, not the build I'm trying to hack. Could this be related to the issue?            (I.e. - Does the vanilla method mean you need to create your SMBIOS profile on the actual machine you'll be Hackintoshing?)
       
      Is there a 9900k or Sapphire RX580 compatibility patch needed for 10.13 I haven't seen mentioned in the Mojave builds?  
      Does the Clover update message package is incompatible with this version of OS X and may fail to install indicate something isn't right with my installer setup?  
       
      Please excuse me if anything above isn't clear, I'm brand new to all this and frankly I'm having a hard time wrapping my head around a lot of it!
       

    • By headkaze
      Framebuffer patching in Mojave
      Binary patching framebuffers using KextsToPatch in Clover is no longer a viable method in Mojave for Skylake and above. Now you need to use Lilu + WhateverGreen.
       
      Not just for Mojave
      This method of framebuffer patching is not only required for Mojave we recommend it for all previous and future releases of macOS.
       
      Coffee Lake Users
      Please note that the new WhateverGreen will not work with fake Kaby Lake platform-id's. You will need to have either macOS 10.14 Beta 4 (18A336e) or macOS High Sierra 10.13.6 (17G2112). The latter is a special build only available to MacBookPro15,1 or MacBookPro15,2 board id's. You can create a macOS High Sierra 10.13.6 (17G2112) installer by running installinstallmacos.py. (Update: vit9696 added back ability to fake Kaby Lake platform-id's)
       
      Lilu + WhateverGreen
      WhateverGreen is going to replace all the other video patching plugins for Lilu (it currently has merged WhateverGreen, IntelGraphicsFixup, NvidiaGraphicsFixup, Shiki and CoreDisplayFixup). Others will likely follow (such as AppleALC, HibernationFixup and IntelGraphicsDVMTFixup). This is aiming to be the all-in-one solution for video.
       
      Preliminary
      1. Remove:
      - FakePCIID_Intel_HD_Graphics
      - IntelGraphicsFixup
      - NvidiaGraphicsFixup
      - CoreDisplayFixup
      - Shiki
      2. Turn off all graphics injections in Clover:
      - config.plist/Graphics/Inject/ATI=NO
      - config.plist/Graphics/Inject/Intel=NO
      - config.plist/Graphics/Inject/NVidia=NO
      - config.plist/Graphics/ig-platform-id=
      - config.plist/Devices/FakeID/IntelGFX=

      3. Disable DSDT Clover fixes:
      - AddHDMI
      - FixDisplay
      - FixIntelGfx
      - AddIMEI
      4. Disable UseIntelHDMI
      5. Remove boot argument: -disablegfxfirmware
      6. Remove any IGPU and HDMI entries from:
      - config.plist/Devices/Arbitrary
      - config.plist/Devices/Properties
      - config.plist/Devices/AddProperties
      7. Remove any IGPU and HDMI related SSDT and DSDT from:
      - CLOVER/ACPI/patched
      8. Renaming GFX0 -> IGPU
      - WhateverGreen will do this automatically (see caveat below)
      - Be aware that WhateverGreen does not rename all instances of GFX0 -> IGPU but should be okay in most cases
      - You may need to include Clover GFX0 -> IGPU rename for other kexts or ACPI patching that require it
       
      Compile Lilu + WhateverGreen
      Download WhateverGreen. Make sure you place the debug version of Lilu into the root of WhateverGreen before you compile. Install Lilu and WhateverGreen kext's into the usual place. Compile WhateverGreen as debug if you want to view debug output.
       
      Having trouble compiling?
      If you're having trouble compiling you can download the official release binaries or download my (unsupported) build_lilu.sh shell script and run it in a folder to download and build Lilu + WhateverGreen using Xcode automatically. I recommend you try the debug versions first (place them into Clover's EFI/Clover/kexts/Other folder).
       
      Get the device path of your IGPU:
      Download and use the gfxutil tool like so:
      $ ./gfxutil -f IGPU DevicePath = PciRoot(0x0)/Pci(0x2,0x0) ig-platform-id
      For the AAPL,ig-platform-id (AAPL,snb-platform-id for Sandy Bridge) entry Clover requires this value to be in Data format so you need to reverse the bytes. So if you want your platform-id to be 0x3EA50009 first reverse the bytes (0900A53E) then use Xcode's plist editor to add the values to Clover's config.plist.

       
      What ig-platform-id should I use for my system?
      You should choose one that is the closest match to your system. I recommend you do some research on this before choosing one. See post #2 for available options. More info can be found here.
       
      You can determine the generation of your CPU by the first digit after the hyphen.
      Examples:
      - Intel(R) Core(TM) i5-2760QM (Gen 2)
      - Intel(R) Core(TM) i7-5257U CPU @ 2.70GHz (Gen 5)
      - Intel(R) Core(TM) m3-6Y30 (Gen 6)
      - Intel(R) Core(TM) i5-8350U (Gen 8)
       
      Spoofing Intel CPU Gen
      If you need to spoof a different Intel CPU generation you can use the lilucpu=N boot flag. The N refers to the following Intel generations:
      4    SandyBridge 5    IvyBridge 6    Haswell 7    Broadwell 8    Skylake 9    KabyLake 10   CoffeeLake To spoof a CPU you will need to set a valid device-id in your GPU entry in Devices/Properties for the appropriate Intel generation.
       
      Eg. Spoofing Skylake (lilucpu=8 boot flag with device-id=0x16190000), Kaby Lake (lilucpu=9 boot flag with device-id=0x12590000).
       
      Here are some recommended frames:
       
      Gen 2: Sandy Bridge (Intel HD Graphics 2000/3000)
      - S/L/E/AppleIntelSNBGraphicsFB.kext
      - Support started with OS X 10.7.x and ended with macOS 10.13.6
      - Metal support is not available
      - device-id: 0x0102 0x0106 0x010A 0x0112 0x0116 0x0122 0x0126
      - AAPL,snb-platform-id (desktop): 0x00030010 (default)
      - AAPL,snb-platform-id (laptop): 0x00010000 (default)
       
      Gen 3: Ivy Bridge (Intel HD Graphics 2500/4000)
      - S/L/E/AppleIntelFramebufferCapri.kext
      - Support started with OS X 10.8.x
      - device-id: 0x0152 0x0156 0x0162 0x0166
      - AAPL,ig-platform-id (desktop): 0x0166000A (default), 0x01620005
      - AAPL,ig-platform-id (laptop): 0x01660003 (default), 0x01660009, 0x01660004
       
      Gen 4: Haswell (Intel HD Graphics 4200-5200)
      - S/L/E/AppleIntelFramebufferAzul.kext
      - Support started with OS X 10.9.x
      - device-id: 0x0D26 0x0A26 0x0A2E 0x0D22 0x0412
      - AAPL,ig-platform-id (desktop): 0x0D220003 (default)
      - AAPL,ig-platform-id (laptop): 0x0A160000 (default), 0x0A260005 (recommended)
       
      Gen 5: Broadwell (Intel HD Graphics 5300-6300)
      - S/L/E/AppleIntelBDWGraphicsFramebuffer.kext
      - Support started with OS X 10.10.2
      - device-id: 0x0BD1 0x0BD2 0x0BD3 0x1606 0x160E 0x1616 0x161E 0x1626 0x1622 0x1612 0x162B
      - AAPL,ig-platform-id (desktop): 0x16220007 (default)
      - AAPL,ig-platform-id (laptop): 0x16260006 (default)
       
      Gen 6: Skylake (Intel HD Graphics 510-580)
      - S/L/E/AppleIntelSKLGraphicsFramebuffer.kext
      - Support started with OS X 10.11.4
      - device-id: 0x1916 0x191E 0x1926 0x1927 0x1912 0x1932 0x1902 0x1917 0x193B 0x191B
      - AAPL,ig-platform-id (desktop): 0x19120000 (default)
      - AAPL,ig-platform-id (laptop): 0x19160000 (default)
       
      Gen 7: Kaby Lake (Intel HD Graphics 610-650)
      - S/L/E/AppleIntelKBLGraphicsFramebuffer.kext
      - Support started with macOS 10.12.6
      - device-id: 0x5912 0x5916 0x591B 0x591C 0x591E 0x5926 0x5927 0x5923 0x87C0
      - AAPL,ig-platform-id (desktop): 0x59160000 (default)
      - AAPL,ig-platform-id (laptop): 0x591B0000 (default)
       
      Gen 8: Coffee Lake (Intel UHD Graphics 630)
      - S/L/E/AppleIntelCFLGraphicsFramebuffer.kext
      - Support started with macOS 10.13.6 (17G2112) / 10.14 beta 4 (18A336e)
      - device-id: 0x3E9B 0x3EA5 0x3EA6 0x3E92 0x3E91 0x3E98
      - AAPL,ig-platform-id (desktop): 0x3EA50000 (default), 0x3E9B0007 (recommended)
      - AAPL,ig-platform-id (laptop): 0x3EA50009 (default)
       
      Framebuffer Patching
      WhateverGreen does most of the work automatically for you and in most cases you do not need any extra Framebuffer Patching. At the minimum though you should choose an ig-platform-id suitable for your system and place it in config.plist/Devices/Properties like this:

      Here are some reasons why you might need extra Framebuffer Patching:
      - Setting DVMT for those who can't set it above 32 MB in BIOS (framebuffer-stolenmem / framebuffer-fbmem)
      - Setting higher VRAM for 4K users who experience graphical glitches (framebuffer-unifiedmem)
      - Disabling eGPU (disable-external-gpu)
      - Enable pixel clock patch for 4K support (enable-hdmi20)
      - Disabling connectors to enable sleep (framebuffer-pipecount / framebuffer-portcount / framebuffer-conX-type=-1)
      - Removing CNConnectorAlwaysConnected flag for eDP laptop screens on < 10.13.6 (framebuffer-con0-flags=0x00000090)
      - Changing connector types to match your systems ports (framebuffer-conX-type)
       
      Framebuffer Patching Types
      We have three different types of patches:
       
      1. Arbitrary (Recommended)
      framebuffer-patch-enable (required to enable below) framebuffer-framebufferid (optional; defaults to current platform-id) (all below are optional) framebuffer-mobile framebuffer-pipecount framebuffer-portcount framebuffer-memorycount framebuffer-stolenmem framebuffer-fbmem framebuffer-unifiedmem framebuffer-cursormem (Haswell only) framebuffer-camellia framebuffer-flags framebuffer-conX-enable (required to enable below) framebuffer-conX-index framebuffer-conX-busid framebuffer-conX-pipe framebuffer-conX-type framebuffer-conX-flags 2. All Data
      framebuffer-conX-enable (required to enable below) framebuffer-conX-alldata 3. Find / Replace
      framebuffer-patchX-enable (required to enable below) framebuffer-patchX-framebufferid (optional; defaults to current platform-id) framebuffer-patchX-find framebuffer-patchX-replace framebuffer-patchX-count (optional; defaults to 1) You should place your patches in config.plist/Devices/Properties in Clover config.plist.
       
      Here are some example patches:
      - 32MB BIOS, 19MB stolen (framebuffer) 9MB fbmem (cursor) 2048MB unifiedmem (vram)

       
      - Pipe / Port Count 3 to 2
      - Connector 1 DP to HDMI
      - Connector 2 Disable

       
      Here is an example of the All Data method:

       
      Here is an example of the Find / Replace method:

       
      Framebuffer Dumps
      There are two ways to dump your framebuffer data (both require WhateverGreen + Lilu debug versions):
       
      1. Using -igfxdump boot flag to dump IGPU framebuffer kext to /AppleIntelFramebuffer_X_Y (root of your boot drive)
       
      There are several ways of reading this dump:
      - Using 010 Editor along with the IntelFramebuffer.bt template
      - Using Hackintool File->Open menu
       
      2. Using -igfxfbdump boot flag to dump native and patched framebuffer table to ioreg at IOService:/IOResources/WhateverGreen
       
      There are several ways of reading this dump:
      - Using dump_platformlist.sh shell script
      - Using Hackintool File->Import->IOReg Dump menu
       
      3. Using Hackintool Framebuffer->macOS 10.14 menu
       
      Debug Output
      To get debug output from Lilu use the -liludbgall liludump=60 boot flags. You will need to compile Lilu and WhateverGreen as debug for both of these flags to work. Log files should be located at /var/log/Lilu_*.
       
      To view debug paste the following into Terminal (weglog.txt will output to your home directory):
      log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot >weglog.txt Getting Help

      To help the users of this forum diagnose issues with your configuration please generate a Lilu debug log and then run gen_debug.sh to generate a folder of debug files you can attach to a forum post requesting help.

      Credits
      - vit9696 and lvs1974 for WhateverGreen (Full Credits) and Lilu (Full Credits)
      - Andrey1970 for his guide on applelife.ru
      - RehabMan for all data patching method, ioreg framebuffer dump and other contributions
       


    • By fantomas1
      macOS Mojave 10.14.6 beta (18G29g)
×