Jump to content
Kogen Mantis

Lenovo ThinkPad T420 with UEFI Only

4,393 posts in this topic

Recommended Posts

well it seems that mcdonnelltech leveraged the same files from this guide - DSDT and kext pack - so its pretty much the same thing as here.

 

if you already have a disk with OSX - you could just clone it to the drive on your X220 - then all you do is add the ESP and custom kexts.

Share this post


Link to post
Share on other sites
Advertisement

well it seems that mcdonnelltech leveraged the same files from this guide - DSDT and kext pack - so its pretty much the same thing as here.

 

if you already have a disk with OSX - you could just clone it to the drive on your X220 - then all you do is add the ESP and custom kexts.

Thank you so much for your time, tluck. I came to the same conclusion and I will try that firstable. Already cloned my Yosemite installation, as I use to do when changing mac´s. When X220 arrived i will begin the "experiment"

 

 

    Much appreciated 

Share this post


Link to post
Share on other sites

Hi all.. First post... :-)

I got a bit annoyed about the bios fan controller..

It seemed to stay at 3500 rpm even if temperature was low and it seemed to run the cpu a little hot when under load load for a long time.

 

Found this post on the thinkpad forum.: http://forum.thinkpads.com/viewtopic.php?f=32&t=91141#p607951
 

After adding the patch to the dsl and compiling, the fan control is perfect.(Just make sure hwmonitor is running and started at login as it poll the TCPU)

Low load is 55C and fan at 1950 rpm and almost silent.

High load is 80-85C and fan about 4500 rpm (was 90-92C before)

 

My install is just a default install following the guide(Thanks!! tluck)
Used a decompile of the existing aml because I had problems compiling the dsl included in the guide.

And in the dsl I just merged the thinkpad forum change.

 

WARNING!! It is important to run hwmonitor with 'continue to monitor sensors in background' or similar that query TCPU in intervals otherwise the fan will not be controlled.

 

The best solution would be to find a method that is called in intervals by the OS. (Could be battery status?) 

 

Does this solution make sense to you good people here and do you have a suggestion to a method polled by the OS we could use to 'ping' TCPU in intervals to ensure the controller code is keeping the temperature correct? 

 

 

The modification ended up like this:
Method (TCPU, 0, NotSerialized) 

{                   

    Store (^^EC.TMP0, Local0)

    /* FAN control START */

    Store (\_SB.PCI0.LPC.EC.TMP0, Local0)

    If (LLessEqual (Local0, 0x32))  // CPU Temp is <= 50C 

    {   

        Store (Zero, \_SB.PCI0.LPC.EC.HFSP) // Set FAN Off 

    }   

    If (LGreaterEqual (Local0, 0x55)) // CPU Temp is >= 85C 

    {   

        Store (0x40, \_SB.PCI0.LPC.EC.HFSP) // Set FAN Mode Disengaged - Total Maximum 

    }   

    Else {

        If (LGreaterEqual (Local0, 0x4B)) // CPU Temp is >= 75C

        {       

            Store (0x07, \_SB.PCI0.LPC.EC.HFSP) // Set FAN Mode 7 - Maximum Speed

        }       

        Else {  

            If (LGreaterEqual (Local0, 0x46)) // CPU Temp is >= 70C

            {           

                Store (0x04, \_SB.PCI0.LPC.EC.HFSP) // Set FAN Mode 4 - Medium Speed

            }           

            Else {      

                If (LGreaterEqual (Local0, 0x41)) // CPU Temp is >= 65C

                {               

                    Store (0x02, \_SB.PCI0.LPC.EC.HFSP) // Set FAN Mode 2

                }               

                Else {          

                    If (LGreaterEqual (Local0, 0x3D)) // CPU Temp is >= 61C

                    {                   

                        Store (0x01, \_SB.PCI0.LPC.EC.HFSP) // Set FAN Mode 1 - Lowest Speed

                    }                   

                }               

            }           

        }       

    } /* FAN control END */

    Return (Local0)

}

Share this post


Link to post
Share on other sites

@mikaeir - welcome to the forum!

 

well thats a pretty cool solution! RehabMan wrote an ACPI poller that should do the trick ...see https://github.com/RehabMan/OS-X-ACPI-Poller

 

