macOS 11 Big Sur on Unsupported Macs Thread

[velvet_man]

I tried searching for anyone having a similar issue and couldn't find anything, but I apologize if this has been covered already.

I have 2011 27" iMac with a K2100m flashed with Nick's bios. I had everything working perfectly in High Sierra using the CatalinaLoader flashed to a bootable SD card using OpenCore 0.5.9. Everything was working flawlessly, but I thought I would finally take the plunge and try to upgrade to Big Sur.

I used Ausdauersportler's "automator-for-barrykn-micropatcher" linked in the first post of the 2011 iMac GPU upgrade thread and followed the instructions. It installed without any issues and then it installed all of the post-install patches with any issues. But when I tried to reboot, it went to the Apple screen and got about 30% through the progress bar and froze. I then tried booting from the CatalinaLoader/OpenCore SD card first, but got the same result. So I put the SD in another computer and replaced the 0.5.9 EFI folder with the newest 0.6.6 (also found in Ausdauersportler's post in the GPU upgrade thread) and renamed the appropriate nvidia file config.plist. But that had the same result, too.

I noticed, though, that it doesn't look like OpenCore is working, even though the drive worked perfectly before. Before, when I selected the CatalinaLoader/OpenCore drive to boot, it went into a white OpenCore screen with options to choose from. Now, when I boot from the CatalinaLoader/OpenCore drive, it goes to a black screen that says:

"Starting OpenCore.efi
Using load options ' '
OCS: No schema for BootProtect at 5 index, context <Security>!"

Then it just tries to continue booting MacOS instead of going into the OpenCore screen. Any ideas what went wrong?

 

[Ausdauersportler]

I tried searching for anyone having a similar issue and couldn't find anything, but I apologize if this has been covered already.

I have 2011 27" iMac with a K2100m flashed with Nick's bios. I had everything working perfectly in High Sierra using the CatalinaLoader flashed to a bootable SD card using OpenCore 0.5.6. Everything was working flawlessly, but I thought I would finally take the plunge and try to upgrade to Big Sur.

I used Ausdauersportler's "automator-for-barrykn-micropatcher" linked in the first post of the 2011 iMac GPU upgrade thread and followed the instructions. It installed without any issues and then it installed all of the post-install patches with any issues. But when I tried to reboot, it went to the Apple screen and got about 30% through the progress bar and froze. I then tried booting from the CatalinaLoader/OpenCore SD card first, but got the same result. So I put the SD in another computer and replaced the 0.5.6 EFI folder with the newest 0.6.6 (also found in Ausdauersportler's post in the GPU upgrade thread) and renamed the appropriate nvidia file config.plist. But that had the same result, too.

I noticed, though, that it doesn't look like OpenCore is working, even though the drive worked perfectly before. Before, when I selected the CatalinaLoader/OpenCore drive to boot, it went into a white OpenCore screen with options to choose from. Now, when I boot from the CatalinaLoader/OpenCore drive, it goes to a black screen that says:

"Starting OpenCore.efi
Using load options ' '
OCS: No schema for BootProtect at 5 index, context <Security>!"

Then it just tries to continue booting MacOS instead of going into the OpenCore screen. Any ideas what went wrong?

Whenever you change the OC version (config) you have to do a PRAM reset.
Honestly I did not check the latest OC configs on K2100M card (do not own such a card).
Starting the installation: PRAM reset
Finishing the installation: PRAM reset (althouth here you got only a different OC config.plist including iMacPro spoofing, unlike the versions from the thread, not another OC version)

The MicropatcherAutomator installed a fitting OC version on the installation media (USB/SD). You have to use this version! There is not free pick. Automator says it all!

 

[velvet_man]

Whenever you change the OC version (config) you have to do a PRAM reset.
Honestly I did not check the latest OC configs on K2100M card (do not own such a card).
Starting the installation: PRAM reset
Finishing the installation: PRAM reset (althouth here you got only a different OC config.plist including iMacPro spoofing, unlike the versions from the thread, not another OC version)

