Install issues MacBook Pro 15,1

June 28, 2026 · by @jimmymcgeepizza

Hello, I have been trying to get this working but the only method I could get it to the first steps of the installer was with spoofing.
Without spoofing, the MacOS tahoe recovery menu says that my mac is unsupported.
I tried again, but spoofing a MBP16,1 on my MBP15,1 but at the 18 minute mark on the recovery menu, I get the error "permission denied" which is likely caused by the spoofing, since the spoofing also prevents me from formatting the drive, or installing to another volume other than the main one.

Comments

@albert-mueller · June 28, 2026

What you can try is outside the installer. Try to boot the last natively supported macOS version via OpenCore, then if Tahoe update appears, click on Restart Tonight, then go to OpenCore Legacy Patcher T2 once it says it’s ready for restart and click on Patch Tahoe Stage 2 if it appears. Only then click Restart once done and see if this works.

@albert-mueller · June 28, 2026

I haven’t tried that out yet since this feature is limited to that MacBook Pro only for now, a broader rollout is planned - I have only Mac mini 2018.

@jimmymcgeepizza · June 28, 2026

Unfortunately I was unable to access the last version supported through the opencore efi, because I was having issues entering my password, even though file vault is off.

@jimmymcgeepizza · June 29, 2026

I'm going to rebuild the EFI and try again with this method

@GUTY345 · June 29, 2026

Now script state2 is just a test and the results are still unable to solve the problem. An error occurred preparing the software update.

@GUTY345 · June 29, 2026

Suggest now that I have deleted script state2. I'm trying to find a way to solve this problem.

@GUTY345 · June 29, 2026

There is still another problem that can't be solved about partitioning. Therefore, in the test division, I used external ssd to test.

@albert-mueller · June 30, 2026 · edited

Okay, 4.0.0 alpha 15.2 is no longer available outside source code as it was adding only this function, and as it seems, it doesn’t work.

@albert-mueller · July 2, 2026

@GUTY345 · July 2, 2026

You can successfully install macos tahoe on macmini 2018, right?

@albert-mueller · July 2, 2026

You can successfully install macos tahoe on macmini 2018, right?

Not really, but it shows Tahoe in Apple Software Update as shown, it's still a step foreward.

@albert-mueller · July 2, 2026

#101 - I found this issue while I was looking on how to fix the APFS issue.

@albert-mueller · July 2, 2026 · edited

https://share.gemini.google/fFgz9QfIHf62 - Gemini thinks it's APFS container auth issue.

@albert-mueller · July 2, 2026

And to fix overall stability and fix the issue where patches are injected where Replace and Find length differs, I'm implementing a change to prevent this and instead - abort. For example:

@GUTY345 · July 2, 2026

Do you have any suggestions for both problems encountered? I still can't find a solution.

@albert-mueller · July 2, 2026 · edited

Do you have any suggestions for both problems encountered? I still can't find a solution.

Not yet, I'm still searching as well. While I was searching I found out that the bytes length for Find and Replace on some patches aren't the same. Some have issues where the length of Find and Replace bytes and is well documented in another fork demonstrating the issue. They didn't fixed it, rather than documented it.

@albert-mueller · July 2, 2026

Do you have any suggestions for both problems encountered? I still can't find a solution.

The issue with the Replace and Find bytes length sizes that differ may have been the problem, but it requires rewriting all patches for T2 Macs once again. It will take time and at least this will be fixed in the next alpha.

@albert-mueller · July 3, 2026

#104 - WhateverGreen causes issues even with the latest 1.7.1, the only workaround is to make a fork and do the necessary changes so it works properly on macOS 26.

@albert-mueller · July 20, 2026

#125

@albert-mueller · July 25, 2026

This issue is related to this one: #130

@GUTY345 · July 27, 2026

My Frok is currently experiencing an issue where the language selection window is frozen. I'm working urgently to fix it, but I haven't identified the exact cause yet.

@GUTY345 · July 27, 2026

@Richard-Hanus · September 6, 2026

So is it working on MacBookPro15,1?

@jimmymcgeepizza · September 6, 2026

I'll give it another go right now

@damian2601dy · September 11, 2026

MacBookPro15,1 (J680AP): RestrictEvents 1.1.6 kernel panic without spoofing; AppleKeyStore selector 84 failure with spoofing

Hardware / environment

Model: MacBookPro15,1 (2018, Coffee Lake, T2)
Bridge model: J680AP
macOS Tahoe: 26.5.2, build 25F84
OpenCore-Legacy-Patcher-T2: [exact release / commit]
Lilu: 1.7.2
RestrictEvents: 1.1.6
SecureBootModel: Disabled

I am testing from external installer media only. I have not attempted an installation to the internal disk.

Test A — no SMBIOS spoofing

With the real MacBookPro15,1 SMBIOS, boot ends in an early kernel panic.

The panic is a type-14 page fault and the backtrace contains:

