done! I am about to update to 11.2.1 now. Going to see if it still happens.
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
done! I am about to update to 11.2.1 now. Going to see if it still happens.
Ciao Vincenzo
Unless you have a new 2019 MacBook... what do you need Big Sur 11.2.2 for?... Corrects the risk of your MacBook turning into a "brick" if you are using third-party HUBs, but if you have a 2019 MacBook, you don't have to patch anything... Big Sur run original!
I wonder what is this impatience that many have in wanting to immediately download every update as soon as it comes out...
Doesn't it teach you anything that Apple sometimes gets it wrong or forgets something and many times, so after a few days, Apple is forced to introduce a new Build?...
Those who were in a hurry to download the Build 11.2.1, for example, to the point of having to use OpenCore, risking a lot, to activate the OTA mode... were screwed because in OTA mode Big Sur installed the Build 20D74, in a partial package of "Delta" type. After a few days, however, we all were able to download version 11.2.1 which is not only complete, but is Build 20D75, instead of 20D74, with an important Finder fix.
Wait, therefore, that on the Apple site an official 11.2.2 is available (as happened for 11.2.1) or wait directly for 11.3.
I always await that Apple fully integrates the version of the Operating System in the official download file that is present in the App Store or that can be downloaded in other ways that you can discover on the Net.
[Hint: Google search for "gibMacOS.command", exactly, including the quotes ""
So! Download the file "Download ZIP" from the green "CODE" button.
Extract the archive and run gibMacOS.command with Terminal]
You will have a pleasant surprise and I think you will thank me; indeed, I think you will thank me in many...
Apple does not immediately integrate the App Store version with patches, but it always does some time after an "Additional Update" or "Security Update".
Buon divertimento!
Last edited:
They're forced to introduce new builds because of people like me and others on this forum that are willing to take a risk, document issues, and report it back to developers. It's how we're even able to install current operating systems on unsupported hardware. And a lot of those folks that work on developing updates to OpenCore are also back feeding to Apple engineers, which in turn leads to CVE updates. So, it's a circular kinda thing. If the guy wants to install an update, let him. I just don't suggest doing it on a system you have to rely on daily for work. Peace!
Ciao Vincenzo
Unless you have a new 2019 MacBook... what do you need Big Sur 11.2.2 for?... Corrects the risk of your MacBook turning into a "brick" if you are using third-party HUBs, but if you have a 2019 MacBook, you don't have to patch anything... Big Sur run original!
I wonder what is this impatience that many have in wanting to immediately download every update as soon as it comes out...
Doesn't it teach you anything that Apple sometimes gets it wrong or forgets something and many times, so after a few days, Apple is forced to introduce a new Build?...
Those who were in a hurry to download the Build 11.2.1, for example, to the point of having to use OpenCore, risking a lot, to activate the OTA mode... were screwed because in OTA mode Big Sur installed the Build 20D74, in a partial package of "Delta" type. After a few days, however, we all were able to download version 11.2.1 which is not only complete, but is Build 20D75, instead of 20D74, with an important Finder fix.
Wait, therefore, that on the Apple site an official 11.2.2 is available (as happened for 11.2.1) or wait directly for 11.3.
I always await that Apple fully integrates the version of the Operating System in the official download file that is present in the App Store or that can be downloaded in other ways that you can discover on the Net.
[Hint: Google search for "gibMacOS.command", exactly, including the quotes ""
So! Download the file "Download ZIP" from the green "CODE" button.
Extract the archive and run gibMacOS.command with Terminal]
You will have a pleasant surprise and I think you will thank me; indeed, I think you will thank me in many...
Apple does not immediately integrate the App Store version with patches, but it always does some time after an "Additional Update" or "Security Update".
Buon divertimento!
Ciao,
First of all, thank you very much for the support.
I was totally unaware of that command, that's great, thank you very much.
No I don't have a 2019 Macbook Pro otherwise I wouldn't be in this forum to understand how to install BigSur 11.2.1 on an incompatible Macbook Pro.
I asked if it was possible to download that update only because after installing version 11.2.1, I noticed some minor worsening of the operating system.
For example Music does not close instantly but after a few seconds (about 5 seconds) and I don't understand the reason for this delay.
I have also noticed that many times my Macbook Pro, when I try to turn it off, remains with the spinner loading and I am forced to perform a forced shutdown with the power button to be able to turn it off permanently.
I don't know if this depends on the update I made, even if everything was done correctly, so I was hoping that with an update I could solve the problem.
I will definitely enjoy it.
"Ciao alla prossima Vincenzo"
You missed some crucial information.
A patched Big Sur installation cannot load and apply OTA delta upgrades, only full upgrades coming on form of full installers.
Also, I'm pretty sure Apple has suspended issuing combo updaters for Big Sur. They seem to have only delta or full installers.
As I understand: a delta updater (also called incremental) will only update your system one "notch" in the build sequence; a combo updater can update any build in the given MacOS system, but can't leap from one system to another (like Catalina to Big Sur); and a full installer can be applied over a previous system or even the same system and same build.
OTA updaters are often incremental and may be very specific for your present build, hence we see various download sizes usually around 3 GB or so.
Check this answer. Also download GibMacOS.command as described in post #9081 just above us. This Terminal command will let you monitor the latest sucatalog for full releases.
Resign yourself, Viciè...
After the great Steve, everything happens in macOS... to the point that you have to consider yourself lucky for the problems you describe and because you didn't happen, instead, to damage your eventual brand new MacBook, with the Big Sur original... simply for having connected it to an HUB which, according to what I read on Macitynet, could also be an HUB of well-known brands. Let's try to put ourselves in the shoes of the unfortunate users to whom this happened...Anyway, back to the topic, I checked with my 27'' iMac (Late 2013, improved via Apple Store for maximum performance) and saw that Musica and shutdown work fine.
I, on the other hand, had encountered problems with Big Sur version 11.2 which also caused me some crashes and therefore I had to force restart the Mac.
So, I give you some advice based on what I understand: if we have problems... we don't have to come and look here first, but it's better to find out if the official Big Sur users have similar or worse problems.
Can I ask you if you installed Big Sur "from Zero" or if you installed it on Catalina or Mojave instead?
I preferred to install Big Sur from a clean installation, on an external 2TB SSD which I then inserted in place of the Fusion Drive Hard Disk. Big Sur practically makes my iMac fly like never before and thinks that even while spinning from the external drive it worked much better than Catalina...
How to proceed with the development?
The micropatcher has two important parts:
After Apple released the installers (11.2.1 and 11.3 Beta 2) which cannot be installed with the current micropatcher (so the first part is broken) I came to a personal conclusion that we should move away from the HAX libs on to using OpenCore as a technology base to install and boot Big Sur using @jackluke type of spoofing:
OCLP is similar approach using currently a more complex spoofing well known form the Hackintosh world. This will likely change. While OCLP does not give us right now full functionality as reached with the micropatcher part 2 (the patch-kext.sh script) we could move on to use a hybrid approach:
Advantages:
P.S.:
In fact this is a similar situation what we face with Catalina right now. The @dosdude1 patcher development has stopped and there is the need to use again @jackluke fixes to enable the access to OTA upgrades.
The micropatcher has two important parts:
- It patches the installer in a way to allow installation of Big Sur on unsupported legacy Macs
- There is a second patch process (patch-kext.sh) which does the modification of in already installed Big Sur to fit with the hardware detected (i.e. enable WiFi, sound, ethernet, sleep to name just a few).
After Apple released the installers (11.2.1 and 11.3 Beta 2) which cannot be installed with the current micropatcher (so the first part is broken) I came to a personal conclusion that we should move away from the HAX libs on to using OpenCore as a technology base to install and boot Big Sur using @jackluke type of spoofing:
Code:
PlatformInfo->Generic->SystemProductName (i.e. iMacPro1,1)
PlatformInfo->Generic->MaxBIOSVersion (true)
PlatformInfo->Automatic (true)OCLP is similar approach using currently a more complex spoofing well known form the Hackintosh world. This will likely change. While OCLP does not give us right now full functionality as reached with the micropatcher part 2 (the patch-kext.sh script) we could move on to use a hybrid approach:
- use OpenCore to install, boot and OTA upgrade
- use micropatcher patch-kext.sh to patch Big Sur to achieve maximum compability unless OLCP overtakes
Advantages:
- OpenCore allows cross macOS installation of Big Sur. I was able to start the Apple macOS Big Sur installer from High Sierra, Mojave, Catalina and Big Sur to do a full installation. There will be no need to have a patch app.
- OpenCore allows OTA full (in every case) and OTA delta upgrades unless you modify the system through patching with patch-kext.sh. This allows at any time to install an arbitrary full Big Sur installer, apply all available OTA upgrades and patch then the system finally. This process can be repeated. (APFS snapshots can help here, too).
- OpenCore allows in some cases (nearly) full functionality without patching. Last week I created an iMac 12,2 Catalina configuration which offers everything except sound - you can us a BT sound cube to get around this.
- OpenCore can be used to install and maintain Mojave and Catalina, too. It is not limited to Big Sur.
- Using the patch-kext.sh (aka patching Big Sur) breaks the OTA delta upgrades - these are the smaller upgrades Apple delivers now from time to time instead publishing a full installer, the latest 11.2.2 is an example.
P.S.:
In fact this is a similar situation what we face with Catalina right now. The @dosdude1 patcher development has stopped and there is the need to use again @jackluke fixes to enable the access to OTA upgrades.
Last edited:
Hello ... the links "Where/how can I download macOS 11.0 Big Sur?" doesn't work.
Please can you update the link?
Regards
Done, but I will not update the list any longer, please use this tool to get macOS updates in future. Has been posted here several times, the latest download link, too. There is a search button where you can search the thread ....
Are you sure is updated?
i'm trying to click over the url's and doesn't work.
One more think, about the tool, there is a readme or guide how to use it?
(what parameter send, how, etc )
Best regards
Another smooth sailing from 11.2.1 to 11.2.2 through Software Update.
Everything works well, including Apple TV+ DRM.
Everything works well, including Apple TV+ DRM.
Sorry , to make this full quote ..
I did it your way like shown in the video .. but when the USB Stick with EFI is not plugged in it says me this Mabook is not supported ,with the USB plugged in i can start over EFI as usual ..
How can i solve this because i dont always want to start with the USB plugged in ..
Attachments
![IMG_20210228_130631[818].jpg](/data/attachments/941/941319-96f0ad618aa97b553841bc825ad706c8.jpg)
Hi everybody! I got a 2009 Mac Pro flashed to 5,1. I had Big Sur installed for awhile on it. I had a problem with Windows 10 that crashed and somehow caused Big Sur to kernel panic and never boot.
i wiped the hard drive and reinstalled High Sierra to have a bootable volume.
the problem I’m running into is that Big Sur runs the first step fine. On reboot it will boot into the Installer partition it created but at the apple screen, right before it should be giving me a time remaining it reboots. Over and over. I tried reinstalling a couple different was. With Barry’s patcher, I first tried by using the EFI to set the variables and then install. Same problem. Then I set the variables using terminal instead of the efi partition with the same outcome. I also tried open core and get the same problem.
I know there is a way around this because I had to deal with it before but I can’t figure out what I did.
anyone that had the same problem, how did you get it to finally install?
Thanks for any help!!
i wiped the hard drive and reinstalled High Sierra to have a bootable volume.
the problem I’m running into is that Big Sur runs the first step fine. On reboot it will boot into the Installer partition it created but at the apple screen, right before it should be giving me a time remaining it reboots. Over and over. I tried reinstalling a couple different was. With Barry’s patcher, I first tried by using the EFI to set the variables and then install. Same problem. Then I set the variables using terminal instead of the efi partition with the same outcome. I also tried open core and get the same problem.
I know there is a way around this because I had to deal with it before but I can’t figure out what I did.
anyone that had the same problem, how did you get it to finally install?
Thanks for any help!!
This really sounds intriguing ! I am currently experimenting with Patched Sur as a front-end to your micro patcher, and with the OPenCoreLegacy Patcher. With Patched Sur, everything seems to works just fine but I need to do the install again for every OS update; with OCLP my wifi isn't working (airport drivers aren't loaded, it seems).
So a combination would be just what we are looking for
Cheers,
Willem
Netherlands
This really sounds intriguing ! I am currently experimenting with Patched Sur as a front-end to your micro patcher, and with the OPenCoreLegacy Patcher. With Patched Sur, everything seems to works just fine but I need to do the install again for every OS update; with OCLP my wifi isn't working (airport drivers aren't loaded, it seems).
So a combination would be just what we are looking for
Cheers,
Willem
I use that opencore imac patcher on my 2011 27” because of the upgraded graphics card. And OTA updates have been installing great without having to do anything. I love having the bootpicker with OC as wellThis really sounds intriguing ! I am currently experimenting with Patched Sur as a front-end to your micro patcher, and with the OPenCoreLegacy Patcher. With Patched Sur, everything seems to works just fine but I need to do the install again for every OS update; with OCLP my wifi isn't working (airport drivers aren't loaded, it seems).
So a combination would be just what we are looking for
Cheers,
Willem
Netherlands
Do you have a link to that version micropatchautomator? I’m having trouble reinstalling Big Sur on my 4,1 flashed to 5,1 Mac Pro. It gets through the first step but continues to reboot after that.
also, do you have screen brightness control slider in the display preferences?
thanks for any help you can give me!
How are things going with the MacBook 7,1? (last of the white unibodies)
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" threadThis really sounds intriguing ! I am currently experimenting with Patched Sur as a front-end to your micro patcher, and with the OPenCoreLegacy Patcher. With Patched Sur, everything seems to works just fine but I need to do the install again for every OS update; with OCLP my wifi isn't working (airport drivers aren't loaded, it seems).
So a combination would be just what we are looking for
Cheers,
Willem
Netherlands
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.