Hackintosh Boot Flags

In the Boot Args section of Clover, enter the boot flags.

If this is your first time building or making a Hackintosh, boot flags may seem like a foreign concept. Once you understand what each of them means, you can get started!

Clover Boot Flags:

An example of verbose mode. When the computer hangs (stops), the last message you see is the message you should search to find a solution. 

Verbose Mode:

 -v 

Safe Mode:

 -x 

Single User Mode:

 -s 

 Zone Postponing: (use if hanging)

 -no-zp 

Single CPU core mode:

 cpus=1 

No Kext Cache Mode: (When changing kexts)

 -f 

Disables VT-x or VT-d:

 dart=0 

Verbose Mode:

 -v 

Enable NVIDIA Web Drivers: (do not use with nv_disable=1)

 nvda_drv=1  

Disable NVIDIA graphics cards: (do not use with nvda_drv=1)

 nv_disable=1 

Kext Dev Mode:

 kext-dev-mode=1 

Rootless Mode: 

Do not boot with this on El Capitan or macOS Sierra

 rootless=0 

  

If you're stuck at [PCI Configuration Began]:

 npci=0x2000 

 npci=0x3000 

Set Maximum Memory (RAM): (In megabytes)

 maxmem=4096 

 maxmem=8192 

Troubleshooting:

If you are having any trouble, first try this string. It works on a lot of systems with Intel HD Graphics to get into the OS X Installer from a Unibeast USB.

 -v -x -s -no-zp 

If you have an NVIDIA Desktop GPU, use this string to boot into the installer:

 -v -x -s nv_disable=1 

If all else fails, or you don't know where to start, use this string:

 -v -x -s -f cpus=1 maxmem=4096 nv_disable=1 -no-zp 

If you have an NVIDIA Desktop GPU and you've installed NVIDIA Web Drivers (Link), use this string:

 -v nvda_drv=1  + your bootflags (do not use nv_disable=1)

Common Issues:

If in verbose mode, a message about [IOBluetoothHCIController][start] -- completed or something similar appears, it normally has to do with a graphics issue. If you have an NVIDIA or AMD GPU, use nv_disable=1 and it should boot. Otherwise, boot into safe mode.

Comment any issues you have and I could recommend you a set of bootflags to use!

Source : http://www.fitzweekly.com

Bootloader should be selected for hackintosh me ??

Wemakeitsimple - Chameleon, Chimera or Clover. What are they? Who’s better than the other? I will explain that to you so you can make the right decision. Let’s begin:

Chameleon is an open-source project created on May 25, 2008 based on Apple’s Boot-132 which aims to create a Darwin/XNU bootloader able to boot OS X on ordinary x86 and x86_64 computers. Chameleon’s source code is organized using the SVN (Subversion control system) and maintained by the Voodoo team. Since it’s an open-source project anyone can edit and view the code to make adjustments, fix bugs and add new features to it.

Chimera, made by MacMan and the folks of tonymacx86.com on April 27, 2011, is a open-source bootloader based on Chameleon. The reason MacMan created Chimera was the fact that there were too many different versions of Chameleon [called “Branches”] each with it’s own purpose and/or patches for different hardware support. So Chimera is a Chameleon version which consolidates the best features from all of the available branches to obtain maximum compatibility across platforms as a result. It can be installed only by using MultiBeast, so if you followed tonymacx86’s guides you’ll will have Chimera by 100%. Chimera’s source code is available here.

Clover is an open-source EFI-based bootloader created on Apr 4, 2011. It has a totally different approach from Chameleon and Chimera, in fact it can emulate the EFI portion present on real macs and boot the OS from there instead of using the regular legacy BIOS approach used by Chameleon and Chimera. For many Clover is considered the next-gen bootloader and soon it will become the only choice since BIOS in being replaced by UEFI in every new motherboard. One big feature of Clover is that iMessage, iCloud, the Mac App Store works along with Find My Mac, Back To My Mac and FileVault since Clover can use the EFI partition. Clover on the other hand has 2 big downsides:

1. It needs a UEFI motherboard to work properly and to do it’s magic.
   Sure, there’s a BIOS option you can select to make it work on old computers but OS X features like Back To My Mac, Find My Mac, FileVault won’t work if you don’t use an UEFI motherboard.
2. It’s a pain to configure since its documentation is just a little wiki and the community behind it it’s not as big as Chameleon and Chimera’s ones.
   If you have a problem you can still try asking someone on the official Clover forum but if no one will reply or they won’t fix your problem it’s on your own.

