We remind you that this material is provided for informational purposes only. If you are going to reproduce the steps described below, we strongly advise you to carefully read the article to the end at least once. The editors of 3DNews are not responsible for any possible consequences.

⇡ Introduction

"Hackintosh" is an ironic name for Mac OS X, which is not installed on an Apple computer, but on a regular PC. This phenomenon became possible when the Cupertino company began migrating its machines from the PowerPC platform to x86 in 2005, and Macs began to be equipped with the same Intel processors and chipsets that are used in personal computers. Since its first modest victories, the so-called OSx86 project has evolved from the entertainment of a handful of enthusiasts into a mass movement with a growing user base. Today, when Apple officially released a new version of its operating system, Lion, it's time to tell everyone who does not have a Mac, but has an interest in Mac OS X and a desire to experiment, about the Hackintosh.

The first questions that a person asks when he sees a Mac operating system on a PC: “Is it difficult to install?” and “Is everything working properly?”. The answer to both is negative. Installation has now been simplified to the extreme, so you can play around with Mac OS X on almost any modern computer, but not everyone has full functionality - a fair share of users will either not get hardware graphics acceleration, or the network, sound or something else will fall off. Hackintosh also has big problems with sleep mode. All these difficulties can be overcome, but for sure you will have to spend several sleepless nights. In general, the situation completely copies what happened with desktop Linux distributions a few years ago. However, this is a very flattering comparison both for the hacker community and for Apple itself: despite the fact that no one has ever prepared Mac OS X to work with non-native hardware, things could be much worse. Yes, some pieces of iron will never run under Mac OS, others will require dancing with a tambourine and a hare's foot for this. But at the same time, a huge fleet of components either works out of the box or starts up after easy manipulations. And software for Mac OS in all cases is installed and works exactly the same as on a real Mac. It turns out that he is not so scary, this Hackintosh.

For those who are not indifferent to the legal side of the phenomenon: of course, Mac OS X can only be legally installed on an Apple-branded computer, and any other options violate the license agreement. Modifying OS components is also prohibited, not to mention the use of pirated distributions from "torrents". However, Apple does not do any persecution of the OSx86 community (although it is suing companies that make money on Hackintosh), and protections against unauthorized use are in their infancy, and ways have long been found to overcome them. Mac OS X doesn't even require a license key or online activation. After all, hackintosh people advertise this OS for free and secretly dream of owning a real Mac. And the most devoted red-eyed experimenters, who fundamentally prefer Hackintosh, are still lost as potential buyers.

If there is no difference, then why pay more? Or is there?

So, if a small offense does not bother you, and technical difficulties only cause healthy excitement, let's try to install Mac OS X on a PC together. In the article, we will describe two easy ways to install the previous, but still popular version of the OS, Snow Leopard (10.6), and one way for the new one, Lion (10.7). It makes no sense to install Leopard (10.5), and even more so Tiger (10.4). If you like the result, then these instructions will be the starting point for self-mastery of Hackintosh. The last section provides links to popular OSx86 community resources where you can learn from other users and find solutions to specific problems.

⇡ Preparation of "Hackintosh"

Actually, why can't Mac OS X just work on a PC and how to overcome these obstacles? The number one reason is that Macs don't use the good old BIOS, but EFI, as a layer between the OS and hardware firmware, and in order for Mac OS to start, EFI is emulated at the level of a special "hacker" bootloader (by the way , we owe this achievement to the Russian hacker under the nickname Netkas). The most popular and rapidly developing bootloader today is Chameleon and its derivatives, such as Chimera.

The second reason is that Mac OS X has a kext (from kernel extension, remember this term) called Dont Steal Mac OS X. It is required to decrypt applications that make up what looks like an operating system to the user (Dock, Finder, loginwindow, SystemUIServer and others), based on the keys from the SMC chip, which is only on real Macs. Well, if "there are no legs, then there are no cartoons." The FakeSMC kext comes to the rescue, which successfully emulates the SMC Device, for which, again, thanks to Netkas. A special bootloader and FakeSMC.kext is all that is needed to boot Mac OS X, if the hardware of the computer is not very different from real Macs.

And this is precisely the third reason. There are no drivers for Mac OS X for unsupported hardware, or there are built-in drivers, but the system cannot use them because it does not recognize hardware with unfamiliar identifiers.

Hardware requirements for Hackintosh are the same - you need a processor with support for SSE2 instructions, best of all - Intel Core 2 Duo and older. AMD users will have to replace the OS kernel with a “hacked” version, as a result, there will be problems updating the system from the Apple server. The same applies to netbooks based on the Atom platform. It is highly desirable to support the AHCI mode from the SATA controller. To install Mac OS X Lion, you need 2 GB of RAM, for Snow Leopard one is enough. The first rule of choosing iron: the more the computer looks like real Macs, the less problems. The second rule: the newest and most advanced devices may not work no matter how hard they try. hardware support depends primarily on the Mac OS itself (heavy hardware drivers for Hackintosh are not written), and Apple has nowhere to rush. The site wiki.osx86project.org will help you evaluate the chances of success, which contains HLC (Hardware Compatibility Lists) for different versions of Mac OS X.

For installation, it is best to use a separate drive with a SATA interface, and turn off the Windows drive, out of harm's way. If it’s not scary to conduct experiments on one HDD with a working OS, then you will have to create a new partition on it using some kind of disk utility (10 GB is enough for a clean Mac OS X). Just keep in mind that during the installation process, the Hackintosh bootloader will be written to the HDD, and then you can only get into Windows through it. Nothing threatens the existing data, but a backup will not hurt either. The disk must be connected to the south bridge port of the motherboard, the SATA controller in the BIOS must be set to AHCI mode. It is recommended to remove overclocking, remove all expansion cards, except for the graphics adapter in the upper PCI-E slot, disable peripherals, in addition to the keyboard and mouse, reduce the amount of RAM to 4 GB (if more is installed). If the installation with minimal functionality is successful, then all this can be returned step by step. Too many conditions? Then you can practice on cats, that is, in a virtual machine. There are even ready-made images for various hypervisors on the Web, although their use will not bring experience in creating a Hackintosh.

We warn readers: although the "Hackintosh" is a completely harmless entertainment that will not break the computer and is unlikely to corrupt any data, all the manipulations described in the article are done at your own peril and risk. In addition, you need to be familiar with the computer and know what the bootloader, OS kernel and hard disk layout are. Well, when you master the Hackintosh to perfection, in no case do not agree if your friends ask you to install it on your PC, otherwise you will have to marry, as an honest person, to keep this miracle working.

⇡ Installing Snow Leopard from iATKOS 10.6.3 v2 assembly

The easiest and most versatile option is to install Mac OS X from a specially modified distribution. Since the release of Snow Leopard, such hacker builds have given way to a more elegant solution - installing from a copy of the branded disk using a separate boot CD, and this is described below. But users of CPUs from AMD or Intel Atom cannot do without assembly, because. the original kernel of Mac OS X (which our English-speaking friends call vanilla kernel) only supports Intel processors with Core architecture and older, and the assembly allows you to immediately select the “patched” version during the installation process. And after you have penetrated the world of Hackintosh with the help of assembly and gained knowledge, you can do a clean installation, the components of which you have complete control over.

iATKOS 10.6.3 v2 is one of the latest builds released, and despite the rather old version of the OS (Snow Leopard has already been updated to 10.6.8), all the "hacker" software on it is quite modern. After downloading the image (we will not tell you where), write it to a disc. Boot from the iATKOS disk and wait for the "hacker" bootloader to work and the OS to start.

