I would guess because they have pushed on past that feature and are working on the issues raised by 14.4b1. It would be nice to get a point release, say 1.3.1, containing the recovery fix though.
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 14 Sonoma on Unsupported Macs Thread
- Thread starter dhinakg
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Probably because it’s not an urgent update.
When you develop a software you have to evaluate the benefits and risks of every update
With each upgrade, you know that it will break something for some people.
So you have to provide upgrades when it’s really useful
Well, I was thinking that as well, when they did 1.2.0 and then 1.2.1 to fix the issues before 1.3.0 was released. It raised the question because I thought open core releases were supposed to be alongside macOS releases, and for the most part they have until now.
Can anyone report if Sonoma via Open Core Patcher is running stable and running without issues on a MacBook Pro Retina 13" A1502 - Mid 2014 (4th gen Intel Core i5 Dual Core, 8GB Ram) ?
BigSur is the latest supported macOS on this machine, but BigSur has no more support, Sonoma or at least Ventura is the only way to go to receive updates past 2025. I am not sure if I should go to Ventura or Sonoma for this older machine, it will be used by a kid for school and ideally I would want everything to update smoothly just like it would be officially from Apple.
BigSur is the latest supported macOS on this machine, but BigSur has no more support, Sonoma or at least Ventura is the only way to go to receive updates past 2025. I am not sure if I should go to Ventura or Sonoma for this older machine, it will be used by a kid for school and ideally I would want everything to update smoothly just like it would be officially from Apple.
After spending a good deal of time perusing Dortania docomentation and having personal experience running many macOS betas with OCLP, nowhere is it written that OCLP does not support beta releases except in this one article. 🤷♂️ Also macOS 14.4b1 boots and runs intact in safe-mode with OCLP, the post-install patches clearly need work, however. FWIW 🤫
Sorry, hold the button down until the iMac beeps, 🎼 about 10 seconds. 🕙
With a mid-2014 Mini, Monterey is supported. Also, Security updates for X-Protect, XPR and MRT are available back to Catalina. Fear not.
and easy to keep current.
Actually the 18,2 is a 2017 model.
Identify your iMac model – Apple Support (UK)
Use this information to find out which iMac you have and where it sits in the history of iMac.
Everything works for me. The patch is working fine. Only the wi-fi driver has been removed. And so everything works! I can send you a video. I installed a third-party wi-fi and everything works!!!
I wouldn't want your desktop, it's way too cluttered and messy I have to have a clean and organized desktop myself.
The settings done in OCLP are only applied when performing a "Build and install" before closing the app.
Those settings aren't saved or read back from the EFI partition when opening the app, so you have to reconfigure everything each time you open the OCLP app.
OCLP is mainly an OpenCore configuration and install helper app - there are barely any true "settings" in the app.
In the attached video that mid-13 iMac has a non-stock GPU which is compatible with the current post-install patches, clearly.
Not what's in the sig. 🤨
Last edited:
Adobe products cant find "People" while using a masking feature. I successfully ran and updated my late 2013 iMac i7 with Sonoma 14.3. Seems all good But, while trying to use the recent masking features in Photoshop or Bridge that can detect “People”, it cant find any people even if they are obvious. Other features in masking work perfectly like select “Background” “Subject” “Object” etc. It’s just the “People” detection that “can’t find any people”. I’m guessing it has something to do with the modern day AI tech not working with the older hardware? Or maybe it’s a something I haven’t done? Tried running the patcher. All seems good. Any explanations or thoughts welcome. 🙏
I'm running a 13" MacBook Pro 2012 Retina (Ivy Bridge MacBookPro10,2) seemingly successfully
using Sonoma 14.3 after a Catalina upgrade via OCLP 1.30, running apps like Maps, Photos,
icloud.com, etc. which seem fine after cursory inspection.
My question relates to AVX2 support. The first posting here, with the heading "Spoiler: Things we will never ... be able to fix" warns that because AVX2 is not native until Haswell, some things
like Adobe software may not work. That's OK by me, but are there any Apple Applications which
break due to this? If they all are supposed to run just fine on my 2012 MBP, is it because
Rosetta now translates to the Intel instruction set without generating AVX2, or does OCLP
use some dynamic translation for AVX2 at least for Apple Apps?
Lastly, to determine if a random application (Apple or otherwise) needs AVX2, is there
some public script or app which can discern such?
My motivation for asking is that if I save the machine for use as a hand-me-down, what
caveats are there to pass on ... perhaps I'm old-fashioned, but I regard MacOS as not
just the kernel, but userland apps, too.
P.S. The work spearheaded by Grymalyuk et. al. is incredible -- I'm surprised that the
main developer is a student -- his conference slides are super. The reverse engineering
work is worthy of an instant master's thesis at minimum, or more formal publication
as an academic paper.
using Sonoma 14.3 after a Catalina upgrade via OCLP 1.30, running apps like Maps, Photos,
icloud.com, etc. which seem fine after cursory inspection.
My question relates to AVX2 support. The first posting here, with the heading "Spoiler: Things we will never ... be able to fix" warns that because AVX2 is not native until Haswell, some things
like Adobe software may not work. That's OK by me, but are there any Apple Applications which
break due to this? If they all are supposed to run just fine on my 2012 MBP, is it because
Rosetta now translates to the Intel instruction set without generating AVX2, or does OCLP
use some dynamic translation for AVX2 at least for Apple Apps?
Lastly, to determine if a random application (Apple or otherwise) needs AVX2, is there
some public script or app which can discern such?
My motivation for asking is that if I save the machine for use as a hand-me-down, what
caveats are there to pass on ... perhaps I'm old-fashioned, but I regard MacOS as not
just the kernel, but userland apps, too.
P.S. The work spearheaded by Grymalyuk et. al. is incredible -- I'm surprised that the
main developer is a student -- his conference slides are super. The reverse engineering
work is worthy of an instant master's thesis at minimum, or more formal publication
as an academic paper.
Last edited:
I have an imac 2011. Where do you see imac 2013? What kind of non-standard GPU are you talking about?In the attached video that mid-13 iMac has a non-stock GPU which is compatible with the current post-install patches, clearly.
For sure, that iMac27 late 2011 does not run a standard graphics card in the video. They were shipped with either AMD Radeon HD 6770M or Radeon HD 6970MIn the attached video that mid-13 iMac has a non-stock GPU which is compatible with the current post-install patches, clearly.
Perhaps this one is running an external GPU?
What’s more, the main developer of OpenCore (that’s the boot loader rootkit that makes OCLP possible) is a Russian computer scientist. Also due to this developer are Lilu (the in-memory patching engine) and other key extensions, all critical to OCLP.
Stand corrected on iMac year but remain firm on non-stock GPU, clipped from your video, attached.
🤔Does Beta 14.4 break opencore? I decided to use a video card with a Kepler chip and see if the patch can be fixed. The answer is yes, you can. My amd rx 5500 xt does not work on sonoma. After a crooked patch, amd 5500 did not fully work, but the screen is black, and then freezes.
Last edited:
macOS 14.4b1 runs intact with OCLP v.1.4.0n in safe-mode, the existing post-install patches break this release on a stock unsupported Mac. 🤔
14.4 b2 is out, but if you’re not a developer stay away from macOS betas ;-) and enjoy 14.3 till 14.4 release and oclp release 👍
The ARM VM solution won't work for me (apps in the VM would need to be ARM-compatible since there's no Intel emulation, and I wouldn't want emulation anyway). I have successfully migrated and built my Android and iOS apps in Visual Studio Windows. Microsoft has done an amazing job with their VS Windows solution. VS Windows connects to a Mac running Xcode for iOS builds and publishing. All iOS development and publishing is fully supported in Windows as long as VS can connect to the Mac. It may be that I just need to keep a cheap Mac that still runs the latest Xcode while doing all my development in Windows. The migration from MacOS to Windows was much easier than I expected.