So, those are the bootloaders but the questions still is: which one? Well choosing the right bootloader for your Hackintosh is crucial to make it work perfectly so you should choose it wisely.

The first thing I suggest you is to try Chimera, it’s the easiest of the three and it has a big community behind so if you need help there always be someone to ask, in addition you can use the tonymacx86’s “Buyers Guide” which contains various builds which works perfectly with the latests OS X versions and updates and those are all supported by Chimera.
The second thing I suggest you is to try Chameleon after you already tried Chimera and everything works fine with your system. In fact even if Chimera is easier than Chameleon it is more powerful and it’s updated more ofter than Chimera, also you can use the wonderful Chameleon Wizard to configure it in any aspect [Boot flags, SMBios, DSDT, etc.] so I suggest you to change Chimera for it.
The third and last thing I suggest you is to try Clover to enable those real-mac-only features, but only if you know what your doing because it can be really easy to break your Hackintosh with it.

Source : https://giuliomac.wordpress.com/2014/02/20/which-bootloader-should-i-choose-for-my-hackintosh/

Tags : hackintosh boot loader, hackintosh boot loader download, hackintosh boot loader error, install bootloader hackintosh, hackintosh dual bootloader, hackintosh change boot loader, best hackintosh bootloader, hackintosh boot without bootloader, hackintosh no bootloader, hackintosh yosemite bootloader

How to set extra boot flags/options/arguments for Clover bootloader

Wemakeitsimple - Starting up Mac OS X for the first time on your Hackintosh can be a very tricky process, which often requires you to set special boot options through the use of boot flags. For those of you who don't know, boot flags are "arguments" (pieces of data that you enter) to change the way that your bootloader runs. The bootloader is the program that boots Mac OS X.

While we've already previously discussed how to use boot flags on the Chameleon and Chimera bootloaders, which were formally the two most popular bootloaders for PCs running Mac OS X, the release of OS X El Capitan has now shifted attention onto the new and upcoming Clover bootloader. All Hackintosh installation methods for El Capitan, including tonymacx86's ever-popular Unibeast method, now use Clover. Unfortunately, using boot flags on Clover requires a slightly different technique than on Chameleon/Chimera (although most of the boot flags themselves remain the same). That's what this guide is here for.


How to use temporary boot flags on Clover

On Chameleon/Chimera, you could enter a temporary boot flag by simply typing it directly into your computer's bootloader menu. In contrast, the process is slightly more involved with Clover.

To enter a temporary boot flag into Clover, first start your computer and wait until you reach the Clover bootloader menu, which will look something like this (aka the Unibeast menu, assuming you installed OS X that way):

Use the arrow keys on your keyboard to select the "Options" button at the bottom of the menu (if you used Unibeast, it'll probably be the button with the picture of gears).

NOTE: There are technically two different options buttons-- one is for "Clover Options", while the other is just "Options." You want to choose "Options."

Open up the Options by press Enter on your keyboard (or Return, or the spacebar). From here, use your arrow keys to select the "Boot Args" line.

Press your spacebar, and then you'll be able to start typing the necessary boot flags. Press Enter when you're done. From here, return to the original Clover boot menu (you can press the "Esc" key on your keyboard to do this), and boot OS X again. Voila!

If you need help finding the right boot flags for your Hackintosh, check out our list of common boot flags (this list is tailored for Chameleon/Chimera, but Clover supports many of the same flags).

How to use permanent boot flags on Clover

Once you've managed to boot into your Hackintosh, you'll probably want to make those boot flags permanent, so that they'll automatically be entered into the bootloader every time you start Mac OS X. This process is also a bit more involved in Clover, compared to Chameleon/Chimera.

Traditionally, you could permanently enable certain boot flags by adding them to the text file "org.Chameleon.boot.plist," which was essentially the settings file for Chameleon/Chimera. Clover's settings rely on a similar text file called "config.plist."

However, Clover's file may be a little bit harder to work with, depending on your particular setup. So instead of editing the file directly, like we did with Chameleon/Chimera, we recommend that you download the free Clover Configurator app instead.

DOWNLOAD: Clover Configurator

Once you've downloaded it, open up the Clover Configurator app (which comes in a ZIP file). The home page of the app will display some number of seemingly identical files named "config.plist," with the exact number depending on how many hard drives your computer has.

Your actual "config.plist" file will be on your computer's EFI partition. To modify it, you first have to mount the EFI partition, which is usually hidden when you boot OS X.

To do this, click on the "Mount EFI" button on the left column. Then, in the page that comes up, click "Mount EFI partition." If you have multiple hard drives, choose the hard drive that OS X is currently booting from. In the screenshot below, Clover Configurator tells me that I'm currently booting from disk0s2, so I choose disk0s1 (because it's part of "disk0").

