Jump to content
Kogen Mantis

Lenovo ThinkPad T420 with UEFI Only

4,393 posts in this topic

Recommended Posts

hi, i'm been following this thread since the star, but never reply so hi to all. i'm having lots of troubles installing. i try 10.8 using clover but i have a quadrant display problem so i try 10.9, i was succefully installing 10.9 using chameleon bootloader(it was imposible to boot with clover) but now i'm stuck, the post install wont boot it gives me a fail loading drivers CPUID kernel panic so a bit of help would be much apreciated. oh i also copy all clover boot files from the clover bootable ISO (including clover replace patch from #486) from a linux distro to the EFI partition in the HDD so i think that is the same to actually install clover, or not? i'm a bit lost with the ketx maybe i did all wrong. specs: t420 4236NUS i5 2.9 8GB RAM/HD300/SSD 512GB

Share this post


Link to post
Share on other sites
Advertisement

Hi!

 

Don't know if my question is offtopic here, but I'm a bit frustrated.

 

I want to update to Mavericks from 10.8.3. If I start the installer and choose my OS_X hard disk partition, the installer tells me, my partition is not guid. So I have to cancel.

To change the partition to guid isn't easy, because on this hard disk is also my Win-Partition and the Recovery from Lenovo. I mustn't loose them...

Is there an Option to Update with the normal Update and changing the Kexts?

 

So I tried to make a bootable USB-Stick like the first time installing ML. But every Guide and every Tool (myHack, DiskMaker X) I use ends with the same Problem: I can't boot from the Stick. I choose it by the Lenovo-Bootmanager (F11 while starting) - the monitor change to black and returns to the Boot-menu.

If I want to use my Chameleon-Boot-Loader, the USB-Stick is not shown.

Changed the USB-Stick. No Effect...

 

So I think I make a 'Master-Mistake' by preparing the USB. Here's my doing:

- Partitioning the USB-Stick to a new Patition 'MAC OS extended' - Option 'GUID'

- starting DiskMaker X ... waiting

- restarting - no USB-Stick will be found.

 

My config: T420, 3 Partitions (Recover, Win7, OSX), Chameleon Bootloader

 

Is there help for me? Another Guide which explains for super-idiots?! ;-)

Or do have I to use in future Win95? ;-)

 

Thanks in advance!!

Greetings, Synymy

Share this post


Link to post
Share on other sites

@amar0 - i just repackaged the zip in #486 that may make it easier for you to make a 10.9 installer. the top level DSDT is a bit more generic so it will work with either low or high resolution LCD. 

 

@Snynymy - i have switched to GUID in general. if you have a 2nd disk - install to GUID disk and then use Carbon Copy to move it to your MBR disk. thats how i used to do it! 

  or here is a link that may be of interest to you. Mavericks MBR patch 10.9 GM (13A603)

Share this post


Link to post
Share on other sites

Thanks to Kogen Mantis, Tluck et al. I now have a fully functional 10.8.5 install. No bluetooth but replaced the wifi card. I have never been happier. Thanks

 

 

bluetooth should be fixable by either replacing or editing: BroadcomBluetoothHostControllerUSBTransport.kext (v4.1.7 with patched Info.plist from 10.8.5) - adds ProductID 8575 to make BT work! Put/replace one in /S/L/E/IOBluetoothFamily.kext/Contents/PlugIns

 

For me I didn't have built-in bluetooth, but buying and installing this USB adapter fixed my wifi with no drivers needed at all:

 

http://www.amazon.com/gp/product/B007GFX0PY/ref=oh_details_o03_s00_i01?ie=UTF8&psc=1

 

Also, wifi works perfectly but needs some software with this adapter:

 

http://www.amazon.com/gp/product/B003X26PMO/ref=oh_details_o03_s00_i05?ie=UTF8&psc=1

Share this post


Link to post
Share on other sites

Now that my hackintosh is working perfectly I am of course teetering on the edge of futzing with it some more. Wanted to see if anyone else had any experience using one of the UltraBay hard drive adapters?

 

I was curious about installing the original HDD back in the ultrabay (I am using a 128gb SSD as my main drive) and doing a Windows Install as an alternative.

 

