Jump to content
Kogen Mantis

Lenovo ThinkPad T420 with UEFI Only

4,393 posts in this topic

Recommended Posts

@d.u.o

if you follow my installation guide exactly, then you will have a fully working system using clover.  The problems you are seeing are not uncommon if the configuration steps are not followed closely. The lack of sound and battery makes me think you don't have the custom dsdt.aml in place - meaning the file  /Volumes/EFI/EFI/CLOVER/ACPI/patched/dsdt.aml is not there? Did you rename the folder ACPI.1366x768 to ACPI?

 

Using clover means direct installation on GPT disks -  so thats the big difference. It means reformatting your system drive GUID/GPT. 

No more MBR formatted system drive  so that means you also boot via UEFI - both OS X an Windows.

 

Not sure why you had so much trouble getting OS X installed? 

if you have a 2nd drive, then i would format that GUID so you can get it working with OS X and Clover - then you can mess with dual boot etc.

Share this post


Link to post
Share on other sites
Advertisement

@tluck, i had toruble because my notebook doesn't have UEFI only bios, i'm able to choose from bios legacy/uefi. Even if I choose uefi only and format the hdd as gpt(as you instructed), after I've finished installing, the os doesn't want to boot. The boot menu(F12) appears and even if I choose the hdd on witch iI installed the OS it doesn't boot, the boot menu window keeps appearing. The only way i've managed to install dual boot os x and windows was with the bios set on legacy mode and I formatted the drive as MBR. I admit I didn't use your tutorial to create a bootable USB Yosemite, instead, I've used http://www.insanelymac.com/forum/topic/299067-boot-usb-os-x-yosemite-v1cloverchameleon/ version 2. After creating the installer I replaced the necessary files to be able to install to a mbr formatted drive. After that i've followed the steps from your gide, placed the dsdt in the correct folder, renamed the folder and the config.plist, etc. 

Also I've noticed something strange, I don't know if it is rellevant. Initially I've installed Yosemite to my msata ssd drive but after a few restarts the computer gave me an error that there is no HDD installed. If I use the bootable USB I'm able to start the OS, but whithout I keep geting the same error. So I installed Yosemite on the sata drive and I dind't had any problems so far. Is clover somehow incompatible with msata drives? Thank you.

Share this post


Link to post
Share on other sites

@d.u.o

 

sorry, i have to ask - did you install the clover zip contents to your GPT formatted HD or USB in the EFI folder?

 

An easy way to boot clover, is to create a GPT/GUID formatted USB.

Take a 4 GB or larger USB and use diskutility to reformat with a single HFS partition (click options to set mode to GPT).

it will actually have 2 partitions.

 

mount the first ESP (named EFI) partition from the USB and copy the zip contents - all of it to the USB /Volumes/EFI location.

 

so you have both folders

/Volumes/EFI/EFI/BOOT and

/Volumes/EFI/EFI/CLOVER

simply:

rename ACPI.1366x768 to ACPI

rename config.1366x768.plist config.plist

 

select USB via F12 to boot up clover

 

the T420 will look at the format of each disk to determine how to boot from it.

if MBR will look for boot0 in the MBR.

if GPT looks for BOOTx64.efi in /EFI/BOOT/

 

if you want to stay with Chameleon thats fine. there is no reason the kexts will not work for that boot loader.

if you are testing yosemite, you may need to add kext-dev-mode=1 to the boot args so it will ignore the custom kext signatures.

 

personally i have not tried an mSATA drive. (I use SATA and SSD.) so can't say why you are having trouble with it.

Share this post


Link to post
Share on other sites

10.10 dp8 / beta3 installed through update with no further issues - even better, iMessage is working again, storage is shown properly as well

post-6861-0-03780000-1410811030_thumb.png

post-6861-0-15776200-1410813388_thumb.png

Share this post


Link to post
Share on other sites

New bundle for DP8: Clover UEFI on T420 Guide

 

Just downloaded and installed the update package for DP8 ... which should be pretty much the same as the Beta 3 update if you are on that track. 
 

Nothing particularly new for Mavericks users in this bundle - but feel free to update any custom kexts, etc. This bundle has the 2 updated Apple kexts for 10.10 DP8. Again AppleHDA and the Broadcom bluetooth kext was changed in this DP update.

 

