macOS 12 Monterey on Unsupported Macs Thread

[Ausdauersportler]

lol Now, you are confused. Where is the dosdude bootROM patcher mentioned? The point is - the dortania headline needs claification or deletion because as written it misleads the newbies and those taking it as written. Also, certain useful now-anecdotal assumptions need to be included into the 'Scriptures' in the proper context. A suggestion? ?‍♂️

This is the last time, please answer honestly:

Where do you find the phrase firmware patching related to running more recent macOS versions on old Macs (or unsupported Macs)?

Who invented this, who used this phrase, and to what purpose? Who needed it to provice support for some pre 2009 systems?

 

[Sven G]

MacBookPro11,3, OCLP 0.4.2 GUI, macOS Monterey 12.2.1 on external 64 GB USB SSD:

* OCLP boot: works without problems;

* FileVault: works without problems;

* OTA software update (this time, from 12.2 to 12.2.1), with FileVault enabled: works without problems;

* root patching (downloading and installing Kepler kernel extensions), with FileVault enabled: works without problems.

Really impressed: everything now works as advertised (except for SIP, which obviously cannot be fully enabled, in this case) - kudos… ????

 

[hvds]

I can't get the Keyboard backlight to work. How did you do it?

Successful update to 12.3b2 via OTA Update and OCLP 0.4.3n, unattended, flawless performance so far.

Sorry for answering late. I see that you've solved this already. In my case it might have worked right away because I hadn't used LabTick but Touché instead.
Just to mention also that today (11 Feb) 0.4.3n got a fix named "Resolve Non-Metal Keyboard Backlight support" which probably is in response to interference with LabTick.

Edit: just applied the post-install root patches of this latest 0.4.3n to my existing Big Sur (11.6.3), and keyboard backlight continues to work well.

 

[mwidjaya]

Also, certain useful now-anecdotal assumptions need to be included into the 'Scriptures' in the proper context

Fair call.

Newbies do get confused.

The guide can be improved to better explain the basics.

 

[thatguywill]

MacBookPro11,3, OCLP 0.4.2 GUI, macOS Monterey 12.2.1 on external 64 GB USB drive:

* OCLP boot: works without problems;

* FileVault: works without problems;

* OTA software update (this time, from 12.2 to 12.2.1), with FileVault enabled: works without problems;

* root patching (downloading and installing Kepler kernel extensions), with FileVault enabled: works without problems.

Really impressed: everything now works as advertised (except for SIP, which obviously cannot be fully enabled, in this case) - kudos… ????

I've got the same model, does SIP automatically disable itself? I've never done anything with it and seen it mentioned a few times

 

[Sven G]

IIRC, it should be disabled directly from OCLP when you make the Kepler root patch; I remember that in the beginning there were some problems, but this was many OCLP and Monterey versions ago: today, it just works. You can see the current SIP status in the Terminal, with a csrutil status command: on the MacBookPro11,3, some items are disabled, others enabled. It would of course be really cool if SIP could be fully re-enabled after root patching, but sadly this isn’t possible…

 

[5tracks]

Can someone knowledgable please answer my question about spoof-less vs minimal spoofing?

(summary: if everything is working fine on 0.3.1 with minimal spoofing, is there a benefit to switch to spoof-less, or update OCLP to latest?)

 

[serafin79]

has anyone noticed with the last couple nightly OCLP that there are black out artifacts in imessage and Mail
I'm on a MBP 8,1
it's nice that the keyboard backlight now works

Thanks,


Found a temp work around
change the Display Setting profile to "sRGB IEC61966-2.1

 

[thatguywill]

IIRC, it should be disabled directly from OCLP when you make the Kepler root patch; I remember that in the beginning there were some problems, but this was many OCLP and Monterey versions ago: today, it just works. You can see the current SIP status in the Terminal, with a csrutil status command: on the MacBookPro11,3, some items are disabled, others enabled. It would of course be really cool if SIP could be fully re-enabled after root patching, but sadly this isn’t possible…

Thanks man, the first 3 are disabled so i'll take that as a good sign

 

[Ausdauersportler]

Can someone knowledgable please answer my question about spoof-less vs minimal spoofing?

(summary: if everything is working fine on 0.3.1 with minimal spoofing, is there a benefit to switch to spoof-less, or update OCLP to latest?)

Did you check the release note of 0.3.2 - maybe the answer is included there.

 

[TheStork]

CCC will not copy the EFI partition. Also CCC in most cases will not produce a bootable clone in Big Sur and later OSes.

Here's a way to do it:

Asus Z690 ProArt Creator WiFi (Thunderbolt 4) + i7-12700K + AMD RX 6800 XT

CaseySJ's Intel Alder Lake i7-12700K: Asus Z690 ProArt Creator WiFi + Intel i7-12700K + AMD RX 6800 XT Please do not quote this guide in its entirety. Post a link instead. This build guide applies to Asus Z790 ProArt Creator as well, but BIOS parameters may need to be adjusted All P-cores...

www.tonymacx86.com

 

[Realityck]

CCC will not copy the EFI partition. Also CCC in most cases will not produce a bootable clone in Big Sur and later OSes.

