2017년 2월 19일 일요일

Clover bootloader failed to install or boot : how & why (not for beginners)


Most frustrated situations using Clover bootloader are failed to boot, which caused from the installation failure even though you've been using Clover bootloader without issues.

1. Fail to boot with Clover bootloader: Whatever the reason why, In this case, you need to create a bootable USB of Clover bootloader under Windows environment, and the most easy way of doing this is done by BDUtility:

http://www.insanelymac.com/forum/topic/283190-bdutilityexe-make-clover-bootflash-with-macos-distr-under-windows/

BDUtility formats the USB and install the latest Clover bootloader by itself. No other easy way to do it under Windows.

After booting with new created USB by BDUtility, you can select the existing partition booted successfully before. Once you boot into that mac partition with USB booting, then you have to install Clover bootloader again into the specific booting partition with fine tunings of parameters.

Of course, you should be familiar with changing boot sequence in BIOS to change booting sequence into new USB to boot at first.

2. Installation failure of Clover bootloader: you should check if EFI partition is filled with backups of previous versions. No space to install would cause the installation failure but no specific reason why failed in the screen. Please delete backup of previous Clover bootloader except for the last one. You can see the sample screen capture that only r3949 is left and all other backups are deleted below:


These are based on the assumption you're in trouble after installing new version of Clover bootloader. Please refer this URL if you are new to Clover bootloader:


https://www.tonymacx86.com/threads/clover-basics-and-switching-advice.171680/

2016년 9월 14일 수요일

Nvidia GTX770 (moving from GTX660 to GTX770) on El Capitan using Clover bootloader


Two things we have to remember :


  • Do not use "Inject NVidia" to prevent from black out after booting. However, this leads the issue of HDMI audio because it was required for HDMI audio.


No others worked for me, but here goes URLs for your information because it is not sure that "HDMIAudio.kext" triggers on top of others :

http://www.rampagedev.com/?page_id=276&page=13


Summing up, avoid "Inject NVidia" and drop kext of HDMIAudio.kext, that's all.

Best Regards.

Specification:

ASUS GTX 770 DirectCUII 2GB DDR5
Gigabyte B75M-D3H / 16GB
Clover 3696


2016년 8월 3일 수요일

Bluetooth dongle at Mac OSX 10.11.6 : Broadcom chipset recommended, CSR doesn't work


Please refer this for any new installation reference of Gigabyte B75M-D3H :
http://macosx4pc.blogspot.kr/2015/10/mac-osx-1011-el-capitan-on-gigabyte.html

You may be suffered from Bluetooth in USB after update to Mac OSX 10.11.6 the latest as of 3-Aug, 2016. The symptom for me is to connect & disconnect in repeat so that I cannot connect to any USB devices due to this symptom. You cannot see nothing in Bluetooth sections in System report as a result.

I've googled more than 3 days to look up the solution of this USB bluetooth issue, but no solution at all.

For your information, my machines are under this environment :

Clover bootloader : v3650 latest
- Please check only the options in below if you install Clover in ESP like me, and include all files under Drivers64UFI. Some document in the internet recommends to install some of them, but you may face the boot failure. So, it is safe to install all files under Drivers64UFI.


- in config.plist in ESP (/EFI/Clover/config.plist), I checked FixUSB. I didn't include anything for USB in KextsToPatch.

Drivers like FakeSMC & Generic USB3 drivers :
- Please update FakeSMC to the latest in /Volumes/EFI/EFI/CLOVER/kexts/10.11/ & /Volumes/EFI/EFI/CLOVER/kexts/10.10/ with same files.


- The latest USB drivers because USB bluetooth dongle caused issues in many cases
   (I installed 'RehabMan-Generic-USB3-2015-1215' & 'RehabMan-FakePCIID-2016-0512') for your information.

Hardware : USB dongles : it is most important after all. CSR 8510 chipset failed after no matter what I did even though it worked very well before 10.11.6. But, I found out Broadcom chipset works well!

