Jump to content
About Just Joined group Read more... ×
avin7000

[Guide] Install Windows 8 UEFI on Legacy BIOS with Clover (and Dual boot with Yosemite)

99 posts in this topic

Recommended Posts

Install Windows 8 UEFI on Legacy BIOS with Clover (and Dual boot with Yosemite)


In this tutorial I am going to explain how to install Windows 8 on a Legacy BIOS in UEFI mode (Yes! It's possible!!) using Clover and dual boot with Yosemite. Technically this tutorial should work for Windows 7 and Mavericks also, but I haven't tried.

What you get?
You have a machine with Legacy BIOS and at the end of tutorial, you would have Yosemite OS X and Windows 8.1, in UEFI mode, on a GPT partition with Clover as Bootloader. Isn't that amazing? This tutorial covers installation of both Yosemite and Windows 8.

Why GPT/UEFI?
  • You can have multiple Recovery Partitions in GPT
  • Depending on BIOS, sometimes Clover doesn't play well in Non-UEFI. You may face all sorts of weird boot/BCD errors
  • GPT can support more than 2TB space (MBR cannot)
  • You can have upto 128 partitions (woot!) in GPT (as opposed ONLY 4 primary partitions in MBR/Hybrid MBR partition scheme)
  • GPT disk provides greater reliability due to replication and cyclical redundancy check (CRC) protection of the partition table.
  • UEFI enables better use of bigger hard drives.
  • Technical changes abound in UEFI. UEFI has room for more useful and usable features than could ever be crammed into the BIOS. Among these are cryptography, network authentication, support for extensions stored on non-volatile media, an integrated boot manager, and even a shell environment for running other EFI applications such as diagnostic utilities or flash updates. In addition, both the architecture and the drivers are CPU-independent, which opens the door to a wider variety of processors (including those using the ARM architecture, for example).
  • GPT/UEFI is the future ;-)
Credits:
A big thanks to fusion71au, he guided me and helped me to install UEFI Windows on my laptop and made it possible. In fact, this tutorial is actually combination of several of his posts (check Sources section).

Prerequisites:
- A pendrive of 200MB (or more) for test Clover config (optional)
- Two pendrives of 8GB (or more), one for OS X and another for Windows installation media. OR a single pen drive of 16GB (or more).
- A running OS X machine in real Mac or Hackintosh or as virtual OS.
- Install OS X Yosemite.app downloaded and present in Applications
- Windows 8 ISO
- Latest Clover, Clover Configurator, Kext Wizard, Rufus, HFSPlus.efi and FakeSMC.kext (and other kexts based on your machine)

Downloads:
- Clover
- Clover Configurator
- Kext Wizard
- Rufus
- HFSPlus.efi

Test Clover Config (Optional):
This is an optional part and only applies to people who already have a hackintosh running. And also for first time users of Clover. Feel free to skip it if it doesn't apply to you.

Before installing Yosmite/Clover, it's better to test Clover on currently installed Hackintosh. First, it saves all the trouble of post-installation and second, you will be proceeding to install Yosemite once you have confirmed everything is working properly (and no dirty surprises). For this, you do NOT need to install Clover on your current HDD, it may mess up your current installation. Idea is to install Clover on a different HDD(or a test HDD) and without harming current installation.
  • Plug in the 200MB (or more) pen drive. Open disk utility, select this drive, under Erase tab choose Format as MS-DOS(FAT) and give name CLOVER(or whatever you want) and hit Erase:

    Bc2948b.png
  • Go to Partition tab, select 1 Partition in Partition Layout, Give name as CLOVER, format as MS-DOS(FAT). Click Options at the bottom and select Master Boot Record. Hit Apply.

    sDcdcik.png
    9UoOKPK.png

    Your drive is formatted properly now. It can have Clover installed for test USB drive.
  • Run Clover and change install location to this drive, CLOVER and customize by selecting Bootloader > Install boot0ss in MBR, CloverEFI > CloverEFI 64-bits SATA and Drivers64UEFI > EmuVariableUefi-64. Perform installation:

    cOtGzUY.png
    ZPpE5h5.png
    Otd8odM.png
  • Clover is installed to the drive. However you need to copy few more files. You will need config.plist, DSDT.aml which are specific to your system.

    - Put config.plist in EFI/CLOVER directory
    - Put DSDT.aml in EFI/CLOVER/ACPI/patched
    - Put HFSPlus.efi in EFI/CLOVER/drivers64 & EFI/CLOVER/drivers64UEFI
    - Delete VBoxHfs-64.efi in EFI/CLOVER/drivers64 & EFI/CLOVER/drivers64UEFI
    - Put FakeSMC.kext and other kexts required in EFI/CLOVER/kexts/10.10

    That's all and your Clover test drive is ready! Now boot using this USB and boot into your Hackintosh. Make sure everything working and once confirmed, proceed next to installation of Yosemite.