This process takes several minutes, but if it suddenly drags on beyond reasonable limits or gives an error message, it means that something went wrong.

In this case, you need to boot from the DVD again, but at the bootloader screen with a green chameleon, press F8, highlight the optical disk, type "-x" from the keyboard and press Enter. This is the so-called safe mode, but if you are not lucky with it, then you need to boot with the “-v” argument, which will allow you to observe the boot log. At the moment where the process is stuck or the phrase Kernel Panic appears, you can take a photo of the screen and then, in a calm environment, try to understand what is happening, using thematic sites, Google and the advice of experienced "hackers".

The appearance of a window with a choice of language indicates that the download was successful and your system is able to run Mac OS X. We recommend that you select the language of Shakespeare if possible, since most instructions and troubleshooting on the Internet are written in it.

Scroll through the pages of the installer until a window appears with a choice of disk.

Open the Utilities section of the menu and launch Disk Utility. If you gave a blank disk to Hackintosh, then with the help of this program you need to “split” it (Partition tab). To install on a partition next to Windows, the partition is simply formatted in the HFS+ file system (Erase tab). For reliability, it is better to choose the HFS + Journaled option, and the Case Sensitive option will not be needed by most users.

Once the HDD is ready for installation, Disk Utility can be closed and the partition specified in the installer window. And now the fundamental point is the choice of drivers and settings that allow Mac OS X to fully work on your hardware. The list opens with the Customize button. All users are advised to look into the Bootloader branch and select the Chameleon v2 RC5 option over the default option. Owners of AMD processors, as well as Intel Atom, must select a modified kernel in the Patches, Modified Kernels section.

You should not select any "drivers" for the graphics adapter in the Drivers, VGA section. It is better to check the box next to the Graphics Enabler option in the Bootloader Options section - in this case, the bootloader itself will try to activate hardware acceleration. Be that as it may, the OS is almost always loaded in 2D mode, and if the Graphics Enabler method did not work, then you can try your luck with separate “drivers”. By the way, these are not drivers, but only injectors that allow the drivers built into Mac OS X to work with unfamiliar video cards, which is why they are quoted.

Select the appropriate package for the network card in the Drivers, Network section - there is a good collection there. For a laptop, the contents of the Drivers, Laptop Hardware section are useful. You can take some driver for CPU power-saving functions from the Drivers, Main Hardware, CPU Power Management section. The "native" kernel extension called AppleIntelCPUPowerManagement.kext, which carries this function, is prudently blocked in the assembly, because it is suitable only for Intel processors, and even then not for all, and in case of errors it does not allow the system to boot.

Do not check Sleep Enabler in the Patches section - if you need sleep mode, then after updating the OS, this extension will still have to be replaced.

The Language Translations section got into iATKOS from the official distribution and contains OS interface localization packages, including Russian.

It is advisable to write down a list of the options that you have chosen, in case the freshly installed OS does not start and you have to look for the culprit. When the selection is made, you can click OK and then Install. Go!

At the end of the installation, the computer will reboot. You can eject the iATKOS disk and boot from the hard drive we rolled Mac OS X onto. While the Chameleon bootloader is counting down the seconds until the OS starts by default, you can press any key and see a list of partitions from which boot is available. If at first there was already Windows on the hard drive, then it starts from a service partition called System Reserved, or directly from its root partition if the service partition is missing for some reason.

But we can't wait to see Mac OS, right? In this case, we just wait, and if the options were selected correctly during installation, a registration window will appear on the screen, and if the Graphics Enabler option worked, then a welcome video will also be shown.

What to do if the operating system is stuck at the boot stage or gives an error message? The first tip in this case is to boot with log view. To do this, you need to stop the bootloader while it counts down the time until the OS starts, select the partition with it, enter the “-v” argument and press Enter. Based on the messages on the screen, you can find the component causing the failure. Then you can try to boot into safe mode with the “-x” argument, and if this succeeds, then it is likely that the matter is in some kind of kext - a device driver or injector that you noted in the Customize menu of the installation disk, and it needs to be replaced. How to work with kexts is described in a special section of the article.

⇡ Installing Snow Leopard from a proprietary distribution

You can also create a Hackintosh using the native Snow Leopard image, which you can even buy to calm your conscience. At the same time, all the software that makes Mac OS X compatible with a PC is recorded on a separate disk. But this method is only suitable for owners of Intel's CPUs, because. both the distribution disk and the copy of the OS that will be installed from it use the original kernel without AMD support. In addition, the unmodified Snow Leopard installer will not allow you to roll the system onto a hard drive partitioned with MBR, and only supports the GUID partitioning scheme. Therefore, the disk with the MBR will have to be repartitioned.

If Windows is already there and you are not ready to say goodbye to the most popular operating system forever, then there is a non-obvious solution: using Disk Utility, first mark the disk with a GUID, create its own partition for “windows” and install Windows, and then to the second partition - snow leopard. The key word here is Disk Utiliy. This program, which, as you already know, also runs from the Mac OS X installation disc, creates a hybrid layout with GUID and MBR synchronized. And the MBR is required to install Windows.

So, first we need an iBoot boot disk image and a MultiBeast driver package - the latest versions of both are available at www.tonymacx86.com/viewforum.php?f=125 (registration required for download). We burn the iBoot ISO image to a disc and boot from it. When a window appears with a choice of a partition to boot, you need to replace iBoot in the drive with the native Mac OS X distribution, press F5, select the DVD and press Enter.

The further procedure is completely similar to what is written about the assembly of iATKOS, only in the Customize menu there are no "left" drivers, but only standard Snow Leopard packages - interface localizations, fonts, etc.

That's just after the installation is completed, booting directly from the hard drive will not work, because. a copy of the OS is pristine and no different from what is on real Macs. Therefore, you need to boot from the iBoot disk again and select the partition with Snow Leopad.

If an error occurs, you already know what to do: boot with the “-v” argument and run diagnostics, then try to start the OS in safe mode with the “-x” argument. The tonymacx86 website also recommends the PCIRootUID=1 argument, which can be combined with "-x" and "-v".

If Mac OS X showed a registration window, then it's time to accustom it to the PC. We need to run MultiBeast from the archive that we downloaded in advance and scroll through all the pages of the installer up to the component selection menu. Here, all users should check the EasyBeast Install item - which sets the installation of a minimum set of kexts. To enable support for specific hardware, you should look into the individual branches of the list and select the necessary extensions. At the end of the procedure, the computer will be restarted, and you can safely boot from the HDD.

In addition to the kexts, the Chimera bootloader will be installed on the disk, and if Windows was previously installed, then it is loaded by selecting the appropriate section.

⇡Lion installation

Here is the most delicious - the latest version of Mac OS X. So far, only Intel users can appreciate it. At the time of this writing, Apple has not yet posted the source of the Lion kernel, which means that there are no modified kernels either. But most kexts written for Snow Leopard work with Lion.

To install Lion, we need a working Snow Leopard version no lower than 10.6.6, a free 5 GB hard drive partition to accommodate the installer files, the Lion distribution (available for $ 29.99 in the App Store and you know where for free), the xMove utility and the familiar MultiBeast package.

The Install Mac OS X Lion program is launched directly from under the running OS, and as the installation partition, you need to select the one from which Snow Leopard is launched, which will not affect the OS in any way. Once the files are copied, you can agree to reboot and log back into Snow Leopard.

