Jump to content
ErmaC

Clover General discussion

18,272 posts in this topic

Recommended Posts

fusion3.zip works perfectly :thumbsup_anim: ...

 

 

 

 

attachicon.gifscreenshot0.png

attachicon.gifscreenshot1.png

attachicon.gifscreenshot2.png

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>ProductBuildVersion</key>
	<string>17B48</string>
	<key>ProductCopyright</key>
	<string>1983-2017 Apple Inc.</string>
	<key>ProductName</key>
	<string>Mac OS X</string>
	<key>ProductUserVisibleVersion</key>
	<string>10.13.1</string>
	<key>ProductVersion</key>
	<string>10.13.1</string>
</dict>
</plist>
 

 

 

Attached is com.apple.boot.R.zip with SystemVersion.plist.

Thank you for detail test and report.

I will cleanup and commit.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites
Advertisement

Thanks Sherlocks.

 

It now correctly detects /com.apple.boot.R/boot.efi from "Boot OS X" as macOS install  :).  

 

At the moment, it is not parsing /com.apple.boot.R/SystemVersion.plist so os ver is not set to 10.13.x ---> will need FakeSMC in /CLOVER/kexts/Other as /10.13 won't be used...

 

 

 

1.temp test to check read other folder.zip file

-i temporarily disabled systemversion check for fusion drive to check to read other folder if os is null

 

2.rc test

-completely done

 

please test on each files, then report. thanks in advance.

temp test to check read other folder if null os.zip

rc test.zip

Share this post


Link to post
Share on other sites

ebe10439cfad046cc91f1498210740d7.jpg

 

Today when I try to delete all the UEFI variables the shell show this.

 

Does this protected variables cause our laptop can’t use native nvram?

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

ebe10439cfad046cc91f1498210740d7.jpg

 

Today when I try to delete all the UEFI variables the shell show this.

 

Does this protected variables cause our laptop can’t use native nvram?

 

 

从我的 iPhone 发送,使用 Tapatalk

Maybe.. It was protected. I don't know exactly.

http://www.insanelymac.com/forum/index.php?/topic/304530-Clover-Change-Explanations&do=findComment&comment=2533580

 

Follow terminal command and check nvram -p after reboot.

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

Maybe.. It was protected. I don't know exactly.

http://www.insanelymac.com/forum/index.php?/topic/304530-Clover-Change-Explanations&do=findComment&comment=2533580

 

Follow terminal command and check nvram -p after reboot.

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

still no native nvram support now

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

still no native nvram support now

 

 

从我的 iPhone 发送,使用 Tapatalk

You have to use emulvariable+rc script if you want to use nvram feature on your system. save brightness value/etc

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

You have to use rc script if you want to use nvram feature on your system. save brightness value/etc

 

나의 LG-F800S 의 Tapatalk에서 보냄

I just want to find some solutions to solve the native nvram support on our laptop.

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

1.temp test to check read other folder.zip file

-i temporarily disabled systemversion check for fusion drive to check to read other folder if os is null

 

2.rc test

-completely done

 

please test on each files, then report. thanks in advance.

 

i tested it on 10.13.2 beta3 if os null

post-980913-0-68231900-1510654664_thumb.png

post-980913-0-88598100-1510654665_thumb.png

 

@fusion71au

please test rc test.file.

http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2534374

 

thanks

Share this post


Link to post
Share on other sites

1.temp test to check read other folder.zip file

-i temporarily disabled systemversion check for fusion drive to check to read other folder if os is null

 

2.rc test

-completely done

 

please test on each files, then report. thanks in advance.

 

For temp test version, GetOSVersion incorrectly finds 10.12 and Clover injects kexts from /Other and /10.12...

 

 

78:972  0:000  Loading boot.efi  status=Success
79:074  0:102  GetOSVersion: 10.12

- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: DE725918
79:362  0:000  ** Warning: Your MLB is not suitable for iMessage(must be 17 chars long) !
79:362  0:000  Use origin smbios table type 1 guid.
79:363  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\OEM\XPS M1530 \kexts\Other
79:363  0:000  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\RTL8192SUs.kext
79:398  0:034  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext
79:400  0:002    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext
79:404  0:003    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Mouse.kext
79:405  0:001    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext
79:407  0:001  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext
79:417  0:010    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\VoodooBatterySMC.kext
79:421  0:004    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\PC8739x.kext
79:424  0:002    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\IntelCPUMonitor.kext
79:427  0:003    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\GeforceSensor.kext
79:430  0:003  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\OEM\XPS M1530 \kexts\10.12
79:430  0:000  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\10.12\NullEthernet.kext

 

 

