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.
Clover r4644 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
Tested with unlocked Workstation 14 running OSX 10.9 -->10.14 guest in Windows X64 host.
1. Download and unzip "EFI_Clover_r4644 for VMware.zip". Mount Clover-v2.4k-4644-X64 by double clicking on it.
2. Mount your VM's EFI System Partition eg in terminal
sudo diskutil mount disk0s1 3. Copy EFI folder from step 1 into the EFI partition
4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host
Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM.
The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
@colt2 HOW TO: Create a bootable El Capitan ISO for VMware
@dsmccombs comment on faking Ivybridge Processor
@Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
VirtualBox Forum: Status of OSX on OSX
Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X) 4GB or more RAM (2GB or more will be needed for OS X) Hard Disk with at least 40GB free for Virtual Machine Oracle VM VirtualBox v 5.0.34 Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75 16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC
Prepare Installation ISO on your Mac or Hack
1. On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
2. Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes. Note: you will need approx 16GB of free space on your hard disk for the script to complete.
3. Open OS X terminal, then run the following commands to execute the script:
cd downloads chmod +x CECI.tool ./CECI.tool 4. At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
Create an El Capitan Virtual Machine in VirtualBox
1. Open the VirtualBox program and click the "New" button to create a new VM.
2. Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version. I named my Virtual Machine "El_Capitan", then clicked next...
3. Leave the Memory size at the recommended 2048 MB, then click next.
4. Choose to "Create a virtual hard disk now", then click the create button.
5. For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare. Click next...
6. For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).
7. On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger. When you click the create button, you will now see your new VM in the VirtualBox main GUI.
8. Click the settings button on the Main Menu to tweak a few settings....
a. On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)
b. On the System/Processor tab, you can increase the allocated CPU cores to 2
c. On the Display tab, you can increase the allocated Video Memory to 128MB
d. On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File".
Navigate and select the El Capitan ISO we created earlier...
e. Click the OK button to finalise the VM settings.
Patch El Capitan vbox configuration file with DMI Settings from a Mac
1. From the start menu, type cmd and click run as administrator to open an administrative command prompt.
2. Choose a Mac Model similar to your host system, then type the following lines, followed by <enter> after each line. Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3. Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors. You can try from one of the following if this happens:
To spoof Lynnfield i5 750 CPU
VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4. Close the command prompt window.
Installation of El Capitan
We are now ready to start the El_Capitan Virtual Machine....
Installation should be relatively straight forward, just following the prompts of the OS X installer:
1. Select language, agree to legal terms
2. Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended. I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan.
3. Quit DU and choose Macintosh HD to install El Capitan on.
4. After 20-30 min (depending on how fast your system is), the installation will complete. At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive. The VM is now ready to reboot into OS X from the virtual hard drive.
5. At the welcome screen, choose your country and keyboard layout. You can skip transfer information, location services and logging in with your Apple ID if you wish…
6. Create a User Account and select your Time Zone. You can skip sending diagnostics and usage data to Apple….
7. Finally, you will arrive at the El Capitan Desktop.
8. Network/internet and audio should work OOB but on my system, the sounds were distorted. Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm).
Customization with VBoxManage
1. You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
Update: For VirtualBox 5.2.x, the command for changing screen resolution has changed...
VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2. Adding serials and other SMBIOS details for the System Information Screen
VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite . Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
To create a Mavericks ISO on your desktop
cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above). Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .
UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
UPDATE macOS High Sierra 17A365: For macOS High Sierra, use CHSI.tool in post#73.
UPDATE macOS Mojave Beta: For macOS Mojave Beta, use CMJI.tool on page 4 of thread.
Good luck and enjoy
you can use this thread to link / talk about of the future Nvidia Web Driver updates for El Capitan
Nvidia Web Driver - 346.03.15f16 --> build 15G22010 (thanks to BreBo) New!
Nvidia Web Driver - 346.03.15f15 --> build 15G21013 (thanks to BreBo)
Nvidia Web Driver - 346.03.15f14 --> build 15G20015 (thanks to DMCrimson)
Nvidia Web Driver - 346.03.15f13 --> build 15G20015 (thanks to Louvier)
Nvidia Web Driver - 346.03.15f12 --> build 15G19009 (thanks to WeBeRiO)
Nvidia Web Driver - 346.03.15f11 --> build 15G18013 (thanks to BreBo)
Nvidia Web Driver - 346.03.15f10 --> build 15G17023 (thanks to Badruzeus)
Nvidia Web Driver - 346.03.15f09 --> build 15G1611 (thanks to Badruzeus)
Nvidia Web Driver - 346.03.15f08 --> build 15G1510 (thanks to Badruzeus)
Nvidia Web Driver - 346.03.15f07 --> build 15G1421 (thanks to bb1045)
Nvidia Web Driver - 346.03.15f06 --> build 15G1217 (thanks to bb1045)
Nvidia Web Driver - 346.03.15f05 --> build 15G1212 (thanks to WeBeRiO)
Nvidia Web Driver - 346.03.15f04 --> build 15G1108 (see this post)
Nvidia Web Driver - 346.03.15f03 --> build 15G1004 (thanks to BreBo)
Nvidia Web Driver - 346.03.15f02 --> build 15G31 (thanks to Moviemakergr)
Nvidia Web Driver - 346.03.15f01 --> build 15G31 (thanks to WeBeRiO)
[uPDATE_3]Nvidia Web Driver - 346.03.15b01 --> build 15G24b (thanks to DMCrimson)
Nvidia Web Driver - 346.03.10f02 --> build 15F34 (thanks to marcozardi)
Nvidia Web Driver - 346.03.10f01 --> build 15F34 (thanks to WeBeRiO)
[uPDATE_2] Nvidia Web Driver - 346.03.10b01 --> build 15F31a (see this post)
Nvidia Web Driver - 346.03.06f01 --> build 15E65 (see this post)
Nvidia Web Driver - 346.03.06b01 --> build 15E (see this post)
Nvidia Web Driver - 346.03.05f02 --> second release for build 15D21 (thanks to Fljagd)
Nvidia Web Driver - 346.03.05f01 --> build 15D21 (see this post)
Nvidia Web Driver - 346.03.05b02 --> build 15D (see this post)
Nvidia Web Driver - 346.03.04f02 --> second public release (see this post)
Nvidia Web Driver - 346.03.04f01 --> build 15C50 (see this post)
Nvidia Web Driver - 346.03.04b02 --> build 15C48a (see this post)
Nvidia Web Driver - 346.03.04b01 --> build 15C47a (see this post)
Nvidia Web Driver - 346.03.03f02 --> second public release (see this post)
Nvidia Web Driver - 346.03.03f01 --> build 15B42 (thanks to jperkins909)
Nvidia Web Driver - 346.03.02f02 --> build 15A284 (thanks to MTWomg)
Nvidia Web Driver - 346.03.02f01 --> build 15A284 (see this post)
Nvidia Web Driver - 346.03.01b07 --> GM/DB/PB6/DB7/PB5 (thanks to BreBo)
Nvidia Web Driver - 346.03.01b06 --> build 15A (thanks to MTWomg)
Hello everybody, it’s been a long long time since my last post here on this forum, I’m having a lot of issues trying to activate my graphic card, the system recognizes the graphic card but there’s not full acceleration, clearly shows up its name as Intel graphics HD 3000 with only 4 MB of video ram.
I would like to know how I could fix this problem or a least any suggestion about it. The reason I came to this site one more time is because I have no clue how to edit or patch a DSDt.aml file, I have clover bootloader and still (seems to be easy but not for me LOL) so I don’t want to ruin the system once again.
My configuration is
OS macOS High Sierra 10.13
SAMSUNG series 3 NP300E5C-A0US
INTEL CORE i3 - 2370M 2.4 GHz
INTEL GRAPHICS HD 3000
WiFi ATHEROS AR5B95
MEMORY 6 GB DDR3
Wifi works *** Sound Works ***Ethernet Works***
Battery indicators and trackpad gestures are not working yet.
Thank you guys in advance, I’ll keep myself reading and searching for any kind of solution for my laptop..