Jump to content
Kogen Mantis

Lenovo ThinkPad T420 with UEFI Only

4,616 posts in this topic

Recommended Posts

10 hours ago, Bugfix said:

My display is the AUO one:


28: None 00.0: 10002 LCD Monitor
  [Created at monitor.125]
  Unique ID: rdCR.xTjZCjuW0P3
  Parent ID: _Znp.L_qGQ0CawLB
  Hardware Class: monitor
  Model: "AUO LCD Monitor"
  Vendor: AUO "AUO"
  Device: eisa 0x213e 
  Resolution: 1600x900@60Hz
  Size: 309x174 mm
  Year of Manufacture: 2010
  Week of Manufacture: 33
  Detailed Timings #0:
     Resolution: 1600x900
     Horizontal: 1600 1664 1706 2010 (+64 +106 +410) -hsync
       Vertical:  900  903  906  912 (+3 +6 +12) -vsync
    Frequencies: 73.33 MHz, 36.48 kHz, 40.00 Hz
  Year of Manufacture: 2010
  Week of Manufacture: 33
  Detailed Timings #1:
     Resolution: 1600x900
     Horizontal: 1600 1664 1706 2010 (+64 +106 +410) -hsync
       Vertical:  900  903  906  912 (+3 +6 +12) -vsync
    Frequencies: 110.00 MHz, 54.73 kHz, 60.01 Hz
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #27 (VGA compatible controller)

 

yeah AUO1 LCD is inferior to LG. to fix the strecthing thing - make sure you have DualLink=1

Share this post


Link to post
Share on other sites
Advertisement
On 6/9/2019 at 2:32 AM, tluck said:

yeah AUO1 LCD is inferior to LG. to fix the strecthing thing - make sure you have DualLink=1

 

That did it! Thank you! Everything is working now. I'm using the config.EDID-2e2.plist without any changes other than the DualLink option.

 

Please add a note about this option to your guide. I'm sure it will help other people with the same issue.

 

 

For anyone wondering how to set DualLink to 1

 

Go to the Graphics section of your config.plist section and add:

 

<key>DualLink</key>
<integer>1</integer>

 

e.g.:

<key>Graphics</key>
<dict>
	<key>DualLink</key>
	<integer>1</integer>
	...
	...
</dict>

 

 

Thank you again! :thumbsup_anim:

Share this post


Link to post
Share on other sites

Well, I recall "mixed" results with Chris´s contributions in the other forum.

Anyway he took the time to try and gave credits to Dosdude etc.

Good to know HD3000 is not dead…Switching to English is maybe asking for too much. ;)

 

29954025_CatalinaBeta.png.5506444ad00e9ab7e0c2c4f4d918e776.png

Share this post


Link to post
Share on other sites
Posted (edited)

Hey guys,

 

I just wanted to try using macOS on my modded T420, since it's running pretty well on my desktop pc. 

 

T420 data: FHD-Panel (0HT622, AUO B140HAN01.3) I i5-2520M Intel HD 3000 8GB RAM

 

As for the display adapter (LVDS->eDP) I'm using this one: https://www.ebay.de/itm/LCD-controller-board-1920X1080-IPS-1080P-FHD-Screen-Kit-for-thinkpad-T430S-T420S/163082575437?hash=item25f87a9e4d:g:g8EAAOSwrCZbDLeu

 

With the help of the included guide in this thread I was able to install and setup macOS Sierra nearly in a perfect manner. But theres a small, but really drastic problem in my case since I upgraded my screen to FHD (it is so much better, trust me). Although it work's perfectly fine on Windows 10, I now got a problem in macOS with the screen I guess. 

 

I've tried nearly everything I can (being a beginner), but it just don't want to work properly. 

 

The situation right now: I can only operate the computer using and external monitor connected through the Displayport on the T420. The internal display remains dark, no matter what I do. It is definitely on, since I can see the backlight working, but it stays black the whole time. In macOS it is being recognized (as you can see in the pictures attached), even with the right resolution and settings. 

 

-Inject Intel, Inject the proper EDID, Duallink=0/1 doesn't solve the problem. 

 

