MaLd0n

Can u extract a dump with this? https://olarila.com/files/macOS-Applications/Collect-HDAUniversal-Release.zip Comming from native things from Apple

HDAUniversal is a modern AppleHDA-like audio kernel extension for macOS and Hackintosh systems, created to deliver clean, stable, and natural onboard audio with a behavior closer to Apple’s native audio stack. This release represents an important milestone for the project. After extensive development, testing, debugging, and fine tuning across desktop and laptop configurations, HDAUniversal now provides a solid AppleHDA-like foundation with native-style volume handling, reliable output routing, combo-jack support, and compatibility with AppleALC-style layout IDs. The goal has always been clear: make audio feel native, predictable, and stable on supported Hackintosh systems. Donations help keep the project alive, supporting development time, testing hardware, hosting, maintenance, and future improvements. If HDAUniversal helps your system, consider supporting the work so the project can continue growing. Link HERE or HERE If you need help with your audio codec, please post a codec dump created with Clover or Linux. HERE A New AppleHDA-like Audio Solution HDAUniversal was designed with a strong focus on native macOS behavior. Instead of relying on artificial volume tricks or unstable routing workarounds, the kext follows a cleaner AppleHDA-like approach for codec initialization, output selection, mute handling, and endpoint switching. The current release includes support for: Internal Speakers Headphones Line-out Internal Microphone Headset Microphone Laptop combo-jack detection Desktop non-combo audio paths AppleHDA-like selector/source behavior Stable speaker/headphone switching Correct headset microphone handling Native-style output volume Proper mute and unmute lifecycle Clean Power/EAPD restore order This release is the result of careful iteration and real-world testing, with each change validated to avoid regressions in volume, routing, combo-jack behavior, or system stability. Installation 1- Remove VoodooHDA, AppleAlc or other and inject bootarg alcid=xx or Device Properties. Check Instructions HERE 2- Run the .pkg installer, then open System Settings > Privacy & Security and allow the HDAUniversal kernel extension if macOS asks for permission. Example: In my ALC897 i'm using alcid=98 and HDAUniversal.kext, only it. You can use Codec-Info to check things about your audio codec HERE For a clean and proper uninstallation, use this then reboot then install new version HERE Problems? Back to previous version! The driver is currently being built, and we will certainly encounter issues with some hardware. To disable HDMI Audio use bootarg -nohdmi Why HDAUniversal Must Be Installed in /Library/Extensions HDAUniversal is designed to work as a system-installed macOS audio kext, not as a simple bootloader-injected kext. For this first release, the correct and supported installation path is: /Library/Extensions/HDAUniversal.kext This requirement is intentional. Unlike small helper kexts that can usually be injected from EFI, HDAUniversal publishes real IOAudio devices, IOAudio engines, selectors, controls, volume ranges, mute controls, input/output sources, and AppleHDA-like audio endpoints. These objects are used not only by the kernel, but also by macOS user-space audio services such as CoreAudio, Sound Settings, Audio MIDI Setup, Control Center, and coreaudiod. Installing the kext in /Library/Extensions gives macOS a proper on-disk bundle with the expected structure, metadata, permissions, cache handling, and resource visibility. This is important for stable audio registration, correct IOAudio behavior, system audio discovery, sleep/wake lifecycle, and future localization or UI-related metadata. Loading HDAUniversal only from EFI may load the binary, but it can produce incomplete or inconsistent behavior because macOS may not treat the kext as a fully installed audio bundle. In that case, CoreAudio and the system UI may not reliably see all metadata, resources, localized names, or audio endpoint information the same way they do when the kext is installed properly in /Library/Extensions. For this reason, EFI injection is not supported for the first public release. Supported Installation Method Install HDAUniversal here: /Library/Extensions/HDAUniversal.kext Then rebuild the kext cache / kernel collection and reboot. Not Supported EFI/OC/Kexts/HDAUniversal.kext EFI/CLOVER/kexts/Other/HDAUniversal.kext Temporary manual loading Mixed copies in EFI and /Library/Extensions Only one copy of HDAUniversal should be present on the system. Multiple copies can cause duplicate matching, wrong versions being loaded, broken audio registration, or inconsistent behavior after reboot or sleep/wake. This approach keeps HDAUniversal closer to the way a real macOS audio driver is expected to live in the system and helps provide the most stable AppleHDA-like experience. Compatible with AppleALC-style Layout IDs HDAUniversal works with the same layout-id concept used by AppleALC, making it familiar and practical for Hackintosh users who already understand AppleALC layouts. This allows users to test audio using known layout IDs while HDAUniversal provides its own AppleHDA-like engine, routing logic, and runtime behavior. The layout-based approach makes the kext easier to configure, easier to compare, and easier to integrate into existing Hackintosh setups. Native Volume Philosophy One of the main goals of HDAUniversal is to provide a correct and natural volume experience. The output volume model is designed around real codec capabilities and AppleHDA-like behavior: Output volume reaches 0 dB No positive output boost is used No artificial -dB cap is applied No defensive volume lock is used Volume range follows real AmpCaps Mute is handled independently from logical volume Volume 0 provides real silence Unmute restores the previous logical volume This avoids common issues such as distorted sound, excessive loudness, broken volume steps, mute getting stuck, or inconsistent speaker/headphone volume behavior. Combo-Jack Support Combo-jack support is one of the strongest points of this release. HDAUniversal now supports AppleHDA-like endpoint behavior for laptops with shared headphone/headset microphone jacks. When a headset is connected, the kext can switch the output source to Headphones and the input source to Headset Microphone. When removed, it can safely return to Internal Speakers and Internal Microphone. This behavior was carefully tuned to preserve desktop non-combo systems while improving laptop combo-jack handling. Built for Stability and Real Hardware Testing HDAUniversal has been developed with stability as a priority. Every major stage of the project focused on avoiding regressions, protecting working audio paths, and keeping the kext predictable under real macOS usage. The release was fine tuned around: Boot stability Runtime audio stability Speaker/headphone separation Combo-jack switching Headset microphone detection Mute/unmute behavior Sleep/wake restore order Output volume correctness Avoiding artificial boost and distortion Keeping validated code paths intact This is not just a feature update. It is a carefully tested release built around practical Hackintosh audio behavior. Download HDA-Universal HERE Experimental HDAUniversal Boot Chime HERE Credits and Acknowledgements HDAUniversal exists because of years of work from Apple, open-source developers, and the Hackintosh audio community. Special thanks to Fabiano and Mirone Credits: Apple For the original AppleHDA architecture, macOS audio stack, IOAudioFamily, codec handling concepts, and the native behavior that inspired the AppleHDA-like design goals of this project. AppleALC For the layout-id ecosystem, codec research, audio patching knowledge, layout data, and years of Hackintosh audio development that helped define how modern macOS audio should be configured on non-Apple hardware. HDAUniversal follows the same layout-id concept familiar to AppleALC users, making testing and configuration easier for the community. VoodooHDA For its long history as one of the most important open-source Hackintosh audio projects, providing valuable knowledge about HDA codecs, routing, mixer handling, and alternative audio implementation strategies. The Hackintosh Community For continuous testing, codec dumps, bug reports, layout experiments, logs, real hardware validation, and years of shared knowledge that make projects like this possible. Olarila For development, testing, debugging, validation, and maintaining tools, guides, patches, and resources for the Hackintosh community. Project development by Daniel Maldonado / MaLd0n - Olarila.com. Disclaimer HDAUniversal is an independent project. It is not affiliated with, endorsed by, or sponsored by Apple, AppleALC, VoodooHDA, or any hardware vendor. Apple, macOS, AppleHDA, and related names are trademarks of Apple Inc. AppleALC and VoodooHDA are separate projects with their own authors, licenses, and development history. Full respect and credit belong to their respective developers and contributors. Reporting Issues If you find a problem with HDAUniversal, please report it with proper logs. Before posting, run the included log collector: Collect-HDAUniversal.command Download HERE This script collects the information needed to understand what is happening on your system, including codec data, IORegistry audio devices, IOAudio engines, CoreAudio state, loaded kexts, system audio information, and relevant HDAUniversal logs. When reporting an issue, please include: 1. The zip generated by Collect-HDAUniversal.command 2. Your codec model 3. Your layout-id 4. macOS version 5. Bootloader used 6. Whether the kext is installed in /Library/Extensions 7. A clear description of the problem 8. Steps to reproduce the issue Please avoid reports without logs. Messages such as “audio does not work” or “headphones are broken” are not enough to debug the problem. Useful examples: - Internal speakers work, but headphones do not switch after plug/unplug. - Headset microphone is not detected on a combo-jack laptop. - Audio works after boot, but not after sleep/wake. - Volume is too low or too high compared to AppleHDA. - The wrong input or output source is selected. For best results, reproduce the problem first, then run Collect-HDAUniversal.command immediately after the issue happens. This gives the log collector a better chance of capturing the real failure. Reports with complete logs are much easier to analyze and help improve HDAUniversal for more codecs, layouts, laptops, and desktop systems.

