Contribute
Register

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

Good news, I just managed to sort the internal Bluetooth issue.

Confirmed working on NUC8i7BEH (Mojave), no idea if it works for older/other NUCs (I included a few firmware files apart from the one actually used for my hardware, one can always find more in the linux-firmware package).

I haven't tested it yet, I have some questions. Will this break at each update? Can it be made into a kext eventually? you know this is awesome. The NUC8 can see its BT in MacOS but doesn't work. I was sure it could be enabled. Does Handoff work too with your fix?
 
Try this config.plist and see if last booted volume works

Hello

I have a problem with my NVRAM - it doesn't seem to work. I did the nvram test and some troubleshooting from the iMessage fix page on this site. They didn't seem to work.

I installed Catalina on my Nuc8i7BEH1 using clover 5102 and your EFI folder from CatNUC8 EFI.zip. I generated new S/N and SmUUID with clover configurator and they are valid.

Did your NVRAM work after the initial install? If so, any suggestions on what I might have missed or can do to fix this issue? I thought about running the Catalina installer again, but I do not want to wipe my current install because I foolishly installed software etc before deciding to use iMessage.

Any help would be appreciated.

Thx
 
Last edited:
Hello

I have a problem with my NVRAM - it doesn't seem to work. I did the nvram test and some troubleshooting from the iMessage fix page on this site. They didn't seem to work.

I installed Catalina on my Nuc8i7BEH1 using clover 5102 and your EFI folder from CatNUC8 EFI.zip. I generated new S/N and SmUUID with clover configurator and they are valid.

Did your NVRAM work after the initial install? If so, any suggestions on what I might have missed or can do to fix this issue? I thought about running the Catalina installer again, but I do not want to wipe my current install because I foolishly installed software etc before deciding to use iMessage.

Any help would be appreciated.

Thx
Never had an issue with MVRAM that I know of, I don't use iMessage because I have an Android phone but its worked for me. Check and see if you have EmuVariableUefi-64.efi installed in your EFI/Clover/Drivers/ UEFI file. If you don't, try adding it. If you do try deleting it.

Edit: Follow the steps in this guide first is my recommendation, there have been zero issues reported with NVRAM with these NUCs I am aware of.
 
Last edited:
Hi!

I have a NUC8i7BEH, 64 GB RAM, Catalina 10.15.2, bios 077, using Leesureone latest EFI folder (I just modified the config.plist to support the 64GB RAM).

Everything works great, I think this has been asked before: when I connect in pre boot a Thunderbolt 3 Sabrent Dock or an external Nvme 2TB drive enclosure they works great, but if I unplug the TB3 device or if my NUC goes to sleep, my computer immediately restart itself, (the TB3 in bios is in legacy).

Any suggestions? this is driving me crazy

thanks!!
 
Hi!

I have a NUC8i7BEH, 64 GB RAM, Catalina 10.15.2, bios 077, using Leesureone latest EFI folder (I just modified the config.plist to support the 64GB RAM).

Everything works great, I think this has been asked before: when I connect in pre boot a Thunderbolt 3 Sabrent Dock or an external Nvme 2TB drive enclosure they works great, but if I unplug the TB3 device or if my NUC goes to sleep, my computer immediately restart itself, (the TB3 in bios is in legacy).

Any suggestions? this is driving me crazy

thanks!!
k
Something new I think or I don't recall this being posted about before. I don't have much advice except to also search outside of this thread for help. Not all Thunderbolt 3 devices work with OS X so at least you have that going for you. I suppose it could be related to how USB is configured in the SSDT you are using but that is only a guess. There is ongoing work on hot plugging Thunderbolt 3 devices here:
https://www.tonymacx86.com/threads/in-progress-ssdt-for-thunderbolt-3-hotplug.248784/
 
Hi guys. Do we have some where instruction (step by step) how to fix BT on NUC8i7BEH?
Am just try this one #2,069 made by Nemphys. By may be I did something wrong (
Try to switch on ubuntu desktop, activate BT and go back to MacOS. BT still not working.
 
Never had an issue with MVRAM that I know of, I don't use iMessage because I have an Android phone but its worked for me. Check and see if you have EmuVariableUefi-64.efi installed in your EFI/Clover/Drivers/ UEFI file. If you don't, try adding it. If you do try deleting it.

Edit: Follow the steps in this guide first is my recommendation, there have been zero issues reported with NVRAM with these NUCs I am aware of.

Thanks for the suggestions.

That is one of the guides I followed before with no luck.

The iMessage troubleshooting script shows that I'm keeping the same nvram values between reboots, but echoing "hello world" to nvram isn't stored between reboots.

I used your EFI folder. Reinstalling clover doesn't allow me to do a custom install to ensure rc scripts are installed, so I am kind of stuck at that point. I think that may be my issue, but I'm not sure.
 
Thanks for the suggestions.

That is one of the guides I followed before with no luck.

The iMessage troubleshooting script shows that I'm keeping the same nvram values between reboots, but echoing "hello world" to nvram isn't stored between reboots.

I used your EFI folder. Reinstalling clover doesn't allow me to do a custom install to ensure rc scripts are installed, so I am kind of stuck at that point. I think that may be my issue, but I'm not sure.
That is odd, customization of clover is a given. Maybe try repairing permissions on your hard drive and try again. I don't think that's the issue though. Did you go through the process of signing all your devices out and then regenerating a new serial number and uuid? You can't reuse the ones in my EFI folder.

 
That is odd, customization of clover is a given. Maybe try repairing permissions on your hard drive and try again. I don't think that's the issue though. Did you go through the process of signing all your devices out and then regenerating a new serial number and uuid? You can't reuse the ones in my EFI folder.


I did my install and then copied over your EFI directory and opened config.plist with clover configurator. I then generated new serial and UUID numbers, checked their validity online with another computer and then saved my config.plist, and rebooted with network connected.

I think it has to do with my clover install. I posted in the clover forum and I will let you know if I get it working.

I appreciate your help and you posting your EFI file. All of my devices work perfectly.

What version is your BIOS at? I'd like to upgrade, but I don't want to go to a version that will cause me to lose functionality.
 
I did my install and then copied over your EFI directory and opened config.plist with clover configurator. I then generated new serial and UUID numbers, checked their validity online with another computer and then saved my config.plist, and rebooted with network connected.

I think it has to do with my clover install. I posted in the clover forum and I will let you know if I get it working.

I appreciate your help and you posting your EFI file. All of my devices work perfectly.

What version is your BIOS at? I'd like to upgrade, but I don't want to go to a version that will cause me to lose functionality.
Version 77. I saw your other post and the answer made me realize how the changes to Clover may have effected you. I haven’t updated so haven't had any issues (ignorance is bliss :eek:) . You know you can always use an older version, it's not really a downgrade, just something else to try.
 
Last edited:
Back
Top