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
Just because no one posted this yet ... unknown if BarryKN's micropatcher works so far!
1. macOS Big Sur 11.2.2 (20D80)
- 071-08935 - Added 2021-03-01 18:20:19
12.2 GB download
http://swcdn.apple.com/content/down...g8zje0wiks3r03r91euyi9sa/InstallAssistant.pkg
It is also available at the Apple Store, but you'll need a supported Mac to download it.
1. macOS Big Sur 11.2.2 (20D80)
- 071-08935 - Added 2021-03-01 18:20:19
12.2 GB download
http://swcdn.apple.com/content/down...g8zje0wiks3r03r91euyi9sa/InstallAssistant.pkg
It is also available at the Apple Store, but you'll need a supported Mac to download it.
Last edited:
Hi @David dongfox
It's very simple to use, you will find MDS at this link: https://twocanoes.com/products/mac/mac-deploy-stick/
Launch MDS, select "Download macOS" at the bottom of the left column. Wait a few seconds for MDS to search for all OS versions to download. Select the one you want from the list that appears. Click on the "Download" button at the very bottom right of the MDS window. Then select the location to save the download to (on the desktop for example).
Waiting for long minutes...
When the download is finished, just mount the obtained .dmg and go to the "Application" folder (contained in this .dmg ), at this location you will find "Install macOS Big Sur.app".
Personally I move "Install macOS Big Sur.app" to the "Application" folder of my system and I run the following command in Terminal to create my USB stick:
Code:
sudo /Applications/Install macOS\ Big\ Sur.app/Content/Resources/createinstallmedia --volume
Last edited:
Tested Barrykn's micropatcher 0.5.1 with BS 11.2.2, it worked, I installed it on 11.2.1.
I installed OpenCore yesterday on the MacbookPro 13" 2012 (MacBook Pro 9,1) with OCLP version 0.0.10. Worked liked a charm. With Catalina, the wifi wasn't working; after updating (OTA with Software Update) to Big Sur 11.2.2, the wifi is back and working great.The 2012/2013 Macs are most likely the best systems to go with OCLP right now. Possibly you can get everything working without any patching and so having OTA delta and full all the time. Just check it out and read the official OpenCore guides - I guess this will not become a "fix my EFI" thread
Your type of system cannot be modified and so after a while a fixed and fully working config.plist should by part of the OCLP distribution.
Things are more difficult for older systems and the modular ones like the MacPro and iMac11,x and 12,x - there you can find a Zoo of closely related but not identical systems right now. This makes the "one size fits all approach" hard to achieve.
So, a happy camper here
I also noticed that there is a new version of OCLP, version 0.0.11. Can anyone recommend to upgrade to the new OCLP version?
Cheers,
Willem
Upgraded to OC 0.6.7 yesterday without OCLP. (This was before they released the patcher update later in the day.) I would say go for it if your comfortable with OC updates. And depending on your depth of knowledge around Opencore, I might even suggest using the stock OC release rather than OCLP to trim off some of the unnecessary additions this go around.I installed OpenCore yesterday on the MacbookPro 13" 2012 (MacBook Pro 9,1) with OCLP version 0.0.10. Worked liked a charm. With Catalina, the wifi wasn't working; after updating (OTA with Software Update) to Big Sur 11.2.2, the wifi is back and working great.
So, a happy camper here
I also noticed that there is a new version of OCLP, version 0.0.11. Can anyone recommend to upgrade to the new OCLP version?
Cheers,
Willem
Out of curiosity, has anyone gotten 11.2 installed on an MP3,1 using OC v0.6.7? I updated OpenCore today, but it still kernel panics and reboots immediately after starting the BS installer volume (2nd reboot).
I have a feeling one of the kexts used for legacy hardware isn't 100% compatible with an MP3,1.
I have a feeling one of the kexts used for legacy hardware isn't 100% compatible with an MP3,1.
The great convergence...
There has been a major revamp of the OCLP published (version 0.0.11 see post #1 for links). An update to OpenCore 0.6.7 and a major step towards better integration with original Apple hardware has been made:
You can opt in while building the EFI folder to use your own serial numbers of your current Apple system.
This way the machine would be recognised as the very same system as used with former (likely supported or @dosdude1 style patched macOS versions) and most importantly you can migrate by far more easy to an upcoming new version of OpenCore and OCLP because you are not using (newly) generated serials but your very own ones - which will be identical all the time!
Right now I would say the most easy way to achieve the hybrid approach with micropatcher for the normal users is using OCLP to create a custom EFI and save this EFI onto the EFI partition of a new USB Installer.
Using the development version dev-v0.5.5 of the micropatcher you can than install the patching scripts onto the USB installer created with OCLP, boot the installer, install Big Sur, apply existing OTA upgrades and then finally patch the system using the patch-kext.sh script.
In short:
Benefits of using OpenCore:
There has been a major revamp of the OCLP published (version 0.0.11 see post #1 for links). An update to OpenCore 0.6.7 and a major step towards better integration with original Apple hardware has been made:
You can opt in while building the EFI folder to use your own serial numbers of your current Apple system.
This way the machine would be recognised as the very same system as used with former (likely supported or @dosdude1 style patched macOS versions) and most importantly you can migrate by far more easy to an upcoming new version of OpenCore and OCLP because you are not using (newly) generated serials but your very own ones - which will be identical all the time!
Right now I would say the most easy way to achieve the hybrid approach with micropatcher for the normal users is using OCLP to create a custom EFI and save this EFI onto the EFI partition of a new USB Installer.
Using the development version dev-v0.5.5 of the micropatcher you can than install the patching scripts onto the USB installer created with OCLP, boot the installer, install Big Sur, apply existing OTA upgrades and then finally patch the system using the patch-kext.sh script.
In short:
- download the latest OCLP
- create an OpenCore EFI folder using your own serial numbers and write the EFI to the USB stick using OCLP
- boot OpenCore (using alt/opton) the Boot EFI of the USB stick and then boot your existing macOS version
- download latest Apple installer and create bootable USB installer using createinstallmedia (as usual)
- apply the dev-v0.5.5 version micropatcher.sh to the USB as described in the docs (as usual)
- reboot (using alt/opton) the Boot EFI of the USB stick OpenCore
- start the USB installer and install or upgrade your Mac
- boot into you new Big Sur installation and apply available OTA upgrades, first (check software update pref pane)
- finally patch the Mac using patch-kext.sh (if you are not satisfied with the functionality OCLP currently offers for your system)
Benefits of using OpenCore:
- The ability to apply full OTA installers via the software update preferences pane all the time and the ability to download those full installers separately to create USB installers (if needed)
- The ability to apply even delta OTA upgrades via the software update preferences pane directly after a new full installation and before using the mircopatcher patches.
- iMac 11,1 and 12,2 users may use in step 2 the install-opencore.sh script of the dev-v0.5.5 version of the micropatcher. This way they get an OpenCore config.plist slightly better adopted to this family of iMac machines.
- I pulled the Night Shift feature from the micropatcher default patching because is is interfering with the installation process.
- Using the @jackluke spoofing you get Night Shift out of the box, there is a Night Shift enabler available with OC using the new normal spoofing described above.
Hi all
cMP5,1 successfully upgraded from 11.2.1 to 11.2.2
cMP5,1 successfully upgraded from 11.2.1 to 11.2.2
Tried the same procedure now with 11.2.2.
No success yet, reboots rather early in phase2 of installation. Will test further.
Edit: installed again from same BS USB installer, worked this time. MBP5,2 now on 11.2.2.
(The only change was replacement of HaxLib.dylib on the USB installer as per ASentientBot's post #8950; but this was unnecessary and not the problem.)
Attachments
Last edited:
Bonsoir,
Update to OpenCore Final 0.6.7 -> OK
Update to 11.3 beta 3 (20E5196f) -> Ok
Bonne soirée.
Update to OpenCore Final 0.6.7 -> OK
Update to 11.3 beta 3 (20E5196f) -> Ok
Bonne soirée.
It is never a question of popular or not, more right or wrong or useful vs. useless...
OCLP is the experiment to find a solution for the homogenous world of Apple hardware. Unlike the PC world we have only a few colored animals using some different hardware componts. It is working quite fine using different kind of spoofing with my machines not only for Big Sur, but also with High Sierra, Mojave, and Catalina (after a lot of fine tuning, which is the work you have to spend into the config.plist).
If you opt to keep your original Apple serial numbers and doing an SMBIOS only spoofing there will be no different serial numbers after another run, only the (single) ones provided by Apple with our hardware. I did this more than one time and the only thing you really get is the very same board-id to be used in the SMBOIS section.
If you opt to do a full PC style spoofing the software tools will pick fitting serials out of an internal database known to work with Apple iCloud....if you run it twice you get two such sets and so on. This is no inconsistence, this is "works as designed" but clearly not as designed for legacy Apple hardware. You can run the macserial tool from the command line to get an idea how it works. Because to this some members here on the forum made a series of CRs to the main OpenCore development to get the original serials back, to get this light SMBIOS spoofing introduced (which I currently do not use).
Which extra variables are you writing about?
The location of the EFI folder is really somewhat hidden, but you have the option to write it immediately to your target device and you get a message during the run where to find it. This way you avoid getting tons of versions in the same download folder and it will be deleted automatically after a run.
Where is deviation from the stock OpenCore?
From my point of view both developers are quite open to pull requests and change requests. In fact both depend on our input because we own the Apple hardware and we can do the tests. If you can solve another miracle of your system then post it and let us move it into this tool (or come up with another one).
Otherwise we can start this "please fix my EFI folder" game played in the Hackintosh world.
Last edited:
Yes, thank you Ausdauersportler for the write up.
Q:
I have 2012 Macmini6,1 patched using micropatcher 0.5.1, now running 11.2.1. Been thinking of switching to OCLP but was worried about bricking the firmware.
Are we there yet with this hybrid approach as suggested by Ausdauersportler?
How best to go about doing that? Is it a start all over from scratch(clean install) or there is a golden path to switch?
Would like to hear from anyone that has done similar switch.
On Mac Pro 3.1 OCLP 0.0.11 get error in step 1 - build opencore config.