Now it's up to the xMove utility. After running it, you need to mark the empty partition that we prepared for Lion in advance, and xMove will transfer the files unpacked by the Install Mac OS X Lion program there. If Snow Leopard is installed using the iBoot + MultiBeast method, then it is enough to boot from the hard drive and select the partition with "Lion" in the Chimera bootloader menu. If iATKOS or another solution was used for installation, but the bootloader and kexts are also not the first freshness, then you will have to boot from the iBoot disk. The further procedure completely repeats the process of installing Snow Leopard from a proprietary distribution. Moreover, as a target, you can select a partition with an already running Mac OS X, and then it will be painlessly updated.

⇡ Installing and removing kexts

How do I remove a problematic driver, injector, or add support for devices that won't start after the initial install? The storage of kexts (kernel extensions) in Mac OS X is the /System/Library/Extensions directory, and they are loaded from a single cache at /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext, where the OS puts only the required extensions. But modern Hackintosh loaders (Chameleon and Chimera already familiar to us) can load additional kexts from the /Extra/Extensions directory, and their own small cache /Extra/Extensions.mkext is formed from them. MultiBeast and iATKOS use this scheme, only in the latter case the /Extra directory is hidden. The display of hidden files is enabled using a command in the terminal.

defaults write com.apple.finder AppleShowAllFiles TRUE
killall Finder

Many kexts can be installed by copying them to /Extra/Extensions. But at the same time, some will not be able to resolve dependencies (there are no necessary extensions in the /S/L/C/c/S/Extensions.mlext cache), and you will have to create a single cache in the /Extra directory from all "native" and "third-party" extensions, which the OS can't remake. This is done by the following command:

sudo kextcache -m /Extra/Extensions.mkext -- /System/Library/Extensions /Extra/Extensions

Before these files in /Extra/Extensions, you need to assign the necessary permissions. Teams:

sudo chown -R 0:0 /Extra/Extensions

sudo chmod -R 755 /Extra/Extensions

And one more nuance: if even with the correct permissions, the kext has not entered the cache and is not loaded, you need to open it using the Show Package Contents option in the file context menu and view the Info.plist file in the Contents directory. This is an xml file, and at the end, before the closing tags should be the following entry:

OSBundleRequired

root

Otherwise, it needs to be added or changed.

In Mac OS X 10.7, things are a little different. Lion uses a different cache format, the prelinked kernel. By default, Chameleon does not read it and scans the entire contents of the /Extra/Extensions directory, which slows down the download. The only thing that can be done so far is to create a shared cache in the system directory /System/Library/Caches/com.apple.kext.caches/Startup. Team:

sudo kextcache -c /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache -v -t -K /mach_kernel -- /System/Library/Extensions /Extra/Extensions

And in order for the bootloader to pick up the kernelcache, you need to use the “UseKernelCache=Yes” argument at startup. But unlike the contents of /Extra, this file is subject to the operating system, and from time to time it will update it, forgetting, of course, about our "hacker" extensions. A solution to the problem is to move the kexts from /Extra to the /System/Library/Extensions directory and set the necessary permissions for them with the commands:

sudo chown -R 0:0 /System/Library/Extensions

sudo chmod -R 755 /System/Library/Extensions

⇡ OS update

Hackintosh can be updated from the Apple server using the built-in Software Update utility. But at the same time, you need to be prepared for the fact that some kexts will stop working after the update or start causing failures and you will have to find a replacement for them. Fortunately, the developers of popular extensions quickly respond to the release of new versions of Mac OS X. In addition, after the update, you need to rebuild the cache of kexts, after booting the system with the “-f” argument. Users of AMD processors, before updating the OS, should make sure that there is a fresh version of the modified kernel, or you can leave the old one.

⇡ Bootloader setup

The operation of the Chameleon bootloader or its analogues is controlled by the com.apple.boot.plist file in the /Extra folder. It can be modified manually, but there is also a special GUI utility, Lizard, which can be downloaded from darwinx86.net/software/darwinx86_software.html . It is desirable to enter the screen resolution, boot arguments (for example, the aforementioned “UseKernelCache=Yes”) into the configuration, and the name of the modified kernel file for owners of “non-standard” processors. In iATKOS, this is the custom file (look, it is in the root partition of the disk). Also check Graphics Injection if this option helped you enable 3D acceleration.

The 32bit Compatibility Mode option will force the kernel to boot in 32-bit mode, which may be necessary for some kexts. At the same time, support for large amounts of RAM is maintained, and applications can run in 64-bit mode regardless of the kernel. The equivalent command line argument is "-x32".

The argument list can also contain special options for individual kexts.

The program automatically opens the /Extra/com.apple.boot.plist file, and if it does not exist, it will create it when you try to save changes. This is exactly what will happen with iATKOS. this assembly by default stores the bootloader configuration in the /Library/Preferences/SystemConfiguration/com.apple.boot.plist system file of the same name. This is not correct, so it is best to clear the system file after creating the file in /Extra, leaving only those lines that are shown in the screenshot.

Another Lizard feature is editing the /Extra/SMBIOS.plist file. It contains information about the computer model and installed hardware and helps to represent the computer as some kind of "Mac" in the System Information program.

⇡ Peripherals from Apple

A question that worries many, but I don’t want to spend money on an experiment: do Mac devices work with the Hackintosh - Apple Cinema Display, Magic Mouse and Magic Trackpad. So, the monitor is compatible with any video card equipped with DisplayPort (DP Mini or a full-format version of the port with an adapter is suitable), and both the light sensor and the brightness control in System Preferences work. The mouse and touchpad need a USB Bluetooth adapter - some work right out of the box without any additional kexts, and the connection process, again, is no different from this on real Macs.

⇡ Free swimming

www.kexts.com - database of original and third-party kexts for Mac OS X.

Instead of an epigraph:
We say driver - we mean kext

To be honest, today will not be quite a full-fledged, so to speak, step. But that doesn't make it any less useful. And it was conceived as an answer to some questions that appear in the comments. I will try to give some useful tips and dispel some fears. Or not dispel. Let's see what happens 🙂

The previous 3 parts can be found either by the tag .

dispelling fears

Based on my own experience, I can assume that the greatest nervous tension occurs in the event of some incorrect user action, as a result of which a seemingly normally working system stops loading. What to do in this case?

First of all, you need to remember - what was it that was delivered that the system stopped loading?
Try booting into safe mode. To do this, before loading, instead of any switches (-v or -s), enter help and read carefully. In my opinion, the -F switches (ignoring the configuration file) and our main trump card -x (booting in safe mode using standard drivers) can help.
If it turned out to boot into safe mode, then manually delete what was installed. Usually all kexts are in /System/Library/Extensions/ .
Read the InsanelyMac forum and find detailed instructions for installing drivers for your video card, network adapter, or any other hardware. Believe me, in 95% of cases you will know exactly where to get everything and how to install it. Or you will find out that there is no driver for this hardware.

And now the most important thing:

If the system is broken, and before that it worked - do not be afraid to format the partition and re-install a more or less "working" Leopard configuration. Usually all problems arise, and they can be solved, at the very beginning, until the moment of constant use of Hackintosh.

This is a normal practice, there is nothing so surprising here. Most of the people I've talked to have reinstalled their system at least 15-30 times in the beginning. So be patient.

Uninstalling Video Drivers

I made this point separately because I have a little surprise for you. In the description of the already obsolete (10.5.2) there is a separate paragraph devoted to this problem:

If you have problems on reboot with video (blue or black screen):
All you have to do is just press F8 at Darwin's prompt and then type -s (single user mode) then at root type mount -uw / and /movevideodrivers then it will be prompt to move video drivers by class (nvidia ; ati ; or intel gma) voila! type yes to confirm or enter to skip !

What does the following mean in translation:

