Jump to content
ErmaC

Clover General discussion

19,118 posts in this topic

Recommended Posts

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

Share this post


Link to post
Share on other sites
Advertisement

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/

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

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 

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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).

Share this post


Link to post
Share on other sites
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?

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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?

 

 

Only the csr-config args is restricted, your regular nvram variables are still applied 

Share this post


Link to post
Share on other sites

Only the csr-config args is restricted, your regular nvram variables are still applied 

Adding an example: 

Last login: Fri Aug  7 13:28:18 on console
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	%ee
backlight-level	%d8%0a
SystemAudioVolume	8
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
p70:~ Lex$ sudo nvram -c
Password:
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>
csr-active-config	%01%00%00%00
p70:~ Lex$ 

Just noticed, with 0x01 the efi-boot-device will stay also.

Share this post


Link to post
Share on other sites

Hi,

 

I used the installer for rev 3253 posted here, did not notice untill just now that i have a new dir. Can i remove it? And how did it even get there? 

 

attachicon.gifSchermafbeelding 2015-08-08 om 11.25.28.png

 

I fail to see why you would bother removing for an under 100k of usage on a partition that is never used for anything but booting. That said it appears to be the file system efi driver for 64bit booting you are concerned about. As to getting there I would go with you selecting the option for it in the installer or it being a dependancy of another selection made.

Share this post


Link to post
Share on other sites

I fail to see why you would bother removing for an under 100k of usage on a partition that is never used for anything but booting. That said it appears to be the file system efi driver for 64bit booting you are concerned about. As to getting there I would go with you selecting the option for it in the installer or it being a dependancy of another selection made.

These are not the droids you are looking for.

Share this post


Link to post
Share on other sites

I fail to see why you would bother removing for an under 100k of usage on a partition that is never used for anything but booting. That said it appears to be the file system efi driver for 64bit booting you are concerned about. As to getting there I would go with you selecting the option for it in the installer or it being a dependancy of another selection made.

Mainly because this folder/file is placed outside my EFI partition. It's just a folder with a file in my /Volumes directory. Just wondering how it got there, since it is not because of user interaction. 

Share this post


Link to post
Share on other sites

Sorry if this is a dumb question...

 

If I set 0x65 instead of 0x67 will any modified kexts in S\L\E be reverted back to their original state with extended permission etc?

Share this post


Link to post
Share on other sites

Mainly because this folder/file is placed outside my EFI partition. It's just a folder with a file in my /Volumes directory. Just wondering how it got there, since it is not because of user interaction. 

If you have failure Installer pkg maybe thats happen ?

maybe its a Beta OS X Bug ?

Clover Source Forge Package as never install EFI on  the root

if I am choose UEFI Only .

Share this post


Link to post
Share on other sites

If you have failure Installer pkg maybe thats happen ?

maybe its a Beta OS X Bug ?

Clover Source Forge Package as never install EFI on  the root

if I am choose UEFI Only .

 

Same here. I deleted the folder, will check on the next update if it occurs again. 

Share this post


Link to post
Share on other sites

Same here. I deleted the folder, will check on the next update if it occurs again. 

Did you check if you have no boot file on i386 Folder ?

 

UEFI Only = No boot file 

Share this post


Link to post
Share on other sites

Did you check if you have no boot file on i386 Folder ?

 

UEFI Only = No boot file 

I do have a boot.efi, but that is the default file from Apple i believe. Clover is on disk0s1, so in the EFI partition. 

post-1090626-0-97082500-1439125925_thumb.png

Share this post


Link to post
Share on other sites

Same here. I deleted the folder, will check on the next update if it occurs again. 

I'm not sure that's a bug. I checked my Volumes and, sure enough, no such folder there. :)

 

Also, I found the name (firmwaresyncd aka firmware synced) to be a bit strange. So here's what I found on that. Check it out. I hope it makes things a little bit clearer. :)

Share this post


Link to post
Share on other sites

Running a hack makes everything different. Third party bootloader + unsigned kexts + god knows what else (user specific). You punched a hole in a wall and are trying to patch it back up with tape so it's 'just like new'. That isn't a winning strategy.

 

Truth.  But let's not forget the goals of OSx86 -- When Apple brings out a new feature, we work to get it functioning on non-Apple hardware.  For now, Apple is introducing SIP because it has dumbed-down the OS so much that most Mac users are clueless about security concerns.  We can all pat ourselves on the back for being smarter and more aware than most Mac users but that's not enough as far as I'm concerned.  If Apple is introducing SIP, I'd like to see it work on non-Apple hardware because that's what we do.

Share this post


Link to post
Share on other sites

I thought 0x00 means enable SIP and other security settings?

 

I reinstall to Developer Beta 1,keep 0x67 settings in clover.  Then install all beta updates to beta 6.

 

Now SIP is disabled. 

 

Too much efforts!

Upgrade Clover back.

