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.
Luigi222 said:
Well, what a disappointment... Was so excited to read this different approach on 0.3.2.

But after making a fresh install on my MacBook Pro 17 from 2010, nothing has changed, still graphics glitches everywhere, no smooth scrolling on basic apps...

You can go into accessibility and turn transparency off, helps a little with menu glitches, but where is the fun in that?

It's a deal breaker for me.

My advise for people with machines from 2008, 2009, 2010 and 2011, stick with macOS Catalina, I will.
It's just way to glitchy for everyday use in my opinion. It's not a pleasant experience.
Click to expand...
I bought a cheap Macbook Pro 15" 2015. So sad to say goodbye to my beloved Macbook Pro 17" 2011. But i got to the same conclusion as you. :(
 
Luigi222 said:
Well, what a disappointment... Was so excited to read this different approach on 0.3.2.

But after making a fresh install on my MacBook Pro 17 from 2010, nothing has changed, still graphics glitches everywhere, no smooth scrolling on basic apps...

You can go into accessibility and turn transparency off, helps a little with menu glitches, but where is the fun in that?

It's a deal breaker for me.

My advise for people with machines from 2008, 2009, 2010 and 2011, stick with macOS Catalina, I will.
It's just way to glitchy for everyday use in my opinion. It's not a pleasant experience.
Click to expand...
2009 Mini3,1 to macOS 12.1 OTA atop 12.b6 via OCLP_031R>033N, install smooth, unattended, no ghosts, browsers all accounted for. At 48 hrs. on, noticed two memory leaks are gone. https://eclecticlight.co/2021/12/13...nd-security-updates-for-big-sur-and-catalina/ And confirmed.

more 12.1.jpg
works on mine.jpg
 
Last edited:
  • Like
Reactions: Pri-est and hvds
adamrc said:
I updated my late 2012 iMac and then updated OCLP to 0.3.2. I then ran the post install patch. All seems to be running smooth and well. The only issue I currently have is I receive the following message every time I reboot and log in to my account. Any ideas on how to resolve this? I can click Cancel or Open and everything loads just fine.View attachment 1928322
Click to expand...
The fix to this issue I had was to download OxyX and run the default maintenance. Found from this thread: https://forums.macrumors.com/thread...f-a-problem-never-stops.2284418/post-30630563
 
peekpt said:
Upgrade Report

iMac 12,2 (2011) with modded Nvidia K610 GPU Upgraded from BigSur to 12.1 Monterey.
  • Full external disk Install with TUI offline.
    • development options - activated modded GPU to Nvidia
  • Some hangs occur on last boot to cleanup but it boot
  • First boot no Wifi and no GPU acceleration.
  • Installed new EFI to Local Disk from 0.32 (config and build again)
  • Post Install for Wifi and Nvidia patches and reboot
✅ Everything seems fine


To free up space from Time Machine:
tmutil listlocalsnapshots /
tmutil deletelocalsnapshots /
Click to expand...
Sorry but correct command for Time Machine is :

tmutil listlocalsnapshotdates

Cheers ;-)
 
At the end i could install OCLP 0.3.2 Monterey in my Macbook pro 17" 2011. Same glitches. Thanks anyway, people from OCLP. You ROCK!
 
tchek said:
Cheers and long life to OCLP !

View attachment 1928229
Successful 12.1 (21C52) update with software update (12 GB) on a Mac mini late 2012 2.3 GHz Intel Core i7 quad core. On this machine I of course used Chapter "3. Post-Install Volume Patch" to run my second screen, graphics acceleration and all the rest. OCLP version 0.3.1
Click to expand...
Does Airplay to Mac still work on Monterey 12.1 with OCLP 0.3.1?

I read something about a fix for that in 0.3.2 but I’m a bit hesitant to update OCLP right now with all of the unfamiliar changes
 