If you have problems with video (blue or black screen): all you need is to boot with the -s switch (in single user mode), then run 2 commands as root: mount -uw / and /movevideodrivers . After that, you will be asked which video driver you have (nvidia, ati or intel gma). Answer yes to confirm and press enter to skip. Voila! The system is loading.

Everything would be fine, but this script was available only for Kalyway and no more for any other assembly. I have been looking for it for a very long time and finally prepared a surprise for you. Before installing video drivers, download and put in / (root partition) here - yes, yes, this is the same movevideodrivers. After that, you will need to go to the terminal and set the rights to run it. If I remember correctly, the following command will suffice:

sudo chmod +x /movevideodrivers

Everything, after that it will be possible to experiment with the video. And now I'll tell you how.

Pacifist is our everything

The utility is designed to work with .pkg packages, .iso and .dmg images, a bunch of archives like .zip, .tar, .tar.gz, etc. In addition, it can also open installation disks (and in our case, any disk with any build). In addition, it can only extract certain packages from archives. This is the function we need.

The program is paid (shareware) and costs $ 20, but in the free mode you just have to wait a certain time before being able to work (20 seconds). And the functionality does not seem to be truncated.

So, after we run the utility and select “Open Apple install disk”, Pacifist will scan it and show the entire list of packages in the form of a directory tree. The tree structure will roughly correspond to a similar menu when you select . According to this structure (or by searching in the application), you can find the driver we are interested in, and by clicking on the Install button, install it into the system. This will require you to enter your password.

After that, we reboot - if the screen is black / blue again - use / movevideodrivers and try to install the appropriate driver again.

Installing kexts

To begin with, I note that kexts (kernel extension) are an extension of the system kernel. In Windows, a similar concept is drivers. It happens that on the same InsanelyMac, as an addition to the post, there is a working kext for launching wifi, video, or a network adapter. You can install it manually (but this is associated with some headaches), or you can use the Kext Helper B7 utility (usually it comes with any assembly).

After that, you will need to reboot and check if the driver is installed correctly. But you need to delete kexts manually from the folder /System/Library/Extensions/ .

Some solutions come already in the form of .pkg - a regular installer. Therefore, installing the driver will be even easier.

Happy installation 😉

READ ME PLEASE

If you CANNOT decompress the files to a flash drive, please move away from the keyboard and immediately read the book "Computer for Dummies: A Detailed Guide to Using a PC" !!!

1. All files are uploaded to MEGU. Who is experiencing problems with her - in the comments they re-uploaded to the torrent.
2. Please don't ask me about installing Macs on laptops. I ask you to. You are welcome. This is a very hemorrhoid process. Install ubuntu and connect the Mac theme. Get the same experience
3. I rarely answer on Habré, write to VK for all questions.

This manual/guide/etc is written for those who are too lazy to piece together this or that information about installing a "poppy" on a PC, everything is clear and on the shelves.

To begin with, before, in fact, installing the system itself on a PC, you need to decide whether we need it or not, since the system itself is very specific in terms of installation and configuration, unless, of course, you have an apple device. It makes no sense to explain that deploying a system that was not originally planned for desktop PCs is a complicated matter and it can take from 2 to N hours, depending on the compatibility of the hardware.

Now, let's figure out what Hackintosh is: the word "hackintosh" was formed from the merger of the two words "Macintosh" and "Hack", which essentially means "hacked mac", although there is nothing to do with "hacking" here.

In this guide, we will consider creating an installation USB flash drive from under Windows (since this is the most popular system among "novice hackintoshniks"), installing the system on a blank disk, expanding the kernel for your hardware, and, in fact, installing and configuring the bootloader (it is at this point that many and there are problems)

CPU: Intel Core i5 4460 3.2 GHz (Haswell)
Memory: 16 GB Crucial Ballistix Sport
Graphics: MSI GeForce GTX 760 2048MB
Motherboard: Gigabyte GA-H81-S2V (UEFI Bios)

I also want to draw your attention to the fact that in this article we are working with NVidia video cards and UEFI BIOS.

Well, let's go.

Step 1. Iron assessment and analysis

Yes, despite the fact that Hackintosh one way or another runs on almost any configuration, it always does it in different ways. Therefore, it is immediately worth analyzing our hardware.

Processors

So, let's start with the fact that on machines with AMD processors system WILL NOT work(It is very difficult to call the dying state of agony in which she will arrive “work”). Yes, in fact, you can put a custom kernel, reflash it, and so on, but it makes sense to reinvent the wheel out of sticks if one way or another it will break anyway. The system gets up without problems on Intel processors, starting with Core i3 (we are talking specifically about macOS Sierra 10.12, previous releases can also get up on Core 2 Duo and Pentium processors). In my case, the i5 4460 stone fell out (4 cores, 4 threads, turbo boost up to 3.4 GHz).

ACHTUNG 2

There are problems on socket 2011-3 processors, in particular on the X99 chipset. It usually manifests itself due to too much bells and whistles on the motherboard.

Video cards

Next, let's look at graphics. If you use integrated Intel graphics (in my case it is HD4600), then most likely you will need a separate graphics “factory” (although they can start natively).

List of supported Intel graphics cores

Intel HD 3000
Intel HD4000
Intel HD 4600 (laptops)
Intel HD 5000

Radeons (AMD) start up, but again with a bang. For example, new cards (RX-4**), as well as the well-known R9 380 or R9 380x, can simply bring the boot to a black screen.

List of exactly supported AMD cards

