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.
My iMac late 2012, 13,1 is configured to dual boot into two different versions of macOS. The fusion drive runs version 11.2 at the moment and 11.2.1 has just been installed on an external HDD drive using BKN's patcher version 0.5.1. The installation went smoothly, if rather slowly, via USB. Patch-kexts.sh restored the WiFi functionality.
Safari does not run and generates the attached error that the Safari version is not compatible with macOS 11.2.1, The Safari version is 14.1 compared with 14.03 that runs without problems under macOS 11.2.
Has anybody else seen this problem?
You may have installed the latest beta Safari, I was tempted to but it didn't like BS 11.2.1. This is my Safari version that does work with BS 11.2.1-
1613777499477.png
 
Last edited:
I can confirm micropatchautomator from @moosethegoose22 working with 11.2.1 and 11.3 Beta 2.....11.3 beta 2 on my Mac Pro 4,1 flashed to 5,1 perfectly 100% working....just some minor sleep issues but that might be related to some of my software that was moved from my Catalina partition which was my upgrade path and I can also confirm that 11.3 beta 2 and 11.2.1 duel booted on a 2012 15 MBP working flawlessly. Ill do further testing and report back........ps stock bluetooth and wifi on the 4,1 Mac Pro works beautifully under his patcher as well!
 
I can confirm micropatchautomator from @moosethegoose22 working with 11.2.1 and 11.3 Beta 2.....11.3 beta 2 on my Mac Pro 4,1 flashed to 5,1 perfectly 100% working....just some minor sleep issues but that might be related to some of my software that was moved from my Catalina partition which was my upgrade path and I can also confirm that 11.3 beta 2 and 11.2.1 duel booted on a 2012 15 MBP working flawlessly. Ill do further testing and report back........ps stock bluetooth and wifi on the 4,1 Mac Pro works beautifully under his patcher as well!
You are the first to confirm success using BarryKN's micropatcher (current ReadMe for Automator-for-BarryKN-Micropatcher says it uses BarryKN's version 0.5.1 micropatcher) to process 11.3 beta 2 (build 20E5186e).

If anyone else has had success please let us know. Thanks
 
  • Like
Reactions: iciconnect
Download the pkg, install it. After installed go to Applications folder, right click the "Install macOS Big Sur Beta" and click "Show Package Contents" then open "Contents" folder, then "Resources" folder. Open terminal and type sudo with a space after it, then drag the "CreateInstallMedia" from the Resources folder into the terminal window. Put a space and then write --volume with a space after that, then drag your Flash drive (USB stick or whatever) into the terminal window and hit enter, that's it. If you're using the multi patcher don't forget to patch the flash drive after it's done.

This is how you create a bootable installer from a pkg, but keep in mind if you are trying to create a bootable installer with 11.3 beta 2 you might run into an error like I did that said the installer was damaged (not sure why because this never happened to me before with any betas or regular releases). I had to instead make a bootable 11.3 beta 1 installer and use opencore to update to 11.3 beta 2 successfully.



Same thing happened to me with 11.3 beta 2 after making a bootable installer, when I was about to install it it told me the installer was damaged. I had to install 11.3 beta 1, then update to 11.3 beta 2 with opencore.
Two pages back the micropatcher 0.5.1 worked with the 11.2.1 - so something you may have missed.
Thank you very much, i did exactly the same as your tutorial, and of course, as you say,i had the installer damaged error
Two pages back the micropatcher 0.5.1 worked with the 11.2.1 - so something you may have missed.
I was talking about 11.3 beta 2
 
  • Like
Reactions: Dr_T
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, @ASentientHedgehog 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.
Hi! If I add this to Barry's 0.5.1 patcher in order to install the 11.3 beta 2 might work? Thanks!
 
Thank you very much, i did exactly the same as your tutorial, and of course, as you say,i had the installer damaged error

I was talking about 11.3 beta 2
Go back three posts. There is currently no evidence that the micropatcher is broken if you get an „installer damaged“ error. Just wanted to make sure that you do not claim things which are unproven, yet. Your posts are persistent and may confuse others.

A message like „I have problems with Big Sur X and micropatcher Y„ will describe the true situation much more appropriately.
 
  • Like
Reactions: David403
Hi! If I add this to Barry's 0.5.1 patcher in order to install the 11.3 beta 2 might work? Thanks!
Please just download and test again or change the USB device. The micropatcher 0.5.1 works fine with this version of Big Sur according to this post.

Edit:
Even @dosdude1 put a warning like this on his own download page. Downloading 12GB of data and creating an USB installer is not a complete error free process. A single bit flip may cause such problems and the file systems we use cannot detect such problems (unlike ZFS and possibly the new APFS).
 
