Jump to content
ErmaC

Clover General discussion

20,006 posts in this topic

Recommended Posts

question: if I use VirtualSMC.kext I have to put it in the Bios VirtualSmc.efi folder or I have to put it in the Uefi folder
Thank you

Share this post


Link to post
Share on other sites
Advertisement
14 minutes ago, Alpha22 said:

question: if I use VirtualSMC.kext I have to put it in the Bios VirtualSmc.efi folder or I have to put it in the Uefi folder
Thank you

 

I though you need to read this,, https://github.com/andreszerocross/VirtualSMC/blob/master/Docs/FAQ.md   especially at the image below 
image.png.a2aa031ce1c210efc7d839d510a05e9f.png

 

Just depend if you boot in Legacy Mode (EFI/CLOVER/Drivers/BIOS) or UEFI Mode (EFI/CLOVER/Drivers/UEFI)

Share this post


Link to post
Share on other sites

Thanks for the reply

boot is UEFI

VirtualSMC.efi module is recommended for boot.efi compatibility when FileVault 2 is enabled. SMCHelper-64.efi is not compatible with VirtualSMC.efi and must be removed.

FileVault 2 is not enabled I have to use SMCHelper-64.efi or I have to delete it

Share this post


Link to post
Share on other sites
Posted (edited)

Ah nevermind, I finally am able to proceed r5015 instalation on HFS+ 10.11.6, 10.13.6, 10.14.6 and 10.15 Beta after removing this line from Distribution package. And the *.plist for auto "$ sudo mount -uw /" on every boot is still working under 10.15 APFS. Have a nice day.

 

<installation-check script="checkFileSystemIsWritable()"/>

 

Edited by Badruzeus

Share this post


Link to post
Share on other sites
1 minute ago, Alpha22 said:

Thanks for the reply

boot is UEFI


VirtualSMC.efi module is recommended for boot.efi compatibility when FileVault 2 is enabled. SMCHelper-64.efi is not compatible with VirtualSMC.efi and must be removed.

FileVault 2 is not enabled I have to use SMCHelper-64.efi or I have to delete it


Then it mean this image will help you :)
Just if you used FakeSMC.kext instead VirtualSMC.kext, CMIIW
image.png.c8c00a239f681a3fe2349682ef3e90b7.png

Share this post


Link to post
Share on other sites
Posted (edited)
Quote

Then it mean this image will help you :)
Just if you used FakeSMC.kext instead VirtualSMC.kext, CMIIW

 

I use VirtualSMC.kext so I have to delete SMCHelper-64.efi

the latest version of FakeSMC.kext

Edited by Alpha22

Share this post


Link to post
Share on other sites
Posted (edited)
2 hours ago, Andres ZeroCross said:

Yes, you're right, The problem is i just want to use Clover Preference Pane in Mojave and Catalina. 

 

I'm...not sure that's possible...? :)) I mean, what would be the point of having the Clover preference pane in Mojave...if you don't have Clover installed on your Mojave SSD? You want to control Catalina's Clover installation...from Mojave? That would be interesting...but...I'm not sure if that preference pane was made with this functionality in mind. :)) 

Edited by arsradu

Share this post


Link to post
Share on other sites
7 minutes ago, arsradu said:

 

I'm...not sure that's possible...? :)) I mean, what would be the point of having the Clover preference pane in Mojave...if you don't have Clover installed on your Mojave SSD? You want to control Catalina's Clover installation...from Mojave? That would be interesting...but...I'm not sure if that preference pane was made with this functionality in mind. :)) 


Sometime i waste my time in Mojave, and sometimes in Catalina :)

So the conclusions is i can't check official release of Clover with Clover Preference pane from other macOS system.

I need to boot to Catalina first, then i can check offical update from its.

It's no big problem,, thanks :)
 

Share this post


Link to post
Share on other sites
7 minutes ago, Andres ZeroCross said:


Sometime i waste my time in Mojave, and sometimes in Catalina :)

So the conclusions is i can't check official release of Clover with Clover Preference pane from other macOS system.

I need to boot to Catalina first, then i can check offical update from its.

It's no big problem,, thanks :)
 

 

Haha! Yeah, I knew that's what you were aiming for! :)) But yeah...I'm not sure that's possible with the current implementation.

 

