Please go into the RefindPlus documentation provided in the Docs folder and read up on how the "banner" configuration token, which you are trying to use, should be structured.
This would be more beneficial in the long run.
P.S. Would be pleased to help on that bit if needed, but it is important to actually get into the path of getting this info. Tried to make them accessible.
You can get to it in: file:///Users/Shared/MyBootMgr/Docs/RefindPlus/refind/configfile.html
EDIT
To cut things short, you will find that it is "banner filename".
Your current filename is set as "overrides/icons/Banner.png" which is a path that does not exist. You don't have an "overrides/icons/Banner.png" file. You copied your file into "icons/Banner.png" and this is what you should use.
Please go into the RefindPlus documentation provided in the Docs folder and read up on how the "banner" configuration token, which you are trying to use, should be structured.
This would be more beneficial in the long run.
P.S. Would be pleased to help on that bit if needed, but it is important to actually get into the path of getting this info. Tried to make them accessible.
Thanks, Dayo. Sorry to be such a burden with constant questions. I'll read the documentation now and only revert if something truly doesn't make sense to me.
Going back to the issue of audio with the MP3,1 - I just wanted to clarify something with you as others in the OC thread have already confirmed that built-in HW audio is still broken with OC and OCLP. Given that revelation, I'm curious as to how you got your configuration working, if not via OC. I assume you must have patched it manually but even then, AppleHDA patching hasn't been implemented yet according to the Dortania guide on OC for legacy Macs. I'm interested to learn how you worked around it on your MP3,1 if you're willing to explain.
Thanks, Dayo. Sorry to be such a burden with constant questions. I'll read the documentation now and only revert if something truly doesn't make sense to me.
Going back to the issue of audio with the MP3,1 - I just wanted to clarify something with you as others in the OC thread have already confirmed that built-in HW audio is still broken with OC and OCLP. Given that revelation, I'm curious as to how you got your configuration working, if not via OC. I assume you must have patched it manually but even then, AppleHDA patching hasn't been implemented yet according to the Dortania guide on OC for legacy Macs. I'm interested to learn how you worked around it on your MP3,1 if you're willing to explain.
Long time ago I was trying to get AppleHDA working on my HP laptop. With Mirone's help I was able to patch it and even get the headphone speakers to work. So if anyone he could help you with that. I believe he is in the tonymacx86 and insanely Mac forums. But for Macs really the easiest thing is to replace the unsupported AppleHDA with a supported one from let's say el Capitan version for your case.
Long time ago I was trying to get AppleHDA working on my HP laptop. With Mirone's help I was able to patch it and even get the headphone speakers to work. So if anyone he could help you with that. I believe he is in the tonymacx86 and insanely Mac forums. But for Macs really the easiest thing is to replace the unsupported AppleHDA with a supported one from let's say el Capitan version for your case.
Tried that. Took AppleHDA.kext from El Cap and used KextWizard to install plus refresh E/S/L. Still didn't work. There were additional kernel dependencies that broke in Mojave with an older version of this kext. Not being very proficient with debugging, I couldn't go further.
Anyway, I've thread-jacked enough. If I have further questions, will take it to the appropriate forum.
Tried that. Took AppleHDA.kext from El Cap and used KextWizard to install plus refresh E/S/L. Still didn't work. There were additional kernel dependencies that broke in Mojave with an older version of this kext. Not being very proficient with debugging, couldn't go further.
Please go into the RefindPlus documentation provided in the Docs folder and read up on how the "banner" configuration token, which you are trying to use, should be structured.
This would be more beneficial in the long run.
P.S. Would be pleased to help on that bit if needed, but it is important to actually get into the path of getting this info. Tried to make them accessible.
You can get to it in: file:///Users/Shared/MyBootMgr/Docs/RefindPlus/refind/configfile.html
EDIT
To cut things short, you will find that it is "banner filename".
Your current filename is set as "overrides/icons/Banner.png" which is a path that does not exist. You don't have an "overrides/icons/Banner.png" file. You copied your file into "icons/Banner.png" and this is what you should use.
The first is a relative path from what is referencing it and leads to your file. This is what I had in my earlier post.
The second is an absolute path on your computer to a file that does not exist.
Thank you [mention]Dayo [/mention]for your hard work (every month when a new OC is released).
I hardly miss something on your insightful Guide on page #1. I had to find out the hard way which Mac OS X Versions that are not supported by one (or all) of your MyBootMgr tools. And since I have been reading in other threads (where you were active) I have my own opinion where the max limit is. (MP3,1 vs. MP5,1)
Please ad that section (see pic) and be honest about your technical limits. Don't let people make assumptions about what could work. Setting boundaries is a sign of strength.
And please;
1) don't hide System Requirements behind a Spoiler several levels deep. It is mandatory reading!I
2) make your section about Release Notes visible on the first level
(not everyone has time each month to search those interesting notes buried some levels deep in you awesome Guide.)
Hi Dayo, are the "Misc Optimisation and Improvements" in 067a limited to just the scripts used for ConfigFactory or has something related to OC or RP changed? I ask because I'm still on 067 with RP v0.13.1.AB.
I have been having an interesting issue with your newer versions of Refind / OC multi boot process (v066f and 067a) where if my internal Windows 10 SSD drive (Legacy boot process) is plugged in then Refind Plus just sits on the grey screen and no drive options are displayed and you cannot boot and have to Reset NVRAM. However, if I disconnect the windows drive then it works fine. Interestingly, it did work when I first updated to v066f for a while, but then stopped working coincidently after I did a Graphic Driver update in Windows. After a lot of trial and error I have reverted back to v059 of your multi-boot process, which works great and finds the Windows drive and the Mac OS drives.
Any thoughts on why this happens and how I could fix it?
I am running:
MacPro 3,1 with DosDude Mojave installation
Radeon RX 580 8gb GC
HDD macOS Mojave (DosDude)
SSD macOS Mojave (DosDude)
SSD Windows 10
If the old v059 works for you as you say, what you could do as a workaround is to copy the EFI/BOOT folder from that version into the current install so that you get the current OC version. You can set WrangleConfig up to do this.
The next version RefindPlus will have quite a few behind-the-scenes updates which might help.
Btw, please raise an issue on GitHub so this can be tracked.
This is a guide to using OpenCore and RefindPlus, to multiboot Classic MacPros (3,1 to 5,1) as well as Xserve3,1. It involves booting Mac OS from one or more OpenCore instances chain-loaded from RefindPlus and booting other OS types directly from RefindPlus.
The guide is focused on configuring a RefindPlus/OpenCore chain-loading arrangement and comes with a working configuration of RefindPlus and OpenCore that is literally "Plug and Play".
NB: This is the only post that is required reading for implementing this setup
The RefindPlus/OpenCore setup created by MyBootMgr is benign and can be implemented or removed without changing any fundamentals and can therefore be safely tested. Just make sure it is implemented on a physical disk that does not hold your main OS, or that only contains data, as this allows you to disconnect the disk if required and still boot into your OS. This is always preferable for boot loaders.
TL; DR
Start at STAGE 1 - PRE INSTALLATION under the IMPLEMENTATION section and follow the steps one after the other to implement a RefindPlus/OpenCore chain-loading arrangement.
The BootBlesser App
This is used to bless either RefindPlus or OpenCore so that they can handle boot actions
The ConfigFactory App
This uses input you provide to configure RefindPlus and OpenCore
The DeployESP App
This migrates RefindPlus and OpenCore from the staging folder to the target EFI System Partition or HFS Volume
The EnterRecovery App
This reboots your Mac into Recovery Mode for you if required
The FetchESP App
This fetches your deployed "EFI Folder" to your staging area for you to facilitate upgrading MyBootMgr
The ResetStartDisk App
This helps reset your computer to a default start disk if required
The SwitchRunMode App
This enables switching back and forth between Release Mode, optimised for day-to-day running, and Debug Mode, optimised for trouble shooting.
The TweakESP App
This is used to mount and unmount EFI System Partitions if required.
The UninstallMgr App
This is used to remove MyBootMgr and the boot utilities from your Mac.
The ValidateOC App
This is used to run some high level checks on OpenCore to help determine if it is properly activated.
The WrangleConfig Tool
This is used to apply arbitrary automated modifications to the generated setup.
MyBootMgr is made up of this guide and a set of Helper Apps to enable you setup and manage RefindPlus and OpenCore:
If you follow this guide step by step, word for word, implement recommended steps, avoid those not recommended, don't second guess it by implementing things not explicitly written, you will not have issues and will be able to easily restore your previous state if required.
MyBootMgr specific issues raised in this thread will be addressed. Other issues, such as those outlined following, should be directed to more appropriate locations.
For help on understanding the workings of Mac OS EFI Loading, compatible GPUs, installing/configuring any supported or unsupported OS, the intricacies of configuring/running RefindPlus and/or OpenCore beyond the configuration provided and such, please refer to, and seek help from, subject specific threads such as:
Documentation is provided in a Docs folder created when you install MyBootMgr ... Read it.
OpenCore's documentation is admittedly a difficult read but you need to get familiar with it if you want to fiddle with the configuration provided by MyBootMgr.
VMM Spoofing for installing/updating Mac OS discussed in the main OpenCore thrread is actually available for all supported cMP Models including cMP3,1, "unflashed" cMP4,1 and cMP5,1 on Nehalem CPUs.
All the capability available to a cMP5,1 running BootROM 144.0.0.0 on a Westmere CPU is also available on all supported cMP Models, including cMP3,1, with the correct configuration settings as provided by the ConfigFactory App.
You do not need a Westmere CPU or to flash cMP 5,1 firmware on cMP4,1 to access all of OpenCore's capabilities.
While you should upgrade your BootROM to 144.0.0.0 if running a "flashed" cMP4,1 or cMP5,1, the ConfigFactory App will detect your BootROM version and automatically configure RefindPlus and OpenCore to fill in the missing capabilities as required.
You can use the DosDude Patcher to install and maintain unsupported Mac OS and currently, you can operate DosDude installations alongside OpenCore.
However, you can overwrite your DosDude patched Mac OS installation with a vanilla version after installing RefindPlus/OpenCore. (Recommended)
The guide in the OpenCore thread also includes instructions on installing Windows.
This is for UEFI Windows which is not recommended here but is a viable option if preferred.
Installing Linux: Try a web search as difficult to get one single resource due to platform fragmentation.
The guide in the OpenCore thread includes instructions on installing Ubuntu Linux.
* Most Importantly, READ THE GUIDE.
* If you face or anticipate any issues, READ THE GUIDE AGAIN
Even if not multi booting into different OS Types, this guide can be used to easily enable OpenCore on a Classic MacPro in a way that is useful to first timers or experienced users that want to test different OpenCore Instances.
This is achieved by first booting into RefindPlus and using this to either load OpenCore (for Mac OS) or other OS Types as while OpenCore is far more powerful and can provide such multi booting along with several other features, configuring RefindPlus is a lot easier and it is a lot more difficult to break things with RefindPlus.
You can easily load any operating system from RefindPlus
You can easily enable or disable SIP from RefindPlus
You can load Legacy Windows installations in addition to UEFI Windows
UEFI Windows is now the orthodox way of installing Windows but it comes with the risk of potentially damaging your cMP as it was not designed with multi-boot cMP setups in mind.
RefindPlus and OpenCore offer protection from this issue as long as you ensure that you never ever deliberately boot, or, inadvertently get booted into Windows from outside of either utility.
Legacy Windows does not have this issue and it also does not have the issue of updates taking over your boot process (Boot Coups)
Legacy Windows implementations do not to have issues with updates consistently reportedly faced on UEFI Windows on each of the frequent updates.
You can manage multiple instances of OpenCore. For instance...
With Hardware Acceleration and Without (See HERE and HERE)
With VMM Spoofing and Without
OpenCore Release Version and Debug Version
Current OpenCore Version and Known Working Version for Recovery
Anything else that takes your fancy ... including a combination of the above
With this chain-loading arrangement, OpenCore would handle Mac OS booting and there can be multiple instances as mentioned. One path to Mac OS via RefindPlus should be maintained for recovery. You basically have all of the awesome power of OpenCore fully tamed by the simplicity of RefindPlus at your disposal.
This package includes one additional OpenCore instance in OC_ALT. You can add more instances by duplicating either of the provided OC or OC_ALT folders, renaming this folder and amending the OpenCore config file as you wish. Note however that the Helper Apps will only process the OC and OC_ALT folders.
MacPro3,1 to MacPro5,1 and Xserve3,1: This is written for MacPro3,1 to 5,1 as well as Xserve3,1. You can install on other units but these are not supported.
GPU: To get the Pre-Boot Configuration Screen AKA "Bootscreen", your GPU must fall into one of the following categories:
"Fully Compatible": GPUs that can load Mac OS and the Mac Pre-Boot Configuration Screen.
It does not matter whether the GPU uses GOP (Modern GPU) or UGA (Legacy GPU).
The capability to show the Pre-Boot Configuration Screen can be either from the factory or flashed afterwards.
GPUs flashed by MacVidCards, which are thus "Fully Compatible" on the surface, may in fact offer a poorer experience than if the GPU is left in a "Semi Compatible" state.
Examples of such flashed GPUs appear to disable AFPS drivers in the Mac's Early Boot Stage which may affect detection of some Mac OS Instances by boot loaders.
There is no need for such flashing as either one or both of RefindPlus and OpenCore can likely show Pre-Boot Configuration Screens with such otherwise "Semi Compatible" GPUs as they are.
"Semi Compatible": GPUs that can load Mac OS but not the Mac Pre-Boot Configuration Screen.
The GPU must be "GOP Capable" and GOP must be either "Usable" or "Fixable".
RefindPlus and OpenCore will both show Pre-Boot Configuration Screens when using GPUs with "Usable" GOP. This capability is avaliable on both utilities independent of the other.
"Usable" GOP in terms of Classic MacPros are actually GOP drivers that do not strictly conform to UEFI 2.x specifications.
This allows RefindPlus and OpenCore to activate them on Classic MacPros, which are actually EFI 1.x devices, without further action.
Most modern AMD GPU units come with "Usable" GOP while most modern Nvidia GPU units do not (They follow the UEFI 2.x specifications).
RefindPlus will show Pre-Boot Configuration Screens when using GPUs with "Fixable" GOP and OpenCore will also show such screens when it is chain-loaded from RefindPlus.
Modern Nvidia GPUs that are not branded "Mac Edition", as well as some variants of AMD GPUs, are fully UEFI 2.x compliant and as such, their GOP drivers need a "fix" to be activated on Classic MacPros.
RefindPlus can implement this fix on most such GPUs allowing Pre-Boot Configuration Screens on several GPUs where this was previously not available.
Every such GPU tested to date but likely there are some that cannot be fixed.
With this fix in place, Pre-Boot Configuration Screens will also be available in OpenCore when chain-loaded from RefindPlus.
You may need to upgrade to the lastest version of GOP for your GPU to enable RefindPlus apply this fix. Please refer to other online resources for details on this.
It is possible to to run RefindPlus/OpenCore without a Graphical Pre-Boot Screen with other Semi Compatible GPUs (Semi Compatible "UGA Only" units or "GOP Capable" units with "Unusable" and "Unfixable" GOP). Refer to the OTHER CONSIDERATIONS section for guidance on this.
This guide outlines things for two possible installation types, "ESP" and "HFS", which you decide based on your preferences.
ESP Type Installation
The EFI System Partition (ESP) is a hidden partition on your drive created when formatting the drive.
USB Sticks formatted as HFS+ (Mac OS Extended Journaled) also have EFI System Partitions that can be used in ESP Type installations. Note that these can be an order of magnitude slower to show the Pre-Boot Configuration Screen.
This partition is not something you create by yourself.
This package contains the TweakESP App which allows you to mount/unmount EFI System Partitions which are otherwise invisible. After mounting one, you will be able to see it in Finder.
You can only mount one at a time
HFS Type Installation (Not Recommended)
HFS Type installations refer to implementations on normal disk volumes which may be on a USB Stick or on a HD/SSD or other type of disk. This basically refers to normal folders/volumes that you can create yourself.
You cannot mount such with the TweakESP App.
Use HFS+ (Mac OS Extended Journaled) Volumes for HFS Type and not APFS.
Note that the debug version of OpenCore will not output debug logs with HFS Type implementations and that the debug version of RefindPlus will not store such logs on the HFS volumes but in the first ESP it finds.
Other Notes:
The /EFI/BOOT folder distributed is a RefindPlus folder.
As a result, the BOOTx64.efi file is a RefindPlus efi file and NOT the OpenCore efi file which has the same name.
The RefindPlus BOOTx64.efi file is modified from the upstream rEFInd release.
Try to make sure the package is not on the same physical disk as any operating system
This is because a last ditch recovery from an issue with an installed operating system is to disconnect the physical disk it is installed on but you will need to maintain access to this package.
The opposite, where you have issues with this package and need to boot into an operating system also applies.
UEFI Windows is not recommended ... Use Legacy Windows.
Both RefindPlus and OpenCore can protect your Mac from damage by UEFI Windows if configured correctly and the ConfigFactory App will configure both utilities to activate this protection.
That is, you can also boot into UEFI Windows directly from RefindPlus (v0.12.0.AN or later) without damaging your BootROM.
This protection can however fail in either of RefindPlus or OpenCore and you must ensure that you never boot into Windows, or get booted into Windows, knowingly or unknowingly, from outside RefindPlus or OpenCore if you insist on UEFI Windows.
Spare yourself problems on your Legacy Mac and stick with Legacy Windows.
You can find a guide to installing Legacy Windows on your Mac HERE
If you still wish to insist on UEFI Windows, ensure it is not installed on the disk containing your RefindPlus/OpenCore implementation.
OpenCanopy from OpenCore is not supported and is not distributed as there is no point having two graphical bootpickers.
You can theme RefindPlus by updating the images in the /EFI/BOOT/icons folder after installation.
You can set the OpenCore Text Bootpicker to only show up when specifically needed and to otherwise go directly to Mac OS. You can also set it so that it shows for a short period only before going to Mac OS.
If you do want to duplicate things and implement OpenCanopy anyway, please direct configuration or troubleshooting queries to the main OpenCore thread.
Looking to upgrade or uninstall MyBootMgr?
Refer to the OTHER CONSIDERATIONS section for instructions.
FOR INFORMATION ONLY ... NOT RECOMMENDED
Install and Use RefindPlus without OpenCore
Download rEFInd from the rEFInd Website and install, following instructions provided there
Once done, replace the rEFInd efi file with one from MyBootMgr (BOOTx64.efi).
Ensure that you rename to match.
Also replace the default rEFInd configuration file with the /Users/Shared/MyBootMgr/EFI/BOOT/config.conf file to configure the additonal options provided.
For full compatibility, copy in the icons in /Users/Shared/MyBootMgr/EFI/BOOT/icons folder to the rEFInd icons folder.
Skip the rest of this guide and refer to the rEFInd project for configuration/operation guidance.
Install and Use OpenCore without RefindPlus
Run the ConfigFactory App and answer the questions as required
Delete everything inside the /Users/Shared/MyBootMgr/EFI/BOOT folder
Get a copy of the BOOTx64.efi file from the same version of OpenCore and copy into the /Users/Shared/MyBootMgr/EFI/BOOT folder
Assume RefindPlus stands for OpenCore in the rest of instructions
Once done, please refer to the OpenCore Thread for configuration/operation guidance
Get MyBootMgr
Download and mount the MyBootMgr dmg file and run MyBootMgrSetup
Due to significant automation introduced as from v062, it appears the package is now too large to attach to this post ... You can download it HERE
This will create a /Users/Shared/MyBootMgr folder for you
If this folder is already present, it will be backed up as MyBootMgr_BAK
If a MyBootMgr_BAK folder is already present in such cases, it will be overwritten
Within this folder will be a MyTools folder containing the Helper Apps that make up MyBootMgr
SKIP THIS STEP IF ON MAC OS v10.10 (YOSEMITE) OR OLDER
Run the EnterRecovery App to boot your computer into Mac Recovery Mode.
The app will inform you if SIP is already disabled in which case you can move on to the next stage.
In the Mac Recovery Mode, run Terminal from the "Utilities" menu item and enter csrutil disable && reboot
Log in as normal once rebooted.
You should never need the EnterRecovery App on the same machine again and can use RefindPlus to enable or disable SIP once RefindPlus is installed.
Run the ConfigFactory App and provide the required responses
This will build and configure both RefindPlus and OpenCore to your specifications
The configured files will be saved in /Users/Shared/MyBootMgr/EFI
You will need to specify where you want to implement your setup when running the app
Remember to avoid using a partition on the same physical disk as your startup drive, or, preferably, any OS installation. This is important if you ever need to reset things.
Deploy RefindPlus and OpenCore
Run the DeployESP App to deploy RefindPlus and OpenCore to your EFI System Partition or HFS Volume.
The app will offer to deploy to the location you designated with the ConfigFactory App.
You can select another location if you have changed your mind in the interim but you really should rerun the ConfigFactory App and change the setting there.
If you already have an EFI folder in the EFI System Partition or HFS Volume, it will be backed up as EFI_BAK
If an EFI_BAK folder is already present in such cases, it will be overwritten
Test RefindPlus
Run the BootBlesser App, select RefindPlus and then, Soft Bless
You must be booted into Mac OS without using OpenCore to Soft Bless. That is, natively or directly through RefindPlus
Remember to select ESP Type or HFS Type to match your implementation mode. If you make a mistake and bless the wrong target or type, run the ResetStartDisk App
Reboot your machine and you should be booted into RefindPlus where you should be presented with two OpenCore Instances, your Mac installations and any other OS you have installed.
If running a Semi Compatible GPU without GOP or with "Unusable" and "Unfixable" GOP, and thus without a bootscreen, refer to the OTHER CONSIDERATIONS section for guidance on running RefindPlus under such conditions.
In the unlikely event of a failure to load, just reboot and you will be in your normal boot mode since only soft blessed and you can go back to fix things.
Test OpenCore
Boot into Mac OS using one of the OpenCore instances provided in RefindPlus and run the ValidateOC App to get output to help determine whether OpenCore is loaded properly.
If running a Semi Compatible GPU without GOP or with "Unusable" and "Unfixable" GOP, and thus without a bootscreen, refer to the OTHER CONSIDERATIONS section for guidance on running OpenCore under such conditions.
In the unlikely case of a failure to load OpenCore, just reboot and you will be in your normal boot mode since only soft blessed and you can go back to fix things
If you have somehow messed things up, shut down, disconnect the physical disk, reset nvram and select a start disk once booted
Observe and Verify Installation
Do a few reboots after soft blessing each time to make sure all is working as expected.
You may want to keep in this state for a couple of days
Finalise Installation (When satisfied everything is working as it should)
Shut down your Mac then switch the power off at the socket
Wait for 5 seconds then switch the power back on at the socket
Disconnect any drives containing any non-Mac OS operating systems if present
Wait for 15 seconds then press the power button to restart
Immediately hold the "OPT", "CMD", "P" and "R" keys down together until you hear the fourth chime.
Release the keys and RefindPlus will be loaded.
Boot into Mac OS without using OpenCore. That is, natively or directly through RefindPlus
Run the SwitchRunMode App to switch from Debug to Release Mode
Run the BootBlesser App and Firm Bless RefindPlus.
Shut down and reconnect any drives previously disconnected
Power on boot into Mac OS using an OpenCore Instance
Select your Startup Disk in System Preferences and reboot using the "restart" option
You can manually amend the configuration files produced by the ConfigFactory App if required but most typical options are already covered by the app. You can always rerun and redeploy if required.
Use the TweakESP App to mount your EFI (ESP Type Only) if you want to manually amend the configuration files. You can obviously directly edit such if in HFS Type.
IMPORTANT: Make sure the OpenCore LauncherOption config key is kept at Disabled.
This setting, to protect OpenCore against Boot Coups, where another boot process takes over the configured/expected boot setup, is not applicable in this chain-loading environment as MyBootMgr involves what would appear to an OpenCore installation with this flag set, to be a Boot Coup by RefindPlus.
If you do experience a Boot Coup against RefindPlus by Linux or UEFI Windows (Not an issue with Legacy Windows, which, like Mac OS, does not attempt Boot Coups), refer to the OTHER CONSIDERATIONS section of this guide for suggestions on reasserting control.
Use the WrangleConfig Tool to automate amendments you find yourself making on each release of MyBootMgr.
For instance, if you like to use OpenCanopy which is not supported by MyBootMgr and find yourself adding this in on every update, you can script the implementation in the WrangleConfig Tool and set the ConfigFactory App up to run this automatically.
OPTIONAL: Getting disks connected to PCIe slots to identify as internal disks
The ConfigFactory App will give you convenient options to use either Innie.kext or AHCI_3rdParty_SATA.kext to have such drives identify as internal drives. If these do not work, or you prefer a manual process, you can implement the steps below:
Click on the heading of the Subclass column so that the data is sorted by subclass
Look for SATA Controller and Mass Storage entries
Right click on each in turn and select Copy Device Path
Save each somewhere such as TextEdit.
You will have text like PciRoot(0x0)/Pci(0x1F,0x2)
Amend <key>DeviceProperties</key> (NB: The standalone top level instance and NOT the one under "ProtocolOverrides") in your installed /EFI/OC/config.plist and /EFI/OC_ALT/config.plist files as below then redeploy with the DeployESP App:
MyBootMgr will be removed on running the UninstallMgr App
On first run, the app will delete the deployed RefindPlus/OpenCore fileset, empty the trash and reboot your computer
After this reboot, running the app a second time will remove the staging folders such as /Users/Shared/MyBootMgr and contents including the UninstallMgr App itself
After this, go to System Preferences, select a default boot disk and restart from System Preferences
If you don't run the app a second time, the deployed files would have been deleted but the staging folder would remain for use later if you so wish.
If you run most of the other apps after the first run of the UninstallMgr App, the run count will be reset to zero.
I am on Mac OS "ABC" ... How do I Upgrade to, or Install, Mac OS "XYZ"?
Install MyBootMgr as outlined in this guide.
Boot into Mac OS via an OpenCore instance with VMM Spoofing active
Run the following Terminal Command to download and run the script: mkdir -p /Users/Shared/MyBootMgr/InstallMacOS && cd /Users/Shared/MyBootMgr/InstallMacOS && curl -O -L https://raw.githubusercontent.com/munki/macadmin-scripts/main/installinstallmacos.py && sudo python installinstallmacos.py
Select your desired installer to have it downloaded to your /Users/Shared/MyBootMgr/InstallMacOS folder where the script will create a dmg file contaning the installer which you can mount.
Run the installer and follow prompts
How do I boot using MyBootMgr without a Graphical Pre-Boot Screen?
In RefindPlus
The Default OpenCore Instance is always mapped to Keyboard Key '1' on start and pressing this key will load this. Similarly, the Alternate OpenCore Instance is always mapped to Keyboard Key '2'. Installed operating systems are mapped to Keyboard Keys '3,4,5 ... 8,9,0'.
If you have a USB Stick with a "Valid OS", including Mac OS Installers and DosDude1 or similar Patchers, this will come in at position '3' and displace the internal OS keys accordingly. Hence, when you need to boot into such, attach the USB Stick, restart your machine and press Keyboard Key '3'.
You may want to use Keyboard Key '3' (without USB attached) to boot into Mac OS directly from RefindPlus and access your debug log to check the keyboard mapping.
In OpenCore
Blind booting in OpenCore is trickier but your operating systems should be listed in alphabetical order mapped to Keyboard Keys from '1' if the HideAuxilliary key in the OpenCore Config file is set to Hide which is what MyBootMgr uses by default. You can infer what key to use accordingly.
Note however that if you have the ScanPolicy key in the OpenCore Config file set to 0, this alphabetical order may include one or more 'EFI' entries.
How do I update MyBootMgr?
Run Step 1 of "STAGE 1: PRE INSTALLATION" which will create a /Users/Shared/MyBootMgr folder
Run the FetchESP App to get your currently installed implementation of MyBootMgr
The app will create a /Users/Shared/MyBootMgrOld folder for you
If this folder is already present, it will be backed up as MyBootMgrOld_BAK
If a MyBootMgrOld_BAK folder is already present, it will be overwritten
Within this folder will be a subfolder containing your currently installed EFI folder
Bring in any Drivers/Kexts you have added to MyBootMgrOld outside the ConfigFactory App to /Users/Shared/MyBootMgr
Use FileMerge (Type name into Spotlight to find) to compare your MyBootMgrOld/OC/config.plist file with the newly distributed one in MyBootMgr/OC/config.plist and update the new one with key items from your old one if you have made changes outside of the ConfigFactory App.
Repeat for your OC_ALT folder.
Only if not preserving OC_ALT as a known working instance.
In such cases, overwrite the MyBootMgr/EFI/OC_ALT folder with your MyBootMgrOld/EFI/OC_ALT folder instead
Carry out equivalent for any other OC_XYZ folders you may have.
Carry out similar for your EFI/BOOT/custom.conf file if you have made manual amendments to the file
Run the DeployESP App to deploy RefindPlus and OpenCore to your designated EFI System Partition or HFS Volume and reboot.
The app only deploys the MyBootMgr/EFI/OC, MyBootMgr/EFI/OC_ALT and MyBootMgr/EFI/BOOT folders and their contents. You will need to manually deploy any additional folders you may have.
Execute a triple NVRAM Reset (Optional Beneficial Step)
Shut down your Mac, wait for 5 seconds, then press the power button to restart.
Hold the "OPT", "CMD", "P" and "R" keys down together until you hear the fourth chime.
Boot into Mac OS without using OpenCore. That is, natively or directly through RefindPlus
Run the BootBlesser App and Firm Bless RefindPlus.
Reboot into Mac OS using an OpenCore Instance
Select your Startup Disk in System Preferences and reboot using the "restart" option
When satisfied everything is working as it should, run the SwitchRunMode App to switch from Debug to Release Mode
How do I update RefindPlus?
You should only upgrade RefindPlus via MyBootMgr updates.
However, you can manually upgrade RefindPlus as follows:
Replace EFI/BOOT/BOOTx64.efi
Update EFI/BOOT/config.conf
Update EFI/BOOT/custom.conf
These steps can be automated with the WrangleConfig Tool if, for instance, MyBootMgr has stopped receiving updates
How do I update OpenCore?
You should only upgrade OpenCore via MyBootMgr updates.
However, you can manually upgrade OpenCore as follows:
Typically, you need to update the following files as a minimum with OpenCore:
EFI/BOOT/BOOTx64.efi
EFI/OC/OpenCore.efi
EFI/OC/Bootstrap/Bootstrap.efi
EFI/OC/Drivers/OpenRuntime.efi
However, as we have swapped BOOTx64.efi for a RefindPlus file, you should only update the other three.
If you experience a Boot Coup by UEFI Windows, your NVRAM is likely to have been compromised and unless remediated, your Mac will be "bricked" in short order.
Shutdown your machine, create a new thread (No point posting to this thread) and ask for help.
The RefindPlus boot screen flashes on and off a few times on boot
No idea why this happens but just wait until it settles.
Alternatively, power down using the power button, disconnect the power cable, wait for 15 Seconds, reconnect it, wait for 5 seconds, restart and immediately hold down the "Option", "Command", "P" and "R" keys until you hear the boot chime the fourth time. Release the keys and log in as normal.
Disable SIP by toggling the shield Icon in RefindPlus if required as it would have been re-enabled by this process.
I am concerned about being unable to boot into an unsupported Mac OS version if the disk containing RefindPlus/OpenCore fails or is lost
Failsafe Option 1: Ensure that you maintain a supported Mac OS Version. If the disk with RefindPlus/OpenCore fails, simply boot into this and implement RefindPlus/OpenCore on another disk
Failsafe Option 2: Implement a duplicate of your setup on another disk. If the main one fails, the other will kick in automatically if you have an ESP Type implementation.
You may want to make it look different to your main implementation so that you know that the main one has failed whenever this appears. The easiest way is to go into custom.conf and implement a distinct Title Banner.
You don't need to update this fallback setup once it is implemented.
How do I set things up for FileVault?
Activating FileVault is outside the scope of MyBootMgr. It will however configure your setup to ensure that you can boot into FileVault encrypted volumes.
Combined DriveLabel_Refind.scpt and DriveLabel_OpenCore.scpt into single DriveLabel.scpt file.
Updated OpenCore Icon in Refind.
MyBootMgr-057c:
Changed distributed config files to explicitly switch off VMM and eliminate one step in instructions
Fixed property label in distributed DefaultVolume.scpt file
MyBootMgr-057d:
Changed OpenCore ScanPolicy setting to 0 so as not to throw users without APFS off
Amended Refind config to show Legacy Windows
Added AHCI_3rdParty_SATA.kext to simplify making external SATA/PCIe drives internal on cMP3,1
Updated RadeonBoost to v1.3
MyBootMgr-057e:
Removed RadeonBoost
Fixed issue that meant the OpenCore instance in the /EFI/OC_ALT folder used the config file in the /EFI/OC folder. (I.E., both instances were the same)
MyBootMgr-058:
Updated for OpenCore v0.5.8
Updated Lilu to v1.4.4
Updated Whatevergreen to v1.3.9
Updated distributed BootBlesser App to v2.0 for compatibility with new Bootstrap efi
Breaks compatibility with OpenCore v0.5.7 and earlier
Updated distributed EFI_Util App to v1.1 for consistency with BootBlesser App
Maintains compatibility with older versions of OpenCore
Changed folder name for helper apps to myUtils to avoid confusion with OpenCore's Utilities folder
Added OpenCore's Docs folder
Changed OC_Alt folder name to OC_ALT for consistent all uppercase format in OpenCore EFI
Renamed default OpenCore instance in Refind to OpenCore as opposed to OpenCore Accel and the second OpenCore instance in Refind to OpenCore ALT as opposed to OpenCore Basic
This is to reflect that users may choose to vary installations on other parameters and not just acceleration
Added debug versions of OpenCore.efi for both OC and OC_ALT
Removed gxutil
MyBootMgr-058a:
Fixed invalid HaltLevel value
Incorrectly amended from v0.5.7 value
Added missing ResetSystem.efi file
Updated icons
MyBootMgr-059:
Updated OpenCore to v0.5.9
Fixed ConsoleAttributes key
Added CrScreenshotDxe.efi
Updated Lilu to v1.4.5
Updated Whatevergreen to v1.4.0
Updated Refind to v0.12.0
Updated config file
Updated icons
Updated banner
Optimised image sizes
MyBootMgr-059a:
Updated Refind to v0.12.0.AB
Extends bootscreen provision to cMP 5.1 Firmware (No longer limited to cMP 3,1)
Requires GPU with valid GOP
Updated BootBlesser to v1.2
v1.1 did not correctly detect volume specified in DiskLabel.scpt
Removed misc unused drivers such as OpenCanopy as the text bootpicker, or better still, no bootpicker, is preferred in OpenCore with this setup since RefindPlus already provides a graphical bootpicker.
I ran into an issue that's really more macOS related vs script related but thought I'd post here and perhaps get some assistance. I totally get why not to instal to the same drive as your boot OS, but I don't really need another drive or want to waste a bunch of space on a RF/OC drive. Thought I had the ideal solution to use a 2GB Adata SATA flash drive from a thin client. However when I went to format it HFS+, it didn't create an EFI volume, so DeployESP kept generating an error and closing. I then used Terminal and DiskUtil to create a FAT32 partition, named it EFI, and formatted the remaining space as HFS+. This allowed DeployESP to complete but it only partially booted after soft blessing and then hung. I suspect this relates to the FAT32 partition not being identified as a true EFI type partition. Did a bunch of research to force create a true EFI partition, but couldn't find a way using diskutil or by attempting to clone another drive's EFI partition using the dd command. I did locate an article explaining that macOS will format volumes 2GB and less without EFI since they aren't really large enough to contain a bootable macOS (at least that was the reason given).
Easiest thing is probably to find a larger drive and have the OS autocreate the EFI partition. But thought I'd put it out there in case anyone else has some ideas?
Did a bunch of research to force create a true EFI partition, but couldn't find a way using diskutil or by attempting to clone another drive's EFI partition using the dd command.
Thanks for the gdisk tip. That did the trick to modify the FAT32 EFI to a legit EFI partition type but unfortunately still hanging during OpenCore boot. I've run ConfigFactory multiple times moving toward more conservative settings each time. The latest build I selected all recommended values other than enabling Innie and the TB3 options as I recently installed a Titan Ridge card (BIOS flashed). Beyond that I have a flashed GTX 680 2GB graphics card and a generic PCIe to M.2 NVME card with a Sabrent Rocket Q 1TB SSD that's been booting into Mojave without issue. The cMP is a legit 5,1 with CPUs upgraded to dual X5690 with 96GB RAM. The Titan Ridge card was showing up in the PCI section of System Report but not fully functional due to lack of OpenCore mods. Short of TB3 support this was all working without issue in Mojave.
Each time I've rebuilt the config RefindPlus seems to work as it should, but after selecting the OC build I get a blank gray screen and that's it. I've waited for over an hour and nothing further happens. Hate to ask, but I have read the guide many times, been anal about following it , and still don't have a clue what's going wrong?
Bless OpenCore instead of RefindPlus with the BootBlesser App to bypass RefindPlus and load OpenCore directly.
If OpenCore works when you reboot, then RefindPlus is somehow interfering with OpenCore on your machine.
Wait for the next release of MyBootMgr due after the Easter holidays as this will include an updated version of RefindPlus that addresses some potential issues that may cause this.
If you end up with the same result when you reboot, ask for help on the main OpenCore thread.
Attach your OpenCore debug log (attach the file, don't paste directly in your post).
The logs are stored in your selected ESP.
Use the TweakESP tool to mount the ESP to get at them.
Bless OpenCore instead of RefindPlus with the BootBlesser App to bypass RefindPlus and load OpenCore directly.
If OpenCore works when you reboot, then RefindPlus is somehow interfering with OpenCore on your machine.
Wait for the next release of MyBootMgr due after the Easter holidays as this will include an updated version of RefindPlus that addresses some potential issues that may cause this.
Thanks for the response Dayo. Blessing OpenCore did the trick. When I run ValidateOC, it only reports that GPU acceleration is not enabled. I didn't enable it on my latest build wondering if it may be contributing to my issue. My Titan Ridge card shows up in the PCI and Thunderbolt sections of System Report just as it should and the Innie kext was properly applied to make my M.2 SSD appear as internal. Can't thank you enough for your hard work and ongoing support. I look forward to your post holiday update and will be glad to test on my cMP or supply my logs if that will help. Happy Easter!
![install target ESP [DATA 840].png](/data/attachments/942/942370-b0db4e6e0edd0f024a2e1b0c0f0cc324.jpg)
