Jump to content
Kogen Mantis

Lenovo ThinkPad T420 with UEFI Only

4,394 posts in this topic

Recommended Posts

@veer

yes - replace intel wifi with OS X supported wifi card and then flash the box with a modified whitelist bios so it will not reject the card. these cards are often sold rebranded by HP, Dell etc on eBay. 

 

here are 3 options (i chose the 1st one)

 

Atheros AR5BHB92
- dual-band: 2.4GHz + 5GHz. МасOS up to 150 Mbps on 2.4GHz and up to 300 Mbps on 5GHz, Windows up to 300 Mbps on both bands.
Broadcom BCM94322HM8L
- dual-band: 2.4GHz + 5GHz. МасOS up to 150 Mbps on 2.4GHz and up to 300 Mbps on 5GHz, Windows up to 300 Mbps on both bands.

Atheros AR5B93

- single-band: 2.4GHz only. МасOS up to 150 Mbps, Windows up to 300 Mbps.

 

@adrenalation

this worked for me:

 

added a credit card to my appleID account.

remove all network location/interface definitions from the |System Network panel

rm        /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist

reboot and redo network interface definitions for ethernet and then wifi

 

(i know i know - some have found the order doesn't matter - but this is just what seems to work for me!)

 

if you are on Yosemite, it was very finicky and for me it took a lot of entering and reentering of ids and passwords.

seems like its looping but eventually it worked. 

Share this post


Link to post
Share on other sites
Advertisement
remove all network location/interface definitions from the |System Network panel

rm        /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist

reboot and redo network interface definitions for ethernet and then wifi

 

(i know i know - some have found the order doesn't matter - but this is just what seems to work for me!)

 

if you are on Yosemite, it was very finicky and for me it took a look of entering and reentering of ids and passwords.

seems like its looping but eventually it worked. 

 

I'm currently on mavericks and after following your suggestion here and on the guide, signing in keeps looping for both iMessage and Facetime. This is beyond my scope.

Share this post


Link to post
Share on other sites

@adrenalation.  it may not be a loop - and not necessarily a bad sign.  i must have entered it about 5 times. same on my real mac. 

Share this post


Link to post
Share on other sites

 

Atheros AR5BHB92

- dual-band: 2.4GHz + 5GHz. МасOS up to 150 Mbps on 2.4GHz and up to 300 Mbps on 5GHz, Windows up to 300 Mbps on both bands.

Broadcom BCM94322HM8L

- dual-band: 2.4GHz + 5GHz. МасOS up to 150 Mbps on 2.4GHz and up to 300 Mbps on 5GHz, Windows up to 300 Mbps on both bands.

Atheros AR5B93

- single-band: 2.4GHz only. МасOS up to 150 Mbps, Windows up to 300 Mbps.

 

 

to be fair, it may be that Windows is over reporting the speed, to make the marketers happy, whereas mac reports the actual speed. A 2.4 GHz chip with 2 antennta has a theoretical maximum speed of 150 Mbps: http://en.wikipedia.org/wiki/Wireless_N#Data_rates. The chip spec claims that it is a 1x2 MIMO configuration with 300 Mbps max speed, so ???

Share this post


Link to post
Share on other sites

Its true that wireless n is maxed at 150 per channel but a 2.4ghz card is only one band. Dual band uses 2.4 and 5 simultaneously hence the dual band. If you are using 1x2 or 1x3 you can get 300 or 450 all the way to 900 but now its unnecessary as ac can top that. So no, windows is not over reporting.

Share this post


Link to post
Share on other sites

whether it can hit that speed is a good question.

it says connected at 300 Mbps on OS X (on 5 G) with my atheros card.

i have not benchmarked it!

post-954945-0-00081500-1409192571_thumb.png

i vaguely recall it reporting 450 on windows. but i could be wrong.

 

 

Share this post


Link to post
Share on other sites

It depends on the antenna config. 1x3 should reach 450 but sometimes they cheap out and make it so that its 2 down and one up but 2x3 should reach 900 unless its 3 up and 3 down then its only 450

Share this post


Link to post
Share on other sites

my iMessage just broke because my credit card info was out-of-date (at least I'm assuming that was the initial reason) afterwards, I couldn't get it to log back in

 

after some googling, I realized my ROM value was possibly bad (all zeros):

/$ nvram -px | egrep 'MLB|ROM'
XX-XX:MLB XX%00
XX-XX:ROM %00%00%00%00%00%00%00%00%00%00%00%00%00

for some reason, this was suddenly a problem? anyways, i decided to try updating it.

 

I couldn't get `nvram` to write a new value from ROM like it is supposed to (it refused to update):

/$ sudo nvram XX-XX-XX:ROM=%00%00%00%00%00%00

So I made the edit by hand:

 

First computing the base64 encoded hex string for my mac address:

/$ python
Python 2.7.5 (default, Mar  9 2014, 22:15:05) 
[GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import base64
>>> base64.encodestring("\x00\x00\x00\x00\x00\x00")
'AAAAAAAA\n'

where the string of 00's was my en0 ether id:

/$ ifconfig en0 | grep ether

And pasting the result (sans \n) into the appropriate section (XX:ROM) of my `/nvram.plist` file

 

Then I moved the nvram shutdown script out of the way to avoid replacing this value:

/$ sudo mv /etc/rc.shutdown.d/80.save_nvram_plist.local /

And rebooted.

 

I was then able to log into iMessage. (and I then also moved the rc.shutdown script back)

Share this post


Link to post
Share on other sites

Hello.

 

I bought a T420 with i5 Cpu and only Intel HD3000 GPU

 

I need a Bios with Whitelist Removed to install a AR5B93 Wlan Card.

 

My Bios is UEFi Version 83ET53WW ( 1.23 )

Maschine Type 4236MBG

 

Its has a German Qwertz Keyboard.

 

My Question is:

 

I found some T420 Bioses with 1.46 and Wlan Whitelist removed.

 

Can i Flash any T420 Bios Files without Problems or exist different T420 with different Bios

 

I attached the Bios as Picture.

 

Thank you

post-47164-0-85693400-1409307563_thumb.jpg

Share this post


Link to post
Share on other sites

@manwe150

 

well its good to know how to do this. i was not familiar with either of these i did some reading. looks like clover supposedly does this for us by reading the SMBIOS now. i don't have either of these vars in my nvram. and perhaps yours were out of date and overiding the SBMIOS values? one may need to remove them from nvram.plist and let clover generate the stuff by populating/reading SMBIOS.

 

from the wiki - says that these 2 vars (MLB and ROM) are now deprecated and clover generates a SMBIOS string with these. clover-genconfig will spit out the MLB value for you. 

 

see RtVariables

 

ioreg -l |grep SMBIOS

cut and paste the stuff between <> and run through xxd -p -r and you see what this byte string has in it.

 

 

@samsunlu55

 

well yes. many of us have done this without issue.

flash to real bios v1.46 and then flash with modded bios v1.46. (i did on my 2 boxes) see post #2036738 on this.

Share this post


Link to post
Share on other sites

my iMessage just broke because my credit card info was out-of-date (at least I'm assuming that was the initial reason) afterwards, I couldn't get it to log back in

 

after some googling, I realized my ROM value was possibly bad (all zeros):

/$ nvram -px | egrep 'MLB|ROM'
XX-XX:MLB XX%00
XX-XX:ROM %00%00%00%00%00%00%00%00%00%00%00%00%00

for some reason, this was suddenly a problem? anyways, i decided to try updating it.

 

I couldn't get `nvram` to write a new value from ROM like it is supposed to (it refused to update):

/$ sudo nvram XX-XX-XX:ROM=%00%00%00%00%00%00

So I made the edit by hand:

 

First computing the base64 encoded hex string for my mac address:

/$ python
Python 2.7.5 (default, Mar  9 2014, 22:15:05) 
[GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import base64
>>> base64.encodestring("\x00\x00\x00\x00\x00\x00")
'AAAAAAAA\n'

where the string of 00's was my en0 ether id:

/$ ifconfig en0 | grep ether

And pasting the result (sans \n) into the appropriate section (XX:ROM) of my `/nvram.plist` file

 

Then I moved the nvram shutdown script out of the way to avoid replacing this value:

/$ sudo mv /etc/rc.shutdown.d/80.save_nvram_plist.local /

And rebooted.

 

I was then able to log into iMessage. (and I then also moved the rc.shutdown script back)

 

i experiment same problem here (same case here visa card was out of date,) except nvram -px | egrep 'MLB|ROM' give me nothing even right now (even if i got further (a bit)

thanks to your advice manwe150

Now :

nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB and nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM give me the same value as i have on my FaceTime/imessage 2nd HD

so i consider is ok (confirmed with iMessage.debug) 

but no connection right now 

 

i moved out all rc.(clover) script from /etc

 

must have a pb with nvram data cos then i try

sudo nvram -d efi-boot-device,

nvram efi-boot-device still there :(

<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>FF33309E-7909-4F25-BEA9-xxxx...</string></dict></dict><key>BLLastBSDName</key><string>disk0s2</string></dict></array>

I don't know how to replace nvram with the one i prepare on /root place

nvram -x -p give me the file i want to delete but not the date stored in /nvram.plist

 

why nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB or ROM give me a value

and i've the trace of 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB  when i do nvram -x -p?

 

FYi : i did visa card update, Apple password change,

Clean up all interfaces in System Preferences > Network and sudo mv /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist

login to AppStore than iCloud,

but FaceTime and iMessage are not usable (message say please contact apple...)

 

when we see number of pages talking about iMessage issue on mackintosh (clover or chameleon)...

may be dev could work on this issue to make it work easyly a improvement of iMessage.debug... ;)

 

many contradictions can be read too :(

iMessage and FaceTime are not my priority but it use to work that the reason why i'd like to make it work again lol

 

I wish to all a good WE :)

 

update : i found that :

nav_m.gif Solving The Nvram Problem, Solved in Clover 2837+

#36

Share this post


Link to post
Share on other sites

My message was that there was a login problem, but not the contact apple problem. My research suggested that changing your ROM, MLB, or wifi card will result in your getting blacklisted by the apple servers and cause the message to say "please contact apple". The correction for which is to call them and ask for them to unblock you.

Share this post


Link to post
Share on other sites

iMessage information :http://www.projectosx.com/forum/index.php?showtopic=3298&st=120&p=41567&&do=findComment&comment=41567

it may be useful many information about this and all are not good quality

my information must be block by apple so i failed to repair (1st HD KO, 2nd HD OK)

 

Hope clover configurator dev will release a auto filled solution then i'll start for a new serial

Share this post


Link to post
Share on other sites

iMessage is dead, I can confirm that. Then I do have another issue with my SSD

 

 


And have a look at this ;)

 

post-6861-0-37018500-1409745075_thumb.png


tluck - are you preparing an updated bundle today? Otherwise I'll go and update clover just like that.

Share this post


Link to post
Share on other sites

Just posted a new bundle for Yosemite DP7 here: Clover UEFI on T420 Guide

 

03-September-2014 - 10.10 DP7/Beta Update

  • Clover updated to v2850
  • 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 (revised AppleHDA.kext and BroadcomBluetooth kext - are different than Mavericks or last DP)
  • Note: To make an Yosemite USB installer, just follow the 10.9 Mavericks method

 

Notes:

  1. screen sharing does weird things with the mouse. have to move mouse to dock or click on menu to show it after moving it out of screen share.
  2. @Cowboy Mike - i am getting the same (not accurate picture for my boot drive  (SSD) that shows inaccurate category amounts
  3. iMessage was dead (got can't use ID until you contact support message/error). So i put in the same MLB and ROM values from my real mac in the config.plist RtVariable section and it worked to register iMessage. not sure if one of both did the trick. my suspicion is it is all about the ROM value. but i have not tested this theory. (ran imessage_debug on my mac and then put the values in config.plist with Plist editor.)

Share this post


Link to post
Share on other sites

 

Just posted a new bundle for Yosemite DP7 here: Clover UEFI on T420 Guide

 

03-September-2014 - 10.10 DP7/Beta Update

  • Clover updated to v2850
  • 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 (revised AppleHDA.kext and BroadcomBluetooth kext - are different than Mavericks or last DP)
  • Note: To make an Yosemite USB installer, just follow the 10.9 Mavericks method

 

Notes:

  1. screen sharing does weird things with the mouse. have to move mouse to dock or click on menu to show it after moving it out of screen share.
  2. @Cowboy Mike - i am getting the same (not accurate picture for my boot drive  (SSD) that shows inaccurate category amounts
  3. iMessage was dead (got can't use ID until you contact support message/error). So i put in the same MLB and ROM values from my real mac in the config.plist RtVariable section and it worked to register iMessage. not sure if one of both did the trick. my suspicion is it is all about the ROM value. but i have not tested this theory. (ran imessage_debug on my mac and then put the values in config.plist with Plist editor.)

 

And for users that don't have access to a mac? Is there any hope in fixing imessage? My smbios looks quite empty :(

Share this post


Link to post
Share on other sites

Thanks for the guide. Everything worked on a first install with the 03-September-2014 release without modifications.

I have a T420i (4177-CTO).

I only had to turn the levels up in the MIDI sound utility to actually hear the internal speakers.

I won't be replacing the Intel (6300) Wi-Fi card, so I am using HoRNDIS for Android USB tethering.

 

EDIT: I guess the only issue is that I've had to disable hibernate (like some other people) because when trying to wake from hibernate it would get stuck on the screen with the apple logo and loading bar. The last bar segment never completes / gets colored. I have to hard power cycle and cancel hibernate from the clover spacebar menu.

Share this post


Link to post
Share on other sites

I just want to thank you tluck because with your gide i've been able to install mavericks on my T420 and everything is working fine. Now i want to install Yosemite, let me mention here that i don't use clover, instead i use the chameleon method. Everything works fine in Yosemite except audio, apparently the kext doesen't load. Can you help me out and give me a solution to the problem? Thank you!

Share this post


Link to post
Share on other sites

@d.u.o - i can't think of a good reason why the AppleHDA.kext would work for Clover and not for Chameleon. why won't it load for you?

 

you have you tried Clover say on a USB? it's very easy to use. I am running Yosemite DP7 on the latest release of clover.

Share this post


Link to post
Share on other sites

I guess i will give it a shot, just to see if the audio works with the clover installation. Thank you and I will get back with the result.

Share this post


Link to post
Share on other sites

Ok, so after countless attempts i've managed to install Yosemite using clover and updated to dp 7. Sound is working tluck, as you said, but only if I choose from system preferences the internal speakers as output and the headphones jack doesen't seem to work. The battery icon doesn't want to appear in the  menu bar. I ran into some problems because on my notebook I'm able to install os x only on a mbr formated drive, but i've managed to bypass the problem. Now I have to learn a little bit about Clover :) Any ideeas on sound output and battery icon? Than you for your hard work!

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 cvad
      Small tool to download, compile and build the latest Clover X64 package.
       
       
       

      The script inside is editable.

       
      Enjoy...
       
      Many thanks to the comrade SunKi for help with creating the script.
       
       
       
       
       
      Best thanks - click "Rate File".
       
    • 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






×