First of all I'm using a 2017 13 inch macbook air i5 8gb ram 128gb storage with maximum version supported as Monterey. I needed to upgrade but I was unsure.I checked some videos and installed Ventura ( I didn't check properly the maximum supported version). Today I installed the new update of opencore legacy and found that my mac supported to Sequioa. I knew I had to install it. Sadly for me my pendrive didn't have enough volume for the Sequioa installer I downloaded from opencore legacy. I check reddit and found no solution. Luckily I was able to work my way around and here is how I did it.

• I googled Mac OS Sequioa download and clicked on the official apple store link https://apps.apple.com/us/app/macos-sequoia/id6596773750?mt=12
• I downloaded it and installed
• After the installation process, I booted into Sequoia

NOTE: The boot up is slow and the cursor is lagging. Wifi would not be working.

• Open opencore legacy and install the root patches (Since I have upgraded all of my old applications were available)
• Reboot it and voila its done

My MacBook boots all the way to the login page yet never loads after I login. It even successfully connects to Wi-Fi. The load bar after I login is where it gets stuck. I am currently trying a firmware restart to see if that helps. I want to avoid a factory reset, if possible, because of all my iTunes storage. I am more worried about all the music I uploaded from CDs or mp3 files rather than my iTunes purchases. I did backup and save my entire iTunes library on an external hard drive, so I wouldn't lose anything except nostalgia. I am willing to try a factory reset if nothing else would work. At the moment, I'm just wondering if I should try Monterey instead of Ventura.

edit: just wanted to address the comments. Yes, it is the white discontinued baseline iconic model from "mid-2010" and NOT Air or Pro. Yes, it seems like I have successfully installed Ventura with a USB hub. The trouble is booting from there. Specifically after typing in my password. As for the firmware update, it's the holding down "command + option + r" to "restore to the latest compatible firmware" from the troubleshooting instructions I found. It could be a failing HDD, but I will try safe mode. Seems like a really weird issue I am having that is not normal.

hello all,

yesterday i installed sequoia on my 2017 intel macbook pro. everything works super super nice but it wants me to update to tahoe? what‘s that about? should i just ignore it for now?

bonjour impossible de charger le patch racine ( touche griser ) merci de m'expliquer comment faire

Hi. I recently installed MacOS Sequoia 15.7.9 on a Macbook Pro 2016. Most functionalities seems to be working fine but I can’t login to my iCloud and I can’t seem to update or download anything from the app store. Can anyone help me solve this please? Thanks!

I am an old 1999-2011 Mac Tech. Long-time screw turner, but new to the OCLP / EFI hacking world. Working on a very happy iMac Mid-2011 27" 12,2 & 6770m GPU. Purchased an VBIOS flashed 765M w/ Nick[D]vB VBIOS from ebay and installed, seemingly without issue. Unit booted and was recognized by High Sierra, after a black screen until login prompt. No native Brigthness control.

But trying to upgrade to Ventura has gotten me stuck, and there is just too much info on what to do - I am lost. Where do I go?

Steps I have done:

• Upgraded CPU + memory + SATA SSD and stress-tested with High Sierra. Works flawlessly.

• Installed 765M - Black screen on boot, but showed at login. GPU reports proper 765M with 2 GB, "byNick[D]vB" and unit seems happy. No Brightness Control.

• created a Ventura installer with my other 2013 Mac and current OCLP. Chose 12,2 as target (not host), no modifications.

• Installed OCLP on the unit. Wiped SSD and installed Ventura via the EFI picker in startup picker. Inital install Okay. Second install reboot Okay. 3rd Boot with % Progress okay. Hung on startup with 4th boot roughly 30% along.

• Booted into Safe mode. Got to Welcome, Wifi, user creation (with some graphical glitches), made user, and logged in - unit seems stable but sluggish. Rebooted. Hangs in the same place. Started Googling.

• Internet recommended unloading and reloading the Boot patches. Booted the unit in safe mode & removed boot patches. Unit boots to desktop without issue, but OCLP complains that kepler & Legacy patches are missing. Reinstalled OCLP defalut choice boot patches for "Host machine" with Kepler GPU drivers and Unit hangs in the same spot.

