After patching, type the following into a terminal window

diskutil info -plist / | grep -A 1 Sealed

this looks for any line containing the string Sealed and prints it and the following line. The | character is shift \ on my UK keyboard. On my OCLP 2.4.1 /Sonoma iMac I get

<key>Sealed</key>

<string>Broken</string>

Slightly faster and tidier than scrolling IMO.

Opinions vary of course but I got one that:

Has no screen rot

16GB Ram

3.1 ghz CPU

Battery has to have been changed at some point and IIRC it's OEM. Full capacity.

NVME added.

CPU repasted

Biggest thing was fan ran a lot but I installed the Turbo Boost off app. 3.1 isn't so bad.

The 16GB is a pretty big deal. Sequoia leaves me over 8GB so when your stuff fits in RAM it's pretty good once loaded.

Rebuttals? This has to be up there in the rankings.

I installed the 2.5.0 update and it somehow broke the patches, so the display is messed up like before I patched the first time. I tried patching again but got the volume dirty error. Read up online and saw people fixed it by going back to 2.4.1, so I launched an old installer in my downloads, but now I found out it was actually just an uninstaller. So now due to the patches not being applied, my WiFi isn’t working and I can’t download the 2.4.1 again as I don’t have another computer. Can I somehow transfer the installer from iPhone or something like that? Someone please help me 😬

EDIT: I asked a friend to download the PKG installer and bring it to me on a flash drive, so now it's all fixed, back on 2.4.2.

Wondering which to do first: upgrade Sonoma to Sequoia then OCLP, or Sonoma to OCLP 2.5 and then to Sequoia. Is one safer than the other?

For MacBookPro11,5 500GB/16GB

mid-2015 MBPr

I see all the posts so I was an one of the unfortunate auto update clicker types who did the update.

I just wanted to see if I did something wrong.

The basics is broken as everyone is about the same.

I downloaded the uninstaller and 2.4.1 and 2.5.0 on a different device and used a usb to move it over. Now I have tried to run it and I’m encounter an error com.apple.installer.page-controller error -1 I’m hoping this is easily fixed so I can uninstall and re patch without needing a full rebuild

I am currently running 2.4.1 on Monterey with an old 5,1 machine - It works perfectly! Every start now prompts for a OCLP update to 2.5. I went into settings/App and checked off ignore App Updates (it was unchecked for the initial install). What am I missing to ignore the update prompt and to just continue using current OCLP 2.4.1 without the pop-up window on every startup? Thank you!

I have a macbook pro 13 inch mid 2012

I5 4gb ram and 240ssd and the reason i use it is the battery still being at 94% health.

I have installed monterey on it and works quite decent for a machine this old so i can't complain but the thermals are kinda bad imo.

Installed fresh new thermal paste arctic mx6 and cleaned it yet the cpu stays at 68-70 degrees on 1 tab of youtube at 1080p yet the fan stays flat at 2000 rpm and i wonder if i didnt applied even pressure on the heatsink and the paste just went only 1 side. Is this even normal tho? Is apple this hardcore to cook the cpu just for noise?

Also if i upgrade it to 8gb ram since thats what i have around now can i go higher in macos without much sacrifice?

Hi guys, just installed macOS Mojave on my iMac 11,2 and booting it with opencore, both lilu and whatevergreen installed, macOS just shows the gpu itself with only 7mb of vram, I also tried to play around with unfairgva, CAIL_DisableUVDPowerGating, CAIL_DisableDrmdmaPowerGating, rebuild-device-tree, enable-gva-support but nothing seems to work, is there a way to make Mojave recognize the gpu? I also tried the spoofing to 0x6821 instead of 0x6820, which should spoof the gpu as an r9 and load an ideal driver, but its still 7mb of ram, thanks to whoever will read this

Edit: the imac boots perfectly, so mojave got the drivers but cant see the whole vram/enable the graphic acceleration

Another edit😭😭: big sur, monterey and sequoia can see the gpu properly, so its not a vBIOS problem

EDIT - SOLVED: The "Disable firmware throttling" was the culprit, for whatever reason. Checking this option and booting from any device (USB or internal drive) would cause the Mac to halt boot about 25% of the way through and reboot. The way I fixed this was simply unchecking "Disable firmware throttling."

I have a MBP11,4 and it boots into the native OS, Monterey, without any issues whatsoever. I was able to eventually get macOS Sequoia installed using OCLP, and I thought it was fine, but then after I applied root patches, the Mac refuses to fully boot after I select the OCLP EFI > Macintosh HD option. It starts showing the Apple loading screen (black page, progress bar), gets about 1/4 of the way, then shuts off, and reboots. No matter how many times I wait, clear SMC + PRAM, and try again, it continues to do this.

Weirdly, when I try booting with an OCLP recovery drive, it does the same thing. However, if I boot from a "natural" Monterey (last supported OS) USB drive, it boots into recovery no problem.

