Sidebar Sidebar
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

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.
moosethegoose2213 said:
Is that clover? Why are you using that trash? The only thing that it can do that OpenCore can't is brick computers.
Click to expand...
sorry but i'm part of the old school

I always used Clover and I continue

I know how to use OpenCore without problems but the bootloader that causes me the most problems between multiboot and NVRAM is OC

later I'm not here to talk about bootloader and even less to see which is or is not better.... I close my speech on that!

I'm here to try using Nvidia GT320M with QE/CI on MonteRey

do you want an advice ? thankfully there are many people with different opinions and many types of solutions are built!
 
OKonnel said:
Mistake...;) My iMac with invidia GTX 780M 4GB, in fact, is well supported perfectly, by default, up to macOS Catalina :)
The nVidia GTX 780M graphics card is original and I chosed in the purchase OTA directly from the Apple Store site. It represents the best of graphic cards for iMac 27'' (Late 2013) equipped with i7 CPU with maximum clock.
However the speech also applies to the others iMac14,2 equipped with other less performing nVidia; they are all supported up to Catalina.

The beauty (or the ugly if we think at one schedulated obsolescence by Apple...) is that my iMac has never gone so well, how it goes now with Monterey! I just tried a very heavy 2K video, downloaded from YouTube and runs in QuickTime without latch, even if I move the window quickly!!!...

We think of all those who, like me, were thinking about buying a new iMac after seeing that with Big Sur their Macs had problems. On Internet I found that even some Macs supported by Big Sur had unresolved issues with Photo Booth, as I had with my IMAC not supported! And instead everything works with Monterey now!... I am convinced that even the Preview defects with the .HEIC files depend on a poor Apple programming and not from my hardware ..
Click to expand...
Please make a step-by-step instruction for installing macOS 12 Monterey on your iMac 2013! I have a similar one ... but after installation it starts, and after the first reboot it does not load into the system! Prohibitory sign appears
 
Last edited:
  • Like
Reactions: OKonnel
maxevens said:
Here is my config:

And as you can see there is no option for that what you mentioned on your post.
Click to expand...
If you refer to my post then options I meant are 1 and 2. Why be so literal?
Have you installed Monterey as I can see of your picture?
 
Tockman said:
If you refer to my post then options I meant are 1 and 2. Why be so literal?
Have you installed Monterey as I can see of your picture?
Click to expand...
Tockman said:
Sure, I can.
1. Start OCLP 0.1.7.
2. Choose "Create OpenCore configuration" option.
3. Choose "Copy EFI on Internal disk".
4. Restart your Mac.
5. Start "Software Update" in System Preferences.
6. Choose "Install MacOS 12 beta".
7. Profit ;)

By the way, what's your model and configuration? It would be more convenient to have it in your signature.
Click to expand...
This model is supported





1. Build OpenCore


2. Install OpenCore to USB/internal drive


3. Post-Install Volume Patch


4. Change Model


5. Patcher Settings


6. Credits


Q. Quit

you can do it in order???
 
jackluke said:
Here is another test on MacBookPro6,2 dualnonmetalGPUs in booting Monterey, without acceleration of course and without Wifi , this is made possible again thanks to @ASentientBot who found the workaround to set "auto login", because the multiuser loginwindow crash without Metal, but applying this is not so simple because you need to complete the apple setup assistant that is very slow, then after the login loop, remove the .AppleSetupDone then reboot to setup assistant from there using a keyboard shortcut key (discussed on discord) to change the login options (setting a blank password won't work properly), more easier if you can boot from a Metal Mac and set the admin user with "auto login".

I am trying to make some LaunchAgents plist to automatically open Accounts.prefpane on setup but it's not easy.

For network ethernet fix using the Catalina AppleBCM5701Ethernet.kext worked as BigSur.

Third party USB Bluetooth CSR still work with stock Monterey drivers.

HighSierra AppleHDA still fix sound and mic (the new siri works), generic IntelHDGraphics kext (without GLdriver) and ASentientBot Nvidia ResmanTesla fixes (without GLDriver) also fixed framebuffer, brightness control and dualGPU switching.
Click to expand...

khronokernel said:
With some impressive finding from @jackluke, we were able to get HD 4000 acceleration in macOS Monterey on our Discord with EduCovas! We will be pushing these changes to OpenCore Legacy Patcher shortly:

View attachment 1791996
Click to expand...
Wow...WOW.


This is amazing, so there was/is hope for the HD4000 Graphics.
 
Would a MacBookPro9,2 be supported via the patcher? I was able to patch Big Sur and it runs great. I hope Montery is supported as well.
 
Hello everyone. installed the beta version on my old macbook:apple::):)
 

