Jump to content
Allan

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

448 posts in this topic

Recommended Posts

Advertisement

New createinstallmedia terminal command?

 

There is no new createinstallmedia terminal command - it's always the same and works well.

Usage: createinstallmedia --volume <path to volume to convert>

Arguments
--volume, A path to a volume that can be unmounted and erased to create the install media.
--applicationpath, A path to copy of the OS installer application to create the bootable media from.
--nointeraction, Erase the disk pointed to by volume without prompting for confirmation.

Example: createinstallmedia --volume /Volumes/Untitled

This tool must be run as root.

Result:

Last login: Tue Sep 26 10:43:58 on ttys000
fantomass-iMac:~ fantomas$ sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ High\ Sierra.app 
Password:
Ready to start.
To continue we need to erase the volume at /Volumes/USB.
If you wish to continue type (Y) then press return: y
Erasing Disk: 0%... 10%... 20%... 30%...100%...
Copying installer files to disk...
Copy complete.
Making disk bootable...
Copying boot files...
Copy complete.
Done.
fantomass-iMac:~ fantomas$

Share this post


Link to post
Share on other sites

 

Hi Guys,

 

Successfully updated both my desktop systems and my Dell XPS M1530 notebook to High Sierra Release - 10.13_17A365 :).

 

1.  GA-P55aUD3 with legacy BIOS/Intel i5-750/ATI HD5770/HFS+ HDD

 

2.  Skylake NUC6i5SYH with UEFI/Intel i5-6260U/Iris 540/APFS SSD

 

3.  Dell XPS M1530 legacy BIOS/Intel T9300/Geforce 8600M GT/HFS+ Ext HDD

 

 

Installation Notes
  • "Install macOS High Sierra.app" v 13.0.64 run directly from Applications folder for upgrade install of existing GM_17A362a
  • Updated to latest Clover r4220, Clover injected default values for FF/FFM/PF and BIOS ver/date/Board-ID data (iMac11,3, iMac17,1, MBP7,1) --> avoid error while "verifying firmware"
  • Latest apfs.efi driver in /EFI/CLOVER/drivers64 or /EFI/CLOVER/drivers64UEFI (only needed if APFS target volume)
  • Removed NVRAM.plist files from all EFI partitions (incl USB drives), ran sudo NVRAM -c command in terminal to reset NVRAM prior to update
  • On my Skylake NUC, I don't need or use EmuVariableUefi-64 ---> avoid OSInstall.mpkg damaged/missing error
  • If upgrading existing OS X on HDD, HFS+ is preserved (on SSD HFS+ will be converted automatically to APFS)
  • Certain SATA controllers will still have issues with AppleAHCIPort v329 (eg ICH10, 5 series, 7 series, ASMedia 1061) ---> Disks may fail to initialize, not readable or hot plug may fail.  AppleAHCIPort.kext v328 with version bundle 999.1.1 survives upgrade if installed in /L/E, and is loaded in preference to v329
  • A windows disk present on the machine during installation is OK.

 

Here, with the kexts on 10.13, the installer did not go up, only in Other.

 

EFI/Clover/kexts/Other

 

 

 

Share this post


Link to post
Share on other sites

 i have used same config.plist and kext/other that im runing with beta version to install the final version but stuck at

 

sound assertion in applehdadriver at line

 

any idea ?

Share this post


Link to post
Share on other sites

Guys, if you still are on a beta or GM build, do not bother with creating a new usb installer with createinstallmedia, use startosinstall instead. :yes:

 

It will start HSierra install and will save you time and stress. :P;)

 

 

what is the method to install in HFS? :rolleyes:

 

 

my HDD is in HFS! ;)

Share this post


Link to post
Share on other sites

Guys, if you still are on a beta or GM build, do not bother with creating a new usb installer with createinstallmedia, use startosinstall instead. :yes:

 

It will start HSierra install and will save you time and stress. ;)

 

 

 

 

my HDD is in HFS! ;)

I just ran the .app I downloaded from app store. What is startosinstall?

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

You'll find it in the same folder as createinstallmedia 

 

/Applications/Install macOS Sierra.app/Contents/Resources

 

For me the installer has only 20 MB, why ? 

Share this post


Link to post
Share on other sites

I found something interesting on my ICH10 hack with 10.13:

I have 2 HDD WesternDigital that not working under 10.13 with AppleAHCIPort v329

Also I have 1 HDD Hitachi and 1 SSD Kingston that are working fine under 10.13 with v329

I tried changing sata ports but the result is the same: WD HDDs not working and Hitachi HDD and Kingston SSD are working fine, I can install HS on them without any trick(changing AppleAHCIPort or anything).

Share this post


Link to post
Share on other sites

I just ran the .app I downloaded from app store. What is startosinstall?

 

Sent from my SM-G930F using Tapatalk

