Create Unibeast from Windows Machine

                           
Computer Requirements
You need a computer with Windows to run Mac OS X on Windows (of course). The "System Type" of your copy of Windows needs to be 64-bit, because OS X Mountain Lion is a 64-bit operating system. If you have a 32-bit copy of Windows, you can only install Mac OS X Snow Leopard on Virtualbox. You will need at least 4 GB of RAM and a dual-core (two core) processor or better. Personally, the computer I was using for this had a 4-core processor and 12 GB RAM, which is way more than enough. You also need about 10 GB of unused hard drive space.
Right click on "My Computer" on your desktop and click "Properties" to check the stats on your computer. If it doesn't directly tell you how many cores your processor has, look up your processor model on Wikipedia or Google. You also want to find out whether your processor is made by "Intel" or "AMD". Computers with AMD processors will not work with Mountain Lion. 
General Requirements
  • Virtualbox : This virtualization suite is free, and though it doesn't offer official support for Mac OS X, it works well enough.

  • iAtkos ML2: Unfortunately, the standard method for installing OS X Mountain Lion on PCs (which uses a paid copy of the Mountain Lion installer) doesn't work with Virtualbox. Instead, you'll have to distros like iAtkos, which is currently the most popular distro for Mountain Lion. I won't go into details, but you can download these copies from about any bittorrent website by using a bittorrent client (it's a ".dmg" file that's about 5 GB in size). 

  • Multibeast 4.6.1 : You will need to use Multibeast 4.6.1, our favorite Hackintosh post-installation tool, to set up the Mountain Lion virtual machine after the initial installation. While Multibeast 4.6.1 is an old version designed for Mac OS X Lion instead of Mountain Lion, in our case, it actually works better than newer versions of Multibeast. Registration is required on the tonymacx86 website to download this.

Step 1: Prep
Download Virtualbox, install it, and open it up. Also, if you want to be able to view USB devices from your OS X Mountain Lion virtual machine, download the Virtualbox Extension Pack and run it before going to Step 2.
Step 2: Create a new virtual machine.
Virtualbox lets you run Mac OSX within Windows by creating a virtual machine, which is a program that simulates a normal computer.  To create a virtual machine, open up Virtualbox and click "New" on the upper left. Give your new virtual machine a name, and choose "Mac OS X" for the OS Type.

If your version of Virtualbox asks you to choose between 64-bit and 32-bit, be sure to choose 64-bit. Choosing 32-bit will result in a critical "Guru Meditation" error later on.

I recommend assigning 4 GB of RAM to the virtual machine, but you can assign as little as 2 GB of RAM. Every time you turn on Mac OS X, that RAM that you assign here will be used to run the virtual machine. The RAM will be given back to your normal computer after you turn Virtualbox off.
You'll need to create a new hard disk for the virtual machine. Virtualbox will ask you what type of disk you want to create: VDI, VDMK, or VHD. VDI is the original format for Virtualbox, while VDMK is the format used by VMWare. If you're considering getting a copy of VMWare, you might want to choose VDMK. Otherwise, just choose VDI. I recommend creating a dynamically expanding disk; the only other option, fixed-size storage, will eat up your hard drive.
Step 3: Give your new virtual machine an operating system.
Your virtual machine will now be created. But don't stop now--you still need to change a few settings before your machine will actually work. Your new virtual machine will show up on the left column of the Virtualbox start page.  Select your Mac OS X virtual machine (single-click) from the main page of Virtualbox, and open up the virtual machine settings. Once the settings open up, go to "System" and uncheck the "Enable EFI" box. This is by far the most important single setting that you will need to change.
EFI, which stands for Extended Firmware Interface, is a feature that helps operating systems start up. Unfortunately, Mac OSX requires 'speshul' EFI, so the EFI that Virtualbox uses doesn't work.
Once you're done with that, go to the settings for "Storage". In the storage tree box, you'll see a CD icon labeled "Empty". Click on it and click "Choose a virtual CD/DVD disk file". In the window that pops up, choose the .dmg file for iAtkos ML2.

This way, when your virtual machine starts for the first time, it will boot into iAtkos.
Step 4: Install OS X Mountain Lion
Start up your virtual machine. You will come up to the iAtkos boot screen, with a CD icon in the middle.

