Jump to content
fusion71au

Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VMware Workstation on a Windows Host

54 posts in this topic

Recommended Posts

Okay so I reinstalled and everything seemed to be working fine. I shut down the VM. Went home. Today it does the same thing. The boot screen with the apple logo comes on. The progress bar gets about 80% across the screen, and then the screen maximizes. The window goes black and nothing. I can see some notifications pop up on the top right side. But they're kind of transparent. But the background is all black and I can't find anywhere to click to get it to do anything. If I leave it setting the screen saver eventually pops up. Any ideas? Thanks.

Share this post


Link to post
Share on other sites
Advertisement

So I reinstalled for a third time. I have tried to install Clover as recommended, and it doesn't seem to work. The vm boots and works, it just is booting like normal and not going to a clover screen. So for now I'm just not "powering down" the VM. I only "suspend" it. And reboot only when necessary. So far its still working, but wish I could get clover to work.

Share this post


Link to post
Share on other sites

hey, guys,

 

what if i build the vm on the mac (get it configured and as set up as possible)?

how would these instructions be modified for that? obviously, i would ignore installation, but, what about editing the v files? does that happen before or after the move?

 

thanks,

bw

Share this post


Link to post
Share on other sites

On KabyLake CPU I had to set MAC OS version to 10.7, else VMWare always crashed when attempting to start the VM. It is kinda counterintuitive, because I have 10.12 (Sierra) installed. I tried with and without SMC mods - the same result.

Share this post


Link to post
Share on other sites

Update for macOS High Sierra and Mojave

 
To prepare the High Sierra or Mojave ISO on your Mac or Hack, the macOS_iso_cim.tool script will chain-load Apple's createinstallmedia utility.
 
1.  On your Mac or Hack, download/copy "Install macOS xxx.app" into your Applications folder.
 
2.  Download and unzip the macOS_iso_cim.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.
 
 
 

#!/bin/bash
 
 # Create macOS sparseimage of 6200mb with a Single Partition - Apple Partition Map
 hdiutil create -o /tmp/macOS -size 6200m -layout SPUD -fs HFS+J -type SPARSE
 
 # Mount the macOS sparseimage
 hdiutil attach /tmp/macOS.sparseimage -noverify -mountpoint /Volumes/install_build
 
 # Chain-load createinstallmedia utility
 /Applications/Install*.app/Contents/Resources/createinstallmedia --volume /Volumes/install_build
 
 # Move sparseimage to desktop
 mv /tmp/macOS.sparseimage ~/Desktop/InstallSystem.sparseimage

 # Unmount the Installer image
 hdiutil detach /Volumes/Install*
 
 # Convert the macOS sparseimage to ISO/CD master
 hdiutil convert ~/Desktop/InstallSystem.sparseimage -format UDTO -o ~/Desktop/macOS.iso
  
 # Rename macOS.iso.cdr to macOS.iso
 mv ~/Desktop/macOS.iso.cdr ~/Desktop/macOS.iso
 
 # Delete macOS.sparseimage file
 rm -f ~/Desktop/InstallSystem.sparseimage

 

 
3.  Open OS X terminal, then run the following commands to execute the script:
cd Downloads
chmod +x macOS_iso_cim.tool
sudo ./macOS_iso_cim.tool

eg

Spoiler

Mac-Pro:~ fusion71au$ cd Downloads
Mac-Pro:Downloads fusion71au$ chmod +x macOS_iso_cim.tool
Mac-Pro:Downloads fusion71au$ sudo ./macOS_iso_cim.tool
Password:
created: /tmp/macOS.sparseimage
/dev/disk4              Apple_partition_scheme             
/dev/disk4s1            Apple_partition_map                
/dev/disk4s2            Apple_HFS                          /Volumes/install_build
Ready to start.
To continue we need to erase the volume at /Volumes/install_build.
If you wish to continue type (Y) then press return: y
Erasing Disk: 0%... 10%... 20%... 30%...100%...
Copying installer files to disk...
Copy complete.
Making disk bootable...
Copying boot files...
Copy complete.
Done.
"disk4" unmounted.
"disk4" ejected.
Reading Driver Descriptor Map (DDM : 0)…
Reading Apple (Apple_partition_map : 1)…
Reading  (Apple_Free : 2)…
Reading disk image (Apple_HFS : 3)…
.............................................................................
Elapsed Time:  2m  3.679s
Speed: 50.1Mbytes/sec
Savings: 0.0%
created: /Users/fusion71au/Desktop/macOS.iso.cdr

 

 

4.  At the end of the process, you will have a macOS.iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
6.  Attach the iso to the Virtual Machine on the PC Host and start the installer, run VMware tools etc...
 
post-846696-0-92489100-1506427308_thumb.png

 

 

 

The VM host settings from post#1 still work for High Sierra 10.13 and Mojave 10.14 (VMware Workstation 12.5 and unlocker 2.0.8, Apple Mac OS X as the Guest operating system and macOS 10.12 as the version).  If the host has sufficient memory, I recommend allocating 3GB or more for a High Sierra VM guest.

 