Once that's done, return to the homepage for Clover Configurator (by clicking the house icon on the bottom left), and click the "config.plist" icon that goes EFI -> EFI -> CLOVER -> config.plist.

Once you've selected the appropriate config.plist, a new Clover Configurator window may pop up. Click on the "Boot" tab of that new window. From here, you can select and de-select common boot flags, as well as add your own!

That's all you need to do to apply a boot flag for your Hackintosh. (Any changes made in Clover Configurator usually save automatically.) Once again, if you need help finding the right boot flags for your Hackintosh, check out our list of common boot flags.

source : http://www.macbreaker.com/2015/10/set-boot-flags-arguments-options-clover-unibeast.html

Tags: Hackintosh boot flags clover, hackintosh how to enter boot flags, how to type boot flags, hackintosh boot flags nvidia, hackintosh boot flags graphics mode

Hackintosh Boot Flags

If your Hackintosh can't boot, changing your boot options with boot flags may be your last chance at getting Mac OS X to start. If you don't know, "boot flags" are options that change the way that your bootloader (the program that boots Mac OS X) runs at startup. Read past the break for list of common boot flags for iBoot, Unibeast, Chimera, Chameleon, and more.


LAST UPDATED ON: October 27, 2014

-v
The mother of all boot flags. Entering -v into the bootloader turns on verbose mode, which is absolutely critical for fixing any Hackintosh issue. Verbose mode displays every single process that takes place during your bootup of Mac OS X. It can be rather intimidating, as it will display hundreds of lines of commands during the bootup process. However, if your Hackintosh isn't booting, then verbose mode should freeze at the exact point where the bootup process is tripping up. Take a photo of what verbose mode says when the bootup freezes. You can then post that photo on a Hackintosh forum to look for help, or check out our guide to reading verbose mode in order to figure out what the problem is on your own.

