macOS 12 Monterey on Unsupported Macs Thread

[Ausdauersportler]

Is it safe to overwrite this from within an updated OCLP app with "Build and Install OpenCore", or do I have to manually exchange files in the EFI?

This is the one (and only) supported method to update OCLP (of course nerds can always remove file manually in advance). So yes, it is save.

Please note there is always a drawback when using latest OCLP version in multi macOS setups. You possibly lower security (by disabling SIP and SBM) because installation of Ventura needs it, installation of previous macOS version might not….

The last pure Big Sur version was 0.2.5, the last Monterey version was 0.4.11, the first Ventura version is 0.5.0.

 

[coasterOneEightThree]

This is the one (and only) supported method to update OCLP (of course nerds can always remove file manually in advance). So yes, it is save.

Please note there is always a drawback when using latest OCLP version in multi macOS setups. You possibly lower security (by disabling SIP and SBM) because installation of Ventura needs it, installation of previous macOS version might not….

The last pure Big Sur version was 0.2.5, the last Monterey version was 0.4.11, the first Ventura version is 0.5.0.

Thank you!

I'm not sure yet if it's wise to switch to Ventura right now with my MacPro 3.1, especially since only a few Macs have been officially named as supported.

Nevertheless, there are hints that even the classic Mac Pro models are already being tested.

I have a Metal-capable graphics card installed, so it should be possible by now, but supposedly there are still display errors in certain situations.

 

[Ausdauersportler]

Thank you!

I'm not sure yet if it's wise to switch to Ventura right now with my MacPro 3.1, especially since only a few Macs have been officially named as supported.

Nevertheless, there are hints that even the classic Mac Pro models are already being tested.

I have a Metal-capable graphics card installed, so it should be possible by now, but supposedly there are still display errors in certain situations.

Kepler patching got even better on Ventura (OpenCL fix), otherwise it is basically the same on Monterey and Ventura. There is no support by the OCLP team and I will not interfere and start a private support business here.

Use a second separate disk with Ventura, install OCLP 0.5.0 on this 2nd disk, use the EFI picker of your Kepler card to select the OpenCore version of choice on boot. I am doing the very same thing here. Sometimes this fails because OpenCore magically decides to pick another installed version to activate on reboots.

Therefore I wrote a long time ago: Do not have multiple OC installations installed on the same machine! It may fail in the way I just described and it is hard to recognize the root cause of the failure, especially when it happens during automatically started reboots while installing macOS.

 

[mwidjaya]

Do not have multiple OC installations installed on the same machine!

Good advice.

Was thinking of doing Big Sur and Ventura on same machine - 2012 mini, but hearing this, I will just install Ventura over Big Sur (upgrade) using USB installer (OCLP) method.

Of course will do a backup of Big Sur to an external disk, just in case Ventura goes south and need to go back.

 

[yusufcpu]

Let's get ready to beta test this.

 

[Ausdauersportler]

Good advice.

Was thinking of doing Big Sur and Ventura on same machine - 2012 mini, but hearing this, I will just install Ventura over Big Sur (upgrade) using USB installer (OCLP) method.

Of course will do a backup of Big Sur to an external disk, just in case Ventura goes south and need to go back.

I did not say it would not work, but you sometimes need to be aware of this double installation feature I described.

 

[philk34]

I had sleep problems on my 3,1 until I removed the Bluetooth card.

Hello,
I thought the card was unique on Macpro 3.1 for wifi and bluetooth management so it was not possible to separate it

 

[Shadow Demon]

Hello,
I thought the card was unique on Macpro 3.1 for wifi and bluetooth management so it was not possible to separate it

With the side cover off, there is card to the left. Remove the screws, disconnect the antenna wires and pull out from the motherboard connector. My card was Bluetooth only.

 

[Ausdauersportler]

Hello,
I thought the card was unique on Macpro 3.1 for wifi and bluetooth management so it was not possible to separate it

Check this page if you want to explore your system in depth…

 

[DinkThifferent]

Hello, since upgrading my macbook to 12.6.1 (again) after running it apparently on 12.6.1 beta 1 (upgrading from catalina with open core 0.4.11) and using safari 16.1 suddenly my macbook cannot properly hibernate anymore. After closing the lid i have to start-up again after a couple of hours. i am greeted by 'your mac shut down due to a problem'. this was not the case with 12.6.1 beta 1 and safari 15.6.
Furthermore, the google search field remains blank when i type (but is visible after i press enter) and typing this message here on macrumors is very slow.

System-wide power settings:


Currently in use:

standbydelaylow 0
standby 0
womp 0
halfdim 1
hibernatefile /var/vm/sleepimage
sms 1
networkoversleep 0
disksleep 0
standbydelayhigh 4200
sleep 0 (sleep prevented by sharingd)
autopoweroffdelay 14400
hibernatemode 3
autopoweroff 1
ttyskeepawake 1
displaysleep 60
highstandbythreshold 50
acwake 0
lidwake 1



