There a alot of id´s hardware with that chip, Dit it work in Ventura OCLP?hello guys, does anyone know a solution to get a BCM 4350C2 bluetooth working ? can't switch it on. in Ventura no problems at all any advice would be great !
There a alot of id´s hardware with that chip, Dit it work in Ventura OCLP?hello guys, does anyone know a solution to get a BCM 4350C2 bluetooth working ? can't switch it on. in Ventura no problems at all any advice would be great !
You can do your analysis as follows:well no I can't test it because I did a upgrade from Ventura to Sonoma (ota) how do I check the OC EFI ?
Wrong approach, with all my respects to you, most respected sir.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? 🧐
yes it did perfectlyThere a alot of id´s hardware with that chip, Dit it work in Ventura OCLP?
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.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.
I guess I can't resist replies to attacks against me. I'll tell you what - you stop attacking, I'll stop responding. Sound good?Thought you said you made your point and where moving on…..
Its nightly , isn´t it?View attachment 2287664
Latest nightly fixes a whole bunch of stuff, including also fixing the last remaining issue I had on my 2012 Mini, certain apps like Fontbook not displaying text!
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?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.
Try to boot with an USB with prevuious OCLP you were using, and choose your hard drive to bootyes it did perfectly
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).+1 for deeveedee's suggestion (and trifero'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.
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.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
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.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:
That's it. Now you can choose between Big Sur and Sonoma when you boot your Mac. Enjoy.
- 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
Thanks for your suggestion and tipCongrats 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:
That's it. Now you can choose between Big Sur and Sonoma when you boot your Mac. Enjoy.
- 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
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.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
Wired connection?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.
Just be happy that you missed that conversation (although it wasn't nearly as fun as the OCLP security conversation we just finished).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.
Wired connection?
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.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?