macOS 12 Monterey on Unsupported Macs Thread

[Ausdauersportler]

Thank you! Do I need to be concerned that OCLP might write to the Catalina installation on my main SSD? I tend to be slow and meticulous so trying to be very careful to keep all this only on the internal blade SSD and the USB flash drive until I have learned OCLP.

Having OpenCore installed on your internal disk can interfere with the Catalina installation, but you can get around this by booting into Catalina directly using the alt/option key and the EFI picker - unfortunately on each boot.

Big Sur and Monterey need OpenCore to be installed, and it is really convenient to have it on an internal disk instead of using the USB installer created during the installation process. But you can of course use the USB Stick and boot into it using the same alt/option EFI trick each time you need it. Depends on the use pattern. It is a good idea to reset the PRAM when moving from OpenCore to non OpenCore.

 

[Ausdauersportler]

I don’t have a MacBook. I’ve said it several times… If this is directed at me - know that I don’t have a MacBook. I have an old 2010 Mac Pro. Aside from my iPhone that’s all I have.

I didn’t say that I talked to an OCLP developer. I said someone “someone“ sent me a fix and it worked. Well it didn’t work entirely… But it worked well enough that I was able to install OCLP in Monterey. I’m going back to Catalina because Monterey doesn’t work well on this particular machine, and I don’t know why… I’m not an engineer, I’m not a programmer… I’m an old man just asking for a little help, and someone did.

Am I guilty of someone helping me? I guess so. Is it wrong for someone to offer me a solution privately? I didn’t read anything in your rules that stated so.

We have (several people did this in different words) tried to explain that you already had a misconfigured OpenCore configuration installed (which is not airborne and needs a user to start and run the OCLP app). There is no other answer which can explain the screen shot you published. OLCP is the only known to me simple program which can achieve such a misconfiguration after a few keys pressed. I doubt you would have used other programs to get into this state. Last time: This was a user misconfiguration, no OCLP bug.

The OpenCore configuration can and will survive even an macOS installation just because OpenCore is stored in a different separate location on the disk.

It is not unusual seeing a beginner struggling with OpenCore although this OLCP app limits the configuration and installation process to a few key strokes. You have no idea what amount of expertise it would need to accomplish this task in a manual way. Believe me, it is not bad to create such a wrong config, it is just unfortunate ....and nobody said you did it on purpose.

My first answer was exactly pointing out these pure facts. There was no judgement, only some slight amusement because I had seen similar error messages myself very often during OCLP development and use, but I am able to recognize the error I made and it does not stop me from using the same OCLP app to fix it. Therefore asked you to run the app again and rewrite the wrong config with a correct new one. This is another beauty of the app. One can simple replace an older version of OpenCore with a newer (sometimes more powerful) one with a few keystrokes...

To sum up the last posts:

You claimed you have never used OLCP to generate the MacBookPro6.x config. Really, really unlikely!

I have no clue how to do that. Not in any way shape or form…So, nope.

You claimed there is an (confirmed) OCLP bug causing your problem. Wrong!

OCLP threw the error - in error.

You claimed this bug would be fixed in an upcoming version. This is definitely a lie!

Apparently this problem will be fixed in an updated version of OCLP. That’s all I can tell you, right now.

You are only guilty to bending the truth. Stop doing this if you really want help.

 

[davidlv]

Thank you! Do I need to be concerned that OCLP might write to the Catalina installation on my main SSD? I tend to be slow and meticulous so trying to be very careful to keep all this only on the internal blade SSD and the USB flash drive until I have learned OCLP.

Aside from the items in the posts after yours, this Monterey and OCLP installation on the internal Apple SSD blade left over from that Fusion drive should work quite well. I have the same SSD blade in an iMac 15,1 left from a Fusion drive.
After initialization, it is only 121GB, so you have to be careful about what you install. In my case I have 74GB left available, and I still have 3.6 GB of MP3s installed! The SSD drive is not really that fast, but it works, and trim is supported. I suggest you simply use the USB drive and its boot picker (OCLP installed to that USB drive) until you are sure you are OK with Monterey. Catalina still has the latest web kit updates, until later this year, so you have some time to investigate. On my late 2014 iMac, no post install root patches are required. There may be some needed on your older machine, I don't know about that. Having the root patches installed slows down my old 2011 MBP a little, and it runs somewhat hotter than it could. Still, due to OCLP, I can use this old trusty machine as a backup, and it has all the latest security patches! Wonderful stuff- thanks to all the devs for OCLP!

 

[TimmuJapan]

