macOS 12 Monterey on Unsupported Macs Thread

[K two]

I have a MacBook Pro 5,5. I had already used OCL to upgrade to Big Sur 11.6. I just now upgraded to Monterey Beta 7! Very nice. I used Monterey 12 beta 6 to install using OCL 0.2.5. It then updated to beta 7. At first, my wireless would not connect. I re-installed Open Core to my EFI partition and rebooted, then it connected. (I updated using ethernet.) Pretty peppy for this older machine! Thank you. I basically just use this laptop to test OCL, so though you might like to know. It has a 128 gig SSD and 8 gigs of memory installed.

"Pretty peppy" is a win!

 

[Tmelon]

have you tried rebuilding the OCLP?

Yep! I tried rebuilt OCLP and then did the post install patches. I assume they’re probably the same, but I tried both the GUI and the command line version of OCLP.

 

[maxsp97]

The last two days were wasted ....

Even using the latest OCLP 0.2.5 my iMac11,2 and iMac11,3 still cannot see the OTA to B7 when starting from an older version or Monterey. It will not be offered by software update at all.

Only by setting the Cpuid1Mask and Cpuid1Data the update becomes available. The newly added FirmwareFeature settings do not harm, but do not help either (checked to both ways with or without those).

Cannot tell you right now if this is an iMac11,x specific problem, did not test the iMac12,x family. Waiting for other users to report their experiences.

View attachment 1844445
​

EDIT:

1. MacPro5,1 users were able to update to Beta7 using the iMacPro1,1 SMBIOS and the VMware flag in the same way. So this confirms my observation.​
2. OCLP iMac 2012-2013 users with the iMac17,1 SMBIOS can obviously update directly (but the EFI/APPLE is filled with SMC and Firmware update files, you man safely delete these). Unfortunately not all Mac owners can simply change the SMBIOS to iMac17,1, it works for (some) iMacs.​

macOS 12 Beta 7 (21A5522h) on iMac 12,1 21.5 mid 2011 with OCLP 0.2.5
. GPU: AMD Radeon HD 6750M 512MB is working OK.
. Bluetooth: Worked.
. WIFI: Atheros 9380: 4.0.74.0-P2P is able to turn ON/OFF but not working.
Performed Post-Install Volume Patch WIFI is working but had problem screen flickering and color kept changing. My GPU is not supported.
That is great just have patching only WIFI function.
Thank you to all people created OCLP.

 

[RBSX1]

macOS 12 Beta 7 (21A5522h) on iMac 12,1 21.5 mid 2011 with OCLP 0.2.5
. GPU: AMD Radeon HD 6750M 512MB is working OK.
. Bluetooth: Worked.
. WIFI: Atheros 9380: 4.0.74.0-P2P is able to turn ON/OFF but not working.
Performed Post-Install Volume Patch WIFI is working but had problem screen flickering and color kept changing. My GPU is not supported.
That is great just have patching only WIFI function.
Thank you to all people created OCLP.

To fix color flashing use ResXtreme and change for a 8 bit color resolution

 

[figyu]

I have a MacBook Pro 5,5. I had already used OCL to upgrade to Big Sur 11.6. I just now upgraded to Monterey Beta 7! Very nice. I used Monterey 12 beta 6 to install using OCL 0.2.5. It then updated to beta 7. At first, my wireless would not connect. I re-installed Open Core to my EFI partition and rebooted, then it connected. (I updated using ethernet.) Pretty peppy for this older machine! Thank you. I basically just use this laptop to test OCL, so though you might like to know. It has a 128 gig SSD and 8 gigs of mem

If I upgrade Monterey B7 with OCLP 0.2.5, is it possible to use MBP 5,5 in everyday using? (including graphic acceleration)

 

[maxsp97]

To fix color flashing use ResXtreme and change for a 8 bit color resolution

Thank you, I did not read the patch notice, and screen is working normal now with ResXtreme applied.

 

[steverae]

Run open core patcher 0.2.5. / patch system volume again and reboot.

Yep. Confirmed on 13.2 iMac. Here are the steps I took

1) Downloaded beta 7update OTA as normal which installed fine
2) After reboot (thinking - hmm this looks strange, black dock, no transparency.... )
3) Read through the various updates on this forum
4) downloaded and installed new OCLP patcher tool
5) Followed various comments in this order :-
5.1) Build Opencore
5.2) Install Open to USB/Internal drive (choose internal drive and EFI partition the default options)
5.3) Post-Install Volume patch - patched System Volume - follow all default prompts

