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

freddomseven

macrumors member
Original poster
Aug 28, 2020
52
3
Followed the instructions on this page https://dortania.github.io/OpenCore-Legacy-Patcher/BUILD.html
when I reboot and hold or not hold the option key, the only option shown is High Sierra
If you select High Sierra it shows the prohibited screen
If you select nothing, it still goes to prohibited screen
Then a few seconds after computer shuts down

Im on a Mac Pro 5,1, with metal GPU, latest boot rom

Please advise
 

BrianBaughn

macrumors G3
Feb 13, 2011
9,843
2,505
Baltimore, Maryland
So you have a by-their-instructions, OCLP-built installer of the macOS of your choice on a USB stick plugged into one of the USB ports on that Mac Pro when your rebooting and holding down the option key?
 
  • Like
Reactions: freddomseven

freddomseven

macrumors member
Original poster
Aug 28, 2020
52
3
So you have a by-their-instructions, OCLP-built installer of the macOS of your choice on a USB stick plugged into one of the USB ports on that Mac Pro when your rebooting and holding down the option key?
I chose to put it on the os drive first as didn’t have it installed on computer
Was that a mistake ?
 

freddomseven

macrumors member
Original poster
Aug 28, 2020
52
3
I don't understand what you mean. If you haven't started from the beginning of the instructions and followed them exactly then perhaps you should try that.
I didn’t have it originally installed on my main drive(High Sierra OS)
So I thought I had to have it in there first before installing it onto the usb drive
But now it seems to have corrupted the boot drive(main drive)
So I can’t even get into computer to change anything as it just shows the prohibited sign after showing high Sierra on the boot picker screen(at least I think it’s the boot picker screen)
Thanks for your help btw
 

tommy chen

macrumors 6502a
Oct 1, 2018
907
390
the OCLP emulates (SMBIOS) as standard a mac pro 7.1 2019 (martins package a imac pro)
and the minumum system for a MP 7.1 is catalina
 
  • Like
Reactions: freddomseven

freddomseven

macrumors member
Original poster
Aug 28, 2020
52
3
the OCLP emulates (SMBIOS) as standard a mac pro 7.1 2019 (martins package a imac pro)
and the minumum system for a MP 7.1 is catalina
I guess I really screwed up then
I just thought that was the latest version of opencore that supported all the OS’s

So if I connected that ssd that I messed up to another computer and installed the correct version of open core to it
Then put it back on my Mac Pro, do you think that would fix it ?
 

sfalatko

macrumors 6502a
Sep 24, 2016
639
364
I guess I really screwed up then
I just thought that was the latest version of opencore that supported all the OS’s

So if I connected that ssd that I messed up to another computer and installed the correct version of open core to it
Then put it back on my Mac Pro, do you think that would fix it ?
You should ask in the OCLP discord for the correct steps. High Sierra does not need OpenCore and if you install OCLP as one of the previous posts stated it will emulate a MacPro7,1 that cannot boot High Sierra.

You probably want to erase OpenCore from your OS drive and start again. If you erase OC then you should be able to boot into High Sierra and start over.
 
  • Like
Reactions: freddomseven

freddomseven

macrumors member
Original poster
Aug 28, 2020
52
3
I found this page about installing Big Sur with OC on the 5,1 Mac Pro
So Ill do a USB installer and Install to either the blank SSD or NVME drive in my MAc Pro
As this will be my video editing computer, do you think its best to use the NVME as the OS drive or use it as the drive that holds the video files ?

As of erasing OpenCore from the High Sierra OS drive
How do I go about that ?
Is it as simple as mounting drive as an external SSD and deleting files for Open Core ?

Thanks for your help

sfalatko

Really appreciate it
 

tommy chen

macrumors 6502a
Oct 1, 2018
907
390
are you shure you are on the latest bootROM 144.0.0.0.0?

and you can do a deep NVRAM reset do start without OC
 

Dayo

