Clover General discussion

[Cyberdevs]

Hey guys;

Hi @savvamitrofanov

 

According to these statement:

"Now for security reasons you should load AppleLoadImage.efi right before ApfsDriverLoader.efi. If you use Clover bootloader, you can just put AppleLoadImage.efi and ApfsDriverLoader.efi into your drivers64uefi folder."

 

Source

 

We need to install AppleLoadImage.efi as well but when I put the driver inside drivers64UEFI my system simply won't boot, it just hangs on the logo, and even if it decides to boot the only partition that is detected by clover is the EFI partition on the hard disk that I have windows installed.

 

Is it gonna be implemented in the clover by default or we just need to compile it manually?

What am I missing?

 

These are the drivers that I currently use to boot into macOS without any issues:

ApfsDriverLoader.efi

AptioMemoryFix-64.efi

VBoxHfs-64.efi

 

Any input on the matter will be highly appreciated.

 

Thanks.

Edited August 16, 2018 by Cyberdevs

[Sherlocks]

11 minutes ago, Cyberdevs said:

Hey guys;
 
According to these statement:
"Now for security reasons you should load AppleLoadImage.efi right before ApfsDriverLoader.efi. If you use Clover bootloader, you can just put AppleLoadImage.efi and ApfsDriverLoader.efi into your drivers64uefi folder."
 
Source
 
We need to install AppleLoadImage.efi as well but when I put the driver inside drivers64UEFI my system simply won't boot, it just hangs on the logo, and even if it decides to boot the only partition that is detected by clover is the EFI partition on the hard disk that I have windows installed.
 
Is it gonna be implemented in the clover by default or we just need to compile it manually?
What am I missing?
 
These are the drivers that I currently use to boot into macOS without any issues:
ApfsDriverLoader.efi
AptioMemoryFix-64.efi
VBoxHfs-64.efi
 
Any input on the matter will be highly appreciated.
 
Thanks.

 

+1. hang on oem logo. need to report it to @savva

built this "https://github.com/acidanthera/AppleSupportPkg/commit/68f14f8161179d718374f4d5ee0f3e902eef416f"

and tested both files in driver64UEFI folder

ApfsDriverLoader.efi
AppleImageLoader.efi

 

 

나의 LG-F800S 의 Tapatalk에서 보냄
 

Edited August 16, 2018 by Sherlocks

[Badruzeus]

Seems normal here, but... these are some logs from yesterday 10.14 APFS, my bad I just cleanse installed it with HFS+

 

Spoiler

0:976  0:000  === [ LoadDrivers ] =======================================
0:981  0:005  Loading ApfsDriverLoader-64.efi  status=Success
1:003  0:022   - driver needs connecting
1:003  0:000  Loading AppleImageCodec-64.efi  status=Success
1:004  0:000  Loading AppleKeyAggregator-64.efi  status=Success
1:005  0:000  Loading AppleUITheme-64.efi  status=Success
1:006  0:000  Loading AptioMemoryFix-64.efi  status=Success
1:006  0:000  Loading CsmVideoDxe-64.efi  status=Success
1:007  0:000   - driver needs connecting
1:007  0:000  Loading DataHubDxe-64.efi  status=Success
1:012  0:004  Loading FirmwareVolume-64.efi  status=Success
1:013  0:000  Loading FSInject-64.efi  status=Success
1:013  0:000  Loading HashServiceFix-64.efi  status=Success
1:014  0:000  Loading OsxFatBinaryDrv-64.efi  status=Success
1:015  0:000  Loading SMCHelper-64.efi  status=Success
1:016  0:000  Loading VBoxHfs-64.efi  status=Success
1:016  0:000   - driver needs connecting
1:016  0:000  3 drivers needs connecting ...
1:016  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
1:016  0:000  APFS driver loaded
1:016  0:000  Video driver loaded: disconnect Success

 

I still don't get it yet, *.efi drivers can be sorted upon load?

[Cyberdevs]

40 minutes ago, Sherlocks said:

+1. hang on oem logo. need to report it to @savva

built this "https://github.com/acidanthera/AppleSupportPkg/commit/68f14f8161179d718374f4d5ee0f3e902eef416f"

and tested both files in driver64UEFI folder

ApfsDriverLoader.efi
AppleImageLoader.efi

I believe I just used that build, I just cloned the GitHub about two hours ago.

I'm gonna give it another try.

 

4 minutes ago, Badruzeus said:

Seems normal here, but... these are some logs from yesterday 10.14 APFS, my bad I just cleanse installed it with HFS+

 

  Reveal hidden contents

