macOS 11 Big Sur on Unsupported Macs Thread

[wire_]

This OpenCore Legacy Patcher is not working at all, it keeps throwing errors like "installer is damaged". You kids should go back to school and test the crap you are distributing BEFORE distributing it!! IDIOTS!

Haha!

If you study the matter a bit more you will find out about a macOS feature called Gatekeeper, and how it protects against fake programs using code signing and when this helps you and when it gets in your way.

As you rampage in to forum an an entitled jerk rather than just doing some simple homework, you can figure it out on your own. But you will find you are welcomed when you have sonething to share, even if it's just good will — or in my case hearty mirth.

Anyway Idk if OCLP is signed by an Apple Developer id. But would it be surprising if it weren't?

Apple set up gatekeeper to prevent true idiots from shooting themselves in foot, but carry on firing, if you must!

 

[khronokernel]

Anyway Idk if OCLP is signed by an Apple Developer id. But would it be surprising if it weren't?

Actually we do sign it! I get an email from Apple every commit to Github, as we sign all binaries on Github Actions:

I don't take offence from comments like c-3po's, more just entertaining watching people yell ;p

But yeah, I appreciate them redacting the comment afterwards. I'm not the only developer of OpenCore Legacy Patcher, so others may feel differently to those messages

 

[OKonnel]

Hello! I would like to ask a question. I have an iMac14,2 which is said to be fully Big Sur ready and therefore cheat the installation it's enough. At this point I said to myself: "Why not disable every additional Kext module in OpenCore EFI Build? (Lilu, WhateverGreen, etc ...)" To do first I used OpenCore Configurator. I deactivated all Kext modules (see attached image) and I see that everything works fine after restarting my 27 '' iMac (Late 2013 - i7 - Nividia GTX 980 4GB). Did I act badly? Are there any aspects that I ignore and for which the additional Kext are essential? Thank you

An additional question for any nerds who may have already addressed and solved this problem; thanks.
I add that I am making a lot of attempts with EFI, since I do not resign that "Photo Booth" works badly (it appears with a black screen and only two effects appear), while it works very very well restarting the Mac in Safe Mode. From the Log I seem to understand that in Normal mode the internal iGPU (it sees it as HD5000) don't uses the OpenCL library but Drivers and Plug-In that cause some conflict.
- If the Mac boots in safe mode, Photo Booth works very well and its Log says it only uses these Open CL libraries:

/System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/unorm8_rgba.dylib
/System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/unorm8_bgra.dylib

- If Mac starts-up in Normal mode, however, Photo Booth appears with a black screen and only two effects are visible..

/System/Library/Extensions/AppleIntelHD5000GraphicsVADriver.bundle/Contents/MacOS/AppleIntelHD5000GraphicsVADriver
/System/Library/Extensions/AppleIntelHSWVA.bundle/Contents/MacOS/AppleIntelHSWVA
/System/Library/Extensions/GeForceVADriver.bundle/Contents/MacOS/GeForceVADriver
/System/Library/Extensions/GeForceMTLDriver.bundle/Contents/Resources/internal.metallib
/System/Library/Frameworks/CoreImage.framework/Versions/A/Resources/ci_stdlib.metallib
/System/Library/Frameworks/CoreImage.framework/Versions/A/Resources/ci_filters.metallib
/System/Library/Frameworks/Security.framework/Versions/A/PlugIns/csparser.bundle/Contents/MacOS/csparser
/System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn

 

[wire_]

Ok so the yelling was about maybe something going wrong with quarantine attributes or maybe Apple's hidden malware detection is glitching — I can't recall what macOS anti malware is called but you can explore its status with Eclectic Light Co tools like Silent Knight or Lock Rattler.

Lately a Big Sur PC I'm building has been surprising me by glitching on disk image mounts and "application is broken" after an intenal SSD croaked and I had to run from a backup. The latter behavior is inconsistent but I can solve by clearing extended attributes (quarantine).