Creating Installation Media:
We will prepare a single USB drive which can be used to install Yosemite, Windows (and even Ubuntu if you fancy!). We have will format this to GPT, create 2 partitions, one for OS X and another for Windows installation files. This drive needs to be more than 16GB so that it can have all three installation files.
  • Erase the USB drive, using Disk Utility. Make 3 partitions for OS X (call it Yosemite), Windows (call it WIN81) and Ubuntu. Select OS X Partition as Mac OS Extended Journaled, Windows partition as MS-DOS(FAT) and Ubuntu partition as ext4. (If you don't want Ubuntu, make only two partitions). Make sure you are giving 7GB (or more) for each OS X and Windows installation partitions. Select ‘GPT (GUID Partition Table)’ under Options.

    BcE2FG5.png
    lH2FkxY.png
  • Mount Windows 8 installation ISO and copy Windows 8 installation files to this FAT32 Windows Partition, WIN81.
  • Install Clover into the EFI partition of this USB by targeting the OSX partition and customize by selecting Install Clover in the ESP, Bootloader > Install boot0ss in MBR, CloverEFI > CloverEFI 64-bits SATA and Drivers64UEFI > EmuVariableUefi-64. Perform installation:

    7p2hE0w.png
    7aLwnHZ.png
    Kk0xNm6.png

    Once clover is installed EFI partition will be mounted automatically. Open it and now you need put few more files. You will need config.plist, DSDT.aml which are specific to your system.

    - Put config.plist in EFI/CLOVER directory
    - Put DSDT.aml in EFI/CLOVER/ACPI/patched
    - Put HFSPlus.efi in EFI/CLOVER/drivers64 & EFI/CLOVER/drivers64UEFI
    - Delete VBoxHfs-64.efi in EFI/CLOVER/drivers64 & EFI/CLOVER/drivers64UEFI
    - Put FakeSMC.kext and other kexts required in EFI/CLOVER/kexts/10.10
  • Now we need to copy Yosemite installation file to USB drive. Make sure /Applications/Install OS X Yosemite.app exists and run following in terminal:

    sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/Yosemite --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --no interaction
    Above command assumes your partition for OS X installation files is named as Yosemite.
Your USB installation drive is ready. This can be used to install both Yosemite and Windows 8.

Installation of Yosemite:
We will create appropriate partitions and install Yosemite.

NOTE: The Yosemite Installation section here is very concise and brief. You should actually refer to the thread relevant your machine/laptop. For starters, check this All In One Guides of Hackintosh. Next, try either here or here. It'd be better if you post all your Yosemite installation doubts in those threads/forums.
  • Boot with USB drive, Clover should be loaded. Click on ‘Install Yosemite from Install Yosemite’.
  • Installation setup should appear. Use Disk Utility from Utilities and format the target drive. Create 2 partitions, for first partition where OS X will be installed, select Mac OS Extended (Journaled). Leave second partition as Free Space (and Windows installation will format it properly)
  • Proceed to Yosemite installation. Once done, it will reboot.
  • Boot again using the USB and boot into Clover. Click on ‘Install Yosemite from Install Yosemite’ to complete the installation.
Post installation and setup of Clover:
So far I have covered installation of Yosemite. Now post installation, we will install Clover and all required kexts. At the end of this section Yosemite will be ready to use and kicking.
  • Boot with USB drive, into Clover Menu. Select Yosemite(or whatever name you gave), to boot into freshly installed Yosemite
  • Install Clover into the EFI partition of the HDD by targeting the Yosemite partition (or whatever you called it) and customize by selecting Install Clover in the ESP, Bootloader > Install boot0ss in MBR, CloverEFI > CloverEFI 64-bits SATA, Drivers64UEFI > EmuVariableUefi-64, Install RC Scripts on target volume and Install Clover Preference Pane. Perform installation:

    3nLmQKE.png
    9g6ZuVM.png
    KKUFAqa.png
  • Once clover is installed, EFI partition will be mounted automatically. Open it and now you need put few more files. You will need config.plist, DSDT.aml which are specific to your system.

    - Put config.plist in EFI/CLOVER directory
    - Put DSDT.aml in EFI/CLOVER/ACPI/patched
    - Put HFSPlus.efi in EFI/CLOVER/drivers64 & EFI/CLOVER/drivers64UEFI
    - Delete VBoxHfs-64.efi in EFI/CLOVER/drivers64 & EFI/CLOVER/drivers64UEFI
    - Put FakeSMC.kext and other kexts required in EFI/CLOVER/kexts/10.10
Installation of Windows 8:
Boot into your machine with HDD's Clover and select Boot UEFI external from WIN81, hit spacebar, select and enter Run bootx64.efi. It should load into Windows installation. (image credits: fusion71au)

essjmDT.png
Ja4W7c1.png


Proceed Windows installation and complete it. Now you have Windows 8 UEFI on a Legacy BIOS!

Extras/Troubleshooting (Optional):
  • Sometimes you want to mount EFI partition manually. There are two ways:

    - If you are paranoid using Terminal, download Clover Configurator. It will ask to mount EFI partition when you open it. And you can also mount manually, see the sidebar at left side, under Tools, Mount EFI.
    - By default, all partitions are not visible in Disk Utility. If you enable Debug Menu, you get an option to show all partitions. To enable, run the following in Terminal:

    defaults write com.apple.DiskUtility DUDebugMenuEnabled 1
    Then you should see an extra Debug Menu in the Disk Utility:

    emmNXYn.png
  • If the Windows ISO size is more than 4GB, then most probably /source/install.wim size will be more than 4GB and copying it to FAT partition will fail. For this we have to split this file.

    - Boot into Windows 8, create a new directory called wim in C:\ drive. Copy install.wim to C:\wim directory.
    - Open command prompt in admin mode and run following:

    Dism /Split-Image /ImageFile:c:\wim\install.wim /SWMFile:c:\wim\install.swm /FileSize:3500
    - You should now see two files in C:\wim directory.
    - Replace install.wim by these two files.

    Now you can copy Windows installation ISO files to FAT partition of the USB.
  • When you want to install Windows, in Clover menu, if nothing happens when you click on Windows Installation in clover, then you have to copy bootmgfw.efi into WIN81/efi/microsoft/boot

    - Use 7-zip in Windows, open install.wim navigate to sources/install.wim/1/Windows/Boot/EFI/bootmgfw.efi and extract bootmgfw.efi (you don't need to extract this big ass file)
    - Rename cdboot.efi in WIN81/efi/microsoft/boot directory to cdboot.BAK
    - Copy bootmgfw.efi into WIN81/efi/microsoft/boot

    Now boot again with this drive. This time select Run bootmgfw.efi in options (as opposed to Run bootx64.efi), now it should boot fine into Windows 8 installation.
  • Even after following above advice, still Windows installation gives some error, then prepare Windows 8 installation media on a separate USB drive using Rufus. You can find instructions here. Use this USB drive instead and perform installation.
  • In Clover installations, you do NOT need to install Drivers64UEFI > EmuVariableUefi-64, it's not necessary for legacy BIOS. However my setup wouldn't work without it and I have no idea why. Since it does not affect the installation, I have included it anyway.
  • Instead of CloverEFI 64-bits SATA, you could try installing CloverEFI 64-bits BiosBlockIO to speed up boot. However it may not work on few machines. So make sure you have test USB drive handy (first section of this tutorial).
  • Disk partitioning guides: How to convert a Hybrid MBR drive to GPT and How to Convert MBR Windows to UEFI Windows Without Reinstalling - link.
Sources:PS: I have also attached PDF and HTML formats of this same tutorial.

Guide.html

Guide.pdf

Share this post


Link to post
Share on other sites
Advertisement

Amazing guide :D Complete!

But:

 

Run Clover and change install location to this drive, CLOVER and customize by selecting Bootloader > Install boot0ss in MBR, CloverEFI > CloverEFI 64-bits SATA and Drivers64UEFI > EmuVariableUefi-64. Perform installation:

Why? I asked Clover Developers, and they told me that in CloverEFI booting (aka Clover Legacy) DOES NOT load the UEFI drivers folder, instead you can copy those driver into the Driver64 folder, however, some drivers may not work since they are made for UEFI firmwares, so for NVRAM saving, you may put that driver in the Driver64 and try to save the nvram into disk by stting it in the Clover.prefpan :)

Thanks for this breif guide :D

Share this post


Link to post
Share on other sites

Don't know why at the part of windows and yosemite installer, you format the USB as GPT ? MBR format on the USB can boot Windows UEFI installer just fine ( of course FAT32 partition ). If so then you must create another FAT32 partition for Clover ( the Test Clover Config section at the beginning ). Different method, same result

Share this post


Link to post
Share on other sites

You are my hero! :D

 

Been trying to get this working for days. When i finally gave up hope, in comes this guide, and now it works flawlessly!

 

Thanks a lot!

Share this post


Link to post
Share on other sites

Hi,

 

thanks for the guide...

 

Am able to get install Yosemite, and then installed Clover to HD.

 

However, when I boot from there, I don't see any option to "Boot UEFI external from WIN81".  Instead I see "Boot Windows from ..." (the stick I have the windows installer on)

 

Any ideas?

 

cheers,

 

David

Share this post


Link to post
Share on other sites

@redcoatd,

 

If you don't see "Boot UEFI external"/bootx64.efi, most likely it is hidden (the latest Clover revisions >r2999 automatically hide bootx64.efi from the GUI, unless you press <F3> at the Main Menu to unhide).  Did you read point no3 in the troubleshooting section?

 

Try this workaround

 

1.  Rename cdboot.efi in WIN81/efi/microsoft/boot folder to cdboot.BAK

2.  Copy bootmgfw.efi into WIN81/efi/microsoft/boot

 

post-846696-0-42354800-1418288879_thumb.

 

3. Reboot the computer with the Installer USB and select "Boot Microsoft EFI boot menu from WIN81", then press <spacebar>

 

post-846696-0-52813400-1418288999_thumb.

 

4.  Select "Run bootmgfw.efi" and then press <spacebar> ---> should now boot into the UEFI Windows Installer!

 

post-846696-0-34464000-1418289116_thumb.

Share this post


Link to post
Share on other sites

@carlocav,

 

Have a look at the Clover wiki for a description of what each of the installation options means. I recommend installing Clover into the ESP and keeping the install options the same as for the USB (providing boot works).

 

"Install Clover in the ESP: Best option when such an EFI partition is available (GPT partitioned drive)"

 

For the hard drive install, I also recommend selecting RC Scripts for proper functioning for NVRAM/iMessage/FT in non UEFI machines.

PS: We are probably spamming this thread too much :P . Maybe ask further questions in @avin7000's thread or the Clover General discussion.

Thank you fusion71au, so finally as I have a non UEFI machine do you recommend me to enable in the Yosemite hard drive clover "Instal Clover in the ESP", enable boot0ss instead of boot0af, remove OSXAptioFixdrv-64 and partition dxe-64 drivers and add install RC Scripts on target volume?

If yes, I just modify config.plist?

Share this post


Link to post
Share on other sites

^^ Yes but you don't need to modify your config.plist.

 

Just run the Clover installer targetting the Yosemite partition and with the new custom options ---> will automatically make the changes and backup your previous EFI folder in /EFI Backups.

Share this post


Link to post
Share on other sites

Thank you just a last question as you are very kind.

I have not dsdt.aml and ssdt.aml

Do you reccomend me to generate them or are they useless?

Share this post


Link to post
Share on other sites

@carlocav,

 

It depends on whether you are happy with how your hack is functioning at the moment :).  Have you installed the latest HWSensors and FakeSMC.kext to monitor temps & CPU/GPU frequencies --> check speed step is working?

 

