Dec_Bra1n Posted June 14, 2017 Share Posted June 14, 2017 Thanks for sharing, mean this firmware thing has something to do with that freeze on blue screen issue. Where did you add this, on top or on bottom of SMBIOS? Would you mind sharing your plist. What about selecting APFS on Beta.app, have you tried that first? I got it working too, here's what I did: Split my working Sierra SSD to three partitions, Sierra, High and APFS Intalled High Sierra to High partition using Core.pkg Booted to High and erased APFS partition with APFS file system Run Core.pkg again to install High Sierra to APFS partition It's working fine with sound, Wi-Fi and display etc, but it's not something proper and it don't update / create recovery. About selecting APFS on Beta.app = Yes I did try but you get APFS upgrade option only if you install on current OS like if you install High Sierra from Sierra then installer will allow you to upgrade with APFS. Another try = I also install High Sierra from Core method but NO MORE RECOVERY DISK by this method. On High Sierra I create one APFS partition and again I install High Sierra with Beta.app on APFS partition but failed.If you stuck with Disk Utility then Problem with two thing the image of High Sierra and Firmware Features. And rest of my plist I used so many customization via DSDT very few things I have in my config.plist so my plist is almost useless But Still <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Debug</key> <false/> <key>DropOEM_DSM</key> <false/> <key>Fixes</key> <dict> <key>FixHDA_8000</key> <true/> </dict> <key>Name</key> <string>dsdt.aml</string> <key>ReuseFFFF</key> <false/> </dict> <key>DropTables</key> <array> <dict> <key>Signature</key> <string>SSDT</string> <key>TableId</key> <string>CpuPm</string> </dict> <dict> <key>Signature</key> <string>SSDT</string> <key>TableId</key> <string>Cpu0Ist</string> </dict> </array> <key>HaltEnabler</key> <true/> <key>ResetAddress</key> <string>0x0CF9</string> <key>ResetValue</key> <string>0x0006</string> <key>SSDT</key> <dict> <key>DropOem</key> <true/> <key>Generate</key> <dict> <key>CStates</key> <false/> <key>PStates</key> <false/> </dict> <key>UseSystemIO</key> <true/> </dict> </dict> <key>Boot</key> <dict> <key>Arguments</key> <string>-lilubeta -alcbeta</string> <key>Debug</key> <false/> <key>DefaultLoader</key> <string>boot.efi</string> <key>DefaultVolume</key> <string>LastBootedVolume</string> <key>Legacy</key> <string>PBR</string> <key>NeverHibernate</key> <true/> <key>NoEarlyProgress</key> <true/> <key>Secure</key> <false/> <key>Timeout</key> <integer>-1</integer> <key>XMPDetection</key> <false/> </dict> <key>CPU</key> <dict> <key>UseARTFrequency</key> <false/> </dict> <key>Devices</key> <dict> <key>Audio</key> <dict> <key>AFGLowPowerState</key> <true/> <key>Inject</key> <string>3</string> </dict> <key>USB</key> <dict> <key>AddClockID</key> <true/> <key>FixOwnership</key> <true/> <key>HighCurrent</key> <true/> <key>Inject</key> <true/> </dict> </dict> <key>GUI</key> <dict> <key>Custom</key> <dict> <key>Entries</key> <array> <dict> <key>Arguments</key> <string>kext-dev-mode=1 slide=0</string> <key>Disabled</key> <false/> <key>FullTitle</key> <string>MacOS Sierra</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\System\Library\CoreServices\boot.efi</string> <key>Type</key> <string>OSX</string> <key>Volume</key> <string>DEB04B34-03A8-473A-82F8-D2C3EC5C8000</string> <key>VolumeType</key> <string>Internal</string> </dict> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>Windows 10</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Path</key> <string>\EFI\Microsoft\Boot\bootmgfw.efi</string> <key>Type</key> <string>Windows</string> <key>Volume</key> <string>44F14A8C-53B6-42E0-B01C-3628E203C4BA</string> <key>VolumeType</key> <string>Internal</string> </dict> <dict> <key>Arguments</key> <string>kext-dev-mode=1 slide=0 -lilubeta -alcbeta</string> <key>Disabled</key> <false/> <key>FullTitle</key> <string>High Sierra</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\System\Library\CoreServices\boot.efi</string> <key>Type</key> <string>OSXInstaller</string> <key>Volume</key> <string>9038BCE9-D36B-4A83-9555-EEA6E041BA8C</string> <key>VolumeType</key> <string>Internal</string> </dict> <dict> <key>Arguments</key> <string>kext-dev-mode=1 slide=0 -lilubeta -alcbeta</string> <key>Disabled</key> <false/> <key>FullTitle</key> <string>Recovery Boot HS </string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\com.apple.recovery.boot\boot.efi</string> <key>Type</key> <string>OSXRecovery</string> <key>Volume</key> <string>438C3766-32E6-4D97-B632-2EF465E934C4</string> <key>VolumeType</key> <string>Internal</string> </dict> </array> <key>Legacy</key> <array> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>Yosemite</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Type</key> <string>Windows</string> <key>Volume</key> <string>YOSEMITE SSD</string> </dict> </array> </dict> <key>Language</key> <string>en:0</string> <key>Mouse</key> <dict> <key>DoubleClick</key> <integer>500</integer> <key>Enabled</key> <false/> <key>Mirror</key> <true/> <key>Speed</key> <integer>8</integer> </dict> <key>Scan</key> <dict> <key>Entries</key> <false/> <key>Kernel</key> <string>None</string> <key>Legacy</key> <false/> <key>Linux</key> <false/> <key>Tool</key> <true/> </dict> <key>ScreenResolution</key> <string>1366x786</string> <key>Theme</key> <string>gold_clover</string> </dict> <key>Graphics</key> <dict> <key>DualLink</key> <integer>0</integer> <key>Inject</key> <dict> <key>ATI</key> <false/> <key>Intel</key> <false/> <key>NVidia</key> <false/> </dict> <key>NvidiaSingle</key> <false/> <key>PatchVBios</key> <true/> </dict> <key>KernelAndKextPatches</key> <dict> <key>AppleRTC</key> <true/> <key>AsusAICPUPM</key> <true/> <key>Debug</key> <false/> <key>KernelCpu</key> <false/> <key>KernelHaswellE</key> <false/> <key>KernelLapic</key> <true/> <key>KernelPm</key> <false/> <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>SSD Trim</string> <key>Disabled</key> <false/> <key>Find</key> <data> QVBQTEUgU1NEAA== </data> <key>Name</key> <string>IOAHCIBlockStorage</string> <key>Replace</key> <data> AAAAAAAAAAAAAA== </data> </dict> <dict> <key>Comment</key> <string>2 Stage Glitch Fix</string> <key>Disabled</key> <false/> <key>Find</key> <data> AQAAdRc= </data> <key>Name</key> <string>IOGraphicsFamily</string> <key>Replace</key> <data> AQAA6xc= </data> </dict> <dict> <key>Comment</key> <string>change F%uT%04x to F%uTxxxx in AppleBacklightInjector.kext (credit RehabMan)</string> <key>Disabled</key> <false/> <key>Find</key> <data> RiV1VCUwNHgA </data> <key>Name</key> <string>com.apple.driver.AppleBacklight</string> <key>Replace</key> <data> RiV1VHh4eHgA </data> </dict> </array> </dict> <key>RtVariables</key> <dict> <key>BooterConfig</key> <string>0x28</string> <key>CsrActiveConfig</key> <string>0x67</string> <key>MLB</key> <string>Sexy MLB</string> <key>ROM</key> <string>Sexy ROM</string> </dict> <key>SMBIOS</key> <dict> <key>BiosReleaseDate</key> <string>05/01/17</string> <key>BiosVendor</key> <string>Apple Inc.</string> <key>BiosVersion</key> <string>MB81.88Z.0164.B31.1705021217</string> <key>Board-ID</key> <string>Mac-94245B3640C91C81</string> <key>BoardManufacturer</key> <string>Apple Inc.</string> <key>BoardType</key> <integer>10</integer> <key>ChassisAssetTag</key> <string>MacBook-Aluminum</string> <key>ChassisManufacturer</key> <string>Apple Inc.</string> <key>ChassisType</key> <string>0x09</string> <key>Family</key> <string>MacBook Pro</string> <key>FirmwareFeatures</key> <string>0xff1fff3f</string> <key>LocationInChassis</key> <string>Part Component</string> <key>Manufacturer</key> <string>Apple Inc.</string> <key>Mobile</key> <true/> <key>ProductName</key> <string>MacBookPro8,1</string> <key>SerialNumber</key> <string>My Sexy Serial Np</string> <key>Trust</key> <true/> <key>Version</key> <string>1.0</string> </dict> <key>SystemParameters</key> <dict> <key>InjectKexts</key> <string>Yes</string> <key>InjectSystemID</key> <true/> </dict> </dict> </plist> Link to comment Share on other sites More sharing options...
MNSiw Posted June 14, 2017 Share Posted June 14, 2017 About selecting APFS on Beta.app = Yes I did try but you get APFS upgrade option only if you install on current OS like if you install High Sierra from Sierra then installer will allow you to upgrade with APFS. Another try = I also install High Sierra from Core method but NO MORE RECOVERY DISK by this method. On High Sierra I create one APFS partition and again I install High Sierra with Beta.app on APFS partition but failed.If you stuck with Disk Utility then Problem with two thing the image of High Sierra and Firmware Features. I hardly ever used recovery to fix anything, so it's not that important for me to have it, still have working recovery on Sierra, right now I have Sierra and High Sierra (APFS) working on same SSD, was trying to figure out how to resize APFS parition, found diskutil apfs resizeContainer, going to try it now, thanks Dec_Bra1n 1 Link to comment Share on other sites More sharing options...
Dec_Bra1n Posted June 14, 2017 Share Posted June 14, 2017 I hardly ever used recovery to fix anything, so it's not that important for me to have it, still have working recovery on Sierra, right now I have Sierra and High Sierra (APFS) working on same SSD, was trying to figure out how to resize APFS parition, found diskutil apfs resizeContainer, going to try it now, thanks Dec_Bra1n Anytime Link to comment Share on other sites More sharing options...
ITzTravelInTime Posted June 14, 2017 Author Share Posted June 14, 2017 so guys we have a method to install mac os high sierra beta the seems to work, so post here your pictures of successful installations of high sierra and let us know 1 Link to comment Share on other sites More sharing options...
xtddd Posted June 14, 2017 Share Posted June 14, 2017 i still wait for webdriver to enable gtx960 1 Link to comment Share on other sites More sharing options...
Max.1974 Posted June 15, 2017 Share Posted June 15, 2017 Hi, my install its very simple, im think the Clover arguments is the "secret". Im using many arguments, and I can install High Sierra in APFS so easy. Im finally get terminal command work and make a usb. 25/06/2017 - Edit: Using Clover 4097 now!! So please, don't forget to delete "other" folder in EFI/CLOVER/kexts EFI.zip 7 Link to comment Share on other sites More sharing options...
nvflash Posted June 15, 2017 Share Posted June 15, 2017 (edited) I'm having trouble getting High Sierra Beta installed on a legacy bios system. Using Clover 4084, it seems kext injection is still broken for legacy bios. I created a USB Installer from the High Sierra Beta.app, but it doesn't seem FakeSMC ever loads, no Dsmos has arrived..... So I moved the PreLinkedKernel file from this thread to the .IABootFiles folder, and was able to boot from the USB stick. I was unable to properly create an APFS disk, so I booted Sierra and created one, then rebooted to the Install USB and chose the APFS disk to install too. The system copied some files and rebooted. I was able to boot from the APFS disk, but I have no FakeSMC, so the install won't continue. Trouble is, I don't have a .IABootFiles folder on my APFS disk, I only get: macOS Install Data-> AppleDiagnostics.chunklist AppleDiagnostics.dmg BaseSystem.chunklist BaseSystem.dmg ia.log index.sproduct InstallESD.dmg InstallInfo.plist Locked Files I tried to convert the BaseSystem.dmg to RW and replace the PreLinkedKernel in /System/Library/PreLinkedKernels, but my system just reboots when I try to use the modified BaseSystem.dmg, I also tied to compress it, but I just get a reboot when it should load. It must be checksummed, I'm not sure. I don't know why I only get these files, and not the .IABootFiles folder, I must be missing a step, somewhere. Can anyone offer some help? EDIT: Never mind, my own stupid fault, I didn't have FakeSMC installed. Now I seem to be stuck in a reboot loop, because the installer thinks the OSInstall.mpkg is missing or corrupt. Edited June 15, 2017 by nvflash Link to comment Share on other sites More sharing options...
MNSiw Posted June 15, 2017 Share Posted June 15, 2017 Hi, my install its very simple, im think the Clover arguments is the "secret". This setup isn't working on my hardware. Most probably it's SMBIOS issue. 1 Link to comment Share on other sites More sharing options...
Slice Posted June 15, 2017 Share Posted June 15, 2017 This screen i got when I try to install from sierra with install macOS 10.13 beta.app Same here. Then I delete apfs.efi driver and install High SIerra on HFS+ volume without the long wait. Clover 4084. It seems new version is not ready. Link to comment Share on other sites More sharing options...
Dec_Bra1n Posted June 15, 2017 Share Posted June 15, 2017 Same here. Then I delete apfs.efi driver and install High SIerra on HFS+ volume without the long wait. Clover 4084. It seems new version is not ready. Yes Sent from my XT1562 using Tapatalk Link to comment Share on other sites More sharing options...
MNSiw Posted June 16, 2017 Share Posted June 16, 2017 I have High Sierra running with APFS using Core.pkg but without Recovery HD. I tried cloning / restoring Recovery HD from High Sierra Virtual Machine it has same issue, boot but stuck on Language Selection screen or on Disk Utility. I'll try experimenting with different SMBIOS as Dec_Bra1n suggested. Link to comment Share on other sites More sharing options...
Dec_Bra1n Posted June 16, 2017 Share Posted June 16, 2017 I have High Sierra running with APFS using Core.pkg but without Recovery HD. I tried cloning / restoring Recovery HD from High Sierra Virtual Machine it has same issue, boot but stuck on Language Selection screen or on Disk Utility. I'll try experimenting with different SMBIOS as Dec_Bra1n suggested.From high sierra try to create recovery partition and and try refer https://davidjb.com/blog/2016/12/creating-a-macos-recovery-partition-without-reinstalling-osx-or-re-running-your-installer/ Link to comment Share on other sites More sharing options...
MNSiw Posted June 17, 2017 Share Posted June 17, 2017 From high sierra try to create recovery partition and and try refer https://davidjb.com/blog/2016/12/creating-a-macos-recovery-partition-without-reinstalling-osx-or-re-running-your-installer/Thanks buddy, I already tried that, same result, freeze on Disk Utility, leaving it as it is for now, everything else working perfect, recovery isn't that important. I have an old MacBook 5,1, trying to install High Sierra or Sierra on it using dosdude patch (it's running Mavericks), it boot fine but stuck halfway, I know its off topic, just sharing. Sent from my XT1060 using Tapatalk Link to comment Share on other sites More sharing options...
Dec_Bra1n Posted June 17, 2017 Share Posted June 17, 2017 Thanks buddy, I already tried that, same result, freeze on Disk Utility, leaving it as it is for now, everything else working perfect, recovery isn't that important. I have an old MacBook 5,1, trying to install High Sierra or Sierra on it using dosdude patch (it's running Mavericks), it boot fine but stuck halfway, I know its off topic, just sharing. Sent from my XT1060 using Tapatalk Never use that so no opinion Link to comment Share on other sites More sharing options...
ITzTravelInTime Posted June 18, 2017 Author Share Posted June 18, 2017 New release of clover out, the r4091 it works fine on mine machine, to upgrade your 10.12 clover configuration to work with 10.13 you have just to upgrade clover with the installer and then add the firmware features in the info.plist and the apfs.efi in the drivers 64 uefi folder, it worked fine for me and also following this method, the mac os installer works fine, the custom preliked kernel seems to not be needed 2 Link to comment Share on other sites More sharing options...
MNSiw Posted June 19, 2017 Share Posted June 19, 2017 New release of clover out, the r4091 it works fine on mine machine, to upgrade your 10.12 clover configuration to work with 10.13 you have just to upgrade clover with the installer and then add the firmware features in the info.plist and the apfs.efi in the drivers 64 uefi folder, it worked fine for me and also following this method, the mac os installer works fine, the custom preliked kernel seems to not be neededFor me it's working without apfs and firmware thing, just default Clover install with essential kexts Sent from my XT1060 using Tapatalk Link to comment Share on other sites More sharing options...
frnic Posted June 19, 2017 Share Posted June 19, 2017 There are people having problems with 4091 - I am stuck at 4084. With 4091 my boot stops with a message saying it is scanning entries. For now I have reverted back to 4081 with no prelinked kernel. I just used the same config I had in 10.12.6 and I think I added the firmware, but I am not sure it was needed. I added apfs.efi also. The installer then runs fine in 10.12.6 to install onto another internal drive - I tried both SSD and Fusion successfully. Pretty much everything works for me. My system is in my signature.I am waiting for web drivers for nVidia, but transparency works fine and I see no drop in frame rates for Elder Scrolls Online. And I am waiting for a new and improved Clover that doesn't hang on me. Otherwise it was not too hard, mostly waited for you to do the heavy lifting and then followed your lead Link to comment Share on other sites More sharing options...
ITzTravelInTime Posted June 19, 2017 Author Share Posted June 19, 2017 For me it's working without apfs and firmware thing, just default Clover install with essential kexts Sent from my XT1060 using Tapatalk ah ok, so i have to test it, but as far as i know, the apfs driver is needed if you want to install mac os high sierra on a apfs partition that will let the new system to work better with ssds (i suggest to you to use hfs+ for hard drives, since the apfs seems to not work vey well on mechanics drives Link to comment Share on other sites More sharing options...
MNSiw Posted June 19, 2017 Share Posted June 19, 2017 ah ok, so i have to test it, but as far as i know, the apfs driver is needed if you want to install mac os high sierra on a apfs partition that will let the new system to work better with ssds (i suggest to you to use hfs+ for hard drives, since the apfs seems to not work vey well on mechanics drivesYeah I'm on High Sierra with APFS on SSD and its working flawless, but I installed it using Core.pkg, I'll add apfs in UEFI to check if it make any difference Sent from my XT1060 using Tapatalk Link to comment Share on other sites More sharing options...
Guitar_Guy_77 Posted June 19, 2017 Share Posted June 19, 2017 Greetings all! Have a X79 UD5 running 10.10.5 via clover. Im able to install the macOS High SIerra - but on boot I get errors. Hoping someone here might be able to get this sorted. It has an error in the -v log cat "USBMC" where it kp's. Please note the working clover settings for my 10.10.5. Any thoughts on the log cat errors? U;timate gola is to get HS working on NVME Samsung 960 Pro. Link to comment Share on other sites More sharing options...
Gigamaxx Posted June 19, 2017 Share Posted June 19, 2017 New release of clover out, the r4091 it works fine on mine machine, to upgrade your 10.12 clover configuration to work with 10.13 you have just to upgrade clover with the installer and then add the firmware features in the info.plist and the apfs.efi in the drivers 64 uefi folder, it worked fine for me and also following this method, the mac os installer works fine, the custom preliked kernel seems to not be needed This sounds very doable how can we get the fixes? Can you please provide links to these basic fixes on first post, it would be a tremendous help, and will help to reduce unnecessary questions that have been covered like mine.. Great thread by the way, thanks for the work on this, very interesting progress as always at IM. Link to comment Share on other sites More sharing options...
schot Posted June 20, 2017 Share Posted June 20, 2017 Well tried High SIerra, on my Z97 with i7-4770 it works like a charm. Everything same as Sierra only new Clover needed and it is working. Now i upgraded to a Asus ROG Strix X99 with E5-2683v3 and... Installation went well only when the RX580 is initialized the machine crashes and reboots (i use a gt210 as helper card). Strange... even with the installation USB drive i can not boot macOS but it boots the installation, however tht is show on the gt210. Did not try yet to boot without the rx580. But i think there is an other problem with the setup. On my Other system (MSI X99A Raider with E5-2696v3) i can boot the installation only when rebooting i can not see the High Sierra partition, i tried on different disks and checked all clover drivers, but I can not see the partition, tired AFPS and HFS+ and both do not appear in the clover bootscreen. I only see sierra and windows. Tried with Clover 4081, 4084 and 4091 However on my old MSI Z97, i7-4770 High Sierra booted without trouble with the RX580. Link to comment Share on other sites More sharing options...
frnic Posted June 20, 2017 Share Posted June 20, 2017 Well tried High SIerra, on my Z97 with i7-4770 it works like a charm. Everything same as Sierra only new Clover needed and it is working. Now i upgraded to a Asus ROG Strix X99 with E5-2683v3 and... Installation went well only when the RX580 is initialized the machine crashes and reboots (i use a gt210 as helper card). Strange... even with the installation USB drive i can not boot macOS but it boots the installation, however tht is show on the gt210. Did not try yet to boot without the rx580. But i think there is an other problem with the setup. On my Other system (MSI X99A Raider with E5-2696v3) i can boot the installation only when rebooting i can not see the High Sierra partition, i tried on different disks and checked all clover drivers, but I can not see the partition, tired AFPS and HFS+ and both do not appear in the clover bootscreen. I only see sierra and windows. Tried with Clover 4081, 4084 and 4091 However on my old MSI Z97, i7-4770 High Sierra booted without trouble with the RX580. I had the same problem, no matter what I did I could not see the HS partition to boot it. I was pointed to this post and it worked for me: http://www.osx86.net/forums/topic/24540-guide-macos-high-sierra-1013-beta/ 1 Link to comment Share on other sites More sharing options...
Dec_Bra1n Posted June 20, 2017 Share Posted June 20, 2017 APFS become very slow any idea guys why but on hfs system boot fast as compared to APFS...? Also have issue with clover r4091 red screen Sent from my XT1562 using Tapatalk Link to comment Share on other sites More sharing options...
ITzTravelInTime Posted June 21, 2017 Author Share Posted June 21, 2017 APFS become very slow any idea guys why but on hfs system boot fast as compared to APFS...? Also have issue with clover r4091 red screen Sent from my XT1562 using Tapatalk if you are using apfs on an hdd, it is very slow on that kind of drives Link to comment Share on other sites More sharing options...
Recommended Posts