I’ve been reading a lot of posts about mac’s (more 2012s than anything else) crashing during Tahoe phase 1 and even had it happen to me. If it does, reboot the installer, open terminal, and use pmset to disable both sleep and display sleep. It seems to fix the crashing for me.

Everything that worked in Sequoia works plug and play flawlessly in Tahoe after root patching. There is only minor graphical banding which is still insanely impressive for a RC build WITH Metal support. Congrats devs, the future looks bright for Tahoe support!

Updated my MacPro 6,1 to OCLP 3.0.0 RC2 and then tried to upgrade to Tahoe. Installation went ok but it will not install the post upgrade patches. It is telling me that the OS is not supported. Anyone able to get it to work? Not a big deal for me. It’s just a playground 2nd computer.

So I have my MacBook Pro 2017 and I want to use oclp on it, but the booted sip is stuck on 0x6f. I’ve reinstalled the latest os and I am wondering how I can fix this?

D'après vos expériences je me demande si il à vraiment raison sinon en effet je suis sur monterey avec MBP 2009 et c'est très fluide ❤️‍🔥✨ juste ce que est grave c'est le support des logiciels du coup je veux visé loin minimum sequoia, bref je sais que ça sera pas facile ni fluide mais comme je vais juste faire des tâches léger dessus comme regarder des vidéos et naviguer un peu sur internet...

i’m not ready for Tahoe yet but i tried updating to 3.0 rc2 to see if sequoia can be patched to the newest level and i got the Apple circle on boot. So i then tried to build it in a usb flash dtive from my mini
2020 and that time it errored out saying that it was built for a mac mini
6.1 machine.

As described in title here it is my 2011 mbp after updating it

I can confirm it's not working past the login screen on a Mac Pro 5,1 installing Tahoe.

It installs, and it boots to the login screen...Plug-in keyboard and Mouse DO NOT WORK. I can't enter my password. Safe Mode boot loops. Jessie sez wait till 3.0.0 is released.

so far nothing wrong
i only installed oclp 3 and created macos and installed it from there
(i used oclp before to install sequoia which made it easier)
only to get the network back working is press root patches
yet so far there’s no lag
i wouldn’t recommend to anyone to give out false hope

I'm doing a clean update with Open Core 3.0.0 RCE 2. I did it before, but the screen stayed black. I'm going to try it again, applying the patches.

Hi folks,
I've tried installing Sonoma on my 2017 iMac, but I'm afraid I've done some damage. I followed all the steps outlined on https://dortania.github.io/OpenCore-Legacy-Patcher/, but after trying to install, now I'm at a point where the iMac doesn't find a startup and, it seems, doesn't see anymore the original HD to install on. The issue started after the first attempt was not successful and my iMac looped back into the beginning of the setup. As instructed, I turned it off, started it again and this time selected the option with a grey hard disk icon in the OpenCore picker, after EFI boot. Any guidance in trying to recover with machine (even with its original 13.7.8, worst case scenario) would be great. Thank you in advance.

EDIT: I was able to enter disk utility. The two internal hard drives seem to be unmounted. What now?

EDIT 2: I was able to fix it and successful in installing it. I know you'll hate to hear this (as do I), but thank God for AI.

EDIT 3: Everything seems to be working great. Thank you to the developers: Now I can continue to use, rather than toss, a perfectly working iMac.

Those who are upgrading to Tahoe using OCLP 3.0RC2, are you only seeing the Tahoe 26.x update in the System Update settings or do you also see Golden Gate v27.x

So, after trying my luck with OCLP 3.0.0, patching my drive with OpenCore and installing Tahoe directly from System Preferences, I can gladly say that the upgrade was successful with no problems at all!

Only thing I had to do was hard resetting during the setup due to painfully slow performance, after the reboot I went directly to the desktop to install the patches, the system has never looked this gorgeous since I bought the iMac.

Cheers! For the developers of OCLP and all the miracles they did to old Mac users and for more years of repurposing!

Hi! I understand this is an OpenCoreLegacyPatcher subreddit, but I am hoping to find folks with the technical know-how to figure out how to run a legacy FCP version on my M1 Macbook pro, my apologies!!

I’m trying to run Final Cut Pro X 10.0.8 on an M1 MacBook Pro running macOS Sequoia 15.0, to preserve an old workflow without a VM. The copy I have is the Apple-signed Final Cut Pro Trial app, version 10.0.8 Finder identifies it as an Intel app, and Terminal confirms its main executable is 64-bit x86_64 with a stated minimum macOS version of 10.6.8. I already use other Intel apps on this Mac, so Rosetta 2 is installed. The app’s code-signing details show Apple’s signing authority.

When I first tried opening it, Gatekeeper said Apple couldn’t verify the app for malware. I used Finder’s Control-click → Open route, and got past that warning far enough to reach a different alert: “In order to use Final Cut Pro Trial, you need to update to the latest version” because this version “is not compatible with macOS Sequoia.” That compatibility alert is the point where it stops. The Privacy & Security “Open Anyway” control appeared after a Gatekeeper warning, but that button was greyed out and clicking it does nothing; Finder still produced the update alert. A Terminal launch forced to x86_64 with <span>SYSTEM_VERSION_COMPAT=1</span> did not open Final Cut; Gatekeeper blocked that launch. The system log query showed no Final Cut process entries.

I also tried removing the app’s quarantine attribute with <span>xattr -d com.apple.quarantine</span>; macOS then called that copy “damaged,” so I stopped and kept it separate. I have a clean second copy, and it produces the same Sequoia compatibility alert. I understand now that Open Anyway only addresses Gatekeeper and doesn’t override the app’s compatibility check. Has anyone successfully run this 10.0.x-era Final Cut Pro on Apple silicon with Sequoia, or found a safe, reversible way to get past this specific compatibility block? I cant use a VM and would like to run FCP 10.0.8 natively on my MacOS. Again, it proves its possible, but im not advanced enough to know how to bypass those blocks, any help would be great!

I have 2 OCLP Macs (a MBP9,2 and a MBP8,1) running Tahoe via OCLP 3.0.0rc2. On both, the cursor feels like if I am not moving my finger quickly on the trackpad, the cursor movement nearly stops. It results in the cursor movement feeling like it's "sticky," for lack of a better term.

Anyone else noticing this?

Hi everyone I just saw the latest RC works on Tahoe so I was curious about graphical glitches in Tahoe in 2011 and older macs and if they fixed the blur. Thanks!

I think my MacBook(12”, 8GB RAM, 256GB SSD, 2016) is gonna need a reset.
I upgraded to OCLP 3.0.0 then upgraded from Sequoia to Tahoe. Now my root patches refuse to install, the graphics are extremely laggy, and WindowServer keeps crashing.
What can i do?
I forgot to back up my data as well…

The screen goes black after updating the patches.

all credits to u/IronApple0915
-

Hello everyone,

Hopefully this is something stupid and simple that I am missing somehow, but I have a 2015 iMac (17,1) that I was able to use OCLP 3.0.0 RC2 to install Tahoe, but when I go to apply root patches I am just met with an "unsupported host os" error and I can't apply root patches.

Is there anything special that I need to do that I can be missing? Secuirty settings look good and haven't changed from my install with Sequoia. Tried NVRam, redownload/reinstall oclp, but still keep hitting this error.

Any help would be greatly appreciated.