The Log says at the end:
"Install macOS Monterey.app" does not appear to be a valid operating system installer application".
So, OCLP works fine, but the downloaded installer might be corrupted, maybe...
You can try again...
^^^ A similar error could also appear if, for some unknown reason, the infamous stub installer were downloaded: is the installer the correct size (about 12 GB, not about 30 MB)…?
Ok, but still being the penultimate build released and knowing that Apple, if it creates and adds a new and latest version, it does it to fix important problems ... maybe you have solved a little annoyance, but unbeknownst to you it remains a bigger bug than you would not have installing the 'latest build released...
In my case, therefore, I prefer to keep the little annoyance of making an initial click, with the external Apple Trackpad and/or the Magic Mouse of my iMac, but having installed the most recent existing Build on the Apple Servers.
The Log says at the end:
"Install macOS Monterey.app" does not appear to be a valid operating system installer application".
So, OCLP works fine, but the downloaded installer might be corrupted, maybe...
You can try again...
Can you get to this site? Iy has the latest version of Monterey. Get the InstallAssistant package file, copy it to the disk that you want to install Monterey on, and run it. It will install the Monterey installer file in your Applications folder, so if you have another such file there, delete it first. That is one extra hoop, but the file it installs is real.
Happy to report full success installing and running Monterey 12.5.1 with OCLP 0.4.10 on a mid-2010 21.5" iMac11,2 I was given a couple of weeks ago and that I modified to increase performance and support macOS Big Sur/Monterey, possibly Ventura.
Clarksdale dual-core i3-540 @3.06GHz (no boost) -> Lynnfield quad-core i7-860s @2.53GHz (boost to 3.46GHz)
ATI Radeon HD 4670 256MB GDDR3 -> AMD FirePro M5100 2GB DDR5 (red MXM-A model of Dell Precision origin)
500GB 7200rpm SATA HDD -> 256GB SATA-III SSD (obviously running at SATA-II speed)
mini-PCIe Atheros AR9285 -> Apple Broadcom-based BCM94360CD on mini-PCIe adapter board
The fun part was definitely flashing the FirePro M5100 dGPU to recover boot screen. Loved the phase where you remotely ssh onto the (black screen) iMac to flash the 3rd party dGPU and recover boot screen!
All running perfectly, no issues found (so far):
bootscreen Ok
full CPU support
full graphics acceleration
Audio fully working
Sleep & Wake fully working
full USB support
full Wifi & Bluetooth support
OTA updates (installed 12.5 and updated to 12.5.1)
Edit: tested external display with my 48" 4K LG TV through mini-DP to HDMI adapter. I did get 4K @30Hz or @60Hz depending on mini-DP to HDMI adapter but it's quite unstable and leads to system freeze after a few minutes. Therefore, not recommended.
And yes, I need to sort out whatever's wrong in my OC config and causes this incorrect dGPU VRAM to be reported. Haven't looked at this yet.
For me the following always worked well when doing a clean installation, with fully taking over data/settings/etc from a previous macOS.
1st make a CCC clone to an erased disk; 2nd do the installation of macOS on it.
Here the macOS installation has the "last word", while when using Migration Assistant, the latter.
I did have problems with Migration Assistant several times before.
Apologies if too late to the party, but are you saying that I could "restore" a CCC backup of an APFS Big Sur volume group (Macintosh HD and Macintosh HD - Data) to an erased drive, run through the OCLP procedure to install Monterey to it (without erasing the drive in the OCLP process), and that Monterey would then have the same settings, same apps installed, and same data (barring a conflict) as the Big Sur installation?
OpenCore thinks I’m on a MacBook 6,2 or some such. I’m not! I download OpenCore (latest version) and when I open it, it says I can’t use it because it’s especially made for a MacBook (pro). It’s weird.
I’m on a mid-2010 5,1 Mac Pro that I bought (new).
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
Non Apple Software (like Word) and Apple software like Maps, Photos, FinalCut, etc rely on the so called metal framework introduced back with Mojave in 2018. This is a low level and high speed interface to modern graphics cards.
Pre 2012 Apple Macs lack of any graphics acceleration in all macOS versions since Mojave. Patching those older systems with basic OpenGL graphics support becomes more and more difficult. And to make it worse, modern apps using more and more metal features. So expect even a patched old Mac will not be able to run this software without loss of partial or full functionality. This problem cannot be solved or patched.
Some Macs can be upgraded with metal dGPU, all modular systems like the MacPro3,1 -4,1 -5,1 and iMacs built in 2009-2011.
AppleTV and watching 4K Netflix with Safari needs either a metal iGPU (Intel CPU 2012+) or a 2017+ dGPU.
AirDrop, HandOff, Continuity needs a BCM94360CD Bluetooth 4.0/WiFi N combo card available since 2013/2014 in Apple Macs. Some Macs can be upgraded with those modules.
SideCar needs Bluetooth 4.0/WiFi N and an metal iGPU or 2017+ dGPU
Universal Control needs Bluetooth 4.0/WiFi N for wireless
All hardware still supported with Big Sur but dropped from Monterey support will get Apple software and firmware updates until late summer 2023. To apply those (valuable and often necessary firmware) updates you need to install and update Big Sur on your system. All firmware upgrades are bundled into the macOS updates.
The most easy way to achieve this is having an APFS container (aka volume) in parallel with your new Monterey installation. No user data needs to be copied in there. Just boot Big Sur when you get an Big Sur update notification and apply all updates.
You may drop (delete) this basic Big Sur installation after Apple stopped delivering new updates. You will not get new firmware releases.
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 prepare my Mac?
A: Install the latest firmware release you can get for your Mac. All system pre 2012 do not receive any new updates. Install the lastest High Sierra or El Capitan (pre 2009) version to force your old Mac to get the firmware update.
All Macs 2012+ may still receive updates with Catalina until Summer 2022 and Big Sur until 2023. The most easy way to get this still upcoming updates is having a small Catalina/Big Sur installation on a separate APFS container on the internal disk and update this installation on a regular basis.
Q: How do I download macOS Monterey?
A: One way is to use tools such as gibMacOS which can download macOS Monterey InstallAssistant packages directly from Apple. The latest version of the OCLP tools included a download functionality and can build an USB installer automatically.
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. The latest OCLP version can download and build an installer.
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 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.
Q: How can I update my unsupported macOS Monterey installation?
A: Just use the standard apple software update as on supported system. But is is a good practice to update OCLP in advance. Check the OCLP docs how to do this and check out the change log of the new OCLP releases. Keep in mind most systems will need post install patching after each macOS update!
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.
When I used screen recording for my meetings, my mac turns off and then turns back on with a black screen and a message saying: Your computer turned off. And I can't use any remote and QuickTime screen recording(given permission in privacy).
But I can turn it on in recovery mode and safe mode (which I'm using right now to type this). I don't know why it works fine in safe mode but it can't go to the login screen normally without turning off. My imac is 21.5" 2011, with Monterey 12.0.1 (and 12.5.1).
Can you get to this site? Iy has the latest version of Monterey. Get the InstallAssistant package file, copy it to the disk that you want to install Monterey on, and run it. It will install the Monterey installer file in your Applications folder, so if you have another such file there, delete it first. That is one extra hoop, but the file it installs is real.
You have a non EFI flashed graphics card. You can press option all day long and will not get an boot picker.
Only way around is installing OpenCore/OCLP offering a boot picker emulation.
Boot Mojave, download OCLP, install OpenCore to your internal disk and reboot.
Please read the OCLP online documentation how to use OCLP or read the great OpenCore on MacPro thread here on MR - there you can find a lot of additional information to READ and a build OpenCore yourself for your MacPro guide.
The thread and it’s first post provides the information OCLP wants to hide - because it is the follow the printed documentation and be happy solution.
It is your choice, but both need at least a minimal amount of preparation.
You have a non EFI flashed graphics card. You can press option alleys long and will not get an boot picker.
Only way around is OpenCore/OCLP with the boot picker emulation.
Boot Mojave, download OCLP, install OpenCore to your internal disk and reboot.
Please read the OCLP online documentation how to use OCLP or read the great OpenCore on MacPro thread here on MR - there you can find a lot of additional information to READ and a build OpenCore yourself for your MacPro guide.
The thread and it’s first post provides the information OCLP wants to hide - because it is the follow the printed documentation and be happy solution.
It is your choice, but both need at least a minimal amount of preparation.
I have High Sierra (went back when OCLP wouldn’t work correctly)
I’ve been at this for 4 days… OCLP thinks I’m on an MBP, but I don’t have an MBP, I have a mid-2010 Mac Pro 5,1 …. 144.000 that I bought new over a decade ago.
I have High Sierra (went back when OCLP wouldn’t work correctly)
I’ve been at this for 4 days… OCLP thinks I’m on an MBP, but I don’t have an MBP, I have a mid-2010 Mac Pro 5,1 …. 144.000 that I bought new over a decade ago.
Yes, this MacBook story is weird, especially because OCLP has a hardware detection and will show the found Mac model as well the detected graphics/WiFi/BT hardware directly or indirectly.
Anyway, you can set the model manually to override the misleading detection results.
Yes, this MacBook story is weird, especially because OCLP has a hardware detection and will show the found Mac model as well the detected graphics/WiFi/BT hardware directly or indirectly.
Anyway, you can set the model manually to override the misleading detection results.
Okay, obviously you already installed once an OpenCore build generated for the MacBookPro6,2. Since OLCP has no known bug which would give you a misleading system detection I can only assume that YOU changed the SMBIOS setting (no setting needs to be touched by an normal non developer user, one can argue why the settings are available at all) and wrote the wrong OpenCore to your system.
To get around it please press build & install, follow the on screen instruction and reboot. The message should disappear.
On reboot you should see an OCLP boot picker.
Just one problem:
You will not be able to reboot into High Sierra with the new OpenCore (MacPro7,1 spoofing). To achieve this a manual change would be necessary, add -no_compat_check to the boot-args in the config.plist.
Okay, obviously you already installed once an OpenCore build generated for the MacBookPro6,2. Since OLCP has no known bug which would give you a misleading system detection I can only assume that YOU changed the SMBIOS setting (no setting needs to be touched by an normal non developer user, one can argue why the settings are available at all) and wrote the wrong OpenCore to your system.
To get around it please press build & install, follow the on screen instruction and reboot. The message should disappear.
On reboot you should see an OCLP boot picker.
Just one problem:
You will not be able to reboot into High Sierra with the new OpenCore (MacPro7,1 spoofing). To achieve this a manual change would be necessary, add -no_compat_check to the boot-args in the config.plist.
Okay, obviously you already installed once an OpenCore build generated for the MacBookPro6,2. Since OLCP has no known bug which would give you a misleading system detection I can only assume that YOU changed the SMBIOS setting (no setting needs to be touched by an normal non developer user, one can argue why the settings are available at all) and wrote the wrong OpenCore to your system.
To get around it please press build & install, follow the on screen instruction and reboot. The message should disappear.
On reboot you should see an OCLP boot picker.
Just one problem:
You will not be able to reboot into High Sierra with the new OpenCore (MacPro7,1 spoofing). To achieve this a manual change would be necessary, add -no_compat_check to the boot-args in the config.plist.
Does not matter, the error message indicates you have already booted OpenCore and when starting the OCLP app it just prints out what has been booted. Have you installed OCLP before?
Does not matter, the error message indicates you have already booted OpenCore and when starting the OCLP app it just prints out what has been booted. Have you installed OCLP before?
I have not. I have read every forum entry on MacRumors related to such, and have read (twice) information and data that covers its installation, from the source.
Would you Kindly tell me where the config.plist is located for the action you mentioned here: "-no_compat_check to the boot-args in the config.plist."
I have not. I have read every forum entry on MacRumors related to such, and have read (twice) information and data that covers its installation, from the source.
Would you Kindly tell me where the config.plist is located for the action you mentioned here: "-no_compat_check to the boot-args in the config.plist."
I already told you where to gather the in depth information you need to do manual changes. Guess you will be able to find the thread knowing its name? Just read my few posts, again.
You should double check who has/had access to you MacPro and who installed the High Sierra macOS before you got the system. There was an OpenCore installation (most likely hidden on the EFI partition of your disk) on this system according to the OCLP error message and the MacPro booted it.