If you have the High Sierra patcher you can install HS over it it should over write the patches just don't apply the post install patches
I moved my SSD from an unsupported to a supported Sierra Mac.
Is there a way to get rid of all the patcher files?
Did not find any infos about that on dos1dues's page
Hi, I had asked what I think is the same question after I migrated my SSD contents to a new machine.
(my question
With deep thanks to dosdude1 and others, I was able to keep my early-2008 MacBook Pro running through High Sierra. I decided that 10 years was enough, and jumped ship to a new MBP, migrating successfully using the Time Machine from the old unit.
All is well, except I occasionally get Patch Updater popping up to say that "New patch updates are available for this model. (Night Shift Patch)", which I clearly don't need anymore. How do I stop this? Is there a way to remove Night Shift Patch so it isn't checked? Or can I just uninstall/delete Patch Updater from Applications/Utilities? (it's only for the "unsupported Macs" feature, right?)
Thanks for any help you can offer!
(answer
Yep remove the Patch Updater app from Applications/ Utilities, and also remove the com.dosdude1.Patchupdater.plist from /Library/LaunchAgents. Restart your Mac and see if you keep getting prompted.
Here is a link to the answer (I hope this is helpful):
https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-486#post-27103953
This is likely, if this was after the 24th of October, simply because the macOS installer certificates have expired. You need to re-download the installer from Apple, via dosdude (which I beieve gets the newer version now) or with some other tool. See The Apple Packagepocalypse, 2019 Edition… (Medium)."No packages were eligible for instal" - with date correct!! [P.S. SOLVED]
I was trying to install High Sierra on a MP 3,1 (using DOSDude's latest HS Patcher and new HS download) and consistently obtained this odd error around 5% of the way into the install bar. I searched and only found the explanation for setting the correct date - usually because the system battery had failed or been removed and the date had defaulted to 'factory zero'. The date and time were correct in Terminal and could find no other information for this error anywhere on the web.
My hunch was it was still a date-related error so I put the date back by two years (yes October 2017) and the problem was solved.
I infer that the High Sierra installer has a built-in obsolescence. Anyway after installation, I set the date correctly and all is fine. I thought I would share my experience as I am sure I won't be the last to be initially stumped by this.
Odd. Installed in my Mac Pro 3.1 without any problem"No packages were eligible for instal" - with date correct!! [P.S. SOLVED]
I was trying to install High Sierra on a MP 3,1 (using DOSDude's latest HS Patcher and new HS download) and consistently obtained this odd error around 5% of the way into the install bar. I searched and only found the explanation for setting the correct date - usually because the system battery had failed or been removed and the date had defaulted to 'factory zero'. The date and time were correct in Terminal and could find no other information for this error anywhere on the web.
My hunch was it was still a date-related error so I put the date back by two years (yes October 2017) and the problem was solved.
I infer that the High Sierra installer has a built-in obsolescence. Anyway after installation, I set the date correctly and all is fine. I thought I would share my experience as I am sure I won't be the last to be initially stumped by this.
Downloading the new installer (yeah, for the old OS) is the right solution. What you're supporting is band aid for any later comment.This is quite normal and has been for many years even on supported macs. Setting back the clock is indeed the right solution.
Yeah, we were talking about this issue (certificates expiring) on this very page.I really don't know exactly how to search to see if this information is already here.
In order to proceed with the Dosdude Sierra patch on iMac, I had to go into Terminal after booting the installer and set the date to 2017. Before I did that, my install would abort with an error message along the lines of no eligible packages found.
Arrgh, the misadventures of a newbie. Normally, I'd say it doesn't hurt to have a repeat, but that's a bit hard to defend if it appears on the same page. Oy vey. Since 10.12 has worked, next step is to try 10.14 and if that works, then I will buy an SSD and install it internally. At the moment, my 10.12 is actually running over usb 2.0 from an external.Yeah, we were talking about this issue (certificates expiring) on this very page.
Slightly off topic, but do you happen to know if I have to buy a drive temperature sensor Sara interface cable if I replace the original Mac 3.5" drive with a 2.5" SSHD? ( I have a spare 500gb SSHD which I'm willing to try out to avoid buying a "real" drive. ) I read somewhere that the fans will come on unless they can detect the drive temperature.No problem, Bobcov1.
I find that on any OS after 10.6 an SSD is really necessary to have a smooth system these days...and that even on older systems it helps a lot.
I tried a regular external USB drive too, but it was the same. The drives do boot initially, then after a few seconds the Apple logo turns into the prohibitory sign. Do I need to use a specific version of 10.12?I'm no expert, but if the USB stick isn't even booting, I would try another stick or another USB port. If you have access to another Mac and it doesn't boot then I would remake the installer on a different flash drive.
They boot to the installer screen or they start to boot but never get to the installer screen? Dosdude's page says this error can indicate a non-eligible machine, but early 2008 is listed as okay. Are the USB devices USB 3 or USB 2 rated? I read USB 3 rated drives can cause a problem but I used one for one of my installs on 2009 iMac without a problem. Did you format the drive as GUID partition map and extended journaled before the patcher install? I don't know if that matters, but if you didn't, it can't hurt to try that. I'm swimming in the deep end here...I tried a regular external USB drive too, but it was the same. The drives do boot initially, then after a few seconds the Apple logo turns into the prohibitory sign. Do I need to use a specific version of 10.12?
Ok, I booted in verbose mode, got this:I’d try booting in verbose mode (command-v while booting) to see what hangs exactly.