MP 1,1-5,1 RefindPlus|OpenCore by MyBootMgr

[jaksemasch]

OK, fair enough. I'll try again. A few question though:

You mention that in Stage 1, only steps 1 & 2 are required, but 2.1 and 2.2 show not recommended. So I only unzipped your attachment as outlined in step 1 and went right on to the optional step 3.1 changing DefaultVolume.scpt to have my HD name "MacOS1012"; and did the same in 4.1.

I did not do 5 and 6 because I have no Retina display and my CPU shows fine (X5672) Quad-Core 3.2 Ghz.

Is that OK?

In step 2 (installation) I have to admit I cannot follow your numbering logic. But I guess what needs to be done is to mount the EFI partition of the disk that contains my MacOS installation. So I mount the EFI partion that already contains /EFI/Apple folder and copy your BOOT and OC folders into the EFI directory alongside the Apple folder. Then I use BootBlesser to specify that EFI volume.

I have another disk in the system which is also GPT and hence contains an EFI volume, but it's that Hybrid/MBR for Windows 7, which I leave alone. There's nothing in the EFI volume of that disk.

Is this OK?

At first I was wondering where you have the refind bootloader, but I suppose it's EFI/BOOT/BOOTx64.efi. Correct? How does the system know whether to use BOOTx64.efi or BOOTx64-DBG.efi as the bootloader? Or do I just rename -DBG for debug?

Am I missing something here?

 

[jaksemasch]

I just analyzed the script in BootBlesser:

property AppTitle : "BootBlesser"
property mountPoint : "/Volumes/EFI"
property blessError : false
property volFlagged : true
property BootLoader : ""
property userResponse : ""
property ourEFI : ""
property BlessTarget : ""
property OpenCoreEFI : "/EFI/OC/Bootstrap/Bootstrap.efi"
property RefindEFI : "/EFI/BOOT/BOOTx64.efi"
property tagVol : ""
property basePath : "/Users/Shared/myBootMgr"
property DriveLabel : basePath & "/DriveLabel.scpt"

I guess that answers some of my questions.

 

[Dayo]

You mention that in Stage 1, only steps 1 & 2 are required, but 2.1 and 2.2 show not recommended.

Note there is a 2.0, renaming the folder. 2.1 and 2.2 are additional information for those that might want to follow those unrecommended paths.

So I only unzipped your attachment as outlined in step 1 and went right on to the optional step 3.1 changing DefaultVolume.scpt to have my HD name "MacOS1012"; and did the same in 4.1.

Good

I did not do 5 and 6 because I have no Retina display and my CPU shows fine (X5672) Quad-Core 3.2 Ghz.

Is that OK?

Not OK. It says skip Point 6 if on a cMP 3,1. You are not on a cMP 3,1 so don't skip it.

In step 2 (installation) I have to admit I cannot follow your numbering logic. But I guess what needs to be done is to mount the EFI partition of the disk that contains my MacOS installation.

Not Correct.

Whether you can follow the numbering logic is not so important. What you need to do is follow the instructions which say:

STEP 1: SKIP IF INSTALLING IN USB MODE (I.E., ONLY IMPLEMENT IF USING EFI MODE)
STEP 2: SKIP IF INSTALLING IN EFI MODE (I.E., ONLY IMPLEMENT IF USING USB MODE)
Continue with Step 3 onward

Seems you want EFI Mode. So implement the items under Step 1, skip Step 2 and continue with Step 3

Mount the EFI Partition of the disk you want to install to. Note that it doesn't say anything about it being your Mac OS disk. Actually, right at the start of the guide, it says:

You can implement anywhere you want in reality but best to avoid your main disk or any with an OS installed for the outlined reason.

So I mount the EFI partion that already contains /EFI/Apple folder and copy your BOOT and OC folders into the EFI directory alongside the Apple folder. Then I use BootBlesser to specify that EFI volume.

That should be fine. You should only Soft Bless until everything is setup.

I have another disk in the system which is also GPT and hence contains an EFI volume, but it's that Hybrid/MBR for Windows 7, which I leave alone. There's nothing in the EFI volume of that disk.

