macOS 13 Ventura on Unsupported Macs Thread

[HotMrmt]

Does airplay work on the MBP with that dongle? (you may have to force the system to use the external BT controller)

Even then from what I can recall that dongle did use a Realtek chipset (which was not supported by MacOS), you’ll have to switch to a Broadcom/Cyprus based dongle, or swap your NIC assembly for one from a later model Mac..

Yes, AirPlay worked on that MBP with this dongle. I’ll try a Brcm dongle one as you suggest.

 

[deeveedee]

Can someone please tell me, re. Library Validation (not talking about Patcher Settings with option to disable): what should be the default, disabled or enabled? (Long story: ran sudo nvram boot-args=amfi_get_out_of_my_way=0x1, which appears to have disabled Library Validation, and which I have tried reversing so far with no luck).

Wondering if Library Validation disabled is needed to run OCLP

Seeing com.apple.security.libraryvalidation.plist set to disabled in /Library/Preferences

I understand your question just well enough to know that it doesn't belong in the OCLP Security thread. Other than that, I'm not sure what you're asking. I'll take a guess without fully understanding and hope that this helps.

In my opinion, you should always try using OCLP to build/install your Open Core EFI with unchecked "Disable Library Validation" and "Disable AMFI" (uncheck the boxes in the OCLP GUI). You should not need to manual inject any amfi-related boot-args in NVRAM.

If that doesn't answer your question, I apologize for not understanding the question.

EDIT: Note that you will need to "Build and Install Open Core" any time you manually change/override the "Security" settings in the OCLP GUI (different from the security discussed in the "OCLP Security" thread). You should be able to experiment with different Library Validation and AMFI settings simply by: 1) check/uncheck the boxes in the OCLP GUI, 2) Build and Install Open Core and 3) reboot. You should never need to manually inject boot-args or manually modify the Open Core config.plist unless that's your preference (I do manually modify config.plist for experiments, so I'm fully supportive of this if you want to and are able to). I'd recommend doing your OC EFI experimentation with a bootable, GUID partitioned USB thumb drive. Keep your SSD EFI untouched so you have a reliable boot drive.

EDIT2: @RK78 Just out of curiosity, are you trying to use OCLP on a Mac where you previously (or currently) installed the DosDude patches?

 

[RK78]

I understand your question just well enough to know that it doesn't belong in the OCLP Security thread. Other than that, I'm not sure what you're asking. I'll take a guess without fully understanding and hope that this helps.

In my opinion, you should always try using OCLP to build/install your Open Core EFI with unchecked "Disable Library Validation" and "Disable AMFI" (uncheck the boxes in the OCLP GUI). You should not need to manual inject any amfi-related boot-args in NVRAM.

If that doesn't answer your question, I apologize for not understanding the question.

EDIT: Note that you will need to "Build and Install Open Core" any time you manually change/override the "Security" settings in the OCLP GUI (different from the security discussed in the "OCLP Security" thread). You should be able to experiment with different Library Validation and AMFI settings simply by: 1) check/uncheck the boxes in the OCLP GUI, 2) Build and Install Open Core and 3) reboot. You should never need to manually inject boot-args or manually modify the Open Core config.plist unless that's your preference (I do manually modify config.plist for experiments, so I'm fully supportive of this if you want to and are able to). I'd recommend doing your OC EFI experimentation with a bootable, GUID partitioned USB thumb drive. Keep your SSD EFI untouched so you have a reliable boot drive.
View attachment 2437802

EDIT2: @RK78 Just out of curiosity, are you trying to use OCLP on a Mac where you previously (or currently) installed the DosDude patches?

Replying to your second edit. Yes, Dosdude Catalina 10.15.7, hardly ever used, on another partition on this Mac. Only because I recently installed an SSD to replace the 14 year old HDD on the iMac, I reinstalled the Catalina, along with the High Sierra, and the Ventura, all 3 on different partitions on the SSD (as before on the HDD). Was trying to fix the widely reported issue on the DosDude Cat, where Firefox must always crash on first open in order to open on second try.

dosdude1 said: I have just released version 1.3.6 of Catalina Patcher, which should fix the issue where some third-party applications wouldn't launch. If you have been having this issue, you can either use the latest Catalina Patcher version, or run "sudo nvram boot-args=amfi_get_out_of_my_way=0x1" in Terminal, and then reboot.
[automerge]1585672919[/automerge]

Run "sudo nvram boot-args=amfi_get_out_of_my_way=0x1" in Terminal then reboot. That should take care of that issue.