-x
Turns on safe mode. Mac OS X in safe mode ignores all kext files and boot settings except those which are absolutely necessary to booting the system. Safe mode is useful if you're trying to run the Mac OS X installer on a PC that's not fully compatible with Mac OS X. Also, if you accidentally installed a kext file that's messing up your Hackintosh, booting into safe mode may work around the problem. In safe mode, you can then remove the offending kext from /Extra/Extensions in your main hard drive (if you're running Mac OS X Snow Leopard), or /System/Library/Extensions (if you're running Mac OS X Lion, Mountain Lion, or Mavericks).

-F
If you've entered some extra boot flags into org.Chameleon.boot.plist, but they're messing up your Hackintosh's bootloader, enter the -F boot flag to ignore them.

-f
Ignores kext caches during bootup on Mac OS X Snow Leopard. If you did not install a kext properly (usually because you forgot to run System Utilities in Multibeast after installing a new kext), your kext cache will be damaged, and Mac OS X might become unbootable unless you use this boot flag. The kext cache was replaced by the kernel cache in Mac OS X Lion, so theoretically, the -f boot flag should no longer work; however, this boot flag can still help some Hackintoshes boot (for reasons unknown).

UseKernelCache=Yes
Mac OS X Lion, Mountain Lion, and Mavericks can use the kernel cache to install kexts, allowing Mac OS X to boot faster. However, the kernel cache is turned off by default, and you have to enable it by using the boot flag "UseKernelCache=Yes" (without quotation marks). Installing Easybeast, UserDSDT, or "DSDT Free Installation" with Multibeast will automatically turn the kernel cache on for you. If Mac OS X is booting extremely slowly on your Hackintosh, the kernel cache might be malfunctioning. In addition, some laptops have trouble with the kernel cache feature. In these cases, you can turn the cache off with "UseKernelCache=No" (without quotation marks). Turning off the kernel cache is equivalent to using the "-f" bootflag in Snow Leopard.

PCIRootUID=1
Some Hackintoshes will only boot when their "PCI Root ID" is set to 0. This usually happens with Hackintoshes that use a AMD Radeon graphics card. Other times, a Hackintosh will only boot when its "PCI Root ID" is set to 1. In some cases, the boot flag "PCIRootUID=1" will also fix Mac App Store verification errors.

GraphicsEnabler=No
This turns Graphics Enabler off/on (you can set "No" to "Yes"). Graphics Enabler is a feature that helps Mac OS X work better with certain graphics cards. These days, Unibeast turns off Graphics Enabler by default, since graphics cards from NVIDIA's 600 and 700 series no longer require GraphicsEnabler to work with Mac OS X. However, most other graphics cards still require Graphics Enabler to be turned on-- on these graphics cards, turning the feature off will break DVD Player, as well as Geekbench, most games, most video editors, and certain other apps.

IGPEnabler=Yes
This turns IGP Enabler on/off (you can set "Yes" to "No"). IGP Enabler is a feature similar to Graphics Enabler that helps Mac OS X work better with your integrated graphics. While Graphics Enabler will already do this normally, if you need to turn off Graphics Enabler for some reason but want to keep your integrated graphics working, use this boot flag. Specifically, this boot flag can be useful if you want to use an NVIDIA 600 or 700 series card in conjunction with your integrated graphics (e.g. when running AirPlay Mirroring).

darkwake=0
The DarkWake feature in Mac OS X Lion, Mountain Lion, and Mavericks allows you to wake up certain parts of your Mac from sleep, while leaving other parts in sleep mode. Unfortunately, this feature often messes up sleep on Hackintoshes. Enter this bootflag to turn it off (enter darkwake=1 to turn it on, if turning it off doesn't do the trick). Additionally, if your verbose bootup is freezing at a bunch of commands that mention "SleepEnabler.kext", entering darkwake=0 should be able to temporarily turn SleepEnabler.kext off. (Once you boot into OS X, be sure to remove SleepEnabler.kext completely by deleting it from either /Extra/Extensions or /System/Library/Extensions in your hard drive.)

npci=0x2000
npci=0x3000
If your verbose mode bootup of Mac OS X Lion or Mountain is freezing at [PCI Configuration Begin], enter the npci=0x3000 boot flag to fix it. This flag is applied by default when you install Easybeast, UserDSDT, or "DSDT Free Installation" with Multibeast. The boot flag npci=0x2000 does the same thing, except that it usually only works for Lion.

dart=0
Disables the VT-d virtualization technology built into certain Intel processors. For Hackintoshes, VT-d is pretty useless; virtually no Mac OS X applications use it (virtualization apps like Virtualbox tend to use the alternative VT-x technology instead), and certain Hackintosh motherboards have been known to crash in Mac OS X when VT-d is enabled.

cpus=1
Limits Mac OS X to using one core of your CPU. This boot flag is often necessary to launch the Mac OS X Snow Leopard installation DVD on a Hackintosh with an unsupported processor (ahem, AMD processors). In OS X Mountain Lion and Mavericks, you may also have to use this boot flag if your computer uses a high-end Intel processor on LGA 2011.

busratio=20
The 20 is replaced with your CPU's bus ratio. This boot flag is usually used when you're installing Mac OS X Snow Leopard on a processor that's not supported (once again, AMD processors). Snow Leopard supports more processors than it used to, so this boot flag isn't as common as before. You can find a list of busratios for 2010-model Intel processors here. You can also find your busratio manually.

arch=i386
Forces Mac OS X to boot into 32-bit mode. Sometimes, your CPU or graphics card won't be fully supported in OS X unless you boot into 32-bit mode. Unlike in Windows, booting the 32-bit kernel for Mac OS X does not limit your total amount of RAM to 4 GB, and you can still run 64-bit applications. However, single applications cannot use up more than 4 GB of RAM, so this is a disadvantage if you do professional video editing, or something else that takes up a lot of RAM.

arch=x86_64
Allows Mac OS X to boot into 64-bit mode. Mac OS X Snow Leopard (and all versions beyond it) will boot into 64-bit mode by default. Nowadays, this boot flag is mainly used on AMD Hackintoshes, where choosing between 32-bit mode and 64-bit mode is actually important.

-legacy
Forces the "userland" of Mac OS X to boot into 32-bit mode. Mac OS X is divided into two parts: the "kernel", where OS X communicates with your computer's hardware, and the "userland", where everything else runs. Boot flags like "arch=i386" and "arch=x86_64" affect the kernel, but when running Mac OS X Lion with certain modified kernels, AMD Hackintoshes often need a 32-bit userland in addition to a 32-bit kernel. In this case, you need to use "-legacy" at the same time as "arch=i386" (both without quotation marks).

-force64
Forces the "userland" of Mac OS X to boot into 64-bit mode. Mac OS X is divided into two parts: the "kernel", where OS X communicates with your computer's hardware, and the "userland", where everything else runs. Boot flags like "arch=i386" and "arch=x86_64" affect the kernel, but when running Mac OS X Snow Leopard, AMD Hackintoshes often need a 32-bit kernel and a 64-bit userland. In this case, you need to use "-force64" at the same time as "arch=i386" (both without quotation marks).

-nossse3bit
Enables SSSE3 emulation for AMD Hackintoshes. Ever since Mac OS X Lion, Mac OS X has required the SSSE3 instruction set to run properly. However, AMD didn't add SSSE3 to their processors until 2011, meaning that only AMD processors with a "FX" in their model number (e.g. FX-4100) natively support the instructions needed by Mac OS X. If your computer uses an older AMD processor (i.e. anything from the Athlon or Phenom lines), you may have to use this boot flag to enable "emulation" of the instructions instead.

mach_kernel
/System/Library/Kernels/kernel
Locates the kernel ("mach_kernel"), an important boot file for Mac OS X. If your Hackintosh's verbose mode says that it can't find mach_kernel for some reason, entering this boot flag will help the bootloader find it. The kernel is either found at the very base of the OS X file system, or in /System/Library/Kernels/kernel if you're using OS X Yosemite. If you actually moved the kernel somewhere else in your hard drive, change "mach_kernel" to wherever the kernel is located. For example, if the kernel is in the Extra folder of your main hard drive, enter the boot flag "/Extra/mach_kernel" (without quotation marks). If your kernel is named something different, you can change the boot flag accordingly. For example, if your kernel is named "cheesecake" instead of "mach_kernel", enter the boot flag "cheesecake" (without quotation marks) instead.

Source : http://www.macbreaker.com/2012/01/list-of-common-hackintosh-boot-flags_29.html

Tags : hackintosh boot flags graphic mode, hackintosh boot flags nvidia, hackintosh boot flags list, unibeast boot flags

hackintosh boot stuck apple logo

So far, I haven't managed to pass Apple logo screen. hackintosh. The process apparently stops there and the spinning circle appears. I've installed Mountain Lion on a USB drive with UniBeast by following the instructions on this page. The only thing I can think of is that there might be some issues with the BIOS settings. Any recommendations would be greatly appreciated

Solutions :

Thank's

Tags : hackintosh won't boot pass apple logo, hackintosh stuck at apple logo with stop sign, unibeast stuck on apple logo, niresh stuck apple logo, niresh install stuck apple logo, hackintosh stuk on installation screen, hackintosh boot screen freeze

hackintosh won't boot pass apple logo, hackintosh stuck at apple logo with stop sign, unibeast stuck on apple logo, niresh stuck apple logo, niresh install stuck apple logo, hackintosh stuk on installation screen, hackintosh boot screen freeze, hackintosh won't boot pass apple logo, hackintosh stuck at apple logo with stop sign, unibeast stuck on apple logo, niresh stuck apple logo, niresh install stuck apple logo, hackintosh stuk on installation screen, hackintosh boot screen freeze ,hackintosh won't boot pass apple logo, hackintosh stuck at apple logo with stop sign, unibeast stuck on apple logo, niresh stuck apple logo, niresh install stuck apple logo, hackintosh stuk on installation screen, hackintosh boot screen freeze, hackintosh won't boot pass apple logo, hackintosh stuck at apple logo with stop sign, unibeast stuck on apple logo, niresh stuck apple logo, niresh install stuck apple logo, hackintosh stuk on installation screen, hackintosh boot screen freeze ,hackintosh won't boot pass apple logo, hackintosh stuck at apple logo with stop sign, unibeast stuck on apple logo, niresh stuck apple logo, niresh install stuck apple logo, hackintosh stuk on installation screen, hackintosh boot screen freeze , hackintosh won't boot pass apple logo, hackintosh stuck at apple logo with stop sign, unibeast stuck on apple logo, niresh stuck apple logo, niresh install stuck apple logo, hackintosh stuk on installation screen, hackintosh boot screen freeze ,hackintosh won't boot pass apple logo, hackintosh stuck at apple logo with stop sign, unibeast stuck on apple logo, niresh stuck apple logo, niresh install stuck apple logo, hackintosh stuk on installation screen, hackintosh boot screen freeze

How To Install OS X 10.11 El Capitan on Hackintosh (Vanilla)

Warning: Please follow these instructions at your own risk. I am not responsible for any damage or information loss that could result from following this guide. Also, note that installing OS X on PC is illegal. Please buy a real Mac if you're satisfied with your Hackintosh. This guide is for evaluation purposes only.

Requirements

• An Intel-based PC with UEFI bios
• A USB flash drive with at least 16GB capacity
• A dedicated hard drive (SSD highly recommended)
• A computer running OS X (10.9 or later) for preparing the installation USB flash drive

I chose to avoid the UniBeast installer (by Tonymacx86) because of its commercialized nature, as described here. Here is a vanilla guide to installing El Capitan on your PC!

Preparing the USB Installation Drive

First things first. We need to prepare a USB thumb drive that will contain the installation files as well as the bootloader and custom kexts for our specific Hackintosh build.

Download El Capitan from the Mac App Store

Head over to your existing OS X environment running 10.9 or later and open the Mac App Store.

Search for "El Capitan" and click Download. The download is completely free if you're running OS X 10.9+.

Wait for the download to finish (this could take some time).

Format the USB Drive

Open Disk Utility in Applications/Utilities and locate your USB device. Make sure you've backed up anything important on that drive as it will be erased forever.

Select it, and then on the right, click the partition tab.

1. Click Curent Layout and change it to 1 Partition.
2. Set the Name to USB.
3. Set the Format to Mac OS Extended (Journaled).
4. Click Options and select GUID Partition Table.

Click Apply to format the drive.

Copy the Installation Files to the USB Drive

Now that we've downloaded the installation files from the Mac App Store and formatted our USB drive, let's copy the installation files to it.

Run the following command in the Terminal (Applications/Utilities):

$ sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction

The command will run a script inside the Install OS X El Capitan application that will copy the installation files to the USB drive.

This process takes about 15 minutes. Go out for a quick run, or a hamburger, or both. When you come back, it should have finished.

Installing a Bootloader

If you tried to boot from the USB drive as is after the previous step on a PC, it wouldn't work. We need a bootloader that makes it possible to boot OS X on x86 and x86_64 PCs.

There are 3 popular bootloaders to choose from.

• Clover
• Chameleon
• Chimera

I went with Clover as it seems to be the most popular choice among other El Capitan installers, mostly for the following reasons:

Clover is an open-source EFI-based bootloader created on Apr 4, 2011. It has a totally different approach from Chameleon and Chimera. It can emulate the EFI portion present on real Macs and boot the OS from there instead of using the regular legacy BIOS approach used by Chameleon and Chimera. For many, Clover is considered the next-gen bootloader and soon it will become the only choice since BIOS in being replaced by UEFI in every new motherboard. One big feature of Clover is that iMessage, iCloud, the Mac App Store works along with Find My Mac, Back To My Mac and FileVault since Clover can use the EFI partition. (Read more)

Install Clover on Your USB Drive

Installing Clover on your USB drive is relatively easy. It involves running an installation wizard and selecting some options.

Download the latest Clover installer from here.

1. Run the installer.
2. Click Continue twice.
3. Click Change Install Location and set it to your formatted USB drive.
4. Click Customize and check the following options: 
   
   • [x] Install for UEFI booting only
   • [x] Install Clover in the ESP
   • [ ] Drivers64UEFI
     • [x] OsxAptioFixDrv-64 - fixes memory map created by AMI Aptio EFI. Booting OS X is impossible otherwise.

1. Click Install and wait for the installation to finish. It shouldn't take more than a minute.

Copy Essential Kexts to the USB Drive

Next, we'll need to copy some kexts (kernal extensions, similar to drivers on Windows) to the USB drive.

• FakeSMC.kext - open source SMC device driver/emulator developed by netkas. Tricks OS X into thinking it's installed on Apple hardware. Absolutely required for Hackintosh installation.
• NullCPUPowerManagement.kext - disables AppleIntelCPUPowerManagement.kext which may cause kernel panics when you try to boot from the USB drive. It's optional, copy it only if you get an AppleIntelCPUPowerManagement-related kernel panic.
• ApplePS2Controller.kext and AppleACPIPS2Nub.kext - adds support for PS2 devices (such as PS2 keyboard/mouse). They're optional, copy them only if you still use PS2 devices.

Download these files from here and copy them to the EFI mounted volume at /EFI/Clover/kexts/10.11/.

Install El Capitan

Now that the installation USB drive is ready, let's install OS X El Capitan!

Boot from the USB Drive

Restart your computer and boot from the USB drive (Press Esc/F8/Del to access the boot selection menu).

Use the arrow keys to select Boot OS X Install from Install OS X El Capitan (It should be selected by default). Press the spacebar and select Boot Mac OS X in verbose mode. Verbose mode means that you'll be able to see exactly what's going on under the hood as OS X attempts to boot up its installer. You'll be able to see the exact error message if booting fails.

Press Enter and cross your fingers. Clover will now boot the installer from your USB drive. This could take some time, in my case, it takes around 5 minutes (Don't worry -- the startup time is around 5 seconds after installing on an SSD).

Did it fail?

It's more than likely that the boot will fail. Don't panic (ha-ha), as kernel panics usually mean that you forgot to copy an essential kext to the EFI partition. Look up the exact error you're getting before the boot log comes to an end and search Google for a solution.

Once you find an additional kext that your system needs, you'd attempt to copy it to the EFI volume, only to discover that it's gone! Not to worry, it's just unmounted and hidden. Follow this guide to mount the hidden partition, and then, follow the Copy Essential Kexts section above to copy it to the USB drive's EFI partition.

Format the Target Hard Drive

Once the installation wizard boots, the next step is to prepare the hard drive that you want to install OS X on.

Click Continue, followed by Disk Utility.

Select the target drive to install to (not the USB drive!) and click the Erase button. Make sure to back up anything important on that drive, as it will be deleted forever.

1. Set the Name to El Capitan.
2. Set the Format to OS X Extended (Journaled).
3. Set the Scheme to GUID Partition Map.

Click Erase to format the drive.

Install OS X to the Target Drive

Exit the Disk Utility and click Install OS X.

Click Show All Disks and select the drive you just formatted to install OS X on it. Finally, click Install.

The process takes about 25 minutes. Be patient. For me, it hung at the end ("1 second remaining") for around 5 minutes. Don't be tempted to reset or cancel the installation.

When that's done, the system will reboot. Make sure to boot from the USB device again, and select Boot OS X Install from Install OS X El Capitan once again, in verbose mode. The installation is a two-part process that continues once you re-boot into the USB drive.

Finally, after about 25 more minutes, OS X El Capitan should be successfully installed on the target drive.

Boot into El Capitan via the USB Device

After the second reboot, boot from the USB device once again, but this time, select Boot OS X from El Capitan, and select verbose mode.

Press Enter and cross your fingers again. If all goes well, you'll be presented with the setup wizard:

Take a minute to set up your new Hackintosh. Once you're done, there are a few things you need to do to finish off the installation.

Reinstall Clover on the Hackintosh Drive

In the previous step, we used Clover on our USB drive to boot our Hackintosh. This is fine, but most of us aren't going to keep that USB drive plugged in forever. Let's make it possible to boot El Capitan independently by reinstalling Clover on it.

Go back up to the Install Clover on Your USB Drive section and follow the steps again, but this time, select your El Capitan volume instead of the USB drive.

Once again, copy the essential kexts to the EFI partition that shows up after installing Clover.

Finally, make sure to add Clover EFI boot options which is possible by pressing Clover Boot Options in the Clover boot window (if there are 2 boot options -- find the one for your SATA drive). I literally spent 3 hours figuring out why Clover would not boot when I disconnected the USB drive before I figured out that I need to manually add the EFI boot options.

Now you'll be able to boot directly from the El Capitan hard drive, as it should be!

Audio and Networking

If you're lucky, audio and networking will work right out of the box. If not, you're on your own from here. You'll need to research your exact hardware (by using System Information in Applications/Utilities) and searching Google to find the right kext or installer to make it work on El Capitan.

Clover Themes

The default Clover theme is pretty ugly (no offense). Check out this theme database to improve Clover's appearance.

This is YosemiteLogin by xenatt:

Enjoy!

That's it! Enjoy your new Hackintosh, and if you absolutely love it, consider buying a Mac!
Source : http://eladnava.com/install-os-x-10-11-el-capitan-on-hackintosh-vanilla/