Also for dual boot any method I should use in particular? In the past I always did boot camp and then installed Parallels configured to my boot camp partition because this gave me the best flexibility with both dual booting and virtualization.

 

Any general tips?

Share this post


Link to post
Share on other sites

@tluck thank you, i tried again but i'm still not able for boot i keep having this problem "AppleACPIlataformExpert::start failed" and a kernel panic. i'm really frustated i try almost every solution posted in this thread unsuccefully. what it could be?

Share this post


Link to post
Share on other sites

@amar0 - well can you explain what step you are at and what you did so far.

 

does the installer work without "quadrants"?

is this KP from the installer or after the install?

did you replace the EFI contents with the zip stuff?

which config.plist and dsdt are you using?

did you rename the OEM folder or are using the top level config.plist?

did you rename OEM folder?

did you copy the kexts to your HD?

did you turn off VT-d Virtualization?

what bios version are on?

Share this post


Link to post
Share on other sites

Good find, @tluck

descriptor 1:    bc 1b 56 84 50 00 16 30 30 20 14 00 35 ae 10 00 00 1a

mine actually was proper already, but i've spent like good couple of month adjusting frequencies in SwitchResX back in the day before I ended up with an EDID that wouldn't glitch the screen.

Share this post


Link to post
Share on other sites

@tluck

great news :)

tested under 10.8.5, 10.9 under 1366x768 and upper ;)

with success

 

i did not have much problem in the past with my EDID but this improuvment is welcome to get rid of this problem

Thanks again

Share this post


Link to post
Share on other sites

@amar0 - well can you explain what step you are at and what you did so far.

 

does the installer work without "quadrants"?

is this KP from the installer or after the install?

did you replace the EFI contents with the zip stuff?

which config.plist and dsdt are you using?

did you rename the OEM folder or are using the top level config.plist?

did you rename OEM folder?

did you copy the kexts to your HD?

did you turn off VT-d Virtualization?

what bios version are on?

thank you again @tluck !!

Ok i re-install from scratch

i made a chamelleon USB installer for 10.9, install was perfect no display problems and it finish all right.

after that i install clover in a USB, apply the patch from #486 (the one uploaded today)and when i try to boot from USB nothing happens it doesn't boot, so i "install"(copy all the files to the EFI Folder)  clover to the EFI partition using a linux distro, after that i was able to enter main screen of clover. When  i select boot the OSX on OSX  i get this (picture attached), so i'm a bit of stuck i can't figure out what is wrong. so resuming your questions:

installer quadrant=no

KP= after install

EFI from zip=yes

Config.plist= i change the name in OEM folder (low screen 1333xetc..) for match my model  (4236NUS i5 1366x768)

Rename OEM folder= yes

kext= i can't copy the kext to HD because i can boot OSX, and from the linux distro i can write to HFS+ Journaled so, dont :/

VT-d= Off

Bios=1.4

PS: i dont know about dsdt, i just use the clover and your patch, i'm i missing something?

 

DSC_1478.jpg

 

Share this post


Link to post
Share on other sites

PMPatch of Powermanagement.kext is actually not well working on Mavericks. It seems to me, that this is a common problem for devices without pmpatched bios.

If you can not get a pmpatched bios for your lappy or patch it by yourself, you can boot from your usb installer and try to copy for now nullcpupowermangement.kext with terminal to S/L/E of your installed hd partiton. Don´t forget to repair permissions. Afterwards boot with flags -f v.

 

Have fun.

Share this post


Link to post
Share on other sites

@anarch99 - you will get ethernet if you installed the AppleIntelE1000e kext ... but wifi AFAIK is only works with modded bios and then you replace the intel wifi with the mini express card. the  bottom slots will not work for wifi. for wifi, i use a USB wifi.

The WWAN slot is also capable of hosting wifi cards. I did this briefly, for kicks, with a card from an old hackintosh. However, there isn't a way to connect a wifi antenna, so the signal strength will probably be much weaker. You need to install the bios mod regardless of where you install it (this is very easy, mostly safe, and probably covered by your warranty if you manage to mess up). New wifi cards can be found for less than $15 with shipping. I've heard there are USB wifi cards in the mini-pcie form-factor -- these could be used without the bios patch. Personally, I like my native wifi support (it supports AirDrop and gets much better speeds and signal coverage then the AirLink that I originally purchased).
 

