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
mac 15,1 with OCLP 1.0.0
I have noticed that memojis are not supported at all
it is already known not to use it as login picture
I have noticed that icloud, address book, iMessage....all apps that show memoji in prefs panels just freeze or crash trying to show memojis.
I have noticed that memojis are not supported at all
it is already known not to use it as login picture
I have noticed that icloud, address book, iMessage....all apps that show memoji in prefs panels just freeze or crash trying to show memojis.
Good morning...
what happens on iMac 12.1?
until this morning starting with efi was fine, I had OCLP 1.0 dated 1 Oct 11.32pm, this morning the system asked me to always update to version 1.0 but dated 2 Oct 5.49pm (which is also found in the official link of version 1.0) , it asked me to reinstall opencore and post-install patch by downloading the KDX add file of 670 MB... but now the boot with efi fails...
furthermore, the new version 1.0 is moved from the applications folder to a new folder created in Library>support application>Dortania
now I restarted the Mac with EFI and USB stick with Sonoma installer, but the normal restart fails after resetting PRAM and SMC too
I tried to re-enter version 1.0 of October 1st, reinstall opencore, but it doesn't start again from EFI
what happens on iMac 12.1?
until this morning starting with efi was fine, I had OCLP 1.0 dated 1 Oct 11.32pm, this morning the system asked me to always update to version 1.0 but dated 2 Oct 5.49pm (which is also found in the official link of version 1.0) , it asked me to reinstall opencore and post-install patch by downloading the KDX add file of 670 MB... but now the boot with efi fails...
furthermore, the new version 1.0 is moved from the applications folder to a new folder created in Library>support application>Dortania
now I restarted the Mac with EFI and USB stick with Sonoma installer, but the normal restart fails after resetting PRAM and SMC too
I tried to re-enter version 1.0 of October 1st, reinstall opencore, but it doesn't start again from EFI
Attachments
Last edited:
I freshly built OCLP 1.0.0 on my cMP 5,1 and it boots up Ventura 13.5 and Sonoma 14.0 perfectly. However, for me, the top bar WiFi icon was crossed out when booting into Monterey 12.7 (which has also been the case with some nightly builds and not others). I looked at the new config.plist and the AirportBrcmFixup.kext kernel injection patch was built with MinKernel = 12.0. I changed this to 22.0, as I believe my BCM943502CD is natively supported under Monterey, and I'm back to having working WiFi again on Monterey.
Could the MinKernel for this kext patch be one digit out for the 5,1 when being built ie. 12 instead of 22? However, 12 may be exactly what's needed for different Mac models or earlier OS's to force some wifi cards to work. However, for me, I needed to manually fix the MinKernel number for this patch. I left everything else automatically configured by OCLP 1.0.0.
Notwithstanding, I continue to be incredibly grateful to the developers for wringing out these hard-won OS gains on our older - but still impressive - Apple hardware.
Could the MinKernel for this kext patch be one digit out for the 5,1 when being built ie. 12 instead of 22? However, 12 may be exactly what's needed for different Mac models or earlier OS's to force some wifi cards to work. However, for me, I needed to manually fix the MinKernel number for this patch. I left everything else automatically configured by OCLP 1.0.0.
Notwithstanding, I continue to be incredibly grateful to the developers for wringing out these hard-won OS gains on our older - but still impressive - Apple hardware.
How did you update? Using OpenCore from USB drive or just through System settings?
Hi,
I have an early 2013 15" MacBook Pro with Ventura 13.6 and OCLP 1.0. In the system settings an update to Sonoma appeared. Is it safe to to update?
Thanks.
I have an early 2013 15" MacBook Pro with Ventura 13.6 and OCLP 1.0. In the system settings an update to Sonoma appeared. Is it safe to to update?
Thanks.
I upgraded using the same method, via System Settings. Everything is working fine.
Just successfully installed macOS 14.0 Sonoma on iMac 27" 14.2 (late 2013), i7 CPU and Nvidia GTX 780M.
ONLY FAILURE: Continuity Camera with my iPhone XS doesn't work with Sonoma, while it worked great with Ventura
First I installed OCLP 1.0.1, then I restarted the Mac and at Boot, at the sound of the Gong, I pressed and held down the Option key to then activate the new EFIBoot 1.0.1
After the reboot, from the Applications Folder I started the Sonoma's original Apple installer that I had created by downloading the Package using GIBmacOS; but it can also be downloaded from MrMacinbtosh.
At the end of the installation, the Mac restarted in Safe Mode.
BUT BE CAREFUL: on my first restart, perhaps because I use FileVault which immediately asks for the Password, I was unable to get to the Desktop screen and a black screen appeared with the clock at the top and the Password box at the bottom. Furthermore, it was not possible to write the password and the cursor moved jerkily.
So. I turned off the Mac from the button.
To be safe, I also connected the Magic Keyboard via the Lightening-USB cable.
I turned the Mac on, got to the Desktop screen fine and
OCLP offered me to install the Post Install Patch which I therefore installed,
I rebooted and now everything works, including LiveText, Remove Background, Music Mini-Player (now works also in full screen and doesn't crashes!), all Widget, Meteo included also in full screen, etc...
But Continuity Camera doesn't work
EDIT:
I corrected the OCLP version number which was wrong.
In the meantime I also tried to reinstall macOS 14.0 Sonoma with USB Key and OCLP 1.0.1 Official and idem for Post Install Patch; but Continuity Camera still doesn't work.
ONLY FAILURE: Continuity Camera with my iPhone XS doesn't work with Sonoma, while it worked great with Ventura First I installed OCLP 1.0.1, then I restarted the Mac and at Boot, at the sound of the Gong, I pressed and held down the Option key to then activate the new EFIBoot 1.0.1
After the reboot, from the Applications Folder I started the Sonoma's original Apple installer that I had created by downloading the Package using GIBmacOS; but it can also be downloaded from MrMacinbtosh.
At the end of the installation, the Mac restarted in Safe Mode.
BUT BE CAREFUL: on my first restart, perhaps because I use FileVault which immediately asks for the Password, I was unable to get to the Desktop screen and a black screen appeared with the clock at the top and the Password box at the bottom. Furthermore, it was not possible to write the password and the cursor moved jerkily.
So. I turned off the Mac from the button.
To be safe, I also connected the Magic Keyboard via the Lightening-USB cable.
I turned the Mac on, got to the Desktop screen fine and
OCLP offered me to install the Post Install Patch which I therefore installed,
I rebooted and now everything works, including LiveText, Remove Background, Music Mini-Player (now works also in full screen and doesn't crashes!), all Widget, Meteo included also in full screen, etc...
But Continuity Camera doesn't work EDIT:
I corrected the OCLP version number which was wrong.
In the meantime I also tried to reinstall macOS 14.0 Sonoma with USB Key and OCLP 1.0.1 Official and idem for Post Install Patch; but Continuity Camera still doesn't work.
Last edited:
Through System settings.
Judging by its size, it downloads a full image, so the installation principle should be the same, I think
For those wondering why I went off on my "silly" computer security tangent, it occurred to me how utterly insane I was for allowing uncertified, 3rd-party software to require that SIP be partially disabled, allow it to root my Mac (breaking the macOS "seal"), allow it to install uncertified software at the network layer (for Wi-Fi) and then to trust my Mac for anything that requires data privacy, data integrity and protected digital identity.
I am typing this on my MacMini8,1 that does not require OCLP (using wired Ethernet). I will be removing OCLP from my Macs and reverting to natively-supported macOS on those devices (macOS that does not require OCLP). I already changed all passwords associated with websites that I visited while using my OCLP-patched Macs.
In order for OCLP to be trustworthy for me, it would need one of the following:
============================
EDIT: I can't emphasize what I am saying strongly enough. I hope that through my assistance to some of you and through the answers that I have provided in this forum that I have at least demonstrated a small technical competence. The Devs clearly are software geniuses and are software experts. Computer security is my area of expertise, I am well-credentialled, heavily tested/certified and I don't take this lightly. This is too important to treat like a hobby.
When you know enough about computer security, you learn that the reality makes the conspiracy theories look like child's play.
I am typing this on my MacMini8,1 that does not require OCLP (using wired Ethernet). I will be removing OCLP from my Macs and reverting to natively-supported macOS on those devices (macOS that does not require OCLP). I already changed all passwords associated with websites that I visited while using my OCLP-patched Macs.
In order for OCLP to be trustworthy for me, it would need one of the following:
- The ability to patch graphics and Wi-Fi without breaking the MacOS "seal" (and thus without rooting my Mac) and the ability to perform the patches without requiring SIP to be partially or fully disabled - OR -
- A certified attestation of the chain of custody of the OCLP software (all of it - the python and the post-install patches) and a certification from a FIPS-certified lab that OCLP and the post-install patches are safe and secure. This certified chain of custody and lab test would need to accompany each new OCLP version.
============================
EDIT: I can't emphasize what I am saying strongly enough. I hope that through my assistance to some of you and through the answers that I have provided in this forum that I have at least demonstrated a small technical competence. The Devs clearly are software geniuses and are software experts. Computer security is my area of expertise, I am well-credentialled, heavily tested/certified and I don't take this lightly. This is too important to treat like a hobby.
When you know enough about computer security, you learn that the reality makes the conspiracy theories look like child's play.
Last edited:
The magic thing: no one force no one to use OCLP.
We all know it reduces security, it's the counterpart of installing uncertified software on uncertified hardware.
It's up to every people to decide if it's acceptable or not.
It's because Apple OS is not modular and because some of their software only work on the last OS that people have created OCLP and OCLP requires to lower security to work.
If I wasn't an Xcode user, I could stay on my supported Monterey for one more year before buying a new Mac.
Personally, I take the risk. I don't believe the (very) small amount of OCLP users is interesting a lot the hackers. They don't care a lot about macOS, so the small part of OCLP users is ridiculous for their needs.
Your conspiracy theory is a bit ridiculous and pollutes this thread. I don't know what you expect, make your choices and that's all.
We all know it reduces security, it's the counterpart of installing uncertified software on uncertified hardware.
It's up to every people to decide if it's acceptable or not.
It's because Apple OS is not modular and because some of their software only work on the last OS that people have created OCLP and OCLP requires to lower security to work.
If I wasn't an Xcode user, I could stay on my supported Monterey for one more year before buying a new Mac.
Personally, I take the risk. I don't believe the (very) small amount of OCLP users is interesting a lot the hackers. They don't care a lot about macOS, so the small part of OCLP users is ridiculous for their needs.
Your conspiracy theory is a bit ridiculous and pollutes this thread. I don't know what you expect, make your choices and that's all.
@rbart That's all well and good. If you look at the strategy employed by the Devs, you will notice that OCLP is designed to be "set it and forget it" so that even the non-technical Intel-Mac user can install OCLP and restore new life to their Mac. Every Intel-Mac user is now a candidate for OCLP - even those that don't frequent this forum.
That's a large addressable market of unsophisticated users who are unaware of the dangers.
I appreciate your view and opinion.
EDIT: When you know enough about computer security, the reality makes the conpspiracy theories look like child's play. If you believe that my warning is just a "conspiracy theory" ...
EDIT2: I am not telling anyone to stop using OCLP. What I am saying is that you should only use it when you realize that it exposes you and your Mac to computer security dangers that most reading this don't understand. Watch the news for ransomware incidents, stolen identities and hacked e-mail accounts. How do you think this happens? Hackers are not dumb. They are very smart, very clever and very sophisticated. And they don't have to be mean and ugly, so you may not even recognize them.
EDIT3: For those who are disappointed in me because I am "polluting this thread," I didn't come here to win a popularity contest. I am sorry if this reality is too much to digest. For me, this is exactly the kind of content that we should be discussing in a technical forum. Please continue to have fun. Just be safe doing it.
That's a large addressable market of unsophisticated users who are unaware of the dangers.
I appreciate your view and opinion.
EDIT: When you know enough about computer security, the reality makes the conpspiracy theories look like child's play. If you believe that my warning is just a "conspiracy theory" ...
EDIT2: I am not telling anyone to stop using OCLP. What I am saying is that you should only use it when you realize that it exposes you and your Mac to computer security dangers that most reading this don't understand. Watch the news for ransomware incidents, stolen identities and hacked e-mail accounts. How do you think this happens? Hackers are not dumb. They are very smart, very clever and very sophisticated. And they don't have to be mean and ugly, so you may not even recognize them.
EDIT3: For those who are disappointed in me because I am "polluting this thread," I didn't come here to win a popularity contest. I am sorry if this reality is too much to digest. For me, this is exactly the kind of content that we should be discussing in a technical forum. Please continue to have fun. Just be safe doing it.
Last edited:
yes i do on my imac 12.2 i can switch on my bluetooth but directly switch off again and not working
make it easy for you dude if your priority is security buy a new macbook that supported new macos. oclp aim is to continue to use legacy macs. this is so irrelevant you are doing this for days here at forum and on discord. make this space for disscusion for the user regarding on their concern using and installing sonoma.
For those who want to take measures to protect themselves after using OCLP on their Mac, these are the site/app passwords that I am changing after using OCLP:
- Apple developer password
- InsanelyMac
- MacRumors
- Discord
I am sorry that you don't like me any more. Darn - I was really hoping to win the MacRumors popularity contest. Oh well.
Hey all, I found some issues with Sonoma, which are probably not OLCP related, but I am going to report them anyway so people are aware:
I keep a copy of XQuartz around in case I want X11 access directly in macOS without a Linux, or other NIX VM.
Sonoma introduced a new type of desktop background feature that uses video instead of still images.
In order to make X11 work, XQuartz installs a couple of Plists for LaunchD that set display values. Well these seem to conflict with Sonoma's new desktop features where on reboot / login, the desktop will not have an image. It will have a plain grey background. In order to fix this, XQuartz must be uninstalled along with it's Plists. As I said, this seems to be a Sonoma issue, not OCLP as I was able to discover the issue by comparing my MBP to the iMac, and the only difference on the iMac was Xquartz.
So anyone who wants X11 support in Sonoma, OCLP, or otherwise, use Linux, either in a VM, or on a separate box or even a dual boot. It won't completely break the system if you continue to use XQuartze, it will just mess with the desktop features and you'll end up with a blank desktop if you want to use the new features. You could logout and back in to make the desktop background re-load, but I just suggest uninstalling for now, until XQuartz is updated to address this. Considering it's such an old project, and doesn't get a lot of updates now, and people want cross platform, then my above suggestion still stands. VM, separate machine, or dual boot.
I keep a copy of XQuartz around in case I want X11 access directly in macOS without a Linux, or other NIX VM.
Sonoma introduced a new type of desktop background feature that uses video instead of still images.
In order to make X11 work, XQuartz installs a couple of Plists for LaunchD that set display values. Well these seem to conflict with Sonoma's new desktop features where on reboot / login, the desktop will not have an image. It will have a plain grey background. In order to fix this, XQuartz must be uninstalled along with it's Plists. As I said, this seems to be a Sonoma issue, not OCLP as I was able to discover the issue by comparing my MBP to the iMac, and the only difference on the iMac was Xquartz.
So anyone who wants X11 support in Sonoma, OCLP, or otherwise, use Linux, either in a VM, or on a separate box or even a dual boot. It won't completely break the system if you continue to use XQuartze, it will just mess with the desktop features and you'll end up with a blank desktop if you want to use the new features. You could logout and back in to make the desktop background re-load, but I just suggest uninstalling for now, until XQuartz is updated to address this. Considering it's such an old project, and doesn't get a lot of updates now, and people want cross platform, then my above suggestion still stands. VM, separate machine, or dual boot.
BTW - I believe that Open Core is safe. It is only OCLP that I have a problem with for the following reasons:
Also, I have formulated an attack scenario that I would use to hack an OCLP-patched Mac. It is a multi-step process that I have shared with one person in this thread, but I will not share publicly.
- OCLP breaks the macOS seal. With the broken seal, macOS loses much of its ability to protect from other threats that are not OCLP
- OCLP injects 3rd-party, uncertified software into the network layer. Without attestation to chain of custody and without a FIPS-certified lab test, allowing this on your Mac is insane
- OCLP must partially disable SIP (the way SIP is partially disabled, I'm not especially concerned about this, but the combination of the broken seal and injected 3rd-party software with SIP expands the threat/attack surface)
Also, I have formulated an attack scenario that I would use to hack an OCLP-patched Mac. It is a multi-step process that I have shared with one person in this thread, but I will not share publicly.
Last edited:
Why? Isn't it important to have some security?
if you have OCLP 1.0.0 already installed, it's safe to update to Sonoma via the system settings...
I generally agree but so far all went smoothly here without clean install...🙏
Thing is what deeveedee is doing is basically just spreading paranoia and FUD.
His claim is correct in a way that the security will be lowered somewhat, this is simply because it is absolutely impossible to put back the proper drivers into the system or downgrade needed frameworks etc without breaking the seal. Access to the root volume is required for the internal system folders and frameworks to do patching.
A sizeable chunk of the patching is basically adding back drivers from previous OS's that Apple removed and downgrading things, then figuring out how to make them work with the changes on new OS's.
The same goes for SIP but OCLP is actually more intelligent about it and disables it only for the parts that are needed and not entirely, to maintain the best security that is possible while allowing patching.
Also if going by the logic he uses in the claims, OpenCore itself would be equally as bad if not worse since it injects many things directly into memory during boot, like BlueToolFixup for Bluetooth as an example. Root patching only came to be because there was no other way, as some things cannot be injected directly via the bootloader and have to be on disk.
EDIT: Also forgot to mention, the app is entirely open source and the code is readable in Github. As for attestations go, pretty unfeasible for such a small scale open source project especially if they cost money.