macrumors 68020
Dec 21, 2018
2,257
1,279
A Boot Coup is when an unexpected and/or undesirable item takes over your boot process. In your specific case, OpenCore is an undesirable item as it has been configured by the OCLP in a way that it cannot load the only Mac OS instance you have as well as to execute a boot coup, if it is not the configured boot target, whenever OpenCore is started.

Reseting your NVRAM, deep or shallow, will not help in your case as after such a reset, your Mac will execute an "undefined boot target start" given that the defined boot target would have been erased by the NVRAM reset.

On such starts of your Mac, the first legitimate EFI loader found, following a fixed predetermined search pattern, will be started. In your case, this will be the OCLP configured OpenCore instance in the ESP of the HiSierra disk. As mentioned earlier, OpenCore is configured by the OCLP to establish boot coup conditions whenever it is started ... Catch 22!

So if I connected that ssd that I messed up to another computer and installed the correct version of open core to it
Then put it back on my Mac Pro, do you think that would fix it ?
Your issue is not with the version of OpenCore but how OpenCore has been configured by the OCLP. You do need another computer in your specific case but what you want to do is to only use this to mount the ESP on that HiSierra disk and to delete all the OpenCore files.

After the deletion, reconnect the disk to the original Mac and then execute an NVRAM Reset to load HiSierra. After HiSierra is loaded, go into System Preferences, select the HiSierra disk and restart using the button there.

Reattaching the disk after the deletion and simply rebooting without an NVRAM Reset will work but OpenCore's "Boot Coup" variable, activated by the OCLP, will still be in your NVRAM waiting to detect any presence of OpenCore, regardless of origin or configuration setting, to spring into action. You need the reset to remove the variable and this time, with the OpenCore files deleted, there will be no OCLP configured OpenCore present to immediately execute a boot coup when you start your Mac.

You can then reinstall OpenCore and you need to put OpenCore on a disk that does not hold the supported Mac OS you rely on to boot into if things go bad. In this way, to fix things in such a case, you can just disconnect the disk with OpenCore. So, either a USB stick or another disk in the Mac that only holds data or that holds another Mac OS (or other OS) ... just not your natively supported "fallback" Mac OS.

As it appears that you only have HiSierra in place, I would say the OCLP is not the best choice for installing OpenCore but if you prefer this, then you definitely want to initially install OpenCore on a USB stick that can easily be detached. You can then proceed to install stuff that work with OCLP configured OpenCore ... basically Big Sur and newer.

If you need to boot into HiSierra after installing OpenCore, especially if you want to do this via OpenCore, then I would recommend avoiding the OCLP altogether and that you look into alternative ways of installing OpenCore. One alternative, MyBootMgr (linked in my signature), gives the following options:
  • RefindPlus Boot (Officially Supported and Next)
    • MP31: From Sierra 10.12 back to Leopard 10.5
    • MP41: From Sierra 10.12 back to Leopard 10.5
    • MP51: From Catalina 10.15 back to Snow Leopard 10.6
  • OpenCore Boot (Monterey and Older)
    • MP31: From Monterey 12.x back to Leopard 10.5
    • MP41: From Monterey 12.x back to Leopard 10.5
    • MP51: From Monterey 12.x back to Snow Leopard 10.6
So basically, MyBootMgr will set things up such that you can trivially boot any Mac OS version from Monterey to whatever your cMP was originally released with; either via RefindPlus or via one of the OpenCore instances MyBootMgr creates.

If you want to roll the dice on Ventura, you can "defang" an OCLP configured OpenCore instance for Ventura and incorporate this. Defanging an OCLP configured OpenCore instance means disabling the "Boot Coup" setting the OCLP activates in the OpenCore config file but note that this setting can actually be beneficial for those that only just want to run what the OCLP configures OpenCore to support.

Other good options to implement OpenCore exist of course.
Every option has some quirks that you will need to bear in mind.
The main ones for the OCLP are the boot coup thing and the coverage level.
 
Last edited:

startergo