as.vit9696.RestrictEvents(1.1.6)::_start
as.vit9696.Lilu(1.7.2)

Test B — with SMBIOS spoofing
With SMBIOS spoofing enabled, the RestrictEvents panic does not occur and boot proceeds further.
However, it then stalls/fails with AppleKeyStore messages such as:

"AppleKeyStore": pid:52, 13262: operation failed (sel: 84 ret: 000002e6, -1)

<img width="3024" height="4032" alt="Image" src="https://github.com/user-attachments/assets/eef5fb00-9c49-456a-b133-580c6e97fefb" />

<img width="3024" height="4032" alt="Image" src="https://github.com/user-attachments/assets/9e1451ac-0eb3-4517-b44d-6fc40e1e2817" />

@m0rtiis1 · September 13, 2026

Mac book pro 15.1 2018
used latest open core legacy patcher T2 .0.0.18009.3 - 4.0.0 alpha 18.9.3

@Medelcartelinc · September 13, 2026

@m0rtiis1 Wow, thank you so much for capturing that verbose frame! This is an incredible find.

Looking at your screenshot, the final freeze happens right here:
AMFI: vnode_check_signature called with platform 1

This gives us the definitive answer: The installer is not hanging because of a slow USB or a generic graphics crash. It is fatally freezing inside the macOS Tahoe kernel due to an Apple Mobile File Integrity (AMFI) conflict on T2 hardware!

When the system tries to verify digital signatures via AMFI during the early recovery boot phase, it stalls forever. This strongly indicates that AMFIPass.kext (v1.4.1) or the AMFI boot-args we are injecting for Tahoe are causing a massive kernel deadlock on T2 Macs.

We are currently investigating a way to bypass or temporarily disable AMFIPass for the USB installer phase to see if it allows you to get past the Apple logo and Language Chooser. Stay tuned, we will drop a test build for you all shortly!

@albert-mueller · October 11, 2026

MacBookPro15,1 (J680AP): RestrictEvents 1.1.6 kernel panic without spoofing; AppleKeyStore selector 84 failure with spoofing

Hardware / environment

Model: MacBookPro15,1 (2018, Coffee Lake, T2)

Bridge model: J680AP

macOS Tahoe: 26.5.2, build 25F84

OpenCore-Legacy-Patcher-T2: [exact release / commit]

Lilu: 1.7.2

RestrictEvents: 1.1.6

SecureBootModel: Disabled

I am testing from external installer media only. I have not attempted an installation to the internal disk.

Test A — no SMBIOS spoofing

With the real MacBookPro15,1 SMBIOS, boot ends in an early kernel panic.

The panic is a type-14 page fault and the backtrace contains:
as.vit9696.RestrictEvents(1.1.6)::_start
as.vit9696.Lilu(1.7.2)

Test B — with SMBIOS spoofing
With SMBIOS spoofing enabled, the RestrictEvents panic does not occur and boot proceeds further.
However, it then stalls/fails with AppleKeyStore messages such as:

"AppleKeyStore": pid:52, 13262: operation failed (sel: 84 ret: 000002e6, -1)

<img width="3024" height="4032" alt="Image" src="https://github.com/user-attachments/assets/eef5fb00-9c49-456a-b133-580c6e97fefb" />

<img width="3024" height="4032" alt="Image" src="https://github.com/user-attachments/assets/9e1451ac-0eb3-4517-b44d-6fc40e1e2817" />

Can you try the latest release?

@albert-mueller · October 11, 2026

@GUTY345

@damian2601dy · October 11, 2026

Still same Problem: Disk Utility: erase of “Macintosh HD” fails with An internal error has occurred (-69624) at “Creating APFS Volume”. What works:
HFS+ on disk0 works, but not APFS.
Last Build

@arlogics · October 11, 2026

On my model (MacBook Pro 15,2)
Creating a seperate volume succeeded but got stucked at second stage.

@m0rtiis1 · October 11, 2026

30. Still same Problem: Disk Utility: erase of “Macintosh HD” fails with An internal error has occurred (-69624) at “Creating APFS Volume”. What works:
HFS+ on disk0 works, but not APFS.
Last Build

@damian2601dy how to do get to the installation page my I get text screen then the laptop shuts down could you please tell me what steps are you doing different to reach to installation page?

@albert-mueller · October 11, 2026

31. > 30. Still same Problem: Disk Utility: erase of “Macintosh HD” fails with An internal error has occurred (-69624) at “Creating APFS Volume”. What works:
> HFS+ on disk0 works, but not APFS.
> Last Build
 [@damian2601dy](https://github.com/damian2601dy) how to do get to the installation page my I get text screen then the laptop shuts down could you please tell me what steps are you doing different to reach to installation page?

On my Mac mini 2018 I simply don't format the internal SSD yet. I'm instead testing on an external one. And I also leave the default configs unless I really need to configure something.

Discuss this issue on GitHub33 comments