Jump to content

yc_richard

Members
  • Content Count

    23
  • Joined

  • Last visited


Reputation Activity

  1. Confused
    yc_richard got a reaction from StephenMip in Secure boot signing tools for OS X (sbsigntool-0.6-Clover_V3 with updates and Apple based libraries)   
    Awesome job, man! by chain loading Clover with Shim, it works in non secure boot at the moment for me. I signed Cloverx64.efi with sbsign and rename to grubx64.efi under the same folder of shim.efi, then enrolled the clover certificates using mokmanager. With secure boot on, it shows "binary is whitelisted" and does not load the secondary bootloader(clover in my case). You have any ideas?
     
    Could you help me to about the long named UEFI script (OnlyDBs.ps1) you mention in the instruction please. I did not find it in any resources. I am also interested about what it does in windows's cmd.
    Secondly, is it necessary to sign the boot.efi in /System/Library/CoreServices ?
    Last, I am on a surface pro 3, it seems to come with the UEFI 3rdParty CA installed, does it mean I will only have to register the clover certificates using mokmanager (or keytool)?
  2. Like
    yc_richard reacted to midi-sama in El Capitan UEFI Clover on Sony Vaio S   
    EXPERIMENTAL
    So hey there, been a while! 
    So I've successfully booted macOS Sierra DP1 and it's kinda good and toooo buggy as expected from a newly released OS. The installation is simple and I'll be sharing it with you here.
     
    Disclamer
    I, or anyone else on this forum, are not taken in responsibility for any harm happened to your device/data/materials/your belongings/... By following this guide you agree to take all the responsibility for your actions. This is highly experimental material, may harm, but it shouldn't, and if it did, you did it!
    This is for people with experience, I'll be putting some known OSx86 jargon like CIM and BaseSystem method. If you don't know this, either stop here, or google that your self and look in the forums.
    End of Disclamer
     
    So what you need is: 
    a working 10.11 machine an optional USB drive of 8GB (optional, but may be needed if you are doing this from another computer) at least 20GB free on space left (this should be left even after downloading the OS X installer, make sure you have plenty of space left on your laptop!!) patience I'll be doing this from my VAIO S laptop directly, if you're using some external device, please try to do some analogy and give it a shot.
     
    Before starting, here are some bugs and problems you may face when suing Sierra DP1
    Many apps may crash, hang or just wont do their work (like Clover Configurator [crash] and telegram [just hangs while spinning the loading wheel]...) Don't expect a good battery life, even if in my tests it wasnt that different but do not take it as granted This is an experimental OS, DO NOT USE IT AS YOUR DAILY DRIVER OS, well unless you have some balls of steel, then you can, I have no physical power over you The touchpad driver we'll be using is total {censored}! Too bad VoodooPS2 causes KP, hoping for RM to fix it (dont get your hopes high on this yet, he may even release a new version until the final OS release!). The kyb doesn't have working Fn keys, and Alt and Win button are swapped! The touchpad prefpan is broken [still needs confirmation] CONFIRMED, RM said he *may* start working on a prefpan, that would be totally gr8! Everything else is working ok-ish.
     
    okey let's start!
     
    Get some patched material! patched AppleALC for 10.12 (we'll be using this instead of DummyHDA)  patched Clover for 10.12 booting (taken from the pkg here http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page-517?do=findComment&comment=2242991 ) A crappy PS2 driver for Synaptics (whereas on ELAN it's the best) not anymore  VoodooPS2Controller.kext.zip https://bitbucket.org/RehabMan/os-x-voodoo-ps2-controller/downloads Latest Rehabman's FakeSMC (google) Get your copy of DP1 (sorry wont be posting links, forum rules) Choose your pill: Old fashioned "make a partition, make cim, install as you would" (I wont be discussing this, but make sure you use the correct Clover procedure, the other stuff is common knowledge) Experiment labtop (pun intended) where you'll make a dmg with OS X installed in, just restore it to any partition (I'll be explaining this one only) Make clover great again: Download the patched clover file, mount EFI (diskutil mount diskXs1, where X is your boot drive, usually 0), copy it under Clover folder Rename the previously downloaded file to BOOTX64.EFI and copy it to /EFI/BOOT folder (note 1: use this if Clover is your main EFI booter. note 2: it will replace any file named BOOTX64.EFI, make a backup of it) Go to Clover > kexts, make a folder named 10.12, copy all kexts from Other (that's what your should be normally using if you're following johnrey's guide) to the 10.12 folder, open 10.12, remove VoodooPS2-FakeSMC-AppleALC (if found). Copy the patched kexts above there. Let's AutoDMG Ok as you can see, use the link above, you'll get it once there Open AutoDMG Open <your OS X partition>/System/Library/CoreServices, locate SystemVersion.plist, duplicate it and rename it to SystemVersion.orig Open SystemVerison.plist (use sublime text or text edit) and replace everything with this:  <?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>ProductBuildVersion</key> <string>16A201w</string> <key>ProductCopyright</key> <string>1983-2016 Apple Inc.</string> <key>ProductName</key> <string>Mac OS X</string> <key>ProductUserVisibleVersion</key> <string>10.12</string> <key>ProductVersion</key> <string>10.12</string> </dict> </plist> Save and go back to AutoDMG Drag the OS X 10.12 installer app on AutoDMG window and let it analyse Hit Install and choose where to put the target dmg, let it install and wait (and this is why 20 GB of free disk on your os x partition is needed) Once done, restore the partition inside the dmg to whatever partition you like : internal HDD/SSD or external one, DO NOT USE USB AS THEY ARE SLOW AF! here is a quick how to: if you're using the ported yosemite disk utility, it's easy if not, open the Disk Utility Mount the dmg file (skip verification) Select your target partition NOT THE SOURCE Hit Edit (top bar) and then Restore Choose the SOURCE partitions (it should be named Macintosh HD) and then hit Resore You may need to restore it a second time (mostly the first time will *fail* but it did not, it just didnt copy the recovery partition) Here, once done restoring, go back to CoreServices folder, remove the SystemVersion.plist and rename SystemVersion.orig to .plist Reboot Enjoy Hope I helped, and thanks to all people who helped in this quick advance in macOS Sierra install
    Notes:
    DO NOT USE THIS OS TO DO YOUR WORK NO MATTER WHAT THE REASON (unless you're looking for bug or whatnot) It may be hella sluggish! even on SSDs! Bluetooth on some chipsets may not work (BCM devices) as the kext responsible of firmware uplaoding needs further fixing, while some of you who may have AR3011 (included in AR5B195 or AR5B197 wifi chips) may work (confirmed but not very sure) Use a usb/bt mouse PLEASE, the driver sux so much that I may only applause the dev for making pinch-to-zoom (which only replace Ctrl++) You may use your touchpad too! but yeah! Some screenshots:
     

     
    Siri
     


     
    Notification Center
     

     
    Bluetooth

     
     
    Some additions for a better OS experience:
    Disabling SIP Reboot to recovery Open terminal type in  csrutil disable Reboot Enable "Anywhere" under Security and Privacy to allow foreign/unsigned apps open terminal type in  sudo spctl  --master-disable Done  
    Enjoy
  3. Like
    yc_richard reacted to johnrey in [GUIDE] Install Mavericks/Yosemite on Sony VAIO S (2012) -and other UEFI capable VAIOs-   
    Here is a list of things that changed in El Capitan:
    no "kext-dev-mode" but new System Integrity Protection (SIP) or "rootless" New USB Drivers New AppleHDA patch CodecCommander no longer works in EFI folder > must be in S/L/E New BT4LE Handoff Hotspot patch & kext New Backlight patch & kext New Boot Glitch patch
  4. Like
    yc_richard reacted to Mirone in AppleHDA for El Capitan discussion   
    the bad news is:
     
    I'll be out of hackintosh scene
    for an indefinite period. that's all, guys   The good news is that updated my github repository: https://github.com/Mirone/AppleHDA_10.11   best regards   Mirone
  5. Like
    yc_richard reacted to MilesTEG1 in Bug connexion iMessage El Capitan with Clover   
    Hello,
    After installing El Capitan GM, I also got an error with iMessage : the contact are not activate with the service...
     
    It appears that my ROM/MLB value are the cause of the problem. On Yosemite, and before with Mavericks, I used my MBA MLB & ROM values. But now with El Capitan, or maybe after installing from zero El Capitan, those values seems not permitting using iMessage & FaceTime anymore.
    I can connect and activate the service, but when I want to chat with someone with whom it works on my MBA, i get an error telling me this email's contact isn't registered with iMessage.
    Here an example of what I get : (with a fake email, so for this one it's normal )

    I tried to change the SMBIOS Values with CloverConfigurator... It works for one time, and after reboot, the error occurred again.
    But I find a way to get iMessage working.
     
    How I managed to get iMessages working ?
    I deleted all SMBIOS values and MLB/ROM from my config.plist, disconnect from all Apple services (iCloud, Messages...) and reboot. Eventually delete all files related to iMessage and other apple configuration files.
     
     
     
     

    I checked with iMessage_debug the value I have : still the same... WTF... I disconnect from internet , and I set new values with CloverConfigurator, but not setting MLB/ROM, still not present in config.plist.
    Reboot.
    And see the SMBIOS values has changed, but the MLB doesn't...
    After severals reboot, still unchanged...
    So, I tried new SMBIOS values again. But this time, I created a MLB with my S/N adding 5 random numbers/letters after to get a 17 long MLB string.
    I fixed it in config.plist, reboot. And go to CloverConfigurator again to generate the rom value with this section by filling the values and hitting Generate button.

    Save the config.plist and then reboot again.
    Check with iMessage_debug the values are persistent.
    Connect again iMessages, and see that now it's working. Connect iCloud. Reboot and check again.
    Now I have iMessage working.
     
    It'a a pain in the ass i admit !

  6. Like
    yc_richard reacted to Quattro74 in Secure boot signing tools for OS X (sbsigntool-0.6-Clover_V3 with updates and Apple based libraries)   
    I was able to use the sbsign tool provided here to get secure boot enabled on my Surface Pro 2. No More Red Screen!
     
    First I had to download the software provided above as I have Mavericks installed I chose version 3, should also work for Yosemite. I just used the pre-built executables by moving them into my /usr/bin I made sure to have newer versions of openssl, etc. installed. Any how once I signed all my Binaries in my Clover folder and Boot Folder. And added Policy <string>Deny</string> and Secure <true/> to by boot section of config.plist, I still couldn't figure out how to make it work.
     
    So I installed the latest version of shim-signed from my ubuntu VM.
     
    sudo apt-get install shim-signed
     
    I copied over shim-signd.efi to my EFI/Microsoft/Boot folder
    and named it bootmgfw.efi
     
    I already had a copy of Cloverx64.efi there so I re-named that first to grubx64.efi which is what shim looks for.
     
    The original microsoft bootmgfw.efi I renamed to bootmgfw-orig.efi, I created a custom entry in my config.plist that points to it.
     
    Surface Pro 2 is tricky as it doesn't come with the UEFI 3rdParty CA installed so I had to find this tool online and download it. It is a series of scripts and files that you can use in windows to upgrade and add the 3rd party DBs so that you can use the signed shim to chain-load Clover.
     
    It usually needs mokmanager to install its certificates. But I found it easier to use a keytool.efi USB key that I was able to create from an easy to find image that is out there.(Google)
     
    I converted the clover signing certificate to a format that shim could use using openssl
     
    openssl -x509 -in /path-to-clover-sign.pem -inform PEM -out /path-to-converted-clover-cert.cer -outform DER
     
    or something like that.
     
    Keytool needs the file to be named .cer in order to use it even though it is DER format.
     
    So the procedure to lock down the surface pro 2 once all the binaries are signed is:
     
    -Clear all of the secure boot section by disableing secure boot.
     
    -Open the long named UEFI script that installs the microsoft dbs with right-click>edit,
     then in powershell eliminate the final line that talks about the PK. save as OnlyDBs.ps1
     
    -Close and open the same long ass file as above, this time eliminate everything except the final line about the PK, save as OnlyPK.ps1
     
    -Then run the OnlyDBs script with a comand prompt as admin. It should run without any errors.
     
    -Copy over all of the .cer files you can find in the sbsigntool package. to the usb keytool stick including the new one that you created above.
     There should be one called cannonical that is used to sign the KEK and DB, another one under /src called Clover-signed.der(Re-name it to .cer)
     
    -shutdown and boot up into the usb keytool. Use the Edit keys>Add to find the .cer files you copied over. The main cert that you used to sign the binaries then converted is the one to add to Mok db. Add all of them, one at a time, to DB, adding is the same as appending. Then the Kek is only getting the Canonical one added.
     
    -Then reboot up into windows and run the OnlyPK.ps1 script. using the Admin Cmd prompt.
     
    -Reboot into UEFI bios and enable secure boot. Save>Re-boot.
     
    Should see black screen. then Clover.
     
    The reason we have to use Shim is cuz it's one of the few trusted loaders that Microsoft decided to sign. So by chain loading Clover with it we can eliminate the red screen. Which we wouldn't be able to do using a self signed key of our own.
  7. Like
    yc_richard reacted to WaldMeister in [How to]Clover on EFI partition/Add to Bios   
    Hi,
     
    Well, i had to write a little tutorial on how to do this: http://www.insanelym...tion-guide-wip/
     
    Just a copy/paste from that topic, so the guide does contain some information that is not present or irrelevant.
    It needs editing, perhaps a lot, but i thought i would post it here.
    Why? I will explain.
     
    Clover comes with an installer package, and people will drop folders on the web everywhere (System specific), but never a descent tutorial on how to actually UEFI boot can be found (perhaps i did not look into this enough)
    Personally the installer package did not make it possible for me to add the option in the bios, nor boot my OS X installation anymore, that is mainly the reason why i wrote this poor excuse of a guide
    I tried every option on the installer, could not make it work, so i figured, let's do it manually. Read about what UEFI can and can not do, went through the Clover documentation, although, i did not understand much about it, until i actually got it to boot.
     
    To install it to the EFI partition, i took information from the Chameleon guide, found here: http://forum.voodoop...x.php/topic,649
    and modified it to suit my BIOS's needs. (MSDOS filesystem)
     
    I hope someone will take the time to modify this tutorial, to make it beginner friendly, or just remove it, if something like this already exists.
    The screenshots are from a Phoenix Bios, don't know about the others.
     
     
     
     

    How to install Clover and add it to the UEFI Boot menu:
    - Be careful when replacing the current boot loader, your system may become unbootable if you skip a step, or do not pay attention!


     
     
    To UEFI boot Clover, we need to install it to a FAT32 partition, UEFI will only find partitions in this format.
    I recommend to test Clover on a USB stick formatted in FAT32, and just copy the files to it, before actually replacing the current bootloader.
     
    1.)
    First we need to find the HDD that has OS X installed on a GUID partition table, and look for the EFI partition. Open terminal and type:

    sudo -s type password diskutil list
     
     

     
    I have Clover already installed on disk0s1, for this guide i will install it to disk1s1, which is my spare HDD, also formatted to GPT.
     
    2.)
    We need to apply a new filesystem to the EFI partition, remember to replace the X corresponding to your disk setup.
    In terminal enter:

    newfs_msdos -v EFI /dev/diskXsX
     

     
    It will give an error, you can ignore it. The EFI partition has been formatted to FAT32 and can now be recognized by UEFI.
     
    3.)
    Now it is time to mount the EFI partition and copy the needed files. Type the following into terminal, remember tot replace the X's:

    mkdir /Volumes/EFI mount_msdos /dev/diskXsX /Volumes/EFI

    Go to finder, on the left hand side, you will now have a disk called EFI.
     
    4.)
    Now download the Clover_Package.zip, if not done already. After extraction, you will have a folder called EFI, copy the folder with all the contents to the EFI partition.

     
    To this:
     
     

     
    5.)
    Go back to terminal and type the following, replace the X's:

    umount -f /dev/diskXsX rm -rf /Volumes/EFI
     
    Now Clover has been installed to the EFI partition, now it is time to add the boot option to the UEFI boot menu.
     
    - Restart your system and press F2 multiple times, you should now enter the bios.
    - Go to the Boot options tab, use the arrow keys. (What keys you can use, are described at the bottom of the screen.)

    - My setup will probably differ from yours, change them accordingly, select add boot option and press enter.

    - Now enter a name, i use Clover, press tab, and select either HDD (If you have Clover installed to the EFI partition) or USB (if you have installed Clover to a USB device on a FAT32 partition), you can select it with the arrow keys. Now press tab and enter: EFI\BOOT\Cloverx64.efi
    Press tab again, select ok, and press Enter.

    - Clover has now been added to the boot menu. Move up with the arrow keys until Clover is highlighted, press +. Press F10 and Enter. (Or follow the screens)




    - The system will now reboot, and Clover should load. Select the OS X partition and press Enter, OS X will boot.

  8. Like
    yc_richard reacted to Allan in Sleep, Hibernation - How it works? and How to use?   
    As many know, those have come from world Windows/Linux, Hibernate mode has helped a lot when we want to avoid the wear on our notebooks, besides which the system always wakes up faster, and we can still leave some open applications when we turn to the PC with all the things ready.
    The safe sleep/hibernation mode in OS X is turned on by default (on Laptops).
    Your Mac will immediately sleep when you do any of the following, regardless of your Energy Saver preference settings:
    Choose Sleep from the Apple () menu Click Sleep after pressing the power key Close the lid of a portable Mac What happens when the Mac goes to sleep (not just into idle mode or display sleep)?

    On all Macs:
    The microprocessor goes into a low-power mode Video output is turned off, and a connected display may turn off or enter its own idle state Apple-supplied hard disks spin down; third-party hard disks may spin down On portable Macs:
    The Ethernet port turns off, if applicable (see note below) Expansion card slots turn off The built-in modem, if present, turns off (see note below) An AirPort card, if present, turns off (see note below) The USB ports only responds to the power key on an external keyboard (see below) The optical media drive, if present, spins down Audio input and output turns off Keyboard illumination, if a feature of your portable computer, turns off A computer uses considerably less power when in sleep mode than when awake. The computer will continue to power RAM in sleep mode, so that whatever was in RAM when the computer went to sleep will still be there when the computer wakes. This also means that computers with more RAM use slightly more power in sleep mode.
    For Sleep/Hibernation works in Hack you will need certificate if all necessary patches is already applied in DSDT and SSDT.
    And the power management (i.e. CPUPM, GPUPM, HDD/SDD) your bootloader Chameleon/Clover are all correct, Sleep will work. 
    Hibernate 
    Now we know how sleep works, let's go for Hibernate. 
    As I said the safe sleep/hibernation mode is native only in Apple's Laptops, so if you have a Laptop this trick will be good for you.
    You can also enable Hibernation Mode for your Desktop Hackintosh, but is not so useful as it is for Laptops.
    What do you need? 
    Notes: 
    Since version 2514 the Sleep/Wake function is working. 
    Hibernate mode works natively in Legacy, but you can also use UEFI. 
    Works from OS X 10.9.1 up. (Does not work with OS X 10.9.0) 
    Don’t work with Chameleon.
    We have news that there is success in UEFI mode with OS X 10.7.5, if you work with another version, let us know if you test. 
    This guide worked for me in version 10.9.2/3/4 and OS X 10.13.x
    Let's make this method with Clover installed in the root, Legacy 
     
    1 - Last version of Clover installed - Download here. [it is recommended to do this using version 2513 or latest]
    2 - Find out which method is being using in your Hack, with this command:
    pmset -g | grep hibernatemode 3 - To Hibernate mode to operate properly, run this in Terminal:
    sudo pmset -a hibernatemode 29 4 - Put your OS X to Sleep, after 1 minute your system will shut down completely.
    5 - Press the (On/Off) power button
    6 - Now the boot screen of Clover (GUI) will appear - Note that this must be written (Hibernated)

    7 - If you put your system to start with countdown (e.g: 5 secs, 10 secs) do nothing, the system will start in Hibernate mode. 
    8 - But if you have no countdown, press ENTER on the partition that you have enabled the Hibernate. 
    9 - Now this loading screen will appear, about 10 seconds.

    And Voila! Go your login screen appears, enter your password (if any) and ready, Hibernate mode works. 
    10 - If you want to start in normal mode, or if you have a problem, check in Clover (GUI) screen and press SPACE, and select "Cancel hibernate wake." 
    But if you still have problems, run this in Terminal:
    sudo pmset -a hibernatemode 0 With this command, the Sleep mode back to native way.

     
    Let's make this method with Clover UEFI. 
    Follow steps 1-5. (Above) 
    Understand my friends to work in UEFI mode is not easy, requires several, yes several tests. 
    See an example of the user droplets (ProjectOSX forum) ,similar to mine, but with different configurations:
     
    On my machine works like this: 
    Version of Clover: 3368. 
    Lenovo G480 - OS X 10.9 /10.10 and 10.11
    Boot args used: Slide = 100 
    Hibernate: Used hibernatemode = 29
    Drivers64 UEFI: DataHubDxe-64.efi, FSInject-64.efi, HFSPlus.efi, OsxFatBinaryDrv-64.efi, EmuVariableUefi, OsxAptioFix2Drv-64.efi.
    In some cases, OsxAptioFix2Drv-64.efi or OsxAptioFixDrv-64.efi can be a problem, so remove this driver.
    But maybe someone has any doubts: Can I use these same drivers you used? 
    Answer: Yes and No, why? See when using the UEFI mode, each driver that is important for the required loading of various BIOS (Gigabyte, H20 Insyde etc...). See which combination is right for you: Choosing EFI drivers
    And these various values boot args?
    This is what you will test later.
    I've tried many values, these were the ones that have given me the best results.
    And now, how do we know if it works? 
    1 - The phrase (hibernated) must appear on the boot screen, and show the loading bar.
    2 - Let marked on your config.plist this option:

    After the system came back, go EFI> CLOVER> misc, and open the debug.log file, and check these lines:
    32:460 0:032 PrepareHibernation: 32:580 0:119 read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Success 32:597 0:017 SleepImage name from pref = \private\var\vm\sleepimage 32:613 0:015 returning previously calculated offset: 32C82A000 32:629 0:015 SleepImageOffset: 32C82A000 32:644 0:015 02 01 0C 00 D0 41 08 0A 00 00 00 00 01 01 06 00 | .....A.......... 33:180 0:535 02 1F 03 12 0A 00 00 00 00 00 00 00 04 04 18 00 | ................ 33:730 0:550 33 00 32 00 43 00 38 00 32 00 41 00 30 00 30 00 | 3.2.C.8.2.A.0.0. 34:262 0:531 30 00 00 00 7F FF 04 00 | 0....... 34:668 0:405 boot-image before: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\32C82A000 If so, congratulations your Hibernate is working.
    I can report that here everything is working perfectly. Both in UEFI as Legacy
    See the official post from Clover - Clover Instructions 
    If you encounter problems, see the official post on the hibernating mode in ProjectOSX. 
    NOTE: Many have had success using the 29 mode, but if it does not work, try using the 21 way, or another.
    sudo pmset -a hibernatemode 21 Bonus.
    A quick explanation about this commands:
    pmset -a hibernatemode 0 will save sleepimage only to RAM, this will be Sleep only.
    pmset -a hibernatemode 1 will save sleepimage only to Disk, this will be a kind of "Soft" Hibernation.
    pmset -a hibernatemode 3 will save sleepimage to RAM AND Disk, this will be Safe Sleep, first the system
    will Sleep and later Hibernate.
    pmset -a hibernatemode 25 will save sleepimage only to Disk and Remove Power from RAM and some
    more devices, this will be "Real" Hibernation.
    What commands the way that OS X will Sleep/Hibernate, is one of the commands above,
    there is no "Hibernate" option in OS X like you can see in Windows and you have to choose
    always Sleep at the "Apple" logo of your MenuBar...
    To have sure that your sleepimage isn't corrupted, run the command below...
    sudo rm -rf /private/var/vm/sleepimage A new sleepimage will be generated at the next time the system
    goes to sleep...
    All the thanks go to: Dmazar, Slice, Kyndder,  and alutam.com. 
    Bonus for Mac users:
    If you have a real Mac, and wants know how use the hibernation mode, you can read this excellent article made by Rahul Saigal.
    Note: This guide has not been tested in macOS High Sierra yet...
  9. Like
    yc_richard got a reaction from panjunwen in [Guide] 10.10 On the Surface Pro 3   
    Hi vladichimescu, thanks for the code support,
    I did all your steps and sucessfully loaded the AppleHDA288. OSX can find the device. headphone jack also switch correctly. There is sound from the sound effect in System Preferences.
     
    However, as soon as I start to play a song, the voice break down in 10s. It happens everywhere in Itunes, web musics and VLC. then there are no more sound until I restart. 10s of music limitation....
    Any idea why this happens?
     
    ps:
    - I have checked my dump which is the same as yours.
    - In dsdt, I add the DTGP method, and inject layout 3 in HDEF.
    - In CLOVER, I have fix DTGP, HPET, IPIC, SBUS. even with ForceHPET, it is the same. Anything else missing here?
  10. Like
    yc_richard reacted to Mirone in Intel HD4400 Full Qe/Ci in Yosemite 10.10.2/10.10.3   
    With the update to version Yosemite 10.10.2, some users It has a IntelHD4400 lost their Qe/Ci the steps outlined below describe how to activate these  features again.

     

             Change Log

       

                 v1.0  1/27/2015 - Yosemite 10.10.2 - Release

                 v1.1  2/10/2015 - Patched_IntelHD4400_v2.sh.zip script, added, (correction in binaries+OpenCL only)

                 v1.2  4/22/2015 - New version of script added, it is no longer necessary to edit the info.plist file with just two clicks all this done.

     

              1- Editing the info.plist.

     

                   1- To Obtain total Qe/Ci in IntelHD4400 these 3 Kexts need to be loaded, they are:

                       

                         1-AppleIntelHD5000Graphics.kext.

                         2-AppleIntelFramebufferAzul. kext.

                         3-AppleGraphicsPowerManagement. kext (AGPM).

                    

                   to make this possible we edit the info.plist file of two of them (AppleIntelHD5000Graphics. kext and AppleIntelFramebufferAzul. kext.)

                   entered our Vendor_id and device_id, which in this case is: 0x0a168086.

     

                  Click on the kext AppleIntelHD5000Graphics. kext with the mouse right  button select Show content then go to:        

                  contents/info.plist/IOKitPersonalities/IOPCIPrimaryMatch and replace 0x04128086 by 0x0a168086.

     

                  Click on the kext AppleIntelFramebufferAzul. kext. with the mouse right  button select Show content then go to:  

                  contents/info.plist/IOKitPersonalities/AppleIntelFramebufferController/IOPCIPrimaryMatch and replace 0x04128086 by 0x0a168086.

     

             2- Editing the files release binaries.

     

                  1- We need to edit the binaries of AppleIntelHD5000Graphics.kext

                      and AppleIntelFramebufferAzul kext, use Hex Fiend  and proceed as follows:

     

                  Click on the kext AppleIntelHD5000Graphics. kext with the mouse right  button select Show content then go to:        

                  contents/MacOS/AppleIntelHD5000Graphics, and open the file with Hex Fiend and proceed as follows:

                   

                       Find: 86801204

                       Replace: 8680160a

      

                 Click on the kext AppleIntelFramebufferAzul.kext with the mouse right  button select Show content then go to:        

                 contents/MacOS/AppleIntelFramebufferAzul, and open the file with Hex Fiend and proceed as follows:

     

                        Find: 86801204

                        Replace: 8680160a

     

              3- Clover patching on-the-fly

     

                      for those who use clover and don't feel

                     comfortable editing binary files can use this patch:


    KextsToPatch


    Comment
    HD4400_Full_Qe/CI_ 1
    Find

    hoASBA==

    Name
    AppleIntelFramebufferAzul
    Replace

    hoAWCg==



    Comment
    HD4400_Full_Qe/CI_ 2
    Find

    hoASBA==

    Name
    AppleIntelHD5000Graphics
    Replace

    hoAWCg==





      4- SSDT/DSDT

     

                1- It is necessary to apply a patch in your SSDT DSDT or inserting the ig-platform-id: 


    Method (_DSM, 4, NotSerialized)
    {
    If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }
    Return (Package()
    {
    "AAPL,ig-platform-id", Buffer() { 0x06, 0x00, 0x26, 0x0a },
    "hda-gfx", Buffer() { "onboard-1" },
    })
    }
    }
    }

     5- New patch for second stage apple logo glitches

              

               1- For those who like me have glitches, in the Apple logo in the second stage of boot use this patch:


    KextsToPatch


    Comment
    Second Stage patch 1
    Find

    hcB0a0g=

    Name
    IOGraphicsFamily
    Replace

    McB0W0g=



    Comment
    Second Stage patch 2
    Find

    QYjE6xE=

    Name
    IOGraphicsFamily
    Replace

    QYjE6zE=





     6- Result

     

             1- If all the steps have been followed correctly the result is a full Qe/Ci.

             

     Enjoy yourself!

  11. Like
    yc_richard reacted to LonelyTV in [Guide] 10.10 On the Surface Pro 3   
    OS X Yosemite on The Surface Pro 3
    ------------------------------------------------------
     
    I wrote this guide with a Hackintosh newbie in mind. I walk everything out step-by-step. And, know that you are following this guide at your own risk. I take no responsibility in any loss of data or broken machine. However, I'm confident that that won't happen if you are careful. 
     
    What is not working:
    WIFI
    Bluetooth
    Touchscreen : Alex.doud is currently coding touchscreen and trackpad drivers for the Surface Pro 3's i2c controller. 
    Sleep
    Trackpad gestures

    What works but is buggy:
    Graphics: QE/CI + HiDPI works with minor graphic glitches
    Audio does not play through the headphone jack
     
     
    ------------------------------------------------------
     
    Requirements
     
    Hardware:
    USB Flash Drive: 8 GB or more Access to a computer running OS X (Can be done in a virtual machine) Optional: A USB Hub, USB Keyboard, and USB Mouse (Just in case the Type Cover doesn't work during install) Software:
    OS X 10.10 Yosemite Install Application Surface Pro 3 Driver Pack.zip Clover bootloader Kext Utility  
    ------------------------------------------------------
    Step 1: Making Space for OS X
     
    Boot into Windows 8 On the Start Screen type: compmgmt.msc
    and press enter. This should open "Computer Management" on your desktop.
    Click on "Disk Management" under the "Storage" header on the left panel.
    Right click on the "Windows (C:)" block on the bottom half of the middle window and choose "Shrink Volume"
    Here you can shrink your Windows partition to make room for you OS X install. Choose a value over 15GB to give yourself room to install OS X and have storage left over.
    Optional: Right click on the new partition and rename it "OS X" (or something you will remember) -- This will make it easier to pick out in the OS X install if need be.
     
    ------------------------------------------------------
    Step 2: Creating the OS X Install USB
    This step requires access to OS X.
     
    If you already have the "Install OS X Yosemite" application in your Application folder skip down to step 2b :
     
    Step 2a: Downloading OS X Yosemite
    Open the App Store Download the OS X Yosemite installer Step 2b: Preparing the USB Drive
    Open the Disk Utility application found in the Utilities folder inside the Application Folder. Click on your USB Drive on the left panel. Choose "Erase" on the top bar Choose "Mac OS X Extended" as the Format and name the drive "Install" Once completed open the Terminal application (Also in the Utilities folder) Copy and paste this command at the prompt:
    sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/Install --applicationpath "/Applications/Install OS X Yosemite.app" --nointeraction This step takes about 30 minutes to finish.
    When it's done you will need to then install the Clover boot loader to the USB.
    Open the Clover installer found in the "Surface Pro 3 Driver Pack"
    Click Continue twice and then choose "Change Install Location"
    Choose the "Install OS X Yosemite" USB drive and press Continue
    Click "Customize". Here check:
    Install for UEFI booting only
    Themes
    Drivers64UEFI
    Click Install and wait for it to finish.
    Once it finishes you should see a new "EFI" drive mounted.
    Navigate to the "CLOVER" folder found in the "EFI" folder at root.
    Copy "config.plist" from the "Surface Pro 3 Driver Pack" here
    Navigate to the "patched" folder found in the "ACPI" folder.
    Copy the contents of "DSDT" from the "Surface Pro 3 Driver Pack" here.
    Navigate back to the "CLOVER" folder.
    Navigate to the "10.10" folder found in the "kexts" folder.
    Copy the contents of "KEXTs" from the "Surface Pro 3 Driver Pack" here.
    Your done, eject the USB drive.
    ------------------------------------------------------
    Step 3: Installing OS X Yosemite
     
    Hold the Up button of the volume rocker on the Surface Pro 3 while powering up the machine. Touch or click on "Secure Boot Control"  choose "Disabled" Touch or click on "Exit Setup" Power the machine off if it boots into Windows 8. Insert your USB drive into the USB port of the Surface Pro 3. Hold the Down button on the volume rocker on the Surface Pro 3 while powering the machine. Once Clover boots navigate to "Boot OS X Install from Install OS X Yosemite" and press space Go down to "Boot Mac OS X with Injected kexts". Wait... the installer will boot eventually. Once booted choose the Disk Utility application from either the top bar or from the window that the installer opens up to (sometimes). Here you will locate your "OS X" partition (or whatever you named it) and choose Erase like you did for the USB drive. Choose "Mac OS X Extended, Journaled" and name it whatever you want. Close the disk utility and follow the installation prompts. Several times I had the installer "finish" and reboot, but it wasn't complete. If you don't see your OS X drive in Clover after the installer reboot, re-run the installer and it will continue on it's own.
     
    ------------------------------------------------------
    Step 4: Finishing Touches
     
    Power off the machine Hold the Down button on the volume rocker to boot from the USB. Once in the Clover boot loader Navigate to "Boot Mac OS X from <OS X partition name>" Press space and go down to "Boot Mac OS X with Injected kexts". Yosemite SHOULD boot and work. If your type cover does not work on boot you will need to modify your "IOUSBFamily.kext".
     
    Step 4a: Modifying ISOUSBFamily.kext for a working Type Cover
    You can do this step on another computer with OS X or you can do it on your new install
    Open a new Finder window by clicking on the Finder icon on the dock. Click on the "Go" option in the top toolbar and choose "Computer" Double click on "Yosemite", followed by "System", then "Library", and finally "Extensions" Scroll down and find "IOUSBFamily.kext", copy it to your desktop. Rename the KEXT in your Extensions folder to "IOUSBFamily.kext.bak" Right click on the "IOUSBFamily.kext" on the desktop and choose "Show Package Contents" Double click on "Contents", and then "Plugins" Right Click on "IOUSBHIDDriver.kext"and choose "Show Package Contents" Double click on "Contents" Right click on "Info.plist", select "Open with", and choose "Other" Choose "Textedit" from the application choices. Scroll down to the bottom and locate: <key>Generic Keyboard</key> Near the bottom.
    Copy the entire section, it should look like this: <key>Generic Keyboard</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.iokit.IOUSBHIDDriver</string> <key>HIDDefaultBehavior</key> <string></string> <key>IOClass</key> <string>IOUSBHIDDriver</string> <key>IOProviderClass</key> <string>IOUSBInterface</string> <key>bInterfaceClass</key> <integer>3</integer> <key>bInterfaceProtocol</key> <integer>1</integer> <key>bInterfaceSubClass</key> <integer>1</integer> </dict> Now, paste what you copied below the first </dict> Once copied, find
    <key>bInterfaceProtocol</key> near the bottom. Change <integer>1</integer> to
    <integer>0</integer> Now, go one below to
    <key>bInterfaceSubClass</key> Change
    <integer>1</integer> to
    <integer>3</integer> your modified portion should look like this:
    <key>Generic Keyboard</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.iokit.IOUSBHIDDriver</string> <key>HIDDefaultBehavior</key> <string></string> <key>IOClass</key> <string>IOUSBHIDDriver</string> <key>IOProviderClass</key> <string>IOUSBInterface</string> <key>bInterfaceClass</key> <integer>3</integer> <key>bInterfaceProtocol</key> <integer>0</integer> <key>bInterfaceSubClass</key> <integer>3</integer> </dict> Save the document and close out all of the windows.
    Download the "Kext Utility"
    Open Kext Utility and drag the modified kext from your desktop to it
    Once KEXT utility completes, reboot your machine and you should have a working Type Cover
     
    Step 4b: Installing Clover and Booting Without a USB Stick
    Do this at your own risk. It seems that it has been hit or miss. 
    Open the Clover installer found in the "Surface Pro 3 Driver Pack"
    Click Continue twice and then choose "Change Install Location"
    Choose your Yosemite partition and press Continue
    Click "Customize". Here check:
    Install Clover in the ESP
    Themes
    Drivers64UEFI
    Click Install and wait for it to finish.
    Once it finishes you should see a new "SYSTEM" drive mounted.
    Navigate to the "CLOVER" folder found in the "EFI" folder at root.
    Copy "config.plist" from the "Surface Pro 3 Driver Pack" here
    Navigate to the "patched" folder found in the "ACPI" folder.
    Copy the contents of "DSDT" from the "Surface Pro 3 Driver Pack" here.
    Navigate back to the "CLOVER" folder.
    Navigate to the "10.10" folder found in the "kexts" folder.
    Copy the contents of "KEXTs" from the "Surface Pro 3 Driver Pack" here.
    Navigate back to the Clover Root folder and copy "CLOVERX64.EFI".
    Navigate back to the "EFI" folder and open the "Microsoft" directory.
    Then navigate to the "Boot" folder.
    Rename "bootmgfw.efi" to "bootmgfw-orig.efi"
    Paste the "CLOVERX64.EFI" into this folder.
    Rename "CLOVERX64.EFI" to "BOOTX64.EFI"
    Now, reboot. Your Surface Pro 3 should now boot into the Clover boot loader allowing you to choose if you want to boot into Windows or OS X
     
    ------------------------------------------------------
     
     
    You will need to get a USB WIFI dongle to access the internet, and a USB Bluetooth dongle to use Bluetooth. To fix SOME of the graphical glitches you can choose the color profile "sRGB IEC61966-2.1" in the Displays section of "System Preferences"
     
    ------------------------------------------------------
  12. Like
    yc_richard reacted to midi-sama in [GUIDE] Install Mavericks/Yosemite on Sony VAIO S (2012) -and other UEFI capable VAIOs-   
    Assalamo Alaikom Wa Rahmato Allahi Ta3ala Wa Barakatuh
    Installing OS X on
    Sony VAIO S
     
     
    HOT: 10.11 Install guide
    BETTER THREAD: 
    El Capitan UEFI Clover on Sony Vaio S
    BY JOHNREY

    Post #369
     
     


     
    I’ve been using this Laptop over a year! And I was trying to get OS X working on it, I failed and retried so many times until I got it (this summer ) to work 100%

    I would like to thank many users and programmers who helped me during that year, including but not limited to:

     


    (This guide MAY work with many other Sony VAIOs with UEFI support, try it Althought I do NOT support other than the model I have, I may help but use your goddam brain )
     
    MY VAIO's Specs:
     
     
    What’s working:
     
     
    Disclaimer:

    NO ONE IN THIS FORUM (INCLUDING ME) IS RESPONSIBLE FOR ANY LOSS (DATA, MATERIAL, EQUIPMENT…) OCCURRED TO YOU, YOU ARE THE ONLY ONE RESPONSIBLE, AND BY FOLLOWING THESE INSTRUCTIONS YOU AGREE TO TAKE ALL THE RISKS AND RESPONSIBILITIES. THIS INSTALLATION ISN'T WITHOUT RISKS SO TAKE ALL THE PRECAUTIONS BEFORE DOING ANY FOOLISH ACTION, BACKUP YOUR DATA! AND FEED YOUR CAT!
    Photos here are only examples, use your brain!

    Important:
    Results may differ depending on your hardware, but since we have a lot of common equipment, the difference may be little. I can’t be always active and answer your questions, and btw, I'm not a dev or coder, I’m just a guy who want to share his experience w/ people who have the same computer, and I gathered information here so you wont need to look for it. A lot of parts from this guide are taken from the original |Guide| AIO Guides For Hackintosh, but since many of you are lazy (not all, just many) I rewrote the important parts here with a slice modification for our laptops. AAAAAAAAAAAAAND
     
     
     
    What we need:
     
     
    SAVE EVERYTHING! NOT BECAUSE WE WILL FORMAT EVERYTHING BUT FOR SAFETY! (YOU MAY TRY TO PARTITION ON WINDOWS, BUT IT MAY NOT WORK TRY ANYWAY!)

    Steps:
     
     

    Fix DSDT and using SSDT!

    Remeber! NEVER EVER USE SOMEONE ELSE’S DSDT!
    AS Pavo SAYS: “It’s like using someone else’s underwear!” SO PLEASE, DO NOT USE OTHER’S DSDT!
     
     
    Fixing Audio(*) & USB Output
     
     
    Now let’s install Windows!
    (only for people who used 10) Type2: Install OS X then Windows)
     
     
    B) LAST TOUCHES B)
     
     
  13. Like
    yc_richard got a reaction from styrian in Sony VAIO S 2012 ML Success! (Ivy i5, HD 4000)   
    If you are using a laptop other than HP, you don't need to add anything, just remove the all the keys under <key>Custom PS2 Map</key>.
    To customize, have a look at this guide:
    How-to-Use-Custom-Keyboard-Mapping
     
    BTW, the battery and CPU power management is really a pain for VAIO S serie!!! I even tried a few ways by editing DSTD, but no luck.Hope someone can fix it...
  14. Like
    yc_richard got a reaction from styrian in Sony VAIO S 2012 ML Success! (Ivy i5, HD 4000)   
    If you are using a laptop other than HP, you don't need to add anything, just remove the all the keys under <key>Custom PS2 Map</key>.
    To customize, have a look at this guide:
    How-to-Use-Custom-Keyboard-Mapping
     
    BTW, the battery and CPU power management is really a pain for VAIO S serie!!! I even tried a few ways by editing DSTD, but no luck.Hope someone can fix it...
  15. Like
    yc_richard got a reaction from jimmyco2008 in Sony VAIO S 2012 ML Success! (Ivy i5, HD 4000)   
    Hey, I'm really excited to find a synaptics trackpad kext almost fully working on my SVS15!
    Just install Rehabman's new VoodooPS2controller and delete old ApplePS2Controller.kext and AppleACPIPS2Nub.kext. You also have to remove 26 customs keyboard mapping in Info.plist of VoodooPS2Keyboard.kext from his build. Because the keyboard hotkey for HP ProBook is different from sony.
    After reboot, map three-finger gestures to the functions you want by changing the assignments in the System Preferences ->Keyboard. Now both two-finger and three-finger gesture work like a charm and I can even swip between workspaces just by three-finger swiping left/right.
     
    PS: anyone have a working battery kext plz?
×