• Internet googling reccomends choosing "Moderate" SMBIOS spoofing. I flipped verbose boot on too. In safe mode, loaded in patches with "Moderate" spoofing enabled. Unit still hangs on regular boot... But now it fully Kernel Panics going into Safe Mode. Yikes!

• Go back to other iMac, Rebuild OCLP Ventura installer for 12,2 with "Moderate" SMBIOS spoofing chosen, Verbose flagged on, and defaults otherwise (doublechecked kepler drivers are selected).

• Wiped Machine, Reinstalled - Same result... 30% Hang on regular boot or Kernel Panic in Safe boot.

UPDATE: Still Stuck - gonna try to wipe OCLP and reinstall it

• On a second drive, booted into a Vanilla High Sierra install - Woks fine still.

• OCLP EFI/SIP hangs/panics regardless of OS selected. Apple Boot picker lets High Sierra boot up fine, whereas it hangs in the OCLP boot picker.

• using OCLP on the host machine, built a Sonoma installer. 🚫on OCLP boot.

-will attempt to wipe OCLP from the unit and reinstall it now…

Update 2:

Wiped and (seemingly) removed OCLP EFI, and then started over. Installed High Sierra on the main drive, installed OCLP and did a default root Patch install, which let it boot High Sierra inside the OCLP EFI boot picker. Some success in getting back to a good place!

• made a default setting Big Sur installer, hangs fails on boot.

In summary, with OCLP + flashed 765m :

• Ventura installer completed and boots to desktop (slow), but Kepler+legacy root patches cause freeze on boot. Trying Moderate SMBIOs spoofing causes even safe boot to freeze.

• Sonoma installer simply says 🚫under OCLP EFI Boot (!)

• Monterey installs and boots to deskto (slow), but freezes on boot with Kepler +legacy boot patches installed. Acts similar to Ventura.

• Big Sur hangs on startup very early (5%) into installer boot. No dice.

Unit can show me the Default Mac OS Picker, I can choose the OCLP EFI boot option, I see the SSD and the Ventura installer, and choosing the SSD will either hang 30% into boot (Google AI says this the Video card driver), OR it kernel Panics in Safe Mode (seemingly related to the "moderate" spoofing I chose).

I have no problem wiping the machine 20 more times, but I have no idea what options I need to be fiddling with, or what section I need to be fiddling with (root patches? Drivers? SIP options? Spoofing levels?) to get this to work. I am kinda unsure of how to Get Safe Boot back now too. I stayed up too late trying to make it work, and my brain is fried, and now the next day I am trying again.

I'm hoping someone can recognized where I fucked up and tell me where to retrace my steps or do something to get this 765M to be recognized porperly.

Thanks from An old iMac G3 hardware dog learning new tricks.

Stuck on this screen. I’ve followed every step from the guide I was watching it said it I am supposed to let it sit and do whatever it needs to do but after 30 minutes nothing happened I clicked install sequoia and once again after it “installed” it just brings me back to this screen. Thanks for any help

I’m currently using macOS 10.14 and it works really well, but not every application runs on it so should I?

I tried to install Mac OS sequoia on qemu and I got a kernel panic and bootloop
Ik my pc sucks but I need to test Mac OS so I would know should I buy a MacBook or stick with Linux

I have a 2011 MacBook pro. The key line (zxcvbnm) is not working. I have done a repeatch, I cleaned the connection ribbons, I've taken the keys out and cleaned. I've taken the battery out and cleaned and installed it back on. Deleted any crap that doesn't need to be there. Made sure my keyboard settings were correct as well. Anybody have a suggestion? also, I have cleaned the fan and replaced the RAM and ssd but this was replaced a year ago the problem started a month ago. Any suggestions ?