DosDude, for whom I have the highest regard, had written sometime a few years earlier (quoted above) that running sudo nvram boot-args=amfi_get_out_of_my_way=0x1 fixes this issue. While it did fix the Firefox issue - but only temporarily - not through a restart, I only realized afterwards that this command disables AMFI, not only in the Cat but in the Ventura OCLP, with both seemingly partially linked - and yes I realize that running 3 different OSs on the same Mac can cause some issues, but never before encountered anything like this. Until then had no idea what AMFI was (now I know a bit better) which has led me to the current questions.

Did check/uncheck the AMFI/Disable Library Validation boxes and restarted. Apparently the OCLP default is with AMFI/Library Validation NOT disabled. But still wondering about the presence of that com.apple.security.libraryvalidation.plist showing LibraryValidation disabled.

Wonder if I can just go ahead and manually edit that .plist from true to false to take care of this? If it will really make any difference?

 

[deeveedee]

@RK78 DosDude and OCLP use different mechanisms for Disabling Library Validation. Don't confuse the two. OCLP uses kernel patches in Open Core's config.plist.

You appear to be confusing the two patchers. Resolving this confusion is beyond the scope of this thread (my opinion).

EDIT: @RK78 While I don't think we should be trying to resolve the OCLP/DosDude differences in this thread (again, my opinion), here are a few things that might help:

• OCLP uses kernel patches in the Open Core config.plist to disable library validation. To view these, "Build Open Core" after making sure that "Disable Library Validation" is checked in the OCLP GUI > Security panel. Look at kernel patches in the OCLP-generated Open Core config.plist "Kernel > Patch" block.
• When "Disable AMFI" is checked in the OCLP GUI, OCLP inserts boot-arg amfi=0x80 in the OC config.plist "NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > boot-args". boot-arg amfi=0x80 achieves the same effect as amfi_get_out_of_my_way=0x1 (use one or the other).
• OCLP injects kext AMFIPass.kext, so that amfi=0x80 (or amfi_get_out_of_my_way=0x1) should be unnecessary. With AMFIPass.kext and "Disable AMFI" unchecked in the OCLP GUI, OCLP post-install patches should still install and work. Test this to confirm on your Mac. I don't know whether AMFIPass.kext works with Catalina (to allow installation and operation of DosDude patches). You would need to test this yourself. When OCLP generates an Open Core EFI, you'll see AMFIPass.kext in the OC/kexts folder and in the config.plist "Kernel > Add" block.

 

[RK78]

@RK78 DosDude and OCLP use different mechanisms for Disabling Library Validation. Don't confuse the two. OCLP uses kernel patches in Open Core's config.plist.

You appear to be confusing the two patchers. Resolving this confusion is beyond the scope of this thread (my opinion).

EDIT: @RK78 While I don't think we should be trying to resolve the OCLP/DosDude differences in this thread (again, my opinion), here are a few things that might help:

• OCLP uses kernel patches in the Open Core config.plist to disable library validation. To view these, "Build Open Core" after making sure that "Disable Library Validation" is checked in the OCLP GUI > Security panel. Look at kernel patches in the OCLP-generated Open Core config.plist "Kernel > Patch" block.
• When "Disable AMFI" is checked in the OCLP GUI, OCLP inserts boot-arg amfi=0x80 in the OC config.plist "NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > boot-args". boot-arg amfi=0x80 achieves the same effect as amfi_get_out_of_my_way=0x1 (use one or the other).
• OCLP injects kext AMFIPass.kext, so that amfi=0x80 (or amfi_get_out_of_my_way=0x1) should be unnecessary. With AMFIPass.kext and "Disable AMFI" unchecked in the OCLP GUI, OCLP post-install patches should still install and work. Test this to confirm on your Mac. I don't know whether AMFIPass.kext works with Catalina (to allow installation and operation of DosDude patches). You would need to test this yourself. When OCLP generates an Open Core EFI, you'll see AMFIPass.kext in the OC/kexts folder and in the config.plist "Kernel > Add" bloc

Not sure that I'm confusing the 2, OCLP with dosdude. But not to get sidetracked by that, I'd simply like to have a look at the items you've mentioned in the Open Core config.plist/OCLP-generated Open Core config.plist. Can you tell me just where they are? Have looked at a number of things via Find Any File, and directly inside Library without much success.

Really do appreciate all the help and effort you've put into this.

 

[deeveedee]

@RK78 This is part of the reason that I said you are confusing OCLP and DosDude. OCLP generates an Open Core EFI that is located in the EFI System Partition (ESP) of your GUID-partitioned boot drive. DosDude patcher changes are all within the macOS volume (analogous to the OCLP post-install patches). You will not find the OCLP / Open Core items that you seek in "/Library." These are basic concepts of the Open Core boot-loader that you should learn if you want to (and will need to learn if you plan to experiment with Open Core and DosDude patcher).

