Jump to content
Allan

macOS High Sierra - Final Release is out! (17A365)

448 posts in this topic

Recommended Posts

@cyberdevs:

 

My FFM and FF are always up to date (that is, the values that are implemented within Clover), so that shouldn't have been the problem in my case... 

By the way: updating my ProBook (Clover UEFI, EmuVariableUEFI.efi present) went really smooth. 

 

At the same time, macrumors is full of people having the exact same problem on a real mac and as far as I can see it's mostly due to a corrupted EFI partition or third party harddrive/SSD.

 

Weird.

Yes that is weird indeed. I had some issues with multiple HDDs being attached to the system a while back and I had to disconnect them all to avoid the error. That was before I discovered the role that the EmuVariableUEFI.efi and the nvram.plist were playing (although nvram.plist never caused the error on my setups but some other people claimed that removing it helped).

 

Anyways I will be doing some more tests later on to see if it's still happening to me or not and if so why. ;)

Share this post


Link to post
Share on other sites
Advertisement

Yup. Well like I said clearing NVRAM (sudo nvram -c) did the trick for me, so I can see that nvram.plist could be an issue. We'll see how it goes when 10.13.1 beta 2 is there  :D

Share this post


Link to post
Share on other sites

I did not encounter the OSinstall.mpkg error since DP2 up to the final release.

However, It happened to me when installing 10.13.1 beta 1. I'm on legacy ESP install, so no EmuVariableUEFI.efi. Disconnected all drives except the one I was installing too (...), but still ran into this error.

Removed install data, redownloaded the update, ran nvram -c and was able to run the second stage without problems.

 

I too experienced this exact same issue when attempting to update a legacy ESP system to the 10.13.1 Beta 1 update directly from the App Store.   Could you list any/all terminal commands (is it just: sudo nvram -c ?) you used to delete the nvram files from your system which then allowed you to successfully apply the update ?   Thank you !

Share this post


Link to post
Share on other sites

Fix for ICH10 with High Sierra. Now with hot-plug support.

 

For this we need two binary patches.

First patch fix I/O error for ICH10:

4585F60F 95C289C8 83E0FE66 85C9780F 84D2750B -> 89C883E0 FE6685C9 0F98C141 08CC9090 9090750B 

With second patch will work hot-plug:

89C82540 6002003D 40200000 750C81E1 BF7FFFFF 898B5101 0000 -> 90909090 90909090 90909090 90909090 90909090 90909090 9090

With these two patches I got ICH10 with hot-plug.

attachicon.gifСнимок экрана 2017-09-30 в 14.40.42.png

 

Good luck ;)

hello. hotpatch in ICH9 not working.

Share this post


Link to post
Share on other sites

I too experienced this exact same issue when attempting to update a legacy ESP system to the 10.13.1 Beta 1 update directly from the App Store.   Could you list any/all terminal commands (is it just: sudo nvram -c ?) you used to delete the nvram files from your system which then allowed you to successfully apply the update ?   Thank you !

I removed the install data (/macOS Install Data/) folder, cleared NVRAM by indeed "sudo nvram -c" and redownloaded the update again.

I did not delete nvram.plist

Share this post


Link to post
Share on other sites

Carbon Copy Cloner (CCC) now able to successfully and directly clone a macOS High Sierra 10.13 APSF Drive! 

 

Straight system disk backup also for APFS Drives! Gorgeous!  :thumbsup_anim:  

 

Yeah, I was stupid enough to install High Sierra on case-sensitive APFS. Used CCC to clone to APFS (non-sensitive), worked great

Share this post


Link to post
Share on other sites

Today I wanna update EL Capitan to High Sierra So I downloaded Install macOS High Sierra.app from App Store instead of showing 5GB file Show 14MB. I delete that file from Application even from recycle bin and re download from app store still same no difference..

Now how to create USB installer ??

Share this post


Link to post
Share on other sites

Well, creating the USB installer is not the problem here. Getting the full installer app is.
 