xattr -c -r Xyz.app

I'm playing with limits of over-clocking too so huge wildcard.

Keep up good work!

 

[David dongfox]

The official guide is already step by step. The 2012 mini is fully supported by OCLP; meaning you can use all the defaults and need not change any of the OCLP patcher settings.

There is however a bar to clear in terms of skills in executing some terminal commands.

Which step(s) are you having trouble with?

not understand in "building and installing" step.
how to format disk to fat32 ?
I want to do clean install so need to format drive to fat32 ? and how ?

 

[David dongfox]

Step by step - https://dortania.github.io/OpenCore-Legacy-Patcher/INSTALLER.html#downloading

Yes,i am following this but can't install it. anyway Thanks.

 

[mwidjaya]

not understand in "building and installing" step.
how to format disk to fat32 ?
I want to do clean install so need to format drive to fat32 ? and how ?

Ok, let's go over some basic things.

1. Your mini is currently running what version of macOS? Catalina? Mojave? Do you have a time machine backup?

2. You have a USB stick ready? 16GB or more? Erase and formatted the stick to macOS Extended (Journaled) and GUID?

3. Downloaded Big Sur? Maybe 11.3 or 11.3.1?

4. Created the bootable installer of Big Sur onto the USB stick?

If you don't understand these basics, I think you should stop and instead get help from a friend with more Mac knowledge...

 

[ChrizLoud]

OCLP uses OpenCore to provide the functionality I was describing. And it is the only professionally supported project to provide working configurations.

The OCLP is just a simple program to be used once to generate a fitting OpenCore and install it in your iMac. Can we now start with reading the available docs on our own?

Thank you! I moved over to OCLP. It is so simple everyone should do it. No "scary terminal job" at all. Its a "GUI" with just some options to choose from. My iMac is almost totally perfect now (except the 16-bit color bug), backlight is working perfectly and finally sound from internal speakers under Windows 10

 

[David dongfox]

Ok, let's go over some basic things.

1. Your mini is currently running what version of macOS? Catalina? Mojave? Do you have a time machine backup?

2. You have a USB stick ready? 16GB or more? Erase and formatted the stick to macOS Extended (Journaled) and GUID?

3. Downloaded Big Sur? Maybe 11.3 or 11.3.1?

4. Created the bootable installer of Big Sur onto the USB stick?

If you don't understand these basics, I think you should stop and instead get help from a friend with more Mac knowledge...

1 my mini is in Big Sur .using Patches Sur.
2,3,4 all i know.

 

[OnawaAfrica]

No idea why anyone would want to install Big Sur on unsupported machines, other than for the cool technical aspect of it. It runs terribly on my officially supported Early 2015 MBP and I ended up downgrading back to Catalina.

ahm im running Big Sur on my mid 2011 21.5" iMac and its runs very smoothly. did u install BS as update over Catalina or u made a fresh install? also wat size of ram do u have?

 

[mwidjaya]

1 my mini is in Big Sur .using Patches Sur.
2,3,4 all i know.

Ah, so you are already on Big Sur using another patcher and you want to switch to OCLP.

See my earlier post on switching to OCLP.

macOS 11 Big Sur on Unsupported Macs Thread

The 2012 MBP is fully supported by OCLP. I think it is worthwhile switching over to OCLP because of simplicity of OTA afterwards. You might think OCLP is complicated but it is straight forward in operations especially for models fully supported. When I switched to OCLP, it was not that hard: -...

forums.macrumors.com

Still not sure exactly what problems you are having...
Maybe you are unsure on installing the OCLP onto the USB stick's EFI ???

Just follow the steps in the official guide.

 

[CuchoM]

Actually we do sign it! I get an email from Apple every commit to Github, as we sign all binaries on Github Actions:
View attachment 1773785
I don't take offence from comments like c-3po's, more just entertaining watching people yell ;p

