MP 1,1-5,1 Requesting guidance to upgrade Mojave as I now have Refindplus and Opencore via *MybootMngr*

[Farravi]

Hello

After several weeks of posting the issues I was having and going back to the drawing board because of my inability to follow instructions meticulously, I managed to install Refindplus boot manager (with Opencore) via Mybootmngr, thanks to @Dayo @tsialex and @Macschrauber

I get the following folders in my bootscreen (attached 3 screenshots below)
1. Boot Opencore Default(this option loops back into recovery screen)
2. Boot Opencore Alternate via EFI (Does nothing)
3. Boot Mac OS from Macintosh HD (takes me into my native OS Mojave)

I would like to upgrade from Mojave into a stable OS (Catalina, Big Sur, Montrey), i'm open to suggestions, but more importantly how do i go about doing this?

Ideally, I would like also to install a window legacy OS but that can come later.

My signature has my current setup.

 

[hwojtek]

Get rid of this mess and install Open Core ONLY. With this setup you are introducing way too much variables into a delicate environment. Why ReFIND when you have OC? You are booting a booter with a booter to boot an OS. Doesn't really make much sense if you are looking to use Mac OS only (and perhaps Windows later, they will work with OC just fine, with an added bonus of GPT and not legacy install).

 

[Dayo]

You will obviously get a lot of opinions such as the garbage above, but it is certain that trying to get into an upgrade on the back of a setup that is obviously not working properly is a very bad idea.

If I recollect correctly, you have by now:

1. Tried the Manual Approach and failed to get it working
2. Tried Martin Lo's Approach and failed to get it working
3. Tried the OCLP Approach and failed to get it working
4. Tried the MyBootMgr Approach and essentially failed to get it working

I am at a loss at what to suggest.

If you are sticking with MyBootMgr, you should get it working first.
Have you tried updating to the current version?

Alternatively, you can delete MyBootMgr and ask the previous poster to set his suggestion up for you.

 

[Farravi]

If you are sticking with MyBootMgr, you should get it working first.
Have you tried updating to the current version?

Yes, used the current version just now.

Alternatively, you can delete MyBootMgr and ask the previous poster to set his suggestion up for you.

I'm not inclined to take that risk. Thanks.

 

[Dayo]

Okay. If that is now working, clean the labels up a bit.
Open the RefindPlus config.conf file and...

• Change iMacPro1,1 MacPro7,1 to just MacPro7,1
  • Might be iMacPro actually, check your ConfigFactory debug log for the correct one
• Remove or HiSeirra/Older to only have Installs/updates

You must have indicated that you intend to install BigSur/Monterey when running ConfigFactory which is why you have an additional instance over the two instances you had before.

Each instance is optimised for a specific function:

• Default OpenCore Instance
  • Spoofs MacPro7,1 (might be iMacPro depending on options selected in ConfigFactory)
  • For Catalina and newer only ... Cannot boot Mojave or older
  • Do not use for installations or updates
• Alternate OpenCore (OC_ALT)
  • Spoofs VMM for Installations and Updates
  • Can actually boot anything but best to only use for the stated purpose
• Legacy OpenCore (OC_LEG)
  • Spoofs iMacPro1,1
  • For Big Sur and older only ... Cannot boot Monterey
  • Do not use for installations or updates
• Direct MacOS Boot (RefindPlus)
  • Use to get into Mojave natively whenever this is needed

If you install Windows and/or Linux, these will appear as well. Legacy Windows is recommended as it does not come with baggage but RefindPlus can work with UEFI Windows and block certificates etc. If you do decide on UEFI Windows however, hide the icon in RefindPlus by selecting it and pressing the minus key and always boot it through OpenCore. You can use any of the OpenCore instances for this.

To install some other MacOS version, boot in via the "OC_ALT" instance, download the installer and run the installation. The various NVRAM issues with installations/updates do not affect this instance but it is not efficient for day to day use.

Of course all depends on whether it is working as you didn't mention.

PS: You can always toggle SIP back on. It is always going into that disabled state when booting without any SIP setting in place. It basically automatically toggles it from empty/enabled to disabled on first boot.
Need to look into tweaking that to leave it empty later.

 

[Farravi]

