Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

khronokernel

macrumors 6502
Original poster
Sep 30, 2020
278
1,425
Alberta, Canada
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 Monterey 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 (and yet it moves, see i.e. this post)
  • 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
  • Legacy Bluetooth Support
    • BRCM2046 and BRCM2070 Bluetooth modules have been dropped from Monterey. More in-depth explantation here
      • Models included:
        • iMac12,x and older
        • Macmini4,1 and older
        • MacBook7,1 and older
        • MacBookAir4,x and older
        • MacBookPro8,x and older
        • MacPro5,1 and older
  • Legacy Wireless Cards
    • 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 those firmware upgrades are bundled into the macOS Big Sur updates, exclusively.

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.

Another method to update the firmware has been described on this site. It requires some system admin technical skills.

New OCLP target new macOS versions. For example releases from 0.6.2 onwards in particular made some severe changes for some Macs (disabled AMFI, again) which will disable functionality on Big Sur and Monterey just to allow the use of the latest Ventura releases. Especially Kepler and IvyBridge 2012 Macs are hit by this.

There is absolutely no use and no need to install and use this new OCLP releases unless you have a double boot installation with Ventura or the change log explicitly mentions your Mac model and a special development only available with new OCLP version, e.g the support for iMac9,1 with metal AMD MXM cards or if you are using a non metal pre 2012 Mac.

The best version for AMD metal will be 0.4.11, the best version for Kepler metal 0.5.0, users of non metal (if there are still brave ones left) can used the latest and greatest.

Bad news:

TM (time machine) restoring and MA (migration assistant) is broken on root patched systems. Do not try, system will only arrive in an unbootable and uncorrectable state after hours of restoring or transferring data.

There are two ways around this:

1. Use the OCLP USB installer and install Sonoma on top of your current (supported or unsupported) macOS. This will retain your current user data. But create a final TM backup before leaving your supported macOS installation, it will be the only return ticket.

2. Simply use MA or TM before system has been root patched by the OCLP app. This is sometimes difficult to achieve when auto-patching ran before you even reached the login page. You can prevent auto-patching by creating an USB installer manually (createinstallmedia and install OpenCore manually). You can revert patches, too.

After many requests, we've finally opened up a way for people to make monetary contributions to OCLP's development, using Open Collective: https://opencollective.com/opencore-legacy-patcher If you appreciate what we do, please considering donating! Your support will help us purchase needed hardware to improve the project. Thanks!


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:
Code:
system_profiler SPHardwareDataType | grep 'Model Identifier'

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.

VersionBuildLinkMirror
12.0 Beta 121A5248pInstallAssistant (Direct)InstallAssistant (archive.org)
12.0 Beta 221A5268hInstallAssistant (Direct)InstallAssistant (archive.org)
12.0 Beta 321A5284eInstallAssistant (Direct)InstallAssistant (archive.org)
12.0 Beta 421A5294gInstallAssistant (Direct)InstallAssistant (archive.org)
12.0 Beta 521A5340gInstallAssistant (Direct)InstallAssistant (archive.org)
12.0 Beta 621A5506jInstallAssistant (Direct)InstallAssistant (archive.org)
12.0 Beta 721A5522hInstallAssistant (Direct)InstallAssistant (archive.org)
12.0 Beta 821A5534dInstallAssistant (Direct)InstallAssistant (archive.org)
12.0 Beta 921A5543bInstallAssistant (Direct)InstallAssistant (archive.org)
12.0 Beta 1021A5552aInstallAssistant (Direct)InstallAssistant (archive.org)
12.0 (M1 Pro/Max)21A344N/AN/A
12.0.1 RC 121A558N/AN/A
12.0.1 Release21A559InstallAssistant (Direct)InstallAssistant (archive.org)
12.1 Beta 121C5021hInstallAssistant (Direct)InstallAssistant (archive.org)
12.1 Beta 221C5031dInstallAssistant (Direct)InstallAssistant (archive.org)
12.1 Beta 321C5039bInstallAssistant (Direct)InstallAssistant (archive.org)
12.1 Beta 421C5045aInstallAssistant (Direct)InstallAssistant (archive.org)
12.1 RC 121C51N/AN/A
12.1 Release21C52InstallAssistant (Direct)InstallAssistant (archive.org)
12.2 Beta 121D5025fInstallAssistant (Direct)InstallAssistant (archive.org)
12.2 Beta 221D5039dInstallAssistant (Direct)InstallAssistant (archive.org)
12.2 RC21D48N/AN/A
12.2 Release21D49InstallAssistant (Direct)InstallAssistant (archive.org)
12.2.1 Release21D62
12.3 Beta 121E5196iUniversalMacAssistant (Dev Paywall)UniversalMacAssistant (archive.org)
12.3 Beta 221E5206eInstallAssistant (Direct)InstallAssistant (archive.org)
12.3 Beta 321E5212fInstallAssistant (Direct)InstallAssistant (archive.org)
12.3 Beta 421E5222aInstallAssistant (Direct)InstallAssistant (archive.org)
12.3 Beta 521E5227aInstallAssistant (Direct)InstallAssistant (archive.org)
12.3 Release21E230InstallAssistant (Direct)InstallAssistant (archive.org)
12.3.121E258InstallAssistant (Direct)
12.4 Beta 221F5058eInstallAssistant (Direct)
Alternative page:Full list of Monterey Installers(Mr. Macintosh)

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:

  1. 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.
    • For easy troubleshooting we recommend joining the OpenCore Patcher Paradise Discord.
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: 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.

