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
what is your problem? you ask me what I saw then I simply answer you that I do not use it and you come back to me with this kind of useless comment
I was simply thanking you with an equally useless response.
This was already happening in Ventura for me on the widgets on the right sidebar. I would imagine with the fact that the widgets can be placed on the desktop in Sonoma that it will eventually be fixed.
I have Wi-Fi working with BCM 94352HMB. I'm not sure that this is all necessary, but here is what I did:
EDIT: It appears that the key to this working solution is the replacement of AirportBrcmFixup.kext 2.1.7 (Acidanthera version) with AirportBrcmFixup.kext 2.17 (the OCLP version). The two kexts have the same version number but are different.
EDIT2: After further testing, I have determined that the AirportBrcmFixup.kext does not matter (either the original Acidanthera AirportBrcmFixup.kext 2.1.7 or the "new" OCLP AirportBrcmFixup.kext 2.1.7 can be used. The key to patching the BCM 94352 is spoofing the device-id to a real Apple Wi-Fi device. After the post-install patches are applied, the AirportBrcmFixup.kext version (either Acidanthera's 2.1.7 or OCLP's 2.1.7) can be used.
===============================
I am posting this with FireFox in Sonoma 14.0 Beta 4 on my Mac over BCM94352 Wi-Fi 😀
EDIT2: After further testing, I have determined that the AirportBrcmFixup.kext does not matter (either the original Acidanthera AirportBrcmFixup.kext 2.1.7 or the "new" OCLP AirportBrcmFixup.kext 2.1.7 can be used. The key to patching the BCM 94352 is spoofing the device-id to a real Apple Wi-Fi device. After the post-install patches are applied, the AirportBrcmFixup.kext version (either Acidanthera's 2.1.7 or OCLP's 2.1.7) can be used.
===============================
Replace AirportBrcmFixup.kext 2.1.7 in OC/Kexts with the AirportBrcmFixup.kext 2.1.7 in the OCLP-Generated EFI (they have the same version, but have different sizes)- config.plist should not have VMM kernel patches and should have revpatch=sbvmm (for RestrictEvents.kext 1.1.2) - may not be necessary (haven't tested without)
- AMFI: should be disabled with amfi=0x80 and kernel patch or use AMFIPass.kext. I am using AMFIPass.kext with AMFI fully enabled.
- Implement ACPI patch to spoof pci14e4,4353
and PXSX->ARPT binary replace (if necessary)to apply post install patches. After patching, the device spoofing is not necessary. - Apply legacy wi-fi post-install patches with 0.6.9n 07.28.23 (use nightly build, not custom build)
- Wi-Fi device spoofing can be disabled after OCLP Wi-Fi patches are applied
I am posting this with FireFox in Sonoma 14.0 Beta 4 on my Mac over BCM94352 Wi-Fi 😀
Last edited:
I don’t believe the team can do anything once Apple ceases intel version completely. I think patching M o/S for intel is a bridge too far?
I that what @deeveedee means is that these OCLP threads and OCLP support will continue to support Intel macs dropped by apple. “Here“ is giving many, many intel macs longer support than Apple is / will.
Yes, more likely than not, when Intel versions cease to exist, they will probably not be portable to intel via patchers…… but sometimes amazing things happen. Never say never.🤷🏻♂️
Sonoma or macOS 15 will probably be the last intel / Apple silicon binary.
When will Intel mac users be "forced" to upgrade to silicon Macs?
Also, just keep in mind what happened with Snow Leopard on PowerPCs. Dropped by Apple, but the developer versions still contained PPC support that led to 10.6 on PowerPC after enthusiasts put a lot of work into it. See thread here.
Not completely ruled out that this might happen again with an internal / developer version of i.e. macOS 15 or 16 still holding (enough) intel code to get it up and running while first public releases are Apple silicon only already.
Waiting for Apple to drop Intel… let’s hope that in the meantime improving OCLP’s SIP enablement is still on the roadmap (it would be the ideal future complement of the excellent AMFIPass: with LV and AMFI fully enabled; and finally also SIP enabled, as much as technically possible):
What is the roadmap?
[…] After merging into mainline OCLP, research will be conducted to see if it is possible to enable more bits of SIP or even fully reenable SIP on OCLP machines. This is a long-term goal and there is no ETA on when this will happen or if this is even possible at all.… So, a big chance that macOS 15 Mammoth (i.e., a big update) - or whatever it will be called - will be Apple Silicon-only…? Very likely, yes (anyway, almost surely for macOS 16, if not 15): so, maybe also OCLP could evolve, in order to cater also for old (in the future) M1, etc. Macs…? Who knows…
Last edited:
This conclusion was incorrect. See revision here.
Last edited:
Hello the team. Install ok iMac 2017 with beta OCLP just patch wifi !!!!! Work 100% !!!!
Thanks team OCLP !!!!
Thanks team OCLP !!!!
Reverted patches on mid 2014 MacBook Pro downloaded software update 1.42gb for beta 4 using personal hotspot with my iPhone connected usb updated , re-patched no problems doing that way , Amazing work.
Update : editing a photo will crash photos and closing photos the status bar disappears abit higher and out of focus (opening safari restores it to its normal place) but on the plus Apple TV works perfectly without the vpn messing about on sonoma it just plays no hassle and again I get it’s a beta only trying because the Devs have been kind enough to let us.
Update : editing a photo will crash photos and closing photos the status bar disappears abit higher and out of focus (opening safari restores it to its normal place) but on the plus Apple TV works perfectly without the vpn messing about on sonoma it just plays no hassle and again I get it’s a beta only trying because the Devs have been kind enough to let us.
Last edited:
My 2012 MacBook Pro 9,1 is STILL 'unofficially' supported, and I've got Monterey 12.6.6 running well on my 2009 MacPro 4,1 (flashed 5,1) so Steve Jobs is STILL alive, since I believe he is who 'started' the HIGHLY UPGRADABLE MacPros?
This thread will be dedicated to the discussion of running macOS 14.0 on unsupported Macs.
At the time of writing, we are waiting for Apple to send out macOS 14 Developer Beta 1. It is currently unknown whether or not Apple will release a publicly-downloadable InstallAssistant.
We will be expanding this thread with much more information as the day goes by including known issues as well as patcher support.
macOS Sonoma Compatibility
- iMac 2019 and later
- iMac19,x
- iMac20,x
- Mac Pro 2019 and later
- MacPro7,1
- iMac Pro 2017
- iMacPro1,1
- Mac Studio 2022 and later
- MacBook Air 2018 and later
- MacBookAir8,x
- MacBookAir9,1
- Mac mini 2018 and later
- Macmini8,1
- MacBook Pro 2018 and later
- MacBookPro15,X
- MacBookPro16,X
* Machine supports the Metal Graphics API on macOS Ventura and older
** Machine is upgradeable to support the Metal Graphics API on macOS Ventura and older
+ Does not currently support any form of graphics acceleration
- Early-2008 or newer Mac Pro, iMac, or MacBook Pro:
- MacPro3,1 + **
- MacPro4,1 + **
- MacPro5,1 + **
- MacPro6,1 + *
- iMac7,1 + (2007 model, requires CPU upgrade)
- iMac8,1 +
- iMac9,1 + **
- iMac10,x + **
- iMac11,x + **
- iMac12,x + **
- iMac13,x + *
- iMac14,x + *
- iMac15,1 + *
- iMac16,x + *
- iMac17,1 + *
- iMac18,x *
- MacBookPro4,1 +
- MacBookPro5,x +
- MacBookPro6,x +
- MacBookPro7,x +
- MacBookPro8,x +
- MacBookPro9,x + *
- MacBookPro10,x + *
- MacBookPro11,x + *
- MacBookPro12,1 + *
- MacBookPro13,x + *
- MacBookPro14,x *
- Late-2008 or newer MacBook Air or MacBook:
- MacBookAir2,1 +
- MacBookAir3,x +
- MacBookAir4,x +
- MacBookAir5,x + *
- MacBookAir6,x + *
- MacBookAir7,x + *
- MacBook5,1 +
- MacBook5,2 +
- Early-2009 or newer Mac Mini or white MacBook:
- Macmini3,1 +
- Macmini4,1 +
- Macmini5,x +
- Macmini6,x + *
- Macmini7,x + *
- MacBook5,2 +
- MacBook6,1 +
- MacBook7,1 +
- MacBook8,1 + *
- MacBook9,1 + *
- MacBook10,1 *
- Early-2008 or newer Xserve:
- Xserve2,1 + **
- Xserve3,1 + **
- 2006-2007 Mac Pros, iMacs, MacBook Pros, and Mac Minis:
- MacPro1,1
- MacPro2,1
- iMac4,1
- iMac5,x
- iMac6,1
- MacBookPro1,1
- MacBookPro2,1
- MacBookPro3,1
- Macmini1,1
- Macmini2,1
- — The 2007 iMac 7,1 is compatible with Monterey if the CPU is upgraded to a Penryn-based Core 2 Duo, such as a T9300.
- 2006-2008 MacBooks:
- MacBook1,1
- MacBook2,1
- MacBook3,1
- MacBook4,1 (let´s see...)
- 2008 MacBook Air (MacBookAir 1,1)
- All PowerPC-based Macs
- All 68k-based Macs
An compilation of known new issues has been published on the OCLP Github. It might be enhanced when new beta versions hit the road and more road blocks appear ahead.
This is not the OCLP support list!
All machines capable of booting Ventura with OCLP will also theoretically boot Sonoma, however, the following machines have been tested.
This is an unconfirmed list of machines Apple dropped, but that have managed to boot Sonoma
(regardless of the patches/method required to enable them, * denotes GPU metal API patch support with appropriate GPUs, whereas + indicates non-metal acceleration patch support):
MacPro3,1 *
MacPro4,1 *
MacPro5,1 *
MacPro6,1 *
MacBook 4,1
MacBook 5,2
MacBook 5,2
MacBook 6,1
MacBook 7,1
MacBook 8,1
MacBookAir 2,1
MacBookAir 3,2
MacBookAir 4,2
MacBookAir 7,1
MacBookAir 7,2
MacBookPro 4,1
MacBookPro 5,1
MacBookPro 5,2
MacBookPro 6,1
MacBookPro 6,2
MacBookPro 7,1
MacBookPro 8,1
MacBookPro 9,1
MacBookPro 11,1
MacBookPro 11,5 *
MacBookPro 12,1
MacBookPro 14,2 *
MacBookPro 14,3
iMac9,1
iMac9,1 *
iMac11,1 *
iMac11,3 *
iMac12,1
iMac12,2 *
iMac18,3
...to be continued!
After many requests, we've finally opened up a way for people to make monetary contributions to OCLP's development, using Open Collective: https://opencollective.com/opencore-legacy-patcher If you appreciate what we do, please considering donating! Your support will help us purchase needed hardware to improve the project.
Thanks!
Hi, I have a 2017 Macbook Pro with touchbar and have upgraded the internal drive to a 1TB SSD. I have installed Ventura on it and that installed without any issues. I've created a Sonoma OCLP boot drive (using the latest version of OCLP) but when I try to start the Sonoma install, my Internal SSD is not detected.
Help!
Help!
Last edited:
You might need to give a little bit more information, but if you *just* installed a new SSD, and if you have never installed a new SSD and then tried an upgrade to your Mac before , you need to first format the SSD before you install macOS. In this case, you click on “disk utility“ from the main screen, and then click on the drive, format it APFS, and name it. Then, you will be able to install an OS on it.
If you have already done that, then my comment is not applicable to your situation, and the reason for your trouble is different. Have you tried installing Sonoma on the old SSD? You might need to give a little more information to get the proper advice here.