* I don't guarantee the solution above would not cause any issue for you. This is just for your information.

2015년 10월 12일 월요일

Mac OSX 10.11 El Capitan on Gigabyte B75M-D3H using Clover Bootloader (together with Yosemite)

Though it is not a major upgrade from Yosemite to El Capitan (10.10 to 10.11), some small things to consider before starting to install El Capitan 10.11, so I'd like to share it here briefly. But, I assume you are familiar with Yosemite and Clover. If not, my previous document for Yosemite installation would be helpful for you :

http://macosx4pc.blogspot.kr/2014/10/clover-bootload-with-yosemite-moving.html

0. Backup, Backup, Backup : You should clone or copy your existing Yosemite partition. I cloned it to another partition in same PC to share the same Clover bootloader.

Notice: Following steps are my trial and errors to install El Capitan, you can refer this by your own risk & responsibility. No guarantee for you to make it work by following same procedures. Please stop here if you can't do that it by your own responsibility.

1. Clover bootloader : Upgrade it to the latest, but I selected 3276 because some of unknown issues for 3280 for me. You need to update Clover Configurator to the latest too.

http://sourceforge.net/projects/cloverefiboot/
http://www.hackintoshosx.com/files/file/49-clover-configurator/

The files I selected for driver64 :
    FSinject-64.efi, UsbMouseDxe-64.efi, VBoxHfs-64.efi
The files I selected for driver64UEFI :
    FSInject-64.efi, OsxFatBinaryDrv-64.efi, EmuVariableUefi-64.efi, HFSPlus.efi, OsxAptioFix2Drv-64.efi

Updated on 30-July.2016: You can click drvier64UEFI to include all kext files. And, check UEFI boot only & EFI Clover only when you create EFI partition in separate like me. If you install Clover EFI in ESP but don't check ESP Clover option, your install would be failed. FYI, I installed Clover 3650 without issues.



2. Clover Configurator : Must-have utility to configure Clover bootloader

You should mount EFI at first to update config.plist file, go to Mount EFI, and select Mount EFI partition. disk0s1 is EFI partition for me. Then select the config.plist file at File -> Open, EFI -> Clover folder in sequence.

All you need to update are 1. BooterConfig and CstActiveConfig at RtVariables like this : 0x28 and 0x3.

And, 2. check rootless=0 at Boot sections (see right picture to see the sections I refer)

Create 10.11 folder under EFI/CLOVER/kexts/, then copy the files under 10.10 into 10.11 folder. But, I downloaded the latest fakeSMC.kext from here :

http://www.tonymacx86.com/downloads.php?do=cat&id=11

