OpenCore is now stable enough for legacy Macs (at least for Metal-capable ones) and OTA updates are smooth without issues.Micropatcher plus a full usb installer is a safe bet. Worked all the time on my mbp 9,2. Time to update 40 min in total.
OpenCore is now stable enough for legacy Macs (at least for Metal-capable ones) and OTA updates are smooth without issues.Micropatcher plus a full usb installer is a safe bet. Worked all the time on my mbp 9,2. Time to update 40 min in total.
Yes, but my guess is it will only work for a limited number of systems. We need to have a table of successful installations and a great start would be if everybody here on the thread add his system, the used patcher to his signatureOpenCore is now stable enough for legacy Macs (at least for Metal-capable ones) and OTA updates are smooth without issues.
Very good idea! I did it.Yes, but my guess is it will only work for a limited number of systems. We need to have a table of successful installations and a great start would be if everybody here on the thread add his system, the used patcher to his signature![]()
Did it! Now, I need to remember to keep it updated! As an aside: I'm not sure if all users know where and how to access their signature. Also, it may be useful to list in your signature if not successful, briefly describe problems.... We need to have a table of successful installations and a great start would be if everybody here on the thread add his system, the used patcher to his signature![]()
I'd skip BS at the moment on all machines that have no metal-capable GPUs (graphics), and the Nvidia in the 7,1 is such a case. You can install and patch BS on it, but everything is laggy as h*ll...Hi friendly guys,
I do have a question but i cant really find the answer to it on this tread , i have a macbook pro 7,1 (MacBook Pro (13-inch, Mid 2010) , now i saw that this model is potentialy is patchable , but i dont see any clear answers to this , could anyone give an conclusive anwser , my macbook is now running DosDude1 Catalina without any problems.
Would love to run Big Sur but if its not possible in a good way i will keep using Catalina
Thanks guys!
Thank you for your fast respons on my question !I'd skip BS at the moment on all machines that have no metal-capable GPUs (graphics), and the Nvidia in the 7,1 is such a case. You can install and patch BS on it, but everything is laggy as h*ll...
I did not see this problem but it did take 7 or 8 attempts to get a booting 11.2 system on a cMP3,1. The bigmac2 installer is an early alpha2 so hiccups are to be expected. One major issue was a 1-hour wait at the message at the end of the install phase that said something like "1 minute remaining..." After waiting 1 hour, it proceeded to the next phase where I could reboot bigmac2 for the postinstall. The final solution to reach a booting cMP, was unchecking the AMD patch (left side of postinstall patch screen, 4th checkbox down) in the postinstall phase b/c I have a GTX 680 video card with boot screens (h/w described in signature) Kudos to StarPlayrX.Found out that with Big Mac 2 (alpha 2) it's already possible to install macOS 11.1 (or newer) onto a cMP3,1 - if you work around one nasty bug that's preventing the post install patching...
The destination drive is not visible for post-install patches in the Big Mac GUI. Seems to be blanked out because it is also named "bigmac2" (like the installer volume). Once you mount the volume on a running system and rename it to something else (i.e. BigSurSSD), it is then selectable for post patching.
As StarPlayrX does not seem to be around here, I´ve "PayPal-donate-messaged" him about it so that it can be changed in later alpha or beta releases of the quite useful tool...
You can reach starplayrx on github, go to his page and then the issues tab: https://github.com/StarPlayrX/bigmac/issuesFound out that with Big Mac 2 (alpha 2) it's already possible to install macOS 11.1 (or newer) onto a cMP3,1 - if you work around one nasty bug that's preventing the post install patching...
The destination drive is not visible for post-install patches in the Big Mac GUI. Seems to be blanked out because it is also named "bigmac2" (like the installer volume). Once you mount the volume on a running system and rename it to something else (i.e. BigSurSSD), it is then selectable for post patching.
As StarPlayrX does not seem to be around here, I´ve "PayPal-donate-messaged" him about it so that it can be changed in later alpha or beta releases of the quite useful tool...
Instead of CCC and SD, this does the job:So I got really mad and tried again with 11.2. Of course it didn’t want to boot.
I grabed Amfeltec board installed Intel Optane NVME M.2 drive on it and installed patched Big Sur 11.2 on nMP. Then moved M.2 back to Mac Pro 5,1, patched kexts and all worked well.
But then another problem showed up – there is no way to clone Big Sur partition from M.2 to SATA SSD I use for Big Sur. SuperDuper fails, Carbon Copy Cloner fails too.
So I borrowed SATA to USB 3.0 chassis and installed patched Big Sur on destination SATA SSD on nMP. Then moved back to cMP. It worked again, even Wi-Fi 802.11n works too.
It seems Big Sur is making some kind of verification of the hardware and if it's not supported then installer will simply reboot, even on patched installation.
I have Big Sur 11.1, installed with the micropatcher, on my mid 2012 MacBook Pro 9,2. Maybe I missed it in the thread or elsewhere but am I able to do system updates OTA or do I have to create a new installer for 11.2 etc? Any help/info would be great...thank you!
Perfect, thanks for the info! 👍create a new installer for 11.2
OTA only OpenCore 0.6.6 or 0.6.7
That won't work with a broken seal, just gives an error. You can still do it with the -toSnapshot switch, use diskutil apfs listsnapshots dev/diskid# to get the Snapshot ID and paste it inline with the rest of the command.Instead of CCC and SD, this does the job:
sudo asr -er -nov -s /Volumes/'yourSourceName' -t /Volumes/'yourTargetName'
Leave the ' and ' single quotes around the yourSourceName and yourTargetName
I loaded 11.2 on a 13" 2011 MBP and while minimizing the Safari app is painful, simply using CMD + H to hide the app is literally instantaneous (as are all other apps I tried). Is there a functional difference between clicking the yellow minimize button inside an app and using CMD + H to hide the app? The laptop seems quite usable with that one small change.No, they meant use dosdude1's Catalina patcher. He still hasn't made a patcher for Big Sur, and I doubt that he will. The graphics profformance issues are huge, a simple example would be minimizing safari which would normally take less than a second, however on your Mac it could take 14 seconds.
MBP9,2 mid-2012 non-retina, updated with opencore legacy 0.0.9 and manually updated OC0.6.7 working really fine no issues.
use this on your MacPro5.1 ...w works perfectIs it possible to do open core on my mac? Or would the patcher be my best bet
And if you use the Scale effect instead to Genie to minimize windows in Dock settings you'll have the same instant effect even with the yellow button...I loaded 11.2 on a 13" 2011 MBP and while minimizing the Safari app is painful, simply using CMD + H to hide the app is literally instantaneous (as are all other apps I tried). Is there a functional difference between clicking the yellow minimize button inside an app and using CMD + H to hide the app? The laptop seems quite usable with that one small change.
Thank you!use this on your MacPro5.1 ...w works perfect
![]()
Activate AMD hardware acceleration
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 1.0.0] For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in...forums.macrumors.com
my MBP 9,2 is not my daily driver so,I'm going to wait until apple stop releasing full installer before i switch to opencore, for now not worth bricking it imho.please post your way to use Big Sure with opencore (unpatched) on MBP9.2 ... at the moment i use patched sur ....but on my macpro5.1 i use opencore 0.6.6 fine. now i will switch on mbp9.2 to opencore ....without "patched sur".
i have uesed opencore-patcher 0.0.9 .... generated OC 0.6.6
the generated config.plist has a spoofing to MacBookPro11,1
Is the Spoofing to MacBookPro11,1 a future risk to corrupt my firmware of my MBP9,2?
How can i backup my Firmware on MBP9,2?
regards