Macos 12 Patcher

0 views

Skip to first unread message

Valda Atkeson

unread,

Aug 4, 2024, 11:17:42 PM8/4/24

to cabasebow

Iwant 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!

Hi folks,

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.

Based on a conversation in MacRumors, I stumbled upon another possible solution to failed OCLP patches. As I noted previously, I had a Monterey 12.6.5 volume patched with OCLP 0.6.3. I was not able to directly update the OCLP patches with version 0.6.5. Each patch attempt resulted in an error when attempting to rebuild kernel cache. However, when I first used the OCLP option "Revert Root Patches" and then rebooted Monterey, I was then able to apply OCLP 0.6.5 root patches.

In the MacRumor's "Ventura on Unsupported Macs" thread, there's a comment suggesting that RSR may never work on pre-Haswell Macs. If 13.3.1 is the last macOS that will run on my HackBookPro6,2, it was all worth it. What an amazing journey and a fun ride.

In the MacRumors "Ventura on Unsupported Macs" thread, there's a comment suggesting that RSR may never work on pre-Haswell Macs. If 13.3.1 is the last macOS that will run on my HackBookPro6,2, it was all worth it. What an amazing journey and a fun ride.

Further clarification in MacRumors thread: pre-Haswell Macs can't apply RSRs (Rapid Security Responses), but that doesn't mean they are "stuck" on 13.3.1. When the security update implemented in the RSR becomes available in the next incremental release, pre-Haswell Macs can apply the update. For example, pre-Haswell Macs will be unable to install RSR 13.3.1a, but they will be able to install 13.4 (and thus benefit from the security update that was included in 13.3.1a).

For whatever reason, the act of applying the RSR requires one or more AVX2.0 opCodes that are not available in pre-Haswell CPUs. This may eventually be resolved using something similar to OpCodeEmulator, but for now, pre-Haswell Macs cannot apply RSRs and simply need to wait for the next incremental release.

@miliuco Unknown by me, too. I felt like an idiot in the MacRumors forum trying to get an explanation. I think that normally, I pick things up fairly quickly. In this case, I had a mental block and was slow on the uptake, but I did understand eventually.

Sharing this to potentially help others who are using OCLP to patch their legacy hacks. I have found that my old HackBookPro6,2 does not boot macOS when FeatureUnlock.kext is enabled. See details here.

Surprised by the new update system, detecting an older OCLP version and offering updating it, even building a new OpenCore EFI, installing it into the macOS disk and applying root patches, impressive.

@miliuco The OCLP developers are world-class software wizards. Their productivity and ability to overcome obstacles is incredible. We are very fortunate to have developers like this in our real Mac and hackintosh communities. Looking at the conversations over at MacRumors, it's fun to see the real Mac and Hackintosh communities working together toward a common goal.

Very excited about the rapid progress being made by the OCLP developers. My HackBookPro6,2 is now booting/running Ventura 13.4 with AMFI and Library Validation both fully ENABLED as described here.

I think this is a big deal. I am able to transition macOS from AMFI-disabled to AMFI-enabled just by updating my EFI and patching with OCLP-067Beta2. OCLP developers have made it clear that they do not support hackintoshes and they do not support patching over previous patches when Settings > Host Model is changed to a specified SMBIOS model. Regardless of the support level or intended operation, it appears to work perfectly.

OpenCore from OCLP not support Hackintosh anyway, your not need to install OC from the patcher to making hack working on unsupported macOS's your only need your EFI adapted for the macOS version and the necessary kexts

So @deeveedee try to use your original config.plist adapted for Ventura of course with a recent OpenCore version then use only RootPatch from the patcher, its suppose to work. I have 3 differant Hackintosh (PC, Laptop) working like that.

I attempted an "in-place" update of Big Sur 11.7.7 (previously installed with AMFI and Library Validation both disabled) to OCLP 0.6.7Beta2. Unfortunately, I was unable to boot Big Sur with AMFI and Library Validation enabled (boot resulted in an AppleAHCIDiskDriver kernel panic). However, I was able to boot the Big Sur 11.7.7 installer with the new EFI (AMFI and Library Validation both ENABLED) and after the successful installation of Big Sur, I was able to apply OCLP 0.6.7Beta2 post-install patches. Now I am booting Big Sur, Monterey and Ventura with the same OC 0.9.2 EFI (AMFI and Library Validation both enabled) and all patched with the same OCLP 0.6.7Beta2 patches.

I am sure that there are better ways to hack my legacy rig and I am always learning. I continue to be reminded that perfect is the enemy of good enough. I continue to be amazed that I'm running the latest macOS version on a 2010 Dell Latitude E6410 and it works very well (not perfect, but definitely good enough for my purposes).

EDIT: DhinaK set me straight on Discord. She suggested installing OCLP0.6.7 Beta2 post-install patches to Big Sur BEFORE enabling AMFI/LV. That worked!

Lesson learned: If you have previously applied post-install patches with OCLP 0.6.6 to a volume with AMFI/LV disabled, install post-install patches with OCLP 0.6.7Beta2 (or newer) BEFORE enabling AMFI/LV.

There was misinformation being spread on MacRumors where some were claiming that Macs did not require AMFI disabled prior to macOS 13.3. As we all know here, this is not true. I received this confirmation on the Open Core Legacy Patcher Discord. Just posting here for clarification:

EDIT: @Allan if it's any consolation, I've experienced the same error when attempting to install Ventura 13.2.1 using an installer that I created with GibMacOS. I didn't spend any time debugging. I just created the installer with OCLP and it worked.

AMFIbeta2 work on Hackintosh

HP Probook 650 G1

I use the Binary kext AMFIPass.kext with my EFI, no OC install from the patcher, only RootPatch from AMFIbeta2

Good news I will Integrate this Future on HP-Probook-EliteBook-Package-Creator-OC

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.