macOS 12 Monterey on Unsupported Macs Thread

[roysterdoyster]

Q: MouSSE 0.95 has a mentioning in the OCLP 0.1.7 change log
"Increment binaries:

• MouSSE (0.95 release - 06-08-2021)
• Fix SSE4,2 Emulation

In OCLP TUI 0.3.4n>#5 Patcher Settings>(...) I couldn't find an option.
Is MouSSE SSE4.2 emulation hence an integral part of OCLP, or has it been dropped? If so, can it be re-activated?

Thanks in advance

 

[joevt]

It is like you said. The suggested modifications to the installer are way over my expertise. Thank you for taking the time to answer.

Can you name the software? Is there a download link?

Q: MouSSE 0.95 has a mentioning in the OCLP 0.1.7 change log
"Increment binaries:

• MouSSE (0.95 release - 06-08-2021)
• Fix SSE4,2 Emulation

In OCLP TUI 0.3.4n>#5 Patcher Settings>(...) I couldn't find an option.
Is MouSSE SSE4.2 emulation hence an integral part of OCLP, or has it been dropped? If so, can it be re-activated?

OCLP adds MousSSE automatically. Mount the EFI partition in look in /EFI/EFI/OC/Kexts and also review the contents of the /EFI/EFI/OC/config.plist file.

 

[roysterdoyster]

Can you name the software? Is there a download link?


OCLP adds MousSSE automatically. Mount the EFI partition in look in /EFI/EFI/OC/Kexts and also review the contents of the /EFI/EFI/OC/config.plist file.

I did as per your instructions and confirm.

I will do some testing and report back.

thanks for your help, joevt

 

[foxfoobar]

May I please enquire how you got AirPlay to Mac working on 0.3.1 with Monterey 12.1?

Right now, something with 0.3.2/3 is working badly on my mini6,1 and so I’m staying on 0.3.1 for now.

I had airplay to Mac on 12.0.1, but as soon as I did the update to 12.1 it stopped working (disappeared from sharing options in System Preferences)

After the update to 12.1 I had the same problem with Airplay not showing up in SysPrefs. You need to use FeatureUnlock.kext from 0.3.3 when having installed 0.3.1. Just delete/backup the FeatureUnlock.kext and copy the one from 0.3.3 to your kexts folder (/Volumes/<EFI-Partition>/EFI/OC/Kexts/). Atleast it worked for me that way.

 

[Fernando Nakashoji]

Good news!