You can create the USB installer using createinstallmedia command. Problem is, you need to have the FULL installer app in the Applications folder.
 
I found this article from OSX Daily to help you with the download part. See if it helps.
 
To make the USB installer, open Terminal and run this command:

sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ macOS\ High\ Sierra.app --nointeraction

When done, install Clover on the USB drive, and you should be good to go.

 

Note 1: the command above assumes the default name of your USB drive is Untitled.  If it's not, make sure you update either the name of the drive itself, or the one in the command above, so they match.

 

Note 2: having Clover on the USB drive itself is not mandatory, though in my experience, it is recommended. If you're coming from an already working system, you can use the Clover on your HDD/SSD and just start your USB installation from there.

Share this post


Link to post
Share on other sites

Well, creating the USB installer is not the problem here. Getting the full installer app is.

 

You can create the USB installer using createinstallmedia command. Problem is, you need to have the FULL installer app in the Applications folder.

 

I found this article from OSX Daily to help you with the download part. See if it helps.

 

To make the USB installer, open Terminal and run this command:

sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ macOS\ High\ Sierra.app --nointeraction

When done, install Clover on the USB drive, and you should be good to go.

 

Note 1: the command above assumes the default name of your USB drive is Untitled.  If it's not, make sure you update either the name of the drive itself, or the one in the command above, so they match.

 

Note 2: having Clover on the USB drive itself is not mandatory, though in my experience, it is recommended. If you're coming from an already working system, you can use the Clover on your HDD/SSD and just start your USB installation from there.

 

I've been plagued with the 19Mb High Sierra download and that little tool mentioned in the OSX Daily article works great! Thanks arsradu :)

Share this post


Link to post
Share on other sites

Yup. Well like I said clearing NVRAM (sudo nvram -c) did the trick for me, so I can see that nvram.plist could be an issue. We'll see how it goes when 10.13.1 beta 2 is there  :D

 

It's still a "No Go" as far as attempting to update to 10.13.1 Public Beta 1 from the App Store.  

 

Things I have tried:

 

- running sudo nvram -c in terminal

​- updating Clover to v2.4k_r4220

- completely removing Windows 10 system which exists on a separate SSD from my rig

- Out of desperation and even though its been reported as no longer necessary, I even tried inserting 0xe907f537 within the Firmware Features in Clover SMBIOS field

 

Each attempt resulted in the same occurrence; Clover stalls/crashes on the installations initial reboot.   Verbose reports some nonsense about needing to rebuild the prelinked-kernel however my suspicion is that I am still not able to circumvent Apple's Firmware check.

 

Upon hard booting my rig, macOS 10.13 boots with no issue and I am left with the macOS Install Data folder as a reminder that updating has indeed failed once again.

Share this post


Link to post
Share on other sites

Fix for ICH10 with High Sierra. Now with hot-plug support.

 

For this we need two binary patches.

First patch fix I/O error for ICH10:

4585F60F 95C289C8 83E0FE66 85C9780F 84D2750B -> 89C883E0 FE6685C9 0F98C141 08CC9090 9090750B 

With second patch will work hot-plug:

89C82540 6002003D 40200000 750C81E1 BF7FFFFF 898B5101 0000 -> 90909090 90909090 90909090 90909090 90909090 90909090 9090

With these two patches I got ICH10 with hot-plug.

attachicon.gifСнимок экрана 2017-09-30 в 14.40.42.png

 

Good luck ;)

 

Thanks ! My HDD for Time Machine works nice now with this patches (AppleAHCIPort.kext modded => Trash ! )

Share this post


Link to post
Share on other sites

Hi,

 

i'm having problems currently on updating from the macOS High Sierra Beta to High Sierra Final. Tried everything, OTA Update, Boot via USB Flash Drive. Just nothing works.

I'm always stuck in the loading screen and the picture is just frozen with the Apple Logo and the loading circle. 

 

I have to say that i had some of these crazy problems the time i installed the beta too. I used the EFI folder from @cyberdevs and got it working. After updating i put back my EFI folder and everything worked fine.