Workstation 15.0 and Unlocker v3.0 support Mojave OOB but Workstation 15 does not support host CPU older than SandyBridge :mad:.

 

macOS_iso_cim.tool.zip

 

Edited by fusion71au
Update for Mojave 10.14 and new macOS_iso_cim.tool

Share this post


Link to post
Share on other sites

I am having some issues with high sierra, the APFS conversion is messing stuff up for me 12.5.7 + unlocker 2.0.8

 

I guess it means I need to install Sierra and then upgrade with the trick that allows you to avoid converting to APFS. 

 

It there a way to to trigger 

 

sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --converttoapfs NO

 

From the terminal? Maybe edit the plist or something? 

 

Anyone running VMWare 12.5.7 with high sierra on APFS? 

sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --converttoapfs NO

 

When I run it in terminal in the recovery/install area it complains "Error: could not find OSInstallerSetup.framework" 

Share this post


Link to post
Share on other sites

@samsam99,

 

That's because you haven't specified --applicationpath /Install\ macOS\ High\ Sierra.app eg

/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/macSSD --converttoapfs NO --applicationpath /Install\ macOS\ High\ Sierra.app

where "macSSD" is name of target volume.

 

Here are some screenshots from the install on "macSSD".  I have booted from the "OS X Base System" installer created with CHSI.tool in post#30, and started terminal from the Utilities menu...


 


post-846696-0-19956300-1506573615_thumb.png


 

post-846696-0-33736600-1506573644_thumb.png


 

post-846696-0-36106000-1506573680_thumb.png


 

post-846696-0-05619200-1506573704_thumb.png


 

post-846696-0-55420800-1506574687_thumb.png

 

Share this post


Link to post
Share on other sites

