- Joined
- Feb 13, 2011
- Messages
- 416
- Motherboard
- Asus Vivobook S15 / x510UAR
- CPU
- i5-8250U
- Graphics
- UHD 620
- Mobile Phone
Wow, time to learn is - always. I always thought if "Inject kexts" is set to "detect", Clover would then inject any kext not present in /L/E, or any newer version kext. Great to know this depends of FakeSMC as indicator! I just tested this myself and can confirm.@bugsb I place BrcmFirmware kexts to Clover in case of booting into Recovery (which is on a different volume)
When you boot macOS with "InjectKexts" set to "Detect", Clover will find FakeSMC in kextcache. If it found, it will not inject kexts in Clover/kexts/Other.
So you don't have to worry about kexts conflict if FakeSMC is installed to /L/E.
My fav kext installer is KCPM Utility Pro. It automatically sets working permissions and rebuilds kext and kernel caches (in contrast to KextBeast...). Cvad's Kext Utility always installs kexts to /S/L/E with no way to alter that, which I think sucks.
gotchaBtw, you don't need VerifyMsrE2, CleanNvram and TOOLS_DEF.X64
Will do asap.@bugsb You may want to try the build I have uploaded several hours ago. It uses hot-patch!
Remember to compile dsl to aml.
Thanks for all the valuable guidance and education!