MaLd0n

if all is updated like kexts, bootloader, just go

Check efi folders for this

HDMI dont work on Icelake

https://olarila.com/topic/5676-hackintosh-efi-folder-with-clover-and-opencore/

the end is near for intel

macOS Golden Gate is the next major macOS generation, introduced as macOS 27 during WWDC 2026. This release represents an important transition point for the Mac platform, with a stronger focus on Apple Silicon, performance improvements, system responsiveness, and newer macOS technologies. For Apple Silicon users, macOS Golden Gate continues Apple’s modern architecture direction, bringing the best compatibility, performance, and long-term support to Macs powered by M-series chips. This includes better integration with Apple’s latest frameworks, improved system-level features, enhanced efficiency, and deeper optimization for Apple Silicon hardware. Intel Mac support appears to be ending with macOS Golden Gate. Early reports indicate that macOS 27 drops support for Intel-based Macs and is designed for Apple Silicon Macs only. This means that macOS Tahoe is likely the final major macOS release for supported Intel Macs, while Golden Gate starts a new Apple Silicon-only era. Because this is still a pre-release stage, compatibility may change during the beta cycle. Some features, APIs, drivers, kernel behavior, and system protections can still be adjusted by Apple before the final public release. For this reason, support for macOS Golden Gate should be considered experimental until the final version is officially released. Our tools and apps are being prepared and tested for macOS Golden Gate with priority support for Apple Silicon. Intel support will continue where possible on older macOS versions, but Golden Gate support will focus on Apple Silicon due to Apple’s platform direction. With macOS Golden Gate, Apple has officially moved macOS into an Apple Silicon-only generation. Intel Mac support has been removed entirely, meaning that the last Intel models supported by macOS Tahoe are no longer eligible for this release. This includes the MacBook Pro 16-inch 2019, MacBook Pro 13-inch 2020 with four Thunderbolt 3 ports, iMac 27-inch 2020, and Mac Pro 2019. These machines may continue to receive security updates on older macOS versions, but they are not part of the macOS Golden Gate compatibility list. Key Points macOS Golden Gate is macOS 27. Apple Silicon is the primary supported platform. Intel Mac support is expected to end with this release. Intel users should remain on macOS Tahoe or earlier supported macOS versions. Golden Gate support is currently pre-release and experimental. Final compatibility depends on Apple’s public release and final system requirements.

AMD VBIOS Patcher is a lightweight and secure utility created to patch AMD Radeon RX580 2048SP VBIOS ROM files for better macOS Hackintosh compatibility. The app automates the known RX580 2048SP VBIOS modification process, helping users convert compatible RX580 2048SP ROM patterns into RX580-compatible values used by macOS. This tool is designed for users who need to edit an AMD Radeon RX580 2048SP VBIOS without manually searching and replacing hexadecimal values. AMD VBIOS Patcher scans the selected .rom or .bin file, detects the required byte patterns, applies the correct RX580 2048SP to RX580 patches, verifies the PCI ROM structure, and optionally repairs the PCI Option ROM checksum after patching. Download for macOS HERE Download for Windows HERE Anyone who would like to support the project with donations is very welcome and greatly appreciated. Link HERE Warning: Flashing a modified VBIOS always involves risk. This application only edits and saves a new VBIOS ROM file. It does not flash your graphics card. Flashing any modified, incorrect, incompatible, or corrupted VBIOS can permanently brick your GPU or make the system unable to boot. Always keep a verified backup of your original VBIOS before flashing. Make sure the patched ROM is correct for your exact GPU model, memory type, and board revision. You are fully responsible for any VBIOS flashing procedure. Use this tool and flash any modified ROM at your own risk. Main Features AMD Radeon RX580 2048SP VBIOS patcher for macOS compatibility Supports .rom and .bin VBIOS files Automatic detection of original and already patched ROMs Applies all supported RX580 2048SP byte patches Patches both Device ID entries when present Preserves AMD/ATI Vendor ID 0x1002 Repairs PCI ROM checksum safely Creates automatic backup with SHA256 hash Generates a detailed patch report Shows patch offsets, checksum status, and ROM validation results Drag and drop support Simple Analyze and Patch workflow Available for macOS, Windows 10, and Windows 11 Windows version can be built as a standalone single .exe No telemetry, no internet connection, no driver installation, no GPU flashing What the App Does AMD VBIOS Patcher checks the AMD Radeon RX580 2048SP VBIOS and searches for the known byte patterns required for macOS compatibility. When the supported patterns are found, the app applies the correct replacements, updates the Device ID from RX580 2048SP to RX580-compatible values, and fixes the checksum of each PCI ROM image when needed. The original ROM is never overwritten automatically. A backup is created before saving the patched file, and a complete local report is generated beside the output ROM. Safety AMD VBIOS Patcher does not flash your graphics card. It only edits and saves a new VBIOS ROM file. Users must verify the patched ROM and flash it manually using their preferred external flashing tool. Always keep the original VBIOS backup before flashing any modified ROM. Flashing an incorrect or corrupted VBIOS can brick the GPU. Recommended For AMD Radeon RX580 2048SP Hackintosh users macOS users with RX580 2048SP compatibility issues Users who need to convert RX580 2048SP VBIOS to RX580-compatible Device ID Hackintosh builders who want a safer VBIOS patching workflow Users who want to avoid manual hex editing Credits Created by MaLd0n / Daniel Maldonado / Olarila. Official Hackintosh support and releases: Olarila.com