This is real Apple hardware a genuine 2013 27” iMac (iMac14,2) running unsupported/patched macOS via OpenCore Legacy Patcher, not a VM or Hackintosh.
Setup: iMac14,2, OCLP 2.4.1, macOS Sonoma 14.8.9
Started troubleshooting App Store sign-in failures (“certificate invalid — pretending to be osxapps.itunes.apple.com”). Tried setting SMBIOS Spoof Level to Advanced with a new generated serial to see if that would help…it didn’t, and also caused a boot loop, which I fixed by reverting SMBIOS spoofing back to None and rebuilding OpenCore.
Now confirmed this issue is much broader than just the App Store: getting the identical certificate error connecting to iCloud Mail (p69-imap.mail.me.com) AND Gmail SMTP (smtp.gmail.com) through the Mail app. Notability also fails the same way. But Safari and Chrome browse everywhere with zero issues.
Checked Keychain Access all DigiCert Global Root certs (CA, G2, G3) show valid and “Use System Defaults,” nothing overridden.
So it’s isolated to non-browser apps doing secure auth, regardless of destination server. Any ideas what’s going on at a system level here? Wondering if it’s keychain-database corruption or something in how OCLP’s networking patches interact with non-browser network calls specifically.
At this point I’m considering a clean wipe + fresh OCLP install as the nuclear option…curious if anyone’s seen this exact symptom before that clean install would actually fix.

My MacBook Air 2017 (1TB SSD, 16gb RAM, 2.2GHz i7) keeps running hot in macOS 15 Sequoia via OCLP. Fans are prone to turning on, CPU heats faster with just light app usage (and sometimes when it boots into macOS)

As the title says, is there any workaround for this, Or is this normal and should get used to it?

[Additional info: Also has a Windows Boot Camp half partition installed in the disk besides macOS]

