why most people with T2 chips can't install Mac osx tahoe or can't even reach the install page although this project is for T2 Macs & it is tahoe is already working in T1 Mac book pro 14.3???

5. September 2026 · Q&A · von @m0rtiis1

why most people with T2 chips can't install Mac osx tahoe or can't even reach the install page although this project is for T2 Macs & it is tahoe is already working in T1 Mac book pro 14.3??? & until now there is no fix of this issue in all updates of all alpha versions

Kommentare

@albert-mueller · 5. September 2026 · bearbeitet

The non-T2 MacBookPro14,3 is working fine unlike the T2 Macs because the T2 chip still requires a lot of work, despite already a lot of work already being done for T2 Macs, it requires significantly more work.
I and @Medelcartelinc are currently working on T2 Macs.
@m0rtiis1

@m0rtiis1 · 5. September 2026

The non-T2 MacBookPro14,3 is working fine unlike the T2 Macs because the T2 chip still requires a lot of work, despite already a lot of work already being done for T2 Macs, it requires significantly more work. I and @Medelcartelinc are currently working on T2 Macs. @m0rtiis1

thanks for your hard work 👍🏻 any estimated time when it will be finished we are so excited to run tahoe in our Macs due to your hard work finally there is hope from this project?

@Medelcartelinc · 5. September 2026

Hi @m0rtiis1
Just to provide a bit more technical context.
Non-T2 machines (like MacBookPro14,3) don't have the BridgeOS/Secure Enclave subsystem enforcing hardware-bound cryptographic keys on the internal drive. On T2 Macs, reaching the macOS installer requires orchestrating factory SMBIOS pass-through, APFS container keybag decryption with the T2 Secure Enclave, and patching booter compatibility without tripping BridgeOS mailbox checks.
We are making steady progress every day (diagnosing the APFS keybag behavior, aligning Booter Quirks, and validating boot paths across multiple T2 models). Because this involves deep hardware reverse-engineering and kernel compatibility, we cannot provide an exact ETA, but we are actively working on it alongside @albert-mueller to make Tahoe bootable and stable for everyone.

@m0rtiis1 · 5. September 2026

Hi @m0rtiis1 Just to provide a bit more technical context. Non-T2 machines (like MacBookPro14,3) don't have the BridgeOS/Secure Enclave subsystem enforcing hardware-bound cryptographic keys on the internal drive. On T2 Macs, reaching the macOS installer requires orchestrating factory SMBIOS pass-through, APFS container keybag decryption with the T2 Secure Enclave, and patching booter compatibility without tripping BridgeOS mailbox checks. We are making steady progress every day (diagnosing the APFS keybag behavior, aligning Booter Quirks, and validating boot paths across multiple T2 models). Because this involves deep hardware reverse-engineering and kernel compatibility, we cannot provide an exact ETA, but we are actively working on it alongside @albert-mueller to make Tahoe bootable and stable for everyone.

ok thanks for your hard work 👍🏻 I hope & wish it will be soon & don't take much time waiting 😊

@WhiteLighter78 · 5. September 2026

I read this comment and thought we should be thanking these guys instead of trying to rush them. Look, I have a T2 Macbook Pro 15,1 and a Mac Mini 8,1 as well, and I'm eagerly waiting to get Tahoe running on them too. Also a Mac Pro 6,1 and Mac Pro 5,1.

An dieser Diskussion auf GitHub teilnehmen5 Kommentare