Jump to content
ricola

[pre-release] macOS Sierra 10.12.4

235 posts in this topic

Recommended Posts

You are first reporter now!!!! Thank you so much.

 

KernelToPatch Enable or disable not working right? Or work like r3974? I dont have good english.

Okay reversed enable/disable in KernelPatch. I will check

 

If have problem about enable/disable in KernelToPatch, i will give you file to fix this issue.

 

나의 LG-F410S 의 Tapatalk에서 보냄

I'm using Clover r3994 and Sierra 12.4

Since I made the update for Clover r3994 and for Sierra 12.4, I was without sound and without XCPM.

I did some tests and discovered the following:

With xcpm patchs enabled in Plist - Cpu blocks at maximum frequency. (No XCPM)

With xcpm patchs disabled in Plist - Everything went back to normal, XCPM working, Speedsteps working, Freq.Vectors loaded, everything loaded.

With your Fix, the sound worked fine again, but the xcpm remains the same. I only have speedsteps if I disable all the xcpm patchs in Clover.

Now I'm going to test your r3995 fix and then report as it ran :yes: 

Tanks

Share this post


Link to post
Share on other sites
Advertisement

Updating to 10.12.4 Public Beta 1 I have a deep trouble.

My screen is flickering. 

If I attach two monitors, one to Intel embedded and second to Radeon then Radeon flickering.

New system has two new kexts AMDLegacy*** and they are attached to my Radeon.

If I move them to trash them no signal.

This is deadened for my AMD Radeon HD6670. It is no more supported since 10.12.4.

As I temporary solution I work in 10.12.2 now.

Nothing new.

I currently have to to content myself with Intel HD Graphics 4600, removing AMD, injecting the id and with intel true in Clover .plist.

Share this post


Link to post
Share on other sites

Hi Sherlock,

I just tested the r3994 Fix and the r3995 Fix and the behavior was the same in both.

With both, the sound (AppleHDA) worked perfect again, but about XCPM, it only works if I disable all the patches in plist.

If I activate them, XCPM stops working. Sounds like the enable/disable are reversed in Clover r3994.

If you want, check out my latest EFI and confirm on my last plist.
BTW, according to my hardware, if you think I should change anything at EFI, please let me know! :) 

Once again, thank you.

EFI.rar

Share this post


Link to post
Share on other sites

Hi @Fergarth.

I just noticed that you set all patches' MatchOS to 10.12, but I was not sure what they mean.

Because if you want to patch something for 10.12.0 and then the MatchOS should be '10.12.0' instead of '10.12'.

But you said that AppleHDA is working and patches for kernel not, this meant that '10.12' just made no difference. (If '10.12' means '10.12.0' then your patches for AppleHDA will not be allowed.)

So I'd like to know that the patches are allowed actually? I checked your /EFI/CLOVER/misc/preboot.log but there must be something missing. May share a new one via "Clover Configurator ==> TOOLS ==> Boot.log ==> Save boot.log to desktop"?

BTW. It seems that your XCPM patches are wrong and therefore this can be a reason for why you said that XCPM not working. You just patched _cpuid_set_info() but actually this made no difference on Haswell-E. It was just required by Broadwell-E cuz we missed some data for it in kernel. So. You have to patch _xcpm_bootstrap() for Haswell-E. But I saw you had disabled it. (# XCPM Bootstrap Sierra © Pike R. Alpha) Also. Some patches for early reboot, performance, were also disabled now. I didn't know which patch for early reboot is necessary to you and thus I enabled all of them. Anyway. Less is more.

I patched your config.plist and you might check whether XCPM would be working. FYI.

No... You mean that KernelToPatch is reversed/broken... Right? Sorry for my brain got messed. In this case, give me some time to check what's wrong...

Edited by PMheart

Share this post


Link to post
Share on other sites

Hi Sherlock,

I just tested the r3994 Fix and the r3995 Fix and the behavior was the same in both.

With both, the sound (AppleHDA) worked perfect again, but about XCPM, it only works if I disable all the patches in plist.

If I activate them, XCPM stops working. Sounds like the enable/disable are reversed in Clover r3994.

If you want, check out my latest EFI and confirm on my last plist.

BTW, according to my hardware, if you think I should change anything at EFI, please let me know! :)

