Jump to content
thehaus

Clover wont Install to the hidden EFI Partition on SSD OSX Install

13 posts in this topic

Recommended Posts

Update (4/25/16):

 

With the guidance of Slice, I was able to reset the flags on my EFI(disk0s1) partition. Now Clover installer/updater correctly mounts and updates the bootloader in the EFI partition.

 

1. I dowloaded the most current gparted (v2016) and there is now a new flag called ESP in addition to the boot flag on the disk0s1 EFI partition. 

2. Apparently, the older gparted (v2009-2010) I was using wasn't showing me all the flags on the partition. 

3. I double checked the technical specs for OSX EFI partitions and there is supposed to be those two flags (boot and ESP) when using gparted to view the drive. 

4. I turned both flags off and then rewrote them both back by turning them back on within gparted for the EFI partition (disk0s1). That seemed to do the trick. There may have been some data corruption on the boot sector area.

5. The most current version of clover installer/updater v3438 was able to now mount my EFI partition and update the bootloader correctly. The other possibility is that there was a slight change to the clover installer that resolved my drive mounting issue within the clover installer package. Either way, I am relieved.---------------------

I have been having issues with Clover (most current and slightly older versions) not wanting to install to my hidden EFI partition on my SSD OSX installation drive (disk0s1).

I didn't have this issue when i was running Yosemite. Clover updated as it should to my hidden EFI partition and I used UEFI boot without problem.

I decided to update my system to El Capitan doing a clean install. I wiped my SSD using Disk Utility. I first errased the drive, reformatted to a new partition (GUID HFS) and created my UEFI USB El Capitan loader. I installed El Capitan to the SSD without issue.

 

After installation, both the EFI and the OSX partition where created properly along with the recovery partition.

 

I rebooted using the UEFI USB and configured OSX after the welcome screen. I then tried to run the latest version of Clover for the UEFI installation and it failed as it couldn't open the EFI hidden partition and install the kexts and Clover. It basically failed to mount the EFI partition and install to the EFI partition. I even mounted the EFI partition on disk0s1 where my OSX install was on my SSD and it didnt create any files or folders in the partition. I did create an EFI folder with everything in my root OSX partition instead (very odd). I double and triple checked that i selected UEFI as I always do and that the drive was indeed the OSX SSD installation drive.

I manually mounted disk0s1 EFI partition and it had nothing from clover in it. 

I wiped the EFI partition and tried again without success.

I reloaded my GA-Z97MX Gaming5 firmware v6 again and it still failed to load clover into the EFI partition. It did create a EFI folder in my root directory for OSX with all the correct files but i couldn't boot to it using UEFI (YES- i was selecting UEFI from the menu, i have done this successfully on Mavericks and Yosemite many times before)

If I move the folder and files from the root EFI folder to the EFI partition, I can boot OSX using UEFI

I used gparted to reformat the SSD and try to do another fresh install of OSX again thinking that Disk Utility didn't get rid of all the old bootloader info. Clover couldn't mount the hidden EFI partition on disk0s1. I could do it manually though.

I manually mounted the EFI boot partition for my SSD and moved all the clover/mulitbeast files over there. I was able to again boot UEFI SSD El Capitan.

When I try to update clover, it doesn't open the hidden EFI partition or update the files in it. It does, however, create an EFi folder in my OSX root with the new Clover bootloader files there.

 

------------------------------------------------

 

Original post:

 

Background facts:

I have done this successfully many times with both Mavericks and Yosemite in the past using the Clover UEFI booloader

1. I clicked uefi

2. The hidden EFI partition exists on my SSD (disk0s1) OSX install

3. I tried reformatting the drive using gparted and Disk Utility as was outlined in the guides

4. I tried erasing just the EFI partition and changing the file structure

5. I reloaded my GA-Z97MX Gaming5 v6 firmware

6. I did check off the box for loading Clover as uefi

7. I told Clover to install into the ssd OS X drive (I doubled and triple checked this)

