7.1.1
I also got a Yoga 720 15", but model 720-15IKB (80X70041GE), with these slightly different specs:
CPU: i5-7300HQ
SSD: 256 GB
GPU: NVIDIA GeForce GTX 1050 2GB
I tried a whole day but gave up. The whole install-boot situation was very instable and a question of luck instead of a deterministic reproducable situation, like computing normally is. (I have more than 25 years of IT and hacking experience). The furthest success I had, was getting through the installer-booting process in verbose mode, arriving in GUI mode and getting stuck in the screen which shows visual instructions to "attach a bluetooth mouse and activate it".
I'd appreciate detailed help. I for one provide in detail what I have attempted so far:
- Sometimes the USB 3.0 HDD installer boot disk showed up in the F12 boot menu, sometimes not. (Ok, this is a timing problem, but still annoying).
- I used a HDD, which holds multiple bootable OS installer partitions, among them a 10.12.6 and a 10.13.4, both created with UniBeast. But of course there's only one EFI partition. So I later erased EFI and both macOS bootable partitions, and installed only one of them, to rule out that EFI and macOS bootable partition did not match together.
- I'm not sure whether my BIOS settings are 100% correct:
- STEP 3: Recommended BIOS Settings is of course generically written.
- I'd appreciate how that corresponds exactly to the settings available on the Lenovo Yoga 720, which features a "InsydeH2O BIOS".
- I did additional research and interpretation, tried to get as close to the instructions as possible, but some settings were best guesses.
- Sometimes Clover loaded, sometimes not, sometimes crashed (sudden reboot, or only an empty prompt remained, or some strange mix of text output and Lenovo boot logo)
- Sometimes Clover got aborted, if you did not reach your your desired menu item in a certain time, or accessed it with the wrong arrow-key-sequences.
- Btw in Clover the USB mouse and keyboard always worked.
- For creating the boot media I had uncertainties which UniBeast for which macOS version:
- I used UniBeast 7.1.1 to create a Sierra 10.12.6 bootdisk
- I used UniBeast 8.3.2 to create a High Sierra 10.13.4 bootdisk. It did not offer to choose Sierra, although that was under /Applications .
- Is the UniBeast 7.x series for Sierra only, and the UniBeast 8.x series for High Sierra only? It was not documented anywhere explicitly, but I had to assume so.
- Also I saw that you provided a customized config.plist and kexts.zip
- As a hackintosh newbie, I also failed in that regard.
- As you mentioned that you integrated your hacks upstream, I first assumed those files got already integrated in the newest UniBeast installers. But after the failed boots in various permutations, I was not too sure about that anymore, therefore tried UniBeast fresh /EFI/ and then yours.
- But also in that regard, I did not know what's the right approach.
- Replace the /EFI/kext/ entirely with yours, or merge your files into the existing /EFI/kexts/ structures, which Unibeast had created?
- Config.plist must obviously be replaced. I simply renamed the original to config-unibeast.plist
- Later discovered that in Clover Settings menu, you can even dynamically switch between config* files. But did not try that.
- When I had gone until the "attach bluetooth mighty mouse screen" I tried plugging an external mouse and keyboard. Hotplugging failed. On my next boot attempts, I tried with mouse/keyboard plugged from boot-start on. But also this was a game of luck. It even seemed to matter in which USB port was the bootdisk and in which the input external devices. The right USB 3.0 Type A port seemed to work best for the boot medium.
- In Clover I always used SPACE to select a boot medium, and then checked the boot flags, always used verbose mode (to see where I get stuck) and set the Nvidia to VESA. Then chose "boot with chosen options" (or similarly named, cannot recall now and have no access to the Yoga 720 currently). There were also other options, like to boot with or without kext injections. Also tried the booting with kext injection. But again I had guessed that if I used a modified /EFI/kexts they would automatically be considered for injection. Or must that be specified in the Clover boot dialog? But as we have a config.plist, I thought this takes care of all the boot parameters and kext injections.
- All together so many permutations, that mere trial and error deductions are fairly impossible.
- I plan to return the Yoga 720, and get the better variant, with 512GB SSD, GTX 1050 with 4GB VRAM, and i7-7700HQ CPU. Will this maybe solve it? Or will I have the same issues?
Hopefully some of you guys can help me. I very likely have misconceptions about some of the involved principles.