Radeon HD 4000 series
Radeon HD 5000 series
Radeon HD 6000 series (Preferred 6600 and 6800)
Radeon HD 7000 series (Preferred 7700, 7800, and 7900)
Radeon R9 200 series (R9 290 won't start)
Radeon R9 300 series (There may be problems with the R9 380. I haven't personally tested it, but judging by the reviews on Reddit with these cards there is Problems)

In this manual, we will not consider the AMD graphics factory, since it all comes down to framebuffer patches and Device ID substitutions in the bootloader (which is individual for each). Read more about AMD cards here: tyk (English).

The situation is quite different with cards from NVidia. Almost everyone starts up, with the exception of some especially gifted ones. Problems are observed on the 10th series, but, most likely, they will not be soon. Everything is fine. On GTX cards, the graphics start up with a pinch, the GT edition cards also do not lag behind, although there are some exceptions there.

List of working NVidia cards

Geforce 7000 series
GeForce 8000 series
Geforce 9000 series
Geforce 200 series
Geforce 400 series
Geforce 500 series
Geforce 600 series
Geforce 700 series
Geforce 900 series
UPD 14.05 Geforce GTX 1000 Series

I am more than sure that you will find your card in the list.

Network Controller

I think you don’t need to chew on how you can determine your network card ...

newby guide

Open Task Manager → “Performance” tab → Ethernet (Windows 10), there will be network card in big black letters.

By the way, you can still look in the BIOS "e

One way or another, we will not dwell on this in detail. In any case, you will have to start a network card, so I will simply provide a list of supported network cards.

network cards

Intel Gigabit

5 Series - 82578LM/82578LC/82578DM/82578DC
6 and 7 Series - 82579LM/82579V
8 and 9 Series – I217LM/I217V/I218LM/I218V/I218LM2/I218V2/I218LM3

Realtek

RTL8111, 8168, 8101E, 8102E, 8131E, 8169, 8110SC, 8169SC
RTL8111/8168 B/C/D/E/F/G
RTL8101E/8102E/8102E/8103E/8103E/8103E/8401E/8105E/8402/8106E/8106EUS
RTL8105/8111E/8111F/8136/8168E/8168F

Atheros

AR8121, 8113, 8114, 8131, 8151, 8161, 8171, 8132, 8151, 8152, 8162, 8172
AR816x, AR817x supported

Broadcom

BCM5722,5752,5754,5754M,5755,5755M,5761,5761e,57780,57781,57785,5784M,5787,5787M,5906,5906M,57788,5784M

Marvell

88E8035, 88E8036, 88E8038, 88E8039, 88E8056, 88E8001

killer

E2200

Memory

There are no restrictions. The system runs on two gigabytes. Recommended 4. Author recommends 8.

With iron, in fact, figured it out. If at this stage you have not changed your mind, move on.

Step 2. Making a bootable flash drive and deploying the installer to it

So, here we come to practice. Let me remind you that we do all this from under Windows. I’ll say right away that we will not use images from the root tracker, which are so vehemently advised by people who have everything working with hackintoshniks “up to 18”. First we need the BDU utility (BootDiskUtiliy).

You will need a flash drive > 8 GB. Any.

1. Run the utility
2. Destination disk → select our flash drive
3. Format disk

Now we are waiting. The flash drive will be formatted in Apple HFS and will be divided into two partitions, one of which will have the bootloader (CLOVER) installed, and the second will remain clean so that the installer can be deployed there.

After the performed manipulations, we get something like the following picture:

Next, you need to deploy the installer to the second partition. We also do this through the BDU utility. However, the question here is where to get the image. There are two options: take a ready-made, already unpacked one, or personally get it from Install Mac OS Sierra.app from the AppStore. Since the second method requires a lot of time, and it takes a very long time to search for this .app itself, we will use the first one. Craftsmen have already prepared ready-made HFS files for this utility, extracted them from .app for us. All we need is to download it (the image weighs almost 5 gigs, so you can just download it). Actually, download macOS 10.12 Sierra from here.

Downloaded.

1. We get the HFS Partition File (HFS +) from the archive, a file with the extension .hfs.
2. In the BDU "Destination disk" utility window, select Part 2 of our broken flash drive.
3. Open "Restore partiton".
4. Search and select our *.hfs file. Please note that it should not be larger than PART 2 sections.
5. We are waiting for it to be unpacked.
Everything, the installer on the flash drive is unpacked and ready to go.

Now we need some files for your system. I collected everything I needed in this archive. Later I will explain what and why.

You will also need this kext, we also download it: tyk. We unpack the folder from the archive to the root of the Clover section, and the kext to the folder that we unpacked. Everything is ready. The flash drive is done. Let's move on.

Step 3Install macOS Sierra on an Intel-PC

We check that the flash drive is inserted into the 2.0 port. Reboot, go to BIOS. Let me remind you that our BIOS is UEFI. Disable virtualization (Intel Virtualization). In the boot priority (BOOT) we indicate our flash drive. Make sure it will boot in UEFI mode. Save and apply settings, reboot. We get into the Clover menu.

Clover ("Clover") is a hackintosh loader, as well as its installer.

Press the down arrow until you reach the Options menu. Press Enter. All we need here is this line:

We write the following into it:

kext-dev-mode=1 rootless=0 -v npci=0x2000 nv_disable=1
Let me explain what each of these arguments does:

kext-dev-mode=1 - necessary arg, without which the hack will not start. Allows you to upload kexts to the system (Initially, FakeSMC.kext).
rootless=0 - disables SIP (System Integrity Protection). Required arg.
-v - "Verbose mode". Instead of a beautiful apple, we will see a "console" download so that we can identify the error, if any.
npci=0x2000 (or 0x3000, depending on PCI-e version) - optional. We warn you that the download will stop at the stage of PCI scanning. You may not write.
nv_disable=1 - optional. To avoid artifacts during loading and other garbage, disable the graphical shell. Loaded in native graphics mode in orthodox 144p resolution. You may not write.

Apply the arguments by pressing Enter. Select Boot Mac OS Sierra from OS X Base System. And so, the native download began. Let's immediately analyze some errors: still waiting for root device - the IDE controller does not have time to connect.

Fix

We reconnect the flash drive to another 2.0 port, boot with the following arguments:
kext-dev-mode=1 rootless=0 cpus=1 npci=0x2000 -v UseKernelCache=No

Missing Bluetooth controller transport - the video card did not turn on, or FakeSMC.kext did not work. Check that there is FakeSMC.kext in the kexts/other folder. Sinezub has nothing to do with it.

Fix

We load like this:

kext-dev-mode=1 rootless=0 -v npci=0x2000
Or like this:
kext-dev-mode=1 rootless=0 -v -x npci=0x2000

If such errors still remain, then we try to load like this:

kext-dev-mode=1 rootless=0 -v npci=0x3000 darkwake=0 nv_disable=1 cpus=1
In other cases, only Google will help, although these fixes should solve these problems.

We wait. At some points, it may freeze. If it hangs for more than a minute - reboot. Should help in some cases.

And here we are, in fact, in the installer. Select the language and click on the arrow. The language pack will be loaded (may freeze for a minute). Now open Utilities>Disk Utility, we need to format the disk for macOS. Select the desired disk, click "Erase". For convenience, we call the new drive "Macintosh HD". Format, close Disk Utility. Next, select the drive on which we will install the system (in our case, Macintosh HD), install.

Installation takes from 15 to 30 minutes, it all depends on the speed of writing to the disk. After installation, the system will prompt us to set up an Internet connection - skip it, we'll do it later. We make a user. Done, we are in the system. Or rather, in her stump. So far, nothing is working for us. If you reboot the machine, it will be impossible to get into the system (due to the lack of a bootloader).

Fix

If the computer still rebooted or turned off, then you can choose to boot from a USB flash drive, then select “Boot macOS Sierra from Macintosh HD” in the clover menu, while not forgetting to write boot arguments in the options menu.

Move on…

Step 4. Basic system setup and installation of kexts

So here we are in the system. While she knows little, we will not go online, the graphics do not work, and in general everything looks somehow very bad. This needs to be corrected.

Let's understand what kexts are.

kext(Kernel Extension) - kernel extensions that run one or another equipment that is incompatible with the original poppy (For example, where can we find a Realtek network card or a sound card in the iMac?). That's what we need right now.

To begin with, we need the PostInstall folder, which you unpacked into the CLOVER section on a bootable USB flash drive. From there, we need, first of all, the Kext Utility, which allows you to install kexts on the system. We launch it, enter the password from the user, wait until we see the inscription “All done”.

We install the kext on the network card (the Network folder, sorted it into folders for each network card), just drag it into the program window. We are waiting for the inscription "All done" to appear. Next, go to the CLOVER section of our flash drive, then to kexts, then to Other. We copy FakeSMC.kext from there to any place (Better to the same PostInstall), then install it in the same way as the kext to the network card. You will also need a USB 3.0 kext. It was in the Legacy_13.2_EHC1.kext.zip archive that you extracted with PostInstall. We install it.

Done, we started the Internet, USB and allowed the system to boot at all (FakeSMC.kext imitates the System Management Control chip, which is present only on Apple motherboards. Without this kext, the system simply will not start).

Now let's install the bootloader. Go to the PostInstall → Clover_v2.3k_r3949 folder. There is a *.pkg file, open it.

We click to continue, we read the information about the bootloader (I'm lying, also click continue). Next, in the lower left corner, click "Settings".

For UEFI boot, set the following settings:

We'll talk about legacy loading later, since everything is a little more complicated there and you will have to patch DSDT.
Click "Install". Let's go through the process of installing the bootloader.
Done, the bootloader is installed.

Step 5Setting Up the Bootloader

After installation, we will get a clean, unconfigured Clover bootloader, which needs to be slightly reconfigured. We open Clover Configurator (in the future I do not advise using this program for point editing of the bootloader config).

First we need to get to the EFI partition with the bootloader. In the left menu, click Mount EFI. Next, click Check partition, a table of all partitions will appear. The partition we need must be on the same partition as Apple_HFS , it is displayed as EFI EFI. Click Mount partition. In the list, select the disk we need (For example, disk0s1). Please note that there is a bug when all sections are not visible. Scroll the mouse wheel, so you can scroll between sections and select the one you need.

Next, click Open Partition. Opens a "folder" with the desired section. We pass EFI>CLOVER. Copy plist.config to the PostInstall folder, for convenience. Also, just in case, we copy it somewhere else, since we will edit the one we just copied. And one more for backup. Copy, open plist.config.

We see something like this:

ACPI - Don't touch the fixes, drop (DropOEM) our video card (DropOEM_DSM works when two DSDT patches meet. Therefore, we leave the original autopatch method as the loader, and disable ours, if it appears).
Go to the BOOT section.

So here's where we need to dig. We set the arguments ourselves, depending on the system.

-v (verbose) - the already familiar "text" boot mode. It is better not to enable, but to prescribe manually if necessary.
arch - architecture. In my case x86_64
npci is the key we already know. We expose if necessary. I recommend doing the first boot without it, but in Verbose mode.
darkwake - responsible for sleep and hibernation. Has 7 modes. If the dream does not start by changing the hibernatemode in the terminal, then I recommend using trial and error to find the desired darkwake mode.
cpus=1 - start using only one core. I do not recommend choosing.
nvda_drv=1 - activation of the Nvidia webdriver, which we will install a little later. Choose if you have nVidia.
nv_disable=1 - disable graphics invisibility and run on the native poppy driver. It is better not to choose, but if necessary, manually prescribe.
kext-dev-mode=1 and rootless=0 have already been explained before.

We pass to the right subsection.

Default Boot Volume - the partition from which, by default, the selection of a disk for booting will begin. By default, LastBootedVolume (last partition selected).
Legacy - Legacy Boot for older versions of Windows and Linux. It very much depends on the hardware and BIOS construction, so several algorithms have been developed:
LegacyBiosDefault - for those UEFI BIOSes that have the LegacyBios protocol.
PBRTest, PBR - variants of PBR Boot, it's just overkill. In my case PBR works.
XMPDetection=YES is an important parameter. Fixes the amount of RAM, slots, dice, frequency and number of channels.
DefaultLoader - if there are several loaders on the partition, select the default one. Must not be empty!
Timeout - time to automatic boot.
Fast - a parameter that skips selecting a partition and immediately proceeding to boot.
-1 (Timeout -1) - disable autoboot.

We skip the CPU section, the bootloader itself will pick up the necessary values. Devices is also best skipped if you have nothing to fake. Disable Drivers - disable unnecessary drivers on boot. GUI - setting the appearance of the bootloader. I think there is no need to explain anything here, there are no special parameters here. Screen resolution, language and menu theme. Everything is simple. Graphics - graphics settings and injections.

Do not touch the Inject NVidia parameter! There will be artifacts at launch. It is designed to run old GT line cards

Kernel and Kext Patches - patches and kernel customization. By default, Apple RTC is selected. Better not to touch. SMBIOS - the most juice, customization and fake "poppy".

To set the factory information, click on the magic wand icon. Next, select iMac (if PC) or MacBook (if laptop).

ACHTUNG 3

You can also look among older configs, such as MacMini or Mac Pro. Your task is to choose the poppy that is most similar to your hardware.

Don't add anything to Memory and Slots. These are purely cosmetic parameters that the clover picks up at the loading stage. Incorrectly set parameters can cause conflicts.

WARNING: Nvidia graphics cards without policy-kext edits only work on iMac13.1 and iMac14.2 macs.

In AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext/Contents/info.plist we fix Config1 to none here:

Now it should work.

Ready. We do not touch anything else, we have done the basic settings. We save our file. Now we copy it to the CLOVER folder of the EFI partition, log in, replace it. Let me remind you that before that you should have made a backup.

Step 6Install the graphics driver and reboot for the first time

Here we are almost at the goal. Now it remains only to start the video card. The PostInstall folder contains the WebDriver*.pkg package. Open it up, install it. Then he prompts us to reboot. We reboot.

Now let's make sure that we are not booting from a USB flash drive, but from hard drive in UEFI mode. Select Boot macOS Sierra from Macintosh HD. Let's start.

Note

I recommend using the -v switch for the first run, so that if something goes wrong, you can immediately identify the error. If the bootloader is broken and you cannot get into the system, then boot from a USB flash drive, enter the necessary keys in the options and boot the system into Verbose mode.

Done, here we are in the system. In the picture, I roughly showed how the axis will look after all the settings. Pay attention to how the system understood your "mac", as well as the frequency of the processor.

A sure sign of the operation of the nvidia driver will be its logo on the taskbar. I turned it off, by the way, because it interferes, but you can access the invisible control panel through "System Preferences ...". We can check the Internet through Safari. USB 3.0 by simply plugging a USB flash drive into a 3.0 port.

Additionally

- Sound

With regards to sound, the situation is different. If you have an external sound card, then just download the drivers for it from the manufacturer's website (analogue devices, such as mixing consoles, do not require drivers and start up immediately). For an onboard sound card, use one of these kexts:

Regarding AppleHDA

The following conditions must be met for it to work:

Availability of vanilla (pure) AppleHDA.kext kext in the system.
Having an HDEF section in your DSDT (or a clover fix FixHDA_8000->True)
Specify layout in DSDT (or in clover config.plist Devices->Audio->Inject->1,2,28...etc. Choose from those specified for your codec above)
Put away ALL sound patches (if they were in your config.plist) from the KextsToPatch section
Remove DummyHDA.kext (if used)
If you used VoodooHDA.kext - delete it. Also delete AppleHDADisabler.kext and rebuild the cache.
Intel HDMI 4000/4600 requires clover fix UseIntelHDMI->True

Actually, that's all. After we get macOS Sierra ready to go.

UPD from 05/14/2017

- In the comments, kind people re-uploaded the file from mega to torrent. This is due to the fact that many people have a problem when downloading a file from a mega. To be honest, I did not know that Mega has a download speed limit (I use a premium account). Also, please write all questions to me in VK, but first check the comments. There is a chance that your problem has already been solved there. Again, I am not responsible for any risk that may be placed on your computer. Also, I want to stipulate one point that the article is presented for educational purposes only. The very fact of installing a hackintosh on a PC is a gross violation of Apple's policy regarding their system, which is punishable by law. The author does not encourage the use of MacOS on non-Apple computers and does not encourage changing the source code of the system.
- The end

Tags: Add tags

READ ME PLEASE

If you CANNOT decompress the files to a flash drive, please move away from the keyboard and immediately read the book "Computer for Dummies: A Detailed Guide to Using a PC" !!!

CPU: Intel Core i5 4460 3.2 GHz (Haswell)
Memory: 16 GB Crucial Ballistix Sport
Graphics: MSI GeForce GTX 760 2048MB
Motherboard: Gigabyte GA-H81-S2V (UEFI Bios)

I also want to draw your attention to the fact that in this article we are working with NVidia video cards and UEFI BIOS.

Well, let's go.

Step 1. Iron assessment and analysis

Yes, despite the fact that Hackintosh one way or another runs on almost any configuration, it always does it in different ways. Therefore, it is immediately worth analyzing our hardware.

Processors

ACHTUNG 2

There are problems on socket 2011-3 processors, in particular on the X99 chipset. It usually manifests itself due to too much bells and whistles on the motherboard.

Video cards

Next, let's look at graphics. If you use integrated Intel graphics (in my case it is HD4600), then most likely you will need a separate graphics “factory” (although they can start natively).

List of supported Intel graphics cores

Intel HD 3000
Intel HD4000
Intel HD 4600 (laptops)
Intel HD 5000

Radeons (AMD) start up, but again with a bang. For example, new cards (RX-4**), as well as the well-known R9 380 or R9 380x, can simply bring the boot to a black screen.

List of exactly supported AMD cards

List of working NVidia cards

I am more than sure that you will find your card in the list.

Network Controller

I think you don’t need to chew on how you can determine your network card ...

newby guide

Open Task Manager → “Performance” tab → Ethernet (Windows 10), there will be network card in big black letters.

By the way, you can still look in the BIOS "e

One way or another, we will not dwell on this in detail. In any case, you will have to start a network card, so I will simply provide a list of supported network cards.

network cards

Intel Gigabit

5 Series - 82578LM/82578LC/82578DM/82578DC
6 and 7 Series - 82579LM/82579V
8 and 9 Series – I217LM/I217V/I218LM/I218V/I218LM2/I218V2/I218LM3

Realtek

RTL8111, 8168, 8101E, 8102E, 8131E, 8169, 8110SC, 8169SC
RTL8111/8168 B/C/D/E/F/G
RTL8101E/8102E/8102E/8103E/8103E/8103E/8401E/8105E/8402/8106E/8106EUS
RTL8105/8111E/8111F/8136/8168E/8168F

Atheros

AR8121, 8113, 8114, 8131, 8151, 8161, 8171, 8132, 8151, 8152, 8162, 8172
AR816x, AR817x supported

Broadcom

BCM5722,5752,5754,5754M,5755,5755M,5761,5761e,57780,57781,57785,5784M,5787,5787M,5906,5906M,57788,5784M

Marvell

88E8035, 88E8036, 88E8038, 88E8039, 88E8056, 88E8001

killer

E2200

Memory

There are no restrictions. The system runs on two gigabytes. Recommended 4. Author recommends 8.

With iron, in fact, figured it out. If at this stage you have not changed your mind, move on.

Step 2. Making a bootable flash drive and deploying the installer to it

You will need a flash drive > 8 GB. Any.

1. Run the utility
2. Destination disk → select our flash drive
3. Format disk

After the performed manipulations, we get something like the following picture:

Downloaded.

Now we need some files for your system. I collected everything I needed in this archive. Later I will explain what and why.

Step 3Install macOS Sierra on an Intel-PC

Clover ("Clover") is a hackintosh loader, as well as its installer.

Press the down arrow until you reach the Options menu. Press Enter. All we need here is this line:

We write the following into it:

kext-dev-mode=1 rootless=0 -v npci=0x2000 nv_disable=1
Let me explain what each of these arguments does:

kext-dev-mode=1 - necessary arg, without which the hack will not start. Allows you to upload kexts to the system (Initially, FakeSMC.kext).
rootless=0 - disables SIP (System Integrity Protection). Required arg.
-v - "Verbose mode". Instead of a beautiful apple, we will see a "console" download so that we can identify the error, if any.
npci=0x2000 (or 0x3000, depending on PCI-e version) - optional. We warn you that the download will stop at the stage of PCI scanning. You may not write.
nv_disable=1 - optional. To avoid artifacts during loading and other garbage, disable the graphical shell. Loaded in native graphics mode in orthodox 144p resolution. You may not write.

Fix

We reconnect the flash drive to another 2.0 port, boot with the following arguments:
kext-dev-mode=1 rootless=0 cpus=1 npci=0x2000 -v UseKernelCache=No

Missing Bluetooth controller transport - the video card did not turn on, or FakeSMC.kext did not work. Check that there is FakeSMC.kext in the kexts/other folder. Sinezub has nothing to do with it.

Fix

We load like this:

kext-dev-mode=1 rootless=0 -v npci=0x2000
Or like this:
kext-dev-mode=1 rootless=0 -v -x npci=0x2000

If such errors still remain, then we try to load like this:

kext-dev-mode=1 rootless=0 -v npci=0x3000 darkwake=0 nv_disable=1 cpus=1
In other cases, only Google will help, although these fixes should solve these problems.

We wait. At some points, it may freeze. If it hangs for more than a minute - reboot. Should help in some cases.

Fix

Move on…

Step 4. Basic system setup and installation of kexts

So here we are in the system. While she knows little, we will not go online, the graphics do not work, and in general everything looks somehow very bad. This needs to be corrected.

Let's understand what kexts are.

Now let's install the bootloader. Go to the PostInstall → Clover_v2.3k_r3949 folder. There is a *.pkg file, open it.

We click to continue, we read the information about the bootloader (I'm lying, also click continue). Next, in the lower left corner, click "Settings".

For UEFI boot, set the following settings:

Step 5Setting Up the Bootloader

We see something like this:

So here's where we need to dig. We set the arguments ourselves, depending on the system.

-v (verbose) - the already familiar "text" boot mode. It is better not to enable, but to prescribe manually if necessary.
arch - architecture. In my case x86_64
npci is the key we already know. We expose if necessary. I recommend doing the first boot without it, but in Verbose mode.
darkwake - responsible for sleep and hibernation. Has 7 modes. If the dream does not start by changing the hibernatemode in the terminal, then I recommend using trial and error to find the desired darkwake mode.
cpus=1 - start using only one core. I do not recommend choosing.
nvda_drv=1 - activation of the Nvidia webdriver, which we will install a little later. Choose if you have nVidia.
nv_disable=1 - disable graphics invisibility and run on the native poppy driver. It is better not to choose, but if necessary, manually prescribe.
kext-dev-mode=1 and rootless=0 have already been explained before.

We pass to the right subsection.

Default Boot Volume - the partition from which, by default, the selection of a disk for booting will begin. By default, LastBootedVolume (last partition selected).
Legacy - Legacy Boot for older versions of Windows and Linux. It very much depends on the hardware and BIOS construction, so several algorithms have been developed:
LegacyBiosDefault - for those UEFI BIOSes that have the LegacyBios protocol.
PBRTest, PBR - variants of PBR Boot, it's just overkill. In my case PBR works.
XMPDetection=YES is an important parameter. Fixes the amount of RAM, slots, dice, frequency and number of channels.
DefaultLoader - if there are several loaders on the partition, select the default one. Must not be empty!
Timeout - time to automatic boot.
Fast - a parameter that skips selecting a partition and immediately proceeding to boot.
-1 (Timeout -1) - disable autoboot.

Do not touch the Inject NVidia parameter! There will be artifacts at launch. It is designed to run old GT line cards

Kernel and Kext Patches - patches and kernel customization. By default, Apple RTC is selected. Better not to touch. SMBIOS - the most juice, customization and fake "poppy".

To set the factory information, click on the magic wand icon. Next, select iMac (if PC) or MacBook (if laptop).

ACHTUNG 3

You can also look among older configs, such as MacMini or Mac Pro. Your task is to choose the poppy that is most similar to your hardware.

Don't add anything to Memory and Slots. These are purely cosmetic parameters that the clover picks up at the loading stage. Incorrectly set parameters can cause conflicts.

WARNING: Nvidia graphics cards without policy-kext edits only work on iMac13.1 and iMac14.2 macs.

In AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext/Contents/info.plist we fix Config1 to none here:

Now it should work.

Step 6Install the graphics driver and reboot for the first time

Now let's make sure that we are not booting from a USB flash drive, but from hard drive in UEFI mode. Select Boot macOS Sierra from Macintosh HD. Let's start.

Note

Additionally

- Sound

Regarding AppleHDA

The following conditions must be met for it to work:

Availability of vanilla (pure) AppleHDA.kext kext in the system.
Having an HDEF section in your DSDT (or a clover fix FixHDA_8000->True)
Specify layout in DSDT (or in clover config.plist Devices->Audio->Inject->1,2,28...etc. Choose from those specified for your codec above)
Put away ALL sound patches (if they were in your config.plist) from the KextsToPatch section
Remove DummyHDA.kext (if used)
If you used VoodooHDA.kext - delete it. Also delete AppleHDADisabler.kext and rebuild the cache.
Intel HDMI 4000/4600 requires clover fix UseIntelHDMI->True

Actually, that's all. After we get macOS Sierra ready to go.

UPD from 05/14/2017

Tags:

apple
hackintosh
mac
hackintosh

Add tags

Kext, or kernel extensions (from the English Kernel Extensions) is a system component, from the set of which the OS structure is formed.
All kexts should be installed from the Release folder if there is no need for debugging.
The latest versions are suitable for all OS versions starting from 10.6.3, unless otherwise specified in the description of the kext itself.
The extensions listed here are somehow written or rewritten to work from EFI, so installing them on the system is not advisable, and sometimes even harmful.

General cakes.

VirtualSMC (vit9696) - github.com

Latest SMC emulator with 2nd generation SMC support. . From monitoring there are sensors on the CPU, laptop battery, auto-brightness on laptops with hardware support, desktop fans. To monitor CPU frequencies, an installed Intel® Power Gadget is required.

Monitoring software: iStat Menus or HWMonitorSMC2
The project is under development but you can already use it.

FakeSMC and sensors (Slice2009 / Vector sigma) -

Necessary kext for hackintosh. Tells the AppleSMC kext the keys that the SMC worked. Without it, the system will not start. Plugins allow you to scan information from the sensors of the motherboard. HWMonitor in the kit displays the readings of these sensors.

FakeSMC and sensors (Kozlek / RehabMan v6.26) - bitbucket.org

A slightly older but no less up-to-date version of the monitor.

It contains a slightly larger but at the same time slightly older chip base.

Fake PCIID and plugins (RehabMan) - bitbucket.org

Beginning with Haswell, any application or service can check the PCI-ID, regardless of what was reported during the initialization phase.
FakePCIID intercepts these requests and returns the value we specified via FakeID in clover or otherwise.
Plugins for FakePCIID have very versatile functionality, all work is described.

ACPIBatteryManager(RehabMan) - bitbucket.org

Driver for displaying battery status on laptops.
Often additional DSDT patches are required, which are described in the work with.

ACPIDebug(RehabMan) - bitbucket.org

For those who know what a kext is, there is no need to explain how it works.
And for those who don't know, they don't need it.
Instructions - bitbucket.org.

BrcmPatchRAM (the-darkvoid, RehabMan) - bitbucket.org

Loads Bluetooth firmware for Broadcom chips.
Instructions - bitbucket.org.

Lilu and plugins.

Lilu(vit9696) - github.com

Kext and process patcher. It does not affect anything by itself, it only works with the corresponding plugins, which are listed below.
Some plugins are not listed here because they come out frequently, and some are very narrowly focused.
All known plugins - github.com.
Information - github.com.

AppleALC(vit9696) - github.com

Kext for AppleHDA dynamic patching. The correct Layout is enough, and the sound works.
Table of supported codecs and layouts - github.com.
Instructions - github.com

WhateverGreen v1.2.5 =(Shiki + IntelGraphicsFixup + NvidiaGraphicsFixup)

WhateverGreen(vit9696) - github.com

Produces the necessary patches for AMD GPUs.
Starts sleep, creates a framebuffer "on the fly", loads 8000+ cards without Intel HD.
Not a cake, but a fairy tale for Radeon!
Instructions - github.com.

Shiki //

User-level patcher for a DRM-protected connection.
That is, it allows you to play movies / clips in iTunes, and similar operations.

Intel Graphics Fixup(lvs1974) //

Multifaceted patch for Intel HD graphics Ivy and above.
Fixes apple crash on boot, disables PAVP for Haswell graphics, and so on.

HibernationFixup(lvs1974) - github.com

A patch allowing the use of 3 and 25 sleep mods.
You can set the sleep mode with the command: sudo pmset -a hibernationmode 25
More information about sleep modes can be found in the discussions on applelife.ru and insanelymac.com
Project page -github.com

IntelGraphicsDMVTFixup(Barbara Palvin) - github.com

Patch to change the required amount of dedicated memory (DMVT) for Intel HD Graphics Broadwell and above.
Recommended only if you cannot change your DMVT.
You also need to turn off the patches that allowed you to bypass this, and rebuild the cache.
Project page - github.com.

NightShiftUnlocker(Austere-J) - github.com

Allows the use of NightShift (10.12.4+) on SMBios that do not support it (2011 and below).
Project page - github.com.

Network kexts.

AtherosE2200 v.2.2.2 (Meize) - vk.com www.insanelymac.com

Supports all Atheros models, upload panic fixed.

Broadcom NetXtreme 57xx is started by the Fake ID method.

FakePCIID is specified above, the package includes a plugin for BCM57XX_as_BCM57765.

IntelMausiEthernet v.2.4.0 (Meize) - vk.com www.insanelymac.com

Supports all Intel models.

Marvell Yukon 88E8056 v.1.0.0- vk.com www.insanelymac.com

Supports Yukon 88E8xxx. In any case, they are already dead.

RealtekRTL8111 v.2.2.2 (Meize) - vk.com www.insanelymac.com

Sound cakes.

AppleALC(vit9696) - github.com

Plugin for Lilu, which is placed above in a separate category of kexts. Information about it is there.

patched AppleHDA(Mirone)-

At the moment, this method is morally obsolete, and all platforms are already present in AppleALC.
It is unlikely that we will rework this article. Upgrade to either AppleALC or VoodooHDA.

VoodooHDA(Voodoo Team)-

Universal sound driver. Helps to start almost any sound.
For example, HDMI sound on Nvidia Pascal, or ALC269 without going through a bunch of layouts.
Remember - voodoo sounds great after great tuning!
Instructions - applelife.ru.

codeccommunder(TimeWalker, RehabMan) - bitbucket.org

Codec Commander is used as a solution that allows you to run an external EAPD amplifier on HDA codecs of laptops and some ITX boards. Typically, such amplifiers sit on the speaker or headphone node. When the codec loses power, the EAPD amplifier also loses power and it is impossible to turn it back on without additional help. Also, using hda-verb, you can manage the state of the nodes through the terminal or aml-table. Setup instructions will be later on the site, including very interesting PDFs.
Information - bitbucket.com.

USB cakes.

USBInjectAll(RehabMan) - bitbucket.org

For "lazy" factory USB on 10.11+. //USB factory via IOKit injection will be on our website soon.
Explanation - bitbucket.org .

XHCIMux(RehabMan) - Included in the FakePCIID above.

Enables the EHCI virtual bus (USB2.0) on Intel controllers of the Haswell generation and above.

GenericUSBXHCI(Zenith432, RehabMan) - bitbucket.org

Factory most XHCI controllers for 10.10 and below.
It also works on 10.11+, in case of a third-party controller.
Instruction -