macrumors 603
Sep 20, 2018
5,021
2,283
Im on a Mac Pro 5,1, with metal GPU, latest boot rom
I am confused. So please explain how do you get to the boot screen with metal GPU? Unless you flashed your GPU or the firmware with the latest OC firmware driver for the boot screen you will not be able to use the option key.
 

freddomseven

macrumors member
Original poster
Aug 28, 2020
52
3
are you shure you are on the latest bootROM 144.0.0.0.0?

and you can do a deep NVRAM reset do start without OC
Yep I do have 144.0.0.0.0
Checked today just to make sure

Great thanks
Ill try a deep NVRAM reset
A Boot Coup is when an unexpected and/or undesirable item takes over your boot process. In your case here, OpenCore is an undesirable item as it has been set up by the OCLP in a way that cannot load the only Mac OS instance you have as well as to execute a boot coup, if it is not the configured boot target, every time OpenCore is started.

Reseting your NVRAM, deep or shallow, will not help in your case as after such a reset, your Mac will execute an "undefined boot target" startup given that the defined boot target would have been erased by the NVRAM reset.

On such starts of your Mac, the first legitimate EFI loader found, after following a defined search pattern, will be booted. In your case, this will be the OpenCore instance in the ESP of the HiSierra disk. As mentioned earlier, OpenCore is set up by the OCLP to establish boot coup conditions every time it is started ... Catch 22!


Your issue is not with the version of OpenCore but how OpenCore has been configured by the OCLP. You do need another computer in your specific case but what you want to do is to only use this to mount the ESP on that HiSierra disk and to delete all the OpenCore files.

After the deletion, reconnect the disk to the original Mac and then execute an NVRAM Reset to load HiSierra. After HiSierra is loaded, go into System Preferences, select the HiSierra disk and restart using the button there.

Reattaching the disk after the deletion and simply rebooting without an NVRAM Reset will work but the OCLP's "Boot Coup" variable will still be in your NVRAM waiting to detect any presence of OpenCore, regardless of origin or configuration setting, to spring into action. You need the reset to remove the variable and this time, with the OpenCore files deleted, there will be no OCLP configured OpenCore present to immediately execute a boot coup when you start your Mac.

You can then reinstall OpenCore and you need to put OpenCore on a disk that does not hold the supported Mac OS you rely on to boot into if things go bad. In this way, to fix things in such a case, you can just disconnect the disk with OpenCore. So, either a USB stick or another disk in the Mac that only holds data or that holds another Mac OS (or other OS) ... just not your natively supported "fallback" Mac OS.

As it appears that you only have HiSierra in place, I would say the OCLP is not the best choice for installing OpenCore but if you prefer this, then you definitely want to put OpenCore on a USB stick that can easily be detached. You can then install stuff that work with the OCLP ... basically Big Sur and newer.

If you need to boot into HiSierra after installing OpenCore, especially if you want to do this via OpenCore, then I would recommend avoiding the OCLP altogether and that you look into alternatives. One alternative, MyBootMgr (linked in my signature), gives the following options:
  • RefindPlus Boot (Officially Supported and Next)
    • MP31: Leopard 10.5 to Sierra 10.12
    • MP41: Snow Leopard 10.6 to Sierra 10.12
    • MP51: Snow Leopard 10.6 to Catalina 10.15
  • OpenCore Boot (Monterey and Older)
    • MP31: Leopard 10.5 to Monterey 12.x
    • MP41: Snow Leopard 10.6 to Monterey 12.x
    • MP51: Snow Leopard 10.6 to Monterey 12.x
So basically, it will set things up such that you can trivially boot any Mac OS version from Monterey to whatever your cMP was originally released with. You can either do this via RefindPlus or via one of the OpenCore instances MyBootMgr creates.

If you want to roll the dice on Ventura, you can "defang" an OCLP instance and incorporate this. Defanging an OCLP instance means disabling the OpenCore "Boot Coup" variable the OCLP activates but note that this variable can actually be beneficial for those that only just want to run what the OCLP supports.

