Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
Yes, you are right. This technology is only usable for nerds who want to spend much of their life time fiddling around on old machines to save a few bugs.

I took your advice and switch back to Monterey and will use it until Apple stopps providing security updates.
Then I will buy a new macMini which is not too expensive and avoid frustration on having achieved nothing after spending a weekend on this stuff.
My intent was not to discourage you, especially since it sounds like you are very close to a working solution. I was offering another way to understand what you're attempting to do. A bit more patience is all that's required to have your issue resolved. But it's likely that you will encounter a similar situation again and will benefit from a basic understanding of the internals.

@educovas was referring to partially disabled FeatureUnlock in the OCLP Settings GUI
Screen Shot 2023-05-13 at 9.41.34 AM.png


If you don't know how to edit your OC config.plist, Open OCLP GUI and change "Misc Settings > Feature Unlock Status" to Partially enabled or Disabled, Return to main menu and rebuild open core. Use the new Open Core build (EFI) to boot your rig.

EDIT: If it's any consolation, I prefer Monterey to Ventura on my MBP6,2. It's more responsive and MS Remote Desktop works better in Monterey (for me). I have Big Sur, Monterey and Ventura installed on my Mac and am finding more and more that I only need Ventura when I need to run XCode 14.3 (which is not supported in Monterey).
 
Last edited:
  • Like
Reactions: retiarius and olad
I was able to modify the OCLP's "config.plist" file get "Live Text" and "Remove Background" to work perfectly with no issues or Kernel Panic in my unsupported iMac with macOS Ventura and OCLP 0.6.2-Night.
Ventura works fine now with all its new features except "Continuity Camera".
My hardware configuration includes iMac 14,2 Late 2013 with CPU i7 (24GB RAM) and nVidia GTX780M graphics card (4GB VRAM)
So may i suggest OCLP's Developers to replace "revblock=media" with "revblock=auto" for iMac 14,2 like mine, recognising the hardware machine at OCLP startup.

Note for Nerd ;) As you can see from the attached screenshot, I used OpenCore Configurator to apply this change, but it is possible to use an editor like BBEdit or others.

WARNING! I advise against making changes to anyone who is not a very expert user and able to unlock the Mac if it were to lock it due to some involuntary error or if this change caused a Kernel Panic in his Mac and he would not know how to fix.

Post also to the kind attention of @khronokernel
Thanks for posting this also works on my mid 2014 Mac Pro on 13.2.1.
 
You could run this command on terminal: sudo defaults write /Library/Preferences/.GlobalPreferences.plist Moraea.EnableSpinHack -bool true and it should animate. It's not perfect but might be enough if you care about that
Thank you, that works well, spinning wheel now animated (MBP5,2, 13.4RC2, OCLP 066n latest).
 
Hi,

I am using a late 2012 27" iMac 13,2 with 13.3.1 and OCLP 0.6.5. It was a fresh install coming from the latest official supported MacOS. Unfortunately I can't activate the camera and mic on any Zoom, Webex, Skype,... Any suggestions how I can solve that issue please?
 
Hi,

I am using a late 2012 27" iMac 13,2 with 13.3.1 and OCLP 0.6.5. It was a fresh install coming from the latest official supported MacOS. Unfortunately I can't activate the camera and mic on any Zoom, Webex, Skype,... Any suggestions how I can solve that issue please?
See post #5507 in this thread. That question has been answered several times. Or do a search for tccplus wrapper.
 
My intent was not to discourage you, especially since it sounds like you are very close to a working solution. I was offering another way to understand what you're attempting to do. A bit more patience is all that's required to have your issue resolved. But it's likely that you will encounter a similar situation again and will benefit from a basic understanding of the internals.

@educovas was referring to partially disabled FeatureUnlock in the OCLP Settings GUI
View attachment 2201543

If you don't know how to edit your OC config.plist, Open OCLP GUI and change "Misc Settings > Feature Unlock Status" to Partially enabled or Disabled, Return to main menu and rebuild open core. Use the new Open Core build (EFI) to boot your rig.

EDIT: If it's any consolation, I prefer Monterey to Ventura on my MBP6,2. It's more responsive and MS Remote Desktop works better in Monterey (for me). I have Big Sur, Monterey and Ventura installed on my Mac and am finding more and more that I only need Ventura when I need to run XCode 14.3 (which is not supported in Monterey).
Thanks for your detailed instruction.
I already tried these 2 possibility and nothing has helped.
After this, I reinstalled Monterey and will use it probably for one additional year.