Okay. If that is now working, clean the labels up a bit.
Open the RefindPlus config.conf file and...

This is still very unknown territory for me so how would i go about doing that? As in go to the Boot folder and open config.conf file ?

You must have indicated that you intend to install BigSur/Monterey when running ConfigFactory which is why you have an additional instance over the two instances you had before.

Correct, my intention still is to install which ever one of BigSur/Monterey recommended for my setup.

Of course all depends on whether it is working as you didn't mention.

Selecting Boot Opencore shows me the following screen and then restarts the computer back to Refindplus bootscreen as previously

then this screen
and then it loops back to the Refindplus Boot manager screen.

Selecting OC_alt and OC_leg does not do anything other than say 'CSR - SIP Disabled' and selecting Mac OS takes me to my native Mojave OS.

I want to be able to use BigSur/Monterey as my main OS simply because I have Office 2021 which i cannot install on Mojave as it does not support it as of Dec 2021 and requires Catalina or newer.

 

[Dayo]

Selecting Boot Opencore loops back to the Refindplus Boot manager screen.
Selecting OC_alt and OC_leg does not do anything other than say 'CSR - SIP Disabled'

I wrongly assumed an absense of a feedback on failure in your previous meant it was working but should have known better. Everything I posted in response was essentially of no use.

This is still very unknown territory for me so how would i go about doing that?
my intention is to install BigSur/Monterey

Your task is to get stuff working with your Mojave setup as it is. So forget about editing the config file or MacOS updates or anything else until that is the case. This means when running ConfigFactory, you select "No" on questions about intentions to upgrade.

Only when you manage to get things up with Mojave do you go back, rerun ConfigFactory and at that point start looking at intending to upgrade. If you can't get it working with Mojave, it will never work with others and may result in bad consequences as it suggests something deeper that needs looking at.

One thing I struggle to understand is why you would even attempt to boot Mojave from an instance that clearly says it is for Catalina/Newer.

If you can't get MyBootMgr working for a Mojave only setup and given the failures over time with implementing OpenCore, then your best best is to uninstall everything and contact someone like @tsialex to take a look at your BootROM etc and advise you on what next steps to take. To be honest, I think you actually need to do this step now.

 

[Farravi]

You were right about my BootROM. It was in shambles and thanks to @tsialex we've sorted it out. I have flashed it and will try and install Opencore via MybootMngr.

 

[Farravi]

Eureka!?

 

[Farravi]

@Dayo is this what should happen ?

 

[Dayo]

Sorry. Not sure what you mean/need here

Did you not:

1. Boot the machine
2. Select an option to load an appropriate OpenCore instance in RefindPlus
3. Get the OpenCore Selection Screen when you did that
4. Select your Mojave instance in that OpenCore Screen
5. See Mojave load afterwards??

If all that happened, then yes, that is what is supposed to happen but doesn't really need me to tell you that though.

EDIT: Regardless, I looked at the attached image and yes, you got that screenshot from a MyBootMgr created OpenCore setup while booted into Mojave or earlier.

 

[Farravi]

Did you not:

1. Boot the machine
2. Select an option to load an appropriate OpenCore instance in RefindPlus
3. Get the OpenCore Selection Screen when you did that
4. Select your Mojave instance in that OpenCore Screen
5. See Mojave load afterwards??

If all that happened, then yes, that is what is supposed to happen but doesn't really need me to tell you that though.

EDIT: Regardless, I looked at the attached image and yes, you got that screenshot from a MyBootMgr created OpenCore setup while booted into Mojave or earlier.

1. Yes
2. Yes
3. Yes
4. Yes
5. Yes, I am typing this from the Opencore instance of Mojave. Copied this from 'system report' (
Boot ROM Version: 8888.9.9.9.9)

So now with the clean up you mentioned previously, how do i go about doing that?

I have two 'opencore' instances and one instance for Boot Mac OS from Mac HD this time.

 

[prefuse07]

@Dayo What's the benefit / why would someone do this over just using OpenCore?

Sorry if I am derailing the thread, but I am confused as to why you would want to layer one bootpicker through another bootpicker to boot into an OS?

Why not just setup one of the bootpickers: Refind only, MyBootMgr only, or OpenCore only?