Depending on your hardware, you may need a patched DSDT/SSDT for optimal functioning of sleep/power management/usb etc.

 

Clover is also able to patch your machine's native DSDT on the fly and generate P & C states for speedstepping so you can try them out first.

 

Have a read of the following guides ....

Share this post


Link to post
Share on other sites

Folloowed the procedure to install Windows UEFI but Windows installation doesn't detect internal hard drive.

I had the same problem with Yosemite, I solved it by removing the hard drive, connect it to the computer via USB with a SATA/USB-ESATA dock and then I put it back inside, And to solve the still waiting for root device error I had to put in /EFI/Clover/Kexts/10.10 legacyappleahciport.kext.

How can I do for Windows? If I remove the drive as I done for Yosemite probably I can manage to install it but when I put inside the drive probably Windows won't load.

Share this post


Link to post
Share on other sites

Folloowed the procedure to install Windows UEFI but Windows installation doesn't detect internal hard drive.

I had the same problem with Yosemite, I solved it by removing the hard drive, connect it to the computer via USB with a SATA/USB-ESATA dock and then I put it back inside, And to solve the still waiting for root device error I had to put in /EFI/Clover/Kexts/10.10 legacyappleahciport.kext.

How can I do for Windows? If I remove the drive as I done for Yosemite probably I can manage to install it but when I put inside the drive probably Windows won't load.

