Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Hello ,
Is it possible to install everything without any USB drive? I would like to use a partition on the internal drive?
I have a MacBook 2012 with internal ssd running Catalina and would like to upgrade to Sonoma. Please point me into the right direction, thank you
 
Video artifacts at login

Mac - MacBook Air 6,2 - mid 2013, 13", Haswell iGPU
OCLP version - 0.6.2
MacOS Monterey 12.7.1

Perhaps a cosmetic issue, but I wonder if it's to be expected. The installation completed successfully, but when booting the Mac, just before the user's login screen appears, the entire display fills up with a flash of multicolored (mainly pink) light, with both horizontal lines and vertical columms being visible. It does this for perhaps 0.2 seconds, then it disappears. I have concerns because it looks a lot like whatever I've seen in the past with a Mac that had a failed video card. Except it's not permanent.

I checked on whether root patches had been applied, and apparently, with Intel HD 5000 graphics and Monterey none are required. At least that's what OCLP says when I click on Post Install Root Patch.

I also got the Monterey volume hash mismatch error notification after initial installation. That hasn't repeated.

Thanks in advance
I saw the exact same video flash and Volume Hash Mismatch notice when clean installing today's Monterey 12.7.3 update on the same MBA 6,2 as you but using OCLP 1.3 final. DU shows nothing wrong with file system on 500 GB NVMe SSD using adapter.
 
Hello ,
Is it possible to install everything without any USB drive? I would like to use a partition on the internal drive?
I have a MacBook 2012 with internal ssd running Catalina and would like to upgrade to Sonoma. Please point me into the right direction, thank you
Yes.
Create 16GB HFS+ partition with Disk Utility.app.
Use OCLP to download the macOS installer which is downloaded to /Applications. After it's done downloading, don't choose to create the installer.
Use the createinstallmedia command in Terminal.app to overwrite the 16GB HFS+ volume. It will be named "Install macOS Sonoma".
Use OCLP to boot "Install macOS Sonoma".
https://support.apple.com/en-us/101578
 
I installed Monterey to Extenal SSD by OCLP, I named it as 'SSD500GB' when I format this SSD, now the OCLP boot picker show entry as 'SSD500GB', what can I change it to 'Monterey'? I tried to change it in Finder not effecti.
 
I installed Monterey to Extenal SSD by OCLP, I named it as 'SSD500GB' when I format this SSD, now the OCLP boot picker show entry as 'SSD500GB', what can I change it to 'Monterey'? I tried to change it in Finder not effecti.
Read the Open Core documentation regarding .disk_label and .contentDetails files.
The booter directory is usually System/Library/CoreServices - probably on the Preboot volume in one of the UUID folders.
 
There are Sonoma on Internal SSD and Monterey on External SSD, both no folders or files, I also searched these two files but found nothing, where can I find .disk_label and .contentDetails files?
 

Attachments

  • Screenshot 2024-01-05 at 17.09.31.png
    Screenshot 2024-01-05 at 17.09.31.png
    120.2 KB · Views: 52
  • Screenshot 2024-01-05 at 17.18.41.png
    Screenshot 2024-01-05 at 17.18.41.png
    59 KB · Views: 50
  • Screenshot 2024-01-05 at 17.19.27.png
    Screenshot 2024-01-05 at 17.19.27.png
    59.4 KB · Views: 52
Yes.
Create 16GB HFS+ partition with Disk Utility.app.
Use OCLP to download the macOS installer which is downloaded to /Applications. After it's done downloading, don't choose to create the installer.
Use the createinstallmedia command in Terminal.app to overwrite the 16GB HFS+ volume. It will be named "Install macOS Sonoma".
Use OCLP to boot "Install macOS Sonoma".
https://support.apple.com/en-us/101578
AWESOME, thank you so much, i am replying from my MacBookPro9,2 running Sonoma 14.2.1.
 
  • Like
Reactions: joevt
Folks, could anyone please provide me with some advice on that issue with mediaanalysisd, the danm thing eats CPU like mad.

I got macbook7,1 (yes, that old) 16 Gb ram, Monterey, and the newest OCLP which has mediaanalysisd option disabled for me.

