MaLd0n

-NoteBook KabyLake Download HERE

An open source kernel extension bringing a platform for arbitrary kext, library, and program patching throughout the system for macOS. Link HERE Features Generic kext patcher Generic process patcher (64-bit with basic 32-bit functionality) Generic framework/library patcher (64-bit with basic 32-bit functionality) Provides a unified plugin API Installation You should install this kext along with the plugin kexts depending on it. The prebuilt binaries are available on releases page. Several existing plugins possibly with code samples are available on known plugins page. To compile a plugin copy the debug version of Lilu.kext into its directory. Configuration Add -liludbg to enable debug printing (available in DEBUG binaries). Add -liludbgall to enable debug printing in Lilu and all loaded plugins (available in DEBUG binaries). Add -liluoff to disable Lilu. Add -liluuseroff to disable Lilu user patcher (for e.g. dyld_shared_cache manipulations). Add -liluslow to enable legacy user patcher. Add -lilulowmem to disable kernel unpack (disables Lilu in recovery mode). Add -lilubeta to enable Lilu on unsupported OS versions (macOS 13 and below are enabled by default). Add -lilubetaall to enable Lilu and all loaded plugins on unsupported os versions (use very carefully). Add -liluforce to enable Lilu regardless of the mode, OS, installer, or recovery. Add liludelay=1000 to enable 1 second delay after each print for troubleshooting. Add lilucpu=N to let Lilu and plugins assume Nth CPUInfo::CpuGeneration. Add liludump=N to let Lilu DEBUG version dump log to /var/log/Lilu_VERSION_KERN_MAJOR.KERN_MINOR.txt after N seconds Peculiarities Most of the plugins cease to function in safe (-x) mode. By default Lilu itself does not function in single-user (-s) mode, unless -liluforce is present. Contribution For the contributors with programming skills the headers are filled with AppleDOC comments. Earlier code changes could be tracked in AppleALC project. Writing and supporting code is fun but it takes time. Please provide most descriptive bugreports or pull requests. Credits Apple for macOS and lzvn decompression Brad Conte for SHA-256 implementation fG! for Onyx The Black Cat used as a base of the kernel patcher Nguyen Anh Quynh for capstone disassembler module Pike R. Alpha for original lzvn decompression Ralph Hempel for umm_malloc static pool allocator Vyacheslav Patkov for hde64 simple disassembler module 07151129 for some code parts and suggestions vit9696 for writing the software and maintaining it

Lilu Kernel extension for installing Rosetta Cryptex in macOS Ventura. Applicable for both OS installation and updates. Link HERE With macOS Ventura, Apple finally dropped the last Mac that lacked the AVX2.0 CPU instruction, the 2013 Trash Can Mac Pro (MacPro6,1). With this, systems lacking AVX2.0 can no longer boot Ventura natively as Apple has stripped the legacy non-AVX2.0 dyld shared caches from the OS. However due to compatibility issues with Rosetta 2, Apple is forced to retain a pre-AVX2.0 dyld shared cache on Apple Silicon systems. Thus to support older machines, this kext will force the macOS installer/updater to install the Apple Silicon Cryptex (OS.dmg) instead of the stock Intel variant. More information can be found under macOS Ventura and OpenCore Legacy Patcher Support: Issue 998. Additionally this kext will disable Cryptex hash verification in APFS.kext. Additional notes: Delta Updates will not be supported with patched Cryptexes, Full Updates will be requested instead. Delta: 1-3GB~ Full Update: 12GB Rapid Secuirty Response Updates are currently not supported at this time. macOS only distributes x86_64h-based deltas on x86 machines, which are incompatible with the Rosetta Cryptex. If CryptexFixup determines your system already supports AVX2.0, it will not do anything (unless explicitly requested).Systems supporting AVX2.0 natively: Intel Haswell and newer AMD Excavator/Ryzen and newer Systems lacking AVX2.0: Intel Ivy Bridge and older AMD Bulldozer/Piledriver/Steamroller and older This kext does not drop the requirement for AVX2.0 in some of Ventura's Graphics Stack AMD Polaris, Vega and Navi Drivers in Ventura will not function without AVX2.0 support, end users will need to find alternative ways to achieve graphics acceleration Apple's Paravirtualized Graphics Stack still supports pre-AVX2.0 systems ex. VMware Fusion on Monterey host lacking AVX2.0, guest VM running Ventura Boot arguments -cryptoff (or -liluoff) to disable -cryptdbg (or -liludbgall) to enable verbose logging (in DEBUG builds) -cryptbeta (or -lilubetaall) to enable on macOS newer than 13 -crypt_allow_hash_validation to disable APFS.kext patching -crypt_force_avx to force install the Rosetta Cryptex on AVX2.0 systems Credits Apple for macOS vit9696 for Lilu.kext DhinakG for research and development khronokernel for research and development