The method to install clover on VM doesn't work any more for the latest version of Clover.  Clover on VM has been broken for a while, and their dev team seems to have no intention to fix that. I cannot use my passthrough GPU, that's pretty bad  :(

Share this post


Link to post
Share on other sites

The method to install clover on VM doesn't work any more for the latest version of Clover.  Clover on VM has been broken for a while, and their dev team seems to have no intention to fix that. I cannot use my passthrough GPU, that's pretty bad   :(

 

The problem is not Clover per se but which toolchain is used to compile it...latest Clover r4223 compiled with GCC5.3 in Linux Mint 18.1 works fine to boot High Sierra 10.13 in VMWare12...

 

post-846696-0-71229400-1506670015_thumb.png

Clover r4223 for VMware.zip

Share this post


Link to post
Share on other sites

Please can the guru's help,

 

I have Fusion 8.5 with an old el caption guest os. I'm booting into an old version of clover which then starts up el capitan.It worsk 100% fine, heck even my imessage.

 

The problem:

I cannot find the site that help me to perform this about 2 years ago.

i want to do the same with Fusion pro 10 firing up latest clover and boot into macOs High Sierra

Share this post


Link to post
Share on other sites

Run Vanilla OS X El Capitan, Sierra, Yosemite or Mavericks in VMware Workstation 12 on a Windows Host

 

I wanted to make a simple guide on how to create a vanilla OS X El Capitan virtual machine running on a Windows host.  The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.

 

There are many guides and videos on the net about running OS X on Windows machines using pre-made VMWare disk images but you can never guarantee what else is in there….

 

I’ve gathered info for this guide from various threads in the Multibooting and Virtualisation section of this forum eg

 

Credit and thanks to @Donk, @Albert Nietsnie and @MSOK for all their hard work in creating and testing the VMware Unlocker program.

 

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
  • VMware Workstation 12 or later
  • VMware Unlocker 2.0.7 or later
  • Install OS X El Capitan app and Mac or Hack to prepare installation iso
  • 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.  Unmount any attached install image/InstallESD.dmg (if currently mounted) by rebooting the system or running the hdiutil unmount command in terminal eg

 

ls /Volumes

hdiutil unmount -force /Volumes/OS\ X\ Base\ System   (if you find 'OS X Base System')

hdiutil unmount -force /Volumes/OS\ X\ Install\ ESD       (if you find 'OS X Install ESD')

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

 

 

 

#!/bin/bash
 
 # Mount the Installer image
 hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg -noverify -nobrowse -mountpoint /Volumes/install_app
 
 # Create El Capitan sparseimage of 7316mb with a Single Partition - Apple Partition Map
 hdiutil create -o /tmp/ElCapitan -size 7316m -layout SPUD -fs HFS+J -type SPARSE
 
 # Mount the El Capitan sparseimage
 hdiutil attach /tmp/ElCapitan.sparseimage -noverify -nobrowse -mountpoint /Volumes/install_build
 
 # Restore the Base System into the El Capitan Blank sparseimage
 asr restore -source /Volumes/install_app/BaseSystem.dmg -target /Volumes/install_build -noprompt -noverify -erase
 
 # Remove Packages link and replace with actual files
 rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages
 cp -rp /Volumes/install_app/Packages /Volumes/OS\ X\ Base\ System/System/Installation/
 
 # Copy El Capitan installer dependencies
 cp -rp /Volumes/install_app/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System/BaseSystem.chunklist
 cp -rp /Volumes/install_app/BaseSystem.dmg /Volumes/OS\ X\ Base\ System/BaseSystem.dmg
 
 # Unmount the installer image
 hdiutil detach /Volumes/install_app
 
 # Unmount the Base System image
 hdiutil detach /Volumes/OS\ X\ Base\ System/
 
 # Convert the ElCapitan spareseimage image to ISO/CD master
  hdiutil convert /tmp/ElCapitan.sparseimage -format UDTO -o /tmp/ElCapitan.iso
 
 # Rename the ElCapitan ISO image and move it to the desktop
  mv /tmp/ElCapitan.iso.cdr ~/Desktop/'EC 10.11.0.iso'
 
 # Delete ElCapitan.sparseimage file
  rm -f /tmp/ElCapitan.sparseimage

 

 

4.  Open OS X terminal, then run the following commands to execute the script:

cd downloads
chmod +x CECI.tool
./CECI.tool

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

 

Update: @shela has created an ISO generating script compatible with OS X 10.6-10.12: create_osx_iso post #362.

 

Install and Patch VMware Workstation 12 on your PC

1.  Download and install VMWare Workstation Player 12 or later

2.  Download and extract Unlocker 2.0.7 or later to your USB stick…

3.  Run the win-install.cmd as administrator by right clicking the file in Windows explorer or run it from an Administrative Command Prompt.

 

attachicon.gifVMWare_unlocker207.png

attachicon.gifRun Command Prompt as administrator.png

attachicon.gifwin-install.cmd.png

 

Create an El Capitan Virtual Machine

1.  Double click on the VMware Workstation 12 Player icon on your desktop and click “Create a New Virtual Machine”.  Choose “I will install the operating system later” at the How will you install screen….

 

attachicon.gifCreate a New Virtual Machine.png

2.  Select Apple Mac OS X as the Guest operating system and OS X 10.11 as the version.  By default, an OS X 10.11 folder will be created in your Documents\Virtual Machines folder.

 

attachicon.gifSelect a Guest Operating System.png

attachicon.gifName the Virtual Machine.png

3.  Under Specify Disk Capacity, you can leave the default 40GB or set a larger value.  I personally store the virtual disk as a single file.  Click Finish and you will see OS X 10.11 on the Main Screen of Workstation 12.

 

attachicon.gifStore virtual disk as a single file.png

attachicon.gifFinish.png

4.  Next, we need to edit the virtual machine settings to map the virtual SATA CD/DVD drive to the El Capitan installation iso we created earlier.

 

attachicon.gifEdit virtual machine settings.png

attachicon.gifBrowse for ISO image file or use physical drive.png

 

5.  To prevent the virtual machine from crashing in Windows, the virtualHW.version set in the vmx configuration file needs to be changed from 12 to 10 (alternatively, the line smc.version = "0" can be added to the file).  The OS X 10.11.vmx file can be edited with the WordPad program (navigate to the OS X 10.11 virtual machine folder with Windows Explorer and right click on the file to open in WordPad).

 

attachicon.gifEdit vmx file with WordPad.png

attachicon.gifSet virtualHW.version to 10 or SMC=0.png

 

6.  For HW10, set USB compatibility to USB 2.0, otherwise your mouse and keyboard might not work in the virtual machine.

 

attachicon.gifSet USB compatibility to USB 2.0.png

7.  Finally click “Play virtual machine”

 

attachicon.gifPlay VM.png

Installation of El Capitan

Installation should be relatively straight forward, just following the prompts of the OS X installer:

1.  Select language, agree to legal terms

 

attachicon.gifSelect language, agree to legal terms.png

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’ve named the drive Macintosh HD but you can enter whatever you like eg El_Capitan.

 

attachicon.gifOS X Installer Utilities - Disk Utility.png

attachicon.gifOpen Disk Utility from Utilities Menu.png

attachicon.gifErase disk and name Macintosh HD.png

3.  Quit DU and choose Macintosh HD to install El Capitan on.

 

attachicon.gifChoose Macintosh HD.png

4.  After 20-30 min (depending on how fast your system is), the installation will complete and the VM will automatically reboot…

 

attachicon.gifReboot for first time.png

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…

 

attachicon.gifWelcome choose country and keyboard.png

attachicon.gifTransfer Information, location services, AppleID, terms and conditions.png

6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….

 

attachicon.gifCreate a Computer Account.png

attachicon.gifSelect Time Zone, Send Diagnostics and Usage Data.png

7.  Finally, you will arrive at the El Capitan Desktop.  You should eject the Installation iso now by right clicking and selecting “Eject OS X Base System”.  This will allow you to install VMware Tools….

 

attachicon.gifEl Capitan Desktop.png

attachicon.gifEject OS X Base System Installer to install VMware Tools.png

attachicon.gifInstall VMware Tools.png

8.  After rebooting, the VM can now be resized or run at full screen resolution.  Audio and network/internet should also work OOB.

 

attachicon.gifSystem Information.png

 

SMBIOS Customization and iMessage Vars

To make the Virtual Machine more "Mac like", you can edit the vmx file to add unique identifiers from a real Mac's SMBIOS -

eg for an iMac 11,3 SMBIOS, you can enter the following lines....

smbios.reflectHost = "FALSE"
board-id.reflectHost = "FALSE"
board-id = "Mac-F2238BAE"
hw.model.reflectHost = "FALSE"
hw.model = "iMac11,3"
serialNumber.reflectHost = "FALSE"
serialNumber = "W80#######6"

Refer How to spoof real Mac in VMware - Multi-booting and Virtualisation.

 

The critical variables for iMessage/Facetime activation are MLB & ROM.  By default, VMware "reflects" the host's MLB and ROM since it assumes you are running the OSX guest on a real Mac host - see post#42 by @Donk.

 

If the host is a Windows PC, the following lines need to be added to the vmx file (requires virtualHW.version 12 and smc.version = "0")....

efi.nvram.var.ROM.reflectHost = "FALSE"
efi.nvram.var.MLB.reflectHost = "FALSE"
system-id.enable = "TRUE"

and the MLB, ROM and optionally system-id entered manually eg

efi.nvram.var.MLB = "W80######BA1A" (MLB can be 13 or 17 characters long, alphanumeric string)
efi.nvram.var.ROM = "<=>?@A" (ROM is entered here as a 6 character ASCII string)
uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##" <---Optional (if you want to inject a given system-id hexadecimal value)

Note the output for ROM from imessage_debug is a 12 character hexadecimal that needs to be entered here as a 6 character ASCII string eg using an Hex to ASCII converter we find that "3c3d3e3f4041" hex is equivalent to   "<=>?@A".

 

Vanilla Mavericks and Yosemite

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

 

attachicon.gifVanilla Mavericks on VMware.jpg

 

Enjoy :)

 

Update for Sierra 10.12

The above settings still work for macOS Sierra after upgrading to VMware Workstation 12.5 and unlocker 2.0.8 - see post #13.

 

Update for High Sierra 10.13

See post#30.

Hi,

 

Does this method work for latest edition of clover, macos high sierra and fusion 10 pro.

 

I have fusion 8.5 and it did work first time when i installed it late 2015 

Share this post


Link to post
Share on other sites

@Beefcat,

 

Sorry, I don't have VMware Fusion on a Mac so I don't know and can't test.  Better to ask @Donk in his thread.

 

The method explained in post#1 was tested with VMware Workstation Player on a Windows host.

 

PS Why do you want to use Clover when your host is a Mac?  It is not required to run the VM or get iMessage working....

Share this post


Link to post
Share on other sites

running Sierra (10.12.6) on top of VMware WS12.5.7. Everything seems to work BUT

I cannot connect my iOS devices via USB 2 anymore :((

key error symptom: endless connect-disconnect loop of USB connected iPhones and iPad

 

This works with identical host HW and identical VM WS 12 in VM with 10.11.6 though.

Tried unsuccessful w/ 10.12.6 VM:

- VM HW version 9-11

- powered USB hub and all HW USB hubs

 

What else can i try?

Thx for help

Share this post


Link to post
Share on other sites

after further systematic tests: different cables, VMtools versions, host USB drivers (vmusb.sys), WS 12 uninstall (incl /clean) and reinstall

I could get 1 iPhone connected after resetting "Settings - General - location & privacy" on iPhone. This did not work for the other iPhone :(

Looks as if this error could be triggered by several causes and my problem looks to me like a timing problem.

 

any help appreciated

Share this post


Link to post
Share on other sites

running Sierra (10.12.6) on top of VMware WS12.5.7. Everything seems to work BUT

I cannot connect my iOS devices via USB 2 anymore :((

key error symptom: endless connect-disconnect loop of USB connected iPhones and iPad

 

This works with identical host HW and identical VM WS 12 in VM with 10.11.6 though.

Tried unsuccessful w/ 10.12.6 VM:

- VM HW version 9-11

- powered USB hub and all HW USB hubs

 

What else can i try?

Thx for help

 

 

Installing 10.12.4 worked for me. The moment I update to 10.12.6, connecting iOS devices to USB will result in the endless loop as you have described. 

 

So at the moment I am forced to sit on 10.12.4, which sucks because my plan was to use the VM for testing out stuff with XCode and the latest Configurator (DEP Provisioning et al) 

 

I would hate to have to have a separate machine on my desk just for OSX, I already have too many machines sitting around here :D

Share this post


Link to post
Share on other sites

How to install High Sierra 10.13 or Mojave 10.14 on a VMware Guest (without access to Mac or App Store Installer.app)

 

Pre-requisites
1)  On a 16GB NTFS formatted USB volume, renamed "USB",  a "SharedSupport" folder was prepared as described in my guide here, containing the following 6 installer files downloaded from Apple's Software Catalog ....

 

 

 

  1. BaseSystem.dmg
  2. BaseSystem.chunklist
  3. InstallInfo.plist <---Edited, attached example 
  4. InstallESDDmg.pkg <---Renamed to InstallESD.dmg 
  5. AppleDiagnostics.dmg
  6. AppleDiagnostics.chunklist

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

 

 

2)  macOS guest created in patched VMware Workstation Player (unlocker patch by @Donk), as described in post#1.  Attached blank virtual disk macOS_apfs.vmdk.zip of 50GB size and Clover r4699 installed in its EFI.

 

 

Procedure
1)  Download & extract the contents of BaseSystem_vmdk_generator.zip to your USB.  For my system, the drive letter was D:

 

MJVM5.png.3507327ea1c40cd13fb1c27d73d81614.png

 

2)  Convert \SharedSupport\BaseSystem.dmg to vmdk by double clicking BaseSystem_vmdk_generator.bat.  The file BaseSystem.vmdk is automatically created in the root directory \ of the USB.

 

Deleting any existing image files and vmdk files...
Could Not Find D:\*.vmdk
Could Not Find D:\qemu-img-win-x64-2_3_0\*.img
Converting BaseSystem.dmg to BaseSystem.img with dmg2img...

dmg2img v1.6.7 (c) vu1tur (to@vu1tur.eu.org)

\SharedSupport\BaseSystem.dmg --> \qemu-img-win-x64-2_3_0\BaseSystem.img


decompressing:
opening partition 0 ...             100.00%  ok
opening partition 1 ...             100.00%  ok
opening partition 2 ...             100.00%  ok
opening partition 3 ...             100.00%  ok
opening partition 4 ...             100.00%  ok
opening partition 5 ...             100.00%  ok
opening partition 6 ...             100.00%  ok
opening partition 7 ...             100.00%  ok

Archive successfully decompressed as \qemu-img-win-x64-2_3_0\BaseSystem.img
Converting BaseSystem.img to BaseSystem.vmdk...
BaseSystem.vmdk created in root directory of USB drive!
Press any key to continue . . .

 

3)  Copy BaseSystem.vmdk from your USB into the VMware macOS guest folder

4)  Attach BaseSystem.vmdk and macOS_apfs.vmdk to your macOS guest as extra hard drives.  When you see the message "Convert existing virtual disk to newer format?", click convert

 