The MicropatcherAutomator installed a fitting OC version on the installation media (USB/SD). You have to use this version! There is not free pick. Automator says it all!

Oh, I think I may have misunderstood something. Does the automator USB drive I made have OpenCore on it? I just boot from that drive instead of from my old CatalinaLoader SD card?

 

[ray308]

Just installed macOS 11.2.1 (build 20D75) on my iMac late 2013 27" with Fusiondrive ;-)
Used micropatcher 0.5.1 from barrykn

I only had to do an extra IFE BOOT after completing install as stated on his Github page (bullet 9). Works smooth no problems at all.

 

[sinbad21]

I'm actually using OC my own 2012 MacBook Pro because I believe it's a cleaner solution, with less changed than using the patcher - for me. (Though that said, I have *some* reservations about the current OCLP config - which also, I believe, changes more than it needs to.) In any event, a direct result of OC's different (and arguable even cleaner) approach, is that it is currently the only known way to get preference pane (aka OTA) updates, if you want them. So you have to live without them, or jump ship!

(OCLP is one easy way to get and configure OC; probably by far the easiest, in fact; but not the only way.)

How do you use OCLP? Don't you need to change the model of your Mac by a supported model to get the OTA updates?

 

[Bmju]

How do you use OCLP? Don't you need to change the model of your Mac by a supported model to get the OTA updates?

Yes that bit you do need to change, but not very much else about the machine ID. Not everything new to match, as you would with a H*ckintosh. OCLP does change a lot more like that. I put a post about it somewhere above.

 

[velvet_man]

Whenever you change the OC version (config) you have to do a PRAM reset.
Honestly I did not check the latest OC configs on K2100M card (do not own such a card).
Starting the installation: PRAM reset
Finishing the installation: PRAM reset (althouth here you got only a different OC config.plist including iMacPro spoofing, unlike the versions from the thread, not another OC version)

The MicropatcherAutomator installed a fitting OC version on the installation media (USB/SD). You have to use this version! There is not free pick. Automator says it all!

OK I had some more time to experiment with this and may have found something helpful. I tried booting from the EFI on the automator USB, but it froze at the same place as it has been all along. So I put the automator install USB in my Macbook and looked through the OpenCore folder. I renamed the NVIDIA Big Sur file to config.plist to try that, but it didn't work either. So I tried the verbose to see what's going on.

It went through a few screens of text before freezing. Just before it froze, it went through a few lines beginning with "com.apple.xpc.launchd[1]". The first line said "entering bootstrap mode" and the second line was something about it constantly running and being "inherently inefficient". But then the next two lines were errors:

