Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Dolphins1972

macrumors regular
Oct 1, 2017
116
43
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.
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.
 

Dolphins1972

macrumors regular
Oct 1, 2017
116
43
But your "current boot screen" is the OpenCore boot picker, not the native Apple boot manager.

You are already running OpenCore. OpenCore is already blessed.
I'm fairly certain I could have fixed my issue if I had read this: https://dortania.github.io/OpenCore-Legacy-Patcher/TROUBLESHOOTING.html#infinite-recovery-os-booting before I panicked and did the TM backup to get access to my files again. I was stuck in infinite recovery when 12.6.8 security update crashed the boot partition. Now how do I revert the Kepler patch?
 

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
Now I'm confused again. I erased the boot drives then did the TM restore via a bootable flash drive. Does that action erase the ESP also?
Depends, Disk Utility default to erase "partition" (Physical Volume / Container) only, but not erase the entire "drive" (Physical Disk). In that case, the EFI partition won't be formatted, and all OpenCore (no matter good or bad) stuff will still be there.

However, if you click the "Show All Devices" first, then select the "Physical Disk" to erase. Then yes, the ESP will be erased.

Screenshot 2023-08-18 at 0.48.44.png

Screenshot 2023-08-18 at 0.48.47.png

Screenshot 2023-08-18 at 0.48.49.png

As you can see from the above screen captures. All Disk, Container, Volume are erasable. Therefore, if you pick the wrong one, the ESP won't be touched.

For HFS+, there is no Container, but just Disk or Volume.
 
Last edited:
  • Like
Reactions: Macschrauber

Dolphins1972

macrumors regular
Oct 1, 2017
116
43
OK first I want to thank you and Macschrauber for all the help and educating me. Thank you!

Currently only the WD500 has an OS, the others are just storage. I can erase the entire disk from the top (highlighted) and that should clear out any traces of OC including the post-install patches, right?

Then I can reinstall Mojave to WD500 using my flash drive in the following order:

Do a clean install of Mojave (not TM backup), replace the GTX 680 (flashed) with the RX 580 (non-flashed), reset NVRAM and disable SIP, install MLOC to the WD500 drive and bless.

Is there anything I'm missing, e.g. OC settings?
Screen Shot 2023-08-17 at 12.06.43 PM.png
 

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
Currently only the WD500 has an OS, the others are just storage. I can erase the entire disk from the top (highlighted) and that should clear out any traces of OC including the post-install patches, right?
Correct

Do a clean install of Mojave (not TM backup), replace the GTX 680 (flashed) with the RX 580 (non-flashed), reset NVRAM and disable SIP, install MLOC to the WD500 drive and bless.

Is there anything I'm missing, e.g. OC settings?
I think you better just use RX580 but not the GTX680. Boot screen is not required for Mojave installation. And the Mojave installer may not recognise the GTX680 as a Metal supported card.

But yes, once you get Mojave running, you can reset NVRAM, disable SIP, install my package to the WD500 ESP.

Anyway, you better mount all drive's EFI partition one by one, and check if there is any OpenCore stuff remaining.

It's more than once that people asking for help (e.g. can't remove OC, or can't update OC, etc). End up because there were multiple OC installed onto different drives. Therefore, their cMP keep running from a "hidden" OC copy.

Before you do anything, you better check all EFI partitions, make sure they are clean.
 
  • Like
Reactions: Dolphins1972

Dolphins1972

macrumors regular
Oct 1, 2017
116
43
RX 580 is DOA. Either both HDMI ports are bad or the GPU itself is dead. It doesn't even turn on monitor. Had to reinstall GTX 680 and do another restore from TM backup because it's not recognized as a Metal capable GPU.
 

Macschrauber

macrumors 68030
Dec 27, 2015
2,979
1,487
Germany
RX 580 is DOA. Either both HDMI ports are bad or the GPU itself is dead. It doesn't even turn on monitor. Had to reinstall GTX 680 and do another restore from TM backup because it's not recognized as a Metal capable GPU.

a Mojave createinstallmedia boot stick does not recognise any Kepler GPU as Metal compatible. This is a known bug.

The solution is to boot High Sierra or another instance of Mojave and run the Installer App.

Everyone should have a working Mojave or High Sierra System to boot from in case of a problem.

An old spinner is enough, or an USB thumb drive with 64GB, nowadays available for peanuts.
 

Dolphins1972

macrumors regular
Oct 1, 2017
116
43
a Mojave createinstallmedia boot stick does not recognise any Kepler GPU as Metal compatible. This is a known bug.

The solution is to boot High Sierra or another instance of Mojave and run the Installer App.

Everyone should have a working Mojave or High Sierra System to boot from in case of a problem.

An old spinner is enough, or an USB thumb drive with 64GB, nowadays available for peanuts.
I have a bootable USB thumb drive with Mojave installed and another one with a Mojave installer. Both of them rebooted me into recovery after loading about a 3rd of the way on the progress bar. I guess I would have to fall back to High Sierra and then update to Mojave, not sure why? I checked the installed drive and I'm able to boot into it normally as if it were my boot drive once I have the TM backup up and running.
 

Dolphins1972

macrumors regular
Oct 1, 2017
116
43
Screen Shot 2023-08-22 at 3.29.42 PM.png
Finally back on the Monterey train with new RX 580 and MLOC question withdrawn for now - but I have 1 more question. I'm running MLOC 0.9.4 but there is no BlueToolFixUp or BlueTooth-Spoof in config.plist. I have legacy bluetooth.
 
Last edited:
  • Like
Reactions: garibaldo
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.