8. I booted everything using Uefi from both my F12 option and BIOS option - I don't Legacy boot

9. I tried the most recent versions of Clover. I also tried an older version of Clover for curiosity. 
----------------------

Nothing I do can seem to get Clover to load to the hidden EFI partition on my SSD OSX install (disk0s1)

 

Does anyone have an idea what I need to fix to get Clover to recognize, mount, open, and install to my EFI partition on my SSD (disk0s1)?

Share this post


Link to post
Share on other sites
Advertisement

i tried all many of the older clover installers and none of them could mount the EFI partition. They all create an EFI folder in the root of the OS X partition.

 

I just reformatted my SSD again and tried a fresh install but no luck.

 

I ran terminal "diskutil list" and disk0s1 is EFI as it should be.

 

Here is my clover install log:

 

Clover EFI installer log - Tue Apr 12 19:14:33 PDT 2016

Installer version: v2.3k r3320 EFI bootloader
======================================================
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *256.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage El Capitan              255.2 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1 (internal, virtual):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS El Capitan             +254.8 GB   disk1
                                 Logical Volume on disk0s2
                                 87062435-B34A-4B60-87A5-BDF4C72E52A5
                                 Unencrypted
/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *16.0 GB    disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS El Capitan USB Insta... 15.7 GB    disk2s2
======================================================
Installing BootSectors/BootLoader
 
Stage 0 - Don't write any of boot0af, boot0md, boot0ss to /
Stage 1 - Don't write any of boot1h2, boot1f32alt, boot1xalt to /
 
======================================================
=========== Clover EFI Installation Finish ===========
======================================================

Share this post


Link to post
Share on other sites

Please read my first post so you understand that I formatted my drives properly, ran Clover properly, Check the terminal commands to check for proper mapping of OSX partitions. I also followed all the plist changes for SIP. IF that wasnt the case, my copy of OSX not only wouldn't install, it also wouldnt boot into OSX. This is not my issue.

 

In plist, among other minor changes, I set:

 

rootless=0

 

<key>RtVariables</key>
<dict>
<key>CsrActiveConfig</key>
<string>0x3</string>
<key>BooterConfig</key>
<string>0x28</string>
</dict>

 

For curiosity, i reformatted my SSD again and loaded Yosemite to see if I could get Clover to install to the EFI partition and it couldn't. For some reason, Clover can't mount my EFI partition on my SSD no matter which OS version I load or which Clover version I use.

 

If i check or uncheck ESP in Clover, it always creates a EFI root folder in OSX. I have to move the contents over to the EFI partition manually to get UEFI functionality. It makes updating Clover a real pain every time I update Clover and should be automated in its functionality.

 

My SSD drive must have a flag set somewhere that makes Clover not mount the EFI partition. I have no issues mounting the EFI partition manually using Clover Configurator, EFI Mounter, and Terminal commands.

 

It doesn't seem due to the OS or the SSD drive partition formats and disk #'s

I reflashed my BIOS firmware many times also.

I tried to reflash my Crucial M4 SSD firmware but it says it is the latest and I cant make it repush the firmware.

 

Anyone else have any ideas how to get Clover to recognize and mount my EFI partition so it will load the booloader there automatically?

Share this post


Link to post
Share on other sites

AFAIK rootless=0 doesn't work in 10.11, it's done through CsrActiveConfig (which you have). I would just try setting it to 0x67 instead of 0x3. See if that makes any difference. :)

 

FYI: You don't have to install Clover in the EFI for UEFI to work. In fact, I think it works better installed to / if your BIOS will support it. ;)

 

You also might want to try changing your Clover install from "CloverEFI 64-bits SATA" to "CloverEFI 64-bits BiosBlockIO". I know it makes a difference on the drives that are recognized by Clover on bootup for my system (Gigabyte X79-UD5).

Share this post


Link to post
Share on other sites

Update (4/25/16):


 


With the guidance of Slice, I was able to reset the flags on my EFI(disk0s1) partition. Now Clover installer/updater correctly mounts and updates the bootloader in the EFI partition.


 