rebooted and all is good in the world - I've even disabled my BTFix automation script as this appears to no longer be needed and is fixed as part of the latest 0.2.5 patcher.

Thanks everyone again for keeping my iMac 13.2 alive and kicking - this is greatly appreciated and a fun journey after every update.

my final 2 cents : from beta 4 to beta 6 only issue I had personally was the BT - now it looks like Apple are disabling more legacy hardware - bring on beta 8 - or full release

 

[Pri-est]

Hi to All again!

Updated my old fart CMP 3.1 from MacOS 12.0 Beta6 o MacOS 12.0 Beta7 by OTA update from Regular Update Channel. Applyed system volume patch to System Volume for keppler GPU.

OCLP 0.3.0NB
Issues - it's damn slow! =)

Update process in attached video (RU, ENG titles will later)

 

[justperry]

Anyway, last MR beta 7 installer app is ODD. Less than 40mb in Applications folder.

Old news, I've said that just after Apple released it, many pages ago, think page 61.

 

[MacRumors3590]

Anyone having problem using Migration Assistant in B7?
It keeps logging me out over and over on my mBP 2010?

 

[qlita42]

Has anyone ever received this message?

I use Monterey Beta, which is patched with OCLP. (MacBookPro11,1)
It works comfortably for four or five hours without any problems, but that message begins to appear a few hours later.
And some apps (especially safari) go out of order, and the os becomes unstable. (Control center, date area disappears, or some settings cannot be accessed from the Preference app, etc.) This problem is completely resolved by restarting mac and repeats the message appearing few hours later.
I wonder if this is the issue of Monterey Beta itself or the issue of Monterey Beta patched with OCLP. Is there anyone who is experiencing this problem or who knows it well? (+ Is this likely to be resolved with a future OCLP patch update?) Thanks for developing a good patch
(Google Translate, please understand)

 

[trifero]

Anyone having problem using Migration Assistant in B7?
It keeps logging me out over and over on my mBP 2010?

Yes , happened to me , even with Big Sur. It just work if it is a clean installation and you use it before creating any account., before entering in the OS for the first time.

 

[hvds]

Yes , happened to me , even with Big Sur. It just work if it is a clean installation and you use it before creating any account., before entering in the OS for the first time.

Yes, it was just as you said trifero also in my case.
I‘m using clean installs very infrequently, wasn‘t necessary for Monterey which could be installed over a complete (including migration) Big Sur.

 

[MacRumors3590]

Yes , happened to me , even with Big Sur. It just work if it is a clean installation and you use it before creating any account., before entering in the OS for the first time.

Oh I see, Thanks!

 

[MacRumors3590]

View attachment 1848564

Has anyone ever received this message?

I use Monterey Beta, which is patched with OCLP. (MacBookPro11,1)
It works comfortably for four or five hours without any problems, but that message begins to appear a few hours later.
And some apps (especially safari) go out of order, and the os becomes unstable. (Control center, date area disappears, or some settings cannot be accessed from the Preference app, etc.) This problem is completely resolved by restarting mac and repeats the message appearing few hours later.
I wonder if this is the issue of Monterey Beta itself or the issue of Monterey Beta patched with OCLP. Is there anyone who is experiencing this problem or who knows it well? (+ Is this likely to be resolved with a future OCLP patch update?) Thanks for developing a good patch
(Google Translate, please understand)

I had this and had to start over to make it right.
Sorry I couldn't help more

 

[justperry]

View attachment 1848564

Has anyone ever received this message?

I use Monterey Beta, which is patched with OCLP. (MacBookPro11,1)
It works comfortably for four or five hours without any problems, but that message begins to appear a few hours later.
And some apps (especially safari) go out of order, and the os becomes unstable. (Control center, date area disappears, or some settings cannot be accessed from the Preference app, etc.) This problem is completely resolved by restarting mac and repeats the message appearing few hours later.
I wonder if this is the issue of Monterey Beta itself or the issue of Monterey Beta patched with OCLP. Is there anyone who is experiencing this problem or who knows it well? (+ Is this likely to be resolved with a future OCLP patch update?) Thanks for developing a good patch
(Google Translate, please understand)

Try a different browser for a day, see if it persists.
There's a page for this subject on Apple's website, there are no real answers there, just the suggestion to use another browser.
EDIT: The post below has a "fix"
Methinks though it is hardware-related, or the index is messed up due to hardware failure.
Test the disk with a different app than apple's provided one, for instance, Smart Utility.

 

