Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
With OpenCore, you can run an entirely unpatched installation of Catalina on the Mac Pro 5,1. You get a boot screen with a standard graphics card, native updates through Software Update, and hardware acceleration. You also benefit from other features, such as FileVault and proper protection for running UEFI Windows. However, because the installation is unpatched, if you want to install Mojave or Catalina, you must satisfy the Metal requirement that exists for all supported Macs.
It is actually the default way ... ESC is an alternative for situations where OPT doesn't work for reasons mentioned.
On most Hacks, primary target of OC, OPT would work just fine as they don't have Apple firmware taking over
If I can give you an advise please can that B drive with whatever is on... Just sayin
I use latest 0.6 beta.
But 0.5.9 also works if all you want is just to spoof the SMBIOS for Big Sur installation.
[automerge]1594192155[/automerge]
As the others said, HWAccel still works when boot with 5,1 ident. However, you still have to spoof the board ID.
Last edited:
I got this weird 2 recovery show up in the boot screen picker. and it does only say recovery and that installer I do not know why.... It happened after the installation of the beta 2
running on opencore-version DBG-060-2020-07-07
Anyone knows how I can fix that? Thank you./
It's Hynix running at 1333 MHz and works great even without OpenCore.
[automerge]1594206048[/automerge]
Disk B is the one with your Mojave fallback. It is imperative that you have a Mojave installation present in case you are ever stuck booting natively and can't get into Catalina.
Last edited:
Hey everyone, managed to get my Mac Pro up and running and tried again, but on startup it shows a wall of text and it's stuck on "Waiting for remote debugger connection."
My steps were:
- I used Clover to mount the EFI partition
- Pasted on EFI the EFI folder provided by Startergo as suggested in this post.
- Edited the .plist file in order to activate automatic boot into Catalina turning <key>ShowPicker</key> to <false/>
- Edited the .plist file in order for About This Mac to show the correct processor like I've been told here
- Double clicked on the Bless OpenCore Automator file as shown in this video, linked on this thread iirc.
- Reboot
In what way should I edit the EFI folder for it to work? Is using Clover or the Automator file what's causing the problem?
I attached the content of my EFI folder so you can take a look. Any help super appreciated.
My steps were:
- I used Clover to mount the EFI partition
- Pasted on EFI the EFI folder provided by Startergo as suggested in this post.
- Edited the .plist file in order to activate automatic boot into Catalina turning <key>ShowPicker</key> to <false/>
- Edited the .plist file in order for About This Mac to show the correct processor like I've been told here
- Double clicked on the Bless OpenCore Automator file as shown in this video, linked on this thread iirc.
- Reboot
In what way should I edit the EFI folder for it to work? Is using Clover or the Automator file what's causing the problem?
I attached the content of my EFI folder so you can take a look. Any help super appreciated.
Last edited:
Another problem each time I am trying to sudo touch /Library/Extensions; kextcache -update-volume /
I get an error like this;
Error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"
authenticated-root disabled
csrutil disabled as well
Anyone knows how to fix it?
Thank you.
I get an error like this;
Error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"
authenticated-root disabled
csrutil disabled as well
Anyone knows how to fix it?
Thank you.
What I mean to, say sorry there was a type due autocorrection on these F machines. What I meant to say is that you always want to keep a partition ( the B ) just in case something goes wrong with Catalina, so that you can always fall back on your feet and restart all over from the B if Catalina is screwed... Got that? Keep that B drive with whatever is on.
Interesting to find this thread....
I'm assuming the answer's no, but is it possible to use OC on a T2 mac?
The end goal would be force compatibility of 10.14 on a newer machine vs being stuck with 10.15.
I'm assuming the answer's no, but is it possible to use OC on a T2 mac?
The end goal would be force compatibility of 10.14 on a newer machine vs being stuck with 10.15.
You do not need to use OC to be able to run Mojave on a T2 Chip ... You can still run Mojave on that Machine...
Thanks. This would be the 16 inch MBP. As far as I can tell, (based on searching) no one's been able to successfully install Mojave on the 16" MBP and 2019 MP. Seems people can complete the install, but on boot they get the screen that indicates it can't find or load the OS.
Reverse compatibility is non-possible with OC.
Btw, OC won't help you at all, it's the macOS version that needs to support it - Mojave public versions don't have the drivers to support MP7,1 or MBP16,1. Only Apple internal development Mojave versions supports MP7,1/MBP16,1.
Alright. Figured that's what the answer would be but you never know unless you ask... Appreciate it!
Did the T2 Chip got an upgrade?
The solution requires a Mojave Installer USB disk. First download the latest Mojave installer. You can do so from by following this App Store link.
If you are running Catalina, you can also use the new option in softwareupdate:
> softwareupdate --fetch-full-installer --full-installer-version 10.14.6
Then you can use the createinstallmedia command in the Install macOS application to build an external installer Drive on a USB drive. You probably want to add the option to add the current firmware to the USB drive as well.
> createinstallmedia --volume /Volumes/Untitled --downloadassets
This will delete the target volume data on the USB disk.
When you run the Mojave createinstallmedia tool without arguments you get the usage documentation:
$ /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia
Usage: createinstallmedia --volume <path to volume to convert>
Arguments
--volume, A path to a volume that can be unmounted and erased to create the install media.
--nointeraction, Erase the disk pointed to by volume without prompting for confirmation.
--downloadassets, Download on-demand assets that may be required for installation.
Example: createinstallmedia --volume /Volumes/Untitled
This tool must be run as root.
Oh and I forgot allow the external media to boot in the recovery T2 Chip settings
This procedure will help him on what? Public versions of Mojave didn't had MP7,1 or MBP16,1 drivers. NAVI drivers don't even exist before 10.15.1DP2. Unless you find a way to back port the drivers, you won't get it working.
Only Apple has internal development releases of Mojave that work with MP7,1/MBP16,1. These releases never leaked.
Anyone can give me some guidance how to convert a Legacy installed Windows 10 to EFI on a SSD in combination of OpenCore 0.5.9 installed on my cMP 2010?
I’ve read about the “mbr2gpt.exe” tool to have an installed legacy windows converted to EFI. I would like to know the steps to take having an installed Legacy Win10 installation on my cMP 2010. Just being cautious to damage the system of what I’ve read not paying attention to this Legacy to EFI conversion when having OC as the bootloader with bootpicker.
I also have an AMD Sapphire 7950 HD Mac Edition GPU with bootscreen and without OC installed I can run the Win10 on the SSD, but now would like to keep my Radeon Vega 64 and free up two slots as I was having both GPU’s for the “Bootscreen”.
Appreciated if any one can support me with this action. Thanks for any feedback.
I’ve read about the “mbr2gpt.exe” tool to have an installed legacy windows converted to EFI. I would like to know the steps to take having an installed Legacy Win10 installation on my cMP 2010. Just being cautious to damage the system of what I’ve read not paying attention to this Legacy to EFI conversion when having OC as the bootloader with bootpicker.
I also have an AMD Sapphire 7950 HD Mac Edition GPU with bootscreen and without OC installed I can run the Win10 on the SSD, but now would like to keep my Radeon Vega 64 and free up two slots as I was having both GPU’s for the “Bootscreen”.
Appreciated if any one can support me with this action. Thanks for any feedback.
Thanks again. Yeah, every thread I've found said the same thing... This includes people who tried the same thumb drive method... It works for a 2019 15 inch that originally shipped with Mojave but not a 2019/2020 16 inch with Catalina...