Finally, the folder I am supposed to rename is "4236Y33" correct? The question is, how do I know what to rename it properly? Where do I find the appropriate string?

The string is on a sticker on the bottom of the laptop.

 

 

Now that my hackintosh is working perfectly I am of course teetering on the edge of futzing with it some more. Wanted to see if anyone else had any experience using one of the UltraBay hard drive adapters?

 

I was curious about installing the original HDD back in the ultrabay (I am using a 128gb SSD as my main drive) and doing a Windows Install as an alternative.

 

Also for dual boot any method I should use in particular? In the past I always did boot camp and then installed Parallels configured to my boot camp partition because this gave me the best flexibility with both dual booting and virtualization.

 

Any general tips?

I do this. It works great. I'm thinking of buying an SSD as a third drive (in the WWAN slot) and making it my system partition. The boot camp wizard obviously doesn't work, but you can install windows the normal way. I turn off UEFI in bios before installing windows to ensure it uses MBR, so that it works with VMware. However, the virtualization environments are starting to support EFI, so your milage may vary.

Share this post


Link to post
Share on other sites

@amar0 - i just repackaged the zip in #486 that may make it easier for you to make a 10.9 installer. the top level DSDT is a bit more generic so it will work with either low or high resolution LCD. 

 

@Snynymy - i have switched to GUID in general. if you have a 2nd disk - install to GUID disk and then use Carbon Copy to move it to your MBR disk. thats how i used to do it! 

  or here is a link that may be of interest to you. Mavericks MBR patch 10.9 GM (13A603)

 

Just reposted the zip file here: Clover UEFI on T420 Guide - revised the instructions a bit - hopefully it will make sense for first timers.

 

- Tetonne reminded me to actually include  HFSPlus-64.efi !!!

@tluck...i cant download...always disconnect, pls re upload on other site. Thanks you tluck :)

Share this post


Link to post
Share on other sites

@T430(i) users

 

There is a new UEFI for T430, T430i that might address some issues:

From the 2.57 readme:

<2.57>
 UEFI: 2.57 / ECP: 1.12
- (Fix) Fix an issue where the system fail to boot from from USB device by 
        configuration.
- (Fix) Fix an issue where WMI interface has incorrect message.
- (Fix) Fix an issue where the mouse pointer was moved when the LCD panel was
        closed.
- (Fix) Fix an issue where the system could not resume from sleep state.

I never encountered the USB issue. It might be under W8 when you use the advanced menu to restart from a specific device. I did encounter the WMI error in W7 and W8. Event viewer would pop a WMI warning every few minutes. Harmless, but annoying. I'm wondering if it would manifest in OS X as an SMC error. Like the one's we've seen when installing or booting. The mouse pointer thing was really annoying. When you have the laptop docked with the lid closed, if you'd set your coffee over where the touchpad or trackpoint is, you would sometimes get a mouse click or the pointer moving. Got a lot of complaint about this one. The interesting one is this sleep fix. I'm hoping it doesn't break anything else. But more importantly, how does it affect/improve our sleep issues in OS X?

 

A word of caution:

if you've already updated past UEFI v2.50, you cannot rollback to earlier than v2.50. And with this new update, 2.57, if you update to it, you won't be able to rollback at all.

 

I know some of us are still on a really old UEFI because it's the only one that it whitelist patched, but I did read somewhere that the modern UEFI's from Lenovo can be patched, but it has to be performed on your own dump. Something about signatures or serials, or somewhere else that claimed new Lenovo UEFI updates are only partial/incremental/incomplete UEFI's. I don't understand it at all, but I get the feeling you can't use someone else's patched UEFI past a certain version. If someone has any information to share on whitelist patching modern Lenovo UEFI's, I'd really appreciate it.


I also have VT-d enabled in UEFI v2.53 (I think, need to check version) and have no problems installing or booting.

g1uj25uc.txt

Share this post


Link to post
Share on other sites

@amar0

 

- you are getting close. but it seems you have not followed my guide closely. it seems you got OSX installed on the HD but the reason you can't boot is there are no custom kexts (FakeSMC etc) used during the boot from the HD.

 