Great.. It did just that. Only needed to adjust the info.plist to match the t420 and use TCPU as poll method. 

 

                        <key>IONameMatch</key>

                        <string>MON0000</string>  <!-- Was FAN00000 -->

                        <key>IOProviderClass</key>

                        <string>IOACPIPlatformDevice</string>

                        <key>Methods</key>

                        <array>

                                <string>TCPU</string> <!-- Was FCPU -->

                        </array>

Loaded the kext and it is now making sure the fan controller logic is polled even if hwmonitor is stopped.

Share this post


Link to post
Share on other sites

tluck pack also work on x220

 

I'm really tempted to get an x220t right now to Hackintosh.

 

I wonder if the tablet (the pen, more importantly) would work? It seems that some people have it working, but I am having trouble finding any recent info.

Share this post


Link to post
Share on other sites

tluck, installation completed. Thank you so much for everything. In fact, i Cloned de Hard Drive, replaced, and only changed two or three files.

It works like a charm

 

Of course, not even by far can compare to the esata, bay for another drive, etc….

 

The display is not as good as that in the T420

 

 

But its so so much portable.

 

 

Really is what need now, fits in my bag as the MBA i had.

 

One curious thing….. it´s the first IBM/Lenovo that i see that close without hinches. Just the magneto.

So i have a T420, HD display, 8GB ram.Wifi and bluetooth just in case anyone is interested...

 

No hard drive, just DVD. And a 9cell original battery i have just bought


I'm really tempted to get an x220t right now to Hackintosh.

 

I wonder if the tablet (the pen, more importantly) would work? It seems that some people have it working, but I am having trouble finding any recent info.

I was not so enthusiastic …till arrived yasterday...

 

Same keyboard, display is perfect in size, nice piece of hardware.

 

 

An just 125 euros

Share this post


Link to post
Share on other sites

Gents,

 

Maybe a little different topic but anyway it is also related with all the stuff we are doing here (if anyone would like to have possibility of use the original lenovo recovery image).

So this is the problem that when I've created lenovo recovery image on the usb key then I can't boot from it... I've tried many many different bios options and and I'm sure that my USB lenovo recovery is prepared ok because I can boot from it my other laptop (dell inspiron).

If I create recovery image but on usb disk drive then it is booting ok... but why it can't boot from usb key and exactly on my T420?

Share this post


Link to post
Share on other sites

Hi guys-

I got a new T450 at work. Anyone has installed OS X on this model or has any tips?

 

Thanks,

AJ

 

PS: My T420 is of course doing great with El Capitan thanks to this thread.

Share this post


Link to post
Share on other sites

@gpspl -

 

is this on a T420? are you using the DSDT from the zip? if so there is logic in the _WAK Device to set the LED depending on sleep mode.

Still don't know where to look in _WAK method :\

 

here is my _WAK, can you tell me where and what patch should i make.