Block injected kexts menu only shows /Other folder...

post-846696-0-00789800-1510653863_thumb.png

 

 

 

For rc test version, GetOSVersion correctly finds 10.13 and Clover injects kexts from /Other and /10.13...

 

 

65:372  0:000  Loading boot.efi  status=Success
65:475  0:103  GetOSVersion: 10.13.1

- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: DE72E718
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: DE72E718
65:762  0:000  ** Warning: Your MLB is not suitable for iMessage(must be 17 chars long) !
65:762  0:000  Use origin smbios table type 1 guid.
65:763  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\OEM\XPS M1530 \kexts\Other
65:763  0:000  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\RTL8192SUs.kext
65:797  0:034  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext
65:799  0:002    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext
65:803  0:003    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Mouse.kext
65:805  0:001    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext
65:806  0:001  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext
65:816  0:010    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\VoodooBatterySMC.kext
65:820  0:004    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\PC8739x.kext
65:823  0:002    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\IntelCPUMonitor.kext
65:826  0:003    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\GeforceSensor.kext
65:829  0:003  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\OEM\XPS M1530 \kexts\10.13
65:829  0:000  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\10.13\NullEthernet.kext

 

 

Block injected kexts menu shows /Other and /10.13 folders...

 

post-846696-0-36182900-1510654167_thumb.png

post-846696-0-10024700-1510654190_thumb.png

post-846696-0-59229200-1510654220_thumb.png

post-846696-0-86896900-1510654295_thumb.png

 

 

Thanks Sherlocks.

I think your rc version is ready to go  :).

Share this post


Link to post
Share on other sites

For temp test version, GetOSVersion incorrectly finds 10.12 and Clover injects kexts from /Other and /10.12...

 

 

78:972  0:000  Loading boot.efi  status=Success
79:074  0:102  GetOSVersion: 10.12

- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: DE725918
79:362  0:000  ** Warning: Your MLB is not suitable for iMessage(must be 17 chars long) !
79:362  0:000  Use origin smbios table type 1 guid.
79:363  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\OEM\XPS M1530 \kexts\Other
79:363  0:000  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\RTL8192SUs.kext
79:398  0:034  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext
79:400  0:002    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext
79:404  0:003    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Mouse.kext
79:405  0:001    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext
79:407  0:001  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext
79:417  0:010    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\VoodooBatterySMC.kext
79:421  0:004    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\PC8739x.kext
79:424  0:002    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\IntelCPUMonitor.kext
79:427  0:003    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\GeforceSensor.kext
79:430  0:003  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\OEM\XPS M1530 \kexts\10.12
79:430  0:000  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\10.12\NullEthernet.kext

 

 

Block injected kexts menu only shows /Other folder...

 

 

 

For rc test version, GetOSVersion correctly finds 10.13 and Clover injects kexts from /Other and /10.13...

 

 

65:372  0:000  Loading boot.efi  status=Success
65:475  0:103  GetOSVersion: 10.13.1

- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: DE72E718
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: DE72E718
65:762  0:000  ** Warning: Your MLB is not suitable for iMessage(must be 17 chars long) !
65:762  0:000  Use origin smbios table type 1 guid.
65:763  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\OEM\XPS M1530 \kexts\Other
65:763  0:000  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\RTL8192SUs.kext
65:797  0:034  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext
65:799  0:002    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext
65:803  0:003    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Mouse.kext
65:805  0:001    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext
65:806  0:001  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext
65:816  0:010    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\VoodooBatterySMC.kext
65:820  0:004    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\PC8739x.kext
65:823  0:002    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\IntelCPUMonitor.kext
65:826  0:003    |-- PlugIn kext: EFI\CLOVER\OEM\XPS M1530 \kexts\Other\FakeSMC.kext\Contents\PlugIns\GeforceSensor.kext
65:829  0:003  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\OEM\XPS M1530 \kexts\10.13
65:829  0:000  Extra kext: EFI\CLOVER\OEM\XPS M1530 \kexts\10.13\NullEthernet.kext

 

 

Block injected kexts menu shows /Other and /10.13 folders...

 

 

Thanks Sherlocks.

I think your rc version is ready to go  :).

committed.

test all again. fusion drive.

thanks in advance.

Share this post


Link to post
Share on other sites

I just want to find some solutions to solve the native nvram support on our laptop.

 

 

从我的 iPhone 发送,使用 Tapatalk

 

Please try this AptioFix2, without EmuVariable.

 

EDIT: Removed attachment.

Share this post


Link to post
Share on other sites