to fix this. boot from the USB you installed from. then follow the instructions to install Clover in the ESP of the HD. Don't rename OEM until you can boot from the top level and get all the kexts on the HD /S/L/E from /EFI/Clover/kexts/10.9 - pay attention to where each of these need to go.

 

to make a Clover USB - 

if it is MBR formatted, will be a single partition typically. Use the clover installer to install the boot loader in the MBR with non UEFI options

if it is GUID formatted, this will have 2 partition typically. ESP is 1st hidden one. use the clover installer to install stuff in ESP

 

in either case - 

replace /EFI/CLOVER with the zip contents - don't match OEM to your product YET!!!

 

@Manwe150

 

- thanks for info around modded Bios and wifi. which min-pci-express card to you use/recommend. i think i saw a link to mod-bios 1.46. currently i use USB (can get around 144 mbps r/w)

 

yeah windows can be a bit tricky. my main HD is dual boot OSX/Win7 - both are UEFI. clover is really good at manage this - /EFI/Clover vs /EFI/microsoft. but both are present in Clover GUI. native boot for either one on 1st disk. (i rarely use this windows instance anymore!)

 

SO i took a different approach for VM, i use Fusion 5 and i prefer to keep my VMs on a 2nd disk MBR formatted.  my VMDKs (C and D drives etc) use physical disks, so i can read these from the VM or when I native boot windows. 

 

/Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/disk1 1 "Disk1" ide

/Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/disk1 2 "Disk2" ide


@styrian - what is this pmpatch issue all about? not sure i understand the problem here?

Share this post


Link to post
Share on other sites

@tluck thank you!! Very much Men, i finally have a functional osx running great!! Thank you Very much for the help. Now i'm gonna make some testing to ser if everything is Ok. I only have 1 remaining question with thi part "If you have 1366x768 LCD, you can probably just use items as is - that is rename OEM/ProductID.1366x768 folder to match your product name. Note: if you have similar CPU as i5-2520, the SSDT.aml from above may work for you (copy from ProductID/ACPI/patched)"

where i have to Copy the dsdt.dsl?

Share this post


Link to post
Share on other sites

 

SO i took a different approach for VM, i use Fusion 5 and i prefer to keep my VMs on a 2nd disk MBR formatted.  my VMDKs (C and D drives etc) use physical disks, so i can read these from the VM or when I native boot windows. 

 

/Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/disk1 1 "Disk1" ide

/Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/disk1 2 "Disk2" ide

@tluck

i'm also interested to use VM on a real partition and to be able to use it as a native boot windows.

In the past on my mini 311c i try to do that without success so i've delete the win partition. (Mac OS X boot only)

your post makes me want to try again :)

 

i'll take all your advice to do so. :)

Share this post


Link to post
Share on other sites

@amar0

you are welcome. since you have the same CPU as me you can use the SSDT from the ProductID.1600x900 folder. just move ssdt.aml to your 

OEM/4236NUS/ACPI/patched folder. 

 

@tetonne - i am no expert with vm, but there are several options for Fusion. physical disks: whole disk, a partition of a disk or virtual disks (a disk in a container).

i suspect most will do VM containers as they are easy and transportable. for windows, i wanted to use physical disk so i can read the data from either a VM guest or a physical host. its been so long since i did this but i remember I had some conflicts with GPT disks and Fusion. the issue is the MBR vs PBR. Fusion seems to need/use the MBR of (either a MBR or GPT disk) to figure out partition boundaries. i recall mac diskutility will convert the PBR to MBR when you create a windows (NTFS or exfat) for bootcamp etc.  but its been so long i don't remember the details but this messed something up for me. i had to dd the PBR back in place. my config is a bit complicated.

 

bottom line: if you want use physical disks for VMS, i suggest a 2nd disk that you can format and experiment with. the vmware-rawdiskCreator command line tool is for creating physical vm disks - there isn't a nice GUI interface like on windows. here some examples

5 disks in the VM

 

disk 1 partition 1 and 2 (happens to be on a MBR disk)

disk 2 partition 3 and 4 (happens to be on a GPT disk)

disk 3 whole disk 

 

you can use ide or scsi

 

 

/Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/disk1 1 "Disk1" ide

/Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/disk1 2 "Disk2" ide

/Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/disk2 3 "Disk3" lsisas

/Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/disk2 4 "Disk4" lsisas

/Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/disk3 "fullDevice" "Disk5" lsisas

 

Share this post


Link to post
Share on other sites

Hi guys, Clover question:

While upgrading to the latest gm of Mavericks, I downloaded the Mavericks upgrade app from the App Store and tried to run it directly. This made the computer restart and a new Clover boot option showed up, something like "Install Mavericks from Mac SSD". I upgraded properly later on, by creating an install USB following tluck's guide, so the upgrade went okay.

The issue is that the entry to Install it is still there, also there is another one to boot from recovery partition.

 

How do I get rid of this new entry? Where are these entries stored?

 

Thanks,

AJ

Share this post


Link to post
Share on other sites

Clover boot options are probed. Meaning that for any given option there exists a partition with an OS on it. This also includes attached devices, so if you have OSX installed to your HD and you still have your thumb drive plugged in at boot, you will see boot options for your thumb drive as well.

 

So if you're seeing extra boot options then you have that many partitions with bootable OS's on them.

The clover config allows you to hide certain types and specific partitions, but more likely you want to actually remove the extraneous partitions and reclaim the space.

Share this post


Link to post
Share on other sites

@AJ 

 

1)  /.IAbootfiles  or something like this is created by the installer on the OS partition you were upgrading by the Install OSX.app ...  if you have HFSplus.efi vs Vboxhfs.efi in your clover drivers folder, then clover can boot from this installer bundle upon reboot. (just like a real mac)

 

since you aborted the install process by not restarting using this bundle, you can get rid of this folder now.

 

2) the installer will create (or update) the recovery partition - which is a 650MB partition on your OS HD. ( i would keep this.)

Share this post


Link to post
Share on other sites

 

i may have figured out why some LCDs are glitchy on HD3000. i looked at 4 good EDIDs (2 real macs, 1 HP, and 1 EDID for my LCD that works) and they have some things in common in the detailed timing section. using an EDID (view sonic) i could see that they all have Sync Offset=48 and Sync Pulse Width=32. So i edited my original EDID and modified these to values to match (which were way off) ....  

guess what? that one worked too without glitches or hangs. anyway... we have a good EDID for 1600x900 and here is one for low-res - possibly:

 

so if anyone is interested in trying this this to remove glitches for 1366x768 LCD (i edited tetonnes) which had sync offset=38 and sync pulse width=22

 

this one below encoded for clover which has the values of  48 and 32 instead of 38 and 22 respectively.

 

put this in your clover config.plist (replace current graphics section)

 

       <key>Graphics</key>

        <dict>

                <key>Comment</key>

                <string>LCD 1366x768</string>

                <key>CustomEDID</key>

                <data>

                AP///////wAGrzwxAAAAAAAUAQOAHxF4ChC2l1hXkiYeUFQAAAABAQEBAQEB

                AQEBAQEBAQEBEhtWRlAAIzAwIDYANa0QAAAYAAAADwAAAAAAAAAAAAAAAAAg

                AAAA/gBBVU8KICAgICAgICAAAAAA/gBYWFhYWFhYWFhYMSAKACM=

                </data>

                <key>DualLink</key>

                <string>0</string>

                <key>Inject</key>

                <dict>

                        <key>Intel</key>

                        <true/>

                </dict>

                <key>InjectEDID</key>

                <true/>

        </dict>

Original:

attachicon.gifScreen Shot 2013-10-31 at 2.17.55 PM.png

Revised: (note 2 values changed on line 60)

attachicon.gifScreen Shot 2013-10-31 at 2.17.25 PM.png

 

I have an hp with 1600x900 and in the original seems to have already that 303020 and i have glitches with clover, so i think this is not real solution

Share this post


Link to post
Share on other sites

Take 2: 

 

took another look at this ... my first attempt at understanding why 1 EDID works and the other does not  by changing sync offset width, pulse etc failed - it eventually hung.....

 

BUT what makes my built-in EDID work without glitches? - it is the panel size!!! i this new EDID tested on 10.8.5 and 10.9.0 by changing the panel size from 309x174  to 310x174 -- and i can NOT make it hang or glitch. this, i believe, is it. 

 

