@tofuconfetti
Would it be too much to ask for a zip of your EFI? I've been working all afternoon trying to get OC7.7 to install Monterey OR BigSur for me. It keeps giving me the middle finger (Prohibited Stop sign).
Catalina continues to work perfectly on OC7.0 But, I'm missing something important with the big changes between 7.0 and 7.7. I would like to comb through yours to see what I am missing... if you don't mind.
Where does your install fail? If it fails very early, saying something like it cannot read the kernel, then for me that was the OpenHFsPlus.efi driver. That is the driver I assumed was the one I wanted, since it was included with the OpenCore 0.7.6 zip file. But I realized that what was happening was that the boot loader could not read the filesystem on the USB drive. So, I went and found the HFsPlus.efi driver that is not in the OpenCore zip file and then everything booted right up. So try that next.
Then if that isn't the problem, as in it's not failing to boot right off the bat, then carefully double check your BIOS settings. I mean CAREFULLY. That also happened to me. For some weird reason, the "Other OS" setting had reverted to "Windows OS".
I'll post my EFI folder, but I just generated a random iMac20,2 SMBIOS, it's up to you to insure it's unique or generate your own per the opencore instructions, which I HIGHLY RECOMMEND. I use the boot-args flag required for the Radeon RX6800XT, "agdpmod=pikera", which apparently you need as well providing you are using the RX5700XT Nitro listed in your profile. So if this EFI does not boot your computer, look carefully at the BIOS settings.
On the matter of creating your own USBMap kext, while the methods were really straightforward using the Opencore recommended tools, they just gave random results on Monterey because the USBInjectAll kext and port limit setting does not work. Also, it took me a while (several hours) to understand the logic behind the USBMap_All kext the original poster provided. But it did start to make sense. I simply took a diagram of the motherboard from the manual, which lists the USB controllers on the board and the header connections and slowly it started to make sense. I was under the impression that you mapped each individual port, but that is not the case. If you map a USB controller to a HSxx resource, all of a sudden all the USB 2.0 ports on that controller work. So, as you read through his "USBMap_All" kext, by opening the kext by right clicking it and selecting "show package contents", then go to that folder and load the Info.plist into ProperTree, you'll see that you can select and reorder and rename ONLY, each resource and choose the ports you want. That took me a long time to get to that point. I just followed my nose and it worked.
What I do not know, and anyone still feel free to point me to a guide, is how to actually discover how the ports are laid out and id their resource from the DSDT handed to the OS by the BIOS (I think that's how it works). I can do it using a standalone USBView under windows, but I certainly don't want to install Windows everytime I install a new motherboard (I only use Windows when forced). Then once discovered, how do you get from that to the USBMap_All kext provided by the original poster? That is what I am still missing.
Here is the generic EFI folder. And remember, create your own SMBIOS as this one may not work. And if you get a black screen, fiddle with the boot-args under the NVRAM section of your config.plist.
SMBIOS creation under platform info on this page of the instructions:
