Gaetano97
Pattern Recognition Developer
LEVEL 1
300 XP
Host System Information (my desktop)
Quick Tutorial on getting El Capitan to run on Virtualbox (May be applicable to other cracked OS X variants such as iAtkos and Niresh)
Firstly you want to start off by creating your virtual machine to get it prepared for the next step.
Now you want to create a batch file in your Virtualbox installation directory with the following code:
This batch file must be ran as administrator unless you installed Virtualbox in a directory that doesn't require administrative privileges to execute data. (Your documents directory should suffice)
Now you can start up your virtual machine and it should be fine for getting OS X installed. (Everything afterwards can be a gamble)
Ways to brick your OS X installation
If you update your OS X installation (perhaps you want to download Xcode or something) you run a major risk of ruining your OS X installation as the updates may patch out the cracking method implemented in your copy of Niresh or iAtkos.
Another way to brick your OS X installation is by adding unnecessary kexts to it. (Rule of thumb: If you don't know what you're doing, then don't run the risk by installing addons/kexts that could brick your OS X installation)
You can also encounter numerous kernel panics in your OS X installation. A kernel panic is essentially when the OS runs a set of instructions that were designed to operate on specific hardware that can't be emulated with your hardware setup. The result is a system halt to prevent possible damages.
You can get a kernel panic by opening iChat as it's unlikely that you would have the webcam designed to operate with the system you're emulating.
You can get a kernel panic by opening Safari which occurs for reasons I don't know.
You can get a kernel panic by not putting the correct bootflags in when you start up your hackintosh. (The method I use doesn't require any bootflags to function and is the most stable hackintosh experience I've had in years)
What hackintosh release am I using for this guide?
It's an ISO named
It's the most stable hackintosh experience I've had because it doesn't kernel panic when messing with Safari and it doesn't brick the OS X installation when updating to 10.11.6 (I've had the same level of success twice thus far with this release)
How about some visual proof?
What about the benchmarks?
So I did 4 benchmark runs using the latest version of Geekbench for Mac OS X.
It's clear that the winner was the Quad-Core with 4 GB of RAM but I wouldn't recommend that setup if you're running with 8 GB of RAM (about 7.4 when you factor in the host system's minimum requirements)
The change between 4 GB and 2 GB of RAM is negligible to nobody's surprise.
The multi-core score increases ~3000 when bumping it up by +2 cores on the i5-4690k (From my current installation)
I'm also running this virtual machine from my SSD which I don't have any benchmarks on how the SSD affects the virtual machine in terms of performance.
Video Recording of the Virtual Machine in action
Edited by ilkrProlapse, 18 February 2017 - 05:51 AM.
Code:
CPU: Intel Core i5-4690K @ 3.50 GHz
GPU: EVGA GeForce GTX 750 Ti SC
RAM: 1x8 GB 1600 MHz DDR3 RAM recycled from defunct ASUS M11BB Essentio desktop from 2013
SSD: 250GB Samsung SSD 850 EVO
HDD: 1000GB 7200RPM HDD recycled from defunct ASUS M11BB Essentio desktop from 2013
PSU: EVGA 80+ 500W Non-Modular
System Cost: ~$800 in December 2015 (without the cost of RAM and both the SSD and HDD)Firstly you want to start off by creating your virtual machine to get it prepared for the next step.
Now you want to create a batch file in your Virtualbox installation directory with the following code:
Code:
@ off
pushd %~dp0
VBoxManage.exe modifyvm "<YOUR VM NAME HERE>" --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
VBoxManage setextradata "<YOUR VM NAME HERE>" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3"
VBoxManage setextradata "<YOUR VM NAME HERE>" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
VBoxManage setextradata "<YOUR VM NAME HERE>" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "0123456789"
VBoxManage setextradata "<YOUR VM NAME HERE>" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "nulled"
VBoxManage setextradata "<YOUR VM NAME HERE>" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1
popd
pauseNow you can start up your virtual machine and it should be fine for getting OS X installed. (Everything afterwards can be a gamble)
Ways to brick your OS X installation
If you update your OS X installation (perhaps you want to download Xcode or something) you run a major risk of ruining your OS X installation as the updates may patch out the cracking method implemented in your copy of Niresh or iAtkos.
Another way to brick your OS X installation is by adding unnecessary kexts to it. (Rule of thumb: If you don't know what you're doing, then don't run the risk by installing addons/kexts that could brick your OS X installation)
You can also encounter numerous kernel panics in your OS X installation. A kernel panic is essentially when the OS runs a set of instructions that were designed to operate on specific hardware that can't be emulated with your hardware setup. The result is a system halt to prevent possible damages.
You can get a kernel panic by opening iChat as it's unlikely that you would have the webcam designed to operate with the system you're emulating.
You can get a kernel panic by opening Safari which occurs for reasons I don't know.
You can get a kernel panic by not putting the correct bootflags in when you start up your hackintosh. (The method I use doesn't require any bootflags to function and is the most stable hackintosh experience I've had in years)
What hackintosh release am I using for this guide?
It's an ISO named
Code:
{DevHackers} OS X El Capitan 10.11.4.isoHow about some visual proof?
What about the benchmarks?
So I did 4 benchmark runs using the latest version of Geekbench for Mac OS X.
- 4 Cores w/ 4 GB of RAM
- 4 Cores w/ 2 GB of RAM
- 2 Cores w/ 4 GB of RAM
- 2 Cores w/ 2 GB of RAM
It's clear that the winner was the Quad-Core with 4 GB of RAM but I wouldn't recommend that setup if you're running with 8 GB of RAM (about 7.4 when you factor in the host system's minimum requirements)
The change between 4 GB and 2 GB of RAM is negligible to nobody's surprise.
The multi-core score increases ~3000 when bumping it up by +2 cores on the i5-4690k (From my current installation)
I'm also running this virtual machine from my SSD which I don't have any benchmarks on how the SSD affects the virtual machine in terms of performance.
Video Recording of the Virtual Machine in action