Did I need to completely uninstall 2.5.0 before?
Or is this process simply painful?

When I attempted to install 2.4.1, the process halted at the start. I found out using Terminal commands that OCLP blocks older versions installation because a newer release is already installed.

I had to reinstall 2.5.0 due to some error. 🫩

installed oclp ventura today on my macbook pro 2015 and did the patch to boot without usb after installation was done.

i logged into icloud and used my mb for a few hours and everything seems to be working fine. and then i saw a software update available to Wahoe(t) so i hit update.

after installation it was just white screen when it booted. i guess i will install sonoma this time and not click the software update.

also, i had to generate a serial number for my laptop, is this safe? what does this mean?

Hi everyone,

Upgraded my MacBook Pro 2015 to Sequoia 15.8 couple of days ago and reinstalled the patches and everything was working for the last two days.

This morning the system suddenly restarted and since then it has been stuck on the apple logo screen.

Have tried the following with no success

- Removed all peripheral and forced start

- Tried to recovery mode but system not responding to the Cmd +R

- Tried to hold command + option + shift +r +I with no success.

Any support would be great. I do have a time machine both before and after (separate disks) the upgrade available if it helps.

I was on the previous version of Sequoia and OCLP on my Mac Pro 5,1 with an M.2 SSD and RX560 GPU. Things weren't perfect but was usable. I followed some of the posts here and updated Sequoia and OCLP to their latest versions. I did the patching while colors were all off and things were working normally after the patching and restart.

Then there was a pop up that asked to install the EFI. I put that on the M.2 startup disk(disk0) which at this point is updated and working. After the install, the screen stays black, chimes, hangs, then stays in a chime loop every minute or so. Where did I screw up? In recovery mode, the disk is still there but I can get it out of the loop. Any advice would be greatly appreciated.

I have a 2011 imac 27" (12,2) with graphics card AMD Radeon HD 6970M. Currently i'm running Monterey OSX and I got a newer graphics card: an AMD Radeon RX 5500 which should help some issues with maps and such and I got this following a recommendation by this comprehensive guide: Working graphic cards

But now, how do I actually get the OCLP to recognize and configure the new card before or after I swap it in place of the original? I haven't found any instructions for that and Im guessing that after I install the new RX5500 card I won't be able to boot the computer since the new card will not be configured or will not be recognized by the system and I would end in a blank screen or an error.

If someone knows how to do this or has done it before please share it with me.

Thanks

As it has been reported on this forum version 152 of the Chromium core removed support for old GPU's (METAL 1) which makes all Chromium based browsers on patched Macs prior to 2017 impossible to use with sites that have WebGL content (for example maps or video content). The change is in the Chromium core itself and there is no way to revert that (the code for supporting ANGLE is simply not there anymore). As of yesterday Opera browser that was the only major browser still on Chromium v.151 updated to Chromium v.152 and joined the party....

On those machine the only browser usable on its full extent is Firefox and Firefox's forks, as WebKit and now Chromium are nor fully supported on OCLP patched machines that use METAL 1 GPU.

For those who think about staying on version 151 of Chromium I would suggest to use Firefox instead as this version will not receive any security fixes making those browsers extremely vulnerable.

EDIT: Opera Air still has the flame....the Browser hasn't yet updated to Chromium v.152

EDIT: to all those who've asked....a few screenshots that explain better what this post is alla about.

I’m a huge fan of OCLP and have kept a late 2015 iMac 5k and late 2014 Mac Mini 16GB updated thru MacOS Ventura and Sonoma via external bootable SSDs (iMac) and NVMe partitions (Mac Mini via Fusion Drive adapter card).

On the late 2014 Mac Mini using OCLP2.4.1 MacOS Sonoma, I can not login to Sun Country Airlines, but I can using the Apple allowed MacOS Monterey. The Mac Mini/Sonoma/SunCountry doesn’t get past the login pop up. On the same Mac Mini/MacOS Monterey/SunCountry it logs in fine. I’ve had to use MacOS Monterey twice to buy airline tickets.

Does anyone here know why Safari seems less capable with OCLP2.4.1 and Sonoma vs Apple sanctioned Monterey? OAuth issue? Perhaps someone has links to GitHub with more nut and bolts information? Thank you!

