crusher Posted August 6, 2015 Share Posted August 6, 2015 Boot into single mode. mount -uw / kextutil -v /FakeSMC.kext exit Where the put FakeSMC? Link to comment Share on other sites More sharing options...
arsradu Posted August 6, 2015 Share Posted August 6, 2015 Where the put FakeSMC? Wherever you want. It doesn't matter. Somewhere easier to grab. For example, make a "kexts" folder on the root of your USB Installer, put your custom kexts there, and when you run that command from single user mode, give it the location to the kext in your kexts folder from on the USB. For example: If your FakeSMC.kext is in /Volumes/ElCapitanUSB/kexts/FakeSMC.kext, then the command should be: kextutil -v /Volumes/ElCapitanUSB/kexts/FakeSMC.kext Where "ElCapitanUSB" is the name of your USB installer. The rest of the commands remain the same. I hope I got it right. Link to comment Share on other sites More sharing options...
crusher Posted August 6, 2015 Share Posted August 6, 2015 But before need use or not sbin/fsck -fy sbin/mount -uw / kextutil -v /Vloumes/USBNAME/folder name/FakeSMC.kext you think like this? Link to comment Share on other sites More sharing options...
arsradu Posted August 6, 2015 Share Posted August 6, 2015 But before need use or not sbin/fsck -fy sbin/mount -uw / kextutil -v /Vloumes/USBNAME/folder name/FakeSMC.kext you think like this? Yes. 1 Link to comment Share on other sites More sharing options...
WaldMeister Posted August 6, 2015 Share Posted August 6, 2015 But before need use or not sbin/fsck -fy sbin/mount -uw / kextutil -v /Vloumes/USBNAME/folder name/FakeSMC.kext you think like this?Mount -uw /Kextutil.... Will do. 1 Link to comment Share on other sites More sharing options...
Slice Posted August 6, 2015 Share Posted August 6, 2015 Example to mount EFI partition mkdir /Volumes/EFI mount -t msdos /dev/disk0s1 /Volumes/EFI For mount HFS+ volume the command mount_hfs 1 Link to comment Share on other sites More sharing options...
crusher Posted August 6, 2015 Share Posted August 6, 2015 Latter need copy to S/L/E or L/E or not? Link to comment Share on other sites More sharing options...
mendietinha Posted August 6, 2015 Share Posted August 6, 2015 sure, Link to comment Share on other sites More sharing options...
arsradu Posted August 6, 2015 Share Posted August 6, 2015 Latter need copy to S/L/E or L/E or not? Copy and set permissions. Otherwise those kexts will not be loaded. 1 Link to comment Share on other sites More sharing options...
mhaeuser Posted August 6, 2015 Share Posted August 6, 2015 LowMemFix was for Insyde firmwares as it doesn't have critical EFI Services data in the kernel address space, so LowMemFix just wiped the general data so the kernel can load... 2 Link to comment Share on other sites More sharing options...
rhcp011235 Posted August 6, 2015 Share Posted August 6, 2015 I can confirm using the following in your clover config: <key>RtVariables</key> <dict> <key>CsrActiveConfig</key> <string>0x67</string> <key>BooterConfig</key> <string>0x28</string> </dict> Will allow you to boot DP6. But, you need to move all your injected kexts from 10.11 to /L/E Link to comment Share on other sites More sharing options...
WaldMeister Posted August 6, 2015 Share Posted August 6, 2015 I can confirm using the following in your clover config: <key>RtVariables</key> <dict> <key>CsrActiveConfig</key> <string>0x67</string> <key>BooterConfig</key> <string>0x28</string> </dict> Will allow you to boot DP6. But, you need to move all your injected kexts from 10.11 to /L/E <key>BooterConfig</key> <string>0x28</string> Is not needed. And for CsrActiveConfig 0x01 will do. csr-active-config added by Clover: p70:~ Lex$ nvram -p efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>89405C34-F6F2-4528-B423-78AF12238763</string></dict></dict></dict></array> fmm-computer-name P70 security-mode none SystemAudioVolumeDB %df backlight-level %d8%0a SystemAudioVolume ) efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%04%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00p%f9o%11%00%00%00%004\@%89%f2%f6(E%b4#x%af%12#%87c%02%02%7f%ff%04%00 csr-active-config %01%00%00%00 Link to comment Share on other sites More sharing options...
Fabio1971 Posted August 6, 2015 Share Posted August 6, 2015 to use and kext in L/E or S/L/E <key>RtVariables</key> <dict> <key>CsrActiveConfig</key> <string>0x67</string> <key>BooterConfig</key> <string>0x28</string> </dict> Fabio 2 Link to comment Share on other sites More sharing options...
rhcp011235 Posted August 6, 2015 Share Posted August 6, 2015 <key>BooterConfig</key> <string>0x28</string> Is not needed. And for CsrActiveConfig 0x01 will do. csr-active-config added by Clover: p70:~ Lex$ nvram -p efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>89405C34-F6F2-4528-B423-78AF12238763</string></dict></dict></dict></array> fmm-computer-name P70 security-mode none SystemAudioVolumeDB %df backlight-level %d8%0a SystemAudioVolume ) efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%04%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00p%f9o%11%00%00%00%004\@%89%f2%f6(E%b4#x%af%12#%87c%02%02%7f%ff%04%00 csr-active-config %01%00%00%00 I do both because I want them to work in both /S/L/E and /L/E Link to comment Share on other sites More sharing options...
X-TRiAL Posted August 6, 2015 Share Posted August 6, 2015 My config.plist is not being read correctly even though there have been no changes to it and there is no errors. I just upgraded Clover to r3253 but still experiencing the same problem. Here is my config.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Fixes</key> <dict> <key>FixLAN_2000</key> <true/> <key>FixUSB_1000</key> <true/> </dict> <key>Name</key> <string>DSDT.aml</string> </dict> <key>SSDT</key> <dict> <key>Name</key> <string>SSDT.aml</string> <key>PLimitDict</key> <string>3</string> <key>UnderVolt</key> <string>4</string> </dict> <key>SmartUPS</key> <string>2</string> </dict> <key>Boot</key> <dict> <key>Arguments</key> <string>npci=0x2000 darkwake=0 slide=0 kext-dev-mode=1</string> <key>DefaultVolume</key> <string>Mac HD</string> <key>Timeout</key> <integer>0</integer> </dict> <key>GUI</key> <dict> <key>Custom</key> <dict> <key>Entries</key> <array> <dict> <key>FullTitle</key> <string>Boot Windows 7 from Windows HD</string> <key>Path</key> <string>\EFI\Microsoft\boot\bootmgfw-orig.efi</string> <key>Type</key> <string>Windows</string> </dict> <dict> <key>FullTitle</key> <string>Boot Kubuntu 13.04 from Linux HD</string> <key>Path</key> <string>\EFI\kubuntu\grubx64.efi</string> <key>Type</key> <string>Linux</string> </dict> <dict> <key>FullTitle</key> <string>Boot OS X Yosemite from Mac HD</string> <key>Type</key> <string>OSX</string> <key>Volume</key> <string>Mac HD</string> </dict> </array> </dict> <key>DebugLog</key> <false/> <key>Mouse</key> <dict> <key>Enabled</key> <false/> </dict> <key>Scan</key> <dict> <key>Legacy</key> <false/> </dict> <key>Theme</key> <string>black_green</string> </dict> <key>Graphics</key> <dict> <key>Inject</key> <dict> <key>Intel</key> <false/> <key>NVidia</key> <true/> </dict> <key>PatchVBios</key> <string>No</string> </dict> <key>KernelAndKextPatches</key> <dict> <key>AppleRTC</key> <false/> <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>TRIM Enabler</string> <key>Find</key> <data> AEFQUExFIFNTRAA= </data> <key>Name</key> <string>IOAHCIBlockStorage</string> <key>Replace</key> <data> AAAAAAAAAAAAAAA= </data> </dict> <dict> <key>Comment</key> <string>AppleHDA Stage1</string> <key>Find</key> <data> hAjsEA== </data> <key>Name</key> <string>AppleHDA</string> <key>Replace</key> <data> AAAAAA== </data> </dict> <dict> <key>Comment</key> <string>AppleHDA Stage2</string> <key>Find</key> <data> hQjsEA== </data> <key>Name</key> <string>AppleHDA</string> <key>Replace</key> <data> AAAAAA== </data> </dict> <dict> <key>Comment</key> <string>AppleHDA Stage3</string> <key>Find</key> <data> hBnUEQ== </data> <key>Name</key> <string>AppleHDA</string> <key>Replace</key> <data> aQLsEA== </data> </dict> <dict> <key>Comment</key> <string>HDMI Audio and Video stage1</string> <key>Find</key> <data> AgUAAAAEAAAHAAAA </data> <key>Name</key> <string>AppleIntelSNBGraphicsFB</string> <key>Replace</key> <data> AgUAAAAIAAAGAAAA </data> </dict> <dict> <key>Comment</key> <string>10.10-SNB-Port _0x6-DP2HDMI</string> <key>Find</key> <data> AwQAAAAEAAAJAAAA </data> <key>Name</key> <string>AppleIntelSNBGraphicsFB</string> <key>Replace</key> <data> AwQAAAAIAAAGAAAA </data> </dict> <dict> <key>Comment</key> <string>Bootloader Graphics - Resolve boot garble</string> <key>Find</key> <data> QYjE6xE= </data> <key>Name</key> <string>IOGraphicsFamily</string> <key>Replace</key> <data> QYjE6zE= </data> </dict> </array> </dict> <key>RtVariables</key> <dict> <key>MLB</key> <string>number</string> <key>ROM</key> <string>stuff</string> </dict> <key>SMBIOS</key> <dict> <key>BiosReleaseDate</key> <string>08/03/10</string> <key>BiosVendor</key> <string>Apple Inc.</string> <key>BiosVersion</key> <string>MBP82.88Z.0047.B27.1201241646</string> <key>BoardManufacturer</key> <string>Apple Inc.</string> <key>BoardSerialNumber</key> <string>number</string> <key>BoardVersion</key> <string>MacBookPro8,2</string> <key>ChassisAssetTag</key> <string>P6TDeluxeV1</string> <key>ChassisManufacturer</key> <string>Apple Inc.</string> <key>Family</key> <string>MacBook Pro</string> <key>LocationInChassis</key> <string>Part Component</string> <key>Manufacturer</key> <string>Apple Inc.</string> <key>Mobile</key> <true/> <key>ProductName</key> <string>MacBookPro8,2</string> <key>SerialNumber</key> <string>number</string> <key>SmUUID</key> <string>serial</string> </dict> <key>SystemParameters</key> <dict> <key>InjectSystemID</key> <true/> <key>prev-lang:kbd</key> <string>en:0</string> </dict> </dict> </plist> Link to comment Share on other sites More sharing options...
AkimoA Posted August 6, 2015 Share Posted August 6, 2015 <key>RtVariables</key> <dict> <key>MLB</key> <string>number</string> <key>ROM</key> <string>stuff</string> <key>CsrActiveConfig</key> <string>0x67</string> <key>BooterConfig</key> <string>0x28</string> </dict> That should do it , just edit it with Text Wrangler or Atom for example. Link to comment Share on other sites More sharing options...
X-TRiAL Posted August 6, 2015 Share Posted August 6, 2015 <key>RtVariables</key> <dict> <key>MLB</key> <string>number</string> <key>ROM</key> <string>stuff</string> <key>CsrActiveConfig</key> <string>0x67</string> <key>BooterConfig</key> <string>0x28</string> </dict> That should do it , just edit it with Text Wrangler or Atom for example. Added it in but nothing changed, it is still not reading my config.plist correctly. Link to comment Share on other sites More sharing options...
Slice Posted August 6, 2015 Share Posted August 6, 2015 Copy and set permissions. Otherwise those kexts will not be loaded. Copy by terminal command sudo cp -R -v some.kext /S/L/E automatically set best permissions 1 Link to comment Share on other sites More sharing options...
rhcp011235 Posted August 6, 2015 Share Posted August 6, 2015 Copy by terminal command sudo cp -R -v some.kext /S/L/E automatically set best permissions Hey Slice, Any idea how you will be going on about injecting KEXT's into the new 10.11 now that apple is blocking it from the kernel. Piker had an idea about patching the kernel on the fly to allow it. https://pikeralpha.wordpress.com/2015/07/28/apples-kext-signing-bypassed/ Link to comment Share on other sites More sharing options...
GhostRaider Posted August 6, 2015 Share Posted August 6, 2015 So if I understood correctly: 0x67 = Kexts in Clover/kext/10.11 and in /L/E and S/L/E right? If I needed to replace an Apple kext, like AppleHDA it would be in S/L/E and any other kext that doesn't need dependencies go to /L/E right? Link to comment Share on other sites More sharing options...
chris1111 Posted August 6, 2015 Share Posted August 6, 2015 So if I understood correctly: 0x67 = Kexts in Clover/kext/10.11 and in /L/E and S/L/E right? If I needed to replace an Apple kext, like AppleHDA it would be in S/L/E and any other kext that doesn't need dependencies go to /L/E right? I have replace AppleHDA on SLE 1 Link to comment Share on other sites More sharing options...
WaldMeister Posted August 6, 2015 Share Posted August 6, 2015 So if I understood correctly: 0x67 = Kexts in Clover/kext/10.11 and in /L/E and S/L/E right? If I needed to replace an Apple kext, like AppleHDA it would be in S/L/E and any other kext that doesn't need dependencies go to /L/E right? 0×67 disables SIP completely. Read the last 5 pages or so, of this topic. A lot of information about this can be found in it. Link to comment Share on other sites More sharing options...
GhostRaider Posted August 7, 2015 Share Posted August 7, 2015 0×67 disables SIP completely. Read the last 5 pages or so, of this topic. A lot of information about this can be found in it. Okay got it now. Too bad Clover kexts don't work anymore which is a hassle since you have to transfer the kexts to /L/E or S/L/E manually and repair permissions using single user mode or boot from another os x partition (assuming that an OS X El Capitan installer doesn't install a kext like FakeSMC automatically for you). Link to comment Share on other sites More sharing options...
calibre™ Posted August 7, 2015 Share Posted August 7, 2015 0x3 enables: CSR_ALLOW_UNTRUSTED_KEXTS CSR_ALLOW_UNRESTRICTED_FS 0x67 enables: CSR_ALLOW_UNTRUSTED_KEXTS CSR_ALLOW_UNRESTRICTED_FS CSR_ALLOW_TASK_FOR_PID CSR_ALLOW_UNRESTRICTED_DTRACE CSR_ALLOW_UNRESTRICTED_NVRAM Does this mean we can't write NVRAM for flag on 0x3? Link to comment Share on other sites More sharing options...
rhcp011235 Posted August 7, 2015 Share Posted August 7, 2015 0x3 enables: CSR_ALLOW_UNTRUSTED_KEXTS CSR_ALLOW_UNRESTRICTED_FS 0x67 enables: CSR_ALLOW_UNTRUSTED_KEXTS CSR_ALLOW_UNRESTRICTED_FS CSR_ALLOW_TASK_FOR_PID CSR_ALLOW_UNRESTRICTED_DTRACE CSR_ALLOW_UNRESTRICTED_NVRAM Does this mean we can't write NVRAM for flag on 0x3? You would need to grep the source because it says "CSR_ALLOW_UNRESTRICTED_NVRAM" meaning you can write anything with 0x67, you can prob write SOMETHING in nvram but NOT anything with 0x3 Link to comment Share on other sites More sharing options...
Recommended Posts