Is this OK?

OK. Contents of other EFI partitions are generally not relevant

How does the system know whether to use BOOTx64.efi or BOOTx64-DBG.efi as the bootloader?

Rename the file

Am I missing something here?

Apart from the deviation with skipping something and assuming you needed to install on your Mac OS disk, seems ok.
On my part, I will change things to use the debug version by default and have users only change after finalisation.

 

[jaksemasch]

I don't want to install on USB and use the EFI partition of the internal Mac OS disk. I'm not exactly a newcomer and know how to fix things. Whether it shows the correct CPU in "About this Mac" I don't care, but it looks OK even without following Step 6. But I will do it again and change it in case there's any CPU feature the bootloader requires.

It might be interesting to find out why it did not show any boot volumes according to the refind scan default, but perhaps there is some bug. I have another 2 disks in the system that are windows dynamic volumes and perhaps that's where it fails. But as I managed to show all the volumes in the end, doing the refind config change and tboot MacOS and Windows and see the Opencore instance, I'd say it should be good to go. It also shows the rEFInd GOPFix bootloader, which I want.

The problem is only, when I replace the Apple GPU with a GTX 760 or 1080 I no longer see a pre-boot screen, until the system loads the nvida driver at OS startup. Changing the GPU doesn't change the bootloader.

 

[startergo]

I don't want to install on USB and use the EFI partition of the internal Mac OS disk. I'm not exactly a newcomer and know how to fix things. Whether it shows the correct CPU in "About this Mac" I don't care, but it looks OK even without following Step 6. But I will do it again and change it in case there's any CPU feature the bootloader requires.

It might be interesting to find out why it did not show any boot volumes according to the refind scan default, but perhaps there is some bug. I have another 2 disks in the system that are windows dynamic volumes and perhaps that's where it fails. But as I managed to show all the volumes in the end, doing the refind config change and tboot MacOS and Windows and see the Opencore instance, I'd say it should be good to go. It also shows the rEFInd GOPFix bootloader, which I want.

The problem is only, when I replace the Apple GPU with a GTX 760 or 1080 I no longer see a pre-boot screen, until the system loads the nvida driver at OS startup. Changing the GPU doesn't change the bootloader.

You need to provide the debug log, otherwise we are blind.

 

[Dayo]

I'd say it should be good to go.

I'd say you have an invalid and misconfigured setup but it's your call at the end of the day.

I no longer see a pre-boot screen, until the system loads the nvida driver at OS startup.

Best to refer queries on GPU operation details to the GPU Thread linked in Post 1.

 

[jaksemasch]

Yes,, of course I did rename "myBootMgr-060c" to "myBootMgr" in /Users/Shared.

Seems you want EFI Mode. So implement the items under Step 1, skip Step 2 and continue with Step 3

Mount the EFI Partition of the disk you want to install to. Note that it doesn't say anything about it being your Mac OS disk. Actually, right at the start of the guide, it says:

You can implement anywhere you want in reality but best to avoid your main disk or any with an OS installed for the outlined reason.

I think the obvious idea here is that people can simply remove the disk to revert back. I don't need that.

Not OK. It says skip Point 6 if on a cMP 3,1. You are not on a cMP 3,1 so don't skip it.

What does the opencore config have to do with eEFInd and the pre-boot screen?

It might be easier to understand if you would split the instructions into separate instructions on their own, showing how to install using USB or EFI, and using rEFInd with or without OpenCore. It will also help to use 1 and 1.1, and 1.1.1 when nesting steps for better reference and readability.

I was also wondering why not renaming the EFI target disk to match the name in the DefaultVolume.scp and DriveLabel.scp, rather than editing these files with the apple script editor to match a volume on the target device. I think this would be easier, to e.g. rename the volume to match your files, e.g. "HD". Currently it should work by simply renaming the OS partition to "VOLUME_LABEL".


Anyway, I will start over again and use a basic setup.

To be continued....

 

[jaksemasch]

So I mounted the EFI partition and removed any folders but /EFI/Apple, and deleted /Users/Shared/myBootMgr, to have a plain vanilla installation.