When I attempt to follow this instruction (https://appleinsider.com/inside/mac...mediaanalysisd-from-hogging-your-cpu-in-macos) and try to disable SIP via OCLP by unchecking all the nesessary boxes in the settings, I’m stuck on boot after root patching and have to patch the system fresh from the external system disk. When I try to disable SIP by restarting os in recovery mode, all I got is a black screen. It feels like my system settings aren't right. Where do I start with all this ?
 
I modified my boot entry name, the folder is different from Internal and External storages, in my case,
The Sonoma in internal SSD on /dev/disk1s2, that is
/System/Volumes/Preboot/6EA8916B-8A05-4AE9-A30F-8D0C81A5138E/System/Library/CoreServices

and the Monterey in External SSD on /dev/disk4s2 where I have to mount /Volumes/Preboot by manual, that is
/Volumes/Preboot/E6F45525-AAD7-44DB-A9EC-55DC3F4A89CD/System/Library/CoreServices
 
Last edited:
When I run a python script on Sonoma 14.2.1, I got message as below, what can I do?
Mac OS Version is 14.2.1 and patch enabled so applying the patch
2024-01-07 22:28:45.021 Python[11227:148966] NSSoftLinking - The function ‘SLSTransactionClearWindowCornerRadius’ can’t be found in the (null) framework.
2024-01-07 22:28:45.021 Python[11227:148966] NSSoftLinking - The function ‘SLSTransactionSetWindowBoundsPath’ can’t be found in the (null) framework.
 
Last edited:
Folks, could anyone please provide me with some advice on that issue with mediaanalysisd, the danm thing eats CPU like mad.

I got macbook7,1 (yes, that old) 16 Gb ram, Monterey, and the newest OCLP which has mediaanalysisd option disabled for me.

When I attempt to follow this instruction (https://appleinsider.com/inside/mac...mediaanalysisd-from-hogging-your-cpu-in-macos) and try to disable SIP via OCLP by unchecking all the nesessary boxes in the settings, I’m stuck on boot after root patching and have to patch the system fresh from the external system disk. When I try to disable SIP by restarting os in recovery mode, all I got is a black screen. It feels like my system settings aren't right. Where do I start with all this ?
Maybe try this -
 
Does anyone has the same problem?
After I select a menu item from the menu bar, the dropdown menu changes its color to red before it disappears.
Same behavior also on the right click menu.
 
Wondering if someone can help me out. I've been using a MacPro4,1>5,1 with dual X5650s for a long time and it has been working great. Recently, I picked up a MacPro5,1 with dual X5690s for cheap and thought it would be an easy upgrade to just move my NVMe drives, video card, USB card, and wifi/BT card over to the new machine. The problem is I couldn't get the original wifi card out of the MacPro5,1 because I stripped one of the screws, so I made the mistake of booting up with the original wifi/BT. Upon loading Monterey, OCLP popped up advising me to install the Legacy wifi root patch, so I did. It did not seem to work because while I could turn on wifi, it did not find any networks. That was not a big deal because I have a CAT5e cable running to the MacPro from my router, but without functioning Bluetooth, I decided to go back to the MacPro4,1>5,1 until I can update both the wifi and Bluetooth on the MacPro5,1. BUT now after switching everything back, my wifi isn't working on my old machine either. It is doing the same thing as it was on the MacPro5,1 where it looks for and fails to find any local wifi networks. I'm pretty sure the legacy wifi root patch must be interfering, but I can't figure out how to delete it. As far as I can see, the only thing that was installed is airportd in my /usr/libexec folder but I am unable to delete it in Terminal. Trying to revert root patches in OCLP just leads to errors.

Can someone help me with how to manually remove the legacy wifi? It would be much appreciated!

EDIT: It's all good, I finally got "revert root patches" to work in OCLP and now we are back to normal!
 
Last edited:
Does anyone on Monterey use ExpressVPN? If so, can you open the app, go into preferences and click all the tabs in there? For some reason, even on clean installs of Monterey, you can't even click the Sign In button and the app crashes. This is an OCLP machine (iMac 12,2 - mid-2011 27" iMac). Just trying to see if anyone else can repro the problem.

I went back to Big Sur and now I can't get the handoff/Apple Watch unlock to work for nothing - even on clean installs of Big Sur. Frustrating. I was thinking about going back to Catalina, but I can't find a direct download for the installer. Anyone have a working URL for that from Apple?

I still have this problem. I cannot get ExpressVPN to work at all on my Late 2013 MBP on Ventura under OCLP 1.3.0. I went through many hours with ExpressVPN Support. They couldn't figure out the reason of the instant crash. I tried many versions of ExpressVPN, including very old versions. Nothing worked. I had to give up, despite my subscription to their service. Did you ever resolve this?
 
Wondering if someone can help me out. I've been using a MacPro4,1>5,1 with dual X5650s for a long time and it has been working great. Recently, I picked up a MacPro5,1 with dual X5690s for cheap and thought it would be an easy upgrade to just move my NVMe drives, video card, USB card, and wifi/BT card over to the new machine. The problem is I couldn't get the original wifi card out of the MacPro5,1 because I stripped one of the screws, so I made the mistake of booting up with the original wifi/BT. Upon loading Monterey, OCLP popped up advising me to install the Legacy wifi root patch, so I did. It did not seem to work because while I could turn on wifi, it did not find any networks. That was not a big deal because I have a CAT5e cable running to the MacPro from my router, but without functioning Bluetooth, I decided to go back to the MacPro4,1>5,1 until I can update both the wifi and Bluetooth on the MacPro5,1. BUT now after switching everything back, my wifi isn't working on my old machine either. It is doing the same thing as it was on the MacPro5,1 where it looks for and fails to find any local wifi networks. I'm pretty sure the legacy wifi root patch must be interfering, but I can't figure out how to delete it. As far as I can see, the only thing that was installed is airportd in my /usr/libexec folder but I am unable to delete it in Terminal. Trying to revert root patches in OCLP just leads to errors.

Can someone help me with how to manually remove the legacy wifi? It would be much appreciated!

EDIT: It's all good, I finally got "revert root patches" to work in OCLP and now we are back to normal!

Manually enter your WiFi credentials. The root patch does see it, but you still have to manually join a network.
 
My Monterey install on my cMP 5,1 seemed to work OK, but when I boot/restart all I get is a black screen after the Apple logo & progress bar. I used Martin Lo's OC 0.9.5, made the changes recommended in the two videos for installing Catalina/Monterey & for the monitor fix. The boot picker is there, it allows me to choose the HD but, no-go. Could be because it's installed on an NVMe? That is a project for next weekend I guess :)
 
Ok, well a few more reboots and Monterey is now accessible--sort of. It boots up, but is pretty quirky: the dock and a lot of the menus & scroll bars on the built-in apps/utilities (like System Preferences) seem to randomly freeze up while my browser works fine. Might still be a problem because of it being installed on the NVMe.
 
Last edited:
Ok, well a few more reboots and Monterey is now accessible--sort of. It boot up, but is preyy quirky: the dock and a lot of the menus & scroll bars on the built-in apps/utilities (like System Preferences) seem to freeze up while my browser works fine. Might still be a problem because of it being installed on the NVMe.
Excuse me, dont know about Martins but im on mac pro 5.1 too and with oclp 0.4.11, Monterey 12.7 runs 100% since day 1 and im on nvme too.
 
Ok, well a few more reboots and Monterey is now accessible--sort of. It boots up, but is pretty quirky: the dock and a lot of the menus & scroll bars on the built-in apps/utilities (like System Preferences) seem to randomly freeze up while my browser works fine. Might still be a problem because of it being installed on the NVMe.
try a pram reset. see if that helps. restart mac, hold option+cmmnd+P=R simultaniously for 3 chimes then let go
 
Black screen after boot picker and load screen. I have a Mac Pro 5,1 that I just used OpenCore Legacy Patcher on to update to MacOS Monterey version 12.7.2 (I'm using OCLP version 1.3.0). I had to put in my original non-metal GPU (NVIDEA GeForce 8800 GT 512 MB) so I could see the boot screen. I followed all the steps and everything ran pretty smoothly but when I removed the old GPU and put my metal card in (AMD Radeon RX 560) I see the OCLP boot picker and the apple load screen runs but once the bar fills I have a black, backlit screen in front of me. Currently I'm able to run Monterey using the old GPU but I would like the metal capabilities of my RX 560. Any ideas?
 
I could really use some help. I have an iMac 14,2 with an external SSD where I installed Monterey 12.7.1 using OCLP. It was running great for about a month, but within the last few days something changed to make everything run extremely slow (I'm assuming it's a problem with graphics acceleration?), plus I can no longer put it to sleep. I'm not sure what caused the change. I did notice at some point the macOS auto-updated to 12.7.2 (I didn't think to disable that). Can that cause these issues?

When I start up the computer I get this prompt:
OCLP has detected you're running without Root Patches, and would like to install them.
Patch detected for your system: Graphics: Nvidia Kepler

I click to apply the patches, but the patching fails.
Reason for Patch Failure (71): Error Domain=KMErrorDomain Code-71
(I can provide more details if needed)

Has anyone else ran into this? Any ideas on how to fix?
 
On a generally more positive note, having decided to stop upgrading my two Macs, I OCLPd both to Monterey and both are fine. MacBook Pro 8,2 early 2011, and iMac 12.1 mid-2011. All is working well, and I'm going to step away from the toolkit...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.