Updating FakeSMC [A Guide]

[rabbit74]

MultiBeast 5.0.2 is designed to remove old FakeSMC components and replace them with the new ones. I have had mixed results in the past so I decided to compile some information regarding FakeSMC and its components. You can do a straight upgrade from multiBeast but if you run into troubles you can refer to this post.

Here is my guide.

..................................................................................

A list of FakeSMC parts components plugins

 

[rabbit74]

What I know so far:

Ref.01
With legacy FakeSMC from circa MultiBeast 4.3.x you will end up with the following if you install FakeSMC and motherboard plugins only:

/System/Library/Extensions/ACPIMonitor.kext 
/System/Library/Extensions/FakeSMC.kext 
/System/Library/Extensions/IntelCPUMonitor.kext 
/System/Library/Extensions/SuperIOFamily.kext

Ref.02
With FakeSMC from circa MultiBeast 4.6.x you will end up with the following if you install FakeSMC and motherboard plugins only:

/System/Library/Extensions/ACPISensors.kext 
/System/Library/Extensions/FakeSMC.kext 
/System/Library/Extensions/FintekF718x.kext 
/System/Library/Extensions/IntelCPUMonitor.kext 
/System/Library/Extensions/ITEIT87x.kext 
/System/Library/Extensions/NSCPC8739x.kext 
/System/Library/Extensions/NuvotonNCT677x.kext 
/System/Library/Extensions/OemSMBIOS.kext 
/System/Library/Extensions/WinbondW836x.kext

Ref.03
With FakeSMC from circa MultiBeast 5.2.x you will end up with the following if you install FakeSMC and motherboard plugins only:

/System/Library/Extensions/FakeSMC.kext 
/System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/ACPISensors.kext 
/System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/FintekF718x.kext 
/System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/IntelCPUMonitor.kext 
/System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/ITEIT87x.kext 
/System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/NSCPC8739x.kext 
/System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/NuvotonNCT677x.kext 
/System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/OemSMBIOS.kext 
/System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/WinbondW836x.kext

 

[rabbit74]

Because the component parts of each are different a simple upgrade install of Fakesmc and its plugins may result in parts of its predecessor being left behind which can cause system failure, KPs or boot failure.

So before upgrading we may want to remove the old fakesmc and all of its components.

Removing the old components​

Do A Complete System Backup Before Proceeding​

You can use finder or Terminal as follows:
Ref.01:

sudo rm -rf /System/Library/Extensions/ACPIMonitor.kext /System/Library/Extensions/FakeSMC.kext /System/Library/Extensions/IntelCPUMonitor.kext /System/Library/Extensions/SuperIOFamily.kext

Ref.02:

sudo rm -rf /System/Library/Extensions/ACPISensors.kext /System/Library/Extensions/FakeSMC.kext /System/Library/Extensions/FintekF718x.kext /System/Library/Extensions/IntelCPUMonitor.kext /System/Library/Extensions/ITEIT87x.kext /System/Library/Extensions/NSCPC8739x.kext /System/Library/Extensions/NuvotonNCT677x.kext /System/Library/Extensions/OemSMBIOS.kext /System/Library/Extensions/WinbondW836x.kext

Ref.03-A: (remove all of FakeSMC and plugins)

sudo rm -rf /System/Library/Extensions/FakeSMC.kext

Ref.03-B: (remove plugins only)

sudo rm -rf /System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/ACPISensors.kext /System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/FintekF718x.kext /System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/IntelCPUMonitor.kext /System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/ITEIT87x.kext /System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/NSCPC8739x.kext /System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/NuvotonNCT677x.kext /System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/OemSMBIOS.kext /System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/WinbondW836x.kext

And clear caches and Kernel caches: (will be rebuilt on next boot)

sudo rm -rf /System/Library/Caches/*

 

[rabbit74]

Other important stuff

Removing the graphics plugins only
Ref.01 and Ref.02
nvidia plugin

sudo rm -rf /System/Library/Extensions/NVClockX.kext

radeon plugin

sudo rm -rf /System/Library/Extensions/RadeonMonitor.kext

Ref.03
nvidia plugin

sudo rm -rf /System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/NVClockX.kext

radeon plugin

sudo rm -rf /System/Library/Extensions/FakeSMC.kext/Contents/PlugIns/RadeonX.kext

If you want to rollback to legacy FakeSMC, here it is with its original MoBo plugins:
View attachment Legacy FakeSMC and MoBo plugins.zip

......................................................................

If you need to do any of this in single user mode:​

reboot
add boot flag:
-s

to begin you must:

fsck -fy

then to be able to move, copy delete files you must:

mount -w

-w allows read/write

Use:

ls

to list current dir

mv = move
cp = copy
rm = remove(delete)
rm -rf will delete entire directories and or kext files. kext files are seen by the system as folders so rm -rf must be used to remove any kext files

here is an example if you wanted to remove and rollback FakeSMC
reboot

-s
fsck -fy
mount -w /
ls /System/Library/Extensions/ 
rm -rf /System/Library/Extensions/FakeSMC.kext
mv /Users/MyUserName/Desktop/FakeSMC.kext /System/Library/Extensions/
rm -rf /System/Library/Caches/*
chmod -R 755 /System/Library/Extensions/
chown -R root:wheel /System/Library/Extensions/
touch /System/Library/Extensions/
reboot

The above example won't work unless your rollback version of FakeSMC is on the desktop of your user account. You could move it from any other location as long as you know the path.​

OSX Mountain Lion Single User Mode Guide​

 

[mvn4wrd]

nice work, I never considered the impact of updating existing fakesmc kexts...learned something new!

 

[freituk]

thanks for the info

so you say that new MB 5.0.2 wont clean the old plugins when you install new fakesmc?
I bet this is not hard thing to implement on future releases.
New fakesmc search for plugins inside own kext, i think old (outside) fakesmc plugins, are not even use.
But i have no idea what i m talking about

 

[rabbit74]

MultiBeast 5.0.2 will remove the old FakeSMC and plugins. It is designed to remove them and replace. But I have had mixed results. Sometimes updating FakeSMC has caused system failure, so I decided to make this guide.

 

[HeavyArms]

I'm still on Lion, which I am fine with. Can I use the new MB for ML to install the latest fakesmc? I would assume all I'd have to do is check the fakesmc box and the plugins I wanted, and probably repair permissions.. right?

 

[rabbit74]

@Heavyarms
Answer, probably. I can't say for sure because I haven't tried that specific operation.

If it were me I'd stay on the safe side, make a new partition, clone my OS to the new partition, test MB5 on the partition, and see how it goes.

Alternatively you could use MB5 to install fakesmc as desired to an empty partition, like a usb drive or ramdisk,... then grab the kext from there and use kext utility to install it onto your main system. Using this method you would have to manually remove the old fakesmc components and clear caches, as described in above posts.. Again I would not try this on my main system. always test stuff like this on a cloned partition.

 

[zotune]

Greatest guide ever, thank you kind sir. Before this I got installed failed on all os x updates etc. Reverted to MB Lion FakeSMC. Can we expect a MB version that fixes this in the future?

I also found these Shell Commands very useful to find troublesome kexts:
sudo kextcache -system-caches
sudo kextcache -update-volume /

Your removal commands should hopefully be implemented in new versions of MultiBeast