Jump to content
TimeWalker75a

OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover

1,148 posts in this topic

Recommended Posts

I believe that these tables are set up for me 14R. I do not understand why the graphics card not being disabled because the method is already implemented in SSDT-2 Scope (\ _SB.PCI0.PEG0). SSDT-3 I extracted the script Revogirl. Actually I had not put this method before and now put, and now my audio and wifi does not work. One detail that is present now in the ioreg GFX0, Please find attached files.

Are you serious? I've looked at ACPI tables injected in your IOREG and you were using SSDT-2 from Vosotro, because it lacks PEG0 scope and has Fresco Logic model for XHCI controller. Your config is not being loaded because none of the patches are bing applied from Clover. When providing dumps intend to use DarwinDumper instead, as it provides complete information about the system as well as most needed logs. I can't tell much based on just ACPI tables and IOREG.

 

Can you explain what is the role of PtidTabl? Should we really drop it?

It's a universal monitoring device on mobile and desktop platforms. kozlek's ACPISensors plugin can read data from it. The thing with these two machines as well as XPS 15/15z/17 and Vostro 3750 is that kozlek's plugin will pick the table and populate sensors with it, but the table actually doesn't work as there is no device H_EC to which grand majority of sensors are referring.. so only DTS1 and DTS2 sensors are being properly picked up, but we already monitor these.

Share this post


Link to post
Share on other sites
Advertisement

0:100  0:000  Clover revision: 1989  running on Dell System Inspiron N4110
0:100  0:000  ... with board 0WVPMX

So your board is 0WVPMX and not a 03NKW8 as @Zprood's 14R has. Probably part number differs because you've got different AMD graphics.

But revision 1989, seriously? With a config file from revision 2k ? The config files are COMPLETELY different for pre 2k and post 2k Clover.. so what do you expect anyway? We are at revision 2269 already, you are 280 revisions behind.

 

So this means you have again used some files from God knows where.. and not from the files I've included in this guide.

Share this post


Link to post
Share on other sites

So friends, let's start from scratch and make the appropriate settings according to this notebook. I will update the clover to latest version and then?

Share this post


Link to post
Share on other sites

And then post #5 of this thread is there to provide you with most necessary files that you need. Make sure to rename the OEM folder from 03NKW8 to 0WVPMX as your part number for motherboard is different. 

Share this post


Link to post
Share on other sites

See, its much easier when you actually follow directions ;)

Everything seems to be in order now, patches are getting applied... . but you still missed a chunk, you haven't changed ROM, MLB, BoardSerialNumber or actual SerialNumber inside the config file... 

 

There's just one thing that will be missing for you after you fix the serials - HDMI audio, but it's a Clover bug at this point, even if you use latest revision hda-gfx won't be properly set to onboard-1 on IGPU, so HDMI won't pass any audio on AMD based machines. And you can't do anything to SSDT or DSDT either, because SgRef table already has _DSM on IGPU with no way of dropping it without getting a kernel panic. 

 

P.S. Uninstall GenericXHCI and update your kernelcache.

Share this post


Link to post
Share on other sites

Really tested here and not have HDMI audio working, the Zprood does not work?

I think, that you have to patch the port for HDMI of your installed AppleIntelSNBGraphicsFB.kext.

 

On my EDGE E320 with AMD 6630m and HD3000 I have done the following steps and got HDMI with audio working:

 

DSDT.aml:

 

In section HDEF:

 

            Method (_DSM, 4, NotSerialized)

            {

                Store (Package (0x16)

                    {

                        "codec-id",

                        Buffer (0x04)

                        {

                            0x6E, 0x50, 0xF1, 0x14

                        },

 

                        "hda-gfx",

                        Buffer (0x0A)

                        {

                            "onboard-2"

                        },

 

                        "AAPL,slot-name",

                        Buffer (0x09)

                        {

                            "Built In"

                        },

 

                        "layout-id",

                        Buffer (0x04)

                        {

                            0x0C, 0x00, 0x00, 0x00

                        },

 

                        "model",

                        Buffer (0x1A)

                        {

                            "HD Audio Conexant Cx20590"

                        },

 

                        "name",

                        Buffer (0x11)

                        {

                            "Conexant Cx20590"

                        },

 

                        "location",

                        Buffer (0x02)

                        {

                            "3"

                        },

 

                        "subsystem-id",

                        Buffer (0x04)

                        {

                            0x0C, 0x00, 0x00, 0x00

                        },

 

                        "subsystem-vendor-id",

                        Buffer (0x04)

                        {

                            0x58, 0x14, 0x00, 0x00

                        },

 

                        "device_type",

                        Buffer (0x09)

                        {

                            "HD audio"

                        },

 

                        "PinConfigurations",

                        Buffer (Zero) {}

                    }, Local0)

                DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))

                Return (Local0)

            }

        }

 

 

 