Monterey 12.1 (or OCLP 0.3.3 or both) bring back a working VMWare Fusion on my late `12 MacMini with Intel HD4000!

 

[mwakious]

hi guys!!!
could someone explain to me pls why i get this error every time on macbook 5,2? i have created the installer 7 times with different monterey install app every time..
ty

edit: changed usb installer and worked like a charm!
my 2 mb's 5,2 hasve now monterey! ty guys for the help!
cheers!!!

 

[Ausdauersportler]

hi guys!!!
could someone explain to me pls why i get this error every time on macbook 5,2? i have created the installer 7 times with different monterey install app every time..
ty

Try a different UBS device...

 

[roysterdoyster]

hi guys!!!
could someone explain to me pls why i get this error every time on macbook 5,2? i have created the installer 7 times with different monterey install app every time..
ty

I tried 3 different USB devices, to no avail.
K two pointed me in the direction of San Disk Cruzer USB 2.0, which worked with my machine. And FireWire800, if you happen to have that port, via OCLP 0.3.4n

 

[trinityblade]

Hi guys, I'm having an issue installing Monterey on an external SSD using OCLP (it installed fine on the internal HDD). I tried searching for a solution in this thread but couldn't find one - I'd appreciate any assistance. During the installation when it reboots, the screen goes black with no activity and it hangs. Do I need to hold down the option key during these reboots? If yes, which partition do I select to continue the installation - the data partition on the SSD? (I'm doing an upgrade from Big Sur, not a clean install.)

Thanks in advance

 

[5tracks]

After the update to 12.1 I had the same problem with Airplay not showing up in SysPrefs. You need to use FeatureUnlock.kext from 0.3.3 when having installed 0.3.1. Just delete/backup the FeatureUnlock.kext and copy the one from 0.3.3 to your kexts folder (/Volumes/<EFI-Partition>/EFI/OC/Kexts/). Atleast it worked for me that way.

Thank you for taking the time to reply. I've never done anything like that before, but will give it a try and see what happens.

Do I need to re-install 0.3.1, or can I just copy the newer kext over?
EDIT: I just copied the newer kext and rebooted and now everything works, no re-install needed! Thanks!

 

[K two]

Hi guys, I'm having an issue installing Monterey on an external SSD using OCLP (it installed fine on the internal HDD). I tried searching for a solution in this thread but couldn't find one - I'd appreciate any assistance. During the installation when it reboots, the screen goes black with no activity and it hangs. Do I need to hold down the option key during these reboots? If yes, which partition do I select to continue the installation - the data partition on the SSD? (I'm doing an upgrade from Big Sur, not a clean install.)

Thanks in advance

The macOS installer is now named 'Macintosh HD.' If that helps? ?‍♂️

 

[nandor690]

hola everyone. Im looking for anyone using the latest OCLP 0.3.3 and have Windows 10 installed. The directions on dortania GitHub say if its a dedicated hard drive I need to make it GUID. But there is also directions to use the same hard drive that Big Sur/Monterey is installed on. That drive is going to be formatted APFS.
My question is, am I missing something or will Windows 10 install on a APFS drive as long as the partition is formatted ExFAT?
thanks for any help

 

[joevt]

Hi guys, I'm having an issue installing Monterey on an external SSD using OCLP (it installed fine on the internal HDD). I tried searching for a solution in this thread but couldn't find one - I'd appreciate any assistance. During the installation when it reboots, the screen goes black with no activity and it hangs. Do I need to hold down the option key during these reboots? If yes, which partition do I select to continue the installation - the data partition on the SSD? (I'm doing an upgrade from Big Sur, not a clean install.)

Thanks in advance

It should be automatic.
https://forums.macrumors.com/thread...unsupported-macs-thread.2299557/post-30715101
How is the external SSD connected? The screen should go black - just wait a few minutes and it should continue.
Maybe change the background color to something special - not white or black or gray - so you know when OpenCore has started.

For example, without OpenCore, I use the following command to set the background color to a light orange color (see it in the Apple Startup Manager by holding the option key):

source "/Volumes/Work/Programming/ThunderboltProjects/Other/OSXOLVED/gfxutil.sh"
setnvramhex 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:DefaultBackgroundColor 7f7fff80

And in the OpenCore config.plist, I use a light blue color:

				<key>DefaultBackgroundColor</key>
				<data>/39/AA==</data>

Which was converted from hex like this:
xxd -p -r <<< ff7f7f00 | base64
And converted to hex like this:
base64 -d <<< /39/AA== | xxd -p

The four bytes are the blue, green, red components (the last byte is unused I think).

So whenever I reboot, I know when OpenCore is booting.

The macOS installer is now named 'Macintosh HD.' If that helps? ?‍♂️

It will say "Macintosh HD" for the update from 12.0.1 to 12.1 but during the installation of 12.0.1, there will be a "macOS Installer" item. Anyway, it should be automatically selected and booted by OCLP.

 

[joevt]

hola everyone. Im looking for anyone using the latest OCLP 0.3.3 and have Windows 10 installed. The directions on dortania GitHub say if its a dedicated hard drive I need to make it GUID. But there is also directions to use the same hard drive that Big Sur/Monterey is installed on. That drive is going to be formatted APFS.
My question is, am I missing something or will Windows 10 install on a APFS drive as long as the partition is formatted ExFAT?
thanks for any help

Put as many partitions of any type you like on a drive.
If you want to boot Windows using UEFI, then the disk should be GPT.
If you want to boot Windows using legacy, then the disk should be hybrid GPT/MBR.

There's no such thing as an APFS drive. It's a GPT drive with an APFS partition. Split the APFS partition in Disk Utility.app and make the new partition ExFAT. When you're installing Windows, you can tell it to format the partition as NTFS (unless you really want the partition to be ExFAT?).

If you have Windows and OCLP on the same drive, be prepared to move stuff around in the EFI partition (create a copy of the EFI folder in the EFI partition so you can have a before/after picture). You probably don't want to boot Windows UEFI without OpenCore, so it may be better to create a small FAT32 partition (200 MB), and put OpenCore there. Bless it using the Startup Manager (unless you don't have boot screen - in that case bless it in macOS using the bless command). Then Windows can have the EFI partition to itself. OpenCore won't let windows take over the boot process (it protects the NVRAM boot variables) and its files will not be affected in the new FAT partition so it will boot first during the Windows install process or during any Windows updates and keep NVRAM protected.

 

[nandor690]

Put as many partitions of any type you like on a drive.
If you want to boot Windows using UEFI, then the disk should be GPT.
If you want to boot Windows using legacy, then the disk should be hybrid GPT/MBR.

There's no such thing as an APFS drive. It's a GPT drive with an APFS partition. Split the APFS partition in Disk Utility.app and make the new partition ExFAT. When you're installing Windows, you can tell it to format the partition as NTFS (unless you really want the partition to be ExFAT?).

If you have Windows and OCLP on the same drive, be prepared to move stuff around in the EFI partition (create a copy of the EFI folder in the EFI partition so you can have a before/after picture). You probably don't want to boot Windows UEFI without OpenCore, so it may be better to create a small FAT32 partition (200 MB), and put OpenCore there. Bless it using the Startup Manager (unless you don't have boot screen - in that case bless it in macOS using the bless command). Then Windows can have the EFI partition to itself. OpenCore won't let windows take over the boot process (it protects the NVRAM boot variables) and its files will not be affected in the new FAT partition so it will boot first during the Windows install process or during any Windows updates and keep NVRAM protected.

Awesome!!! Thanks a lot for the reply. You really cleared that up for me to understand better.
I’ll be putting windows on the same ssd. When I move the EFI folder from the EFI partition to the new 200mb FAT32 partition, should I delete it from the EFI partition in case it causes any confusion?

 

[0134168]

Good news!

Monterey 12.1 (or OCLP 0.3.3 or both) bring back a working VMWare Fusion on my late `12 MacMini with Intel HD4000!