Last edited:
  • Like
Reactions: David403
Go back three posts. There is currently no evidence that the micropatcher is broken if you get an „installer damaged“ error. Just wanted to make sure that you do not claim things which are unproven, yet. Your posts are persistent and may confuse others.

A message like „I have problems with Big Sur X and micropatcher Y„ will describe the true situation much more appropriately.
Ok, sorry but...relax, no need to be so aggressive
 
Please just download and test again or change the USB device. The micropatcher 0.5.1 works fine with this version of Big Sur according to this post.

Edit:
Even @dosdude1 put a warning like this on his own download page. Downloading 12GB of data and creating an USB installer is not a complete error free process. A single bit flip may cause such problems and the file systems we use cannot detect such problems (unlike ZFS and possibly the new APFS).
HI! Just tried again downloading the installer and the 0.5.1 patcher and when trying to install got the same error... The USB I am using is new... Do you have by any chance a link for the installer? Appreciated...

I just want to mention that up to now I have never had any issues updating to a new version of BS betas. Thank you.
 
Last edited:
Hi all

I can confirm that I have successfully installed 11.2.1 with Barry's micropatcher 0.5.1 since 5 days and all is working well.

Capture d’écran 2021-02-16 à 17.15.13.png

I also wrote a script to automate some tasks:
To check if SIP is disabled
To mount snapshot to RW access
To replace "CoreBrightness.framework" (thanks @jackluke) to get functional NightShift,
To disable Library Validation
To add cMP5,1 board ID with PlistBuddy in "SystemParameters.plist" into "IOBluetooth.framework" to get Continuity
To add cMP5,1 board ID with PlistBuddy in "Info.plist" into "AppleGVA.framework" to enable H264 Hardware acceleration
To create "com.apple.AppleGVA" to enable H264 Hardware acceleration
To add cMP5,1 board ID with PlistBuddy in "/S/L/CoreService/PlatformSupport.plist"
To add cMP5,1 board ID with PlistBuddy in "PlatformSupport.plist" on PREBOOT Volume
To copy 2 ringtones for Message & FaceTime in "/S/L/PrivateFrameworks/ToneLibrary.framework/Versions/A/Resources/Ringtones/"
To add 2 ringtones for Message & FaceTime with PlistBuddy in "TKRingtones.plist" into "ToneKit.framework"
To create a new snapshot
To restart automatically after executing all these tasks

Capture d’écran 2021-02-16 à 17.17.23.png
 
Last edited:
Download the pkg, install it. After installed go to Applications folder, right click the "Install macOS Big Sur Beta" and click "Show Package Contents" then open "Contents" folder, then "Resources" folder. Open terminal and type sudo with a space after it, then drag the "CreateInstallMedia" from the Resources folder into the terminal window. Put a space and then write --volume with a space after that, then drag your Flash drive (USB stick or whatever) into the terminal window and hit enter, that's it. If you're using the multi patcher don't forget to patch the flash drive after it's done.

This is how you create a bootable installer from a pkg, but keep in mind if you are trying to create a bootable installer with 11.3 beta 2 you might run into an error like I did that said the installer was damaged (not sure why because this never happened to me before with any betas or regular releases). I had to instead make a bootable 11.3 beta 1 installer and use opencore to update to 11.3 beta 2 successfully.



Same thing happened to me with 11.3 beta 2 after making a bootable installer, when I was about to install it it told me the installer was damaged. I had to install 11.3 beta 1, then update to 11.3 beta 2 with opencore.
Hi! Do you have by any chance a link for 11.3 beta 1? Thank you.

 
Last edited:
You may have installed the latest beta Safari, I was tempted to but it didn't like BS 11.2.1. This is my Safari version that does work with BS 11.2.1-
View attachment 1732505
Not sure where the Safari beta came from; was probably with a beta of Big Sur. The HDD was installed so that various software could be installed without risking unwanted changes to the fusion drive. The HDD was reformatted and now runs Big Sur 11.2.1 and Safari 14.03 without problems.
 
  • Like
Reactions: cab_007
HI! Just tried again downloading the installer and the 0.5.1 patcher and when trying to install got the same error... The USB I am using is new... Do you have by any chance a link for the installer? Appreciated...

I just want to mention that up to now I have never had any issues updating to a new version of BS betas. Thank you.
Hi everyone.
I'm running smoothly Big Sur 11.2.1 (20D75) on my MBPr mid 2012, but when I tried to install BS 11.3 beta 2 I got the same error as furdi (EDIT: I meant using micropatcher 0.5.1). No errors are prompted while patching the USB drive. I downloaded BS via gibMacOs.
1613827696752.png
 