But yeah, I appreciate them redacting the comment afterwards. I'm not the only developer of OpenCore Legacy Patcher, so others may feel differently to those messages

Thank you for your job, it work's really fine and better than others. Please don't consider any offence and still continuing a great development. OCLP is a great tool to use OpenCore. MBP9,2 non-retina working fine with OCLP 01.4, BS11.4 and OC0.7.0 beta testing everything daily.

 

[Ausdauersportler]

Hello! I would like to ask a question. I have an iMac14,2 which is said to be fully Big Sur ready and therefore cheat the installation it's enough. At this point I said to myself: "Why not disable every additional Kext module in OpenCore EFI Build? (Lilu, WhateverGreen, etc ...)" To do first I used OpenCore Configurator. I deactivated all Kext modules (see attached image) and I see that everything works fine after restarting my 27 '' iMac (Late 2013 - i7 - Nividia GTX 980 4GB). Did I act badly? Are there any aspects that I ignore and for which the additional Kext are essential? Thank you

An additional question for any nerds who may have already addressed and solved this problem; thanks.
I add that I am making a lot of attempts with EFI, since I do not resign that "Photo Booth" works badly (it appears with a black screen and only two effects appear), while it works very very well restarting the Mac in Safe Mode. From the Log I seem to understand that in Normal mode the internal iGPU (it sees it as HD5000) don't uses the OpenCL library but Drivers and Plug-In that cause some conflict.
- If the Mac boots in safe mode, Photo Booth works very well and its Log says it only uses these Open CL libraries:

/System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/unorm8_rgba.dylib
/System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/unorm8_bgra.dylib

- If Mac starts-up in Normal mode, however, Photo Booth appears with a black screen and only two effects are visible..

/System/Library/Extensions/AppleIntelHD5000GraphicsVADriver.bundle/Contents/MacOS/AppleIntelHD5000GraphicsVADriver
/System/Library/Extensions/AppleIntelHSWVA.bundle/Contents/MacOS/AppleIntelHSWVA
/System/Library/Extensions/GeForceVADriver.bundle/Contents/MacOS/GeForceVADriver
/System/Library/Extensions/GeForceMTLDriver.bundle/Contents/Resources/internal.metallib
/System/Library/Frameworks/CoreImage.framework/Versions/A/Resources/ci_stdlib.metallib
/System/Library/Frameworks/CoreImage.framework/Versions/A/Resources/ci_filters.metallib
/System/Library/Frameworks/Security.framework/Versions/A/PlugIns/csparser.bundle/Contents/MacOS/csparser
/System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn

View attachment 1773789