Once again, thank you.

 

 

i want to test 2 times.

 

first

for r3974.zip

download. and install r3974 official pkg, and replace config.plist from "for r3974.zip". before reboot, you can see what i did(i did enable your all kernel patch). then reboot.

r3974 link

https://sourceforge.net/projects/cloverefiboot/files/Installer/

 

two

r3995 newfix.zip

download. install r3994 official pkg, and replace efi files. before reboot, you use your pure config.plist(you used it before) with enable kernel patch.

 

 

report please. also i want to know when you install 10.12.3 official with r3974,  is enable kernel patch no problem?

 

 

thank you for report and effort.

Share this post


Link to post
Share on other sites

Hi @Fergarth.

I just noticed that you set all patches' MatchOS to 10.12, but I was not sure what they mean.

Because if you want to patch something for 10.12.0 and then the MatchOS should be '10.12.0' instead of '10.12'.

But you said that AppleHDA is working and patches for kernel not, this meant that '10.12' just made no difference. (If '10.12' means '10.12.0' then your patches for AppleHDA will not be allowed.)

So I'd like to know that the patches are allowed actually? I checked your /EFI/CLOVER/misc/preboot.log but there must be something missing. May share a new one via "Clover Configurator ==> TOOLS ==> Boot.log ==> Save boot.log to desktop"?

BTW. It seems that your XCPM patches are wrong and therefore this can be a reason for why you said that XCPM not working. You just patched _cpuid_set_info() but actually this made no difference on Haswell-E. It was just required by Broadwell-E cuz we missed some data for it in kernel. So. You have to patch _xcpm_bootstrap() for Haswell-E. But I saw you had disabled it. (# XCPM Bootstrap Sierra © Pike R. Alpha) Also. Some patches for early reboot, performance, were also disabled now. I didn't know which patch for early reboot is necessary to you and thus I enabled all of them. Anyway. Less is more.

I patched your config.plist and you might check whether XCPM would be working. FYI.

No... You mean that KernelToPatch is reversed/broken... Right? Sorry for my brain got messed. In this case, give me some time to check what's wrong...

attachicon.gifconfig.plist.zip

Yes, I can even change the MatchOS, but from what I've seen, it's just a question of cosmetics. As it is or with nothing, it always worked well lol. I only started to have stress since I installed Sierra 12.4 and last Clover r3994 that appears to have a bug, for the reason I mentioned.

I tried it with Clover r3974, but it did not finish the boot in 12.4 and that's why I installed r3994.

As for the Patchs, they were always the ones I used in 10.12.1, 12.2, 12.3 (betas included) and I never had problems, reboots, freezes... etc

But if you think I should change anything on my EFI, feel free to tell me. I appreciate it :) 

Share this post


Link to post
Share on other sites

Yes, I can even change the MatchOS, but from what I've seen, it's just a question of cosmetics. As it is or with nothing, it always worked well lol. I only started to have stress since I installed Sierra 12.4 and last Clover r3994 that appears to have a bug, for the reason I mentioned.

I tried it with Clover r3374, but it did not finish the boot in 12.4 and that's why I installed r3994.

As for the Patchs, they were always the ones I used in 10.12.1, 12.2, 12.3 (betas included) and I never had problems, reboots, freezes... etc

But if you think I should change anything on my EFI, feel free to tell me. I appreciate it :)

This means if Clover got an illegal MatchOS then it may set MatchOS to "" (Null string.) and thus the patch will be allowed.

IMHO. Before Clover gets stable, just revert back to 3974 and add a KernelToPatch that I mentioned in PM. And 10.12.4 should work fine with Clover r3974 w/ KernelToPatch for InjectKext.

Share this post


Link to post
Share on other sites

i want to test 2 times.

 

first

attachicon.giffor r3974.zip

download. and install r3974 official pkg, and replace config.plist from "for r3974.zip". before reboot, you can see what i did(i did enable your all kernel patch). then reboot.

r3974 link

https://sourceforge.net/projects/cloverefiboot/files/Installer/

 

two

attachicon.gifr3995 newfix.zip

download. install r3994 official pkg, and replace efi files. before reboot, you use your pure config.plist(you used it before) with enable kernel patch.

 

 

