Jump to content

Clover General discussion


ErmaC
29,866 posts in this topic

Recommended Posts

No idea right now. It might help to take a look at your Clover's config.plist (the one you're trying to use with your USB drive) if you want to upload it. :)

You might also try to add kext-dev-mode=1 as boot flag. See if that makes any difference.

 

If you can boot in Safe Mode, sounds like a kext problem to me.

Once you're booted up in Safe Mode, you could try fixing permissions using this command in Terminal:

diskutil repairPermissions /

And  also removing kext cache so that it can be recreated on the next reboot, using this command:

sudo rm -r -v /System/Library/Caches/com.apple.kext.caches/Startup/*

For the second one, you will also need to enter your password.

 

Hey arsradu, so I gave up on 10.10 and reinstalled 10.9.4 using a USB installer created using your method; the installation went flawlessly. The one obstacle I had after installation was getting my Intel HD4600 recognized with QE/CI. I tried dozens of things but the one thing that worked for me was using a Fake device ID of 0x04128086 for the HD4600. It didn't work initially, there were severe graphical aberrations that made it unusable although it was clear QE/CI was enabled. So I tried using your command to remove kext cache and repair permissions and everything worked! Thanks a lot friend.

 

Before I forget, I read in this thread that the reason the createinstallmedia USB installer didn't work for me because of the HFS driver I was using. I had Vboxhfs.efi loaded in clover and apparently if I upgraded to HFSPlus.efi it ought to work.

Link to comment
Share on other sites

Hey arsradu, so I gave up on 10.10 and reinstalled 10.9.4 using a USB installer created using your method; the installation went flawlessly. The one obstacle I had after installation was getting my Intel HD4600 recognized with QE/CI. I tried dozens of things but the one thing that worked for me was using a Fake device ID of 0x04128086 for the HD4600. It didn't work initially, there were severe graphical aberrations that made it unusable although it was clear QE/CI was enabled. So I tried using your command to remove kext cache and repair permissions and everything worked! Thanks a lot friend.

 

Before I forget, I read in this thread that the reason the createinstallmedia USB installer didn't work for me because of the HFS driver I was using. I had Vboxhfs.efi loaded in clover and apparently if I upgraded to HFSPlus.efi it ought to work.

Yeah, I had this same problem initially when installing mavericks. An installer made with createinstallmedia requires hfsplus.efi otherwise it just goes back to the clover screen immediately.
Link to comment
Share on other sites

I was asking what would be the returned result of the -nvram command for unlocked nvrams, since you posted an example for a locked one. :)

This is what a unlocked BIOS looks like:

Henrys-iMac:~ henrybrock$ nvram -p
OsxAptioFixDrv-RelocBase	%00%10*%c4%00%00%00%00
fmm-mobileme-token-FMM	bplist00%d8%01%02%03%04%05%06%07%08%09%0a%15%16%17%18%19%1aVuserid_%10%13dataclassPropertiesYauthTokenXpersonIDXusernameWaddTime_%10%12enabledDataclassesXuserInfo%11%01%f5%d1%0b%0c_%10!com.apple.Dataclass.DeviceLocator%d4%0d%0e%0f%10%11%12%13%14VapsEnvXhostname]authMechanismVschemeZProduction_%10%13p08-fmip.icloud.comUtokenUhttps_%10(AQAAAABT1UtHcBkNfFTDMR54b522Jz_VuzhuE4o~Y128870592_%10%14#A%d4%f5R%d2Bb%f2%a1%0b%d3%1b%1c%1d%1e%1f _%10%15InUseOwnerDisplayName_%10%13InUseOwnerFirstName_%10%12InUseOwnerLastName%00%08%00%19%00 %006%00@%00I%00R%00Z%00o%00x%00{%00~%00%a2%00%ab%00%b2%00%bb%00%c9%00%d0%00%db%00%f1%00%f7%00%fd%01(%012%01I%01R%01T%01[%01s%01%89%01%9e%01%aa%01%b0%00%00%00%00%00%00%02%01%00%00%00%00%00%00%00!%00%00%00%00%00%00%00%00%00%00%00%00%00%00%01%b6
Clover.LogLineCount	3000
security-mode	none
prev-lang:kbd	en:0
SystemAudioVolumeDB	%f0
Clover.LogEveryBoot	10
Clover.MountEFI	No
efi-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>B8B608B7-56E9-4A1C-B580-04E5A91D0085</string></dict></dict></dict></array>
fmm-computer-name	Henry%e2%80%99s iMac
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%00%00%ff%ff%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00@#%ce%0e%00%00%00%00%b7%08%b6%b8%e9V%1cJ%b5%80%04%e5%a9%1d%00%85%02%02%7f%ff%04%00
SystemAudioVolume	A
LocationServicesEnabled	%01
Henrys-iMac:~ henrybrock$ 
  • Like 1
Link to comment
Share on other sites

Hi, I was directed to this thread to ask this - apparently this could be a bug, although I think it's a lot more likely that I'm doing something terribly wrong. 

 

I have been attempting to do a fresh install of the Yosemite PB on my Hackintosh, for which I have decided to use Clover. I have created Clover installation USBs, both with r2774, as well as Chris's "Special Edition." No matter which I use, I am able to install Yosemite on my GPT-formatted HDD just fine. However, once I am in the OS, I can't install Clover to the HDD. I get a generic "Installation Failed" message. Any help would be greatly appreciated!

 

Mobo: Asus Sabertooth z87

GPU: Nvidia GTX 770

CPU: Intel i5-4670k 

Link to comment
Share on other sites

Hi, I was directed to this thread to ask this - apparently this could be a bug, although I think it's a lot more likely that I'm doing something terribly wrong. 

 

I have been attempting to do a fresh install of the Yosemite PB on my Hackintosh, for which I have decided to use Clover. I have created Clover installation USBs, both with r2774, as well as Chris's "Special Edition." No matter which I use, I am able to install Yosemite on my GPT-formatted HDD just fine. However, once I am in the OS, I can't install Clover to the HDD. I get a generic "Installation Failed" message. Any help would be greatly appreciated!

 

Mobo: Asus Sabertooth z87

GPU: Nvidia GTX 770

CPU: Intel i5-4670k 

what is the setting you trying? , post pics of the setting of the Installer pkg ! 

Link to comment
Share on other sites

Hi, I was directed to this thread to ask this - apparently this could be a bug, although I think it's a lot more likely that I'm doing something terribly wrong. 

 

I have been attempting to do a fresh install of the Yosemite PB on my Hackintosh, for which I have decided to use Clover. I have created Clover installation USBs, both with r2774, as well as Chris's "Special Edition." No matter which I use, I am able to install Yosemite on my GPT-formatted HDD just fine. However, once I am in the OS, I can't install Clover to the HDD. I get a generic "Installation Failed" message. Any help would be greatly appreciated!

 

Mobo: Asus Sabertooth z87

GPU: Nvidia GTX 770

CPU: Intel i5-4670k 

Are you booting in safe mode? Cannot mount the required Fat32 EFI when in safe mode.

Link to comment
Share on other sites

 

This is what a unlocked BIOS looks like:

Henrys-iMac:~ henrybrock$ nvram -p
OsxAptioFixDrv-RelocBase	%00%10*%c4%00%00%00%00
fmm-mobileme-token-FMM	bplist00%d8%01%02%03%04%05%06%07%08%09%0a%15%16%17%18%19%1aVuserid_%10%13dataclassPropertiesYauthTokenXpersonIDXusernameWaddTime_%10%12enabledDataclassesXuserInfo%11%01%f5%d1%0b%0c_%10!com.apple.Dataclass.DeviceLocator%d4%0d%0e%0f%10%11%12%13%14VapsEnvXhostname]authMechanismVschemeZProduction_%10%13p08-fmip.icloud.comUtokenUhttps_%10(AQAAAABT1UtHcBkNfFTDMR54b522Jz_VuzhuE4o~Y128870592_%10%14#A%d4%f5R%d2Bb%f2%a1%0b%d3%1b%1c%1d%1e%1f _%10%15InUseOwnerDisplayName_%10%13InUseOwnerFirstName_%10%12InUseOwnerLastName%00%08%00%19%00 %006%00@%00I%00R%00Z%00o%00x%00{%00~%00%a2%00%ab%00%b2%00%bb%00%c9%00%d0%00%db%00%f1%00%f7%00%fd%01(%012%01I%01R%01T%01[%01s%01%89%01%9e%01%aa%01%b0%00%00%00%00%00%00%02%01%00%00%00%00%00%00%00!%00%00%00%00%00%00%00%00%00%00%00%00%00%00%01%b6
Clover.LogLineCount	3000
security-mode	none
prev-lang:kbd	en:0
SystemAudioVolumeDB	%f0
Clover.LogEveryBoot	10
Clover.MountEFI	No
efi-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>B8B608B7-56E9-4A1C-B580-04E5A91D0085</string></dict></dict></dict></array>
fmm-computer-name	Henry%e2%80%99s iMac
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%00%00%ff%ff%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00@#%ce%0e%00%00%00%00%b7%08%b6%b8%e9V%1cJ%b5%80%04%e5%a9%1d%00%85%02%02%7f%ff%04%00
SystemAudioVolume	A
LocationServicesEnabled	%01
Henrys-iMac:~ henrybrock$ 

 

Oh, cool! You just confirmed mine is unlocked, at least the H77-DS3H's. Except for the fmm-mobileme-token-FMM stuff, which is absent, it's essentially the same output as the one you posted. Didn't try the command on my AMD machine, or my 1201N yet. Can non-UEFI boards have unlocked NVRAM?

Link to comment
Share on other sites

what is the setting you trying? , post pics of the setting of the Installer pkg ! 

 

http://i.imgur.com/LX3ivh4.png

 

These are the settings I use for both the USB and to install to my hard drive. Of course, when I use your custom package for the USB I select the top option as well. 

 

 

Are you booting in safe mode? Cannot mount the required Fat32 EFI when in safe mode.

 

Nope, not in safe mode. I don't think I have any boot flags, actually. 

 

EDIT: Ignore all of Niresh's stuff -- I've tried installing Yosemite that way as well, although my last attempts have been with Chris's method. Either way I end up at the same place.

Link to comment
Share on other sites

http://i.imgur.com/LX3ivh4.png

 

These are the settings I use for both the USB and to install to my hard drive. Of course, when I use your custom package for the USB I select the top option as well. 

 

 

Try same setting with r2782 but dont cheek the  OS X Installer   box  :P

 

You have a lots niresh on your Machine maiby is this causing issue 

Link to comment
Share on other sites

Try same setting with r2782 but dont cheek the  OS X Installer   box  :P

 

You have a lots niresh on your Machine maiby is this causing issue 

 

Nope, same error.  :(

 

The system that the screenshot was taken on was my laptop - I'm trying to install Yosemite on my desktop, which is a completely clean partition without any of Niresh's stuff. Yosemite was installed only with your program, so there shouldn't be any incompatibilities.  :P

Link to comment
Share on other sites

@powermapler,

 

Make sure your desktop's EFI partition is formatted FAT32  - what is the output you get when you run

diskutil list

from OSX terminal?  If you have installed Chameleon into the EFI previously, it can format the EFI to HFS+ & prevent Clover from installing there. 

 

Also make sure that the EFI partition is unmounted before you run the Clover installer, otherwise it will also fail to complete.

  • Like 1
Link to comment
Share on other sites

Nope, same error.  :(

 

The system that the screenshot was taken on was my laptop - I'm trying to install Yosemite on my desktop, which is a completely clean partition without any of Niresh's stuff. Yosemite was installed only with your program, so there shouldn't be any incompatibilities.  :P

Are you formate  the  hdd /GUID ?

Formate your EFI because I am pretty sure you have a problem partition on that drive 

Looks like a HDD trouble 

 

Type this on terminal 

diskutil list

 

and see the good  efi  partition to formate 

and type this 

 

sudo -s 

pasword 

 

 

newfs_msdos -v EFI -F 32 /dev/rdisk0s1

 

this is my exemple here rdisk0s1

Link to comment
Share on other sites

http://pastie.org/9429171

 

I do have locked nvram in OSX and I'm currently booting with Ozmosis without using EmuVariable so that is a paste of nvram.plist created from booting Clover using EmuVar.

 

Ozmosis uses a file called Defaults.plist (similar to clovers config.plist)  that does enter its contents to my boards real nvram because its loaded in to firmware before entering OSX.

 

Doh. Sorry, Joe75: I somehow didn't notice the link at the top of your post.

 

All the best!

  • Like 1
Link to comment
Share on other sites

Can non-UEFI boards have unlocked NVRAM?

Legacy boards don't even have nvram so no, but that's what Clover's shutdown scripts are for. At shutdown the script dumps the nvram content into the nvram.plist file located in the root partition, then next boot Clover will look for such file, choose the latest one and load its content again for the OS to use. The OS won't even know it's emulated.

  • Like 1
Link to comment
Share on other sites

Are you formate  the  hdd /GUID ?

Formate your EFI because I am pretty sure you have a problem partition on that drive 

Looks like a HDD trouble 

 

Type this on terminal 

diskutil list

 

and see the good  efi  partition to formate 

and type this 

 

sudo -s 

pasword 

 

 

newfs_msdos -v EFI -F 32 /dev/rdisk0s1

 

this is my exemple here rdisk0s1

 

I'm not sure I understand... I am starting to wonder if my partitioning is off. This is what my diskutil list turns up: http://i.imgur.com/tSxXPda.png

 

Where do I go from here? 

 

disk1s1 is my storage partition for Windows - as you can see the drive is formatted as GPT. In order to install OSX I created a separate, smaller partition. 

Link to comment
Share on other sites

I'm not sure I understand... I am starting to wonder if my partitioning is off. This is what my diskutil list turns up: http://i.imgur.com/tSxXPda.png

 

Where do I go from here? 

 

disk1s1 is my storage partition for Windows - as you can see the drive is formatted as GPT. In order to install OSX I created a separate, smaller partition. 

I was right !

You see you dont Have EFI on your drive  thats why clover failed  :)

 

This drive haves problem  

Link to comment
Share on other sites

Legacy boards don't even have nvram so no, but that's what Clover's shutdown scripts are for. At shutdown the script dumps the nvram content into the nvram.plist file located in the root partition, then next boot Clover will look for such file, choose the latest one and load its content again for the OS to use. The OS won't even know it's emulated.

 

Yes, my 1201N has indeed a working "nvram" because of the said RC scripts. Since legacy boards don't have real non-volatile RAM as you said, and the RC scripts are perhaps the Clover equivalent of Chameleon's FileNVRAM.dylib, I suppose I'll also have a working "nvram" on my AMD machine, which is still in Mavericks and use Chameleon to boot.

 

All the best!

  • Like 1
Link to comment
Share on other sites

Doh. Sorry, Joe75: I somehow didn't notice the link at the top of your post.

 

All the best!

 

Wanted to add most of Pavo's nvram is generated by Clover :P If yours looks similar its not an indication that nvram is unlocked. To check for sure you need to remove EmuVar, delete /nvram.plist and use nvram -c, than use something like sudo nvram boot-args="-v" and set an nvram variable yourself. Check that -v was written by using nvram -p before rebooting. After rebooting use nvram -p again and check that -v is returned, if its saved in args you do have writable nvram.

  • Like 1
Link to comment
Share on other sites

 I recently had a problem where ESP was formatted as a Microsoft Data partition using "newfs_msdos" command and had to recreate the EFI partition with gpt tool.

 

diskutil list

 

sudo -s

 

gpt -r show diskX

 

diskutil unmountDisk diskX

 

gpt remove -i 1 diskX

 

gpt add -b 40 -i 1 -s 409600 -t C12A7328-F81F-11D2-BA4B-00A0C93EC93B diskX

 

*with the disk needing to be unmounted this needs to be completed from recovery or an install different from the disk needing to be repaired

 

*C12A7328-F81F-11D2-BA4B-00A0C93EC93B is the intended GUID for ESP

 

https://developer.apple.com/library/mac/technotes/tn2166/_index.html

 

 

@joe75 posted a solution to recreate a corrupted EFI a few pages back.

 

The other option is to backup your data and repartition your drive GUID with Disk Utility's partition tab ie start from scratch with a clean slate (easier).

 

Interesting... So would his "diskx" be disk1s1 for me? And would this cause any data loss from that partition? 

Link to comment
Share on other sites

Wanted to add most of Pavo's nvram is generated by Clover :P If yours looks similar its not an indication that nvram is unlocked. To check for sure you need to remove EmuVar, delete /nvram.plist and use nvram -c, than use something like sudo nvram boot-args="-v" and set an nvram variable yourself. Check that -v was written by using nvram -p before rebooting. After rebooting use nvram -p again and check that -v is returned, if its saved in args you do have writable nvram.

 

I don't have EmuVar, Joe75. :)

Link to comment
Share on other sites

score! i didn't see that before.. so nvm :P


Interesting... So would his "diskx" be disk1s1 for me? And would this cause any data loss from that partition?

 

Yes, disk is disk1 "-i" in the command is what dictates the partition 

 

understand any commands you use with gpt because its a powerful tool

 

Yes, complete data loss of efi partition because you are removing it and recreating it

  • Like 2
Link to comment
Share on other sites

×
×
  • Create New...