Monterey 12.3.1 and OCLP 0.4.3 no issues.
Yes unpatch the root volume then install the update which should be around 2.7 GB to 3GB then once in your desktop apply the root patchesUpdated my MacBook Pro 2014 (MacBookPro11,3) to 12.3.1. Had to reinstall the Root Patches twice and safe boot because of the black screen after the upgrade. Before installing the Root Patches the first time the screen was black with just a cursor for a long time, ~5 minutes at least. After that it started up just fine.
I've read mixed results about the delta updates. Is there a trick to receive delta updates? I keep having to download the entire OS.
If you demand certainty buy a supported Mac, an unsupported machine is NEVER a sure thing but being wise and entitled, you know that? Being demoted to "Dude" while trying to help seemed very inappropriate, btw. And you can forget "bruh" as well. Another reason Migration Assistant fails is something on the source is hosed-up, incompatible with the Migration process. Apparently, you failed to notice others reporting success?Dude, don't assume it's THAT easy for anyone or everyone. If I had access to other Macs, I wouldn't have done it already myself. I don't post or comment here if I don't have to, and when I do, it's either to confirm, verify or add information, not grovel.
Again, thank you, but, you have not added any new or useful information I do not already know.
Wait... so it's possible for someone who didn't keep Catalina around to install it on an external drive and update firmware? (asking for a friend)
If you can, try to maintain a bare bones install of the last supported macOS version for your m/c. For me, that was Catalina, I guess we're in the same boat.
That way, if a security update to Catalina hits which contains a firmware update you can install it and keep your firmware up to date. You're probably thinking it's weird I totally agree with you. But that's what I had to do, and it does work, strangely enough.
You have A LOT of patience.If you demand certainty buy a supported Mac, an unsupported machine is NEVER a sure thing but being wise and entitled, you know that? Being demoted to "Dude" while trying to help seemed very inappropriate, btw. And you can forget "bruh" as well. Another reason Migration Assistant fails is something on the source is hosed-up, incompatible with the Migration process. Apparently, you failed to notice others reporting success?
Configure VM graphics settings to allways use discrete graphics if your machine has one.On 12.3.1 I still can't use VMware Fusion (or Parallels). VMware fails to start my VM with "error -14: Pipe connection has been broken".
This was no issue with Big Sur, and the VMware forums mention this is an issue with Intel GPUs. Is this an OCLP related issue or just some Monterey problem?
Headless VMs like with Docker Desktop still seem to work.
I wasn't demanding, I was ASKING. None of your responses were any help, because you keep insisting on things that re not possible for me or everyone else, and you could have just left it that that.If you demand certainty buy a supported Mac, an unsupported machine is NEVER a sure thing but being wise and entitled, you know that? Being demoted to "Dude" while trying to help seemed very inappropriate, btw. And you can forget "bruh" as well. Another reason Migration Assistant fails is something on the source is hosed-up, incompatible with the Migration process. Apparently, you failed to notice others reporting success?
Just to be sure: I have this bug on my non-metal Big Sur machines (MBP9,1 Monterey and MBP10,2 Big Sur are doing fine). Therefore I thought, that probably only an OCLP update could solve this. 🤔View attachment 1984410
So far, so good OCLP_043. Testing for the 1,200 second bug, now. 💪
🚧 AHOY! Messages still quits after 1200 seconds, bummer!!
That's not patience, that's insistence.You have A LOT of patience.
...or a partition or even a volume on your internal SSD as experience showsYou need an external USB drive or external SSD drive
As long as it is the original drive, right? I'd done a lot of testing, but only after I found the old HDDs and installed them or connected them via USB, I succeeded. I didn't try PRAM reset, though......or a partition or even a volume on your internal SSD as experience shows
A convenient place for getting macOS installers is e.g. hereWait... so it's possible for someone who didn't keep Catalina around to install it on an external drive and update firmware? (asking for a friend)
Maybe Mr Macintosh should add, that you only can download in the AppStore, what you "bought", when it was supported. If Catalina never was connected to your Apple-ID, you'll have to use one of the other ways.A convenient place for getting macOS installers is e.g. here
MrMacintosh has assembled links to the latest as well as older OSs, including Catalina, together with good description.How to Download macOS Sequoia, Sonoma, Ventura, Monterey, Big Sur, Catalina & Mojave Full Installers
How to download macOS Monterey, Big Sur, Catalina, Mojave, High Sierra, Sierra, El Capitan, Yosemite, Mavericks, Mountain Lion & Lion 7 ways!mrmacintosh.com
Yes, it occurs in Big Sur, as well. Effects all of the Catalyst apps, 1200 seconds to crash after launch, often the crashed app will not re-launch, Messages is the worst. Brought the topic up on Discord and was not warmly received. No end to this real drawback for us lowly non-Metal folks according to the developers, btw.Just to be sure: I have this bug on my non-metal Big Sur machines (MBP9,1 Monterey and MBP10,2 Big Sur are doing fine). Therefore I thought, that probably only an OCLP update could solve this. 🤔
"Dude", "snowflake," what's next - flinging poo? Please, get over yourself? This is a forum to provide useful discussion on unsupported Macs not antagonized those who intend to help. You can't or won't do what has been recommended, I get it. And please, take the subject and verb switching, name-calling "faction-speak" with you. 🐘I wasn't demanding, I was ASKING. None of your responses were any help, because you keep insisting on things that re not possible for me or everyone else, and you could have just left it that that.
Also, Dude is NOT a demotion, thinking that it is is such a snowflake response.
Anyway, I already thanked you, but it seems you're one of those who need to have the last word.
So you can have it.
To be blunt, this is not for you.If my installation fails, That's time lost I can never take back.
Right. Wife wanted MBA 11". Ebay said, why don't you buy MBA6,1 and MBP10,2 as a bundle. And if it hadn't been for the Catalyst problems, I might have said, what's wrong with my MBP8,1. But I didn't...Yes, it occurs in Big Sur, as well. Effects all of the Catalyst apps, 1200 seconds to crash after launch, often the crashed app will not re-launch, Messages is the worst. Brought the topic up on Discord and was not warmly received. No end to this real drawback for us lowly non-Metal folks according to the developers, btw.
Well maybe, maybe not. Collectively we've assembled a lot of knowledge in these unsupported Mac threads. You could write a book on this whole topic, it's a way bigger topic than the forum thread format allows. Oftentimes, we're working our way through issues as they arise, as are the OCLP developers. Sometimes the intermediate fixes we come up with are not the eventual best solution.To be blunt, this is not for you.
You: one Mac only and can't afford down time
Most here: multiple macs and can experiment; skilled enough to recover if something borks
Very valid and helpful points.Well maybe, maybe not. Collectively we've assembled a lot of knowledge in these unsupported Mac threads. You could write a book on this whole topic, it's a way bigger topic than the forum thread format allows. Oftentimes, we're working our way through issues as they arise, as are the OCLP developers. Sometimes the intermediate fixes we come up with are not the eventual best solution.
Maybe we could develop a 'best practices' thread for people just getting into it. Or add it to post #1 of this thread. That would have helped me and many others when we started on this journey. 'Best practices' that come immediately to mind are:
Bear in mind that in the past many issues have been fixed when a new version of OCLP drops; the war in Ukraine will slow that process down for the foreseeable future. Personally, I'm considering freezing my installation at this point (12.3.1)
- read this entire thread, that could take you days but do it anyway
- learn how to install macOS & OCLP on an external drive (SSD or USB pen drive)
- create a copy of your m/c's last supported macOS version on an external drive so you can get firmware updates, see previous discussions on this page
- install new versions of macOS on the external drive and test them before installing them on your internal drive
- don't install betas on your main internal SSD, only install public releases
- learn how to do a clean install, you can practice on an external drive
- do not expect everything to go smoothly. If it does, you're having a good day!
- contribute your experiences to this thread
- add your m/c and macOS version to your signature so others can help you easily
- helpful tools to have installed are gibMacOS & SilentKnight. Helpful websites are Mr. Macintosh, OCLP's Discord discussion group and https://dortania.github.io/OpenCore-Legacy-Patcher/
- have two backups handy
Absolutely. The key information here is that when you run an installer it will ask you which drive you want to install the op sys on. You can even copy the installer to your main boot drive, run it from there and when it prompts you for which drive to install it on be sure to specify the external drive.Thanks. I already have a Catalina USB installer, I just didn't know that it could be used to install onto an external drive. I thought it could only be used on a partition internally (which I'm not comfortable doing)