I'm not going to pretend to understand the output of all these tools but I'm working on it. This issue has forced me to take a crash course in the inner workings of OC. I'm fairly certain that I had OC boot loader when I restored from a TM backup, I just didn't notice the difference since the OC EFI was no longer showing at boot. I actually installed 3 mojave backups, 1 SATA SSD (WD500), 1 PCIe NVMe SSD and a USB 3.1 flash drive on PCIe slot 3. The 2 SSDs were identical Mojave installs and the flash drive is a clean install of Mojave. I left the WD500 alone and turned off TM backups for all drives. My intention is to install Monterey on the WD500 again. I used the other 2 to see if the TM backup with OC loaded was the problem which as it turns out, is yes. I was hoping to try out MLOC on the flash drive to make sure there are no more issues but my renewed RX 580 came today and I'm anxious to get installed with Monterey running. I'm also fairly certain that all I have left to do is uninstall OCLP via Dortania's instructions and install MLOC along with the RX 580 but I want to get confirmation first.we can see OpenCore is blessed (BootOrder0001),
OpenCore is sitting in Sata Bay 1, on the WD500 drive.
The path was disk1s1 during reading the dump. The path varies from boot to boot.
You can use my little script: mount ESP from list. This shows Sata Bay 1 and WD500ish, too.
config.plist in the ESP also shows the OCLP version.
OCLP 0.6.8 was written in a NVRAM variable. That dont mean it was running.
The Romdump-timestamp.log shows if OpenCore runtime variable was written. Firmware spoofing is another clear sign of OC running or not. Both should be read in the log.
Those are some data points to troubleshoot with the information the Dumper gives.