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.
No, I meant what I said, option 3, Post-Install Volume Patch. I assume you're asking because you have a MBP 10,1 which has an HD4000 gpu on board. You are probably tired of trying to read the hi-res tiny, tiny text on your MBP screen.

So run OCLP TUI option 3, read the screen text prompts (there are plenty of options actually) and when done reboot. It will turn off SIP for your rMBP 10,1 every time you boot it so the HD4000 gpu can drive the internal display. Trust me, don't overthink this! And please read the documentation.

Jeesh, I'm starting to sound like Ausdauersportler...
Mac Pro 5,1
 
I am getting an error « a required firmware update could not be installed » while trying to do a clean install of beta 10 on a MacBook 2015 (macbook8,1), with OCLP 0.3.1n.

It occurs after the first reboot.

Any idea?

EDIT: seems I needed to enable VMM.

Hi,

I am having the same issue as @Jeremesk - same Macbook, using OCLP 0.3.1 and Monterey 12.0.1

Macbook8,1 (OCLP id's it at Macbook9,1 during EFI build), EFI built to both USB & original SSD that came with the Macbook. Running Big Sur 11.6.1. Installs Monterey from USB. Macos Update Assistant gives error "A required firmware update could not be installed."

Can you please post how you got this working (if you did)?

Thanks!
 
  • Like
Reactions: bogdanf
Hi,

I am having the same issue as @Jeremesk - same Macbook, using OCLP 0.3.1 and Monterey 12.0.1

Macbook8,1 (OCLP id's it at Macbook9,1 during EFI build), EFI built to both USB & original SSD that came with the Macbook. Running Big Sur 11.6.1. Installs Monterey from USB. Macos Update Assistant gives error "A required firmware update could not be installed."

Can you please post how you got this working (if you did)?

Thanks!
I just managed to install Monterey onto Macbook8,1 today. OCLP 0.3.1 (current release) gave that same 'firmware update error', however the current OCLP nightly build (OCLP 0.3.2n) already avoids Macbook9,1 spoofing and opts for spoofless WMM approach. So download OCLP 0.3.2 nightly, rebuild (1.), reinstall OCLP (2.), and install Monterey. It worked for me.
 
Anyone got this up and running on a 2014 MBR 11,1? From what I’m reading it shouldn’t be an issue doing an upgrade from my existing stock Big Sur install but just thought I’d check.

As for using OCLP, have I essentially got this right?

- download and patch Monterey
- put on usb stick
- select usb install on reboot
- profit?

Does OCLP work like Cydia did for jail breaking where you can just update it as you use the device or does it need a complete reinstall of the OS?

As always, thanks for the work the devs are doing here; it’s amazing at some of the age of devices still working.
 
Anyone got this up and running on a 2014 MBR 11,1? From what I’m reading it shouldn’t be an issue doing an upgrade from my existing stock Big Sur install but just thought I’d check.

As for using OCLP, have I essentially got this right?

- download and patch Monterey
- put on usb stick
- select usb install on reboot
- profit?

Does OCLP work like Cydia did for jail breaking where you can just update it as you use the device or does it need a complete reinstall of the OS?

As always, thanks for the work the devs are doing here; it’s amazing at some of the age of devices still working.
Just check the OCLP Github page and read the docs. Installing Big Sur or Monterey is the same process. Prepare a TM backup.

Later you can upgrade your Mac using the Apple software update process.
 
I just managed to install Monterey onto Macbook8,1 today. OCLP 0.3.1 (current release) gave that same 'firmware update error', however the current OCLP nightly build (OCLP 0.3.2n) already avoids Macbook9,1 spoofing and opts for spoofless WMM approach. So download OCLP 0.3.2 nightly, rebuild (1.), reinstall OCLP (2.), and install Monterey. It worked for me.
Worked like a charm! Thanks @dfranetic (and to the devs who changed the approach!)

Nightly builds can be found here courteous of nightly.link:
 
Hello everyone, please tell me. I installed macOS Monterey on my iMac 27 (late 2013) using the Open-Core Patcher method. Then I installed Patch System Volume. Everything started working well, but Photoshop gives an OpenCL unavailable error before launching. I also saw small artifacts in the system interface. Does anyone know a solution to this problem?
 

Attachments

  • 1635446259600.png
    1635446259600.png
    41.6 KB · Views: 137
  • 1635446853574.png
    1635446853574.png
    30.7 KB · Views: 103
  • Like
Reactions: OKonnel
The Black A1181 Frankenbook Lives again....

A Sucsesfull OCLP install to a A1181 5.2 MacBook

I really do have better things to be doing, but it is now running Monterey with a MacBook 5.2 2.13Ghz logicboard and a ac WiFi and BT 4.0 from a BCM94360CS2 WiFi upgrade along with an SSD.

It froze 3 times on the progress bar each time I waited an hr then rebooted and it finally installed !

Actually surprisingly usable will quite happily play a YouTube video or browse the web, and idles with not a lot of fan noise !

Not working is right clicking but I know there's a Prefpane to fix that somewhere no backlight control and the function keys don’t work with their shortcuts…. everything else including airdrop etc works great.

So much for Apples planned obsolescence, a perfectly capable machine for simple necessities….. and they look so much better in black.
 

Attachments

  • 7DF0394C-D75C-4BAE-85BF-F07D4AEF8B3E.jpeg
    7DF0394C-D75C-4BAE-85BF-F07D4AEF8B3E.jpeg
    236.9 KB · Views: 170
  • A2599715-554E-4AB5-BE1B-59D0B670A52B.jpeg
    A2599715-554E-4AB5-BE1B-59D0B670A52B.jpeg
    505.1 KB · Views: 193
  • 13A8E0AC-F93B-45A7-95ED-AE295B6934FB.jpeg
    13A8E0AC-F93B-45A7-95ED-AE295B6934FB.jpeg
    733.8 KB · Views: 178
For everyone planning to run macOS 12.1 Beta 1 seeded today, ensure your Mac has an Ivy Bridge or newer CPU
Currently all older CPUs will fail to boot due to RDRAND CPU requirement:
 
For everyone planning to run macOS 12.1 Beta 1 seeded today, ensure your Mac has an Ivy Bridge or newer CPU
Currently all older CPUs will fail to boot due to RDRAND CPU requirement:
And a good % of unsupp Macs are zonked by this change. Apparently, your efforts became too popular for Tim_Apple? :apple::apple::apple::apple:$
 
  • Like
Reactions: OCLP76 and gw463
Just check the OCLP Github page and read the docs. Installing Big Sur or Monterey is the same process. Prepare a TM backup.

Later you can upgrade your Mac using the Apple software update process.

Thanks for this, I'm new to github but eventually found what I was looking for ?
 
Hi everyone, quick question. I followed the other thread to install Big Sur on my 2011 27" iMac with an upgraded GPU, and it worked great. I was even able to use the built-in MacOS updater to update a few times to whatever the current version is (11.6.1 I think?). However, just now, my system update popped up and asked me to update to Monterey. I don't think that will work given what @K two posted above. I think this computer will be left on Big Sur since it's a Sandy Bridge chip.

But I'm wondering about my 2013 MacBook Pro, which has an Ivy Bridge i7 3740QM. I haven't checked yet, but if this one pops up and asks me to upgrade, would I just be able to click Update Now and have it update to Monetary, or would I have to go through the whole process from scratch again with OCLP and all that?
 
Yesterday mine ran with the fans going for most of the day. It has now stopped, no fans today. I put it down to post-upgrade activity. Open the case and clean the fans, if necessary.

BTW, how do you know the temperatures? Are you running a utility?
I gave it a couple of days post upgrade to settle down but even though the fans have slowed down, the temps remain higher. I've been using MenuMeters to monitor temps and other parameters for some time as I've had heat/fan issues in the past when upgrading non ssd hard drives. I wonder if the post install drivers required for the Intel HD4000 graphics are the same drivers from Big Sur or if they are some sort of emulation which is pushing the hardware more ?
 
  • Like
Reactions: rehkram
Anyone got any results from installing Monterey onto a 2013 iMac with Fusion Drive? Lots of chat last year about issues with Big Sur and fusion drives (some people had no issues, some had copious slow down), but I haven't heard anything about it this year with Monterey.
 
For everyone planning to run macOS 12.1 Beta 1 seeded today, ensure your Mac has an Ivy Bridge or newer CPU
Currently all older CPUs will fail to boot due to RDRAND CPU requirement:
Is it possible to emulate the instruction like AAAMouSSE.kext does for other instructions?
Is it possible to setup this emulation in EFI before the kernel is loaded? For example, code for setting and reading NVRAM variables is setup by EFI. I guess it depends if the illegal instruction vector (or whatever its called in x86 land) is modifiable in EFI and preserved by the kernel.
 
Have a trouble with installing macOS Monterey on my MBP Late 2013 with discrete video card (MacBookPro11,3). Once macOS starting to boot at the very first time right after installation process, it hangs on the Apple logo with progress bar (~40%). After that I realize that the system itselt is booted for further setting because I hear voice over and some system sounds after pressing some keyboard buttons, although I still observe the logo with progress bar and it isn't dissapeared.
I tried resetting NVRAM by pressing Option-Command-P-R, but it didn't help.
P.S.I am booting with plugged in flash drive via EFI and then selecting the hdd with already installed macOS. Initially I erased my SSD with Mac OS Extended (Journaled) format and GUID Partition Map scheme.
 
Anyone got any results from installing Monterey onto a 2013 iMac with Fusion Drive? Lots of chat last year about issues with Big Sur and fusion drives (some people had no issues, some had copious slow down), but I haven't heard anything about it this year with Monterey.
My Monterey is installed in a partition on the HDD part of the Fusion drive of the iMac14,2 (27-inch, Late 2013) since Catalina is in the fusion drive container. It runs fine (I don't use it all the time) but I am thinking about replacing the Fusion drive with normal SSDs.

It was slow in the beginning but the OCLP post install (adds Nvidia Kepler acceleration) and maybe some time fixes that.

Thunderbolt Target Display Mode (TB TDM) (press command F2) works in Monterey (before, I was using High Sierra for TB TDM).
 
Odd. 0.3.2N and 12.0.1 Mini5,3 and the bluetooth Magic Keyboard and Magic TrackPad stopped working wirelessly. Bluetooth also will not toggle on. Unpatched and repatched, same. Toggle was broken in 0.3.1 however devices were working, assume bc they were paired before. Thoughts?
 
  • Like
Reactions: K two
could it be the limit for my old beloved 3.1 ?? ..... shame but i still trust you ....
macOS 12.1 STOPS the following Macs -
  • MacPro5,1 and older
  • MacBook7,1 and older
  • MacBookAir4,x and older
  • MacBookPro8,x and older
  • iMac12,x and older
  • Macmini5,x and older
  • Xserve3,1 and older
  • ? ??
 
  • Like
Reactions: OCLP76
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.