For your information, followings are not matter for me (so to speak, it doesn't matter to do or not do to) :

  • Copy the files under 10.10 to [Other] folder
  • Removing kext-dev-mode=1
  • CstActiveConfig : 0x3 or 0x63
  • Deleting all folders under EFI/CLOVER/kexts except for [Other] or [11.11]
You need to check if new Clover bootloader is working with your exisiting Yosemite before starting El Capitan. That's why I turned on Verbose (-v).

3. Enable HDMI sound of NVidia GTX 660 after installation : please run audio_cloverALC-110.sh at following site after downloading and decompression. No need to select "Enable HDMI of Intel CPU" but need to select ALC887 for B75M-D3H mainboard, but this enables HDMI sound of GTX 660 too for me.

https://github.com/toleda/audio_CloverALC

Added on 30-July.2016: If your HDMI Audio doesn't work after installing latest Clover, then please check if NVAudio.kext file exists in /Volumes/EFI/EFI/CLOVER/kexts/10.11/ even though audio_cloverALC-110.sh executed. You can copy it from ../10.10/ to ../10.11/ folder.

That's all! You finished major steps to install El Capitan on Gigabyte B75M-D3H.

P.S: Following URL is the references for trial and errors, and I found out the clue for sound issue here. But, no other issues for me at this moment:

http://www.tonymacx86.com/el-capitan-desktop-support/173991-big-list-solutions-el-capitan-install-problems.html

FYI, I failed to upgrade my existing Yosemite to El Capitan as I've done from Maverick to Yosemite due to unknown Kernel Panic issue. So I install newly on new partition after making backup of Yosemite into another partition. I will share any new fact findings from now on here.

13-Oct. 2015 updated: I found out that files in driver64 & driver64UEFI are essential to boot Yosemite successfully with updated Clover bootloader. If you are in trouble like stuck in boot screen +++++++++++++++, or kernel panic, then please check files in these two folders in EFI partition. Most of the errors while booting are relevant with files in these two folder in my experience.

Only one issue unsolved are no SATA/SAS information displayed at About My Mac, which blocks to check if Trim is working or not. But, I assume it works by config.plist update as I stated in my previous posting for Yosemite :
http://macosx4pc.blogspot.kr/2014/10/clover-bootload-with-yosemite-moving.html

Thanks for your reading!

Added on 22-Oct : I updated Mac OSX 10.11.1 natively by installing at AppStore without issue.

2014년 10월 19일 일요일

Mac OSX 10.10 Yosemite installation by moving from Chameleon to Clover Bootloader @ Gigabyte B75M-D3H, HDMI & ALC887

http://macosx4pc.blogspot.kr/2013/10/maverick-109-on-b75m-d3h-unsing.html

Please refer the link above to understand my environment.

    Yosemite has finally announced on 17-Oct, but the migration from Maverick to Yosemite is not easy than I expect with following reasons : 1. Mutibeast 7.0.0 installation generated the booting error : Still Waiting for root device... with repeating, or BUG in process suhelped[1580]... with repeating, or USBMSC Identifier (non-unique).., and all the solutions mentioned with googling doesn't solve these issues, so I made conclusion that Unibeast 5.0.1 + Multibeast 7.0.0 is not the solution at least for me. Two days has been passed, so I decided to give up Chameleon/Multibeast and move to Clover bootloader.

Updated on 21-Oct : I realized that Bluebooth issues are not caused by Bluetooth but by USB3.0, because I plugged Bluetooth USB into USB3.0 port, and moving to USB 2.0 port works. So, I guess that something wrong with the USB 3.0 driver, and I found out same thing here, and now USB 3.0 is back to work! Summing up, you need to delete GenericUSBXHCI if it's installed in /S/L/E, delete it and download new driver here & install it by using Kext Drop etc.

https://bitbucket.org/RehabMan/os-x-generic-usb3/downloads/RehabMan-Generic-USB3-2014-1016.zip

Full explanation here :

http://www.tonymacx86.com/yosemite-desktop-support/144794-ga-z77x-ud5h-tips-yosemite-vs-usb-3-0-a.html

Following steps are assumed that you read the URLs above already :

Updated on 22-Oct : If this is your first time of Yosemite, you have to understand the key change versus Maverick : In MAC OSX 10.10 (Yosemite), Apple has introduced a new security policy called kext signing. Kext signing works by checking if all the drivers in the system are unaltered by a third party or approved by Apple. If they have been modified, Yosemite will no longer load the driver. So, you need to set boot argument : kext-dev-mode=1 by default for Hackintosh.

Following explanation is started from the point where my installation of Yosemite by using Unibeast 5.0 was failed to boot with Chimera 4.0 or Clover bootloader. Fortunately, I can boot new installed Yosemite by using USB created by Unibeast 5.0, and LAN is working without installed any kext file. If you want to start Yosemite by Clover from the beginning, please refer below:

http://www.tonymacx86.com/yosemite-desktop-guides/144426-how-install-os-x-yosemite-using-clover.html

You can refer my document from here is to understand Clover as an user of Chameleon :


1. Install Clover (I assume you have the mainboard with UEFI BIO, otherwise no benefit of using Clover I heard)

We have to format the disk with GUID not MBR to install Clover bootloader, and the BIOS of your mainboard would be UEFI like B75M-D3H. (I assume that no issue for you to use GUID because we usually format the disk with GUID option before installing Mac OSX)

The disk in GUID has the EFI partiton as you the picture below named EFI - /dev/disk0s1 in this case:

[boot partition is where Yosemite installed, EFI partition is where to install Clover bootloader in a same drive : you can see 209.7MB EFI partition created by itself below, this is where Clover bootload will be installed]

Now, we need to format this EFI partition before installing Clover bootloader:

sudo newfs_msdos -v EFI -F 32 /dev/disk0s1

Then, install Clover bootloader, and please make sure of the drive you want to install it, but no customization required for option. Leave it as default.


Now, you need to add the kext files fit to your system which requires to mount EFI partition to move the files:
mkdir /Volumes/efi
sudo mount -t msdos /dev/disk0s1 /Volumes/efi
Please refer if you're into these kind of commands here:

http://themacadmin.com/mounting-the-efi-boot-partition-on-mac-os-x/

Now you can see the icon of EFI partition on the desktop, Please Navigate into EFI/CLOVER/kexts folder, then create new folder there named "10.10".


Finallly, you need to move some files like FakeSMC.kext, NullCUPP...ement.kext, NVAudio.kext, Patched_1...eRTC.kext. It depends on your system, but FakeSMC.kext is required at least. I copied NVAudio.kext to enable HDMI audio of NVidia GTX 660 OC Graphic card. Recommend you to look for the latest version of these by googling, because it would be out of dated when you read this document.


You completed the installation, but one more step remains to add boot argument to Clover bootloader.

2. Clover Configurator : Easy tool to change the option of Clover bootloader.


http://www.hackintoshosx.com/files/file/49-clover-configurator/

You need to modify config.plist at /EFI/CLOVER as you see above, and Clover Configurator is the simple tool to do it.

Please copy config.plist in EFI partition at /EFI/CLOVER you mounted to the desktop, then open it by Clover Configurator.app.


After importing, move to Boot Sections by clicking the name at left pane, then check verbose, kext-dev-mode options to see the booting message to see if something wrong, you can disable verbose later by same way.


Added on 21-Oct : I realized the rebooting caused the issue on HDMI Audio & Bluetooth again strange enough. And, I found out NVidia Injection solved this issue even though GTX 660 OC should be recognized by default.

Some changes I made here (check box) :
  • Boot / Verbose
  • Boot / dart=0
  • Boot / kext-dev-mode=1
  • Graphics / Inject Intel
  • Graphics / Inject NVidia

Updated: Enabler Trim @ Yosemite GA - Clover Configurator added wrong value

http://www.tonymacx86.com/general-help/144796-yosemite-trim-clover.html

I found out the same issue as above link, Clover Configurator added wrong value different from what I stored at 'Kernel and Kext Patches'. So I modified config.plist by BBEDIT.app & store, then it works!

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

[Trim support : Yes]

For your information, the actual number registered in config.plist shown by Clover Configurator is like this :

Find :      004150504C452053534400
Replace : 0000000000000000000000




If you want to know more about the detail of Clover SECTIONS, please refer this URL:

http://clover-wiki.zetam.org/Configuration

Save this file, and replace config.plist in EFI partition, /EFI/CLOVER as I explained.

Then reboot the system to see if working well, and I found out the HDMI Audio of GTX 660 OC and bluetooth are working well.

Added on 19-Nov.2014 : You can enable the ALC887 on-board soundchip together with or without HDMI audio. You can refer following URL :

https://github.com/toleda/audio_CloverALC

It's simple though full of explanation. I can see HDMI and ALC887 line-output both in Sound.

Clover Patched AppleHDA - Installation
  1. Clover Realtek ALC AppleHDA.kext  (patch in place)
 1. https://github.com/toleda/audio_CloverALC/blob/master/audio_cloverALC-100.command.zip
 2. Download (View Raw)
 3. Double click Downloads/audio_cloverALC-100.command
 4. Password?
 5. Verify Codec? (885, 887, 888, 889, 892, 898, 1150 only)
 6. Legacy_v100202 - y/n? (887, 888 only)
  2. Restart
  3. Verify ALC onboard audio
 1. System Preferences/Sound/Output/select audio device 


Summing up, it's too early to expect the complete solution like Multibeast or Unibeast. And, it's good time to move to Clover Bootloader. But, it would be better when you read this document.

And, I recommend you to migrate your existing Maverick partition into Yosemite after clean installation of Yosemite. Which is the more simple and clean(?) method rather than upgrading your existing Maverick partition up to Yosemite.

P.S: You're wondering that how can I have Yosemite installed partition without the bootloader installed success. Good question!. I installed Yosemite into new partition by Unibeast 5, but failed to boot it with Multibeast with errors I mentioned at the beginning of this document. So, I changed my mind to install Clover Bootloader by giving up Chimera & Multibeast.

Added on 19-Nov.2014 : After update to 10.10.1, all you have to do is to reinstall USB 3.0 kext mentioned above. All others are working with same config.plist of Clover you generated.

2014년 5월 2일 금요일

Back to Chameleon from Clover bootloader (removing EFI partition is key)

    All of my trials to enable iMessage & Facetime at AMD CPU have been failed for last half year. The last thing I didn't try to do is changing bootloader from Chameleon to Clover. (Following is my history of installation of Maverick on AMD CPU)

http://macosx4pc.blogspot.kr/2013/12/maverick-mac-osx-109-installation-on.html
http://macosx4pc.blogspot.kr/2013/11/maverick-mac-osx-109-installation-on.html

    Replacing Chameleon with Clover was simple, and I think it's not necessary to write it because you are reading this document to delete Clover bootloader. I installed Clover bootloader after booting Maverick with Chameleon.

    However, Clover didn't solve the issue on iMessage & Facetime even though all the things work fine (HDMI audio, LAN, Video etc.) But, I think the Chameleon is better because it's simple, and no benefit of using Clover for me.

   Here comes the trouble, cannot move back from Clover to Chameleon even though I uninstalled Clover bootload by using AppCleaner, delete all EFI directories on boot disk, reinstall Chameleon bootloader many times. All trials failed.

    The reason why I cannot move back to Chameleon is due to EFI partition which was created during installation of Clover I think. So I've been looking for how-to delete this. But, it was not easy because it's used when booting Maverick. (aka protected)

    What about to delete this at Windows, because that EFI partition is not used anymore. And, here is the solution: using diskpart at cmd in Windows environment.

http://www.youtube.com/watch?v=fgZBKwhNhTs


  1. cmd
  2. diskpart
  3. list disk
  4. select disk x (x means the disk number where EFI exists)
  5. list partition
  6. select partition x (x means the partition number where EFI exists in disk x)
  7. delete partition override
  8. list partition
  9. exit or quit
You should make sure if you select right partition you want to delete several times!


    Now I can see Chameleon bootloader again by selecting the disk where Chameleon installed!


2014년 3월 9일 일요일

Using KeyRemap4MacBook : Ctrl key doesn't work at Hackintosh

This is a fact finding to assign Command key feature to Ctrl key of Lenovo ThinkPad USB keyboard.

http://www.amazon.com/Lenovo-ThinkPad-USB-Keyboard-English/dp/B002NSDWPM

You need to download KeyRemap4MacBook app, and check the option :

Change Option_L Key (Left Option)
-> Option_L to Command_L

Close the KeyRemap4MacBook, you can use Ctrl key for Ctrl-C or Ctrl-V from now on.