What version of VMWare Fusion?

 

[joevt]

Awesome!!! Thanks a lot for the reply. You really cleared that up for me to understand better.
I’ll be putting windows on the same ssd. When I move the EFI folder from the EFI partition to the new 200mb FAT32 partition, should I delete it from the EFI partition in case it causes any confusion?

I think you only need one copy of OpenCore.
It might be less confusing for Windows if you did not remove the EFI folder.
Just make sure you have the OpenCore in the OpenCore partition as the blessed OpenCore. You can give each OpenCore a different background color in the config.plist. Make sure the new OpenCore is the one that boots from cold boot.
Do you have boot screen? If not, does OpenCore add boot screen support for you? If not, then the background color idea isn't going to be helpful. If it is helpful, then I would choose colors that are not white, black, or gray, so you know it's OpenCore doing stuff and not gray from old Apple Startup Manager, or black from non functioning GPU, or white from something weird.

Then begin your Windows install process. Let Windows muck up the EFI partition however it likes, then when it's installed and working, you can clean things up in macOS by comparing the EFI partition with your OpenCore partition. In the EFI partition, see what bits were put in the EFI folder by Windows and just remove the OpenCore bits.

Now, if by some weird unexpected circumstance Windows decided to muck with your OpenCore partition, I suppose you could move the Windows bits to the EFI partition and restore any missing OpenCore bits in the OpenCore partition.

It's all about being aware of what was there before, what is there after, and what you want to be there.
So you need to know what's in your EFI partitions and in your bootvars before and after.
I use the mountEFIpartitions and dumpallbootvars commands from these scripts:
https://gist.github.com/joevt/477fe842d16095c2bfd839e2ab4794ff
https://gist.github.com/joevt/6d7a0ede45106345a39bdfa0ac10ffd6
If possible, I would like the dumpallbootvars command to be able to show the bootvars that are being hidden/protected by OpenCore - because the current results won't show, for example, that OpenCore is actually the currently blessed boot file if OpenCore was used during boot.

 

[roysterdoyster]

Since updating from Monterey 12.1 to 12.2b, TRIM won't stick with my internal SSD, a Samsung SSD 840 EVO 128GB

I used the terminal command

sudo trimforce enable

TRIM didn't last until next reboot, then I used Sensei.app, TRIM then held up for a number of reboots, then gone again.

Is there a solution?

 

[internetzel]

Since updating from Monterey 12.1 to 12.2b, TRIM won't stick with my internal SSD, a Samsung SSD 840 EVO 128GB

I used the terminal command

sudo trimforce enable

TRIM didn't last until next reboot, then I used Sensei.app, TRIM then held up for a number of reboots, then gone again.

Is there a solution?