MJVM1.png.be8756663bc8d0b54ea5fb9fef241540.png

 

5)  Boot your VM to the macOS Utilities screen.  Attach the usb (named "USB" and containing the \SharedSupport folder) to the VM and open Disk Utility, show all devices ---> will see blank 50GB drive for installation, 2GB "OS X Base System" and the USB volume "USB"

Spoiler

 

MJVM2.thumb.png.444ec4fdd051be1c559d35114d324f38.pngMJVM3.thumb.png.562c50d430d5ac06084a4144c287172a.pngMJVM4.thumb.png.98a9f0c4399042eb041d44f344ff6215.png

MJVM6.thumb.png.865d0842e462f2177ce703fb1ac02842.pngMJVM7.thumb.png.831ee61cb1b7f0c11efb5b0abe5d3b05.pngMJVM8.png.e1f8dba514dff5d9df7400d0b6268ee5.png

 

 

 

6)  Erase blank drive, format it to apfs named "macOS"

7)  Close DU and start Terminal...

 

-bash-3.2# cd /Volumes/USB
-bash-3.2# ./startosinstall.command

The startosinstall.command script builds the full "Install macOS ******.app" and chain loads the startosinstall utility on the "macOS" target volume.  It combines both the "small" installer app (approx 15MB in size on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted on /Volumes/USB).  Note the full installer app is >5GB in size ...

 