ZeroRPMBuilder is a Windows and macOS utility designed to create ready-to-use OpenCore or Clover DeviceProperties patches for AMD RDNA2 graphics cards on Hackintosh systems. The app reads a saved AMD GPU VBIOS ROM or SPPT/PowerPlay table, applies a built-in Zero RPM or Fan 35 °C patch, and automatically generates a patched config.plist with PP_PhmSoftPowerPlayTable injected under DeviceProperties. Download for macOS HERE Download for Windows HERE Anyone who would like to support the project with donations is very welcome and greatly appreciated. Link HERE ZeroRPMBuilder supports AMD RDNA2 Navi21, Navi22 and Navi23 GPUs, including: Radeon RX 6600 / RX 6600 XT Radeon RX 6650 XT Radeon RX 6700 / RX 6700 XT Radeon RX 6750 XT Radeon RX 6800 / RX 6800 XT Radeon RX 6900 XT Radeon RX 6950 XT The app includes two patch modes: ZeroRPM Pure Solution Disables Zero RPM behavior by patching the PowerPlay table so the GPU fan does not remain stopped under low-temperature conditions. Fan 35 °C Solution Keeps Zero RPM enabled but changes the fan temperature curve so the fan starts at 35 °C and stops at 30 °C, offering a safer and quieter cooling profile for many Hackintosh builds. ZeroRPMBuilder does not flash the VBIOS, does not write firmware, does not install drivers, does not generate SSDTs, and does not modify the system. It only creates OpenCore-ready files for manual use. Each ZIP includes the patched config.plist, modified PowerPlay table, backup files, report, README, and DeviceProperties snippets. ZeroRPMBuilder is ideal for Hackintosh users who want a simple and safe way to apply AMD RX 6000 series fan control patches without MorePowerTool, SSDT injection, firmware flashing, or manual hex editing. How to Use ZeroRPMBuilder Save your AMD GPU VBIOS Use GPU-Z on Windows or another trusted tool to save your AMD RX 6000 series VBIOS ROM. Supported input files: .rom .bin .reg .txt .sppt .pp_table Open ZeroRPMBuilder Launch the app on Windows or macOS. Load your VBIOS or SPPT file Click: Load VBIOS ROM / SPPT Select your saved VBIOS ROM or exported PowerPlay/SPPT file. Choose the patch mode Use one of the available buttons: Generate ZeroRPM Pure Solution This disables Zero RPM completely. Or: Generate FAN 35 °C Solution This keeps Zero RPM enabled but changes the fan behavior: Fan starts at 35 °C Fan stops at 30 °C Check the DeviceProperties path Before using the generated config.plist, confirm that the GPU DeviceProperties path is correct for your machine. RX6xxx cards must use this full path format: PciRoot(...) / Pci(...) / Pci(...) / Pci(...) / Pci(...) Example: PciRoot(0x0)/Pci(0x6,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) Get the generated files The app creates the output on your Desktop: ZeroRPM.zip ZeroRPM35.zip Each ZIP contains: config.plist ZeroRPM-Report.txt README.txt Backup/ Modified/ Snippets/ Use the generated config.plist Copy the generated config.plist to your OpenCore EFI, or copy only the generated DeviceProperties section into your current OpenCore config.plist. Reboot and test Reboot macOS and check the GPU fan behavior. Start with FAN 35 °C Solution first if you want the safer/conservative option. Important Notes ZeroRPMBuilder does not flash VBIOS, does not write firmware, does not install drivers, does not generate SSDTs, and does not modify your system. It only reads the selected file and generates OpenCore-ready files. Created by ®Daniel Maldonado – Olarila

