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.
Thank you for the APFS ROM patch, which I successfully applied to my MBP4,1. on Big Sur 11.6.2

In OCLP 0.3.2 TUI OFFLINE I did the following steps:
1. Re-Built OpenCore
2. Re-Installed OpenCore to internal drive

6. Installer Creation with Monterey 12.1 on external USB, patched OpenCore to the drive's EFI

I could n o t find the RDRAND patch, I went through all settings twice.

With Verbose mode enabled, I booted into the Monterey external USB installer, after about 30mins. automatic reboot, stuck with black screen after a few lines of verbose code.
Rebooted from internal SSD, back into Big Sur 11.6.2.
Deleted the macOS Install data leftovers from System.

Where is the RDRAND patch located within OpenCore-Patcher?
What am I missing?
Hi, sorry, the nickname is SurPlus, the function it serves is RDRAND. Can be found here (see screenshot).
Also, can you take a photo of the few lines when your 2nd boot stalls?

Bildschirmfoto 2021-12-14 um 10.52.04.jpg
 
  • Like
Reactions: macinfo and hvds
Hi, sorry, the nickname is SurPlus, the function it serves is RDRAND. Can be found here (see screenshot).
Also, can you take a photo of the few lines when your 2nd boot stalls?

View attachment 1928198
Hi Larsvonhier, thanks for pointing me to this item. I saw that entry, but of course didn't fiddle with it, as each and every step or item is mission-critical.

I will do as per your suggestion and take the photo of the lines of code in verbose mode, right before upgrade process seems to get stuck in some strange idle mode.

I'll report back and hope you will find the time to look into it. that'd be rightfully appreciated

P.S.: do you suggest using OCLP v.0.3.1 or 0.3.2.?

It would heöp a great deal of understanding the process, if you could share, how Y o u were able to put Monterey onto your MBP4,1. Like I said, we have the same machines (almost).

