Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
Thank you for your answer, I expressed myself badly (not very good in English, I must say...).

I redid the snapshot and erased the old one several times with the same result in the end, either directly under my session or via recovery.
 
Thanks but i want make a clean install :-(
You can also use the MicropatcherAutomator. It uses the same patcher core and offers a GUI supported from 10.11 on and offer a clean install, too. I have added manually my update fork to it, but did not find a suitable place to upload. Possibly i will fork it, too.
 
MBP 9,2 non-retina display, with opencore legacy 0.0.9 and OC 0.6.6 working fine macOS Big Sur 11.2 (20D53) until now the only problem is with boot-camp win10 audio not working all of the rest is perfectly working.
 

Attachments

  • 11.2.jpg
    11.2.jpg
    308.4 KB · Views: 123
OpenCore 0.6.6 with MaxBIOSVersion = true successfully stopped my MacBookPro10,2 from entering the black-screen semi-brick state during the latest update to Big Sur 11.2 RC.

I double-checked and would say it definitely is the new flag which is making the difference; without it the update still semi-bricks.



With many thanks to @naylom11, @khronokernel, @jackluke, @h9826790, @vit9696 and all the many other people working on this for letting me and many others enjoy Big Sur! 😊
 
You cannot boot to recovery partition for Dosdude Catalina. The recovery partition isn't patched, therefore, your cMP is not supported, and can't boot to it. This is the expected behaviour.


Is access to SAFE MODE affected by the patch?. I cannot get into safe mode.


Thank you.
 
MBP 9,2 non-retina display, with opencore legacy 0.0.9 and OC 0.6.6 working fine macOS Big Sur 11.2 (20D53) until now the only problem is with boot-camp win10 audio not working all of the rest is perfectly working.
How did you do it? Can you share what instructions you followed, if any? I tried an MBP9,2 just yesterday using opencore legacy patcher 0.0.9 (OC 0.6.6) and it stopped even booting to Catalina, instead giving an immutablekernel error. Thanks so much in advance.
 
Sounds on my Mac keeps vanishing (turns gray on control center).. its goes back and forth without a reason..

iMac 27 2011 K610M OpenCore 0.6.4 Micropatcher 0.5.1

Has anybody gone through something like that?
Whenever it happened again try the next:
1. Open System monitoring
2. Find coreaudiod process under Memory tab
3. Double-click on it and choose Close and then Close Force
4. Process would restart, and disappeared sound device(s) are back
 
Last edited:
Is access to SAFE MODE affected by the patch?. I cannot get into safe mode.


Thank you.
Safe mode is the patched OS itself, however, it won't load any extra kext.

So, if your Mac rely on the extra kext to run Big Sur, then highly likely it won't work either.
 
Safe mode is the patched OS itself, however, it won't load any extra kext.

So, if your Mac rely on the extra kext to run Big Sur, then highly likely it won't work either.
Due to the limitation on Macs with Metal GPU the vast majority to Big Sur users (on unsupported Macs) will be owners of 2012-2013 Macs which are mostly unpatched at all (unless an older WiFi cards need one). So booting into save mode should work for this majority of users if these enhance the plist as the attached one - somewhere on the thread or within the comments of the micropatcher issues I found the recipe and added it to this particular micropatcher release with option patch-kext.sh —saveboot.

Other uses may try this (based on the micropatcher scripts to patch a root volume) without reinstalling Big Sur:
Code:
me@myMac % /Volumes/Install\ macOS\ Big\ Sur/remount-sysvol.sh
Volume appears to have a Big Sur installation (build 20D5042d). Continuing.
Volume is mounted from device:  /dev/disk1s5s1
Mounted device is a snapshot. Will now mount underlying volume
from device /dev/disk1s5 at temporary mountpoint:
/System/Volumes/Update/mnt1
RECOVERY="NO";
WASSNAPSHOT="YES";
VOLUME="/System/Volumes/Update/mnt1";
SVPL_BUILD="20D5042d";
Dropping into subshell. Run 'exit' when done.
Don't forget to run either "$REBUILD_KC" (including quotation marks)
or: "/Volumes/Install macOS Big Sur/rebuild-kc.sh"
(copy and paste it, including the quotation marks)
before you exit.
me@myMac Extensions # cd ../CoreServices
me@myMac Extensions # mv PlatformSupport.plist PlatformSupport.plist.original
Now copy in the attached enhanced plist into exactly this directory...and enter then the following commands:
Code:
me@myMac Extensions # "$REBUILD_KC"
me@myMac Extensions # exit
me@myMac % sudo reboot

The drawback will be of course, the system becomes „patched“ now and you loose the clean root volume. Systems already patched will not change this state.
Since you made a backup of your original PlatformSupport.plist you may revert nearly to the former state or do a reinstallation.

After each OTA upgrade and/or new installation this change is gone.

Disclaimer:
1. Did not check this feature myself!
2. Please find an report back any typos in the script above :)
 