Set

	<key>RtVariables</key>
	<dict>
		<key>CsrActiveConfig</key>
		<string>0x00</string>
	</dict>

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By AppleBytes
      OK, I've searching for days trying to gather up the tools to make my current install work correctly. I'm well on my way. But all the links to the things I currently must have were apparently nuked "during a forum upgrade". :(
      As far as EFI Studio goes; I can find many links to it. But for Insanelymac, they're broken (due to the upgrade), or for the Netkas site, they're links to either Rapidshare, or Mediafire that also no linger exist. I see many users here indicating that they used it to tweak their DSDT. But the web (google/duckduckgo), Instanelymac, and Netkas seem to have no idea where it's gone.
      Could some kind soul please share a copy, or a link? I'm a loooong time hacker, and would love to bring it back to life. In fact, I'd love to improve it -- or at least bring it up to current times. If only I knew where it was.
      Thank you for all your time, and consideration.
       
      --Chris
       
    • By SoThOr
      This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.
       
      Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge.  Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries. 
       
      Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable. 
       
      DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.
       
      1) Copy {bootmgr} entry.
      C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell" The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}. 2) Edit the new entry using the new GUID bcdedit generated in the copy step.
        a) Set the device and path for UEFI shell on my USB stick.
      bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G: bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi   b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
      3) Put the new EFI entry first in boot order. (optional)
       
      After completing the steps above, here is what "bcdedit /enum firmware" shows:
       
      I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
      Here is the resulting dump using "bcfg boot dump -v" from that shell:
       
      You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

      There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.
    • By cvad
      Small tool to download, compile and build the latest Clover X64 package.
       
       
       

      The script inside is editable.

       
      Enjoy...
       
      Many thanks to the comrade SunKi for help with creating the script.
       
       
       
       
       
      Best thanks - click "Rate File".
       
    • By blxkspell
      Hey!
      As I have 3 Monitors connected, my RX 570 gets arround 50°C while ideling/ web browsing etc. The problem is, that this temp is apparently just the threshold, when the fans start to spin. So the fans start spinning for a minute then they stop for a while again... This is very annoying for me as the rest of my hackintosh is nearly quiet (SSD, 120mm low RPM cpu fan, nearly silent PSU,...), especially when Im using the pc to revise for school. Does somebody know wether its possible to "change" the threshold till the fans start spinning? Like it would probably not be a problem for the gpu at all, if the temp rises to 55°C but therefore be soundless....
       
       
    • By kylon
      Cloud Clover Editor allows you to manage Clover EFI and Ozmosis configs everywhere!
       
       
      WEB
      Open Cloud Clover Editor
       
      APP (MacOS - Discontinued)
      Clover flying editor ( Micky1979 )
       
       
       
       
      Sources: https://bitbucket.org/kylon/cloud-clover-editor-cce/overview


      To run CCE at home you will need:
       
      An HTTP server (Apache, Nginx, ...) PHP 5.3.3+ (latest PHP version is always recommended for better performances/security) Sqlite3 PHP extension  
       
      Some Features:
       
      Edit text in tables:
      Editable fields are marked with a text cursor.
      Double click, or tap and hold, to open the inline editor.
      You can now press Enter or click outside to save your changes.
       
       
      Tri-state checkboxes:
      There are 3 possible states for a checkbox: Checked, indeterminate and unchecked.
       
      Checked: Value is true;
      Indeterminate: Value is false;
      Unchecked: Value is not set (ie, removed from plist)
       
      Working with multiple configs:
      The right sidebar is your multitasking menu.
      Use the add button to create a new config and add it to the list.
      You can safely switch between all your configs, no changes will be lost.
      You can mix Clover EFI and Ozmosis configs.


      Config Upgrade feature:
      In the case you are using old configuration options, CCE gives you the ability to automatically upgrade your config.
       
       
      Copy to:
      You can copy patches between your configs (you will love this when you need to copy kernel and kext patches ;D ).
      You will find a yellow copy icon if that field does support the copyTo feature.
       
       
      Ozmosis Mode:
      A new setting, Cloud Clover Editor Mode, is now added in Cloud Clover Editor -> CCE Settings.
      This will let you switch from Clover EFI to Ozmosis mode.
      Changes to your current file will be lost.
       
       
      CCE Bank 2.0:
      Thanks to @cecekpawon for the idea.
       
      CCE Bank is a database where you can save/load Clover EFI and Ozmosis configs.
      You can protect your config from unwanted modifications or make a publicly editable config.
       
      To save a config in CCE Bank you only need to check the "Save to CCE Bank" option.
       
      Tick the box generate a new CID, if you don t have one.
       
      A CID (CCE ID) acts like a container and it is your authentication key.
      You can group multiple configs under the same CID or generate as many CIDs as you like.
       
      Edit Modes:
      Public: Anyone can make modifications, only the owner can change its settings. Private: Only the owner can make modifications and change its settings. MyBank: Only the owner can see this config, make modifications or change its settings.  
      MyBank is your private area.
      Change the 'view mode' to switch between the public bank and your personal bank.
       
      To manage your currently loaded config, go to Cloud Clover Editor -> Open config -> click the settings button.
       
       
      Notes:
      Locked/Private configs are marked with a padlock MyBank configs are only visibile in your private area Only the owner of a locked config can save the modifications in CCE Bank, hower you are free to do whatever you want in CCE and download the modified config If you loose your CID you can just reply or pm me No account is required!  
       
      Main Features:
      Left sidebar does support touch swipe on touch devices.
      No changes will be lost on page reload.
       
       
      Credits
      mackie100 - took some ideas from his app Clover EFI dev team Eric Slivka - new serial number Virtual1 - new serial number cecekpawon - PHP 5.3.3 patch, , help with the ACPI Loader Mode flag and more Micky1979 - Clover flying editor crusher. - Help with the ACPI Loader Mode flag Download-Fritz - Help with the ACPI Loader Mode flag Pavo - Ozmosis fields and values stehor - Ozmosis fields and values Sherlocks - General help and support gujiangjiang - General help and support Please let me know if i forgot you!
×