Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Just an update on Radeon 6x support. Final drivers are being released tomorrow......
Like I told you all weeks ago before it was annnounced apple would no longer provide update packages as standalone! Just annnounced today....I have some ways around this.....stay tuned for announcement Tuesday

Can't wait!
 
  • Like
Reactions: macinfo
After almost a week of testing I can definitively say there is no appreciable performance benefit to the OpenCore method. As much as I wanted to see a performance boost, or a reason to switch over permanently, there's no factor that makes it better than the patcher (atleast for my use case with a mbp 9,2). Here are my takeaways from testing OC:

Pros:
- Allows for a more secure system overall, assuming you need sip or FileVault enabled.
- Might have a slight benefit in some graphics workloads, and single-core benchmarking, however the differences are minimal, and possibly insignificant.
- Easy to modify, adding kexts, or other boot variables
- ***OTA Updates are received, but not stable. So its a Pro because it means future versions of the legacy patcher could be more stable, receiving delta updates, but see the cons list...

Cons:
- Time consuming. Yes, the patcher is easy to implement. But understanding how opencore works is fundamental to updating the system in the future. So if you're not willing to troubleshoot and learn how it works, stay away.
- ** OTA updates can, and most likely will break your system. Is it permanent? No. But you may have to disconnect the battery of your machine, and clear nvram/pram. BigSur seems to update in a very different way than previous OS's, so OTA updates are a NO-Go for the time being.
- Slower boot times. Yes, you can tweak settings within OC to improve this, bypassing the boot loader, and debuging. But it is absolutely slower.
- Spoofing a new board ID/SMBIOS, while allowing for updates, can add complexity to your iCloud account, and some deauthorization issues down the road if you aren't vigilant.


For now, the Micropatcher just works, it's simpler to use, and is in no way going to mess with your system firmware. I'm not trying to steer anyone away from OC, and in fact I do believe its the future for these patchers. It just needs time to be refined with future releases of BigSur. Just thought I'd give my opinion. I will continue to use opencore for testing purposes, and I want to thank everyone for their hard work extending the life of our machines
 
Last edited:
Thunderbolt Displays 27 coming to my MBP8,3. External display on Catalina/Big Sur!
From what I’ve read it should work better on Catalina (and presumably also Mojave) than on Big Sur. The support for the graphics card using the drivers on Big Sur is said to only be basic, but still that’s better than nothing.
 
  • Like
Reactions: laertemeira
So I think it working fine on Catalina is probably likely. Whether it works on Big Sur would depend on to what extent the driver provides support, but even if it works on Big Sur performance may be very slow.
 
Careful with that advice, spoofing a new system could mess with the supported Catalina install if accessed through the OpenCore menu. Not to mention the recent issues with OTA updates via OC... I've been using both OC and the Micropatcher. And the Micropatcher is a much simpler solution for a dual boot system.

You must use both systems, it is together, never use just the micropatcher or just OpenCore, one complements the other, in case of a reset in NVRAM OpenCore helps you if you don't have a pendrive nearby.
 
  • Like
Reactions: Ausdauersportler
Do you have a thunderbolt cable available? If so I would first try booting off the internal drive using target disk mode. This may require clearing the nvram/pram of the good iMac and creating a new OpenCore usb, but doing so would help troubleshoot the problem further. Then you can look at using the ROMTool from dosdude to dump the system ROM of the good iMac, and flash it to the bricked one... At least this would be my approach. If anybody else has more experience with this please chime in, I'm just throwing out some ideas
I used USB CH341A programmer with SOP8 clip to flash the EFI chip with modified EFI from clean one with my onw serial number, valid checksum and hash code. Now it backs to normal, so I can confrm that OC with spoofing can brick the EFI ROM firmware in the chip. Thanks for you idears.
 
I used USB CH341A programmer with SOP8 clip to flash the EFI chip with modified EFI from clean one with my onw serial number, valid checksum and hash code. Now it backs to normal, so I can confrm that OC with spoofing can brick the EFI ROM firmware in the chip. Thanks for you idears.
Out of curiosity:
Which iMac system you got bricked using which particular OC version?
Where did you find the clean EFI and how to get the serial, checksum and hash code back?
A write up may be helpful...
 
  • Like