We have (several people did this in different words) tried to explain that you already had a misconfigured OpenCore configuration installed (which is not airborne and needs a user to start and run the OCLP app). There is no other answer which can explain the screen shot you published. OLCP is the only known to me simple program which can achieve such a misconfiguration after a few keys pressed. I doubt you would have used other programs to get into this state. Last time: This was a user misconfiguration, no OCLP bug.

The OpenCore configuration can and will survive even an macOS installation just because OpenCore is stored in a different separate location on the disk.

It is not unusual seeing a beginner struggling with OpenCore although this OLCP app limits the configuration and installation process to a few key strokes. You have no idea what amount of expertise it would need to accomplish this task in a manual way. Believe me, it is not bad to create such a wrong config, it is just unfortunate ....and nobody said you did it on purpose.

My first answer was exactly pointing out these pure facts. There was no judgement, only some slight amusement because I had seen similar error messages myself very often during OCLP development and use, but I am able to recognize the error I made and it does not stop me from using the same OCLP app to fix it. Therefore asked you to run the app again and rewrite the wrong config with a correct new one. This is another beauty of the app. One can simple replace an older version of OpenCore with a newer (sometimes more powerful) one with a few keystrokes...

To sum up the last posts:

You claimed you have never used OLCP to generate the MacBookPro6.x config. Really, really unlikely!

I have no clue how to do that. Not in any way shape or form…So, nope.

You claimed there is an (confirmed) OCLP bug causing your problem. Wrong!

OCLP threw the error - in error.

You claimed this bug would be fixed in an upcoming version. This is definitely a lie!

Apparently this problem will be fixed in an updated version of OCLP. That’s all I can tell you, right now.

You are only guilty to bending the truth. Stop doing this if you really want help.

There is a lot of misinformation spewn on this site about OCLP. I saw in another thread users falsely claiming that there were back doors installed in OCLP and dosdude patches to make it easier for bad actors to steal personal information from our computers. Complete nonsense and totally unfair.

Knowing what we know here about how amazing and wonderful dosdude1 and subsequently OCLP’s work has been to keep life in these old macs, I think that it is essential for people to speak out against misinformation towards OCLP. Misinformation, people using the program incorrectly, or people who don’t read the docs carefully and come to this site writing about their situation often paint OCLP in an unfair light (i.e. “it wasn’t my fault! It was the bug in the program!”)…… The bug in the program that doesn’t exist… 😏 I think that this is exactly what @Ausdauersportler is reacting to in these posts above, and good for him for doing that. If people are allowed to make unfair claims about the functionality of OCLP without being corrected, then it just adds to the cycle of misinformation and distrust about a wonderful free service that we all enjoy to keep our old macs alive.

 

[gw463]

Hi all I would need to install photoshop 2022 on my Macpro 3.1 but obviously I don't have a processor with SSE 4.2 but I get to 4.1 which is not enough to install photoshop. Now I have looked for various info but it seems that the only way is to change Mac although I would regret it since it works very well with Monterey 12.5 and OCLP. I already have photoshop 2019 which works well but I have some plugins that need the new version. Is there any hope or will I have to resign myself ??? thanks in advance and congratulations to the OCLP developers who are working wonders .......

 

[Sven G]

Since I made Monterey my MacBookPro11,3’s main OS (previously on Big Sur), I have an odd problem with Acronis: some of the application’s windows (such as preferences and some setup windows) won’t even appear when booted normally, while they appear only when booted into safe mode; never had this quite strange and annoying behaviour in Big Sur: so, what could cause this? perhaps it could be something related to the semi-broken OpenCL in patched Monterey? Here, taken in safe mode, are the screenshots of two windows that won’t appear in normal mode, as if they were non-existent (BTW, on my other MacBookPro11,1, which doesn’t need root patches, those windows always appear normally)…

 

[knyght]

I successfully installed Monterey (thanks Mr. Macintosh) on my 5,1 Mac Pro. RX580 GPU, OS 12.5.1, OpenCore Legacy Patcher 0.4.10

Issue: after the install, I cannot turn on Bluetooth or Wi-Fi.

Solution??

 

[dKupe]

Aside from the items in the posts after yours, this Monterey and OCLP installation on the internal Apple SSD blade left over from that Fusion drive should work quite well. I have the same SSD blade in an iMac 15,1 left from a Fusion drive.

Wow I am lucky to have another use here also running dual internal SSDs! Like you, one is the 128gb Blade SSD that was part of my Fusion drive, and the other is a new WD 4TB SSD that replaced the old HDD. This is a Late-2013 iMac 14,2.