Method (_WAK, 1, NotSerialized)
    {
        Store (Zero, SPS)
        Store (Zero, \_SB.PCI0.LPC.EC.HCMU)
        \_SB.PCI0.LPC.EC.EVNT (One)
        \_SB.PCI0.LPC.EC.HKEY.MHKE (One)
        \_SB.PCI0.LPC.EC.FNST ()
        UCMS (0x0D)
        Store (Zero, LIDB)
        If (LEqual (Arg0, One))
        {
            Store (\_SB.PCI0.LPC.EC.HFNI, FNID)
        }

        If (LEqual (Arg0, 0x03))
        {
            Store (\_SB.PCI0.LPC.EC.AC._PSR (), PWRS)
            If (OSC4)
            {
                PNTF (0x81)
            }

            If (LNotEqual (ACST, \_SB.PCI0.LPC.EC.AC._PSR ()))
            {
                \_SB.PCI0.LPC.EC.ATMC ()
            }

            If (SCRM)
            {
                Store (0x07, \_SB.PCI0.LPC.EC.HFSP)
                If (MTAU)
                {
                    Store (0x03E8, Local2)
                    While (LAnd (\_SB.PCI0.LPC.EC.PIBS, Local2))
                    {
                        Sleep (One)
                        Decrement (Local2)
                    }

                    If (Local2)
                    {
                        Store (One, \_SB.PCI0.LPC.EC.PLSL)
                        Store (MTAU, \_SB.PCI0.LPC.EC.PLTU)
                        Store (PL1L, \_SB.PCI0.LPC.EC.PLLS)
                        Store (PL1M, \_SB.PCI0.LPC.EC.PLMS)
                    }
                }
            }

            If (VIGD)
            {
                \_SB.PCI0.VID.GLIS (\_SB.LID._LID ())
                If (WVIS)
                {
                    VBTD ()
                }
            }
            Else
            {
                If (WVIS)
                {
                    \_SB.PCI0.VID.GLIS (\_SB.LID._LID ())
                    VBTD ()
                }
            }

            VCMS (One, \_SB.LID._LID ())
            AWON (Zero)
            If (CMPR)
            {
                Notify (\_SB.SLPB, 0x02)
                Store (Zero, CMPR)
            }

            Store (One, \_SB.PCI0.LPC.EC.OCPF)
        }

        If (LEqual (Arg0, 0x04))
        {
            NVSS (Zero)
            Store (Zero, \_SB.PCI0.LPC.EC.HSPA)
            Store (\_SB.PCI0.LPC.EC.AC._PSR (), PWRS)
            If (OSC4)
            {
                PNTF (0x81)
            }

            \_SB.PCI0.LPC.EC.ATMC ()
            Store (One, \_SB.PCI0.LPC.EC.OCPF)
            If (LNot (NBCF))
            {
                If (VIGD)
                {
                    \_SB.PCI0.LPC.EC.BRNS ()
                }
                Else
                {
                    VBRC (BRLV)
                }
            }
        }

        If (XOr (\_SB.PCI0.EXP4.PDS, \_SB.PCI0.EXP4.PDSF))
        {
            Store (\_SB.PCI0.EXP4.PDS, \_SB.PCI0.EXP4.PDSF)
            Notify (\_SB.PCI0.EXP4, Zero)
        }

        If (XOr (\_SB.PCI0.EXP5.PDS, \_SB.PCI0.EXP5.PDSF))
        {
            Store (\_SB.PCI0.EXP5.PDS, \_SB.PCI0.EXP5.PDSF)
            Notify (\_SB.PCI0.EXP5, Zero)
        }

        \_SB.PCI0.LPC.EC.BATW (Arg0)
        \_SB.PCI0.LPC.EC.BWAK (Arg0)
        \_SB.PCI0.LPC.EC.HKEY.WGWK (Arg0)
        Notify (\_TZ.THM0, 0x80)
        VSLD (\_SB.LID._LID ())
        If (VIGD)
        {
            \_SB.PCI0.VID.GLIS (\_SB.LID._LID ())
        }
        Else
        {
            If (WVIS)
            {
                \_SB.PCI0.VID.GLIS (\_SB.LID._LID ())
            }
        }

        If (LLess (Arg0, 0x04))
        {
            If (And (RRBF, 0x02))
            {
                ShiftLeft (Arg0, 0x08, Local0)
                Store (Or (0x2013, Local0), Local0)
                \_SB.PCI0.LPC.EC.HKEY.MHKQ (Local0)
            }
        }

        If (LEqual (Arg0, 0x04))
        {
            Store (Zero, Local0)
            Store (CSUM (Zero), Local1)
            If (LNotEqual (Local1, CHKC))
            {
                Store (One, Local0)
                Store (Local1, CHKC)
            }

            Store (CSUM (One), Local1)
            If (LNotEqual (Local1, CHKE))
            {
                Store (One, Local0)
                Store (Local1, CHKE)
            }

            If (Local0)
            {
                Notify (_SB, Zero)
            }
        }

        Store (Zero, RRBF)
        Return (WAKI)
    }

Share this post


Link to post
Share on other sites

@gpspl 

 

i take it this is not for a T420 (but T410?). so anyway, look in the zip file in this guide and refer to file:  dsdt.dsl

it has comments (search for tjl) that indicate the changes that were made. you can probably cut and paste quite a bit into your DSDT

Share this post


Link to post
Share on other sites

just a few words to tell you that the card AW-CB160H has this speed on T420

 

 

 

Amazing. But I don´t know why, though previously  I could, now its impossible to me to boot into Yosemite with the card installed. (kernel panic)

 

This results were obtained booting from windows 7

post-355016-0-26828300-1458223371_thumb.jpg

Share this post


Link to post
Share on other sites

