[GUIDE] Installing 3rd Party Kexts - El Capitan, Sierra, High Sierra, Mojave, Catalina

[jaymonkey]

1. You're stating that if Clover detects FakeSMC in /L/E it will not load anything from /Other. Prerequisite is the "Detect" flag. Does this definitely apply to VirtualSMC as well?

Yes as long as Lilu + VirtualSMC is installed in /L/E and "Inject Kexts" is set to "Detect" then Clover will not inject Kexts, I use this myself on all my Hacks.

2. I copy the kexts with the finder to /L/E and then run the Hackingtool to repair the permissions and rebuild the cache is that sufficient? Or do I have to "Install" them with the Hackingtool. Does Hackingtool maybe set any other parameters in the system?

Do not use Finder to copt the kexts, use Hackintool's Install kexts feature, or use the Terminal method as detailed in the guide.

3. How can I verify which kexts were loaded from L/E and which ones from /Other?

Examine the output of the kextcache command (the last block of red text in hackingtool), or simply execute the command at anytime in terminal :-

sudo kextcache -i /

Each line will show the path from which the kext was loaded by the kernel.

Cheers
Jay

 

[Ennio1985]

Hello Community. I have question, I have a debate of using the kexts int /L/E and set in config.plist detect instead of inject and put them in /EFI/Clover/kexts/other.

in this guide says that the kexts will be inside the kernel, so the SO will run more flawless and smooth; but in many treads I read that I have to set SIP completely disable because if I did not do that at any time being if the cache has to be rebuild it could crash with sip enable.

and in other guides (USB, Power management, iMessages) suggest to use the kexts to be injected so that way you could full enable SIP, (in the iMessages guide request to sip be disabled) and you will have less problems to update in the future etc etc.

So I tried the 2 options. I don't see any performance difference within any of them; so I ask sip has to be disabled to iMessage to work? I intend to stay in Mojave for a while because the 2 vpn apps for my work that I use are 32 bits so I could not use them in catalina, but if I decide to update to catalina is better to inject the kext ? I tried to many times and the USB ports only works with kexts being detected.

some say in those guides that apple will change things and is better to assume that can no longer use kexts in /L/E

so I see the community divided in two.

what do you think?

 

[michaelbp]

2. Where should I install 3rd Party Kexts ?

You should install all 3rd Party kexts (including FakeSMC) to /Library/Extensions (/L/E)
Warning: you can not simply use Finder to copy kexts into /L/E (see Section 7 below)

Jay,
your guide says to install kexts into /L/E...
I have LOTS of kext files in my System/Library/Extensions folder.
like over 300.
- can they cause problems?
- should I delete them - OR- copy them to /L/E?

 

[Feartech]

Jay,
your guide says to install kexts into /L/E...
I have LOTS of kext files in my System/Library/Extensions folder.
like over 300.
- can they cause problems?
- should I delete them - OR- copy them to /L/E?

System/Library/Extensions is where apple keeps its system kexts, best leave them there

 

[jaymonkey]

your guide says to install kexts into /L/E...I have LOTS of kext files in my System/Library/Extensions folder.

@michaelbp,

There are basically two types of kexts.

System Kexts - Are the kexts and drivers written by Apple and are installed in /S/L/E during macOS Install.
3rd Party kexts - Are non Apple supplied kexts and drivers that are installed in /L/E as per the Guide

You should not touch the kexts in /S/L/E or install 3rd party kexts in /S/L/E.

Cheers
Jay

 

[elfcake]

@jaymonkey I found FakeSMC.kext and related kexts in S/L/E. I understand that they should not be there. I attempted to delete them from S/L/E but was unable to do so. Is there a way to delete them? Additionally, I thought that with VirtualSMC.kext the FakeSMC.kext was not needed. VirtualSMC and related kexts are in kexts/other.

 

[jaymonkey]

I found FakeSMC.kext and related kexts in S/L/E. I understand that they should not be there. I attempted to delete them from S/L/E but was unable to do so. Is there a way to delete them?

@elfcake,

I assume your running MacOS Catalina ?, if so then to delete the FakeSMC kexts in /S/L/E you need to do the following:-

• Run Hackintool
• Click on the Tools icon (step 1 below)
• Click on the icon to mount the System drive as Read/Write, enter password when prompted (step 2 below)
• You should now be able to delete the FakeSMC kexts in /S/L/E using finder (step 3 below)
• Go back to Hackintool
• Click on the icon to rebuild kernel kext cache (step 4 below)
• Reboot

Additionally, I thought that with VirtualSMC.kext the FakeSMC.kext was not needed.

Correct, you should not have FakeSMC or any of the FakeSMC sensor kexts installed if using VirtualSMC.

Cheers
Jay

 

[elfcake]

@elfcake,

I assume your running MacOS Catalina ?, if so then to delete the FakeSMC kexts in /S/L/E you need to do the following:-

• Run Hackintool
• Click on the Tools icon (step 1 below)
• Click on the icon to mount the System drive as Read/Write, enter password when prompted (step 2 below)
• You should now be able to delete the FakeSMC kexts in /S/L/E using finder (step 3 below)
• Go back to Hackintool
• Click on the icon to rebuild kernel kext cache (step 4 below)
• Reboot

View attachment 446164



Correct, you should not have FakeSMC or any of the FakeSMC sensor kexts installed if using VirtualSMC.

Cheers
Jay

Jay, Thank you! That Hackintool is really amazing.

 

[LUCKYLUKEY456]

Thank you for the guide. I will do what you say in the guide

 

[Kanclerz]

Hello,
It does not work ?