I installed OCLP today on the 128gb Blade SSD and have to say it was an amazing success! I can boot either to Catalina on my 4TB SSD, or to Monterey on my 128gb Blade SSD. I installed OCLP on the Blade SSD and don't need the USB drive to boot. Amazing!

But there is something strange going on when viewing the Blade SSD from the Desktop when running in Catalina. The volume name is "Apple Blade SSD" and it appears as such in the Finder in Monterey. But the same volume in Catalina is named "Update". And opening "Update" displays files that are undoubtedly related to OCLP, but there is no sign of the Folders that should be there- namely Applications, Library, System, and Users. Disk Utility also has an issue with "Update" when viewed in Catalina, with an unmountable volume named disk3s5. So the real problem is that it is impossible to view the "Apple Blade SSD-Data" in the Finder. But when booted into Monterey, I can see all directories on both drives. Ideas anyone?

The two SSDs as seen on the Desktop in Monterey

The same two SSDs viewed from the Desktop in Catalina

And the contents of "Update" as viewed in Catalina. All OCLP files?

"Update" as viewed in Disk Utility

 

[davidlv]

Wow I am lucky to have another use here also running dual internal SSDs! Like you, one is the 128gb Blade SSD that was part of my Fusion drive, and the other is a new WD 4TB SSD that replaced the old HDD. This is a Late-2013 iMac 14,2.

I installed OCLP today on the 128gb Blade SSD and have to say it was an amazing success! I can boot either to Catalina on my 4TB SSD, or to Monterey on my 128gb Blade SSD. I installed OCLP on the Blade SSD and don't need the USB drive to boot. Amazing!

But there is something strange going on when viewing the Blade SSD from the Desktop when running in Catalina. The volume name is "Apple Blade SSD" and it appears as such in the Finder in Monterey. But the same volume in Catalina is named "Update". And opening "Update" displays files that are undoubtedly related to OCLP, but there is no sign of the Folders that should be there- namely Applications, Library, System, and Users. Disk Utility also has an issue with "Update" when viewed in Catalina, with an unmountable volume named disk3s5. So the real problem is that it is impossible to view the "Apple Blade SSD-Data" in the Finder. But when booted into Monterey, I can see all directories on both drives. Ideas anyone?

The two SSDs as seen on the Desktop in Monterey

View attachment 2050348

The same two SSDs viewed from the Desktop in Catalina

View attachment 2050349

And the contents of "Update" as viewed in Catalina. All OCLP files?

View attachment 2050350

"Update" as viewed in Disk Utility

View attachment 2050351

In my case, the other internal disk is a Seagate 1TB HDD, not an SSD. I use it as a storage disk only. Apple made a lot of changes when they released Big Sur and then again with Monterey, so that issue is probably related to Catalina's inability to recognize the Apple blade SSD correctly. I assume you initialized the blade SSD while booted up from the USB Monterey install disk. There are many differences in the Disk Utility app from Monterey and that in Catalina. After you are confident that Monterey running on OCLP works for you, it would probably be best to upgrade that big SSD to at least Big Sur and probably best to Monterey. However, Monterey seems to be somewhat sensitive to having two bootable Monterey disks. See the Carbon Copy Cloner page for more details. The Monterey system is really quite complex, and it has its quirks. I am sure someone with more experience than I have will offer some related advice.
In short, great that your installation of Monterey on that blade SSD went well. Did you try starting up OCLP and try to run the Post Install Patches? (Not sure any are required with that hardware)
You should be aware that you should have only one installation of OCLP on the computer, even if you decide to install Monterey on. the large SSD.

 

[JedNZ]

Wow I am lucky to have another use here also running dual internal SSDs! Like you, one is the 128gb Blade SSD that was part of my Fusion drive, and the other is a new WD 4TB SSD that replaced the old HDD. This is a Late-2013 iMac 14,2.

I installed OCLP today on the 128gb Blade SSD and have to say it was an amazing success! I can boot either to Catalina on my 4TB SSD, or to Monterey on my 128gb Blade SSD. I installed OCLP on the Blade SSD and don't need the USB drive to boot. Amazing!

But there is something strange going on when viewing the Blade SSD from the Desktop when running in Catalina. The volume name is "Apple Blade SSD" and it appears as such in the Finder in Monterey. But the same volume in Catalina is named "Update". And opening "Update" displays files that are undoubtedly related to OCLP, but there is no sign of the Folders that should be there- namely Applications, Library, System, and Users. Disk Utility also has an issue with "Update" when viewed in Catalina, with an unmountable volume named disk3s5. So the real problem is that it is impossible to view the "Apple Blade SSD-Data" in the Finder. But when booted into Monterey, I can see all directories on both drives. Ideas anyone?