Attachments

  • 7F491736-B0FD-4731-AC6A-C5E226F65B24.jpeg
    7F491736-B0FD-4731-AC6A-C5E226F65B24.jpeg
    367.5 KB · Views: 182
  • Like
Reactions: Bumblebee1984 and Tockman
Did more tests with HD 4000, we can comfortably say that HD 4000 support is doing great on my personal MacBookPro9,2. Will note, Delta updates will unfortunately break the moment you root patch the system. Additionally FileVault and SIP will be unsupported however all other features should work wonderfully like WPA Network support, OTA updates, etc

OpenCore Legacy Patcher has been updated to set these patches however we recommend users wait till official release of v0.1.7 to mess with out patch set.

Additionally while we will not provide support for non-OpenCore Legacy Patcher setups, our root volume patch have no requirements of OCLP and therefore could be run on either a Micropatched Mac or a Hackintosh. Note you must ensure SIP is properly disabled. For HD 4000 patching in Monterey, we check the follow csr-active-config (SIP) bits are flipped:

Code: 
CSR_ALLOW_UNTRUSTED_KEXTS            - 0x1
CSR_ALLOW_UNRESTRICTED_FS            - 0x2
CSR_ALLOW_UNAPPROVED_KEXTS           - 0x200
CSR_ALLOW_EXECUTABLE_POLICY_OVERRIDE - 0x400
CSR_ALLOW_UNAUTHENTICATED_ROOT       - 0x800

Screen Shot 2021-06-12 at 9.39.06 PM.png
 
  • Like
  • Love
Reactions: Bmju, Strategia, pyedog and 6 others
khronokernel said:
Did more tests with HD 4000, we can comfortably say that HD 4000 support is doing great on my personal MacBookPro9,2. Will note, Delta updates will unfortunately break the moment you root patch the system. Additionally FileVault and SIP will be unsupported however all other features should work wonderfully like WPA Network support, OTA updates, etc

OpenCore Legacy Patcher has been updated to set these patches however we recommend users wait till official release of v0.1.7 to mess with out patch set.

Additionally while we will not provide support for non-OpenCore Legacy Patcher setups, our root volume patch have no requirements of OCLP and therefore could be run on either a Micropatched Mac or a Hackintosh. Note you must ensure SIP is properly disabled. For HD 4000 patching in Monterey, we check the follow csr-active-config (SIP) bits are flipped:

Code: 
CSR_ALLOW_UNTRUSTED_KEXTS            - 0x1
CSR_ALLOW_UNRESTRICTED_FS            - 0x2
CSR_ALLOW_UNAPPROVED_KEXTS           - 0x200
CSR_ALLOW_EXECUTABLE_POLICY_OVERRIDE - 0x400
CSR_ALLOW_UNAUTHENTICATED_ROOT       - 0x800

View attachment 1792363
Click to expand...
should i wait my mid 2012 mbp is my daily driver i would like to use monterey
 
lee1302 said:
should i wait my mid 2012 mbp is my daily driver i would like to use monterey
Click to expand...
Well our patch set should be fine up till macOS 12 so long as Apple doesn't do anything radical with the graphics stack in later Monterey Builds.

However no one should ever run a developer beta on their main machine, regardless if it's unsupported or officially supported. There is a much higher chance of data lose running betas due to unfortunate oversight on the engineers' part during development.

