mokeev1995

threre's not way to do so. You should use only MBR for legacy or "hybrid disk" with gpt and mbr partitions(that is real workaround, don't think you should do somthing like that). BTW you can use own disks for each OS.

i'm not sure if google translate can help you, but here's link(RUSSIAN language) that can help you.

try to clear nvram and cmos. or flash modded bios again with rewriting all sections, it should help

yeah, our Wi-Fi+BT card don't support airdrop and continuity. if you want this you should replace it with compatible card like azurewave aw-ce123h. if you'll do this then you'll have Wi-Fi 802.11b/g/n/ac support and Bluetooth 4.0

last my attempt shows that all you needed -- run kext utility and drag&drop this kext (i use yosemite, so don't know if it works in el capitan) ----- HERE IS LINK IN GOOGLE DRIVE: https://drive.google.com/open?id=0B7C42B_4OyzTRFRNWkx4el9iM3c

can you send this kext one more time and via Google Drive/Mega or something like that?

azurewave aw-ce123h ( http://www.ebay.com/sch/i.html?_from=R40&_trksid=p2047675.m570.l1313.TR0.TRC0.H0.TRS0&_nkw=azurewave+aw-ce123h&_sacat=0 ) with this card you can use airdrop and continuity, as i know :-) try to use it

clover uses built in EFI if exists or emulates it with rEFIt chameleon/chimera only emulates EFI if your system has (U)EFI it's better to use clover instead of chameleon or chimera

So, and what about clover? As I know Clover is much more better than Chameleon.

a few posts earlier you can see something like new guide. but i'm not sure, that all will work fine.

Hi there, I've got a small question: In clover directory we've EmuVariableUEFI-64.efi. As I think it uses for NVRAM emulation. BUT with this file NVRAM reset after reboot. If you delete this file all works fine. So, that's the question: for what purposes this file are there? 1) you should set timeout to 1 or 0 and set your default bool volume to LABLE of volume, where OS X is installed. 2) ... 3) maybe it can be fixed by deleting EmuVariableUEFI-64.efi from clover directory

What did you do to make it work?

yep

Maybe you did something wrong while creating bootable usb.. Try to do it once more, sometimes it's can help to solve your problem)