Jake Lo

you could try verbose mode if you're having installation issue. Hit the space bar at Clover GUI and select it.

Install Clover to the Internal drive with the same files and settings as you did when building the USB Installer.

This is the Clover guide I support. Don't use Uni stuff here.

Can't remember, but it'll set the value to 0x3 if it's not already. Enter setup_var 0x432 to see the value to confirm.

Make sure to install latest Clover prior to upgrading. If you have everything working on 10.12.4, they will continue working the same.

Attach screenshot of the output after running the permission fix and rebuild cache Also attach screenshot of Audio under System Reports.

The offset won't change no matter what version of BIOS you're on. Are on getting the same KP even after changing the dvmt?

EDIT: Fixed belive me or not... I moved the RAM from Slot B to A and I can start the install now. May you can add this to your guide! It is in the troubleshooting post... As for sound, did you add the kexts in /EFI/Clover/kexts/Other/LE to /Library/Extensions and run the permission fix and rebuild cache? This is in the post installation.

Make sure to use latest boot files from here under 10.12.4 update

Yes, that should work.

Make sure you have HFSPlus.efi in /EfI/Clover/driver64UEFI

Yes! The fat32 could be an SDCard, could be as small as 256MB.

Nothing, you only use the text file to find the offsets. Continue on with Step 5 -> 8

Are you on BIOS version 1.5.4? Latest bootpack was based on that. If that still doesn't work, then you'll have to patch all your SSDT/DSDT from your raw files exported through Clover menu - F4 Patches for DSDT are the following in this order: rename HDAS to HDEF Rename HECI to IMEI From Rehabman github _DSM to XDSM HDEF layout1 GFX0 to IGPU Mutex HPET Fix IRQ Fix OS X Check Fix (Windows 2013) RTC Fix LPC Skylake USB 3.0 _pwr 0x6D Skylake Finally add this for graphics + menu glitch fix # Use this patch if your laptop has Skylake HD 520 graphics# into method label _DSM parent_adr 0x00020000 remove_entry; into device name_adr 0x00020000 insert begin Method (_DSM, 4, NotSerialized)\n {\n If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }\n Return (Package()\n {\n "AAPL,ig-platform-id", Buffer() { 0x00, 0x00, 0x16, 0x19 },\n "hda-gfx", Buffer() { "onboard-1" },\n "model", Buffer() { "Intel HD 520" },\n "AAPL,GfxYTile", Buffer() { 0x01, 0x00, 0x00, 0x00 },\n })\n }\n end; You'll need to patch the SSDTs without the xx after the numbers as well, place them in the patched folder along with SSDT-PNLF.aml included in my bootpack. Change the Config.plist SSDT sort order accordingly with the new SSDT-xx.aml

You don't install OS X to the USB stick. You install it to the internal SSD. If you don't see the SSD, perhaps you have NVME drive? Check the BIOS to confirm.

Try booting to Clover GUI ->Options ACPI patching -> DSDT name: Change it to BIOS.aml Tables dropping -> Uncheck Drop all OEM SSDT, place check next to all the Drop "SSDT-xx.aml" below it. Return to main menu and boot up OS X. Note: This disables all the patched SSDT/DSDT. See if Wireless show up.

You can verify by going into system report->SATA/SATA Express Select your SSD on the right Below you should see TRIM Support: Yes is enabled or No if it's not

can you add a new interface and select wifi?

I meant these steps: 1) Universal BIOS Backup ToolKit 2.0.exe - to backup the BIOS (DellInc.-1.5.3.rom) At time of writing - BIOS version 1.5.3 2) UEFITool.exe to find the module labeled Setup and extract the PE32 image section (setup.bin) Update: For Dell Only: Search with this GUID then extracting the PE32 body under it would be faster /easier than finding the module per guide 899407d7-99fe-43d8-9a21-79ec328cac21 3) Universal IFR Extractor.exe to extract setup.bin to a readable text file 4) Use notepad to search for DVMT in the text file, 2 were found at 0x432 and 0x433 Both with value of 0x1 but only 0x432 needs to be set to 0x3 5) Format a USB drive to fat32 and create a folder name EFI (SD Card works too) 6) Download the EFI Shell and extract the Boot folder into the newly created EFI folder i.e.. /EFI/Boot/bootx64.efi 7) Boot system with the USB and select UEFI Boot 8) At the grub prompt, enter these commands, hit enter after each command, then exit and reboot setup_var 0x3 but if you opt for the kext, you need to build it with Xcode from the source code provided.

check if you already have the patch in Config file if not you could run this in terminal sudo trimforce enable

just follow the steps I had posted, executable and links are provided.

You need to set the DVMT pre-allocation. See Prerequisite here or add Lilu.kext and IntelGraphicsDVMTFixup.kext to /Kexts/Other

this output is from my E7450 with DW1560. Seems yours is still missing the 2 Brcm* kexts. and I don't use USBInjectAll in my bootpack. All USB ports works just fine. sudo permission.sh Password: rebuilding //System/Library/PrelinkedKernels/prelinkedkernel kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_Intel_HD_Graphics.kext kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_Broadcom_WiFi.kext kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext EAPDFix.kext kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmPatchRAM2.kext kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmFirmwareRepo.kext kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleHDA_ALC293.kext kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AppleBacklightInjector.kext kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIPoller.kext kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext AppleMobileDevice.kext KernelCache ID: 0E62D8923D08C5FAC6C57E9023283835 kextcache updated critical boot files, requesting launchd reboot Finished

Does it have power coming out of the monitor? Had you tried unplugging the power of the display, wait a minute and replug it again to see if it comes on?

Replace your bootpack with this updated bootpack.