However, something else you might be able to do...is subscribe for notifications on the Clover's SF page by clicking the Get Updates button.

 

It's not quite the same thing, but if the point of this is to know when new releases are out...that's one way to do it. And not just new official releases, but any new development updates. If you're interested to know what's knew...that might work.

 

137324267_Screenshot2019-07-15at12_20_43.thumb.png.86f0f281f1dd4dceb3c2effe6c0de2db.png

 

Share this post


Link to post
Share on other sites
3 minutes ago, arsradu said:

 

Haha! Yeah, I knew that's what you were aiming for! :)) But yeah...I'm not sure that's possible with the current implementation.

 

However, something else you might be able to do...is subscribe for notifications on the Clover's SF page by clicking the Get Updates button.

 

It's not quite the same thing, but if the point of this is to know when new releases are out...that's one way to do it. And not just new official releases, but any new development updates. If you're interested to know what's knew...that might work.

 

137324267_Screenshot2019-07-15at12_20_43.thumb.png.86f0f281f1dd4dceb3c2effe6c0de2db.png

 


Get update information from Email Release is different thing :)

I just want to know if we can do it from Clover Preference Pane with single CLover installed in EFI partition for Multi macOS/OSX in different disk :)

Share this post


Link to post
Share on other sites

@Andres ZeroCross 

 

If you had both OSes on the same drive, it miiiight have had a better chance of working. Since it's linking to the same EFI partition. But with Clover on a separate SSD...I don't see how it would work. Of course, I could be wrong here, and there might be a very simple fix for this exact scenario. I just don't know it. :) 

Share this post


Link to post
Share on other sites
Posted (edited)
2 hours ago, Andres ZeroCross said:


Get update information from Email Release is different thing :)

I just want to know if we can do it from Clover Preference Pane with single CLover installed in EFI partition for Multi macOS/OSX in different disk :)

 

I don't think so. Clover Preference Panel is installed in Preference/System for macOS Mojave (for example). You can only update through this OS. If you have another disk with Catalina (for example) with Clover  PrefPane in Preference/System, you do the same, for the same reason.

Edited by Matgen84

Share this post


Link to post
Share on other sites

Anyone install CLOVER to Catalina Disk parition from Mojave???

 I did it,  and i get issues.

1. I am in Mojave system,  i install Clover to Catalina disk and check "Clover Theme Manager'
2. After that i reboot to Catalina Disk, and when i go to /Applications with Finder, i only get Clover Theme Manager in there.
3. In Launchpad, i still can see all my Previous app
4. If i boot to Mojave again, i still can see my other App is in "/Volumes/CatalinaDiskPartition-Data/Applications" and system app still in "/Volume/CatalinaDiskPartition/System/Applications"

It's look in Catalina, CatalinaDiskName/Applications just a symlink.

How can i fix/re-index all my App???

 

image.thumb.png.6e38135902756011f7c9e0a29069c38a.png

Share this post


Link to post
Share on other sites
4 minutes ago, Andres ZeroCross said:

Anyone install CLOVER to Catalina Disk parition from Mojave???

 I did it,  and i get issues.

1. I am in Mojave system,  i install Clover to Catalina disk and check "Clover Theme Manager'
2. After that i reboot to Catalina Disk, and when i go to /Applications with Finder, i only get Clover Theme Manager in there.
3. In Launchpad, i still can see all my Previous app
4. If i boot to Mojave again, i still can see my other App is in "/Volumes/CatalinaDiskPartition-Data/Applications" and system app still in "/Volume/CatalinaDiskPartition/System/Applications"

It's look in Catalina, CatalinaDiskName/Applications just a symlink.

How can i fix/re-index all my App???

 

image.thumb.png.6e38135902756011f7c9e0a29069c38a.png

 

Why do you install CLOVER to Catalina Disk partition from Mojave? Not directly under Catalina.

 

For this re-index issue, post on catalina topic. I think.

Share this post


Link to post
Share on other sites
Posted (edited)
10 minutes ago, Andres ZeroCross said:


4. If i boot to Mojave again, i still can see my other App is in "/Volumes/CatalinaDiskPartition-Data/Applications" and system app still in "/Volume/CatalinaDiskPartition/System/Applications"

