Jump to content
Welcome to InsanelyMac.com - No more ads! And some exciting news... Read more... ×
Sign in to follow this  
Followers 0

[Guides]NEC(Lenovo) Lavie Z HZ550 hackintosh with UEFI only

5 posts in this topic

Recommended Posts

Posted (edited)

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:

                 -/+:.          [email protected]
                :++++.          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



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.



Edited by y010204025

Share this post

Link to post
Share on other sites

I have the same laptop and I want to try to make it run on catalina.


My problem is that I do not have any macbook or any mac machine here to create the installation disk.


Is there a way to create it on windows only? I tried running vmware + mac ... but it was super slow.. that is why I ask if there are other tools on windows that I could use to create the installation disk.


how is your battery running on catalina? is it the same? or it consumes battery faster on catalina? how about the temperatures? comparing it when running on windows 10



Share this post

Link to post
Share on other sites

Hey, I can understand your confusion. This is how I tried. You need a mirror that can be used for installation, and you can get it here. Then use etcher or transmac to write to the U disk, so you will get an installation disk with clover boot. It is recommended to delete the EFI directory in the installation disk and move to the EFI provided by me. You will be able to or a USB flash drive that can be booted/installed on HZ550.
1. Make and install U disk, replace EFI boot
2. Make a winPE maintenance disk, which is helpful for you to perform some other operations, including modifying the disk partition and the ESP partition size of the notebook hard disk (500M is recommended, and the minimum is not less than 200M)
3. Modify the BIOS settings, disable fast startup, and select UEFI boot mode.
4. Shut down, insert winPE maintenance U disk, enter winPE, modify what you need to modify
5. Using bootice, add clover boot item in UEFI series, locate the location of cloverx64.efi, then rename the name of boot item to clover, and move it to the first boot item.
6. Shut down, insert the macOS installation U disk, boot, if you are lucky, you will see a brand new interface, and then you can install normally.
Tip: Prepare 2 U disks, one for making macOS boot disk and the other for making winPE maintenance U disk. The remaining space of the hard disk ESP partition cannot be less than 200M, otherwise you will not be able to format the hard disk partition as HFS before installation or apfs format. Finally, don't choose encryption, don't choose anytime.
Maybe you have difficulty reading Chinese. This is the same as when I read English. On blog.daliansky.net, there are some articles similar to insanelymac, you can read them. skepe:[email protected], you can communicate with me if necessary.

Share this post

Link to post
Share on other sites



Sorry if I can't really understand some steps... I am pretty new with Hackintosh. A friend lend me a hackintosh running on catalina but he is not the one who installed it so I cannot ask him.


1. Downloaded catalina from app store.

2. Formatted the USB (Sandisk 128GB - I have no other usb drive here): Opened `DiskUtility` > Erase (Format: Mac OS Extended, Scheme: GUID Partition Map)

3. Run this in Terminal: sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/USB /Applications/Install\ macOS\ Catalina.app --nointeraction

4. Downloaded Clover Configurator

   a. Tools > Mount EFI

   b. On `EFI Partitions`, click `Mount Partition` on the USB drive

   c. On the USB drive, click `Open Partition` and it will open in Finder

5. Downloaded your `EFI_HZ550.zip`, and Extracted it. I found two folders `BOOT` and `CLOVER`

6. Replaced the EFI folder on the USB installer with the downloaded EFI from y010204025

7. Restarted my lavie and go to BIOS to disable secured boot, and set boot priority to USB disk. Then Restart lavie

8. When it boots from USB, select boot from USB to install catalina (left side choice)

9. It shows something like when booting in recovery mode, do not install catalina yet... Open disk utility to erase the partition on the disk where you will install catalina.

10. Before erasing the main disk, Select Format as `Mac Journaled` and Scheme `GUID Partition Map`. Then click `Erase`

11. After erasing the main disk, its time to install catalina on the main disk. Proceed with the installation process/steps. It may restart a couple of times, when it do... during booting on USB... select the option on the right side (boot mac on disk... not on usb installer).


Issues I encountered AFTER installing catalina on my lavie:

1. Whenever my lavie restarts, before showing the apple loading logo... it first show the clover boot UI and you have to press enter first to select boot mac from HDD. It would be great to just see the apple logo loading directly instead of presenting the clover boot page for a few seconds before the apple loading logo.

   Solution: None as of the moment 

2. Wifi and Bluetooth not working:

   Solution: I need to change the wifi card to an apple compatible card like DW1560, hopefully it will be supported by apple and no driver/kext will be needed (just a guess)

