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.
Clean install macOS Moterey 12.3 with OpenCore Legacy Patcher 0.4.3, all went well.
There are no more GPU glitches.
Intel HD Graphics 4000

MacBook Air 11" 2012 4GB

run Windows 11 Pro (Bootcamp) 250GB
run macOS Monterey 12.3 (OCLP) 750GB

Thank You very much to everyone involved in this Project.
 
MrMacintosh confirmed over Reddit chat that Migration Assistant (ether before or after Monterey upgrade) is problematic.

Screen Shot 2022-03-30 at 08.14.56.png
 
Last edited:
Running All My studio with my Daw Cubase pro 12 and all my plugs in under Monterey on My Mac Pro 2010 12 cores 3,46 ghz + 128 Go ram + Radeon 580 Sapphire pulse Mac + U25 Inateck USBC USB 3 card 4 NVME Samsung on Highpoint 7101 A NVME CARD + Titan ridge V2 flashed with V47 Apple firmware for my Apollo Silver thunderbolt 2 + Satellite Quad Thunderbolt 2 Wifi and Bluetooth Module Updated to V4

Using OCLP 043 + SSDT Titan Ridge injected in Package

Just an Automatic reboot and Everything works Great
 
MrMacintosh confirmed over Reddit chat that Migration Assistant (ether before or after Monterey upgrade) is problematic.

View attachment 1983357
For me the following always worked well when doing a clean installation, with fully taking over data/settings/etc from a previous macOS.
1st make a CCC clone to an erased disk; 2nd do the installation of macOS on it.
Here the macOS installation has the "last word", while when using Migration Assistant, the latter.
I did have problems with Migration Assistant several times before.
 
  • Like
Reactions: TimothyR734
For me the following always worked well when doing a clean installation, with fully taking over data/settings/etc from a previous macOS.
1st make a CCC clone to an erased disk; 2nd do the installation of macOS on it.
Here the macOS installation has the "last word", while when using Migration Assistant, the latter.
I did have problems with Migration Assistant several times before.
what works for me is simply doing a fresh install, then use CCC to clone ONLY the Data Volume.
No need for Migration Assistant if you on the same macOS.
Cheers
 
what works for me is simply doing a fresh install, then use CCC to clone ONLY the Data Volume.
No need for Migration Assistant if you on the same macOS.
Cheers

I don't need to clone my Data, since I can simply transfer that from my manual backups (or Time Machine). What I need is the system settings, so I don't have to set all my network connectivity and passwords.

I'm still on the testing phase, Adobe apps are launching okay, but I have to do live file tests where I edit files and do saves.
 
^^^ Thank you very much for your post, which made me search for the broken seal issue on Google; and I found this (very interesting):


… where it is suggested, in order to enable SIP as much as possible after root patching, to only disable the “autenticated root”, thus leaving SIP almost completely enabled - and, well… it worked! So, I reconfigured SIP in this way, on my already root patched MacBookPro11,3:

View attachment 1981367

… and then rebooted without problems; now also with TCC fully working again, while csrutil status shows up as enabled in the Terminal (and SilentKnight, too, shows SIP as enabled and only SSV as disabled). So, it is indeed possible to boot a root patched MacBookPro11,3 with SIP almost completely turned on and thus also with a fully working TCC: very good, indeed! I’ll of course experiment a little more, still only from an external SSD, also to see if there are any other issues: sofar, everything seems to work well, with SIP enabled and SSV disabled… :cool::)
Don't know, if these results are of importance to anyone:

MBP9,1 Monterey/MBP10,2 Big Sur: Ok.
MPB8,1/6,2 Big Sur: Both failed to boot. Rebuilt and installed OpenCore by USB Pen Drive with standard settings.
 
  • Like
Reactions: TimothyR734
Succesfully updated my Macbook Pro 17" 2011 from 12.2.3 to 12.3. Everything works like a charm.
 

Attachments

  • Captura de Pantalla 2022-03-31 a las 10.03.53.jpg
    Captura de Pantalla 2022-03-31 a las 10.03.53.jpg
    82.8 KB · Views: 85
  • Like
Reactions: hvds
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.