Seems the problem is PS2Controller Some wrong bootargs for ur build too

DMIDecode Hardware List is a modern macOS hardware information app designed to display useful system details from dmidecode in a clean, organized and searchable interface. The app reads hardware data directly on each machine and dynamically lists the detected components, making it useful for real Macs and Hackintosh systems. It helps users inspect SMBIOS, CPU, memory, BIOS, baseboard, PCI devices, GPU, network adapters, storage controllers, audio devices, USB controllers and other important hardware information. Unlike raw terminal output, DMIDecode Hardware List filters the useful data and presents it in categorized sections, making hardware inspection faster and easier. It is especially useful for Hackintosh troubleshooting, EFI creation, ACPI work, device property checks, PCI device identification and system compatibility analysis. Download: HERE Anyone who would like to support the project with donations is very welcome and greatly appreciated. Link HERE Key Features Modern macOS dark interface Dynamic hardware detection per machine Clean categorized hardware list Search and filter system information Detects CPU, memory, BIOS, baseboard and platform data Lists PCI devices, GPU, network, storage, audio and USB information Shows useful IDs such as vendor-id, device-id, class-code and subsystem IDs when available Helps identify Hackintosh hardware for EFI, ACPI and DeviceProperties work Includes raw dmidecode output viewer Export report to TXT Copy visible filtered data Runs locally without sending data to the internet No background service after quitting the app Hackintosh Usage DMIDecode Hardware List is useful for Hackintosh users who need to inspect hardware details quickly before creating or adjusting an EFI folder. The app can help identify real PCI devices, GPU, Ethernet, Wi-Fi, storage, USB and audio controllers exposed by macOS and IORegistry. This makes it easier to check hardware compatibility, prepare OpenCore or Clover configurations, review DeviceProperties, inspect SMBIOS data and troubleshoot missing or incorrectly detected devices. Privacy and Safety The app runs locally on macOS. It does not collect, upload, transmit or store private user data online. All hardware detection is performed locally using the bundled dmidecode tool and macOS system information exposed by the machine. Security Notice All release files are checked with VirusTotal before publication. The app is distributed clean, without adware, spyware, miners, telemetry, unwanted installers or any malicious components. Credits This app uses dmidecode as its hardware information backend. Credits and third-party notices are included in the app package. Created by MaLd0n / Daniel Maldonado / Olarila.