I also removed any disks but the MacOS disk and the only graphics card installed in slot 1 is the Apple ATI HD 2600 XT. That's a pretty standard setup, apart from using a GPU from a Mac Pro 2008 in a Mac Pro 2009 with patched 5.1 firmware. On power on the system boots right into 10.12, which is the specified startup disk.

My HD, btw, contains 4 GUID/GPT partitions. MacOSX 10.9, MacOS 10.12, and 2 empty. I don't use FileFault. I have set MacOS 10.12 as the default in the Startup Disk control panel.

I followed step 1, 2, and 6 of your instructions.
I changed one of the empty disks to "VOLUME_LABEL" to match your script files.
I then mounted the EFI partition and dropped the BOOT and OC, OC_ALT into the EFI alongside the existing APPLE folder.
Then opened BootBlesser, choose EFI, refdind and soft bless. It did not show an overwrite button.
Reboot.

What I see is a grey screen, showing only the black apple logo on top and the Mac Pro case at the bottom.
Nothing to select. I also let it sit for a few minutes just to be sure.

Then reset the computer, mounted the EFI partition and opened the BOOT folder.
I renamed BOOTx64.efi to BOOTx64.efi_nodebug, and
BOOTx64-DBG.efi to BOOTx64.efi.
Opened BootBlesser, selected EFI, refind and soft bless.
Reboot.

Now it works:

So why does the debug version work, but the non-debug doesn't?

 

[jaksemasch]

I also tried the opencore bootloader and it works too, albeit in text mode only,

So I then removed the Apple HD 2600 XT card and installed the GTX 1080 Gaming 8GB

Of course, no pre-boot screen, but I remember to enter Return to open the opencore bootloader, and then select 3 to start 10.12.

The refind.log shows the following, which is the extract I think is relevant:

15:274 0:025 Read Config...
15:306 0:032 Detected Overrides - Read Config...
15:377 0:070 Adjust Default Selection...
15:407 0:030 Init Screen...
15:436 0:028 Check for Graphics:
15:465 0:028 - Seek ConsoleControl
15:494 0:028 * Seek on ConsoleOutHandle ...Success
15:562 0:067 - Check ConsoleControl ...ok

15:590 0:028 - Seek UGADraw
15:619 0:028 * Seek on ConsoleOutHandle ...Unsupported
15:644 0:024 * Seek on HandleBuffer[0] ...Success
15:670 0:025 - Check UGADraw ...ok

15:699 0:028 - Seek GraphicsOutput
15:727 0:028 * Seek on ConsoleOutHandle ...Success
15:752 0:024 - Check GraphicsOutput ...NOT OK!

15:778 0:025 INFO: Provide GOP on ConsoleOutHandle ...Success

15:846 0:067 Query GraphicsOutputProtocol Modes:
15:873 0:027 Modes = 1, Framebuffer Base = 0, Framebuffer Size = 0x0
15:902 0:028 Set Screen Resolution:
15:928 0:025 - BestMode: GOP Mode[0] @ 0x0 Resolution
15:957 0:028 Screen Resolution Already Set

15:986 0:028 INFO: Implemented GraphicsOutputProtocol

16:011 0:025 INFO: Inititated Builtin Text Renderer

16:040 0:028 Setup Screen...
16:069 0:028 Prepare for Graphics Mode Switch:
16:094 0:024 - HiDPI Not Detected ...Maintain Icon Scale

16:162 0:067 INFO: Running Graphics Mode Switch

16:190 0:028 Clear Screen and Show Banner:
16:219 0:028 Refresh Screen:
16:244 0:024 - Get Banner
16:315 0:070 - Scale Banner
16:345 0:029 - Clear Screen
16:374 0:028 - Show Banner

16:402 0:028 INFO: Switched to Graphics Mode

16:427 0:024 Get Volume Icons...


So what's next?

Update:

Same issue using a GTX 760 and using HDMI output instead of DVI.

Perhaps GOP is only supposed to work with Apple firmware GPU's supporting GOP?

 

[Dayo]