Other good options to implement OpenCore exist of course.
Every option has some quirks that you will need to bear in mind.
The main ones for the OCLP are the boot coup thing and the coverage level.
Many thanks for your very thorough post
As you stated, resetting the NVRAM did nothing
I tried it multiple times, but see now why it wouldn’t work
Im not sure what OCLP stands for ?
What is the ESP thing to install ?
How do I delete the Open Core Files
I will do some more research based on your guidance and try that approach
Thanks again
 

freddomseven

macrumors member
Original poster
Aug 28, 2020
52
3
I am confused. So please explain how do you get to the boot screen with metal GPU? Unless you flashed your GPU or the firmware with the latest OC firmware driver for the boot screen you will not be able to use the option key.
Yes you are correct
I did have a version of Open Core, but deleted it to install the other Open core version that I messed up
Comedy of errors really
Basically thinking I understood what I was doing, but obviously didn’t 🤣
 

startergo

macrumors 603
Sep 20, 2018
5,021
2,283
Yes you are correct
I did have a version of Open Core, but deleted it to install the other Open core version that I messed up
Comedy of errors really
Basically thinking I understood what I was doing, but obviously didn’t 🤣
If you have a Mac GPU you can install it temporarily to boot with OPTION key. Then you can bless the desired boot option by selecting it and using CNTRL+ENTER.
 

freddomseven

macrumors member
Original poster
Aug 28, 2020
52
3
If you have a Mac GPU you can install it temporarily to boot with OPTION key. Then you can bless the desired boot option by selecting it and using CNTRL+ENTER.
Thanks but as you can see above, it won’t boot using option key
Unless I’m not understanding what you’re saying
 

Dayo

macrumors 68020
Dec 21, 2018
2,257
1,279
Im not sure what OCLP stands for
OpenCore Legacy Patcher.

What is the ESP?
EFI System Partition

Explained in the MyBootMgr Documentation:

Screen Shot 2023-02-13 at 06.09.25.jpg

To mount the ESP ...
  • Run diskutil list in Terminal
  • Look for the Identifier of the disk whose ESP you want to mount
    • It will have a value like disk0 or disk8 etc
  • Run sudo mkdir /Volumes/EFI && sudo mount -t msdos /dev/disk#s1 /Volumes/EFI in Terminal
    • Change disk# in the command to match the disk id
    • Remember to keep s1 at the end of the portion
You will now have an EFI volume showing in Finder that you can navigate.
You should be able to right click and eject it when you are done.

How do I delete the Open Core Files?
By mounting the the ESP and deleting the OpenCore related stuff.
In your case:
  • The /EFI/BOOT folder and everything in it
  • The /EFI/OC folder and everything in it
NB: Empty the trash with the ESP still mounted afterwards


I will do some more research
Always a good idea.
 
Last edited:

freddomseven

macrumors member
Original poster
Aug 28, 2020
52
3
OpenCore Legacy Patcher.


EFI System Partition

Explained in the MyBootMgr Documentation:

To mount the ESP ...
  • Run diskutil list in Terminal
  • Look for the Identifier of the disk whose ESP you want to mount
    • It will have a value like disk0 or disk8 etc
  • Run sudo mkdir /Volumes/EFI && sudo mount -t msdos /dev/disk#s1 /Volumes/EFI in Terminal
    • Change disk# in the command to match the disk id
    • Remember to keep s1 at the end of the portion
You will now have an EFI volume showing in Finder that you can navigate.
You should be able to right click and eject it when you are done.


By mounting the the ESP and deleting the OpenCore related stuff.
In your case:
  • The /EFI/BOOT folder and everything in it
  • The /EFI/OC folder and everything in it
NB: Empty the trash with the ESP still mounted afterwards



Always a good idea.
Wow, thanks Dayo for that amazing breakdown and instructions
I’ll try that out tonight and see if I can accurately follow and succeed with your instructions
 

startergo