New VoodooPS2Trackpad uses VoodooInput's Magic Trackpad II emulation in order to use macOS native driver instead of handling all gestures itself. Link HERE This enables the use of any from one to four finger gestures defined by Apple including: Look up & data detectors Secondary click (with two fingers, in bottom left corner*, in bottom right corner*) Tap to click Scrolling Zoom in or out Smart zoom Rotate Swipe between pages Swipe between full-screen apps (with three or four fingers) Notification Centre Mission Control (with three or four fingers) App Exposé (with three or four fingers) Dragging with or without drag lock (configured in 'Accessibility'/'Universal Access' prefpane) Three finger drag (configured in 'Accessibility'/'Universal Access' prefpane, may work unreliably**) Launchpad (may work unreliably) Show Desktop (may work unreliably) Screen zoom (configured in 'Accessibility'/'Universal Access' -> Zoom -> Advanced -> Controls -> Use trackpad gesture to zoom) It also supports BetterTouchTool. In addition this kext supports Force Touch emulation (configured in Info.plist): Mode 0 – Force Touch emulation is disabled (you can also disable it in System Preferences without setting the mode). Mode 1 – Force Touch emulation using a physical button: on ClickPads (touchpads which have the whole surface clickable (the physical button is inside the laptop under the bottom of touchpad)), the physical button can be remapped to Force Touch. In such mode a tap is a regular click, if Tap to click gesture is enabled in System Preferences, and a click is a Force Touch. This mode is convenient for people who usually tap on the touchpad, not click. Mode 2 – 'wide tap': for Force Touch one needs to increase the area of a finger touching the touchpad***. The necessary width can be set in Info.plist. Mode 3 – pressure value is passed to the system as is; this mode shouldn't be used. Mode 4 (by @Tarik02) – pressure is passed to the system using the following formula: The parameters in the formula are configured using ForceTouchCustomUpThreshold, ForceTouchCustomDownThreshold and ForceTouchCustomPower keys in Info.plist or configuration SSDT. Note that ForceTouchCustomDownThreshold is the upper limit on the pressure value and vice versa, because it corresponds to the touchpad being fully pressed down. For Elan touchpad, only mode 0 and mode 1 are supported. For ALPS touchpads, V1, V2 and V6 do not support Force Touch. V3, V4 and V5 only support mode 0, 2, 3 and 4. V7 only supports mode 0 and 1. V8 supports all modes. Installation and compilation For VoodooPS2Trackpad.kext to work multitouch interface engine, named VoodooInput.kext, is required. For released binaries a compatible version of VoodooInput.kext is already included in the PlugIns directory. For custom compiled versions VoodooInput.kext bootstrapping is required prior to compilation. By default Xcode project will do this automatically. If you prefer to have your own control over the process execute the following command in the project directory to have VoodooInput bootstrapped: src=$(/usr/bin/curl -Lfs https://raw.githubusercontent.com/acidanthera/VoodooInput/master/VoodooInput/Scripts/bootstrap.sh) && eval "$src" || exit 1 Touchpad and Keyboard Input Toggle This kext supports disabling touch input by pressing the Printscreen key on your keyboard, or the touchpad disable key on many laptops. Simply press the key to toggle touchpad input off and again to toggle it back on. In addition, for 2-in-1 systems that do not support disabling the keyboard in hardware while in tablet mode you may toggle keyboard input off and on by holding option(Windows) and pressing the Printscreen key. Repeat the keypress to re-enable keyboard input. These settings are runtime only and do not persist across a reboot. Credits: VoodooPS2Controller etc. – turbo, mackerintel, @RehabMan, nhand42, phb, Chunnan, jape, bumby (see RehabMan's repository). Magic Trackpad 2 reverse engineering and implementation – https://github.com/alexandred/VoodooI2C project team. VoodooPS2Trackpad integration – @kprinssu. Force Touch emulation and finger renumbering algorithm** – @usr-sse2. Elan touchpad driver – linux kernel contributors, @kprinssu, @BAndysc and @hieplpvip * On my touchpad this gesture was practically impossible to perform with the old VoodooPS2Trackpad. Now it works well. ** Due to the limitations of PS/2 bus, Synaptics touchpad reports only the number of fingers and coordinates of two of them to the computer. When there are two fingers on the touchpad and third finger is added, a 'jump' may happen, because the coordinates of one of the fingers are replaced with the coordinates of the added finger. Finger renumbering algorithm estimates the distance from old coordinates to new ones in order to hide this 'jump' from the OS and to calculate approximate position of the 'hidden' finger, in assumption that fingers move together in parallel to each other. Now third and fourth fingers are reported at the same position as one of the first two fingers. It allows Launchpad/Show desktop gesture to work more reliably. *** The touchpad reports both finger width (ranged from 4 to 15) and pressure (ranged from 0 to 255), but in practice the measured width is almost always 4, and the reported pressure depends more on actual touch width than on actual pressure.

Most Broadcom USB Bluetooth devices make use of a system called RAMUSB. RAMUSB allows the firmware for the device to be updated on-the-fly, however any updates previously applied are lost when shutting down the machine. The Broadcom Windows driver will upload firmware into the Broadcom Bluetooth device on every startup, however for macOS this functionality is not supported out of the box. BrcmPatchRAM kext is a macOS driver which applies PatchRAM updates for Broadcom RAMUSB based devices. It will apply the firmware update to your Broadcom Bluetooth device on every startup / wakeup, identical to the Windows drivers. The firmware applied is extracted from the Windows drivers and the functionality should be equal to Windows. Note that the original Apple Broadcom bluetooth devices are not RAMUSB devices, and thus do not have the same firmware mechanism. Link HERE Installation Note if you have an Apple MacBook/iMac/Mac Pro etc, follow the Mac instructions Install one of BrcmPatchRAM.kext or BrcmPatchRAM2.kext or BrcmPatchRAM3.kext depending on macOS version, never both. BrcmPatchRAM.kext: for 10.10 or earlier. BrcmPatchRAM2.kext: for 10.11 - 10.14. BrcmPatchRAM3.kext: for 10.15 or later. Also, install one firmware kext BrcmFirmwareData.kext or BrcmFirmwareRepo.kext, depending on installation location, never both. BrcmFirmwareData.kext: Most appropriate for bootloader injection. This is the preferred configuration. BrcmFirmwareRepo.kext: Install to /System/Library/Extensions (/Library/Extensions on 10.11 and later). This kext is slightly more memory efficient than BrcmFirmwareData.kext, but cannot be injected by a bootloader. Advanced users: For custom firmware injectors, install the injector plus BrcmFirmwareRepo.kext. This works from either /S/L/E or through bootloader injection. Optionally, you may remove all the firmwares from BrcmFirmwareRepo.kext/Contents/Resources. If you're using the injector through the bootloader, the IOProviderClass in the Info.plist for BrcmFirmwareRepo.kext must be changed from "disabled_IOResources" to "IOResources". Keep in mind that BrcmPatchRAM3.kext also requires BrcmBluetoothInjector.kext to be installed. Starting with macOS 10.15, this is the only supported configuration because due to framework changes BrcmPatchRAM.kext and BrcmPatchRAM2.kext are incompatible with macOS 10.15. In case you forget to install BrcmBluetoothInjector.kext, Bluetooth will appear to be available but it won't work at all. Also, if you have a non-PatchRAM device (or you're not sure), install one of BrcmNonPatchRAM.kext or BrcmNonPatchRAM2.kext, depending on macOS version, never both. Although these kexts do not install any firmware (these devices have firmware built-in), they still depend on BrcmPatchRAM/BrcmPatchRAM2.kext. BrcmNonPatchRAM.kext: for 10.10 or earlier BrcmNonPatchRAM2.kext: for 10.11 or later. BrcmBluetoothInjector.kext To be used for macOS 10.11-11. Use BrcmBluetoothInjectorLegacy.kext for older systems. Using BrcmPatchRAM3.kext also requires BrcmBluetoothInjector.kext as changes in macOS Catalina (10.15) requires the use of a separate injector kext. This is due to the removal of the following IOCatalogue methods: IOCatalogue::addDrivers, IOCatalogue::removeDrivers and IOCatalogue::startMatching Consequently to have the native BT driver load for the device (BroadcomBluetoothHostControllerUSBTransport) we inject using a plist with a slightly lower IOProbeScore than BrcmPatchRAM3 so it doesn't probe before the firmware upload. The BrcmBluetoothInjector.kext is a codeless kernel extension which injects the BT hardware data using a plist; it does not contain a firmware uploader. You might also want to try this kext if you wish to see if your device will work without a firmware uploader. Do not use BrcmPatchRAM or BrcmPatchRAM2 with this kext. BrcmBluetoothInjector supported devices: [0489:e030] BCM2070 - BCM943224HMB, BCM943225HMB Combo [0489:e032] 20702 E032 Combo [0489:e042] 20702A1 Lenovo China standalone [0489:e046] 20702A1 Acer 43228+20702 combo card [0489:e04f] 20702A1 Lenovo China 43227 WLAN + 20702A1 Combo card [0489:e052] 20702 non-UHE Generic [0489:e055] 43142A0 Acer combo [0489:e059] Acer 43228 + 20702A1 combo [0489:e079] Lenovo China 43162 NGFF [0489:e07a] Lenovo China 4352+20702 NGFF [0489:e087] Acer 43228 NGFF combo module [0489:e096] BCM43142A0 [0489:e097] Acer Foxconn BCM4356A2 NGFF [0489:e0a1] 20703A1 Lenovo 43602 NGFF combo [04b4:f901] Laird BT851 Bluetooth 5.0 USB dongle [04ca:2003] 20702A1 Lenovo China standalone [04ca:2004] LiteOn 43228+20702 combo [04ca:2005] LiteOn 43228+20702 combo [04ca:2006] LiteOn 43142 combo [04ca:2009] LiteOn 43142 combo [04ca:200a] LiteOn 4352 combo [04ca:200b] LiteOn 4352 combo [04ca:200c] LiteOn 4352 combo [04ca:200e] Liteon 43228 NGFF combo [04ca:200f] Acer_LiteOn BCM20702A1_4352 [04ca:2012] Acer BCM943142Y NGFF [04ca:2013] Acer LiteOn BCM4356A2 NGFF [04ca:2014] Asus LiteOn BCM4356A2 NGFF [04ca:2016] Lenovo 43162 NGFF combo module [04f2:b4a1] ASUS Chicony BCM43142A0 NGFF [04f2:b4a2] BCM4356A2 [050d:065a] 20702 standalone [0930:021e] 20702A1 Toshiba standalone [0930:021f] Toshiba 43142 [0930:0221] 20702A1 Toshiba 4352 [0930:0223] 20702A1 Toshiba 4352 [0930:0225] Toshiba 43142 combo NGFF [0930:0226] Toshiba 43142 combo NGFF [0930:0229] 43162 combo NGFF [0a5c:2168] BRCM Generic 43162Z [0a5c:2169] BRCM Generic 43228z [0a5c:216a] Dell DW1708 43142Y combo [0a5c:216b] HP Rapture 4352z ngff combo [0a5c:216c] HP Harrier 43142 [0a5c:216d] HP Hornet 43142Y ngff combo [0a5c:216e] HP Blackbird 43162 NGFF [0a5c:216f] Dell DW1560 4352+20702 M.2 [0a5c:217d] BCM2070 - BCM943224HMB, BCM943225HMB Combo [0a5c:21d7] BRCM Generic 43142A0 RAMUSB [0a5c:21de] 4352+20702A1 combo [0a5c:21e1] 20702A1 non-UHE HP SoftSailing [0a5c:21e3] 20702A1 non-UHE 4313 combo HP Valentine [0a5c:21e6] 20702 non-UHE Lenovo Japan [0a5c:21e8] 20702A1 dongles [0a5c:21ec] 20702A1 REF6 OTP module standalone [0a5c:21f1] 43228 combo [0a5c:21f3] Lenovo Edge 43228 + 20702A1 combo [0a5c:21f4] Lenovo Edge 4313 + 20702A1 combo [0a5c:21fb] HP Supra 4352 20702A1 combo [0a5c:21fd] BRCM Generic 4352z RAMUSB [0a5c:640a] BRCM Generic Reference 4356 [0a5c:640b] HP Luffy 43228 + 20702 M.2 [0a5c:640e] Lenovo 4356 NGFF combo [0a5c:6410] 20703A1 RAM download - DW1830 43602 [0a5c:6412] Dell 4350C5 [0a5c:6413] Broadcom Generic 4350C5 [0a5c:6414] Lenovo 4350C5 [0a5c:6417] Zebra 4352 [0a5c:6418] HP Brook 2x2ac [0a5c:7460] 20703A1 RAM download [0a5c:828d] Fenvi BCM94352Z [0b05:178a] BCM2070 - BCM943224HMB, BCM943225HMB Combo [0b05:17b5] Asus 43228+20702A1 combo [0b05:17cb] 20702 standalone [0b05:17cf] Asus 4352_20702A1 combo [0b05:180a] Azurewave 4360+20702 combo [0b05:181d] Asus AZUREWAVE MB BCM4356A2 [0bb4:0306] 20703A1 HTC runtime RAM dongle [105b:e065] LenovoChina 43142A0 combo [105b:e066] LenovoChina 43228+20702 combo [13d3:3384] 20702A1 Azurewave standalone [13d3:3388] BRCM Generic 43142A0 RAMUSB [13d3:3389] BRCM Generic 43142A0 RAMUSB [13d3:3392] Azurewave 43228+20702 [13d3:3404] 4352HMB Azurewave Module [13d3:3411] Dell Alienware 4352 20702A1 combo [13d3:3413] Azurewave 4360+20702 combo [13d3:3418] Azurewave 4352+20702 combo module [13d3:3427] Toshiba 43142 combo NGFF [13d3:3435] AZUREWAVE BCM20702A1_4352 [13d3:3456] AZUREWAVE BCM20702A1_4352 [13d3:3473] Asus AZUREWAVE BCM4356A2 NGFF [13d3:3482] AZUREWAVE BCM43142A0 NGFF [13d3:3484] Acer AZUREWAVE BCM43142A0 NGFF [13d3:3485] Asus AZUREWAVE BCM4356A2 NB 2217NF [13d3:3488] Asus AZUREWAVE BCM4356A2 NB 2210 [13d3:3492] Asus AZUREWAVE BCM4356A2 NGFF [13d3:3504] AW CM217NF BCM4371C2 [13d3:3508] AW ASUS CM217NF BCM4371C2 [13d3:3517] AW CE160H BCM20702 [145f:01a3] 20702A1 Asus Trust standalone [2b54:5600] Emdoor AP6356SD BCM4356A2 [2b54:5601] Asus AP6356SDP1A BCM4356A2 [2b54:5602] AMPAK AP6356SDP2A BCM4356A2 [33ba:03e8] TOULINEUA BCM94360Z4 4360+20702 combo [33ba:03e9] TOULINEUA BCM94360Z3 4360+20702 combo [413c:8143] DW1550 4352+20702 combo [413c:8197] Dell DW380 Nancy Blakes standalone If yours is not present, edit the Info.plist as needed. BlueToolFixup.kext Required for macOS 12 or newer, as in macOS 12 Apple has changed parts of the Bluetooth stack from kernel-space to user-space as detailed in here and here. Requires Lilu 1.5.4+ Do not use it with BrcmBluetoothInjector for macOS 12 or newer. Supported Devices BrcmPatchRAM supports any Broadcom USB bluetooth device based on the BCM20702 chipset (possibly other chipsets are supported also, but this has not been tested). The following devices are supported at the moment: Devices marked with * are tested successfully Non-PatchRAM devices (BrcmPatchRAM used to speed up recovery after sleep): [03f0:231d] HP 231d (ProBook BT built-in firmware) [13d3:3295] Azurewave BCM943225 (20702A bult-in firmware) Tested PatchRAM devices: [0489:e032] 20702 Combo USB [0489:e042] 20702A1 Lenovo China * [0489:e079] Lenovo China 43162 NGFF [0489:e07a] Lenovo NGFF (4352 / 20702) [04ca:2003] 20702A1 Lenovo China [04ca:200a] LiteOn (4352 Combo) [04ca:200b] LiteOn (4352 Combo) * [04ca:200c] LiteOn (4352 Combo) [04ca:200f] Acer / LiteOn (4352 Combo) [050d:065a] Belkin (20702) [0930:0221] Toshiba (4352 / 20702) [0930:0223] Toshiba NGFF (4352 / 20702) * [0a5c:216b] HP Rapture 4352Z NGFF Combo [0a5c:216e] HP Blackbird 43162 NGFF [0a5c:216f] Dell DW1560 (4352/20702) [0a5c:21de] 4352/20702A1 combo [0a5c:21e1] HP Softsailing (20702A1) [0a5c:21e6] non-UHE Lenovo Bluetooth (20702) [0a5c:21e8] Bluetooth USB Dongle (20702A1) * [0a5c:21ec] Inateck Bluetooth (20702A1) [0a5c:21fb] HP Supra 4352 (20702A1 Combo) [0a5c:21fd] Broadcom 4352Z [0a5c:22be] Broadcom BCM20702 Bluetooth 4.0 USB Device [0a5c:6410] Dell Wireless 1830 Bluetooth 4.1 LE [0a5c:6412] Dell Wireless 1820 Bluetooth 4.1 LE [0a5c:828d] Fenvi BCM94352Z [0b05:17cb] Asus BT-400 (20702 stand-alone) * [0b05:17cf] Asus (4352/20702A1 combo) * [0b05:180a] Azurewave (4360/20702 combo) [13d3:3404] Azurewave (4352HMB) * [13d3:3411] Dell Alienware (4352/20702A1 combo) * [13d3:3413] Azurewave (4360/20702 combo) [13d3:3418] Azurewave (4352/20702 combo) [13d3:3435] Azurewave (4352/20702 combo) [13d3:3456] Azurewave (4352/20702 combo) [413c:8143] Dell DW1550 (4352/20702 combo) All of the firmwares from the Windows package are present in the kext and automatically associated with their vendor/device-ids. They are expected to work, but have not been confirmed. If you can confirm a working device not listed above, please notify via the "issues" database on github. The firmwares have been updated to version 12.0.1.1105. More Installation Details BrcmPatchRAM.kext, BrcmPatchRAM2.kext and BrcmPatchRAM3.kext can be installed either through bootloader kext injection or placed in /System/Library/Extensions (/Library/Extensions on 10.11 and later). Make sure to install only one of them, depending on system version. BrcmFirmwareRepo.kext does not work with bootloader kext injection, unless using a device specific firmware injector. BrcmFirmwareData.kext can work with bootloader kext injection. You can also use a device specific firmware injector (in conjunction with BrcmFirmwareRepo.kext). In this scenario, BrcmFirmwareRepo.kext does work from bootloader kexts. You will find device specfic injectors in the 'firmwares' directory of the git repository. They are not included in the distribution ZIP. Configuration There are a number of delays which can be changed with the following kernel boot arguments. You might change these values if you find BrcmPatchRAM is hanging during firmware load. Refer to the source for futher details on these delays. bpr_initialdelay: Changes mInitialDelay, the delay in ms before any communication happens with the device. Default value is 100. bpr_handshake: Overrides mSupportsHandshake, firmware uploaded handshake support status. 0 means wait bpr_preresetdelay ms after uploading firmware, and then reset the device. 1 means wait for a specific response from the device and then reset the device. Default value depends on the device identifier. bpr_preresetdelay: Changes mPreResetDelay, the delay in ms assumed to be needed for the device to accept the firmware. The value is unused when bpr_handshake is 1 (passed manually or applied automatically based on the device identifier). Default value is 250. bpr_postresetdelay: Changes mPostResetDelay, the delay in ms assumed to be needed for the firmware to initialise after reseting the device upon firmware upload. Default value is 100. bpr_probedelay: Changes mProbeDelay (removed in BrcmPatchRAM3), the delay in ms before probing the device. Default value is 0. For example, to change mPostResetDelay to 400 ms, use the kernel boot argument: bpr_postresetdelay=400. Note: Some with the typical "wake from sleep" problems are reporting success with: bpr_probedelay=100 bpr_initialdelay=300 bpr_postresetdelay=300. Or slightly longer delays: bpr_probedelay=200 bpr_initialdelay=400 bpr_postresetdelay=400. On macOS 12.4 and newer versions, a new address check has been introduced in bluetoothd, thus an error will be triggered if two Bluetooth devices have the same address. However, this check can be circumvented by adding the boot argument -btlfxallowanyaddr. Details BrcmPatchRAM consists of 2 parts: BrcmPatchRAM itself communicates with supported Broadcom Bluetooth USB devices (as configured in the Info.plist), and detects if they require a firmware update. If a firmware update is required, the matching firmware data will be uploaded to the device and the device will be reset. BrcmFirmwareStore (implemented by either BrcmFirmwareData.kext or BrcmFirmwareRepo.kext) is a shared resource which holds all the configured firmwares for different Broadcom Bluetooth USB devices. Some devices require device specific firmware, while others can use the newest version available in the Windows drivers without issue. New firmwares are added/configured on a regular basis to support devices, so be sure to follow release updates, or log an issue if you find your device is not supported. Firmwares can be stored using zlib compression in order to keep the configuration size manageable. After the device firmware is uploaded, the device control is handed over to Apple's BroadcomBluetoothHostControllerUSBTransport. This means that for all intents and purposes your device will be native on macOS and support all functionalities fully. It is possible to use the Continuity Activation Patch in combination with BrcmPatchRAM through BT4LEContinuityFixup, or through dokterdok's script Continuity-Activation-Tool, or through OpenCore quirk ExtendBTFeatureFlags. Troubleshooting After installing BrcmPatchRAM, even though your Bluetooth icon may show up, it could be that the firmware has not been properly updated. Verify the firmware is updated by going to System Information and check the Bluetooth firmware version number under the Bluetooth information panel. If the version number is "4096", this means no firmware was updated for your device and it will not work properly. Verify any errors in the system log by running the following command in the terminal: # For 10.12 and newer: log show --last boot | grep -i brcm[fp] # For older macOS versions: cat /var/log/system.log | grep -i brcm[fp] Ensure you check only the latest boot messages, as the system.log might go back several days. If the firmware upload failed with an error, try installing the debug version of BrcmPatchRAM in order to get more detailed information in the log. In order to report an error log an issue on github with the following information: Device product ID Device vendor ID BrcmPatchRAM version used Dump of BrcmPatchRAM debug output from /var/log/system.log showing the firmware upload failure Firmware Compatibility Some USB devices are very firmware specific and trying to upload any other firmware for the same chipset into them will fail. This usually displays in the system log as: BrcmPatchRAM: Version 0.5 starting. BrcmPatchRAM: USB [0a5c:21e8 5CF3706267E9 v274] "BCM20702A0" by "Broadcom Corp" BrcmPatchRAM: Retrieved firmware for firmware key "BCM20702A1_001.002.014.1443.1612_v5708". BrcmPatchRAM: Decompressed firmware (29714 bytes --> 70016 bytes). BrcmPatchRAM: device request failed (0xe000404f). BrcmPatchRAM: Failed to reset the device (0xe00002d5). BrcmPatchRAM: Unable to get device status (0xe000404f). BrcmPatchRAM: Firmware upgrade completed successfully. The errors in between mean the firmware was not uploaded successfully, and the device will most likely need a specific firmware configured. For other devices the newest firmware available (even though not specified specifically in the Windows drivers) works fine. New devices In order to support a new device, the firmware for the device needs to be extracted from existing Windows drivers. A copy of the (current) latest Broadcom USB bluetooth drivers can be found here: http://drivers.softpedia.com/get/BLUETOOTH/Broadcom/ASUS-X99-DELUXE-Broadcom-Bluetooth-Driver-6515800-12009860.shtml#download For an automatic update you can unpack the Broadcom USB bluetooth files and run firmware_update.tool. Should you come across newer drivers than 12.0.0.9860, please let me know. In order to get the device specific firmware for your device take the following steps: Look up your USB device vendor and product ID, in this example we will be using the BCM94352Z PCI NGFF WiFi/BT combo card, for which the vendor is 0930 and product ID 0233. Extract the Windows Bluetooth driver package and open the bcbtums-win8x64-brcm.inf file. Find your vendor / device ID combination in the .inf file %BRCM20702.DeviceDesc%=BlueRAMUSB0223, USB\VID_0930&PID_0223 ; 20702A1 Toshiba 4352 Locate the mentioned "RAMUSB0223" device in the .inf file: ;;;;;;;;;;;;;RAMUSB0223;;;;;;;;;;;;;;;;; [RAMUSB0223.CopyList] bcbtums.sys btwampfl.sys BCM20702A1_001.002.014.1443.1457.hex Copy the firmware hex file matching your device from the Windows package, in this case "BCM20702A1_001.002.014.1443.1457.hex" The firmware file can now optionally be compressed using the included zlib.pl script: zlib.pl deflate BCM20702A1_001.002.014.1443.1457.hex > BCM20702A1_001.002.014.1443.1457.zhx After this a hex dump can be created for pasting into a plist editor: xxd -ps BCM20702A1_001.002.014.1443.1457.zhx|tr '\n' ' ' > BCM20702A1_001.002.014.1443.1457.dmp Using a plist editor create a new firmware key under the BcmFirmwareStore/Firmwares dictionary. Note that the version number displayed in macOS is the last number in the file name (1457 in our sample) + 4096. So in this case the firmware version in macOS would be: "c14 v5553". After configuring a key under BcmFirmwareStore/Firmwares, add your device ID as a new device for BrcmPatchRAM. Firmwares can also be loaded directly from BrcmFirmwareRepo.kext/Contents/Resources, either by firmware key name (see above), or by naming the file with just the vendor and device-id. For example, 0930_0223.hex (uncompressed) or 0930_0223.zhx (compressed). Copying an existing IOKit personality and modifying its properties is the easiest way to do this. Configure the earlier firmware using its unique firmware key.

An open source kernel extension providing a sync between RTC variables and NVRAM. By design the mach kernel encrypts hibernate sleepimage and writes the encryption key to variable "IOHibernateRTCVariables" in the system registry (PMRootDomain). Somehow this value has to be written into RTC (or SMC) in order the boot.efi could read it. But in case if you have to limit your RTC memory to 1 bank (128 bytes), it doesn't work: there are no any variables in SMC/NVRAM/RTC (actually FakeSMC). Fortunately, boot.efi can read key "IOHibernateRTCVariables" from NVRAM! This kext detects entering into "hibernate" power state, reads variable IOHibernateRTCVariables from the system registry and writes it to NVRAM. Link HERE Features Enables 'native' hibernation on PC's with hardware NVRAM on 10.10.5 and later. 'Native' means hibernation with encryption (standard hibernate modes 3 & 25) Enables dumping NVRAM to file /nvram.plist before hibernation or panic Boot-args -hbfx-dump-nvram saves NVRAM to a file nvram.plist before hibernation and after kernel panic (with panic info) -hbfx-disable-patch-pci disables patching of IOPCIFamily (this patch helps to avoid hang & black screen after resume (restoreMachineState won't be called for all devices) hbfx-patch-pci=XHC,IMEI,IGPU allows to specify explicit device list (and restoreMachineState won't be called only for these devices). Also supports values none, false, off. -hbfxdbg turns on debugging output -hbfxbeta enables loading on unsupported osx -hbfxoff disables kext loading hbfx-ahbm=abhm_value controls auto-hibernation feature, where abhm_value is an arithmetic sum of respective values below: EnableAutoHibernation = 1: If this flag is set, system will hibernate instead of regular sleep (flags below can be used to limit this behavior) WhenLidIsClosed = 2: Auto hibernation can happen when lid is closed (if bit is not set - no matter which status lid has) WhenExternalPowerIsDisconnected = 4: Auto hibernation can happen when external power is disconnected (if bit is not set - no matter whether it is connected) WhenBatteryIsNotCharging = 8: Auto hibernation can happen when battery is not charging (if bit is not set - no matter whether it is charging) WhenBatteryIsAtWarnLevel = 16: Auto hibernation can happen when battery is at warning level (macOS and battery kext are responsible for this level) WhenBatteryAtCriticalLevel = 32: Auto hibernation can happen when battery is at critical level (macOS and battery kext are responsible for this level) DoNotOverrideWakeUpTime = 64: Do not alter next wake up time, macOS is fully responsible for sleep maintenance dark wakes DisableStimulusDarkWakeActivityTickle = 128: Disable power event kStimulusDarkWakeActivityTickle in kernel, so this event cannot trigger a switching from dark wake to full wake When when IOPMPowerSource cannot detect warning or critical battery level (it happens on hackintosh), next 4 bits can be used to specify minimal capacity percent remaining value when hibernation will be forced: RemainCapacityBit1 = 256 (1) RemainCapacityBit2 = 512 (2) RemainCapacityBit3 = 1024 (4) RemainCapacityBit4 = 2048 (8) Specified minimal capacity will be also used to put macOS into sleep/hibernate state (when the remaining capacity is less than it). 4 bits can be used to specify the battery levels from 1 to 15. Bits RemainCapacityBit1-RemainCapacityBit4 are 1,2,4,8 in percentage, so for example if you want to have 10 percent level to be the point where the laptop goes into sleep/hibernation, you would add Bits RemainCapacityBit4 and RemainCapacityBit2 which would be 2048+512=2560 (8+2=10 percent) in hbfx-ahbm. Bit EnableAutoHibernation defines a final state (sleep or hibernate). NVRAM options The following options can be stored in NVRAM (GUID = E09B9297-7928-4440-9AAB-D1F8536FBF0A), they can be used instead of respective boot-args hbfx-dump-nvram - type Boolean hbfx-disable-patch-pci - type Boolean hbfx-patch-pci=XHC,IMEI,IGPU,none,false,off - type String hbfx-ahbm - type Number Dependencies Lilu Credits Apple for macOS vit9696 for Lilu.kext and great help in implementing some features lvs1974 for writing the software and maintaining it

Lilu Kernel extension for enabling Sidecar, NightShift, AirPlay and Universal Control. Link HERE Additional Notes NightShift (macOS 10.12.4+) AirPlay to Mac (macOS 12.0+) Universal Control (macOS 12.3+) Requires minimum of Wifi N and Bluetooth 4.0 for wireless, wired is supported between iPad and Mac as an alternative Note all parties check each other for compatibility, thus requiring FeatureUnlock on all models in the chain Seen as Ineligible Device Found Md MacBookPro11,4, SV 340.17.2 in Console under UniversalControl: com.apple.universalcontrol Recommend using a different SMBIOS if possible, otherwise use -force_uc_unlock for machines that are not blacklisted but are connecting with a blacklisted model. Due to the nature of requiring FeatureUnlock for both models, Apple Silicon and iPads will not work Sidecar (macOS 10.15.0+) Requires minimum of Wifi N and Bluetooth 4.0 for wireless, wired is supported between iPad and Mac as an alternative Requires a machine with an Intel iGPU active for reliable usage, most dGPU-only machines will experience difficulties. An H.265 capable iGPU is recommended for best streaming quality. AMD dGPU-only machines may work if using an iMac19,x or iMac20,x SMBIOS with gvaForceAMDKE setting applied: defaults write com.apple.AppleGVA gvaForceAMDKE -boolean yes Boot arguments -caroff (or -liluoff) to disable -cardbg (or -liludbgall) to enable verbose logging (in DEBUG builds) -carbeta (or -lilubetaall) to enable on macOS newer than 13 -allow_sidecar_ipad enables Sidecar support for unsupported iPads -disable_sidecar_mac disables Sidecar/AirPlay/Universal Control patches -disable_nightshift disables NightShift patches -force_uni_control forces Universal Control patching even when model doesn't require Credits Apple for macOS vit9696 for Lilu.kext khronokernel for developing AirPlay to Mac and Universal Control patch sets and maintaining Sidecar patch set Osy and DhinakG for Polaris22Fixup base Ben-z for original SidecarCore patch set Pike R. Alpha and cdf for NightShift patch set

MacOS kernel extension for devices complying with the Secure Digital Host Controller (SDHC) specification. Currently only supports eMMC/MMC cards at up to HS200 speeds. Link HERE

Lilu plugin providing patches to select GPUs on macOS. Link HERE Features Fixes boot to black screen on AMD and NVIDIA Fixes sleep wake to black screen on AMD Fixes boot screen distortion in certain cases Fixes transmitter/encoder in autodetected connectors for multimonitor support (-raddvi) Fixes HD 7730/7750/7770/R7 250/R7 250X initialisation (radpg=15) Allows tuning of aty_config, aty_properties, cail_properties via ACPI Allows enforcing 24-bit mode on unsupported displays (-rad24) Allows booting without video acceleration (-radvesa) Allows automatically setting GPU model name or providing it manually for RadeonFramebuffer Allows specifying custom connectors via device properties for RadeonFramebuffer Allows tuning autodetected connector priority via device properties (HD 7xxx or newer) Fixes an issue in AppleGraphicsDevicePolicy.kext so that we could use a MacPro6,1 board-id/model combination, without the usual hang with a black screen. Patching AppleGraphicsDevicePolicy.kext Modifies macOS to recognize NVIDIA's web drivers as platform binaries. This resolves the issue with transparent windows without content, which appear for applications that use Metal and have Library Validation enabled. Common affected applications are iBooks and Little Snitch Network Monitor, though this patch is universal and fixes them all. NVWebDriverLibValFix Injects IOVARendererID into GPU properties (required for Shiki-based solution for non-freezing Intel and/or any discrete GPU) For Intel HD digital audio HDMI, DP, Digital DVI (Patches connector-type DP -> HDMI) Fixes NVIDIA GPU interface stuttering on 10.13 (official and web drivers) Fixes the kernel panic caused by an invalid link rate reported by DPCD on some laptops with Intel IGPU. Fixes the infinite loop on establishing Intel HDMI connections with a higher pixel clock rate on Skylake, Kaby Lake and Coffee Lake platforms. Implements the driver support for onboard LSPCON chips to enable DisplayPort to HDMI 2.0 output on some platforms with Intel IGPU. Enforces complete modeset on non-built-in displays on Kaby Lake and newer to fix booting to black screen. Allows non-supported cards to use HW video encoder (-radcodec) Fixes choppy video playback on Intel Kaby Lake and newer. Fixes black screen on Intel HD since 10.15.5. Adds workaround for rare force wake timeout panics on Intel KBL and CFL. Supports all valid Core Display Clock (CDCLK) freqencies on Intel ICL platforms. Fixes the kernel panic caused by an incorrectly calculated amount of DVMT pre-allocated memory on Intel ICL platforms. Makes brightness transitions smoother on Intel IVB+ platforms. Fixes the short period garbled screen issue after the system boots on Intel ICL platforms. Fixes the PWM backlight control of the built-in display that is directly wired to AMD Radeon RX 5000 series graphic cards. Fixes the freeze during iGPU initialization that may occur on certain laptops such as Chromebooks on macOS 10.15 and later.

An opensource trackpad aggregator kernel extension providing Magic Trackpad 2 software emulation for arbitrary input sources like VoodooPS2. Link HERE

A native AML compiler and IDE for macOS, with syntax coloring, tree navigation, automated patching, online patch file repositories, and iASL binary updates. Written entirely in Cocoa, conforms to macOS guidelines. Link HERE Features Syntax Coloring Live tree navigation Native OS X autosaving and restore File patching Online patch file repositories Updatable iASL binary Customizable text and layout Compiler summary and hinting

VirtualSMC - Advanced Apple SMC emulator in the kernel - Hackintosh Link HERE Features Supports macOS 10.4 and newer (10.9 and newer is recommended) Implements MMIO protocol and interrupt-based responses for compatibility with modern OS Properly reports key attributes and r/w protection in the keys Allows tuning on per-model basis and allows to use different SMC generations Extensible by the plugins for sensor and key addition support Enables smcdebug=XX boot argument support on 10.9 Replaces hardware SMC it finds (to disable SMC entirely you need to flash a dedicated firmware)

No support for amd 6500, go to rx580 or 6600 and others with native support

U can try check github search with igpu for ur processor

try remap usb and check what device cause it.

Use this efi folder https://www.transfernow.net/dl/20230224PpFuJdRl Save one ioreg with ioregExplorer app https://olarila.com/files/Utils/IORegistryExplorer.app.zip

Enjoy!

somethings is wrong in procedure -Bios/UEFI in full default settings(Just change settings if need) -Use USB2 port for easy installation with no remap USB -Users with IGPU can use -igfxvesa bootarg for easy installation -Delete old EFI folder and paste new. 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

kill _prw to avoid auto wake

What hardware? https://www.olarila.com/topic/20908-easy-fast-and-perfect-vanilla-hackintosh/

DSDT.aml.zip VIDEO PATCH start with this u need change smbios to iMac19,2

Ok. Go.

1- Hello community. Some of users are telling that they aren't receiving the "reward" of their Donation, such as joining at the Premium/Donators group and others privileges. And to fix that we need that you do something for us, it's simple: 2- Take a screenshot of the confirmation of your donation - I don't need your personal data, only the confirmation. 3- Send me screenshot with proof and your nick HERE or you can open one topic HERE. 30$ = Donator User with Personal room, Private Message, unlimited upload with 10mb per file. 50$ = Premium User with Personal room, Private Message, unlimited upload with 30mb per file. 100$ = Premium Black User with Personal room, Private Message, unlimited upload with 60mb per file and no ADS. 4- Problems with Paypal Donate? CHECK HERE! 5- Visit DONATORS ROOM for premium support! (Only Donators and Premium Users) 6- If you will consider a donation to Olarila.com, we will spend the money on buying more bandwidth and more servers to offer the best speed, guides, patches, etc. Thank you for any donation! -Donations Links- PayPal HERE - Ko-Fi HERE - Mercado Livre HERE Skrill danielnmaldonado@gmail.com BTC 1BDzsV4bw3DVCiffFAeNKsdEzqkPXNVrXR ETH BSC BEP20 0xb57cfdfa371fad1981910f0e8332409ab99f74d9 BNB 0x10D1d656eCa00bD521f9b4A43B83098B8142e115 USDT BSC BEP20 0xb57cfdfa371fad1981910f0e8332409ab99f74d9 USDT TRC20 TUR6Z9AVS4AYzqPnULoHrfFvppRbhXmNbZ PicPay @danielnmaldonado PiX @danielnmaldonado@gmail.com Problems with Paypal HERE

https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md Yes

this igpu don't have support under macos