Any idea what to do?

 

[chrickers]

I'm experiencing sleep/hibernation problems too. In my case it's a beach ball of death. I enabled the hibernation workaround in developer options, let's see if that helps

 

[battmatth]

Hi,

I have a question about the Safari reloading pages issue with Safari 16.
Some weeks ago, on my MacBook Pro early 2011 (MPB 8,1) with MacOS 12.6 and Safari 16 the issue was there on a lot of websites.
To resolve it, I have now MacOS 12.6.1 (21G215) with Safari 15.6.1 (17613.3.9.1.16). All is OK.
But what if I update my MBP to the Public release of 12.6.1. I want to be sure that Safari will not have problems to load pages.
What is your feedback for the users who had the issue ?
Thanks a lot in advance

 

[deeveedee]

@battmatth I applied the Monterey 12.6.1 and Safari 16.1 updates to my HackBookPro6,2 (after being prompted by Software Update) and websites with which I had issues before the update are now working for me without issues. I can't guarantee that my experience will dictate yours, but for me, the update worked well.

 

[roysterdoyster]

MBP4,1 17-inch (Early 2008): OTA Update 12.6 -> 12.6.1 via OCLP 0.4.12 successful. Safari "reload webpage" problem persisted.
After re-patching with OCLP 0.5.1n including Post-install patches: Safari problem solved.

The work of the developers is highly appreciated. This iconic machine of mine is --with the help of OCLP-- running Monterey reliably like a German Panzer with the elegant appearance of a fighter jet.

 

[philk34]

Consultez cette page si vous souhaitez explorer votre système en profondeur…

Thanks

 

[battmatth]

MBP4,1 17-inch (Early 2008): OTA Update 12.6 -> 12.6.1 via OCLP 0.4.12 successful. Safari "reload webpage" problem persisted.
After re-patching with OCLP 0.5.1n including Post-install patches: Safari problem solved.

The work of the developers is highly appreciated. This iconic machine of mine is --with the help of OCLP-- running Monterey reliably like a German Panzer with the elegant appearance of a fighter jet.

Thank you for your feedback. All work fine thanks to OCLP 0.5. Before applying Post install patches, problem persisted with Safari 16.1.
After applying patches and rebooting the MBP, the problem was solved.
A big thank you to the OCLP team.

 

[coasterOneEightThree]

Editing images in Apple Photos has become extremely slow here since switching from Catalina to Monterey, can anyone confirm this?

For example, when I want to remove dust with the retouching tool, the process of applying a brush takes 10-15 seconds. In Catalina it was maybe half a second.

Of course I have installed the root patches for NVIDIA Kepler.

 

[kral84]

hi i have an imac 2011 with nvidia card ...all working fine but can i disable the autoupdate ? it´s say update to mac os 13 ... when i done it i brick my imac I would like to stay with macos 12, any patch for this?

 

[hwojtek]

hi i have an imac 2011 with nvidia card ...all working fine but can i disable the autoupdate ? it´s say update to mac os 13 ... when i done it i brick my imac I would like to stay with macos 12, any patch for this?

Literally in this very thread.

 

[ng0757]

I upgraded one of my computers to 13.0. Safari's bugs seriously affected me.
so I formatted it and installed the old monterey 12.1. I have two questions.

1. I want to prevent the upgrade 12.6 or 13.0 prompt from appearing at some time in the future.
what should I do now? I want to never see it.

2. ventura-desktop is /System/Library/Desktop Pictures/Ventura Graphic.heic
I want to copy it to monterey.I was prompted that there was no permission to copy it to the folder in montery /System/Library/Desktop Pictures/.It's read only. How to change it?

 

[plugsnpixels]

[See end for update!]

Trying to get my 2013 MBA firmware updated from 433.120 to 433.140 as recommended by SilentKnight. I never had Big Sur on this system, went straight from Catalina to unsupported Monterey.

I understand you need to install the last supported OS for the computer (Big Sur) to get that update. I am on Monterey via OCLP and get this error:

Can't install an older OS...

The advice was to install the older OS onto an external drive, which I have ready to go.

Since it won't fly from within Monterey, am I looking at the USB install approach?

(Making bootable Big Sur flash drive...)

From the interwebs (eclecticlight.co):

"the only way to update the firmware in an Intel Mac is to install macOS or an update to it which contains that version of the firmware. You can perform that installation to an external disk which you never use again with that Mac, but that remains the one and only way."