report please. also i want to know when you install 10.12.3 official with r3974,  is enable kernel patch no problem?

 

 

thank you for report and effort.

 

Thank you for your attention Sherlocks,

I'm not really sure, but if I'm not mistaken, r3974 already had it with 12.3 betas until 12.3 Final. One thing I'm sure, EFI / Plist Patchs has always been the same, but as soon as new versions of Clover or OS come out I do the updates and in fact, it has always gone well. It just went bad now with the last Clover r3994, for the reasons I said.

I have not had a chance yet, but as soon as I can, I'll try out these new FIX attached and then report it. :) 

Share this post


Link to post
Share on other sites

Thank you for your attention Sherlocks,

I'm not really sure, but if I'm not mistaken, r3974 already had it with 12.3 betas until 12.3 Final. One thing I'm sure, EFI / Plist Patchs has always been the same, but as soon as new versions of Clover or OS come out I do the updates and in fact, it has always gone well. It just went bad now with the last Clover r3994, for the reasons I said.

I have not had a chance yet, but as soon as I can, I'll try out these new FIX attached and then report it. :)

 

confirmed your report content before by myself in my laptop.

right. disable and enable become reverse. i reported it to clover team. 

 

until clover update, we have to wait.

 

thank you. have a good day

Share this post


Link to post
Share on other sites

Hi PMheart, Hi Sherlocks, (by alphabetical order) :P 

Ok, I already installed Clover r3998 on OS 12.4 and the Enable/Disable bug has been fixed. Everything went back to normal except the sound. With the same plist that always worked well, the sound stopped working. If i use the (r3994 Fix) suggested by Sherlocks, the sound works, but XCPM stops working, (unless I disable the patches as in r3994).
At this point everything works fine except the ALC1150 sound.
For sound, I use the patchs that are in the zip attachment and have been added by audio_cloverALC-120.command.zip, which always worked fine.
About the patchs for XCPM, given your knowledge, I would like to have your opinion!
If you can see my attachment and tell me which of the two plist suits my system better. One has 4 patches and the other has 7 patches, but in both XCPM works fine.
Thank you for your attention, for your knowledge, for everything... :) 

Zip.rar

Share this post


Link to post
Share on other sites

Hi PMheart, Hi Sherlocks, (by alphabetical order) :P

Ok, I already installed Clover r3998 on OS 12.4 and the Enable/Disable bug has been fixed. Everything went back to normal except the sound. With the same plist that always worked well, the sound stopped working. If i use the (r3994 Fix) suggested by Sherlocks, the sound works, but XCPM stops working, (unless I disable the patches as in r3994).

At this point everything works fine except the ALC1150 sound.

For sound, I use the patchs that are in the zip attachment and have been added by audio_cloverALC-120.command.zip, which always worked fine.

About the patchs for XCPM, given your knowledge, I would like to have your opinion!

If you can see my attachment and tell me which of the two plist suits my system better. One has 4 patches and the other has 7 patches, but in both XCPM works fine.

Thank you for your attention, for your knowledge, for everything... :)

Okay. I think you should acquaint how the patches work. I shall tell you how they work based on the comment of each patch.

Since all the patches are included in config2.plist and I won't tell anything about config1.plist, is that okay?  ;)

1. "XCPM Bootstrap Sierra © Pike R. Alpha". This is necessary. It will patch CPUID definition under _xcpm_bootstrap() and thus XCPM will be enabled on your Haswell-E.

2. "XCPM SMT Scope MSRS © Pike R. Alpha" This will prevent SMT Scope MSRs from calling. You may need this to fix early reboot issue. But typically. We don't need it. Note: You should do some experiments to know whether you need it.

3. "XCPM Idle Replace All Fix © Pike R. Alpha" This will make a difference if your 0xe2 register get locked. If your 0xe2 is okay. Just get rid of it. Else you will get an early reboot. Also. Do some experiments.

4. "XCPM PKG Scope MSRS © Pike R. Alpha" This will prevent PKG Scope MSRs from calling. Typically this is necessary. But if you can even remove this and then... Just remove it!  :P

