- #Movie editor for mac os x 10.10.5 install#
- #Movie editor for mac os x 10.10.5 drivers#
- #Movie editor for mac os x 10.10.5 update#
#Movie editor for mac os x 10.10.5 update#
So, instead of clicking it, what worked for me was to fix permissions, download the combo update and run it, then inside the update restart the system. Once in Mac Os X Yosemite, the Photos icon was broken and the App Store showed the 10.10.5 update ready to restart. I did nothing at the command prompt (I could not delete any kexts nor run DiskUtility), so I just rebooted from there using command exit. but no one made me arrive to the login screen again except command -s. I tried all different boot commands like -x, -f and different combinations of npci=0x2000, GraphicsEnabler=No, dv_disable=1, etc. I created the MultiBeast USB drive and substituted everything in my USB Key and all the installation of Yosemite over Mavericks went fine, except for FaceTime and iMessage until I hit the App Store Update to 10.10.5 from 10.10.2 and all but headaches came to me since then. I already had Mavericks working fine (Windows 8.1 and Mac dual boot), including iMessage until 3 days ago I decided to update to Yosemite.
Thanks in advance for all your help on this.Īs soon as I got home, I tried several thing but none work with the Old SSD disk, it never boot again, so, I decided to move on and clone the 10.10.5 working installation (on my 300GB HD) back to my SSD.įirst attempt didn't work, I didn't change the 10.10.4 configuration on Mutibeast, so I changed it, unchecked the Trim Enable option and that was it, my SSD boot again now want 10.10.5 and everything is working as before. do I need to do something special to that installation before clone it to the SSD?
#Movie editor for mac os x 10.10.5 install#
If so, any way I can fix my current OS X on the SSD? I'm almost sure, clonning my successful install of 10.10.5 to the SSD might work, but.
#Movie editor for mac os x 10.10.5 drivers#
I'm sure is not drivers related ( I have a Radeon HD6850) as all work on the 300 GB Hard Drive.Īny Idea what could be the problem? well, I think it could be something related to 'TRIM", right?. The 1st installation (trial) worked flawlessly on an exact copy of my system disc (except is was on a 300GB Hard Drive), but when trying to install on the SSD it did't even complete the installation. I booted from my 300 GB HD, ran Multibeast 7.5 to the SSD (just in case) but it still doesn't boot, it dies on the screen with the little apple haldfway booting. Unfortunately it doesn't boot anymore to 10.10.4.
I was able to reboot again to 10.10.4 on my SSD, so tried again the update, and again black screen as soon as it tries to reboot to complete installation. So I decided to run the update for real on my system disk (this time to a SSD 240 GB), so I repair permisions, execute combo, and just when it re-boot (to complete the installation) my system died (black screen), and it was not because a power failure. Building a CustoMac Hackintosh: Buyer's GuideĪs a rule, I always clone my OS X to a different drive and try the install over there first, so that I did, I cloned my OS X 10.10.4 to an internal 300MB HD that I use as an alternate Boot or Sandbox to experiment, I followed all recomendations (repair permision, download 10.10.5 combo, execute combo, re-boot, Multibeast 7.5, re-boot, Success!!! all working fine.