Since I am using a non-Clover generated set of MLB and ROM values, iMessage continued to work fine for me. However, I hope others see the same results that Cowboy Mike reported regarding iMessage or FaceTime!

 

Note: I recommend re-indexing your drives after Yosemite installation - seems to fix up problems with odd space reports and missing files on searches. For example on the system partition you can run:

sudo mdutil -E /

16-September-2014 - 10.10 DP8/Beta Update

  • Clover updated to r2910 (r2890 is latest posted on Sourceforge - either is fine)
  • FakeSMC updated to 6.11.1328
  • Added drop table MCFG for Nvidia/Optimus (mixed gfx)
  • Added drop table DMAR so VT-d does not have to be disabled
  • ACPIBacklight.kext - v2.0.3 - with modified code to fix/workaround for LCD brightness in Yosemite.
  • Added 10.10 kext folder (AppleHDA.kext and BroadcomBluetooth kext are different)
  • Note: To make an Yosemite USB installer, just follow the 10.9 Mavericks method
Edited by tluck

Share this post


Link to post
Share on other sites

 

New bundle for DP8: Clover UEFI on T420 Guide

 

Just downloaded and installed the update package for DP8 ... which should be pretty much the same as the Beta 3 update if you are on that track. 

 

Nothing particularly new for Mavericks users in this bundle - but feel free to update any custom kexts, etc. This bundle has the 2 updated Apple kexts for 10.10 DP8. Again AppleHDA and the Broadcom bluetooth kext was changed in this DP update.

 

Since I am using a non-Clover generated set of MLB and ROM values, iMessage continued to work fine for me. However, I hope others see the same results that Cowboy Mike reported regarding iMessage or FaceTime!

 

Note: I recommend re-indexing your drives after Yosemite installation - seems to fix up problems with odd space reports and missing files on searches. For example on the system partition you can run:

sudo mdutil -E /

16-September-2014 - 10.10 DP8/Beta Update

  • Clover updated to r2910 (r2890 is latest posted on Sourceforge - either is fine)
  • FakeSMC updated to 6.11.1328
  • Added drop table MCFG for Nvidia/Optimus (mixed gfx)
  • Added drop table DMAR so VT-d does not have to be disabled
  • ACPIBacklight.kext - v2.0.3 - with modified code to fix/workaround for LCD brightness in Yosemite.
  • Added 10.10 kext folder (AppleHDA.kext and BroadcomBluetooth kext are different)
  • Note: To make an Yosemite USB installer, just follow the 10.9 Mavericks method

 

How you created a non clover generated MLB and ROM value?
have you extracted them from a real mac?
 
thx

Share this post


Link to post
Share on other sites

tluck,

 

Thanks for much for you work on this. Followed the directions and have my t420s working with 10.9.5. With a little extra searching I got the screen brightness fn keys working.

 

I have a few questions..

 

I noticed an error about LPC not being initialized, not sure you have also seen that error message before? I did find a post saying to not drop the MCFG table. Not sure what the impact of this would be?

 

For some reason I have two batteries listed in the battery monitor. Not sure this is normal or not?

Share this post


Link to post
Share on other sites

@eilatuna - i ran a tool called imessage_debug on a real mac to see what are MLB and ROM values it used. and then i have clover inject these instead of coming up with its own values.

 

@IHateAliases - sounds good. there maybe be some differences between the DSDT for a T420 vs T420s. you should not have to drop the MCFG table unless you are having problems with PCI and/or have a 2nd gfx (optimus/nvidia) card.  dropping it didn't seem to bother my system. however, you could remove the MCFG drop lines in the config.plist. hmm.

 

not sure about the double battery thing. again maybe a dsdt thing?  i have not upgraded to 10.9.5 yet. but will do that when i get back home.

Share this post


Link to post
Share on other sites

Thx tluck,

Now i have only one problem if I change value in confit.plist, the ROM value don't change, how is possible?!?!? I've tried to leave blank the rom value but iMessage_debug report the same value...I'm very confused

Share this post


Link to post
Share on other sites

@eilatuno -

 

note: these are fake values

run imessage_debug on a mac and you get output something like this:

 

...