5. "XCPM Performance Fix 1 (Fix CPU Max) © Okrasit" If you have any performance issues, just enable this one. IMHO. You ought to take a mess on here after all XCPM is okay. (So. Don't take a look at here until XCPM works.)

6. "XCPM Core Scope MSRS © Pike R. Alpha" is similar to "2. XCPM SMT Scope MSRS © Pike R. Alpha". Do some experiments to decide whether you need it.

7. "XCPM SMT Scope MSRS © Pike R. Alpha". Just the same as 2 & 6.  ^_^

 

IMHO. I don't own your case and thus I don't know details. But nevertheless. I think 1 & 3 & 4 & 5 are enough. Enable other ones if you encounter further issues...

Share this post


Link to post
Share on other sites

Also lost brightness after updating my Ivy Bridge/HD4000 Latitude E6230 to 10.12.4.b1. The brightness bar is there (thanks to IntelBacklight kext) but ineffective.

 

On rebuilding the cache, I've noticed what seems to be the culprits:

kxld[com.apple.driver.AppleMCCSControl]: The following symbols are unresolved for this kext:
kxld[com.apple.driver.AppleMCCSControl]: _gIODisplayBrightnessProbeKey
kxld[com.apple.driver.AppleMCCSControl]: _gIODisplayLinearBrightnessProbeKey
Link failed (error code 5).
Prelink failed for com.apple.driver.AppleMCCSControl; omitting from prelinked kernel.
kxld[com.apple.driver.AppleMuxControl]: The following symbols are unresolved for this kext:
kxld[com.apple.driver.AppleMuxControl]: _gIODisplayBrightnessProbeKey
kxld[com.apple.driver.AppleMuxControl]: _gIODisplayLinearBrightnessProbeKey
Link failed (error code 5).
Prelink failed for com.apple.driver.AppleMuxControl; omitting from prelinked kernel.
kxld[com.apple.driver.AppleBacklight]: The following symbols are unresolved for this kext:
kxld[com.apple.driver.AppleBacklight]: _gIODisplayBrightnessProbeKey
kxld[com.apple.driver.AppleBacklight]: _gIODisplayLinearBrightnessProbeKey
Link failed (error code 5).
Prelink failed for com.apple.driver.AppleBacklight; omitting from prelinked kernel.

Share this post


Link to post
Share on other sites
Hi PMheart, hi Sherlocks, hi RehabMan, hi others coders,

 

no way to be able to use yet adequately amd hd 5000 series and to avoid the flickering colors on the screen?

 

Help or expert advice would be very welcome.

Thanks.

Share this post


Link to post
Share on other sites

Okay. I think you should acquaint how the patches work. I shall tell you how they work based on the comment of each patch.

Since all the patches are included in config2.plist and I won't tell anything about config1.plist, is that okay?  ;)

1. "XCPM Bootstrap Sierra © Pike R. Alpha". This is necessary. It will patch CPUID definition under _xcpm_bootstrap() and thus XCPM will be enabled on your Haswell-E.

2. "XCPM SMT Scope MSRS © Pike R. Alpha" This will prevent SMT Scope MSRs from calling. You may need this to fix early reboot issue. But typically. We don't need it. Note: You should do some experiments to know whether you need it.

3. "XCPM Idle Replace All Fix © Pike R. Alpha" This will make a difference if your 0xe2 register get locked. If your 0xe2 is okay. Just get rid of it. Else you will get an early reboot. Also. Do some experiments.

4. "XCPM PKG Scope MSRS © Pike R. Alpha" This will prevent PKG Scope MSRs from calling. Typically this is necessary. But if you can even remove this and then... Just remove it!  :P

5. "XCPM Performance Fix 1 (Fix CPU Max) © Okrasit" If you have any performance issues, just enable this one. IMHO. You ought to take a mess on here after all XCPM is okay. (So. Don't take a look at here until XCPM works.)

6. "XCPM Core Scope MSRS © Pike R. Alpha" is similar to "2. XCPM SMT Scope MSRS © Pike R. Alpha". Do some experiments to decide whether you need it.

7. "XCPM SMT Scope MSRS © Pike R. Alpha". Just the same as 2 & 6.  ^_^

 

IMHO. I don't own your case and thus I don't know details. But nevertheless. I think 1 & 3 & 4 & 5 are enough. Enable other ones if you encounter further issues...

Hi friend,

When I asked, I was just curious to hear your opinion. But everything is fine, whether with 7 patches or 4, the system works perfect and stable as I want. Actually, I've mostly used only 4 and it's always been okay.

Thank you very much for your clarification :) 

Share this post


Link to post
Share on other sites

this thread about brightness working or not is getting very long haha anyway beta 1 was nice but how about beta 2 this week and my hack has been flawless with ozmosis 

Share this post


Link to post
Share on other sites

Ok, the cache rebuilding errors went away after I replaced my patched IOGraphicsFamily of 10.12.3 origin by 10.12.4.b1's patched version. I'm using Enoch so no on-the-fly patching like with Clover and I place up-versioned patched kexts in /L/E.

 

And the brightness issue was due to a simple error in DSDT's PNLF device (UID set to 0x0E instead of 0x0A)...  :blush:

 

All Ok now.

Share this post


Link to post
Share on other sites

Ok, the cache rebuilding errors went away after I replaced my patched IOGraphicsFamily of 10.12.3 origin by 10.12.4.b1's patched version. I'm using Enoch so no on-the-fly patching like with Clover and I place up-versioned patched kexts in /L/E.

 

And the brightness issue was due to a simple error in DSDT's PNLF device (UID set to 0x0E instead of 0x0A)...  :blush:

 

All Ok now.

You have brightness adjustment using Intelbacklight.kext?

Share this post


Link to post
Share on other sites

Following PNLF _UID value change, full brightness adjustment is available natively. I no longer require the IntelBacklight kext which, indeed, does not seem to work under 10.12.4.b1 (it worked Ok up to 10.12.3).

 

NB: the PNLF device of the DSDT includes the brightness definition code, i.e. the various _BCM, _BQC and _BCL methods.

Share this post


Link to post
Share on other sites

Hi friend,

When I asked, I was just curious to hear your opinion. But everything is fine, whether with 7 patches or 4, the system works perfect and stable as I want. Actually, I've mostly used only 4 and it's always been okay.

Thank you very much for your clarification :)