After a few seconds, the virtual machine will automatically start the Mac OS X installer. (This startup process may take a few minutes.) Eventually, you will reach the welcome page of the installer.
Continue, and you will come up to a page that asks you for a "destination" for your Mac install. Oh no, the page is blank! We'll have to fix that. To do this, start up Disk Utility (located under the Utilities menu).

Mac OSX can only be installed on a completely clean disk, so you need to use Disk Utility to wipe your Virtualbox hard disk. Click on the Virtualbox hard disk in Disk Utility and erase it. Don't worry, there's nothing important on it.

On the installation summary page for Mac OSX, the Virtualbox hard disk should now be showing up. Click the "Customize" button on the lower left-hand corner of the summary page. This is where using a distro becomes really useful: iAtkos allows you to install extra Hackintosh drivers and kexts, straight from the Mac OS X Lion installer. The "Customize" page essentially does the same thing as Multibeast, though the layout (and most of the names of the options) are different.

The default selection will enable Mac OS X to boot from the virtual machine without any assistance. In addition to this selection, go to Bootloader Options -> Graphics Mode and choose whatever resolution best fits your monitor (in my case, I chose "1920x1080"). Selecting this won't actually change anything at the moment; however, you will need this for Step 7, when we make the screen of the virtual machine bigger.

Once you have selected the appropriate options from the "Customize" screen, return to the installation summary page and click "Install". When the installation finishes, Mac OS X will crash into a black screen with white text. This is normal; Mac OS X has installed successfully. Now proceed to the next step.

Step 5: Boot it up
Restart your virtual machine, and eject iAtkos from your virtual DVD drive. To eject iAtkos, right-click on the CD icon at the bottom right of the Virtualbox window, and un-check the iAtkos file. Your mouse cursor will probably be trapped inside the virtual machine. Press the right "Ctrl" key on your keyboard to allow your mouse to escape.

After ejecting iAtkos, restart your virtual machine again. Now, at the bootup screen, you'll see an icon for the hard drive where you installed Mountain Lion (also, the screen of your virtual machine might be bigger than before).

After a few seconds, Mountain Lion will boot, and you should eventually be led to the Mac OS X setup screen. Fill it out, then mission accomplished!

This concludes the first part of the guide. However, you're not done yet! You still have to enable sound on your virtual machine, and increase the screen resolution.

Step 6: Enable sound
By default, your ethernet (internet) should work in the virtual machine. However, the virtual machine will not have sound, or be able to boot from the hard drive without help. To fix this, open Safari, and download Multibeast 4.6.1. While Multibeast 4.6.1 is an old version designed for Mac OS X Lion instead of Mountain Lion, in our case, it actually works better than newer versions of Multibeast. Registration is required on the tonymacx86 website to download this.

DOWNLOAD: Multibeast 4.6.1

Before starting Multibeast, you have to go the "Security" section of System Preferences in Mac OS X, go to the "General" section, and check "Anywhere" in the "Allow applications" section. Once that's done, run Multibeast and install the following options.

That's all there is to it; restart your virtual machine. Mac OS X will now be able to play audio normally. Congratulations!

Step 7: Make the screen bigger
Though this step is optional, I still recommend you do it anyways. Anyways, when you first use your virtual machine, you'll probably notice one thing: your screen resolution is 1024x768. Since Virtualbox doesn't "technically" support Mac OS X, there's no official way to change this. But here's how you can change it anyways.

First, turn off your virtual machine. Open the Command Prompt in Windows (make sure you are logged into an Administrator account on Windows). You can do this by opening the Start Menu, and typing "command prompt" into the Start Menu search bar. Then, type the following command into the Command Prompt.

cd "C:\Program Files\Oracle\Virtualbox"

This command will change the focus of the Command Prompt to the program folder for Virtualbox (if you installed Virtualbox somewhere different, then change the command to wherever you installed it). Next, type in this command:

vboxmanage setextradata "Name of virtual machine" "CustomVideoMode1" "1920x1080x32"

This command activates "vboxmanage", a command-line program included with Virtualbox that allows you to edit the properties of your virtual machine, including its built-in resolutions. Replace "Name of virtual machine" with the name of your virtual machine-- you can find the name of your virtual machine in the left pane of the Virtualbox main window (in the screenshot below, my virtual machine is named "Mountain Mac 2"). Replace "1920x1080x32" with whatever resolution you're using.

Press the enter key to submit the command. Once that's done, start your virtual machine again.

 Your virtual machine will now boot Mountain Lion in full resolution. Congrats!
