Ok, but until the system is installed in the internal SSD the only OCLP version I have is the one on the USB stick and I rely on that to boot the system and complete the installation.
Anyway I got out of the loop by resetting NVRAM after I got the Lily error. After that, the installer managed to complete the ramrod stuff (God knows what that means) and gave the final checkpoint successful (which I assume is what it needs to boot the system at next startup).
Writing from Monterey now... I'll let you know if I encounter any bug or whatsoever
The Lilu error happens from time to time (rarely) and a reboot is the cure. When installing OCLP onto your internal EFI pull the USB on reboot.
The guide always recommend to have the OC on the USB, after using it for two years now (installed on an internal disk) and knowing exactly how to get rid of it (reboot with PRAM reset and using the alt/option to reach the EFI boot picker directly) I do not see any advantage of using the additional step using it on the USB.
P.S.:
I have a bunch of prepared external maOS installer SD cards, no one has it's own OC version. This way I can use them with all my systems.
EDIT:
This is entirely different story if having a system without an EFI boot picker.
This seems to work for my SanDisk SSD (System Profiler shows TRIM as being enabled), although it's not clear whether having TRIM enabled is really beneficial for every drive type.
Ok, just to make sure I got it. you're telling me that OCLP is not needed on the usb stick from which I install the system!? In that case, you choose the boot media directly from the boot picker of the computer (assuming you have an apple machine).
But with no OCLP there is no injection in NVRAM to make the installer think this is a newer machine. How do you happen to boot the installer?
Does anyone have problems with USB pendrives? If I tried to copy under FAT format and it works fine, but if I try to do it under Expanded Journaling it's very slow, looks like it's sending data chunks with delay, like 10x slower.
I got a problem with a remotely serviced Mac Pro 5,1 Dual with RX580 and OCLP 0.33 Minimal Spoofing
Tried a clean install of 12.1 via createinstallmedia thumb drive installing on a sata ssd on southbridge and we run always in an error after the 1st reboot:
Failed to get local signing public key
the odd thing is: I can install it performing the same steps on my machine, we use the same 0.33 built generated on the Mac Pro what hangs. My machine has a RX560, the other problematic one a RX580.
12.0 runs fine on a NVMe drive we dont touch at the moment.
the machine is stripped down to just what is needed to do the installation.
we did even a firmware cleanup.
USB hardware is a standard alu keyboard and a usb mouse.
Ok, just to make sure I got it. you're telling me that OCLP is not needed on the usb stick from which I install the system!? In that case, you choose the boot media directly from the boot picker of the computer (assuming you have an apple machine).
But with no OCLP there is no injection in NVRAM to make the installer think this is a newer machine. How do you happen to boot the installer?
Put OCLP somewhere - internal drive or USB drive. Use the boot picker to choose that OCLP (select it, hold the Control key down, press enter to bless it - makes it the default booter - and start it), launch the installer from the OpenCore boot picker.
hello!!
after fixing the usb installer, now i have a new problem.
installation goes well, mac boots fine but after first reboot it blocks on a white screen with a danger icon...
on one of the two macbooks 5,2 i did the post install from the oclp 0.33 but i had the same result...any sugestion??
using 12.1 version
ty
hello!!
after fixing the usb installer, now i have a new problem.
installation goes well, mac boots fine but after first reboot it blocks on a white screen with a danger icon...
on one of the two macbooks 5,2 i did the post install from the oclp 0.33 but i had the same result...any sugestion??
using 12.1 version
ty
i did that to install, the after install is the problem...i even booted with install usb in - pressed alt - picked oclp - and then i picked my HD and not install monterey, still same error
Put OCLP somewhere - internal drive or USB drive. Use the boot picker to choose that OCLP (select it, hold the Control key down, press enter to bless it - makes it the default booter - and start it), launch the installer from the OpenCore boot picker.
i did that to install, the after install is the problem...i even booted with install usb in - pressed alt - picked oclp - and then i picked my HD and not install monterey, still same error
This is also how I use the OCLP on a SD card to boot my 3 internal SSDs each with different macOS ...
No need to remember which version is on which drive and sync them.
Just update the OCLP on the SD card once for all drives.
Hello!
I have a problem when I boot into the drive: "Display: Lilu Dev failed to obtain model information, retrying" Model: mpb 15 - 2012 (i disabled GPU Nvidia)
Mac Pro 5,1 Opencore REL-076-2021-12-06 OCLP 0.3.3 and Montery 12.1 Sometimes I get the Lilu dev: @ failed to obtain model information, retrying... error when booting. I have bootpicker enabled and...
Mac Pro 5,1 Opencore REL-076-2021-12-06 OCLP 0.3.3 and Montery 12.1 Sometimes I get the Lilu dev: @ failed to obtain model information, retrying... error when booting. I have bootpicker enabled and...
During the last two years of using OpenCore I have seen this issue rarely with different versions of OC and Lilu. From my perspective it happens after changing the OC version (which I do frequently on a number of test systems) and it is gone after a simple reboot or a reboot with a simple PRAM reset. Just because I cannot force the error it is difficult to describe and more difficult to debug.
So it is still unclear to me if this a follow up of the OC change or a rarely occurring issue with Lilu and OpenCore.
The Lilu error happens from time to time (rarely) and a reboot is the cure. When installing OCLP onto your internal EFI pull the USB on reboot.
The guide always recommend to have the OC on the USB, after using it for two years now (installed on an internal disk) and knowing exactly how to get rid of it (reboot with PRAM reset and using the alt/option to reach the EFI boot picker directly) I do not see any advantage of using the additional step using it on the USB.
P.S.:
I have a bunch of prepared external maOS installer SD cards, no one has it's own OC version. This way I can uses them with all my systems.
thank you for the guidance,
I think I've done these steps, without altering the settings in OCLP, is there a specific thing to change in order to have a boot scree? I'm planning to do that on an external usb.
I don't know if using the external usb 3.1 card ca be utilised as original 1.1 USB
the OCLP TUI has a hardware detection and creates a config fitting to the GPU used. If you plan to use the RX 580 please boot into the latest supported macOS (Mojave) with this GPU installed, run OCLP and create the config and install it (internally or externally on the USB installer) and go ahead following the OCLP online docs.
You need a GOP vBIOS on the 580. Using the 7970 would make the installation smooth but after changing the card the system will possibly just boot into a black screen. Best case will allow you to access the system remotely using screen sharing. Here you may be able to run OCLP to generate a new RX580 aware config and write if to the boot disk.
Unfortunately everything went bad.
-tried to create a new USB installation so created from latest 3.3 the patcher then transferred to USB ONLY, but seems that system EFI has been destroyed from root ssd as well!. Why really? never asked to affect this partition!
No recovery mode appears, no time machine backup, nothing! just black screen of death and only if putting 8800 Nvidia I see a poor choice for current Mohave boot from root ssd, which gives a no signal soon afterwards. Again no time-machine, no internet-recovery, just nothing. The poor arrow to back (down below) forces again system to shut-down.
I'm so desperate right now.
Any tips to recover from this total mess?
Just a time-machine option would be enough I guess.
UPD* USB seems to be a real problem for OCLP, I plugged keyboard and mouse in different usb ports and now seems that Monterey is installing!
I could need a tip or help. Since I updated my iMac 14,2 with NVIDIA GTX 780M from Big Sur to Monterey using OLCP (now) 0.3.3 I needed to post install the patches. The overall graphics performance of macOS seems to run better but my graphic apps (i.e. PhotoShop etc all) have an issue with weak performance. Photoshop gives the following note that I haven't had under Big Sur.
I could need a tip or help. Since I updated my iMac 14,2 with NVIDIA GTX 780M from Big Sur to Monterey using OLCP (now) 0.3.3 I needed to post install the patches. The overall graphics performance of macOS seems to run better but my graphic apps (i.e. PhotoShop etc all) have an issue with weak performance. Photoshop gives the following note that I haven't had under Big Sur.
This is a known issue since October and I have seen a fix on Discord for HD4000, but do not know if it has been added or even if it works for the Kepler GPU, too.
It is obvious that some libs within the OpenCL.framework are missing on Monterey, while still present on Big Sur!
This thread will be dedicated to the discussion of running macOS 12.0 on unsupported Macs
At the time of writing, WWDC has wrapped up and Developer Seeds have been sent out. We're eagerly awaiting for all our community developers and enthusiasts to test out the new version of macOS
We will be expanding this thread with much more information as the day goes by including known issues as well as patcher support
macOS Monterey Compatibility
2016 and later MacBook
MacBook9,1
MacBook10,1
2015 and later MacBook Air
MacBookAir7,x
MacBookAir8,x
MacBookAir9,1
2015 and later MacBook Pro
MacBookPro11,4-5
MacBookPro12,1
MacBookPro13,x
MacBookPro14,x
MacBookPro15,x
MacBookPro16,x
2015 and later iMac
iMac16,x
iMac17,1
iMac18,x
iMac19,x
iMac20,x
2017 and later iMac Pro
iMacPro1,1
2014 and later Mac mini
Macmini7,1
Macmini8,1
2013 and later Mac Pro
MacPro6,1
MacPro7,1
Not officially supported in macOS Monterey, but most likely fully capable of running Monterey (details will be found in the patcher documentation)
2013 and 2014 MacBook Pro
MacBookPro11,1-3
2013 and 2014 MacBook Air
MacBookAir6,x
2015 MacBook
MacBook8,1
2014 and early 2015 iMac
iMac14,4
iMac15,1
* Not officially supported in macOS Big Sur, but are fully capable of running both Big Sur and Monterey with a Metal-compatible GPU and upgraded WiFi/BT card. Nvidia dGPU based systems need Kepler patches (Beta 7+)
+ Does not support any form of graphics acceleration currently
++ Catalina supported system capable of running Monterey with Kepler (Beta 7+) and/or HD4000 patches
Early-2008 or newer Mac Pro, iMac, or MacBook Pro:
MacPro3,1 *
MacPro4,1 *
MacPro5,1 *
iMac7,1 +
iMac8,1 +
iMac9,1 +
iMac10,x +
iMac11,x *
iMac12,x *
iMac13,x ++
iMac14,1-3 ++
MacBookPro4,1 +
MacBookPro5,x +
MacBookPro6,x +
MacBookPro7,x +
MacBookPro8,x +
MacBookPro9,x ++
MacBookPro10,x ++
Late-2008 or newer MacBook Air or Aluminum Unibody MacBook:
MacBookAir2,1 +
MacBookAir3,x +
MacBookAir4,x +
MacBookAir5,x ++
MacBook5,1 +
Early-2009 or newer Mac Mini or white MacBook:
Macmini3,1 +
Macmini4,1 +
Macmini5,x +
Macmini6,x ++
MacBook5,2 +
MacBook6,1 +
MacBook7,1 +
MacBook8,1 ++
Early-2008 or newer Xserve:
Xserve2,1 *
Xserve3,1 *
2006-2007 Mac Pros, iMacs, MacBook Pros, and Mac Minis:
MacPro1,1
MacPro2,1
iMac4,1
iMac5,x
iMac6,1
MacBookPro1,1
MacBookPro2,1
MacBookPro3,1
Macmini1,1
Macmini2,1
— The 2007 iMac 7,1 is compatible with Catalina and potentially Big Sur if the CPU is upgraded to a Penryn-based Core 2 Duo, such as a T9300.
2006-2008 MacBooks:
MacBook1,1
MacBook2,1
MacBook3,1
MacBook4,1 (as with Mojave and Catalina, we'll be on our own here, but Big Sur will be running on this machine!)
2008 MacBook Air (MacBookAir 1,1)
All PowerPC-based Macs
All 68k-based Macs
Nvidia Kepler GPU drivers
Beta7 dropped Nvidia Kepler support. This is affecting all stock 2012/2013 Mac models with Nvidia GPU including iMacs and MacBookPro systems, MacPro3.1/4.1/5.1 with Nvidia PCI GPU cards, and all iMac Late 2009 - Mid 2011 which have been modded with a MXM Nvidia Kepler GPU.
OpenCore Legacy Patcher has re-added support for these systems in v0.2.5
Intel HD 4000 drivers
Compared to macOS Big Sur, macOS Monterey has dropped support for Intel's Ivy Bridge Graphics. This means laptops with Intel HD 4000 GPUs will no longer have graphics acceleration such as the Macmini6,x, MacBookAir5,x, MacBookPro9,x and MacBookPro10,x
OpenCore Legacy Patcher has re-added support for these GPUs in v0.1.7
BCM94322, BCM94328 and Atheros drivers currently can't be re-added currently
Models included:
iMac12,x and older
Macmini3,1 and older
MacBook5,x and older
MacBookAir2,1 and older
MacBookPro7,1 and older (6,x excluded)
MacPro5,1 and older
BCM943224, BCM94331, BCM94360 and BCM943602 still function correctly with OpenCore Legacy Patcher
Installing macOS Monterey on an unsupported Mac Q: How do I determine what Mac model I have?
A: To determine your Mac's SMBIOS model identifier, simply run the below command in Terminal:
Q: How do I download macOS Monterey?
A: The easiest way is to use tools such as gibMacOS which can download macOS Monterey InstallAssistant packages directly from Apple.
Q: How to create a USB installer after downloading the InstallAssistant package?
A: Install the package, it creates an app named Install macOS Monterey in your applications folder. Create the USB installer following this official Apple guide.
Q: How can I use this installer on my unsupported Mac?
A:Before hitting the download button of the patcher tool (see below) please check OpenCore legacy Patcher's documentation. It contains a support statement about unsupported Macs running Monterey, too.
Q: Where/how can I download a patcher tool?
A: Currently there is only one patcher that will soon be supporting macOS 12, Monterey being OpenCore Legacy Patcher. As time goes on, we expect many more developers to join in with their own implementations of the patching process:
OpenCore Legacy Patcher by @khronokernel and @dhinakg is a completely different approach compared to older patcher methods based on OpenCore. This is currently the only option offering system updates via Apple software update like all supported Macs as well as Intel HD4000 iGPU and NVIDIA Kepler acceleration. While the preparation uses a simple GUI the Monterey installation and updating happens in the same way as on supported systems via System Preferences.
Supports macOS 10.9, Mavericks and later to run.
Supports macOS 10.7, Lion and later if Python3 is installed manually.
Q: How can I enable acceleration on my newly unsupported metal GPU?
A: Currently one can regain acceleration for both the Intel's HD4000 iGPUs and the NVIDIA Kepler dGPU via OpenCore Legacy Patcher. For users who wish to install the HD4000/Kepler acceleration patches on non-OpenCore Legacy Patcher machines see here: How to Root Patch with non-OpenCore Legacy Patcher Macs/Hackintoshes
Q: When can we expect OpenGL/non-Metal GPU Acceleration?
A: Starting with OCLP version 0.2.5 legacy OpenGL/non-Metal acceleration for Monterey has been implemented.
Please understand no one can predict when there will be patch sets ready or if current glitches can or will ever be resolved. Remember that it took over 300 days from Big Sur's unveiling to achieve public acceleration for non-Metal GPUs. And with TeraScale 2 acceleration, this took almost 3 years to achieve public acceleration. So be patient as developers are hard at work, however expect no error free support in Monterey. Additionally most applications rely more and more on Metal GPU features. Such apps may cause just a feature loss or will completely fail on non-Metal system. This will never change and the only way out is changing the GPU (iMac Late 2009-Mid 2011 and MacPro systems) with a Metal compatible one or buying a new Mac.
Please remember it is highly suggested that you have a backup in place before installing new system software on your main devices, overwriting any stable releases.
Apple and all patch developers are not responsible for any potential damage or data loss caused by using pre-release software or unofficial support patches. Please use at your own risk.
I have a Late 2013 iMac which I want to upgrade to Monterey. Followed this excellent guide very carefully I selected 12.0.1 and OCLP TUI 0.31. I had a couple of problems down the line, first, I have a Fusion Drive so had to find an alternative method of erasing it (
). After a number of apparent abortive restarts and watching the Verbose scripts, I got to recover my data. All was going well but I took my eye off the screen and after finishing recovering my data it did a restart. Bearing in mind that I was expecting to go to the reload the OCLP step, the restart gave me the "This version of Mac OS X is not supported on this platform!" message. A search on GitHub seemed to recommend parking the NVRAM but now all I get is a prohibited sign and pointer to support.apple.com/mac/startup. CMD R doesn't take me to Mac OSX Recovery. Any clues on how to recover from this? Thanks in advance.
I have a Late 2013 iMac which I want to upgrade to Monterey. Followed this excellent guide very carefully and had a couple of problems down the line, first, I have a Fusion Drive so had to find an alternative method of erasing it (
). After a number of apparent abortive restarts and watching the Verbose scripts, I got to recover my data. All was going well but I took my eye off the screen and after finishing recovering my data it did a restart. Bearing in mind that I was expecting to go to the reload the OCLP step, the restart gave me the "This version of Mac OS X is not supported on this platform!" message. A search on GitHub seemed to recommend parking the NVRAM but now all I get is a prohibited sign and pointer to support.apple.com/mac/startup. Any clues on how to recover from this? Thanks in advance.
Hello guys, from today I am finally on macOS Monterey 12.1 using OCLP 0.3.3 on my old 2011 iMac 27". Few years ago I exchanged Wi-Fi/BT module, so even handoff, continuity are working great. I can even connect AirPods Max to this 10 years old machine! Great and thanks to devs so much! ?
I experienced few graphics glitches - turning off transparency in Accessibility settings helped a lot.
Anyway, there are still few glithes as maps within Maps app not showing at all and whats weird - in Photos app I can't see first item (Library) on the left panel. But I actually CAN see other items as People, Places, Favorites, Newest, Imports etc. Why? Is this caused by non-metal graphics card? Is Photos app somhow only partly metal-capable? I have AMD Radeon HD 6770M.
Would exchanging for Metal-capable card fix all my issues, even with Photos app?