Maybe i have the same problem again? I already updated the SMBIOS.

 

I'm currently using these SMBIOS settings:

 

BiosVersion: MP61.88Z.0120.B00.1708080652

Release Date: 08/08/2017

Firmware Features: 0xE80FE136

Features Mask: 0xFF1FFF3F

Plattform Features: 0x04

 

Maybe someone is nice enough to give me his EFI folder so i can try to get it work that way? :)

 

You need to boot in verbose mode, -v, so we can see when in the boot process your computer is hanging.  Also, you need to post your computer's specs in you signature?  Do you really think that the type of hardware you have doesn't matter?

 

That said, I can pretty much assure you that your video is not loading because that produces the scenario you described of the apple logo and the spinning circle at the same time.  You need to have only one detectable video card, your OEM SSDT, and let Clover generate P-States and C-States.  That's what got the Intel HD video to load on my laptop.  I have no idea what it will take for you without your specs.

Share this post


Link to post
Share on other sites

It's still a "No Go" as far as attempting to update to 10.13.1 Public Beta 1 from the App Store.  

 

Things I have tried:

 

- running sudo nvram -c in terminal

​- updating Clover to v2.4k_r4220

- completely removing Windows 10 system which exists on a separate SSD from my rig

- Out of desperation and even though its been reported as no longer necessary, I even tried inserting 0xe907f537 within the Firmware Features in Clover SMBIOS field

 

Each attempt resulted in the same occurrence; Clover stalls/crashes on the installations initial reboot.   Verbose reports some nonsense about needing to rebuild the prelinked-kernel however my suspicion is that I am still not able to circumvent Apple's Firmware check.

 

Upon hard booting my rig, macOS 10.13 boots with no issue and I am left with the macOS Install Data folder as a reminder that updating has indeed failed once again.

 