nice internet plan!

 

with my plan, I get 60 Mbps down and 6 up... what can that chip do on your home network? presuming you are bandwidth limited by your service provider. and then again, my home wifi is limited to 450 Mbps per channel. i use an atheros chip and it connects at 300 Mbps  on OS X.

Share this post


Link to post
Share on other sites

Hi all.. First post... :-)

 

I got a bit annoyed about the bios fan controller..

It seemed to stay at 3500 rpm even if temperature was low and it seemed to run the cpu a little hot when under load load for a long time.

 

Found this post on the thinkpad forum.: http://forum.thinkpads.com/viewtopic.php?f=32&t=91141#p607951

 

After adding the patch to the dsl and compiling, the fan control is perfect.(Just make sure hwmonitor is running and started at login as it poll the TCPU)

Low load is 55C and fan at 1950 rpm and almost silent.

High load is 80-85C and fan about 4500 rpm (was 90-92C before)

 

My install is just a default install following the guide(Thanks!! tluck)

Used a decompile of the existing aml because I had problems compiling the dsl included in the guide.

And in the dsl I just merged the thinkpad forum change.

 

WARNING!! It is important to run hwmonitor with 'continue to monitor sensors in background' or similar that query TCPU in intervals otherwise the fan will not be controlled.

 

The best solution would be to find a method that is called in intervals by the OS. (Could be battery status?) 

 

Does this solution make sense to you good people here and do you have a suggestion to a method polled by the OS we could use to 'ping' TCPU in intervals to ensure the controller code is keeping the temperature correct? 

 

 

The modification ended up like this:

Method (TCPU, 0, NotSerialized) 

{                   

    Store (^^EC.TMP0, Local0)

    /* FAN control START */

    Store (\_SB.PCI0.LPC.EC.TMP0, Local0)

    If (LLessEqual (Local0, 0x32))  // CPU Temp is <= 50C 

    {   

        Store (Zero, \_SB.PCI0.LPC.EC.HFSP) // Set FAN Off 

    }   

    If (LGreaterEqual (Local0, 0x55)) // CPU Temp is >= 85C 

    {   

        Store (0x40, \_SB.PCI0.LPC.EC.HFSP) // Set FAN Mode Disengaged - Total Maximum 

    }   

    Else {

        If (LGreaterEqual (Local0, 0x4B)) // CPU Temp is >= 75C

        {       

            Store (0x07, \_SB.PCI0.LPC.EC.HFSP) // Set FAN Mode 7 - Maximum Speed

        }       

        Else {  

            If (LGreaterEqual (Local0, 0x46)) // CPU Temp is >= 70C

            {           

                Store (0x04, \_SB.PCI0.LPC.EC.HFSP) // Set FAN Mode 4 - Medium Speed

            }           

            Else {      

                If (LGreaterEqual (Local0, 0x41)) // CPU Temp is >= 65C

                {               

                    Store (0x02, \_SB.PCI0.LPC.EC.HFSP) // Set FAN Mode 2

                }               

                Else {          

                    If (LGreaterEqual (Local0, 0x3D)) // CPU Temp is >= 61C

                    {                   

                        Store (0x01, \_SB.PCI0.LPC.EC.HFSP) // Set FAN Mode 1 - Lowest Speed

                    }                   

                }               

            }           

        }       

    } /* FAN control END */

    Return (Local0)

}

 

Hi mikaelr, is it possible to detect wether AC adapter is plugged in or not in DSDT? So we could add a different routine for fan speed based on power source. I already implement these codes in my DSDT for quite long time but still can not figure it out. 

Share this post


Link to post
Share on other sites

AW-CB160H has MHF4 connectors.

How did you connect the antennas?

With MHF4 antennas, of course.

 

But i keep wonder why now i have the kernel panic booting from Yosemite….

nice internet plan!

 

with my plan, I get 60 Mbps down and 6 up... what can that chip do on your home network? presuming you are bandwidth limited by your service provider. and then again, my home wifi is limited to 450 Mbps per channel. i use an atheros chip and it connects at 300 Mbps  on OS X.optic fiber

 

nice internet plan!

 

with my plan, I get 60 Mbps down and 6 up... what can that chip do on your home network? presuming you are bandwidth limited by your service provider. and then again, my home wifi is limited to 450 Mbps per channel. i use an atheros chip and it connects at 300 Mbps  on OS X.

