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

[THESCHU]

Indeed, as any normal macos installation you will encounter a few reboots during installation (I think 3 or 4 time) the only difference here you will each time be presented with the clover boot menu from you bootable USB (remember your SSD is not yet bootable at this time).
You just have to select to continue installation from ssd (not usb, I guess that you restart the installation then) as many times is needed. At some point you get to the macos configuration screens (where you enter your icloud credentials etc)

Just tested it again with a USB 2.0 64GB stick, as I thought maybe the 3.0 stick might be the issue. But alas, the same result: Exactly 5 times rebooting and selecting the SSD, then everything ends in utter darkness. I'm a little bit out of ideas right now... Cheers from Hamburg, Mike

 

[Leesureone]

Dear all,

I recently acquired an Intel NUC 8i7BEH with 32GB Ram and an Samsung Evo Plus 970 NVME. Following every step from the excellent post #901 in this thread (updating SSD to newest firmware, creating USB with Unibeast, replacing EFI-Folder), I am able so start the Mojave installation up until the point "15 Minutes Remaining" after choosing the language, from that moment on the system keeps rebooting and I always end up in the Clover menu, where I can choose between starting the installation from the USB-Stick or the Samsung SSD. What am I missing here? Thanks in advance for any help, much appreciated!

Mike

Hi Mike, are you sure you updated the firmware on your Samsung Evo Plus 970 drive?

Just tested it again with a USB 2.0 64GB stick, as I thought maybe the 3.0 stick might be the issue. But alas, the same result: Exactly 5 times rebooting and selecting the SSD, then everything ends in utter darkness. I'm a little bit out of ideas right now... Cheers from Hamburg, Mike

Are you selecting "Install Mojave" from your hard drive after the first reboot?

 

[HedgeHog2k]

Just tested it again with a USB 2.0 64GB stick, as I thought maybe the 3.0 stick might be the issue. But alas, the same result: Exactly 5 times rebooting and selecting the SSD, then everything ends in utter darkness. I'm a little bit out of ideas right now... Cheers from Hamburg, Mike

Did some searching and it’s actually really the way macos works! I’m baffled...https://www.macrumors.com/how-to/use-mac-volume-keys-adjust-monitor-audio/

 

[THESCHU]

Hi Mike, are you sure yo updated the firmware on your Samsung Evo Plus 970 drive? That sounds lik

Are you selecting "Install Mojave" from your hard drive after the first reboot?

Hey Leesureone,
YES!!!! That was the solution, thanks so much!!!! I trusted the Samsung "Magician" software in updating correctly under windows, which it didn't somehow. Correctly updated the Samsung firmware now via unetbootin, after that the installation finished and everything runs perfectly. Thanks to everyone helping so quickly, great community indeed!

 

[spottsy]

See here:

#1,009

Hi Leesureone, sounds like this will fix my having no audio after I wake from sleep or do system restart using HDMI out for both video and Audio. If I unplug and plug in the HDMI cord to monitor all works. IS THIS CORRECT OR DOES THIS FIX ANOTHER OPTION?

The solution you quote says the below. How does one rebuild caches. I think I found the solution and understand what to do here. Just checking it is correct. https://www.tonymacx86.com/threads/solved-how-to-rebuild-kextcache.224241/

So I put the reboot into the clover screen and put the -f at the end of the line.

Then I put the following into terminal: sudo kextcache -i / and reboot

BELOW IS THE COMMENT OF MOVING KEXT LOCATION
Ok so I had nothing in the Library/Extension folder from Rehabman installation.
So it was all good. All the kexts were in the Other folder.

What I did is I moved ALL THE KEXTS but FakeSMC.kext to the Library/Extension folder and rebuilt caches

 

[HedgeHog2k]

Hi Leesureone, sounds like this will fix my having no audio after I wake from sleep or do system restart using HDMI out for both video and Audio. If I unplug and plug in the HDMI cord to monitor all works. IS THIS CORRECT OR DOES THIS FIX ANOTHER OPTION?

