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.
Legacy Video Patch involve too many kext and frameworks, for Metal GPU to remove "legacy video patch" the simpler way is re-install Catalina, and when you post-install patch don't select "Legacy Video Patch".

I have it but after restore from timemachine its checked and installed automatic...the migration assistant must install the libarary...
 
  • Like
Reactions: TimothyR734
@jackluke can it be installed on your previous usbopencore drive or it has to be installed fresh after formatting the usb stick

Yes, it can, you should use the Near an usb device after selected the previous USB opencore, moreover this will give a dual OpenCoreAPFSloader after power-on alt-option key, I made a different icon (and menu) color the green one is the newest (that includes the Syncretic telemetrap.kext), but also previous version still works.
[automerge]1586594891[/automerge]
I have it but after restore from timemachine its checked and installed automatic...the migration assistant must install the libarary...

You could manually remove the legacy video patch, but you need a stock Catalina copy of these kext and frameworks:
https://github.com/dosdude1/macos-c...a Patcher/macOS Post Install/videocardpatches

In your case of a Metal Nvidia GPU I guess just replacing stock Catalina of these are suffice:
https://github.com/dosdude1/macos-c...macOS Post Install/videocardpatches/gfxshared
 
Last edited:
Have you seen my previous post?
Yes, I will try this if later if I still encounter problems. It is a bit strange because after some restarts I have no crashes at all but then again I have some crashes. I feel that after running Onyx, then reapplying the patches and running the taskgated command I have no problems but I feel something is triggering then the crashes again.

In the meantime I also have uninstalled soundflower drivers because I think they might could have caused a problem.

If anyone can explain to me how I can set sleep function with power supply with help of the Terminal with the command "pmset –g" on a MacBook Pro Mid 2009 I would be happy!
 
  • Like
Reactions: TimothyR734
Legacy Video Patch involve too many kext and frameworks, for Metal GPU to remove "legacy video patch" the simpler way is re-install Catalina, and when you post-install patch don't select "Legacy Video Patch".



Even if meant 10.14.6 , that Macmini4,1 AirDrop patch should work on Mojave too.
Sorry, it really is 10.15.4, my mistake. Btw thank you so much, AirDrop works great! After applying continuity patch i have a trouble with Bluetooth at all. After some digging I found out, that my usb dongle is defective, doesn’t work even in window
Strange. I have the Mac Pro 5,1 (2012) and have Catalina 10.15.4 working well WITHOUT SIP being disabled. The Mac Pro runs well with 10.15.4. I heard it's recommended that SIP be enabled for the Mac Pro 5,1 (2012). I use Dosdude1's 1.4.1 patcher for the installation but no Post Installs from the patcher.
[automerge]1586586595[/automerge]

What??? macOS 10.15.6? Could you please verify. Thanks.
Sorry, it is 10.15.4, my mistake. I almost slept, when I was writing it
[automerge]1586604044[/automerge]
Try this attached install properly replacing the two Wifi kext in your Catalina /System/Library/Extensions/

open Catalina terminal after replaced:
Code:
sudo mount -uw / ; killall Finder
sudo chown -R 0:0 /S*/L*/E*/
sudo chmod -R 755 /S*/L*/E*/
sudo kextcache -i /
sudo reboot

this should work for Macmini4,1 .

If you get a working AirDrop, to enable continuity on your Asus BT400 try this: catalinacontinuityfix.command.zip

But before any continuity feature you need AirDrop on Catalina Finder.
Thank you so much!! AirDrop work like a charm. Now I have to buy new bt4 dongle. After some digging a found out it’s defective, doesn’t work event in windows. In Mac it is endless reconnect, in windows error 10, device cannot start.
 
Last edited:
  • Like
Reactions: TimothyR734
Yes, it can, you should use the Near an usb device after selected the previous USB opencore, moreover this will give a dual OpenCoreAPFSloader after power-on alt-option key, I made a different icon (and menu) color the green one is the newest (that includes the Syncretic telemetrap.kext), but also previous version still works.
[automerge]1586594891[/automerge]


You could manually remove the legacy video patch, but you need a stock Catalina copy of these kext and frameworks:
https://github.com/dosdude1/macos-c...a Patcher/macOS Post Install/videocardpatches