Optic fiber. 300 Mbps up, 30 Mbps down.

post-355016-0-45991700-1458227538_thumb.jpg

Share this post


Link to post
Share on other sites

Hello!

I just managed to install El Capitan on my T420, huge props to all the people involved in gathering and making the information available (esp tluck).

I browsed the topic for the "external monitor" keywords, and if I understood correctly, I can only attach an external monitor through the ports on the docking station?

I don't have a docking station, so my question is if there is any way of making this work plugging the VGA/DP cable directly into the laptop?

If I plug in the VGA or DP cable after booting up, no monitor is recognized (also if cables were in when booting). But I saw that a lot of people got it to work, but I assume it was through the docking station.

If I plug in the monitor at boot time, switch the picture to the ext monitor with Fn+F7 before continuing with booting, then after the apple boot loading indicator disappears (right before getting to login screen), laptop reboots.

 

I appreciate any suggestions. Right now I dont know much about DSDT, but if sthing like that is necessary for this, I will look into it.

 

my T420 has i7-2720qm cpu, 2x4Gb of ram, and only the integrated hd3000 (no dGpu).

 

Thank you

 

 

Share this post


Link to post
Share on other sites

@davidian

 

welcome to our growing forum! 

 

without the dock station, you have 2 options for external monitor - DP or VGA - both ports are on the left side and work with the clover config (and patches) in the Zip.

VGA is not active so you must boot or do a sleep wake cycle.

 

i use DP on the side often. I have a DP to DP cable for my HP monitor. I also have 2 converters:

(1) DP to HDMI - good for TVs

and

(2) DP to VGA - which is dynamic and way better than trying to use the built-in VGA. 

 

you shouldn't have to do any FN keys - as soon as the DP cable is connected - it should recognize it. does this cable/monitor work with Windows? 

Share this post


Link to post
Share on other sites

@davidian

 

welcome to our growing forum! 

 

without the dock station, you have 2 options for external monitor - DP or VGA - both ports are on the left side and work with the clover config (and patches) in the Zip.

VGA is not active so you must boot or do a sleep wake cycle.

 

i use DP on the side often. I have a DP to DP cable for my HP monitor. I also have 2 converters:

(1) DP to HDMI - good for TVs

and

(2) DP to VGA - which is dynamic and way better than trying to use the built-in VGA. 

 

you shouldn't have to do any FN keys - as soon as the DP cable is connected - it should recognize it. does this cable/monitor work with Windows? 

 

Thank you for the quick reply. What I tried was DP-DP, and VGA-VGA between laptop and monitor, none of them worked.

I also tried the suggested sleep-wake cycle with the VGA, nothing changed.

Regarding the install, I followed the steps from your post, did the post install steps also (copy to EFI folder from zip to HD just like for the USB installer, copied and renamed config 1366 plist file, copied Vendor files, and run the _kext install script), did I miss something?

On the laptop LCD monitor works great, but the resolution is to small and TN panel is quite weak, thats why I would like to take advantage of the external monitor.

Monitor is Dell U2410, but I tried with a Samsung 2333 also (just VGA, no DP on that model).

Share this post


Link to post
Share on other sites

@davidian

 

the DP should just work? when you plug in the DP-DP monitor - does the screen change at all? i mean register that you plugged something in?

 

what mac model does it think it is? run these on the command line please:

 

ioreg -l | grep model

 

ioreg -l | grep FrameBuffer

Share this post


Link to post
Share on other sites

@davidian

 

the DP should just work? when you plug in the DP-DP monitor - does the screen change at all? i mean register that you plugged something in?

 

what mac model does it think it is? run these on the command line please:

 

ioreg -l | grep model

 

ioreg -l | grep FrameBuffer

 

no change in the screen on the laptop (Displays is open from System Settings)

monitor just aknowledges that5 the cable was plugged in into something, but goes into standby

 

Attilas-MacBook-Pro:~ attila$ ioreg -l | grep model

    |   "model" = <"MacBookPro8,3">

    | |   | |   "model" = <"Intel HD Graphics 3000">

    | |   | |   "model" = <"Intel E1000e">

    | |   |   |   "model" = "Intel 82579LM PCI Express Gigabit Ethernet"

    | |   |         "model" = <"Apple WiFi card">

      |     "model" = "Disk Image Driver for MacOS X"