The kernel panic is: pmap_recycle_page: page 0x180003000 is referenced @pmap.c:1520 This is not a normal app crash. It means macOS detected a memory page that was still in use while the kernel was trying to recycle it. This usually points to low-level memory corruption or kernel-level instability. DaVinci Resolve was the active process, but it was probably only the trigger because it was using heavy GPU/Metal/memory resources. The real cause is more likely related to unstable RAM/XMP, VT-d/DMA, CPU topology/kernel patches, or a problematic kext/driver. In short: the KP is a kernel/memory corruption panic, not a Resolve crash.

No. Some cases need edit kext or other thing.

i2c or ps2?

No support for this gpu

Z890FreezeQuickInfo-Release.zipU can use this command and check what u need for check if have some log or other thing in system

Update bluetooth kexts. These kexts work good.

Some points Disable VMD / Intel RST / VMD Controller in BIOS. This is the main suspect because the dump shows PCH RP01-RP04 mapped under VMD. Disable ASPM / PCI Express Native Power Management / DMI ASPM in BIOS. The hard-freeze pattern is compatible with an incorrect PCIe power-state transition. AppleAHCIPort plus the 8086:7f62 Arrow Lake SATA controller being spoofed as 8086:8c02. Do u use zeroprpm on RX580? Disable Serial Port / COM Port in BIOS. This removes Apple16X50ACPI and the fake PPP serial network ports from macOS, reducing unnecessary ACPI/device noise.