Please try this AptioFix2, without EmuVariable.

910cd2bbb1699595b1afa2c0016a4db8.jpg

 

Stuck here and reboot instantly...

 

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 

So, so, so, so, so many build errors.


Stuck here and reboot instantly...


从我的 iPhone 发送,使用 Tapatalk

 

You have ACPI error loading table?? So ACPI sensors looks like it fails. What's up with that table? Looks like you didn't drop a table but reinjected it.

 

EDIT: Actually, it appears that namespace is declared in another table already and you are redeclaring it in that table...


Anyone else with EmuVariable problem please try that AptioFix? I think gujiangjiang may also have another issue.

 

EDIT: Anyone can try it. It (hopefully) should still work for working nvram.

EDIT2: I need reports people!

Share this post


Link to post
Share on other sites

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 

So, so, so, so, so many build errors.

 

 

You have ACPI error loading table?? So ACPI sensors looks like it fails. What's up with that table? Looks like you didn't drop a table but reinjected it.

 

EDIT: Actually, it appears that namespace is declared in another table already and you are redeclaring it in that table...

 

Anyone else with EmuVariable problem please try that AptioFix? I think gujiangjiang may also have another issue.

My dsdt have no error with hotpatch ssdts.

 

I have try to delete acpisensors.kext but have no use.

 

I only drop dmar in my dropping table Id

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

My dsdt have no error with hotpatch ssdts.

 

I have try to delete acpisensors.kext but have no use.

 

I only drop dmar in my dropping table Id

 

 

从我的 iPhone 发送,使用 Tapatalk

 

Looks like you do have an error. Maybe it wasn't known cause you did not have correctly working system. You have add IMEI fix set? Maybe disable it.

 

EDIT: You may also need to set some nvram variables, that are set by nvram.plist in EFI shell before booting.

Share this post


Link to post
Share on other sites

do you have fixheaders / fixheader20000000 patch maybe you need it.

I don’t need fix header or drop bgrt.

 

 

从我的 iPhone 发送,使用 Tapatalk

Looks like you do have an error. Maybe it wasn't known cause you did not have correctly working system. You have add IMEI fix set? Maybe disable it.

 

EDIT: You may also need to set some nvram variables, that are set by nvram.plist in EFI shell before booting.

Yes I have add SSDT-IMEI.aml to fix Imei because imei could cause many problem in video playback.

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

I don’t need fix header or drop bgrt.

 

 

从我的 iPhone 发送,使用 Tapatalk

 

Yes I have add SSDT-IMEI.aml to fix Imei because imei could cause many problem in video playback.

 

 

从我的 iPhone 发送,使用 Tapatalk

 

You are redefining it, it's already defined. You need to edit your original tables and remove or fix it, or make sure you don't have add IMEI dsdt fix enabled. Don't reinject that table without removing the previous definition.

 

EDIT: Also, reconcile your nvram since all the stuff from nvram.plist needs added back.

Share this post


Link to post
Share on other sites

You are redefining it, it's already defined. You need to edit your original tables and remove or fix it, or make sure you don't have add IMEI dsdt fix enabled. Don't reinject that table without removing the previous definition.

 

EDIT: Also, reconcile your nvram since all the stuff from nvram.plist needs added back.

When I use official osxaptiov2 have no problem.

 

I will test more and give some feedback.

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

When I use official osxaptiov2 have no problem.

 

I will test more and give some feedback.

 

 

从我的 iPhone 发送,使用 Tapatalk

 

Yes, I am aware but the fixes have bugs, three of which I am aware, maybe more. I'm trying to fix them. I modified to prevent from moving runtime code areas, where SMM would be located, SMM uses physical mode so cannot be moved because the moving means that you have to adjust the physical addresses which can't be done, only virtual mode addresses can be changed.

Share this post


Link to post
Share on other sites

I test again with drop SSDT-IMEI but no use.

 

Try to remove IMEI Dsdt parched from heci but still can’t boot into OS X and always reboot.

 

 

 

从我的 iPhone 发送,使用 Tapatalk

Now I test add fix headers and drop bgrt but still reboot.

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

I test again with drop SSDT-IMEI but no use.

 

Try to remove IMEI Dsdt parched from heci but still can’t boot into OS X and always reboot.

 

 

 

从我的 iPhone 发送,使用 Tapatalk

 

I don't know what you mean. Are you injecting that table? Are you using the dsdt fix mask from clover? Did you edit your original table where IMEI is? Did you restore the values from your nvram.plist into your actual nvram? It may be easier for you to run the installer again to get proper nvram. See if you can launch the installer.

Share this post


Link to post
Share on other sites

