The icons shown on the OC boot screen above are from a Windows drive (middle icon); what I assume is a FAT32 partition on a pen drive (left hand icon); and the right hand icon is the ResetNvram.efi tool that comes with OpenCore. Although I am surprised it is displayed as the ResetNvram.efi tool is not present in the EFI you linked. In fact the /EFI/OC/Tools folder is not present in the EFI.
You are would need to boot the system using the left hand icon, external drive. Which I assume contains your macOS installer.
The alternative OpenCore EFI you are using is built from OC release 0.6.5 (January 2021), so it is quite old given there have been 13 or 14 additional releases since 0.6.5.
The EFI contains a few items that may not work with your setup, these include but are not limited to the following:
- Spoof-SSDT.aml
- SSDT-XHC.aml
- USBPorts.kext
I would remove these three items from their respective folders and also the entries for the items in the config.plist. The SSDT's may be using alternative ACPI addresses, and the USBPorts.kext will not be set for your motherboard.
The config.plist also contains a number of settings/entries that I wouldn't use with your setup.
- It uses the Outdated AMD Kernel Patches, which contains 39 patches when the new set only use 16 patches. These lack the option to set the CPU core count correctly. They are not bad per say, but are not ideal for your setup.
- The Kernel > Quirks > XhciPortLimit entry is enabled, which is nonsense when you have a USBPorts.kext in your setup. These two will clash.
- It lacks the ProvideCurrentCpuInfo quirk, so your CPU won't be identified correctly.
- It lacks the npci=0x2000 boot argument, which AMD systems require if Above4G Decode is not enabled in the bios.
- The creator of the config has been playing with the SIP (csr-active-config) and Bootercfg entries in the NVRAM section.
- It lacks the SecureBootMode entry required for Big Sur and Monterey, probably not included in this older OC release.
I wouldn't recommend using this EFI.