- No Packages Were Eligible For Install Os X Catalina
- No Packages Were Eligible For Install Os X
- No Packages Were Eligible For Install Os X 10
Tags: Mac OS X
MacOS – Mac stuck in “El Capitan” installer loop: “no packages were eligible for install”. My problem is that my Mac starts up to the 'El Capitan' installer. After restarting several times, OS X is still on screen telling me that 'no packages were eligible for install'. Can someone help please, and can you bear in mind that I’m not. At that time, it’s a good idea to erase the disk and install a fresh copy of OS X for the next owner. Os X El Capitan No Packages Were Eligible For Install If you’re thinking about reinstalling because something has gone wrong with your Mac, know that an OS X reinstallation should be your last resort.
A key step for upgrading the disk on a MacBook Pro is to install a new operating system on the new drive, and then use Migration Assistant to copy over the old data. Depending on how you went about the work, installing Mac OS X on the new system may give you a message: OS X could not be installed on your computer. No packages were eligible for install.
This is what it looks like in the installer. Upon seeing this I went 'HUH?' because the installation was from a thumb drive I'd used many times to install Mac OS X (El Capitan) successfully.
The above image came from an attempt to install El Capitan. I just got the following message, macOS could not be installed on your computer, while trying to install macOS High Sierra.
In both cases there was the same cause. In the El Capitan case, as I say in the next paragraph, the hardware clock had reset to zero because it did not have a battery pack. In the High Sierra case, I had performed a hardware reset of the computer in an attempt to fix a bootup problem. I had found advice to disconnect the battery, the power supply, then hold down the power key for a few moments. In both cases the hardware clock had been reset to zero, and macOS refused to boot.
After some yahoogling (duckduckgoing) I came across a simple solution. This particular computer had been running with no battery, and therefore the hardware clock was reset to zero, and Mac OS X had a test against that condition.
We've discussed elsewhere the process to install Mac OS X onto a computer, and transfer information from an old drive. It's during that process when the above message appears. A couple steps prior is where you can take action to correct the problem.
At this step, click on Terminal ..
Como usar apowersoft screen recorder. Then change the operating system date.
When running this particular Terminal session, you are ROOT meaning you can change anything on the computer. Normally we type 'date' at the command line just to find out the current day/month/year/time. But, the date command can be used to change the time registered in the system clock.
As I said above, for this particular computer the system clock had been reset to zero because the battery pack had been changed. In fact, the computer had run without a battery for many months because the old battery had gone bad.
No Packages Were Eligible For Install Os X Catalina
As you see on the screen, the date had been January 1, 2001. I then changed the system date to the current time as of the writing of this posting.
To understand the second command, go to a terminal window and type 'man date'.
In the synopsis section you'll see this as an option for the 'date' command:
No Packages Were Eligible For Install Os X
That's a little obtuse, but further down the manpage is this key:
In other words, the date code for this purpose is month-day-hour-minutes-year .. hence, that's what I entered and it changed the system date to match.
Afterward I closed the Terminal window and was able to successfully install Mac OS X on the computer.