Read marked lines are neccessary if not injected or activated by bootloader.

 

 In GFX0 (IGPU) the following DSM method right after:

            Name (_ADR, 0x00020000)

 

 

 

            Method (_DSM, 4, NotSerialized)

            {

                Store (Package (0x06)

                    {

                        "AAPL,snb-platform-id",

                        Buffer (0x04)

                        {

                            0x00, 0x00, 0x01, 0x00

                        },

 

                        "hda-gfx",

                        Buffer (0x0A)

                        {

                            "onboard-2"

                        },

 

                        "device-id",

                        Buffer (0x04)

                        {

                            0x26, 0x01, 0x00, 0x00

                        }

                    }, Local0)

                DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))

                Return (Local0)

            }

 

I have also patched the blue marked line for HDMI port of AppleIntelSNBGraphicsFB from

 

0000000: 0102 0400 1007 0000 1007 0000  ............

000000c: 0503 0000 0200 0000 3000 0000  ........0...

0000018: 0205 0000 0004 0000 0700 0000  ............

0000024: 0304 0000 0004 0000 0900 0000  ............

0000030: 0406 0000 0004 0000 0900 0000  ............

 

to

 

0000000: 0102 0300 1007 0000 1007 0000  ............

000000c: 0100 0000 0200 0000 3000 0000  ........0...

0000018: 0205 0000 0008 0000 0600 0000  ............

0000024: 0602 0000 1000 0000 0900 0000  ............

0000030: 0000 0000 0004 0000 0900 0000  ............

 

The green marked lines are for working VGA port on my e320. (Last port set to zero, because it is does not exist on e320 and caused gfx-glitches)

 

For doing the hex edit you can use a hex editor or just run the attached script of modigliani (olarila.com).

 

I hope this can help you to solve your problem with hdmi audio.

 

Have fun.

 

 

 

 

 

 

modigliani-intelhd3000Patch-v4-ML.zip

Share this post


Link to post
Share on other sites

Really tested here and not have HDMI audio working, the Zprood does not work?

post-459659-0-42302400-1383358523_thumb.png

you can see what's going on hdmi audio, i haven't a device to test whether it works or not. but basically it should work. 

 

<6f 6e 62 6f 61 72 64 2d 31> means "<onboard-1>"

Share this post


Link to post
Share on other sites

I think, that you have to patch the port for HDMI of your installed AppleIntelSNBGraphicsFB.kext.

 

On my EDGE E320 with AMD 6630m and HD3000 I have done the following steps and got HDMI with audio working:

 

DSDT.aml

 

Please don't mislead people in this guide. The connectors are already being properly patched. I've also described the situation with _DSM on GFX0 twice in my last two post, so if you don't full understand the concept of ACPI and what happens when you have two DSM methods on same device across two ACPI tables I suggest you try yourself... also, this guide doesn't need you to have a prepatched dsdt, so there goes misleading again.

 

@Zprood, it's a bug in clover, it should be MacRoman and say onboard-1, but it doesn't.. a lot of people have noticed it doesn't actually allow hdmi audio to pass through.

Share this post


Link to post
Share on other sites

@TW, thanks explain, i'd talk about candy HDD more, i have two partitions mounted when login system, when reboot system, candy power shutdown, it happens when candy HDD is in using, so i edit fstab to unmount the partitions of HDD, then when i reboot, the power shutdown sound won't appears any more. 

Share this post


Link to post
Share on other sites

Sure, go ahead and document fstab if you know configuring it can solve the immediate power down of the caddy across restarts.

Only thing is, my OSX installation is on that HDD caddy, and my main drive has Windows 8.1 installed on it, both main drive partitions are unmounted at login with an app created with automator. 

Share this post


Link to post
Share on other sites

yeah, i use this way to prevent hfs/ntfs partition mount when it boots.