Last edited:
I was wondering, what were you thinking of? Specifically, what is it that is putting you off using it on your MacBook Pro, especially if you're already familiar with it?

I wonder, it may be because there's a perception (I believe, incorrect!) that OpenCore is somehow more hacky, because it comes from the Hackintosh universe?

Don't forget:
  • OpenCore is an incredibly clean and well-written program
  • In the end, either approach has to change something (and the more, the more incompatible your machine is - you have a very compatible machine)
  • The basic key to fixing any larger incompatibilities (i.e. using non-Apple kexts, and patches) is the *same* in both OC and in the micropatcher, and also in the legacy Mac and the Hackintosh world!
  • So it's not OC that makes your unsupported Mac partially a Hackintosh - in some sense - it's that you're running an unsupported OS on it. (Already!)
  • The clearest difference between OC and a patcher is that, in OC, any changes are not permanently applied to the OS on the disk, i.e. 'patching', but instead are applied by 'injection': any changes needed are applied on the fly, as you boot up, from the completely clean, unmodified OS which remains on disk (this is NOT the case, in the patcher)
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.)

I've just installed BS 11.2.1 on my Non-Retina Unibody MBP Mid-2012, using the OCLP method. I also manually upgraded the physical wifi card to 802.11ac like you. I was therefore wondering, for someone who wants as minimal a patch as possible, where do I find the @jackluke config you've talked about? And is it a case of just placing the jackluke config in place of the one generated during the OCLP process?
 
hmmmm not sure I used micropatchautomator from @moosethegoose22 and 11.3 beta 2 installed no problem. I did have the same issues you guys were having......instead of dragging the patcher to the hard drive in the applications folder......I ran it directly from the dmg.. . and it worked.....once the dmg Is mounted I right clicked micropatchautomator and hit open and it created the installer and Installed no problem on Mac Pro 4,1 flashed to 5,1
 
  • Like
Reactions: David403
I've just installed BS 11.2.1 on my Non-Retina Unibody MBP Mid-2012, using the OCLP method. I also manually upgraded the physical wifi card to 802.11ac like you. I was therefore wondering, for someone who wants as minimal a patch as possible, where do I find the @jackluke config you've talked about? And is it a case of just placing the jackluke config in place of the one generated during the OCLP process?
I'd currently recommend the p.1 config from the OpenCore on the MacPro thread if you have a machine like this. It's designed for the MacPro, but it's a very clean OC config. As far as I'm currently aware, the only really MacPro specific settings are to do with making the OC boot menu work on the MacPro (i.e. you don't really need to change them back). You should just need their basic config.plist (i.e. the one from the Basic settings on that page) but without what they call the VMM setting and with what they call hybridization (i.e. read through Advanced settings to find out about those, but there are only those two small changes which you need to make to the basic file). Use that file with the matching OpenCore download mentioned on the same page, of course (currently 0.6.6 - but the config may change - slightly - as new OC versions are released).
 
Last edited:
Hi all

I can confirm that I have successfully installed 11.2.1 with Barry's micropatcher 0.5.1 since 5 days and all is working well.

I also wrote a script to automate some tasks:
To mount snapshot to RW access
To replace "CoreBrightness.framework" (thanks @jackluke) to get functional NightShift,
To add cMP5,1 board ID with PlistBuddy in "SystemParameters.plist" into "IOBluetooth.framework"
To get functional Continuity, to add my cMP5,1 board ID with PlistBuddy in "Info.plist" into "AppleGVA.framework" to enable H264 Hardware acceleration
To add cMP5,1 board ID with PlistBuddy in "/S/L/CoreService/PlatformSupport.plist"
To add cMP5,1 board ID with PlistBuddy in "PlatformSupport.plist" on PREBOOT Volume
To create "com.apple.AppleGVA" to enable H264 Hardware acceleration
To copy 2 ringtones for Message & FaceTime in "/S/L/PrivateFrameworks/ToneLibrary.framework/Versions/A/Resources/Ringtones/"
To add 2 ringtones for Message & FaceTime with PlistBuddy in "TKRingtones.plist" into "ToneKit.framework"
To create a new snapshot
To restart automatically after executing all these tasks

View attachment 1732663
Nice! This has already been added to iMac micropatcher fork which is a suitable alternative to go...
 
Anyone encountering problems or oddities with a 2012 iMac 27" Core i7 680MX 2GB?

Is Big Sur 11.2.1 so much better than Catalina 10.15.7 or Mojave 10.14.6?
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.