The .command don't generate?

Its hard to check it. All asus z890 is very problematic. Extract one full dump with this command and lets try check it ASUS_Z890_Freeze_Diagnostics-Release.zip and post one full dump with this too https://olarila.com/files/Utils/DumpGenerator-Release.zip

Erro no download

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

SuiteBench is a professional benchmark suite for macOS designed to measure real-world performance across Apple Silicon, Intel Macs and Hackintosh. It tests CPU speed, multi-core performance, memory bandwidth, SSD read and write speed, GPU compute, Metal graphics performance, RAW processing, and system responsiveness in one clean, lightweight app. Donations Link HERE or HERE Built for users who want accurate, repeatable, and easy-to-read performance results, SuiteBench combines practical workloads with live progress, real-time test explanations, temperature monitoring, and final score summaries. Each benchmark is designed to help compare hardware, validate upgrades, check system stability, and measure performance changes after macOS updates, tuning, or hardware modifications. SuiteBench includes CPU benchmarks, memory streaming tests, SSD sequential and real-speed measurements, GPU compute tests, RAW decode workloads, and a real-time visual Metal benchmark scene. The app runs locally, does not collect analytics, does not upload results, and does not install background services. Optimized for speed, privacy, and clarity, SuiteBench provides a modern benchmark experience for creators, developers, technicians, hardware enthusiasts, and Mac power users who need reliable performance testing on macOS. Download HERE Anyone who would like to support the project with donations is very welcome and greatly appreciated. Link HERE CPU Single-Core: Measures one-core performance with mixed text, binary, image, simulation, and vector workloads. CPU Multi-Core: Runs the same workload across all logical cores to measure total CPU throughput and scaling. CPU Workflow: Simulates production tasks such as data transforms, compression-style work, and hashing. Memory Stream: Measures memory bandwidth with large copy, scale, and add operations. CPU Tile Render: Renders procedural CPU tiles with lighting to measure sustained render performance. GPU Visual Tour: Runs a real-time Metal scene with camera motion, geometry, lighting, and GPU load. Metal Compute: Tests GPU compute performance with Metal kernels over large buffers. OpenCL Compute: Measures parallel compute performance through OpenCL when available. RAW CPU Decode: Simulates 4K RAW decoding on the CPU with demosaic and color processing. RAW Metal Decode: Simulates 8K RAW decoding accelerated by Metal. SSD Sequential: Measures sequential read and write speed using a large temporary file. SSD Real Speed: Measures real uncached volume throughput in MB/s or GB/s. SSD Random: Measures 4K random read and write responsiveness.

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

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.