Maybe in one year from now, I will do a final try with OCLP and Ventura hoping that the tooling is more DAU friendly.
 
  • Like
Reactions: deeveedee
I was reviewing OCLP 0.6.6 changelog and saw a reference to NVidia Tesla WebDriver-387.10.10.10.40.140. Is anyone using NVidia web drivers with their legacy NVidia graphics? Would we benefit from applying NVidia web drivers to our unsupported Macs with NVidia graphics?
I found some posts in other forums that implied that OCLP is already installing NVidia webdrivers. Is this true (is it true that OCLP is installing NVidia web drivers as part of the post-install patching)?

Also, I noticed in "OCLP > Settings > Developer Settings" for my MBP6,2 that "Delete Unused KDKs" is unchecked by default.

Screen Shot 2023-05-14 at 8.37.34 AM.png


The tooltip indicates that deleting unused KDKs saves space. Should we be checking "Delete Unused KDKs" to save space when applying post-install patches?

Thank you.

EDIT: I noticed that OCLP retains user preferences, so it is very possible that I had unchecked "Delete Unused KDKs" during a previous use of OCLP (although I'm not sure why I would have). With this new information, I can't be certain of the default selection of "Delete Unused KDKs."
 
Last edited:
image.jpg
image.jpg

I need some help here guys . I have a iMac 14,2 here running OCLP 0.6.5 and the latest Ventura . I can only boot in safe mode and whenever I try to root patch to boot normally , it’ll get stuck on this screen
 
I need some help here guys . I have a iMac 14,2 here running OCLP 0.6.5 and the latest Ventura . I can only boot in safe mode and whenever I try to root patch to boot normally , it’ll get stuck on this screen
Your screen shot shows that you're running 13.1 (not "the latest Ventura"). There were issues with early Venturas - not sure if that's part of the problem. If you need Ventura and this is your first test with Ventura, I'd start with 13.2.1.

Also, what Make/Model SSD is installed in your iMac14,2?
 
Last edited:
View attachment 2201956View attachment 2201955
I need some help here guys . I have a iMac 14,2 here running OCLP 0.6.5 and the latest Ventura . I can only boot in safe mode and whenever I try to root patch to boot normally , it’ll get stuck on this screen
You must checked amfi disable
View attachment 2201956View attachment 2201955
I need some help here guys . I have a iMac 14,2 here running OCLP 0.6.5 and the latest Ventura . I can only boot in safe mode and whenever I try to root patch to boot normally , it’ll get stuck on this screen
You must disable Amfi in OCLP.
 
Last edited:
Possible to guide me ? Apologies on it .
Start the OCLP app, no need to use the USB version.
In the OCLP menu, select Settings, the Developer Settings, and
make sure "Disable AMFI" is checked. (You may want to increase the timeout setting for the Boot Picker to 10 seconds (default is 5)).
Return to the main window and run the "Build and Install" to disk (choosing the internal SSD and then the internal EFI partition). After a reboot you should be OK, but you may need to run the post install root patches again.
Finish
 
Start the OCLP app, no need to use the USB version.
In the OCLP menu, select Settings, the Developer Settings, and
make sure "Disable AMFI" is checked. (You may want to increase the timeout setting for the Boot Picker to 10 seconds (default is 5)).
Return to the main window and run the "Build and Install" to disk (choosing the internal SSD and then the internal EFI partition). After a reboot you should be OK, but you may need to run the post install root patches again.
Finish
Ok lemme try on it now . I'll update on it .
 
View attachment 2201956View attachment 2201955
I need some help here guys . I have a iMac 14,2 here running OCLP 0.6.5 and the latest Ventura . I can only boot in safe mode and whenever I try to root patch to boot normally , it’ll get stuck on this screen
Or if not is there any way for me to reinstall macOS Monterey with OCLP ? I've been trying to reinstall using a USB made from OCLP with the right macos type , but whenever I boot , it'll get stuck and theres no way to get to a boot page .
 
Start the OCLP app, no need to use the USB version.
In the OCLP menu, select Settings, the Developer Settings, and
make sure "Disable AMFI" is checked. (You may want to increase the timeout setting for the Boot Picker to 10 seconds (default is 5)).
Return to the main window and run the "Build and Install" to disk (choosing the internal SSD and then the internal EFI partition). After a reboot you should be OK, but you may need to run the post install root patches again.
 

Attachments

  • image.jpg
    image.jpg
    614.8 KB · Views: 71
Hello Need an invitation to Discord Server Open Core Legacy patcher as I mistakingly erased it.
Thy Jan
 
How are you posting here? Do you have another Mac?
That kernel panic screen shot doesn't look good. How did you make the OCLP USB OS install memory stick?
If you made it on another Mac, ie., not the target iMac 14,1, you MUST specify the iMac 14,1 in the setting menu, and the disable AMFI item in the Developer's Settings menu before you use the Build and Install to disk (USB OS installer disk). Then, when booting up, on the iMac with the USB startup disk, first reset the PRAM (NVRAM) via holding down the Option+Command+r+p keys at startup (hold them down until you hear the BONG twice).
Then hold down the Option key at boot, and first chose the EFI icon, and then the target SSD or HDD icon.

I haven't really looked at that kernel panic screen shot, so I can't tell what was causing the panic.
Are you sure the hardware is OK? Kernel panics are usually hardware related or basic system software related, serious glitches indeed. I have never seen one on my late 2014 iMac15,1 model.
Try to get us some more information, as it is I have no idea as to how to proceed.
 
  • Like
Reactions: coolio2004
I would like a little help I just finished installing Ventura 13.1 with opencore legacy patcher on my Macbook Pro 13' 2010 and it is working fine so far, but I can't get Siri to work. Does Siri simply not work with this machine in ventura anymore? Or is there something I have to do to get it working again?
 
Meanwhile I found this (following) seeting - maybe someone could help out 🙏 what exactly to expect from this setting before I make a new try with 13.4 (as I wrote #5,442 my 15" rMBP, Mid 2014 (base model) is crashing with 13.3.1):
In OCLP - Misc Settings is an option checked "NVMe Power Management" and popup says is for "with upgraded NVMe drives". But I have no upgraded NVMe drives, so should I uncheck it??
tempImageMZBP2g.png tempImageaYtQR6.png
 
  • Like
Reactions: MacRumors3590
Meanwhile I found this (following) seeting - maybe someone could help out 🙏 what exactly to expect from this setting before I make a new try with 13.4 (as I wrote #5,442 my 15" rMBP, Mid 2014 (base model) is crashing with 13.3.1):
In OCLP - Misc Settings is an option checked "NVMe Power Management" and popup says is for "with upgraded NVMe drives". But I have no upgraded NVMe drives, so should I uncheck it??
View attachment 2202202
If you do not have an NVMe drive, as I don't (mine is PCI), it makes no difference. If you do have an NVME drive, then if you are experiencing the kernel panics associated with the drive (some OWC drives caused this), then you need to enable it. For ordinary PCIe drives, it doesn't matter
 
Meanwhile I found this (following) seeting - maybe someone could help out 🙏 what exactly to expect from this setting before I make a new try with 13.4 (as I wrote #5,442 my 15" rMBP, Mid 2014 (base model) is crashing with 13.3.1):
In OCLP - Misc Settings is an option checked "NVMe Power Management" and popup says is for "with upgraded NVMe drives". But I have no upgraded NVMe drives, so should I uncheck it??
Not sure how technical you want the answer to be, but when checked, OCLP includes NVMeFix.kext in the OpenCore EFI. You can learn more about the kext here. As olad said, if you don't have an NVMe drive, it makes no difference.

For those who have upgraded their NVMe SSDs (and even their SATA SSDs), Macs and macOS can be picky about the manufacturer and model of the SSD. If you're having boot issues after upgrading an SSD and all attempts to fix have failed, it may be worth looking at the SSD. See this and this.
 
@olad @deeveedee Thanks for your answers.
Okay, if that doesn't make a difference, then I'll leave it enabled as OCLP preset it for the MacBookPro 11,2.😉

Then I don't know what else it can be that my 15" rMBP, mid 2014 (base model) with macOS 13.3.1 always crashes to the LogIn page (cursor jumps to left-up at the same time).🤷‍♂️😔

Would be very thankful🤗 if someone of you OCLP experts could have a look at the crash reports (see here: #5,377). Maybe you have some ideas for a solution?
 
Similar experience/outcome as 22F62, LS working but Apple TV not playing videos/streams.
I take back the issueless operation on 22F63, after waking up from sleep both my wifi and wired connections are unstable (unable to connect), only way I can get things working is rebooting. This does not happen all of the time, I just put my machine to sleep just before and woke it up to return to normal operational state - seems to be hit or miss.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.