Sidebar Sidebar
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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I was thinking to install 11.2 on my iMac. I have downloaded the 12GB file and created the USB installer. I see that @Ausdauersportler micropatcher 0.5.3 has an option to install a preconfigured opencore in USB by using install-opencore.sh instead of install-setvars.sh.
At the moment I don’t use opencore since my GPU is flashed with a vBIOS and I can have the native boot picker if I hold option during boot.

What would be the benefit of opencore in my system? Will I be able to use OTA in the future to install 11.3 when it becomes available?

If I choose to install opencore could I still boot my iMac without the USB and insert it only if I need an OTA update?

With my current system if I reset PRAM I have to insert the patched USB and select EFI Boot to be able to boot again. Is this option available (EFI Boot) with the opencore installation on the same USB? What should I do after a PRAM reset to be able to boot again without the USB?

I read that after installation we have to run config-opencore.sh. Do we run this after patch-kexts.sh or instead of patch-kexts.sh?
 
Successful upgrade to Big Sur on mid 2012 Macbook pro. But why my mac app store screen is completely empty or blank?
Any ideas ?
 
Dayo said:
Not looked into these issues but still prefer to run one spoofed version (from the OC Thread here which is not as highly spoofed as the OCLP but with some spoofing all the same) and one largely vanilla version for interacting with Apple on updates etc ... mainly updates.

You get the two instances when booting and can just select and go.
Click to expand...
No longer convinced this is needed, and also pretty certain that if you are really fully faking the ids on your fake id version (ProtocolOverrides/DataHub = true) then you would be getting iCloud problems when you switch between the two configs (unless you are doing something else again, to allow downloads but prevent your machine connecting to iCloud?); also that if you are not fully faking the ids (i.e. if that setting is false), then for non-obvious reasons which have only just been documented in OC, I unfortunately think that it is at least possible that your fake id setup is not really doing what you think it is doing.
 
Bmju said:
Really fully faking the ids on your fake id version (ProtocolOverrides/DataHub = true)
Click to expand...
@cdf based minimal approach does not involve spoofing such items.

It involves the least amount of spoofing possible. This has been dubbed "hybridisation" and this is basically all a real Mac needs.

I believe you use the OCLP which is the polar opposite. Perhaps a reflection of the Hackintosh roots.
 
Last edited:
  • Like
Reactions: Bmju
johnrak said:
I was thinking to install 11.2 on my iMac. I have downloaded the 12GB file and created the USB installer. I see that @Ausdauersportler micropatcher 0.5.3 has an option to install a preconfigured opencore in USB by using install-opencore.sh instead of install-setvars.sh.
At the moment I don’t use opencore since my GPU is flashed with a vBIOS and I can have the native boot picker if I hold option during boot.

What would be the benefit of opencore in my system? Will I be able to use OTA in the future to install 11.3 when it becomes available?

If I choose to install opencore could I still boot my iMac without the USB and insert it only if I need an OTA update?

With my current system if I reset PRAM I have to insert the patched USB and select EFI Boot to be able to boot again. Is this option available (EFI Boot) with the opencore installation on the same USB? What should I do after a PRAM reset to be able to boot again without the USB?

I read that after installation we have to run config-opencore.sh. Do we run this after patch-kexts.sh or instead of patch-kexts.sh?
Click to expand...
Some facts:
  1. iMac 2009 and 2010 cannot run Big Sur without OC
  2. iMac 2011 with AMD cards will not get the AMD GPU hardware features enabled without OC
  3. iMac 2011 with K610M, K1100M, K2100M will not get brightness control without OC
  4. only a few NVIDIA cards in the 2011 run Big Sur without OC
  5. NO iMac will get OTA in future without OC
Putting it all together it was my choice to make it the standard to use OC from now on.

If you opt out you may use install-servars.sh and the —nikey22 command line option with the patch-kext.sh

In case you will use OC run configure-opencore.sh after patch-kext.sh and before rebooting.

After a PRAM reset you have to follow the same procedure - only difference is that the system does not switch off, it just starts another boot selector from where you select the Big Sur installation disk.

If you have a dual installation setup select the other macOS installations without OC! Sleep will be broken otherwise.

—

I am pretty sure the existing documentation describes all this in exactly the same way.
 
  • Like
Reactions: webg3
  • Like
Reactions: Rob1n
Dayo said:
@cdf based minimal approach does not involve spoofing such items.

It involves the least amount of spoofing possible. This has been dubbed "hybridisation" and this is basically all a real Mac needs.

