Recently Browsing 0 members
No registered users viewing this page.
I created an installer for my version of FakeSMC with plugins and applications latest revision.
Compatibility from 10.6 up to 10.15.
Download here: HWSensors.pkg.zip
See my signature
New project home
FakeSMC v3.5.3 and plugins
FakeSMC 3.4.0 revision 751
New project home is
where you can download most recent versions.
Now it is FakeSMC 3.4.1
Explanations about the difference between versions 3 and 6
Revision 32 with explanation at #220
FakeSMC is 3.5.0 compatible with High Sierra.
New plugin VoodooBatterySMC created on the base of VoodooBattery by Superhai but with SMC keys generating to show Battery voltage and amperage. As well it created key BATP needed for right speedstep and FileVault2.
Other kexts revised.
How to create a macOS Installer which doesn't need bootloader kext injection (FakeSMC in pre-linked kernel), bypass High Sierra firmware and MBR checkBy fusion71au
This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.
It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.
Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”
1. Boot into Yosemite with the kext-dev-mode=1 boot flag
2. Open OS X terminal and type the following lines, followed by <Enter> after each line.
The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3. Right click on the “OS X Base System” Volume and click “Get Info”
4. Click on the lock icon and untick “Ignore ownership on this volume”
5. Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist. NB It is found in the "Essentials.pkg" in /System/Installation/Packages
6. Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
7. Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
8. Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.
9. Install your Bootloader targeting the OS X Base System volume
10. Boot your system with the USB without injected kexts into the OS X Installer GUI....
The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts. In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
1. Boot into Yosemite with the kext-dev-mode=1 boot flag
2. Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
3. Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
4. Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel. In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume. This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
6. Reboot your system without injected kexts into El Capitan!
The All-In-One Guide to Vanilla OS X for beginners
Updates for Sierra and High Sierra Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan. Instructions: 1. Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder. 2. Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3. Copy BaseSystem.dmg to ~/Downloads/BaseSystem 4. Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop. macOS High Sierra bypass Firmware and MBR checks in post#13.
BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
Dell laptops and desktop can be monitored by SMM methods as mentioned is the old topic
I made a plugin SMIMonitor for FakeSMC in 2014 but it was 32bits and was not working. Only now I made it to be 64bits (as darkvoid did with kozleks branch) and got positive results
and after heating
So I have monitoring of 4 additional temperature sensors (CPU Proximity, GPU, DIMM, and Motherboard) and a CPU fan which initially stay at 0 rpm and start rotating after heating with 2882rpm.
Moreover I implemented a function for brave people to control fans
sudo SMC_util3 -kF0As -w2 The last digit 2 is a FAN speed you want to set
0 = Off
1 = Low
2 = High
If you have more then 1 fan then you can manage other one by choosing next key F1As, F2As etc.
Precaution! Writing the fan speed is dangerous and may cause a computer damage. Do this at your own risk!
Note. SMIMonitor.kext will work only with FakeSMC v3 provided with HWSensors3 in my signature.
Official release at sf.net contains SMIMonitor without write possibility.
Please test and report your successes and fails.
This should be an interesting challenge for you guys.
I have a 2010 - ish Mac Pro 5,1. Its running either Snow Leopard for legacy compatibility or Mojave when I'm in a flashy mood.
I have a single processor tray which works fine for practical purposes but I also have a dual processor tray which is where the challenge arises. In order to get the dual processor tray to work, I have to put it in the freezer for half an hour before fitting it to
the machine. If I do this it boots fine and runs for a good five minutes before the second processor (B) warms up, I get a red light on the tray and the machine shuts down.
If I try and start it without putting the tray in the freezer it fails to boot and the red light comes on. All the usual suspects have been tried, replacing thermal paste on heatsinks, replacing spring rivets on Southbridge chip heatsink etc etc. When the B processor is removed, the machine boots fine and the fans are noisy but can be slowed with software.
After much investigation it seems there is a fault/misalignment in the temperature value/voltage being reported by the hardware to the SMC device, which is (mis)detecting an overtemp and shutting the system down when it needn't.
The question for you guys is this. The SMC firmware is updated regularly and is accessible with software debugging tools (MacProSMCUpdate11.dmg). Can some clever person more up to speed (than me) with Mac firmware and software generally, point me in the right direction as to how I can:
a) locate the B processor temperature detection logic.
b) modify it so it either ignores the erroneous overtemp data or re-interprets it to give a correct (ish) value which does not cause a red light and a shut down.
c) install the tweaked software so as to avoid/evade the shut down issue?
That should keep you guys out of trouble for a few minutes at least, and stop you hanging round street corners and chewing gum.