The two SSDs as seen on the Desktop in Monterey

View attachment 2050348

The same two SSDs viewed from the Desktop in Catalina

View attachment 2050349

And the contents of "Update" as viewed in Catalina. All OCLP files?

View attachment 2050350

"Update" as viewed in Disk Utility

View attachment 2050351

I think it's got something to do with the Catalina version of APFS not being able to fully read/understand the newer (BigSur+) version of APFS (some discussion here).

 

[Larsvonhier]

I successfully installed Monterey (thanks Mr. Macintosh) on my 5,1 Mac Pro. RX580 GPU, OS 12.5.1, OpenCore Legacy Patcher 0.4.10

Issue: after the install, I cannot turn on Bluetooth or Wi-Fi.

Solution??

Have you applied the post install (root-volume) patches with OCLP?
What type of card do you have installed (is it still supported either natively or through patches?)

 

[OKonnel]

There is a lot of misinformation spewn on this site about OCLP. I saw in another thread users falsely claiming that there were back doors installed in OCLP and dosdude patches to make it easier for bad actors to steal personal information from our computers. Complete nonsense and totally unfair.
Knowing what we know here about how amazing and wonderful dosdude1 and subsequently OCLP’s work has been to keep life in these old macs, I think that it is essential for people to speak out against misinformation towards OCLP. Misinformation, people using the program incorrectly, or people who don’t read the docs carefully and come to this site writing about their situation often paint OCLP in an unfair light (i.e. “it wasn’t my fault! It was the bug in the program!”)…… The bug in the program that doesn’t exist… 😏 I think that this is exactly what @Ausdauersportler is reacting to in these posts above, and good for him for doing that. If people are allowed to make unfair claims about the functionality of OCLP without being corrected, then it just adds to the cycle of misinformation and distrust about a wonderful free service that we all enjoy to keep our old macs alive.

Hi @TimmuJapan. I wholeheartedly join your defense of honor of OpenCore Legacy Patcher and its Developers: @khronokernel, @dosdude1, DinakG, vt9696, @ASentientBot and others, above all; but also highly experienced people such as the good @Ausdauersportler who actively collaborate to improve the product.
Backdoor in OCLP?... ... I'm not a developer, but I'm a good nerd and very interested in computing and as far as I know both the OCLP and dosdude1 patches are all open and clean. If anything, they are MS Winzozz and perhaps also macOS who unfortunately do many things in the background and in any case profile us...

 

[OKonnel]

Deleted message for error. My bad.
Question OT: Is it possible to delete a message sent by mistake? And how can it be canceled? In my iPhone, in Safari, only the possibility to edit the message appears.

 

[knyght]

Have you applied the post install (root-volume) patches with OCLP?
What type of card do you have installed (is it still supported either natively or through patches?)

I did not apply post install patches.

So I just tried and it gives me this message:

Available patches for system:
- Networking: Legacy Wireless

Cannot Patch due to following reasons:
- SIP is enabled (required: 0x802 or higher)
- Currently Booted SIP: (0x6f)

I disabled SIP in terminal and rebooted. OCLP still says SIP is enabled.

??

This is my bluetooth info:
Bluetooth Controller:
Address: NULL
State: Off
Chipset: BCM_4350C2
Discoverable: Off
Firmware Version: v0 c0
Product ID: 0x0001
Supported services: 0x382039 < HFP AVRCP A2DP HID Braille AACP GATT Serial >
Transport: USB
Vendor ID: 0x004C (Apple)

 

[Tockman]

Deleted message for error. My bad.
Question OT: Is it possible to delete a message sent by mistake? And how can it be canceled? In my iPhone, in Safari, only the possibility to edit the message appears.

As far as I know, there's no option like that. But you may anytime delete your message's content, mark it as "del" or something else, and moderator will remove it some time later - that's verified

 

[davidlv]

I did not apply post install patches.

So I just tried and it gives me this message:

Available patches for system:
- Networking: Legacy Wireless

Cannot Patch due to following reasons:
- SIP is enabled (required: 0x802 or higher)
- Currently Booted SIP: (0x6f)

I disabled SIP in terminal and rebooted. OCLP still says SIP is enabled.

??

This is my bluetooth info:
Bluetooth Controller:
Address: NULL
State: Off
Chipset: BCM_4350C2
Discoverable: Off
Firmware Version: v0 c0
Product ID: 0x0001
Supported services: 0x382039 < HFP AVRCP A2DP HID Braille AACP GATT Serial >
Transport: USB
Vendor ID: 0x004C (Apple)