[Ausdauersportler]

View attachment 1848564

Has anyone ever received this message?

I use Monterey Beta, which is patched with OCLP. (MacBookPro11,1)
It works comfortably for four or five hours without any problems, but that message begins to appear a few hours later.
And some apps (especially safari) go out of order, and the os becomes unstable. (Control center, date area disappears, or some settings cannot be accessed from the Preference app, etc.) This problem is completely resolved by restarting mac and repeats the message appearing few hours later.
I wonder if this is the issue of Monterey Beta itself or the issue of Monterey Beta patched with OCLP. Is there anyone who is experiencing this problem or who knows it well? (+ Is this likely to be resolved with a future OCLP patch update?) Thanks for developing a good patch
(Google Translate, please understand)

Yes, we saw this with Big Sur, too. Unfortunately the core development team of OCLP did never experienced this and so no one was able to debug it.


EDIT:
The only cure is using sudo purge in terminal app when things start to go wrong. You might even use ssh to enter the command when you cannot start new apps any longer like the terminal app.

 

[RBSX1]

I successfully upgraded a 2011 27-inch iMac with stock GPU, Bluetooth and WiFi

I just needed to fix the installer before doing the whole procedure.
I did a tutorial in Brazilian Portuguese, but with English subtitles (automatic translation from YouTube).

So far no visible bugs other than the visual glitches that have been around since Big Sur

I hope it helps

macOS Monterey com aceleração gráfica em Macs não suportados | Monterey on unsupported Macs | PT-BR

 

[ARK]

Hi there first time asking anything about installing an unsupported MacOS. I figured once it’s not supported that’s it.

So I have an iMac15,1 which is the late 2014 model. Only has a 256gb SSD. How would I go about installing Monterey once it finally releases?

I saw on the first post that this iMac is officially compatible with Big Sur but has been dropped from official support. I did notice this model is not in the potentially capable of being patched to run Monterey section as well. So what does this all mean if I wanted to try Monterey?

Again complete newbie to how this all works.

 

[davemp88]

I just wanted to say that macOS Monterey Beta 7 DID IN FACT work on my mid 2012 "unsupported" macbook pro, however even with 16gb of RAM and a 500gb SSD drive, macOS Big Sur 11.6 is EXPONENTIALLY faster than macOS Monterey Beta 7.

 

[Ausdauersportler]

Hi there first time asking anything about installing an unsupported MacOS. I figured once it’s not supported that’s it.

So I have an iMac15,1 which is the late 2014 model. Only has a 256gb SSD. How would I go about installing Monterey once it finally releases?

I saw on the first post that this iMac is officially compatible with Big Sur but has been dropped from official support. I did notice this model is not in the potentially capable of being patched to run Monterey section as well. So what does this all mean if I wanted to try Monterey?

Again complete newbie to how this all works.

Just check this guide ....

 

[davemp88]

**Also, I finally learned that if you go into number 5 on OCLP's TUI options and turn on graphics acceleration, you finally get the correct color scheme, as when I did it with just the GUI, my toolbar was appearing grey, as well as my home bar? (Bottom row of buttons). SO, word to the wise, if you're using OCLP to put macOS Big Sur on your unsupported MBP, use the TUI version and turn on graphics acceleration to get the correct color scheme, assuming your computer can handle the rendering.

 

[Ausdauersportler]

I just wanted to say that macOS Monterey Beta 7 DID IN FACT work on my mid 2012 "unsupported" macbook pro, however even with 16gb of RAM and a 500gb SSD drive, macOS Big Sur 11.6 is EXPONENTIALLY faster than macOS Monterey Beta 7.

Did you apply the root volume patches for HD4000 (and Kepler on 15") and which tests did you run to come to this conclusion

 

[davemp88]

Did you apply the root volume patches for HD4000 (and Kepler on 15") and which tests did you run to come to this conclusion

yes I ATTEMPTED the volume patching, but with my model macbook OCLP deems it unnecessary.

 

[Ausdauersportler]

yes I ATTEMPTED the volume patching, but with my model macbook OCLP deems it unnecessary.

Which version of OCLP did you use with your Monterey Beta7 experience? You might add full information to your empirical experience post like machines type, macOS version, OCLP version, etc.

It is a real struggle to get the glass back back from the attic which each of those posts.

To make it less cryptic: Only OCLP 0.2.5 offers the HD4000 (and Kepler) patching support. You might just read the release notes of the most recent versions and you might als consider to update the OLCP just in case you want to repeat your experiment.