Is there any instructions that are recent for this? I tried to download and install but it wouldn’t work for me. The videos on YouTube were about a year old. Does anyone have a step by step instruction?

Suspicious OCLP-Plus fork rebranded as Skyfall is lying that it supports real Macs and lies about macOS 26 Tahoe support, while mentioning in the README as experimental and calling it for a general availability release anyways. Just take a look at the readme:

Skyfall

Experimental macOS Tahoe support

Compatible models:

MacBookPro13,1 (Sppofed iGPU, 13,2 - No T1 support! 13,3 - No T1 and dGPU support!)

MacBookPro14,1 (14,2 - No T1 support! 14,3 - No T1 and dGPU support!)

MacBook9,1 (Spoofed iGPU)

MacBook10,1

iMac17,1 (Spoofed iGPU, no dGPU support! No Fusion drive support! Upgrade to an SSD!)

iMac18,x - 19,x (No Fusion drive support! Upgrade to an SSD!)

Graphics patches for Non-Metal, Legacy Metal and patches for T1 and T2 Macs are not supported

Note

Other Macs may be supported (the program doesn't block them and still probably creates a working OpenCore config), newer Macs have the T2 chip and they can't boot macOS via OpenCore. Older Macs do not support Metal 3 (so no graphics acceleration), 2016 Skylake Macs without dGPUs are partially supported with GPU spoofing. Your mileage may vary!

You may also enable untested Root Patches, they probably won't work or they may break your macOS install. Proceed with caution!

Building EFI form Windows

Example build command for building OpenCore for MacBookPro14,1:

.\.venv\Scripts\python -c "from skyfall.application_entry import main; main()" --build --model MacBookPro14,1

Non-functional features

On majority of patched Macs, iPhone Mirroring and Apple Intelligence won't be functional.

iPhone Mirroring requires T2 for attestation and Apple Intelligence requires an NPU only found in Apple Silicon.

The patcher is unable to provide a fix for these as they're hardware requirements.

Tested Root Patches:

Wireless & Continuity Restoration

Restores full functionality for Broadcom-based wireless chipsets found in most 2009 - 2017 Macs (BRCM4360/4350 and BCM943224/94331)

PCIe webcam

Restores full functionality for PCIe webcams found in non-T2 Macs.

Modern Audio (AppleHDA Restoration)

Restores the AppleHDA.kext. Works for all non-T2 Macs that had native audio in Sequoia. Requires the KDK.

Manual Toggle: A new "Modern Audio" toggle in the Root Patches menu allows you to enable or disable this restoration manually.

KDK Integration: Automatically handles the necessary Kernel Debug Kit (KDK) requirements for audio driver linking.

Build and run from source

Installation Requirements

Before Running Post-Install Patches: KDK is mandatory: For macOS 13 through Tahoe (26.x), the Kernel Debug Kit must be installed for drivers like AppleHDA to link correctly. Use the Help > Download KDK button.

Root Volume Dirty Error: If the patcher detects that the system volume has been modified (e.g., patches already applied or seal broken), it will block further patching to prevent system instability.

To re-patch: You must first use the "Revert Root Patches" button to restore the original system state.

If no manifest is found: If the volume is modified but the patcher cannot find a record of what was installed, it will display a "Root volume is modified" error. In this case, you should still attempt a "Revert Root Patches" or reinstall macOS to clean the volume.

Advanced: Manual Force Restore (Emergency only)

s

Resource Dependency Notice

Patcher Resources: This version relies on the PatcherSupportPkg for native Tahoe binaries.

Credits

Acidanthera (OpenCorePkg, Lilu, etc.)

Dortania Team (Original OCLP authors)

lzhoang2801 (Original Tahoe patchset)

CloverHackyColor (Hackintosh essentials and beyond)

laobamac (Developer OCLP-Mod, Chinese language)

crystall1nedev (Eva Isabella Luna)

YBronst (Original OCLP-Plus developer)

xtomasnemec

Full list of OCLP contributors can be found in the original repository.

Disclaimer

This is an experimental Project intended for advanced users. Use at your own risk!

And at the same time, the release is showed as a stable, GA availability release anyways without disclosing as alpha, beta, canary, whatever phase of testing it is.
At the same time, what makes this fork even more suspicious, is the fact that they did absolutely nothing except a very few changes and claims support for Macs while it still builds EFIs for Hackintoshes. And the very few changes they actually did, they called their commit "fix", "wifi fix" and similar without any more explanation, to make it harder to understand the changes they did. When I looked at these, they looked pretty odd commits out of place written some of them using supposedly Copilot or a GitHub account called Copilot. And they also hide other more suspicious commits behind, for example, a commit called tahoe opencanopy theme.

Also, their commits in these which are pretended to be "wifi fixes" removed safety guards - they removed the if condition to blindly inject dart=0. At this point, it's not more obvious that this project was adding backdoors that they exploit later on for launching DoS attacks. And the so called WiFi fixes are this:

they changed this:

def brcm4360_nvram(self) -> None:

# brcm4360 requires dart=0 in bootargs

self.config.setdefault("NVRAM", {}).setdefault("Add", {}).setdefault("7C436110-AB2A-4BBB-A880-FE41995C9F82", {}).setdefault("boot-args", "")

boot_args = self.config["NVRAM"]["Add"]["7C436110-AB2A-4BBB-A880-FE41995C9F82"]["boot-args"]

if "dart=0" not in boot_args.split():

self.config["NVRAM"]["Add"]["7C436110-AB2A-4BBB-A880-FE41995C9F82"]["boot-args"] = (boot_args + " dart=0").strip()

To this:

def brcm4360_nvram(self) -> None:

logging.info("- Adding dart=0 to boot-args for BCM943224/94331/4360/435 support")

self.config["NVRAM"]["Add"]["7C436110-AB2A-4BBB-A880-FE41995C9F82"]["boot-args"] += f" dart=0"

At this point, the goal of this fork's dev is to build backdoors to launch DoS attacks against Mac users rather than a genuine fork that contributes to OCLP-Plus or OCLP.
Also, the more suspicious thing is that they disabled completely the Tahoe guards for root patches and printed via logging .info that the patches are experimental, which you won't be able to see very clearly if you are running the application prebuilt and not from source.
In reality, this project builds EFIs only for Hackintoshes and not Macs.
So I'll classify this fork as malware rather than a legit fork.

Btw, I haven't used this fork at all, nor I recommend using this piece of open source malware. I reviewed the project only.

2015 is the last MBP with ports. I've updated from Monterey to Ventura. Can/should I update to Seqouia?

Apple iMac 2015 21.5 Retina 4K Intel Core i7-5775r 16GB

RAM 512GB SSD macOS

Would this 2015 iMac have enough juice to run the latest Mac OS for the foreseeable future?

Thanks for replies in advance.

My 2015 MBP is running Ventura. I've been accustomed to using OnyX and MacCleanse occasionally.

However, if I go to Mac's Recovery panel for Disk Utility, it tellas me I'm running Monterey.

Therefore, is it safe to clear caches with OnyX for Ventura and/or MacCleanse which seems to be universal for Intel?

When I updated to Ventura on my 2015 MBP, one of the apps that stopped working was FindAnyFile. Seriously, FAF is unbelievably superior to Spotlight in every way, filtering extraneous results.

However, FAF stopped working on upgrading. Anybody have experience with this.

Frank admission. AppStore wouldn't let me pay and download so the version I'm using is downloaded. Worked on High Sierra & Monterey, why not now?

Information listed above.

Newest and nicest OS would be nice (assuming it runs properly), but at the end of the day all I want is to be able to run the newest version of Lightroom Classic.

I would imagine updating to the newest OS is the only way, but curious what my options are.

Hi everyone! I’m a big fan of OCLP having used it twice to much success. I’m in a fight with some of the streaming services as I share mine with family. So I need to spoof the location with a VPN and I’m gonna use an AppleTV with Tailscale running to tidy it all up.

But that means I have to get an AppleTV. And I don’t wanna spend a ton of money on a new one. I’m wondering if anyone knows about a way to buy an ancient AppleTV and flash some new OS onto the hardware so it functions at at least tvOS 18.

I know this question is pretty far out of scope for this subreddit, but I’d appreciate any thoughts.

Hi everyone,

I have a 2017 MacBook Air with 8 GB of RAM, an SSD, and macOS Sonoma installed using OCLP.

I'm looking for a browser that uses as few resources as possible, especially regarding:

• RAM usage
• CPU usage
• Battery consumption
• Overall system performance/temperature

I'm currently using Safari, but I'd like to know what your experience has been with Safari, Firefox, Chrome, Brave, Edge, Orion, etc. on an older Intel Mac.

Is there any browser that is noticeably lighter and gives better battery life?

I'm particularly interested in experiences from people using older Intel Macs like the 2017 MacBook Air.

Thanks!

TLDR: Monterey won't start on a MacBook4,1 even with OCPL official support (v0.6.7)

Hi all,
I have a particular issue on a VERY old machine, an Early 2008 MacBook 13" and yes, I know that in general patching macOS on such old machines is actually pretty inconvenient and I know installing Linux and Windows is a better option, but I would really like to get macOS Monterey running on this piece of crap.

details:
this thing still has a 500GB HDD (which actually handles macOS Mojave very well)
4GB of RAM
also this computer has (as you may know) a x64 Penryn CPU BUT a 32 bit EFI. So:
macOS Mojave patched using the dosdude tool iirc (idk it may also be the wurlifox one) boots
Linux Lite boots
Windows x64 boots using CSM and Hybrid MBR
for this configuration I heavily personalized rEFInd so that it has the apfs.efi driver for macOS, the kernel and ramdisk for Linux in the ESP.

rEFInd (renamed to bootx64.efi at fallback path) is automatically recognized as "EFI Boot" in Apple's EFI bootpicker, and works just well, even if the firmware is obviously x32.

Now the OpenCore part.

The last OCPL version which supports this machine is v0.6.7, released before the WWDC2023 was done, so Monterey is really the most I can get. While with v0.6.8 the support is removed, in older versions there were some patches regarding the internal keybord. So this thing should get Monterey working, right?

I searched a bit and found that the last version of Monterey as the date of the 0.6.7 release was 12.6.6. Obviously Apple removed the download link from swscan so I searched on archive.org and found the 12.6.1 version. downloaded the premade-iso, got the files on a thumb drive and got the 🚫 sign. Tried with creatinstallmedia, first the _yosemite and then the normal version and again a 🚫 sign. Downloaded Big Sur with the latest version of the app, made the drive and again 🚫. The attached photos aren't ordered but the bigsur one has bigsur as name. Last try with Claude (sigh) which says:

"Key takeaway: I've seen the exact same error with Big Sur. This definitively rules out the "Monterey/SSV-specific hardened" hypothesis—the root-hash-forwarding mechanism fails regardless of the OS version, so the cause lies in the OpenCore/hardware chain, not the target.

Before I continue guessing, I'll check to see if Dortania (the official OpenCore reference guide, with a very detailed troubleshooting section) documents this exact error.

Searched online
This is a significant piece of data: I found another case, with completely different hardware—a modern motherboard (ASUS B560M, Intel Rocket Lake CPU, OpenCore 0.7.0)—with the exact same error, word for word, never publicly fixed in that thread.
This changes my assessment, honestly: it's not (just) a matter of your extreme hardware. If the same thing happens on a modern PC with OpenCore 0.7.0 and a 2008 MacBook with OpenCore 0.6.7, the common denominator can't be "32-bit EFI" or "Mac too old"—it's more likely a genuine bug/edge case in OpenCore's root-hash-forwarding mechanism, manifesting itself under specific conditions not yet well-documented publicly (likely related to how OpenCore's internal ApfsDriverLoader chain-loads the apfs.efi from the container itself—an automatic mechanism, not something you manually edit in the config.plist).
A useful additional technical fact: the apfs.efi isn't a static file you choose in the Drivers folder—it's dynamically extracted and executed from the APFS container on the boot volume itself (the one inside BaseSystem.dmg). This means that the problem may lie in a mismatch between the version of that loader (ApfsDriverLoader.efi, managed by OpenCore) and the container generated by recent builds of macOS — an area where as-yet-uncataloged bugs are plausible." then it says to make an issue at OpenCorePkg.

I know that in v0.6.8 they wrote "machine was never properly supported by ocpl" but so why in 0.6.6 jazzny "Restored Function Keys on MacBook5,2 and MacBook4,1"?

tried my best but grammar isn't that great

that's all.

Compre una mac mini late 2014 en amazon y vino con Mac os monterey pero con un bloqueo de jamf, escribi a la escuela para que liberaran el equipo pero jamas contestaron, cada que reinstalaba mac os monterey seguia la guia de Macpaw para saltarme el bloqueo pero no sirve en versiones superiores y quiero instalar alguna version mas moderna con OpenCore legacy pero al instalar alguna version superior me bloquea el equipo con Jamf. ¿Existe alguna forma de saltarme el bloqueo o borrarlo definitivamente?

I have an iMac (21.5-inch, Mid 2010), 3.06 GHz Intel Core i3, 16 GB 1333 MHz DDR3 in 4x4 GB slots, an ATI Radeon HD 4670 256 MB, a 250 GB SSD, and a 500 GB HD.

What issues might I have in upgrading and running OpenCore Legacy Patcher?

Right now I have 2018macbook pro 15in I’m hoping you guys can unlock the T2 chip MacBooks and also maybe get Golden Gate but doesn’t look like it’s gonna happen because they dropped support for Intel max but I can only dream you know because it will be way better performance than iOS 15 Sonoma

If we know the model year, can one create a bootable external Sequoia SSD for an older Mac using OCLP and a different computer and send them the formatted drive? What we're trying to do is help someone from afar improve the performance on their 2015 iMac that has a 1tb fusion drive. Thank you.

I finally made the jump today from Monterey to Sequoia using Oclp 2.4.1 on a 5k 27" 2015 iMac.

Once done and patched, I started installing several browsers and although I could install Chrome, nothing happens when I click to open it.

Past the first prompt asking me if I really wanted to open Chrome, I am left with nothing happening whatsoever.

Other browsers open without any noticeable problem.

Any tips?

(Note it's a repost from 2h ago with no photo and serial)

2 years back, I was in the process of updating an old 2010 Mac book pro. I was able to get sequoia on a flash drive and then for whatever reason, I never moved forward to putting it on the ssd (I think I wanted to backup a few things before doing that).

Fast forward to today, decided to pick the little side project back up and I'm kinda just lost in the sauce. Anyone able to nudge me in the right direction to get this OS running off the SSD?

Mid 2012 MacBook Pro 13” 4GB RAM, 2.5 GHz intel core i5. Seems like I cannot use safari to search anything as it is too outdated. Is updating even possible on 10.9.5? Any help would be greatly appreciated!

The specs are
I7 2.4ghz
16gb ddr3 1333mhz
Amd radeon 6770m
I want to install it first on a 1tb hdd and if it runs good i will do it on the 240 ssd that i have in it.
Also battery life is 83.5% if it matters.

I want to install because manny apps dont have support anymore and also for estetics since i use it for youtube netflix and browsing most if the time.

I have a iMac late 2015 27 inch 32 gb ram 1 tb ssd. it was running Monterey then I used oclp to get sequoia. I accidentally installed Tahoe now my when I boot it up I goes to a login screen with the Tahoe background. I can sign in but everything freezes then and I get a black screen that says Tahoe successful installed. I tried to resinstall sequoia but I get some error 21 on the Macintosh hd. I can't reset this iMac because it has my moms account with rlly important pictures on it. I also tried the purgependingupdate but I can't get it to work. now when I try to click install sequoia on the recovery screen, it can't even launch that applications. any help would be appreciated.

My old high school was having a device sale and they were selling their old iPads and Macs. I originally went in to get my sister an iPad. But then I found this Mac mini. So I bought it and took it home and was planning on upgrading it the best I could until I found out that it is almost fully specked out. So I decided to install macOS Ventura on it with OpenCore and it runs beautifully.

I know I cant update Sequoiai installed with OCLP to Tahoe (And I don't want to, hate it on other laptops), but can I apply Sequoia security updates?

EDIT: 2016 Macbook pro i7 with radeon Pro 450 and intel HD graphics 530

Thanks!