If you hold down the Option key as soon as the Mac starts to boot, you should see the OpenCore icon plus those of the various boot drives. To continue booting into the supported system, just select that drive's icon, this bypasses OpenCore. To boot into the unsupported OS, select the OpenCore icon first, then the icon for the unsupported OS.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 15 Sequoia on Unsupported Macs Thread
- Thread starter flagers
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
How safe is it to OTA update to Sequoia a Mac Pro 5,1 that is currently running Sonoma 14.7 via OCLP 2.0.1? Would creating a bootable USB Sequoia installer be preferable?
OK, just getting back to those who responded. I forgot to mention in my initial post that hitting option on boot automatically boots open core, even after the initial PRAM reset. If I restart again, then I can do as normal and select the Monterey volume directly. However, with this said because open core loads the first time it changes the sip config so even though I can directly boot monterey, the sip and SSV settings are still messed up. I've only been able to fully fix this by removing open core. Now, I wonder if part of this problem is because I'm not using separate drives / partitions for this dual boot, and just APFS volumes that all share the same space as the original Macintosh HD volume.
I thought about loading open core from a usb drive, so it's separate. That might fix the problem.
I thought about loading open core from a usb drive, so it's separate. That might fix the problem.
Thanks, I went and re-read your post to make sure I got what i missed the first read. I will give your suggestion a try. Thanks.
Just wanted to point out, I incorrectly said use Cmd+R to get to the boot selector. Of course, this is for Recovery. You use the Option/Alt key, but you probably knew that. Good luck.
Needs Kaby Lake or newer for hardware VP9 decoding, Apple defaults to 1080p with h.264. Use a 3rd party browser for software based VP9 decode.
I fixed the issue I was having. Here is what I did:
After using Sequoia, or any other patched OS.
1. Reboot as normal
2. Hold option
3. When open core appears, hit space bar
4. select reset NVRAM
5. Hold option and select the Macintosh HD (Monterey install) and this also resets SIP and SSV so it's in the correct state for the supported OS.
Very safe if you don't OTA update and instead install Sequoia in its own APFS volume while leaving Sonoma untouched.
2013 MBA 6,2 i5 with 8GB RAM report. Doable but slow. It's a test machine and the update was OTA. If you clean-install on a separate volume it might be faster. Will see if it perks up in future updates.
I've already done the Sonoma-to-Sequoia update. Without having done the Metalib workaround first. If I download and install the pkg..and then I reattempt the post-install patching..will my wifi be up-n-running, do you think? Thank you in advance. Your instructions, as well as the explanations you provide, are superhelpful for me!
Very, very slow. I make use of OCLP only so that I can download 'latest macOS only' apps.
I used OTA for a 13.2 Imac. It worked well.
Hi everyone! I’m trying to install Sequoia on my 8,1 iMac. I’m trying to make a fresh install. The installer doesn’t go any further the install disk selection. I select the disk (formatted in APFS, or in Mac Journaled, nothing change), I click on “continue” and nothing happens. I can go back and I can move through the installer, but I can’t go forward the installation. I tried to make the oclp usb with sip enabled but nothing changes. Any suggestions? Thank in advance!
Thank you again for this!
I got it working. My device's wifi. I've no idea how!
I went to the Metalib repo. [Thank you for the link!] I downloaded the version that's right for my 15.0GM environment. Before doing the install I went to the /Library/Application\ Support/Dortania/MetalibSupportPkg directory. In it I found a directory bearing the same version number as what you instruct me to install -- in other words the correct version has been there the entire time?!?
So I go off on some tangents. First I install the latest version in the repo overall. It's a version for macOS v15.1 beta.
Then I delete the directory for the *proper* Metalib version.
I redo the root patching.
Still, no wifi.
I reinstall Metalib version that's proper for macOS v15.0.
I redo the root patching.
Stlil, no wifi.
I see in the menubar a darkened (active) wifi graphic. But, in Safari, I cannot load webpages. I look at the 'details' screen for my wifi connection. I see that the 'Limit IP address tracking' button is turned ON. I turn it off. Lo! and behold! Wifi working again.
In this case, I think my issues attributable to the privacy setting??
Year after year, I hate Apple software more and more. Security theatre, privacy emphasis leading to complexity and/or bugs.
THANK YOU, kind readers, and especially @luckyduke23, for this advising!
I sort of feel the same with operating systems in general, most of all with Windows, sometimes Mac and sometimes Linux. The security threats are real and the "theatre" is always behind. I certainly don't want Apple to give up on security or privacy. If that happens I think will we be stuck waiting for some new player to take up the mantle. Who knows what might happen in the meantime. I'd probably have to switch to NixOS or something extreme on the Linux side which would probably be quite a bit less pleasant to operate. For now I am quite happy to still be able to run my aging MBP on a current MacOS. It works well for 90%+ of my daily needs and it's basically trouble free at this point except for my fan which is making a bit of noise now and then and might need to be replaced soon. I really appreciate OCLP and the devs and testers.
I'll suggest keeping an eye on Asahi OS 👀😍I sort of feel the same with operating systems in general, most of all with Windows, sometimes Mac and sometimes Linux. The security threats are real and the "theatre" is always behind. I certainly don't want Apple to give up on security or privacy. If that happens I think will we be stuck waiting for some new player to take up the mantle. Who knows what might happen in the meantime. I'd probably have to switch to NixOS or something extreme on the Linux side which would probably be quite a bit less pleasant to operate. For now I am quite happy to still be able to run my aging MBP on a current MacOS. It works well for 90%+ of my daily needs and it's basically trouble free at this point except for my fan which is making a bit of noise now and then and might need to be replaced soon. I really appreciate OCLP and the devs and testers.
Just a quick heads-up – I decided to dabble with an iPhone mirroring app out of sheer curiosity, and let me tell you, the GPU performance was a total mess! 🤯
It's like the whole app is swimming in a pool of glitches. It's like trying to run a VM or an early beta emulator – laggy, choppy, and full of weird visual artifacts. 😵💫
It's like the whole app is swimming in a pool of glitches. It's like trying to run a VM or an early beta emulator – laggy, choppy, and full of weird visual artifacts. 😵💫
OTA went super smoothly with mine (security didn't allow me to use the installer USB stick so i did OTA). All the others i did with the USB installer.
Attachments
I downloaded the file off of Mr Macintosh's website then installed---for some reason my imac 2012 showed the Sequoia update was available but said my computer was up to date.
which MacOS version do you use as a base to start? You cannot start with an unsupported OS but need to install the latest supported version first...then install OCLP and then do the upgrade...🤓
that is "most probably yes" as an answer to your question. During the patching you may already read in the logfile that OCLP is applying the metallib package...after restart your wifi shall work...
It worked on my 13.2 Imac with 2.01/OTA