Attilas-MacBook-Pro:~ attila$ ioreg -l | grep FrameBuffer

    | |   | | |   "NumFrameBuffer" = <01>

    | |   | |     "kFrameBufferType" = 1

Attilas-MacBook-Pro:~ attila$

Share this post


Link to post
Share on other sites

{censored} clover changed how it figures out the product type - 8,3 is not going to work, so you only have 1 buffer

 

change add the 8,1 definition to your config.plist and you should be good to go. i have to add that back in explicitly 

 

<key>SMBIOS</key>
        <dict>
                <key>Mobile</key>
                <true/>
                <key>Trust</key>
                <true/>
                <key>BoardVersion</key>
                <string>MacBookPro8,1</string>
                <key>ProductName</key>
                <string>MacBookPro8,1</string>
        </dict>

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 fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host
      Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. 
       
      The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
       
      @colt2 HOW TO: Create a bootable El Capitan ISO for VMware
      @dsmccombs comment on faking Ivybridge Processor
      @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6
      @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
      VirtualBox Forum: Status of OSX on OSX
       
      Requirements
         Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X)    4GB or more RAM (2GB or more will be needed for OS X)    Hard Disk with at least 40GB free for Virtual Machine    Oracle VM VirtualBox v 5.0.34    Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75    16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC  
      Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes.  Note: you will need approx 16GB of free space on your hard disk for the script to complete.
       
       
       
      3.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 4.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
       
      Create an El Capitan Virtual Machine in VirtualBox
      1.  Open the VirtualBox program and click the "New" button to create a new VM.
       

       
      2.  Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version.  I named my Virtual Machine "El_Capitan", then clicked next...
       

       
      3.  Leave the Memory size at the recommended 2048 MB, then click next.
       

       
      4.  Choose to "Create a virtual hard disk now", then click the create button.
       

       
      5.  For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare.  Click next...
       

       
      6.  For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).
       

       
      7.  On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger.  When you click the create button, you will now see your new VM in the VirtualBox main GUI.
       

       
      8.  Click the settings button on the Main Menu to tweak a few settings....
         a.  On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)
       

       
         b.  On the System/Processor tab, you can increase the allocated CPU cores to 2
       

       
         c.  On the Display tab, you can increase the allocated Video Memory to 128MB
       

       
         d.  On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". 
       

       
      Navigate and select the El Capitan ISO we created earlier...
       

       
         e.  Click the OK button to finalise the VM settings.
       
       
      Patch El Capitan vbox configuration file with DMI Settings from a Mac
      1.  From the start menu, type cmd and click run as administrator to open an administrative command prompt. 
       

       
      2.  Choose a Mac Model similar to your host system, then type the following lines, followed by <enter>  after each line.  Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
       
      Eg iMac11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3.  Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.  You can try from one of the following if this happens:

      To spoof Lynnfield i5 750 CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4.  Close the command prompt window.
       
       
      Installation of El Capitan
      We are now ready to start the El_Capitan Virtual Machine....
       



       
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

       
      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan.
       

       
      3.  Quit DU and choose Macintosh HD to install El Capitan on.
      4.  After 20-30 min (depending on how fast your system is), the installation will complete.  At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive.  The VM is now ready to reboot into OS X from the virtual hard drive.
      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
      7.  Finally, you will arrive at the El Capitan Desktop.
       

       
      8.  Network/internet and audio should work OOB but on my system, the sounds were distorted.  Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). 
       
       
      Customization with VBoxManage
      1.  You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
       
      Update:  For VirtualBox 5.2.x, the command for changing screen resolution has changed...
       
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
      eg
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2.  Adding serials and other SMBIOS details for the System Information Screen
      VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
       
      Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above).  Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .
       

       
      UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
      UPDATE macOS High Sierra 17A365:  For macOS High Sierra, use CHSI.tool in post#73.
      UPDATE macOS Mojave 18A391:  For macOS Mojave or High Sierra, use macOS_iso_creator.tool on page 4 of thread.
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
    • By Masha24
      Hi guys, I've been lurking in the shadows for months trying to learn how to hackintosh this laptop.  Perhaps if anyone has the time, I could use some help getting it to install 
       
      Trying to install High Sierra on this Laptop:
       
      Lenovo Ideapad 110-171KB-80VK (2017)
      Intel Core i5 7200U
      Intel HD 620 Graphics
      Resolution: 1600x900
       
      Elan PS2 Track Pad - [ACPI\VEN_ETD&DEV_0675 - system device -PCI\VEN_8086&DEV_9D23&SUBSYS_383117AA&REV_21]
      Realtek Network    - [PCI\VEN_10EC&DEV_8136&SUBSYS_383317AA&REV_07]
      Realtech audio
       
      SATA Controller    - [PCI\VEN_8086&DEV_9D03&SUBSYS_382F17AA&REV_21]
      USB 3.0 XHC        - [PCI\VEN_808
       
      --- Using Clover *
      --- I'll attach it below.
       
      I can't quite get it to install, and i've been going in circles for months now ...
      I'll attach everything I have so far including, verbose pics, clover preboot, Clover folder, etc.
       
      Here are some photos of the verbose text leading up to the installer, if maybe there is something useful in here?
       

       
       
       
      And now photos of the installer
       
       
       

       
       

       
       
      Above is an image of the Installer log, (the main pop up window loads from about 10 mins and stops arbitrarily at 2 minutes left, every time) of the nearly hundred attempts i have made, this is the final screen i get, pretty much no matter what i do.
      Sometimes the the order of what it says is different , but the main things of interest are:
       
      "Target is not convertible to APFS: This volume is not formatted as Mac OS Extended journaled."
      "Warning: Couldn't find Board ID, Chip ID, & ECID in new namespace, falling back"
      "Unable to get fs for null"
      " NO native mechanism to verify Applediagnostics.chunklist"
      " NO native mechanism to verify Installfa.plist"
      " NO native mechanism to verify Basesystem.dmg"
      " NO native mechanism to verify AppleDiagnostics.dmg"
      " NO native mechanism to verify InstallESD.dmg"
      " NO native mechanism to verify Basesystem.chumklist"
       
      I have tried many many ... many .. different combinations of kexts, drivers, copies of clover, forks of clover - different copies of drivers and kexts from different sources.. including from all the official repositories.
       
      * I am not trying to install with APFS - the drive i am using is a spinning HDD - so i don't understand the first line quote above.
      * I am using a usb2 slot - there is only two on this machine - 1- usb2 and 1- usb3
      * As you'll see in the Clover folder i'm using APFSdriverloader. - so the installer should detect the installer-APFS-thing - and see it should be HFS+ ?? no?
       
      I'll detail the procedures:
       
      I wiped the Target HDD drive with a live linux USB.
      i prepair the USB with Createinstallmedia method, install clover to the EFI on usb, load kexts and drivers (I've been recently attempting with the Plist from a 'certain other site' Ton*****86) As it has the dvmt preallocation patch and other bits - i'm of course open to ANY other files/pLists .. this is just the one i've been experimenting with lately.)
      Add ' -v ' in clover options to see the verbose output
      in the installer (acts sketchy sorta, delayed and sluggish) i use DiskUtility to erase the drive 'Macos extended journaled'
      Make initial selections, agree to license and begin install.
      it proceeds to 2 minutes left every time, and hangs. many times i've left it for hours, and even overnight.
      I'm honestly not kidding, it's nearly 100 times ive' tried this, i've downloaded high sierra from the app store 5 times to rule out that, i've used countless combinations of everything .. i'm almost completely burned out.
       
       
      If anyone can shed some light i'll be VERY thankful!... I'm ready to go in a completely new direction...please please please help
       
      I'll put the Clover in the next post because i ran out of space in this one......
       
       
       
       
       
       
       
      Here is the latest clover i've been using, with the preboot, and DSDT/SSDT (F2 & F4) in it.
       
      CLOVER-Oct15.zip
       
      Thank you very much for ANY help you can provide
    • By tluck
      Lenovo T460 macOS with Clover Guide
      Release v2018.10.12 on GitHub Updated to Clover r4703 Updated Kexts SSDT updates for T460 Added Frank's T470p DSDT files Added T470 DSDT
        Various Tweaks over Last months The zip file is a complete Clover ESP (/EFI) bundle and kext pack for the Lenovo T460. The current file bundle is tested on Sierra. 
      Note: I never got the GFX fully working on El Capitan. 
      Full Clover file set - config.plist etc. Includes all custom kexts Includes custom DSDT/SSDT scripts and patches Utility scripts The zip bundles are posted to GitHub: https://github.com/tluck/Lenovo-T460-Clover/releases
      Caveat: The T460 systems used here was configured with: i5-6300U, Intel HD Graphics 520, 1920x1080 touch screen. If you have a different system model, then extract the ACPI files and use the included scripts to create a set of files consistent with your system type and BIOS version. See below for details.
      Credits: RehabMan, Shmilee, vusun123, TimeWalker, Mieze from which, much of their work and help is/was was used to get the T460 to this point.
      Devices and aspects working:
      Ethernet -  Intel I219LM is enabled via IntelMausiEthernext.kext WiFi/BT - substitute the Intel WiFi/BT with a compatible Broadcom or Atheros chip Audio - ALC293 codec implemented via AppleALC.kext (old AppleHDA_ALC293 and CodecCommander kexts are not needed) PS2 - ClickPad + TrackPoint + all 3 buttons - using a modified VoodooPS2Controller to support new layouts - and added some custom Fn key maps based on 440/450 dsdt USB - implemented via custom SSDT + USBInjectAll kext. All USB3/USB2 ports are intel-based and work -  3 external USB and internal Camera, BT, etc  Sleep/Wake - the sleepwatcher package and custom sleep/wake scripts are used to help with sleep/wake for BT and PS2 devices. Note: have not tried to implement the SD card reader - no driver found.
      ACPI Files
      New Installation - Steps and Details
      Part 1 - OS Installation
      Part 2- Post OS Installation and Setup
      Notes on Custom Kexts
       
    • 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  selezionate OsxAptioFixDrv-64
                             *  :Se nel vostro sistema è presente una scheda grafica (discreta) della serie 9xx nVidia selezionate OsxAptioFix2Drv-64 al posto di  OsxAptioFixDrv-64 *
      ** OsxAptioFix2Drv :E' necessario per poter impostare CsrActiveConfig= 0x3 **
      ***OsxAptioFix3Drv oppure AptioMemory --> (consigliato) devono essere usati su hardware Skylake o successivi perché permettono alla nvram di lavorare correttamente
           (mi raccomando o uno o l'altro)
      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 
       
       
       
      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
      apfs.efi-10.13-NoLog.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      apfs.efi-10.13.1-No_LOG.zip
      apfs.efi-10.13.2_No_Log.zip
      apfs.efi-10.13.3-No_Log.zip
      apfs.efi-10.13.4-No_Log.zip
      apfs.efi-10.13.5_No_Log.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip






    • By warty
      On 8/20/2018 at 5:22PM, TessereKt said:
       
      On 8/21/2018 at 7:34AM, insanelyDeepak said:
       
      @insanelyDeepak, I would like to try cloverHDA, but I need help understanding how to use it.
       
      I have an Asus laptop that uses Realtek ALC295.
       
      My questions with regard to using cloverHDA:
      1.  I am running High Sierra (10.13.6). Is cloverHDA directly compatible? If not, can it easily be made compatible with adjustments I can apply?
       
      2.  What needs to be done with the original AppleHDA.kext that is already present in /S/L/E? Should it be left alone? Should it be removed? If it is removed, does the AppleHDA.kext that comes with cloverHDA, for example /Vanilla AppleHDA/Mac OS Sierra 10.12.6/AppleHDA.kext, need to be installed in its place?
       
      3.  In the 21 aug 18 reply to TessereKt, you mentioned "there is ALCPluxfix must install this." I noticed that there is a directory for alc_fix in one ALC295 directory (the ALC295_v2 Asus UX430UA directory) but not in the other ALC 295 directory that is provided (the ALC295/3254 directory). In which situation(s) is ALCPlugFix required?
       
      4.  My pathmaps are somewhat different from those in the cloverHDA.kext. Is there an easy way for me to customize the kext? For example, if I just switch the values in the xml files, will that be enough? Or does the whole thing then need to be recompiled?
       
      needed pathmaps:
      33-2
      23-3
      7-36-18
      9-34-19
       
      (My highest priority for the moment is getting headphone working, which is 33-2, and I might even be able to use the 33-3 that is already included. But I would like to eventually get all of them working.)
       
       
×