Also, what does a layered setup like this do to the cMP's already fragile NVRAM?

 

[Dayo]

Sorry if I am derailing the thread

I'll respond on the MyBootMgr thread.

So now with the clean up you mentioned previously, how do i go about doing that?

I don't think you have the same labelling issues on a two instance setup but if you do, open the current config.conf file as you showed earlier in the screenshot with a text editor and make the changes. Then use the DeployConfig tool to deploy every thing.

If/when you go to a three or more instance setup, make the changes before deploying. On the other hand, you might be best served just leaving it alone to avoid mistakes in the config. It is just a cosmetic glitch and will be resolved in the next MyBootMgr.

 

[Farravi]

Sorry. Not sure what you mean/need here

Did you not:

1. Boot the machine
2. Select an option to load an appropriate OpenCore instance in RefindPlus
3. Get the OpenCore Selection Screen when you did that
4. Select your Mojave instance in that OpenCore Screen
5. See Mojave load afterwards??

So after rebooting / restarting a few times these are my findings :

> Boot Opencore Default - Spoofs Mojave and does this without any issues

> Boot Opencore (OC_ALT : Installs / Updates or HiSierra/Older) from EFI - loads into a white screen and nothing else

EDIT :
As i don't have much knowledge about Python and scripts, is there another way, I can install Monterey
on Opencore Default?

 

[Dayo]

Share the config file from OC_ALT

 

[Farravi]

Attached

 

[Dayo]

It looks as expected from looking on a phone but replace with the attached instead and let's see if any different.

 

[Farravi]

It looks as expected from looking on a phone but replace with the attached instead and let's see if any different.

Same outcome.

Can we move on to installing Monterey on the Opencore Default instance?

 

[Dayo]

I see. Might be missing something in the packaging.

Copy your /User/shared/MyBootMgr/EFi/OC_ALT folder to your desktop, zip it up and attach here so i can take a look later.

In the meantime, delete the actual /User/shared/MyBootMgr/EFi/OC_ALT folder, duplicate the /User/shared/MyBootMgr/EFi/OC folder and rename this as OC_ALT.

Open the new OC_ALT config file and make the following edits:

• Search for <key>Cpuid1Data</key>
  • Amend the item under this to <data>AAAAAAAAAAAAAACAAAAAAA==</data>
• Search for <key>Cpuid1Mask</key>
  • Amend the item under this to <data>AAAAAAAAAAAAAACAAAAAAA==</data>
• Search for <string>Mac-7BA5B2D9E42DDD94</string> (more than one place)
  • Amend this to <string></string>

Then deploy the setup.

 

[Dayo]

Can we move on to installing Monterey on the Opencore Default instance?

BTW, just so that you are clear, my role here is to make sure the OC instance created by ConfigFactory to enable installation is working as it should (or find a workaround) since you indicated this was not the case from your first post of this thread.

You will most likely be best placed asking for help on the installation aspect on the relevant "XYZ on Unsupported Macs" thread.

 

[Farravi]

Please find OC_Alt file zip attached.

 

[Farravi]

I see. Might be missing something in the packaging.

Copy your /User/shared/MyBootMgr/EFi/OC_ALT folder to your desktop, zip it up and attach here so i can take a look later.

Done (post above)

In the meantime, delete the actual /User/shared/MyBootMgr/EFi/OC_ALT folder, duplicate the /User/shared/MyBootMgr/EFi/OC folder and rename this as OC_ALT.

Open the new OC_ALT config file and make the following edits:

• Search for <key>Cpuid1Data</key>
  • Amend the item under this to <data>AAAAAAAAAAAAAACAAAAAAA==</data>
• Search for <key>Cpuid1Mask</key>
  • Amend the item under this to <data>AAAAAAAAAAAAAACAAAAAAA==</data>
• Search for <string>Mac-7BA5B2D9E42DDD94</string> (more than one place)
  • Amend this to <string></string>

Done

Then deploy the setup.

Using DeployConfig?

 

[Dayo]

Using DeployConfig?

Yes

 

[Farravi]

Replicated same issue for OC_ALT - White screen
I also get the following error on Refindplus Bootmanager screen.