Sidebar Sidebar
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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
reneroeten said:
well no I can't test it because I did a upgrade from Ventura to Sonoma (ota) how do I check the OC EFI ?
Click to expand...
You can do your analysis as follows:
  1. Find the version of OCLP that you were using and that produced working Ventura Bluetooth
  2. Use that version of OCLP to "Build and Instal Open Core" to a USB stick
  3. Compare the config.plist in the EFI on the USB Stick to the one you're now using with Sonoma. Also compare kext versions. What is different?
 
K two said:
How about getting REAL?! Has anyone on this forum or any other reported and CONFIRMED a verifiable security breach using OCLP OR OpenCore in ANY form or function???? If so, please post some evidence. Otherwise, we can all get back on-topic? :rolleyes: 🧐
Click to expand...
Wrong approach, with all my respects to you, most respected sir.
 
  • Like
Reactions: K two
MacNB2 said:
If you think OpenCore is safe, then you need to check its architecture first.
OpenCore achieves its objectives by hacking ... urr sorry..patching the kernel...or jailbreaking.
Lily.kext is the patcher that hacks the kernel in memory.
If that can hack the kernel.....then where's your security ?
Also, OpenCore injects kexts in the Kernel cache...that in effect exposes a risk of rogue actors' kext being injected.
So your hackintosh's are safe ? ...no need to answer back here.

OCLP is a "configurator" for OpenCore firstly and then a patcher for things that are impossible for OpenCore to patch "on the fly" because of the new security model Apple has created.

So if you have security concerns with OCLP, then that's not what you should be worried about but OpenCore itself as well.

Anyway, I think your discussion here in this thread is going off topic and you should really start a separate thread as it is an important topic that does need to be discussed by those who are concerned...just not here IMHO.
Click to expand...
I am not an expert but I believe you pretty much answered what is the difference between patchers made by dosdude1 and OCLP patchers. Somebody was asking this question in one of the threads.
 
cybazaar said:
Installed OCLP 1.0.0 and MacOS 14 Sonoma on my MacBook Pro 15" Late 2013 (MacbookPro 11,2) using a USB installer. All is well after some gotchas to get the OS to start. It finally boots and everything seems to work. However, I still get a "macOS Installer" option at boot even though the USB stick is not plugged in. I can't find an installer on the disk either, so no idea what could be causing that additional boot option to be present.
Click to expand...
I think that means that the installer didn't actually finish (and so it didn't delete the macOS Installer). Are you in a position to attempt the Sonoma install again?
 
dfkinca said:
+1 for deeveedee's suggestion (and *******'s endorsement of that suggestion).

Having an option in OCLP that "allow the user to selectively disable post-install root patches " would allow me to operate my MacBookPro9,1 (with upgraded WiFi/BT card (to BCM43602)) without wireless network functionality root patching.

Thanks in advance.
Click to expand...
Now you, too, can forget about winning the MacRumors popularity contest. But I am glad you like the suggestion (even if my feature request was off-topic in this thread).
 
  • Like
Reactions: eSaF-Eddie
Sonoma beta 2 released comes in at 1.18gb if you revert patches .
Took around 10 minutes to install re-patched all went smoothly using latest OCLP release.
 
Last edited:
  • Like
Reactions: deeveedee
Hi@all :)

Just short questions:

I made it finally successful, to bring my MBP 6,2 to Sonoma. But I'm missing Stage Manager, as on my MBA M1. It's shown in System Preferences, but will not work. Is it, because of the resolution of the MBP?

Also, Maps will not show its maps. Also because of the graphics?

Thanks in advance, and Best regards from Switzerland,
Thomas
 
  • Like
Reactions: deeveedee
ThommiTechnik said:
Hi@all :)

Just short questions:

I made it finally successful, to bring my MBP 6,2 to Sonoma. But I'm missing Stage Manager, as on my MBA M1. It's shown in System Preferences, but will not work. Is it, because of the resolution of the MBP?

Also, Maps will not show its maps. Also because of the graphics?

Thanks in advance, and Best regards from Switzerland,
Thomas
Click to expand...
Congrats on your MBP6,2! Maps is a known problem for all non-metal Macs patched with OCLP. In my experience, you need to revert to Big Sur for working Maps. Fortunately, with OCLP (Open Core), you can run two different versions of macOS very easily. While there has been some debate about the legality of running two versions of macOS, you can tell from earlier discussion that I have no standards or morals, so this isn't an issue for me.

To install Big Sur as a second macOS on your MBP6,2, do the following:
  • Make sure you have enough storage space
  • Add an APFS volume
  • Use a bootable USB Big Sur macOS installer to install Big Sur in your newly added APFS volume
  • Apply post-install patches to Big Sur with OCLP
That's it. Now you can choose between Big Sur and Sonoma when you boot your Mac. Enjoy.
 
Last edited:
deeveedee said:
Congrats on your MBP6,2! Maps is a known problem for all non-metal Macs patched with OCLP. In my experience, you need to revert to Big Sur for working Maps. Fortunately, with OCLP (Open Core), you can run two different versions of macOS very easily. While there has been some debate about the legality of running two versions of macOS, you can tell from earlier discussion that I have no standards or morals, so this isn't an issue for me.