As Apple slowly but surely obsoletes all Macs containing any intel-specific code to get everyone to buy new Mx Apple products, eventually all unsupported Macs will suffer, even those cobbled to replicate currently supported machines. OCLP can only do so much. @ASentientBot has performed wonders with the NVIDIA graphics patch set but for some worthy of complaint. Running the most primitive of unsupported Macs has taught lowering expectations and using what is given greatly reduces stress. END PATRONIZING ;)
 
  • Like
Reactions: 0134168, MacRumors3590, makra and 3 others
K two said:
As Apple slowly but surely obsoletes all Macs containing any intel-specific code to get everyone to buy new Mx Apple products, eventually all unsupported Macs will suffer, even those cobbled to replicate currently supported machines. OCLP can only do so much. @ASentientBot has performed wonders with the NVIDIA graphics patch set but for some worthy of complaint. Running the most primitive of unsupported Macs has taught lowering expectations and using what is given greatly reduces stress. END PATRONIZING ;)
Click to expand...
I hope that wasn't aimed at me, all I did was ask if Airplay to Mac still works in 0.3.1 on Monterey 12.1— and I just confirmed for myself that it doesn't. So I'll be cautiously updating OCLP.
 
  • Like
Reactions: K two
Lucky736 said:
Changed spoof settings, it changed them back after reboot. Tried twice along with reinstalling 0.3.2 after changes.

Reverted to 0.3.1 and the installer is working without a hitch. Looks like maybe a change in the latest 0.3.2 from yesterday has a hiccup on it.
Click to expand...
Meanwhile installed 12.1 on MBP5,2, to an external SSD.
Using a USB installer made with createinstallmedia, booted it with OCLP 0.3.2.
It properly showed the desired target disk. This had 12.1b4 on it, which was installed OTA when it became available while booted from 0.3.1 (when booting with a 0.3.2 nightly, the update was not shown), and post-install patched with a recent 0.3.2 nightly.
Used 0.3.2 for the reboots during installation and for booting the installed 12.1. Also used 0.3.2 to do the post-install patches. Running fine.
Remains to be seen if a future macOS version will be visible for OTA updating. Anyway whenever available, I will make a USB installer as this gives a better defined starting condition, and a better fallback in case installation fails.
As for nvram, I've reset it a few days ago. The contents visible with nvram -p looks fine to me.
 

Attachments

  • Bildschirmfoto 2021-12-14 um 18.47.55.png
    Bildschirmfoto 2021-12-14 um 18.47.55.png
    71.2 KB · Views: 70
  • thissys.png
    thissys.png
    51.4 KB · Views: 72
  • Like
Reactions: Hackintosh HD and K two
hvds said:
Meanwhile installed 12.1 on MBP5,2, to an external SSD.
Using a USB installer made with createinstallmedia, booted it with OCLP 0.3.2.
It properly showed the desired target disk. This had 12.1b4 on it, which was installed OTA when it became available while booted from 0.3.1 (when booting with a 0.3.2 nightly, the update was not shown), and post-install patched with a recent 0.3.2 nightly.
Used 0.3.2 for the reboots during installation and for booting the installed 12.1. Also used 0.3.2 to do the post-install patches. Running fine.
Remains to be seen if a future macOS version will be visible for OTA updating. Anyway whenever available, I will make a USB installer as this gives a better defined starting condition, and a better fallback in case installation fails.
As for nvram, I've reset it a few days ago. The contents visible with nvram -p looks fine to me.
Click to expand...
The current nightly is 033, works fine. No new issues. :cool:

033N.jpg
Suspect non-spoofed Macs may require OCLP_031>032/033 two-step to perform OTA updates?
 
Last edited:
Reporting in, I successfully upgraded OCLP to 0.3.2 however, now TRIM is permanently enabled for some reason and even sudo trimforce disable does not work to disable it. This means I'm back to 4+ minute long boot times. If I cannot find some solution, I'll be reverting back to 0.3.1
 
  • Like