Reactions: paul.zhu
but there is no method to install 11.2 without the installer?
You can use Opencore-Legacy-Patcher-0.0.7 https://github.com/dortania/Opencore-Legacy-Patcher/releases/tag/0.0.7 to make EFI and update all files .efi extension with Opencore 0.6.5 profdrluigi / OpenCorePKG Beta / Downloads — Bitbucket
Then if do a software update it works fine with no issues , in case of software update does not appear
you can use the following terminal commands (don't use any other command in root mode)

sudo -i

/System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil enroll DeveloperSeed

exit

then software update again
 
  • Like
Reactions: macinfo
If I'm not mistaken, someone has created a patched controller for a few non-Metal GPUs so that they can work in Big Sur with acceleration. Is there a list of the non-Metal GPUs currently supported by said patch and of those that may be supported in the near future. More specifically, is there a realistic possibility that the original GPU of an iMac 7,1 (with an upgraded CPU) will work in Big Sur? Dosdude1's Catalina Patcher successfully achieved acceleration for that old computer. I wonder if it will ever run Big Sur with a similar patch.
 
There are patches due for release soon for some AMD GPUs used in 2011 Macs which should provide good support for Catalina but only basic support in Big Sur.

I don't know where the iMac 7,1 would be at.
 
Out of curiosity:
Which iMac system you got bricked using which particular OC version?
Where did you find the clean EFI and how to get the serial, checksum and hash code back?
A write up may be helpful...
Mac model: iMac 27" late 2013
Opencore: Opencore-Legacy-Patcher 0.0.7 release
Issue: it was fine to install Big Sur 11.01 with intaller but bricked iMac when updating to 11.1 by OTA. The display did not show anything at all. EFI rom firmware was currupted.
Solution: Used USB CH341A programmer with SOP8 clip to flash the EFI chip with modified EFI from clean one with my own serial number, valid checksum and hash code. followed "
", and "
", and got clean EFI from ebay search "clean EFI bios firmware fle" US$8
Lesson learned: Opencore can be risky and do not use OTA at least this case. It was so painful to open iMac and expose the EFI chip.
 
Mac model: iMac 27" late 2013
Opencore: Opencore-Legacy-Patcher 0.0.7 release
Issue: it was fine to install Big Sur 11.01 with intaller but bricked iMac when updating to 11.1 by OTA. The display did not show anything at all. EFI rom firmware was currupted.
Solution: Used USB CH341A programmer with SOP8 clip to flash the EFI chip with modified EFI from clean one with my own serial number, valid checksum and hash code. followed "
", and "
", and got clean EFI from ebay search "clean EFI bios firmware fle" US$8
Lesson learned: Opencore can be risky and do not use OTA at least this case. It was so painful to open iMac and expose the EFI chip.
Did you downloaded Opencore-Legacy-Patcher 0.0.7 before 12/2020?
If it's the case, BlacklistAppleUpdate wasn't set, then firmware updates were not disabled. And you were spoofing iMac15,1 ID, isn't it?
 
Last edited:
After almost a week of testing I can definitively say there is no appreciable performance benefit to the OpenCore method. As much as I wanted to see a performance boost, or a reason to switch over permanently, there's no factor that makes it better than the patcher (atleast for my use case with a mbp 9,2). Here are my takeaways from testing OC:

Pros:
- Allows for a more secure system overall, assuming you need sip or FileVault enabled.
- Might have a slight benefit in some graphics workloads, and single-core benchmarking, however the differences are minimal, and possibly insignificant.
- Easy to modify, adding kexts, or other boot variables
- ***OTA Updates are received, but not stable. So its a Pro because it means future versions of the legacy patcher could be more stable, receiving delta updates, but see the cons list...

Cons:
- Time consuming. Yes, the patcher is easy to implement. But understanding how opencore works is fundamental to updating the system in the future. So if you're not willing to troubleshoot and learn how it works, stay away.
- ** OTA updates can, and most likely will break your system. Is it permanent? No. But you may have to disconnect the battery of your machine, and clear nvram/pram. BigSur seems to update in a very different way than previous OS's, so OTA updates are a NO-Go for the time being.
- Slower boot times. Yes, you can tweak settings within OC to improve this, bypassing the boot loader, and debuging. But it is absolutely slower.
- Spoofing a new board ID/SMBIOS, while allowing for updates, can add complexity to your iCloud account, and some deauthorization issues down the road if you aren't vigilant.


For now, the Micropatcher just works, it's simpler to use, and is in no way going to mess with your system firmware. I'm not trying to steer anyone away from OC, and in fact I do believe its the future for these patchers. It just needs time to be refined with future releases of BigSur. Just thought I'd give my opinion. I will continue to use opencore for testing purposes, and I want to thank everyone for their hard work extending the life of our machines
I vote for opencore, easy to configure, OTA updates with no VMM flag or spoofing with the correct package
 

Attachments

  • 11.2 beta.png
    11.2 beta.png
    523.3 KB · Views: 235
  • Like
Reactions: iMac-iPad
If I'm not mistaken, someone has created a patched controller for a few non-Metal GPUs so that they can work in Big Sur with acceleration. Is there a list of the non-Metal GPUs currently supported by said patch and of those that may be supported in the near future. More specifically, is there a realistic possibility that the original GPU of an iMac 7,1 (with an upgraded CPU) will work in Big Sur? Dosdude1's Catalina Patcher successfully achieved acceleration for that old computer. I wonder if it will ever run Big Sur with a similar patch.
I think you mean disabling animations (disable-animations.sh in the BarryKN Patcher). That is NOT NEARLY the same thing as graphics acceleration, it only makes it a little bit more tolerable to not have graphics acceleration. As of right now, there is no possibility of patching metal on non-metal Macs, and there likely will never be.
 
  • Like
Reactions: Ausdauersportler
I think you mean disabling animations (disable-animations.sh in the BarryKN Patcher). That is NOT NEARLY the same thing as graphics acceleration, it only makes it a little bit more tolerable to not have graphics acceleration. As of right now, there is no possibility of patching metal on non-metal Macs, and there likely will never be.
And if you're talking about 2012-2013 Macs, they have metal.
 
Hi I have a question , I have a 2012 mac mini with Big Sur 11.0 installed , it has worked great ever since install a few weeks back , the SSD originally came from a Windows machine and I used mac utilities to erase it and format it . The BS 11.0 option key boot EFI has a yellow color EFI and there is also a grey color EFI , but the problem is when I shut down computer or restart it will not boot unless I use option key and manually select the Mac HD to get it to boot then all is fine . I have tried selecting the yellow EFI but has no effect on restart .

I also have a drive with BS 11.1 and when selecting it at option key and it has a red EFI choice but it has no effect either .....is there a way to resolve this to get it to start and restart without having to use option key to manually select the Mac HD ?
When I try to boot normally it comes up with the Windows BSOD, this machine does not have Windows OS on it , this is strange since I used Mac utilities to erase it and format it
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.