That's why I'm desperately asking for help here. 

 

I've attached all the informations I have including my current EFI/config.plist

 

I would really appreciate your help! :)

LEN03.txt

 

EFI_now.zipScreen.pngsettings.png

Edited by D4Ci0

Share this post


Link to post
Share on other sites

Looks like a nice display hack!

From the specs, could it be your display is built in from factory e.g. with a T460 or similar Dell Skylake notebooks?

I that case, it might help to look at the display config of those HackBooks - I´m only guessing though.

 

Off topic:

How much did you pay for the IPS hack and how long did it take swapping the display?

 

 

Share this post


Link to post
Share on other sites
Posted (edited)

Yeah, it‘s basically a display for the T450(s), which is one of the best for 14” and besides that fits perfectly into the T420/T430 top cover. 

 

Changing the display is a 15 minute job, you just need to place the converter board somewhere behind the panel or in the connector area of the motherboard behind the keyboard. Price all in all somewhere 100-115€, really woth it. 

 

I’ve already tried copying some files in terms of the graphics from T450 EFIs, but they don’t really changed/patched that much, since the HD4000 onwards eDP connectors seem to be standard. 

 

I think trying a different SMBIOS would be a option (towards MBP Pro Retina 2012), but they are using HD4000 and Ivy-Bridge, which could be problematic? 

 

 

Edited by D4Ci0

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/24/2019 at 2:30 AM, D4Ci0 said:

Hey guys,

 

I just wanted to try using macOS on my modded T420, since it's running pretty well on my desktop pc. 

 

T420 data: FHD-Panel (0HT622, AUO B140HAN01.3) I i5-2520M Intel HD 3000 8GB RAM

 

As for the display adapter (LVDS->eDP) I'm using this one: https://www.ebay.de/itm/LCD-controller-board-1920X1080-IPS-1080P-FHD-Screen-Kit-for-thinkpad-T430S-T420S/163082575437?hash=item25f87a9e4d:g:g8EAAOSwrCZbDLeu

 

With the help of the included guide in this thread I was able to install and setup macOS Sierra nearly in a perfect manner. But theres a small, but really drastic problem in my case since I upgraded my screen to FHD (it is so much better, trust me). Although it work's perfectly fine on Windows 10, I now got a problem in macOS with the screen I guess. 

 

I've tried nearly everything I can (being a beginner), but it just don't want to work properly. 

 

The situation right now: I can only operate the computer using and external monitor connected through the Displayport on the T420. The internal display remains dark, no matter what I do. It is definitely on, since I can see the backlight working, but it stays black the whole time. In macOS it is being recognized (as you can see in the pictures attached), even with the right resolution and settings. 

 

-Inject Intel, Inject the proper EDID, Duallink=0/1 doesn't solve the problem. 

 

That's why I'm desperately asking for help here. 

 

I've attached all the informations I have including my current EFI/config.plist

 

I would really appreciate your help! :)

LEN03.txt

 

EFI_now.zipScreen.pngsettings.png

Hi

My computer is T420s Mod FHD display.  Same panel.

This is my config.plist. You can try.

Sorry all. the old config.plist is my X220.

The T420s/FHD config.plist

 

config T420s.plist

Edited by jenyunhuang

Share this post


Link to post
Share on other sites
4 hours ago, jenyunhuang said:

Hi

My computer is T420s Mod FHD display.  Same panel.

This is my config.plist. You can try.

 

config.plist

Thank you @jenyunhuang for your config.plist 

 

With @jenyunhuang config.plist there is a big step forward. The display is still recognized by Sierra, it shows a selection window for the internal monitors refresh rate. And there‘s backlight working according the adjusted brightness in the settings. So I can adjust the brightness on the go.

 

But there‘s still no image on the screen. It‘s still completely black.

 

I‘ve tried to copy&paste my EDID (we both have the same monitor - but different EDID, most likely because my monitor is an original/branded Lenovo one with Lenovos EDID. When I do so, backlight/brightness control isn‘t working like with my original config.plist. 

 

Still don‘t know how to solve this problem. Appreciate every help :)

 

 

 

Share this post


