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

[Leesureone]

I got to delete the files listed under "Cleaning the Clover Junk in macOS" but did not do the steps under “Removing kexts from macOS(S/L/E and L/E)” and “Cleaning the Clover Junk in your hardware” because those commands seem like I would need to be booted into the os on the NVMe drive to do so. I did not want to take the chance or running it will using the external drive and it applies the process to the external drive instead of the NVMe drive.

I restarted the NUC and reset the NVRAM but still could not get the Mojave OS to go.

Do you know if I can apply the commands listed under “Removing kexts from macOS(S/L/E and L/E)” and “Cleaning the Clover Junk in your hardware” to the NNMe drive while still running off of the external SATA drive? If so, how can I do that?

Doing this "“Removing kexts from macOS(S/L/E and L/E)” and “Cleaning the Clover Junk in your hardware" using terminal but targeting a different drive seems like a good idea but I'm not sure how to change the command to target a different drive. You can delete kexts manually but then you'd still need to reset the kextcache which is about the same problem. I have a couple other suggestions for you though.
1. Now that you can see the USB drives and can pick one to boot from try using Clover again but with the one version I have uploaded on page 90. That maybe all you have to do to get back to your original desktop and if you like you can then finish clearing out Clover and trying to boot with OC.
2. If 1. works just keep using that version of Clover that has the RTC fix in it. If it doesn't you can use one of the newer versions of the Clover boot drive you created and copy the ACPI/DSDT/Patches section of the config.plist from my Clover EFI to yours. It has the RTC fix in it you need. I use PlistEdit Pro for editing which is free for 15 days or something. There are other plist editions you can use, don't use a text editor though.
3. Make sure you have everything you need backed up and start fresh again using Open Core

Hope that helps and please report back

 

[firepandem]

You saved the day @Leesureone! I got it working agian with the clover you had on page 90.

I did try "Removing kexts from macOS(S/L/E and L/E)” and “Cleaning the Clover Junk in your hardware" using terminal and manually removing the kext files but that did not work even after clearing nvram. So I move on to your #1 suggestion of using the clover EFI form page 90. That worked.

to be safe and not having much time to devote to it at the moment, I will rest it here as-is for now. When I get more down time, I will try to switch to OC again and upgrade to Big Sur

Question:
At this point, using Clover 5112 with Mojave, What steps do I need to make in order to upgrade to Big Sur (when I'm ready to do so)?

Thanks again for the great help and support you provided. Greatly appreciated!!

 

[Leesureone]

You saved the day @Leesureone! I got it working agian with the clover you had on page 90.

I did try "Removing kexts from macOS(S/L/E and L/E)” and “Cleaning the Clover Junk in your hardware" using terminal and manually removing the kext files but that did not work even after clearing nvram. So I move on to your #1 suggestion of using the clover EFI form page 90. That worked.

to be safe and not having much time to devote to it at the moment, I will rest it here as-is for now. When I get more down time, I will try to switch to OC again and upgrade to Big Sur

Question:
At this point, using Clover 5112 with Mojave, What steps do I need to make in order to upgrade to Big Sur (when I'm ready to do so)?

Thanks again for the great help and support you provided. Greatly appreciated!!

Glad to hear you are back and have Mojave working again. If you are thinking about upgrading to Big Sur then I do not recommend Clover as your boot loader. It can work, there are folks who are using Big Sur and Clover. To me its odd though in that the latest versions of Clover that support Big Sur have to utilize core components of (wait for it...) OpenCore.

It's a mash up now and requires tweaking the config.plist, like OpenCore, to work. Might as well learn OpenCore is my opinion.

 

[me0076]

has someone updated to Big Sur 11.2.3 with the EFI folder (OC6.7) provided in the page 90? any issues?

 

[Leesureone]

has someone updated to Big Sur 11.2.3 with the EFI folder (OC6.7) provided in the page 90? any issues?

Sorry for the late reply, away for a few days. You should be fine if you haven't already updated.

 

[me0076]

Sorry for the late reply, away for a few days. You should be fine if you haven't already updated.

Hi Leesureone, thanks for your reply. Actually I have tried but no success until now. First I have updated my OC from 6.3 to 6.7 on my main drive. Everything went smoothly and faced to issues (currently running Big Sur 11.0.1). Unfortunately I can't just update to latest version of Big Sur with software update within macOS Big Sur. It tells me your mac is up to date and no newer update is available. I think this is mostly due to broken snapshot seal. Anyhow I decided to do a clean install. I have created a bootable USB disk for Big Sur 11.2.3 and put your EFI folder in the EFI partition of that drive. After that I have restarted my NUC but OpenCore 6.7 doesn't show me the drive, from which I can install Big Sur 11.2.3. To be sure that my newly created USB drive is not faulty, I also connected an older version of Big Sur USB installation drive that had OpenCore 6.3 on it and booted to OC 6.3. Surprise... I could see both of Big Sur Installation drives. I don't know what is causing the issue that does not let me see the installations drives from OC 6.7. I have also checked the ScanPolicy and it is set to 0 in my config.plist.

Any help would be appreciated and many thanks in advance.

 

[Leesureone]

Hi Leesureone, thanks for your reply. Actually I have tried but no success until now. First I have updated my OC from 6.3 to 6.7 on my main drive. Everything went smoothly and faced to issues (currently running Big Sur 11.0.1). Unfortunately I can't just update to latest version of Big Sur with software update within macOS Big Sur. It tells me your mac is up to date and no newer update is available. I think this is mostly due to broken snapshot seal. Anyhow I decided to do a clean install. I have created a bootable USB disk for Big Sur 11.2.3 and put your EFI folder in the EFI partition of that drive. After that I have restarted my NUC but OpenCore 6.7 doesn't show me the drive, from which I can install Big Sur 11.2.3. To be sure that my newly created USB drive is not faulty, I also connected an older version of Big Sur USB installation drive that had OpenCore 6.3 on it and booted to OC 6.3. Surprise... I could see both of Big Sur Installation drives. I don't know what is causing the issue that does not let me see the installations drives from OC 6.7. I have also checked the ScanPolicy and it is set to 0 in my config.plist.

Any help would be appreciated and many thanks in advance.

There's something odd, I haven't found what it is yet but have a work around. Use the OC6.6 EFI folder to install off the USB drive and then you can update the hard drive to 6.7 later if you want.

 

[bitbass]

Sorry if I'm missing the obvious, but which page do I start from to rebuild with OC and Big Sur? Not sure I want to wade through 406 pages until I find it.

 

[Leesureone]

Sorry if I'm missing the obvious, but which page do I start from to rebuild with OC and Big Sur? Not sure I want to wade through 406 pages until I find it.

Page 90

 

[me0076]

There's something odd, I haven't found what it is yet but have a work around. Use the OC6.6 EFI folder to install off the USB drive and then you can update the hard drive to 6.7 later if you want.

Indeed really odd. I found some spare time and did as you suggested and it worked Many thanks for your help.