I done it many times see this post, the very recent 12.3 betas have issues using the bless utility that is part of APFS replication. That new 12.3 bug has been reported to Apple contacts. This is for creating a bootable snapshot of Big Sur or Monterey. In order for the system to be updated you need to wipe the storage again and make use of legacy bootable backup assistant. But it will allows infinite data volume backup if you don't need to do that.

 

[K two]

This is the last time, please answer honestly:

Where do you find the phrase firmware patching related to running more recent macOS versions on old Macs (or unsupported Macs)?

Who invented this, who used this phrase, and to what purpose? Who needed it to provice support for some pre 2009 systems?

The point is, the attached is misleading if various non-specified qualifications exist. ?‍♂️

 

[TimmuJapan]

So people are getting confused about what it means to have their [firmware up-to-date] versus [(zero) firmware patching]……

I think that Ausdauersportler summed it up well in post #4,596. But, for less experienced users, it probably would be helpful for it to somewhere say, “Installing the highest native macOS possible + the most recent security updates for that native macOS before installing opencore will yield the best results. This will ensure that your computer’s firmware is up-to-date.”

Some people probably grab these old macs that started with Lion or Snow leopard and were never upgraded, and they try to go straight to opencore, and things don’t work right… before opencore, Shouldn’t they first install the highest native macOS that they can on their machines to get that up-to-date firmware? In the case of an old Mac starting on Lion, they will have to make a pitstop at El Capitan probably first before getting to high sierra.

 

[rehkram]

My own opinion is that things are evolving so fast it's very hard for the OCLP developers to keep the documentation up-to-date and fully comprehensive. I've been in the industry for decades. The problems in our case can involve many permutations of machines, opsys software, app software, 3rd party hardware, 3rd party app s/w, and firmware versions. This is not a trivial task.

My approach, and you guys probably do the same, is to try and figure out problems myself, as they occur. If I don't find a fix (or workaround) then I read the documentation again. If I still don't find a fix (or workaround), I post my findings here.

If I do find a fix (or workaround), I'll post it here also. So we're all involved in helping the OCLP devs get to completion. The OCLP team can assist by delegating people to keep the documentation up-to-date as soon as possible. I'm guessing they are under-resourced in that area. That's usually the case on big projects.

This is all completely normal in the world I come from. Documentation is always behind reality on projects, particularly one as vast as this. I'm just blown away at how far OCLP has come in a relatively short time.

 

[TigerA]

I'd like to know where you guys get the OCLP v0.4.3n from? I know the nightly-build has been removed from the GitHub to avoid confusion for the newbies.

 

[rehkram]

I think you may be able to get that information by doing a search of this thread by clicking on the magnifying glass at the top of the page using the term "nightly".

Personally I stay away from nightly builds which are by definition betas but I understand they may solve various issues.

 

[TigerA]

I think you may be able to get that information by doing a search of this thread by clicking on the magnifying glass at the top of the page using the term "nightly".

Personally I stay away from nightly builds which are by definition betas but I understand they may solve various issues.

Thanks. found at #4311 ?
There is no urgency for me to use it: Curiosity only for now.

 

[mwidjaya]

“Installing the highest native macOS possible + the most recent security updates for that native macOS before installing opencore will yield the best results. This will ensure that your computer’s firmware is up-to-date.”

Yes.

Also, if you mac is on still supported macOS version, new security updates may contain firmware update.

As an example, my 2012 mini officially on Catalina, which is still getting sec updates; sometimes bundling firmware update.

Heck, Apple occasionally release sec update for macOS that is even older.

As such, I have kept a small partition (50GB) of Catalina. I can reset NVRAM, boot into that and apply sec update. Thus able to keep up w/ future firmware.

 

[rehkram]

Thanks. found at #4311 ?
There is no urgency for me to use it: Curiosity only for now.

Remember the old saying about killing the cat

In emergency, break glass.

 

[0134168]

.

 

[0134168]

CCC will not copy the EFI partition. Also CCC in most cases will not produce a bootable clone in Big Sur and later OSes.

Using CCC long time ago. Makes perfect bootable clones even in Monterey. Of course, does not copy the EFI partition. It seems it´s not working in the recent beta. I hope they fix it when released.

 

[5tracks]

Did you check the release note of 0.3.2 - maybe the answer is included there.

Yes, I always read the release notes, Changelog, and read me for any new version.
I tried to stumble along myself, and only post here if I get stuck or have a question I can’t find an answer to.

Since I’m not a programmer and don’t understand the underlying differences between spoof-less and minimal spoofing besides one uses a VM, I think it’s only natural to wonder what the benefits are for a regular user such as myself.

 

[Tockman]

Well, now it's my turn to ask a question If I installed Catalina on a separated volume of my SSD as second OS (OCLP'd Monterey is on another volume of the same SSD) won't it affect in any way my existing Monterey installation and OpenCore status?

 

[TimothyR734]

I am learning as well as I haven't had a iMac since the early betas of macOS Big Sur I have successfully installed macOS Monterey 12,3 beta 2 using the the night OpenCore Patcher 0.4.3 so with that I have the grey login screen and when I run Is;ent Nigh it says my SIP in enabled, the terminal says its disabled, when I boot into my install macOS Monterey usb and run csrutil status in the terminal my SIP is disabled but when I reboot holding Command-R and type csrutil status in the built in recovery terminal its says command not found as the built recovery terminal is still using BASH