Wait till official release in the fall, otherwise ensure all data is backed up and you have a stable OS to return to in the event of issues.
 
  • Like
  • Love
Reactions: PG7 and iMac-iPad
khronokernel said:
Well our patch set should be fine up till macOS 12 so long as Apple doesn't do anything radical with the graphics stack in later Monterey Builds.

However no one should ever run a developer beta on their main machine, regardless if it's unsupported or officially supported. There is a much higher chance of data lose running betas due to unfortunate oversight on the engineers' part during development.

Wait till official release in the fall, otherwise ensure all data is backed up and you have a stable OS to return to in the event of issues.
Click to expand...
well all files are backed up im currently on big sur with no issues
 
khronokernel said:
Did more tests with HD 4000, we can comfortably say that HD 4000 support is doing great on my personal MacBookPro9,2. Will note, Delta updates will unfortunately break the moment you root patch the system. Additionally FileVault and SIP will be unsupported however all other features should work wonderfully like WPA Network support, OTA updates, etc

OpenCore Legacy Patcher has been updated to set these patches however we recommend users wait till official release of v0.1.7 to mess with out patch set.

Additionally while we will not provide support for non-OpenCore Legacy Patcher setups, our root volume patch have no requirements of OCLP and therefore could be run on either a Micropatched Mac or a Hackintosh. Note you must ensure SIP is properly disabled. For HD 4000 patching in Monterey, we check the follow csr-active-config (SIP) bits are flipped:

Code: 
CSR_ALLOW_UNTRUSTED_KEXTS            - 0x1
CSR_ALLOW_UNRESTRICTED_FS            - 0x2
CSR_ALLOW_UNAPPROVED_KEXTS           - 0x200
CSR_ALLOW_EXECUTABLE_POLICY_OVERRIDE - 0x400
CSR_ALLOW_UNAUTHENTICATED_ROOT       - 0x800

View attachment 1792363
Click to expand...
Do you mean that, I can use it for my Micropatched Monterey? That is great!
 
hi guys! so I'm new with all this OpenCore patching and apparently i did not understand how to use it in order to update to Monterey. here is what i did:

opened OpenCore patcher 0.1.7, completed step 1, than 2, quit, restarted the machine, tried to update, nothing happened. even tried the macos 12 installer and couldn't do it.

what did i do wrong?

i am using a MacBook pro retina 13, mid 2014.

thank you in advance for helping the newbie!!! :)
 
Last edited:
khronokernel said:
Well our patch set should be fine up till macOS 12 so long as Apple doesn't do anything radical with the graphics stack in later Monterey Builds.

However no one should ever run a developer beta on their main machine, regardless if it's unsupported or officially supported. There is a much higher chance of data lose running betas due to unfortunate oversight on the engineers' part during development.

Wait till official release in the fall, otherwise ensure all data is backed up and you have a stable OS to return to in the event of issues.
Click to expand...
What about those who want to use the public beta which could be a bit more polished then the dev beta which is supposed to be released in July? I ran the public beta of Big Sur on a separate partition just in case something could go awry. Yes for a daly driver, best to wait untill the officially release.
 
  • Like
Reactions: PG7
khronokernel said:
Well our patch set should be fine up till macOS 12 so long as Apple doesn't do anything radical with the graphics stack in later Monterey Builds.

However no one should ever run a developer beta on their main machine, regardless if it's unsupported or officially supported. There is a much higher chance of data lose running betas due to unfortunate oversight on the engineers' part during development.

Wait till official release in the fall, otherwise ensure all data is backed up and you have a stable OS to return to in the event of issues.
Click to expand...
Overall this is good advise for most.

But, I have been using OS X/macOS since the 10.0b and I never had any problem with data loss.

What I did get twice is a borked Upgrade from 1 version to the other, this includes the one I did a couple of days ago (Monterey) and the one (beta) that got the new APFS file system, forgot which one that was.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back