Q: Which is the best OCLP version to usenwith Monterey?
A:
The last Monterey version was 0.4.11 - all following versions target Ventura only with a few exceptions. In general read the OCLP change log carefully, new versions may have unexpected side effects on Monterey installations when changing general settings (like SecureBootModel, AMFI, SIP). Macs with Kepler graphics should use OCLP 0.5.0, non metal Macs (pre 2012 systems) should use the latest version since non-metal updates are included into the development stream independently of the most recent macOS version.

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.
 
Last edited:
Apparently the compatibility is the same as Big Sur according to Techradar
  • 12-inch MacBook (2015 and later)
  • MacBook Air (2013 and later)
  • MacBook Air M1 (Late 2020 and later)
  • MacBook Pro (Late 2013 and later)
  • MacBook Pro M1 (Late 2020 and later)
  • Mac mini (2014 and later)
  • Mac mini (Late 2020 and later)
  • iMac (2014 and later)
  • iMac M1 (2021 and later)
  • iMac Pro (all models)
  • Mac Pro (2013 and later)
Nvm they lied
 
Supported machines:
unknown.png
 
Apparently the compatibility is the same as Big Sur according to Techradar
  • 12-inch MacBook (2015 and later)
  • MacBook Air (2013 and later)
  • MacBook Air M1 (Late 2020 and later)
  • MacBook Pro (Late 2013 and later)
  • MacBook Pro M1 (Late 2020 and later)
  • Mac mini (2014 and later)
  • Mac mini (Late 2020 and later)
  • iMac (2014 and later)
  • iMac M1 (2021 and later)
  • iMac Pro (all models)
  • Mac Pro (2013 and later)
 

Attachments

  • 62407FC3-0EAC-49D6-ABBC-64B7C71E21CE.png
    62407FC3-0EAC-49D6-ABBC-64B7C71E21CE.png
    1.5 MB · Views: 1,696
What about 2013/2014 MacBooks Airs and Pros with Intel Integrated graphics?
No MBAs or MBPs before 2015, think as generous as they have been with iOS and iPad OS they've been quite harsh with Monterey, especially given Big Sur dropped a lot of macs last year too. OTOH I can see they probably want to move forward quite quickly due to the complexity of the situation?
 
No MBAs or MBPs before 2015, think as generous as they have been with iOS and iPad OS they've been quite harsh with Monterey, especially given Big Sur dropped a lot of macs last year too. OTOH I can see they probably want to move forward quite quickly due to the complexity of the situation?

yeah they want to drop intel macs ASAP. We have seen this before with PPC->Intel transition
 
Regarding OS support, here are supported Board IDs:

Code:
<string>Mac-06F11F11946D27C5</string>

<string>Mac-06F11FD93F0323C5</string>

<string>Mac-0CFF9C7C2B63DF8D</string>

<string>Mac-112818653D3AABFC</string>

<string>Mac-112B0A653D3AAB9C</string>

<string>Mac-1E7E29AD0135F9BC</string>

<string>Mac-226CB3C6A851A671</string>

<string>Mac-27AD2F918AE68F61</string>

<string>Mac-35C5E08120C7EEAF</string>

<string>Mac-473D31EABEB93F9B</string>

<string>Mac-4B682C642B45593E</string>

<string>Mac-50619A408DB004DA</string>

<string>Mac-53FDB3D8DB8CA971</string>

<string>Mac-551B86E5744E2388</string>

<string>Mac-5A49A77366F81C72</string>

<string>Mac-5F9802EFE386AA28</string>

<string>Mac-63001698E7A34814</string>

<string>Mac-65CE76090165799A</string>

<string>Mac-66E35819EE2D0D05</string>

<string>Mac-747B1AEFF11738BE</string>

<string>Mac-77F17D7DA9285301</string>

<string>Mac-7BA5B2D9E42DDD94</string>

<string>Mac-7BA5B2DFE22DDD8C</string>

<string>Mac-827FAC58A8FDFA22</string>

<string>Mac-827FB448E656EC26</string>

<string>Mac-90BE64C3CB5A9AEB</string>

<string>Mac-937A206F2EE63C01</string>

<string>Mac-937CB26E2E02BB01</string>

<string>Mac-9394BDF4BF862EE7</string>

<string>Mac-9AE82516C7C6B903</string>

<string>Mac-9F18E312C5C2BF0B</string>

<string>Mac-A369DDC4E67F1C45</string>

<string>Mac-A5C67F76ED83108C</string>

<string>Mac-A61BADE1FDAD7B05</string>

<string>Mac-AA95B1DDAB278B95</string>

<string>Mac-AF89B6D9451A490B</string>

<string>Mac-B4831CEBD52A0C4C</string>

<string>Mac-B809C3757DA9BB8D</string>

<string>Mac-BE088AF8C5EB4FA2</string>

<string>Mac-C6F71043CEAA02A6</string>

<string>Mac-CAD6701F7CEA0921</string>

<string>Mac-CF21D135A7D34AA6</string>

<string>Mac-CFF7D910A743CAAF</string>

<string>Mac-DB15BD556843C820</string>

<string>Mac-E1008331FDC96864</string>

<string>Mac-E43C1C25D4880AD6</string>

<string>Mac-E7203C0F68AA0004</string>

<string>Mac-EE2EBD4B90B839A8</string>

<string>Mac-F60DEB81FF30ACF6</string>

<string>Mac-FFE5EF870D7BA81A</string>
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.