I went from Catalina (dosdude1's patcher) to Big Sur 11.6.1 and 11.6.2 via OCLP_GUI 0.3.1, stuck for now trying to upgrade to Monterey 12.0.1 via OCLP 0.3.1 TUI, then 12.1 both OCLP 0.3.1 AND 0.3.2, all versions (TUI, TUI OFFLINE, GUI)
 
Last edited:
Right... so I've upgraded my 2011 iMac to 12.1 with OpenCore - upgrade went flawlessly...

But... my 2015 MacBook - I am having the same issues and its driving me nuts - downloads the update spends 30 mins preparing - reboots back into 12.0.1. I have tried my fix I used before but I get the struck out circle first time now so I don't know what's happening. has this been tested on a 2015 MacBook? Im really stuck with this I've tried 6 times now...

Cheers
Any update to this issue? seem to be getting the same with general release? very odd
 
Cheers and long life to OCLP !

Macmini12.1OCLP.jpeg

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

** I just repatched it with OCLP 0.3.3 and everything is ok again.
 
Last edited:
  • Like
Reactions: x-man and macinfo
Update to 21C52 OTA went smooth as butter. It took 30min ish. Patched using OCLP 0.3.2 afterwards, rebooted. Done.

Thank you!
 
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.
 
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.
Unless you upgrade the graphics card to a metal supported one, mainly for iMacs though.
 
  • Like
Reactions: macinfo
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.
I am satisfied with Big Sur, and increasingly Monterey, on my mid 2009 MBP5,2 17“.
If I understand the changes from OCLP 0.3.1 to 0.3.2 correctly it is about simplifying the software needed to install and run BS or MR on unsupported machines; not about end user experience. This depends, as before, on SkyLight and other essentials included in OCLP, like in 0.3.1.
So I didn‘t expect fun, other than the pleasure to still have an old but reliable 17“ workhorse. It doesn‘t need to look pretty anymore. If I could plug in a Metal GPU, of course I would; but that‘s not possible.
I still have a Catalina installation on an external SSD which I keep up to date. But I like BS and MR better.
A new MBP with Apple silicon? Probably, later next year.
 
OCLP 0.3.2 Dec 13 Release and a downloaded full installer of 12.1 yields a gray HD and unable to install onto this drive when attempting to update from Beta 5 to 12.1 release. Thoughts?
 
Last edited:
OCLP 0.3.2 Dec 13 Release and a downloaded full installer of 12.1 yields a gray HD and unable to install onto this drive when attempting tp update from Beta 5 to 12.1 release. Thoughts?
What reason does the installer give when you click the greyed-out HD icon?
 
Last edited:
States update cannot be installed on this computer. Very odd.
Looks like the new Virtual Machine (rather than spoofing) method doesn‘ cover your case.
If you boot the installer with 0.3.1, or make a new 0.3.2 set to do minimal spoofing (I think I saw a post on this).
Strange because yesterday I successfully installed 11.6.2 on an MBP5,2 with 0.3.2. 12.1 yet to be tried with 0.3.2.
 
Looks like the new Virtual Machine (rather than spoofing) method doesn‘ cover your case.
If you boot the installer with 0.3.1, or make a new 0.3.2 set to do minimal spoofing (I think I saw a post on this).
Strange because yesterday I successfully installed 11.6.2 on an MBP5,2 with 0.3.2. 12.1 yet to be tried with 0.3.2.
Just double checked. Spoof Level is None and Spoof Model is Default. So odd.
 
The update to Mac OS 12.1 went fine on my 2012 15" unibody MacBook Pro. But now Google Chrome doesn't work properly. Websites don't want to load or display properly, often with a big block in the center, even as I scroll. I tried updating Chrome to the latest version, but that didn't help. I can't even clear my browsing data now!
Anyone else having the same issue? Perhaps I just need to uninstall and then re-install Chrome?
 
The update to Mac OS 12.1 went fine on my 2012 15" unibody MacBook Pro. But now Google Chrome doesn't work properly. Websites don't want to load or display properly, often with a big block in the center, even as I scroll. I tried updating Chrome to the latest version, but that didn't help. I can't even clear my browsing data now!
Anyone else having the same issue? Perhaps I just need to uninstall and then re-install Chrome?
Post install patching?
 
  • Like
Reactions: K two
Just double checked. Spoof Level is None and Spoof Model is Default. So odd.
None is the new default on all systems not having a post 2016 AMD metal GPU installed.
Please try a PRAM reset on reboot and report back if the OTA update becomes visible.
 
Looks like the new Virtual Machine (rather than spoofing) method doesn‘ cover your case.
If you boot the installer with 0.3.1, or make a new 0.3.2 set to do minimal spoofing (I think I saw a post on this).
Strange because yesterday I successfully installed 11.6.2 on an MBP5,2 with 0.3.2. 12.1 yet to be tried with 0.3.2.

Just double checked. Spoof Level is None and Spoof Model is Default. So odd.

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.
 
  • Like
Reactions: hvds and K two
None is the new default on all systems not having a post 2016 AMD metal GPU installed.
Please try a PRAM reset on reboot and report back if the OTA update becomes visible.
None doesn’t cut it on my system. The full installer doesn’t work and complains about a firmware update. Minimal is required for everything to work properly.
 
  • Like
Reactions: K two
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.
tempImageyBmsFU.jpg
 
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
Check your log files with the corresponding time stamp.
 
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 /
 
Hi everyone. In my iMac 27” 14,2 I had returned from Monterey to Catalina, as I had grown tired of the various changes of Apple, in the Beta updates, with continuous malfunctions, problems and bugs.
In the meantime, since I returned to Catalina, I have also returned happy and peaceful ...
I kindly ask, now, if anyone can tell me if with macOS 12.1 and the new spoofing method introduced by OCLP 0.3.2 (as well as with the Kepler patch for the nVidia GPU) my iMac 27" 14,2 (Late 2013 ) will work flawlessly again in everything, as worked perfectly full with OCLP and Big Sur, exactly as a supported Mac.
Thank you
yes I have the same iMac and I had to go back to Big Sur (patched-sur)due to all the bugs and problem with the display
I wonder if its safe to update to 12.1 with 0.3.2 OCLP I really want to update but do not want go through all that mess of installing and the same display problem still there and then go back to Big Sur again.
thanks in advance for the help
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.