You can add the following kernel patch to your OpenCore config.plist .

            <dict>
                <key>Arch</key>
                <string>x86_64</string>
                <key>Base</key>
                <string></string>
                <key>Comment</key>
                <string>Enable TRIM for SSD</string>
                <key>Count</key>
                <integer>0</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>AEFQUExFIFNTRAA=</data>
                <key>Identifier</key>
                <string>com.apple.iokit.IOAHCIBlockStorage</string>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data></data>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>Replace</key>
                <data>AAAAAAAAAAAAAAA=</data>
                <key>ReplaceMask</key>
                <data></data>
                <key>Skip</key>
                <integer>0</integer>
            </dict>

This seems to work for my SanDisk SSD (System Profiler shows TRIM as being enabled), although it's not clear whether having TRIM enabled is really beneficial for every drive type.

 

[hvds]

You can add the following kernel patch to your OpenCore config.plist .

            <dict>
                <key>Arch</key>
                <string>x86_64</string>
                <key>Base</key>
                <string></string>
                <key>Comment</key>
                <string>Enable TRIM for SSD</string>
                <key>Count</key>
                <integer>0</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>AEFQUExFIFNTRAA=</data>
                <key>Identifier</key>
                <string>com.apple.iokit.IOAHCIBlockStorage</string>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data></data>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>Replace</key>
                <data>AAAAAAAAAAAAAAA=</data>
                <key>ReplaceMask</key>
                <data></data>
                <key>Skip</key>
                <integer>0</integer>
            </dict>

This seems to work for my SanDisk SSD (System Profiler shows TRIM as being enabled), although it's not clear whether having TRIM enabled is really beneficial for every drive type.

Thank you for the XML!
I have the opposite in mind, for just trying out if TRIM is indeed beneficial for my internal Samsung QVO.
I guess I just set Enabled to false for this?

EDIT: probably this setting to false will just disable this patch, and the real change is happening in IOAHCIFamily.kext/Contents/PlugIns/IOAHCIBlockStorage.kext/Contents/MacOS/IOAHCIBlockStorage with the AEFQ... to AAAA... replacement, is it? Sorry if this is too naive, but worth learning it. - In this case, need to see with hopper disassembler where and what this is.

 

[morphina19]

Hi all,
I'm on my 3rd day of trying to update my mid 2010 imac to monterey. I was really close to a conclusion so I thought I could use some help from the community.
The Machine is a mid 2010 iMac upgraded with xeon processor, 20GB ram, SSD, nvidia quadro K1100 with flashed rom.
The iMac was running fine with 10.13.6 installed, but I wanted something newer. So I did a complete backup on my NAS with time machine and followed the guide by MrMacintosh to create a bootable USB flashdrive and perform a fresh installation of monterey.
My first installation was successfull, I got the system up and running with post instal volume paches and everything looked wonderful. Well, not everything because the migration assistant actually broke up my installation while trying to get my data back from time machine.
So I restarted with a second installation which was again successfull. This time I tried to access the backup from finder instead of using migration assistant, but I was unable to get my data back. I think the version of time machine that comes with Monterey has problems with backups performed on High Sierra, and infact when I tried to do a complete system restore from time machine with the bootable flashdrive I just created for Monterey, it miserably failed.
So this time I booted in the internet recovery (with CMD+R) and successfully restore my system to High Sierra.
Now I saved manually my data to an external drive and went for the third installation of Monterey which was UNSUCCESSFULL.
I tried many times now, and I'm stuck. The installer is doing all its things till the file copy and at the second reboot I can still see the volume called macOS Installer (the other times it showed the name of the volume) then does again the file copy, shutdown and restarts again in the installer over and over again.
I thought it could be the version of OCLP I had previously installed on my SSD, so I attended the whole installation process making sure I booted off the USB flash drive with the OCLP installed there. I even tried resetting NVRAM/PRAM but it didn't work.
I can't understand what's wrong this time.
Hope I can get some help here.
Thanks in advance, Andy

edit:
after many times rebooting the macOS installer it goes into the "Lilu dev: @ failed to obtain model information, retrying"
I read that error occured only with OCLP 0.3.1 and Lilu 1.5.6. But I am on OCLP 0.3.3... Can't understand if this has something to do with NVRAM on my mac or opencore on the USB stick that's being corrupted

 

[Kwstas]