2014-09-18 21:06:15.744 imessage_debug[88950:717741] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM: <1c2df32ac 4abc>

2014-09-18 21:06:15.745 imessage_debug[88950:717741] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB: C02012300UDDDMRAC
...
 
i then put a new section into the config.plist using a plist editor by cutting and pasting the values above and it looks something like this:
 
<key>RtVariables</key>
<dict>
      <key>MLB</key>
      <string>C02012300UDDDMRAC</string>
      <key>ROM</key>
      <data>
      AcLfMqxKvA==
      </data>
</dict>

Share this post


Link to post
Share on other sites

Anybody installed 10.9.5? Any issues? Thanks.

I did it without any issue (apple menu update…)

i have no sound anymore (but i did not take the time to put kext again, i was too lazy)

so it's explained.

I will do it this WE

 

update : sound back with 10.9.5 added to bundle at  Clover UEFI on T420 Guide

 

20-September-2014 - 10.9.5 and 10.10 DP8/Beta Update

 

thanks to tluck :)

Share this post


Link to post
Share on other sites

Just got to it last night. No obvious issues so far. but i have been running on yosemite for awhile despite a few bugs in finder and mail.

 

10.9.5 added to bundle at  Clover UEFI on T420 Guide

 

20-September-2014 - 10.9.5 and 10.10 DP8/Beta Update

 

  • Clover updated to v2912 (2890 is latest posted)
  • FakeSMC updated to 6.11.1328
  • Added drop table MCFG for Nvidia/Optimus (mixed gfx)
  • Added drop table DMAR so VT-d does not have to be disabled
  • ACPIBacklight.kext - v2.0.3 - with modified code to fix/workaround for LCD brightness in Yosemite.
  • Updated 10.10 kexts folder (10.10.DP8 AppleHDA and BroadcomBluetooth kexts + Hackintosh Kexts)
  • Updated 10.9  kexts folder (10.9.5 AppleHDA and BroadcomBluetooth kexts + Hackintosh Kexts)
Edited by tluck

Share this post


Link to post
Share on other sites

@IHateAliases

here is an unpatched DSDT from my T420

Note: you may want to decompile from the aml file the same way as your dsdt.aml file so the source dsl files are more consistently formatted and similar syntax

 

t420-dsdt-original.zip

Share this post


Link to post
Share on other sites

Yosemite 10.10 GM update on Clover UEFI on T420 Guide.

 

used apple store update and all went well.

it installed new AppleHDA and BroadcomBluetooth kexts again.

so replace those!

 

30-September-2014 - 10.9.5 and 10.10 GM1 Update

  • Clover updated to v2932
  • Removed EmuVariableUefi-64.efi driver to use native NVRAM (vs /nvram.plist) - see note in guide on how to migrate.

Also, see the guide for those that want use Hibernation mode. Need to install OsxAptioFix2Drv.efi instead of standard OsxAptioFix-64.efi (file not included in zip at this time)

This is still pretty experimental but it works mostly. System will boot from the hibernated image, but LCD will be a bit scrambled until you close lid and then do a quick sleep/wake cycle.

Share this post


Link to post
Share on other sites

@Tluck

I used your EFI directly on my x220 with x220 dsdt to boot 10.10 PB4. Everything seems OK except that the power light is always blinking after waking from sleep. The sleeping is also not normal.The sleep light is on without blinking first after closing the lid. Do you have any idea how to fix it? Thanks.

Share this post


Link to post
Share on other sites

[sOLVED] Just hit Space bar to come over it.

 

@Tluck

 

I came across several problems as below, I think it should be better to note them in this great guide:

 

1, When boots up the installer sticking at: 

 
"To pair a Bluetooth keyboard, turn it on and wait for your computer to connect to it.”
 
Just hit Space bar to come over it.
 
2, When installer hangs at: 
 
"About a second remaining”
 
Don’t Panic!! 
 
This very second takes about 10 minutes or more to go, just wait for the installer reboot the computer and continue the installation.
 
The whole install process take nearly 1 hour to complete.
 
3, When first boot from HD, asked: 
 
“How Do You Connect?”
 
Select:
 
“My computer does not connect to the Internet”
 
and set up network later after install the NIC driver.

 