Firmware failure most likely will result in an error message from the installer itself (i.e. "macOS couldn't be installed on this computer [an error occurred while verifying firmware|OSinstall.mpkg missing or damaged])

and not in Clover crashing. Take a pic from the verbose at the point it stalls.

Share this post


Link to post
Share on other sites

Hi Guys, 

 

The OSinstall.mpkg missing or damaged issue on hacks can be caused by incorrect FakeSMC keys stored in NVRAM.  

 

You can try updating to @Slice's latest FakeSMC v3.50 which @Sherlocks reported fixes osinstall.mpkg issue related to EmuVariableUefi-64.efi on HS - post#277.

Share this post


Link to post
Share on other sites

I think we've all been at that point a few times. This happens when you do it right. (instead of doing it wrong and use some ready to go thing that will patch your system with loads of modded kext files but you don't know exactly what's going on and for the price of what)

 

If you can get to the desktop with -x it's not that bad. Without knowing your system I'd recommend this: In most cases it's the best option to start excluding the graphics drivers first. You are booting VESA mode anyway, so I'd recommend to start with an mkdir an make a new folder called e.g. extensions_disabled and move your graphics drivers there from S/L/E. From there you can see if it boots fine w/o -x and start adding drivers back. You can always move them back by booting into -s, doing fsck and mount and after that just cd .. in your directory and move files with mv. 

This. Did everything myself without using any patches. Will try to disable the drivers. Maybe that's the key to success. 

 

 

That looks like a Clover/EFI issue to me. What did it change in there from Beta to Final? I remember having this issue while trying to recover a Skylake build. In my case, it was just missing kexts in Clover/kexts/Other. I just forgot to add the kexts (especially FakeSMC) in there. I managed to get Clover installed on the USB drive, using another computer, but I totally forgot to add the kexts, too. So i was having all kinds of crazy issue.

 

By the way, I understand your frustration. I had to recover a Skylake build after simply updating it to 10.13 and installing the Nvidia drivers. And now that I think about it, there might have been a better way to fix it. But you know, when you're in the moment, you don't always find the best solution. So you try what you know hoping that it will work. Sometime does, sometimes (like in my case booting with nv_disable=1), doesn't. So you need to improvise.

 

Like creating a bootable USB with Clover on it. Having all the right files on it. Optionally with MacOS install on it, as well. But Clover is essential here.

 

And, pro tip: update your kexts once in a while. Not having NvidiaGraphicsFixup.kext updated from 1.1.2 to 1.1.3 (if you think that's a minor update, well, you would be wrong) cost me a lot of time and stress. So yeah, update your kexts once in a while.

 

And pro tip #2: try to use, as much as possible, supported hardware. Do your research before trying to make a computer run software that's not supposed to run by default. Having a supported video card, for example, can save you from A TON of pain and frustration. And this is just one example. So do your research beforehand.

I was really frustrated and already thought about an clean install only cause i put a lot of time into it to get it back running and nothing worked.

Like i said back in the Beta i had the same problems. I used other EFI Folders and run into the same problems until i got one that worked. 

 

I currently have an Sapphire R9 390 Nitro running in the system. Got it working with an Boot GPU (Nvidia) cause i use an Intel Xeon CPU (I first build the system for gaming only). It worked very fast on Sierra and in the High Sierra Beta.

Didn't had any issues with it. As well as System Updates via the Update Tab on the Mac App Store. Only these Big Update are a pain in the .... for me. I also have to to update the amd controllers after an big update to get the GPU back

running fast.

Share this post


Link to post
Share on other sites

Well, creating the USB installer is not the problem here. Getting the full installer app is.

 

You can create the USB installer using createinstallmedia command. Problem is, you need to have the FULL installer app in the Applications folder.

 

I found this article from OSX Daily to help you with the download part. See if it helps.

 

To make the USB installer, open Terminal and run this command:

sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ macOS\ High\ Sierra.app --nointeraction

When done, install Clover on the USB drive, and you should be good to go.

 

Note 1: the command above assumes the default name of your USB drive is Untitled.  If it's not, make sure you update either the name of the drive itself, or the one in the command above, so they match.

 

Note 2: having Clover on the USB drive itself is not mandatory, though in my experience, it is recommended. If you're coming from an already working system, you can use the Clover on your HDD/SSD and just start your USB installation from there.

 

Thank You .. appreciate..

 

But why this problem started from this version ?

Before I have download macOS sierra that have no problem.

Share this post


Link to post
Share on other sites

Fix for ICH10 with High Sierra. Now with hot-plug support.

 

For this we need two binary patches.

First patch fix I/O error for ICH10:

4585F60F 95C289C8 83E0FE66 85C9780F 84D2750B -> 89C883E0 FE6685C9 0F98C141 08CC9090 9090750B 

With second patch will work hot-plug:

89C82540 6002003D 40200000 750C81E1 BF7FFFFF 898B5101 0000 -> 90909090 90909090 90909090 90909090 90909090 90909090 9090

With these two patches I got ICH10 with hot-plug.

attachicon.gifСнимок экрана 2017-09-30 в 14.40.42.png

 

Good luck ;)

As I said before Hot-Plug patch work like a charm for 7-Series and Asmedia. I try also Fix I/O patch without Fabio1971's kext; system show Generic. So, I always use the AppleAHCIPort.kext by Fabio1971 (EFI/Clover/Kext/10.13) the GenericAHCI display by the system instead of "Asmedia"  :)

 

Sorry for my bad english.

post-1110743-0-28763000-1506840889_thumb.png

Share this post


Link to post
Share on other sites

Thank You .. appreciate..

 

But why this problem started from this version ?

Before I have download macOS sierra that have no problem.

 

I'm not sure. I would say it's a server issue on Apple's side...? Because, on the same system, sometimes it works, sometimes it doesn't. I've also encountered this issue with a Skylake build. Never with the one in the signature. So not sure what to say. I have no technical explanation for it. Just that, maybe, sometimes, the server fails to download the file. Maybe something is not properly recognized, maybe too many people download the same thing at the same time... I honestly don't know.

Share this post


Link to post
Share on other sites

Fix for ICH10 with High Sierra. Now with hot-plug support.

 

For this we need two binary patches.

First patch fix I/O error for ICH10:

4585F60F 95C289C8 83E0FE66 85C9780F 84D2750B -> 89C883E0 FE6685C9 0F98C141 08CC9090 9090750B 

With second patch will work hot-plug:

89C82540 6002003D 40200000 750C81E1 BF7FFFFF 898B5101 0000 -> 90909090 90909090 90909090 90909090 90909090 90909090 9090

With these two patches I got ICH10 with hot-plug.

attachicon.gifСнимок экрана 2017-09-30 в 14.40.42.png

 

Good luck ;)

 

 

