Recently Browsing 1 member
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
@Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
VirtualBox Forum: Status of OSX on OSX
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...
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)
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.
Good luck and enjoy
Hi guys, I've been lurking in the shadows for months trying to learn how to hackintosh this laptop. Perhaps if anyone has the time, I could use some help getting it to install
Trying to install High Sierra on this Laptop:
Lenovo Ideapad 110-171KB-80VK (2017)
Intel Core i5 7200U
Intel HD 620 Graphics
Elan PS2 Track Pad - [ACPI\VEN_ETD&DEV_0675 - system device -PCI\VEN_8086&DEV_9D23&SUBSYS_383117AA&REV_21]
Realtek Network - [PCI\VEN_10EC&DEV_8136&SUBSYS_383317AA&REV_07]
SATA Controller - [PCI\VEN_8086&DEV_9D03&SUBSYS_382F17AA&REV_21]
USB 3.0 XHC - [PCI\VEN_808
--- Using Clover *
--- I'll attach it below.
I can't quite get it to install, and i've been going in circles for months now ...
I'll attach everything I have so far including, verbose pics, clover preboot, Clover folder, etc.
Here are some photos of the verbose text leading up to the installer, if maybe there is something useful in here?
And now photos of the installer
Above is an image of the Installer log, (the main pop up window loads from about 10 mins and stops arbitrarily at 2 minutes left, every time) of the nearly hundred attempts i have made, this is the final screen i get, pretty much no matter what i do.
Sometimes the the order of what it says is different , but the main things of interest are:
"Target is not convertible to APFS: This volume is not formatted as Mac OS Extended journaled."
"Warning: Couldn't find Board ID, Chip ID, & ECID in new namespace, falling back"
"Unable to get fs for null"
" NO native mechanism to verify Applediagnostics.chunklist"
" NO native mechanism to verify Installfa.plist"
" NO native mechanism to verify Basesystem.dmg"
" NO native mechanism to verify AppleDiagnostics.dmg"
" NO native mechanism to verify InstallESD.dmg"
" NO native mechanism to verify Basesystem.chumklist"
I have tried many many ... many .. different combinations of kexts, drivers, copies of clover, forks of clover - different copies of drivers and kexts from different sources.. including from all the official repositories.
* I am not trying to install with APFS - the drive i am using is a spinning HDD - so i don't understand the first line quote above.
* I am using a usb2 slot - there is only two on this machine - 1- usb2 and 1- usb3
* As you'll see in the Clover folder i'm using APFSdriverloader. - so the installer should detect the installer-APFS-thing - and see it should be HFS+ ?? no?
I'll detail the procedures:
I wiped the Target HDD drive with a live linux USB.
i prepair the USB with Createinstallmedia method, install clover to the EFI on usb, load kexts and drivers (I've been recently attempting with the Plist from a 'certain other site' Ton*****86) As it has the dvmt preallocation patch and other bits - i'm of course open to ANY other files/pLists .. this is just the one i've been experimenting with lately.)
Add ' -v ' in clover options to see the verbose output
in the installer (acts sketchy sorta, delayed and sluggish) i use DiskUtility to erase the drive 'Macos extended journaled'
Make initial selections, agree to license and begin install.
it proceeds to 2 minutes left every time, and hangs. many times i've left it for hours, and even overnight.
I'm honestly not kidding, it's nearly 100 times ive' tried this, i've downloaded high sierra from the app store 5 times to rule out that, i've used countless combinations of everything .. i'm almost completely burned out.
If anyone can shed some light i'll be VERY thankful!... I'm ready to go in a completely new direction...please please please help
I'll put the Clover in the next post because i ran out of space in this one......
Here is the latest clover i've been using, with the preboot, and DSDT/SSDT (F2 & F4) in it.
Thank you very much for ANY help you can provide
By Luan Eduardo
Installing macOS Mojave 10.14 on Gigabyte Z370N WIFI + i7 8700K + UHD 630
10/11/2018 04:15h GMT-0
- Added USB 3.0 patch.
- Adjusted some steps.
- Changed text formatting.
10/11/2018 03:42h GMT-0
- Added missing UEFI configuration.
10/07/2018 00:36h GMT-0
- First version.
What works and what does not
- Processor -> Work. All SpeedStep stages.
- Video Card -> Work. QE/CI and Metal.
- Chipset -> Work.
- HDMI (1st) -> Work.
- HDMI (2nd) -> Work.
- DP -> Not tested.
- Audio -> Not work.
- WiFi/Bluetooth -> Not work.
- Ethernet (1st) -> Work.
- Ethernet (2nd) -> Not work.
- USB3.0 -> Work.
- Sleep -> Work.
- Make audio work.
- Make HDMI audio work.
- Test DisplayPort.
- Make second ethernet work.
- Replace Wifi/Bluetooth.
What you need to install
- Running install of macOS
- One USB flash drive of 8GB or bigger
- macOS Mojave install app
- Clover EFI
- Clover Configurator
- Some KEXTs
How create create the install flash drive
Prepare install flash drive
Format the flash drive with GUID partition mapping and name it "Install".
- Open Disk Utility.
- Click in View, then "Show All Devices".
- Select the destination flash drive, then Erase.
- Name: Install, Format: Mac OS Extended (Journaled) and Scheme: GUID Partition Map
Create install flash drive
Open terminal and run this command:
sudo /Applications/Install\ macOS\ .app/Contents/Resources/createinstallmedia --volume /Volumes/Install--nointeraction This will take about 30 minutes.
Download the CloverEFI (used 4674) and install with this options on "Install macOS Mojave":
- Install for UEFI booting only
- Install Clover in the ESP
- UEFI Drivers - ApfsDriverLoader-64
- UEFI Drivers - AptioMemoryFix64
Make things works
Will be created a partition named EFI and mounted in Desktop. Edit the /Volumes/EFI/CLOVER/config.plist inside this new partition, open with Clover Configurator (used 22.214.171.124)
Full UHD630 Acceleration
config.plist (Clover Configurator):
- Uncheck: Acpi - Fixes - FixDisplay
- Uncheck: Acpi - Fixes - AddHDMI
- Add value: Devices - Properties - Devices*: PciRoot(0x0)/Pci(0x2,0x0)
- Add value: Devices - Properties - Devices* - PciRoot(0x0)/Pci(0x2,0x0):
Propertie Key: framebuffer-patch-enable
Propertie Value: 01000000
Propertie Key: AAPL,ig-platform-id
Propertie Value: 07009B3E
- Change value: Gui - Screen Resolution to 3840x2160 (Your screen resolution, mine is 4k)
- Change value: Rt Variables - CsrActiveConfig to 0x3
- Select value: SMBIOS - Up/Down arrows - iMac18,1 - Intel Core i5-7360U @ 2.30Ghz (I know, it's not our processor, but is that option)
Download those Kexts and put in /EFI/CLOVER/kexts/10.14/
- Download the Lilu.kext from here. I used the version 1.2.7.
- Download the WhateverGreen.kext. I used the version 1.2.3.RELEASE.
All USBs (2.0, 3.0, Type-C, internal)
config.plist (Clover Configurator):
- Add value: Kernel and Kext Patches - KextsToPatch:
Find* [HEX]: 83FB0F0F 83030500 00
Replace* [HEX]: 83FB0F90 90909090 90
Comment: disable port limit in XHCI kext (credit PMHeart)
config.plist (Clover Configurator):
- Check: Boot - Arguments - dart=0
Download those Kexts and put in /EFI/CLOVER/kexts/10.14/
- Download the FakeSMC.kext from here. I used the version 2018-0915.
- Download the IntelMausiEthernet.kext from here. I used the version 2018-0424.
Put the Clover installer on the flash drive too.
Now you can start the instalation without problem (I guess).
UEFI Setup Configuration and Installation
- Shutdown and insert the flash.
- Power on with DEL pressed to enter BIOS setup.
- Change value: Periphelrals - Initial Display to IGP
- Change value: Periphelrals - USB Configuration - XHCI Hand-off to ENABLE
- Change value: Chipset - VT-d to DISABLE
- Change value: Chipset - Internal Graphics to ENABLE
- Change value: Chipset - DVMT Pre-Allocated to 128M
- Change value: Chipset - Wake On Lan to DISABLE
- Save & Exit Setup
- Now, hold the F12
- In the list, select your flash drive.
- It will show twice. One with UEFI prefix and another without.
- Select with UEFI prefix. Ie.: "UEFI: Sandisk Cruzer"
The installer will start.
Format destination disk
Format the disk with GUID partition mapping and name it "HD".
- Select Disk Utility in the list, then press Continue.
- Click in View, then "Show All Devices".
- Select the destination Disk, then Erase.
- Name: HD, Format: APFS and Scheme: GUID Partition Map
Close Disk Utility.
Select "Install macOS", then Continue.
Follow instructions in screen.
After first part install the system will reboot.
The second part of the installation will begin. This will take 16 minutes.
When the second part of install finish, the system will reboot again.
After performing the user initial setup and go to the desktop, you need to install Clover on internal disk.
Open the Clover installer inside flash drive that you copied before.
Use same options above but choose the system partition this time.
Now you need to replace the config.plist inside your destination disk EFI parittion with config.plist inside flash card EFI partition.
The flash drive EFI partition is unmounted. Mount with terminal "sudo diskutil mount /dev/rdiskXs1". To know what X is, use "diskutil list", most likely is 1.
Copy all Kexts from flash drive to /Library/Extensions, with those commands in Terminal:
sudo cp -R /Volumes/EFI/EFI/CLOVER/kexts/10.14/* /Library/Extensions/ sudo chmod -Rf 755 /Library/Extensions sudo chown -Rf 0:0 /Library/Extensions sudo kextcache -system-prelinked-kernel sudo kextcache -system-caches Restart the system.
And last but not least
I would like to thank the following community members, by making these dream possible:
@crushers, @snatch, @apianti, @blackosx, @blusseau, @dmazar, @slice2009, @autumnrain, @phpdev32, @EMlyDinEsH, @RehabMan, @Scellow, @mitch_de, @Shailua, @Andy Vandijck, @maxfierke, @ArturXXX, @LexHimself, @brumas and all others members involved directly or indirectly.
So, this little tutorial is meant to help people fix a new issue with Mojave: opening jpg files (looks like it happens with larger files, not so much with smaller ones) using Quick Look (on spacebar key pressed) or Preview app using the dedicated GPUs.
The issue is that, when trying to open jpg files (for some reason, it doesn't occur with pngs), the pop-up window would remain in an endless loop. And from that point forward, any other app trying to open the same file, will either become unresponsive (in the case of the Preview app) or just stay in endless loop (in case of Quick Look)
As a workaround, in case the tutorial below doesn't work for you, you can use Grab (built-in app in MacOS) to open said files.
This issues DOES NOT occur using the iGPU. So...if you're comfortable using the iGPU, just switch to that and you should be good to go. You don't need this tutorial.
This tutorial is based on @Cyberdevs' research and testing on this topic (especially useful if you're using an RX series AMD video card), and my own very limited time testing this on my rig. I just thought it would be useful to create a new thread for it so that people can discuss this particular issue here.
With that being said, I'll just move on to the actual tutorial.
New (probably better) method.
Switch your SMBIOS in Clover config in regards to the dedicated GPU you're using, instead of the CPU. Take a look here and choose the corresponding SMBIOS closest to your hardware.
Yeah, that's it.
In case you lose CPU PM with this method, there are multiple ways to fix that, and they do not make the object of this thread. It worked perfectly fine for me though and I didn't need to change anything else.
A simple Lilu plugin
Thanks to vulgo for the plugin and @Matgen84 for sharing and testing it, we now have yet another possible solution to this issue. It's a Lilu plugin (which means that it requires Lilu.kext in order to work) it's called NoVPAJpeg, and it can be downloaded from here.
You use it as a regular kext, alongside Lilu. I prefer (and recommend) using it within the EFI folder, in Clover/kexts/Other. But if you want to use it in S/L/E, that should work just fine.
More info can be found in this post here.
In case you wanna try alternative medicine ...
The main thing we need to do is actually very simple: we need to enable the iGPU (integrated GPU) by default, in BIOS, while actually being connected to the dedicated GPU.
For ATI GPUs (curtesy of @Cyberdevs' post here).
The discreet GPU should be set as primary in BIOS and your displays should be connected to your discreet GPU
The iGD/iGPU/iGFX must be enabled in BIOS/UEFI as the secondary GPU.
I removed the DSDT Reconfigured the config.plist to and removed some flags which weren't needed because of the DSDT added the InjectATI + Ornioco Framebuffer (I removed the Orinoco framebuffer because of some weird glitches but it might be useful for other AMD GPUs if you inject the correct framebuffer according to your GPU. No need to inject anything for nVidia GPUs unless your GPU needs it) Added the InjectIntel + ig-platform-id for my intel HD530 (for intel HD 530 I use the 0x19120001 ig-platform-id)
Steps 5 to 7 might not be necessary I just did them anyway, if anyone succeeded to get quicklook working without those steps let me know so I can exclude those steps.
Also confirmed to work with AMD R9 270X on a SandyBridge rig (without an iGPU) using WhateverGreen + Lilu kexts, which also helped to solve the transparency issue along with the Quick Look problem, it also resolved the buggy Screen Capture (Command+Shift+5) issue as well.
nvram cleanup kextcache & prelinked kernel rebuild reboot More info on that here.
For NVIDIA GPUs
This is what I needed for my NVIDIA rig and the MSI motherboard in the signature. Your milage may vary, depending on your hardware. But, the idea should be the same regardless.
For MSi motherboads (check out my motherboard details in the signature)
Set your BIOS to use PEG (dedicated GPU) so you can boot.
Since you're reading this, chances are that you're already connected to the dedicated GPU and the BIOS is set to PEG. So just go into BIOS and see if you're using the iGPU or the dedicated (PEG) graphics device by default.
If you're already using this, skip to Step 3 (the part AFTER Reboot). Reboot (I think you don't necessarily need to boot into the OS...but you do need to reboot at least until Clover UI) Reboot back into BIOS and set it from PEG to IGD (integrated graphics) WITHOUT removing the cable. Save Reboot again.
The result should be that the OS is tricked into thinking you're booting with the IGPU when in fact you're using the dedicated GPU.
For Gigabyte motherboards
Peripherals -> Initial Display Output -> iGFX Chipset -> Internal Graphics -> Enabled
DVMT Pre-Allocation -> default 64M.
DVMT Total Gfx Mem -> default 256M Save Reboot
You should do this with the cable connected to the dedicated GPU.
You will also need to patch the iGPU from Clover config.
1. Graphics -> Inject Intel (UNCHECK Inject Nvidia or ATI if it's checked).
2. ig-platform-id (in my case for Intel HD 4600 Desktop) it was: 0x0d220003
And use IntelGraphicsFixup.kext (now included into WhateverGreen.kext) in Clover/kexts/Other. In my particular case, without the kext, I would get freezes in Safari.
This might be a bug with Mojave and it could be fixed by Apple in the future. but in the meantime, feel free to use this if it helps you fix the issue.
For HP motherboards (including laptops), so far no solution, unless the BIOS somehow allows to switch from eGPU to iGPU and vice-versa.
After a long run, I successfully upgraded High Sierra to mojave 10.14 on an intel 5 series chipset MotherBoard.
GPU1: Saphire AMD RX 460
GPU2: Nvidia 8400GS
Storage: 500 GB HDD WD Green.
1) macOS pre mojave.
2) macOS mojave installer from Apple store.
3) Empty partition or USB to upgrade from.
4) Un-mout all unused dmgs.
5) GPT/GUID HDD.
1) Prepare an empty partition or USB with at least 6 GB.
2) Format the partition or USB with GUID partition table and HFS+ partition with a name BootablePartition.
3) Go to /Application/Install macOS High Sierra.app.
4) Show Package Contents.
5) Go to Contents/SharedSupport you will find BaseSystem.dmg.
6) Double click on BaseSystem.dmg to mount.
7) From Disk Utilty click on your partition or the USB that you prepared from number (2).
8) Click on restore, and chose OS X Base System (BaseSystem.dmg image), then restore it to that partition or USB.
9) After restoring rename the partition back to BootablePartition.
9) Run this command:
rm -rfv /Volumes/BootablePartition/System/Installation/Packages 10) Create a new folder instead of the broken link and name it Packages, run this command:
mkdir -v /Volumes/BootablePartition/System/Installation/Packages 11) Go back to /Application/Install macOS High Sierra.app and repeat number 2.
12) Go to Contents/SharedSupport you will find InstallESD.dmg.
13) Mount InstallESD.dmg.
14) Run this command:
cp -v /Volumes/InstallESD/Packages/OSInstall.mpkg /Volumes/BootablePartition/System/Installation/Packages/ 15) Download the latest clover from https://sourceforge.net/projects/cloverefiboot/
16) Install clover on your USB BootablePartition or in a different USB to boot from it. delete all your CLOVER/kext/10.xx and keep others, make sure you don't have any extra kext rather than FakeSMC.kext in the other folder.
in my case I used FakeSMC.kext and my lan kext RealtekRTL8111.kext.
17) known Problems in my build:
If I updated directly from the apple store the installer in clover will boot with a cross circle sign.
The FIX is to add this to Clover KextToPatch Thanks to @sunKi http://www.insanelymac.com/forum/topic/327488-macos-high-sierra-final-release-is-out-17a365/page-10?do=findComment&comment=2505086 this fix is still working for me in mojave.
<key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>fix IO error ICH10 for 10.13, credit SunKi</string> <key>Disabled</key> <false/> <key>Find</key> <data> RYX2D5XCiciD4P5mhcl4D4TSdQs= </data> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data> iciD4P5mhckPmMFBCMyQkJCQdQs= </data> </dict> <dict> <key>Comment</key> <string>fix hotplug ICH10 for 10.13, credit SunKi</string> <key>Disabled</key> <false/> <key>Find</key> <data> icglQGACAD1AIAAAdQyB4b9///+Ji1EBAAA= </data> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data> kJCQkJCQkJCQkJCQkJCQkJCQkJCQkJCQkJA= </data> </dict> <dict> <key>Comment</key> <string>External icons patch</string> <key>Disabled</key> <false/> <key>Find</key> <data> RXh0ZXJuYWw= </data> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data> SW50ZXJuYWw= </data> </dict> </array> 18) make sure you have apfs.efi copy it from /Volumes/BootablePartition/usr/standalone/i386/apfs.efi to your EFI/CLOVER/drivers64/ and EFI/CLOVER/drivers64UEFI/.
19) SMBIOS mac model that I use is iMac13,2.
20) Go to /Application/Install macOS High Sierra.app click on it and chose to install to your macOS High Sierra partition.
22) From clover chose BootablePartion.
23) If everything is okie BootablePartition will boot to install macOS mojave, wait wait wait till it finish it might take to 1 hour just wait it will reach the auto reboot soon .
24) Boot to your old macOS Hight Sierra that will be your mojave partition now and enjoy.
a) Download Lilu.kext and AppleALC.kext or build them from source (which I did).
b) place them in your /EFI/CLOVER/kext/others/
c) add your audio layout in clover/Devices dict options in my case it's ALC888B which has the layout of 1:
<key>Audio</key> <dict> <key>Inject</key> <string>1</string> </dict> d) I had to add beta args to clover/Boot dict, argument (-lilubeta -alcbeta):
<key>Arguments</key> <string>-lilubeta -alcbeta</string> 2) Add number 14 KextsToPath array to your clover as well.
Anything else is working for me I didn't need any extra clover kext so far, I tried whatevergreen.kext to fire up my rx 460 without the helper card but no success, So I am just sticking with booting from Nvidia as a first GPU from my motherboard configuration then swap the cables after choosing my macOS partion from clover.
After upgrading my HFS+ High Sierra partition converted to APFS, no know problem so far.
Happy build and more info about the partitioning method with a more detailed instructions in this post that I used to update my Sierra to High Sierra
Special thanks to crazybirdy, sunKi and all of you out there that make this happens.