3. USB ports works selectively depending on the device plugged in: I tried plugging in my wireless mouse (2.4Ghz) and it cannot connect via USB dongle, Same with my USB mech keyboard (wired and wireless BT)... it does not connect also. But when I plugin my USB -> Ethernet which is from apple.. it works like charm. I am using this to connect to LAN (Internet). Also, I connect a generic wired mouse via USB and it also worked.

   Solution: Seems not all USB devices can be used with mac.

4. Track/touch pad basic functionality only: Only left and right click and mouse pointer functions on my track/touch pad. No gestures yet, unlike when running on windows where I can do multi fingers gestures.

   Solution: Download VoodooI2C, extract and copy VoodooI2C.kext and VoodooI2CELAN.kext to (mac partition) EFI > CLOVER > kexts > Other. Then restart. You should be able to use simple gestures.

5. Display resolution quality: The current resolution is 1440p which displays the texts and icons very small. I need to lower the resolution to make the text readable. In windows, I can set the resolution to 1440p but set the quality to either 150% to 200% and the texts will be readable and images are more sharp (nice to look at). In catalina, I cannot find the settings for display quality 100%-200%... I can only change the resolution.

   Solution: Select appropriate scale/resolution in Settings > Displays > Display. This is not the best solution but with this you can set/change the resolution.


Update: DW1560 I bought seems not compatible with Lenovo, what is the specific wifi card you use y010204025? I just installed my DW1560 on the other catalina hackintosh machine and it works... but not on my lavie.

Problem is that I do not know how to install the wifi antenna for DW1560 in a SFF/Mini PC .. seems there is no improvement in the Wifi/BT hahaha.



Thanks y010204025!


Edited by Borgy Manotoy

Share this post

Link to post
Share on other sites

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.


Share this post

