Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Mac Mini Late 2009 (3,1) - Samsung SSD, APFS
Running Mojave 10.14

After creating a New Patch Tool, v1.2.3, from earlier this evening,
I began Update from within System Preferences/Software Update
After normal download and installation, Mac mini was caught in a boot-up loop, where it never fully finished the boot-up to login screen.

While Mac mini was still going through boot-up loop, I attached the newly created Patch Tool, v1.2.3,
and held down option key, where I was then able to select Patch Tool and apply post-Install patches

Which immediately, Successfully upgraded to Mojave 10.14.1
Thank You @dosdude1

View attachment 799767

Same here, after apply post-Install patches, and reboot, except i'm stuck on the end off the progress bar since 30 minutes. No desktop.

Now trying clean Install.

iMac 10.1
Samsung SSD
 
Last edited:
  • Like
Reactions: TimothyR734
What I am experiencing is iconserviceagent is taking up about 40% of CPU, so have these Terminal commands from earlier an OS, to rebuild cache, which may be corrupt;

$ sudo find /private/var/folders/ \-name com.apple.dock.iconcache -exec rm {} \;

$ sudo find /private/var/folders/ \-name com.apple.iconservices -exec rm -rf {} \;

$ sudo rm -rf /Library/Caches/com.apple.iconservices.store


restart

Anyone had this experience before on Mojave?


I have massive problem with iconserviceagent, it will eat up all my 32GB RAM and i9 processor until the macbook reboot by it self. All I did was just open finder, then go to Application folder or go to External drive. Every time!! This is not isolated incident
 
  • Like
Reactions: TimothyR734
Can I just upgrade my system from 10.14 and apply post install patches or do I have to make a fresh install?
[doublepost=1540979306][/doublepost]
The patcher has been updated to v1.2.3, which fixes that issue.


Can I just upgrade my system from 10.14 and apply post install patches or do I have to make a fresh install?
 
  • Like
Reactions: TimothyR734
I can confirm exactly the same situation with my Mac Pro 3.1 here. "29 minutes" for the last 60 minutes ...

Oh, edit: There's a little progress in the bar now, but still "29 minutes".

Update: The very long lasting complete install of 10.14.1 and the post install procedure (without the APFS patch, because I already patched the ROM for 10.14.0 before) is done now, but the boot disk shows a stop sign on startup. I'm going back to 10.14.0 now.
 
  • Like
Reactions: TimothyR734
I have posted instructions on how to verify sha1 code.
It is very simple!
[doublepost=1540988763][/doublepost]
Update: The very long lasting complete install of 10.14.1 and the post install procedure (without the APFS patch, because I already patched the ROM for 10.14.0 before) is done now, but the boot disk shows a stop sign on startup. I'm going back to 10.14.0 now.
The stop sign is what you get if you don't execute the patch when you boot from the usb drive.
Try execute it with all the settings and with force cache on and tell us if you succeeded.
 
  • Like
Reactions: TimothyR734
I saw all the posts but I wanted to try the installation for myself, so I do the following in a macbook 5.2

- I updated mojave by the options in system preferences, as it was a supported system. In High Sierra i allways make the updates like this. In High Sierra I allways update, reboot, and in the first boot i reinstall all the patches.
- The update ends, but in the first reboot the system doesn't boot. I have an apfs filesystem in this computer (I have installed an SSD).
- I prepared previously a pen drive with the patch (As I say, i readed all your comments, so i was prepared for this). So i start the pen drive and only reinstall the patches. The system still can't boot.
- I reboot again the pen drive and make the installation of the system. At first boot, i Boot the pen drive again and install the patches.
- Now the system works fine. I reinstall all the patches at first boot (to enable night shift and other things). And now the system works well.
 
  • Like
Reactions: TimothyR734
Thanks.
I'll wait for Hybrid patch update for install this.
Recovery partition can be fixed the same as in the previous version?

Yes, since 10.14.1 introduced a new kernel, the APFS Recovery will contain a new kernel, then you have to re-replace the new prelinkedkernel generated, so for you (and for those who have one only APFS scheme) just redo these steps: APFS Recovery fix part1

While for others with hybrid HFS/APFS redo both part1 and part2: APFS Recovery fix part2
 
  • Like
Reactions: TimothyR734
The stop sign is what you get if you don't execute the patch when you boot from the usb drive.
Try execute it with all the settings and with force cache on and tell us if you succeeded.

Thanks. Maybe in the next days, because I already spent a lot of time and because I need this machine working ...
 
  • Like
Reactions: TimothyR734
Since 14.1 my Mac Pro 3.1 does not boot from Mojave until I use the boot picker (alt-key on cold start)

Just a freezing white screen, no stop sign. EFI GPU is in.

-no_compat_check and -v is set as boot-args

Zapping pram wont help, setting startup disk via control panal neither.

I am not exactly sure if that happened before as I almost always chose the boot picker.
 
  • Like
Reactions: TimothyR734
Download dosdude1's patcher 1.2.3
Create a new USB bootable drive with the 10.14.1 version that 1.2.3 patcher can download
Install from your USB drive
After 1 restart, go back to the USB drive to patch the installation drive
Restart normally
Working 100% here

Lucky you are :)
Not here iMac 10,1 samsung SSD
I had to do a clean installation (erase SSD) and then transfer from a clone the user with the migration assistant

But even with that i get stuck on a blank screen with a loop restart/blank screen/restart/blank screen ...:mad:

any idea ?
 
Last edited:
  • Like
Reactions: TimothyR734
Yes, since 10.14.1 introduced a new kernel, the APFS Recovery will contain a new kernel, then you have to re-replace the new prelinkedkernel generated, so for you (and for those who have one only APFS scheme) just redo these steps: APFS Recovery fix part1

While for others with hybrid HFS/APFS redo both part1 and part2: APFS Recovery fix part2
Then is the same that with 10.14 with my Macbook 6,1. Thanks, now I only wait for Hybrid patch update for install the new Mojave 10.14.1
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.