So what's next?

Provide the debug log requested about 18 hours ago. Specifically...

• Mount the EFI
• Delete the existing log
• Shut computer down
• Insert the Apple GPU
• Boot computer up
• Log in as normal
• Shut computer down
• Insert one of the other GPUs
• Boot computer up
  • Click "Enter" to select OpenCore
• Log in as normal
• Mount the EFI
• Zip up the log file
• Attach zipped log file to a new post here

 

[jaksemasch]

Did you see the log in my previous post. Not good enough?

 

[jaksemasch]

OK. Here's the complete log.

Please note the following:

After I put back the Apple GPU and used BootBlesser, refind did again show only the background picture, but no opencore or volumes. However, I just reset the machine, used BootBlesser again, restart, and it sort of kicked in. It showed the boot options again. That seems a bit strange.

I then shutdown the system, put in the GTX 1080 and the system started without refind. I then used BootBlesser, restarted the system. I only got a black window. I let it sit for a while, hit Enter (opencore) and 3. However, nothing appeared on the screen. So I reset the machine again.

Using BootBlesser again, I set efi, refind, soft boot and restarted the system.At the black screen I hit Return, then 3 ,and the system started.

So that's why there are 3 boot sequences in the log file.

 

[jaksemasch]

perhaps to make it easier, I compared the logs side by side, here is the difference:

Apple GPU (HD2600)

14:469 0:025 Check for Graphics:
14:494 0:024 - Seek ConsoleControl
14:519 0:024 * Seek on ConsoleOutHandle ...Success
14:587 0:067 - Check ConsoleControl ...ok

14:610 0:023 - Seek UGADraw
14:636 0:025 * Seek on ConsoleOutHandle ...Unsupported
14:661 0:024 * Seek on HandleBuffer[0] ...Success
14:686 0:024 - Check UGADraw ...ok

14:711 0:025 - Seek GraphicsOutput
14:736 0:024 * Seek on ConsoleOutHandle ...Success
14:761 0:024 - Check GraphicsOutput ...ok

14:785 0:024 Query GraphicsOutputProtocol Modes:
14:811 0:025 Modes = 1, Framebuffer Base = 80010000, Framebuffer Size = 0x10000000
14:879 0:067 - Query GOP Mode[0] ...Success
14:903 0:023 * Resolution = 1920x1200, PixelsPerScannedLine = 1920, PixelFormat = 8bit BlueGreenRed

14:927 0:024 Set Screen Resolution:
14:952 0:024 - BestMode: GOP Mode[0] @ 1920x1200 Resolution
14:978 0:025 Screen Resolution Already Set

15:070 0:092 INFO: Inititated Builtin Text Renderer

15:094 0:023 Setup Screen...


GTX 1080

17:352 0:032 Check for Graphics:
17:386 0:033 - Seek ConsoleControl
17:419 0:032 * Seek on ConsoleOutHandle ...Success
17:486 0:066 - Check ConsoleControl ...ok

17:519 0:032 - Seek UGADraw
17:553 0:033 * Seek on ConsoleOutHandle ...Unsupported
17:586 0:032 * Seek on HandleBuffer[0] ...Success
17:620 0:033 - Check UGADraw ...ok

17:653 0:032 - Seek GraphicsOutput
17:686 0:032 * Seek on ConsoleOutHandle ...Success
17:719 0:033 - Check GraphicsOutput ...NOT OK!

17:752 0:032 INFO: Provide GOP on ConsoleOutHandle ...Success

17:785 0:032 Query GraphicsOutputProtocol Modes:
17:852 0:066 Modes = 1, Framebuffer Base = 0, Framebuffer Size = 0x0
17:886 0:033 Set Screen Resolution:
17:919 0:032 - BestMode: GOP Mode[0] @ 0x0 Resolution
17:952 0:032 Screen Resolution Already Set

17:986 0:033 INFO: Implemented GraphicsOutputProtocol

18:019 0:032 INFO: Inititated Builtin Text Renderer

18:053 0:033 Setup Screen...