And, thanks for this great guide!! I'm running Mavericks 10.9.5 now, grab a dw1510 another day. 

 

-------------------------------------------------------------------------------------

 

Thanks for the great work. 

 

I tried T420_UEFI-Clover-b2932-10.8.8_10.9.5_10.10.GM1_2014-09-30.zip with Mavericks 10.9.5 and 10.9.4, both got stuck at asking for bluetooth keyboard screen. USB mouse working but no luck with internal keyboard. And I got no USB keyboard at home...

 

I followed the instructions: patition with GUID, createinstallmedia, rename ACPI.1366x768 and config.1366x768.plist, disable optimus and virtulization. 

 

I got one msata ssd and another one in ultrabay, did that causing the problem?? They both works under Windows7. Currently I'm booting Windows from msata, and is planning to erase the ultrabay ssd for Mavericks.

 

I got Thinkpad T420(4180-J4C) Core i5-2410M/HD3000/NVS 4200M(disabled)/1366x768/8G.

 

Did I miss something or the VoodooPS2 broken?

Share this post


Link to post
Share on other sites

[sOLVED]

 

Boot up using Windows 8 disk and Shift-F10 to open command window, use diskpart>>list volume to get corresponding drive letter, then

 

bcdboot f:\windows /s d: /f uefi

 

to copy uefi boot files to reserved partition. where f:\ is my Windows 7 drive and d: is its reserved partition.

 

It seems to work only if the BIOS set to "Legacy First", or get a BSOD. And the boot screen only a progress bar, no Windows logo, But it boots.

 

Then I tried to set Windows 7 to default.Hit F2 in Clover boot menu to store log to preboot.log, get corresponding device path and add it into the config.list.

 

Done. 

 

----------------------------------------------------------------------------------

 

Hey guys. 

 

Currently I select boot disk using F12 in BIOS. Is there a way to dual boot using bootmgr or Clover??

 

The OSX lays on one disk using GPT and Windows lays on another disk using MBR. 

 

Thanks in advanced.

 

----------------------------------------------------------------------------------

 

I tried to play with config.plist, comment out GUI>>Hide>>Windows, and set Scan>>Legacy=true, Windows partitions showed up but won't boot after a XP style Windows logo, and OSX boot failed too. I had to boot into Windows using F12, mount the ESP and revert config.plist to original. 

Share this post


Link to post
Share on other sites

Yosemite 10.10 GM update on Clover UEFI on T420 Guide.

 

used apple store update and all went well.

it installed new AppleHDA and BroadcomBluetooth kexts again.

so replace those!

 

30-September-2014 - 10.9.5 and 10.10 GM1 Update

  • Clover updated to v2932
  • Removed EmuVariableUefi-64.efi driver to use native NVRAM (vs /nvram.plist) - see note in guide on how to migrate.

Also, see the guide for those that want use Hibernation mode. Need to install OsxAptioFix2Drv.efi instead of standard OsxAptioFix-64.efi (file not included in zip at this time)

This is still pretty experimental but it works mostly. System will boot from the hibernated image, but LCD will be a bit scrambled until you close lid and then do a quick sleep/wake cycle.

 

 

 

So now it is using the native NVRAM. Does this mean iMessage will be working? I need a little clarification. What exactly is needed to get iMessage and FaceTime working?

 

Do I need a real mac to extract the MLB and ROM values, then place them into RtVariables? Please excuse my poor understanding of this subject, I'm trying!

Share this post


Link to post
Share on other sites

What does removing EmuVariable mean?  it means now the nvram variables/values are now kept in the bios vs a file on disk.  we don't need EmuVariable.efi to emulate nvram anymore as Clover (and OS X) can read from "NVRAM". So that's 1 less driver and that has some other benefits derived not reading and writing to a file.

 

As far as iMessage - I'm no expert here, but i learned a lot recently. So instead of trying to summarize - there is a amazingly comprehensive post by jaymonkey (search "jaymonkey fix iMessage" and read on. (sorry to be indirect but it is posted on a certain  (*x86) website - not mentionable in this forum). the author is a clover fan and explains very clearly what one needs to do in Step-5d. Read all of Step-5 for good background. Anyway, for me, I am using real MLB and ROM values currently set by RtVariable section of config.plist. ... but according to this post, this method may become deprecated or obsolete. (will add my values to nvram!) 