MJVM10b.png.e8f22371299b6a4077d73d22fe340b9f.png

 

8)  After a few minutes, Apple's Software License agreement will appear ---> type "A" to agree to the License Agreement ---> install files will be placed in /Volumes/macOS/macOS Install Data ---> System will reboot ---> Phase 2 installation extracting installer pkg files from /macOS Install Data ---> Final reboot into completed system, ready to setup new user account...
 

Spoiler

 

MJVM11b.png.def9e7848bca0450f99871f37bf0f348.png

VMware_Mojave2.png.0aad93b7843575d0a0734d401a4f67fc.png

VMware_Mojave3.thumb.png.01610156ba9fbc0414c8fbb0a443adf1.png

VMware_Mojave4.thumb.png.0ba5e0c4adf4b9e672bbbdf6ebb674bd.pngVMware_Mojave5.thumb.png.0851223f103bf9df9b6873f581d2dc6a.png

 

 

9)  After setting up a new user account, install VMware Tools to improve the graphics performance of the macOS guest.  You can also delete or archive the "Install macOS ******.app" that remains in /Previous Content

 

VMware_Mojave6.thumb.png.e9d2684a84ccd7e656960e233f0dde85.png

VMware_Mojave7.thumb.png.6293d923b9ac05c4562de840037411ac.pngVMware_Mojave8.png.e8f44e09b7e0a37ddf14c992168f8b73.png

 

10)   If you subsequently want to start the VM through Clover, edit the VM's vmx file to add the line bios.bootDelay = "3000"...

 

MJVM12.thumb.png.53cb457e5ea02242e30265f13d56f3f4.png

 