the one below that i obtained from Kogen is/was 310x174 panel size - so i matched my built-in to the same size changed 309 to 310 - Note: the pixel clock in built-in EDID was 110MHz vs 96Mhz along with other param diffs -  but that does not seem to matter. all the ways i know to make it hang (which is pretty easy to do with mission control on/off about 3-4 times or moving safari between monitors) fail to hang it up. 

 

@Yum - yeah i agree, it does seems to be a bit more that just that. it may be that + pixel clock -- the ones that work have plus other timings ... which affects vertical frequency. Have you tried injecting the 1600x900 EDID i posted that is glitch free? this one works:

 

 

00FFFFFF FFFFFF00 30E4E202 00000000 00140103 801F1178 0A434597 59578E28 21505400 00000101 01010101 01010101 01010101 01018025 40806084 1A303020 350036AE 10000019 00000000 00000000 00000000 00000000 00000000 00FE004C 47204469 73706C61 790A2020 000000FE 004C5031 34305744 322D544C 42310038 

 

        <key>Graphics</key>

        <dict>

                <key>Comment</key>

                <string>LCD 1600x900</string>

                <key>CustomEDID</key>

                <data>

                AP///////wAw5OICAAAAAAAUAQOAHxF4CkNFl1lXjighUFQAAAABAQEBAQEB

                AQEBAQEBAQEBgCVAgGCEGjAwIDUANq4QAAAZAAAAAAAAAAAAAAAAAAAAAAAA

                AAAA/gBMRyBEaXNwbGF5CiAgAAAA/gBMUDE0MFdEMi1UTEIxADg=

                </data>

                <key>DualLink</key>

                <string>1</string>

                <key>Inject</key>

                <dict>

                        <key>Intel</key>

                        <true/>

                </dict>

                <key>InjectEDID</key>

                <true/>

        </dict>

Edited by tluck

Share this post


Link to post
Share on other sites

@Yum - yeah i agree, it does seems to be a bit more that just that. it may be that + pixel clock -- the ones that work have plus other timings ... which affects vertical frequency. have you tried injecting the 1600x900 EDID i posted that is glitch free? this one works:

 

00FFFFFF FFFFFF00 30E4E202 00000000 00140103 801F1178 0A434597 59578E28 21505400 00000101 01010101 01010101 01010101 01018025 40806084 1A303020 350036AE 10000019 00000000 00000000 00000000 00000000 00000000 00FE004C 47204469 73706C61 790A2020 000000FE 004C5031 34305744 322D544C 42310038 

 

        <key>Graphics</key>

        <dict>

                <key>Comment</key>

                <string>LCD 1600x900</string>

                <key>CustomEDID</key>

                <data>

                AP///////wAw5OICAAAAAAAUAQOAHxF4CkNFl1lXjighUFQAAAABAQEBAQEB

                AQEBAQEBAQEBgCVAgGCEGjAwIDUANq4QAAAZAAAAAAAAAAAAAAAAAAAAAAAA

                AAAA/gBMRyBEaXNwbGF5CiAgAAAA/gBMUDE0MFdEMi1UTEIxADg=

                </data>

                <key>DualLink</key>

                <string>1</string>

                <key>Inject</key>

                <dict>

                        <key>Intel</key>

                        <true/>

                </dict>

                <key>InjectEDID</key>

                <true/>

        </dict>

Now i try to inject all this edid