Link to post
Share on other sites
Sign in to follow this  
Followers 0

  • Similar Content

    • By 5T33Z0
      Background: Since the Pre-Release of Clover v5123, OpenCore Momory Fixes have been integrated into Clover in the form of OpenRuntime.efi. It replaces previous AptioMemory Fixes. Since v5126 AptioMemoryFixes are obsolete and no longer supported, so an upgrade to v5126 is mandatory in order to be able to install and boot macOS BigSur with Clover.
      This guide is for everyone trying to update to the latest Clover version or having issues while updating from previous versions, so they can install and run BigSur on their Machines. While updating to the latest iteration of Clover, there are several obstacles one can come across along the way. This guide is here to assist users trying to make the switch from the "old" Clover version with AptioMemory Fixes to the new one with OpenRuntime and Quirks Settings in CloverConfigurator.
      Problem: If you update your existing Clover installation by either installing the clover.pkg file or manually updating it the way you used to this will most likely result in an inoperable bootlader due to missing boot parameters.
      Approach: In order to avoid the dilemma of your system not wanting to boot, you have to know that the following files are obsolete and are no longer necessary, so they should eiither be disbabled/deleted when updating Clover from a built prior to v 5123 or omitted altogether when setting up a new EFI Folder:
      AptioMemoryFixes: AptioMemoryFix.efi, OsxAptioFix3Drv.efi, OsxAptioFixDrv.efi and everyhing else containing "memoryfix". Unnecessary Drivers (for UEFI-based Systems): DataHubDxe.efi – enables DataHub Protocol Support if it is missing from the BIOS. Modern UEFI BIOSes support this. So it's probably only necessary for Legacy Systems. FSInject.efi – For Kext-Injecttion. But pretty much obsolete since it's fully integrated in Clover nowadays. Might be necessary for Legacy Systems, though. SMCHelper.efi – Necessary when using FakeSMC.kext and ONLY FakeSMC. If you use it in combination with VirtualSMC.efi, it leads to an instant Kernel Panics. So, in other words: when using VirtualSMC – which is higly recommended over FakeSMC – DON'T use SMCHelper, use it in conjunction with VirtulSMC.efi (although unnecessary in most cases). EmuVariableUefi.efi – necessary for emulating NVRAM, if NVRAM is either not available (legacy systems) or working incorrectly. OcQuirks.efi and OcQuirks.plist – delete if present. OcQuirks is a relict from earlier attempts to include OpenCore Booter Quirks into Clover up until version 5122. Incompatible Kexts – wherever possible, you should use the latest available kexts provided by acidanthera (one of the devs behind OpenCore). Because incompatible Kexts are a source for Kernel Panics. I had an issue with my Laptop where VoodooPS2Controller.kext would cause a kernel Panic when used alongside VoodooPS2Mouse.kext, VoodooPS2Trackpad.kext and VoodooPS2Controller.kext. At the time I updated clover from 5122 to 5123, I didn't know that these 3 kexts are now includes as plugins inside of VoodooPS2Controller, so having them twice would cause a panic.

      In general, having Kexts wich have depedencies to oher kexts can cause a KernelPanic if not loaded in the correct order. In OpenCore, you can and have to set up the correct loading order of kexts manually by yourself, but in Clover only a few essential kexts like Lilu and Fake/VirtualSMC are hard-coded in, so they are always loaded first. It took me a while to figure this out. So when you update Clover and you are using lot of Kexts (usually on Laptops), try to update all Kexts first using Kext-Updater which is incredibly useful tool to download all sorts of bootloader-related files, have a look inside of them so see if they include more kexts as plugins and make sure nothing is present twice – HID, Wifi and Bluetooth kexts come to mind here. If you get panics you can not isolate, just move all unnecessary kexts to the "off" folder to temporarily to work around the issue by starting with a minimal set up to get the system running. Then put the disabled kexts back one by one to find the culprit for the panic.  
      Updating your EFI
      Prepare an USB Stick. Format it to FAT32 (MBR). We'll use it for testing our updated EFI Folder first, before copying it to the ESP on the HDD. Download the latest Clover Release  as a .zip archive for a manual update (currently "CloverV2-5126.zip"): https://github.com/CloverHackyColor/CloverBootloader/releases Extract the .zip. We'll create our EFI based on the one insides of it. Have a look at the "EFI > Clover > drivers > off > UEFI" Folder – you find the following Files: Copy the following files over to EFI > Clover > drivers > UEFI: ApfsDriverLoader.efi, VBoxHfs.efi and OpenRuntime.efi Now we have a minimal set of Drivers which looks like shown below. The files tagged in gray are in the drivers Folder by defautl and are most likely unnecessary on UEFI-based systems. As mentioned earlier, SMCHelper MUST be deleted when using VirualSMC.kext! I would turn of each of the gray drivers one by one and chick if the system still boots without them.
      Next, copy over your kexts (updated to the latest available version, of course), your ACPI > patched folder and your config.plist form your existing EFI Folder Open CloverConfigurator and update it to the latest Version. It should now include a new section at the bottom called Quirks, as mentioned earlier Now open your config.plist you copied over from your working EFI and click on "Quirks". It should look like this (without the descriptions of course):
      Head over to the OpenCore Install Guide and pick the guide for your CPU Family and Platform. Jump to the "Booter" Section. It contains all required Booter Quirks tinted green in the screenshot. Make sure to unfold the "more in-depth info" box to see what they do. Find the options for your system and tick them away in Clover Configurator. Next, jump to the "Kernel" section of Dortania's guide and copy over the settings from "Quirks" and "Scheme". Again, make sure to unfold the "more in-depth" section to find all necessary settings. NOTE: some of the settings Located in "Kernel > Quirks" have different names and are located in the "Kernel and Kext Patches" section of Clover Configurator. These include:

      In most cases you have these set up correctly already, otherwise your system wouldn't have started before. But it's good to double check if you have settings enabled which may be unnecessary. Once you've ticked all the necessary quirks, save your configuration, copy the new EFI Folder to the root of your USB Flash Drive and try booting from it. If everything was set up correctly, the system should boot as expected. If it does boot, you can mount the ESP partition of your hard drive, backup your EFI Folder, delete it and put in the one from your USB Flash drive to make the changes permanent.  
      TROUBLESHOOTING: If you get Kernel Panics take a note of them and head over to the OpenCore Troubleshooting Guide and have a look at the "OpenCore Boot issues" and "Kernelspace Issues" sections to find your error message and possible fixes to resolve it. Another great resource to check if your Clover config is set-up correctly in general (excluding Quirks) is the Hackintosh Vanilla Desktop Guide For more info about how OpenCore differs from clover and see which settings, drivers and features are compatible, check out the Clover Conversion Guide.
      Good luck!
      PS: If you run into trouble after following this guide you can upload your config.plist and I can have a look at the quirks.
      PSS: When running BigSur, you need to remove the PreBoot Volume from the "Hide" Section of the GUI because if I understand correctly, BigSur requires booting from it.
      PSSS: if your system boots correctly you can upload a screenshot with your quirks with additional Info like your Board and CPU which might be helpful for other users.
    • By fantomas
      In Big Sur Apple decided to exempt many of its apps from being routed thru the frameworks they now require 3rd-party firewalls to use (LuLu, Little Snitch, etc.)
      Q: Could this be (ab)used by malware to also bypass such firewalls?
      A: Apparently yes, and trivially so.

      View full article
    • By fantomas
      Q: Could this be (ab)used by malware to also bypass such firewalls?
      A: Apparently yes, and trivially so.

    • By fantomas
      macOS Big Sur 11.1 beta (20C5048k)