macOS 12 Monterey on Unsupported Macs Thread

[Ausdauersportler]

Will universal control work on a macbook pro 2011 13 late with this card?

BCM94331PCIEBT4AX WiFi Airport Bluetooth Card for Macbook Pro A1278 A1286 A1297 | eBay

WiFi Bluetooth Card BCM943224PCIEBT for Apple Unibody Macbook Pro 13" A1278 15" A1286 17" A1297 2011. Macbook Pro 17" A1297 2011. (This WIFI BT Card just for unibody macbook Pro A1278 A1286 A1297 2011 Models ).

www.ebay.com

Check the FeatureUnlock GitHub page yourself. I would go with the fully supported BMC94360xxx modules.

 

[sigbals]

Check the FeatureUnlock GitHub page yourself.

I had already checked

I just wanted confirmation

Thanks for reply

Universal Control on unsupported Macs | OpenCore Legacy Patcher

MacBookPro8,1

Wi-Fi 4 + BT 2.1 EDR

Upgrade to BCM94331

BCM94331PCIEBT4AX WiFi Airport Bluetooth Card for Macbook Pro A1278 A1286 A1297 | eBay

WiFi Bluetooth Card BCM943224PCIEBT for Apple Unibody Macbook Pro 13" A1278 15" A1286 17" A1297 2011. Macbook Pro 17" A1297 2011. (This WIFI BT Card just for unibody macbook Pro A1278 A1286 A1297 2011 Models ).

www.ebay.com

 

[walterwhite1]

Just put put Monterey on a Mac mini mid 2011 with 16gb memory and 870 evo. However I've got issues. I went for a fresh install - so went to efi usb OCLP, utilities, erased the drive, installed Monteray. So fine so far. On first boot, the OCLP identified it was installed and asked if I wanted to install this on the internal drive. I said yes and selected the EFI partition and rebooted. It lets me boot into the OpenCore efi hard drive boot, Open Core is there in apps but doesn't open. I've downloaded again, but when I open it just doesn't load at all. I've now tried the terminal version, fails on load stating:

/Contents/MacOS/OpenCore-Patcher ; exit;

- Loading...

Traceback (most recent call last):

File "OpenCore-Patcher.command", line 6, in <module>

File "main.py", line 17, in __init__

File "main.py", line 50, in generate_base_data

File "defaults.py", line 185, in probe

File "global_settings.py", line 16, in __init__

File "global_settings.py", line 44, in convert_defaults_to_global_settings

File "pathlib.py", line 1242, in open

File "pathlib.py", line 1110, in _opener

PermissionError: [Errno 13] Permission denied: '/Users/Shared/.com.dortania.opencore-legacy-patcher.plist'

[721] Failed to execute script 'OpenCore-Patcher' due to unhandled exception!


What am I doing wrong and why wont OCLP install again when I click on the download? Totally confused! Thanks

 

[Ausdauersportler]

PermissionError: [Errno 13] Permission denied: '/Users/Shared/.com.dortania.opencore-legacy-patcher.plist'

[721] Failed to execute script 'OpenCore-Patcher' due to unhandled exception!

What am I doing wrong and why wont OCLP install again when I click on the download? Totally confused! Thanks

PermissionError: [Errno 13] Permission denied: '/Users/Shared/.com.dortania.opencore-legacy-patcher.plist'

Try to delete the file manually from Terminal in advance using:

rm /Users/Shared/.com.dortania.opencore-legacy-patcher.plist

(copy and paste and confirm command by pressing enter key)

 

[walterwhite1]

PermissionError: [Errno 13] Permission denied: '/Users/Shared/.com.dortania.opencore-legacy-patcher.plist'

Try to delete the file manually from Terminal in advance using:

rm /Users/Shared/.com.dortania.opencore-legacy-patcher.plist

(copy and paste and confirm command by pressing enter key)

