Things I have tried myself, adding a Device Properties section for the GPU, and the corresponding boot args, that OCLP 2.4.1 would normally generate for this machine, Mac Pro 6,1. Still no luck. I'm not exactly sure what the issue is, the patcher recognizes the proper GPU and patches accordingly. This also happened with the Mac Pro 5,1 2010. I have a Radeon RX 570 in there, same yellow screen after patches. I tried connecting different monitors to the HDMI port as well as trying through the thunderbolt to HDMI adapter.
Do we know where the other forks got to regarding these packages?
I think someone needs to fork Dortania's PatcherSupportPkg at this point. I'm currently using OCLP-Plus's PatcherSupportPkg, which - to an extent - provides some Tahoe support.
OCLP-R's PatcherSupportPkg is missing on Tahoe support for nearly all patches that requires it. However, their Metallibs works.
Regarding PatcherSupportPkg, the best one to support Tahoe at the moment is the one that uses OCLP-Plus, anyone else's is missing on nearly all patches or are completely unstable.
Checked OCLP-Mod, OCLP-R, OCLP-X, OCLP-Plus and others already, the one from OCLP-Plus is the only one that comes close to full Tahoe support. @DrDonk
Do we know where the other forks got to regarding these packages?
Otherwise, the PatcherSupportPkg from OCLP-Plus is still the only one that I can say at least it supports Tahoe properly, even when some patches are missing. To fix this, I think someone like @DrDonk or @gandolf243 needs to fork PatcherSupportPkg from OCLP-Plus and add the missing patches. For Metallibs, however, the best one for Tahoe is OCLP-R, but theirs still is missing on Metal 3802 patches: hackdoc/OCLP-R#15. Except this, there are no other known issues. @DrDonk@gandolf243
Sorry I haven't been active in this. I was stuck on my iPhone, and the webkit on it can't render the comments section of issues (infact, with the new website design that github sent out, it can't render anything. but I am back on my mac!) What patches are missing?
Sorry I haven't been active in this. I was stuck on my iPhone, and the webkit on it can't render the comments section of issues (infact, with the new website design that github sent out, it can't render anything. but I am back on my mac!) What patches are missing?
On the Metallibs side, there are no Metal 3802 patches at all in OCLP-R's Metallibs, everything else is there.
On the PatcherSupportPkg side, in the one from OCLP-Plus, non-Metal patches are mostly missing and also some others, everything else is there.
I have released again an update to remove AI generated security patches to increase stability, but I can’t guarantee the yellow screen and the missing patches issue is gone, but you can give a try.
Yes the missing patches is the problem for the Mac Pro 6,1 and most likely Mac Pro 5,1, my guess is due to the CPU being Ivy Bridge and lacking AVX2, no matter what GPU is there. Considering your OCLP fork is called T2, I can leave these two Macs on the back burner LOL and focus on my MacbookPro 15,1 and Macmini 8,1. (Forgot to mention I also have the MacMini8,1)
Yes the missing patches is the problem for the Mac Pro 6,1 and most likely Mac Pro 5,1, my guess is due to the CPU being Ivy Bridge and lacking AVX2, no matter what GPU is there. Considering your OCLP fork is called T2, I can leave these two Macs on the back burner LOL and focus on my MacbookPro 15,1 and Macmini 8,1. (Forgot to mention I also have the MacMini8,1)
I also found that the PatcherSupportPkg is missing on many patches, yet still is the only one that fully works with Tahoe at least on some GPUs.
I am so sorry, but until I get my mac on Tahoe, I don't think I can help. The unfortunate thing is that currently, the macbookpro7,1 is the only mac I have.
Hey @WhiteLighter78 and @albert-mueller, the "yellow screen" bug on the Mac Pro 2013 (FirePro) and iMac 2015 (Radeon R9) is a known issue with the legacy AMD Metal drivers (GCN architecture) failing to parse Tahoe's updated CoreDisplay.framework color management hooks.
When root patches are applied, the hardware Color Lookup Table (LUT) fails to load the default .icc display profile correctly, resulting in a permanent yellow/orange tint.
While we wait for the upstream developers to reverse engineer a proper binary patch for the AMD drivers or CoreDisplay, there is a very reliable workaround you can try:
Boot your Mac into macOS Tahoe.
Go to System Settings > Displays.
Change your Color Profile from the default one (usually "iMac" or "Mac Pro") to Generic RGB Profile or sRGB IEC61966-2.1.
Make sure Night Shift and True Tone are completely turned off.
This should immediately restore normal colors on your display until a definitive fix is integrated into the root patcher.
Hey @WhiteLighter78 and @albert-mueller, the "yellow screen" bug on the Mac Pro 2013 (FirePro) and iMac 2015 (Radeon R9) is a known issue with the legacy AMD Metal drivers (GCN architecture) failing to parse Tahoe's updated CoreDisplay.framework color management hooks.
When root patches are applied, the hardware Color Lookup Table (LUT) fails to load the default .icc display profile correctly, resulting in a permanent yellow/orange tint.
While we wait for the upstream developers to reverse engineer a proper binary patch for the AMD drivers or CoreDisplay, there is a very reliable workaround you can try:
Boot your Mac into macOS Tahoe.
Go to System Settings > Displays.
Change your Color Profile from the default one (usually "iMac" or "Mac Pro") to Generic RGB Profile or sRGB IEC61966-2.1.
Make sure Night Shift and True Tone are completely turned off.
This should immediately restore normal colors on your display until a definitive fix is integrated into the root patcher.
If you're okay, you can start working in my fork for PatcherSupportPkg? Once the patches are ready, I'll migrate to it, but at the moment I'm using OCLP-Plus's own directly. @Medelcartelinc
Ok but the problem for me is, I can't see anything on the screen at all. It's solid yellow so I don't know how to change that setting if I can't see anything. Should I try reinstalling and then changing that setting BEFORE doing the root patches?
4.0.0.18002.6 ist erschienen mit neuen Patches verfügbar, inklusiv für nicht-Metal-Grafikkarten. Können sie jetzt diese Version ausprobieren? @WhiteLighter78@yasars
Just to clarify what 4.0.0.18002.6 addressed: that update added the detection and payload target routing mappings so that macOS 26 Tahoe recognizes legacy Intel and AMD GCN GPUs instead of failing to stage them altogether.
However, the "solid yellow screen" on Mac Pro 6,1 (FirePro D300/D500/D700) is a separate rendering bug in the Metal 31001 color pipeline on Tahoe:
Tahoe's compositor expects updated Metal metallib bitcode / color lookup tables (Hardware LUT) that AMDMTLBronzeDriver.bundle does not supply when talking to macOS 26's WindowServer / CoreDisplay.
In safe mode or before root patching, software fallback renders standard RGB, but once the GCN Bronze driver initializes without an explicit gamma/LUT bypass, the entire display framebuffer gets flooded with that solid yellow tint.
We are currently investigating a binary patch / driver shim for AMDMTLBronzeDriver to clamp or bypass the incompatible color-profile calls on Tahoe. We'll keep you posted as soon as we have a test patch ready!
Thanks for the report and screenshot! Two quick things regarding the iMac 11,2:
The preflight error (12.7.2-25): The patcher is currently looking for a Tahoe-specific Wi-Fi payload folder that doesn't exist yet in the DMG (it only has up to Sequoia 12.7.2-24), which causes the check to fail. We will push a quick fallback fix for this.
Graphics support: The iMac 11,2 uses an AMD TeraScale 1 GPU (HD 4670/5670), which is Non-Metal. Non-Metal graphics acceleration is currently not working on macOS 26 Tahoe and causes panics, so graphics won't be accelerated on this machine yet. For the 2010 iMac, macOS 12 Monterey or 13 Ventura is still the best and most stable option.
Oh okay! Thank you for the information! Just figured I'd try it out! I created a folder called 12.7.2-25 and copied the files from the 12.7.2-24 folder lol and reran the patcher. It worked. Until I rebooted and had a black screen. This explains it 😆
Haha, great minds think alike! That confirms the Wi-Fi fallback logic works nicely, and definitely explains the black screen with TeraScale on Tahoe. 😄
By the way, regarding your Mac Pro 6,1, we just finished and released the fix for the yellow screen in the new build:
👉 4.0.0.18002.7-exp-tahoe-beta
Whenever you have a chance, give it a run on your Mac Pro 6,1 with Root Patching and let us know if the colors are back to normal!
From the stack trace, the crash was triggered by a missing AMDOpenCL import in amd_legacy_gcn.py when enumerating the Legacy GCN patchset.
We pushed a commit restoring that import and refreshed the experimental build 4.0.0.18002.8 (the certificate OCLP-Self-Signed.cer is also attached to the release if ever needed).
Whenever you get a chance, please try this updated build to see if it gets past that specific exception on your MacPro6,1 and let us know.
Imac 2015 starting, GPU is working... Yellow screen is fixxed, but the assistant is to laggy to use it, i install LEVEL SAFE and LEVEL D but no difference .. but hey yellow is gone :) i see the install asistant ... now can fix the laggy mouse.
We have just pushed a fix to our open PR (#342) that specifically addresses the yellow screen for both AMD Polaris (MacPro5,1) and Dual AMD GCN (MacPro6,1) GPUs on macOS Tahoe.
For Polaris (MacPro5,1): The AppleColorSyncLinearGamma root patch fix was missing entirely for the Polaris patchset. We've now included it so it gets applied during root patching.
For Dual GCN (MacPro6,1): The agdpmod=pikera mitigation was previously only injected via DeviceProperties, which often fails to apply correctly to the primary display GPU in dual-GPU configurations (resulting in the AGDCDiagnose yellow screen). We have now moved agdpmod=pikera to the global OpenCore boot-args for all AMD GPUs, ensuring the AppleGraphicsDevicePolicy parses it correctly across all displays.
Once our PR is merged or Albert compiles a new release from our branch, please test it out!
@WhiteLighter78@yasars
The "yellow screen" issue on WindowServer initialization is a known side-effect of amfi=0x80 entirely breaking the MAC policy framework on macOS Tahoe (Darwin 25).
In our latest test build 4.0.0.18009.8, I have enforced a strict AMFIPass-only injection that scrubs legacy amfi=0x80 boot arguments that were causing these panics and WindowServer crashes.
Ok I will try once tahoe is re-installed. I'm not smart enough to know how to reverse those root patches when the screen is yellow and I can't even boot into safe mode, so I've just erased and restarted. Once I'm in, I'll run the new 18009.8 and report back!
@WhiteLighter78 No worries! For future reference, if you ever get stuck with a yellow/black screen and Safe Mode doesn't work, you don't need to erase your disk and reinstall macOS!
You can easily revert the OCLP root patches by doing this:
Boot into macOS Recovery.
Open Terminal (from the Utilities menu at the top).
Run this command: bless --mount "/Volumes/Macintosh HD" --bootefi --last-sealed-snapshot (Note: Change "Macintosh HD" if you named your internal drive differently).
This tells macOS to discard the root patches and boot safely into the clean, original system snapshot.
Looking forward to your test results with the .8 build!
Oh really? Thank you! I've screenshotted that, so I'll have that ready to go for next time. That will save a lot of time! 😆 I'll let you know what happens. I'm into the second reboot now. (About 29 minutes remaining) stage
@WhiteLighter78@yasars
The "yellow screen" issue on WindowServer initialization is a known side-effect of amfi=0x80 entirely breaking the MAC policy framework on macOS Tahoe (Darwin 25).
In our latest test build 4.0.0.18009.8, I have enforced a strict AMFIPass-only injection that scrubs legacy amfi=0x80 boot arguments that were causing these panics and WindowServer crashes.
So unfortunately it didn't worked for me. The only thing I did was apply the root patches. I did not do anything with OpenCore, EFI or anything else whatsoever. Should I like rebuild the OpenCore and boot with the new EFI or something like that?
@Richard-Hanus That is exactly why it failed! You MUST "Build and Install OpenCore" to your disk's EFI first!
The fix for the yellow screen is entirely based on updating your OpenCore EFI configuration (specifically, injecting AMFIPass.kext and removing the buggy amfi=0x80 boot-arg). If you only run the "Post-Install Root Patch" without updating your EFI first, your Mac continues to boot using your old EFI configuration, which still contains the bug!
Please follow these exact steps:
Revert your root patches (via Recovery) or reinstall macOS over the top to get back in.
Open the new .8 OCLP app.
Click "Build and Install OpenCore" and install it to your internal disk.
Reboot your Mac to apply the new EFI.
Only AFTER rebooting, open OCLP again and run "Post-Install Root Patch".
@Richard-Hanus That is exactly why it failed! You MUST "Build and Install OpenCore" to your disk's EFI first!
The fix for the yellow screen is entirely based on updating your OpenCore EFI configuration (specifically, injecting AMFIPass.kext and removing the buggy amfi=0x80 boot-arg). If you only run the "Post-Install Root Patch" without updating your EFI first, your Mac continues to boot using your old EFI configuration, which still contains the bug!
Please follow these exact steps:
Revert your root patches (via Recovery) or reinstall macOS over the top to get back in.
Open the new .8 OCLP app.
Click "Build and Install OpenCore" and install it to your internal disk.
Reboot your Mac to apply the new EFI.
Only AFTER rebooting, open OCLP again and run "Post-Install Root Patch".
@Richard-Hanus
I've analyzed the kernel panic screenshot. The crash occurs in RestrictEvents during its early initialization (__start + 0xb).
Since I completely removed amfi=0x80 in .8, the macOS MAC policy framework is no longer entirely disabled (which is a good thing for fixing the WindowServer / yellow screen issue). However, it seems that RestrictEvents 1.1.6 is incompatible with Darwin 25's new MAC framework and crashes the kernel if it attempts to load without amfi=0x80 present.
I have just released a new test build (4.0.0.18009.9) that appends -revoff to the boot-args specifically for non-T2 Macs on macOS Tahoe. This will safely abort RestrictEvents initialization, preventing the kernel panic while allowing the system to boot. You will temporarily lose some cosmetic features (like RAM notifications being hidden on the Mac Pro), but you should now be able to reach the desktop!
Please download the new .9 build, build and install OpenCore again, reboot, and let me know how it goes!
@Richard-Hanus
I've analyzed the kernel panic screenshot. The crash occurs in RestrictEvents during its early initialization (__start + 0xb).
Since I completely removed amfi=0x80 in .8, the macOS MAC policy framework is no longer entirely disabled (which is a good thing for fixing the WindowServer / yellow screen issue). However, it seems that RestrictEvents 1.1.6 is incompatible with Darwin 25's new MAC framework and crashes the kernel if it attempts to load without amfi=0x80 present.
I have just released a new test build (4.0.0.18009.9) that appends -revoff to the boot-args specifically for non-T2 Macs on macOS Tahoe. This will safely abort RestrictEvents initialization, preventing the kernel panic while allowing the system to boot. You will temporarily lose some cosmetic features (like RAM notifications being hidden on the Mac Pro), but you should now be able to reach the desktop!
Please download the new .9 build, build and install OpenCore again, reboot, and let me know how it goes!
Well. Like this. Another Kernel Panic.
I've used the OCLP-Mod's OpenCore EFI which worked out for me. So there is something else going on here.
Hi @albert-mueller, thanks for the report! To look into this we need to know exactly which versions you're running. Please edit your issue or reply below with:
macOS version, ideally with the build number (e.g. 26.6.1 (25G76)). You can find it under → About This Mac, or by running sw_vers in Terminal.
"Latest" or "new" isn't enough, since new builds come out often. This comment will go away once the versions are added.
Comments
@albert-mueller ·
@gandolf243 I’m not sure how to fix this issue, can you try to fix it?
@WhiteLighter78 ·
Things I have tried myself, adding a Device Properties section for the GPU, and the corresponding boot args, that OCLP 2.4.1 would normally generate for this machine, Mac Pro 6,1. Still no luck. I'm not exactly sure what the issue is, the patcher recognizes the proper GPU and patches accordingly. This also happened with the Mac Pro 5,1 2010. I have a Radeon RX 570 in there, same yellow screen after patches. I tried connecting different monitors to the HDMI port as well as trying through the thunderbolt to HDMI adapter.
@WhiteLighter78 ·
@WhiteLighter78 ·
Could this error at the bottom be the issue?
@albert-mueller ·
The no kexts found in GPUCompanionBundles is the likely reason… not 100% sure, @gandolf243 or @DrDonk can confirm what’s going on.
@DrDonk ·
Yep there are no compatible KEXTs present. This is possible a guess but there are a ton of unmerged files for Tahoe dortania/PatcherSupportPkg#18 and dortania/PatcherSupportPkg#16
Also probably need a MetallibSupportPkg update.
Do we know where the other forks got to regarding these packages?
@albert-mueller · · edited
I think someone needs to fork Dortania's PatcherSupportPkg at this point. I'm currently using OCLP-Plus's PatcherSupportPkg, which - to an extent - provides some Tahoe support.
OCLP-R's PatcherSupportPkg is missing on Tahoe support for nearly all patches that requires it. However, their Metallibs works.
Regarding PatcherSupportPkg, the best one to support Tahoe at the moment is the one that uses OCLP-Plus, anyone else's is missing on nearly all patches or are completely unstable.
Checked OCLP-Mod, OCLP-R, OCLP-X, OCLP-Plus and others already, the one from OCLP-Plus is the only one that comes close to full Tahoe support.
@DrDonk
@albert-mueller ·
And this one only adds AppleHDA.kext for Tahoe and that's it:
https://github.com/crystall1nedev/PatcherSupportPkg/tree/patches-tahoe/Universal-Binaries
Nothing else.
@DrDonk
@yasars ·
imac 2015 black screen with white bar not fix bro....^^
@albert-mueller · · edited
Otherwise, the PatcherSupportPkg from OCLP-Plus is still the only one that I can say at least it supports Tahoe properly, even when some patches are missing. To fix this, I think someone like @DrDonk or @gandolf243 needs to fork PatcherSupportPkg from OCLP-Plus and add the missing patches. For Metallibs, however, the best one for Tahoe is OCLP-R, but theirs still is missing on Metal 3802 patches: hackdoc/OCLP-R#15. Except this, there are no other known issues.
@DrDonk @gandolf243
@gandolf243 ·
Sorry I haven't been active in this. I was stuck on my iPhone, and the webkit on it can't render the comments section of issues (infact, with the new website design that github sent out, it can't render anything. but I am back on my mac!) What patches are missing?
@albert-mueller · · edited
On the Metallibs side, there are no Metal 3802 patches at all in OCLP-R's Metallibs, everything else is there.
On the PatcherSupportPkg side, in the one from OCLP-Plus, non-Metal patches are mostly missing and also some others, everything else is there.
@albert-mueller ·
I have released again an update to remove AI generated security patches to increase stability, but I can’t guarantee the yellow screen and the missing patches issue is gone, but you can give a try.
@WhiteLighter78 ·
Yes the missing patches is the problem for the Mac Pro 6,1 and most likely Mac Pro 5,1, my guess is due to the CPU being Ivy Bridge and lacking AVX2, no matter what GPU is there. Considering your OCLP fork is called T2, I can leave these two Macs on the back burner LOL and focus on my MacbookPro 15,1 and Macmini 8,1. (Forgot to mention I also have the MacMini8,1)
@yasars ·
yellow is fixxed, but black screen with logo is still here... and in the background read sirri...
@DrDonk ·
Looks like need a new define somewhere for Tahoe as it looks like it’s mistaking the version.
@WhiteLighter78 ·
@albert-mueller ·
I also found that the PatcherSupportPkg is missing on many patches, yet still is the only one that fully works with Tahoe at least on some GPUs.
@WhiteLighter78 ·
Just finished installing again, and still yellow screen after reboots. I'll be happy if the MacbookPro 15,1 and MacMini8,1 will work hahaha
@albert-mueller ·
That’s what I’m saying for the MacPro5,1-6,1 - the patches inside PatcherSupportPkg that are needed for these Macs are currently missing.
@WhiteLighter78 ·
Yes I understood that, but I tried anyway lol.
@yasars ·
Und wie willst du den schwarzen bildschirm fixxen? Sirri.redet aber der balken bleibt stehen
@albert-mueller ·
@gandolf243
@gandolf243 ·
I am so sorry, but until I get my mac on Tahoe, I don't think I can help. The unfortunate thing is that currently, the macbookpro7,1 is the only mac I have.
@albert-mueller · · edited
@Medelcartelinc Do you know how to fix this issue?
@Medelcartelinc ·
Hey @WhiteLighter78 and @albert-mueller, the "yellow screen" bug on the Mac Pro 2013 (FirePro) and iMac 2015 (Radeon R9) is a known issue with the legacy AMD Metal drivers (GCN architecture) failing to parse Tahoe's updated CoreDisplay.framework color management hooks.
When root patches are applied, the hardware Color Lookup Table (LUT) fails to load the default .icc display profile correctly, resulting in a permanent yellow/orange tint.
While we wait for the upstream developers to reverse engineer a proper binary patch for the AMD drivers or CoreDisplay, there is a very reliable workaround you can try:
Boot your Mac into macOS Tahoe.
Go to System Settings > Displays.
Change your Color Profile from the default one (usually "iMac" or "Mac Pro") to Generic RGB Profile or sRGB IEC61966-2.1.
Make sure Night Shift and True Tone are completely turned off.
This should immediately restore normal colors on your display until a definitive fix is integrated into the root patcher.
@albert-mueller ·
If you're okay, you can start working in my fork for PatcherSupportPkg? Once the patches are ready, I'll migrate to it, but at the moment I'm using OCLP-Plus's own directly.
@Medelcartelinc
@WhiteLighter78 ·
Ok but the problem for me is, I can't see anything on the screen at all. It's solid yellow so I don't know how to change that setting if I can't see anything. Should I try reinstalling and then changing that setting BEFORE doing the root patches?
@WhiteLighter78 ·
I booted into safe mode, changed the monitor profile and rebooted. Same solid yellow :(
@albert-mueller ·
4.0.0.18002.6 ist erschienen mit neuen Patches verfügbar, inklusiv für nicht-Metal-Grafikkarten. Können sie jetzt diese Version ausprobieren?
@WhiteLighter78 @yasars
@WhiteLighter78 ·
Naturliche! lol I am trying right now! Very excited.
@WhiteLighter78 ·
oh no :( Mac Pro 6,1 still a yellow screen after redoing the root patches with new version.
@Medelcartelinc ·
Hi @WhiteLighter78 and @albert-mueller,
Just to clarify what 4.0.0.18002.6 addressed: that update added the detection and payload target routing mappings so that macOS 26 Tahoe recognizes legacy Intel and AMD GCN GPUs instead of failing to stage them altogether.
However, the "solid yellow screen" on Mac Pro 6,1 (FirePro D300/D500/D700) is a separate rendering bug in the Metal 31001 color pipeline on Tahoe:
AMDMTLBronzeDriver.bundledoes not supply when talking to macOS 26's WindowServer / CoreDisplay.We are currently investigating a binary patch / driver shim for
AMDMTLBronzeDriverto clamp or bypass the incompatible color-profile calls on Tahoe. We'll keep you posted as soon as we have a test patch ready!@WhiteLighter78 ·
Oh okay! Thank you! I'm ready to test when you are!
@WhiteLighter78 ·
@WhiteLighter78 ·
I'm also testing on an iMac 11,2. I get this error trying to run root patches
@Medelcartelinc ·
Hi @WhiteLighter78,
Thanks for the report and screenshot! Two quick things regarding the iMac 11,2:
12.7.2-25): The patcher is currently looking for a Tahoe-specific Wi-Fi payload folder that doesn't exist yet in the DMG (it only has up to Sequoia12.7.2-24), which causes the check to fail. We will push a quick fallback fix for this.@WhiteLighter78 ·
Oh okay! Thank you for the information! Just figured I'd try it out! I created a folder called 12.7.2-25 and copied the files from the 12.7.2-24 folder lol and reran the patcher. It worked. Until I rebooted and had a black screen. This explains it 😆
@Medelcartelinc ·
Haha, great minds think alike! That confirms the Wi-Fi fallback logic works nicely, and definitely explains the black screen with TeraScale on Tahoe. 😄
By the way, regarding your Mac Pro 6,1, we just finished and released the fix for the yellow screen in the new build:
👉 4.0.0.18002.7-exp-tahoe-beta
Whenever you have a chance, give it a run on your Mac Pro 6,1 with Root Patching and let us know if the colors are back to normal!
@WhiteLighter78 ·
@WhiteLighter78 ·
I downloaded your link, installed but it still shows 18002.6 and throws this error when I try to root patch
@WhiteLighter78 ·
@Medelcartelinc · · edited
Thanks for the log photo! @WhiteLighter78
From the stack trace, the crash was triggered by a missing
AMDOpenCLimport inamd_legacy_gcn.pywhen enumerating the Legacy GCN patchset.We pushed a commit restoring that import and refreshed the experimental build 4.0.0.18002.8 (the certificate
OCLP-Self-Signed.ceris also attached to the release if ever needed).Whenever you get a chance, please try this updated build to see if it gets past that specific exception on your MacPro6,1 and let us know.
@WhiteLighter78 ·
@yasars · · edited
Imac 2015 starting, GPU is working... Yellow screen is fixxed, but the assistant is to laggy to use it, i install LEVEL SAFE and LEVEL D but no difference .. but hey yellow is gone :) i see the install asistant ... now can fix the laggy mouse.
Use xxxx 2.9 version
@yasars ·
All working now fux pla root patching imac 2015
@WhiteLighter78 ·
Unfortunately this issue is not fixed for Mac pro 6,1
@WhiteLighter78 ·
@Richard-Hanus ·
Same for me. I have MacPro5,1 with Polaris GPU and it also have a yellow screen after a root patch. Anyway how to fix it if it is even fixable? Thx.
@Medelcartelinc · · edited
Hi @WhiteLighter78 and @Richard-Hanus,
We have just pushed a fix to our open PR (#342) that specifically addresses the yellow screen for both AMD Polaris (MacPro5,1) and Dual AMD GCN (MacPro6,1) GPUs on macOS Tahoe.
AppleColorSyncLinearGammaroot patch fix was missing entirely for the Polaris patchset. We've now included it so it gets applied during root patching.agdpmod=pikeramitigation was previously only injected viaDeviceProperties, which often fails to apply correctly to the primary display GPU in dual-GPU configurations (resulting in theAGDCDiagnoseyellow screen). We have now movedagdpmod=pikerato the global OpenCoreboot-argsfor all AMD GPUs, ensuring the AppleGraphicsDevicePolicy parses it correctly across all displays.Once our PR is merged or Albert compiles a new release from our branch, please test it out!
@WhiteLighter78 ·
Ok I'm testing on the Mac Pro 5,1 right now. Radeon rx 570. Will report back!
@WhiteLighter78 ·
Using medelcartelinc's latest 4.0.0.18009.7 after root patching, still yellow screen on Mac pro 5,1
@WhiteLighter78 ·
@WhiteLighter78 ·
Can't even boot into safe mode.
@WhiteLighter78 ·
@Richard-Hanus ·
I also wanted to test it out but because of the evidently still persisting problem - I will wait until the proper fix is released.
@Medelcartelinc ·
@WhiteLighter78 @yasars
The "yellow screen" issue on WindowServer initialization is a known side-effect of
amfi=0x80entirely breaking the MAC policy framework on macOS Tahoe (Darwin 25).In our latest test build
4.0.0.18009.8, I have enforced a strict AMFIPass-only injection that scrubs legacyamfi=0x80boot arguments that were causing these panics and WindowServer crashes.Could you please test the
.8release and let me know if it solves the yellow screen on your Mac Pro 2013 / iMac 2015?https://github.com/Medelcartelinc/OpenCore-Legacy-Patcher-T2/releases/tag/4.0.0.18009.8
@WhiteLighter78 ·
Ok I will try once tahoe is re-installed. I'm not smart enough to know how to reverse those root patches when the screen is yellow and I can't even boot into safe mode, so I've just erased and restarted. Once I'm in, I'll run the new 18009.8 and report back!
@Medelcartelinc ·
@WhiteLighter78 No worries! For future reference, if you ever get stuck with a yellow/black screen and Safe Mode doesn't work, you don't need to erase your disk and reinstall macOS!
You can easily revert the OCLP root patches by doing this:
Boot into macOS Recovery.
Open Terminal (from the Utilities menu at the top).
Run this command: bless --mount "/Volumes/Macintosh HD" --bootefi --last-sealed-snapshot (Note: Change "Macintosh HD" if you named your internal drive differently).
This tells macOS to discard the root patches and boot safely into the clean, original system snapshot.
Looking forward to your test results with the .8 build!
@yasars · · edited
Doesnt work ... Read only
... Install tahoe renew and you are go...
Medelcartelinc#4
Have you fix the black logo with withe bar?
@WhiteLighter78 ·
Oh really? Thank you! I've screenshotted that, so I'll have that ready to go for next time. That will save a lot of time! 😆 I'll let you know what happens. I'm into the second reboot now. (About 29 minutes remaining) stage
@yasars ·
Just install it over the existing installation; it takes 15 minutes.
The commands doenst working... And safe mode doesnt work too
@WhiteLighter78 ·
Yeah? Ok I'll try both. If those commands don't work for me either I'll just reinstall over top instead of erase and reinstall.
@Richard-Hanus · · edited
So unfortunately it didn't worked for me. The only thing I did was apply the root patches. I did not do anything with OpenCore, EFI or anything else whatsoever. Should I like rebuild the OpenCore and boot with the new EFI or something like that?
@Medelcartelinc ·
@Richard-Hanus That is exactly why it failed! You MUST "Build and Install OpenCore" to your disk's EFI first!
The fix for the yellow screen is entirely based on updating your OpenCore EFI configuration (specifically, injecting AMFIPass.kext and removing the buggy amfi=0x80 boot-arg). If you only run the "Post-Install Root Patch" without updating your EFI first, your Mac continues to boot using your old EFI configuration, which still contains the bug!
Please follow these exact steps:
Revert your root patches (via Recovery) or reinstall macOS over the top to get back in.
Open the new .8 OCLP app.
Click "Build and Install OpenCore" and install it to your internal disk.
Reboot your Mac to apply the new EFI.
Only AFTER rebooting, open OCLP again and run "Post-Install Root Patch".
@Richard-Hanus ·
Well. Now it's not booting at all. 😄
@Medelcartelinc ·
@Richard-Hanus
I've analyzed the kernel panic screenshot. The crash occurs in
RestrictEventsduring its early initialization (__start + 0xb).Since I completely removed
amfi=0x80in.8, the macOS MAC policy framework is no longer entirely disabled (which is a good thing for fixing the WindowServer / yellow screen issue). However, it seems thatRestrictEvents 1.1.6is incompatible with Darwin 25's new MAC framework and crashes the kernel if it attempts to load withoutamfi=0x80present.I have just released a new test build (
4.0.0.18009.9) that appends-revoffto the boot-args specifically for non-T2 Macs on macOS Tahoe. This will safely abort RestrictEvents initialization, preventing the kernel panic while allowing the system to boot. You will temporarily lose some cosmetic features (like RAM notifications being hidden on the Mac Pro), but you should now be able to reach the desktop!Please download the new
.9build, build and install OpenCore again, reboot, and let me know how it goes!@WhiteLighter78 ·
I'm sorry to report, .8 causes the same yellow screen after root patching again on the Mac Pro 5,1 with Radeon RX 570.
@Richard-Hanus ·
Well. Like this. Another Kernel Panic.
I've used the OCLP-Mod's OpenCore EFI which worked out for me. So there is something else going on here.
@WhiteLighter78 ·
and the bless mount command didn't work for me either @yasars read-only. I'm just reinstalling over top.
@yasars · · edited
But same error after patching black loading screen... Must reinstall os to revert patches.... Any new infos?
Imac 2015...
@albert-mueller ·
@github-actions ·
Hi @albert-mueller, thanks for the report! To look into this we need to know exactly which versions you're running. Please edit your issue or reply below with:
26.6.1 (25G76)). You can find it under → About This Mac, or by runningsw_versin Terminal."Latest" or "new" isn't enough, since new builds come out often. This comment will go away once the versions are added.