It doesnt work buddy, glitches everywhere. I always thiought that these glitch are not edid linked honestly, i have tried everything for this but nothing work. only on chameleon and smcping i am well, on clover always glitch

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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



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

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

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

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

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

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

       
       
       
      And now photos of the installer
       
       
       

       
       

       
       
      Above is an image of the Installer log, (the main pop up window loads from about 10 mins and stops arbitrarily at 2 minutes left, every time) of the nearly hundred attempts i have made, this is the final screen i get, pretty much no matter what i do.
      Sometimes the the order of what it says is different , but the main things of interest are:
       
      "Target is not convertible to APFS: This volume is not formatted as Mac OS Extended journaled."
      "Warning: Couldn't find Board ID, Chip ID, & ECID in new namespace, falling back"
      "Unable to get fs for null"
      " NO native mechanism to verify Applediagnostics.chunklist"
      " NO native mechanism to verify Installfa.plist"
      " NO native mechanism to verify Basesystem.dmg"
      " NO native mechanism to verify AppleDiagnostics.dmg"
      " NO native mechanism to verify InstallESD.dmg"
      " NO native mechanism to verify Basesystem.chumklist"
       
      I have tried many many ... many .. different combinations of kexts, drivers, copies of clover, forks of clover - different copies of drivers and kexts from different sources.. including from all the official repositories.
       
      * I am not trying to install with APFS - the drive i am using is a spinning HDD - so i don't understand the first line quote above.
      * I am using a usb2 slot - there is only two on this machine - 1- usb2 and 1- usb3
      * As you'll see in the Clover folder i'm using APFSdriverloader. - so the installer should detect the installer-APFS-thing - and see it should be HFS+ ?? no?
       
      I'll detail the procedures:
       
      I wiped the Target HDD drive with a live linux USB.
      i prepair the USB with Createinstallmedia method, install clover to the EFI on usb, load kexts and drivers (I've been recently attempting with the Plist from a 'certain other site' Ton*****86) As it has the dvmt preallocation patch and other bits - i'm of course open to ANY other files/pLists .. this is just the one i've been experimenting with lately.)
      Add ' -v ' in clover options to see the verbose output
      in the installer (acts sketchy sorta, delayed and sluggish) i use DiskUtility to erase the drive 'Macos extended journaled'
      Make initial selections, agree to license and begin install.
      it proceeds to 2 minutes left every time, and hangs. many times i've left it for hours, and even overnight.
      I'm honestly not kidding, it's nearly 100 times ive' tried this, i've downloaded high sierra from the app store 5 times to rule out that, i've used countless combinations of everything .. i'm almost completely burned out.
       
       
      If anyone can shed some light i'll be VERY thankful!... I'm ready to go in a completely new direction...please please please help
       
      I'll put the Clover in the next post because i ran out of space in this one......
       
       
       
       
       
       
       
      Here is the latest clover i've been using, with the preboot, and DSDT/SSDT (F2 & F4) in it.
       
      CLOVER-Oct15.zip
       
      Thank you very much for ANY help you can provide
    • By tluck
      Lenovo T460 macOS with Clover Guide
      Release v2018.10.12 on GitHub Updated to Clover r4703 Updated Kexts SSDT updates for T460 Added Frank's T470p DSDT files Added T470 DSDT
        Various Tweaks over Last months The zip file is a complete Clover ESP (/EFI) bundle and kext pack for the Lenovo T460. The current file bundle is tested on Sierra. 
      Note: I never got the GFX fully working on El Capitan. 
      Full Clover file set - config.plist etc. Includes all custom kexts Includes custom DSDT/SSDT scripts and patches Utility scripts The zip bundles are posted to GitHub: https://github.com/tluck/Lenovo-T460-Clover/releases
      Caveat: The T460 systems used here was configured with: i5-6300U, Intel HD Graphics 520, 1920x1080 touch screen. If you have a different system model, then extract the ACPI files and use the included scripts to create a set of files consistent with your system type and BIOS version. See below for details.
      Credits: RehabMan, Shmilee, vusun123, TimeWalker, Mieze from which, much of their work and help is/was was used to get the T460 to this point.
      Devices and aspects working:
      Ethernet -  Intel I219LM is enabled via IntelMausiEthernext.kext WiFi/BT - substitute the Intel WiFi/BT with a compatible Broadcom or Atheros chip Audio - ALC293 codec implemented via AppleALC.kext (old AppleHDA_ALC293 and CodecCommander kexts are not needed) PS2 - ClickPad + TrackPoint + all 3 buttons - using a modified VoodooPS2Controller to support new layouts - and added some custom Fn key maps based on 440/450 dsdt USB - implemented via custom SSDT + USBInjectAll kext. All USB3/USB2 ports are intel-based and work -  3 external USB and internal Camera, BT, etc  Sleep/Wake - the sleepwatcher package and custom sleep/wake scripts are used to help with sleep/wake for BT and PS2 devices. Note: have not tried to implement the SD card reader - no driver found.
      ACPI Files
      New Installation - Steps and Details
      Part 1 - OS Installation
      Part 2- Post OS Installation and Setup
      Notes on Custom Kexts
       
    • By gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

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






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