This project will try to add support for T2 Macs
This project will try to add support for T2 Macs. This project will try its best to fix dortania/OpenCore-Legacy-Patcher#1167, dortania/OpenCore-Legacy-Patcher#1136, laobamac/OCLP-Mod#81. I strongly recomnmend to contribute to this project. There is already a lot of progress and now MacBook Air 2018 and 2019 can boot the installer too. And also note if you find any vulnerabilities, don't hesitate to report them via Security Advisories, however, disabling AMFI and SIP are not counted as vulnerabilities as they are necessary to bypass the minimum requirements in certain cases.
Discuss this issue on GitHub86 comments
Comments
@vytska69 · · edited
Seems everything goes well here
@albert-mueller · · edited
There is some progress on adding support for T2 Macs:macOS 26 Tahoe's installer can boot but the next issue is this:
I'm working on a fix for this, but it requires an OpenCore upgrade to 1.0.7 so it's not going to be easy to fix. Pre-alpha versions are released to test OpenCore 1.0.7 as it's not like to update your app or the operating system - many changes are needed so it works 100% properly on OpenCore 1.0.7. Thank you @vytska69 and all other alpha testers. And thanks to @vytska69 for contributing to this project!
@kodeaqua ·
Just to reporting in,
On MacBookAir8,2, stuck on language selector
Using 1.0.7 branch
@albert-mueller · · edited
Now, pre-alpha 3 is out. But it's about to fix #23 .
@albert-mueller · · edited
The issue where the MacBook Air is stuck at the language selector is likely fixed in pre-alpha 5, you can give it a try. I test it myself on a Mac mini 2018 only since the other MacBook that I have is MacBook Pro 2020 4 thunderbolt 3 ports which is natively supported and as such for the rest of the Macs I'm entirely relying on feedback to try to fix these. And my Mac mini didn't have issues detecting USB devices - my mouse was working inside the installer, WiFi and even the disk was detected.
@kodeaqua ·
Still no luck
@kodeaqua · · edited
I want to clarify if i was doing the right things or not:
is what i'm doing right? or there a miss?
Edit: funfact, i've been watching this repo for a whole day, and test whenever you doing a new commit, i want to help contributing but idk how
@albert-mueller · · edited
Unfortunately, I’ve discovered a bug (tracked here: albert-mueller/OpenCore-Legacy-Patcher-T2 #25) that is likely causing that hang. Until I can automate the fix in the patcher, you’ll need to manually inject the necessary T2 kexts using OCAT or ProperTree into your config.plist. And you’re correct—using createinstallmedia is perfectly fine; the result is the same as the OCLP internal tool.
Regarding contributing: I would love your help.
Right now, I’m in a bit of a 'desktop silo'—my patches work 100% on the Mac mini and iMac Pro, but the MacBooks are hitting that language selection wall. Since you have the hardware, you are in the best position to test HID and BridgeOS patches. If you’re up for it, try to get a verbose log (-v) during that hang. If we can identify exactly which T2 process is timing out on the Air, we can write a permanent fix together.
Are you familiar with using IORegistryExplorer? That would be our first step in seeing how your MacBook's T2 mapping differs from the Mini!
@kodeaqua ·
OK let's try, what should i give to you from IORegistryExplorer?
But I might be slow response, i have 9to5 job
@albert-mueller · · edited
Mac mini 2018:
@albert-mueller · · edited
Looking at the IORegistry on my supported T2 MacBook Pro 2020 4 thunderbolt 3 ports and looking at what issues have opened other people, it cleared out what happens: when pressing -> in the Select Language, the T2 controller kernel panics with an error UNSUPPORTED_MANTISSA_SPEED and the T2 shuts down, causing the installer to stall. An update is on the way, but I'm not sure whether this update will fix it by 100%.
@kodeaqua ·
Here's from MacBookAir8,2
AppleT2Controller:
AppleKeyStore:
SMC:
AppleSMC:
@albert-mueller
@albert-mueller ·
4.0.0 alpha 1 is out - however, it fixes kexts injection and vulnerabilities, rather than Unsupported Mentissa speed patches.
@albert-mueller ·
I will soon push an update that allows Macs affected by Unsupported Mantissa Speed bugs to be able to boot properly to macOS's installer.
@albert-mueller ·
Can you test 4.0.0 alpha 4 on your MacBookAir8,2?
@vytska69 ·
I will test on mbair8,1
@vytska69 ·
Stuck at apple logo with empty progressbar. Atleast not blue one as before
@albert-mueller ·
Where is it stuck? Waiting on , apfs_sysctl_register, pci pause: SDXC or watchdog panic?
@vytska69 ·
Idk, just after verbose shows apple logo because tries to bot and stuck. Even no mouse cursor
@albert-mueller ·
Have you make sure that:
On my Mac mini 2018, when either of those is not done, it causes this hang.
@vytska69 ·
Secure boot disabled
Sip enabled
@albert-mueller ·
You should disable SIP to get that past the Apple logo. If your Mac is stuck:
csrutil disable
csrutil authenticated-boot disable
@albert-mueller ·
Can you try this?
@vytska69 ·
Will try that
@vytska69 ·
Same happens
@albert-mueller · · edited
Oh well. And I have bad news: I just discovered a bug where security.py would apply NVRAM variables that already exist, thus end up having some boot args not once, but twice or even more times. I'm not sure if that's the culprit. Can you try booting like this also your natively supported OS via OpenCore to see whether it's an OpenCore issue or not? And if it doesn't boot, can you send then which kernel panic do you get? This will help diagnose the issue. For example, choose Macintosh HD instead of Install macOS Tahoe from the OpenCore menu. And also, did you make sure as well that it is set to Allow booting external USB media?
@kodeaqua ·
Sorry for late testing,
I have tested 4.0.0 alpha 5, it's still no luck, but there's a progress ig
it doesn't showing language picker, just a blank gray background with cursor
@albert-mueller ·
Hi! 4.0.0 alpha 6 has just been released. You can try this release. It fixes a bunch of duplicate NVRAM variables and adds additional patches.
@kodeaqua ·
Hi, thank you for your hard work! I have tested 4.0.0-alpha6, there are issues:
@vytska69 ·
Why need that gemini button at all? Just open browser and go to gemini.google.com
@albert-mueller ·
For example, you have root patching issues. And your browser Chrome doesn't open at all because of GPU accelaration issues. That button can save a lot of time. It's not a shortcut - it opens Gemini in WKWebView window inside the app.
Or you just want to ask Gemini for an error and you want to quickly copy-paste the error without first going to the web browser.
@albert-mueller · · edited
I just fixed the issue where the Ask Gemini button would overlap and when building OpenCore finishes, the popup crashes.
@albert-mueller ·
This is fixed in alpha 7.
@kodeaqua ·
It crashed again,
AttributeError: 'Constants' object has no attribute 'computer_model'
<FrameSummary opencore_legacy_patcher/wx_gui/gui_install_oc.py, line 305 in _invoke_install_oc>
@albert-mueller ·
With alpha 8, I fixed this, however, on my Mac mini 2018 with the latest patches I see hangs at Apple, so need to disable Library Validation instead of CPUID1Masking.
@kodeaqua ·
Me too, it hanging at Apple logo with progress bar ±5% for a while, then continue to gray background with cursor
@albert-mueller ·
Should be fixed in alpha 13-14, but remains to be tested.
@vytska69 ·
Not fixed on alpha14
@albert-mueller · · edited
There are significant roadblocks: #39 . Now mailbox kernel panics appear on my Mac mini 2018 when trying to boot the installer via OpenCore. Fixing this will require a bunch of time.
@albert-mueller · · edited
Pre-alpha 3 for alpha 15 is out. @vytska69 you can test this release. If you don't progress past the Apple logo, then do the following:
@albert-mueller ·
This issue should be fixed: #39 in pre-alpha 3, however it remains to be tested
@albert-mueller · · edited
@thayn3 ·
add dart=0 to boot-args if wifi and bluetooth aren't working
@albert-mueller · · edited
Pre-alpha rc for alpha 15 is out. It fixes most but not all kernel panics. The following kernel panics still happen:
#74 on MacBook Air 2018 and 2019
And while installing macOS 26 Tahoe or booting from external SSD:
#60
@albert-mueller ·
#74 on MacBook Air 2018 and 2019 should be fixed with pre-alpha rc 2 for alpha 15, but real world testing remains.
@cxknms923-maker ·
I have MacBook Pro 15-inch 2018 (Sequoia) 、iMac 4K 2017 (Tahoe) 、MacBook Air M1 (Golden Gate) . If you need any support, I am glad to help you to do some test.
@albert-mueller ·
Can you test on the MacBook Pro 2018 then?
@jamesb0nd007 ·
i have a 2018 Macbook Air. i5 CPU and while i could get it to boot to the EFI and then choose the OS after, it gets to a black screen where i have a cursor that can move but nothing else. The caps lock key does light up and turn off when i push it. This is on 4.0 alpha release 3. Any ideas?
@albert-mueller ·
#75
@albert-mueller ·
https://github.com/albert-mueller/OpenCore-Legacy-Patcher-T2/issues/109
@albert-mueller ·
#104
@kodeaqua ·
Hi @albert-mueller ,
Using 4.0.0.12041 - 4.0.0 alpha 15.7.1 got error when building OC.
Using 4.0.0.13031, got gray screen after boot.
MacBookAir8,2
Thanks
@kodeaqua · · edited
Also using 4.0.0.13031, i have to enter password many times when "Installing OC to Disk". That's so annoying ig
@nkyzr929hc-netizen ·
I have this too
@albert-mueller ·
4.0.0.13032 is out to fix this issue. You can update to this version or to 4.0.0.13040.
@albert-mueller ·
On the prompt that says An update is available, click on Update if you want to update to 4.0.0.13040.
@albert-mueller ·
With 4.0.0.13050, that will be released in the next days, I’ll try to fix this issue with the gray screen: https://github.com/albert-mueller/OpenCore-Legacy-Patcher-T2/discussions/122
@albert-mueller ·
@vytska69 Can you test the latest update?
@vytska69 ·
No, since you blocked EFI creation on 27, I’m using 27 beta on my m4 Mac
@vytska69 ·
And my MacBook air currently runs windows
@albert-mueller ·
Just fixed the issue, but you need to select your target computer, otherwise it will fail.
@vytska69 ·
Ok will try
@vytska69 ·
Still not passing apple logo. BTW I had to install official macOS Sonoma to be able to find EFI boot
@vytska69 ·
My fork boots sequoia on mb air 8,1
@albert-mueller ·
It boots to the desktop?
@vytska69 ·
I broke boot but I booted properly to the installer
@albert-mueller ·
Jaa, also das Problem mit dem MacBook Air 2019/2018 ist nicht weg. Auf meinen Mac mini 2018, es geht bis zur Installationsprogramme von macOS 26 Tahoe, aber die Partition lässt ins APFS sich noch nicht einmal formatieren, wegen AppleSEPManager.kext. Einen Umweg sieht aus, es benötigt einen Lilu-Plugin zu schreiben, die genau dieses Problem umgeht, um weiter fortzufahren mit die Installation. Für den MacBook Air 2018-2019 - ich bin noch nicht dahin bekommen. Erstmals, den Mac mini 2018 und andere MacBook Pros muss behoben werden, dann das MacBook Air 2018-2019. Sieh dieses Problem: #130 . Das Problem mit den MacBook Air 2019-2018 ist es, sie verwenden erstmals einen Intel Core M-Prozessor, die sehr empfindlich und momentan spielt nicht besonders gut mit OpenCore, mit die Zeit wird das ändern, aber das benötigt Zeit. Zweitens, das Builtin ACPI für MacBook Air 2018-2019 ist auch empfindlich, was ich seit 1 Monat herausgefunden habe, und das ACPI in Sequoia/Tahoe ist mehr strikter als den Builtin ACPI des MacBook Pro 2018-2020, Mac mini 2018 und iMac Pro 2017. Also benötigt viel Recherche für den MacBook Air 2018-2019.
Sorry for writing in German, but my English is my 3rd language. I do speak German a lot better than English.
@albert-mueller · · edited
@vytska69 You can try this kext (although it's still not fully ready), but you'll need to read the readme first and eventually fork the project and then push a pull request to the mainstream project: https://github.com/albert-mueller/SEPRetry-for-T2-Macs/tree/main
@kodeaqua ·
Any updates for MBAir8,2?
@albert-mueller ·
I have updates for the Macmini8,1 right now and they’re positive. I’m very close to reaching to reaching the macOS Setup Assistant while testing internally together with @DrDonk. For the MacBookAir8,1, I don’t have news yet.
@albert-mueller · · edited
Now Metallibs (since 4.0.0.16040) fully supports macOS 26 Tahoe. And also, PatcherSupportPkg fully supports macOS 26 Tahoe. This means, on unsupported non-T2 Macs, most stuff should be finally working. Exception: for audio, you may need to install drivers likely like this: https://github.com/albert-mueller/OpenCore-Legacy-Patcher-T2/discussions/121 .
@kodeaqua ·
The latest release has some issue on my MacbookAir8,2:
@albert-mueller ·
I have some unfortunate news: on unsupported T2 Macs, the only way to properly boot into the installer is to spoof the SMBIOS.
@vytska69 as per reports, other testers were able to reach past the language selection screen for the first time on MacBookAir8,1.
@kodeaqua
@GUTY345
@blacksabath2 ·
Does this work on t2 macbook pro 2018 15 inch?
@albert-mueller ·
@Medelcartelinc
@Medelcartelinc ·
@albert-mueller @blacksabath2
The 15-inch 2018 MacBook Pro (MacBookPro15,1 and 15,3) is fully supported by this patcher on macOS Sonoma and Sequoia. On those releases, it runs reliably with full hardware acceleration for both the Intel UHD 630 and discrete AMD Radeon Pro graphics, complete Touch Bar functionality, internal keyboard and trackpad support, and T2 bridgeOS integration.
For macOS Tahoe 26, the EFI boot chain and installer environment are functional, but post-install graphics acceleration for the dual-GPU switching setup is still under active development and testing. If you plan to experiment with Tahoe, installing onto an external drive or a separate APFS volume is strongly recommended while the remaining graphics shims are being refined.
@blacksabath2 · · edited
@albert-mueller ·
@vytska69 ·
@albert-mueller ·
@albert-mueller ·
Most T2 Macs hang at the language selection screen, @Medelcartelinc is testing and working on this.
@kodeaqua ·
Hi @albert-mueller ,
It’s been a long time since I last tried it, does it work on the MacBookAir8,2 now?
@albert-mueller ·
MacBookAir8,2 now is able to boot into the installer.
@kodeaqua
@kodeaqua ·
so is it safe to install now?
@albert-mueller ·
It gets stuck at second stage
@kodeaqua
@kodeaqua ·
okay, thanks for your hardwork!