<Error>: com.apple.cvmsCompAgent_arm64_1 (lint): UserName is not supported for non-System services
<Error>: com.apple.cvmsCompAgent_arm64 (lint):UserName is not supported for non-System services
<Notice>: Did not import service from caller: path = /System/Library/LaunchAgents/com.apple.loginwindowLite.plist, caller = recoverosd.75, error = 152: Service cannot load in current boot environment
<Warning>: com.apple.VoiceOver (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.

Then it froze there for several minutes before adding one last line and stopping entirely:


"Please go to https://panic.apple.com to report this panic"

I looked back a bit further, before it crashed, and noticed a few instances of "failed to bootstrap path" followed by a path (one is /System/Library/LaunchAgents/com.apple.Safari.PasswordBreachAgent.plist and the other was /Library/Apple/System/Library/LaunchAgents) followed by "No such file or directory".

I hope that makes some sense to someone here who could offer some help. If it matters, before all of that happened, it looks like it was loading kexts. Thanks in advance!

 

[Ausdauersportler]

OK I had some more time to experiment with this and may have found something helpful. I tried booting from the EFI on the automator USB, but it froze at the same place as it has been all along. So I put the automator install USB in my Macbook and looked through the OpenCore folder. I renamed the NVIDIA Big Sur file to config.plist to try that, but it didn't work either. So I tried the verbose to see what's going on.

It went through a few screens of text before freezing. Just before it froze, it went through a few lines beginning with "com.apple.xpc.launchd[1]". The first line said "entering bootstrap mode" and the second line was something about it constantly running and being "inherently inefficient". But then the next two lines were errors:

<Error>: com.apple.cvmsCompAgent_arm64_1 (lint): UserName is not supported for non-System services
<Error>: com.apple.cvmsCompAgent_arm64 (lint):UserName is not supported for non-System services
<Notice>: Did not import service from caller: path = /System/Library/LaunchAgents/com.apple.loginwindowLite.plist, caller = recoverosd.75, error = 152: Service cannot load in current boot environment
<Warning>: com.apple.VoiceOver (lint): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.

Then it froze there for several minutes before adding one last line and stopping entirely:


"Please go to https://panic.apple.com to report this panic"

I looked back a bit further, before it crashed, and noticed a few instances of "failed to bootstrap path" followed by a path (one is /System/Library/LaunchAgents/com.apple.Safari.PasswordBreachAgent.plist and the other was /Library/Apple/System/Library/LaunchAgents) followed by "No such file or directory".

I hope that makes some sense to someone here who could offer some help. If it matters, before all of that happened, it looks like it was loading kexts. Thanks in advance!

You need to get a Big Sur compatible OC version for the Catalina Loader on the iMac GPU thread and check it out with your card and the current installation. It should be the 0.6.6+ version.

The only difference between the NVIDIA config.plist files there and on the EFI delivered with the Micropatcher Automator is the PlatformInfo section - which will not stop the system.

You have to reset the PRAM when using a different/new OC version. There is no way around this. You have to make it work.

BTW:
Cross posting on Discord is not helpful either. You are forcing several people to work on the same problem in parallel.

 

[velvet_man]

You need to get a Big Sur compatible OC version for the Catalina Loader on the iMac GPU thread and check it out with your card and the current installation. It should be the 0.6.6+ version.

The only difference between the NVIDIA config.plist files there and on the EFI delivered with the Micropatcher Automator is the PlatformInfo section - which will not stop the system.

You have to reset the PRAM when using a different/new OC version. There is no way around this. You have to make it work.

BTW:
Cross posting on Discord is not helpful either. You are forcing several people to work on the same problem in parallel.

Thank you for the help. I updated my Catalina Loader SD card following the instructional video from h9826790 in the other thread. So it has a 0.6.6 OC now with the Nvideo plists. And of course, I did the PRAM reset as always. It's still freezing/crashing during boot, but according to the verbose boot, it's at a different place. It now freezes when it gets to "waiting for remote debugger connection". The last thing it said before that is "In Memory Panic Stackshot Succeeded" followed by what looks like a bunch hex code.

 

[Peatwheat]

11.3 Beta 1 doesn't seem to have the security update for sudo listed here...

https://mrmacintosh.com/macos-big-sur-11-2-1-update-20d74-is-live-whats-new/

 

[Earl Urley]

That's okay, because beta 2 does.

Running sudo -V on beta 2 gives me version 1.9.5p2, which is the patched sudo version that patches out the bug.

 

[StephN999]

Bonjour,

No problems with 11.3 Beta 2 (20E5186d) patching with big-sur-micropatcher fork by Ausdauersportler,
as well as the latest version of OpenCore 0.6.7 (3aa6bc3).

Bonne journée.

Edit: Music.app has been upgraded to version 1.1.4.78

 

[Friends4U]

Here the install also succeeded, but I must say... The Mac is quite a bit slower (especially with Photoshop).
I'm thinking about reverting back... Dunno why it's slower

 

[vvapple]

Can anyone answer me if running an AppleID on an unsupported Mac with Bigger, would Mess around with my AppleID and iCloud? Would be interesting to know, as I started experiencing contacts sometimes only showing the number instead of the name in iMessage since I run Bigsur on my unsupported iMac late 2013.

 

[Jack Neill]

Can anyone answer me if running an AppleID on an unsupported Mac with Bigger, would Mess around with my AppleID and iCloud? Would be interesting to know, as I started experiencing contacts sometimes only showing the number instead of the name in iMessage since I run Bigsur on my unsupported iMac late 2013.

I have never had any issues with Hacks or Unsupported Macs and iCloud syncing properly. iMessage/Photos work great for me. That usually happens when one of your accounts isn't synced. Like my Google has some of mine and iCloud has the rest and I need to sync both accounts to get all the names back.

 

[Jack Neill]

Bonjour,

No problems with 11.3 Beta 2 (20E5186d) patching with big-sur-micropatcher fork by Ausdauersportler,
as well as the latest version of OpenCore 0.6.7 (3aa6bc3).

Bonne journée.

Edit: Music.app has been upgraded to version 1.1.4.78

Does it suck any less?

 

[vvapple]

I have never had any issues with Hacks or Unsupported Macs and iCloud syncing properly. iMessage/Photos work great for me. That usually happens when one of your accounts isn't synced. Like my Google has some of mine and iCloud has the rest and I need to sync both accounts to get all the names back.

Thats what made me wonder. Its an iCloud only account. so it is not in any connections with google or what so ever - I couldn't explain it to myself other than the fact that the Mac runs an unsupported OS on it. Maybe the update to 11.2.1 will help

 

[borp99]

Big Sur 11.2 on Mac Pro 3,1 (2008)??

Hi all,

I've been avidly following this forum since day one and have enjoyed getting BS running on my trusty 2010 cMP 5,1 through all of the early betas and stable later releases.

I recently bought a cMP 3,1 to gift to my sister as a surprise (to replace her cMP 1,1 which is limited to 10.11). I've installed 10.6.8, 10.12.6 and 10.15.7 on a Samsung Pro SSD inside the 3,1 and everything is running fast and sweetly. The GPU has been updated with a 'metal' HD7950 card I had spare and the dual CPU's upped to 3GHz E5472's (SSE4.1 compliant).

However, trying to install Big Sur is causing me endless frustration. I've tried using micropatcher 0.51 and 0.53, the MicropatcherAutomator app, BigMac’s 2.0alpha2 patcher and even jackluke's BaseSystemFix restore image (where you swap out the SharedSupport.dmg with the latest one), and also tried various types of OpenCore - but all suffer from the same one problem I've found mentioned only once on a Google search (with no solution), and haven't found anything searching this specific thread either,... which is that the patched BS installer gets to the Install window but with no USB keyboard or mouse support - so the mouse pointer is stuck in the top left hand corner and no installation is possible to enact. The various patching methods are supposed to inject a LegacyUSB kext but it just doesn't seem to be working for me. I tried adding the legacy (USB 1.1) MacPro3,1 integer strings under IOKitPersonalities_x86_64 in the AppleUSBHostMergeProperties.kext's Info.plist (that kext inside the IOUSBHostFamily.kext), but the modified BaseSystem.dmg then no longer matches the BaseSystem.chunklist file, so the installer fails to load that way too. I'd love to add BS to my sister's 'present', so she's up to date with all things Mac.

So, has anyone with a 3,1 had the frozen USB pointer problem and found a way to get around it to install Big Sur?

UPDATE (@22 Feb 2021): After sending 4 full days trying to get BS11.2 installed on the cMP 3.1, the only way that finally worked for me was to clone a working 10.15.7 to a to-be-11.2 new partition, run StarPlayrX BigMac 2.0 (alpha2) from that new partition - only selecting the PreInstall pane and launching the BS installer app (in the Applications folder) from there (which patches Hax3 on the fly and sets nvram parameters (although I'd already ran the 'install-setvars.sh' from the 0.51 micropatcher shortly earlier). All other methods (for me) either didn't liven the pointer, did get the pointer to work in Single User mode but then barely started to install before crashing or got to an endless loop 50% to 80% through (often with a 'too many corpses' string respawning every second or so) that no amount of patcher options could fix. With the 10.15 upgrade route, once it reach what appeared to be its last auto reboot, I booted into a prepared BigMac USB installer stick (with the 12.2GB SharedSupport.dmg replaced with a zero sized file by the same name...although that's only optional/but it does deduce the files to about 1.8GB) and ran the PostInstall patches for 11.2 from there. Once Big Sur was blessed and rebooted, the updated 10.15->11.2 desktop came up (although initially none of the drive icons were showing, even though the Finder Preferences for showing HD's was selected. A further reboot seemed to fix this anomaly). I hope this method helps some other poor soul trying to freshen up their old 2008 machine.

 

[kayaman80]

Hi guys, sorry but, i tried evrything, every guide, every tutorial, but i found no solution for my BCM on Mid2012 A1278.The installer went fine at first boot, and installation too, but i can't unlock permission on disk in any way to try to fix my wifi issue. The last try was this steps through Installer/recovery, but as u can see, another problem...can u help me or do you think it's better to buy another wifi card?

 

[Ausdauersportler]

Hi guys, sorry but, i tried evrything, every guide, every tutorial, but i found no solution for my BCM on Mid2012 A1278.The installer went fine at first boot, and installation too, but i can't unlock permission on disk in any way to try to fix my wifi issue. The last try was this steps through Installer/recovery, but as u can see, another problem...can u help me or do you think it's better to buy another wifi card?

Read the last section of the micropatcher online GitHub README.md file to learn how to unlock and change the system volume yourself. You clearly missed that part of a guide.

And it would be nice to know what patcher you have used. Add a signature to your account. This will come much closer to "everything"!

 

[ASentientBot]

New version of the "Hax.dylib" which fixes the issue (as discussed on Discord) when launching the installer on a running Big Sur system. Thanks to @Minh_Ton, @moosethegoose2213 * and @BenSova for reporting the problem and helping test. As always, feel free to use this in your patchers.

This is not necessary if you're installing from an older OS or BaseSystem environment.

 

[kayaman80]

Ok, maybe i didn't understand clearly the guide, i will give it another chance...as patcher i used Patched_Sur to create the installer, but i had no problem to create the installer.

Update:
Ok, everything fine, i fix my wifi problem with this command

/Volumes/Image\ Volume/patch-kexts.sh /Volumes/Macintosh\ HD

Wifi perfectly working, thank you...regarding the update, is there a way to update in the future or better to stay with this version?

 

[velvet_man]

I've been trying to get Big Sur to boot with my Catalina Loader/OpenCore 0.6.6 EFI, but it still keeps freezing/crashing about 30% through the boot.

Previously, I noticed when it tried to launch OpenCore, it gave me the black screen that said "starting OpenCore.efi" but then it had a not about "no schema for BootProtect at index 5". That's changed now with the new EFI/config that I'm using. It's now saying "no schema for DSDT at index 1, context <ACPI>!" Any idea what could be causing that?

 

[mixel]

This is going to be incredibly noob-ish but I'd really like to upgrade my already updated to Big Sur iMac to a later point release because of a few issues im having with icloud.. My problem is i can't remember how I upgraded it in the first place..

It's a late 2013 iMac.. And this is the USB stick I used to install it (maybe you recognise the files). I.. Don't remember though, and things seem to have got a lot more complicated since I did it. What's going to be the most painless way of further updating this setup?

Thanks.

 

[CuchoM]

Can anyone answer me if running an AppleID on an unsupported Mac with Bigger, would Mess around with my AppleID and iCloud? Would be interesting to know, as I started experiencing contacts sometimes only showing the number instead of the name in iMessage since I run Bigsur on my unsupported iMac late 2013.

No mess and no problem with AppleID, I am MBP9,2 no retina with BS 11.3 beta 2 running OCPL 0.0.10 and OC 0.6.7