1. I dowloaded the most current gparted (v2016) and there is now a new flag called ESP in addition to the boot flag on the disk0s1 EFI partition.


2. Apparently, the older gparted (v2009-2010) I was using wasn't showing me all the flags on the partition. 


3. I double checked the technical specs for OSX EFI partitions and there is supposed to be those two flags (boot and ESP) when using gparted to view the drive.


4. I turned both flags off and then rewrote them both back by turning them back on within gparted for the EFI partition (disk0s1). That seemed to do the trick. There may have been some data corruption on the boot sector area.


5. The most current version of clover installer/updater v3438 was able to now mount my EFI partition and update the bootloader correctly. The other possibility is that there was a slight change to the clover installer that resolved my drive mounting issue within the clover installer package. Either way, I am relieved.


Share this post


Link to post
Share on other sites

I have this issue as well, and have always had it since using Clover.

 

I can mount the EFI partition myself and copy the Clover files to it and boot from it without issue, but Clover never sees the partition itself when I choose Installation Location whether I have the EFI partition mounted or not.

 

I've checked the partition flags and both boot and ESP are set, but I haven't yet tried re-setting them yet (I had to use PARTED on the SysRescue live CD as the GPARTED live CD wouldn't boot for me)

Share this post


Link to post
Share on other sites

I have this issue as well, and have always had it since using Clover.

 

I can mount the EFI partition myself and copy the Clover files to it and boot from it without issue, but Clover never sees the partition itself when I choose Installation Location whether I have the EFI partition mounted or not.

 

I've checked the partition flags and both boot and ESP are set, but I haven't yet tried re-setting them yet (I had to use PARTED on the SysRescue live CD as the GPARTED live CD wouldn't boot for me)

 

I am also having the same issue. What is odd to me is that the Clover installation was working correctly, but I reformatted the drive to start fresh and now I cannot get Clover to install my second time around. I've even went through GParted Live USB and reset the "ESP" and "Boot" flags but still can't get the machine to find it. I'm kicking myself now... :wallbash:

 

Edit: I had to have GParted Live on my USB as just the FAT partition type. FAT32, which it says is compatible, wouldn't boot it.

 

2nd Edit: Does your system have CoreStorage when you type out 'diskutil list' in Terminal?

Share this post


Link to post
Share on other sites

 

2nd Edit: Does your system have CoreStorage when you type out 'diskutil list' in Terminal?

 

Apologies for the delay, have a guest visiting and not been at the comp much.

 

Just ran the command and no, CoreStorage is not mentioned. Here are my results:

[01:59][rob@iMac:~]$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS MacPC                   499.1 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

The EFI partition is currently mounted and I can access it via Finder but the Clover installer doesn't see it. (Just tried the 3726 release)

Share this post


Link to post
Share on other sites

Apologies for the delay, have a guest visiting and not been at the comp much.

 

Just ran the command and no, CoreStorage is not mentioned. Here are my results:

[01:59][rob@iMac:~]$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS MacPC                   499.1 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3

The EFI partition is currently mounted and I can access it via Finder but the Clover installer doesn't see it. (Just tried the 3726 release)

 

 

If you use this clover

there are no such problems with installation on the SSD or HDD.

post-617057-0-14349800-1472967881_thumb.jpg
 
SSD disk.


Clover EFI installer log - Sun Sep  4 09:40:44 OMST 2016
Installer version: v2.3k r3726 EFI bootloader
======================================================
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *256.1 GB   disk0
   1:                        EFI UEFI                    209.7 MB   disk0s1
   2:                  Apple_HFS OSX10.9.5               201.1 GB   disk0s2
   3:                  Apple_HFS PlextorArch             54.0 GB    disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *750.2 GB   disk1
   1:                       0x1C                         23.1 GB    disk1s1
   2:               Windows_NTFS OS                      187.5 GB   disk1s2
   3:               Windows_NTFS DATA                    539.5 GB   disk1s5
======================================================
Backing up EFI files
 
Backing up stage2 file /Volumes/OSX10.9.5/EFIROOTDIR/boot  to /Volumes/OSX10.9.5/EFI-Backups/r3728/2016-09-04-09h40/boot
Backing up /Volumes/OSX10.9.5/EFIROOTDIR/EFI folder to /Volumes/OSX10.9.5/EFI-Backups/r3728/2016-09-04-09h40/EFI
======================================================
Installing BootSectors/BootLoader
 
Stage 0 - Don't write any of boot0af, boot0md, boot0ss to /
Stage 1 - Don't write any of boot1h2, boot1f32alt, boot1xalt to /
Stage 2 - Written boot7 (x64) to /Volumes/ESP/boot
======================================================
Installing RC Scripts
 
Installing RC scripts on target volume '/'
 
Activating /etc/rc.boot.d/70.disable_sleep_proxy_client.local rc script
 
======================================================
=========== Clover EFI Installation Finish ===========
================================================

0:723  0:000  Now is 4.9.2016,  4:6:24 (GMT)
0:723  0:000  Starting Clover revision: 3726 on CLOVER EFI
0:723  0:000  Build with: [Args: ./ebuild.sh -fr -D NO_GRUB_DRIVERS_EMBEDDED | Command: build -D NO_GRUB_DRIVERS_EMBEDDED -D USE_LOW_EBDA -p Clover/Clover.dsc -a X64 -b RELEASE -t XCODE5 -n 5 | OS: 10.12 | XCODE: 7.3.1]
0:723  0:000  SelfDevicePath=PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(1,GPT,F61211C5-87B9-4CDD-BE33-9DC9BD4A478E,0x28,0x64000) @1F44E698
0:723  0:000  SelfDirPath = \EFI\CLOVER

HDD disk.

 


Clover EFI installer log - Sun Sep  4 10:19:34 OMST 2016
Installer version: v2.3k r3726 EFI bootloader
======================================================
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *240.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS OS_X10.11.xssd          190.2 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:                  Apple_HFS archssd                 48.9 GB    disk0s4
 
/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS 12x                     499.6 GB   disk1s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
   4:                  Apple_HFS arch12x                 499.6 GB   disk1s4
 
======================================================
Backing up EFI files
 
Backing up stage2 file /Volumes/12x/EFIROOTDIR/boot  to /Volumes/12x/EFI-Backups/r3728/2016-09-04-10h19/boot
Backing up /Volumes/12x/EFIROOTDIR/EFI folder to /Volumes/12x/EFI-Backups/r3728/2016-09-04-10h19/EFI
======================================================
Installing BootSectors/BootLoader
 
Stage 0 - Don't write any of boot0af, boot0md, boot0ss to /
Stage 1 - Don't write any of boot1h2, boot1f32alt, boot1xalt to /
Stage 2 - Written boot7 (x64) to /Volumes/ESP/boot
======================================================
Installing RC Scripts
 
Installing RC scripts on target volume '/'
 
Activating /etc/rc.boot.d/70.disable_sleep_proxy_client.local rc script
 
======================================================
=========== Clover EFI Installation Finish ===========
======================================================
 

 
0:834  0:000  Now is 4.9.2016,  4:24:17 (GMT)
0:834  0:000  Starting Clover revision: 3726 on CLOVER EFI
0:834  0:000  Build with: [Args: ./ebuild.sh -fr -D NO_GRUB_DRIVERS_EMBEDDED | Command: build -D NO_GRUB_DRIVERS_EMBEDDED -D USE_LOW_EBDA -p Clover/Clover.dsc -a X64 -b RELEASE -t XCODE5 -n 5 | OS: 10.12 | XCODE: 7.3.1]
0:834  0:000  SelfDevicePath=PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(1,GPT,FBA19309-7C18-433A-9A9C-33D50952839D,0x28,0x64000) @DD442098
0:834  0:000  SelfDirPath = \EFI\CLOVER

Share this post


Link to post
Share on other sites

--EDIT Deleted everything.

 

*sigh* Was operator error. I was (wrongly) assuming that the EFI installer would appear in the list of drives which it wasn't. I had to choose the drive with the EFI partition. Then Select Customise and then Install clover in ESP for it to install on the EFI partition.

post-1462892-0-45227900-1472982868_thumb.png

post-1462892-0-58032300-1472982879_thumb.png

Edited by tarasis

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 Slice
      OK, 4988 released.
      Now, @vector sigma, what have we do to update translations?
    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host
      Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. 
       
      The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
       
      @colt2 HOW TO: Create a bootable El Capitan ISO for VMware
      @dsmccombs comment on faking Ivybridge Processor
      @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6
      @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
      VirtualBox Forum: Status of OSX on OSX
       
      Requirements
         Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X)    4GB or more RAM (2GB or more will be needed for OS X)    Hard Disk with at least 40GB free for Virtual Machine    Oracle VM VirtualBox v 5.0.34    Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75    16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC  
      Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes.  Note: you will need approx 16GB of free space on your hard disk for the script to complete.
       
       
       
      3.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 4.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
       
      Create an El Capitan Virtual Machine in VirtualBox
      1.  Open the VirtualBox program and click the "New" button to create a new VM.
       

       
      2.  Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version.  I named my Virtual Machine "El_Capitan", then clicked next...
       

       
      3.  Leave the Memory size at the recommended 2048 MB, then click next.
       

       
      4.  Choose to "Create a virtual hard disk now", then click the create button.
       

       
      5.  For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare.  Click next...
       

       
      6.  For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).
       

       
      7.  On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger.  When you click the create button, you will now see your new VM in the VirtualBox main GUI.
       

       
      8.  Click the settings button on the Main Menu to tweak a few settings....
         a.  On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)
       

       
         b.  On the System/Processor tab, you can increase the allocated CPU cores to 2
       

       
         c.  On the Display tab, you can increase the allocated Video Memory to 128MB
       

       
         d.  On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". 
       

       
      Navigate and select the El Capitan ISO we created earlier...
       

       
         e.  Click the OK button to finalise the VM settings.
       
       
      Patch El Capitan vbox configuration file with DMI Settings from a Mac
      1.  From the start menu, type cmd and click run as administrator to open an administrative command prompt. 
       

       
      2.  Choose a Mac Model similar to your host system, then type the following lines, followed by <enter>  after each line.  Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
       
      Eg iMac11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3.  Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.  You can try from one of the following if this happens:

      To spoof Lynnfield i5 750 CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4.  Close the command prompt window.
       
       
      Installation of El Capitan
      We are now ready to start the El_Capitan Virtual Machine....
       



       
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

       
      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan.
       

       
      3.  Quit DU and choose Macintosh HD to install El Capitan on.
      4.  After 20-30 min (depending on how fast your system is), the installation will complete.  At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive.  The VM is now ready to reboot into OS X from the virtual hard drive.
      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
      7.  Finally, you will arrive at the El Capitan Desktop.
       

       
      8.  Network/internet and audio should work OOB but on my system, the sounds were distorted.  Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). 
       
       
      Customization with VBoxManage
      1.  You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
       
      Update:  For VirtualBox 5.2.x, the command for changing screen resolution has changed...
       
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
      eg
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2.  Adding serials and other SMBIOS details for the System Information Screen
      VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
       
      Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above).  Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .
       

       
      UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
      UPDATE macOS High Sierra 17A365:  For macOS High Sierra, use CHSI.tool in post#73.
      UPDATE macOS Mojave 18A391:  For macOS Mojave or High Sierra, use macOS_iso_creator.tool on page 4 of thread.
      UPDATE macOS Catalina Beta DP3_19A501i:  For Catalina, @jpz4085 has made an automated batch file to create a Catalina VM in Windows with iMac 14,2 SMBIOS.  You can still use my macOS_iso_creator.tool on page 5 to make an installer ISO to attach to the VM.
       
       
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
×