Thursday, April 7, 2016

Hackintosh Boot Flags


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

Clover Boot Flags:

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

 -v 

Safe Mode:

 -x 

Single User Mode:

 -s 

 Zone Postponing: (use if hanging)

 -no-zp 

Single CPU core mode:

 cpus=1 

No Kext Cache Mode: (When changing kexts)

 -f 

Disables VT-x or VT-d:

 dart=0 

Verbose Mode:

 -v 

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

 nvda_drv=1  

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

 nv_disable=1 

Kext Dev Mode:

 kext-dev-mode=1 
  
If you're stuck at [PCI Configuration Began]:

 npci=0x2000 
 npci=0x3000 

Set Maximum Memory (RAM): (In megabytes)

 maxmem=4096 
 maxmem=8192 

Troubleshooting:

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

 -v -x -s -no-zp 

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

 -v -x -s nv_disable=1 

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

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

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

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

Common Issues:

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

Comment any issues you have and I could recommend you a set of bootflags to use!
Share This:    Facebook Twitter Google

8 comments:

  1. Hi i have an gtx 960 and crash right after the [IOBluetoothHCIController][start] -- completed

    but nv_disable=1 doesn't help the problem and i can't install nvidia drivers from safe mode, what to do? :o

    ReplyDelete
  2. After days of trying every possible thing I could think of, as well as every proposed solution I could find online, I chanced upon this page, and the "nv_disable=1" flag managed to compensate for my nvidia gt-730 card (for which I could find no suitable driver), and now I'm able to boot into Mavericks, . . . FINALLY ! THANK YOU ! Mel.

    ReplyDelete
  3. what is "reason=Mac-F22788A9" can bootflags changing cure it???

    ReplyDelete
  4. What boot args should I use with clover on a hackintosh? My error says reboot with proper boot device. Please help

    ReplyDelete
  5. I'd recommend reinstalling macOS, your computer does not recognize a bootable drive (I.E. There is no operating sustem). If you've made any progress, reply and I'll try and help you out!

    ReplyDelete
  6. OK, this is killing me!!!!

    I have a HP Pavillion g7 laptop (iCore3, 8GB Ram, 1.5TB Drive Intel 3000 video) that I have had running Mavericks, El Capitan, and now I'm trying to get Sierra on there. I'm using UniBeast 7.0.1 to create the USB drive and Clover 3923 as the boot loader.

    I'm using the following boot args in clover:
    dart=o nv_disable=1 -v -x -f cpus=1
    And I checked off APCI disable in the Clover CPU options.

    I keep getting the following kernel panic:

    panic (cpu 3 caller 0xfffff000041873): "Local APIC error, ESB: 64\n"0/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3709.1.32/osfmk/i386/lpaic_native.c:770"

    Below that It lists my boot args, but the only ones that show up are "-v -x"

    Anyone got a clue on this????

    ReplyDelete
  7. My loading stops at 50% and after that the apple logo show stop sign

    If i use -v
    Then some coding stop and show still waiting for root device
    What should i do plzzzz help

    ReplyDelete
    Replies
    1. Hello sorry my english, if you have "still waiting for root device" maybe you must change your Sata mode to AHCI on your bios regards

      Delete