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

[Macschrauber]

If you need to install Windows again its better to do it in Legacy / Bios mode.

RefindPlus can boot it
OpenCore can boot it too if OC chainloads Refind

make a firmware dump if you dont have it, so u can get ridd of certificates.


if thats too late I or tsialex can help removing them.

 

[H2SO4]

If you need to install Windows again its better to do it in Legacy / Bios mode.

RefindPlus can boot it
OpenCore can boot it too if OC chainloads Refind

make a firmware dump if you dont have it, so u can get ridd of certificates.


if thats too late I or tsialex can help removing them.

Who is this in reply to?

 

[Macschrauber]

Who is this in reply to?

if nothing is noted always the previous poster, so to you

 

[H2SO4]

if nothing is noted always the previous poster, so to you

Ok, great thanks.

 

[Macschrauber]

as you installed Windows on a sata disk Legacy/Bios is possible.

Uefi Windows is needed if you install to a NVME Blade.

 

[H2SO4]

as you installed Windows on a sata disk Legacy/Bios is possible.

Uefi Windows is needed if you install to a NVME Blade.

Yep, got that. Unless Windows itself is broken I'll stay as is for now as it did work fine.

 

[Macschrauber]

the problem is not if uefi windows is booting or not, the problem is that uefi windows write certificates where it shoudnt.

Those certificates might help an almost full 1st Nvram Stream to collaps.

OpenCore protects (with the right settings) nvram from getting certificates from Windows. Even booting the USB Installer writes the 1st certificate without protection.

But if things go mad, for example OpenCore Drive is missing and the Mac boots uefi Windows without OpenCore protection the certificates get into nvram.


These certificates can't get deleted, with no nvram reset or other magic. Just with Firmware reconstruction (or flashing back a firmware backup without certificates)

At least everyone should have a rom backup to write back a rom without certificates when dealing with uefi Windows.

MP5,1: BootROM thread | 144.0.0.0.0

I have already updated to 140.0.0.0.0 and originally had an EFI install of Win10 on my 2009 MacPro 5,1. After reading about possible bricking of the ROM, I wiped and completed a Legacy install of Win10. Problem is, I still have the certificates inserted from the old EFI install. Is there a...

forums.macrumors.com

How to Backup the Firmware: #9

 

[H2SO4]

the problem is not if uefi windows is booting or not, the problem is that uefi windows write certificates where it shoudnt.

Those certificates might help an almost full 1st Nvram Stream to collaps.

OpenCore protects (with the right settings) nvram from getting certificates from Windows. Even booting the USB Installer writes the 1st certificate without protection.

But if things go mad, for example OpenCore Drive is missing and the Mac boots uefi Windows without OpenCore protection the certificates get into nvram.


These certificates can't get deleted, with no nvram reset or other magic. Just with Firmware reconstruction (or flashing back a firmware backup without certificates)

At least everyone should have a rom backup to write back a rom without certificates when dealing with uefi Windows.

MP5,1: BootROM thread | 144.0.0.0.0

I have already updated to 140.0.0.0.0 and originally had an EFI install of Win10 on my 2009 MacPro 5,1. After reading about possible bricking of the ROM, I wiped and completed a Legacy install of Win10. Problem is, I still have the certificates inserted from the old EFI install. Is there a...

forums.macrumors.com

How to Backup the Firmware: #9

I assume you're still talking to me.

I've followed the guide for Opencore and read the links to the warnings and preventative measures.
They are implemented.
The Opencore drive is almost always in the Mac, I am particularly careful to remove the Windows drive before I 'mess about' with the Mac. Not necessarily to prevent the ROM problem more to prevent having to reload or fix Windows. I have my Windows set up exactly as I want it and I find it far harder to recover Windows than I do a Mac installation.
I do have the ROM backup, (on three separate drives).

 

[Dayo]

Updated to v064a

 

[Dayo]

@H2SO4 ... answering your question posted to the OpenCore thread as that issue turned out to be MyBootMgr specific.

