Jake Lo

Sure, full detailed guide here

I already had files posted here for BS but should work for Mojave too. I have it currently running Catalina and BS. https://osxlatitude.com/forums/topic/9179-dell-latitude-e7x70-installation-guides-uefi-only-clover-and-opencore/?do=findComment&comment=104256

just compress the Clover folder, don't need the entire EFI, leave out themes folder too

Yes! Just need Other. Off is for kext you want to test during boot but disable. You can enabled it during boot at Clover option

do you have any other directory inside Kexts folder other than Other? if yes, delete them, just need Other and Off if you have it

For Mojave, use BrcmPatchRAM2.kext instead of BrcmPatchRAM3.kext. BrcmPatchRAM3.kext is for Catalina and higher

take out battery to reset the hardware. Just a suggestion

what wireless / BT does it have? Getting a bit confuse now, are you on Mojave or Catalina? Maybe a courtesy to add all you specs into the signature file, so I don't have to go back and forth to read entire thread for information

that's fine, just mean no 3rd party kexts found in /L/E Did you update Lilu and reboot?

you could try download latest version from here https://dortania.github.io/builds/?viewall=true

try taking a video because the error is usually just above this message

1) boot with verbose + debug 0x100 mode, post screenshot 2) google or use kext updater.app to download, many ways to do this, please put in a little effort 3) Make sure to repair permission and rebuild cache after 4) DSDT has nothing to do with what version of MacOS, but with BIOS version and configuration. The old kext I meant is for wifi (IO80211Family.kext) Did you read Hervé's guide? Here's the link if you have not. Make sure to read the last post.

Yes, I believe they both do the same thing. Clicking a button is definitely easier than typing a bunch of commands but you won't know if it encounter error or not. With the commands you at least get an idea from the output. Up to you how you want to deal with it.

Anytime you make any changes to /L/E or /S/L/E, you should run those commands before rebooting, not after.

No need to install to /L/E, all can be injected from /EFI, undo that. You should also update your kexts especially Lilu Whatevergreen You didn't post what the issue is with booting...so can't tell you why it won't boot normally. As for wifi, Atheros has been dropped from Catalina, you'll need to install old kexts from Mojave or inject some patched kexts. See Hervé's guide on Wifi devices

Ahhh, did you google? https://github.com/acidanthera/BrcmPatchRAM/releases make sure to delete the 2 brcm* from /l/e

Yes, if you don't have them in /EFI/Clover/kexts/Other. They are for Broadcom Bluetooth. Add these instead if you need them for Broadcom BT. BrcmBluetoothInjector BrcmFirmwareData BrcmPatchRAM3

Try layout-id 13 and 15 for audio, you currently have 3 set.

You said you didn't install any kexts to /L/E The above output tells me otherwise. Did you update these kexts are well? BrcmPatchRAM2 BrcmFirmwareRepo.kext BrcmNonPatchRAM2 Better to just delete them and run the commands again. You should keep these in EFI. You don't even need BrcmNonPatchRAM2.

As I said earlier, why do you have vanilla kexts from /L/E in your /EFI/Clover/kexts/Other and 10.15? Makes no sense, delete these from both directories in the EFI

post the output of the commands

run in terminal and post the output sudo kextcache -i /

Did you update the kext in /L/E as well when you update the kexts in EFI?

I'm not sure what you did while upgrading the kexts. Normally updating kexts will not cause boot issue. As far as I know, kext updater will download the latest kexts to the desktop and you'll replace them to the EFI or /L/E if you have them there.

replace DSDT DSDT.aml.zip Looks like you moved all the kexts found in /L/E to EFi/Clover/Kexts/10.15. Don't do that, remove them from EFI. Those are vanilla kexts native to the OS. Keep all kexts in Other, no need to split. You now have 2 different versions of kext in 10.15 and Other...messy. Clean that up. Either use FakeSMC +ACPIBatteryManager or VirtualSMC + SMCBatterymanager.kext.