0:976  0:000  === [ LoadDrivers ] =======================================
0:981  0:005  Loading ApfsDriverLoader-64.efi  status=Success
1:003  0:022   - driver needs connecting
1:003  0:000  Loading AppleImageCodec-64.efi  status=Success
1:004  0:000  Loading AppleKeyAggregator-64.efi  status=Success
1:005  0:000  Loading AppleUITheme-64.efi  status=Success
1:006  0:000  Loading AptioMemoryFix-64.efi  status=Success
1:006  0:000  Loading CsmVideoDxe-64.efi  status=Success
1:007  0:000   - driver needs connecting
1:007  0:000  Loading DataHubDxe-64.efi  status=Success
1:012  0:004  Loading FirmwareVolume-64.efi  status=Success
1:013  0:000  Loading FSInject-64.efi  status=Success
1:013  0:000  Loading HashServiceFix-64.efi  status=Success
1:014  0:000  Loading OsxFatBinaryDrv-64.efi  status=Success
1:015  0:000  Loading SMCHelper-64.efi  status=Success
1:016  0:000  Loading VBoxHfs-64.efi  status=Success
1:016  0:000   - driver needs connecting
1:016  0:000  3 drivers needs connecting ...
1:016  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
1:016  0:000  APFS driver loaded
1:016  0:000  Video driver loaded: disconnect Success

 

I still don't get it yet, *.efi drivers can be sorted upon load?

I guess what it means is just simply place it in the driversUEFI64 folder. Not to actually load it upon boot like Ozmosis.

[Matgen84]

47 minutes ago, Sherlocks said:

 

+1. hang on oem logo. need to report it to @savva

built this "https://github.com/acidanthera/AppleSupportPkg/commit/68f14f8161179d718374f4d5ee0f3e902eef416f"

and tested both files in driver64UEFI folder

ApfsDriverLoader.efi
AppleImageLoader.efi

 

 

나의 LG-F800S 의 Tapatalk에서 보냄
 

 

How to build AppleImageLoader.efi for testing. Please. 

[Cyberdevs]

@Sherlocks

Still the same issue,

If I press Tab twice on the OEM logo clover loads but still doesn't detect any of my hard disks except for the Windows's EFI partition.

These are the files I'm using.

AppleSupport-v2.0.1-RELEASE.zip

[savvas]

Hello guys!

I hope I fixed this issue for now, you can try this debug prebuilt binaries

 

AppleSupport-v2.0.1-DEBUG.zip

Edited August 16, 2018 by savvamitrofanov

[Cyberdevs]

8 minutes ago, savvamitrofanov said:

Hello guys!

I hope I fixed this issue for now, you can try this debug prebuilt binaries

 

AppleSupport-v2.0.1-DEBUG.zip

I just booted successfully into High Sierra with 2.0.1 version, although the verbose log is still there but I'm sure that you will fix it in the next release.

I'm gonna try to boot into Mojave and report back.

 

Thanks a lot

[savvas]

1 minute ago, Cyberdevs said:

I just booted successfully into High Sierra with 2.0.1 version, although the verbose log is still there but I'm sure that you will fix it in the next release.

I'm gonna try to boot into Mojave and report back.

 

Thanks a lot

Nice! With AppleImageLoader loaded?

[Cyberdevs]

3 minutes ago, savvamitrofanov said:

Nice! With AppleImageLoader loaded?

Yes I put those two files in the driversUEFI64 and successfully booted into High Sierra, but on Mojave clover loads but the boot process hangs right after AptioMemoryFix.efi loads. I'm building the latest Clover revision as we speak to update the clover on my Mojave SSD (I'm currently using 4646 on Mojave) and see if that I can boot into Mojave as well.

[Awesome Donkey]

Shouldn't AppleImageLoader.efi be added to Clover's installer alongside ApfsDriverLoader.efi when building Clover and installing (automatically if using ApfsDriverLoader.efi)?

[Cyberdevs]

@savvamitrofanov

Ok it works on Mojave as well.

I successfully booted into High Sierra and Mojave DP7 with these drivers:

 

AptioMemoryFix-64.efi

AppleImageLoader.efi

ApfsDriverLoader.efi

VBoxHfs-64.efi

 

Nice job man thanks!

[fusion71au]

On 8/15/2018 at 10:55 PM, Tetonne said:

how can i upgrade my Window 10 on a dual boot (window/HS) same HD?

the upgrade always failed

==> easy win 10 upgrade on a dual boot clover HD  

 

You can try the following:

1.  Before major Windows upgrade, make Windows 10 the default boot option on startup - either make your BIOS boot to the Windows bootloader first (before Clover) or edit Clover's config.plist to make it start Windows first eg if you have Windows installed in UEFI mode (recommended) with Clover, set the default volume and loader in config.plist/boot as below...

 

		<key>DefaultLoader</key>
		<string>bootmgfw.efi</string>
		<key>DefaultVolume</key>
		<string>EFI</string>

2.  Disable Windows 10 fast startup under Power Options.

 

Good luck .

 

10 hours ago, Matgen84 said:

 

How to build AppleImageLoader.efi for testing. Please. 

 

Have a look inside your edk2 or UDK2018 /Build/AppleSupportPkg/RELEASE_XCODE8/X64 folder...

Spoiler

 

8 hours ago, savvamitrofanov said:

Nice! With AppleImageLoader loaded?

 

All loaded and working here on 10.13.6 and 10.14 DB7.  Bootlog...

Spoiler