You can find explanation on previous thread: http://www.insanelymac.com/forum/topic/324194-pre-release-macos-high-sierra/page-191 But I don't try it because I don't know how to migrate apps and data with this method

Share this post


Link to post
Share on other sites

Anyone has tried with an amd r7 vga?

 

I've got the black screen after apple logo problem, but the strange thing is that lilu + whatevergreen didn't fix it. I'm also using Pike's path for GraphicPolicy.kext

 

I'm using the r7 260x with fakeid injection connected with displayport. Even if screen si black I can hear sound routed from the vga.

Also if I boot with the intel igpu I can notice that the 260x is detected and (as ioRegistyExploer reports) everything is as in El Capitan.

 

I couln't understand why it isn't working.

 

 

Inviato dal mio iPhone utilizzando Tapatalk

Share this post


Link to post
Share on other sites

how did you install it in HFS?

 

 

As I said, I previously had GM installed on my HFS+ formatted HDD. Then I downloaded HS final release. When I wanted to create my new usb installer with createinstallmedia, I was curious about that startosinstall file that I found in the same folder (/Applications/Install macOS Sierra.app/Contents/Resources). I just clicked on it and Terminal was opened. Asked me to agree the licence (put A for agree) and my PC rebooted. After rebooting, it directly came at the second stage, when the install started (it remains 45minutes...).   :)

 

EDIT:

 

As I launched that file from my primary partition (to be installed on it), the installation processing worked well (finally, it more updated my GM build, instead of made a proper install), my apps and files were all safe.   :yes:

 

EDIT 2:

 

The funny thing in this story is that I have no longer HS app in my Application folder.   :P . I guess it served as a temporary file and once installed ,the app has been deleted.

Edited by fantomas1

Share this post


Link to post
Share on other sites

All fine except sleep (first hack in signature).

0YM1ZkS.png


LuCys-Mac-Pro:~ lucy$ diskutil ap convert disk3s3
Started APFS operation on disk3s3 High Sierra
Converting HFS Volume to an APFS Container which will export one APFS Volume
The target is the Journaled HFS+ volume "High Sierra" backed by the GPT partition disk3s3
Exiting conversion operations with error code -69546
Error: -69546: Conversion to APFS of a macOS system volume is only allowed in the OS Installer Environment

Any suggestions?

Share this post


Link to post
Share on other sites

All fine except sleep (first hack in signature).

0YM1ZkS.png

LuCys-Mac-Pro:~ lucy$ diskutil ap convert disk3s3
Started APFS operation on disk3s3 High Sierra
Converting HFS Volume to an APFS Container which will export one APFS Volume
The target is the Journaled HFS+ volume "High Sierra" backed by the GPT partition disk3s3
Exiting conversion operations with error code -69546
Error: -69546: Conversion to APFS of a macOS system volume is only allowed in the OS Installer Environment

Any suggestions?

Boot with macOS High Sierra installer and run the command in terminal 

Share this post


Link to post
Share on other sites

Boot with macOS High Sierra installer and run the command in terminal 

Thanks, but I can't do this because my drive isn't recognized in installer because of AppleAHCIPort, I explained it at post #64

Share this post


Link to post
Share on other sites

Thanks, but I can't do this because my drive isn't recognized in installer because of AppleAHCIPort, I explained it at post #64

Which of your hard disks is disk3s3? I assume that's the one that you are trying to convert to APFS. Right?

Share this post


Link to post
Share on other sites

Which of your hard disks is disk3s3? I assume that's the one that you are trying to convert to APFS. Right?

Yes, it's an WD 320GB with High Sierra installed.

Share this post


Link to post
Share on other sites

All good here, when returning from sleep USB devices are ejected is there any way/patch to fix it?

installing CUDA 9RC davinci resolve not recognize CUDA...strange

post-474300-0-75240100-1506433958_thumb.png

Share this post


Link to post
Share on other sites

Yes, it's an WD 320GB with High Sierra installed.

Sorry I'm confused, the installer doesn't recognize that HDD but in an installed version it's detected?

Share this post


Link to post
Share on other sites

Sorry I'm confused, the installer doesn't recognize that HDD but in an installed version it's detected?

I installed it on an recognized hdd and then restore the unrecognized hdd from high sierra installed with disk utility then replaced AppleAHCIPort and it's working.

Sorry, it's a little complicated, I hope you understand now :D

 

Sent from my HTC One M9 using Tapatalk

Share this post


Link to post
Share on other sites

I installed it on an recognized hdd and then restore the unrecognized hdd from high sierra installed with disk utility then replaced AppleAHCIPort and it's working.

Sorry, it's a little complicated, I hope you understand now :D

 

Sent from my HTC One M9 using Tapatalk

Ok, I see, in that case you might be able to boot from the recovery partition on your WD HDD and use the terminal in the recovery mode. But since you didn't install the macOS directly on that hard disk you might be missing the recovery partition.

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
×