macOS 13 Ventura on Unsupported Macs Thread

[amaze1499]

OTA update to 22C5059b using 0.5.2 on a 9,2. No issues.

 

[bloosik]

Hello,
I updated my early 2015 MacBook Pro to Ventura using Opencore Legacy Patcher. I'm surprised that everything run so good.
Nevertheless I found some issues.
First of all, Calendar widgets. It doesn't work correctly. For example, small widget with whole month view shows only days from 1st to 9th day of month. Bigger widgets are missing words "Today" and "Tomorow". And so on.
Another issue is just cosmetic issue. I turned off Verbose and Boot Picker to get seamless boot experience. And when I press power button, there's a chime sound and Apple logo appears. Then, when status bar shows up Apple logo disappears and shows up for a second just before login screen. How to make the logo visible during all boot process?
Can anyone help to fix those issues?

 

[olad]

I got me a 15-inch MBP11,4 and, using OCLP 0.5.3, upgraded its OS to Ventura successfully (spoofed to MBP14,3). No hitch along the way that a little bit of patience didn't solve. Also, I have an M1 MBA which runs alongside. The other day, I decided to take a picture of both side by side. To my surprise, the screen of the MBP (on the right) went off. Separation by 9mm (0.354-inch) reversed the black screen. I can't figure out why (I should, but at 77...). Can anyone tell me what is causing the phenomenon? I am putting it out here, because I wanted to report success upgrading the OS of the black-listed MBP11,4 to Ventura (how is blacklisting achieved, BTW?). Kudos to the OCLP developers.

 

[yellowbunny]

Pr

I got me a 15-inch MBP11,4 and, using OCLP 0.5.3, upgraded its OS to Ventura successfully (spoofed to MBP14,3). No hitch along the way that a little bit of patience didn't solve. Also, I have an M1 MBA which runs alongside. The other day, I decided to take a picture of both side by side. To my surprise, the screen of the MBP (on the right) went off. Separation by 9mm (0.354-inch) reversed the black screen. I can't figure out why (I should, but at 77...). Can anyone tell me what is causing the phenomenon? I am putting it out here, because I wanted to report success upgrading the OS of the black-listed MBP11,4 to Ventura (how is blacklisting achieved, BTW?). Kudos to the OCLP developers.

probably the magnets in the other laptop making it think the lid is closed. I’ve done this before in a lecture hall 🙈

 

[hyperions]

Hello,
I updated my early 2015 MacBook Pro to Ventura using Opencore Legacy Patcher. I'm surprised that everything run so good.
Nevertheless I found some issues.
First of all, Calendar widgets. It doesn't work correctly. For example, small widget with whole month view shows only days from 1st to 9th day of month. Bigger widgets are missing words "Today" and "Tomorow". And so on.
Another issue is just cosmetic issue. I turned off Verbose and Boot Picker to get seamless boot experience. And when I press power button, there's a chime sound and Apple logo appears. Then, when status bar shows up Apple logo disappears and shows up for a second just before login screen. How to make the logo visible during all boot process?
Can anyone help to fix those issues?