macrumors 603
Sep 20, 2018
5,021
2,283
Yes I do
Found it in loft yesterday
see attached pic
Ok so this card is NOT metal capable as you stated before, but should have a boot screen. Installing this card and holding OPTION key at boot should take you to the boot screen.
 

freddomseven

macrumors member
Original poster
Aug 28, 2020
52
3
OpenCore Legacy Patcher.


EFI System Partition

Explained in the MyBootMgr Documentation:

To mount the ESP ...
  • Run diskutil list in Terminal
  • Look for the Identifier of the disk whose ESP you want to mount
    • It will have a value like disk0 or disk8 etc
  • Run sudo mkdir /Volumes/EFI && sudo mount -t msdos /dev/disk#s1 /Volumes/EFI in Terminal
    • Change disk# in the command to match the disk id
    • Remember to keep s1 at the end of the portion
You will now have an EFI volume showing in Finder that you can navigate.
You should be able to right click and eject it when you are done.


By mounting the the ESP and deleting the OpenCore related stuff.
In your case:
  • The /EFI/BOOT folder and everything in it
  • The /EFI/OC folder and everything in it
NB: Empty the trash with the ESP still mounted afterwards



Always a good idea.
Tried to mount the ESP, got this update from Terminal

Last login: Tue Feb 14 11:00:25 on ttys000
paulrichards@Mac-mini ~ % diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *251.0 GB disk0
1: EFI ⁨EFI⁩ 209.7 MB disk0s1
2: Apple_APFS ⁨Container disk2⁩ 250.7 GB disk0s2

/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI ⁨EFI⁩ 209.7 MB disk1s1
2: Apple_HFS ⁨Internal 1TB HD⁩ 999.9 GB disk1s2

/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +250.7 GB disk2
Physical Store disk0s2
1: APFS Volume ⁨MacBigSur - Data⁩ 69.4 GB disk2s1
2: APFS Volume ⁨Preboot⁩ 284.3 MB disk2s2
3: APFS Volume ⁨Recovery⁩ 620.3 MB disk2s3
4: APFS Volume ⁨VM⁩ 1.1 MB disk2s4
5: APFS Volume ⁨MacBigSur⁩ 15.3 GB disk2s5
6: APFS Snapshot ⁨com.apple.os.update-...⁩ 15.3 GB disk2s5s1

/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *480.1 GB disk3
1: EFI ⁨EFI⁩ 209.7 MB disk3s1
2: Apple_APFS ⁨Container disk4⁩ 479.9 GB disk3s2

/dev/disk4 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +479.9 GB disk4
Physical Store disk3s2
1: APFS Volume ⁨Mojave OS Int⁩ 416.2 GB disk4s1
2: APFS Volume ⁨Preboot⁩ 132.0 MB disk4s2
3: APFS Volume ⁨Recovery⁩ 2.5 GB disk4s3
4: APFS Volume ⁨VM⁩ 20.5 KB disk4s4

paulrichards@Mac-mini ~ % sudo mkdir /Volumes/EFI && sudo mount -t msdos /dev/dis3s1 /Volumes/EFI
Password:
mkdir: /Volumes/EFI: File exists
paulrichards@Mac-mini ~ % sudo mkdir /Volumes/EFI && sudo mount -t msdos /dev/disk3s1 /Volumes/EFI
mkdir: /Volumes/EFI: File exists
paulrichards@Mac-mini ~ %


But no EFI in Finder to navigate or eject ?

Ive also just noticed that its Mojave, not High Sierra

Not sure if Ive done something wrong again lol
 

Dayo

macrumors 68020
Dec 21, 2018
2,257
1,279
You don't need to quote entire posts with each reply BTW.

It doesn't particularly bode well if you are not clear on which Mac OS version you have in place but anyway, it seems you already have /Volumes/EFI mounted.

Issue diskutil unmount /Volumes/EFI and rerun the previous command.
Do not keep retrying the command.
The EFI will be mounted in Finder ... It is actually already mounted and you just need to look for it in Finder but do the unmount and remount
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.