The solution you quote says the below. How does one rebuild caches. I think I found the solution and understand what to do here. Just checking it is correct. https://www.tonymacx86.com/threads/solved-how-to-rebuild-kextcache.224241/

So I put the reboot into the clover screen and put the -f at the end of the line.

Then I put the following into terminal: sudo kextcache -i / and reboot

BELOW IS THE COMMENT OF MOVING KEXT LOCATION
Ok so I had nothing in the Library/Extension folder from Rehabman installation.
So it was all good. All the kexts were in the Other folder.

What I did is I moved ALL THE KEXTS but FakeSMC.kext to the Library/Extension folder and rebuilt caches

And did it fixed your audio issue? I also moved my kexts to L/E (I used hackintool). I didnt lose my audio the few times I woke my system out of sleep. Haven’t rebooted yet.

 

[Leesureone]

Hi Leesureone, sounds like this will fix my having no audio after I wake from sleep or do system restart using HDMI out for both video and Audio. If I unplug and plug in the HDMI cord to monitor all works. IS THIS CORRECT OR DOES THIS FIX ANOTHER OPTION?

The solution you quote says the below. How does one rebuild caches. I think I found the solution and understand what to do here. Just checking it is correct. https://www.tonymacx86.com/threads/solved-how-to-rebuild-kextcache.224241/

So I put the reboot into the clover screen and put the -f at the end of the line.

Then I put the following into terminal: sudo kextcache -i / and reboot

BELOW IS THE COMMENT OF MOVING KEXT LOCATION
Ok so I had nothing in the Library/Extension folder from Rehabman installation.
So it was all good. All the kexts were in the Other folder.

What I did is I moved ALL THE KEXTS but FakeSMC.kext to the Library/Extension folder and rebuilt caches

Sounds like you did well, next time rebuilding the kext cache is as easy as executing the terminal command, you can forgo the -f at boot.

 

[Anotherone]

Is it still possible to install Sierra on a NUC8i5BEB with BIOS 74 (i bought my NUC only a few days ago)? I tried with the explanations in Post #1, but all my tries stuck at/after IntelMausiEthernet and i found a post that the newer bios versions require a newer Clover (otherwise stucks) but when i use it (e.g. Clover 5070) i get the error "This version of Mac OS X is not supported on this platform". Has someone Sierra running with newer BIOS?

 

[chinese_spy]

Is it still possible to install Sierra on a NUC8i5BEB with BIOS 74 (i bought my NUC only a few days ago)? I tried with the explanations in Post #1, but all my tries stuck at/after IntelMausiEthernet and i found a post that the newer bios versions require a newer Clover (otherwise stucks) but when i use it (e.g. Clover 5070) i get the error "This version of Mac OS X is not supported on this platform". Has someone Sierra running with newer BIOS?

NUC8i5 in terms of specs looks like MacBookPro15,2 - A1989 - 3214 with High Sierra 10.13.6 minimum os supported. NMHO it's unlikely that anyone will be able to install Sierra on it.

 

[Leesureone]

NUC8i5 in terms of specs looks like MacBookPro15,2 - A1989 - 3214 with High Sierra 10.13.6 minimum os supported. NMHO it's unlikely that anyone will be able to install Sierra on it.

Is it still possible to install Sierra on a NUC8i5BEB with BIOS 74 (i bought my NUC only a few days ago)? I tried with the explanations in Post #1, but all my tries stuck at/after IntelMausiEthernet and i found a post that the newer bios versions require a newer Clover (otherwise stucks) but when i use it (e.g. Clover 5070) i get the error "This version of Mac OS X is not supported on this platform". Has someone Sierra running with newer BIOS?

It could be possible but why would you want to? A few hoops to jump through with bios revisions and system definitions for sure. Older software to accomadate?