[Guide] Intel NUC7/NUC8 using Clover UEFI (NUC7i7Bxx,NUC8i7Bxx,etc)

[jvelascov]

Hi, I am very interested in trying the "Enable ON/OFF Bluetooth and Enable WiFi Beta Support". I managed to set up a NUC8i3BEK2 with Catalina and OP 0.6.2, thanks to Leesureone's guides yesterday. With some fiddling it works very good now apart from Blt onoff and onboard wifi. Only thing am not so sure of is the best way to add your strings Code=Bash to get the kexts to work. I did try with ProperTree but did not quite understand exactly where I should enter your Codes. Can you give some info about that? This is my first Hack with OpenCore aswell, so quite many thinks to look for....

With ProperTree, for BLuetooth you have to create a Children in Kernel> Add> after loading the Bluetooth Firmware,
with the parameters that are in the post, and to increase the WiFi one Children to the last.
Perhaps something easier to work with plists is "PlistEdit Pro" but it is a paid tool.
Although with a plain text editor it does the same job.
The current version of OC is 0.6.3, something easier may be to download this version NUC8OC6.3EFI_JV.zip it already includes everything mentioned.

 

[nane30]

I have it going on my Z490 but I haven't done anything with my NUC8 yet, it will work, there are no major changes in it that affect how this platform performs. The 6.2 version I posted should boot Big Sur with changes in the config.plist under Misc/ Security/SecureBootModel from "Default" to "Disabled"

Works fine, download from you the "EFINUC8i7OC6.3 Big Sur Ready", adjusted the id/serials, disabled verbose + updated some kexts. all fine

 

[Richtw]

I think it's about time for me to move from clover to opencore 1) big sur is coming. 2) it looks like appleALC kext has issues with my install if I update beyond 1.49. 3) Clover 5123 and above seem to have an opencore kludge/componenent and I would need to figure that out. What's my first steps as far as reading and homework? Are the guides/forums to start with? I tried going back 30 or so pages here.

 

[Leesureone]

I think it's about time for me to move from clover to opencore 1) big sur is coming. 2) it looks like appleALC kext has issues with my install if I update beyond 1.49. 3) Clover 5123 and above seem to have an opencore kludge/componenent and I would need to figure that out. What's my first steps as far as reading and homework? Are the guides/forums to start with? I tried going back 30 or so pages here.

Here's your reading assignment (just kidding) but this is the best source of information by platform. https://dortania.github.io/OpenCore-Install-Guide/config.plist/coffee-lake.html#starting-point


The NUC8's are Coffee Lake CPUs so keep that in mind, I've got an EFI Folder for OpenCore version 6.3 on page 90 of this thread that works with Big Sur Release 1 but which will also work for Catalina. To test it out back up your important data, create or use your USB boot Disk, mount the hidden EFI Partition and then add my EFI folder there. Hit F10 and choose the USB UEFI partition to boot it. If everything is working you can follow the guide to create your serial numbers, I recommend using CorpNewt's GENSymios (search for it).

Hope that helps

 

[Richtw]

Here's your reading assignment (just kidding) but this is the best source of information by platform. https://dortania.github.io/OpenCore-Install-Guide/config.plist/coffee-lake.html#starting-point


The NUC8's are Coffee Lake CPUs so keep that in mind, I've got an EFI Folder for OpenCore version 6.3 on page 90 of this thread that works with Big Sur Release 1 but which will also work for Catalina. To test it out back up your important data, create or use your USB boot Disk, mount the hidden EFI Partition and then add my EFI folder there. Hit F10 and choose the USB UEFI partition to boot it. If everything is working you can follow the guide to create your serial numbers, I recommend using CorpNewt's GENSymios (search for it).

Hope that helps

Thanks! I had already downloaded your file, stuck it on the efi partition of a usb stick and it rebooted into macos, so I was starting to wonder if all I had to d was transfer over my personal stuff like serial

 

[Leesureone]

Thanks! I already just finished downloading your file, stick in on the efi partition of a usb stick and it rebooted into macos, so I was starting to wonder if all I had to d was transfer over my personal stuff like serial

Pretty much, if you want to roll your own next update there is a bit of a learning curve. It’s not like Clover where you just download the installer and check a few boxes.

 

[danilovitch]

I had a problem updating Catalina today (19H15) NUC8i3BEK (M.2 only version) I use OPC 0.6.2 and before update I also updated appleALC Lilu WhateverGreen and VirtualSMC. It started alright but after a while an error came up: Couldn't attach disc image error -69736. Is it perhaps a SIP error? I run in full 0x0 mode. Never seen that one before. I tried to update via internal system update.

 

[Leesureone]

I had a problem updating Catalina today (19H15) NUC8i3BEK (M.2 only version) I use OPC 0.6.2 and before update I also updated appleALC Lilu WhateverGreen and VirtualSMC. It started alright but after a while an error came up: Couldn't attach disc image error -69736. Is it perhaps a SIP error? I run in full 0x0 mode. Never seen that one before.

It could be the file is corrupt, delete and download again. Copied this from another site:

Could Not Write Installation Information to Disk​

This message usually shows up as a sheet that drops down from the macOS or OS X installer shortly after you start the install process. It may seem odd but the usual cause is a corrupt installer, and simply deleting the installer app and downloading a new copy will likely fix the issue. The error message seems to occur most often when the Mac installer is downloaded from a third-party site. This is a good reason to download the official copy from the Mac App Store, or join the free public beta program if you want to try out a new version of the Mac OS early.

Other possible causes include a damaged boot drive. Try using Disk Utility’s First Aid capabilities to test and repair your disk, as outlined in First Aid: Verify and Repair HFS+, APFS Drives with Disk Utility.

 

[Drfrag]

I've got an EFI Folder for OpenCore version 6.3 on page 90

I am pretty sure that SecureBootModel can be turned back to Default for BigSur after 6.3 update.

 

[danilovitch]

It could be the file is corrupt, delete and download again. Copied this from another site:

Could Not Write Installation Information to Disk​

This message usually shows up as a sheet that drops down from the macOS or OS X installer shortly after you start the install process. It may seem odd but the usual cause is a corrupt installer, and simply deleting the installer app and downloading a new copy will likely fix the issue. The error message seems to occur most often when the Mac installer is downloaded from a third-party site. This is a good reason to download the official copy from the Mac App Store, or join the free public beta program if you want to try out a new version of the Mac OS early.

Other possible causes include a damaged boot drive. Try using Disk Utility’s First Aid capabilities to test and repair your disk, as outlined in First Aid: Verify and Repair HFS+, APFS Drives with Disk Utility.

Thanks a lot for sharing this info Leesureone! Indeed it must have been a corrupt file. Strangely I did download it from the system update. I had to restart from a cloned disk and I saw in Disk Utility that there was an dmgupdate disc there. Unfortunately it could not be removed with any method that I know of and the disc itself refused to be repaired. I had to restart from a Ubuntu usb stick, reformat the whole disc and then clone Mac OS back from there. I hope it does not have anything to do with my Samsung Nvme disk. I updated that one as you mentioned it on page 90. Maybe I shall try the combined update file next time to see what happens. Apart from that this NUC8i3 works very well with OpenCore 0.6.2.