0:111  0:000  === [ LoadDrivers ] =======================================
0:111  0:000  Loading HFSPlus.efi  status=Success
0:113  0:001   - driver needs connecting
0:113  0:000  Loading ApfsDriverLoader-64.efi  status=Success
0:113  0:000   - driver needs connecting
0:113  0:000  Loading AppleImageCodec-64.efi  status=Success
0:114  0:001  Loading AppleKeyAggregator-64.efi  status=Success
0:115  0:000  Loading AppleUITheme-64.efi  status=Success
0:115  0:000  Loading AptioMemoryFix-64.efi  status=Success
0:116  0:000  Loading DataHubDxe-64.efi  status=Success
0:120  0:004  Loading FirmwareVolume-64.efi  status=Success
0:121  0:000  Loading FSInject-64.efi  status=Success
0:123  0:001  Loading SMCHelper-64.efi  status=Success
0:123  0:000  Loading VBoxExt4-64.efi  status=Success
0:125  0:001   - driver needs connecting
0:125  0:000  Loading AppleImageLoader-64.efi  status=Success
0:125  0:000  3 drivers needs connecting ...
0:125  0:000  PlatformDriverOverrideProtocol->GetDriver overriden
0:125  0:000  HFS+ driver loaded
0:125  0:000  APFS driver loaded
0:125  0:000  Searching for invalid DiskIo BY_DRIVER connects: not found, all ok

 

 

Edited August 17, 2018 by fusion71au
upload image

[xtddd]

5 hours ago, savvamitrofanov said:

Nice! With AppleImageLoader loaded?

test it..can boot into mojave db7

[Sherlocks]

7 hours ago, savvamitrofanov said:

Hello guys!

I hope I fixed this issue for now, you can try this debug prebuilt binaries

 

AppleSupport-v2.0.1-DEBUG.zip

 

here is debug log

AppleImageLoader: Binary isn't AppleEfiFat
Starting ApfsDriverLoader ver. 2.0.1
No partition info protocol, using Legacy scan
Image 'FS0:\1.efi' loaded at D4DCC000 - Success

 

AppleImageLoader: Binary isn't AppleEfiFat
Image 'FS0:\2.efi' loaded at D4DC5000 - Success

[chris1111]

AppleImageLoader.efi  status=Success

Build UDK2018, Xcode 9.4.1 (9F2000)

 

UEFI Booting Dell Optiplex 790

 

[Matgen84]

HI

 

Here too: AppleImageLoader.efi  status=Success. I can boot on Mojave Beta 7.

 

 

"Now for security reasons you should load AppleLoadImage.efi right before ApfsDriverLoader.efi." Can Clover do it (load its drivers in specific order)? 

 

Thanks

Edited August 17, 2018 by Matgen84

[Slice]

12 minutes ago, Matgen84 said:

HI

 

Here too: AppleImageLoader.efi  status=Success. I can boot on Mojave Beta 7.

 

 

"Now for security reasons you should load AppleLoadImage.efi right before ApfsDriverLoader.efi." Can Clover do it (load its drivers in specific order)? 

 

Thanks

Good driver should wait for its dependencies.

[Sherlocks]

HI
 
Here too: AppleImageLoader.efi  status=Success. I can boot on Mojave Beta 7.
 
 
"Now for security reasons you should load AppleLoadImage.efi right before ApfsDriverLoader.efi." Can Clover do it (load its drivers in specific order)? 
 
Thanks

did you add appleloadimage.efi? or appleimageloader and apfsloader?

나의 LG-F800S 의 Tapatalk에서 보냄

[Matgen84]

2 hours ago, Sherlocks said:

did you add appleloadimage.efi? or appleimageloader and apfsloader?

나의 LG-F800S 의 Tapatalk에서 보냄
 

 

I reproduced an extract from the readme file in my previous post. In fact, I added appleimageloader and apfsdriverloader. 

[Sherlocks]

 
I reproduced an extract from the readme file in my previous post. In fact, I added appleimageloader and apfsdriverloader. 

just both files? without appleloadimage.efi?
in my case, strangely not success. hmm..

나의 LG-F800S 의 Tapatalk에서 보냄

[Matgen84]

5 minutes ago, Sherlocks said:

just both files? without appleloadimage.efi?
in my case, strangely not success. hmm..

나의 LG-F800S 의 Tapatalk에서 보냄
 

 

I think appleloadimage.efi was rename appleimageloader.efi according to the source

 

 

[Sherlocks]

 
I think appleloadimage.efi was rename appleimageloader.efi according to the source
 
 

i knew. i want to know that your appleefifat binary load or not like me in uefi shell.
in clover log, my system also shown that appleimageloader.efi success.

나의 LG-F800S 의 Tapatalk에서 보냄

[Matgen84]

4 hours ago, Sherlocks said:

i knew. i want to know that your appleefifat binary load or not like me in uefi shell.
in clover log, my system also shown that appleimageloader.efi success.

나의 LG-F800S 의 Tapatalk에서 보냄
 

 

How to verify appleefifat binary is load or not? I don't know how to do.

Thanks

[Slice]

44 minutes ago, Matgen84 said:

 

How to verify appleefifat binary is load or not? I don't know how to do.

Thanks

It is for 10.7 which has fatbinary images. Not needed for 10.13.