Thanks, thought I would try it against to see if I get more luck. Doing a fresh install now. Is there anything obvious I've done wrong?

 

[DragenFi]

If you are going to put Monterey on this machine, you may want to consider keeping your Catalina install and putting Monterey on a separate partition or separate volume (if a separate volume instead of partition for OCLP Monterey is also possible—I'm not sure). Until later this year, machines that natively run Catalina like the MBP 9,2 will still be getting firmware updates sometimes when you do the Catalina security update. You will want to receive those firmware updates bundled with the security updates. Up-to-date firmware will help your machine run [OCLP Monterey] as well as possible.

You don’t need to install Big Sur first, per my knowledge.

I would do a clean install of Monterey on a separate partition (or a separate volume if that is good too—you can double check the partition vs. volume issue in the docs, I imagine.)

Thank you for your reply, I was going to have a USB Drive with a Catalina Installer on and use that to boot from to update my firmware, but this sounds a simpler way to get the updates.

I think I will back up all my data and do a fresh Catalina install and then create the separate partition /or volume for Monterey.

Would 30gb be enough for the Catalina install partition?

 

[Tockman]

After updating to Beta 3 (OCLP 0.4.6), on iMac 13.2, successful reboot and login, installing post-install patches and final reboot, the posinstall doesn't work. No graphic acceleration. I received these 2 messages. After applying the root patches, as suggested by OLCp, it still doesn't work. I need some help please.

I reverted to Beta 2, and all is working just like before. It's OS-related problem.

 

[walterwhite1]

Could you look in your accumulated box of tricks and see if there is anything that can help:
1. Update to 0.4.6 from 0.4.5 on my ancient 2011 MBP8,2? Tried 3 nvram resets, reran the nvram code to disable the discrete and problematic Radeon gpu again, & downloaded the new 0.4.6 version. It will not run, just bounces like Hamilton's F1 car, and then settles down. Doesn't even throw up any apologies. I think (not sure) that is because the nvram resets didn't clear out the 0.4.5 installed on the EFI partition of the 128GB Apple SSD. The post-install root patches were applied using 0.4.5.
2. Also, the bluetooth absolutely refuses to connect to either a battery magic mouse or a white older rechargeable magic mouse. Using the somewhat erratic trackpad with my old shacking hands is driving me nuts!
I was hoping the 0.4.6 update would help with these issues, but I am stuck out in the middle of the pond without a paddle!
'Tis enough to make me want to buy a new MacBook Air!!

Seems similar to mine. I've got a Mac mini 5,1. On first boot of usb, OpenCore automatically detects it's not installed on the hard drive and offers to install. However once done after rebooting via efi SSD the OpenCore application just doesn't open and bounces up and down. When you try to reinstall it, it does nothing apart from bounce up and down. Just reinstalling now to try again. Love the Hamilton reference lol!

 

[RogueB]

I reverted to Beta 2, and all is working just like before. It's OS-related problem.

I installed Monterey 12.5 beta 3 on a MacBook Pro 5,2 (2009, 17 inch, C2D, Evo SSD) and installation went without a problem. After I applied patches (OCLP 0.4.6) I was able to routinely login into a working OS 12.5 Beta3.
I have video acceleration and no discernible issues

However, same installation onto iMac 13,2 (late 2012, quad i7) resulted in login window loop as described in your post.
I used 0.4.6 release and 0.4.7n, and neither resolved the problem.

Allowing auto- login made no difference; login window loop persisted.

Given above information, from two disparate systems (and other posts), it would appear (no hard proof) that OCLP can not fully compensate for changes in Monterey 12.5 beta3, particulalrly when installing OS on certain 2012 build machines.

Hope this information may be of help.

 

[walterwhite1]

Thanks, thought I would try it against to see if I get more luck. Doing a fresh install now. Is there anything obvious I've done wrong?

Ok so it's now working perfectly. Did a fresh install, deleted that line and installed to disk. Opencore now loads off the SSD, rather than not loading at all. Wonder why none of the guides mention deleting
rm /Users/Shared/.com.dortania.opencore-legacy-patcher.plist

 

[Ausdauersportler]

Ok so it's now working perfectly. Did a fresh install, deleted that line and installed to disk. Opencore now loads off the SSD, rather than not loading at all. Wonder why none of the guides mention deleting
rm /Users/Shared/.com.dortania.opencore-legacy-patcher.plist

This was/is a local problem. Something must have changed the access flags in a way a normal user could not change the file there.

 

[vendini]

However, same installation onto iMac 13,2 (late 2012, quad i7) resulted in login window loop as described in your post.
I used 0.4.6 release and 0.4.7n, and neither resolved the problem.

Same configuration (iMac 13.2 late 2012 quad i7) and exactly the same problem

 

[hvds]

This was/is a local problem. Something must have changed the access flags in a way a normal user could not change the file there.

I had that a long while ago when switching between TUI and GUI of a version built from source.

 

[Taipan]

Hi!

After upgrading my Mac Pro 5,1 to Monterey, I noticed that my Bluetooth module (BCM20702, IIRC, that I had added for Handoff support in Mojave) was no longer supporting Handoff/Airdrop. So I bought a new module, BCM20703A2, which should work in Monterey. It must be installed correctly, since it is recognized and everything works in Mojave.
But now in Monterey it's not recognized at all. System Report says "Chipset: BCM_4350C2", but status "Off" and address "NULL". I can't even turn Bluetooth on. For some reason, basic functions of my Magic Trackpad work nevertheless, but no "tap to click" etc, since Trackpad preferences cannot be opened, and of course no Handoff.

Is there something I can do about this? This model should work, shouldn't it? Do I need to reinstall Monterey with the card present (although I didn't have to do that in Mojave)?