As far as I can tell, the GTX 1080 does not detected a screen, hence hasn't been initialized.
From what I understand, this is what to expect with a non-Apple card. That's also why it shows up as PCIE vers. 1.1, even after software driver initializes the card.

So what role does GOP play here? Does it work-around the EFI/UEFI firmware issues?

 

[Dayo]

Please provide a debug log from OpenCore v0.6.0. Specifically...
**EDITED FOR FULL SCOPE COVERAGE**

• Mount the EFI
• Rename the distributed MyBootMgr /EFI/OC/OpenCore.efi file as REL-OpenCore.efi
• Rename the distributed MyBootMgr /EFI/OC/Bootstrap/Bootstrap.efi file as REL-Bootstrap.efi
• Rename the distributed MyBootMgr /EFI/OC/Drivers/OpenRuntime.efi file as REL-OpenRuntime.efi
• Download a copy of the OpenCore v0.6.0 debug package from GitHub
• Copy OpenCore.efi from the package and paste into your /EFI/OC folder
• Copy Bootstrap.efi from the package and paste into your /EFI/OC/Bootstrap folder
• Copy OpenRuntime.efi from the package and paste into your /EFI/OC/Drivers folder
• Shut computer down
• Insert your GTX GPU
• Boot computer up
  • Click "Enter" to select OpenCore
• Log in as normal
• Mount the EFI
• Zip up the OpenCore debug log file
• Attach zipped log file to a new post here

 

[jaksemasch]

I noticed there is a UEFI GOP update from Nvidia, which applied.

NVIDIA Graphics Firmware Update Tool for DisplayPort 1.3 and 1.4 Displays

Download English (U.S.) drivers for NVIDIA hardware - , , ,

www.nvidia.com

I installed that firmware update, but same thing.

 

[jaksemasch]

Please provide a debug log from OpenCore v0.6.0. Specifically...

• Mount the EFI
• Rename the distributed MyBootMgr OpenCore.efi file as REL-OpenCore.efi
• Download a copy of the OpenCore v0.6.0 debug package from GitHub
• Copy the OpenCore.efi file from the OpenCore v0.6.0 debug package and paste into your /EFI/OC folder
• Shut computer down
• Insert your GTX GPU
• Boot computer up
  • Click "Enter" to select OpenCore
• Log in as normal
• Mount the EFI
• Zip up the OpenCore debug log file
• Attach zipped log file to a new post here

Are you sure? I did that, but where's the logfile.

Reading https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/debug.html#file-swaps it looks like there's more configuration necessary.

 

[Dayo]

It looks like there's more configuration necessary.

Sorry. You need to set the Target Key in your config to 65.
Important: Don't go above 65 on a Mac.

PS. I suppose you could also swap Bootstrap.efi and OpenRuntime.efi to get full coverage.
Don't change BOOTx64.efi obviously.

 

[jaksemasch]

Sorry for the delay. Patching the Nvidia firmware with the UEFI / GOP update as mentioned required to reinstall the Nvidia web driver. So I had to swap cards back in and out again, etc, and started from scratch again. I'm getting very tired swapping the graphics cards around.

I'm able to boot pressing Return/3 on a black screen with the normal opencore boot loader, but with the debug version the screen remains dark. It did however create a log file as below:

Here's the opencore log. I guess the interesting lines are:

02:493 00:051 OC: Driver OpenRuntime.efi at 0 is successfully loaded!
02:560 00:066 OC: Driver #OpenCanopy.efi at 1 is skipped!
02:609 00:049 OC: Driver #NvmExpressDxe.efi at 2 is skipped!
02:658 00:049 OC: Driver #XhciDxe.efi at 3 is skipped!
02:710 00:051 OC: Driver #CrScreenshotDxe.efi at 4 is skipped!
02:776 00:065 OC: Connecting drivers...
02:887 00:111 OC: Connecting drivers done...
02:934 00:047 OCC: GOP exists on ConsoleOutHandle and has 0 modes
02:992 00:057 OCC: Looking for GOP replacement due to invalid mode count
03:042 00:050 OCC: Alternative GOP status is - Not Found
03:100 00:057 OCC: Missing compatible GOP - Not Found
03:151 00:051 OC: Requested resolution is 0x0@0 (max: 1) from Max
03:218 00:066 OCC: Requesting 0x0@0 (max: 1) resolution, curr 0, total 0
03:268 00:049 OCC: No compatible mode for 0x0@0 (max: 1) resolution
03:325 00:057 OC: Changed resolution to 0x0@0 (max: 1) from Max - Not Found
03:376 00:050 OCC: Found 1 handles with UGA draw
03:433 00:057 OCC: Found 1 handles with GOP for UGA check
03:485 00:051 OCC: Trying handle 0 - 7DDC5B98