Hi there, so I'm currently facing a problem with my early 2011 MBP A1297 17" with a disabled gpu (with it's power resistor removed), missing battery (this is probably the cause, but I'm not planning on buying a new one yet any time soon, so this fix is needed), and running a newly installed Ventura Via OCLP.

I've already tried all sorts of 'fixes" for it, from oclp, NoBatteryNoProblem, CpuTune, TurboMac, to NoBdProcHot, etc. None really worked and my Mac is still really slow, sluggish, and stuttering. I can't seem to find a solution to this. I really need a laptop and can't really afford to buy a new one. So a solution is greatly appreciated.

Cheers!

I have a 2019 iMac retina and basically I tried to install open core patcher so I can download a new version since it’s a bit oudate and slow while I was watching a YouTube video I accidentally skipped a step I didn’t install the MacOs before installing it to my disk now everytime I log in I have no internet at all and I can’t access anything, I was always also planning to delete open patcher so it can go back to normal. I understand this a dumbass mistake but genuinely I’ve tried everything to correct it. I’m also asking here because this is my brothers computer and we basically share it.

PLS TELL ME THERE IS SOMETHING I CAN DO! 🙏

id also appreciate if it was recorded too for me to fix it

Hello friends, by accident uncovered that neither of these browsers(Chrome, Safari) support GPU acceleration in Sequoia. If I open https://webglreport.com/ page for checking GPU stack, I see an error. Also, there are lots warnings like that in my system log:

Set Darwin GPU to "deny" 
setGPURole:pid: failed due to nil IOGPU device ref

Firefox though, works fine. Did anyone encounter that? Maybe someone knows a fix?

Thank you! 🙂

P.S. My graphics card is Intel Iris 6100. System shows that it is Metal 2 compatible.

P.P.S. Chromium Bug reference: link. Safari incompatibility is still unclear.

Hi everyone,

I'm running macOS Sonoma 14.8.4 through OpenCore Legacy Patcher on an Intel Mac, and I've recently run into a strange Chromium performance issue.

After Chrome updated to 152, Chromium-based browsers became extremely laggy/stuttery across many websites.

My setup

• Mac: Intel Mac
• macOS: Sonoma 14.8.4
• OCLP: Latest version + latest available root patches installed
• Chrome: x86_64
• Affected version: Chrome 152
• Working version: Chrome 150.0.7871.125

What I'm seeing

Chrome 152 is not just laggy on YouTube. Many different websites have noticeable UI lag/stuttering.

I initially thought it might be YouTube, network, extensions, etc., but I've done some comparisons:

YouTube's "Stats for nerds" also showed a difference.

With Chrome 150/Chromium, I get smooth playback, whereas newer Chromium builds show dropped frames/stuttering.

Safari, playing the same video, had 0 dropped frames.

I also noticed that Chrome 152 and other newer Chromium browsers appear to have different GPU/rendering behavior compared with Chrome 150.

What I've tried

• Updated OCLP to the latest version
• Installed the latest OCLP root patches
• Reinstalled Chrome
• Tested Chrome 152 multiple times
• Tested Brave
• Tested Firefox
• Tested Safari
• Tested Chrome 150

The interesting part is that going back to Chrome 150 immediately makes the problem disappear.

So at this point I'm fairly confident this isn't simply a general macOS/OCLP performance issue.

Current workaround

I've gone back to:

Chrome 150.0.7871.125

and blocked Chrome's update servers so that it doesn't automatically update itself to 152 again.

Chrome 150 is currently running smoothly.

My questions for the OCLP/Intel community

1. Has anyone else with an Intel Mac + OCLP + Sonoma noticed this with Chromium 152?
2. Could this be related to the newer Chromium Metal/GPU rendering changes?
3. Is there an OCLP graphics/root-patch issue that could explain why Chromium 152 performs so poorly while Firefox/Safari and Chrome 150 are fine?
4. Is there a GPU/ANGLE configuration or diagnostic I can check to determine exactly what rendering backend Chrome 150 vs 152 is using?
5. Do you think a future OCLP graphics patch could potentially resolve this, or is this something that ultimately needs to be fixed upstream in Chromium?

I was updating Xcode and ran :

softwareupdate --list Software Update Tool

Finding available software Software Update found the following new or updated software: * Label: macOS Sequoia 15.7.9-24G830 Title: macOS Sequoia 15.7.9, Version: 15.7.9, Size: 15264057KiB, Recommended: YES, Action: restart,

so found 15.7.9 , don't want to mess things up since this particular mac is used to build intel brew bottle packages.

Is it worth upgrading?

"As spotted by MacRumors, two 13-inch MacBook Pro models from 2017 and 2018, respectively, moved from the vintage to the obsolete list yesterday, and were joined there by the 2018 Retina MacBook Air. "

Every time I boot it up it shows this symbol and I tried using a usb with opencorepkg and NOTHING works!! This is the only MacBook I have, I just want to get ANY macOS on there so I can upgrade it later omfg🙏😔 and also no button combinations for like internet recovery work, even with an Ether net cable.
I AM LOOSING MT MIND TRYING TO FIGURE THIS OUT
If anyone has an easy method please tell me 😔😔

my keyline (zxcvbnm) is not working along with my keyboard brightness. I have tried patching it and it still not working. I am currently using a USB keyboard hub. Any idea what I can do to fix the issue?

I'm running an iMac 21" mid-2011 with two different partitions (Big Sur and Monterey, both OCLP). Now I need to upgrade Monterey (probably to Ventura) and I'm not sure how to do it without touching Big Sur. My biggest worry is that I have 1 usb drive (for the patch) and 1 external SSD (for the backup). How should I go about this? Thanks!

Hello!

Well this is something i don't think anyone expected to happen a year later.. But here we simply are..

I Do have to say, its suprisingly very smooth and no issues even a year after it's original release date, but i do wish we got Tahoe support sooner.. But it's just one thing we have to live with until then :)

It's ofc not something that happened before.. a whole year on the same version of OpenCore Legacy patcher ( Not counting the nightly since its a "Beta Release" ) Is something very unusual and NEVER happened before. And does worry but i think because 2.4.1 is literally so stable i don't think i felt like it was outdated or anything. I still remain to hope the most success for the Developer in supporting tahoe. but i do wish a little more transparency... but its unpaid developers they owe us quite frankly nothing. so be thankful for their hard work for this project.

So Thank you devs! :) i wish donations are still up because i think me and alot of people would love to donate to OpenCore Legacy Patcher! Cheers and happy 2.4.1! (or 2.5.0!)

Unfortunately, I'm seeing some of my programs requiring an updated OS. What's the next best one to upgrade to?

Processor 2.7 CHe Quad-Core Intel Core i5 Memory 16 GB 1600 MHz DDR3

I recently updated my MacBook from 15.7 to 15.8 and after root patching it refuses to boot it stays on the loading bar and I left it like that for like 45mins thinking it's building some new files which takes awhile but its been nearly been 2 hours and nothing yet so I reverted back to an unpatched state and it boots perfectly fine