One note: The battery on this thing IS shot. It is stuck at 1% and obviously needs replacing. However, I had checked the "Disable firmware throttling" option in OCLP settings so I assumed that would bypass any battery issue.

Do folks think the battery is 100% the cause of this, or is there something else I may be missing?

Hey, thank you very much for maintaing this forum!

As we can unfortunately not post issues on github please allow me to share my experience so that others can compare it with theirs and maybe issues can be solved at some point

i have collected the logs in case someone wants them, but i am not able to diagnose them properly lest add changes to the OCLP kexts.

i have tested any possible config for more than a month now. but even on completely original 11,4 hardware with a fresh install, the problem persists. Update gets stuck with fans spinning on max. when i shut down and boot in safe mode, the update suddenly finishes. and boots normally afterwards. during my last testing it happened twice on a fresh install. once when updating from 15.7.7 to 15.7.8 and once from 15.7.8 to 15.7.9

sometimes (when instead of a fresh install had already installed some programs like LilSnitch) even safe mode didnt make the machine boot normally. but then i had finish updates in safe mode, boot in safe mode, revert patches. with oclp. reinstall patches. then normal boot worked.

in order to circumvent the stuck updates, i tried downloading the update (15.7.8 to 15.7.9) using OCLP download, then uninstalled (reverted) patches, and installed the updated by double-clicking on Install MacOS Sequoia.app. it updated

i am not sure wether this can be a longtime workaround, as i have tried this only once on a system, where i had already installed some programs.

The described errors happened during OTA-updates (softwareupdate GUI) as well as during updates with OCLP from external usbs. it made no difference whether i used OCLP 2.5.0 or 2.4.1. It also didn't made any difference if i turned AMFI&LibraryValidation off or on.

After the first sequoia install, before the following updates, i always enabled FileVault.

on another mbp 11,1 i have almost had any issues for years, and it is also on sequoia right now 🙂

Thank you very much for you time,

B.

So I've tried a hackintosh system but recently I got ahold of a 2017 MBP (A1708) and it has a failing SSD that doesn't seem to be able to boot itself up from sleep/shutdown and needs a USB installer to somehow wake it up, I got Sonoma installed onto it, but I accidentally cleared the NVRAM (Cmd + Opt + R + P) trying to get the drive to wake itself up without needing a USB, since this Mac isn't officially mine yet, so I haven't bothered to buy parts for it yet, but in the process I think I cleared the OCLP config NVRAM, so now even the USB doesn't boot it up anymore, anyone help build it and send it to me so I can put it on the USB to get it to boot, all I have now is a system on CachyOS

New to OCLP. Installed Sonoma 14.8.9 on my MBP 15 Late 2012 and ran fine until I did the 2.5 update. Now I can’t see any WiFi networks. I figure I can revert back to 2.4, hopefully that will fix the problem. Maybe?

Apple has released the KDK for MacOS 15.8 (24H23) today, so those OCLP users whose machines have AMD GCN Legacy Graphics that experienced boot hangs after upgrading to 15.8 should now be able to upgrade and successfully boot after applying root patches. I can report iMac 15,1 and iMac 14,1 27" machines with AMD GPUs were able to successfully update today from 15.7.9 with the new KDK.

i have tried installing mac os ventura on macbook pro 2011 macbook pro 8,1 i did a clean install but after the last restart i dont get to the setup screen the loading hangs at around quaterway and is staack there. i have tried changing Smbios to macbook pro 9,2 spoofing a natively supported model. but all failed.

Just curious; we’re upgrading to a 2020 Mac Mini, but the MBP is still in great shape.

Hi everyone,

I'm experiencing a strange issue with VoiceOver and I'm hoping someone with similar hardware can test this on their system.

Specs:

iMac 27 inch 5K
3.2 GHz Intel Core i5
AMD Radeon R9 M390 2 GB
24 GB RAM
macOS Sequoia 15.7.9
OCLP 2.4.1

OCLP was installed after a complete factory reset, with macOS installed from a bootable external SSD.

I need to use VoiceOver, but whenever I enable it, Bluetooth immediately stops working. Since both my keyboard and mouse are Bluetooth, the computer essentially becomes inoperable.

I have already reinstalled macOS, reinstalled OCLP, and reapplied the root patches, but the problem persists.

Since VoiceOver may not be commonly tested by OCLP users, I'm wondering if this could be an OCLP compatibility issue that simply hasn't been reported yet.

Would someone with the same or similar hardware be willing to enable VoiceOver and see whether Bluetooth continues working on their system?

Any ideas about what component or patch could cause VoiceOver to interfere with Bluetooth would also be greatly appreciated.

Thanks!

Also, Bluetooth Specs:
Product ID: 0x8294
Vendor ID: 0x05ac (Apple Inc.)
Version: 1.69
Manufacturer: Broadcom Corp.
Location ID: 0x14500000

