Direct Update to macOS Sierra using Clover

[VioletDragon]

trying to use 14,2 - I've tried through MultiBeast and Clover Configurator but it doesn't seem to stick and reverts to my previous set up of 13,1.

Been trying now to install through USB instead but just boots into my previous Lion install after black apple loading screen for 30m.

Are you using Clover?

 

[chiechi]

trying to use 14,2 - I've tried through MultiBeast and Clover Configurator but it doesn't seem to stick and reverts to my previous set up of 13,1.

I had the same problem at first because my BIOS simply says "macos" as the EFI boot device and I was never sure which drive it booted, the one with the updated system definition or the backup with the old definition.

Assuming you have Clover installed, make sure MultiBeast is editing the config.plist on the EFI partition that your BIOS actually boots; in my case the drives are also listed by brand/model as UEFI devices. If you still aren't sure, try creating a file called "config-new.plist" in /Volumes/EFI/EFI/CLOVER. When you boot into the Clover go into settings and load "config-new.plist." If it doesn't show up, then you are booting the wrong EFI partition.

In my case it still took two reboots to get the new system definition to stick and one more reboot that seemed to do something with the kext cache before Sierra booted successfully.

 

[irish_man]

Hi guys, tried everything but can't pass "System uptime in nanoseconds" error.
Running latest Clover version on 14,2 System Definition.
Anyone found the solution?

Edit: It's 14,1 not 14,2

 

[VioletDragon]

Hi guys, tried everything but can't pass "System uptime in nanoseconds" error.
Running latest Clover version on 14,2 System Definition.
Anyone found the solution?

Attach screenshot.

 

[irish_man]

Attach screenshot.

Here it is, tnx.

 

[VioletDragon]

Here it is, tnx.

View attachment 215544

Try booting with nv_disable=1.

 

[irish_man]

Try booting with nv_disable=1.

Thank you but unfortunately it didnt work. Still getting the same error.

 

[jrii]

Thank you but unfortunately it didnt work. Still getting the same error.

I suggest you create USB installation media and upgrade with that.

 

[PetarHolland]

I suggest you create USB installation media and upgrade with that.

So in my case I just simply run the latests MultiBeast and reinstall the HD530 driver... As simple as that? Or it's better to reinstall all the kext and patch with the new MultiBeast?

 

[jrii]

So in my case I just simply run the latests MultiBeast and reinstall the HD530 driver... As simple as that? Or it's better to reinstall all the kext and patch with the new MultiBeast?

It should be enough just to install HD530.
But there are still problems unsolved with HD530 & Sierra (artifacts etc.).