Link to post
Share on other sites
On 6/24/2019 at 7:42 AM, D4Ci0 said:

Thank you @jenyunhuang for your config.plist 

 

With @jenyunhuang config.plist there is a big step forward. The display is still recognized by Sierra, it shows a selection window for the internal monitors refresh rate. And there‘s backlight working according the adjusted brightness in the settings. So I can adjust the brightness on the go.

 

But there‘s still no image on the screen. It‘s still completely black.

 

I‘ve tried to copy&paste my EDID (we both have the same monitor - but different EDID, most likely because my monitor is an original/branded Lenovo one with Lenovos EDID. When I do so, backlight/brightness control isn‘t working like with my original config.plist. 

 

Still don‘t know how to solve this problem. Appreciate every help :)

 

are you using WhateverGreen.kext -- if so, maybe you can remove it to test.

you definitely need to inject an EDID to match the LCD: your EDID shows ProductID 40A3 vs jenyunhuang is 40E2 - so these are 2 different models. 

 

@jenyunhuang do you have the eDP adapter too? that could be different? the 1st frame buffer for HD 3000 MBP8,1 is set to LVDS vs eDP?

 

 

Share this post


Link to post
Share on other sites
Posted (edited)

@tluck Thank You so much for Your answer. 

 

I tried removing WhateverGreen.kext, didn't help. Setting platform-id to 0x12345678 didn't help too.

 

@jenyunhuang I'll just go out on a limb here and guess that his adapter is basically the same LVDS->eDP, because they're nearly identical from the outside perspective and as from I know through all the thinkpad-forums, these FHD-boards are the same. There are some differences between T420 FHD-boards and T420/ T430- WQHD-Boards though. 

The T420board is also sold from the same seller that I bought mine from on eBay.

 

Strangely with his config.plist I get backlight (and backlight control in Sierra) on the internal screen which I don't get when using my EDID in his config.plist or using "my" config.plist. Since 3 hours im figuring out on how to edit the AppleBacklightInjector.kext in the EFI under "ApplePanels", where all the "F10Txxx"-listing are, to enable backlight with my EDID at least and from there on work further.

 

My current ioreg status:

 

T420:~ nutzer$ ioreg -l | grep ApplePanel
    | |       "ApplePanels" = {"F10T0366"=<00110000008c00d80136018f01fe02a3034503e704c70535075a091c0b130d9b10591312>,"F10T159e"=<00110000001c002c003f00510068008a00ab00cc00fa0135018101dd024402c9035903e8>,"F10T02e3"=<00110000008c00d80136018f01fe02a3034503e704c70535075a091c0b130d9b10591312>,"F10T11ed"=<00110000004f007a00b000e30122017f01db023802b7035a042e052e064c07bc094b0ad8>,"F10T050b"=<00110000001c002c003f00510068008a00ab00cc00fa0135018101dd024402c9035903e8>,"F10T02e2"=<00110000008c00d80136018f01fe02a3034503e704c70535075a091c0b130d9b10591312>,"F10T213e"=<00110000008c00d80136018f01fe02a3034503e704c70535075a091c0b130d9b10591312>,"F10T313c"=<00110000008c00d80136018f01fe02a3034503e704c70535075a091c0b130d9b10591312>,"F10T40e2"=<00110000008c00d80136018f01fe02a3034503e704c70535075a091c0b130d9b10591312>}

and:

T420:~ nutzer$ ioreg -l| grep -i yEDID
    | |   | | |       "IODisplayEDID" = <00ffffffffffff0030aea340000000000c190104951f1178ea8545a45a54a1270c505400000001010101010101010101010101010101293680a070381f403020350035af1000001e0000000000000000000000000000000000000000000f00d1093bd1093b1e0a0006af3d12000000fe004231343048414e30312e33200a0036>
    | |   | | |       "IODisplayEDID" = <00ffffffffffff000469c324ef7700000a17010380341d782a2ac5a4564f9e280f5054b7ef00d1c0814081809500b300714f81c08100023a801871382d40582c450009252100001e000000ff0044334c4d54463033303730330a000000fd00324b185311000a202020202020000000fc004153555320564e3234370a2020019c020322714f0102031112130414050e0f1d1e1f10230917078301000065030c0020008c0ad08a20e02d10103e9600fd1e11000018011d007251d01e206e285500fd1e1100001e011d00bc52d01e20b8285540fd1e1100001e8c0ad090204031200c405500fd1e11000018000000000000000000000000000000000000000000d9>