It's look in Catalina, CatalinaDiskName/Applications just a symlink.

How can i fix/re-index all my App???

 

 

 

This is normal in Catalina

If you want copy the app on /System /Applications you need the RW access

Edited by chris1111

Share this post


Link to post
Share on other sites
Just now, chris1111 said:

 

This is normal in Catalina

If you want copy the app on /System /Applications you need the RW access


The directory is normal = True

But in default condition, if you click "Applcations" folder in left sidebar menu, you will see all app in there. But now all gone.

This happened because i install clover to Catalina from Mojave and i check "Clover Theme Manager". Clover should install Clover Theme Manager in "CatalinaDiskName-Data/Applications not in "CatalinaDiskName/Applications"

Share this post


Link to post
Share on other sites

After boot to Mojave and install clover to Catalina Disk from there (check Clover Theme Manager too),, then i reboot to Catalina.

Applications menu in left side bar is gone,,

I need to make shortcut but i don't know how to do this.

/CatalinaDiskName/Applications = Empty
/CatalinaDiskName/System/Applications=Sytem App

I can't access CatalinaDiskName - Data/Aplications from Catalina system (except in Mojave).

How can i re-create index of App??? i only can use Launchpad, Spotlight search, or Finder Search to find App. 

Screen Shot 2019-07-15 at 19.16.20.png

Screen Shot 2019-07-15 at 19.16.47.png

Screen Shot 2019-07-15 at 19.17.08.png

31 minutes ago, Matgen84 said:

 

Why do you install CLOVER to Catalina Disk partition from Mojave? Not directly under Catalina.

 

For this re-index issue, post on catalina topic. I think.


Cmon,, long ago. We still can install CLOVER from any of kind of different macOS (Maverick, El Capitan, Yosemite, Sierra, High Sierra, Mojave). Even you have 6 macOS type with 1 EFI partition for Clover, you still can update CLOVER from every macOS type. It's not problem, but now Catalina use different Applications directory. So people must be carefull to not install/check "Clover Theme Manager"

Share this post


Link to post
Share on other sites
Posted (edited)
40 minutes ago, Andres ZeroCross said:



I can't access CatalinaDiskName - Data/Aplications from Catalina system (except in Mojave).

How can i re-create index of App??? i only can use Launchpad, Spotlight search, or Finder Search to find App. 

 

Did you try Finder / Preferances

Chek Box Applications 

 

339232031_Capturedcranle2019-07-1508_57_50.thumb.png.54a9b775e3f1726061b78336a034aad2.png

 

Edited by chris1111

Share this post


Link to post
Share on other sites
Posted (edited)
25 minutes ago, chris1111 said:

Did you try Finder / Preferances

Chek Box Applications 

 

339232031_Capturedcranle2019-07-1508_57_50.thumb.png.54a9b775e3f1726061b78336a034aad2.png

 


Thanks it works, but please check this image below
 

All Aplications path is different, after install clover in Catalina from Mojave (install clover theme manager too),, i need to reIndex some Applications, eg XCode-Beta.app. I need to run "sudo xcode-select --switch /System/Volumes/Data/Applications/Xcode-beta.app",, I works before with "sudo xcode-select --switch /Applications/Xcode-beta.app"


Or maybe you can make test it right now (Install Clover from Mojave to Catalina disk and check Clover Theme Manager),, you will see the different :D


 

photo_2019-07-15_19-03-38.jpg

Screen Shot 2019-07-15 at 20.05.05.png

Edited by Andres ZeroCross

Share this post


Link to post
Share on other sites
On 7/14/2019 at 12:43 PM, Slice said:

After 4992 there are no more error "Not found"?

Don't replace boot6 with boot7. boot7 is BiosBlockIo, it will not work with DVD.

And about UEFI DVD I think it is impossible because there is no EFI partition.


Did Clover get problem to patch Kext/kernel cache in Catalina?? I have this,

 

====

Find : 00040000 04030000 00000001 00000000 10000202 00000000 00040000 04030000 00000001 00000000 20010101 00000000 00040000 04030000 00000001 00000000 11020404 00000000 00040000 04030000 00000001 00000000 21030303 00000000 00040000 04030000 00000001 00000000 12040505 00000000