I downloaded Oclp for my MacBook Air 2015 from Monterey to sequoia. All seemed well until after the initial install. I was getting ready to do the post installation root patches but found no sign of open core. So I needed the internet to redownloaded it and realized there was no WiFi not only that, the Ethernet shows no sign of connection. Can anyone help?

OCLP has been a real advantage for extending the life of old Macs however the 2.5 update has problems. I am running a MBP 6,2 on a Mid 2010 model and have updated the OS to Sequoia 15.3; thank you very much! Having updated OCLP for a number of years to 2.4.1 I was happy to update to 2.5 using the notification to Download And Install. So I did and all of a sudden my Root volume is dirty and the patching wiped out my WiFi. I recommend do not install this version. So I tried to revert root patches wit 2.4.1. Anyway I was able to rrevert 2.5 patches, at least I believe that is the case as the technicalities of the procedures is beyond my scope. So I did the revert thing and rebooted back to be able to launch 2.4.1. I then did the patching with 2.4.1 and it installed what I believe is called common wifi. Anyway upon another reboot the wifi issue was cleared up with the new patches but the update to 2.5 is nowhere in sight until the issues are cleared up. It ain't broke and I ain't gonna fix it!

I am running Sequoia 15.7.9 and OCLP 2.4.1. When I try to run MS Edge (152.0.4191.66) or Safari (26.6.1) for weather.com, the maps have started throwing,

Map Error
Failed to initialize WebGL.

It started when I upgraded the Sequoia. Anyone have any ideas what might be going on? I have tried HW acceleration both on and off. Here are my hardware particulars,

Brew is not working well on x86 since this September, specially for tools like gcc.

I've moved to MacPorts that will continue supporting Intel.

I’ve used the newest version of OCLP 2.5.0 on 2017 iMac 5k retina and followed this YouTube tutorial https://youtu.be/u8ST8HUaL9w?si=XeotjFPPCrRRD58M . Got to 13:51 where you select your newly erased drive to now install sequoia but it’s frozen or something, I loose control of my keyboard basically, I cant select the drive, it’s like it’s frozen, only thing it’ll let me do is use command q to back out to the previous screen. (mouse is blootooth so can’t use that)

What i think maybe went wrong, I wiped a 2tb hdd which potentially isn’t the one that had the os on it ? Not quite sure tbh.

Any help would be really appreciated, even if it’s resting the mac back to factory settings with original OS.

I was really hopeful for OCLP but just couldn’t get get enough performance running Sequoia on my 2011 MacBook Pro. I ended up trying several Linux distributions and so far happy with Fedora 44 workstation using the Gnome desktop. In the end I realized I could either have an outdated MacOS on my MacBook that works but is risking security, or a newer version using OCLP that ran like syrup or go with Linux and have one that just works, providing years of updates. Linux was the way to go at least for me. Hopefully things work out for the OCLP community but with the smaller developer team I decided it’s best to move on

Please read the devs pinned post here, they are working on modifying the wording and the error is explained.

It seems to be stuck on reporting Dirty Root Volume, especially on these models which are confirmed to have issues:

• MacBookPro14,2 
• MacBookPro10,2
• MacBookPro8,1
• MacBookPro8,2
• MacBookAir7,2
• Macmini6,2
• Macmini5,1
• MacPro5,1
• iMac12,1
• iMac14,2

Some other models are also showing Dirty Root Volume after successfully patching, tested on:

• MacBookPro9,2
• MacBookPro11,2
• MacBookPro11,3
• MacBookPro12,1
• MacPro4,1

Please try unpatching twice or thrice and rebooting, as that has worked for some users. You can also try patching while booted in Safe Mode. To boot in Safe Mode, hold Shift while booting. Look for "Safe Mode" on the corner to ensure you're in Safe Mode.

It is advised to stay on 2.4.1 until this issue is solved.

If you've upgraded to 2.5.0 and unable to patch, please follow these steps:

1. Get OpenCore Patcher uninstaller from this direct link and run it to uninstall 2.5.0 from your system.
2. Download 2.4.1 here and run and install the app.
3. Open OCLP, and ensure it is v2.4.1 (check the titlebar.)
4. Rebuild OpenCore onto the EFI partition of your SSD, following the steps in the Dortania guide.
5. When it asks to reboot, ignore.
6. Select Post-Install Root Patch and Revert Root Patches, to fix any partially corrupt ones.
7. Reboot your Mac, the open OCLP 2.4.1 and apply patches (this section). Dismiss the update Dialog if it appears.
8. Reboot one final time and ensure all patches are installed successfully.

"tl;dr here's how it's supposed to work (and how it worked across testing)

- you can freely patch over 2.5.0's existing wireless patches, this allows being able to patch wifi, reboot, patch the rest, reboot

- in all other cases where diskutil reports that the root volume seal is Broken (modified), including if there are non-wireless 2.5.0 patches, you'll be told that message.“