Reactions: K two
5tracks said:
Reporting in, I successfully upgraded OCLP to 0.3.2 however, now TRIM is permanently enabled for some reason and even sudo trimforce disable does not work to disable it. This means I'm back to 4+ minute long boot times. If I cannot find some solution, I'll be reverting back to 0.3.1
Click to expand...
Boot into any macOS Recovery and disable SIP csrutil false there, then run csrutil status to confirm. TRIM can now be disabled. ;)

Additional - Look at #2 - Security and #3 - Spoofing in OCLP?
 
Last edited:
K two said:
Boot into macOS Recovery and disable there then run csrutil status to confirm.
Click to expand...
Thanks, however I already reverted to 0.3.1
after only a few minutes on 0.3.2 I started to notice general system sluggishness, and spotty Wifi that would hang and stall randomly.
As soon as I went back to 0.3.1 everything behaved perfectly again.

Clearly something about 0.3.2 isn't playing well with my system.
Since the only thing missing on 0.3.1 is AirPlay to Mac (on 12.1) , I can happily live without that until a solution is found.

Edit: I also tried with the new 0.3.3, and experience the same issues as 0.3.2
 
Last edited:
  • Like
Reactions: K two
I'm unable to do a clean install of 12.1 onto a MacBookPro11,3 with either oclp 0.3.2 or 0.3.3.

I'm getting a hang at "About 20 minutes remaining." (I've waited about an hour with it sitting there after booting with oclp 0.3.2, with nothing happening.)

Any ideas?

My next step will be to try doing a clean install of 12.0.1.
 
ivofonseca said:
Hello. I have a MacBookPro11,3 working flawlessly with Monterey. I tried to update yesterday to 12.1 trough System Update (a big 11Gb download, as expected), and after reboot and install of the post-update patches, my system says that I'm still at 12.0.1, and System Update says that there is no new update ?. Anyone knows what is happening? Thanks.
Click to expand...
I don't want to be boring or anything like that, but has what I describe here ever happened to anyone else? Does anyone know what happened or how to solve it? Thank you.
 
K two said:
The current nightly is 033, works fine. No new issues. :cool:

View attachment 1928485 Suspect non-spoofed Macs may require OCLP_031>032/033 two-step to perform OTA updates?
Click to expand...
So far, yes.
It seems that Apple has a bug/feature in the handling of virtual machines, so spoofing rather than VM is needed to hide the fact that a machine is unsupported.
Setting some (minimal) spoofing in 0.3.2/0.3.3 should also be fine, instead of 0.3.1.

Edit: just to confirm: put an OCLP 0.3.2 with minimal spoofing on a USB stick. Booting 11.6.2 (20G311) with this, and it sees the 20G313; while it doesn‘t see it with non-spoofing default 0.3.2.
To enable the spoofing in TUI: 5 Patcher settings -> 3 SMBIOS settings -> 1 set SMBIOS spoof level -> 1 minimal.

Now updating BS on internal SSD to 20G313 and default 0.3.2, and will also update MR on the internal SSD to 12.1 (from full installer).

OCLP 0.3.2 looks very mature.
 
Last edited:
  • Like
Reactions: K two
hvds said:
So far, yes.
It seems that Apple has a bug/feature in the handling of virtual machines, so spoofing rather than VM is needed to hide the fact that a machine is unsupported.
Setting some (minimal) spoofing in 0.3.2/0.3.3 should also be fine, instead of 0.3.1.

Edit: just to confirm: put an OCLP 0.3.2 with minimal spoofing on a USB stick. Booting 11.6.2 (20G311) with this, and it sees the 20G313; while it doesn‘t see it with non-spoofing default 0.3.2.
To enable the spoofing in TUI: 5 Patcher settings -> 3 SMBIOS settings -> 1 set SMBIOS spoof level -> 1 minimal.

Now updating BS on internal SSD to 20G313 and default 0.3.2, and will also update MR on the internal SSD to 12.1 (from full installer).

OCLP 0.3.2 looks very mature.
Click to expand...
Looks like the 12/14 2PM Nightly may be the fix? Testing now. ?
 
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