Patcher Macos

2 views

Skip to first unread message

Darios Uclaray

unread,

Aug 4, 2024, 4:38:38 PM8/4/24

to suitelsiti

Hifolks,

What do you all think about this software from github, opencore legacy patcher that can allow a newer Mac OS to be installed on older hardware ??? Is this really legit ? Does anyone know what Apple is saying about this ?

I just installed OpenCore Legacy Patcher and Sonoma on my 2015 iMac and everything seems to have gone smoothly with no glitches yet. Now I'am wondering what will happen with new Apple updates? Will the computer update normally like it has in the past? Or will I have to go through this installation rain dance every time?

To answer my own question, I just went thru the update process for 14.1.2 and it was pretty painless. Soon after the new update started downloading, the Opencore patcher popped up and requested permission to update itself (I think). I gave it permission and the OS update proceeded with one hang near the end. I restarted, let it finish and since then everything has been fine.

To add to that Apple is likely to pull Intel support soon focusing only on M Series based systems. So while the older macOSs still will work if your Apps need something newer or you want what the newer OS offers you may not have much of a choice.

Unfortunately updating is quite difficult with OpenCore. You will have to redo Root Patching, and you may have to disable SIP completely, and keep it disabled. You may even need to rebuild the kext cache many times before it works. But, security updates are the only updates that will give you problems. Other than that, any app updates, minor updates, etc., you won't have too many issues.

I want to install Catalina on a MacBook Pro (13-inch, Early 2011) with 10.13.6 (High Sierra) installed. Therefore I made a bootable USB drive with the macOS Catalina Patcher. First, I had the problem that the USB drive wasn't recognized. Now I used another USB drive and now it will let me boot from. But it always is stuck at the loading screen (nearly 100%). What I'm doing wrong?

Now I deleted the patcher and everything related to it from the machine. Then re-download the tool and also created the bootable USB drive again. I was able to boot from the drive and also install Catalina. But the MacBook again hang at nearly 100%. Then I restarted the machine and the setup dialog appeared! Yes, my MacBookPro8,1 is supported!

I use an old 2014 Intel-based Mac with MacOS Ventura. To make this possible, I use OpenCore Patcher. But BitDefender cannot even complete a system scan on this system. Is OpenCore Patcher the culprit?

I don't think this scenario was ever tested, so I would recommend contacting the Technical Support Teams, as more information might be required for diagnosis. You can get in touch with our engineers by choosing one of the contact channels available here:

I have the same problem, Just renewed my annual subscription and upgraded to the new IOS using the Open Core patcher. every thing runs like a dream "EXEPT Bitdefender" it wont upgrade latest definitions or will not run a scan either system or Quick scan when you click on scan it just locks. Obviously not Bitdefenders problem because im using a 2013 i'mac . just disappointed that Bit Defender wont work and i may have to change to a different anti Virus after using Bit defender for years. I will hang off a few weeks to see if there is a work around before i change.

Well, I haven't come to it yet, but I'm considering doing what Alexandru suggested. As I have no clue what is happening and cannot fix it. However OpenCore obviously opens up some possibly problematic things to make MacOS Ventura work. Would be awesome if BitDefender would secure it a bit.

Apple dropping on-going development for FireWire devices that were supported with the Core Audio driver standard is a catastrophe for a lot of struggling musicians who need to both keep up to date on security updates that come with new OS releases, and continue to utilise their hard earned investments in very expensive and still pristine audio devices that have been reduced to e-waste by Apple's seemingly tone-deaf ignorance in the cries for on-going support.

Probably not the first time you gurus have had someone make the logical leap leading to a request for something like this, but I was wondering if it might be somehow possible of shoe-horning the code used in previous versions of Mac OS that allowed the Mac to speak with the audio features of such devices to run inside the Ventura version of the OS.

AppleFWAudio.kext was removed from Ventura. I took a Mac that still has Monterey, took AppleFWAudio.kext, and modified it slightly so it would install on Ventura. The installation process is the same as installing any third party kernel extension, so you'll have to grant permission in System Settings once prompted.

The google drive link below is a download of the installer package I made. I suggest using the free Suspicious Package application developed by Mothers Ruin Software to inspect this installer package, so you know that it does what I'm telling you it does.

