How is the performance? , It's a bit sluggish for me, screensaver animation is choppy.smooth update macOS 14.0 Beta4
Build latest commit of sonoma-dev branch
Wifi connect imediatly as known network
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
System is ok here not perfect like Big Sur
no issue with screensaver I test Shuffle Landscape without problem
I‘m guessing the 2025 release will be the final version of macOS that runs on intel and only the 2019/20 macs will be able to natively run it.
You don't say now you did the installation; OTA or with a USB patcher? Which Beta were you truing to install?
Two suggestions:
1. This sort of problem can occur if an old installation file is cached somewhere.
Delete all your downloads, or move them to new folder. Shutdown the system, reboot and do an NVRAM reset. Download the Installer and OCLP again.
2. My iMac did not recognise the target drive until Beta 4 was available.
I performed a clean install of Sonoma 14.0 Beta 4 and repeated my post-install patching with OCLP 0.6.9 to make sure that I was correctly interpreting my test results. It turns out that AirportBrcmFixup.kext 2.1.7 can be either the OCLP version (with a plugin removed) or the Acidanthera version. Both "2.1.7" kexts allow working Wi-Fi in Sonoma. The key to applying post-install patches to the BCM 94352HMB (for me) was device spoofing. See my revised post here.
I misinterpreted my initial test results because I was experimenting with device spoofing and multiple versions of AirportBrcmFixup.kext at the same time. I have now repeated the clean installation of Sonoma 14.0 Beta 4 and application of OCLP 0.6.9 post-install patches and have confirmed that the Wi-Fi device must appear to OCLP post-install patcher as a Wi-Fi device in a real Mac (no surprise, since OCLP is designed and supported only for real Macs).
My BCM 94352HMB Wi-Fi is still working perfectly in Sonoma. After applying the post-install patches, I can disable the Wi-Fi device spoofing and Wi-Fi still works fine in Sonoma without the device spoofing.
EDIT: I performed yet another clean installation and patching of Sonoma to make sure that I accurately captured all steps. You can see my exact steps and sample files here. Ignore this if you have a real Mac.
EDIT2: I have confirmed that Sonoma Beta updates and OCLP post-install patches work perfectly with AMFI / LV fully enabled and AMFIPass.kext. No need to disable AMFI.
I misinterpreted my initial test results because I was experimenting with device spoofing and multiple versions of AirportBrcmFixup.kext at the same time. I have now repeated the clean installation of Sonoma 14.0 Beta 4 and application of OCLP 0.6.9 post-install patches and have confirmed that the Wi-Fi device must appear to OCLP post-install patcher as a Wi-Fi device in a real Mac (no surprise, since OCLP is designed and supported only for real Macs).
My BCM 94352HMB Wi-Fi is still working perfectly in Sonoma. After applying the post-install patches, I can disable the Wi-Fi device spoofing and Wi-Fi still works fine in Sonoma without the device spoofing.
EDIT: I performed yet another clean installation and patching of Sonoma to make sure that I accurately captured all steps. You can see my exact steps and sample files here. Ignore this if you have a real Mac.
EDIT2: I have confirmed that Sonoma Beta updates and OCLP post-install patches work perfectly with AMFI / LV fully enabled and AMFIPass.kext. No need to disable AMFI.
Last edited:
Mac Pro 5,1
and Samsung 970 Evo plus running Monterey
OCLP 0.6.9 nightly
if I boot Sonoma Public Beta 1 on a Sata SSD it stalls in the NVMe driver. It works on an identical machine with no NVMe.
and Samsung 970 Evo plus running Monterey
OCLP 0.6.9 nightly
if I boot Sonoma Public Beta 1 on a Sata SSD it stalls in the NVMe driver. It works on an identical machine with no NVMe.
is it a Samsung drive thing ? Do you have another NVMe drive you could test? (I know Samsung drives can have issues anyway)
Weird things happen with my "toy MP5.1"
Patched last week Wednesday with the second OCLP 068n from the afternoon and as far as possible things were working
Installed the 069n today and after the restart I want to patch ...
... and find out from OCLP that I have a non-supported host OS with Sonoma.
Neither start root patching nor revert root patching is possible.
Did I miss or overlook something what didn't exist last week? I've never seen this message before.
Patched last week Wednesday with the second OCLP 068n from the afternoon and as far as possible things were working
Installed the 069n today and after the restart I want to patch ...
... and find out from OCLP that I have a non-supported host OS with Sonoma.
Neither start root patching nor revert root patching is possible.
Did I miss or overlook something what didn't exist last week? I've never seen this message before.
Last edited:
Is the same message as using 0.6.8 Version where patching Sonoma is switched off.
Made a post some days ago when exactly the same thing happened to me.
If I remember correctly, that was with the 0.6.8.
Is there possibly something mixed up with the versions?
Made a post some days ago when exactly the same thing happened to me.
If I remember correctly, that was with the 0.6.8.
Is there possibly something mixed up with the versions?
@Mark1966
You mean like using the 068 first and then after the reboot try patching with the 069?
No, impossible because i used the OCLP 069 I just grabbed (from the certain place that shouldn't be linked), put it on a stick und used it from there.
This is even more weird because it says the i still have intalled 068n but I shou ....
I'm gonne wipe the whole OCLP whatever in the ESP and install it brandnew.
You mean like using the 068 first and then after the reboot try patching with the 069?
No, impossible because i used the OCLP 069 I just grabbed (from the certain place that shouldn't be linked), put it on a stick und used it from there.
This is even more weird because it says the i still have intalled 068n but I shou ....
I'm gonne wipe the whole OCLP whatever in the ESP and install it brandnew.
No first i tried the new 0.6.8 because I thought it was the newest, but i learned that it not supports Sonoma for post patching.
Version 0.6.9 that i am using is build from 27.07.2023 at 19:11
With this version all Ok here!
What date has the version that gives you the problem ?
What version do you have in library/application support/Dortania ? please have a look there !
That must be a Version 0.6.8 because from the version at this place comes the message to update to new version.
hope this helps
or this is a bug because i have never seen version that tells about nightly
i will try to load current nightly and post what it tells to me !!
current loaded nightly is from 26.07.2023 21:55 but all ok with this version for post patch on imac 12,2
but why is current nightly older than my used version, maybe i have build this by myself !?
Version 0.6.9 that i am using is build from 27.07.2023 at 19:11
With this version all Ok here!
What date has the version that gives you the problem ?
What version do you have in library/application support/Dortania ? please have a look there !
That must be a Version 0.6.8 because from the version at this place comes the message to update to new version.
hope this helps
or this is a bug because i have never seen version that tells about nightly
i will try to load current nightly and post what it tells to me !!
current loaded nightly is from 26.07.2023 21:55 but all ok with this version for post patch on imac 12,2
but why is current nightly older than my used version, maybe i have build this by myself !?
Last edited:
You have to use nightly from sonoma branch -not from main branch.
I thought I did because I switched from main to sonoma branch but apparently not.
Do it again ...
Yes, checking the host OS was tightened just before OCLP 068 was released. The main OCLP branch supports upto Ventura.
The sonoma branch is needed for post-install patching under/for Sonoma. So please use 069 nightlies from the sonoma branch.
MBP9,2 updated successfully to public beta 2 using nightly sonoma branch. Root patch needs to be re-applied.
... which I did today (no unsupported Host OS
):
However, I couldn't see any differences compared to the 0.6.8n: the WLAN works as it did with the 0.6.8n, BT can be set to ON, but it flashes back to OFF after a few seconds.
No BT device recognized although the MM is directly in front of the display
I'm trying to install Sonoma on my Macbook Pro 2016 with Ventura, but no success, i'm using the OCLP 0.6.9 - sonoma branch and if i try to install using the usb it doesn't show my SSD to select and proceed with the installation and if i try to install via OTA, after reboot and when the installation starts i got a 🚫 support.apple.com/mac/startup 🚫 message on the screen, anyone with the same problem?
I have the exact same issue MacBook Pro 2017 - OCLP 0.6.9
Request to OCLP Developers
Could you please add the MacBook Pro 13,2 to the Restore S1X/S3X Drive Support for 14.0 Beta 2 plist.
I have a MBP 13,2 with the Apple AP0256J NVMe SSD and it’s not seen by Sonoma beta 4 or earlier. I’ve installed Sonoma on an external USB drive and everything works well apart from not being able to access the internal drive.
I’m wondering if this would help the 2 posts above who seem to be having the same issue.
Many thanks and keep up the great work!
Could you please add the MacBook Pro 13,2 to the Restore S1X/S3X Drive Support for 14.0 Beta 2 plist.
I have a MBP 13,2 with the Apple AP0256J NVMe SSD and it’s not seen by Sonoma beta 4 or earlier. I’ve installed Sonoma on an external USB drive and everything works well apart from not being able to access the internal drive.
I’m wondering if this would help the 2 posts above who seem to be having the same issue.
Many thanks and keep up the great work!
Last edited:
Will try this soon, I patched my 2012 MM weeks ago, it didn't go well.
Have Ventura installed on a HDD, man, soooo slow.
Have Ventura installed on a HDD, man, soooo slow.