Broadcom Patcher is a macOS utility designed to simplify the Broadcom Wi-Fi patching process on Hackintosh systems using OpenCore, Clover, or both bootloaders in the same EFI folder. The app provides a simple drag and drop workflow: just drop your EFI folder, mounted EFI partition, OpenCore folder, Clover folder, or IORegistry dump, and Broadcom Patcher automatically applies the required Wi-Fi patches for supported macOS versions, including macOS Tahoe, macOS Sequoia and macOS Sonoma. Broadcom Patcher is especially useful for users who need to restore or enable Broadcom Wi-Fi support after Apple removed native support for many legacy Broadcom wireless cards in newer macOS releases. Download HERE Anyone who would like to support the project with donations is very welcome and greatly appreciated. Link HERE Main Features Drag and drop EFI patching Supports OpenCore Supports Clover Supports EFI folders containing OpenCore and Clover together Automatic bootloader detection Automatic Broadcom Wi-Fi detection using IORegistry Supports IORegistry dump files for patching EFI folders from another computer Automatically copies the required Broadcom kexts Replaces outdated Broadcom kexts with the correct included versions Applies OpenCore Kernel/Add, Kernel/Block, NVRAM, Misc/Security, and DeviceProperties Applies Clover KernelAndKextPatches/KextsToBlock, RtVariables, Boot/Arguments, and Devices/Properties Automatically applies the correct SIP configuration Automatically applies Tahoe-specific boot arguments only when needed Supports Intel and AMD Hackintosh systems Automatically disables AirportBrcmFixup.kext on AMD systems Creates automatic config.plist backups before patching Shows a final OpenCore Legacy Patcher download prompt after patching Uses OCLP-Plus link for macOS Tahoe Uses Dortania OpenCore Legacy Patcher link for Sonoma, and Sequoia OpenCore Support For OpenCore EFI folders, Broadcom Patcher automatically updates: EFI/OC/Kexts Kernel -> Add Kernel -> Block NVRAM Misc -> Security DeviceProperties -> Add The app keeps the correct Broadcom kext order and avoids duplicate entries in config.plist. Clover Support For Clover EFI folders, Broadcom Patcher automatically updates: EFI/CLOVER/kexts/Other KernelAndKextPatches -> KextsToBlock RtVariables -> CsrActiveConfig Boot -> Arguments Devices -> Properties Clover support is useful for users who still maintain legacy Clover EFI folders or dual-bootloader setups. OpenCore + Clover in the Same EFI Broadcom Patcher supports EFI folders using both bootloaders together, such as BootLoaderSelector setups: EFI/ ├── BOOT/ ├── OC/ │ └── config.plist └── CLOVER/ └── config.plist If both bootloaders are detected, the app patches both OpenCore and Clover in the same process. macOS Tahoe Support For macOS Tahoe, Broadcom Patcher automatically applies the extra boot arguments required for Broadcom Wi-Fi patching: -amfipassbeta amfi=0x80 ipc_control_port_options=0 These Tahoe-specific boot arguments are not applied to Sonoma, or Sequoia. After patching, the app shows the correct OCLP download link: macOS Tahoe: OCLP-Plus macOS Sonoma, Sequoia: Dortania OpenCore Legacy Patcher Broadcom DeviceProperties Detection Broadcom Patcher can scan the current IORegistry or an IORegistry dump from another Hackintosh to detect the Broadcom Wi-Fi device path dynamically. When a valid Broadcom Wi-Fi device is detected, the app applies the required properties automatically: OpenCore: DeviceProperties -> Add Clover: Devices -> Properties If no Broadcom Wi-Fi device is detected, the app does not create fake or generic PCI paths. This keeps the EFI safer and avoids incorrect device injection. AMD Hackintosh Support On AMD Hackintosh systems, Broadcom Patcher automatically handles AirportBrcmFixup.kext differently: OpenCore: keeps the entry but disables it Clover: does not copy AirportBrcmFixup.kext This helps avoid known compatibility issues on AMD platforms. Safety Broadcom Patcher works locally on your Mac. It does not collect data, upload files, send telemetry, or modify anything outside the selected EFI folder. Before changing any config.plist, the app creates a backup so users can restore their previous configuration if needed. Credits Created by MaLd0n / Daniel Maldonado / Olarila Credits and thanks to the developers and projects that made Broadcom Wi-Fi patching possible: OpenCore / Acidanthera AirportBrcmFixup AMFIPass OpenCore Legacy Patcher / Dortania OCLP-Plus / YBronst Apple legacy Broadcom Wi-Fi frameworks and kexts