Regarding matt9's hack, well, we all really appreciate it man. Does it work for everybody that tried it? I'm thinking about upgrading to Ventura to try this also, I have a perfectly working RME Fireface 400 interface. But not sure how an eventual downgrade would work or if I would need to actually reinstall everything from scratch..

If you have any familiarity with the 'underground collective who builds Mac clones using regular PC parts' - you may have heard of an app called Kext Wizard. It's used to do just exactly this sort of thing (properly install kexts & then rebuilds permissions).

I am in the same boat...Maybe Apple is more sensitive for security risks. And this decision does introduce a risk caused by an Apple decision.Very often a seemingly more secure, but in reality more complicated technology completely removes security in the real world. People need to get work done, if security measures are in the way, they bypass them.This is a perfect example, it should be reported as a security flaw! Maybe they are willing to listen to that aspect...

Hoping Apple will reply, or even notice, a few requests among the millions received daily, may be a tad optimistic.However, how would we go about creating petition, or some kind of group poll, that they might react too?What would be the best format to accomplish this in?

Unfortunately doesn't work with my Motu Traveler v1 on M2 pro Mac mini. I tried installing with Kext Wizard and pacifist after disabling SIP and it never shows up after multiple restarts and accepting extensions in system settings.

Have been playing around with getting this to work this afternoon. I'm on a Mac Mini M2 PRO + Ventura 13.2. I wasn't able to make the installer work, unfortunately. So I used 'Suspicious Package' to extract the AppleFWAudio.kext file from the installer. I've dabbled for years in the Tonymacx86.com world, so I am somewhat used to doing this sort of thing.

...but nothing shows up in the Sound System Settings option. I have another audio interface now that is my primary interface, but I could sure use the extra input channels with doing a bigger session & need more than 8 channels of input (other interface has 8 mic pre's).

I have managed to get this working on an M2 2023 MacBookPro. I'm using an Apogee Ensemble Firewire and it is now detected and works, mostly. I had to use kmutil myself to get the kernel extension to load. The script in the package didn't work so I just grabbed the files from it using Suspicious Package, disabled SIP, modified my Startup Security Utility settings and then ran kmutil in the terminal.

However, I have been having problems with my system crashing at random intervals when using the ensemble. I'm going to keep tinkering and see if I can figure out a work around. Any assistance folks can provide would be greatly appreciated. I noticed a similar situation for folks here: eyetvforum.com/index.php?/topic/305278-incompatibility-with-macos-13-ventura-beta/My console reports: Library not loaded: /System/Library/Frameworks/FWAUserLib.framework/Versions/A/FWAUserLib

Thanks Apple ??? You now disabled this ability in Ventura 13.4 ??? I have no words.... Now I'm getting error message that this Kext cannot be loaded. Once I'm clicking on "Allow" button, I'm getting to the loop where I need restart computer.

Hey! Need help from you guys. Im got a Mac Mini M2 Pro, with ventura installed, i have a Mackie Onyx 1640i, Firewire audio interface. With the help of this post, i was able to make Ventura recognise the audio interface in the System Report, on the firewire devices, but it doesnt appear on Audio Midi Setup, System Sound or in Ableton Live. I followed all steps from this post, minus the "kmutil" command, it always give me an error. Anyone can help me please? I need this audio interface to work...thanks in advance

Note that macOS patchers cannot perform magic and not all Macs will be compatible. Before installing Ventura on an older Mac, make sure that your Mac is compatible with the patcher. You can find a list of all the Macs supported here.

Once you have installed macOS Sonoma (or whatever version of macOS you choose), updates will appear in Software Updates as soon as they are available. However, you should not install these. Instead you need to create a USB stick with the new installation files and install the update in that way.

The procedure for updating to an incompatible Mac to Big Sur is the same as above. This time you can obtain the installation files from this Mac App Store link. Follow our guide linked to above to make a bootable installer.

The update can take several hours. In our case it sometimes looked like the installer had crashed during the update. In this case you should wait, as the installation is usually still in progress. Over time, better ways to update a machine may be found. Currently, the safest approach is to update using a bootable USB stick.