MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[Dayo]

With the driver and with ExFat dives connected, stuck before the bootpicker.

Sounds like a bug. You might want to report this on the project bugtracker: https://github.com/acidanthera/bugtracker/issues

You will most likely be asked for a debug log. You can generate one by setting the "target" key in your config file to 65 and restarting after temporarily swapping your BOOTx64.efi, OpenCore.efi, Bootstrap.efi and OpenRuntime.efi files for debug versions.

 

[paalb]

and would like to know in general if it is only cosmetic that these SSDs look external. Will it cause a issue in the future and with performance?

I asked the same. Have a look here and backwards you will find some answers to your question.

 

[g_five]

Sounds like a bug. You might want to report this on the project bugtracker: https://github.com/acidanthera/bugtracker/issues

You will most likely be asked for a debug log. You can generate one by setting the "target" key in your config file to 65 and restarting after temporarily swapping your BOOTx64.efi, OpenCore.efi, Bootstrap.efi and OpenRuntime.efi files for debug versions.

I think I found the issue.. I hadn't the BootRom 144.0.0.0.0. Now the question is how I was able to run Catalina!
Once updated the BootRom I was able to see the drives and install Win

 

[cdf]

The guide has been updated to OpenCore version 0.6.5.

 

[Dewdman42]

Updated the script to actively disable any firmware update payloads in update packages.

Thanks for that script and I'm going to use it. One quick question about applying this security update, notwithstanding though... do I need to have VMM enabled in order to manually run the security update pkg? I am assuming that this did not show up in my system preferences because I have VMM disabled for performance reasons.

2nd question, in reading through posts over the past couple weeks, I see mention about the firmware update only being a concern if we are "spoofing" something. I don't think I am spoofing, but how would I check for that to make sure I'm not? I realize that with your pkg tweaker, I shouldn't have to worry about it, but I just want to have some clarity for the future.

UPDATE: when I attempted to run the ModifiedUpdate.pkg I get the following error:

 

[Dayo]

do I need to have VMM enabled in order to manually run the security update pkg?

No. The script will disable the model checks so that it will run on any mac once the script is done

I am assuming that this did not show up in my system preferences because I have VMM disabled for performance reasons.

Not sure why it did not show up for you ... VMM does not influence what updates shows up.

I see mention about the firmware update only being a concern if we are "spoofing" something. I don't think I am spoofing, but how would I check for that to make sure I'm not?

If you are still running MyBootMgr, you are spoofing when you have GPU Acceleration switched on. If not, it is set to use your Mac Model details.

Look in the OpenCore Config file for "BoardProduct". This will have "Mac-XYZ" which is a model identifier.
Do a google search for your Model ID and if different from what is there, then it is spoofing another model in order to provide features that Apple has switched off for Classic MacPros but which magically become available once the Mac says it is another model.

MyBootMgr allows you to have GPU Acceleration and associated spoofing on one instance and a plain vanilla on the other. You can also have both with GPU Acceleration or without as you wish.

EDIT ON ERROR FOUND
I will check the script later.

You can do what it does manually:
1. Follow the steps in Post 1 of the High Sierra on Unsupported Macs Thread

 

[cdf]

I don't think I am spoofing, but how would I check for that to make sure I'm not?

Quick check: If your processor frequency is expressed with a single decimal point (for example, 3.5 instead of 3.46) in "About This Mac," then you are spoofing.

 

[startergo]

VMM does not influence what updates shows up.

Without the VMM Catalina will not present you the updates.

 

[startergo]

Thanks for that script and I'm going to use it. One quick question about applying this security update, notwithstanding though... do I need to have VMM enabled in order to manually run the security update pkg? I am assuming that this did not show up in my system preferences because I have VMM disabled for performance reasons.

2nd question, in reading through posts over the past couple weeks, I see mention about the firmware update only being a concern if we are "spoofing" something. I don't think I am spoofing, but how would I check for that to make sure I'm not? I realize that with your pkg tweaker, I shouldn't have to worry about it, but I just want to have some clarity for the future.

UPDATE: when I attempted to run the ModifiedUpdate.pkg I get the following error:

View attachment 1706779

I had similar error, but my whole partition was not bootable. At least you can boot back.

 

[Dewdman42]

So it sounds like I am spoofing because I am using GPU acceleration.. and yes About THis Mac shows 3.5 instead of 3.46, I am going to have a look at my OpenCore config file just to make sure I understand exactly the config item that would constitute spoofing, and a concern about firmware problems during an update

I did try to run Dayo's pkg tweaker script, but it didn't work (see above). I ran the script with VMM disabled and then tried to run the modified pkg with VMM enabled (before I heard back from Dayo), so I don't know if that is why the modified pkg is confused and can't find stuff to install. The error happens immediately before the computer restarts, it never restarts actually...so its kind of like the actual install components needed are not found in the pkg or something like that.

If I can't get that to work, then it sounds like the best procedure for me for updating in general would be to make sure the GPU acceleration is diabled when I enable VMM for Catalina updates...then I ought to just be able to run the security updates from system preferences without concern yea?