The Open Core EFI generated by OCLP can be found / viewed in two ways:

• "Build and Install Open Core" and then "Install to Disk" to the EFI System Partition (ESP) of a GUID formatted drive and then inspect the EFI by mounting the ESP. Search for how-tos to learn how to do this.
• "Build and Install Open Core" and then "View Build Log" to generate the Open Core EFI without installing it to the ESP. View the Open Core EFI in the "/var/folders" path specified in the OCLP dialog.

Once you find the OCLP-Generated Open Core EFI, navigate the directory structure (EFI/OC/...). Use your favorite plist editor (I use Xcode) to examine the config.plist (EFI/OC/config.plist).

This should get you started with the things you need to learn. I don't want to clobber this thread with Open Core basic info, so I'll stop here. Good luck!

 

[RK78]

@RK78 DosDude and OCLP use different mechanisms for Disabling Library Validation. Don't confuse the two. OCLP uses kernel patches in Open Core's config.plist.

You appear to be confusing the two patchers. Resolving this confusion is beyond the scope of this thread (my opinion).

EDIT: @RK78 While I don't think we should be trying to resolve the OCLP/DosDude differences in this thread (again, my opinion), here are a few things that might help:

• OCLP uses kernel patches in the Open Core config.plist to disable library validation. To view these, "Build Open Core" after making sure that "Disable Library Validation" is checked in the OCLP GUI > Security panel. Look at kernel patches in the OCLP-generated Open Core config.plist "Kernel > Patch" block.
• When "Disable AMFI" is checked in the OCLP GUI, OCLP inserts boot-arg amfi=0x80 in the OC config.plist "NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > boot-args". boot-arg amfi=0x80 achieves the same effect as amfi_get_out_of_my_way=0x1 (use one or the other).
• OCLP injects kext AMFIPass.kext, so that amfi=0x80 (or amfi_get_out_of_my_way=0x1) should be unnecessary. With AMFIPass.kext and "Disable AMFI" unchecked in the OCLP GUI, OCLP post-install patches should still install and work. Test this to confirm on your Mac. I don't know whether AMFIPass.kext works with Catalina (to allow installation and operation of DosDude patches). You would need to test this yourself. When OCLP generates an Open Core EFI, you'll see AMFIPass.kext in the OC/kexts folder and in the config.plist "Kernel > Add" block.

Thanks for all that.

Was able to get into the config.plist quite easily by running EFI Agent https://github.com/benbaker76/EFI-Agent, which I've had for some time; quite useful.

OK, so now as you wrote: OCLP injects kext AMFIPass.kext, so that amfi=0x80 (or amfi_get_out_of_my_way=0x1) should be unnecessary, once the config.plist was open, did a search for "AMFI", which returned the AMFIPass.kext.

This was after doing a new build to disk with Disable Library Validation and Disable AMFI quite clearly unchecked.
So since both of those were unchecked for a new build to disk (based on my iMac 10,1) and if that particular kext is loaded in the disable scenario, then why is it still present? Sorry for the confusion, what am I still not understanding?

Maybe screenshots will help:

 

[RK78]

No room to add an edit above. Note, also searched for these 3 in the config.plist which you mentioned - came up completely empty handed.

NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > boot-args

boot-arg amfi=0x80

Kernel > Patch

Realize that you are reluctant to keep this going much longer, and don't want to unnecessarily draw this out; simply want to be certain that Library Validation and AMFI are what they're supposed to be by default.

 

[deeveedee]

@RK78 Not going to discuss this any more. Everything you are asking is searchable. Sorry - I don't want to clobber this thread and I feel like I've spent enough of my time on this.

EDIT: I will clarify one thing: At some point during development of OCLP, Devs decided to always inject AMFIPass.kext. When you check/uncheck "Disable AMFI" in OCLP GUI, you are turning the amfi=0x80 boot-arg on and off.

EDIT2: Starting with OCLP 1.4.3 (maybe earlier) It looks like having "Disable AMFI" checked in OCLP GUI adds boot-arg amfi=0x80 only when "Disable Library Validation" is also checked.

 

[RK78]

OK, from what I can tell from all that things are what they should be. No more thread clobbering.

EDIT: plus I learned something

 

[ArrayDecay]

I'm installing 13.7.1 on an old iMac I use as a media server.

 

[K two]

macOS 13.7.1 installed atop 13.7 OTA, OCLP 2.1.2, runs as expected.
👏

 

[deeveedee]

Smooth upgrade from Ventura 13.7 -> 13.7.1 on my HackBookPro6,2 patched with OCLP 0.6.8.

Note that my hack doesn't need Ventura Wi-Fi patches (only Nvidia Tesla patches), so OCLP 0.6.8 is still perfect for me.