Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 12 Monterey on Unsupported Macs Thread
- Thread starter khronokernel
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Should I install this to upgrade to Monterey or continue to use OCLP 0.1.2 on my iMac 13.2? Thank you.
Hi @iMac-Oldschool
Yes mainly replaced this line:
Code:
for x in "Install macOS Big Sur" "Install macOS Big Sur Beta" "Install macOS Beta"by it:
Code:
for x in "Install macOS Monterey" "Install macOS Monterey Beta" "Install macOS Beta" "Install macOS 12 Beta"But also of course replaced in all places "Big Sur" by "Monterey" including in error messages (even if this is not essential and does not interfere with the operation)
here is the full modified script:
EDIT: I forgot to specify that this same line is to be modified in the scripts "install-setvars.sh" and "unpatch.sh"
Last edited:
Hi, I installed Monterey Beta 1 on my iMac 13.2 Late 2012 with 802.11ac Wi-Fi card without any problem, I used OCLP (Version 0.1.7). Thanks and greetings!
Can you please just put simple steps of how you used the patcher and installation method. I wanna try on my 2014 MacBook. thanks
Hi, as I already had the latest Big Sur beta with OCLP installed, what I did was to remove the developer profile and installed a new one to be able to install the Monterey Beta from software update.
I also downloaded the Nightly OpenCore-Patcher.app version from Post 1 and then ran it by compiling the files for my iMac model.
I then went to software update and installed the new Beta normally, the process took about 30 minutes.
Interesting crash behaviour of macOS 12 on Mac Pro 3,1 (0.1.7 patcher does not help here):
Whenever a (previously working, usable) WiFi card is connected to the internal miniPCIe slot, boot process crashes at a very very early time (never seen this before). Last verbose output reporting number of CPUs and cores. Then the hard crash with reset.
Have tried with three different Atheros cards (one of them proven to work up to Big Sur).
Whenever a (previously working, usable) WiFi card is connected to the internal miniPCIe slot, boot process crashes at a very very early time (never seen this before). Last verbose output reporting number of CPUs and cores. Then the hard crash with reset.
Have tried with three different Atheros cards (one of them proven to work up to Big Sur).
2nd glitch: BT module works, keyboard and magic trackpad (II) are recognized, but trackpad show up with mouse behaviour (no multi-touch gestures, laggy).
Any ideas here?
Any ideas here?
Hello everyone, I made some attempts to install and boot Monterey either on unsupported non metal and unsupported metal Mac, I'd share my insights.
All the known installing method are nearly identical to Big Sur, some main examples: @ASentientBot HaxLib.dylib , OpenCore, OCLP
in my case to install Monterey I used a modified BigSurBaseSystemfix making a new patched Monterey BaseSystem, through the ASentientBot HaxLib, IOHIDFamily and patched boot.efi
I used MacBook7,1 and installation completed correctly on external USB SSD with less efforts than I had on Big Sur, then using my previous BigSurBaseSystemfix (based on a patched hybrid BigSur beta3 beta9 BaseSystem), through "BigSurFixes delete snapshot" I still can even delete the "com.apple.os.update" of Monterey resulting in a working "mount -uw /" (hence I removed telemetry plugin for C2D kp and PlatformSupport.plist from Preboot)
Now the weird part, while installation completed smoothly, on MacBook7,1 the welcome screen worked even if is very slow, after create the admin user there is a kind of loginwindow or skylight crash so can't log to desktop, let's say only the "setup assistant" graphical environment showed correctly, I'd attempt some AGC kext and plugins replacements.
I also noticed that apple changed and renamed the Wifi kext in this way:
IO80211Family.kext in IO80211FamilyLegacy.kext
IO80211FamilyV2.kext in IO80211Family.kext
I tried to replace some patched Wifi kext but kmutil refuses to rebuild kc correctly, because they rely on many dependency symbols on AppleBCMWLAN* and IOSkywalkFamily.kext so eventually an OpenCore kc patch would fix the AirPort4360 and 4331 drivers while keeping the stock Monterey Wifi driver.
About the minimum unsupported Metal Mac that are Ivy bridge, as many already wrote what surely works without efforts (just with -no_compat_check) on unsupported Metal acceleration OOB is any Nvidia Kepler based GPU because those drivers are present on stock monterey kernel collection (and its Extensions folder).
Weirdly if manually installed the IntelHD4000 Big Sur drivers currently only works on a dualGPUs Nvidia Kepler GPU, while on a single GPU IntelHD4000 produces a similar loginwindow crash as non Metal (non framebuffer patched) GPUs .
On dualGPUs IntelHD4000 IGPU Nvidia Kepler dGPU the Big Sur AppleIntelGraphicsHD4000* kext and its AppleIntelFramebufferCapri provide the Brightness control, GPU power management and switching, Ethernet also works without kext patching.
The picture is the same external USB SSD installed Monterey plugged to a MacBookPro9,1 , booting currently without OpenCore.
All the known installing method are nearly identical to Big Sur, some main examples: @ASentientBot HaxLib.dylib , OpenCore, OCLP
in my case to install Monterey I used a modified BigSurBaseSystemfix making a new patched Monterey BaseSystem, through the ASentientBot HaxLib, IOHIDFamily and patched boot.efi
I used MacBook7,1 and installation completed correctly on external USB SSD with less efforts than I had on Big Sur, then using my previous BigSurBaseSystemfix (based on a patched hybrid BigSur beta3 beta9 BaseSystem), through "BigSurFixes delete snapshot" I still can even delete the "com.apple.os.update" of Monterey resulting in a working "mount -uw /" (hence I removed telemetry plugin for C2D kp and PlatformSupport.plist from Preboot)
Now the weird part, while installation completed smoothly, on MacBook7,1 the welcome screen worked even if is very slow, after create the admin user there is a kind of loginwindow or skylight crash so can't log to desktop, let's say only the "setup assistant" graphical environment showed correctly, I'd attempt some AGC kext and plugins replacements.
I also noticed that apple changed and renamed the Wifi kext in this way:
IO80211Family.kext in IO80211FamilyLegacy.kext
IO80211FamilyV2.kext in IO80211Family.kext
I tried to replace some patched Wifi kext but kmutil refuses to rebuild kc correctly, because they rely on many dependency symbols on AppleBCMWLAN* and IOSkywalkFamily.kext so eventually an OpenCore kc patch would fix the AirPort4360 and 4331 drivers while keeping the stock Monterey Wifi driver.
About the minimum unsupported Metal Mac that are Ivy bridge, as many already wrote what surely works without efforts (just with -no_compat_check) on unsupported Metal acceleration OOB is any Nvidia Kepler based GPU because those drivers are present on stock monterey kernel collection (and its Extensions folder).
Weirdly if manually installed the IntelHD4000 Big Sur drivers currently only works on a dualGPUs Nvidia Kepler GPU, while on a single GPU IntelHD4000 produces a similar loginwindow crash as non Metal (non framebuffer patched) GPUs .
On dualGPUs IntelHD4000 IGPU Nvidia Kepler dGPU the Big Sur AppleIntelGraphicsHD4000* kext and its AppleIntelFramebufferCapri provide the Brightness control, GPU power management and switching, Ethernet also works without kext patching.
The picture is the same external USB SSD installed Monterey plugged to a MacBookPro9,1 , booting currently without OpenCore.
Attachments
I'm trying to install Monterey on a 15-inch mid 2014 MBP. I tried using both OCLP and a modified version of Big Sur micropatcher. It boots to the installer but I keep getting "PKDownloadError error 15" during installation. Any ideas?
Thank you.
macOS 12 Monterey installed successfully and without any issues. and runs smoothly on my Late 2014 MacBook Pro
Attachments
I finally made it work on my iMac 13,2.
First created the bootable usb using Micropatcher, installed everything normal on my iMac and after installed I ran the OCLP efi and it worked.
Wifi wasn't working with Micropatcher but everything works fine after booting with OCLP.
Someone else posted this up before - but seems relevant: https://eclecticlight.co/2021/06/08/which-macs-will-run-macos-12-monterey-the-answer-isnt-simple/ - i.e. are you faking your Mac to one which should support these features? (Realise you may well be aware and doing this already, but just in case!)
I've tried multiple methods and haven't been able to install it as a Virtual Machine. So I will have to look at doing it on real hardware.
Bonjour,
Full installation via OpenCore, I really appreciate having an unpatched system, vanilla as they say for hackintoshes?
You definitely _can_ run these OSes in a virtual machine, in fact OC 0.7.0 added initial beta support for running macOS in Hyper-V on Windows - which I think you can't get anywhere else. However, I haven't ever tried setting this up, so maybe someone who has (I guess you're trying to run your VM under macOS host OS?) might be able to chip in with more info.
It installed fine on a new APFS container instead of a new volume. macOS 12 runs great on my 2014 MBP.
That's my problem! I can't start the patcher. With 0.1.6 and also with 0.1.7 it says "only for macOS 11" und i can only quit.
To be more specific, how can one know which model is faked to? For example, in my case?
Hi,
Installed beta 1 developper without problem on my MBP 9,1. There is an annoying bug : when the Mac goes to sleep, it is impossible to wake it again. I have to force power button to restart the machine.
Also, I wonder, no kext for HD 4000 integrated card, does it mean it is never used ?
Installed beta 1 developper without problem on my MBP 9,1. There is an annoying bug : when the Mac goes to sleep, it is impossible to wake it again. I have to force power button to restart the machine.
Also, I wonder, no kext for HD 4000 integrated card, does it mean it is never used ?