I cannot really believe to asked this question. The most extensions names are speaking, so let`s check them out:

- Lilu/WhatEvergreen: needed for GPU patching, in your case most likely using the vit9696 to enable external display ports and avoid black screen on boot (which does no occur in every case, can only be detected if used)
- AirportBrcmFixup: likely enables continuity and handoff with your system (can only be detected if used)
- CPUFriend and DataProvider: enables correct CPU boosting on load (can only be detected if used)
- USB-Map: enables all USB ports and all functionality like charging as before on your supported macOS version Catalina (can only be detected if used)
SMC-Spoof: set a high version number of the SMC software to avoid unwanted SMC updates coming in with new Big Sur updates (Big Sur installers believes to run on iMac15,x and will try to apply updates according to this)
SidecarFixup: since you own a HD4000/HD5000 (metal capable iGPU) you can now use SideCar with an USB connected SideCar capable iPad (can only be detected if used)

In fact you turned off every security and feature enabling extension just to get Photo Booth running. Well done.

About the Photo Booth and save mode:

From the dying ATI cards in iMac11,x and 12,x we know that running the save mode disables OpenCL/OpenGL acceleration and one could use the half dead card until it breaks completely.

Your experiment shows that something in the Big Sur versions of the Kepler related extensions breaks the Photo Booth. This can be an unknown Apple bug (do we know if the same thing happens on the last supported Nvidia based machines?), but this can also be the result of an intended code change for future macOS updates and releases. NVIDIA cards will be likely dropped on the next major release?

(IMHO) One can only fix this by patching back the Catalina extensions as it is currently done with the unsupported GPU types. This would break the OTA upgrades.


About OpenCore Configurator:

While being easy to use it is known to break sometimes the validity of the config files generated. The current consensus is to use Xcode or ProperTree to edit config.plist files. In any case make backups before touching config files with this program.

About the iMac14,2 and being fully Big Sur ready:

Nobody claimed this. From the past experiences we found out that nearly everything may work on Catalina supported systems without major patching. You already can see from the list of extensions used with OC above that your system is not fully Big Sur ready.

 

[Ausdauersportler]

Hello! Apologies in advance for my english)
I studied the forum for a long time and looked for my problem through a search in the branch, but unfortunately I did not find anything, so I ask for help. I want to thank in advance all active users of this forum, for the already completed upgrade of my iMac 12.2 27"(2011) from HD6970 to GTX 880m(already a year in use and everything works well), now I'm waiting for a WX7100 card and details for updating WIFI + BT, I hope that the card with the number "C" will be working)
Now I'm trying to update my iMac to Big Sur via Opencore, but I ran into a problem in the form of an endless restart into recovery mode during installation and I have been trying to deal with it for two days

I will describe the order of my actions:

1. Made a bootable USB with Big Sur (tried different versions 11.2.1 / 11.3 / 11.3.1), formatted the drive in a GUID, as indicated in the instructions, to create an additional EFI partition.

2. Launched the Opencore app(0.1.4), created an assembly for my model and wrote it to the EFI partition of the pre-created Big Sur boot disk.

3. Restarting in the drive selection mode and choosing to boot "EFI boot opencore" (no further black screen with text followed, as shown in many videos, but the background turned black, not white), chose the Big Sur installation.

4. Installation proceeds normally until the remainder of 12 minutes before completion, then a reboot occurs and goes into OS Sierra recovery mode.
I tried resetting PRAM every time I boot, go into disk selection mode and then go to Opencore and turn on the Big Sur installation, but either a black screen with a lock sign came out, or the Sierra recovery process loaded.

I read that this is possible due to a broken disk signature, but I don't quite understand how to fix it.

Thanks in advance!

A. Try to shut down the system once completely and do not touch or start from the internal HDD holding the old Sierra installation. This should avoid the signature problem.

B. Try on 3. pressing CRTL when choosing the „EFI boot opencore“ to make it the standard boot selection on reboot automatically. This way you can watch the installation unattended. There will be only text shown during the boot phase if you choose the verbose boot mode within the OCLP app. Now you get an idea why watching videos does not replace reading docs.

C. You did not create a APFS partition to install Big Sur in advance? From your photos I cannot see which USB partitions you are planning to use to install Big Sur onto? Make sure to start the disk utilities from the Big Sur installer and prepare a APFS container to hold the installation. Name it Big Sur?!

D. Resetting the PRAM kicks out OpenCore - without you cannot install or run Big Sur.

E. Use 11.2.3 or older - it is known to install without any problems and race conditions. You can update later on when you are familiar with your system and can survive failing installations.

I manage several systems like yours and have never seen this problem before.

 

[macinfo]

Is it only me, or are others as well have the close and resize buttons missing on the top left edge
of Quick Look windows? (Big Sur 11.2.3 with OCLP 0.1.2, MacBook Pro 2008 with non-metal gpu)

Clicking where they normally should appear does work, though.
(resizing and closing behaviour of the window is as expected)

 

[Capeto]

ahm im running Big Sur on my mid 2011 21.5" iMac and its runs very smoothly. did u install BS as update over Catalina or u made a fresh install? also wat size of ram do u have?

I updated from Catalina rather than doing a clean install, and have 8GB of RAM.

Maybe a clean install would have helped, but a fresh install back to Catalina has my computer running smoothly again and I don't need any Big Sur-exclusive features so I'll just wait it out. I'll probably be updating once the new MBPs release later this year anyways.

 

[Neo_Hunt]

About the iMac14,2 and being fully Big Sur ready:

Nobody claimed this. From the past experiences we found out that nearly everything may work on Catalina supported systems without major patching. You already can see from the list of extensions used with OC above that your system is not fully Big Sur ready.

Sorry to disagree... On my iMac14,3 I also removed every kext (Even SMCSpoof for aesthetics on System Info, but would NOT recommend this particular one for security reasons regarding bricking the machine) and the iMac works flawlessly, just with no SideCar support as supposedly it would not have that anyways.

The iMac14,4 being fully officially supported and the MacBookPro11,x as well (The later for Nvidia Kepler GT 7xxM Microarchitecture) I myself also wonder why each and every one of those kexts are necessary for iMac's 14,x. Again, I have no problem using it myself and its my opinion (just an opinion) calling these iMacs "fully Big Sur ready" is not as heretical as it might seem ;ˆ) But I am also the first to admit I'm probably missing something here...

 

[khronokernel]

Sorry to disagree... On my iMac14,3 I also removed every kext (Even SMCSpoof for aesthetics on System Info, but would NOT recommend this particular one for security reasons regarding bricking the machine) and the iMac works flawlessly, just with no SideCar support as it supposedly would not have it anyways.

The iMac14,4 being fully officially supported and the MacBookPro11,x as well (The later for Nvidia Kepler GT 7xxM Microarchitecture) I myself also wonder why each and every one of those kexts are necessary for iMac's 14,x. Again, I have no problem using it myself and its my opinion (just an opinion) calling these iMacs "fully Big Sur ready" is not as heretical as it might seem ;ˆ) But I am also the first to admit I'm probably missing something here...

So we do in fact document OpenCore Legacy Patcher on our site, so anyone can easily search what properties we apply and why. But I can give a quick explainer of every kext

• Lilu.kext
  • Patching engine used to avoid any root patching, required for WhateverGreen, CPUFriend and AirportBrcmFixup
• WhateverGreen.kext
  • Kext used for patching graphical portions, macOS hardcodes display outputs, DRM and such to SMBIOS models and thus we recommend them to all users to avoid edge cases such as external monitor support as well as failing to wake display from sleep
• CPUFriend.kext + CPUFriendDataProvider.kext
  • Kext used for reinjecting power profiles. Required as since we spoof a different Mac, incorrect power profiles are applied
• USB-Map.kext
  • Kext used for defining USB ports. Since we spoof different Mac, need to ensure USB ports are still mapped correctly
• AirportBrcmFixup.kext
  • Edge case to patch Airport cards that suddenly reduce speeds even on native models. This issue is exhibited on supported models in Big Sur, we're just working around an Apple bug

Hope this clarifies, we respect kernel space resources and would not inject kexts unless they're used to fix issues or add functionality.

 

[kakumakaku]

A. Try to shut down the system once completely and do not touch or start from the internal HDD holding the old Sierra installation. This should avoid the signature problem.

B. Try on 3. pressing CRTL when choosing the „EFI boot opencore“ to make it the standard boot selection on reboot automatically. This way you can watch the installation unattended. There will be only text shown during the boot phase if you choose the verbose boot mode within the OCLP app. Now you get an idea why watching videos does not replace reading docs.

C. You did not create a APFS partition to install Big Sur in advance? From your photos I cannot see which USB partitions you are planning to use to install Big Sur onto? Make sure to start the disk utilities from the Big Sur installer and prepare a APFS container to hold the installation. Name it Big Sur?!

D. Resetting the PRAM kicks out OpenCore - without you cannot install or run Big Sur.

E. Use 11.2.3 or older - it is known to install without any problems and race conditions. You can update later on when you are familiar with your system and can survive failing installations.

I manage several systems like yours and have never seen this problem before.

Thanks for the answer!
I am using 11.2.1.
When installing, I cannot select a disk in APFS format, the installer requires Mac OS Extended. The disk is fully APFS formatted and has no other volumes. When loading, I held down CTRL as indicated in the OpenCore instruction. I found information in old messages that in such cases it is necessary to edit the OpenCore installer, but as far as I understand this assembly is automated and does not require such fixes.

 

[Ausdauersportler]

Sorry to disagree... On my iMac14,3 I also removed every kext (Even SMCSpoof for aesthetics on System Info, but would NOT recommend this particular one for security reasons regarding bricking the machine) and the iMac works flawlessly, just with no SideCar support as supposedly it would not have that anyways.

The iMac14,4 being fully officially supported and the MacBookPro11,x as well (The later for Nvidia Kepler GT 7xxM Microarchitecture) I myself also wonder why each and every one of those kexts are necessary for iMac's 14,x. Again, I have no problem using it myself and its my opinion (just an opinion) calling these iMacs "fully Big Sur ready" is not as heretical as it might seem ;ˆ) But I am also the first to admit I'm probably missing something here...

As I wrote before, you can detect issues only if you use the hardware. Go to the Github page, look at the issues tab, deselect the filter and search through the list of more than 200 issues raised. You will find at least one from an iMac14,x user.

Just because you cannot see a problem it does not mean there is no. Logic and mathematical proofs work slightly different: One counter example can negate an assumption. But a single positive example proofs nothing. I would call your post ego emperical studies using a different model which I did not mention at all.

 

[Ausdauersportler]

Thanks for the answer!
I am using 11.2.1.
When installing, I cannot select a disk in APFS format, the installer requires Mac OS Extended. The disk is fully APFS formatted and has no other volumes. When loading, I held down CTRL as indicated in the OpenCore instruction. I found information in old messages that in such cases it is necessary to edit the OpenCore installer, but as far as I understand this assembly is automated and does not require such fixes.

This should not happen at all. I have see this error message only when trying to install Catalina with light spoofing.
Please try to use the disk utility from the Big Sur installer and delete the complete SSD using APFS or try moderate spoofing.

You should always use the Big Sur disk utility to prepare Big Sur disks.

 

[Neo_Hunt]

Hope this clarifies, we respect kernel space resources and would not inject kexts unless they're used to fix issues or add functionality.

Thanks for your time! But that was somewhat clear already. Still don't explain (IMHO) why Spoofing an iMac14,x to an iMac15,1 would REQUIRE those KEXTs. As I explained earlier, I am using my iMac flawlessly, including external monitors (mDP to DP 1440p and mDP to HDMI 768p) with no injected KEXTs. I don't know half of what you guys do, so I can't say why it is working in my case without the WhateverGreen kext. Regarding CPUFriend and USBMap, I'd assume it's perhaps because both SMBIOS relate to similar Haswell CPU's with similar (if not identical) USB controllers? Go figure.

And I've also tried changing the Spoofing from 15,1 to 14,4. Everything worked nice but HandBreak would miss its iGPU's QuickSync option.

Just because you cannot see a problem it does not mean there is no. Logic and mathematical proofs work slightly different: One counter example can negate an assumption. But a single positive example proofs nothing. I would call your post ego emperical studies using a different model which I did not mention at all.

I was just chipping in my experience. I did not detect any of the referred issues myself using an iMac14,3, which is very similar to the iMac14,2 of the original OKonnel's post, which by themselves are very similar to an officially supported iMac14,4, not to mention the iMac15,1 used by OCLP for Spoofing. If you think this experience should not be shared, OK! Talk about ego sir! Thanks for your time replying anyhow... Signing off.

 

[kakumakaku]

This should not happen at all. I have see this error message only when trying to install Catalina with light spoofing.
Please try to use the disk utility from the Big Sur installer and delete the complete SSD using APFS or try moderate spoofing.

You should always use the Big Sur disk utility to prepare Big Sur disks.

The disc is formatted in the Big Sur installer. I tried to do it the first time. Maybe the problem is, it's HDD, not SSD? But I did the same installation on a separate SSD partition, formatted in APFS and also had no success.

 

[Ausdauersportler]

Thanks for your time! But that was somewhat clear already. Still don't explain (IMHO) why Spoofing an iMac14,x to an iMac15,1 would REQUIRE those KEXTs. As I explained earlier, I am using my iMac flawlessly, including external monitors (mDP to DP 1440p and mDP to HDMI 768p) with no injected KEXTs. I don't know half of what you guys do, so I can't say why it is working in my case without the WhateverGreen kext. Regarding CPUFriend and USBMap, I'd assume it's perhaps because both SMBIOS relate to similar Haswell CPU's with similar (if not identical) USB controllers? Go figure.

And I've also tried changing the Spoofing from 15,1 to 14,4. Everything worked nice but HandBreak would miss its iGPU's QuickSync option.


I was just chipping in my experience. I did not detect any of the referred issues myself using an iMac14,3, which is very similar to the iMac14,2 of the original OKonnel's post, which by themselves are very similar to an officially supported iMac14,4, not to mention the iMac15,1 used by OCLP for Spoofing. If you think this experience should not be shared, OK! Talk about ego sir! Thanks for your time replying anyhow... Signing off.

It is your own choice: Go back and use the micropatcher approach experiencing a fully working unsuppported system with not a single extension or patch needed or use OpenCore and need some add ons to survice the effects of spoofing. Photo Booth is not working on the micropatcher, too. The little NVIDIA gltiches reported will be the same. Updating will work until summer when Apple releases the last full installer.

I am sorry, I am just the messanger. Generations of Mac owners experienced this move into the land of unsupported systems before year by year. This OpenCore story is by far more comfortable and functional as every patcher before. Just an opinion, too. On the iMac 2009-2011 GPU thread we had somethig like a party as we discovered to have this fully working ”patcher” OCLP solution.

Just the arkward installation method to be used with other patchers is reason enough not to go back.

Since you still not accept the basics of (math) proofs I cannot really help you. The enlightenment happend centuries before. I am tired of opinions and believes when discussing about facts. Ego te absolvo from this burden. Do not discuss if you are not used to it.

 

[Neo_Hunt]

Since you still not accept the basics of (math) proofs I cannot really help you. The enlightenment happend centuries before. I am tired of opinions and believes when discussing about facts. Ego te absolvo from this burden. Do not discuss if you are not used to it.

Kind of binary this reasoning... Option 0 OR Option 1? Math as you say, maybe...?!? I am earnestly sorry to know you really don't understand that I can run my iMac flawlessly just tinkering OCLP my own way, with NO KEXTs whatsoever. And I am not the first one... People in the same GitHub you proposed did that with some luck and an unreset NVRAM. Luck in that case could be translated to "-no_compat_check".

I'd suggest you to go to Wikipedia or download MacTracker and compare the Specifications among the unsupported Late 2013 and supported Mid 2014 iMacs. It might surprise you how similar they are. This is the first time I recall Apple removing macOS compatibility from machines more powerful than supported ones, sharing EVERY and EACH peripheral. This is easily illustrated by the FACT that it's the first time a less powerful iMacXY,b remains supported while a more powerful iMacXY,a is not. Even in the case of New World vs Old World ROM Macs and XPostFacto the unsupported Macs were less powerful overall.

Thats why this time around, regardless of OPINION, running the new macOS on "unsupported" machines, at least the most recent ones such as the 14,x iMacs, might be simply a matter of patching the compatibility list. But this is a discussion for another thread already.

You write a lot about EGO, interesting... When getting tired it might be a good idea to rest a little. Cheers man!