"When Apple releases security updates for the non-current but supported versions of macOS, it normally includes firmware updates to bring all those Macs up to a common firmware version, which is currently [as of 3/21] 430.0.0.0.0 or later for the iMac14,2.
As Apple doesn’t normally release any such updates to earlier versions of macOS, Macs which are running those can’t get firmware updates either. They’re normally left with the last version which was current when they received their last security update.
For that to work, though, you must keep your Mac up to date with Apple’s security updates, of course."

*So what happens when we run current Security Updates to our patched systems?

>UPDATE: I did the latest Big Sur install from a flash drive onto an external SSD. Checked firmware while booted from SSD, 474.0.0.0.0! Booted back into OCLP version of Monterey, still 474. That was a cool trick!

So again, can I expect additional firmware upgrades going forward with OCLP-based Monterey and Ventura installs?

How does this Terminal result apply to an OCLP patched system?
_______________

/usr/libexec/firmwarecheckers/eficheck/eficheck --integrity-check

ReadBinaryFromKernel: No matching services found. Either this system is not supported by eficheck, or you need to re-load the kext

IntegrityCheck: couldn't get EFI contents from kext
________________

More fun reading:

The Apple of Your EFI: Mac Firmware Security Research

The security research team at Duo known as Duo Labs has published a research paper on Apple’s EFI firmware security - learn more about their findings and recommendations, including a link to security tools developed to mitigate the risk. Get the full technical paper here.

duo.com

Which firmware should your Mac be using? (version 6)

This article lists the firmware versions of Macs which have been successfully updated to run macOS 12.7.6. Apple doesn’t provide an official list of the current firmware versions which should…

eclecticlight.co

 

[plugsnpixels]

One minor bugger I keep noticing upon restarts (2013 MBA): The Dock becomes unresponsive and has to be killed, then it's good until next time.

 

[Ausdauersportler]

[See end for update!]

Trying to get my 2013 MBA firmware updated from 433.120 to 433.140 as recommended by SilentKnight. I never had Big Sur on this system, went straight from Catalina to unsupported Monterey.

I understand you need to install the last supported OS for the computer (Big Sur) to get that update. I am on Monterey via OCLP and get this error:

Can't install an older OS...

The advice was to install the older OS onto an external drive, which I have ready to go.

Since it won't fly from within Monterey, am I looking at the USB install approach?

(Making bootable Big Sur flash drive...)

From the interwebs (eclecticlight.co):

"the only way to update the firmware in an Intel Mac is to install macOS or an update to it which contains that version of the firmware. You can perform that installation to an external disk which you never use again with that Mac, but that remains the one and only way."

"When Apple releases security updates for the non-current but supported versions of macOS, it normally includes firmware updates to bring all those Macs up to a common firmware version, which is currently [as of 3/21] 430.0.0.0.0 or later for the iMac14,2.
As Apple doesn’t normally release any such updates to earlier versions of macOS, Macs which are running those can’t get firmware updates either. They’re normally left with the last version which was current when they received their last security update.
For that to work, though, you must keep your Mac up to date with Apple’s security updates, of course."

*So what happens when we run current Security Updates to our patched systems?

>UPDATE: I did the latest Big Sur install from a flash drive onto an external SSD. Checked firmware while booted from SSD, 474.0.0.0.0! Booted back into OCLP version of Monterey, still 474. That was a cool trick!

So again, can I expect additional firmware upgrades going forward with OCLP-based Monterey and Ventura installs?

How does this Terminal result apply to an OCLP patched system?
_______________

/usr/libexec/firmwarecheckers/eficheck/eficheck --integrity-check

ReadBinaryFromKernel: No matching services found. Either this system is not supported by eficheck, or you need to re-load the kext

IntegrityCheck: couldn't get EFI contents from kext
________________

More fun reading:

The Apple of Your EFI: Mac Firmware Security Research

The security research team at Duo known as Duo Labs has published a research paper on Apple’s EFI firmware security - learn more about their findings and recommendations, including a link to security tools developed to mitigate the risk. Get the full technical paper here.

duo.com

Which firmware should your Mac be using? (version 6)

This article lists the firmware versions of Macs which have been successfully updated to run macOS 12.7.6. Apple doesn’t provide an official list of the current firmware versions which should…

eclecticlight.co

Check the first post about firmware updates…
We are doing this for years now and are well aware of the upcoming tasks and problems. This information has been there before even a patcher was available to the public.

 

[hwojtek]

1. I want to prevent the upgrade 12.6 or 13.0 prompt from appearing at some time in the future.
what should I do now? I want to never see it.

It was answered right above your post, for Christ's sake.

 

[plugsnpixels]

Check the first post about firmware updates…
We are doing this for years now and are well aware of the upcoming tasks and problems. This information has been there before even a patcher was available to the public.

Thanks, I will do a rewind and check it out!

And thanks again for your efforts.