doesn't work for me !

 

does anyone know the patch to apply?

post-1373167-0-02539400-1506847207.png

Share this post


Link to post
Share on other sites

I really need help with the Update. I unpluged the Boot GPU and now i'm in the Update Settings. Problem now is, that apparently my system isn't allowrd to pass the Firmware check even with using current SMBIOS Settings that i posted earlyer. Maybe someone would be nice enough to post hus EFI folder to me to use for the update? Please

Share this post


Link to post
Share on other sites

@all

in this final High Sierra release is it possible to boot in "VGA"mode if you have a Nvidia (Pascal,Maxwell) if you have Nvidiaweb driver installed?

in my case all old method do not work

maybe

 

<dict>
<key>Comment</key>
<string>17A365 to 16G29</string>
<key>Disabled</key>
<true/>
<key>Find</key>
<data>
PHN0cmluZz4xN0EzNjU8L3N0cmluZz4=
</data>
<key>InfoPlistPatch</key>
<true/>
<key>Name</key>
<string>NVDAStartupWeb</string>
<key>Replace</key>
<data>
PHN0cmluZz4xNkcyOTwvc3RyaW5nPg==
</data>
 

Share this post


Link to post
Share on other sites

 

Everything works here almost perfectly

I am really proud of the work accomplished
on my HP ProBook 6570B B)

 

Did you got a good performance with APFS?

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
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
       
    • By ThatsMatt
      Salve, sono nuovo nel forum e mi serviva una mano nell'installazione dell' ultima versione di MacOs sul mio notebook HP Pavilion 15-ak112nl.
      Specifiche Tecniche: 
      CPU: Intel Core i7-6700HQ (2.60 / 3.50 GHz, 4 core, 6 MB CACHE L3). 
      Scheda Grafica: Intel HD Graphics 530 + NVIDIA GeForce GTX 950M 4 GB DDR3.
      Hard Disk: 1 TB SATA 5400 rpm.
      Ram: 8 GB DDR3L-1600.
      Audio: altoparlanti stereo Bang & Olufsen PLAY. 
      Rete: LAN 10/100, WLAN 802.11b/g/n, bluetooth 4.0 (Miracast).
      Grazie in Anticipo a chi mi risponderà
    • By fantomas1
      First beta... macOS Catalina 10.15 beta (19A471t)  Release Notes!!!
       
      Useful information:
       
      macOSDeveloperBetaAccessUtility.dmg.zip (thanks to gengik84)
      Clover r4945 (thanks to Cyberdevs)
      Lilu_plugins (thanks to gengik84)
      Port Limit Patch (thanks to daliansky)
      older non metal nVidia and Intel cards (thanks to fusion71au)
      MBR installation on macOS Catalina (thanks to crazybirdy) - workaround!!!
    • By t0mmenhansen
      I havent used my hackintosh in a while. I wanted to boot to my mac drive. This error comes up when i try to boot. Ive tryed using explorer++ and update the lilu kext and whatevergreen kext, no luck yet. Any ideas?
       
      9700k
      16GB corsair
      1080 nvidia card
      z370-f mobo
      mac drive is an SSD from kingston
      Display port outpoot
       
    • By fantomas1
      Première bêta... macOS Catalina 10.15 beta (19A471t)
       
       
      anciennes carte graphiques Nvidia + Intel HD 3000
×