Attachments

  • PlatformSupport.plist.zip
    1.5 KB · Views: 138
Last edited:
How did you do it? Can you share what instructions you followed, if any? I tried an MBP9,2 just yesterday using opencore legacy patcher 0.0.9 (OC 0.6.6) and it stopped even booting to Catalina, instead giving an immutablekernel error. Thanks so much in advance.
I will share with you my EFI, I've just changed the serial number, a serial number of the motherboard, and UUID this you can use yours. Delete the content of your EFI and change by this one then boot from EFI and chose your Macbook HD.
To show EFI volume use EFImountainshow tool it's easy.
 

Attachments

  • EFI.zip
    9 MB · Views: 117
  • EFI MountainShow.zip
    64.8 KB · Views: 85
Micropatcher 0.5.3 using the integrated OpenCore option updated successfully (OTA) to Big Sur 11.2 (20D53). After completing the installation just called the patch script from the USB installer again:
Code:
/Volumes/Install\ macOS\ Big\ Sur/patch-kexts.sh --ns
The --ns just to enable Night Shift.

Big Sur 11.2.png


Edit: iMac 2010 and iMac 2011 updated the same way! Save your firmware before starting this :)
 
Last edited:
Micropatcher 0.5.3 using the integrated OpenCore option updated successfully (OTA) to Big Sur 11.2 (20D53). After completing the installation just called the patch script from the USB installer again:
Code:
/Volumes/Install\ macOS\ Big\ Sur/patch-kexts.sh --ns
The --ns just to enable Night Shift.

View attachment 1718188
Where can micropatcher 0.5.3 can be downloaded?
 
  • Like
Reactions: WT_
Where can micropatcher 0.5.3 can be downloaded?
First page, option #6 on the list. Follow the slightly changed docs and install opencore instead of servars. Which Mac you are going to use?
Alternatively you can use the OLP to create an opencore setup and use this. Please backup you firmware in advance. Read all docs available!
 
First page, option #6 on the list. Follow the slightly changed docs and install opencore instead of servars. Which Mac you are going to use?
Alternatively you can use the OLP to create an opencore setup and use this. Please backup you firmware in advance. Read all docs available!
Mac mini late 2012
 
Mac mini late 2012
I would give the OLP a try if I had a 2012/2013 system. Currently you only need a WiFi patch (if ever) and so the whole micropatcher machine is just used to make the installer boot your iMac. This can be achieved by the other method, too.
 
  • Like
Reactions: webg3
I don’t mind if it’s patched or if I need to switch to open core. The 760 is upwards of 200$ wich is more then what I have right now. Is there any cheaper ones? I saw someone say that a gt 710 is cheap and worked but I don’t think I can throw it in with my gt 120 and get Big Sur running better. Any idea if my 5670 works along with my gt 120 in Mac OS?
Amd and nvidia don’t like to play on the same seesaw. But I have an rx480 8gb which is flashe’d for boot option and a radeon VII. The 480 is an ideal card
 
You may just search this thread for an answer...or take option #6. There have been several posts about that and I will not start to cite myself here.
Hi there do you mean the patcher option 6 for iMac on the main post?

if so I had already done that that’s why I’m asking now about night shift as it does not enable it? I just need to know if possible or not?
 
Is there any reason Continuity and handoff would all of a sudden stop working? It was working fine yesterday and earlier today. After a reboot ti stopped working. Would these snapshots that BS does be affecting it?
 
Is there any reason Continuity and handoff would all of a sudden stop working? It was working fine yesterday and earlier today. After a reboot ti stopped working. Would these snapshots that BS does be affecting it?
Cant tell. But the first thing I would do, is to boot from a patched USB Installer and rerun the scripts. Micropatcher 0.5.3
 
  • Like