You will probably have to start up OCLP and use it to disable SIP. Tell OCLP to write to the disk (overwrite the present settings, and reboot. Then run OCLP and do the Post Install Root patch to get that Legacy Wireless enabled.
Did that fix the wireless system?
I don't know what it will take to get the bluetooth working, probably you will have to install a later Bluetooth and wireless card. I have seen several examples of this on the forum somewhere. Search time it seems.
First do a search for that BCM_4350C2 bluetooth card to determine if it will work with Monterey.
Old hardware .....

 

[knyght]

You will probably have to start up OCLP and use it to disable SIP. Tell OCLP to write to the disk (overwrite the present settings, and reboot. Then run OCLP and do the Post Install Root patch to get that Legacy Wireless enabled. After the reboot, use OCLP again to set SIP enabled, write to disk, and reboot.
Did that fix the wireless system?
I don't know what it will take to get the bluetooth working, probably you will have to install a later Bluetooth and wireless card. I have seen several examples of this on the forum somewhere. Search time it seems.
First do a search for that BCM_4350C2 bluetooth card to determine if it will work with Monterey.
Old hardware .....

How do I use OCLP to disable SIP? I don't want to screw up the install by configuring it wrong.

 

[Ausdauersportler]

You will probably have to start up OCLP and use it to disable SIP. Tell OCLP to write to the disk (overwrite the present settings, and reboot. Then run OCLP and do the Post Install Root patch to get that Legacy Wireless enabled. After the reboot, use OCLP again to set SIP enabled, write to disk, and reboot.
Did that fix the wireless system?
I don't know what it will take to get the bluetooth working, probably you will have to install a later Bluetooth and wireless card. I have seen several examples of this on the forum somewhere. Search time it seems.
First do a search for that BCM_4350C2 bluetooth card to determine if it will work with Monterey.
Old hardware .....

You cannot enable SIP on a root patched system, this would break booting.

To enable WiFi all pre 2011 systems need root patches unless the hardware has been updated.

Using OpenCore one has to change the SIP status through the OC config, which can be done using the OCLP app and rewriting a new config with corrected SIP settings.

Only change SIP if your are 100% sure you do not need patches.

Read the unknown OCLP documentation about changing SIP.

 

[knyght]

You cannot enable SIP on a root patched system, this would break booting.

To enable WiFi all pre 2011 systems need root patches unless the hardware has been updated.

Using OpenCore one has to change the SIP status through the OC config, which can be done using the OCLP app and rewriting a new config with corrected SIP settings.

Only change SIP if your are 100% sure you do not need patches.

Read the unknown OCLP documentation about changing SIP.

I read it. Not really understanding it completely. Any way of simplifying it?

 

[Ausdauersportler]

I read it. Not really understanding it completely. Any way of simplifying it?

How can one simplify three pictures within the docs describing all three states from completely disabled over lowered (needed for root patching) to enabled??

 

[knyght]

How can one simplify three pictures within the docs describing all three states from completely disabled over lowered (needed for root patching) to enabled??

I thought I read something about altering code. My bad. So I am set at LOWERED right now. I want to mirror the settings for DISABLED from the guide?

 

[Ausdauersportler]

I thought I read something about altering code. My bad. So I am set at LOWERED right now. I want to mirror the settings for DISABLED from the guide?

Try a PRAM reset on reboot before touching it.

The LOWERED state should work out of the box and it is the setting chosen by the OLCP app per default. As I said, there is absolutely no need to manually modify those settings. Something different must be broken in your current softwarte setup.

 

[nandor690]

anyone figured out a way to enable Touch ID with the new keyboards on intel Macs?

 

[knyght]

Try a PRAM reset on reboot before touching it.

The LOWERED state should work out of the box and it is the setting chosen by the OLCP app per default. As I said, there is absolutely no need to manually modify those settings. Something different must be broken in your current softwarte setup.

PRAM (or NVRAM) reset did not work. The Monterey install went flawlessly using OCLP. Not sure what I could have missed. Followed every step from Mr. Macintosh

 

[Ausdauersportler]

PRAM (or NVRAM) reset did not work. The Monterey install went flawlessly using OCLP. Not sure what I could have missed. Followed every step from Mr. Macintosh

Change the SIP value in the OCLP app and rebuild and rewrite OpenCore and reboot and try again.

The videos published by Mr. Macintosh do not replace the official guide. Please use the OCLP online documentation, only. As you have seen in any case of trouble a video does not respond to questions.