Btw, the GTX 1080 sits in pcie slot 2. It does not fit into slot 1 without removing the backplate. Plus you can put in another card in slot 2 without covering the fans in slot 1. But slot 1 and 2 are both x16 so it shouldn't matter. I don't see any difference having it in slot 1.

So what this mean? It also doesn't work with the GTX 760 and both cards should have UEFI / GOP. The firmware patch for the 1080 at least mentions this.

 

[Dayo]

Summary is that your cards do not have valid GOP and cannot show boot screen.
Actually, the one you gave the Refind log for does have GOP but the GOP is not valid (has a 0x0 resolution).

The next version of RefindPlus (The version of Refind bundled with MyBootMgr) will include checks for such invalid GOP implementations and kick to text mode in such cases.

If you hadn't had GOP at all, you would have gotten a text screen but it currently only checks if GOP is present (didn't realise people have GPUs with such broken GOP instances) and tries to use this if found.
This results in a black screen in your case.

If the GPU models are supposed to have GOP, then please address queries on how to fix the situation to the GPU Thread linked in the guide.

Initial guess is that someone may have tampered with your VBIOS and it is likely your GPUs were being used for cryto mining before you bought them.

Goes back to this:

Your GTX has the original vbios right?

Either way, now out of scope here.
Please address further queries to the GPU Thread.

 

[jaksemasch]

Summary is that your cards do not have valid GOP and cannot show boot screen.
Actually, the one you gave the Refind log for does have GOP but the GOP is not valid (has a 0x0 resolution).

The next version of RefindPlus (The version of Refind bundled with MyBootMgr) will include checks for such invalid GOP implementations and kick to text mode in such cases.

If you hadn't had GOP at all, you would have gotten a text screen but it currently only checks if GOP is present (didn't realise people have GPUs with such broken GOP instances) and tries to use this if found.
This results in a black screen in your case.

If the GPU models are supposed to have GOP, then please address queries on how to fix the situation to the GPU Thread linked in the guide.

Initial guess is that someone may have tampered with your VBIOS and it is likely your GPUs were being used for cryto mining before you bought them.

Goes back to this:



Either way, now out of scope here.
Please address further queries to the GPU Thread.

Thanks for your time and analysis. Broken GOP or not, that what's NVIDIA ships, and yes it's the original firmware, otherwise the NVIDIA firmware patch would not have worked.

 

[startergo]

Thanks for your time and analysis. Broken GOP or not, that what's NVIDIA ships, and yes it's the original firmware, otherwise the NVIDIA firmware patch would not have worked.

Do you have Windows? What is the result of:

nvflash --version

EEPROM ID (EF,6013) : WBond W25Q40EW 1.65-1.95V 4096Kx1S, page

Sign-On Message       : GP107 PG210 SKU 0 VGA BIOS
Build GUID            : B73978D4D1844651B3B3D66DDE2C6BCE
IFR Subsystem ID      : 3842-6258
Subsystem Vendor ID   : 0x3842
Subsystem ID          : 0x6258
Version               : 86.07.42.00.50
Image Hash            : 33B32C993A0630EFFDC0FD054506C191
Product Name          : GP107 Board
Device Name(s)        : GeForce GTX 1050 Ti
Board ID              : 0xF001
Vendor ID             : 0x10DE
Device ID             : 0x1C82
Hierarchy ID          : Normal Board
Chip SKU              : 400-0
Project               : G210-0000
Build Date            : 03/21/17
Modification Date     : 07/11/17
UEFI Version          : 0x30008
UEFI Variant ID       : 0x0000000000000007 ( GP1xx )
UEFI Signer(s)        : Microsoft Corporation UEFI CA 2011
XUSB-FW Version ID    : N/A
XUSB-FW Build Time    : N/A
InfoROM Version       : G001.0000.01.04
InfoROM Backup        : Not Present
License Placeholder   : Not Present
GPU Mode              : N/A

 

