Search the Community

As the title suggest, this guide will make you able to boot directly an NVMe drive with older motherboard that does not support booting trough NVMe protocol natively. Some preparation and checklist is including (and not limited to): Other PC that will be used to prepare the Bootable clover USB drive - Or you can use your target system that already have OS installed in other drive (SATA SSD/HDD) Motherboard with at least 1 free PCIe slot - having physical PCIe x4 or larger that unoccupied will help, but you can also put the NVMe drive in PCIe x1 slot with some speed penalty Motherboard with USB boot capabilities - Please beware, sometimes SD/MicroSD card reader built inside your laptop may doesn't support boot mode inside the BIOS An PCIe NVMe drive - Make sure it's not a M.2 SATA or M.2 PCIe AHCI SSD! A M.2 M Key to PCIe x4 adapter - for motherboard that only have PCIe x1 slot free, please bought applicable adapter or you can butcher either your adapter or motherboard PCIe slot (NOT RECOMMENDED) An unused USB drive or SD Card/MicroSD with the USB adapter - 2GB or more in capacity with good transfer speed recommended, but you can getaway with smaller drive (at least 128MB or more) Internet connection - For downloading the clover files Tested system: Dell Inspiron 3647 / Vostro 3900 (i3-4160) + Samsung PM891a 512GB NVMe SSD - Windows 10 - UEFI (Used in this guide) Lenovo ThinkPad T430 (i7-3610QM) + Western Digital SN530 256GB SSD - Manjaro 20 KDE Plasma - UEFI Lenovo ThinkPad T400 (C2D P9700) + Western Digital SN530 256GB SSD - Manjaro 20 KDE Plasma - UEFI Asus X453MA (Pentium N3540) + Kingspec NE 2242 128GB SSD - Windows 10 - UEFI ASUS Z8NA-D6C (2x Xeon X5650) + Samsung 960 Evo 256GB - Windows 10 - UEFI Asrock P4i945GC (Pentium 4 550 HT) + Kingspec NE 2242 128GB SSD - Debian 10 XFCE Minimal - Legacy Guide (Windows - Type all command without the quotation mark): Make sure your NVMe drive is recognized in other system, you can do this by booting an OS from officially supported media, and see if partition in the drive is either detected or mounted, or you can launch your OS specific disk drive manager like Windows Disk Management (windows) or lsblk (Linux) and see if the NVMe drive is detected. Download the clover files here - Choose the latest release, in the case of writing this article is CloverV2-5155.zip Prepare your SD/USB drive, make sure you backup your important data before formatting it. launch diskpart, either trough run or windows search or command prompt/Windows Terminal/Powershell, this will prompt windows admin warning, click OK to continue Now type "list disk", and you can identify which drive is the USB drive you mount by see the total capacity (in my case is disk 2) Type "select disk X" (X = your SD/USB disk number, eg. "select disk 2), and type "clean" to delete all partition (WARNING - YOUR DATA WILL BE DELETED) Now open windows Disk Management, and find your SD/USB disk that already been formatted, right click on formatted partition, and select "New simple volume" option For the size, type "512" (in MB; for USB/SD drive capacity more than 512MB), and click next, and select your desired drive letter path (or use default assigned by windows) and click next For filesystem, choose FAT32, with default allocation size, and volume label "clover" for ease of navigation later and click next and finish After your new partition is successfully mounted, extract the zipped clover folder, and go to inside of "CloverV2" folder, and copy the content to your USB drive now inside your USB Drive root folder, copy "NvmExpressDxe.efi" file, located in "/EFI/Clover/drivers/off" folder, to "/EFI/CLOVER/BIOS", "/EFI/CLOVER/UEFI", "/EFI/CLOVER/drivers32uefi", and /EFI/CLOVER/drivers32uefi" folder respectively. Now, back to your USB Drive root folder, go to "/EFI/CLOVER" folder and rename "config-sample.plist" to "config.plist". Edit the "config.plist" file with notepad or other plain text editor (Notepad++ is recommended) Find "<Key>Boot</Key>" line and scroll down a bit and you will find "<Key>Timeout</Key>" line, below that, default value is "<interger>5</interger>", this value represented how many second clover will automatically boot when user input is not detected, you can change it to your desired value, in my case, I put "10" for 10 seconds. Save and close the text editor. Now reboot your PC, and select boot drive to the USB/SD drive (either using boot menu shortcut or set it up manually via BIOS boot order). If you see the clover boot menu, congrats! Now shutdown your PC, plug your NVMe drive (if not already), and try to boot from it. If your NVMe drive doesn't have any OS installed, please install it like usual. Now, after installing either your NVMe drive or installing the OS inside it (or both), you can directly boot to the NVMe drive via the clover boot menu selector! Photos for the guide: Diskpart: Windows Disk Management (in this case clover drive already prepared beforehand): Clover root folder inside the USB/SD drive: Editing the "config.plist" file: System info for the test system (Dell Inspiron 3647/Vostro 3900) using HWInfo: If you have any question regarding this thread, don't afraid to ask down below, Cheers!

So! First post on LTT. Yay! I have an old HP Envy 23-d044 I'm fixing up for funsies (Core i7-3770S, 16GB DDR3 1600), and after watching Linus's $169 Gaming PC Video plus figuring that my HP's MXM slot is basically a PCIe (gen 2) slot, I went to AliExpress for this MXM-to-NVMe adapter plus this NVMe SSD. The gameplan? Make this old computer boot from NVMe via the adapted MXM card slot. I downloaded Clover and anxiously anticipated the moment of truth. But, that's where I started tripping up. For the love of God, I can't get Clover to boot my Windows 11 (or 10) installer disk! The BIOS is set to SecureBoot on with Legacy/CSM disabled; I've tried using both official Windows Media Creation Tool and Rufus to make the installer; I've tried a couple older versions of Clover; I've tried using both Rufus and cvad's BDU to create the Clover disk; I've even tried it on my main PC (MSI B550 Tomahawk, Ryzen 5 5600X, 16GB DDR4 3600) and it exhibits the same problem! Clover boots fine, and when I select my Windows installer USB, I get hung on a black screen. I've also noted that (on both machines) for my main Windows SATA SSD there appear to be two options in Clover: Microsoft EFI Boot from EFI and Windows from EFI, but only choosing the former actually boots the SSD successfully, whereas selecting the latter gets me the same hanging black screen. Again, this behavior exhibits on both my fixer-upper HP and my main PC. So, the only EFI Clover can successfully boot on either machine is the Windows Boot Manager, I guess? So I figure I've gotta be missing something super basic with Clover or my computers' boot settings, but I'm left scouring four-year-old forum threads and scratching my head.

Hello, I have a PC with an ASUS P7P55D-E board and want to install windows on an NVMe drive using that PC and boot from it, on that PC. I installed the latest version of the clover bootloader on 2 USB drives, because with NVMe drivers, it can use NVMe drives normally, but every time I try to boot from one of those USB drives, I only get a black screen with a blinking cursor. I also tried booting my Windows 10 installation media, which gave me the same blinking cursor for a few minutes and then it eventually booted. I have been trying to boot clover for 20 minutes straight but still nothing happened. I made 2 drives to see if the drive was the problem, but that doesn't seem to make a diffrence. I read online this could be because of conflicting boot drives, but when I remove it, I get an error message saying it can't find any boot devices, so there shouldn't be any conflicts. I also tried booting clover with an other boot drive installed, to see if clover needs one to actually boot, since it's a bootloader, but that didn't change anything, same result. Can you help me? I don't know what the problem could be. Btw this is an ASUS P7P55D-E board and I'm trying to use Windows on an NVMe drive, that's why need clover for the NVMe drivers. Later : I tried making a GPT instead of MBR partition with rufus and this time it actually gave me an error screen. I then tried finding anything like "BIOS Legacy mode" in the Firmware settings, but without success. I then checked rufus but it only lets me select UEFI, not BIOS. I don't know what to do now, can you help me?

I have a LG Gram 14Z960-LR 10k should I use Opencore or Clover ?

Hey guys. So I decided to install Mac OS X catalina on my PC but after installing I learnt that the RTX 2060 is not supported so I deleted the partition in which Mac os x was installed (my entire hard drive). Then in order to remove the EFI partition, I booted up linux and deleted it using GParted. After doing so, I can by default boot into Windows 10, but can't boot into bios. It always shows a black screen everytime I try to do so. I tried resetting CMOS twice, with no luck. Please help me, I need to change a few settings in my BIOS asap. Thanks in advance. My RIG: Mobo: Asus TUF-B450 Gaming Plus Graphics: Zotac RTX 2060 Pro: Ryzen 5 3600 PSU: 550W 120GB SSD (windows) 1TB HDD (used for Hackintosh and deleted it later)

Hello Friends , I am trying to create a hackintosh for first time . I figured it out somehow how to install Clover bootloader in the USB . Clover is booting properly . Now I can't find a single topic on web which can tell about the basics . Every post give instructions . No one is telling how to use clover . Now I don't know how to tell clover where are the things it has to boot . Where to put the MAC DMG extracted files . Help please .

Hello guys , I am trying to create a hackintosh for first time . I figured it out somehow how to install Clover bootloader in the USB . Clover is booting properly . Now I can't find a single topic on web which can tell about the basics . Every post give instructions . No one is telling how to use clover . Now I don't know how to tell clover where are the things it has to boot . Where to put the MAC DMG extracted files . Help please .

Hi Im making a hackintosh the old fashioned way. No VM or linux UniBeast Multibeast (so clover) on fresh hardware, most importantly an Aorus wifi MOBO and a WD black M.2 SSD. I have heard that for some reason macOS doesn't work over m.2 and i do not understand why nor do i understand the premise of the workaround. Will i be able to stick my boot usb into a computer with only an M.2 drive for storage and make a bootable disk?

This has been the most painfully irritating build i have ever attempted, but i finally have a desktop machine that can boot Linux Mint 18, OSX Sierra and Windows 10, but it has many quirks. I noticed that triple/quad booting has been asked about on the web for years but nobody has ever really done a good case study of how on earth you do it, least of all with pictures and guides. Ill just give a quick run down of what we have here. The machine is a lenovo thinkcenter E73 tower, OEM machine with only upgrade being the 9800GT, it has a 128GB sata SSD and a 1TB HDD. First step was to install the hackintosh on the entire SSD using clover and the fantastic instructions on TonyMacx86. Spend weeks trying to figure out how kexts work and getting the nvidia web driver to run persistently, a basic tutorial on clover configurator comes in handy here. So once OSX was installed, i then introduced the 1TB HDD to the system and installed windows 10 on it in the usual manner, just boot off the USB stick and give windows the entire 1TB. From here on i believe you are at the mercy of your UEFI whether the windows bootloader makes it onto the SSD where it should go, or whether windows craps out and put it on the HDD. In my case windows put it's bootloader into the EFI partition of the SSD, therefore clover was able to see it and i was instantly given a windows option in clover. 2 down one to go. Finally in order to cram linux mint onto the machine, i refrained from shrinking the NTFS partition from within windows as this screwed everything the first time i did it, partition table went completely out of whack. instead, at this point simply boot off the live Mint setup USB, and proceed to install, Mint will detect the windows bootloader (but not the OSX one) and prompt you to install alongside windows. At this point i used the linux setup to cut the 1TB in half and installed mint into the second half. When mint has finished installing, reboot into clover and you should now have a linux boot option. In my case, the installation of linux destroyed my ability to boot windows from clover, but i was still able to boot windows from grub, which appears after you select linux from clover, ugly i know. The fix i found for this was to boot back into Mint and run sudo update-grub, which then rejiggers all the bootloaders around into their right places, after this, i was able to boot all 3 OS's from clover, as well as the OSX recovery partition (doesn't quite count as a quad-boot right ?) The main issue i found with this project was the trial and error nature of screwing up bootloaders and having to start again, clover is a bit fragile when it comes to making it boot more than just OSX. Essentially this machine went through about 5 iterations before it was finally stable. In summary, windows 10 and Mint run perfectly on the hardware as you would expect, but that's the easy bit, the challenge lies with making OSX happy with "peasant grade" non proprietary hardware, and this almost entirely revolves around onboard realtek audio. From what i can tell, clover has kexts for basically any realtek 3.5mm jack bay that has 5 ports, but seeing as i have this weird OEM machine, i only have a bay of 3 x 3.5mm jacks, and this is tragically not supported AFAIK. i solved this by cannibalising a USB DAC, velcro-ing it to the floor of the case, and running XLR's out of the rear I/O, looks janky as hell but works a charm, and the sound quality is far superior to the onboard anyway. One final thing i was unable to get working within OSX was hardware reporting like CPU temps and stuff, from what i can tell this is all low-level apple kernel stuff that goes over my head, but hopefully someone can make or port a kext for this functionality. Thanks for reading anyway guys i just wanted to share what i learnt building this frankenstein PC, as i know many of you are interested in the concept of multiple OS's on a PC, but are maybe confused as to where you even start. DnFx

Parts list I am seeking a solution to my missing drives in disk utility during install. I am following the vanilla guide here. Platform is Z290 Kaby Lake. I have tried both HboxHfs-64 and HFSPlus in clover setup. I have tried the SSDT key fix here. I do own an NVMe drive but it is not the target and none of my other 4 normal drives show up. AHCI on everything. Here is my config.plist https://pastebin.com/Z89rhtuH

Hi, i can someone help me with installing mac OS Mojave on my HP ENVY - 15-as102na? I have an imac to use for setting up my usb & installing MacOS Mojave.There are various kext files etc that i'm not sure about and need some help as some are hardware specific. I tried previously but got stuck on an apple logo and couldn't get past that, and tried today and had problems with Clover. Specs: Cpu: i5 7200u GPU: HD 620 8GB ram Wifi card- Intel Wireless 7265 ( Intel® 802.11ac (2x2) ) Motherboard - HP 81D2 & BIOS version is f.56

So a while back I installed Mac OS X on a laptop (Which at the time was my main driver). I then transferred it to a desktop, and it had no issues booting. I recently had to wipe my drive because I had nothing important on there, and the system was getting kinda full as well. I remade a clover USB and attempted to reinstall Mac OS X Mojave on to it. The system found nothing. None of my SATA disks were even acknowledged by the OS as existing. I don't know if this will help any but here are my current specs: My system is an H61 based chipset running on a 3rd gen i7, has 16 GB ram, runs off of a 1 tb SATA (since I'm broke af) and has a GeForce GTX 750 Ti (again, I'm broke af). The motherboard has the latest bios and I have set it back to optimal settings yet nothing has worked. Sorry if I sound stupid by writing this I just need someway to fix this problem if at all possible.

I am trying clover for a vanilla Mojave install on: aorus ultra z390 9600hk 32gb gskill ram amd Vega frontier air wd black m.d nvme ssd 500gb i have tried every USB port and I am pretty sure my bios settings are correct.

Please help. I'm new at building hackintoshes. I finished installation of El Capitan in unibeast and installed the drivers in multibeast, but I believe I installed the wrong drivers, because when I restart, after installing drivers, it won't boot. I see the apple logo and the loading bar, but it never makes it past that point. I don't know what to do.

Hey guys. I'm so into the Team Hackintosh and I'm having this issue. Nothing to do with OS X btw. One of the most recommended installation methods for OS X in a PC is clover, as you may or may not know. I did the whole process exactly two times in my system because of reasons, but then I notices when I enter in the UEFI i have two new options to boot from: Mac OS X and Mac OS X I thought it was normal, but I removed all my drivers and then realized these two options were still there. Even when there weren't any single HDD or SSD or USB memory or Disc connected. The Mac OS Xs boot options are carved into the UEFI and not even by cleaning the CMOS can't get rid of it. I asked for help in the Hackingtosh community but they haven't been able to help me. And also this wouldn't be a serious issue if my computer performed well, but the motherboard also seems not to save the changes I make on the UEFI. Primely in the boot options. Here's a screenshot Motherboard Gigabyte Z77X UD5H

Is the evga z97 stinger wifi clover compatible? Everything, including audio, wifi, Bluetooth, and Ethernet.

Hi, I recently installed Yosemite successfully on my custom built rig. I used the Unibeast+Multibeast method. I couldn't boot with Chimera so I decided to go for Clover. I followed Bob Roche's (cpukid's) tutorial on how to install clover as a boot loader. It worked fine but at the end I get a kernel panic and I think that this is odd buy under Mac OS version it says: Not yet set (in the kernel panic). Here's a picture of it. Rig: Intel core i7 4790(NON-K) @ 3.6GHz Gigabyte Z97 HD3 (rev 2.0) Sapphire Toxic R9 280X HyperX Fury 120GB SSD Seagate Barracuda 1TB HDD Corsair CX750W PSU Thanks in advance! <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"><plist version="1.0"><dict> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Debug</key> <false/> <key>DropOEM_DSM</key> <false/> <key>Fixes</key> <dict> <key>AddDTGP_0001</key> <true/> <key>AddHDMI_8000000</key> <true/> <key>AddIMEI_80000</key> <true/> <key>AddPNLF_1000000</key> <true/> <key>DeleteUnused_400000</key> <true/> <key>FIX_ACST_4000000</key> <true/> <key>FIX_ADP1_800000</key> <true/> <key>FIX_RTC_20000</key> <true/> <key>FIX_S3D_2000000</key> <true/> <key>FixAirport_4000</key> <true/> <key>FixDisplay_0100</key> <true/> <key>FixFirewire_0800</key> <true/> <key>FixHDA_8000</key> <true/> <key>FixHPET_0010</key> <true/> <key>FixIPIC_0040</key> <true/> <key>FixLAN_2000</key> <true/> <key>FixRegions_10000000</key> <true/> <key>FixShutdown_0004</key> <true/> <key>NewWay_80000000</key> <true/> </dict> <key>Name</key> <string>DSDT.aml</string> <key>ReuseFFFF</key> <false/> </dict> <key>DropTables</key> <array> <dict> <key>Signature</key> <string>DMAR</string> </dict> <dict> <key>Signature</key> <string>SSDT</string> <key>TableId</key> <string>Cpu0Ist</string> </dict> <dict> <key>Signature</key> <string>SSDT</string> <key>TableId</key> <string>CpuPm</string> </dict> </array> <key>HaltEnabler</key> <true/> <key>SSDT</key> <dict> <key>DropOem</key> <false/> <key>EnableC6</key> <true/> <key>Generate</key> <dict> <key>CStates</key> <true/> <key>PStates</key> <true/> </dict> </dict> </dict> <key>Boot</key> <dict> <key>Arguments</key> <string>npci=0x2000 kext-dev-mode=1 PCIRootUID=0</string> <key>Debug</key> <false/> <key>DefaultVolume</key> <string>Cheeseburger</string> <key>Legacy</key> <string>PBR</string> <key>Secure</key> <false/> <key>Timeout</key> <integer>5</integer> <key>XMPDetection</key> <false/> </dict> <key>Devices</key> <dict> <key>Audio</key> <dict> <key>Inject</key> <string>No</string> </dict> <key>FakeID</key> <dict> <key>ATI</key> <string>0x0</string> <key>IMEI</key> <string>0x0</string> <key>IntelGFX</key> <string>0x0</string> <key>LAN</key> <string>0x0</string> <key>NVidia</key> <string>0x0</string> <key>SATA</key> <string>0x0</string> <key>WIFI</key> <string>0x0</string> <key>XHCI</key> <string>0x0</string> </dict> <key>USB</key> <dict> <key>AddClockID</key> <true/> <key>FixOwnership</key> <true/> <key>Inject</key> <true/> </dict> </dict> <key>DisableDrivers</key> <array> <string>Nothing</string> </array> <key>GUI</key> <dict> <key>Hide</key> <array> <string>BOOTX64.EFI</string> <string>Windows</string> </array> <key>Language</key> <string>en:0</string> <key>Mouse</key> <dict> <key>Enabled</key> <true/> <key>Mirror</key> <false/> <key>Speed</key> <integer>8</integer> </dict> <key>Scan</key> <dict> <key>Entries</key> <true/> <key>Legacy</key> <true/> <key>Tool</key> <true/> </dict> <key>Theme</key> <string>YosemiteLogin</string> </dict> <key>Graphics</key> <dict> <key>Inject</key> <dict> <key>ATI</key> <false/> <key>Intel</key> <false/> <key>NVidia</key> <false/> </dict> </dict> <key>KernelAndKextPatches</key> <dict> <key>AppleRTC</key> <true/> <key>AsusAICPUPM</key> <true/> <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>External icons patch</string> <key>Find</key> <data> RXh0ZXJuYWw= </data> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data> SW50ZXJuYWw= </data> </dict> </array> </dict> <key>SMBIOS</key> <dict> <key>BiosReleaseDate</key> <string>06/12/13</string> <key>BiosVendor</key> <string>Apple Inc.</string> <key>BiosVersion</key> <string>MP61.88Z.0116.B04.1312061508</string> <key>Board-ID</key> <string>Mac-F60DEB81FF30ACF6</string> <key>BoardManufacturer</key> <string>Apple Inc.</string> <key>BoardType</key> <integer>11</integer> <key>ChassisAssetTag</key> <string>Pro-Enclosure</string> <key>ChassisManufacturer</key> <string>Apple Inc.</string> <key>ChassisType</key> <string>06</string> <key>Family</key> <string>Mac Pro</string> <key>Manufacturer</key> <string>Apple Inc.</string> <key>Mobile</key> <false/> <key>ProductName</key> <string>MacPro6,1</string> <key>SerialNumber</key> <string>C02KVUZIF693</string> <key>Trust</key> <false/> <key>Version</key> <string>1.0</string> </dict> <key>SystemParameters</key> <dict> <key>InjectKexts</key> <string>Detect</string> <key>InjectSystemID</key> <true/> </dict></dict></plist>