You don't. That's what sealed system volume is, read only, so inexperienced users won't break the system.
Your pic belongs to /Library/Desktop Pictures.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 12 Monterey on Unsupported Macs Thread
- Thread starter khronokernel
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Your pic belongs to /Library/Desktop Pictures.
I have a late 2013 iMac (14,2), and I used 0.4.11 (which I think is the last version for Monterey) to take it to 12.6.1, and I do have to install the post install patches. So I would update OCLP if I were you.
Yes, updating is a good idea, you should always study the change log / release notes coming with each new OCLP version. Writing about the new version: 0.5.0 fixed some Kepler related issues (OpenCL), so it might be worth trying on all iMacs 13,x and 14,x using a Kepler dGPU. Kepler based iMacs need at least 0.4.11 to get to 12.6 and later, as far as I remember…
thank you ,and yes it's read only.
I've tried
sudo cp Ventura\ Graphic.heic /System/Library/Desktop\ Pictures/Ventura\ Graphic.heic
cp: /System/Library/Desktop Pictures/Ventura Graphic.heic: Read-only file system
but I still think there is terminal command that can do this...
Hi, i need help running monterey on my iMac late 2013 27". I previously had it installed, however had to erase and partition my disc so now I am back to my original software. I am trying to run Monterey 12.4 (Open Legacy version 0.4.5) but get the error message
'
Failed to execute script 'OpenCore-Patcher' due to unhandled exception!
logout'
Any suggestions? Thanks
'
Failed to execute script 'OpenCore-Patcher' due to unhandled exception!
logout'
Any suggestions? Thanks
Ausdauersportler,
I have a strange glitch with OCLP 0.5.1 and my iMac15,1 running Monterey. There are 2 internal disks, an SSD 128GB and a HDD, Apple's 1TB named MacSSD and A@@le HDD, respectively. I have an external USB 3.0 enclosure with a Crucial 500MX SSD in it, but that drive is not normally connected.
I only use it as a CCC backup disk.
On a reboot, holding the Option key, I see only the MacSSD drive (Monterey 12.6.1) but after selecting the internal OCLP icon i get a drive icon named "Crucial" on the boot picker screen. (Again, the Crucial drive is not connected!)
Hitting the enter key, in turn, the system will boot up from the MacSSD drive.
Obviously the OCLP info is wrong somehow. Should I do a drive wipe and install again from a USB install drive, and migrate my data from a separate CCC backup disk (not the "Crucial" drive)?
Thanks in advance.
Edit; a disk erase via a USB installer disk, followed by a migration, and a reinstall of OCLP fixed that!
An hour well spent!
Last edited:
My iMac 21 late 2013 isn’t using Kepler dGPU iMac 14,1 with only Iris Pro 5200. I’ running Monterey without post instal patches.
The recommended approach is to update OCLP to its latest version.
Actually, what I did with my MBP which did not require any root patches in Monterey was this: I used OCLP 0.3.2 to generate the config.plist for the spoofless approach introduced in that version. After that, I kept OpenCore up to date to version 0.8.2 by downloading the new versions when they were released, compiling them, and updating the files in the EFI partition, including the config.plist based on the Differences.pdf files available with each new OC release (I know it would be easier if I had used the updated OCLP instead).
Summarizing: If you don't use Root Patches, there is a good chance you do not need to update OCLP for 12.6.1 to work.
You could use the tool BigSurmountsrw by jackluke - but use with caution, and recommended only if really needed! - which temporarily mounts the system volume as read/writeable. After that procedure the volume isn’t sealed anymore (which gave me no problems so far, as OCLP is needed anyways for these machines, just to mention it).
I wonder what Apple’s own installers will do when such a unsealed system has OTA updates waiting for it? I think it will still work, maybe it reverts to the last sealed system snapshot or creates a new one or just stays unsealed from that point on.
Last edited:
You're trying to put it into the wrong folder.
You want /Library/Desktop Pictures/ not /System/Library/Desktop Pictures/.
I am having wired ethernet connectivity issues with 12.6.1. Connecting to the Internet was fine, but SMB cannot connect. For instance my Time Machine backups over the network works fine over WiFi but never finds the backup disk over a wired connection. I upgraded to Ventura 13.0 and it was the same. This was on both a Late 2013 21.5" iMac (Kepler 750M) and a Mid-2010 27" iMac. I can only upgrade the former to Ventura of course, at this time.
They don't install. The incremental (delta) updates do not work on unsealed systems and full updates work because they are more or less "reinstalling" the OS.
Thank you !!! for providing the name of the tool. I succeeded in getting it in,
The only flaw is that it is not displayed horizontally as it is in ventura or others in monterey.
Attachments
It was working fine for me on 12.6, it decided to update itself even though I had it turned off, not sure how that changed but now on 12.6.1 it no longer works. MBP 9,2. Assertations show nothing preventing idle sleep.
Close the lid everything stays on, press sleep in the menu it locks up like its asleep but everything even the display is still on. Reset NVRAM and SMC. Tried everything, every setting and nothing has worked so far
However, the red notification badge is there after restart, on my MBP4,1. I guess, it is supposed to be that way.
The dot will reappear every time the OS checks for any type of update, obviously. You asked for a way to disable the dot, not for a way to disable Software Updates.
If you want to avoid the dot to reappear, never go in Software Updates system preferences, do a check in Terminal.
Code:
defaults read /Library/Preferences/com.apple.softwareupdate
@rehkram Did you ever resolve this problem? Having the same problem on 2021 Macmini6,2 but now on Ventura.
No, I did not, didn't have to, it resolved itself. It's a weird thing about Apple OS behahiours. Sometimes you just need to reboot a few times, and magically it works...
Hello all - been running OC 0.8.x + Monty 12.6 + cMP5,1 (2012) for a few weeks now and overall pretty stable. However, every few days, the system will start having these intermittent periods of incredibly slow performance. As time continues, the gap between these slow periods decreases until eventually I need to reboot and start the whole cycle over again.
I've tried all the usual things: activity monitor, close high-CPU apps (if any), disable Spotlight, reset PRAM, etc. Nothing has worked to prevent the pattern nor to even get the system running like it did when I first installed OC + Monty.
That is until today when I decided to try a Safe Boot which actually did nothing for me except a bit of education. I learned that the main thing SB does is clear boot caches. So I decided to just use the Onyx tool to clear the same caches and also fire off some maintenance scripts. VOILA - the system is running like Verstoppen's F1 ride (for non-racing folks - that's mighty fast).
Now everything I have ever read says that manually running maintenance scripts should never be required on a Mac. The same goes for having to manually clear out the boot caches. Nonetheless, this seems to have worked so to the community, any thoughts on this?
Is the conventional wisdom re: no need to manually run maintenance scripts or manually clearing caches just bunk? Do we really need to run these manually? Or is this just a coincidence? I know it's hard to say but because this forum has been the source of many incredible pearls of wisdom, I figured it is worth a shot.
Thanks in advance for your feedback...
I've tried all the usual things: activity monitor, close high-CPU apps (if any), disable Spotlight, reset PRAM, etc. Nothing has worked to prevent the pattern nor to even get the system running like it did when I first installed OC + Monty.
That is until today when I decided to try a Safe Boot which actually did nothing for me except a bit of education. I learned that the main thing SB does is clear boot caches. So I decided to just use the Onyx tool to clear the same caches and also fire off some maintenance scripts. VOILA - the system is running like Verstoppen's F1 ride (for non-racing folks - that's mighty fast).
Now everything I have ever read says that manually running maintenance scripts should never be required on a Mac. The same goes for having to manually clear out the boot caches. Nonetheless, this seems to have worked so to the community, any thoughts on this?
Is the conventional wisdom re: no need to manually run maintenance scripts or manually clearing caches just bunk? Do we really need to run these manually? Or is this just a coincidence? I know it's hard to say but because this forum has been the source of many incredible pearls of wisdom, I figured it is worth a shot.
Thanks in advance for your feedback...
Last edited: