Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Problem creating USB Bootable installer

B

bramhall

macrumors newbie
Original poster
Nov 25, 2014
22
2
Hi,

I would be very grateful if someone could advise me.

I am using a Mac Mini 2012 that has had a clean install of macOS Sierra and I was using this guide to make a bootable Mojave installer :-

https://support.apple.com/en-us/HT201372

My problem is that when I copy and pasted the 'createinstallmedia' command in terminal it seemed to run and work OK but I noticed the * next to the Mojave heading, the note said:-

* If your Mac is using macOS Sierra or earlier, include the --applicationpath argument. The Sierra and El Capitan commands show the proper format of this argument.

Presumable the installer will not work correctly as I did not do this.

Can anyone tell me if I should include the --applicationpath argument as suggested or whether the installer I made would work without?

I did find this Youtube guide for High Sierra and was wondering if I should use this method instead to create an installer? :-


Many thanks for any replies. :)
 
Try the free apps:
- Diskmaker X
- Install Disk Creator

Very easy to use, no foolin' around with terminal...
 
  • Like
Reactions: MSastre
Thanks Fishrrman I will look at using those.

I suppose I could also use "macOS Recovery" as an alternative to USB installer. It's only one install on a Mac Mini 2012 Samsung 860 Evo upgrade.

I'll try to find out the Pros and Cons of each method.
 
Erehy Dobon said:
Presumably, Apple actually knows what they are talking about given than it's their operating system. If they explicitly give certain instructions on an official support document posted on their website, I assume they have a justifiable reason to include such directives.

I have been using the command line to make bootable USB installers ever since they were first supported, years and years ago. I always use a bootable USB installer when upgrading between major versions. In fact, I usually keep a few generations of USB installers on SD cards.

FOLLOW THEIR INSTRUCTIONS.

Of course, you could use the utilities that have been recommended above but they are simply GUIs wrapped around the same command line operation. Because they have been around for years, perhaps they are safe, but one doesn't know if they could be injecting malware into your computer.

For sure, Apple does not mention them in the support document which implies that they are not an officially sanctioned method of creating a USB bootable installer.

Anyhow, your call.

Best of luck.
Click to expand...

Thanks for the info Erehy Dobon. In case I get command syntax wrong adding the --applicationpath argument I might chicken out and use "macOS Recovery" as it is only one install on a Samsung 860 Evo upgrade.
 
These instructions are straight from support.apple.com

macOS Mojave
sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled

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

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

OS X El Capitan
sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app

OS X Yosemite
sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ OS\ X\ Yosemite.app

OS X Mavericks
sudo /Applications/Install\ OS\ X\ Mavericks.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ OS\ X\ Mavericks.app
 
RyanXM said:
These instructions are straight from support.apple.com

macOS Mojave
sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled

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

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

OS X El Capitan
sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app

OS X Yosemite
sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ OS\ X\ Yosemite.app

OS X Mavericks
sudo /Applications/Install\ OS\ X\ Mavericks.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ OS\ X\ Mavericks.app
Click to expand...

Thanks RyanXM but the problem is the * above the Mojave example and it's instruction: "* If your Mac is using macOS Sierra or earlier, include the --applicationpath argument. The Sierra and El Capitan commands show the proper format of this argument."

The problem I have is if you follow the apple support instructions including the --applicationpath argument as I am running Sierra, when I use Terminal I get the following warning:-

"WARNING: "--applicationpath" is deprecated in macOS 10.14 and greater. Please remove it from your invocation."

So I cancelled out of Terminal.

It seems to create the installer OK if I ignore their apple support instruction and do not include the --applicationpath argument, but I would not be confident as I would not have followed their exact instruction.

Can anyone tell me if using macOS Recovery Option-⌘-R (Upgrade to the latest macOS that is compatible with your Mac.) is a reliable method of installing Mojave on a new Samsung Evo 860 if I have a good internet (& ethernet) connection?

If not I might get a UASP supported, USB 3.0 external Hard Drive Case and install Mojave whilst in that.

Many thanks for any replies. :)
 
  • Like
Reactions: RyanXM
OP:

Have you tried either or both of the apps I pointed you towards in reply 2 above?
 
  • Like
Reactions: RyanXM
Fishrrman said:
Try the free apps:
- Diskmaker X
- Install Disk Creator

Very easy to use, no foolin' around with terminal...
Click to expand...

Definitely agree with Fishrrman. All my USB installers, going back through Mavericks, have been made with one or the other of those two apps. They work a treat and are way easier to use than messing around with terminal.
 
  • Like
Reactions: RyanXM
Fishrrman said:
OP:

Have you tried either or both of the apps I pointed you towards in reply 2 above?
Click to expand...

Hi Fishrrman, because the apple support instruction does not work if you follow it specifically, for Mojave from Sierra, ..I am now a bit worried about using the third-party apps.

I am sure they are OK/used by many but, you can always find the odd bad review about apps, as I did for these, and if the apple support doc is misleading I have lost a bit of confidence.

Hence, wondering if I can just use Recovery on a new SSD. It's only the one install, not multiple Macs.
 
MSastre said:
Definitely agree with Fishrrman. All my USB installers, going back through Mavericks, have been made with one or the other of those two apps. They work a treat and are way easier to use than messing around with terminal.
Click to expand...

Hi MSastre , I am sure you are both right. I am just a bit concerned that the apple support instruction, if followed to the letter, gives the error in Terminal I mentioned and I have found various guides with conflicting info on the exact terminal command to use. Might the apps be problematic if used for Mojave installer, from Sierra.

Might get a external case for the SSD and try a clean install with an installer created by one of the apps suggested.
I could then revert to the HDD with Sierra if any problems.

Thanks for the replies. :)
 
  • Like
Reactions: RyanXM
bramhall said:
Thanks RyanXM but the problem is the * above the Mojave example and it's instruction: "* If your Mac is using macOS Sierra or earlier, include the --applicationpath argument. The Sierra and El Capitan commands show the proper format of this argument."

The problem I have is if you follow the apple support instructions including the --applicationpath argument as I am running Sierra, when I use Terminal I get the following warning:-

"WARNING: "--applicationpath" is deprecated in macOS 10.14 and greater. Please remove it from your invocation."

So I cancelled out of Terminal.

It seems to create the installer OK if I ignore their apple support instruction and do not include the --applicationpath argument, but I would not be confident as I would not have followed their exact instruction.

Can anyone tell me if using macOS Recovery Option-⌘-R (Upgrade to the latest macOS that is compatible with your Mac.) is a reliable method of installing Mojave on a new Samsung Evo 860 if I have a good internet (& ethernet) connection?

If not I might get a UASP supported, USB 3.0 external Hard Drive Case and install Mojave whilst in that.

Many thanks for any replies. :)
Click to expand...

Try Install Disk Creator.

https://macdaddy.io/install-disk-creator/
 
  • Like
Reactions: MSastre
OP:

You have the option of continuing to flop around like a fish out of water with terminal
or
Use the 3rd party apps I suggested above and have a working, bootable drive.

Your choice.
 
  • Like
Reactions: MSastre and RyanXM
Fishrrman said:
OP:

You have the option of continuing to flop around like a fish out of water with terminal
or
Use the 3rd party apps I suggested above and have a working, bootable drive.

Your choice.
Click to expand...

I'll try Diskmaker X. It will be nice to have a bootable installer for Mojave.

Shouldn't worry as I still have the working Sierra installer and could try macOS Recovery also, in the unlikely event that the Mojave one did not work!

Now just have to find out whether its recommended to enable TRIM (sudo trimforce enable) with the Samsung 860 Evo's?

Thanks for all the replies.
 
bramhall said:
Now just have to find out whether its recommended to enable TRIM (sudo trimforce enable) with the Samsung 860 Evo's?
Click to expand...

It doesn't set it up automatically. So yes you need to first verify via the Terminal if TRIM is enabled. Use this command and copy it in the Terminal. It will tell you if it is enabled:

system_profiler SPSerialATADataType | grep 'TRIM'
 
Last edited:
  • Like
Reactions: RyanXM
Hey guys,

Sorry to jump into this thread but hoping someone can assist with me creating a bootable USB.

I have installed `Install Disk Creator` and have attempted the process but was shown this message..

It is lacking the file "Contents/SharedSupport/InstallESD.dmg"

This is with the macOS High Sierra install.

Im not mega technical but any help and pointers would be greatly recieved.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back