Share this post


Link to post
Share on other sites

Thanks tluck, I was able to finally get iMessage/Facetime to work.

I followed the iMessage posting you mentioned, Step-5d, specifically following the excerpt below.

After entering the values for ROM and MLB as described there, and making sure it was not changing between reboots, I got the contacting oracle support message (described in Step-8).

I called apple with the code provided in the message and they unlocked my imessage without problems.

 

 

******************************

The official (new) method of injecting/specifying the ROM & MLB values for Clover is as follows:

ROM: This will now be read from the last 6 bytes of the 'SmUUID' field. If you have nothing in the SmUUID field then Clover will try to use your BIOS's SystemId (see Part-2 of the guide) however, I personally think it's always best to override The BIOS (even if it does not suffer from the SId bug) and to use the terminal command 'uuidgen' to generate a new random value (See Part-2, Step 7, Path-C). Enter the generated UUID as the SmUUID value on the SMBIOS page. If this is a new OSX Install then you can leave it like that. If you want to keep you old ROM value then replace the last 6 bytes of SmUUID with the ROM value you were using before which is normally the MAC address of an ethernet port (usually en0).

Note: It is important to understand that configuring Clover like this will cause your existing Hardware (Platform) UUID to change (if it's an existing install). Whilst this in-it's-self is not a problem it will change the identity of your system from your previous install which in-turn may cause some user profile settings to be changed due to the Hardware (Platform) UUID being used as a key value for storing critical OSX configuration against.

MLB: This is now read from the 'Board Serial Number' field on the SMBIOS page, on a clean Clover install this is defaulted to Clovers own set value which is now black-listed on Apples systems. You therefore must replace this with your existing MLB value (on an existing install) or use your OSX S/N + Random Alpha / Numeric digits to make it up to 17 digits.

******************************

Share this post


Link to post
Share on other sites

Thanks tluck, I was able to finally get iMessage/Facetime to work.

I followed the iMessage posting you mentioned, Step-5d, specifically following the excerpt below.

After entering the values for ROM and MLB as described there, and making sure it was not changing between reboots, I got the contacting oracle support message (described in Step-8).

I called apple with the code provided in the message and they unlocked my imessage without problems.

 

 

******************************

The official (new) method of injecting/specifying the ROM & MLB values for Clover is as follows:

 

ROM: This will now be read from the last 6 bytes of the 'SmUUID' field. If you have nothing in the SmUUID field then Clover will try to use your BIOS's SystemId (see Part-2 of the guide) however, I personally think it's always best to override The BIOS (even if it does not suffer from the SId bug) and to use the terminal command 'uuidgen' to generate a new random value (See Part-2, Step 7, Path-C). Enter the generated UUID as the SmUUID value on the SMBIOS page. If this is a new OSX Install then you can leave it like that. If you want to keep you old ROM value then replace the last 6 bytes of SmUUID with the ROM value you were using before which is normally the MAC address of an ethernet port (usually en0).

 

Note: It is important to understand that configuring Clover like this will cause your existing Hardware (Platform) UUID to change (if it's an existing install). Whilst this in-it's-self is not a problem it will change the identity of your system from your previous install which in-turn may cause some user profile settings to be changed due to the Hardware (Platform) UUID being used as a key value for storing critical OSX configuration against.

 

MLB: This is now read from the 'Board Serial Number' field on the SMBIOS page, on a clean Clover install this is defaulted to Clovers own set value which is now black-listed on Apples systems. You therefore must replace this with your existing MLB value (on an existing install) or use your OSX S/N + Random Alpha / Numeric digits to make it up to 17 digits.

******************************

Exactly this. Read this same bit of info, generated a new SmUUID, and put in a valid serial number according to my machine specs (which is not hard to find), and it worked. Though I had to unlock my appleid email by calling apple support, and thanks to some fast talking asian male, I was able to get my facetime and imessage working. New way of doing things with Clover seems more efficient and streamlined.

Any idea why I have two clover boot Yosemite entries?

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 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.)
       
       
    • By C0nvert
      EFI Clover zip: https://aster-cloud.de/nextcloud/index.php/s/TjXg3qs2ydRTmS9
×