JuanPerezzzzz

Hi everyone, I need help choosing the perfect SMBIOS for macOS Sequoia on my laptop and confirming the correct iGPU spoof. My hardware: CPU: Intel Core i5-6200U (Skylake, U series) iGPU: Intel HD 520 No dGPU Laptop (mobile hardware) Since Skylake is no longer natively supported in newer macOS versions, I understand that I need to spoof my HD 520 to a Kaby Lake iGPU (HD 620). What would be: The most appropriate SMBIOS for macOS Sequoia in my case? (MacBookPro13,1 or MacBookPro14,1?) The correct device-id and AAPL,ig-platform-id values for HD 520 → HD 620 spoof in Sequoia? Currently considering: device-id: 16590000 (HD 620) AAPL,ig-platform-id: 59160000 Is this correct for Sequoia, or is there a better configuration? I’m using OpenCore (latest version) and WhateverGreen (latest). Thanks in advance.

Hi MaLd0n, ForceRGBEasy worked — the purple/magenta tint is completely gone now. HDMI is running in proper RGB 4:4:4 and the image looks correct. Thank you very much. However, after applying the patch (CEA extension removed), HDMI audio disappeared and no longer shows up as an output device in macOS. Is there any way to keep forced RGB while also preserving HDMI audio through the same cable? Thanks again for the help. ❤️

Hello everyone, I'm experiencing an HDMI color issue in macOS Ventura using a Skylake HD 520 iGPU with Kaby Lake spoofing. After extensive testing, the problem persists. Here are the full details. 💻 System Laptop with Intel Skylake HD 520 macOS Ventura OpenCore (latest stable version) SMBIOS tested: MacBookPro14,1 MacBookPro14,2 iGPU spoofed as Kaby Lake (required for Ventura) 🖥️ The Problem HDMI works and outputs a stable image, but: Entire screen has a purple/magenta tint White appears greenish Colors are clearly incorrect Changing color profiles has no effect System log shows: The color mode = 0x100 is not RGB for DP 🔍 What the logs show Framebuffer attempts DP initialization first: Setting DP power state = 1 WriteAUX Timeout ReadAUX Timeout Setting DP power failed (0xe00002bc) Then it falls back to HDMI, but color mode seems already locked in a non-RGB state. It appears the Kaby Lake framebuffer is initializing in a DP-like color space (possibly YCbCr) even though the physical port is HDMI/TMDS. 🧪 What Has Been Tried ✔ Boot arguments tested -cdfon -agdpmod=ignore -igfxhdmi No change in color behavior. ✔ Connector patching Connectors set as HDMI Adjusted busID and pipe values Multiple connector configurations tested HDMI works functionally, but color remains incorrect. ✔ Manual EDID Override Extracted EDID via: ioreg -lw0 | grep IODisplayEDID Converted to Base64 Created override in: /Library/Displays/Contents/Resources/Overrides/ Attempted to force RGB Result: no change. ✔ Color profile calibration Tested advanced calibration and different color profiles. Result: no impact on the magenta tint. 📌 Important Detail This exact hardware works perfectly in macOS Monterey. The issue only appears in Ventura, where Skylake must be spoofed as Kaby Lake. 🎯 Working Theory It seems: Kaby Lake framebuffer forces color mode 0x100 DP initialization fails, then falls back to HDMI Color space remains non-RGB EDID override is ignored HDMI output is locked in incorrect color mode This looks like a structural incompatibility between: Real Skylake hardware + Kaby Lake framebuffer spoof + Ventura graphics stack ❓ Question Is there any known method to force true RGB output in HDMI under Ventura with Skylake spoof? Has anyone patched out the color mode 0x100 behavior? Or is this a known limitation of Skylake on Ventura? Any insight would be greatly appreciated. Thank you.

Hello MaLd0n, Thank you for your reply. I want to clarify that I already have an RTC fix applied in my config.plist. In my case, I’m using the HP-specific RTC patch recommended for HP Pavilion laptops (Fix HP Real-Time Clock Power Loss / Error 005), and it is enabled correctly. Even with this RTC patch active, the problem persists: macOS Monterey RAW installer (Olarila Vanilla) is still detected as corrupted Installer shows: “This copy of macOS is damaged and can’t be used to install macOS” Balena Etcher also reports corruption at the end of the flashing process BIOS date and hour are correct and verified Secure Boot is disabled SSD is detected correctly in Disk Utility So far, applying the RTC patch did not change the installer validation behavior. That’s why I’m trying to understand if this issue could be related to: The Monterey RAW image itself when created/flashed from Windows Balena Etcher false corruption warnings or write issues Monterey installer validation on Skylake systems SecureBootModel / SMBIOS mismatch affecting installer verification If there is a preferred method or tool on Windows to create a reliable Monterey offline installer for this hardware, I’d appreciate the guidance. Thanks again for your time and support.

Hello MaLd0n, This is my exact hardware: Laptop: HP Pavilion 14-al001la CPU: Intel Core i5-6200U (Skylake) iGPU: Intel HD Graphics 520 RAM: 8 GB DDR4 Storage: SATA SSD (AHCI) WiFi / Bluetooth: Broadcom BCM94352Z Ethernet: Realtek RTL8111 BIOS: HP UEFI (Secure Boot disabled) Bootloader: OpenCore (latest release) Issue: macOS Monterey RAW installer (Olarila Vanilla) always reports “This copy of macOS is damaged and can’t be used to install macOS” Balena Etcher also reports image corruption Recovery online works partially, Ethernet is detected but disconnects after some time System date already corrected in Recovery SecureBootModel set to Default SSD is detected (using AHCIPortInjector.kext) Could this be related to: Skylake + Monterey installer validation? SecureBootModel / SMBIOS choice? Recommended method to create a full offline installer on Windows for this hardware? Thanks.

Hello everyone, I’m having a persistent issue installing macOS Monterey, where the installer is always detected as corrupted, even after multiple clean downloads. My setup Host OS: Windows 10 x64 Target: Hackintosh Bootloader: OpenCore WiFi/BT card: BCM94352Z SSD: SATA, detected after using AHCIPortInjector.kext USB drives tested: 16 GB and 4 GB macOS version: Monterey What I already tried Downloaded macOS Monterey RAW image from Olarila – Vanilla Images Verified the download completed fully Flashed the RAW image using Balena Etcher (Etcher warns about corruption at the end) Re-downloaded the image multiple times Used different USB drives Tried both offline installer and Recovery Set system date manually in Recovery Confirmed the SSD is visible in Disk Utility The problem No matter what I do, the installer always shows: “This copy of macOS is damaged and can’t be used to install macOS.” Even after re-downloading the RAW image from Olarila Vanilla Images, the issue persists. Limitations I do NOT have access to a real Mac I cannot use a virtual machine Internet during Recovery is unreliable (WiFi not available in Recovery, Ethernet also failing) My questions Is there any known issue with Olarila Monterey RAW images when created from Windows? Could Balena Etcher be causing false corruption or writing issues with macOS RAW images? Is there a recommended tool or method on Windows to flash Monterey installers more reliably? Could this error be related to OpenCore configuration (SecureBootModel, SIP, etc.) rather than the image itself? Any help or guidance would be greatly appreciated. Thanks in advance.