Replace : 00040000 04030000 00000501 00000000 12040601 00000000 00040000 04030000 00000401 00000000 22050403 00000000 00080000 04020000 00000101 00000000 11020102 00000000 00080000 04020000 00000201 00000000 21030504 00000000 04000000 14020000 00000301 00000000 10000306 00000000 


Name : com.apple.kext.AMD9500Controller
====

 

image.thumb.png.345f4644c8462a20c2eebda220cd7106.png


But patch didn't work in Catalina (Get Reddish Image with Salado fb name and can't dual display),, i have checked / open "AMD9500Controller" of Catalina with Hex Fiend.app and i still can found "00040000 04030000 00000001 00000000 10000202 00000000 00040000 04030000 00000001 00000000 20010101 00000000 00040000 04030000 00000001 00000000 11020404 00000000 00040000 04030000 00000001 00000000 21030303 00000000 00040000 04030000 00000001 00000000 12040505 00000000". So, it should be no problem.

 

image.png.78cd95ff89ab7af3b4b603995ed32155.png

But if i boot in to Mojave and use Salado as fb name for my RX 580,, i can see patch succesful (and i get normal screen with Dual Display Capability).


IMG_3350.thumb.png.aa74b6916122762d379abc4cd9f143a9.png

Share this post


Link to post
Share on other sites
Posted (edited)
30 minutes ago, Slice said:
@Andres ZeroCross
1. Are you sure Mojave patch will be same for Catalina?
2. The patch was made in RAM, not in file. No sense to check the patch in the kext.

 

 


What do you mean by "non sense to check in the file?"

AFAIK, the hex value must be founded in the kext itself. eg,, find = aaaa, replace = bbbb name = target.kext,,. Of course we must make sure we can find aaaa in target.kext itself before make otf patch with clover.

I can see "Hex byte of Find" in "AMD9500Controller" of Mojave and Catalina.

So i should see the same debug log like Mojave log. But i can't see the succesful patched log. Any explanation why did patch fail?


Sent from my iPhone using Tapatalk

 

 

 

 

Edited by Andres ZeroCross

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, Andres ZeroCross said:

AFAIK, the hex value must be founded in the kext itself. eg,, find = aaaa, replace = bbbb name = target.kext,,. Of course we must make sure we can find aaaa in target.kext itself before make otf patch with clover.

I can see "Hex byte of Find" in "AMD9500Controller" of Mojave and Catalina.

I guess that this is true until any other patch are performed on the same offset in memory before yours.

4 hours ago, Andres ZeroCross said:

All Aplications path is different, after install clover in Catalina from Mojave (install clover theme manager too),, i need to reIndex some Applications, eg XCode-Beta.app. I need to run "sudo xcode-select --switch /System/Volumes/Data/Applications/Xcode-beta.app",, I works before with "sudo xcode-select --switch /Applications/Xcode-beta.app"

Your "Machintosh SSD" should have a read-only twin called  "Machintosh SSD - Dati", but this I guess is true for vanilla installations, I'm referring to Catalina on proper apfs partition, e.g. not hfs.

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)
5 hours ago, Andres ZeroCross said:

This happened because i install clover to Catalina from Mojave and i check "Clover Theme Manager". Clover should install Clover Theme Manager in "CatalinaDiskName-Data/Applications not in "CatalinaDiskName/Applications"

This should performed as intended as the OS should take cares on what happens in the filesystem.

 

12 hours ago, Badruzeus said:

Honestly, it' s not big deal as Vector has said already he'll take a look and could be fixed later LOL

The problem is that I have a job and a family.. By the way can I ask why there's a need to use hfs instead of apfs? It is not clear to me if this is allowed.. Catalina installer creates two volumes on the same container, but what happen if we modify them?

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)
43 minutes ago, vector sigma said:

I guess that this is true until any other patch are performed on the same offset in memory before yours.

Your "Machintosh SSD" should have a read-only twin called  "Machintosh SSD - Dati", but this I guess is true for vanilla installations, I'm referring to Catalina on proper apfs partition, e.g. not hfs.