I believe you use the OCLP which is the polar opposite. Perhaps a reflection of the Hackintosh roots.
Click to expand...
Okay, I appreciate my comments are 100% based off OCLP and OpenCoreAPFSLoader. Where is the link to the @cdf approach? (It's not in the list on the first page, right?) I am definitely interested in this, and more generally in trying to work out what the most minimal OC setup is for my Mac (or for any Mac).
 
Bmju said:
Okay, I appreciate my comments are 100% based off OCLP and OpenCoreAPFSLoader. Where is the link to the @cdf approach? (It's not in the list on the first page, right?) I am definitely interested in this, and more generally in trying to work out what the most minimal OC setup is for my Mac (or for any Mac).
Click to expand...
forums.macrumors.com

OpenCore on the Mac Pro

This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.
forums.macrumors.com forums.macrumors.com
 
  • Like
Reactions: AlexSakha67 and Bmju
RogueB said:
Installation of Big Sur 11.2 on Macbook Pro 5,2 (mid 2009)
...
defaults write NSGlobalDomain NSAutomaticWindowAnimationsEnabled -bool NO
...

Hope this post is of help.
Click to expand...
Thanks for reporting your positive experience of installing and using BS on MBP5,2.
I also have an MBP5,2 and definitely disabling animations helps for a usable (if slow) BS on that machine.

Barry K. Nathan's micropatcher contains in the payloads the script disable-animations.sh, described in his readme as point 19, contributed by johncaling40.
I am using a copy of this (also in Catalina) and have now added the command you found. Works well. - Other change: commented out the DisableAllAnimations for the Finder to see where things go when closing a Finder window.
Modified script attached.
 

Attachments

  • Bildschirmfoto 2021-02-07 um 18.03.59.png
    Bildschirmfoto 2021-02-07 um 18.03.59.png
    184.8 KB · Views: 75
  • disable-animations-mod.sh.zip
    1.1 KB · Views: 106
  • Like
Reactions: RogueB, AlexSakha67 and Ausdauersportler
Bmju said:
Where is the link to the @cdf approach?
Click to expand...
You know this:
forums.macrumors.com

OpenCore on the Mac Pro

This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.
forums.macrumors.com forums.macrumors.com

It is targeted at MacPro5,1 running a specific type of GPU and with a specific BootROM andCPU

The OpenCore implementation in MyBootMgr (my signature below) is based on this with some deviations such as explicitly defining all the required failsafe values and being automated, caters for a wider set of machines, I use a MacPro3,1 for instance, GPUs, CPUs and BootROMs. Plan to expand the coverage further with a Tier 2 Support List leveraging the OCLP.

That main OC Thread however, is the source of most OpenCore on Mac impementations apart perhaps from the OCLP.
 
Last edited:
  • Like
Reactions: AlexSakha67 and Bmju
@Ausdauersportler Thanks again for your answer.
I think I will stuck with the install-servars.sh method for now because my GPU works without OC and there is no way to have brightness control. In the future I might try OC to enable OTA.

I didn't use the --nikey22 command with 11.1 and micropatcher 0.5.1. In the docs I read that its deprecated. Should I try it?

I have an issue with the bootable disk.
I decided to make a clean install of High Sierra on my secondary internal disk because it wasn't able to boot. It's installed fine but after booting in High Sierra and restarted with option key I noticed that I don't have "Macintosh" as an option (my primary disk with Big Sur) but it shows "Macintosh - Data".
If I select "Macintosh - Data" it boots fine in Big Sur.
In High Sierra there is no Macintosh as an option in System Preferences > startup disk.
In Big Sur I can see Macintosh in System Preferences > startup disk but if I select it and click restart I get this error:
Screenshot 2021-02-07 at 20.43.05.png

These are my disks
Screenshot 2021-02-07 at 21.05.47.png

What could that mean and how could it be fixed?
 
Last edited:
johnrak said:
@Ausdauersportler Thanks again for your answer.
I think I will stuck with the install-servars.sh method for now because my GPU works without OC and there is no way to have brightness control. In the future I might try OC to enable OTA.

I didn't use the --nikey22 command with 11.1 and micropatcher 0.5.1. In the docs I read that its deprecated. Should I try it?

I have an issue with the bootable disk.
I decided to make a clean install of High Sierra on my secondary internal disk because it wasn't able to boot. It's installed fine but after booting in High Sierra and restarted with option key I noticed that I don't have "Macintosh" as an option (my primary disk with Big Sur) but it shows "Macintosh - Data".
If I select "Macintosh - Data" it boots fine in Big Sur.
In High Sierra there is no Macintosh as an option in System Preferences > startup disk.
In Big Sur I can see Macintosh in System Preferences > startup disk but if I select it and click restart I get this error:
View attachment 1726632
These are my disks
View attachment 1726634
What could that mean and how could it be fixed?
Click to expand...
High Sierra cannot understand Big Sur APFS containers and Big Sur cannot be used to set some older startup disks. Use alt/option on boot.

-nikey22 is to be used with 0.5.4 and later just to enable a installation not using OC
You can use 0.5.1, but you will not get updates and new feature unless @Barry K. Nathan continue to work. We have no access to his repository. So no Night Shift etc...
 
  • Like
Reactions: hvds
Ausdauersportler said:
High Sierra cannot understand Big Sur APFS containers and Big Sur cannot be used to set some older startup disks. Use alt/option on boot.ra

-nikey22 is to be used with 0.5.4 and later just to enable a installation not using OC
You can use 0.5.1, but you will not get updates and new feature unless @Barry K. Nathan continue to work. We have no access to his repository. So no Night Shift etc...
Click to expand...
I use alt/option on boot but for some reason it shows the data volume (Macintosh - Data) after booting once in High Sierra. I reinstalled 11.1 and it got fixed but after booting in High Sierra I see again the data volume in boot picker.

Update: I created a USB installer for 11.2, restarted with option key and I saw the Macintosh volume again instead of Macintohc-Data. I don’t know how but it’s fixed. I will update to 11.2 using micropatcher 0.5.4 without opencore. Thanks for your help.
 
Last edited:
  • Like
Reactions: Ausdauersportler
johnrak said:
With my current system if I reset PRAM I have to insert the patched USB and select EFI Boot to be able to boot again. Is this option available (EFI Boot) with the opencore installation on the same USB? What should I do after a PRAM reset to be able to boot again without the USB?

I read that after installation we have to run config-opencore.sh. Do we run this after patch-kexts.sh or instead of patch-kexts.sh?
Click to expand...
Use OpenCore 0.6.6 on EFI System partition internal


Post in thread 'macOS 11 Big Sur on Unsupported Macs Thread' https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-29582758
 
johnrak said:
I was thinking to install 11.2 on my iMac. I have downloaded the 12GB file and created the USB installer. I see that @Ausdauersportler micropatcher 0.5.3 has an option to install a preconfigured opencore in USB by using install-opencore.sh instead of install-setvars.sh.
At the moment I don’t use opencore since my GPU is flashed with a vBIOS and I can have the native boot picker if I hold option during boot.

What would be the benefit of opencore in my system? Will I be able to use OTA in the future to install 11.3 when it becomes available?

If I choose to install opencore could I still boot my iMac without the USB and insert it only if I need an OTA update?

With my current system if I reset PRAM I have to insert the patched USB and select EFI Boot to be able to boot again. Is this option available (EFI Boot) with the opencore installation on the same USB? What should I do after a PRAM reset to be able to boot again without the USB?

I read that after installation we have to run config-opencore.sh. Do we run this after patch-kexts.sh or instead of patch-kexts.sh?
Click to expand...
Try —whitelist to enable your BCM94331CD
 
Hi, All,
Thanks to Patcher Sur, since I updated from MP on mac10,1, there existed unknown error from connecting to my iPhone personal hotspot. Then I updated directly from 11.1 to 11.2 by Patcher Sur, and after post patched, everything works fine now. Wireless to hotspot, handover, etc. are working smoothly.
Thanks everyone in this forum for your information, and thanks to those who are working on the unsupported patchers.
May you have a happy lunar new year.
😄
 
Folks - day 2 of Big Sur on 27" iMac 2011 w/ NVIDIA GTX860M and dev-v0.5.4+patch-kexts.sh --nikey22

Videos in Apple TV and music videos in Music app have no image (black screen) but audio is playing.

Can someone give a quick note if this is expected?
 
electricimp123 said:
Hello to everyone - special thank you to @Ausdauersportler

Reporting successful upgrade to Big Sur on mid-2011 iMac 12,2.

Details:
27" iMac 12,2 (mid-2011) i7-2600
+ hardware upgrades:
- BCM94360CD (802.11 a/b/g/n/ac with Bluetooth 4.0 Upgrade Kit from osxwifi)
- SSD 960GB OWC Mercury Extreme Pro 6G SSD 7MM (OWC)
- Graphics card NVIDIA GeForce GTX860M by nikey22

Used @Ausdauersportler dev-v0.5.4 fork of big-sur-micropatcher to do an in-place Upgrade from High Sierra (not clean install):
Followed this thread's instructions:
Steps: 1, 2, 3, 4, 5, 6, 7, x, 9, 10, x, x, 13, x
(Did not have to do Step 14 because when I came back to the iMac it was already on the Big Sur login page!)
(Logged in, everything seemed to work at this stage and I couldn't find anything wrong, but I proceeded)
Steps: 15
(did it without rebooting, just using terminal when I was logged in after Step 13)
(only flag I used was: patch-kexts.sh --nikey22)
Reboot
That's it

It was overall extremely painless and frankly everything worked right out of the box with no shenanigans. I was surprised that I did not have to deal with Setup Assistant but I am guessing this is because I did an upgrade not a fresh install.
Click to expand...
Did you get night shift working?
 
Ausdauersportler said:
Try —whitelist to enable your BCM94331CD
Click to expand...
I tried it but there might be some syntax error. It patched IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist but it didn't patch AirPortBrcm4360 and AirPortBrcmNIC. I had to patch them manually.
In patch-kexts.sh there is an echo before patching those two files:
echo 'patching IO80211Family.kext for Continuity and HandOff for board-id ' $MYBOARD
but it's not shown in the log.

I notice that after setting ContinuitySupport true, RESULT is changing and the script is checking again the same statement before patching the other two files if [ "x$RESULT" = "xfalse" ]. So it doesn't execute the commands between 937-949 lines.
 
  • Like
Reactions: Ausdauersportler
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back