Contribute
Register

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

Attachments

  • 3.png
    3.png
    238.5 KB · Views: 69
I had my NUC stop working, but reinstalled Cat and maybe EFI. The Hacs don't seem to like having more than one drive running Clover on the NUCs (I had three installed). The Clover installs seem to write on each other's EFIs (and Win10's efi which I removed). This is probably half of my troubles with the Hacs. I got it working again and am trying to put the serials into it with SMBIOS and got a serial that is Invalid and one that is not activated/Validated. The problem is that the instructions say that you want number three (Validated) but in Note 2 it says that in the long term it may be better to use the invalid serial since someone may purchase and want to activate their serial. (Big Conflict) That makes sense, but I thought that the procedure was to get a Valid serial and activate it - but note two advises against it more or less. I find this a little contradicting/difficult. I could care less about iMessage etc. I am still running Yosemite on my UD5H which has been much less trouble. No iMessage and I guess you don't need the serials (on Yosemite). It works reliably, but is aged. The Question is: do I just use the Invalid serial to avoid hassle later which makes some sense, or use an invalid and not expect to call the support line with issues? I have my new (2018) mac mini which I can use if a problem arises. It appears that the issue is iMessage requires a Unique Serial to know where to send the messages, so you want a serial. Don't use the Valid one because of Later conflict, and the only real problem is Don't Bother the support line with your issues since they may object. Is this the bottom line? I am putting my serial operation on hold while I wait for your input.

I really appreciate and value your input and advice. Thanks,
You can not use valid serials because it will cause issues with people that own the actual product.
  1. Generate a serial in clover or macserial
  2. Check it is not valid
  3. Use this for the EFI
Tip: ditching clover and moving to OpenCore is the best way to get support
 
This is the first time in over 300 pages I've ever heard a user report slow boot times. My only suggestion at this point is to turn on the -v flag (its off now) so you can see where it stops or slows down (you should see "ignoring kextcache from early boot" early on where it will pause for a couple of seconds, that's normal). Pay attention to other stops points and take a photo or write down what it says and then post it or search Dortania for an answer.
Apparently, TURNS OUT it was cause of low disk space. Of all the chokes in verbose, low disk space was one of them.
It significantly increased boot time and actually messed up Youtube VP9 decoder (weird ikr). So I extracted ˜100GB from another partition back and it fixed everything.

I originally uploaded a few chokes for you but I guess the mod never went through with my post. Thank you for the suggestion tho.
 
Apparently, TURNS OUT it was cause of low disk space. Of all the chokes in verbose, low disk space was one of them.
It significantly increased boot time and actually messed up Youtube VP9 decoder (weird ikr). So I extracted ˜100GB from another partition back and it fixed everything.

I originally uploaded a few chokes for you but I guess the mod never went through with my post. Thank you for the suggestion tho.
It was an unusual issue, glad you got that figured out. What do you mean "choke"?
 
It was an unusual issue, glad you got that figured out. What do you mean "choke"?
Well I did what you asked and recorded every point that was a slow in verbose boot. So whenever a line just sits there, i called it a choke.
Funny thing is that low apfs volume warning caused a bunch of other warning like "Intel Firmware" kept getting repeated for MINUTES.
Therefore, I kept messing arround with Intel Bluetooh on/off, kext/cache etc...it was a nightmare. But a simple increase in storage volume fixed everything :)
 
So, you want to hear a story, eh...? A tale of adventure across the config.plist & kext files? Ha!
But i, just put this here... :)
BEHOOOOOLD!!!
...ULTRA SUPER MEGA FULL HDmi 4K WiFi T
ype-C BT HiRes BIG SWAG BUILD of EFI OC 0.6.6 for Catalina 10.15.7 on NUC8i7BEH (and big sur 11.2.2)

Works:
  • ALL!(wifi, bluetooth, type-c, hdmi, hdmi and type-c monitor together, audio over hdmi, sleep, headphones(i have Sennheiser HD380 Pro - sound perfect), MicroSD)
Just add your MLB, ROM, SystemSerialNumber and SystemUUID to config.plist file start from line 1282

PS: BIG THANKS to comrade Leesureone!!!
Hope my EFI helps someone get a fully functional Catalina or Big Sur )
From Russia with Love :)

warning! - on some models nothing will work and the device can make exploooosion, but you can try... and tell me how it worked on your model =)

---------------------------------------------------------------------------
0) 0087 BIOS > load BIOS defaults > click advanced and change:
1) Devices > USB > Port Device Charging Mode: off
2) Devices > USB > USB Legacy > Disabled
3) Security > Thunderbolt Security Level > Legacy Mode
4) Power > Wake on LAN from S4/S5 > Stay Off
5) Boot > Boot Configuration -> Network Boot > Disable
6) Boot > Secure Boot > Disable
---------------------------------------------------------------------------
GOOD LUCK TO YOU HACK HUNTER!!!
 

Attachments

  • EFI.zip
    10.5 MB · Views: 153
Last edited:
Hi everyone,

I've just updated open core with leesureone EFINUC8i7OC6.7.
just add MLB, ROM, SystemSerialNumber and SystemUUID to config.plist.
restart and I'm still with OC 0.6.6.
when I type In terminal : nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version
the result is REL-066-2021-02-02
Same result with Hackintool tell me I'm using open core 0.6.6
What I did wrong?
 
Hi everyone,

I've just updated open core with leesureone EFINUC8i7OC6.7.
just add MLB, ROM, SystemSerialNumber and SystemUUID to config.plist.
restart and I'm still with OC 0.6.6.
when I type In terminal : nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version
the result is REL-066-2021-02-02
Same result with Hackintool tell me I'm using open core 0.6.6
What I did wrong?
Reboot and clear the Nvram, it will show 6.7 is installed after that.
 
Back
Top