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.
macOS works without a T2, sure, but does the Mac work without the T2? That's the main issue.

The problem with OCLP and the T2 is that we are stuck in a weird state where we have the T2, but we can't use it (out of the box, at least). Because they dropped these models, there are no longer things like Secure Boot manifests for these machines. That leaves pretending to not have a T2, which has its own problems, as a significant chunk of hardware on the Mac is handled by the T2. That leaves us having to walk a fine line between claiming we have a T2 to some parts of the OS while pretending we don't to other parts of the OS. This is more complicated than just not having (or at least saying we don't have) a T2 at all.

We have made some progress on this front, but it has been extremely unstable. My test machine would kernel panic on sleep when booting a supported OS through OpenCore. Other times, it would stall for 5 minutes, boot to the OS, spend another few minutes validating my password, and then not let me in - only fixable by booting a supported OS outside of OC. If that wasn't enough, I managed to soft-brick my test machine to the point where it refused to boot anything, supported or unsupported, OC or not, even after an NVRAM reset. I eventually had to wipe and DFU restore it.

So T2 support is really a completely different beast compared to anyt
Very interesting, thanks. Are you trying to boot off the internal SSD controlled by the T2?
 
Message from today 🙁
"Hello everyone,

In June 2025, Apple announced at WWDC25 that macOS Tahoe would be the last release for Intel Macs. Since then, we have known that Tahoe would be the last frontier for the legacy Macs that we have been supporting since Big Sur.

Since the project's future after Tahoe is uncertain, as we do not know if any Apple silicon Macs will become unsupported anytime soon, and if they are, whether developing a patcher is feasible, we have decided to stop taking new donations and cancel any recurring donations at this time. We will also refund any donations made in the last 30 days (the most our platform allows us to do).

We are still working on Tahoe support, but with multiple developers having left the team, development progress has become much slower and more perilous than before. Please remember that OpenCore Legacy Patcher is a hobby project developed by volunteers in their spare time, and our daily lives come first. We are trying our best, but Tahoe has brought significant changes (especially with recent updates), and with fewer developers and less time, we cannot commit to an OCLP update for Tahoe.

Thank you,
The OpenCore Legacy Patcher team"
 

Attachments

  • Screenshot 2026-03-22 at 19.02.08.png
    Screenshot 2026-03-22 at 19.02.08.png
    311.5 KB · Views: 205
Message from today 🙁
"Hello everyone,

In June 2025, Apple announced at WWDC25 that macOS Tahoe would be the last release for Intel Macs. Since then, we have known that Tahoe would be the last frontier for the legacy Macs that we have been supporting since Big Sur.

Since the project's future after Tahoe is uncertain, as we do not know if any Apple silicon Macs will become unsupported anytime soon, and if they are, whether developing a patcher is feasible, we have decided to stop taking new donations and cancel any recurring donations at this time. We will also refund any donations made in the last 30 days (the most our platform allows us to do).

We are still working on Tahoe support, but with multiple developers having left the team, development progress has become much slower and more perilous than before. Please remember that OpenCore Legacy Patcher is a hobby project developed by volunteers in their spare time, and our daily lives come first. We are trying our best, but Tahoe has brought significant changes (especially with recent updates), and with fewer developers and less time, we cannot commit to an OCLP update for Tahoe.

Thank you,
The OpenCore Legacy Patcher team"
WOW!!!! This sucks
 
Fair play to the devs for stopping the donations, and another huge thanks for all they've done with this project. ♥️

I guess Sequoia is still a supported OS until late next year, so fingers crossed there'll be one last OCLP miracle performed with Tahoe by then, even just for a limited number of Metal-supported/non-T2 machines. But if not, it's been a hell of a ride. 🫡
 
BTW, for a hypothetical post-OCLP era (but let’s hope there will be room for keeping it alive), there are some interesting Linux distributions for our old Intel Macs that offer a partly Mac-like experience: especially with KDE, which supports a global menu natively and also a dock (which can be easily added, after moving the main panel to the top); and some distros, like for example Ubuntu Studio (and even Ubuntu MATE), also have pre-configured macOS-like layouts for the desktop; and finally there’s also the new COSMIC desktop environment, which reminds of a Mac. Also installing Windows 11 can be done, even if it would be an unsupported configuration (no TPM). Anyway, let’s hope that at least Sequoia can be used for another year or more, with an actively developed OCLP; while Tahoe support would of course be good, especially for Xcode: as the next version will require Tahoe, as was said here. Looking forward to OCLP 2.5.0, for now… 😎🙂
 
Last edited:
This isn’t a problem with the T2 chip, but rather with support for older graphics cards. Tahoe officially runs on Intel machines with a T2 chip as well as on computers without a T2 chip – that is, on Hackintoshes, with the help of OpenCore, of course. There is therefore no logical reason why the T2 chip should prevent older Macs from running Tahoe. If we prepare an installer with the latest version of OC and the appropriate drivers, they will work, but without graphics. So they won’t work properly, but not because of the T2 chip.

The good news is that the OCLP-mod project via Laobamac is continuing now version 3.1.7 :
Thanks for the link.
Using the OCLP-mod I have been able to prepare an installer and with it to install Tahoe on my iMac 18.3 (2017).

The computer appears to be lively, excellent screen and very good sound using Boom 3D.

The only drawback so far is no WI-FI, but that is no problem for me as I use an ethernet connection for my internet.

Screenshot 2026-03-23 at 17.59.16.png
 
Thanks for the link.
Using the OCLP-mod I have been able to prepare an installer and with it to install Tahoe on my iMac 18.3 (2017).

The computer appears to be lively, excellent screen and very good sound using Boom 3D.

The only drawback so far is no WI-FI, but that is no problem for me as I use an ethernet connection for my internet.
Looks good! I don't even know if this could work with one of my Kepler 2011 iMacs (ethernet connection would be fine for the moment) but I remember one of the devs stating that the OCLP-mod app was built in developer mode, meaning "sudo without a password". Given that OCLP is running a permanent agent in the background, this would be a factor holding me back (for obvious security reasons).
 
  • Like
Reactions: jotzet
Thanks for the link.
Using the OCLP-mod I have been able to prepare an installer and with it to install Tahoe on my iMac 18.3 (2017).

The computer appears to be lively, excellent screen and very good sound using Boom 3D.

The only drawback so far is no WI-FI, but that is no problem for me as I use an ethernet connection for my internet.

View attachment 2615937
Please can you explain to me exactly by file by sign how you did?
 
macOS works without a T2, sure, but does the Mac work without the T2? That's the main issue.

The problem with OCLP and the T2 is that we are stuck in a weird state where we have the T2, but we can't use it (out of the box, at least). Because they dropped these models, there are no longer things like Secure Boot manifests for these machines. That leaves pretending to not have a T2, which has its own problems, as a significant chunk of hardware on the Mac is handled by the T2. That leaves us having to walk a fine line between claiming we have a T2 to some parts of the OS while pretending we don't to other parts of the OS. This is more complicated than just not having (or at least saying we don't have) a T2 at all.

We have made some progress on this front, but it has been extremely unstable. My test machine would kernel panic on sleep when booting a supported OS through OpenCore. Other times, it would stall for 5 minutes, boot to the OS, spend another few minutes validating my password, and then not let me in - only fixable by booting a supported OS outside of OC. If that wasn't enough, I managed to soft-brick my test machine to the point where it refused to boot anything, supported or unsupported, OC or not, even after an NVRAM reset. I eventually had to wipe and DFU restore it.

So T2 support is really a completely different beast compared to anything else.

EDIT: latter half of my post was invisible in dark mode
It's honestly rather interesting to think about, if the Intel T2 chip is already this bad, imagine when apple years later drop the M1 chips and someone (whose sane enough to even try)tries to do it, as far as I know, apple silicon devices don't have a standalone security chip, it's built into the SoC so it would be pretty hard. (Plus the iBoot boot process + a custom bootloader would be pretty hard as is...)
Either way, but if you managed to get it atleast booting it's progress, compared to last year when it was still panicking, either way, all work is respected by y'all
 
“The T2 Chip shouldn’t be a problem.”

It controls the SSD and many other core parts of the machine. The machine is designed to run with the T2 in sync. Without the T2, There is no machine.

If you’d like to know more, Research it yourself. The T2 OCLP struggles are public knowledge readily available for anyone to find.
T2 chip is pretty much a need not an optional really, as you mentioned the SSD controller runs through it, touch id, security, passwords and verifications for payments etc.. pretty much nothing works without it.. ( a developer commented his struggles with it a couple of days ago)
 
It's honestly rather interesting to think about, if the Intel T2 chip is already this bad, imagine when apple years later drop the M1 chips and someone (whose sane enough to even try)tries to do it, as far as I know, apple silicon devices don't have a standalone security chip, it's built into the SoC so it would be pretty hard. (Plus the iBoot boot process + a custom bootloader would be pretty hard as is...)
Either way, but if you managed to get it atleast booting it's progress, compared to last year when it was still panicking, either way, all work is respected by y'all
The T2 is not just a security chip it's an ARM64 coprocessor that shares a lot of features with the M series Macs including the SSD controller, the boot process and even the DFU process is somewhat similar (just restores the T2 operating system and the SSD though). The Intel side of the machine is controlled by the T2. It actually gets shutdown when the T2 OS is being updated.
 
Please can you explain to me exactly by file by sign how you did?

Please can you explain to me exactly by file by sign how you did?
1. Using the link provided by bombadier10, I downloaded the file <OCLP-Mod.pkg>.
2. I opened the file and installed <OCLP-MOD>.
3. Tahoe splits fusion drives (there is one on 18.3) so I installed Tahoe on an external SSD drive.
4. Because the text in <OCLP-Mod> is in Chinese, I also opened the OCLP patcher 2.5 as a guide. The bottom left shows the "Create macOS installer" tab, so using the same tab on the Chinese app I created a macOS installer using a 62GB USB stick and downloaded the Tahoe installer.
5. After the system rebooted I used the top left tab to Build and install Opencore on the USB stick. I rebooted and holding down the Option key installed the EFI on the installer.
6. Opening the installer during a reboot I chose the option to install Tahoe on my SSD. It proceeded normally.
 
1. Using the link provided by bombadier10, I downloaded the file <OCLP-Mod.pkg>.
2. I opened the file and installed <OCLP-MOD>.
3. Tahoe splits fusion drives (there is one on 18.3) so I installed Tahoe on an external SSD drive.
4. Because the text in <OCLP-Mod> is in Chinese, I also opened the OCLP patcher 2.5 as a guide. The bottom left shows the "Create macOS installer" tab, so using the same tab on the Chinese app I created a macOS installer using a 62GB USB stick and downloaded the Tahoe installer.
5. After the system rebooted I used the top left tab to Build and install Opencore on the USB stick. I rebooted and holding down the Option key installed the EFI on the installer.
6. Opening the installer during a reboot I chose the option to install Tahoe on my SSD. It proceeded normally.
Thank you very much, I will try as soon as possible 👍👍👍
 
1. Using the link provided by bombadier10, I downloaded the file <OCLP-Mod.pkg>.
2. I opened the file and installed <OCLP-MOD>.
3. Tahoe splits fusion drives (there is one on 18.3) so I installed Tahoe on an external SSD drive.
4. Because the text in <OCLP-Mod> is in Chinese, I also opened the OCLP patcher 2.5 as a guide. The bottom left shows the "Create macOS installer" tab, so using the same tab on the Chinese app I created a macOS installer using a 62GB USB stick and downloaded the Tahoe installer.
5. After the system rebooted I used the top left tab to Build and install Opencore on the USB stick. I rebooted and holding down the Option key installed the EFI on the installer.
6. Opening the installer during a reboot I chose the option to install Tahoe on my SSD. It proceeded normally.
Installed successfully on my late 2013 MBP 11,1 but unfortunately no support for Iris graphics, every thing seem to work fine except for WIFI and Graphics.
 
  • Like
Reactions: macinfo and olad
Message from today 🙁
"Hello everyone,

In June 2025, Apple announced at WWDC25 that macOS Tahoe would be the last release for Intel Macs. Since then, we have known that Tahoe would be the last frontier for the legacy Macs that we have been supporting since Big Sur.

Since the project's future after Tahoe is uncertain, as we do not know if any Apple silicon Macs will become unsupported anytime soon, and if they are, whether developing a patcher is feasible, we have decided to stop taking new donations and cancel any recurring donations at this time. We will also refund any donations made in the last 30 days (the most our platform allows us to do).

We are still working on Tahoe support, but with multiple developers having left the team, development progress has become much slower and more perilous than before. Please remember that OpenCore Legacy Patcher is a hobby project developed by volunteers in their spare time, and our daily lives come first. We are trying our best, but Tahoe has brought significant changes (especially with recent updates), and with fewer developers and less time, we cannot commit to an OCLP update for Tahoe.

Thank you,
The OpenCore Legacy Patcher team"
how interesting this comes right after someone accused them of scammers to the openinitiative
 
how interesting this comes right after someone accused them of scammers to the openinitiative
Yeah it was seen better to just end it especially cause Tahoe release is looking more uncertain now with sudden dev departures and such. Dhinak answered the person accusing on the Discord server and clarified things. As it says, work will still continue on Tahoe but it's not yet certain whether a release can be made which is why it's better to not accept donations anymore going forward.

OpenCollective is also pretty strict about that the money is being used only for the project related things, they want reasons and receipts which means the devs could not use the money for things outside of the project. If someone bought something that OpenCollective doesn't approve of, then OpenCollective doesn't reimburse the money and the money goes out of the dev's own pocket. This was one of the reasons why OpenCollective was chosen because money related things can easily get muddy, originally the devs didn't like having money donations at all but due to wishes of multiple people they sought out the best option.

The team has also been always clear that it's a hobby project and all estimates have been "rough estimates", it is not a company or anything behind the project but just few devs in their free time.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.