BootLoaderSelector is a lightweight and fast UEFI bootloader selector designed for Hackintosh users who want to easily choose between OpenCore and Clover from the same EFI partition. It provides a clean visual interface, automatic OpenCore/Clover detection, hardware information display, timeout boot, last selected bootloader memory, and safe fallback behavior without modifying NVRAM, BootOrder, BootNext, or creating unwanted UEFI boot entries. Inspired by the original work and concept from jief666, BootLoaderSelector was created as a clean, modern and simplified project focused on speed, safety and compatibility for Hackintosh environments. Download BOOTX64-Release.zip Just replace BOOTX64.efi in EFI/BOOT folder Anyone who would like to support the project with donations is very welcome and greatly appreciated. Link HERE Up Arrow Hotkey Explanation BootLoaderSelector includes a silent recovery hotkey using the Up Arrow key. When Remember last selected bootloader is enabled, BootLoaderSelector automatically starts the last bootloader selected by the user on the next boot. This means that after choosing OpenCore or Clover once, the next boot can go directly to that bootloader without showing the BootLoaderSelector menu again. To open the BootLoaderSelector menu again, press or hold the Up Arrow key during the BIOS/UEFI logo screen. No warning screen is shown. The hotkey works silently before the automatic boot starts. This behavior was chosen to avoid conflicts with common BIOS and motherboard hotkeys such as F8, which many systems already use for boot menu or firmware options. In short: First boot: BootLoaderSelector menu is shown. Select OpenCore or Clover. Next boot: the last selected bootloader starts automatically. To show BootLoaderSelector again: press/hold Up Arrow during the BIOS/UEFI logo. No NVRAM, BootOrder or BootNext changes are made. BootLoaderSelector is a clean UEFI application for selecting between OpenCore and Clover at boot time. It is designed for users who keep both bootloaders available in the same EFI and want a simple, safe and fast way to choose which one to start. The selector runs before macOS and loads the selected bootloader directly using standard UEFI methods. It does not patch firmware, does not modify OpenCore or Clover, does not write to NVRAM, does not create Boot#### entries, and does not change BootOrder or BootNext. Main features: Supports OpenCore and Clover Clean visual UEFI interface Automatic bootloader detection Hardware information display: CPU GPU Board Memory Default 10-second timeout Options menu for timeout and behavior Remember last selected bootloader, enabled by default Silent hotkey access using Up Arrow during BIOS/UEFI logo F10 screenshot support Uses BLS.plist inside EFI/BOOT Generates both: BootLoaderSelector.efi BOOTX64.efi No NVRAM modification No BootOrder modification No BootNext modification No UEFI boot entry creation BootLoaderSelector is especially useful for Hackintosh testing, dual-bootloader EFI setups, OpenCore/Clover comparison, recovery environments and users who want a safer boot selection layer without relying on firmware boot menus. This project was inspired by jief666, whose work and ideas helped guide the concept of a dedicated UEFI bootloader chooser for Hackintosh systems.

https://github.com/Carnations-Botanica/IntelMKLFixup

https://olarila.com/topic/5676-hackintosh-efi-folder-with-clover-and-opencore/

Ill check it soon

Use debug and check what happens

Or vídeo patch or TSC_sync_margin=0 for CpuTscSync or -noDC9 bootarg

Try thisEFI.zip -Delete old EFI folder and paste new then empty trash. Don't use merge files. -Don't use Drag and Drop into EFI partition. Use Copy/Paste instead. -Reset NVRAM one time - with OpenCore use entry "Reset Nvram" / with Clover use F11 key on boot screen.

Check if have some duplicate kext like vodooinput

full acpi tables

Where acpi?

Check this efi folder and change smbios https://olarila.com/files/OPENCORE1/EFI.Opencore.Desktop.LGA775.zip

Save acpi and usb kext with usbtoolbox, post here

I think is a hide option. extract ACPI and usb kext on windows with USBTOOLBOX https://olarila.com/topic/37827-hackintosh-remap-usb-with-usbtoolbox-windows-or-macos/

Whats happens with link? Do u tried with HT disable on bios/uefi setup?