Monterey patcher
Author: J | 2025-04-24
Monterey Patcher 0.7 will be delayed due to additional testing with macOS Monterey 12.0.1 Beta. Monterey Patcher 0.7 will be releasing soon it is being tested on mcaos Monterey beta 6 - 10. Monterey Patcher now supports Monterey Patcher 0.7 will be delayed due to additional testing with macOS Monterey 12.0.1 Beta. Monterey Patcher 0.7 will be releasing soon it is being tested on mcaos Monterey
GitHub - fjteam/macOS-Monterey-Patcher: macOS Monterey Patcher
Need to do the OpenCore Legacy Patcher root kernel patches for graphics & wifi? #17 I successful booted into Monterey!I’m not sure what I did that made that happen. It’s one of two things. 1. I installed Catalina with Dos Dudes patcher. Then downloaded opencore and did the Monterey install. 2. At some point during the process in 1, I installed just the OpenCore EFI stuff on a USB and then was able to boot into 12.5 from there. My new issues- 1. I wiped the drive completely before I installed Catalina with the Dos Dude Patcher. I know that I could make a partition later for Snow Leopard. I figured installing High Sierra after installing Catalina shouldn’t be a problem. I did it previously without issue. I planned on deleting the volume with Catalina after I installed 10.13. 2. After installing 10.13 (HS), I got an Incompatible disk warning. I understand why I have that warning. It likely a result of Monterey already being installed on the disk (remember, I didn’t have this issue when I installed HS after installing Catalina previously). 3. Can I ignore the message? Will some kind of corruption occur? Or does the message basically mean I can’t take advantage of the never version of APFS that installed with Monterey? I can wipe the drive and start again by installing the OS in order, but I’m afraid I’m going to have trouble getting Monterey to install and boot again. It took me days to get it booting. #18 Howard Oakley gives a thumbnail history of APFS in this blog article. Since HS, features have been added to support the splitting of the system volume into read-only and read-write parts and presenting those two parts as a single root filesystem in Finder. You're seeing the Incompatible Disk message because HS has mounted a volume which was created by a newer version of APFS.I see the same message, as I mentioned previously, and I haven't seen any corruption or other problems, but I've been careful to avoid accessing the Monterey volumes from HS. Trying to avoid mounting the Monterey volumes in HS by putting 'noauto' entries in /etc/fstab didn't work for me, so I just hid them from the desktop: Code: sudo SetFile -a V /Volumes/Monterey\ HD\ -\ Datasudo SetFile -a V /Volumes/Updatekillall Finder The Update volume appeared after I installed all of the available HS updates. SetFile is part of the Xcode command line developer tools.My disk layout looks like this: Code: grumpus$ diskutil list/dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_APFS Container disk1 499.9 GB disk0s2/dev/disk1 (synthesized): #: TYPE NAME SIZE IDENTIFIER
GitHub - Skywalkerx1/macos-monterey-patcher: macOS Monterey Patcher
Installed. #10 I don't know what happened, sorry. In my experience, several reboots happen during an OCLP Monterey install, and each reboot took place with no intervention on my part. Maybe you've seen it already, but Mr. Macintosh has an excellent video walking you through the entire process.Were I in your shoes, I'd start over. First, I would reset the NVRAM and reset the SMC of the laptop, just to be starting from a clean slate. Then start the OCLP Monterey install again, but this time erase the entire drive. The reboot(s) during the installation shouldn't require any manual intervention. After the Monterey install is complete, OCLP should prompt you regarding booting from disk rather than the installer USB, so just follow the prompt. Also, Mr. Macintosh shows how to set the default boot device in the video.Once Monterey is up and running, use disk utility to partition the drive to make room for Snow Leopard and whatever else you have planned. Leave enough room for Monterey + High Sierra. Use disk utility to create a new volume inside the Monterey container for High Sierra. Now do your High Sierra install.When Monterey and High Sierra are working, you can turn your attention to Snow Leopard.EDIT: Maybe it is better to install Snow Leopard first, just to insure that it doesn't mess with whatever OCLP does to the EFI. Me, when it comes to more than a couple of OSes on the same disk, I'm a fan of VirtualBox Last edited: Aug 23, 2022 #11 No worries, I appreciate all the help.I did watch Mr. Macintosh's video several times. I figured something was wrong when it wouldn’t reboot on its own like in the video.At this point I have nothing to lose and could just reformat the entire drive to run SL.Before I embarked on this project, I was running Catalina with Dod Dude’s patcher and HS on a separate volume. I also had Windows 10 on there. Maybe I should start with Catalina? My guess is I will still have the same issue, but who knows #12 I still think it's worth resetting NVRAM and SMC, that has cleared up mysterious boot failures for me several times in the past, and it can't hurt (to the best of my meager knowledge). #13 Just to put it out there, I've got a 2010 MacBook (White, not Pro, but same CPU and GPU) and it's running OpenCore with both Snow Leopard and Big Sur underneath it.I used USB to install Big Sur through OpenCore Legacy Patcher, did all of the updates (11.6.5 at the time, now 11.6.8), partitioned the SSD outside of the APFS container and made a GPT HFS+ (Mac OSGitHub - fjteam/macOS-Monterey-Patcher: macOS Monterey Patcher is now
記事ではOpenCore Legacy Patcher (OCLP)を使用して、Appleからのサポートを失った古いMacに最新のmacOS をインストールする方法について紹介します。Appleは毎年秋に新しいmacOSを公開しますが、その度に多くのMacユーザが最新のmacOSにアップデートできない状況に直面します。このガイドでは、OpenCore Legacy Patcherを用いて、出来るだけ安全に公式サポート対象外のMacに最新のmacOSをインストールする方法について詳しく解説します。なお、この記事ではOCLPを使ってmacOS SonomaとmacOS Ventura、macOS Monterey、macOS Big Surに対応しています。▼ macOS Sonomaに特化した記事をご用意いたしました。目次はじめに諸注意サポートOpenCore Legacy Patcherとは?主な特徴この記事でインストール可能なmacOSの一覧OpenCore Legacy Patcherのインストール要件用意するもの及び注意点インストールメディアを作成するブート可能なmacOSのインストーラを作成するOpenCore Legacy PatcherをUSBメモリにインストールするはじめに諸注意 この度は弊ブログ(あのかぼ)にアクセス頂きまして誠にありがとうございます。この記事ではAppleからサポートを打ち切られたMacに対し、最新のmacOSをインストールすることを目的とした非公式のマニュアルです。そのためAppleのサポートは受けられません。また、この記事または弊ブログで紹介している全ての記事をもとに生じたあらゆる損害について弊ブログ及び筆者は何ら責任を負わない旨ご承知おきいただきますようお願いいたします。サポート作業中やご利用中にトラブルが生じてしまった場合には「Plats.app」内にある国内の非公式OpenCore Legacy Patcherコミュニティをご利用ください。このコミュニティではインストールについての問題解決の他、インストール成功例やTipsなどの幅広い内容を網羅します。のんびりと書き込める空間なので、ぜひOpenCore Legacy Patcherをご利用の方はご参加ください!また、OpenCore Legacy Patcher関連のニュースは弊ブログの他、「おんかぼ!」でも扱っております。これらの更新内容はPlats.appの他、筆者Twitterでも告知いたしますので、併せてチェックいただければ幸いです。是非一緒に楽しみながら頑張りましょう!一番読み飛ばされそうな部分ですが、お読みいただきありがとうございました。インストールが無事に完了することを心より祈念申し上げます。ファイトです!OpenCore Legacy Patcherとは?OpenCore Legacy Patcherは、Appleによってサポート対象外とされた古いMacに最新のmacOS VenturaやmacOS Monterey、mac OS Big Sirをインストールするためのツールです。このOpenCore Legacy Patcherを利用することで、最新のmacOSの機能やセキュリティを、古いMacでも体験することができます。さらに、OpenCore Legacy Patcherは安全性に配慮した非常にモダンな設計をしており、ユーザは安心して使用することができます。OpenCore Legacy Patcherの主な特徴ここでOpenCore Legacy Patcherの特徴や安全性などについて紹介します。ネイティブな体験ディスク上ではなく、メモリ上でのデータ注入とパッチが行われます。そのため、正式にサポートされているMacと同様の経験が得られます。セキュリティを最優先にセキュリティ機能の中でも、System Integrity Protection(SIP)、FileVault 2、.im4m Secure Boot、Vaultingなどがサポートされています。これにより、OpenCore Legacy Patcherを使用するユーザは安心して最新のmacOSを利用することができます。※ ただし、インストールするOSによってはSIPを有効にできなかったり、一部制約があるなど、条件によってはすべてを有効にできない場合があります。OTAアップデートにネイティブ対応サポート対象のMac同様に、システム設定(システム環境設定)から直接、新しいアップデートを簡単にインストールすることが可能。アップデートの手間や時間を大幅に削減できます。※ Appleより配信されるアップデートのうち、macOS Ventura以降で配信される緊急対応(RSR)に関してはハードウェアの構成や環境により特定のインストールできない場合があります。詳しくは「OpenCore Legacy Patcherを使用してmacOS VenturaをインストールしたMacでの「macOS Security Response」をインストールする注意点」をご覧ください。さまざまなハードウェアへの対応強化OpenCore Legacy Patcherの利点は、単にOSのサポートを拡張するだけでなく、古いグラフィックカードやWi-Fi、BluetoothチップセットなどのAppleからサポートを打ち切られたハードウェアをも対応させ、Macを快適に利用できるようになる点にあります。最新のmacOS機能をあなたのMacでもSidecar、AirPlay to Mac、Night Shift、Universal Controlといった、最新のmacOSでのみ利用できる機能も、このPatcherを使用することで体験することが可能になります。※ 各機能のハードウェア要件を満たしている場合には通常自動的にmacOSに含まれる新機能を利用できますが、一部のモデルでは手動で有効にする必要があります。詳しくは「非対応MacでもUniversal Controlを有効にする方法: OpenCoreとSMBIOSスプーフィングの利用法」をご覧ください。有用なコミュニティのサポートOpenCore Legacy Patcherのコミュニティは活発で、問題や新しい機能に関する質問に答えてくれるユーザーや開発者が数多く存在します。日本国内では筆者(かぼしー)が2023年8月に新しく立ち上げたPCやIT専門のコミュニティサイト、「Plats.app」にはOpenCore Legacy Patcherの専門コミュニティスペースがあり、質問や動作報告が行えます。(Plats.appは「ユーザと造るSKS」を標榜しているコミュニティサイトです。一部未完成の機能を含みます。)※ SKSはSocial Knowledge Serviceの略です。この記事を参考にインストールがインストール可能なmacOS のバージョン一覧は以下の通りです。macOS 11 Big SurmacOS 12 MontererymacOS 13 VenturamacOS 14 Sonomaこの記事を基に2020年にリリースされたmacOS Big Sur以降から執筆時点で最新のmacOS Sonomaまでをインストールすることが可能です。macOS 14 Sonoma をインストールしたい方は、この記事でも作業が可能な他、macOS Sonoma専用に作成した記事、「macOS SonomaをインストールできないMacにOpenCore Legacy Patcherを使用してインストールする」でも作業が可能です。macOS Sonoma専用に作成した記事では、macOS 14 Sonomaに特化した注意点を盛り込み、より詳しく解説しています。なお、macOS Catalinaが非対応のモデルにmacOS Catalinaをインストールしたい方は、OpenCore Legacy Patcherではなく、dosdude1氏が開発するmacOS Catalina Patcherをご利用ください。OpenCore Legacy Patcherのインストール要件OpenCore Legacy PatcherがサポートするMacは以下の通りです。MacBook (Early 2008以降)MacBook Air (Late 2008以降)MacBook Pro (Early 2008以降)Mac mini (Early 2009以降)iMac (Mid 2007以降)Mac Pro (Early 2008以降)Xserve (Early 2008以降)ただしiMac (Mid 2007)についてはSSE4.1をサポートしているCPU、つまりCore 2 Duo T9300やCore 2 Duo T9500などのIntel Penrynファミリーに換装することでOpenCore Legacy Patcherを使用することが可能です。持ってるMac、OpenCore Legacy Patcherに対応していなかった…という方に朗報です。もしかしたらWindows 10やWindows 11ならインストールできるかもしれません!動画版のご案内 ▲ この記事をベースにOCLPを使って最新のmacOSをインストールする方法を紹介する動画を作成いたしました。実際の作業の流れを動画として確認できるので、初めの取っ掛かりとしてもオススメです!用意するものOpenCore Legacy Patcherを使用する上で用意するべきものをまとめました。16GB以上のUSBメモリ(またはSDカード)インターネット環境インストーラを作成するMac必要となるものは非常にシンプルです。USBメモリは16GB以上の空き容量を持つものを使用してください。もし、USBメモリを新しく用意される方は16GBのUSBメモリより、32GBのUSBメモリの方がコストパフォーマンスに優れているためお勧めです。なお、ここで作成したUSBメモリ(インストールメディア)はトラブルが発生した際に利用しますので、フォーマットや初期化をせず保管しておきましょう。macOSをアップグレードして最新OSにする方法ではUSBメモリやSDカードを用意せずとも作業が可能ですが、トラブルが発生した際、修復するためにこの記事で作成したUSBメモリ(インストールメディア)が必要になる場合がありますので、必ずUSBメモリやSDカードは用意しておくことをおすすめします。インストールしたいOSがmacOS 13 Ventura以降の場合の注意点②OpenCore Legacy Patcherを使用してmacOS Venturaをインストールしたい方のうち、GPUにAMD GCN 1~3世代の製品が使われているMacではルートパッチインストール時にKernel Debug Kit (通称KDK)が必要になります。この作業にはインターネット接続が必要です。もしも、対象のMacにmacOS Venturaがインストールされた際、インターネット接続ができない場合には別のPCやMacを使用してKDKをダウンロードする必要があります。方法や詳細は「AMD GCN 1~3世代を搭載したMacでOpenCore Legacy Patcherのルートパッチがインストールできない時の対処法」をご覧ください。なお、この問題はmacOS Monterey以前の場合には発生しません。インストールを行うMacがAVXを利用できない(2011年モデル以前の)Macの場合お使いのMacがSandy Bridge以前のCPUを搭載したMacなど、AVXが利用できないMacの場合にはApple日本語入力プログラム (旧ことえり)が正しく動作しません。その為日本語入力を行う場合には別途「Google 日本語入力」をご利用ください。詳しくは「macOS Catalina Patcherで日本語入力をする」をご覧ください。いよいよ次のページからインストールメディアの作成を開始します。. Monterey Patcher 0.7 will be delayed due to additional testing with macOS Monterey 12.0.1 Beta. Monterey Patcher 0.7 will be releasing soon it is being tested on mcaos Monterey beta 6 - 10. Monterey Patcher now supports Monterey Patcher 0.7 will be delayed due to additional testing with macOS Monterey 12.0.1 Beta. Monterey Patcher 0.7 will be releasing soon it is being tested on mcaos MontereyGitHub - fjteam/macOS-Monterey-Patcher: macOS Monterey
Machine ModeliMac14,1Application VersionLatest Build (nightly)Application VariantTUI (Text User Interface)What versions of macOS are you seeing the problem on?macOS 12, MontereyWhere does this issue happen?Between booting macOS and Login ScreenWhat is the Isssue?Hi! I was running Big Sur with patched sur without any problems.Yesterday I installed Monterey using OpenCore Legacy and the installation was successful .... except my external HDMI monitor is not working. I use a thunderbolt 2 to HDMI cable. It works using other patchers, like Monterey mini patcher but this one fails to complete the installation.Using any other method or OS I can see image in my external display even on boot or the installation process.This is iMac 14.1 with Iris Pro iGPUAny help?Sorry for my english and thanks for your timeAny Additional InformationResumen del hardware:Nombre del modelo: iMacIdentificador del modelo: iMac14,1Nombre del procesador: Quad-Core Intel Core i5Velocidad del procesador: 2,7 GHzCantidad de procesadores: 1Cantidad total de núcleos: 4Caché de nivel 2 (por núcleo): 256 KBCaché de nivel 3: 4 MBMemoria: 16 GBVersión de la ROM de arranque: 146.0.0.0.0Versión SMC (sistema): 2.14f24sashka3076/macOS-Monterey-Patcher - GitHub
#1 Update 23 April 2022 Support in Github only!--------------------------------------------------------------------------------------------How to install macOS Monterey on a MacBook Pro retina late 2013Without patcher, without any kexts files. Genuine macOS booting with OpenCore SIP activateProbably work on other Mac?Guide ➤ Install macOS Monterey 12 MacBook Pro retina late 2013For support open Issue: [New Issue]If you are using OCLP, please post your comments on the subject to dedicate this effect, do not post here.If you have a mac with are you using dual Graphics or any GPU other than the Intel Iris Pro Graphics I recommand to using OCLP and post your comments on the subject to dedicate this effect. Last edited: Apr 23, 2022 #4 this is great but can you do it without encore nd keep it all native? my 2015 MacBook 12 has all the drivers still available in Monterey its just an arbitrary cut off?Thanks #5 To achieve this would have to change a few things in the system.Currently with only OC as bootloader without any kexts inject it is original untouch #6 One of cool things with OC is bootning Windows directly from the boot menue Windows 11 is installed on a Thunderbolt Drive , independant of my Monterey drive Windows 11 is really fast and cool #7 To achieve this would have to change a few things in the system.Currently with only OC as bootloader without any kexts inject it is original untouch any idea how I would do this? as I say every device is still natively supported. #9 Hi @chris1111,Your solution worked for me. What I did:1- Generated an EFI folder using OCLP 0.2.4;2- Removed all Kext files from Kexts;3- Added HfsPlus.efi on Drivers (OpenCanopy.efi, OpenRuntime.efi, and HfsPlus.efi);4- Added CleanNvram.efi in Tools (BootKicker.efi, OpenShell.efi, and CleanNvram.efi);5- Removed ALL PCI in including the key for brcmfx-country fromBen216k/Mini-Monterey-Patcher - GitHub
Extended Journaled) partition, from there I installed Snow Leopard from USB. Works great now. View media item"> View media item"> #14 I used USB to install Big Sur through OpenCore Legacy Patcher, did all of the updates (11.6.5 at the time, now 11.6.8), partitioned the SSD outside of the APFS container and made a GPT HFS+ (Mac OS Extended Journaled) partition, from there I installed Snow Leopard from USB. Works great now. Cool, thanks, good to know! #15 Just to put it out there, I've got a 2010 MacBook (White, not Pro, but same CPU and GPU) and it's running OpenCore with both Snow Leopard and Big Sur underneath it.I used USB to install Big Sur through OpenCore Legacy Patcher, did all of the updates (11.6.5 at the time, now 11.6.8), partitioned the SSD outside of the APFS container and made a GPT HFS+ (Mac OS Extended Journaled) partition, from there I installed Snow Leopard from USB. Works great now.View attachment 2046418View attachment 2046419That was going to be my next try! I am going to wipe the drive and just install Monterey and SL after #16 Didn't read posts carefully, sorry if in error. My experiences on old Macs with patchers: 1st: make sure firmware on old Mac is latest available. Often that involves upgrading to the last supported version of MacOS, since later MacOS software only had the firmware updates as part of system software updates, not as stand-alone firmware updaters, so in your case, you might need to have installed a 10.13.6 High Sierra installation in order to be certain of the latest firmware version? 2nd: DosDude's patchers are incompatible with OpenCore Legacy Patcher, so if you have multiple partitions using both, when you use the Option key boot, select any DosDude partition directly, never with an OpenCore first. When booting OpenCore installations, sometimes it doesn't complete the patching process, which requires booting from the Installer USB EFI partition first, which then gives a 2nd selection to the installed partition, to then select the installed partition and boot. Sometimes this doesn't work, I often use the verbose boot to 'see' what the issue is, on older Macs the 'legacy USB bus' often causes a stall in the boot process which will result in a non-boot. Sometimes disconnecting a USB device might help the boot. Perhaps zap PRAM and try again, sometimes it takes a few tries. If you ever upgrade a partition from a DosDude Catalina patcher to an OpenCore Legacy, you MUST remove ALL the DosDude patches, preferences, etc. from the upgraded partition. Also, maybe download a 12.5.1 (21G83) installer and reinstall rather than proceeding with your 12.5 (21G72) and then updating. After installation, I think you'llkhronokernel/Mini-Monterey-Patcher - GitHub
OpenCore Legacy PatcherA Python-based project revolving around Acidanthera's OpenCorePkg and Lilu for both running and unlocking features in macOS on supported and unsupported Macs.Our project's main goal is to breathe new life into Macs no longer supported by Apple, allowing for the installation and usage of macOS Big Sur and newer on machines as old as 2007. Noteworthy features of OpenCore Legacy Patcher:Support for macOS Big Sur, Monterey, Ventura, and SonomaNative Over the Air (OTA) System UpdatesSupports Penryn and newer MacsFull support for WPA Wi-Fi and Personal Hotspot on BCM943224 and newer wireless chipsetsSystem Integrity Protection, FileVault 2, .im4m Secure Boot and VaultingRecovery OS, Safe Mode and Single-user Mode booting on non-native OSesUnlocks features such as Sidecar and AirPlay to Mac even on native MacsEnables enhanced SATA and NVMe power management on non-Apple storage devicesZero firmware patching required (ie. APFS ROM patching)Graphics acceleration for both Metal and non-Metal GPUsNote: Only clean-installs and upgrades are supported. macOS Big Sur installs already patched with other patchers, such as Patched Sur or bigmac, cannot be used due to broken file integrity with APFS snapshots and SIP.You can, however, reinstall macOS with this patcher and retain your original dataNote 2: Currently, OpenCore Legacy Patcher officially supports patching to run macOS Big Sur through Sonoma installs. For older OSes, OpenCore may function; however, support is currently not provided from Dortania.For macOS Mojave and Catalina support, we recommend the use of dosdude1's patchersGetting StartedTo start using the project, please see our in-depth guide:OpenCore Legacy Patcher GuideSupportThis project is offered on an AS-IS basis, we do not guarantee support for any issues that may arise. However, there is a community server with other passionate users and developers that can aid you:OpenCore Patcher Paradise Discord ServerKeep in mind that the Discord server is maintained by the community, so we ask everyone to be respectful.Please review our docs on how to debug with OpenCore to gather important information to help others with troubleshooting.Running from sourceTo run the project from source, see here: Build and run from sourceCreditsAcidantheraOpenCorePkg, as well as many of the core kexts and toolsDhinakGMain co-authorKhronokernelMain co-authorAusdauersportleriMacs. Monterey Patcher 0.7 will be delayed due to additional testing with macOS Monterey 12.0.1 Beta. Monterey Patcher 0.7 will be releasing soon it is being tested on mcaos Monterey beta 6 - 10. Monterey Patcher now supports Monterey Patcher 0.7 will be delayed due to additional testing with macOS Monterey 12.0.1 Beta. Monterey Patcher 0.7 will be releasing soon it is being tested on mcaos Monterey
Faycel2025/Mini-Monterey-Patcher - GitHub
Why dortania opencore team on GitHub used a different account for the core package, inacidanthera.As its probably the same opencore package used in the dortania account.As far as I can see they share some developers so probably partly the same team.Maybe they used different accounts to keep it more accessible by creating a distinction between corepackage and patcher? In my opinion OCLP is a project totaly apart from OpenCore development and the OC developers are not really involved in this project, on my side it was very easy to arrive at this solution because I use OC on a lot of my Hackintosh #13 In my opinion With the Flavours theme this is more beautyful then the original Mac boot Attaching theme FlavoursUpdate theme Flavours new Windows Disk Icon attaching Windows.icns.zip.zip Flavours.zip 521.7 KB · Views: 178 Windows.icns.zip 11.7 KB · Views: 147 Last edited: Aug 24, 2021 #14 Just wondering… Without OpenCore and native Big Sur install obviously it’s impossible to download the Monterey public beta via Apple’s system update because this MacBook isn’t supported anymore for macOS 12.Do you think that it’s possible to use your approach using the BigSur installer instead of Monterey and afterwards upgrade the official way to the public beta?As mentioned above all that’s needed for the system update to download macos12 public beta probably is making it appear as a 11,4 MacBook Pro?And if this is possible, do you think installing OpenCore bootloader only in the existing native Big Sur will do the trick?So technically i mean only replacing the regular EFI by OpenCore in a regular working Big Sur install. #15 Just wondering… Without OpenCore and native Big Sur install obviously it’s impossible to download the Monterey public beta via Apple’s system update because this MacBook isn’t supported anymore for macOS 12.DoOpencore Legacy Patcher Monterey Download - 4shared
Help improve the project!Donate to OpenCore Legacy PatcherFull Changelog2.0.1 and 2.0.0 Changelog (click to expand)2.0.1Fix MacBookPro13,3 listing 'Available patches' after having installed all applicable patchesFix Nvidia Tesla and Kepler patches not installing on Monterey (and older if applicable)Fix Nvidia Web Drivers incorrectly listing 'OpenGL', 'compat' and 'nvda_drv(_vrl)' missing2.0.0Set AssociatedBundleIdentifiers property in launch services as an arrayMove to auto-generated pre/postinstall scripts for PKGsStreamlines PKG creation process, ensuring Install and AutoPKG scripts are always in syncAdd support for gktool in PKG postinstall scriptsRemoves Gatekeeper "verifying" prompt on first launch after PKG installationNote gktool is only available on macOS Sonoma and newerResolve unpatching crash edge case when host doesn't require patches.Implement new Software Update Catalog Parser for macOS InstallersImplement new Copy on Write detection mechanism for all file copying operationsImplemented using getattrlist and VOL_CAP_INT_CLONE flagHelps improve performance on APFS volumesIncrease model range for S1X/S3X patching to include Haswell Macs and MacPro6,1Helps avoid an issue where older machines with newer, unsupported SSDs would fail to bootOnly affects building EFI from another machineResolve AMD Navi MXM GPU detection for modded iMac9,x-12,xThanks @Ausdauersportler for the patch!Implement early macOS Sequoia support:Supporting Macs with Metal and non-Metal-based graphics:MacBook5,x - 10,1MacBookAir2,x - 7,xMacBookPro4,1 - 14,xMacmini3,1 - 7,1iMac7,1 - 18,xMacPro3,1 - 6,1MacPro3,1 can only boot with 4 cores max currently8 cores can be re-enabled for older OSes in the GUI:Settings -> Build -> MacPro3,1/Xserve2,1 WorkaroundXserve2,1 - 3,1Xserve2,1 can only boot with 4 cores max currently8 cores can be re-enabled for older OSes in the GUI:Settings -> Build -> MacPro3,1/Xserve2,1 WorkaroundExcludes the newly dropped MacBookAir8,x series.No estimate can be given when support will be added.For non-Metal graphics, Photos app will be broken.No estimate can be given when support will be added.Implement new MetallibSupportPkg system to support macOS Sequoia on Metal 3802-based GPUs.See repository for more details: MetallibSupportPkg.Implement new Patchset Detection architecture.Implement new kernel cache building architecture.Resolve "Label" error in com.dortania.opencore-legacy-patcher.os-caching.plist.Add macOS Sequoia icons to boot picker and GUI.Resolve Memoji crashes on 3802 GPUs.Resolve Photos Memories tab crash on Intel Ivy Bridge/Haswell iGPUs.Increment Binaries:PatcherSupportPkg 1.8.0 - releaseOpenCorePkg 1.0.1 - releaseLilu 1.6.8 - releaseWhateverGreen 1.6.7 - releaseRestrictEvents 1.1.4 - releaseFeatureUnlock 1.1.6 - releaseDebugEnhancer 1.0.9 - releaseCPUFriend 1.2.8 - releaseAutoPkgInstaller 1.0.4 - releaseCryptexFixup 1.0.3 - releaseAsset InformationOpenCore-Patcher.pkg:Visual GUI-based app installerRecommended for all usersOpenCore-Patcher-Uninstaller.pkg:Uninstalls OpenCore-Patcher.app and additional utilitiesDoes not revert any patches installedOpenCore-Patcher-GUI.app:Legacy app, installs OpenCore-Patcher.pkg internallyDirect app download is deprecated, and planned for remove in the futureAutoPkg-Assets.pkg:Additional resources used by OpenCore-PatcherAutomatically pulled when needed, don't download 2.0.0 With the release of OpenCore Legacy Patcher 2.0.0, we're proud to announce macOS Sequoia support! And with it, 83 unsupported Mac models will be able to run Apple's latest operating system!With macOS Sequoia, we spent many months working tirelessly to get these old machines running. And because of the sheer number of different hardware we support and the challenges of working on a closed-source operating system, not all features are currently available.Main limitations with macOS Sequoia:Lack of support for recently dropped 2018 T2 MacBook Airs (MacBookAir8,x).macOS Sequoia and OpenCore Legacy Patcher Support #1136Single CPU limitation on 2008. Monterey Patcher 0.7 will be delayed due to additional testing with macOS Monterey 12.0.1 Beta. Monterey Patcher 0.7 will be releasing soon it is being tested on mcaos Monterey beta 6 - 10. Monterey Patcher now supportsno internet on opencore legacy patcher macOS monterey :
ASUS P8P67 PRO/EVO HackintoshInstall macOS Monterey on ASUS P8P67 PRO/EVO (REV3.0) Mainboard with Sandy Bridge CPU.InformationThis Hackintosh was created with help of Qraxin/Asus-P8P67-OpenCore-EFI repository and OpenCore guide Desktop Sandy Bridge as base.macOS: Monterey 12.6.1bootloader: OpenCore 0.8.5Table of ContentsASUS P8P67 PRO/EVO HackintoshInformationHardwarePerformanceInstall macOS1. Installer-Drive2. BIOS Settings3. Install macOS4. Post InstallUpdate macOSDualBoot WindowsResourcesBoot FlagsACPI PatchesKextsToolsTroubleshootingLinks and DocumentationHardwareComponentVariantInfoBuyMainboardASUS P8P67 PRO / ASUS P8P67 EVOorigin.asus.com origin.asus.comebay.de ebay.deProcessorIntel Core i7 2600Kark.intel.comebay.deDDR3 RAMRipjawsX DDR3 16GBgskill.comamazon.deSSDSamsung 870 EVOsamsung.comamazon.deGraphicsAsus Radeon RX 570 / MSI GeForce GTX 760 / Sapphire Radeon R7 250Xasus.com de.msi.com techpowerup.comamazon.de ebay.de ebay.deWiFi / BTASUS PCE-AC58BT + BCM94352Z / ASUS PCE-AC55BT + BCM4352 / Fenvi FV T919 PCI-Easus.com | fenvi.cn asus.com | osxlatitude.com fenvi.comamazon.de | amazon.de ebay.de | ebay.de amazon.deUSB 3.0Inateck USB 3.0 PCIe KT4006inateck.deamazon.dePerformanceGeekbench 5 Score of Intel Core i7 2600K CPUGeekbench 5 Score (Metal) of Radeon RX 570 GPUBlackmagic Disk Speed of Samsung 870 EVO SSDInstall macOS1. Installer-Drivea) macOS InstallerTo create a working macOS Installer-Drive, you need the following:An empty USB flash drive (minimum 16GB)A device already running macOSCreate an USB Installer-Drive with OpenCore Legacy Patcher following the How to install macOS Monterey on an unsupported Mac guide.b) OpenCoreDownload latest OpenCore: acidanthera/opencorepkgChose debug for installation and testing or release for final useMount EFI partition of Installer-Drive (e.g. with OpenCore Configurator)Follow this guide OpenCore-Install-GuideBasically the files mentioned in file-swaps need to be copied/updatedAdd OpenCanopy.efi to EFI/OC/Drivers for GUI pickerAdd VBoxHfs.efi to EFI/OC/Drivers for HFS+ supportRepeat this step when switching from debug to release versionc) Patches and KextsCopy all ACPI patches from/to EFI/OC/ACPI/Copy config.plist from/to EFI/OC/config.plistCopy all kexts from/to EFI/OC/Kexts/2. BIOS SettingsUpdate to version 3602 (firmware in BIOS folder)Use following BIOS settings (F8/DEL on boot):EZ-Mode- System Performance - Asus OptimizedAdvanced Mode- Advanced - CPU - Ai Overclock Tuner: X.M.P. - Intel VT-d: Enabled - SATA - Mode Selection: AHCI - S.M.A.R.T.: Enabled - USB - Legacy: Enabled - Legacy USB 3.0: Enabled - EHCI Hand-off: Enabled - Onboard Devices - Renesas USB 3.0: Disabled - Bluetooth: Disabled - VIA 1394: Disabled - Marvell Storage: AHCI - Serial Port: Disabled- Boot - PCI ROM: Legacy ROM - Option ROM: Force BIOS3. Install macOSConnect Installer-Drive to USB2 portBoot from Installer-Drive (F8 on BIOS post -> [UEFI] USB Drive)Select macOS Installer (Install macOS Monterey)Begin installation on APFS formatted SSDFinish the initial macOS setup process4. Post Installa) OpenCoreAfter successful install copy OpenCore to system EFI partitionRepeat steps 1b + 1c but with EFI of macOS SSD as targetSwitch OpenCore from debug to release version (file-swaps)To disable all logging apply following config-changesb) Sleep/WakeRead and follow instructions in Docs/SLEEP.c) ToolsInstall the following from Tools folder:Intel Power Gadget to test CPU frequency and speed steppingOpenCore Configurator (OCC) to modify/update config.plistHackintool to check for loaded kexts and system settingsd) Audio(Optional) Install VoodooHDA by following instructions in Docs/AUDIO.Update macOSCheck the official update-guide: OpenCore-Post-Install/updateBackupFull system backup with Time Machine or similar softwareCopy current EFI to OpenCore USB-Drive for recovery purposeDownloadLatest version of OpenCore and replace files in EFIUpdates for all installed kexts and replace in EFIRebootBoot with updated OpenCore version and kextsIf the system doesn'tComments
Need to do the OpenCore Legacy Patcher root kernel patches for graphics & wifi? #17 I successful booted into Monterey!I’m not sure what I did that made that happen. It’s one of two things. 1. I installed Catalina with Dos Dudes patcher. Then downloaded opencore and did the Monterey install. 2. At some point during the process in 1, I installed just the OpenCore EFI stuff on a USB and then was able to boot into 12.5 from there. My new issues- 1. I wiped the drive completely before I installed Catalina with the Dos Dude Patcher. I know that I could make a partition later for Snow Leopard. I figured installing High Sierra after installing Catalina shouldn’t be a problem. I did it previously without issue. I planned on deleting the volume with Catalina after I installed 10.13. 2. After installing 10.13 (HS), I got an Incompatible disk warning. I understand why I have that warning. It likely a result of Monterey already being installed on the disk (remember, I didn’t have this issue when I installed HS after installing Catalina previously). 3. Can I ignore the message? Will some kind of corruption occur? Or does the message basically mean I can’t take advantage of the never version of APFS that installed with Monterey? I can wipe the drive and start again by installing the OS in order, but I’m afraid I’m going to have trouble getting Monterey to install and boot again. It took me days to get it booting. #18 Howard Oakley gives a thumbnail history of APFS in this blog article. Since HS, features have been added to support the splitting of the system volume into read-only and read-write parts and presenting those two parts as a single root filesystem in Finder. You're seeing the Incompatible Disk message because HS has mounted a volume which was created by a newer version of APFS.I see the same message, as I mentioned previously, and I haven't seen any corruption or other problems, but I've been careful to avoid accessing the Monterey volumes from HS. Trying to avoid mounting the Monterey volumes in HS by putting 'noauto' entries in /etc/fstab didn't work for me, so I just hid them from the desktop: Code: sudo SetFile -a V /Volumes/Monterey\ HD\ -\ Datasudo SetFile -a V /Volumes/Updatekillall Finder The Update volume appeared after I installed all of the available HS updates. SetFile is part of the Xcode command line developer tools.My disk layout looks like this: Code: grumpus$ diskutil list/dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_APFS Container disk1 499.9 GB disk0s2/dev/disk1 (synthesized): #: TYPE NAME SIZE IDENTIFIER
2025-04-07Installed. #10 I don't know what happened, sorry. In my experience, several reboots happen during an OCLP Monterey install, and each reboot took place with no intervention on my part. Maybe you've seen it already, but Mr. Macintosh has an excellent video walking you through the entire process.Were I in your shoes, I'd start over. First, I would reset the NVRAM and reset the SMC of the laptop, just to be starting from a clean slate. Then start the OCLP Monterey install again, but this time erase the entire drive. The reboot(s) during the installation shouldn't require any manual intervention. After the Monterey install is complete, OCLP should prompt you regarding booting from disk rather than the installer USB, so just follow the prompt. Also, Mr. Macintosh shows how to set the default boot device in the video.Once Monterey is up and running, use disk utility to partition the drive to make room for Snow Leopard and whatever else you have planned. Leave enough room for Monterey + High Sierra. Use disk utility to create a new volume inside the Monterey container for High Sierra. Now do your High Sierra install.When Monterey and High Sierra are working, you can turn your attention to Snow Leopard.EDIT: Maybe it is better to install Snow Leopard first, just to insure that it doesn't mess with whatever OCLP does to the EFI. Me, when it comes to more than a couple of OSes on the same disk, I'm a fan of VirtualBox Last edited: Aug 23, 2022 #11 No worries, I appreciate all the help.I did watch Mr. Macintosh's video several times. I figured something was wrong when it wouldn’t reboot on its own like in the video.At this point I have nothing to lose and could just reformat the entire drive to run SL.Before I embarked on this project, I was running Catalina with Dod Dude’s patcher and HS on a separate volume. I also had Windows 10 on there. Maybe I should start with Catalina? My guess is I will still have the same issue, but who knows #12 I still think it's worth resetting NVRAM and SMC, that has cleared up mysterious boot failures for me several times in the past, and it can't hurt (to the best of my meager knowledge). #13 Just to put it out there, I've got a 2010 MacBook (White, not Pro, but same CPU and GPU) and it's running OpenCore with both Snow Leopard and Big Sur underneath it.I used USB to install Big Sur through OpenCore Legacy Patcher, did all of the updates (11.6.5 at the time, now 11.6.8), partitioned the SSD outside of the APFS container and made a GPT HFS+ (Mac OS
2025-04-01Machine ModeliMac14,1Application VersionLatest Build (nightly)Application VariantTUI (Text User Interface)What versions of macOS are you seeing the problem on?macOS 12, MontereyWhere does this issue happen?Between booting macOS and Login ScreenWhat is the Isssue?Hi! I was running Big Sur with patched sur without any problems.Yesterday I installed Monterey using OpenCore Legacy and the installation was successful .... except my external HDMI monitor is not working. I use a thunderbolt 2 to HDMI cable. It works using other patchers, like Monterey mini patcher but this one fails to complete the installation.Using any other method or OS I can see image in my external display even on boot or the installation process.This is iMac 14.1 with Iris Pro iGPUAny help?Sorry for my english and thanks for your timeAny Additional InformationResumen del hardware:Nombre del modelo: iMacIdentificador del modelo: iMac14,1Nombre del procesador: Quad-Core Intel Core i5Velocidad del procesador: 2,7 GHzCantidad de procesadores: 1Cantidad total de núcleos: 4Caché de nivel 2 (por núcleo): 256 KBCaché de nivel 3: 4 MBMemoria: 16 GBVersión de la ROM de arranque: 146.0.0.0.0Versión SMC (sistema): 2.14f24
2025-04-06#1 Update 23 April 2022 Support in Github only!--------------------------------------------------------------------------------------------How to install macOS Monterey on a MacBook Pro retina late 2013Without patcher, without any kexts files. Genuine macOS booting with OpenCore SIP activateProbably work on other Mac?Guide ➤ Install macOS Monterey 12 MacBook Pro retina late 2013For support open Issue: [New Issue]If you are using OCLP, please post your comments on the subject to dedicate this effect, do not post here.If you have a mac with are you using dual Graphics or any GPU other than the Intel Iris Pro Graphics I recommand to using OCLP and post your comments on the subject to dedicate this effect. Last edited: Apr 23, 2022 #4 this is great but can you do it without encore nd keep it all native? my 2015 MacBook 12 has all the drivers still available in Monterey its just an arbitrary cut off?Thanks #5 To achieve this would have to change a few things in the system.Currently with only OC as bootloader without any kexts inject it is original untouch #6 One of cool things with OC is bootning Windows directly from the boot menue Windows 11 is installed on a Thunderbolt Drive , independant of my Monterey drive Windows 11 is really fast and cool #7 To achieve this would have to change a few things in the system.Currently with only OC as bootloader without any kexts inject it is original untouch any idea how I would do this? as I say every device is still natively supported. #9 Hi @chris1111,Your solution worked for me. What I did:1- Generated an EFI folder using OCLP 0.2.4;2- Removed all Kext files from Kexts;3- Added HfsPlus.efi on Drivers (OpenCanopy.efi, OpenRuntime.efi, and HfsPlus.efi);4- Added CleanNvram.efi in Tools (BootKicker.efi, OpenShell.efi, and CleanNvram.efi);5- Removed ALL PCI in including the key for brcmfx-country from
2025-03-31OpenCore Legacy PatcherA Python-based project revolving around Acidanthera's OpenCorePkg and Lilu for both running and unlocking features in macOS on supported and unsupported Macs.Our project's main goal is to breathe new life into Macs no longer supported by Apple, allowing for the installation and usage of macOS Big Sur and newer on machines as old as 2007. Noteworthy features of OpenCore Legacy Patcher:Support for macOS Big Sur, Monterey, Ventura, and SonomaNative Over the Air (OTA) System UpdatesSupports Penryn and newer MacsFull support for WPA Wi-Fi and Personal Hotspot on BCM943224 and newer wireless chipsetsSystem Integrity Protection, FileVault 2, .im4m Secure Boot and VaultingRecovery OS, Safe Mode and Single-user Mode booting on non-native OSesUnlocks features such as Sidecar and AirPlay to Mac even on native MacsEnables enhanced SATA and NVMe power management on non-Apple storage devicesZero firmware patching required (ie. APFS ROM patching)Graphics acceleration for both Metal and non-Metal GPUsNote: Only clean-installs and upgrades are supported. macOS Big Sur installs already patched with other patchers, such as Patched Sur or bigmac, cannot be used due to broken file integrity with APFS snapshots and SIP.You can, however, reinstall macOS with this patcher and retain your original dataNote 2: Currently, OpenCore Legacy Patcher officially supports patching to run macOS Big Sur through Sonoma installs. For older OSes, OpenCore may function; however, support is currently not provided from Dortania.For macOS Mojave and Catalina support, we recommend the use of dosdude1's patchersGetting StartedTo start using the project, please see our in-depth guide:OpenCore Legacy Patcher GuideSupportThis project is offered on an AS-IS basis, we do not guarantee support for any issues that may arise. However, there is a community server with other passionate users and developers that can aid you:OpenCore Patcher Paradise Discord ServerKeep in mind that the Discord server is maintained by the community, so we ask everyone to be respectful.Please review our docs on how to debug with OpenCore to gather important information to help others with troubleshooting.Running from sourceTo run the project from source, see here: Build and run from sourceCreditsAcidantheraOpenCorePkg, as well as many of the core kexts and toolsDhinakGMain co-authorKhronokernelMain co-authorAusdauersportleriMacs
2025-04-16Why dortania opencore team on GitHub used a different account for the core package, inacidanthera.As its probably the same opencore package used in the dortania account.As far as I can see they share some developers so probably partly the same team.Maybe they used different accounts to keep it more accessible by creating a distinction between corepackage and patcher? In my opinion OCLP is a project totaly apart from OpenCore development and the OC developers are not really involved in this project, on my side it was very easy to arrive at this solution because I use OC on a lot of my Hackintosh #13 In my opinion With the Flavours theme this is more beautyful then the original Mac boot Attaching theme FlavoursUpdate theme Flavours new Windows Disk Icon attaching Windows.icns.zip.zip Flavours.zip 521.7 KB · Views: 178 Windows.icns.zip 11.7 KB · Views: 147 Last edited: Aug 24, 2021 #14 Just wondering… Without OpenCore and native Big Sur install obviously it’s impossible to download the Monterey public beta via Apple’s system update because this MacBook isn’t supported anymore for macOS 12.Do you think that it’s possible to use your approach using the BigSur installer instead of Monterey and afterwards upgrade the official way to the public beta?As mentioned above all that’s needed for the system update to download macos12 public beta probably is making it appear as a 11,4 MacBook Pro?And if this is possible, do you think installing OpenCore bootloader only in the existing native Big Sur will do the trick?So technically i mean only replacing the regular EFI by OpenCore in a regular working Big Sur install. #15 Just wondering… Without OpenCore and native Big Sur install obviously it’s impossible to download the Monterey public beta via Apple’s system update because this MacBook isn’t supported anymore for macOS 12.Do
2025-04-24