Why not? But you have to keep in mind two things: it will be full installer, not delta file, and you'll reinstall post-install patches.
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 13 Ventura on Unsupported Macs Thread
- Thread starter 0xCUBE
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Yes. Just update like you would on a supported machine and apply root patches again when the update is finished.
Some people prefer to remove the root patches before performing an update. This will usually lead to a smaller download, but it is not a necessary thing to do.
Updated to macOS Ventura 13.0.1 using the Ventura installer app by /Applications, created using the package downloaded with GibMacOS.
Note: System Settings offered me a very long download time (Apple's servers clogged?...), otherwise I would have used this simpler method.
So, everything works fine as before and I have only a few of the known issues associated with Kepler graphics; for example Continuity Camera doesn't work and if the Music Mini Player is maximized to full screen it causes the Music app to crash.
The rest works fine and bug-free, including AirPlay (if in... Minimal ...), the Weather app and the Font Book.
Note: System Settings offered me a very long download time (Apple's servers clogged?...), otherwise I would have used this simpler method.
So, everything works fine as before and I have only a few of the known issues associated with Kepler graphics; for example Continuity Camera doesn't work and if the Music Mini Player is maximized to full screen it causes the Music app to crash.
The rest works fine and bug-free, including AirPlay (if in... Minimal ...), the Weather app and the Font Book.
Where do you get the nightly builds from? I've got some funnies on my 2014 iMac retina and want to try it. Funnies as in my external monitor has just stopped working in ventura, and some USB devices keep disappearing and reappearing.
Thanks
look under build and and run from source on main page of oclp or compile by yourself.
Direct link to nighties are not wanted by the developers.
Direct link to nighties are not wanted by the developers.
Last edited:
Not for me on 2014 retina iMac... However, I had a copy of AirServer floating around and using that, which does work.
I've updated to 13.0.1 via Software Update. I left it to do its thing and came back to my iMac shutdown (no power cuts or anything like that during the update) upon startup I got this error on login, I got prompted to reapply the post install patches by Open-core which went fine.
However every time I startup or reboot I'm now getting this error after login.
EDIT: Just tried installing the standalone 13.0.1 update again and I'm still getting this error.
Anything I can do to clear it?
However every time I startup or reboot I'm now getting this error after login.
EDIT: Just tried installing the standalone 13.0.1 update again and I'm still getting this error.
Anything I can do to clear it?
Last edited:
Update to macOS Ventura 13.0.1 OTA.
Everything working as usual.
Need to re-patch with OCLP 0.5.1 to use acceleration in Ventura 13.0.1.
Everything working as usual.
Need to re-patch with OCLP 0.5.1 to use acceleration in Ventura 13.0.1.
My MP5,1 did the same thing! Once I said Update again and it went through this process, this time I physically sat there and made sure each time it restarted, I held option and booted EFI OC 0.5.2 and then it would continue the rest automatically by itself. It restarted [I think] 4 times. Last two times it gave an estimate for time remaining. On the final reboot, it took me into Ventura 13.0.1 with no issue.
AirPlay is acting kind of funny for me. Sometimes it works, sometimes it doesn't. For example, to older AirPort Express 802.11g, no issue. To an ecobee Siri/AirPlay thermostat, no issue. But on HomePod with latest firmware, it shows it connects successfully with a checkmark in Control Center, but won't actually play thru sound. Haven't spent too much more time than this, but did notice this strange behavior.
Content Caching Update: This system behavior is occurring for me on BOTH MP3,1 & MP5,1 under both OC 0.5.1/0.5.2 and whether Ventura 13.0/13.0.1.
System Settings > General > Sharing > Content Caching is dimmed with message "This service is currently unavailable". No matter if I Force Quit in Activity Monitor the assetCache processes, reboot, erase settings, use terminal command utility for Content Caching settings, etc., it won't work. I even tried moving content cache with Option Advanced Options... setting. Moved it to different drives and then it would let me turn it on with message Starting Up... followed by same 'unavailable' message shortly after. Is anyone else who uses content caching experiencing this?
System Settings > General > Sharing > Content Caching is dimmed with message "This service is currently unavailable". No matter if I Force Quit in Activity Monitor the assetCache processes, reboot, erase settings, use terminal command utility for Content Caching settings, etc., it won't work. I even tried moving content cache with Option Advanced Options... setting. Moved it to different drives and then it would let me turn it on with message Starting Up... followed by same 'unavailable' message shortly after. Is anyone else who uses content caching experiencing this?
I do the same and got much faster MacBook Pro 9.2 on VenturaUpdate to macOS Ventura 13.0.1 OTA.
Everything working as usual.
Need to re-patch with OCLP 0.5.1 to use acceleration in Ventura 13.0.1.
When it was in in Monterey, my MBP run without any root patches but only with the VMM set (spoofless approach) in Open Core.
I tried to enable Content Cache but discovered that it cannot be enabled because my MBP was treated as a Virtual Machine.
I think that this is the reason you cannot enable the Content Cache on your machine. OCLP defaults to spoofless in SMBIOS.
I am still on 13.0 and OCLP 0.5.1 and the mini is fine using amphetamine.
Would suggest to keep using that band-aid for now. Hope there is a proper fix later on.