Download and run Unibeast -> install Unibeast to your USB drive
Done!!!!
Boot0:Error Fix

Boot0:Error Fix

                                                            Easy way to Fix boot0:error



The Issue:
Upon successful installation, boot from hard drive results in this:

Loading Operating System …

boot0: GPT
boot0: test
boot0: test
boot0: GPT
boot0: test
boot0: test
boot0: error


The Actual Problem: 
With disk drives getting larger and larger manufacturers have had to change the default block size from 512 bytes to 4,096 bytes. These new drives are known as "Advanced Format" or 4K drives. Initially this was only seen on drives larger than 1 TB but will soon be on all drives. As part of this change there is an issue with OS X writing the boot helper code to these drives when booted from the drive. Because of this they require a workaround to boot on their own.

Solution 1: Use UniBeast
Pros: Easy- OS X Only
Cons: Requires use of the Terminal and UniBeast drive.

How To Do it:
1. Install using UniBeast
2. Boot new installation using UniBeast created USB.
3. Run MultiBeast and install as normal
4. Reboot system back into OS X installer.
5. Run Disk Utility and unmount the drive you installed OS Lion on.
6. Launch Terminal and execute the following command:

Code:
dd if=/usr/standalone/i386/boot1h of=/dev/disk0s2
7. Exit Terminal
8. Reboot Normally

NOTE: The above instructions are based on OS X being installed to a hard drive connected to SATA port 0. If you are using a different port you will need to get the drive device name from Disk Utility by selecting the volume and clicking Info.
HP ProBook - Mavericks

HP ProBook - Mavericks

                                    

Introduction


New Hp laptops series have UEFI implemented in BIOS, and it provides much more advantages over current BIOS-based bootloaders like Chimera/Chameleon.
- Faster BIOS boot time
- Easier OS X install/Upgrade with native methods
- Create and boot to Recovery HD, which enables Find My Mac option.
- Patching kexts on the fly
- Bootmenu customization
- Can boot to Windows UEFI (which recognizes > 4 partitions GPT drive)
- Don't need to mess with master boot records
- Native NVRam on 7-series laptops

The guide is for:
- 6-series laptop: HP Probook 4x30s, 6x60b, Elitebook 8x60p, 2x60p using 6-series chipset
- 7-series laptop: HP Probook 4x40s, 4x0, 6x70b, Elitebook 8x70p, 2x70p using 7-series chipset.
*Only HP Elitebook/Probook 6xx0b without Radeon card is supported
* HP Probook 4xx0s with/without Radeon card is supported
You can download the latest Clover files here:
https://www.dropbox.com/sh/083x2j1mvmfh4l9/ZSYm2_iQRf

*Always search in the first post before asking questions*

Known issues

- Distorted bootscreen with 7-series laptops using 1366x768 display + UEFI native (without CSM) setting. Changing Clover resolution to 1024x768 can fix it.

- Sleep is not reliable on 6-series laptops. It can cause the system to auto restart some minutes after wake.

- Use HaltEnabler or other SLP_SMI_EN keys in config.plist may brick your laptop, the only way to solve is reflash your ROM! They are disabled by default but AVOID IT AT ALL COST

- There is 10s-15s delay before going to sleep. It's a function (or a bug?) in Mavericks, even on real Mac (confirmed by RehabMan)

- Find My Mac does not work properly. Don't lock your mac because it's hard (or unable) to unlock again.

- NVRam in 7-series laptops only remembers the last boot partition value, others (like Find My Mac, Boot theme) are lost after restart. You can install EmuVariableUefi-64 to have Emulation nvram.

- Battery status is slow to update on some 4540s. If you have the problem, remove EmuVariableUefi-64.efi.

Guide changelog

12/10/2013: Added Mavs Style small S and bluemac S theme for Clover stretched screen.
12/8/2013
: Added HPFanReset.efi by RehabMan to work with DSDT Fan patches. Current users can use it by downloading the drivers here and put it to EFI/CLOVER/drivers64UEFI/, then repatch DSDT by PBI.

12/5/2013: Change Clover's SSDT by PBI's SSDT.aml. Added Mavs Style small theme by CosmosCJ. Change InjectKexts from Automatic to Detect.
11/17/2013
: Update the Clover download link for latest version, which caused some problems with latest config.plist.

11/13/2013
: New Clover bootloader with InjectKexts=Automatic. Now Clover will automatically detect if FakeSMC is already in kernel cache to inject kexts. Cleanup the guide.
11/5/2013: Some improvement in the guide and config.plist, remove Default Boot section because DefaultVolumes key is ignored. Added GenericUSBXHCI and ProbookARPT kexts to Clover.zip
11/1/2013: Some minor improvement in the guide, Fast Boot, SSDT and Sleep sections. New config.plist drops CPU SSDT tables only, instead of dropping all OEM SSDT tables. Added console spamming fix in Customization
10/29/2013: Make the guide easier to follow, add RealtekRTL8111 to Clover.zip and remove USB fixes in Config.plist
10/28/2013: Add DropOEM SSDT in config.plist to fix default behavior on laptops using Sandybridge CPU.


Install OS X Mavericks

1. Create partition for Clover bootloader:
- Create a FAT32 partition on USB drive (GPT or MBR partition table), with size at least 100MB and extract all files from Clover.zip to that partition.
- Select the right config.plist in config.zip and copy to EFI/Clover/.

2. Create Mavericks Installer partition (need a Mac):
- Use Disk Utility to create a Mac OS Extended (Journaled) partition, size at least 6GB on USB drive (it can be the same drive with 1st step, or another drive), name it "Untitled".
- Download Mavericks Install app from AppStore.
- Launch terminal and run the following script:
Code:
"sudo /Applications/Install\ OS\ X\ Mavericks.app
/Contents/Resources/createinstallmedia --volume /Volumes
/Untitled --applicationpath /Applications/Install\
 OS\ X\ Mavericks.app --nointeraction"
- Your Mavericks Installer partition will be renamed "Install OS X Mavericks"

3. Enable these options in BIOS:
6-series laptop: UEFI Boot.
7-series laptop: UEFI Native without CSM or UEFI Hybrid with CSM (if you have Windows Legacy)
Disable Wake on LAN.

4. Plug all the flashdrives in step 1 and 2 to USB 2.0 ports. Restart and press F9 to choose Boot devices > Boot from EFI file > choose your Clover bootloader partition > EFI > Boot > BOOTX64.efi

5. Clover bootloader screen shows up, select "Boot OS X Install from Install OS X Mavericks" (your Mavericks Installer partition).

6. Install screen will appear, use Disk Utility to format your drive as GPT, create a Mac OS X Extended (Journaled) partition and Install Mavericks. The installer will extract necessary files to "Install OS X Mavericks" (not your target partition). This takes a lot of time at the end, though you only see "a minute remaining". This will end PHASE 1.

7. Restart and press F9 to choose Boot devices > Boot from EFI file > choose your Clover bootloader partition > EFI > Boot > BOOTX64.efi

8. Clover bootloader screen shows up, select "Boot OS X Install from Install OS X Mavericks" (your Mavericks Installer partition, not your install target partition).

9. Install screen will appear and continue installation. This time, installer will install files to your target partition and create Recovery HD partition. This will end PHASE 2.

10. Restart and press F9 to choose Boot devices > Boot from EFI file > choose your Clover bootloader partition > EFI > Boot > BOOTX64.efi

11. Clover bootloader screen shows up, select "Boot OS X from YourPartition".

12. If everything goes well, you can boot straight to Mavericks desktop.

13. Download HP Probook Installer here http://www.tonymacx86.com/hp-probook...s-support.html and install with these options:

OS X support kexts: select only the version that matches your laptop (4x30s, 4x40s, etc).

DSDT generator/patcher:
- ProBook model: your Probook Model
- Fan behavior: your prefered fan methods, need HPFanReset.efi to work.
- Display type: your display
SSDT generator/patcher: Generate SSDT.aml for your CPU Management
Optional patches:
- Intel USB3.0 patch: allows the use of vanilla AppleUSBXHCI.kext instead of GenericUSBXHCI.kext. This USB3 patch is valid only if you have a 7-series chipset.

Note: you must select one option from each of the first three groups to generate a patched DSDT.

Optional hardware-specific fixes:
- AHCI 3rd party kext: You can apply this option later if it turns out your DVD drive is not recognized by the system. It is not needed on every laptop.
- EDID generator: Inject correct display EDID to your system.
Misc OS X fixes:
- Color profiles: Recommended.
- Sleep fix: disables OS X version of "hybrid sleep" where upon entering sleep, a "hibernation image" is written to the boot drive. Recommend for SSD.
- blinkscreen: This option will very quickly "blink" the screen when you login, fixing the brightness issues:
Intel HD 3000: Screen brightness levels are not available before the first display sleep on
Intel HD 4000: The display is dimmed before the first display sleep on