After starting the virtual machine, click in the VM window and quickly press the <F2> key to access the VMware Boot Manager ---> select EFI Hard Drive ---> Boot macOS from macOS at the Clover Main Menu.  Clover nicely fills in the System's details, including a serial number (you can change this later + add custom MLB + ROM for iMessage by mounting the EFI partition and editing Clover's config.plist).

 

 

BaseSystem_vmdk_generator.zip

macOS_apfs.vmdk.zip

Edited by fusion71au
Update for macOS Mojave

Share this post


Link to post
Share on other sites

@kebjjjjoooooa,

 

It means the system cannot read your install media.

  • Ensure that you download only from official sources ie the installer.app from App Store or BaseSystem.dmg from the Apple Software Catalog URL.  You can compare the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg (Hint: right click on the installer.app in Finder and "Show Package Contents") with the correct ones at this website.

          Eg for "Install macOS High Sierra.app" 10.13.1_17B48, determine its SHA1 in Terminal..

 

fusion71aus-iMac:~ fusion71au$ shasum /Volumes/Macintosh\ HD/Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/InstallESD.dmg 

d815748c242fbbe35754a8f37aea1cfbc7e919f6  /Volumes/Macintosh HD/Applications/Install macOS High Sierra.app/Contents/SharedSupport/InstallESD.dmg

fusion71aus-iMac:~ fusion71au$ shasum /Volumes/Macintosh\ HD/Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/BaseSystem.dmg 

b38e5f4daa014d324f1a78f91c1f30f6d68289ef  /Volumes/Macintosh HD/Applications/Install macOS High Sierra.app/Contents/SharedSupport/BaseSystem.dmg

 

  • Prepare the install media with the tools provided/described in post#1 (Mavericks, Yosemite, El Capitan ISOs), post#13 (Sierra ISO), #30 & post#41 (High Sierra ISO or vmdk from BaseSystem.dmg).

Share this post


Link to post
Share on other sites

I get a boot loop. Looking through the vmware.log file, I see several suspicious things. Any ideas what could be wrong?

2017-12-08T14:24:20.932-07:00| vcpu-3| W115: DarwinPanic: panic(cpu 3 caller 0xffffff801ca9e657): "a freed zone element has been modified in zone kalloc.48: expected 0xc0ffee3c8f1b6b4c but found 0, bits changed 0xc0ffee3c8f1b6b4c, at offset 0 of 48 in element 0xffffff80306634e0, cookies 0x3f0011bcbf7d52bc 0x53521d4324e2ff9"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4570.31.3/osfmk/kern/zalloc.c:1120

2017-12-08T14:24:20.935-07:00| vcpu-0| W115: PVNVRAMSetMacOSROM: Unable to retrieve host value.
2017-12-08T14:24:20.935-07:00| vcpu-0| W115: PVNVRAMSetMacOSMLB: Unable to retrieve host value.

2017-12-08T14:24:51.761-07:00| vcpu-1| W115: DarwinPanic: panic(cpu 1 caller 0xffffff801c16f2e9): Kernel trap at 0xffffff801c60c056, type 14=page fault, registers:
2017-12-08T14:24:51.763-07:00| vcpu-0| I125: DEVICE: Resetting device 'ALL'.

Share this post


Link to post
Share on other sites

I've got a boot loop as well just my kernel panic message in log is different:

vcpu-0| W115: DarwinPanic: panic(cpu 0 caller 0xffffff801f30fdf0): initproc exited -- exit reason namespace 2 subcode 0x4 description: none 

This is on Workstation 14 Pro on Arch Linux using an Intel CPU. I converted the BaseSystem.dmg downloaded from the regular catalog (there are two in there?) with dmg2img and then installed qemu and used qemu-img from cli with the exact same command. I used unlocker2.1.1 and could successfully select MacOS as operating system in Workstation. The resulting BaseSystem.vmdk was attached as 2nd disk. Apple on black shows up then immediately reboots.

Share this post


Link to post
Share on other sites

First, thank you  fusion71au for a very informative and splendid guide.

 

I was able to download High Sierra from the Apple servers and complete a functional installation of v10.13.3 on VMware Workstation Player v12.5.9.

 

However, I came across a couple issues.

 

1) The preformatted 50 GB disk with Clover in post #44 did not appear to be compatible with the BaseSystem for my case.

 

The bootloader screen does launch. However, when I click on the BaseSystem to boot, I get an immediate firmware error and the entire virtual machine quits. I had to create a completely blank disk and go through steps 6-8 to accomplish the installation.

 

2) All iterations of Clover do not seem to work with my virtual High Sierra.

 

I have tried following all instructions and copies of Clover in this thread. The system still immediately goes to the Apple logo and OS starts.

 

 

Has anyone recently gotten the Clover Bootloader to install and run successfully on a VMware High Sierra machine? Any help would be greatly appreciated.

Share this post


Link to post
Share on other sites

Hi,

I've one question: I'm using El Capitan on WM Player (Windows 10 x64, ssd, 16gb ram), but my vram is locked to 128mb.

If I'll install Clover, Will I be able to use my graphic card (nvidia 970m) or at least get more vram?

 

Thanks! ^^

Share this post


Link to post
Share on other sites

Compilation of Clover with Build_Clover with GNU and launch of Clover using Alt startup was successful, but still getting a similar firmware error as before.

 

