I have been trying to do this for days. The terminal command just results with "zhs: killed". Every. Single. Time.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
You can't use an M1 Mac to create bootable pre-BigSur macOS installers
- Thread starter segers909
- Start date
- Sort by reaction score
This sucks. So far, trying to follow Apple's instructions, you can't the InstallOS.pkg to create the install app, because of an unnecessary compatibility check (I'm trying to create a bootable installer for an older machine, no need to check - the Installer app it creates does that check anyways), got around that with Pacifist. Then tried making the bootable installer with the createinstallmedia command (no need to check for compatibility then, I'm making the media, not running the installer).
Some developers are just too clever by half.
This wouldn't be an issue if Apple would give a way to update the damn certificate stores - the "marketing" decision (I have no doubt that Marketing forced this situation) to forego security in the name of repeat sales is why I'm starting to hate Apple.
Some developers are just too clever by half.
This wouldn't be an issue if Apple would give a way to update the damn certificate stores - the "marketing" decision (I have no doubt that Marketing forced this situation) to forego security in the name of repeat sales is why I'm starting to hate Apple.
While this old topic has been bumped... same for me on Ventura 13.2.1 (tried my 2023 Mac mini M2 Pro, and 2017 Intel macbook 12-inch). Can't make Mojave USB bootable installers from them... luckily I have an ancient 2009 Mac Pro I could make them from (otherwise I would be screwed).
While, I'm instinctively worried about the inability to make bootable installers for OSes that are Intel-only on Apple Silicon Macs, it is March 2023 now and the oldest supported macOS release is not an Intel-only one. A bootable macOS Mojave drive seems like a handy thing to have in the event that one needs to spin up 32-bit Intel Mac apps. But that also requires an Intel Mac to install Mojave onto in the first place. Furthermore, Catalina is total crap (I'd take Big Sur over Catalina any day) and Macs that can even run Mojave are no older than four and a half years old. I'm not saying the flexibility isn't nice. But I can't remember the last time I thought to myself "Man, I wish I could make a USB drive out of a nearly five year old OS that is no longer getting any kind of security updates". Like, having a Mojave setup for those apps makes sense to a point. Past that point, an I'm not entirely sure when I'd need to create an Intel-Mac-only macOS release on an Apple Silicon Mac. Certainly not in an IT environment where you should always be on a supported macOS release.
I'm surprised that this won't work on an Intel Mac on Ventura. I thought that the mechanisms preventing being able to run the createinstallmedia command for those older OSes had more to do with signing features that are required for Apple Silicon Mac apps to execute that Apple simply had no need to put in those older installer apps.
I literally tried it 5+ times on the 2017 Intel MacBook running Ventura... would not complete using the normal terminal command I have used 50+ times before... Had to switch to the 2009 Mac pro to make the bootable Mojave installer.
I have 4 Intel Macs that are strong enough to create bootable installers (2009, 2010 iMacs, 2014, 2015 MacBook Pros) and I was considering selling several of these but it turns out that these old systems come in handy for various things. I am quite surprised that this doesn't work on the AS Macs.
That's pretty wild. Also seems needless, but I'll bet it's a security change that requires some sort of updated signature type that Apple just isn't issuing for the older releases. I believe that's similar to the elements that prevent you from being able to run the createinstallmedia command from Catalina and earlier installers on an Apple Silicon Mac.
I was already planning on hanging onto my MacBook Pro (Retina, 13-inch, Early 2015) for one-off just-in-case measures. Being able to make a Mojave drive is one of the things I might need (as I do have a couple of 2014-2015 MacBook Airs specifically to be able to mess with older Mac software). But outside of that, I don't really see a need to be able to make installers for older than Big Sur considering my consulting practice is generally geared toward IT and IT only wants OS versions that are still supported. Plus, with the exception of maybe one other Intel Mac (which will be kept current), everything in my personal arsenal is either Apple Silicon macOS or x64 Windows.
This has to do with a bug in Apple's ASR code. Hopefully they fix it soon! It's why none of the backup utils are currently able to make and restore a fully bootable backup of your system anymore on Apple Silicon machines. Apple forces them to use their ASR routine which as I previously stated has a bug in it which prevents the successful copy of the OS during the 3rd party util's backup process. Hence, these programs are now used to backup the user data volume and don't bother trying to copy the OS until Apple fixes this situation. The current workaround process for doing a clean restore is to erase the target (internal) disk, and then reload the OS to it from scratch. Then on reboot of the new OS one uses the Migration option to copy the user data volume back over to it from the backup your util made. You'll then have a fully bootable clean system restored.
Last edited:
I don’t quite understand why you’re so sure this is a bug rather than Apple’s desired functionality.Update2: Both the Ventura 13.3 release as well as the new Ventura public beta 13.4 still haven't fixed Apple's ASR bug that prevents utils like Carbon Copy Cloner, and SuperDuper from being able to make a fully bootable system disk backup.
Because it is documented by both Carbon Copy Cloner and SuperDuper authors.
From Mike Bombich's Blog:
When Apple introduced Apple Silicon Macs, we discovered another snag. The "Apple Fabric" storage in these Macs offers per-file encryption keys (like the storage in iOS devices), and for months, ASR didn't work with it. Apple partially resolved that in macOS 11.3, but even now using ASR to clone the system back to the internal storage of these Macs doesn't quite work – it causes a kernel panic.
Back in December I had a conference call with Apple about the reliability and functionality of ASR on macOS and regarding Apple Silicon Macs in particular. They indicated that they were working to resolve the ASR/Apple Fabric issue, but they made it very clear that copying macOS system files was not something that would be supportable in the future. Many of us in the Mac community could see that this was the direction Apple was moving, and now we finally have confirmation. Especially since the introduction of APFS, Apple has been moving towards a lockdown of macOS system files, sacrificing some convenience for increased security.
Last edited:
wow, this means that full clone of the SSD using apps like macrium or others is not gping to be possible on macs in a near future? we are not going to be able to create images of our computer disk? This is a bit strange, whole image backup is the best and fastest way to restore a computer.
I had to do a rollback on 13.3 this week and I wasn't able to create an external bootable SSD. I am going to try again as I want the ability to do this so that I can look at used systems. It will be a royal pain if this is no longer possible. I was also surprised that I could do a full restore from Time Machine to the system. Time Machine only had "Data" backups. It told me to install macOS and then use Migration Assistant to move the userspace and applications to the system. Is that how you have to do full restores now? This will definitely make things less flexible.
Indeed! It won't work no matter how many times you try because of the ASR bug. Both those backup utils advise to just use them to backup your data volume onto your external drive since neither can make a bootable backup at this point. Then one needs to reinstall the OS onto your internal drive, when completed boot it and then choose the Migration option to restore your data backup to the system drive. That is the only way presently to do a clean bootable restore to your internal system disk. Yes, exactly the same procedure TM advised you. This procedure is required for Apple Silicon machines. If you think this is bad wait until your internal system drive goes belly up and your Silicon Mac is rendered useless! It won't allow you to boot off of any other device if the internal system drive goes bad! At that point you'll have to get Apple to replace the motherboard (which the drive is part of now) or junk it and buy a new machine. Thanks Apple for that great decision!
Last edited:
Is this true for Intel Macs too? I have run Monterey on an external SSD on my 2015 MacBook Pro. Is this bug in Big Sur, Monterey and Ventura on Apple Silicon?
With Mac OS 13.3 coming out this week, I downloaded the revised Ventura installer and reformatted my two Ventura USB installer thumb drives at my workplace with the new version so we don't have that SMB network problem on any Macs we get that I install Ventura onto. Of course, I used my 2015 Retina 15" MacBook Pro for this process, running Ventura via OCLP 0.6.2.
I was able to create a Ventura 13.2.1 Flash installer this week so that still works - this was on my Mac Studio and I used it to install on my M1 Pro MacBook Pro.
AHHHHH this is so helpful!
Here's my situation:
I have a Macbook Air 2017 that I'm ready to sell, so I reformatted my disk and tried reinstalling macOS. It gave me reinstallation issues like, "An error occurred when reinstalling....." I've tried it multiple times for almost three days. Almost gave up lol
Until I saw from Apple forums that creating a bootable installer could help, and so I tried! I tried the terminal thing from this article: https://support.apple.com/en-us/HT201372, but I guess Terminal and I are not besties. Hence, it gave me "command not found errors"
I scanned through articles and tons of Youtube videos again and found another way - which was to use MDS to download the installer. Tried with Catalina but encountered an issue again. SOOOOOOO FRUSTRATED! UNTIL!!!! I saw the quoted comment. YAYYYY Big Sur indeed worked! Now I am soon handing out this Macbook Air 2017 to the buyer. Thanks a bunch!
Here's my situation:
I have a Macbook Air 2017 that I'm ready to sell, so I reformatted my disk and tried reinstalling macOS. It gave me reinstallation issues like, "An error occurred when reinstalling....." I've tried it multiple times for almost three days. Almost gave up lol
Until I saw from Apple forums that creating a bootable installer could help, and so I tried! I tried the terminal thing from this article: https://support.apple.com/en-us/HT201372, but I guess Terminal and I are not besties. Hence, it gave me "command not found errors"
I scanned through articles and tons of Youtube videos again and found another way - which was to use MDS to download the installer. Tried with Catalina but encountered an issue again. SOOOOOOO FRUSTRATED! UNTIL!!!! I saw the quoted comment. YAYYYY Big Sur indeed worked! Now I am soon handing out this Macbook Air 2017 to the buyer. Thanks a bunch!
Thank you!
After a week of searching this worked on my MacBook Pro 2017 that I needed to install High Sierra on.
This made it possible to create the boot-USB from a M1 MacBook Pro 14.
The High Sierra installer I got from the "High Sierra Patcher" where you can download the installer to a non-valid Mac.
I registered just to say a big thank you! Thanks to all of you that with your research and advices it tooks me only one day to figure out how to maka a High Sierra bootable USB for my Mac Mini 2012, while on a MacBook Pro M1.
My steps:
1. Download High Sierra with the help of MDS app
2. Right click on file and select "Show Package Content" and open the teminal there
3. Run the
terminal command
4. Run the specific terminal command in order to make the bootable USB (I used an 8GB USB flash)
5. The resurrection of my mac mini happened
My steps:
1. Download High Sierra with the help of MDS app
2. Right click on file and select "Show Package Content" and open the teminal there
3. Run the
Bash:
codesign -s - -f createinstallmedia4. Run the specific terminal command in order to make the bootable USB (I used an 8GB USB flash)
5. The resurrection of my mac mini happened
Yes you can using installinstallmacos.py
Post in thread 'Install OSX on machine with no OS'
https://forums.macrumors.com/threads/install-osx-on-machine-with-no-os.2399084/post-32398084
Post in thread 'Install OSX on machine with no OS'
https://forums.macrumors.com/threads/install-osx-on-machine-with-no-os.2399084/post-32398084
I ran this command:
cd /Applications/Install\ macOS \ Catalina.app (High Sierra in my case)
find . -type f -exec codesign -s - -f "{}" \;
After this command I managed to create a bootable USB (High Sierra) but when trying to install this on a 2010 MBpro it gave me errors when starting the installation.
My solution:
Deleted the installer, downloaded the installer again.
Rebooted into the recovery mode, opened terminal, disabled SIP (terminal command: csrutil disable )
And I am able to make all the installers I want, without any terminal commands to resign anything.. so solved. I know disabling the SIP is not a populair solution, but at least it's something.
cd /Applications/Install\ macOS \ Catalina.app (High Sierra in my case)
find . -type f -exec codesign -s - -f "{}" \;
After this command I managed to create a bootable USB (High Sierra) but when trying to install this on a 2010 MBpro it gave me errors when starting the installation.
My solution:
Deleted the installer, downloaded the installer again.
Rebooted into the recovery mode, opened terminal, disabled SIP (terminal command: csrutil disable )
And I am able to make all the installers I want, without any terminal commands to resign anything.. so solved. I know disabling the SIP is not a populair solution, but at least it's something.