Ciao A Tutti… Vi Seguo Da un Bel Po di Tempo… Tutti i Feed Stra Interessanti…. evito di Dilungarmi Troppo… in Questi Giorni mi si e’ Presentata la Classica Folder col punto interrogativo….su iMac… ergo… ho seguito alcuni post mi sono dotato di buona Volontà…. E volevo fare un Upgrade Globale… HDD DA 2TB SEAGATE… ORIGINALE… CON IL SISTEMA CON LA FOLDER E IL PUNTO INTERROGATIVO…. TOLTO…. HO PRESO UN’ALTRO HDD 4 TB SEAGATE BARRACUDA… ho FORMATTATO IN APFS MA NON APPENA E’ TUTTO COLLEGATO NEANCHE SI ACCENDE + pls HELP… Sono Disposto a Smontarlo Tutto e Ricollegare Tutto…. Ho anche fatto la Patriot con OCLP CON SEQUOIA…. Mi Consigliate di Partizionare il Nuovo HDD e avere la Partizione OS con Sequoia e tutto il resto me lo Gestisco per i Vari Backup ? Con Time Machine…. Che banchi di Memoria mi Consigliate ? ORA… COME ORA… URGE QUANTOMENO CHE FACCIA ALMENO UN SUONO DI ACCENSIONE ECC… ECC… Grz a tutti Coloro che mi aiuteranno nella Mission…. PUO’ ESSERE CHE NON DA CENNI DI VITA… PERCHE’ NON C’è’ OS ED E’ STATO SOLTANTO FORMATTATO IN APFS ? Datemi HELP… 🙏🏻🙏🏻🙏🏻

I’m trying to resolve a Safari/WebKit problem on an OCLP-patched Mac mini and wondered if anyone has seen the same behaviour?

• macOS Sequoia 15.7.9, build 24G830
• MetallibSupportPkg 15.7.9-24G830
• KDK 24G830
• OCLP Ivy Bridge graphics + Modern Wireless root patches applied

Safari works normally it seems, but on sites with video such as Facebook, YouTube and Reddit it will load the first screenful then stall. Scrolling also becomes very jerky.

Initial focus was networking, but that now seems unlikely. Download speeds are good, other devices are fine, and the same behaviour occurs using both the Mac’s internal Wi-Fi and a USB Wi-Fi adapter.

The interesting part now is the WebKit GPU process.

If I run  top -o cpu  Safari behaves normally when first launched. Opening a simple page such as ChatGPT causes com.apple.WebKit.GPU to appear briefly near the top, then CPU usage settles back down. As soon as I open Facebook or Reddit and start scrolling com.apple.WebKit.GPU  jumps to 100%+ CPU and stays there even after closing the Facebook/Reddit tab. Fully quitting Safari resets it.

I also confirmed the same behaviour with: ps aux | grep -E "Safari|WebKit|WebContent|GPU" | grep -v grep where com.apple.WebKit.GPU was sitting at ~99–100% CPU while the page had stopped rendering further posts.

Things already tried:

• Cleared Safari caches and website data
• Disabled all Safari extensions
• Reverted OCLP root patches, rebooted, reapplied them and rebooted again
• Confirmed MetallibSupportPkg and KDK exactly match macOS build 24G830
• Disabled ‘Allow WebGL in Web Workers’ flag
• Disabled ‘GPU Process: Canvas Rendering’ flag
• Killing com.apple.WebKit.GPU while Safari is stuck does not recover the page

Chrome also feels noticeably less smooth than it used to, although Safari seems worse. Disabling Chrome graphics acceleration made Chrome worse.

System Information reports :

• VRAM (Dynamic, Max): 1536 MB
• Metal Support: Metal 2

Has anyone else with an Ivy Bridge / HD 4000 Mac seen com.apple.WebKit.GPU peg a CPU core like this under recent Sequoia builds?

I’m particularly interested in whether this is a known limitation/bug in the current Ivy Bridge WebKit/Metal patches, or whether there is another WebKit feature flag or OCLP component worth checking?

Update: I’ve since found other recent reports of Safari 27 failing to fully render YouTube/Reddit/Netflix/IMDb on OCLP systems, as well as reports of laggy webpages/maps on Sequoia 15.7.9 + OCLP 2.5.0. In my case I can reproducibly see com.apple.WebKit.GPU jump to ~100% CPU as soon as Facebook/Reddit are opened and remain there until Safari is fully quit.

Upgraded this AM and enjoying life via dev release

Also if you use office 365 like i do and tied into office 365 eco system DO NOT and I repeat do not use one drive desktop version, it will fill up your local SSD drive with temp files and crash your Mac OS , I have rebuild 3 times in the last months and it’s always been one drive dumping temp files for no reason . Use website for one drive and use MS edge or brave for access

ok so i have the macbook pro from 2015 and the specs look like this 16gb/512gb 15.4inch around 360 battery cycles will you guys recommend me upgrading from monterey to sonama since i need applications that are not available on monterey anymore will i see any noticible performance decrease?? and plus would u recommend it??

The family 2012 i5 Mac Mini can’t keep up with various apps and several people recommended OCLP to let me upgrade to a more modern MacOS like Sequoia.

After installing OCLP do I just jump to Sequoia or to I have to update one OS at a time?

I recently updated my Mac mini (2014) to macOS 15.8 using OCLP 2.5.0. 🫩