This is in spite of applying all settings as suggested in post #5.

 

Will keep working around with it.

 

EDIT:

 

Found ticket in SourceForge for Clover pointing out that SMBIOS was a major culprit:

https://sourceforge.net/p/cloverefiboot/tickets/403/

 

Filled out SMBIOS information with Clover Configurator, but that wasn't enough. Crash persisted.

 

Went back and filled out Rt Variables information and put in Custom UUID under System Parameters.

 

Now, Clover v4416 bootloader is fully functioning, boots the High Sierra virtual machine with updated hardware ID.

 

Will begin experimenting with pass throughs, especially on the graphics card side.

 

Major goal of mine to enable a highly functional version of Osirix.

 

 

EDIT 2:

Guess this should be obvious, but basic Mac profile should mimic whatever CPU setting chosen for the virtual machine.

Share this post


Link to post
Share on other sites
On 24/02/2018 at 12:51 PM, tachycore said:

Compilation of Clover with Build_Clover with GNU and launch of Clover using Alt startup was successful, but still getting a similar firmware error as before.

 

This is in spite of applying all settings as suggested in post #5.

 

Will keep working around with it.

 

EDIT:

 

Found ticket in SourceForge for Clover pointing out that SMBIOS was a major culprit:

https://sourceforge.net/p/cloverefiboot/tickets/403/

 

Filled out SMBIOS information with Clover Configurator, but that wasn't enough. Crash persisted.

 

Went back and filled out Rt Variables information and put in Custom UUID under System Parameters.

 

Now, Clover v4416 bootloader is fully functioning, boots the High Sierra virtual machine with updated hardware ID.

 

Will begin experimenting with pass throughs, especially on the graphics card side.

 

Major goal of mine to enable a highly functional version of Osirix.

 

 

EDIT 2:

Guess this should be obvious, but basic Mac profile should mimic whatever CPU setting chosen for the virtual machine.

 

 

 

Hi, how the GPU passthrough works?

Share this post


Link to post
Share on other sites

Hi,

 

thanks for the very detailed guide!

I used it to install High Sierra 10.13 on VMWare Workstation running on a Windows 10 (1803, x64) host. I used Donk's unlocker (2.1.1). I installed VMWare Tools from the Workstation menu, and the display looked fine on reboot but as soon as I log in and get to the desktop, after 3 seconds the screen resolution keeps switching back from the native 1920x1080 to scaled down 960x540 HiDPI.

 

When I access the OSX display settings and click 1920x1080 it stays for 1-2 seconds and switches back to 960x540 HiDPI. I can't make it stick...

 

I tried uninstalling and reinstalling VMWare Tools using the Darwin.iso created by the Unlocker, but the result is the same.

 

Running

/Library/Application\ Support/VMware\ Tools/vmware-resolutionSet 1920 1080

 in the terminal doesn't fix anything either (with or without sudo).

 

What am I missing..? Help!

 

EDIT: While initially searching for other posts relating to my issue I missed this one that solved it for me.

 

On 12/1/2017 at 9:24 PM, moisiss said:

I was having the same issue with my 10.12 VM in ESXi 6.0.  I would go to display resolution and try to select 1600x900 and it would auto-switch it to 800x450 HiDPI no matter what I did.  I was able to fix it by doing the following:

 

1) Open terminal in the OSX VM

2) Enter the following command (no quotes) "sudo defaults delete /Library/Preferences/com.apple.windowserver.plist DisplayResolutionEnabled"

3) Enter you admin password

4) Restart the VM

 

When the VM restarts it will now go to 1600x900 and the 800x450 HiDPI setting is gone.

 