I replaced with official osxaptiofixdrv2 with no emu driver and can run into the OS X.

 

 

从我的 iPhone 发送,使用 Tapatalk

I don't know what you mean. Are you injecting that table? Are you using the dsdt fix mask from clover? Did you edit your original table where IMEI is? Did you restore the values from your nvram.plist into your actual nvram? It may be easier for you to run the installer again to get proper nvram. See if you can launch the installer.

1. I don’t inject that table and I delete the dsdt patch (heci to Imei) and delete dsdt-imei.aml but still.

 

2. I didn’t need restore full nvram to native native because when I use official osxfix2 it works well.

 

3. Both system ,recoveryhd and installer can’t boot anymore.

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

I replaced with official osxaptiofixdrv2 with no emu driver and can run into the OS X.

 

 

从我的 iPhone 发送,使用 Tapatalk

 

Dude, I get that. There's a huge difference if you have working runtime that was not before. Do you still get message about it failing to load table because IMEI was already defined?

Share this post


Link to post
Share on other sites

Dude, I get that. There's a huge difference if you have working runtime that was not before. Do you still get message about it failing to load table because IMEI was already defined?

Yes I have removed all the patch and ssdt related with Imei but with no use.

 

I want test this kext but can’t boot into OS X.

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Clover r4747 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.14 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4747 for VMware.zip". Mount Clover-v2.4k-4747-X64 by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By superdooper71
      Hi all,
      I hope someone can help me as I am struggling with this bloody installation.
      I am running on several problems that I can't face : (
       
      First of all my config:
      Mobo: ASROCK H81M-DGS R2
      CPU: Intel Xeon E3-1220 v3 @3.10ghz
      RAM: 16gb DDR3 1600Mhz
      SSD: Crucial BX100 120Gb SSD
      Monitor: Hp 27w Hdmi
       
      POST Installation CLOVER
       
      Current Issues:
      • System will not boot (clover boot loader do not shows up) from SSD
         - System boot only with USB stick
      • Screen Resolution is only 1024x768
      • Monitor recognised as 17" instead of 24"
      • Monitor identified as secondary
      • Grafic Card Geforce GT710 shows 0 Mb
      • System info do not match Config.plistin Clover
       
      I attach screenshot of System Info, Kext in Clover, Resolution etc etc.
       
      Please can someonhelp me?
       
      Please can you tell me what is the Clover Parameter to activate when installing Clover  (Clover_v2.4k_r4722) into Boot Disk?
       
      I hope someone can help me out of this little troble: )
       
      Cheers
      Franco
       
      system info.tiff
      kext.tiff
      resolution.tiff
      system.tiff
      config.plist
    • By gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  selezionate OsxAptioFixDrv-64
                             *  :Se nel vostro sistema è presente una scheda grafica (discreta) della serie 9xx nVidia selezionate OsxAptioFix2Drv-64 al posto di  OsxAptioFixDrv-64 *
      ** OsxAptioFix2Drv :E' necessario per poter impostare CsrActiveConfig= 0x3 **
      ***OsxAptioFix3Drv oppure AptioMemory --> (consigliato) devono essere usati su hardware Skylake o successivi perché permettono alla nvram di lavorare correttamente
           (mi raccomando o uno o l'altro)
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione, nel caso può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      apfs.efi-10.13-NoLog.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      apfs.efi-10.13.1-No_LOG.zip
      apfs.efi-10.13.2_No_Log.zip
      apfs.efi-10.13.3-No_Log.zip
      apfs.efi-10.13.4-No_Log.zip
      apfs.efi-10.13.5_No_Log.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip






    • By marianopela
      Hi, I'm an Hackintosh user on my HP ProDesk and I'd like to try getting Mojave on my HP 250 G6
      Could anybody help me with the EFI folder?
       
      Thanks in advance
    • By Donk
      Here is a new utility to patch the EFI firmware in VMware Workstation and Fusion to allow the non-server versions of Mac OS X 10.5 (Leopard) and 10.6 (Snow Leopard) to run. Yoiu will need macOS unlocker 3 if you are using Workstation on non-Apple hardware. I still have to find a way to do this on ESXi as the UEFIPatch utility will not run in the ESXi console.
      This currently supports:
       
      Workstation 11/12/14/15 on Windows and Linux Workstation Player 7/12/14/15 on Windows and Linux Fusion 10/11 on macOS  
      https://github.com/DrDonk/efi-unlocker/releases/download/1.0.0/efi-unlocker100.zip
      https://github.com/DrDonk/efi-unlocker
       
      Please read the readme.txt file for details.
      readme.txt
×