Hey guys,
I have a problem upgrading to 12,1 Monterey through OpenCore usb stick as I have no boot screen to begin installation
My status is
-mac pro 4,1 flashed to 5,1
-Aorus 580
I also tried an old nvidia 8800 (along with 580) and installation stuck soon after the progress bar appeared.
Any ideas?
Can I try installing Monterey with a flashed 7970 and then switch back to 580?
All the Best,
K.

 

[Ausdauersportler]

Hi all,
I'm on my 3rd day of trying to update my mid 2010 imac to monterey. I was really close to a conclusion so I thought I could use some help from the community.
The Machine is a mid 2010 iMac upgraded with xeon processor, 20GB ram, SSD, nvidia quadro K1100 with flashed rom.
The iMac was running fine with 10.13.6 installed, but I wanted something newer. So I did a complete backup on my NAS with time machine and followed the guide by MrMacintosh to create a bootable USB flashdrive and perform a fresh installation of monterey.
My first installation was successfull, I got the system up and running with post instal volume paches and everything looked wonderful. Well, not everything because the migration assistant actually broke up my installation while trying to get my data back from time machine.
So I restarted with a second installation which was again successfull. This time I tried to access the backup from finder instead of using migration assistant, but I was unable to get my data back. I think the version of time machine that comes with Monterey has problems with backups performed on High Sierra, and infact when I tried to do a complete system restore from time machine with the bootable flashdrive I just created for Monterey, it miserably failed.
So this time I booted in the internet recovery (with CMD+R) and successfully restore my system to High Sierra.
Now I saved manually my data to an external drive and went for the third installation of Monterey which was UNSUCCESSFULL.
I tried many times now, and I'm stuck. The installer is doing all its things till the file copy and at the second reboot I can still see the volume called macOS Installer (the other times it showed the name of the volume) then does again the file copy, shutdown and restarts again in the installer over and over again.
I thought it could be the version of OCLP I had previously installed on my SSD, so I attended the whole installation process making sure I booted off the USB flash drive with the OCLP installed there. I even tried resetting NVRAM/PRAM but it didn't work.
I can't understand what's wrong this time.
Hope I can get some help here.
Thanks in advance, Andy

edit:
after many times rebooting the macOS installer it goes into the "Lilu dev: @ failed to obtain model information, retrying"
I read that error occured only with OCLP 0.3.1 and Lilu 1.5.6. But I am on OCLP 0.3.3... Can't understand if this has something to do with NVRAM on my mac or opencore on the USB stick that's being corrupted

You can only have a single OC version installed on your system. So please install the current version on your internal SSD and delete the USB version or vice versa.

Since your system has a real EFI boot picker you should go with the first solution and have OC installed internally. At least this is the way I handle it successfully.

 

[Ausdauersportler]

Hey guys,
I have a problem upgrading to 12,1 Monterey through OpenCore usb stick as I have no boot screen to begin installation
My status is
-mac pro 4,1 flashed to 5,1
-Aorus 580
I also tried an old nvidia 8800 (along with 580) and installation stuck soon after the progress bar appeared.
Any ideas?
Can I try installing Monterey with a flashed 7970 and then switch back to 580?
All the Best,
K.

No,

the OCLP TUI has a hardware detection and creates a config fitting to the GPU used. If you plan to use the RX 580 please boot into the latest supported macOS (Mojave) with this GPU installed, run OCLP and create the config and install it (internally or externally on the USB installer) and go ahead following the OCLP online docs.

You need a GOP vBIOS on the 580. Using the 7970 would make the installation smooth but after changing the card the system will possibly just boot into a black screen. Best case will allow you to access the system remotely using screen sharing. Here you may be able to run OCLP to generate a new RX580 aware config and write if to the boot disk.

 

[morphina19]

You can only have a single OC version installed on your system. So please install the current version on your internal SSD and delete the USB version or vice versa.

Since your system has a real EFI boot picker you should go with the first solution and have OC installed internally. At least this is the way I handle it successfully.

Ok, but until the system is installed in the internal SSD the only OCLP version I have is the one on the USB stick and I rely on that to boot the system and complete the installation.
Anyway I got out of the loop by resetting NVRAM after I got the Lily error. After that, the installer managed to complete the ramrod stuff (God knows what that means) and gave the final checkpoint successful (which I assume is what it needs to boot the system at next startup).
Writing from Monterey now... I'll let you know if I encounter any bug or whatsoever