Oops. First of all sorry for delaying replying...

I think you can use even less than 4 patches, let's talk about the details:

"XCPM Bootstrap Sierra © Pike R. Alpha" is necessary and you have to keep it.

The rest 3 patches, which may be deleted, you may need to do some experiments to delete some of them, IMHO, "XCPM PKG Scope MSRS © Pike R. Alpha" could be not useful and thus you may disable/delete it. And the 2 other patches... Just do some experiments...

 

Hi PMheart, hi Sherlocks, hi RehabMan, hi others coders,
 
no way to be able to use yet adequately amd hd 5000 series and to avoid the flickering colors on the screen?
 
Help or expert advice would be very welcome.
Thanks.

 

Sorry. I don't have any AMD device and thus I must have no idea...

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By IDON-NO
      Supplemental update
      macOS Catalina 10.15.4 (19E287)
       
      Update went Fine 
       
      https://developer.apple.com/news/releases/?id=04082020b

    • By End3rPower50
      Hi, i want install MacOS catalina in my laptop.
      i created a USB bootable with Catalina and Clover but it crashed at startup.
      Thanks in advance. 
       
      P.S I upload my EFI’s folder and crash screenshot
       
      Sorry for my bad english.
       
      This is my laptop: 
      CPU: intel i7 6500U 
      Graphics: Intel HD Graphics 520
      Ethernet: Realtek FE Family 
      Wireless: Dell 1820A (BCM94350ZAE)
      USB 3.0
       

      EFI.zip
    • By Rohan20
      Opencore is running really really slow on Catalina 10.15.4. So It was running perfectly before I put the ssdt-pnlf for enabling Brightness control. it is running really slow and I verified my config with the sanity checker and its all correct. can someone please help. I am attaching my oc folder.

       
      https://www.dropbox.com/s/drkek0eaz19ina5/OC.zip?dl=0
       
    • By Sagnik Ganguly
      Hello I'm Sagnik Ganguly, I'm trying to dual boot macOS 10.14 and Windows 10 (already installed) on a PC with Legacy BIOS. I've two hard drives one in where the windows is installed and another which is converted to GPT to install macOS Mojave 10.14 with a partion of Mac OS Extended (Journal) or APFS but when I went to the Install Disk Selection page, I'm selecting the partition but it says "This version of macOS 10.14 cannot be installed on this computer." can you help me please? 
      P. S. My motherboard doesn't support UEFI. 
      I'm attaching some pictures of the screens.


    • By y010204025
      Disclaimer: All files of this article are from itpwd.com and rehabman ’s github.com

       
      After Testing:
       
      Graphics card: NVIDIA K1000M / K2000M / K2100M / K3000M / K3100M / K4000M / M1000M (ordinary TN1600x900 or 1920x1080), AMD W5170M / W7170M (DC2 or 4K), Intel HD4000 (ordinary TN1600x900 or 1920x1080) can be driven normally, but NVIDIA graphics card Brightness adjustment is disabled. AMD W5170m and w7170m are the best choices on 8570W and 8770W. The brightness can be adjusted normally and the graphics performance is very good. For WX7100m and WX4170m, the graphics card fans cannot be controlled, and other methods are required to control the fans. CPU: 3rd generation Intel Core i3, i5 and i7 (Ivy Bridge architecture, including all dual-core and quad-core. Celeron and Pentium are not supported), frequency conversion is normal. In general: If you have 8570W, 8770W, and hope you can get the best Hackintosh experience, it is recommended to replace the CPU with i7-3840QM / i7-3940XM, 8570W is recommended to choose W5170M, 8770W, and it is recommended to choose W7170M. In addition: If you want to have a 4K experience or perfect HIDPI, W5170m / W7170M supports 4K output, you can choose a suitable 4K screen to replace, but because 4K screens are mostly edp interface, and 8570W / 8770W motherboard is lvds interface, This requires a custom screen cable, which seems to be a difficult choice, but you can choose to do it yourself or buy it separately. In China, taobao.com is almighty and may be more suitable for you than eBay.
       
      EFI features:
      out of the box, the relevant hardware can be driven after the OS is installed, and it is easy to use without code operation.
      Supported models: HP EliteBook 8470p, 8570p, 8570w, 8770w (click the model for official specifications)
      Wireless network card: Recommended: BCM94360cd (requires ipex4 to ipex1,3 antenna 1300mbps), BCM94352HMB / DW1550 (2 antennas, 867mbps)
      Wireless characteristics: no white list, wireless network card with Bluetooth does not support the Bluetooth function of the wireless network card (also does not need to shield the pins), but the wireless normal use, you need the Bluetooth function to use this machine comes with Bluetooth:
      Clover version: 5103, keyboard mapping has been added Command key = Alt key, Option key = Win key
      Supported systems: macOS Mojave 10.14.6 (18G103)-macOS Catalina 10.15.x,
       
      Notes on known issues:
      1. The touchpad and the left and right keys under the touchpad are normal, the pointing stick and the left and right keys above the touchpad are temporarily unavailable (recommended to use the second generation of Apple Magic Trackpad)
      2. Indicator display problem (can be ignored, function is normal): Caps light is sometimes not switched in time, mute / wireless key may be yellow
      3.AMD graphics card / Intel nuclear display has supported sleep and 15 levels of brightness adjustment, NVIDIA has no
      4. If the AMD graphics card enters Huaping, refer to editing the Clover startup parameters, and add the Boot parameter radpg = 15 (the EFI file that has been configured with this parameter has been uploaded, refer to the following EFI-guided download link)
      5. Using the above NVIDIA graphics card with a normal TN screen 1600x900 or 1920x1080 can not enter the installation interface, please check whether the VBiOS of the graphics card is exclusively for HP, thank you for your test face K1000M
      6. Due to product design defects, the MSata positions of 8570w and 8770w cannot be used as boot disks, so EFI boot can only be placed on the main hard disk (turn the machine over and open the hard disk in the lower left corner of the cover, which is the main hard disk). Put on msata plate
      +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
      Hardware requirements:
      Model: 8470p, 8570p, 8570W, 8770W 1 or more, it is recommended to use another notebook for emergency Hard disk: It is recommended to choose an SSD hard disk of 240g or more. Samsung or Intel SATA hard disk is a good choice. Wireless card: BCM94352HMB, DW1550, BCM94360CD, miniPCIe slot U disk: 1 for 16g and above, another winPE emergency USB disk is recommended If you use a rescue USB flash drive, it means that you read this post carefully
       
      Make and install a USB flash drive:
      Get the mirror: please do it your way Making and installing a USB flash drive: macOS command line production is recommended, whether it is a real macOS model or a virtual machine (although this is not allowed to be discussed in many forums)Or you can choose to use TransMac or ether under Windows. This is not recommended, but it is simple enough for those new to Hackintosh. Make boot U disk: If you know how to put the boot into the installation U disk, unzip the EFI file and put it in the EFI partition, or you can choose a fat32 format U disk to store the EFI file separately Note: EFI is an unzipped folder, not a zip or ISO suffix file.
       
      BIOS settings From RehabMan
      To start, set BIOS to defaults.
      Then insure:
      UEFI boot is enabled (hybrid/with CSM for best result) secure boot is disabled disable fast boot IGPU graphics memory set to 64mb, if available disable the serial port via BIOS option, if available disable "LAN/WLAN switching", if available disable "Extended Idle Power States" if you find it under "Power Management Options" disable "Wake on LAN" and "Wake on USB" disable Firewire/IEEE 1394, if your laptop has it for Skylake and KabyLake laptop, enable "Launch Hotkeys without Fn keypress" Note: If you have a laptop with switchable graphics, leave it enabled. You can still use it on Windows, although the discrete card will be disabled when running OS X by the ACPI patches provided here. If you want to also disable it in Windows (via BIOS option), make sure you read about the DGPU option in your model specific SSDT (source is in SSDT-HACK.dsl), as in the scenario where the DGPU is disabled by BIOS, DGPU should be set to zero.
       
      Install:
      Please modify according to the above BIOS settings: Press F9 after booting, select the boot efi to file option, which is generally the last item. Enter your boot USB disk to find the location of cloverx64.efi, select cloverx64.efi, press Enter, and enter the clover boot interface. Select the location of the install entry and press Enter. Enter the macOS interface, use the disk tool to format the partition you need to install to hfs + or apfs format, do not choose the encryption option, this will make your efforts in vain. Note: The disk must be in gpt format, and the remaining EFI space is greater than 200M, 300mb + is recommended. If it is not, please try to modify it in WindowsPE environment. This may cause you to lose the Windows system boot and disk data. Please prepare for backup.
      After formatting the partition successfully, close the disk tool and select install, you will find the partition you installed, and follow the interface prompts. When the installation reaches a certain progress, it will restart. When restarting, select F9, enter from the boot U disk, select the disk partition where you installed macOS (no longer the U disk installation), the installation will continue, and it may restart 2 ~ 3 times Every time, you need F9 to select the boot. After entering the installation interface, except for the first installation, select the U disk, and then select the disk installation partition. Eventually you will enter the settings interface. After following the interface prompts, you will enter the macOS system interface. Remember the system password and turn off the Find my mac option.  
      Post install:
       
      After the installation is complete, you need to hang the EFI partition of the disk, copy the EFI file of the U disk to the EFI partition of the disk, so that you can directly use the disk to boot, otherwise you need to select the U disk to boot each time. The mount tool can choose cloverconfigurator. If after copying the EFI file to the disk, the computer cannot recognize your clover boot, you can use the custom boot option of bios: set the custom boot path to \efi\clover\cloverx64.efi, and set it as the first boot, Use bootice or easyUEFI to increase the clover boot option under Windows and set it as the first boot. If you do not have a wireless network card available temporarily, you can use the USB binding function of your Android phone to share the network. This may require the HoRndis driver. It is not recommended to use a US wireless network card. If you need Windows or Linux, you can install it normally. Be careful not to let Windows overwrite your boot files.  
      For other uses of macOS and brew, please pay attention to forums and other communities. Hackintosh is just the beginning.
       
      Finally, I would like to thank rehabman, vit9696 and others who contributed to Hackintosh. I also thank Cwen for his efforts to modify files and hardware tests. I hope that Hackintosh will be eternal.
       
      Please comply with the laws and regulations of your country or region. My description may not be clear or professional, but I think it is necessary. I think the existence of Hackintosh is everyone's technical hobby and experience macOS, not as a substitute for macOS cheap hardware.

      EFI_8x70_5103_W7170m_20200116 .zip
×