Dayo I realize MyBootMgr (which I did use initially yes to setup RefindPlus) may by default disable GPU acceleration for the ALT boot, but I think at some point I overwrote the OC configs using CDF's model for that...the only difference currently being that my ALT boot has VMM enabled. I can go back and also disable GPU acceleration on ALT, then I guess I should be good to go...

 

[startergo]

So it sounds like I am spoofing because I am using GPU acceleration.. and yes About THis Mac shows 3.5 instead of 3.46, I am going to have a look at my OpenCore config file just to make sure I understand exactly the config item that would constitute spoofing, and a concern about firmware problems during an update

I did try to run Dayo's pkg tweaker script, but it didn't work (see above). I ran the script with VMM disabled and then tried to run the modified pkg with VMM enabled (before I heard back from Dayo), so I don't know if that is why the modified pkg is confused and can't find stuff to install. The error happens immediately before the computer restarts, it never restarts actually...so its kind of like the actual install components needed are not found in the pkg or something like that.

If I can't get that to work, then it sounds like the best procedure for me for updating in general would be to make sure the GPU acceleration is diabled when I enable VMM for Catalina updates...then I ought to just be able to run the security updates from system preferences without concern yea?

Dayo I realize MyBootMgr (which I did use initially yes to setup RefindPlus) may by default disable GPU acceleration for the ALT boot, but I think at some point I overwrote the OC configs using CDF's model for that...the only difference currently being that my ALT boot has VMM enabled. I can go back and also disable GPU acceleration on ALT, then I guess I should be good to go...

That error is from the security update not from package managers. As I said it screwed my partition, so I had to reformat. But first I created an image of the container so later I copied it with CCC. Sounds like you can't boot either. Try another partition/drive this will not work.

 

[Dewdman42]

I was about to try to reboot, are you saying it may be screwed up now? great.

 

[Dewdman42]

How did it screw up your partition? Maybe I can un-screw it up before I reboot.

 

[Dayo]

Without the VMM Catalina will not present you the updates.

I see. I get them on Mojave without. Assumed it was the same.

 

[startergo]

How did it screw up your partition? Maybe I can un-screw it up before I reboot.

Boot with another partition and inspect both system and DATA volumes of that container. Search for the user folder in the system container. You will see what is missing. On mine eventually the whole system volume was empty but the installer could not recreate it due to the error.

 

[Dewdman42]

Follow up to previous question, I am using Mac-7BA5B2D9E42DDD94 as the model id, which is from CDF's hybridization GPU acceleration step in post#1. That corresponds to iMacPro, so definitely yes i am spoofing.

Rather then try to figure out how to hack the security update pkg, i think I feel more comfortable setting up my ALT boot without GPU acceleration. I think probably I just need to revert that hybridization step back to my true model ID, and then I should be able to update through App Store... yea? Dayo, do you think for any reason it would be wise to fully turn off GPU acceleration in the ALT boot?

Its not clear to me what @startergo is suggesting I do before I reboot though. Based on his experience its possible that when I restart, my computer won't be coming back to Catalina at all. I can boot to mojave, but aside from restoring the latest Catalina backup, which I'd rather avoid if possible..I have no idea what you're suggesting here:

Boot with another partition and inspect both system and DATA volumes of that container. Search for the user folder in the system container. You will see what is missing. On mine eventually the whole system volume was empty but the installer could not recreate it due to the error.

 

[Dayo]

Dayo, do you think for any reason it would be wise to fully turn off GPU acceleration in the ALT boot?

Its not clear to me what @startergo is suggesting I do before I reboot though. Based on his experience its possible that when I restart, my computer won't be coming back to Catalina at all. I can boot to mojave, but aside from restoring the latest Catalina backup, which I'd rather avoid if possible..I have no idea what you're suggesting here:

Not really sure why you decided to mix and match things. No real harm in it but seems you did it without actually knowing what you were looking for or getting. The point of the ConfigFactory is that you answer questions in plain English telling it what you want as opposed to grabbing a config you don't understand.

Anyway, you only need GPU acceleration for video work and for watching DRM restricted movies. You can turn it off if you don't need it. That's why it is an option as opposed to something mandated. As mentioned earlier, you can turn it off on both instances or have it on both. It is purely optional.

 

[Dewdman42]

welp... yea Catalina is F__ed now. @startergo I hope you can help me figure out how to un-f__ it. I am booted into Mojave now. Whatever the combination so Dayo's patcher and the attempt to run the security update....failed...and messed up Catalina so it won't boot at all now, just get the Cricle with the slash through it screen.

Unfortunately I don't have a CCC backup of Catalina yet, I had been holding off on setting that up because I wanted to keep my old Mojave Backup around...and just recently really installed Catalina. I do have Time Machine backups, so maybe I could use that to restore things to catalina in some way if someone has any ideas... or how I can go get rid of whatever the security updater changed or added such that i can't boot now.

 