So my EDID is recognized correctly as I from what I see and think. 

 

When I watched the internal display while using the notebook, here and there I saw some white little lines/point flashing for milliseconds. 

 

What is the 1st framebuffer, something I could change?

 

Call me "dumb". Reading @tluck guide with 2 open eyes would be better than with only one. Patched the AppleBacklightInjector, et voila

 

 

 

Edited by D4Ci0

Share this post


Link to post
Share on other sites
Posted (edited)
10 hours ago, tluck said:

are you using WhateverGreen.kext -- if so, maybe you can remove it to test.

you definitely need to inject an EDID to match the LCD: your EDID shows ProductID 40A3 vs jenyunhuang is 40E2 - so these are 2 different models. 

 

@jenyunhuang do you have the eDP adapter too? that could be different? the 1st frame buffer for HD 3000 MBP8,1 is set to LVDS vs eDP?

 

 

@tluck Sorry, post the config.plist is for my X220. Yes, T420s/T420 mod FHD must need the LVDS to eDP adapter board. So, I have the edp adapter on my T420s. The T420s mod fhd productID is 40A3 (It is define by LVDS to eDP board, not LCD panel). The 40E2 ID is my other computer(X220 ips panel, original machine, original Lenovo X220 panel) . My two computer can use you config.plist but need change the CsrActiveConfig value and inject the EDID. So no more change.

 

@D4Ci0 Sorry, the config.plist is my X220. This is my T420s whole EFI file

 

efi.zip

Edited by jenyunhuang

Share this post


Link to post
Share on other sites

pain and the neck to reach to 10.4.5 via the last OS X installer :( on and HD (HFS+)

 

must apply dudepatch, MBR patch?? pff

 

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 Pentothal.Z
      Hello all,
      I have a working hackintosh....ok.....but it takes a lot to boot and according to the boot.log there are a few problems.
      One of them is a black screen that stays on for a long time.
      I would like to ask anyone in this community some help to fine tune my machine.
      Boot.log and config.plist attached


      Any help would be appreciated.
      bootlog.txt
      config.plist
    • By metaphysician
      hi folks! i'm just checking for opinions here on a Clover based install of High Sierra. currently i can't boot directly from the internal drive on my hackbook, an ASUS ROG GL502-VS laptop (with the replaced WiFi card), though i can boot from the USB bootloader/installer

      i installed 10.13.6 fine using a prepared vanilla installer on HFS+ (not APFS), but my configuration is somewhat unusual. i have two drives. the first SSD has the Windows system, the second has two partitions with the 2nd partition holding the macOS system. when i ran Clover installer i could not use the UEFI option to copy to the EFI partition because it couldn't find one on that drive. so it installed the EFI folder on the root of the macOS partition instead.
       
      however, after a bit of tinkering around, i found out that there is an existing EFI partition on the primary drive called SYSTEM. it has a EFI folder and underneath that is a Windows folder, a Boot folder, and one called APPLE. i can mount this partition with Clover Configurator and copy files to it, but i don't know if this is a good or risky solution. i was thinking i would manually copy the CLOVER folder and the uefi64.boot file to this partition , making sure not to overwrite anything existing. using the UEFI setup, i can create a boot path from the SYSTEM partition to the Clover boot file, but i'm just curious if this is a useful solution or not, and i don't want to ruin the existing Windows 10 installation for sure. any advice appreciated!
    • By Slice
      OK, 4988 released.
      Now, @vector sigma, what have we do to update translations?
    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By 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.
      UPDATE macOS Catalina Beta DP3_19A501i:  For Catalina, @jpz4085 has made an automated batch file to create a Catalina VM in Windows with iMac 14,2 SMBIOS.  You can still use my macOS_iso_creator.tool on page 5 to make an installer ISO to attach to the VM.
       
       
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
×