Edit: I have updated OCLP from 4.5 to 4.6, which at first led to loss of even the basic BT functions (and sleep mode). I then did another NVRAM reset, and BT seems to work now, including handoff. It's a little strange that System Information is missing the usual info about BT version, handoff support etc., but as long as it's working, that's fine with me.

 

[walterwhite1]

This was/is a local problem. Something must have changed the access flags in a way a normal user could not change the file there.

Yep surprised this has been missed. Anyway all good now, really appreciate the help sorting this on the thread here.

 

[thet4nk1983]

Hi All,

Mac mini 2012 I7 16gb, Installed Monterey 12.4 using latest OLCP TUI on 12/6 all working fine post install script running no issues or problems graphics nice and smooth. However after a couple of days booted up the mac to be met by the no entry sign which goes into a loop of booting.

Wondered if anyone else has had this issue and if there is any known fix?

 

[webg3]

Hi All,

Mac mini 2012 I7 16gb, Installed Monterey 12.4 using latest OLCP TUI on 12/6 all working fine post install script running no issues or problems graphics nice and smooth. However after a couple of days booted up the mac to be met by the no entry sign which goes into a loop of booting.

Wondered if anyone else has had this issue and if there is any known fix?

You need to install OpenCore on the EFI internal partition, and when powering on the system, hold Option key, then select EFI boot and hold Command key to mark as launcher, from there whenever power on or restart, it will proceed correctly .

 

[Aston441]

Not really. I've check that today on windows 10 and disk is not visible. Now I don't know is that disk problem or case. I've order new better case and will see. That Ugreen one start's heating after plug in. I hope that didn't burn the disk.

Personally, I would suspect bad disk. I’ve been there. Many times. There’s no more quality control testing, it went away decades ago. Cost analysis found it’s cheaper to do warranty exchanges than test units at the factory. Just exchange it.

 

[rehkram]

Would 30gb be enough for the Catalina install partition?

