Since the T2 has been out since 2018, it should have been able to be patched by now.
How long did we wait for the Xbox one ? 13 years lol
Since the T2 has been out since 2018, it should have been able to be patched by now.
Very interesting, thanks. Are you trying to boot off the internal SSD controlled by the T2?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
WOW!!!! This sucksMessage 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"
Not a huge shock to be honest. I admire their honesty and their decision not to take further donations and refund recent donations.WOW!!!! This sucks
Interesting example. The Xbox SoC actually contained ARM cores that have a similar function to the T2 in the Mac. Modern Playstations also have an ARM coprocessor with similar functions.How long did we wait for the Xbox one ? 13 years lol
I was, until having to DFU and subsequently losing my 4 macOS installs. Of course, no actual data was lost, but it was really annoying and a lot of time wastedVery interesting, thanks. Are you trying to boot off the internal SSD controlled by the T2?
Thanks for the link.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 :
![]()
Releases · laobamac/OCLP-Mod
A mod version for OCLP,with more interesting features. - laobamac/OCLP-Modgithub.com

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).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.
Please can you explain to me exactly by file by sign how you did?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
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...)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
Not even the 2016 & 2017 models ( one s and one x) but hey it's progressHow long did we wait for the Xbox one ? 13 years lol
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)“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.
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.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
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>.Please can you explain to me exactly by file by sign how you did?
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.
Isn't checkm8 firmware independent? It uses an exploit in the A7-A11 BootROM.I know. The latest ibridgeOS, is not supported either by checkm8. Maybe they finally managed to patch the unpatchable security exploit.
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.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.
Do you mean the OCLP mod 2.5.0 file always from Labomac, or where can I find this file?4. Because the text in <OCLP-Mod> is in Chinese, I also opened the OCLP patcher 2.5 as a guide.
how interesting this comes right after someone accused them of scammers to the openinitiativeMessage 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"
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.how interesting this comes right after someone accused them of scammers to the openinitiative
Do you mean the OCLP mod 2.5.0 file always from Labomac, or where can I find this file?
thank you