To install Big Sur as a second macOS on your MBP6,2, do the following:
  • Make sure you have enough storage space
  • Add an APFS volume
  • Use a bootable USB Big Sur macOS installer to install Big Sur in your newly added APFS volume
  • Apply post-install patches to Big Sur with OCLP
That's it. Now you can choose between Big Sur and Sonoma when you boot your Mac. Enjoy.
Click to expand...
Since when were there any legal questions about running multiple versions of macOS? I've done it off and on for years, especially for testing and never heard of such a thing. The only legal items I've ever heard when it comes to running macOS is that it has to be run on Apple hardware.
 
  • Like
Reactions: Mainyehc
deeveedee said:
Congrats on your MBP6,2! Maps is a known problem for all non-metal Macs patched with OCLP. In my experience, you need to revert to Big Sur for working Maps. Fortunately, with OCLP (Open Core), you can run two different versions of macOS very easily. While there has been some debate about the legality of running two versions of macOS, you can tell from earlier discussion that I have no standards or morals, so this isn't an issue for me.

To install Big Sur as a second macOS on your MBP6,2, do the following:
  • Make sure you have enough storage space
  • Add an APFS volume
  • Use a bootable USB Big Sur macOS installer to install Big Sur in your newly added APFS volume
  • Apply post-install patches to Big Sur with OCLP
That's it. Now you can choose between Big Sur and Sonoma when you boot your Mac. Enjoy.
Click to expand...
Thanks for your suggestion and tip :)

One last question: that the Trackpad isn't doing the page backward/forward in Safari, also a known bug, missing thing?

Maybe really the best, to revert to Big Sur :)
 
ThommiTechnik said:
Thanks for your suggestion and tip :)

One last question: that the Trackpad isn't doing the page backward/forward in Safari, also a known bug, missing thing?

Maybe really the best, to revert to Big Sur :)
Click to expand...
Each user has their own favorite apps and their own desired experience. My success and satisfaction with my MBP6,2 can't guarantee yours. I do like having the option to boot Big Sur and newer versions of macOS. I think you'll like it, too. Big Sur runs great on the MBP6,2.
 
MacinMan said:
Since when were there any legal questions about running multiple versions of macOS? I've done it off and on for years, especially for testing and never heard of such a thing. The only legal items I've ever heard when it comes to running macOS is that it has to be run on Apple hardware.
Click to expand...
Just be happy that you missed that conversation (although it wasn't nearly as fun as the OCLP security conversation we just finished).
 
Question regarding upgrading Ventura (installed with OCLP) to Sonoma.

With OCLP updated to version 1, can I upgrade via the system settings, or do I need to go through the entire process of creating an install USB key via OCLP?
 
Hello,

I allready installed Sonoma 17.0 with OpenCore 1.0 on my MacBookAir 7,2.
Finally is works, but some questions:
-in /"username"/libary/developer/ I have a CoreSimulater folder with 13Gb. Can I delete that?
-SilentKnight tells me I need a EFI update, SIP and SSV protection is OFF. Is this normal for an OCLP running system (not the EFI stuff ;-)???

M.
 
amaze1499 said:
Wired connection?
Click to expand...

Nope using the patch mentioned in a previous post for usb WiFi by chris1111 wireless usb adapter on GitHub works fine for me and a old adapter I have that used to be installed on a pc windows 7 or something.
 
Sigvard said:
I haven't updated my 2016 MBP yet but can someone let me know if I can still use my Watch to unlock the computer/keychain and use Apple Pay on the laptop with my Apple Watch?
Click to expand...
My 2017 15” MBP (MacBookPro15,3) on Sonoma RC and OCLP 1.0.0 does not let the watch unlock the laptop and Touch ID is broken. I think there are documented issues with the T1 chips - that would probably also break Apple Pay. But everything else I've used works perfectly.
 
Installed 1.0.0 and Ventura (14.0) on my Mid 2015 MBP 11,4.....All is working well so far. A few things to note:
--I had to reinstall HCL notes for my work (Simply installed the file DMG exe) and it worked again.
--As others mentioned, the set up process where it gets to "wallpaper" was brutal as everything was very sluggish. Once I got past that, I was prompted to install root patches, rebooted and all was good.
--So far it's snappy and with no sluggishness.

I (still) don't have "smart charging" while connected to power but I haven't since Ventura and OCLP. I simply use "Aldente".
 
So, for those who are using OCLP on a mac that still has an official supported OS, are you remembering to keep a copy of that OS installed so you can continue to patch the EFI with the firmware updates Apple bundles with the OS updates? That was the main advice given to me is to never go completely OCLP until the mac is fully out of support of firmware updates.
 
  • Like
Reactions: Sanmiguel71, m4v3r1ck, makra and 2 others
fyrefly said:
My 2017 15” MBP (MacBookPro15,3) on Sonoma RC and OCLP 1.0.0 does not let the watch unlock the laptop and Touch ID is broken. I think there are documented issues with the T1 chips - that would probably also break Apple Pay. But everything else I've used works perfectly.
Click to expand...
Is the watch listed under the "Lock Screen" settings?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back