[jaksemasch]

I have a flashed GTX 680 in the system now and was planning to update the Mac Pro firmware to whatever is the latest available. So I'm going to instanll 10.13 and 10.14 and update the firmware. I read that updating the firmware does not affect the ability to install an older OS version. So I 'm going to do that and then see further. I will post the nvflash output when I put the GTX 1080 back in.

 

[Amenophis]

I am a newbie about multi boot and I don’t succeed using myBootMgr.

I followed step by step tutorial up to “Installation item 4”.
To limit risk, I tried installing on a USB stick formatted HFS+, named REFIND_OC
I copied on it EFI folder from myBootMgr folder, then

With following choices
BootBlesser.app => USB => Refind => Soft Bless => Yes, I get error message “Could not find /Volumes/REFIND_OC/EFI/refind”

BootBlesser.app => USB => Refind => Soft Bless => Override=> /Volumes/REFIND_OC
I get error message “Could Not Soft Bless Refind Boot Manager Make sure all files are copied to correct locations or try again if running after a cold start”

Something is surely wrong in what I did, but I wonder where is Refind.app.

In discussion thread I read “Our patched Refind version “ or “The version of Refind bundled with MyBootMgr” but I didn’t find Refind.app within myBootMgr.
Is Refind.app to be installed before installing myBootMgr ? And where ?

A lot of questions from a newbie.

Thanks for your help.

 

[startergo]

I am a newbie about multi boot and I don’t succeed using myBootMgr.

I followed step by step tutorial up to “Installation item 4”.
To limit risk, I tried installing on a USB stick formatted HFS+, named REFIND_OC
I copied on it EFI folder from myBootMgr folder, then

With following choices
BootBlesser.app => USB => Refind => Soft Bless => Yes, I get error message “Could not find /Volumes/REFIND_OC/EFI/refind”

BootBlesser.app => USB => Refind => Soft Bless => Override=> /Volumes/REFIND_OC
I get error message “Could Not Soft Bless Refind Boot Manager Make sure all files are copied to correct locations or try again if running after a cold start”

Something is surely wrong in what I did, but I wonder where is Refind.app.

In discussion thread I read “Our patched Refind version “ or “The version of Refind bundled with MyBootMgr” but I didn’t find Refind.app within myBootMgr.
Is Refind.app to be installed before installing myBootMgr ? And where ?

A lot of questions from a newbie.

Thanks for your help.

You first need to install rEFind "Installing rEFInd Manually Using MacOS" and then replace the refind_x64.efi and/or boot.efi (depending on your method of installation) with the provided one here. There is no refind.app. @Dayo you might want to include that in the instructions for newbies.

 

[Dayo]

@Amenophis,

Looks like your issue is here:

I will amend this bit to make it clearer.

Your folder structure should be:

| /Volumes
| /Volumes/REFIND_OC
| /Volumes/REFIND_OC/EFI
| /Volumes/REFIND_OC/EFI/BOOT
| /Volumes/REFIND_OC/EFI/OC
| /Volumes/REFIND_OC/EFI/OC_ALT

I.E., you have /Users/Shared/myBootMgr/EFI/Various folders
To deploy on your REFIND_OC USB Volume, it becomes /Volumes/REFIND_OC/EFI/Various folders

“Could not find /Volumes/REFIND_OC/EFI/refind”
That “refind” should not be present

Other queries addressed below for general info only:

Is Refind.app to be installed before installing myBootMgr ? And where ?

The package is a self contained package. Do not consider anything not explicitly mentioned in the guide. If anything of such needs to be done, it would have been stated.

As for the "Refind App", See here (for background info only):