It should be possible but I wouldn’t take the risk. Also, the patcher is actually a generator for OC files put inside ESP— it doesn’t really patch.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 11 Big Sur on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
-
- Tags
- 10.16 macos unsupported
- Sort by reaction score
- Status
Thanks for that, I guess it has to be a clean drive. One last question if you do not mind, with the OpenCore Legacy Patcher can I use any Big Sur usb installer or does it have to be one with opencore on it as well? I have made an installer using an apple downloaded Big Sur installer app.
Thanks!
I understand Opencore .... but....
these documentation tells something .... the opencore-patcher result isn't conform the documentation...
by the way...i have also cMP5.1 with working Opencore 0.6.6 and Intel NUC8i7BEH2 with Opencore 0.6.6. One MBP9,2 with .... micropather working, but i will have these Macbook Pro 9,2 also with OpenCore 0.6.6 ....
i have questions to build a save config for my MacBookPro 9,2. See here ...
macOS 11 Big Sur on Unsupported Macs Thread
hello, i use OpenCore 0.6.6 on my MBP9,2 A1278. Please give me feedback to my config.plist, specialy the configuration to protect my BootRom in front of Apple firmware updates. (The config spoofes the MBP9.2 to Macbook 11,1 ....) 1. what config-entrys are relevant to protect my BootRom? 2...
forums.macrumors.com
is anybody here, who helps me with my config.plist?
I just used OCLP (option 4) to install Big Sur on an iMac14,3 today. Used the 11.1 installer and the OTA update to 11.2.1 worked perfectly afterwards. Bricking issues with the iMac14,x were resolved in version 0.0.9 (I used the current 0.0.10 main repo linked at the bottom of the OCLP github page). The instructions are very easy to follow. I made sure I was up to date on Catalina which installs the 130.0.0.0 firmware. OCLP seemed like the best bet for me since it is set it and forget it. Updates work from inside macOS which is not the case for micro patched installs.
Finally, I took the plunge and installed open core 0.6.6 on my Mac Pro. As we "speak" I am running 11.2.1 beautifully, so far. One question though: I need to activate the macros original wifi card. Could someone point me to the right kext to copy into the OC kexts folder and tell me how to add it to config.plist? Is the procedure similar for other kexts, for example RadeonBoost.kext?
Thanks!
Thanks!
Get the lates OLCP, create a config on your system for your system and compare your own with the generated configuration.
There is separate OpenCore on MacPro thread for such more generic OpenCore questions and you probably start reading the original documentation on GitHub to get used to the procedures related to OC configuration.
How to disable FileVault?
Can't disable it from system preferences.
gyazo.com
How can I disable it using terminal command?
Can't disable it from system preferences.
Gyazo Screen Video
How can I disable it using terminal command?
I can confirm that my 27" iMac (late 2013) with a 3TB Fusion drives now runs BidSur 11.2, without a single problem and MUCH faster than on Catalina. I used Option 5, PatchedSur. Now hoping to be able to update soon to 11.2.1 or 11.3 when it comes to the official release.
Where OpenCore files should be placed is only the EFI system partition of either your USB drive or system drive. What you should do before adding OC files is making a bootable drive via the createinstallmedia command.
Thanks! I managed to install OC 0.6.6 and have 11.2.1 running beautifully. I am still trying to figure out how to activate my macros wifi card, which kexts to copy into OC/kexts and how to go about them in config.plist!
The only way that OCLP is different than generating your own config is the following: 1. It automatically generates the most compatible spoofed system id. 2. It adds necessary kexts based off your hardware. 3. It changes some config settings to optimize performance on a real Mac.... All of these automatically generated features can, and should be modified by the user. Part of the opencore process itself is being able to upgrade the config release to release on your own. This is why its not at the top of the list. Because it requires a much higher time investment, along with a much larger learning curve. However it pays off in the long runYou're missing the history of how the different projects came into being!
I agree with your reading that if you've got a beefed up enough Mac that unpatched Big Sur can run on it, then pure OpenCore is the way to go. One problem with OpenCore Legacy Patcher (not with OC itself - which intentionally does not have any 'default' config) is that OCLP applies all the patches that your Mac model *would* have needed if it wasn't upgraded (and then some), but I don't know any widely available way (i.e. other than to generate, or at least significantly modify, your own config) to avoid that.
It what OCLP does about #1 that I have a problem with!
I am not talking about just faking one or the other of
/PlatformInfo/Generic/SystemProductName (which fakes both board id and board product name), or just /PlatformInfo/SMBIOS/BoardProduct (which just fakes board id). I agree that one or the other of those is 100% necessary to get updates from Apple. OCLP does the first of these, not the second (which I prefer, though both are fine) and chooses the most compatible board for you, as you say (and which I like)! All good.BUT... OCLP (also!) fakes:
/PlatformInfo/Generic/MLB, /PlatformInfo/Generic/ROM, /PlatformInfo/Generic/SystemSerialNumber and /PlatformInfo/Generic/SystemUUID.It is these additional fakes which are unnecessary, I believe, based on my own testing (which is just one machine), but also based on this extra faking not being done in OpenCoreAPFSLoader by @jackluke nor in the @cdf method, both of which are fine for updates and iCloud safety - or at least no-one has reported otherwise so far! 😏 Worse, OCLP also only partially fakes these generated serial numbers (specifically, they are not actually faked into the Data Hub, because of very tricky OC issues which are still being discussed in the OC bugtracker), and I believe (again because I tested it, on my machine, which is all I can do for now) that it is only because they are NOT faking these IDs into the Data Hub that OCLP is not creating iCloud problems for everyone!
Hi again @naylom11,
I just remembered that @TECK on 'the other thread'
is developing a project in Python with the exact goal of letting you specify your custom OC settings in a file, and then it will update from version to version of OC for you with any new settings at safe defaults, just re-applying your custom mods - so that might be of interest?
Last edited:
I have actually (today) come up against a problem that has sent me back to the micropatcher; VideoToolbox does not work for me under opencore. I have absolutely no idea why, so until I can work it out (I strongly suspect it is something I have done) the micropatcher will do. @Bmju I also don't like to fake too much, but if I cannot use all my hardware features then I can't stick with it.
This is a direct quote from BarryKN's micropatcher ReadMe:How to disable FileVault?
Can't disable it from system preferences.
Gyazo Screen Video
How can I disable it using terminal command?
Not a great option, but entirely predicted problem. Sorry!
You'd probably just want to turn on the OC graphical bootpicker once you've got everything working (again as per their instructions) - and maybe turn on the lovely 'Modern' OC bootpicker style, which I've only just discovered!
View attachment 1728567
I prefer the silent mode, like a real mac, not even showing this screen there, just putting OpenCore on EFI and disabling the OC boot time and screen
Bonjour,You'd probably just want to turn on the OC graphical bootpicker once you've got everything working (again as per their instructions) - and maybe turn on the lovely 'Modern' OC bootpicker style, which I've only just discovered!
View attachment 1728567
I also enjoy doing the same thing, however I haven't found a solution to get a more readable (or larger) font.
There is even an explanation on the OpenCore website to create your own fonts, I tried without success...
Edit: although it's not necessary at all, I don't understand why you can't see my Time Machine disk, and I've tried some options.
Edit2: If I understood well it's normal, there is no boot possible on the macOS Big Sur Time Machine.
Last edited:
Good morning!
Over the weekend I did some more tests.
MacBookAir5,1
Using OCLP 0.0.10 and creating a new config for my 2012 MacBookAir5,1 - installing it directly to my main internal SDD EFI partition, managing to boot into OCLP and from there into my existing Catalina installation (10.15.7) I prepared my adventure. On this machines FileVault was enabled, a TM backup was in place.
I started directly the update to Big Sur using the software update pref pane (as on a completely supported machine) and did this update to 11.2 (current full installer) and directly after the last reboot the next OTA delta update into Big Sur 11.2.1.
This was the smoothest update ever! As of now everything is working out of the box including sleep, WiFI, BT, FileVault and whatever you may miss (create a fully TM backup before you update).
iMac12,2
Most of you know that I spent some time on getting these machines supported with several patcher options. I decided to redo the first experiment with some minor differences. I started with @dosdude1 patcher installed Catalina 10.15.7 (19H2) and used an OC config similar to @jackluke USBOpenCore4s1 , i.e. setting only the BoardProduct within the Platforminfo->SMBIOS (Mac-7BA5B2D9E42DDD94) section and the SystemProductName (iMacPro1,1) in PlatformInfo->DataHub->General section and checked additionally the new MaxBIOSVersion flag there, too. The latter SystemProductName setting was necessary to make the internal SSD accessible for the Big Sur installer in the first step starting from Catalina. The former BoardProduct only will work for later OTA upgrades within Big Sur.
Starting from Catalina I did the two steps exacly as described above: First downloading the 11.2 Big Sur installer using the software update pref pane, waiting an hour and several reboots, applying the OTA delta upgrade (2.43 GB) to 11.2.1 and got after watching a complete movie in parallel and fully installed Big Sur 11.2.1 on my iMac12,2 from 2011.
The crucial step in the middle was just not patching the system using the micropatcher to leave the installed system volume untouched. Only that way you get offered the delta update (thanks to @Bmju pointing this out again and @jackluke for creating his USBOpenCore4s1).
OCLP vs. @jackluke OC config
Why two different OpenCore configurations?
The first one generated by the OCLP makes your system completely new (i.e. new serial numbers) and it will show up within the iCloud->My devices list as new and different Mac. The second one is used by some other user groups here (@cdf) to maintain the original identity of the Mac and offers at the same time (at least using it that way for a year now myself) no problems with iCloud login at all, too.
There is an ongoing discussion with the OpenCore developers about that change. You have to keep into your mind that OpenCore was mainly used to replace Clover on Hackintosh (Intel) systems. These systems do not offer valid system serial numbers and more and so this data has to be provided by OpenCore to disguise the PC as a normal Mac. Legacy Macs do not need such a full disguise to be recognized as a Mac system.
Summary:
Using OC you can get around the USB boot stick creation. It gives you nearly all the features during an update of a completely supported Mac. Older systems (like my iMac12,2) need real patching with the micropatcher patch-kext.sh thereafter to become fully usable (i.e. ethernet, sound, sleep in this particular case here). But such patching breaks getting OTA delta upgrades (snapshots may be our solution, here). 2012+ systems may even need no single patch and as of now it looks like OCLP is the nearly perfect way to go.
Note:
@jackluke himself advised to not use his USBOpenCore4s1 for Big Sur upgrades any longer back in November when the first firmware accidents happened. I will follow his advice and did this by moving to OpenCore 0.6.6 release in all tests to use the MaxBIOSVersion flag as a safety belt. Additionally please download @dosdude1 romtool app (first post) and save your firmware in advance.
Over the weekend I did some more tests.
MacBookAir5,1
Using OCLP 0.0.10 and creating a new config for my 2012 MacBookAir5,1 - installing it directly to my main internal SDD EFI partition, managing to boot into OCLP and from there into my existing Catalina installation (10.15.7) I prepared my adventure. On this machines FileVault was enabled, a TM backup was in place.
I started directly the update to Big Sur using the software update pref pane (as on a completely supported machine) and did this update to 11.2 (current full installer) and directly after the last reboot the next OTA delta update into Big Sur 11.2.1.
This was the smoothest update ever! As of now everything is working out of the box including sleep, WiFI, BT, FileVault and whatever you may miss (create a fully TM backup before you update).
iMac12,2
Most of you know that I spent some time on getting these machines supported with several patcher options. I decided to redo the first experiment with some minor differences. I started with @dosdude1 patcher installed Catalina 10.15.7 (19H2) and used an OC config similar to @jackluke USBOpenCore4s1 , i.e. setting only the BoardProduct within the Platforminfo->SMBIOS (Mac-7BA5B2D9E42DDD94) section and the SystemProductName (iMacPro1,1) in PlatformInfo->DataHub->General section and checked additionally the new MaxBIOSVersion flag there, too. The latter SystemProductName setting was necessary to make the internal SSD accessible for the Big Sur installer in the first step starting from Catalina. The former BoardProduct only will work for later OTA upgrades within Big Sur.
Starting from Catalina I did the two steps exacly as described above: First downloading the 11.2 Big Sur installer using the software update pref pane, waiting an hour and several reboots, applying the OTA delta upgrade (2.43 GB) to 11.2.1 and got after watching a complete movie in parallel and fully installed Big Sur 11.2.1 on my iMac12,2 from 2011.
The crucial step in the middle was just not patching the system using the micropatcher to leave the installed system volume untouched. Only that way you get offered the delta update (thanks to @Bmju pointing this out again and @jackluke for creating his USBOpenCore4s1).
OCLP vs. @jackluke OC config
Why two different OpenCore configurations?
The first one generated by the OCLP makes your system completely new (i.e. new serial numbers) and it will show up within the iCloud->My devices list as new and different Mac. The second one is used by some other user groups here (@cdf) to maintain the original identity of the Mac and offers at the same time (at least using it that way for a year now myself) no problems with iCloud login at all, too.
There is an ongoing discussion with the OpenCore developers about that change. You have to keep into your mind that OpenCore was mainly used to replace Clover on Hackintosh (Intel) systems. These systems do not offer valid system serial numbers and more and so this data has to be provided by OpenCore to disguise the PC as a normal Mac. Legacy Macs do not need such a full disguise to be recognized as a Mac system.
Summary:
Using OC you can get around the USB boot stick creation. It gives you nearly all the features during an update of a completely supported Mac. Older systems (like my iMac12,2) need real patching with the micropatcher patch-kext.sh thereafter to become fully usable (i.e. ethernet, sound, sleep in this particular case here). But such patching breaks getting OTA delta upgrades (snapshots may be our solution, here). 2012+ systems may even need no single patch and as of now it looks like OCLP is the nearly perfect way to go.
Note:
@jackluke himself advised to not use his USBOpenCore4s1 for Big Sur upgrades any longer back in November when the first firmware accidents happened. I will follow his advice and did this by moving to OpenCore 0.6.6 release in all tests to use the MaxBIOSVersion flag as a safety belt. Additionally please download @dosdude1 romtool app (first post) and save your firmware in advance.
Last edited:
@OKonnel,
Thank you, I will do this
For me, a true noob, I think option 5 would be the best choice then (Patched Sur), the micropatcher with a GUI
Too bad we will not get updates that way or do we?
I am still figuring out what to do with that...
Greetings,
Richard
11.2.1 (20D75)
Full Installer HOT OFF THE PRESS!!!
Full Installer HOT OFF THE PRESS!!!