Reactions: nandor690
Cant tell. But the first thing I would do, is to boot from a patched USB Installer and rerun the scripts. Micropatcher 0.5.3
Normally software does not appear from the system, but the SMC can become confused and does not recognises hardware components on POST and so these cannot be used. I would recommend an SMC reset before touching software.

Do not touch snapshots! Unless you are an expert on APFS and know exactly what you are doing let the system unchanged.

Before doing a second run of the scripts on the micropatcher please unpatch the system first, i.e.: patch-kext.sh -u reboot and patch again patch-kext.sh your arguments like --ns. Use the full path to the patch script exactly as documented.
 
Last edited:
  • Like
Reactions: nandor690
I did it!!!!!!!! I finally got Catalina installed on my Mac Pro 5,1, dual cpu, with the gt 120 😂, its actually running better then Mojave (patched) at this rate. I’m going for the big win with Big Sur on this machine.
Yup! I also have a MacBook 5.1 (Aluminum Unibody) and I still haven't figured out if it would work well with Big Sur and, possibly, how to manage the patcher using the various flags.
My 5.1 works fine with Catalina, except that Safari extensions (ex: Downie, PullTube, 1Password, etc.) don't work!
In addition, applications often close multiple times when started and must be restarted many times before remaining open.
IMovie for Catalina also doesn't work and you need to use the macOS High Sierra version.
Apart from that, you are right that the MacBook 5.1 with Catalina works much better than Mojave and I hope to be able to install Big Sur soon too.
 
Hi!

There is a new development version dev-v0.5.3 of the micro patcher available.

Users of iMac11,x and MacBookPro6,x and iMac12,2 can use an integrated opencore configuration ready to install Big Sur on those machines and run it later including OTA upgrades. Please get @dosdude romtool and save your firmware in case something is going south.

Currently there have no further adjustments for other systems made. It is still based on the same 0.5.1 patcher core for all systems except iMac11,x and iMac 12,x.

  1. in step 7 use install_opencore.sh instead of install_setvars.sh to install an OpenCore 0.6.5 version to the EFI partition of the USB/SD/disk installer (verbose mode will be enabled during installation, it is chatty!)
  2. in step 9 boot the "Boot EFI" partition by pressing the CRTL (control key) when selecting it - now OpenCore starts with a simple boot picker and has become the default start object and select the Volume with the Big Sur Installer and follow the installation as usual
  3. at the end of step 15 now use configure_opencore.sh in the same way you did it with install_opencore.sh before to install a fitting config.plist for your iMac and GPU type (verbose mode will be disabled)
This way you have the opencore version on the USB installer and this way a recovery until we get this back in disk.

Some more notes:
  • It will be easy to add configurations for MacPro users with AMD RX480/RX580/Navi GPU using the config files provided on this thread.
  • MacbookPro 6.x users can now install Big Sur, but no adjustments have been made so far. These systems lack of the so badly needed Metal GPU anyway.
  • Using the opencore settings all other supported systems may enable OTA upgrades.
  • One can use the configure_opencore.sh to install opencore to the internal boot disk, too.
  • I chose the iMacPro1,1 ID to spoof because it is needed with the AMD GPUs and it does not hurt on other systems as far as I know. You can install special config files on your own or change it entirely and add extensions as you like. It is opencore as you know it.
  • DRM for AMD GPU users has been enables (experimental) through beta versions of Lilu and Whatevergreen.
Last but not least:
  • Before thinking about making experiments with the opencore (you would not need to reinstall Big Sur, just use your existing UBS installer as a opencore vehicle) please, please download the romtool (password rom) and backup your Mac firmware in advance!
  • Will make it a release after OC 0.6.6 has been published and I got some feedback.
  • Next project is to feed this version into the Automator or link it to Patched Sur.
Is it possible to apply this to an iMac late 2013? On that iMac everything works except OTA updates (it says that there is no updates, but I have 11.0.1, so 11.1 should be available).
 
I think the amount of patchers on the first post is starting to get really overwhelming and redundant...
Can I use the iMac micro-patcher on my mid-2012 MBP and will it support OTA updates?
 
Y'all think Linux QEMU KVM might be the answer for non-metal macs? Or would the higher amount of resources needed trump all the benefits of graphics acceleration?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.