Yes, I confirm only problem calendar widget also on MacBook Pro 2012 9,2 and on another widget (time of use…I'm sorry for a possible inaccurate translation)… instead on iMac 2011 with updated metal card everything is ok

 

[bloosik]

Yes, I confirm only problem calendar widget also on MacBook Pro 2012 9,2 and on another widget (time of use…I'm sorry for a possible inaccurate translation)… instead on iMac 2011 with updated metal card everything is ok

Yes, Screen Time widget doesn't show time next to apps icons, just blank space

 

[chris1111]

Update without issue MacBookPro-retina-late-2013​

 

[hvds]

Update without issue MacBookPro-retina-late-2013​

View attachment 2122851

View attachment 2122850

Is this an MBP 11,1? Just curious as the 2nd screen shot says MBP Retina 13inch, but Early 2015.
Thanks. I want to convert an MBP 11,1 from BS to 13.1 once this is released.

 

[msjones]

Installed and running perfect on Late 2015 iMac 21.5" 1080p model from external USB 3.0 SSD.

 

[chris1111]

Is this an MBP 11,1? Just curious as the 2nd screen shot says MBP Retina 13inch, but Early 2015.
Thanks. I want to convert an MBP 11,1 from BS to 13.1 once this is released.

Yes its MacBookPro-retina-late-2013 OC SMBIOS MacBook retina early 2015

 

[kopurando]

Just upgraded late 2013 MBP Retina 15" to Ventura 13.0.1 via OCLP, no issues during upgrade, and some annoying bugs of Monterey are gone. Great job, developers, very impressive!

However, for some reason I can see com.apple.siri.embeddedspeech and suggestd running amok, eating 30%+ CPU each on both accounts even though Siri is disabled! This makes MBP constantly hot (which was not the case prior Ventura), needless to say I don't like seeing baseline CPU load about 3-5%.

Very few results on google to make sense of what's happening, anyone experienced it?

 

[chris1111]

My latest theme. is Flavours-Wonderfull 🤣 EDIT *** Site is Dark

 

[rdfincher]

This thread will be dedicated to the discussion of running macOS 13.0 on Unsupported Macs

---

Welcome to the new macOS Ventura on Unsupported Macs thread! We're eagerly awaiting for all our community developers and enthusiasts to test out the new version of macOS. Please play it by ear and only experiment with the new OS if you really know what you're doing.

We will be expanding this thread with much more information as the day goes by including known issues as well as patcher support.

macOS Ventura Compatibility

Spoiler: Intel Macs Officially Compatible With macOS Ventura

• MacBook Air (2018 and Later)
  • MacBookAir8,x
  • MacBookAir9,x
• MacBook Pro (2017 and Later)
  • MacBookPro14,x
  • MacBookPro15,x
  • MacBookPro16,x
• MacBook (2017 and Later)
  • MacBook10,1
• Mac Mini (2018 and Later)
  • MacMini8,1
• iMac (2017 and Later)
  • iMac18,x
  • iMac19,x
  • iMac20,x
• iMac Pro (2017 and Later)
  • iMacPro1,1
• Mac Pro (2019)
  • MacPro7,1

* Note: List does not include Apple Silicon Macs

Spoiler: Macs officially compatible with Monterey but have been dropped from official support in Ventura

Not officially supported in macOS Ventura, but most likely fully capable of running it

• 2015/17 MacBook Air
  • MacBookAir7,x
• 2015/16 MacBook Pro
  • MacBookPro11,4-5
  • MacBookPro12,1
  • MacBookPro13,x
• 2016 MacBook
  • MacBook9,1
• 2014 Mac Mini
  • Macmini7,1
• 2015 iMac
  • iMac16,x
  • iMac17,1
• 2013 Mac Pro
  • MacPro6,1

Spoiler: Current issues with Ventura on legacy Macs

Not officially supported in macOS Ventura, but currently not or only partly capable of running it

• Machines without AVX2 support will no longer boot without workaround**
  • If you're unsure whether or not your Mac supports AVX2, type in this command into Terminal sysctl -a | grep machdep.cpu.leaf7_features | grep -o AVX2. Getting AVX2 printed out it means your system has a (decent) chance to run Ventura in future.
  • UPDATE: A workaround has been found: Using the Rosetta 2 x64 emulation library from Apple Silicon Ventura installations, all intel processors from Core 2 Duo (Penryn) on can successfully boot the current macos 13.0 beta
• Devices with Ivy Bridge CPUs and older, basically all Macs older than Late 2013 do not support AVX2 natively. See above.
• Support of these systems would require an opcode emulator to work around it, a complex piece of software. See workaround above.
• GPU drivers from before Kaby Lake (Intel) or Polaris (AMD) are removed. Graphics drivers have been patched on all metal-supported (basically post-2012) GPUs. See this post for details.
• Even if you can boot, you might not have GPU acceleration, just frame buffer at most. Can be circumvented by applying alpha acceleration patches on metal-supported GPUs
• Non-metal GPUs have absolutely no support for graphics acceleration (see #998)

Developers will investigate re-adding support. No guarantees

Spoiler: I am new here - where can I get more information about using and installing the old Monterey patcher?

Owners of older Macs are used to the procedure...

• Just check the first post of the macOS 12 Monterey on Unsupported Macs thread

The Monterey thread/post already covers how to download the Apple installer packages and why and how it is limited to end users by Apple (Beta program), it mentions the state-of-the-art patcher (OCLP) and explains everything else worth knowing right now. Since there isn't even basic support for Ventura right now, please jump onto this train only if you have a fair amount of developing or troubleshooting skills.

Get used the reading the first post of this thread again and again, it is the most valuable source of information. It will be updated constantly.

Spoiler: List of officially unsupported machines that have shown Ventura booting ability to some degree

This is not the OLCP support llist!

This is an unconfirmed list of machines Apple dropped, but that have managed to boot Ventura
(regardless of the patches/method required to enable them, * denotes GPU metal API patch support with appropriate GPUs):

MacPro3,1 *
MacPro4,1 *
MacPro5,1 *

iMac13,1 (21.5") *
iMac14,1 (21.5") *
iMac14,3 (21.5") *
iMac15,1 (5k) *
iMac16,2 (21.5") *
iMac17,1 (5k) *

MacMini4,1
MacMini5,1
MacMini6,1 *
MacMini6,2 *
MacMini7,1 *

MacBookAir2,1
MacBookAir3,2
MacBookAir4,2 (13")
MacBookAir5,x *
MacBookAir6,1 (11") *
MacBookAir7,x *

MacBook4,1
MacBook5,2
MacBook6,1
MacBook7,1
MacBook8,1 *
MacBook9,1 *

MacBookPro4,1 (17")
MacBookPro5,x
MacBookPro6,1 (17")
MacBookPro7,1 (13")
MacBookPro8,x
MacBookPro9,2 *
MacBookPro10,1 *
MacBookPro11,1 *
MacBookPro13,3 *

...to be continued!

Even using a supported metal GPU on pre Haswell systems fails because the AMD driver stack (AMDRadeonX4000GLDriver.bundle) now uses AVX2 instructions. AVX2 use will not be limited to the kernel and drivers. You may check this link about the current situation.

For all of who have installed Ventura on any supported/unsupported devices you may use this method to check for AVX2 instructions hidden in any executables or libs. Unfortunately is is not that easy to access binaries from the kernel extensions any longer since they are not stored on disk but hidden in a big cache.

Please mention @0xCUBE in a post if a different Mac that is not on this list is confirmed to boot.

Spoiler: About (new) Apple firmware updates

All hardware still supported with Monterey but dropped from Ventura support will get Apple software and firmware updates until late summer 2024. To apply those (valuable and often necessary firmware) updates you need to install and update Monterey on your system. All firmware upgrades are bundled into the macOS updates.

The easiest way to achieve this is having an APFS container (aka volume) in parallel with your new Ventura installation. No user data needs to be copied in there. Just boot Monterey when you get an Monterey update notification and apply all updates. Note that when booting a supported OS to get firmware updates, this should be booted NOT via OpenCore, since OpenCore is typically configured so as to block firmware updates for the wrong machine, when using an unsupported OS.

You may drop (delete) this basic Monterey installation after Apple stopped delivering new updates in autumn 2024. You will not get new firmware releases.

(If you read this section after 2024 just prepare your unsupported system by installing once the latest Monterey version released by Apple including all updates to get the latest firmware update installed.)

Another method to update the firmware has been described on this site. It requires some system admin technical skills.

Spoiler: How to migrate user data on patched systems?

Bad news:

TM (time machine) restoring and MA (migration assistant) is broken on root patched systems. Do not try, system will only arrive in an unbootable and uncorrectable state after hours of restoring or transferring data.

There are two ways around this:

1. Use the OCLP USB installer and install Ventura on top of your current (supported or unsupported) macOS. This will retain your current user data. But create a final TM backup before leaving your supported macOS installation, it will be the only return ticket.

2. Simply use MA or TM before system has been root patched by the OCLP app. This is sometimes difficult to achieve when auto-patching ran before you even reached the login page. You can prevent auto-patching by creating an USB installer manually (createinstallmedia and install OpenCore manually).

The OCLP (OpenCore Legacy Patcher) for Ventura has been released. Support is experimental.

A lot of known issues exist, do not expect fixes and please do not even ask for fixes - this constant noise only ruins motivation of all people involved into this project.

A complete step by step guide is available in the ventura documentation. Please read this documentation before you start the installation process. Please understand only USB installer based installations are supported. Support is limited to legacy Apple systems only as listed within the docs.

Please retain the USB installer, it is a simple recovery tool in case your shiny new Ventura installation breaks for some reason.

OLCP gets regularly updates, please check those updates by reading the release notes and the full changelog.

 

[rdfincher]

Way back in Post #1, the spoiler "About (new) Apple firmware updates" suggested users should also install a copy of Monterey on their machines now running on Ventura. I guess that that was written before the public version of Ventura was released in October 2022, with the beta release being a temporary option until then. Now that the 13.0.1 release is current and operating well, I can't see any reason to continue with Monterey system and firmware updates, since OCLP installs of 13.0.1 will permit seamless updates released by Apple as they occur. Perhaps this has been discussed somewhere in the succeeding 98 pages of this thread, and I've missed it as a newbie. So could someone please advise if Monterey can now be discarded from machines which run successfully with Ventura 13.0.1 and later, (later). And finally, so many thanks are due to those who have developed and perfected OCLP - a superb effort! Rob - iMac 17.1.

 

[TOM1211]

Way back in Post #1, the spoiler "About (new) Apple firmware updates" suggested users should also install a copy of Monterey on their machines now running on Ventura. I guess that that was written before the public version of Ventura was released in October 2022, with the beta release being a temporary option until then. Now that the 13.0.1 release is current and operating well, I can't see any reason to continue with Monterey system and firmware updates, since OCLP installs of 13.0.1 will permit seamless updates released by Apple as they occur. Perhaps this has been discussed somewhere in the succeeding 98 pages of this thread, and I've missed it as a newbie. So could someone please advise if Monterey can now be discarded from machines which run successfully with Ventura 13.0.1 and later, (later). And finally, so many thanks are due to those who have developed and perfected OCLP - a superb effort! Rob - iMac 17.1.

I would say it’s always good practice to keep the latest supported official Apple release for your computer in case any issues arise you can always boot into it and have it as back up installing the latest supported updates will also update your efi bootrom . If you have space to keep it I would recommend it or keep latest supported for your computer on a external as a fail safe like the issue you had with Ventura earlier in your posts if you keep Monterey you would have a fail safe.

 

[MacRumors3590]

Thanks to khronokernel and Team this cMP 5,1 is running awesome!
All I need now is legacy wifi and I'll make the switch!!!

Note: I would switch now but I don't have either-net throughout my place and I don't want cat-5 wires running to 5 computers..

 

[MacRumors3590]

deleted

 

[rdfincher]

I would say it’s always good practice to keep the latest supported official Apple release for your computer in case any issues arise you can always boot into it and have it as back up installing the latest supported updates will also update your efi bootrom . If you have space to keep it I would recommend it or keep latest supported for your computer on a external as a fail safe like the issue you had with Ventura earlier in your posts if you keep Monterey you would have a fail safe.

Thanks Tom. I did download a copy of Install macOS Monterey, just in case, but I was then informed that I couldn't install it from a machine running a later version of macOS, ie Ventura. The Spoiler's suggestion was to park the Install macOS Monterey in a separate volume. Alternatively in an external drive such as Time Machine, or elsewhere as you suggest. So why couldn't I keep a backup of Ventura instead - either the bootable USB stick which I needed for the OCLP operation, or as a "Install macOS Ventura" file in a separate location? I'm just not sure why I need to go back to Monterey in the event of a potentially major problem with Ventura.

 

[makra]

So why couldn't I keep a backup of Ventura instead - either the bootable USB stick which I needed for the OCLP operation, or as a "Install macOS Ventura" file in a separate location? I'm just not sure why I need to go back to Monterey in the event of a potentially major problem with Ventura.

The security issue could be discussed, but if you have a look at the spoiler again: You simply won't get firmware updates on hardware, that is still supported by Apple, but doesn't support Ventura. Firmware will only be updated automatically in the course of an OS update, if the installer finds hardware it is meant for.

Until recently, I had Catalina volumes on those machines that support it (all from 2012). After Catalina has been dropped and no more firmware updates are to be expected, I have deleted those volumes.

 

[rdfincher]

OK that seems sensible. So that means that if a bootable copy of Monterey is stored on its own separate volume on my internal drive, any firmware upgrade which is applicable to my iMac 17.1 hardware (but not necessarily Ventura specific) will detect Monterey and then upgrade the iMac firmware - even though Ventura is stored on another volume and is in fact the start-up volume?

 

[Tockman]

OK that seems sensible. So that means that if a bootable copy of Monterey is stored on its own separate volume on my internal drive, any firmware upgrade which is applicable to my iMac 17.1 hardware (but not necessarily Ventura specific) will detect Monterey and then upgrade the iMac firmware - even though Ventura is stored on another volume and is in fact the start-up volume?

1. You learn about new security update for your last supported OS (Monterey, in your case). It may be done using Silent Knight, for instance, or reading Apple's announcements.
2. You boot into Monterey, check for updates and install them (very important detail - you have to boot directly, bypassing OCLP EFI. There many instructions on the forum, how to do that).
3. You inspect System Info to prove the version of your EFI firmware has changed up to the latest.
4. Now you boot back into Ventura and go on usual living.

 

[rdfincher]

1. You learn about new security update for your last supported OS (Monterey, in your case). It may be done using Silent Knight, for instance, or reading Apple's announcements.
2. You boot into Monterey, check for updates and install them (very important detail - you have to boot directly, bypassing OCLP EFI. There many instructions on the forum, how to do that).
3. You inspect System Info to prove the version of your EFI firmware has changed up to the latest.
4. Now you boot back into Ventura and go on usual living.

Many thanks - it's a bit more complicated than you would have thought, but I'll take your advice.

 

[fernando.c.neves]

OTA update to 22C5059b using 0.5.2 on a 9,2. No issues.

Here the same, just updated to 22C5059b.

 

[gkri]

My eternal gratitude to the devs!!! The installation experience was not smooth, but I managed to install Ventura on a macbook air 5.2 (mid 2012)!

The process:

I downloaded the OCLP v0.5.2.
I chose to download the macOS from the OCPL menu (Create macOS Installer -> Download macOS Installer -> macOS 13.0.1 (22A400) - 12.2GB). After the download finished I got the error : "No Installers found in Application folder". I am not confident with macOS disk internals, so I did not manage to find where the downloaded file went, to see what is wrong...

So I manually downloaded the macOS from this link (mrmacintosh.com/macos-ventura-13-full-installer-database-download-directly-from-apple). When the download finished, I moved the ventura installation app file from "InstallAssistant.pkg" into Application folder.

I erased the usb flash drive with disk utility, using format APFS and Scheme GUID partition map. Then I tried to flash the ventura installer into the usb flash drive using OCLP. After about 5 minutes I got the error "The bless of the installer disk failed.". So after a bit of googling I decided to flash the usb via terminal.

The flashing via terminal was successful and I used the OCPL's top menu option "Install OpenCore to disk". I chose the destination to be the efi of the usd flash drive but I got permission error 1. I googled a bit and I found how to give permission to OCPL to access drives (apple icon menu -> System settings -> Privacy and Setting (iirmc)). After giving permission the installation to efi was successful.

I booted from usb, deleted the sdd with the old ventura OS and I made a clean ventura install. At some point I got the error : "an error occurred preparing the software update". Clueless I chose to select a start disk, there was none to select. I rebooted and I found a white page showing the charging icon (no os found I guess...).

I started again the clean install (deleting again the ssd) and eventually I got the same error. I rebooted but while pressing the option button, I chose again the usb efi to boot. I had lost any hope but eventually after many automatic reboots the new Ventura showed up!!!

Soon I realised that I cannot boot without the usb stick. So I downloaded the OCPL again (clean install I had to) and I used the "Install OpenCore to disk" choosing ssd efi this time. It asked for reboot, I did it, then I removed the usb drive and I reboot again to confirm... and yes it booted without usb. I open OCPL again I check the post install root and I saw I had to apply a patch. I did it and rebooted. Now everything seems to working great!

Thanks again!!!!

 

[fernando.c.neves]

Fresh install OCLP 0.5.3 build from source.

Re-Patch of OCLP 0.5.3 and new EFI.



Notable change in speed of Ventura 13.1 Beta 4 (22C5059b) with OCLP 0.5.3 build from source.
Now my Real Mac (MacBookPro12,1) MacBook Pro Retina 13'' Early 2015 is notable faster then before. With Safari and Chrome Canary, Youtube with 1440 Resolution and 2160 (30fps) is smooth Full and windowed mode. Is faster then Monterey I guess too.

For those who doesn't know how to build from source => OpenCore-Patcher 0.5.3 build from source.app.zip

After change your EFI and Re-Patch with OCLP 0.5.3, please share if your Real Mac became faster than before with Ventura 13.1 Beta 4 (22C5059b).