UUID=EA58E9CF-4C8F-39F9-94E9-570DAD1733CC none hfs rw,noauto

Share this post


Link to post
Share on other sites

hi TimeWalker75a

 

i need from you small help on activating iMessages through calling Apple care ?

 

can you help me on this ?

about iMessage, if you use clover you should add two options  under "RtVariables"

MLB > "SerialNumber"+ five digital

ROM > your network MAC address

 

one more thing, if your account doesn't activated in iso device or real mac, you should add a credit card to it, then change your password of account, then problem solved. 

Share this post


Link to post
Share on other sites

about iMessage, if you use clover you should add two options  under "RtVariables"

one more thing, if your account doesn't activated in iso device or real mac, you should add a credit card to it, then change your password of account, then problem solved. 

didn't used my account on any idevice or mac 

want to try first call apple care as a try before add credit card 

tried to call but can't deal with them as they speak rapidly so can't understand them english :)

 

hope that someone help me on this :)

 

 

Share this post


Link to post
Share on other sites
Hey,

 

I'm really new to all this Hackintosh stuff and don't know or understand many things (but I'm trying, yeah) about different kinds of DSDTs and so on. I'm trying to apply this guide to my Vostro 3750 having almost the same motherboard (as mentioned in this thread) but can't even run the Installer. I've patched my BIOS, now it's fully UEFI compatible with a bunch of the needed options unlocked, I've copied the prepared Clover stuff only modifying the motherboard ID from 3450s to 3750s in the appropriate folder name (inside the OEM folder). Sooo... Clover runs without GUI (I don't know if it should), OS X Installer boot process stucks on the following error: p-state stepper error 18 at step 35 — unfortunately, I don't even understand WTF is that.

 

I would really appreciate any possible help.

Thanks.

Share this post


Link to post
Share on other sites

@sky-lo-fi, you can't just use his patches for you until you know how these patches work. i see you have 1600x900 resolution display, and TW has 1366x768.

Share this post


Link to post
Share on other sites

@sky-lo-fi, you can't just use his patches for you until you know how these patches work. i see you have 1600x900 resolution display, and TW has 1366x768.

 

Yes, I understand that. But 1) I should start with something and want to get help not just to fix everything (like "guys, go and make a working image for my laptop while I'm drinking coffee" - never this way) but also to understand it, however there is so much information, etc. that I don't know where to look at first; 2) in this case I prefer to go in a backward direction and to use the patches and then fix what doesn't work, because this guide is made for the closest model to my lappy I've found on the Web.

Share this post


Link to post
Share on other sites

as i suggest that you can make it install successfully, then apply this patches to you. because you have much things to learn and understand. 

about GUI, TW set text only mod, so you won't see it. And you have a different CPU compare with TW, i need delete SSDT-2.aml from patched folder, and i modify a config.plist to you, replace it. config.plist.zip

Share this post


Link to post
Share on other sites

as i suggest that you can make it install successfully, then apply this patches to you. because you have much things to learn and understand. 

about GUI, TW set text only mod, so you won't see it. And you have a different CPU compare with TW, i need delete SSDT-2.aml from patched folder, and i modify a config.plist to you, replace it. attachicon.gifconfig.plist.zip

Thank you. Done what you said. But now I'm having a "USBMSC identifier (non-unique) [blah-blah...] Still waiting for root device" issue. I can see USB Injection is turned on. BTW when I try ncpi=0x3000 or 2000 (read somewhere that this can help solve this problem) nothing changes, but after enabling P-States and C-States generation, it passes a "USBMSC..." string, goes far and finally gives the same P-State Stepper error just like before.

Share this post


Link to post
Share on other sites
ncpi=0x3000 or 2000

there is no need to use it. what's kind install media you are using ? 

Still waiting for root device

 

it means mac doesn't find a boot device, i suggest that you should use a simple way to install mac, like chameleon, then switch to clover. 

EDIT:

1. make a install media, put Fakesmc.kext and Voodoops2controller in the S/L/E.

2. copy smbios.plist which is define macbook pro 8.1, put it in the Extra/

3. edit org.chameleon.boot.plist, add DualLink=1 to it. 

then boot and install.

Share this post


Link to post
Share on other sites
ncpi=0x3000 or 2000

there is no need to use it. what's kind install media you are using ? 

it means mac doesn't find a boot device, i suggest that you should use a simple way to install mac, like chameleon, then switch to clover. 

 

I'm using a USB stick for Clover and a USB HDD for Installer. Going to install it to an internal SATA HDD.

Yes, I know the meaning of this string, but you see it RUNS through it and continues booting until the P-State Stepper error message when C-States and P-States generation is turned on, so it looks like the media is not a real problem. As for npci I've already realized there's no need to use it.

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 rtke333
      Acer Aspire V15 V5-591G - Mojave 10.14.4
       
      (Note: mine is 55TU version, but the bootpack will work fine with another versions of 591G, for example: V5-591G-71K2, -764Z, -59PU, etc.)
      Specifications:
      - Motherboard: USOPP_SLS (Skylake-H PCH)
      - BIOS:Insyde Corp. v 1.15
      - CPU:Intel Core i5-6300HQ 2.3 GHz (Skylake)
      - GPU: NVIDIA GeForce GTX 950M 2 GB (Optimus) & Intel HD Graphics 530
      - RAM:SK hynix 4 GB DDR4 (Later I bought + KINGSTON 4 GB) 2133 MHz
      - WiFi + Bluetooth:Qualcomm Atheros QCNFA344A 5 GHz (Later -> Broadcom BRCM94352Z M.2 5 GHz WiFi + 4.0 Bluetooth)
      - Audio:Realtek HD Audio: ALC 255 
      - Ethernet: Realtek RTL8168/8111
      - Card Reader:Realtek USB 2.0 Card Reader (USB2.0-CRW)
      - Webcam:HD Webcam
      - HDD:TOSHIBA MQ01ACF032 320 GB HDD
      - SSD:SPCC M.2 230 GB SSD
      - Display:1366x768 (15.6", Matte)
      - Battery: 6 cell 56Wh / 5040mAh
      - Connectors: 
      1x SD Card Reader 2x USB 3.0 (1x USB Charging), 1x USB 2.0 1x VGA 1x HDMI 1x 3.5mm microphone/audio combined jack connector 1x Ethernet (Rj-45) - Keyboard & Touchpad:Multi-Touch & Multi-gestures ELAN 501 Touchpad, Backlight Keyboard.
      Working:  
      - Wi-Fi (with BCM94352Z)
      - Bluetooth hand-off (With BCM94352Z)
      -Full Graphics enabled on HD 530: ig-platform-id: 0x191b0000 (HD 530 Mobile)
      - Display: if default colour profile is corrupted (blue is not actual blue but purplish) Use "Rec. ITU-R BT. 709-5" Color Profile (System Pref. -> Displays -> Color)
      -HDMI & VGA Outputs: AppleGraphicsDevicePolicy.kext Clover patch
      - Audio (ALC 255):(Internal Speakers, Internal Microphone, Headphone jack with AppleALC, ALCPlugFix -> layout-id=17)
      - Ethernet Realtek 8168/8111: RealtekRTL8111.kext
      - App Store, Messages, FaceTime, Siri, iCloud(native)
      - Integrated webcam(native)
      - 3.0 USB (native)
      - Touchpad and Keyboard(ELAN501): Fn keys are good, the weird thing is the Brightness key. On my keyboard it's Pause Break:Br-up, Fn+F12:Br-dwn-> To fix this try Karabiner (VoodoPS2Controller.kext), - for gestures try SmartTouchpad drivers
      - Battery info:Install ACPIBatteryManager.kext with Kext Utility or other installer.
      - Sleep Mode
      - SSD with TRIM enabled (to enable trim, open Terminal and write "sudo trimforce enable")
      Not working:
      - Original Wi-Fi (Qualcomm Atheros QCNFA344A):  unsupported, you need switch to BCM94352Z or just use a mini usb wifi dongle.
      - NVIDIA GeForce GTX 950M: Optimus not supported.
      - Card Reader: Unsupported -> Can't really fix because I don't have any SD Card at the moment, maybe can be fixed by adding Prod & Ven IDs to AppleStorageDevices.kext, I never used it anyway. name: "USB2.0-CRW" Prod ID: "0x0129" Ven ID: "0x0bda  (Realtek Semiconductor Corp.)"
      For Wi-Fi:
      - 1st method:You can choose an external USB wifi dongle (I used TP-Link Archer T1U (5GHz support), TP-Link has official macOS drivers, you just need to install it
      -2nd and I think the best method:Replace your M.2 Qualcomm Card with a compatible BCM94352Zcard (you will have hand-off Bluetooth too), just install the kexts (enabled with BrcmFirmwareData.kext, BrcmPatchRAM2.kext, FakePCIID.kext, FakePCIID_Broadcom_WiFi.kext, they're all in my attached zip). You could buy this card from ebay, aliexpress, or amazon
       
      Issues:
      - None
      BIOS Settings:
      - BIOS version 1.15 (irrelevant)
      - Secure Boot: Disabled
      - Touchpad: Advanced
      - Boot mode:UEFI
      Getting ready for Installation:
      - Download the install zip (bootpack & postinstall): Click here -> acer_aspire_v591g_installfiles.zip
      Installation:
      - Create an installer with any method you know (- Mac: createinstallmedia - Windows: Transmac, Vmware, Win32diskimager)
      - Copy my Clover folder to the USB's EFI folder
      - Boot with the Installer USB
      - If you stuck in boot, reboot and in the Clover bootloader select "config_debug.cfg" -> you'll have more informations about the freeze
       
      Please open the README.rtf in my install zip for more informations about the USB Installer & Post installation!
      If you have a single RAM and getting panic at boot, then you need to edit the "config.plist" with these (SMBIOS->after "Version 1.0"):
      ->Edit "Frequency" and "Size" to match your RAM values
      <key>Version</key> <string>1.0</string> <key>Memory</key> <dict> <key>Channels</key> <integer>1</integer> <key>SlotCount</key> <integer>1</integer> <key>Modules</key> <array> <dict> <key>Slot</key> <integer>0</integer> <key>Size</key> <integer>8192</integer> <key>Frequency</key> <integer>2133</integer> <key>Type</key> <string>DDR4</string> </dict> </array> </dict> </dict>  
      PowerManagement  fix:
      Set HWPEnable=YES in Clover (already set), CPUFloor to "700", Frequency to "2300" and "3200"(Normal and Turbo, if you have i7-6700HQ version then it should be "2600", "3500") and "FrequencyVectors" from "0x0d000000" to "0x07000000" in "S/L/E/IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext/Contents/Resources/Mac-A5C67F76ED83108C.plist", MSR _xcpm_idle Patch to KernelToPatch in Clover (If you have High Sierra, change "MatchOS" to 10.13):

      <key>KernelToPatch</key> <array> <dict> <key>Comment</key> <string>MSR 0xE2 _xcpm_idle instant reboot(c) Pike R. Alpha</string> <key>Disabled</key> <false/> <key>Find</key> <data> ILniAAAADzA= </data> <key>MatchOS</key> <string>10.14</string> <key>Replace</key> <data> ILniAAAAkJA= </data> </dict> </array> Reboot, and it's 800MHz in idle state, same on Windows.
       

       
      Before updating to a new version of Mojave please update kexts (and clover if necessary) to newer versions to avoid kernel panics.
      Generate a serial number with Clover Configurator.app (open up your config.plist with CC then -> SMBIOS -> Serial Number -> Generate New)
      Mojave & Windows 10 Dual-Boot:
      Dual-boot clean install (on one drive), UEFI Only:
       
       Boot into your Mac installer, Create 2 partitions in GUID table (1 for Win (I used FAT32 but I think it doesn't matter what you choose), 1 for Mac),   Install Mac, boot with your USB, mount your EFI partition (use terminal or an EFI mounter app), create an EFI folder (if there is no folder), copy the CLOVER folder I attached to the EFI folder, restart,  Boot into your Win installer, Format the partition you created for Win, install.   Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type:  bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi       5.  You're done! It will booting into Clover when you start the system, and you can select Win or Mac (or another OS if installed on a 3rd partition).
       
      Dual-boot with Windows installed first (on one drive), UEFI Only:
      If you already have Windows and you don't want to lose all your data there is a hope:
      I created a video from this restore method: [Hackintosh] Dual-Boot High Sierra & Windows - when Windows already installed - no data waste - UEFI
      You need bootable Mac Installer and a full system restore image (link is in my video's description).
      (You may see errors if your EFI partition is not 200 MB)
       Boot into your Windows, resize your partition or create one for Mac.  Boot into your Mac installer and in Disk Utility format the partition you created.  Restore from image: select your full system restore image.  When it's finished restoring you just need to restart, then boot to the system with your usb.  When you successfully booted to Mac desktop, mount your EFI partition (use terminal or an EFI mounter app), open EFI, you will see there is a Microsoft folder already (don't touch that!). Copy my CLOVER folder to the EFI folder then Restart.  Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type:  bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi       7.  You're done! You can select your old Windows and your new macOS!
      (Only tried with Windows 8/8.1/10. I don't know Windows 7,etc.)
       
      IF YOU GETTING ERRORS DURING MAC RESTORE:
      - Make sure you have partitions in GPT
      - Windows using 100 MB EFI and will annoy the Mac restore. Don't worry, just ignore the errors.
       
      IF YOU GETTING ERRORS DURING WINDOWS INSTALLATION (could not be formatted, etc):
      - Make sure you have GPT partitions, and GPT (UEFI) installer, also disconnect all external storage drives (except the installer USB)
       
      IF YOU USED RESTORE METHOD THEN CAN'T MOUNT YOUR EFI PARTITION (No EFI partition found):
      - It's because your EFI is not 200 MB or not an "Apple" original EFI,  but do not worry, try another EFI mounter, or mount from terminal (I used EFI mounter v3: Getting errors, but you can mount and use without problem)
      - You also could "mount" the EFI from Windows:
      1st method: open cmd in administrator mode and type:
      diskpart
      list vol (Now select the "System" volume,(FAT 32) For example I select 4)
      sel vol 4
      list part(Select System type partition, for example 2)
      sel part 2
      assign letter=b(This will "mount" your EFI partition)
      Open Explorer++ or TotalCommander in administrator mode to manage EFI
      remove letter=b (This will "unmount" your EFI)
      2nd method: open cmd in administrator mode and type:
      mountvol b: /s (This will mount your EFI)
      Open Explorer++ or TotalCommander in administrator mode to manage EFI
      mountvol b: /d (This will unmount your EFI)
      Thanks to all OSXLatitude members for helping me out! (Jake Lo, Hervé, Bronxteck, black.dragon74)!
      Notes:
      2019.03.30: Fixed USB 3.0 ports, fixed Bluetooth crashes after sleep -> updated bootpack
      2019.03.28: Updated to 10.14.4. Unexpected crashes while updating to 10.14.4 -> fixed by updating Clover to the latest (v4910) version. Bluetooth crashes appeared -> fixed by downgraded Brcm*.kexts. Updated bootpack.
      2019.02.24: Bluetooth crashes after sleep -> fixed, updated bootpack. 
      2019.02.22: Updated to 10.14.3. Fixed HDMI Audio by installing "FakePCIID_Intel_HDMI_Audio.kext" -> fixed freezing during boot. Fixed brightness levels by installing "AppleBacklightFixup.kext". Also updated bootpack & postinstall zip down in attachments.
      2019.01.21: Removed FakeSMC.kext, SMCHelper-64.efi, replaced by VirtualSMC.kext, VirtualSMC.efi because I got random freezes when booting system (kextd stall[0], (120s): 'AppleACPICPU' -> CPU is at 100%, fans are spinning fast), also updated bootpack in the attachments "acer_aspire_v591g-55tu_clover.zip"-> Freeze continued, brought back FakeSMC, deleted VirtualSMC (caused BT crashes).
      2019.01.18: HDMI Audio is fixed, I didn't do anything HDMI Audio is not fixed, sometimes it worked but most likely not. (no idea why)
      2018.12.09: Updated to 10.14.2 -> did without any complication
      2018.11.28: Fixed combo-jack garbage sound output by installing ALCPlugFix and CodecCommander.kext
      2018.11.01: Updated to 10.14.1 -> HDMI & VGA ports are gone again. -> Fixed by "AppleIntelSKLGraphicsFramebuffer.kext" rollback from 10.14.
      2018.09.28: Updated to Mojave 10.14 -> Fixed HDMI & VGA Outputs by adding "AppleGraphicsDevicePolicy.kext" patches to config.plist, HDMI audio not working
    • By ciriousjoker
      TLDR:
      I'm trying to boot MacOS on a Chromebook without UEFI. I'm stuck at getting the bootloader (Chameleon/Clover) to work.  
      My setup / context:
      I have an Acer Chromebook Spin 13.
      Available ports:
      2 x USB-C 1 x USB-A 3.0 MicroSD Slot No USB A 2.0 (I've read that Clover has problems with USB 3.0) Firmware:
      There's no UEFI firmware available and by default, it doesn't even allow booting anything other than ChromeOS. Thanks to MrChromebox (big shoutouts!), I flashed a custom legacy bios that allows me to boot anything linux related. This bios is flashed into the RW_LEGACY section of the existing bootloader (coreboot afaik) and doesn't have any configuration options. If I have to change a setting, I could try compiling his bios payload myself with the specific setting enabled.  
      What I've tried so far:
      Chameleon attempts:
      Only selected setting was "Install chameleon on the chosen path", rest was unselected.
       
      1 - Install chameleon first without restoring the basesystem:
      Output:
      > boot0: GPT
      > boot0: done
      (hangs; pressing power button once shuts down
      Chameleon installation log is attached as "Chameleon_Installer_Log_BEFORE".
       
      2 - Install Chameleon after restoring the base system:
      Output:
      > boot0: GPT
      > boot0: GPT
      > boot0: doneboot1: /boot       <- Exactly like that, no line break in between
      (hangs; pressing power button once shuts down)
       
      I haven't been able to reproduce #2 after wiping the drive and doing the same thing again. Subsequent attempts have resulted in either #1 of either Chameleon or Clover.
      Chameleon installation log is attached as "Chameleon_Installer_Log_AFTER".
       
      Clover attempts:
      I tried multiple settings and configurations, but all of them boiled down to either one of these.
       
      1 - Doesn't do anything, just hangs at "Booting from usb..."
      2 - Boots into the blue/grey mode as shown in the attached images.
      According to MrChromebox, this could be an old Tianocore DUET It doesn't detect anything (cpu frequency, ram, partitions or disks)  
      I've read pretty much every article, github readme and other types of documentation for coreboot, tianocore, clover, chameleon and MrChromebox' rw_legacy payloads and right now, I'm totally clueless as to what to try next...
       
      A few questions that came up:
      Why does chameleon hang? What is it looking for, /boot was clearly written to the disk by the Chameleon installer? What exactly is the blue/grey image? According to MrChromebox, it could be Tianocore DUET Where does it come from? Clover? The mainboard itself? Why does the blue/grey thing not detect my processor frequency or any partitions/drives? Can I use some sort of DUET bootloader to chainload Clover?  
      If you guys could answer any of them or if you have any other guesses or information as to what's happening, I'd be really happy!
      Chameleon_Installer_Log_BEFORE.txt
      Chameleon_Installer_Log_AFTER.txt





    • By outdoormagic
      Short Version:
      I have two drives with the exact same EFI folder (and I can boot into Clover from either one), shouldn't I be able to boot into MacOS from either one?
       
      More Detail:
      I've done a few hacks so far and this never happened. (Gigabyte z370 / 8700k / Vega, Asus z390 / i5-9600k / 1080). Now, I'm setting up a ThinkPad X1 Gen 6. (Yes, I do expect problems on laptops, but that's not the question).
       
      Mojave 10.14.4 now boots from the internal SSD. So far, so good. Here's the problem.
       
      I installed Mojave on a USB drive (for backup / rescue) and copied the entire EFI partition of my boot drive to the EFI partition on the USB drive. So... I should be able to boot from the USB drive, right? Wrong. Ran Clover installer on the USB itself. Same outcome.
       
      With F12, I can boot from the USB into Clover and select the OS on the USB. The boot sequence hangs on End Random Seed, but before the usual '++++++++' line.
      So, boot into Clover on internal boot drive, then select OS on USB. Same thing.
       
      Read the forums, I saw the posts about AptioMemoryFix, so I tried the various other drivers on the USB. No go.
       
      I haven't found the solution yet to the USB boot issue, but what puzzles me is that if I have two drives with the exact same EFI folder (and I can boot into Clover from either one), shouldn't I be able to boot into MacOS from either one?
       
       
    • By fusion71au
      Clover r4914 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.14 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4914 for VMware.zip". Mount Clover-v2.4k-4914-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  AptioMemory --> (consigliato) 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
       
      *Nota: Altri driver che si possono usare  al suo posto  sono:
       informazioni 
       
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione, nel caso può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip





       

×