Extra tools: All optional. Select the ones you want.

After making your selections, click 'Continue' and allow the ProBook Installer to work.

14. (Optional) Restore vanilla AppleIntelCPUPowerManagement.kext, AppleRTC.kext (they're backed up in desktop) by using Kext Wizard.

15. Download latest Clover here: http://sourceforge.net/projects/clov...les/Installer/ (Download latest version in folder, not in "Looking for the latest version?") Run the installer with Customized options:
Install for UEFI motherboards
Themes: Choose your desired themes
Drivers64UEFI:
- EmuVariableUefi-64 (not needed on 7-series laptops)
- OsxAptioFixDrv-64
Install RC scripts on target volume
Install Clover Preference Pane

16. Clover installer will automatically mount your EFI partition and copy Clover bootloader files there. Copy following files to EFI partition of your internal drive (don't mistake with EFI partition of other drives):
- Copy patched DSDT.aml and SSDT.aml created by PBI from /Extra folder to /EFI/Clover/ACPI/patched/
- Copy config.plist from USB to /EFI/Clover/
- Copy HFSPlus.efi and HPFanReset.efi in /EFI/CLOVER/drivers64UEFI/ from your USB to /EFI/CLOVER/drivers64UEFI/ in EFI partition, remove VBoxHfs-64.efi

17. Install Clover Configurator here: http://www.osx86.net/files/file/49-clover-configurator/ , open config.plist with CC and edit those values:
- ACPI > GeneratePStates/CStates: uncheck
- Gui > Theme: set your theme name
- SMBIOS: create your new SMBIOS with random Serial Number

18. Recheck if config.plist, dsdt.aml and ssdt.aml are placed correctly in EFI partition of internal drive.

19. Restart, you should see Clover screen and option to boot to Mavericks. Enjoy!

Update OS X Mavericks

10.9.1: Run the update and restart, then run PBI again and select OS X Support Kexts > your laptop.

Install Windows UEFI as dual boot

Install Windows UEFI (and other UEFI OSes) are quite easy because you don't need to mess up with Boot records. See FAQ for more detail.

1. Create your Windows UEFI install USB key by following the guide here:
http://www.eightforums.com/tutorials...e-windows.html

2. Use Disk Utility or GParted to create a partition with Mac OS X Extended format on hard drive for Windows. This will prevent OS X from convert your drive to GPT/Hybrid MBR.

3. Restart and press F9 to choose Boot devices > Boot from EFI file > choose your Windows Install USB key > EFI > Boot > BOOTX64.efi

4. Use Windows installer to format the partition you prepared as NTFS. Complete install and now you will boot to Windows by default, Clover disappears.

5. Restart and press F9 to choose Boot devices > Boot from EFI file > choose your EFI partition (which contains Clover bootloader) > EFI > Clover > CLOVERX64.efi

6. You can now see Clover bootloader with new entry "Boot Microsoft UEFI Menu from EFI".

7. Boot to OS X and use Clover Configurator to mount EFI partition of your Windows UEFI drive (in case you have installed Windows to second drive, select disk1s1). Go to EFI/Microsoft/Boot/ and rename bootmgfw.efi to bootmgfw-orig.efi

8. In EFI partition containing Clover bootloader, remove EFI/Boot/bootx64.efi and copy EFI/Clover/CLOVERX64.efi to EFI/Boot/ and rename it to BOOTX64.efi

9. Restart.

Migrate from Chimera/Chameleon bootloader to Clover

CAUTION: You can't use Clover UEFI on MBR drive.

1. Boot to OS X, download latest Clover here: http://sourceforge.net/projects/clov...les/Installer/ (Download latest version in folder, not in "Looking for the latest version?"). Run the installer with Customized options:
Install for UEFI motherboards
Themes:
Choose your desired themes
Drivers64UEFI:
- EmuVariableUefi-64
(not needed on 7-series laptops)
- OsxAptioFixDrv-64
Install RC scripts on target volume
Install Clover Preference Pane

2. Clover installer will automatically mount your EFI partition and copy Clover bootloader files there. Copy following files to EFI partition of your internal drive (don't mistake with EFI partition of other drives):
- Copy patched DSDT.aml and SSDT.aml created by PBI from /Extra folder to /EFI/Clover/ACPI/patched/
- Extract config.plist from config.zip and copy it to /EFI/Clover/
- Copy HFSPlus.efi and HPFanReset.efi in /EFI/CLOVER/drivers64UEFI/ from your USB to /EFI/CLOVER/drivers64UEFI/ in EFI partition, remove VBoxHfs-64.efi

3. Use Clover Configurator here: http://www.osx86.net/files/file/49-clover-configurator/ to edit some values in your config.plist:
- ACPI > GeneratePStates/CStates: uncheck
- Gui > Theme: set your theme name
- SMBIOS: create your new SMBIOS with random Serial Number

4. (Optional) Restore vanilla AppleIntelCPUPowerManagement.kext, AppleRTC.kext by using Kext Wizard.

5. Recheck if config.plist, dsdt.aml and ssdt.aml are placed correctly in EFI partition of internal drive.

6. Restart to BIOS and enable these options in BIOS:
6-series laptop: UEFI Boot.
7-series laptop: UEFI without CSM.

7. Save settings and exit, you should see Clover screen and option to boot to Mavericks.

*If you get problems with new Clover bootloader, turn off UEFI settings in BIOS and you will get Chameleon/Chimera back*

Config Clover

I suggest that you always update to the latest Clover Configurator to avoid removed keys in latest Clover

1. Mount EFI partition

The recommend way is using Clover Configurator to mount EFI partition (Extra > MountEFI). Note that you have to unmount existing EFI partition first.

To mount EFI partition, you can use the following command in terminal:
Code:
diskutil list
mkdir /Volumes/EFI
sudo mount -t msdos /dev/disk0s1 /Volumes/EFI  
--Note:  if diskutil tells you your mavericks install is on disk1, disk2, etc change /disk0s1 appropriately.
2. SSDT

SSDT CpuPm and Cpu0Ist have to be dropped to avoid conflict with new CPU SSDT tables. You shouldn't drop all OEM SSDT tables because some tables is benefitcal like SataAhci or PtidDevc SSDT (it can slow down sata in rare chance).
Code:
        <key>DropTables</key>
        <array>
            <dict>
                <key>Signature</key>
                <string>SSDT</string>
                <key>TableId</key>
                <string>CpuPm</string>
            </dict>
            <dict>
                <key>Signature</key>
                <string>SSDT</string>
                <key>TableId</key>
                <string>Cpu0Ist</string>
            </dict>
        </array>



SSDT can be generated automatically by select Generate in config.plist:
- GeneratePStates
- GenerateCStates

If you want to use SSDT.aml, remove Generate and put your SSDT.aml to EFI/Clover/ACPI/patched/

3. Fast Boot

To reduce the BIOS checking time (HP logo on screen) significantly by 5-6s, you can turn on Fast Boot in BIOS (it will be disabled if you installed HP Protect Tools in Windows). Please note that this will disable mouse devices and booting to USB devices from Clover bootscreen. To enable Full Boot temporarily, press ESC at boot and select Continue Startup.

To bypass the Clover bootscreen, set Boot/Timeout to 0. You can trigger the Clover bootscreen by pressing any key right after HP logo disappears.

4. Legacy OS boot

If you have Legacy OSes installed, you can enable Clover to boot legacy OS by editing your config.plist:
- Gui > Scan > Custom: check Legacy
- Boot > Legacy: LegacyBiosDefault

For 7-series laptops, you also have to select UEFI with CSM in BIOS.

5. Disable wake up by USB devices


To prevent USB devices from waking up your sleep, add this to your Devices section in config.plist
- USB Inject
- Add ClockID

6. Patching Kexts on-the-fly

Clover can patch your kexts in kernel cache on-the-fly in KextsToPatch section. Clover will find bits value in your specified kexts and replace it. AppleRTC and AppleIntelCPUPowerManagement are patched by default in Kernel and Kext Patches:
- AppleRTC
- ASUS AICPUPM

You can patch other kexts in Config.plist. Note that the config.plist uses 64-base value, while Clover Configurator shows your hexa value.

Trim Enabler
CC: 4150504C4520535344 -> 000000000000000000
config.plist
Code:
            <dict>
                <key>Comment</key>
                <string>Trim Enabler</string>
                <key>Find</key>
                <data>
                QVBQTEUgU1NE
                </data>
                <key>Name</key>
                <string>IOAHCIBlockStorage</string>
                <key>Replace</key>
                <data>
                AAAAAAAAAAAA
                </data>
            </dict>



AppleHDA:
Patch AppleHDA kext on-the-fly with Clover bootloader



7. Custom Entry

You can customize entries in Clover bootscreen. A typical entry looks like this:
Code:
                <dict>
                    <key>Disabled</key>
                    <false/>
                    <key>FullTitle</key>
                    <string>OS X Mavericks</string>
                    <key>Hidden</key>
                    <false/>
                    <key>Hotkey</key>
                    <string>m</string>
                    <key>InjectKexts</key>
                    <false/>
                    <key>NoCaches</key>
                    <false/>
                    <key>SubEntries</key>
                    <true/>
                    <key>Type</key>
                    <string>OSX</string>
                    <key>Volume</key>
                    <string>Your MacHDD UUID</string>
                </dict>





Note that the Volume value is your drive UUID in Clover bootloader, not UUID shown in OS X. You can find it in /Library/Logs/CloverEFI/boot.log. A guide for Custom Entry can be found here: http://clover-wiki.zetam.org/Configu...stom-/-Entries, it's recommended to create custom entries by Clover Configurator.



The custom entry will be added in Clover boot screen if it's matched. Other entries will be scanned if you set Scan Entries to true.

Hidden entries can be shown by pressing F3 in Clover bootscreen. Here are some useful custom entries.

Disable UEFI Internal entry:
Code:
                <dict>
                    <key>Disabled</key>
                    <true/>
                    <key>FullTitle</key>
                    <string>UEFI Internal</string>
                    <key>Hidden</key>
                    <false/>
                    <key>SubEntries</key>
                    <true/>
                    <key>Type</key>
                    <string>Other</string>
                </dict>



Inject kexts for Recovery partition:
Code:

                <dict>
                    <key>Disabled</key>
                    <false/>
                    <key>FullTitle</key>
                    <string>OS X Recovery</string>
                    <key>Hidden</key>
                    <true/>
                    <key>InjectKexts</key>
                    <true/>
                    <key>NoCaches</key>
                    <false/>
                    <key>SubEntries</key>
                    <true/>
                    <key>Type</key>
                    <string>OSXRecovery</string>
                </dict>



Modified Windows custom entry
Code:

               <dict>
                    <key>Disabled</key>
                    <false/>
                    <key>FullTitle</key>
                    <string>Windows 8.1 Professional</string>
                    <key>Hidden</key>
                    <false/>
                    <key>Hotkey</key>
                    <string>w</string>
                    <key>Path</key>
                    <string>\EFI\Microsoft\Boot\bootmgfw-orig.efi</string>
                    <key>SubEntries</key>
                    <true/>
                    <key>Type</key>
                    <string>Windows</string>
                    <key>Volume</key>
                    <string>Your EFI partition UUID</string>
                </dict>




Frequently Ask Question

1. Spotlight Console spamming

When you mount a FAT32 or faulty partition in Mavericks, especially EFI partition, Spotlight will try to index your partition and fail, which lead to tons of console errors. To disable permanently spotlight in a specific partition, go to that partition and create .metadata_never_index file by using the following command in terminal:
Code:
touch .metadata_never_index
2. Recovery partition

If you don't have a Recovery partition, you can create one by using RecoveryHDUpdater:
https://plus.google.com/104196173613...ts/6fPkZSoiDHs

To boot to Recovery partition, place all your essential kexts (FakeSMC, VoodooHDA, network kexts) in EFI/CLOVER/kexts/10.9

3. Sleep

Turn off Wake on Ethernet in System Preferences and BIOS. If you have trouble with auto-wake caused by USB devices, turn off Wake on USB in BIOS, or disable wake by USB in your config.plist (see above).

Some HP laptops have fingerprint sensor. If you disable it in BIOS, your system will auto wake after sleep. Enable it in BIOS will fix this

4. Reinstall or Update Clover bootloader

Make sure you unmount EFI partition before reinstall/update Clover. Run the installer with your settings. Then go to EFI/CLOVER/drivers64UEFI/ and remove VBoxHfs-64.efi.
Always check the information of new Clover version before updating.

5. Install Chameleon

Set up your Chameleon bootloader, Extra partition, patch AICPM and AppleRTC kexts, then turn off UEFI in BIOS.

6. How to know if you're installing Windows UEFI

In 7-series laptops, if your Windows installation can boot with UEFI (without CSM) option in BIOS, you're installing Windows UEFI.
In 6-series laptops, use gdisk to check if your drive is GPT/Protective MBR. Only Windows UEFI can install to GPT/Protective MBR drive.

7. Can't install Windows UEFI because it says this is a MBR drive

If you use Disk Utility to create a FAT partition, your drive will be converted to GPT/Hybrid MBR. To fix this, delete or reformat that FAT partition to Mac OS Extended, or use gdisk in Linux usb to convert your drive to GPT/Protective MBR.

 

AMD ATHLON X2 x6 with Mavericks (10.9.1)

AMD ATHLON X2 x6 with Mavericks (10.9.1)

AMD ATHLON X2 x6 with Mavericks (10.9.1)

SWX3Rr9.jpg

This is my third guide and I finally know my way pretty damn well around Hackintoshes. My latest build has Mavericks working almost perfectly (very minor graphical glitches and no iCoud). I decided to make a guide because there are lots of AMD users dying to get their hands on Mavericks working properly.

Before before we start, please don’t hesitate to ask any questions. This guide isn’t anything perfect so I do understand if you get lost. I’ve tried my best to correctly put everything you may need in. I will be able to help a lot though so don’t worry if you get lost. 

Before we start:

This build involves 2 hard drives, OS X being on one and Windows being on the other for dual booting. I have not yet been successful with OS X and Windows on the same hard drive. If you have only one hard drive you can follow this guide to install OS X and then maybe try the dual boot yourself outside the guide. As I said, I don't know how to do this so won't be able to help at all.

The build: 
  • AMD Athlon X2 x64 @ 3.3Ghz
  • Biostar A780L Motherboard
  • ATI Radeon HD5770
  • 4GB DDR2 RAM
  • TrendNet TEW-648UBM USB wireless adapter
  • Apple Wired Keyboard
The ingredients:
  • OS X 10.9 Install DMG (download from the AppStore for free or via a torrent for stable speeds)
  • A working Hackintosh or real Mac
  • Pandora Installer (here)
  • 10.9 AMD kernel (here)
  • 8GB flash drive
  • OPTIONAL: Another 8GB flash drive
  • Kexts needed for your build
  • VoodooHDA Installer (here)
  • System.kext bundle (here) (its called AMD _Kernel_And_PM_rel2)
  • MyHack (here)
  • Kext Utiliy (here)
The reason I use two flash drives is just to save my skin. Hackintosh is not perfect so tiny things can really mess it up. I make a flash drive that is identical to the first one with the installer on. This is just incase anything goes wrong with the first one, and this second one I keep in a safe place in case my Hackintosh messes up for any reason. Its entirely up to you to use the second one, it is not needed for the installer at all.

Also I uploaded the kernel to Zippyshare cause I honestly cannot remember when page I got it from from THIS thread, and it would take forever to find that again.

Native Support for Intel Haswell CPUs in OS X 10.8.5

Native Support for Intel Haswell CPUs in OS X 10.8.5


As of 10.8.5, Intel's 4th Generation Haswell CPUs and 8-Series chipsets are natively supported in OS X! This means that there is no further need for HaswellHelper or any other installation complications. Systems will work with the standard UniBeast installation method, as long as the USB is prepared using the freshly updated 10.8.5 app.

Apple has also added native drivers for Haswell's Intel HD 4600/5000 integrated graphics. Be sure to use Chimera 2.2 for support via GraphicsEnabler=Yes. We've just posted a refresh to our monthly Buyer's Guide, and we'll be posting details and benchmarks from some of our own test rigs in the coming days. Exciting update!
Update Your Mavericks App to 10.9.1

Update Your Mavericks App to 10.9.1



http://www.tonymacx86.com/attachments/77214-install109.jpg.html
The original installation media for Mac OS X Snow Leopard was a 10.6 DVD. The DVD was only updated once to version 10.6.3. In order to provide more frequent updates to users, Apple is now slipstreaming the latest version of OS X directly into the download. Upon fresh installation, no updating is necessary!
  If you downloaded Mavericks from the App Store prior to December 16, 2013, you most likely have 10.9. To re-download Mavericks and update your Installation App to 10.9.1, simply log into the Mac App Store and click Download. When the download finishes, the app will automatically open. The updated 10.9.1 Install OS X Mavericks App can be found in the Applications folder. You can then re-create your UniBeast installation USB.