- Making a bootable disk for mac does not appear to be a valid os installer application. install#
- Making a bootable disk for mac does not appear to be a valid os installer application. full#
- Making a bootable disk for mac does not appear to be a valid os installer application. trial#
- Making a bootable disk for mac does not appear to be a valid os installer application. download#
Below is what I ended up with after using the High Sierra App Store link. To be consistent, extract the MacOS installer app to the /Application directory.
Making a bootable disk for mac does not appear to be a valid os installer application. download#
In each of the above cases, you want to either download and extract the file (from the direct link) or download it from the App Store directly. Then, go to the macOS version you want to target on the unbootable. With OS booted in VMware, make sure you have a network card and it can connect to the Internet. With Vmware, you’ll also need the auto-unlocker to make sure OS X boots. This is by no means the only way to get OS X working in Vmware, but it is likely the quickest way. You can get the Operating System image from Google Drive and this article explains more. Essentially you’ll need to download an image of OS X (El Capitan in this case) and run it VMWare Player. If you’re any reasonable person, you’ve already wasted a day – if, of course, you haven’t thrown your Mac out the window.
Making a bootable disk for mac does not appear to be a valid os installer application. full#
So, you could now pull out the drive and do a full wipe or empty the current drive, but on some machines, that’s not even an option. Not so fast! Apple must have thought of this, so with this old date and installer, you won’t be able to see or access the Mac’s local drive. Go and re-run setup and voila, setup runs. Going to the Terminal from the setup screen and issuing something like “date 1116211618” (this sets the date to Nov 16, 2018. For High Sierra, it’s reasonable to target a date somewhere in 2018. So, while I’m using a 2017 installer on a machine in 2020, I’ll get that error saying the setup is “corrupted” – but it’s just the certificate.
Making a bootable disk for mac does not appear to be a valid os installer application. install#
Not so fast! The installer booted, but when you run the process, there’s an error “This copy of the Install application is damaged, and can’t be used to install macOS/OSX.” Well, so it goes, Apple doesn’t explain it, but what they’ve been doing is using certificates and these certificates expire. This seemed to be the best option so I downloaded it and used TransMac again.
Making a bootable disk for mac does not appear to be a valid os installer application. trial#
You’re told that you can just use DISKPART in Windows to set up GPT, but that wipes the drive and you’re back to square one!Īfter some trial and error, I found an image with the file name “macOS High Sierra 10.13.dmg” on mega.nz. Even worse, every time you try, it takes 30 minutes or more. 90% of my tries were not GPT, so they wouldn’t boot. The trouble with this is TransMac doesn’t make sure the partitioning is GPT (which is required), so you’re bound to the partition inside the installer DMG. The process involves first formatting the key for Mac and then dump an image of OS X to the key. With another key, I used the commonly described process with TransMac. During that process, the drive went read-only and never returned. First I needed to find something big enough. Then there’s the process of preparing a USB key on Windows. I would not expect this to work for you either, but, without the recovery partition, every boot-up ends up at this failing process. This process seems more like a hail Mary and no matter what kind of connection I provided (direct Ethernet, WiFI) it failed. I did that by holding down Command + Option + R which is great, the spinning globe started. Here’s a look at recovery options, what failed at every turn and what finally got me there.įirst, they say to boot into Internet Recovery. But, those steps also kill your recovery options too. I think this happens most often when we try to re-use a Mac and follow the steps (which include erasing the drive). The process of reinstalling OS X on a Mac when you have only Windows computers around (and no recovery partition) is very specific, yes, but it’s happened to me a few times. But, I can off you hope that it is possible and you can get your Mac running again. Every other step you’re going to take will lead you to failure. You could do this faster on another Mac (but I know you don’t have one of those). Or, more specifically OS X running in a virtual machine on a Windows computer. I’ll just cut to the chase: You need a Mac.
0 kommentar(er)