[Dewdman42]

Not really sure why you decided to mix and match things. No real harm in it but seems you did it without actually knowing what you were looking for or getting. The point of the ConfigFactory is that you answer questions in plain English telling it what you want as opposed to grabbing a config you don't understand.

Anyway, you only need GPU acceleration for video work and for watching DRM restricted movies. You can turn it off if you don't need it. That's why it is an option as opposed to something mandated. As mentioned earlier, you can turn it off on both instances or have it on both. It is purely optional.

I didn't really mix and match anything. I used MyBootMgr initially, which led to me to learn and understand about RefindPlus. For whatever a reason, a month ago when I was doing this, I was happier with CDF's OC configuration so I just kept that...using the overall structure that you setup with MyBootMgr. My setup was (until a few minutes ago), working great so I just left it as is. Its CDF's well documented OC configuration...except that I use RefindPlus......with the ALT config having VMM enabled. Nothing tricky about it.

Except now the attempt to patch and run the security update has completely lost ability to boot catalina now... So I don't know, there is more info needed to use that script of yours.

I hope someone can help me figure out how to get my catalina back....

If the spoofing is the only thing that needs to be turned off, then I think I just need to specifically not use CDF's "hybridization" step, explained in post#1 of this thread, which using RefindPlus I can put on the ALT boot.

 

[Dayo]

So I don't know, there is more info needed to use that script of yours.

I hope someone can help me figure out how to get my catalina back....

Your issues are not down to the script ... @startergo had issues with his update without this.
He might be able to guide you.

 

[Dewdman42]

No real harm in it but seems you did it without actually knowing what you were looking for or getting. The point of the ConfigFactory is that you answer questions in plain English telling it what you want as opposed to grabbing a config you don't understand.

ps - I specifically using CDF's configuration for the exact reason that I *DO* want to understand exactly what I am configuring, I don't want to answer plain english questions and blindly install a config.plist which I have no understanding about. That is precisely why I am using CDF's OC configuration steps. And I do understand more or less what I have done, so don't make such assumptions please.

I just wanted some exact clarity about what I need to do to the config.plist so that I can run the security update without concern about the firmware update, which apparently failed anyway even after using your script, which I had hoped would be safe...but it was not safe. Hope I can restore it. Many hours went into setting up this Catalina install

 

[Dewdman42]

does anyone know what stuff the security updater installs into the Catalina system or data drives prior to restart...which it would have halfway installed before giving me the message that it couldn't do it... whatever stuff that security updater does prior to restart is what I need to back out now.

 

[Dewdman42]

Boot with another partition and inspect both system and DATA volumes of that container. Search for the user folder in the system container. You will see what is missing. On mine eventually the whole system volume was empty but the installer could not recreate it due to the error.

so first off I am looking at it from mojave and there is some weird stuff for sure. like the main Catalina Drive has an empty /Applications folder, for example, but on the "Catalina - Data" volume, there is an /Applications folder that has all my apps. Did they all get moved to the protected DATA partition as part of this security update or something? Maybe apps were always on DATA, I'm not really sure, but I didn't think so.

my home folder and all other Users data are also now on the DATA partition, and there must be some kind of link that would be enabled when booted into Catalina that would make it show up as if its on the main drive.. (shrug)

When I attempt to boot catalina, I go through the OC boot loader and when I hit ENTER on the Catalina partition, it IMMEDIATELY goes to the circle with slash symbol...there is no time spent attempting to load anything before that...which makes me think...somehow some very fundamental thing about the Catalina partition itself has been changed in some way by the half-baked security updater which broke it.

@startergo, did you ever figure this out or did you just revert back to an old backup? After getting catalina back did you ignore the security update or figure out a way to install it?

I'm very unhappy right now, but unless anyone has an idea how to back out that damage caused by apple's security updater, I will be facing hours and hours of catalina reinstall. The best I can hope is to reinstall catalina, restore whatever I have from TimeMachine(which should be most of the important stuff actually..there were a few large 3rd party things I was excluding from TM. But anyway, it might not be the end of the world, but I'd rather prefer to see if i can fix whatever the security update broke rather then resort to that...

 

[cdf]

When I attempt to boot catalina, I go through the OC boot loader and when I hit ENTER on the Catalina partition, it IMMEDIATELY goes to the circle with slash symbol...there is no time spent attempting to load anything before that...which makes me think...somehow some very fundamental thing about the Catalina partition itself has been changed in some way by the half-baked security updater which broke it.

Catalina might just be seeing your Mac as unsupported (that's what that symbol usually means). Perhaps you could try the sample config in the guide (you'll have to upgrade to OC 0.6.5 though).

 

[Dewdman42]

Thanks CDF... Its interesting this is only happening after the failed attempt to run the security updater. Not sure why that would have changed it to be this way.

I will definitely consider upgrading OC before wiping and reinstalling. If nothing else I will shortly do a diff between my config and your latest one, but is there something about OC 0.6.5 that would have been required for this security update? That you know of...