Edited by DisplayError

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 fusion71au
      Making a High Sierra USB Installer Entirely From Scratch in Windows
      This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ).  @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet...
       

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

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

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

      My build:
       
      Intel i7 8700K Gigabyte Aorus Z370 Ultra Gaming 2.0-OP Gigabyte Aorus Radeon RX570 4G Corsair Vengeance LPX 32GB (2x 16GB) Samsung 970 Evo 500GB be quiet! Silent Base 600 be quiet! Dark Rock Pro 4 be quiet! Dark Power Pro 11 550W I've tried creating an install USB using this vanilla guide: https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/
      I seem to get to about 50% loading the installer. Then it will get kernel panic.

      Trying with macos 10.14.2.

      Here's a video of what happens: https://nizzlay.stackstorage.com/s/4r71CXWCenNCgX9
       


      Any advice would be greatly appreciated!
    • By ITzTravelInTime
      Hi guys, this thread is to show you a new and open source app, created by me, that I called TINU:
       
      The name means: TINU Is Not #####, the U refers to a popular software that is used to create macOS hackintosh installers (that for good reasons is banned on this forum), but the aim of the name is to explain that this app is a totally different thing from that software and works in a totally different way.
       
      This app basically is a graphical interface for the createinstallmedia executable that is inside the macOS and Mac OS X installer apps, it is capable to create a bootable installer completely vanilla like what you do using the command line method, and also this method is recommended by apple itself. In addition to this, this app provvides to you simplicity and flexybility, and lets you to avoid most of the steps needed with every other app.
       
      TINU allows you to create easily a bootable macOS installer without messing around with command line stuff and without using disk utility, all you need to do is use the app and then install clover on the usb drive once TINU has finished or leave it as is if you want to use it on a real Mac.
       
      Features:
      - Simple-to-use UI that allows you to easily start the bootable macOS installer creation process.
      - It can work with every macOS installer app that has the createinstallmedia executable inside its resources folder (including also beta and newly released installers).
      - You can use any erasable volume that is at least 7 GB of size (if the volume's drive is not in GUID format, TINU will re-format it accordingly).
      - Can work with the Mac OS recovery system, so you can create a bootable macOS installer from the macOS installer itself or from the macOS recovery partition, and you can use TINU to install macOS, too.
      - 100% clean: The bootable macOS installers created with this tool are vanilla, just as if you created them using the command line "createinstallmedia" method in Terminal.
      - Open Source: You can verify what this program does on your computer and you can create your own version by downloading and playing with the source code.
      - Does not require any special preparations. Just open the program, make sure you have a USB drive plugged in and have a macOS installer app on your disk.
      - No need to use Disk Utility. TINU can format your drive or partition for you.
      - Integrated EFI partition mounter tool.
      - Uses recent, modern, APIs and SDKs and the Swift 3 language.
      - Transparent graphics style available (type alt-S or choose from the menu bar: View -> Use transparent style).
      - Works using the latest versions of macOS and will also support newer Mac installers out of the box without requiring an update.
      - Offers advanced features to customize your bootable macOS installer.
       
      Features that are planned for future versions:
      - Install and configure [Clover](https://sourceforge.net/projects/cloverefiboot/).
      - Install kexts into Clover's kexts folder.
      - Clover drivers customization
      - Use custom DSDT in Clover
      - Integrated pre-made Clover config templates database from a remote and open repository.
      - Support for other languages, at least Italian.
       
      # Requirements:
      - A computer that runs Mac OS X Yosemite or a more recent version (Mac OS X El Capitan is required to use TINU in a macOS recovery or installer).
      - A drive or a free partition (on a drive which already supports GUID) of least 7 GB that you want to turn into a macOS/Mac OS X installer.
      - A copy of a macOS/Mac OS X installer app (Maveriks or newer versions are supported) in the /Applications folder or in the root of any storage drive on your machine (excepted the drive or volume you want to turn into your macOS install media).
       
      Download:
      https://github.com/ITzTravelInTime/TINU/releases

      Frequently asked questions:
      https://github.com/ITzTravelInTime/TINU/wiki/FAQs
       
      Useful links:
      Thread (english) on insanelymac.com:
      - http://www.insanelymac.com/forum/topic/326959-tinu-the-macos-installer-creator-app-mac-app/
      Thread (italian) on insanelymac.com:
      - https://www.insanelymac.com/forum/topic/333261-tinu-app-per-creare-chiavette-di-installazione-di-macos-thread-in-italiano/
      Thread (english-german) on hackintosh-forum.de:
      - https://www.hackintosh-forum.de/index.php/Thread/33630-TINU/
      Post on Reddit:
      - https://www.reddit.com/r/hackintosh/comments/a1h61d/tinu_vanilla_bootable_macos_installer_creation/
      Facebook hackintosh help and beta testing (Italian only):
      - https://www.facebook.com/groups/Italia.hackintosh/?fref=ts
      Contact me (project creator):
      - Insanelymac.com profile: http://www.insanelymac.com/forum/user/1390153-itztravelintime/
      - email: piecaruso97@gmail.com
       
      Note that:
      - This software is under GNU GPL v3 license so any new branch/mod/third party release must be open source and under the same license
      - I (project creator) assume no responsibility for any use of this app and this source code, and also for any kind of hardware and software damage to any computer and any device or peripheral that may come from this app or source code during it's use and outside it's usage
      - I (project creator) do not guarantee support to you, this is only an open source project, not a product released by a company!
      - This project is born only for educational and demonstrative purposes, it's not intended to be used for commercial purposes and it will never be, don't use source code from this project to create apps or software for that aim.
      - This is a no-profit project, born only to let people to create macOS install medias in a more simple way and also to learn how to create this kind of apps.
       
      Credits:
      - Apple for macos and installer apps and scripts
      - People that helped me a lot:
      Francesco Perchiazzi, Nicola Tomarelli, Roberto Sciortino, Raffaele Sonnessa, Ermanno Nicoletti, Tommaso Dimatore, Michele Vitiello Bonaventura, Massimiliano Faralli, Davide Dessì, Giorgio Dall'Aglio, Peter Paul Chato.   
      - Special thanks to Italian Hackintosh group!! for help (https://www.facebook.com/groups/Italia.hackintosh/?fref=ts)
      - Thomas Tempelmann for help with the UI
      - Pietro Caruso (ITzTravelInTime) for creating, maintaing and developing this project
       
       
         
    • By fusion71au
      Clover r4799 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.14 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4799 for VMware.zip". Mount Clover-v2.4k-4799-X64 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.
×