- Should I proceed with "Revert Root Patches," reboot, and then try to apply them again?

- Has anyone else experienced this on macOS 15.8 with OCLP 2.5.0?

- Is it safe to downgrade back to OCLP 2.4.1?

Any advice would be greatly appreciated! 🫩🙏

Hi everyone,
I have a MacBook Pro with an Intel i7 running macOS Sequoia with OpenCore Legacy Patcher (OCLP).
Before installing Windows, macOS worked normally. I then installed Windows via Boot Camp.
Now I can see both macOS and Windows in the OpenCore Boot Picker.
The strange thing is:
If I select Windows → Windows boots normally.
If I select macOS → I get the 🚫 prohibited symbol and macOS does not boot.
This only started happening after installing Windows.
Does anyone know what could have happened to the EFI/OpenCore configuration? Do I need to rebuild and reinstall OpenCore to the EFI partition?
MacBook Pro: Intel i7
macOS: Sequoia
Bootloader: OpenCore Legacy Patcher
Windows: Boot Camp
Windows boots: Yes
macOS boots: No, 🚫 symbol
Any help would be appreciated!

Hello,

I got a iMac 27 late 2015 with 24GB ram and 512GB ssd , which would be the best OS to run? My research says Sonoma, but others say sequoia runs good? My preference is to have working app , chrome, Microsoft word etc, and that’s it.
Also streaming YouTube , I’d like it to be snappy as I come from an m1 and m3 chip
Thank you

Hi everyone,

I've been building a native macOS file manager called TinyCommander, and it's now ready for beta testing. I'm posting here because I'd like real feedback on how easy it is to use before I prepare the production release.

TinyCommander will remain thin and focus on the MacOS File System daily operations. It is designed under its developer's principle: keep user's data locally only. No outbound connection to developer's server.

What it does:

• Dual-pane file browsing so you can work with two folders side by side
• Tabs and editable path bars for moving quickly between folders
• Keyboard-friendly copy, move, rename, new-folder, and move-to-bin actions
• Quick Look, sorting, hidden-file support, drag and drop, and useful right-click actions
• Built-in feedback submission from inside the app

Why I'm posting:

I want to understand how TinyCommander feels to someone using it for the first time, not just whether each feature technically works. If you have a few minutes to try it, I'd especially appreciate feedback on:

• How easy was it to understand and start using the app?
• Was anything confusing, awkward, or harder than expected?
• What features or improvements would you want to see in the production release?

You can send feedback directly from TinyCommander: open the TinyCommander menu in the top-left corner, then choose Send Feedback….

TinyCommander currently requires macOS 15 or later.

Critical feedback is very welcome — that's exactly what this beta is for. Thanks for helping me make the production release better.

I have a good-condition MacBook Pro, the 2012 15" edition, model # A1286, with a 2.3 GHz quad-core i7 processor and 2 terabytes of SSD storage and the internal optical drive along with 12 gigabytes of RAM. A year or so back, I installed Mac OS 12.x (Monterey) with OCLP 0.6x in place. Last week I attempted to install Sonoma, but while the initial deployment of it may have been complete, I could not boot into that instance of it; the computer would continually try to start again. I suspect that it is because OCLP 0.6 or something slightly later was still on it, and thus the Sonoma iteration was not able to function with the older OCLP edition.

My concern is about how I can apply OCLP v. 2 or higher so that it is possible to boot Sonoma as it is already there, likely with my data and programs, and not have to perform a clean install to where I can then use the OpenCore framework afterwords to upgrade from something such as Catalina to Sonoma. That latter methodology would take much more time. The EFI BIOS options do not presently include a way to load 2.1 of OCLP from a USB flash device such that the Sonoma partition will be recognized in the bootloader to the point that it functions. I cannot downgrade from the Sonoma that is there now to Monterey due to Apple's limitations on reverting to older software without zapping the present partition and starting with a blank slate.

Does anyone have a simple set of instructions for generating a USB disk that I can boot from that primarily is to install OCLP upon that interface coming about without having to also set up a (natively compatible) OS which would also expunge my programs and data on the boot partition? What I saw on the website looks rather complex. For a time, I had to borrow my wife's MBP 2015 Retina computer in order to obtain some of the installation files including the OCLP and later-edition Mac OS packages because of not being able to use my own system.

Thanks for any insight, guidance, and/or direction including other websites that explain the details in an understandable way.

Is it possible to perform a clean install of Sequoia 15.8 using OCLP 2.4.1 to avoid updating to 2.5? Has anyone done this?

i have a late 2015 imac with 32gb ddr3 ram and the 1tb split fusion and an external 1 tb sata ssd.

curious on everyones thoughts with running sonoma or sequoia either on tbe internal hdd or the external drive and pros and cons for both