Direct Update to macOS Sierra using Clover

[MOOOO]

I've been trying to install Sierra (In the method described here and using a vanilla USB I created through createinstallmedia without). Whenever I try to boot I get a line of plus symbols when in verbose mode and when not using verbose mode it just hangs at the Apple logo. I'm using FakeSMC version 6.21 built from source in /EFI/kexts/Other. I have a BIOS system (not using UEFI) and I'm using the Late 2009 iMac System Definition.

 

[Stork]

I've been trying to install Sierra (In the method described here and using a vanilla USB I created through createinstallmedia without). Whenever I try to boot I get a line of plus symbols when in verbose mode and when not using verbose mode it just hangs at the Apple logo. I'm using FakeSMC version 6.21 built from source in /EFI/kexts/Other. I have a BIOS system (not using UEFI) and I'm using the Late 2009 iMac System Definition.

Use UniBeast to create the installer USB thumb driver. There's no longer the need to use the "vanilla" method.

But, that's as far as I can tell you what to do since I'm not telepathic. We need to know your system components. See the tonymacx86 Forum Rules & Policies on signature block components.

Additionally, please provide complete details in your Profile.

Mobo: motherboard manufacturer/model
CPU: detailed CPU model (e.g., i7-4770K)
Graphics: Video card manufacturer/model and/or Intel Integrated Graphics version (e.g., HD4600)

See my Profile items to the left of my post, under my name.

By completing your Profile and signature block, you help us help you better.

 

[kiiroaka]

I may perform a fresh install of Sierra on a separate blank drive and see if I can utilize the new Multibeast 9.0 to make it work....

Just don't be surprised if even that doesn't work since you may have to install the blank disk in the PC, format it as usual, run the Sierra installer from within EL Cap, after installing the latest Clover (which for me did not work at all - and I've since found that no matter which one I update, all the config.plist files get updated - and if I booted from the USB stick, the USB stick would get updated when I specifically told it to just write it out to the Sierra disk), reboot, then select the Mac OSX Installer drive icon from the Clover boot.

I had installed Sierra that way and I had to use Linux to wipe away the EFI partition on the Sierra HDD and then found that when I updated the nVidia WebDriver that it blew up the nVidia driver on El Cap, and when I fixed the audio 'no devices found' in Sierra that the El Cap audio devices were not detected.

Maybe the new UniBeast v9 will work if you disconnect El Cap, install the Sierra drive and try a full install. Just be aware that you are working with EFI and NVRAM, so after you install Sierra you may not be able to re-install the El CAP drive, leave the Sierra drive connected and expect Clover not to have conniptions. (Among other things each drive will have its own NVRAM.plist in the root directory.) [I made the mistake of getting into Clover UEFI and moving the boot disk drives around and I had all sorts of BIOS type problems after I moved El Cap back into the rotation.]

 

[jminiman]

Is anyone seeing weird behavior with screen saver freezing?

 

[kiiroaka]

Really?
View attachment 212911

And for those dependent on third party tools, Unibeast 7.01 works fine. Then install Clover to it and boot to the installer... (Tested on sig builds)

Really. https://sourceforge.net/projects/cloverefiboot/files/Installer/

 

[Asus-Freak]

Well then it's been removed...

 

[Asus-Freak]

Just don't be surprised if even that doesn't work since you may have to install the blank disk in the PC, format it as usual, run the Sierra installer from within EL Cap, after installing the latest Clover (which for me did not work at all - and I've since found that no matter which one I update, all the config.plist files get updated - and if I booted from the USB stick, the USB stick would get updated when I specifically told it to just write it out to the Sierra disk), reboot, then select the Mac OSX Installer drive icon from the Clover boot.

I had installed Sierra that way and I had to use Linux to wipe away the EFI partition on the Sierra HDD and then found that when I updated the nVidia WebDriver that it blew up the nVidia driver on El Cap, and when I fixed the audio 'no devices found' in Sierra that the El Cap audio devices were not detected.

What kind of nonsense it this? Are you suggesting that Apple's install app modifies clover config.files, not a chance...

 

[kiiroaka]

I'd like to know where those files were that you pointed to. Looks like a nice site.

 

[kiiroaka]

In my case, I couldn't get Sierra to install through UniBeast, so I created two UniBeast sticks on my work machine. Neither worked. So I had to resort to installing Sierra from El Cap. When I finally got Sierra working correctly, El Cap video and audio blew up. When I got El Cap video and audio working correctly, Sierra audi and video blew up. El Cap kext files are in its own 10.11 folder and Sierra kext files are in "Other"folder. But both are using the same Config.plist file, no? Trying to install Clover v3726 onto the Sierra disk EFI parition did not work, even when I specifically told it to save it there. I eventually just deleted the Sierra EFI partition.

Your experiences may be different, especially since I use Legacy boot loader because I have W10 and two different Linuxes at the same time as El Cap and Sierra - all on separate drives and you're probably using UEFI boot loader. If that's the case and one goes and connects and disconnects drives under UEFI one may experience some problems. I'm not the type to resort to clearing the BIOS anytime I have a problem, although I did update my BIOS after copying the old BIOS to the backup area. After that it was just a matter of booting in Safe Mode into El Cap, deleting the audio kext, uninstalling the nVidia WebDriver, running MultiBeast to install just the audio driver, rebooting, installing the video driver.

 

[kiiroaka]

Vanilla flavour installs did not work. So I had to resort to installing Sierra from El Cap onto a separate drives. El Cap kexts are in its own 10.11 folder and Sierra kexts are in its own 10.Other folder. But they both share the same config.plist file, no? Therefore audio and video changes made to one OS will probably affect the other OS.

I'm not saying that Apple's installer modifies Clover's config.plist. I said that each drive had its own NVRAM.plist file in its root, therefore it works with the UEFI BIOS.