Yes,, but if you boot in to Catalina then somehow as default path for applications is "/Applications/XCode-beta.app" or in "/System/Volumes/Data/Applications/XCode-Beta.app". But if i boot to Mojave and check the Application path of Catalina app eg XCode-Beta, then yes the path is "Catalina Disk - Data/Applications/XCode-Beta.app"

43 minutes ago, vector sigma said:

I guess that this is true until any other patch are performed on the same offset in memory before yours.


The config of clover is same for Mojave and Catalina (SSDT, kext, drivers, and other exactly same). In mojave, i can see about succesful patch, but i don't see it in Catalina. I just don't know what cause of this

Edited by Andres ZeroCross

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 MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI CLOVER Z390 DESIGNARE.zip
       
      ---OPENCORE FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI OPENCORE Z390 DESIGNARE.zip
       
      ---DSDT patch requests is here---
       
      https://olarila.com/forum/viewtopic.php?f=19&t=1131
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By kylon
      Cloud Clover Editor is an open source application that allows you to manage various Hackintosh Bootloaders configs everywhere.

      Open Cloud Clover Editor
       
      Cloud Clover Editor Wiki
      Cloud Clover Editor Sources
       
       
      Features
      Supports Clover EFI, Ozmosis, Chameleon, OpenCore GUI and Text Editor Mode CCE Bank Mobile friendly  
      Officially supported browsers
      Chrome 42+ Microsoft Edge 14+ Firefox 39+ Safari 10+ Opera 29+ Opera Mobile 12+ Chrome for Android 75+ Firefox for Android 67+  
       
      Credits
      mackie100 - took some ideas from his app Clover EFI dev team Eric Slivka - new serial number Virtual1 - new serial number cecekpawon - PHP 5.3.3 patch, , help with the ACPI Loader Mode flag and more Micky1979 - Clover flying editor  (Discontinued) crusher. - Help with the ACPI Loader Mode flag Download-Fritz - Help with the ACPI Loader Mode flag Pavo - Ozmosis fields and values stehor - Ozmosis fields and values Sherlocks - General help and support gujiangjiang - General help and support  
      Please let me know if i forgot you!
    • 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  AptioMemory --> (consigliato) ->  Link download
       Può essere solo aggiunto manualmente scaricando dal link sopra e collocandolo nella rispettiva cartella
       NOTA: in questo caso non selezionare nessun OsxAptioFixDRV durante l'installazione di clover oppure rimuovetelo                        successivamente. 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
       
      *Nota: Altri driver che si possono usare  al suo posto  sono:
       informazioni 
       
      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
      Pacchetto-Fake+Sensors 6.26.1440.zip
      C_I_M.zip
       
       
       
       
       
       
       
       
       
       
       
       
       
    • By Alesss
      Good morning,
       
      I've the following pieces of hardware:
      - i7 6700K
      - GTX 1080
      - Asus Z170 Deluxe
      - NVME hard drives
       
      Yesterday I've successfully completed a High Sierra installation (I can't migrate to Mojave due to missing NVIDIA web drivers) but the system (even though it works correctly) seems to show a kernel panic at every shutdown/reboot.
       
      Please find the RunMe.app report attached.
       
      A couple of notes:
      - I've installed the audio kexts through the acidanthera AppleALC procedure
      - I've generated the SSDT with pikessdt script
      - Nvidia web drivers have been installed with the vulgo/webdriver.sh script that requires the WhateverGreen and the ngfxcompat=1 boot argument
      - AirportBrcmFixup.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext have been used to unlock the full potential of the integrated Wi-Fi card
      - I've tried to clean nvram and motherboard CMOS with no avail
      - I've tried to update Clover to the latest version but it always results in an unbootable system
       
      It's a pity because everything seems to work correctly (USB ports, graphics, Wifi card, Continuity and so on. I haven't tried sleep but I don't use it anyway ) but this crash is fairly annoying.
       
      Thank you very much,
      Alesss
       
      Send me Ales-iMac.zip
    • By Pentothal.Z
      Hello all,
      I have a working hackintosh....ok.....but it takes a lot to boot and according to the boot.log there are a few problems.
      One of them is a black screen that stays on for a long time.
      I would like to ask anyone in this community some help to fine tune my machine.
      Boot.log and config.plist attached


      Any help would be appreciated.
      bootlog.txt
      config.plist
×