The bare bones Catalina install volume I created on external SSD for getting firmware updates currently occupies 34 GB, with 7.2 GB allocated for unmounted 'other volumes'. So you'd better make it bigger, maybe 50 GB. I did a clean install and just created an admin login. Did not migrate any data or apps other than installing SilentKnight.

 

[Vacusuck]

Anyone help me with this problem? I'm running Monterey 21G5046c on a 2012 iMac13,1 in safe mode because when I try to install the post install patches onto an external drive, I get the following:

An error occurred!
0:188: execution error: Volume on disk2s1 failed to mount
If you think the volume is supported but damaged, try the "readOnly" option
(1)

Traceback (most recent call last):
File "gui_main.py", line 747, in <lambda>
File "gui_main.py", line 794, in install_oc_process
File "install.py", line 180, in install_opencore
File "utilities.py", line 556, in check_boot_mode
File "plistlib.py", line 883, in loads
File "plistlib.py", line 869, in load
plistlib.InvalidFileException: Invalid file

I can mount to the external drive no problem in finder. This also happens with the TUI. Note: the reason I booted to safe mode is because the login screen locks up and eventually shows a black screen, then back to the login screen. Safe mode allows me to get past that problem. However, even if I install the post install patches on the internal drive (SSD), it does not fix the login problem. I'm running OCLP TUI and GUI 0.4.5 with 22G5046c and have never had a problem this entire time with Monterey on this iMac.

 

[Tockman]

Anyone help me with this problem? I'm running Monterey 21G5046c on a 2012 iMac13,1 in safe mode because when I try to install the post install patches onto an external drive, I get the following:

An error occurred!
0:188: execution error: Volume on disk2s1 failed to mount
If you think the volume is supported but damaged, try the "readOnly" option
(1)

Traceback (most recent call last):
File "gui_main.py", line 747, in <lambda>
File "gui_main.py", line 794, in install_oc_process
File "install.py", line 180, in install_opencore
File "utilities.py", line 556, in check_boot_mode
File "plistlib.py", line 883, in loads
File "plistlib.py", line 869, in load
plistlib.InvalidFileException: Invalid file

I can mount to the external drive no problem in finder. This also happens with the TUI. Note: the reason I booted to safe mode is because the login screen locks up and eventually shows a black screen, then back to the login screen. Safe mode allows me to get past that problem. However, even if I install the post install patches on the internal drive (SSD), it does not fix the login problem. I'm running OCLP TUI and GUI 0.4.5 with 22G5046c and have never had a problem this entire time with Monterey on this iMac.

This one and lower. It's a problem with Beta 3. Developers are aware.

 

[davidlv]

This one and lower. It's a problem with Beta 3. Developers are aware.

There is an update to 0.4.7 out.

Release 0.4.7 · dortania/OpenCore-Legacy-Patcher

This release is a simple bug fix, see 0.4.6's release notes for previous changes and noteworthy updates: With the initial developer beta of macOS Ventura, we've seen many drastic changes to the pa...

github.com

 

[Vacusuck]

There is an update to 0.4.7 out.

Release 0.4.7 · dortania/OpenCore-Legacy-Patcher

This release is a simple bug fix, see 0.4.6's release notes for previous changes and noteworthy updates: With the initial developer beta of macOS Ventura, we've seen many drastic changes to the pa...

github.com

I reverted back to Beta 2 and have no problems now. I have no idea if 0.4.7 works around this, but there's something goofy with 21G5046c OCLP does not play nice with.

 

[Vacusuck]

Also, something interesting about this, I was able to update my 2009 Core2Duo Mac mini to Beta 3 without any problems at all. I was using 0.4.5, installed the post install patches and it's up and running without a problem. So, something weird with the iMac13,1 here.

 

[Tockman]

Also, something interesting about this, I was able to update my 2009 Core2Duo Mac mini to Beta 3 without any problems at all. I was using 0.4.5, installed the post install patches and it's up and running without a problem. So, something weird with the iMac13,1 here.

13,2, to be precise