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

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 OS

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.14f24

#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

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