Hullo again, so just so I' heading in the right direction I headed to 'MyTools' and ran FetchEFI. Now this places a folder called MyBootMgrOld in your /Users/Shared folder.

Refer back to the guide. The operation is explained there.

It appears then that I need to edit config.plist that resides in two locations, (/Users/Shared/MyBootMgr/EFI/OC and /Users/Shared/MyBootMgr/EFI/OC_ALT)?

When you need to manually edit your config, you edit in as many instances of OpenCore you have that you want the edit to apply to. So, yes, edit both instances.

Better still, use MyBootMgr v064a where the issue should be fixed as long as you tell it you intend to ignore all the warnings and insist on UEFI Windows.

 

[H2SO4]

@H2SO4 ... answering your question posted to the OpenCore thread as that issue turned out to be MyBootMgr specific.

When you need to manually edit your config, you edit in as many instances of OpenCore you have that you want the edit to apply to. So, yes, edit both instances.

Better still, use MyBootMgr v064a where the issue should be fixed as long as you tell it you intend to use UEFI Windows.

Thanks for coming back so quickly. I'll have a look at the upgrade route first and report back.

 

[JedNZ]

v064a works great on my cMP. Loving the great work being done!!

Incidentally, I have also applied the Security Update 2020-007 and have had no issues.

UPDATE: And I've installed macOS Big Sur (via OC_ALT), and updated it to 11.1 (via OC) with their default settings, and have Apple Watch Unlock working as well.

 

[narg999]

Updated to v064a

I tried downloading v064a but the zip seems to be corrupt?

 

[Dayo]

What were the symptoms?

 

[narg999]

"Unable to expand... (Error 2 - No such file or directory)"

 

[Dayo]

"Unable to expand... (Error 2 - No such file or directory)"

You might have been downloading while I was tinkering on the site.

Give it some time and try to download again as there is a minimum gap before it will allow you to download again.

I set the page up several years ago and don't recollect the details of the setting any longer but I think you should also be able to download again after you close and reopen your browser or if you try another browser.

 

[Macschrauber]

Same here: Data is corrupted,
downloaded with Safari and Firefox on Mojave

 

[Dayo]

Confirmed ... will fix and update here.

UPDATE:
Fixed

 

[Macschrauber]

it's fixed,
needed to make a private window to bypass "already downloaded" check.

 

[narg999]

Yup, just got it. Time to have some fun. Thanks!

 

[startergo]

@Dayo after NVRAM reset the system boots to OC not RefindPlus even though RefindPlus is first in the list and OC in the middle. I did several NVRAM resets and it defaults to OC:

 

[Dayo]

after NVRAM reset the system boots to OC not RefindPlus

As long as you don't have some other Fallback Boot Loader present in another ESP, RP will be loaded after reseting NVRAM if you setup according to Post 1 and use the recommended ESP Mode.

 

[startergo]

As long as you don't have some other Fallback Boot Loader present in another ESP, RP will be loaded after reseting NVRAM if you setup according to Post 1 and use the recommended ESP Mode.

If I enable BootProtect and delete the BOOTx64.efi of OC and Reset NVRAM (before loading OC) then it boots to RefindPlus.

 

[Dayo]

If I enable BootProtect and delete the BOOTx64.efi of OC and Reset NVRAM (before loading OC) then it boots to RefindPlus.

So as not to confuse anyone that has set things up according to this thread Post 1, all these actions listed are because a totally different and unrelated setup (apart from that OpenCore and RefindPlus are involved) is being used.

Do NOT Implement any of these with MyBootMgr.

If following Post 1 in the recommended ESP Mode, booting into RefindPlus if/when NVRAM is reset is the default action without any user intervention.

 

[startergo]

all these actions listed are because a totally different and unrelated setup (apart from that OpenCore and RefindPlus are involved)

RefindPlus/OpenCore Chainload​

That is the label of the thread. It is not MyBootMgr.
To clarify for the readers of this thread I was not using MyBootMgr, but my setup is similar to what is called USB Mode. It was just done manually.