In your case of a Metal Nvidia GPU I guess just replacing stock Catalina of these are suffice:
https://github.com/dosdude1/macos-c...macOS Post Install/videocardpatches/gfxshared

i have try this: https://forums.macrumors.com/thread....1596614/page-162?post=28109056#post-28109056

but dont`t working..
 
  • Like
Reactions: TimothyR734
Download a 10.11 installer, open Basesystem.dmg and in /System/Library/Extensions/ there are the macos recovery kext.
Thanks, Will download 10.11 and get the kex from it do I put it in the patched USB in the exact place that you suggested the other day?
 
  • Like
Reactions: TimothyR734
I recently made a new version of USB OpenCoreAPFSloader2, this is an alternate version to install OpenCoreAPFSloader on an external USB as EFI Boot volume, to store OpenCore configuration directly on the external USB without copying anything on the internal disks.

It can be installed in two ways:

1) Near an USB macOS Installer or USB macOS installation (so you can have a dual booting from apple startup manager)

2) On an empty USB drive (you can use any usb drive in case you need to quickly fix csrutil, amfi, no_compat_check, telemetry plugin and legacy usb kext)


Download here: USBOpenCoreAPFSloader2.app.zip


Moreover this version includes also "telemetrap.kext", developed thanks to @Syncretic (the developer of MouSSE), using telemetrap.kext allows to boot any Penryn Core2Duo while keeping the stock "com.apple.telemetry.plugin" (that since Mojave caused the kernel panic on any Penryn Core2Duo).

@Syncretic made a great work developing a kext upon my request, that eventually can be installed on SLE or /Library/Extensions/ , having it in kextcache prevents (without deleting or replacing) the telemetry plugin loading from xnu kernel.

telemetrap.kext results useful in many situations:

- works both on Mojave and Catalina
- can include it in any custom bootloader
- after any Software Update apple copied again the stock telemetry plugin, don't need more to delete it from single user mode
- can continue an OTA update or an upgrade macOS installer booting directly to the desktop without any kernel panic or bootloop
Thank you jackluke.
I tried to make a new USB stick with USBOpenCoreAPFSloader2, using the 2nd (erase) option. There was an error message in the end (attached) and the USB stick wasn't shown in the alt/opt boot selector, and the stick appeared to be empty.
I looked at the usbopencoreapfsloader2.command and it seemed to me that /Volumes/EFI used in unzip and bless might refer to the EFI of the internal SSD, disk0. Experimentally I replaced it with /Volumes/OpenCoreAPFSloader2 as this name is anyway fixed in main.scpt.
That worked for me, but probably won't for the 1st option (without erasing).
I used the new stick successfully.
 

Attachments

  • Bildschirmfoto 2020-04-11 um 09.36.18.png
    Bildschirmfoto 2020-04-11 um 09.36.18.png
    31.2 KB · Views: 117
  • Bildschirmfoto 2020-04-11 um 09.39.32.png
    Bildschirmfoto 2020-04-11 um 09.39.32.png
    49.7 KB · Views: 115
Last edited:
Thank you jackluke.
I tried to make a new USB stick with USBOpenCoreAPFSloader2, using the 2nd (erase) option. There was an error message in the end (attached) and the USB stick wasn't shown in the alt/opt boot selector, and the stick appeared to be empty.
I looked at the usbopencoreapfsloader2.command and it seemed to me that /Volumes/EFI used in unzip and bless might refer to the EFI of the internal SSD, disk0. Experimentally I replaced it with /Volumes/OpenCoreAPFSloader2 as this name is anyway fixed in main.scpt.
That worked for me, but probably won't for the 1st option (without erasing).
I used the new stick successfully.

This second option warning occurred for two reasons:

1) if you boot your USB external macOS apple assigns to it the main EFI volume disk0s1 (because it's the root disk), while instead an external disk can't be physically on disk0 but disk(0+x), in the script I disallow that any disk0* should be erased even for mistake and also disallow it for the current macOS in use (example APFS container)
2) if you boot after power-on with an USB device plugged to your internal macOS apple assigns the main label EFI, so the next label I could use for an external USB is "EFI 1", for the same reason I disallow to erase for mistake an internal volume so it throws an error


You could use the second option (to use an empty usb drive with erase) in these cases:

- booting your external USB macOS and change the label to your external USB empty drive
- booting your internal macOS but without any plugged usb devices, just plug them after you login the desktop
- erase first your external USB drive as macOS Extended Journaled with GUID scheme (because MBR is not supported for EFI Boot)

But the purpose of this USBOpenCoreAPFSloader2 is that it is stored on the hidden USB external EFI volume diskXs1, and to make this I can't use a different name from EFI, because this is the standard apple name for an EFI Boot either internal or external.

You could use even both the versions together in this way:
- From an empty USB drive make first a: USBOpenCoreAPFSloader (blue icon, version 1)
- Then using USBOpenCoreAPFSloader2 select the same USB drive and choose the "Near to an usb device" option

At the power-on chime holding alt-option you'll notice two OpenCoreAPFSloader, the green icon is the newest with telemetrap.kext that should allow to complete an OTA update without kp or bootloop.

edit: @hvds from your picture your external USB drive hasn't a proper GUID scheme, this is the correct apple GUID scheme (example using my 32 gb usb drive):
Code:
/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *31.1 GB    disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS USBopencore             30.8 GB    disk2s2
 
Last edited:
have you tried running in the terminal sudo killall taskgated that worked for me
[automerge]1586532607[/automerge]

If you used Catalina Patcher 1.4 it should have popped from your patch updater if you download Catalina Patcher 1.4.1 create a new usb with macOS Catalina 10.15.4.02 and reapply the post install patches from the usb

First check this in System Preferences then go to your applications folder/Utilities open patch updater find the LibraryValidation patch rich click on it and reinstall the patch it does take a bit of time to rebuild the kext caches 25 to 30 mins and see if that works

Thank you for your answer, I've tried both solution, reapply post install with no succes, after that created a new usb key with Patcher 1.4.1, re download Catalina 10.15.4.02, boot, then reapply post install patch, reboot, but still have no webcam and no mic in Skype.

Some advices for my problem ?

Thank you!
 
  • Like
Reactions: Tim Thomason
The same... Doesn't work. Do you have the latest Catalina 10.15.04? On 10.15.01, with dosdude1 patcher it worked.
I am on 10.15.4.02 which Mac are you using
[automerge]1586617759[/automerge]
Thank you for your answer, I've tried both solution, reapply post install with no succes, after that created a new usb key with Patcher 1.4.1, re download Catalina 10.15.4.02, boot, then reapply post install patch, reboot, but still have no webcam and no mic in Skype.

Some advices for my problem ?

Thank you!
have you tried this
 

Attachments

  • tccplus wrapper hotfix.zip
    59.9 KB · Views: 118
Last edited:
I am on 10.15.4.02 which Mac are you using
I'm using an iMac 27inch mid 2011.
I allready call Vodafone for help: it is a unreported bug. It doesn't work on a MacBook pro 13inch mid 2019 either...
When Apple updates last time the Catalina, some apps downloaded from elsewhere than the APP store have the same problem regarding permissions...
EDIT: i use the USB install pen, select post install paches, maintain the recommended patches and tccplus works again.
 
Yes, I will try this if later if I still encounter problems. It is a bit strange because after some restarts I have no crashes at all but then again I have some crashes. I feel that after running Onyx, then reapplying the patches and running the taskgated command I have no problems but I feel something is triggering then the crashes again.

In the meantime I also have uninstalled soundflower drivers because I think they might could have caused a problem.

If anyone can explain to me how I can set sleep function with power supply with help of the Terminal with the command "pmset –g" on a MacBook Pro Mid 2009 I would be happy!
[automerge]1586618090[/automerge]
I'm using an iMac 27inch mid 2011.
I allready call Vodafone for help: it is a unreported bug. It doesn't work on a MacBook pro 13inch mid 2019 either...
When Apple updates last time the Catalina, some apps downloaded from elsewhere than the APP store have the same problem regarding permissions...
Do they have a previous version of Vodaphone that you can download it might work as with the newest version of zoom we can use it on our unsupported Macs due to metal gpu being required
 
[automerge]1586618090[/automerge]

Do they have a previous version of Vodaphone that you can download it might work as with the newest version of zoom we can use it on our unsupported Macs due to metal gpu being required
I edited my post, installed the recommended patches for my iMac again, tccplus works again...
They don't have previous versions. The software is made by wit, not by Vodafone.
OBS and TeamViewer will have problems too, also solved using tccplus.
 
That tool seems correct to remove the "Legacy Video Patch" only thing I guess it doesn't re-replace two very important macOS frameworks: SkyLight.framework and CoreDisplay.framework to use a Metal GPU these must be stock from Catalina.

edit: and also the IOSurface.kext needs stock from Catalina.

I have all you say replace ... with this all


And then chmod 755 , chown 0:0 ...replace with kext utility.. nothing helped... Patcher say legancy is installed ... Have @dosdude1 any idea?

I have installed stock catalina without legancy patch to the external hdd... Copy all things to usb and replace on my computer...
 
  • Like
Reactions: TimothyR734
This second option warning occurred for two reasons:

1) if you boot your USB external macOS apple assigns to it the main EFI volume disk0s1 (because it's the root disk), while instead an external disk can't be physically on disk0 but disk(0+x), in the script I disallow that any disk0* should be erased even for mistake and also disallow it for the current macOS in use (example APFS container)
2) if you boot after power-on with an USB device plugged to your internal macOS apple assigns the main label EFI, so the next label I could use for an external USB is "EFI 1", for the same reason I disallow to erase for mistake an internal volume so it throws an error


You could use the second option (to use an empty usb drive with erase) in these cases:

- booting your external USB macOS and change the label to your external USB empty drive
- booting your internal macOS but without any plugged usb devices, just plug them after you login the desktop
- erase first your external USB drive as macOS Extended Journaled with GUID scheme (because MBR is not supported for EFI Boot)

But the purpose of this USBOpenCoreAPFSloader2 is that it is stored on the hidden USB external EFI volume diskXs1, and to make this I can't use a different name from EFI, because this is the standard apple name for an EFI Boot either internal or external.

You could use even both the versions together in this way:
- From an empty USB drive make first a: USBOpenCoreAPFSloader (blue icon, version 1)
- Then using USBOpenCoreAPFSloader2 select the same USB drive and choose the "Near to an usb device" option

At the power-on chime holding alt-option you'll notice two OpenCoreAPFSloader, the green icon is the newest with telemetrap.kext that should allow to complete an OTA update without kp or bootloop.

edit: @hvds from your picture your external USB drive hasn't a proper GUID scheme, this is the correct apple GUID scheme (example using my 32 gb usb drive):
Code:
/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *31.1 GB    disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS USBopencore             30.8 GB    disk2s2
Thanks jackluke.
I'm very happy with the USBOpenCoreAPFSloader.app (version 1), and I'm looking forward to installing the next beta OTA.

So I remade the USB stick, by re-formating it to JHFS+ with GUID partitioning, and then running version 1. The result shows in the alt/opt boot selector, and boots fine.

For further testing only and for information, I booted again to my internal SSD without devices on USB.
- inserted the USB stick, renamed it to xxx
- applied USBOpenCoreAPFSloader2.app. Inserted into main.scpt after the set USBselect..., the line
display dialog "Selected, USBselect: " & Selected & ", " & USBselect to verify that infact disk2 was selected
- still the message, disk0s1 was already unmounted, came up at the end, and there was no additional booter made.
I've also checked what is in the EFI on disk0s1, and it looks ok to me.
As I said I am happy with version 1, but I can do more testing or mdifications to my system if that be useful.
 

Attachments

  • Bildschirmfoto 2020-04-11 um 20.30.34.png
    Bildschirmfoto 2020-04-11 um 20.30.34.png
    22.3 KB · Views: 112
  • Bildschirmfoto 2020-04-11 um 18.38.13.png
    Bildschirmfoto 2020-04-11 um 18.38.13.png
    31.2 KB · Views: 104
  • Bildschirmfoto 2020-04-11 um 18.38.20.png
    Bildschirmfoto 2020-04-11 um 18.38.20.png
    34.5 KB · Views: 107
  • Bildschirmfoto 2020-04-11 um 18.42.10.png
    Bildschirmfoto 2020-04-11 um 18.42.10.png
    68.9 KB · Views: 110
  • Like
Reactions: TimothyR734
Thanks jackluke.
I'm very happy with the USBOpenCoreAPFSloader.app (version 1), and I'm looking forward to to installing the next beta OTA.

So I remade the USB stick, by re-formating it to JHFS+ with GUID partitioning, and then running version 1. The result shows in the alt/opt boot selector, and boots fine.

For further testing only and for information, I booted again to my internal SSD without devices on USB.
- inserted the USB stick, renamed to xxx
- applied USBOpenCoreAPFSloader2.app. Inserted into main.scpt after the set USBselect... the line
display dialog "Selected, USBselect: " & Selected & ", " & USBselect to verify that infact disk2 was selected
- still the message, disk0s1 was already unmounted, came up at the end, and there was no additional booter made.
I've also checked what is in the EFI on disk0s1, and it looks ok to me.
As I said I am happy with version 1, but I can do more testing or mdifications to my system if that be useful.

If you edit my main script it won't work for sure, if you want to use it properly delete any previous USBOpenCoreAPFS app from Downloads folder, then re-download from my previous link.

From the picture seems your USB device disk2 is not right for the EFI Boot, I mean it doesn't support multipartition, because on your disk2 GUID scheme you only have one partition, instead as per apple GUID standards you should have two partitions, to have two partitions try erase from DiskUtility your USB drive and select the GUID scheme and JHFS+ .

The USB device that you intend to use for USBOpenCoreAPFSloader2 needs to show two partitions as this example:
Code:
/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *31.1 GB    disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS USBopencore             30.8 GB    disk2s2
 
Thanks, Will download 10.11 and get the kex from it do I put it in the patched USB in the exact place that you suggested the other day?
I have found a copy of 10.11 and when I open the file, there is install os 10 El Capitan.app and when I open that there are contents folder and in there they have the following folders please see the following image
 

Attachments

  • image.jpg
    image.jpg
    478.4 KB · Views: 113
  • Like
Reactions: TimothyR734
I have found a copy of 10.11 and when I open the file, there is install os 10 El Capitan.app and when I open that there are contents folder and in there they have the following folders please see the following image

Open SharedSupport folder, but I already made some attempts and can't get the Audio working on Catalina macOS recovery or installer. You should ask to dosdude1 if can include the CMD+F5 audio on his USB Catalina Patcher, because he knows how build a general prelinkedkernel for unsupported machines.
 
  • Like
Reactions: Meelas
Open SharedSupport folder, but I already made some attempts and can't get the Audio working on Catalina macOS recovery or installer. You should ask to dosdude1 if can include the CMD+F5 audio on his USB Catalina Patcher, because he knows how build a general prelinkedkernel for unsupported machines.
Thanks jackluke for helping me with this, I will ask dosdude1 if he can add that support.
Thanks again for your help
 
After an update to 10.15.4 on my MacPro5,1 iMessage won't sign in anymore, getting "An error occurred during activation. Try again."

Any idea what that might be?


UPDATE: cmd-opt-p-r NVRAM reset resolved that. All working right now it seems.
 
Last edited:
If you edit my main script it won't work for sure, if you want to use it properly delete any previous USBOpenCoreAPFS app from Downloads folder, then re-download from my previous link.

From the picture seems your USB device disk2 is not right for the EFI Boot, I mean it doesn't support multipartition, because on your disk2 GUID scheme you only have one partition, instead as per apple GUID standards you should have two partitions, to have two partitions try erase from DiskUtility your USB drive and select the GUID scheme and JHFS+ .

The USB device that you intend to use for USBOpenCoreAPFSloader2 needs to show two partitions as this example:
Code:
/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *31.1 GB    disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS USBopencore             30.8 GB    disk2s2
Using another USB memory stick now. USBOpenCoreAPFSloader2.app runs fine with this.

diskutil list shows the two partitions. Sorry for the trivial problem... and thanks again.

(The memory stick used previously was 1GB. Disk Utility, when erasing, generates only one sub partition for it, maybe due to size, and two subpartitions for the memory stick now used which is 8GB)
 

Attachments

  • Bildschirmfoto 2020-04-11 um 21.35.36.png
    Bildschirmfoto 2020-04-11 um 21.35.36.png
    42.6 KB · Views: 96
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.