Did you have the same issue when you previously installed legacy Windows?  Does your system come with extra OEM drivers?

 

Maybe try loading extra drivers (Dell's OEM SATA drivers for your machine) during the UEFI Windows install - see  SevenForums post here.

 

Also have a look at WinToUSB program to install Windows in "to go" mode on a USB hard drive.

Share this post


Link to post
Share on other sites

I tried loading the SATA and chipset drivers available in Dell website but still no sata hard drives found.

If I boot with Windows CD the installation detect the drives, the problem is the installation in UEFI mode.

In your opinion if I install Windows connecting the drive via USB, when I will put back the drive inside the computer (SATA), will I have an error similar to still waiting for root device?

Share this post


Link to post
Share on other sites

@carlocav,

 

It may work, I'm not sure since I haven't encountered your problem on my system....

 

Other Suggestions

1.  Install Clover using the BiosBlockIO option instead of the standard 64-bits SATA

2.  Install an older version of Clover eg r2957 from this post.

3.  Maybe try starting the UEFI Windows installation directly from the Windows DVD by booting the system with a FAT32 Clover boot USB. 

 

You can also ask the Clover developers in the Clover General Discussion thread if they have any ideas why your disk is not being detected by the Windows installer in UEFI mode....

Share this post


Link to post
Share on other sites

Thank you Very much I'll try! In your opinion is this related to the fact that even the OS X installer couldn't find the hard drives as my bios has not AHCI mode?

Share this post


Link to post
Share on other sites

^^

That could very well be the problem.  Your BIOS probably has IDE mode as default for your SATA hard drives.  If there is no AHCI option, then try setting it to RAID mode in the BIOS (roughly equivalent to AHCI), then reboot your system with the Clover UEFI Windows USB ---> see if the hard disk is now recognized.

 

Failing that, try installing Clover with the BiosBlockIO option instead of the standard 64-bits SATA.

 

Good Luck!

Share this post


Link to post
Share on other sites

Not work even with Raid

Failing that, try installing Clover with the BiosBlockIO option instead of the standard 64-bits SATA.

In the USB or even in the Yosemite hard drive?

Share this post


Link to post
Share on other sites

@Dr Hurt,

 

According to @Slice post#46, it is possible as long as the DVD is ISO9660+Joilet format, not UDF.  Also make sure the target hard drive is formatted pure GPT with protective MBR instead of hybrid MBR (can convert hybrid MBR back to GPT using gdisk).

 

So I converted my ISO to joliet and burned it to a new DVD but Clover still doesn't see the disk.

Share this post


Link to post
Share on other sites

@fusion so we convert the normal iso in terminal to Joliet, then burn it directly with Disk Utility ?

Yes, that's correct eg

hdiutil makehybrid -iso -joliet -o image.iso /path/to/source

 

So I converted my ISO to joliet and burned it to a new DVD but Clover still doesn't see the disk.

  • Did you install Clover with VBoxIso9600-64.efi in /Drivers64? ---> needed if using Clover version later than r2986 (since no longer included in the "boot" file)
  • Is bootx64.efi/"UEFI External" hidden by your config.plist?

 

I've just tested a converted Windows8 iso burned to joliet DVD and the UEFI Windows Installer works after booting it with Clover r2953.  Here's what you should see at the Clover Main Menu ....

 

1.  Choose "Boot UEFI optical from XXXX"

post-846696-0-17234000-1421656665_thumb.png

2.  Select "Run BOOTX64.efi", then <Spacebar>....for some reason, it was initially unresponsive & I had to do this twice.

post-846696-0-00276600-1421656765_thumb.png

 

TBH, I don't usually burn the iso to DVD because I've always transferred the Windows install files to a FAT32 USB partition instead (booted by Clover to install UEFI Windows as detailed in @avin7000's guide) ---> much faster installation than with optical drives :).

 

Edit

Conversion to Joliet is no longer necessary if GrubUDF-64.efi is installed in EFI/CLOVER/drivers64.  Below are screenshots of Clover r3150 booting to UDF formatted Windows 7 X64 DVD....

post-846696-0-17234000-1421656665_thumb.png

post-846696-0-00276600-1421656765_thumb.png

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • By MaLd0n
      -OpenCore Vanilla TUTORIAL-
       
       
      -USB Port Mapping TUTORIAL-
       
        1 -Create a USB bootable
       
      Create your usb installer, use this tool and download Catalina or Big Sur from Apple servers
       
      Catalina
      installScript_allfullapp.zip
       
      Big Sur
      installScript_1016fullapp.zip
       
      Credits: crazybirdy
       
      Copy Catalina / Big Sur installer to Applications folder, open terminal and run
       
      Catalina
       
       
      Big Sur
       
       
      If you want check one step by step, check here
       
      -Opencore Vanilla Tutorial
      https://tinyurl.com/ycvcnp8h
       
      2- EFI folder USB installation
       
      -EFI OpenCore Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition in your USB STICK
      https://tinyurl.com/ybwr9kq3
       
      -EFI Clover Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition in your USB STICK
      https://tinyurl.com/y6avuxsv
       
       
      3- EFI folder SSD
       
      -EFI OpenCore Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition SSD 
      https://tinyurl.com/ybwr9kq3
       
      -EFI Clover Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition SSD
      https://tinyurl.com/y6avuxsv
       
      4- Start Fine Tune
       
      Run this app and post full dump here for full ACPI solution
       
      RunMe.app
      https://tinyurl.com/y9562hz7
       
       
      If you like a SSDT way, here we go
      SSDT-OLARILA.aml.zip
       
      5- USB Solution
      USB INTEL SERIE 400.zip
       
      Use these kexts, enable XHCI port limit patch and follow this tutorial for remap USB ports
       
       
       
      --DSDT PATCHES--
       
      -FIX ERRORS AND WARNINGS -FIX ACPI ERRORS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE ID -DMAC -REMOVE LINES, PROBLEMATIC and UNUSED -FIX K.P in REBOOT -NVRAM -REAL TIME CLOCK -SLPB -DARWIN / WINDOWS -XHCI -PLUGIN TYPE -HDEF -ARTC -IPIC -TIMR -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -UAR1 -LAN -FWHD -USBX -PMCR -PPMC -XSPI -kUSBCompanionIndex -io-device-location -IMEI -EC -PNLF -ARPT -GFX0 -NVME -ACPI-WAKE-GPE -DTGP -HDMI / HDAU  
      --SCREENSHOTS--































      -If you want to buy me a beer - Donations with PayPal
      https://tinyurl.com/r2bvzm7
       
      Big Thanks to XLR and your Badass Motherboard, Ultrafast CPU, Coolest Heatsink, Huge Graphics Card, Tonnes of RAM,
      Gigantic Hard Drive, Lightspeed Disk Burner, Professional Sound Card, Massive LCD Display.
       
       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others!

      We're all here to have fun and learn from each other!
    • By y010204025
      Update: On October 24, 2020, using clover to solve the macOS11 beta10 boot problem, you can now enjoy macOS11beta10, and the compatibility of subsequent versions is not guaranteed.
      HIDPI uses a modified version. You can directly execute the hidpi script to get a better experience. If you lose the repair, it is not within the scope of my support.
      Support upgrades without destroying the integrity of the original image.
      There seems to be a problem with the shortcut keys. If you can help solve it, thank you for your contribution.
       
      Perhaps it was the first NEC (Lenovo) Lavie Z HZ550 to install hackintosh. I hope more people who like Lavie Z series can experience Hackintosh at HZ550. She is really great.
       
      I found HZ550 & HZ750 on the Chinese website, which is amazing. It weighs only 790g, 13.3 inches, and the standard 2k screen, which is too attractive to me. I am a Hackintosh enthusiast. I think HZ550 or HZ750 with MacOS is the best Unfortunately, the Lavie Z series is not listed in China, only exists in the Japanese and American markets, and in the Japanese market is the NEC brand, while the American market uses the Lenovo logo.
       
      Fortunately, I got an HZ550 from Taobao. Yes, not HZ750. In comparison, HZ750 has more touch screens and 360 ° flip. These are hard to attract me. More importantly, HZ750 is about 200g heavier than HZ550 That's why I chose HZ550. Well, because he is only 2,000 RMB.
       
      The specific introduction can refer to NEC Japan official website:http://nec-lavie.jp/products/hz13b/
       
      The HZ550 hardware list I obtained:
                                    
                       -/+:.          ningnan@ningnandeMacBook-Air
                      :++++.          OS: 64bit Mac OS X 10.15.5 19F96
                     /+++/.           Kernel: x86_64 Darwin 19.5.0
             .:-::- .+/:-``.::-       Uptime: 19m
          .:/++++++/::::/++++++/:`    Packages: 1
        .:///////////////////////:`   Shell: zsh 5.7.1
        ////////////////////////`     Resolution: 3840x2160
       -+++++++++++++++++++++++`      DE: Aqua
       /++++++++++++++++++++++/       WM: Quartz Compositor
       /sssssssssssssssssssssss.      WM Theme: Blue (Dark)
       :ssssssssssssssssssssssss-     Disk: 11G / 108G (12%)
        osssssssssssssssssssssssso/`  CPU: Intel Core i7-5500U @ 2.40GHz
        `syyyyyyyyyyyyyyyyyyyyyyyy+`  GPU: Intel Iris Graphics 6100
         `ossssssssssssssssssssss/    RAM: 4376MiB / 8192MiB
           :ooooooooooooooooooo+.    
            `:+oo+/:-..-:/+o+/-     
       
       
      Advantages: small size, light weight, 2K screen, 8G memory, 512g SSD, keyboard feels good, and wireless network card can be replaced, which is unimaginable in today's thin and light books.
      Disadvantages: The sound is small, almost the same as the mosquitoes.
       
      Ok, bragging is over!
      In order to use the wireless network, I changed the wireless network card from inter 7265 to BCM94352ZAE. Some people called it DW1560. It is uncomfortable that in China, this card and his elder brother DW1830 were hyped to a high price of 480RMB. of. Fortunately, I bought it early, and this card is also very stable under win10, and there is no high delay and outage. The hard disk should be PM951 of Samsung, not PM981, which is lucky.   Before installing Hackintosh: You need to prepare a 16G U disk, SanDisk is not a rough choice for making MacOS installation disk, I used the latest MacOS Catalina 10.15.5, got config.plist from Rehabman, and put together an EFI, the latest version of clover and kext drivers. Thanks to Rehabman and the developers of the Black Apple community. I do n’t like that OC team very much.
      Make an installation disk: If you have a computer running MacOS, you can use the command line to make it, if you do n’t have a computer running MacOS, you can try VMware, I know that the insanelymac forum allows discussion, or use ether to write the image to U disk, use the EFI I provided to boot into the installation process.   BIOS setting: Press F12 at boot to enter the BIOS settings, Tab switches to "Security-Secure boot", set to "DISable", this is what we need, and switch to "Boot -Boot devices", set the U disk as the first boot item You can directly enter the clover guide interface, please follow it for google it.
      It is worth noting that the remaining space of your EFI partition needs to be greater than 200M, otherwise, the disk format will be wrong. In addition, the format partition format is APFS, do not choose to encrypt, your data is not valuable, at least you must have this awareness of Hackintosh, the file safe is also the same, do not enable, do not use to find your mac, otherwise, change the machine, OK .   Fortunately, no additional ssdt patch is required. All the patch functions are implemented through clover. The flat Apple is turned on. This is to solve the problem of the flower screen. You can find a solution yourself.
      Experience your black apple, this will bring a better experience than MacBook Pro.  
       
    • By miliuco
      What is CFG Lock and MSR 0xE2?
       
      CFG Lock is a BIOS setting that allows writing to a specific register, in this case MSR E2 (MSR = Model Specific Register). An MSR consists of one or more registers in blocks of instructions used to do certain tasks on a CPU. MTRs are also used to control CPU's access to memory ranges. Commands capable of reading and writing to MSR work with elevated privileges (the operating system, primarily).

      Many motherboards come from factory with MSR E2 region locked (read but not write) and quite a few of them even hide this option in BIOS user interface. In those that do show the option to block or unblock this variable, it is usually called CFG Lock. CFG Lock is a bit with 2 values, 0x1 or 0x0. When it is 0x1, macOS cannot write into this region and kernel patches are required.

      macOS wants to write this registry, both the Kernel and AppleIntelPowerManagement. It defines the C-states of the CPU, which is why it is essential for macOS. Without the ability to write to MSR E2, all or most of the CPU power management is lost and the system does not boot.

      In Clover 2 patches have been used: KernelPM (for AppleIntelPowerManagement.kext) and KernelXCPM (for the kernel). In OpenCore 2 others have been used: AppleCpuPmCfgLock (for AppleIntelPowerManagement.kext) and AppleXcpmCfgLock (for the kernel). These patches fix the problem but the registry is still read-only. To ensure native CPU power management, CFG Lock bit must be set to 0x0.

      To achieve this, the firmware must be modified to support writing to MSR E2. This method is preferred over Clover and OC patches, it generates greater system stability and the CPU power management more closely resembles that of a real Mac. The methods that are usually proposed for this task are too complex for most users who do not have a high level of knowledge, requiring specialized tools and even modified Grub.

      Below I comment on an alternative method that is much simpler and that, at least in my case, seems to have been successful. Like any of the methods that modify this bit, it has the risk of not working or even damaging the BIOS, so if you try it it is under your entire responsibility.

      CFGLock.efi

      User @Brumbaer has a tool called CFGLock.efi (see post). It is an EFI application, it has to be installed in OC Tools folder (Misc - Tools in config.plist) and in this way it is available in the OC menu next to Reset NVRAM. It should be accompanied by another tool included in the OC package called VerifyMsrE2.efi that reports current status of CFG Lock (locked / unlocked).

      When CFGLock.efi runs, it displays information (CFG variable found, varstore in which it resides, current reading and requests user intervention to make the change from 0x1 to 0x0 or vice versa). Then you have to restart. With VerifyMsrE2.efi we can check if the change has been successful.

      Both EFI applications can be run by selecting them directly in the OC menu but it is also possible, by installing OpenShell.efi tool, to run this shell and running them from there. Information for handling OpenShell.efi is available in OC and elsewhere.
       

       
      After CFGLock.efi

      I have tried CFGLock.efi and apparently it has worked well.
       
      macOS boots up and works fine with the OC patches AppleCpuPmCfgLock and AppleXcpmCfgLock disabled.
        VerifyMsrE2.efi reports "This firmware has UNLOCKED MSR 0XE2 register!".
        Hackintool in Utilities - Get AppleIntelInfo displays this text: AppleIntelInfo.kext v3.0 Copyright © 2012-2017 Pike R. Alpha. All rights reserved. IA32_MISC_ENABLES................(0x1A0) : 0x850089 ------------------------------------------ - CFG Lock............................. : 0 (MSR not locked) Note: Hackintool current version (3.4.6) doesn't show text after Get AppleIntelInfo in Big Sur beta 10. It's got from Catalina.
        Intel Power Gadget - Frequency graph shows variations between maximum and minimum suggestive of CPUPM.  

    • By chris1111
      Here my theme of OC 

      How to create are own Theme with Icnspack-Builder
       

       
      You can Download the themes with ➤ Themes Downloader
      You can also have the themes on ➤ Github
      You can also have the themes on ➤ HTML Page
       
    • By qmgoqwe
      I have installed MacOS and Windows on the following hardware:
       
      AMD Ryzen 7 3700X MSI B450M Mortar Max Sapphire Radeon Pulse RX 5600 XT 6G Samsung 860 QVO, 1 TB SSD (PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x1)/Sata(0x5,0xFFFF,0x0)) - MacOS on this disk Kingston A2000 SSD 1TB M.2 2280 NVMe (PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,15-AD-CD-26-28-B7-26-00)) - Windows on this disk  
      OpenCore 0.6.1 MacOS 10.15.7 both disks GPT UEFI  
      Both OSs boot nicely and work as a charm when selecting either of the disks as boot disks in the BIOS.
       
      However, trying to boot Windows 10 from the Opencore Bootmanager (no matter whether PickerMode=internal or OpenCanopy) causes a Windows Blue Screen ("SYSTEM THREAD EXCEPTION NOT HANDLED").
      To be on the safe side, I have added an appropriate entry to Misc->Entries:
      <key>Arguments</key> <string></string> <key>Auxiliary</key> <false/> <key>Comment</key> <string>Not signed for security reasons</string> <key>Enabled</key> <true/> <key>Name</key> <string>Windows 10</string> <key>Path</key> <string>PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,15-AD-CD-26-28-B7-26-00)/HD(1,GPT,2E9695CB-0F9A-4005-AADB-2FF9C96AD02C,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi</string> It points to the Windows 10 bootmanager on the Windows disk's EFI partition.
       
      What's wrong with that? Why does this cause a BSOD? It is not clear to me why it works when booting from BIOS but not here.
       
      config.plist attached (but maybe it has no relevance for the problem).
      config.plist
×