Clover's menu never shows up when put EFI\Clover\drivers\UEFI\ApfsDriverLoader.efi

[oldman20]

Provide the original Clover Install EFI which you created couple of days ago.

Your mean Clover stock from github? I used Clover pkg 5148 from https://github.com/CloverHackyColor/CloverBootloader

 

[EliteMacx86]

Your mean Clover stock from github? I used Clover pkg 5148 from https://github.com/CloverHackyColor/CloverBootloader

Here's what you need to do.

Backup your existing Clover EFI
Delete your current EFI
Install Clover using the guide linked below

GUIDE - How to Install Clover Bootloader [UEFI/Legacy]

How to Install Clover Bootloader [UEFI/Legacy] An EliteMacx86 Exclusive Guide - This guide covers the installation of Clover Bootloader for UEFI and Legacy systems for booting macOS. 1. Download Clover Bootloader 2. Right click on the .pkg file you downloaded above and select Open. 3. Once you...

elitemacx86.com

Make changes to your config.plist
Attach the EFI

 

[oldman20]

Here's what you need to do.

Backup your existing Clover EFI
Delete your current EFI
Install Clover using the guide linked below

GUIDE - How to Install Clover Bootloader [UEFI/Legacy]

How to Install Clover Bootloader [UEFI/Legacy] An EliteMacx86 Exclusive Guide - This guide covers the installation of Clover Bootloader for UEFI and Legacy systems for booting macOS. 1. Download Clover Bootloader 2. Right click on the .pkg file you downloaded above and select Open. 3. Once you...

elitemacx86.com

Make changes to your config.plist
Attach the EFI

I followed first your post , but same. I think if config.plist wrong, macos cant boot, right?
My problem: if load ApfsDriverLoader and HFS.efi from root usb via EFI Shell, mac can boot. But if put they in properly path Efi/clover/drivers, clover GUI even cant showup

 

[EliteMacx86]

I followed first your post , but same. I think if config.plist wrong, macos cant boot, right?
My problem: if load ApfsDriverLoader and HFS.efi from root usb via EFI Shell, mac can boot. But if put they in properly path Efi/clover/drivers, clover GUI even cant showup

You need to understand that you don't need to boot with that as you have already tried to boot and there is some issue. So, i need to check first and then outline what's wrong with that.

 

[oldman20]

You need to understand that you don't need to boot with that as you have already tried to boot and there is some issue. So, i need to check first and then outline what's wrong with that.

I create new EFI and same! Black Clover GUI. Dont think of any reason. Suck
Even in the early days of getting acquainted with hackintosh, I have not encountered a situation like this. Normally when I choose to boot into the mac partition, I will panic, bbut this case can't enter the Clover GUI interface even

 

[EliteMacx86]

I create new EFI and same! Black Clover GUI. Dont think of any reason. Suck
Even in the early days of getting acquainted with hackintosh, I have not encountered a situation like this. Normally when I choose to boot into the mac partition, I will panic, bbut this case can't enter the Clover GUI interface even

Now, all you need to do is attach that EFI so that i can check for you

 

[oldman20]

Now, all you need to do is attach that EFI so that i can check for you

off course, plz

oldman20-CloverEFI.zip

drive.google.com

 

[EliteMacx86]

off course, plz

oldman20-CloverEFI.zip

drive.google.com

Well, you did not install the Clover as per the guide.

If you used the Clover installation guide, a Clover Install log file is created within the EFI directory which is missing in your case.

Here are the issues

- Remove the off directory from Clover/drivers directory
- ApfsDriverLoader.efi, AudioDxe.efi and SMCHelper.efi are missing.
- You're having multiple kext folders which are not recommended at all. A new guide for Clover is coming soon with everything updated. But it has been already discussed here

GUIDE - How to Boot macOS Installer on Laptops using Clover (UEFI/Legacy)

Booting macOS installer on laptops can be a challenge for the new users. This guide covers a complete step to boot the macOS installer on your Laptop using Clover bootloader. Those who are not using Clover, can update their configuration for clover and continue to use it. Clover is one of the...

elitemacx86.com

See "Placing required Kexts" section.

- You forgot to install a theme. The following guide recommends installing BGM theme, regardless of the UEFI or Legacy install.

GUIDE - How to Install Clover Bootloader [UEFI/Legacy]

How to Install Clover Bootloader [UEFI/Legacy] An EliteMacx86 Exclusive Guide - This guide covers the installation of Clover Bootloader for UEFI and Legacy systems for booting macOS. 1. Download Clover Bootloader 2. Right click on the .pkg file you downloaded above and select Open. 3. Once you...

elitemacx86.com

- You're using PluginType=YES and also using SSDT-PLUG which is the wrong approach. Read here

GUIDE - How to Enable CPU Power Management on macOS [Intel/AMD]

How to Enable CPU Power Management on macOS [Intel/AMD] This guide covers the implementation of CPU Power Management for Intel and AMD CPUs on macOS using Clover and OpenCore. By following this guide, you'll be able to enable Intel or AMD CPU Power Management on macOS using Clover or OpenCore...

elitemacx86.com

- The Default Boot Volume and Legacy parameter is missing.
- Also, the recovery should be disabled using "NeverDoRecovery" option in Boot section.
- NVIDIA and ATI properties are still added which should be removed.
- Language and Screen Resolution is not set
- Inject ATI and Inject NVidia should be unchecked/disabled.
- DellSMBIOSPatch must be set to True to fix the truncating issue on Dell Systems.

 

[macpro]

- Inject ATI and Inject NVidia should be unchecked/disabled.

if you had read all of Rehabman's guide you would know why they are set to enable

although you could use your own config.plist's for your guide, then there would be no issue

 

[EliteMacx86]

if you had read all of Rehabman's guide you would know why they are set to enable

Looks like you're having outdated information. They're no longer required as a user can use the Device Properties method to disable the discrete GPU (either NVIDIA or AMD) using disable-external-gpu WEG's property. Secondly, the user can also use "-wegnoegpu" boot arg which is also a property of WEG.

Other solutions are to define an external declaration in an SSDT with the path of the actual GPU and it can also disable the GPU. The other way is traditional which requires DSDT+SSDT to disable the GPU.

although you could use your own config.plist's for your guide, then there would be no issue

Indeed!