Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

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 :)

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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

1835430450_edk2Buildfolder.png.a43edcfa3dd221ec73c5bf79d6ee1386.png

 

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 by fusion71au
upload image
  • Like 2
  • Thanks 1
Link to comment
Share on other sites

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

  • Like 1
Link to comment
Share on other sites

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 by Matgen84
Link to comment
Share on other sites

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.

  • Like 1
Link to comment
Share on other sites

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에서 보냄

  • Like 1
Link to comment
Share on other sites

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. 

Link to comment
Share on other sites

 
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에서 보냄

  • Sad 1
Link to comment
Share on other sites

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

 

 

Capture d’écran 2018-08-17 à 18.37.40.png

Link to comment
Share on other sites

 
I think appleloadimage.efi was rename appleimageloader.efi according to the source
 
 
1036126755_Capturedcran2018-08-1718_37_40.png.ff4b14a2270d78f0b8bb5d297bbca4d4.png
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에서 보냄

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

1 hour ago, Matgen84 said:

 

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

Thanks

 

copy efi files in root on ESP

then, go shell option in GUI

and type fsX: X is your ESP

then load efi filename

if you want to save txt file,

load efi filename > filename.txt

and reboot

Link to comment
Share on other sites

17 minutes ago, Sherlocks said:

 

copy efi files in root on ESP

then, go shell option in GUI

and type fsX: X is your ESP

then load efi filename

if you want to save txt file,

load efi filename > filename.txt

and reboot

 

Ok. One more precision: how to load efi fllename? 

 

sorry for my bad english

Edited by Matgen84
Link to comment
Share on other sites

 
Ok. One more precision: how to load efi fllename? 
you can rename filename as simple or short.
appleimageloader.efi to 1.efi
then copy in root on ESP
go shell.
type fsX: X is your ESP(need check)
type load 1.efi or type load 1.efi > 1.txt
then type reboot
return GUI. boot macos. then mount ESP. and check txt file



나의 LG-F800S 의 Tapatalk에서 보냄

  • Like 1
Link to comment
Share on other sites

1 hour ago, Sherlocks said:

you can rename filename as simple or short.
appleimageloader.efi to 1.efi
then copy in root on ESP
go shell.
type fsX: X is your ESP(need check)
type load 1.efi or type load 1.efi > 1.txt
then type reboot
return GUI. boot macos. then mount ESP. and check txt file



나의 LG-F800S 의 Tapatalk에서 보냄
 

 

I type load 1.efi > 1.txt

Shell is stuck without going back to FS3: So I can't type reboot. txt file generated is empty of course.

 

I try again

EDIT: same issue. I don't understand why

Edited by Matgen84
Link to comment
Share on other sites

×
×
  • Create New...