Joe Winke

Q: El Capitan won't Boot after update

I installed  El Capitan and it was booting fine. Then I installed the latest update and after the restart, the Mac loads the Apple logo and then screen goes white and it just freezes there. I tried restarting holding shift to log into safe mode and it remains white. I've even held down command and R to get the recovery mode to load.  I see are the boot options but when I select one, I just goes into a white screen.

iMac 24", Mac OS X (10.6.2)

Posted on Oct 4, 2015 11:30 AM

Close

Q: El Capitan won't Boot after update

  • All replies
  • Helpful answers

first Previous Page 15 of 17 last Next
  • by Patsymouse,

    Patsymouse Patsymouse Nov 28, 2015 2:11 AM in response to Wismann
    Level 1 (0 points)
    Nov 28, 2015 2:11 AM in response to Wismann

    I Have same problem now having read your post will reinstall again and not turn off this time. Thanks

  • by hygom163,

    hygom163 hygom163 Nov 28, 2015 4:55 AM in response to Patsymouse
    Level 1 (0 points)
    Nov 28, 2015 4:55 AM in response to Patsymouse

    i had same situation as you - after many trial and error i ended up with my mid-2010 iMac working with 10.11.1

     

    i made a clean install - Lion - upgraded directly to 10.11.1 - apple store "purchased selection" and had i installed from there.

     

    i did not re-install applications using "time machine" back-up, i did not work out properly, i tried migrating from another Mac and had fatal results. again had to do the clean install 3 times before "grasping it"

     

    on my other machines i have found some of the files mentioned elsewhere in this tread and removed them - cannot understand Apple has removed the "in compatible software" function if they did hide it i cannot know.

  • by Doctor Ebok,

    Doctor Ebok Doctor Ebok Nov 28, 2015 10:31 PM in response to PeterPan100
    Level 1 (0 points)
    Nov 28, 2015 10:31 PM in response to PeterPan100

    Hi,

     

    Did you find a fix since your last post? I am having the same issue, have to enter the command line again and again to boot up!

     

    Thanks

  • by Doctor Ebok,

    Doctor Ebok Doctor Ebok Nov 29, 2015 1:18 AM in response to Neue Horizonte Film
    Level 1 (0 points)
    Nov 29, 2015 1:18 AM in response to Neue Horizonte Film

    Hey, FIXED!

     

    Thanks for sharing this. I used this uninstaller to cleanly remove Syncmate from Eltima, which I never installed or used... and it fixed my issue!

    After running the command line "touch" with CMD-R and the terminal, it would still have the same issue after the following reboot, and again and again...

    So, try and install this .pkg which will remove the software:

    http://wiki.eltima.com/knowledge-base/syncmate/uninstall-syncmate.html

  • by Doctor Ebok,

    Doctor Ebok Doctor Ebok Nov 29, 2015 1:18 AM in response to Patsymouse
    Level 1 (0 points)
    Nov 29, 2015 1:18 AM in response to Patsymouse

    Hey, FIXED!

     

    Thanks for sharing this. I used this uninstaller to cleanly remove Syncmate from Eltima, which I never installed or used... and it fixed my issue!

    After running the command line "touch" with CMD-R and the terminal, it would still have the same issue after the following reboot, and again and again...

    So, try and install this .pkg which will remove the software:

    http://wiki.eltima.com/knowledge-base/syncmate/uninstall-syncmate.html

  • by Ferryman,

    Ferryman Ferryman Nov 29, 2015 12:36 PM in response to Joe Winke
    Level 1 (0 points)
    Nov 29, 2015 12:36 PM in response to Joe Winke

    I had this problem on my late 2014 Mac Mini. The solution of getting rid of that obscure eltima.kext file (???) was absolutely right. However the sudo command would not work for me from Terminal in recovery mode. But now Eltima have fessed up and given a better series of commands:

     

    http://blog.eltima.com/2015/10/critical-issues-with-syncmate-4-on-el-capitan-os- x-10-11.html

     

    When I restarted the first time after this, it still didn't work. But restarting via the startup disk, which can be accessed by clicking on the Apple on the top left corner of the screen in recovery mode, did.

  • by jabish1,

    jabish1 jabish1 Dec 10, 2015 11:57 AM in response to Joe Winke
    Level 1 (0 points)
    Windows Software
    Dec 10, 2015 11:57 AM in response to Joe Winke

    This crap is worse than "Winders" ever was!  My system will not even get past the apple logo before it reboots over and over again!  Apple should pay me for all of the $200.00 per hour billable that I'm losing!... Too bad I have to respond to this thread via a "Winders" Machine, but at least updates from Microsuck don't render my machines completely inaccessible!

  • by jabish1,

    jabish1 jabish1 Dec 10, 2015 1:22 PM in response to no time flat
    Level 1 (0 points)
    Windows Software
    Dec 10, 2015 1:22 PM in response to no time flat

    I agree with you on this one.  Currently restoring back one release.  For all of the money I have spent with Apple, I expect them to be BETTER than Microsoft... not 100 percent worse!!  Responding via "Winders 7", which boots just fine after its updates!

  • by doublehardkent,

    doublehardkent doublehardkent Dec 11, 2015 8:29 AM in response to mgahinga
    Level 1 (0 points)
    Dec 11, 2015 8:29 AM in response to mgahinga

    So, I spent an absolute fortune on the iMac 5k, had to do an update to El Capitan and the same thing happened - was halfway through an update when I had just a blank screen with a mouse cursor. Tried a restart, same thing, tried again, same thing again. Thought I'd try the above suggestion of connecting my MacBook Air to it and it did indeed have further updates to install... Didn't take long once I had managed to get into it. Somewhat peeved that in order to update a £2.5k Mac I have to use a different £1k Mac - seems like an expensive fix for those that don't have an alternative?! Shoddy workmanship really on the part of Apple. Clearly released an update without proper testing.

  • by PanAcorn,

    PanAcorn PanAcorn Dec 16, 2015 6:11 AM in response to JFPP
    Level 1 (0 points)
    Dec 16, 2015 6:11 AM in response to JFPP

    Thank you, RusFox!!! This https://discussions.apple.com/message/29059688#29059688 helped me on MBP 13 mid 2012, upgraded to SSD and 16G

  • by marc_rod,

    marc_rod marc_rod Dec 16, 2015 7:49 AM in response to PanAcorn
    Level 1 (0 points)
    Dec 16, 2015 7:49 AM in response to PanAcorn

    Hello guys,

     

    I'm new here. So I installed El Capitan without issue on my Macbook Pro 2014 Retina but it wouldn't boot on my dad's Macbook Pro 2013 Retina, after trying everything mentioned (terminal trick, NVRAM and reinstall of OSX), today I simply restarted the computer holding the option (alt key) and selected the Drive (Macintosh HD) in my case and the computer started perfectly. Not really sure why it worked al of a sudden, but for those of you who tried everything and are still stuck it can't hurt !

     

    Hope it helps !

     

    Cheers

  • by chrisfromham,

    chrisfromham chrisfromham Dec 16, 2015 8:26 AM in response to marc_rod
    Level 1 (0 points)
    Dec 16, 2015 8:26 AM in response to marc_rod

    APologies....it is rendered unreadable by this mini  - always starts with two   case letters, won't respond in the text box when it try to correct.

    so, I  recovered my mbpro to Yosemite - lost a day or so, small fry as it isn't work.

    best of good luck to you

    and happy thanksgiving - if you're in the USA

    poetry is good

  • by chrisfromham,

    chrisfromham chrisfromham Dec 16, 2015 8:29 AM in response to marc_rod
    Level 1 (0 points)
    Dec 16, 2015 8:29 AM in response to marc_rod

    Does this mean that the issues with El Capitan have been resolved?

    I would like to have my operating system up to date, but after the first drama I don't think my nerves would stand that whole process of wiping my MBP hard drive again and holding my breath...and quite a few hours while I hope the back up works...it did.

  • by smurcia22,

    smurcia22 smurcia22 Dec 26, 2015 4:06 PM in response to Joe Winke
    Level 1 (0 points)
    Dec 26, 2015 4:06 PM in response to Joe Winke

    I tried many of the options I have seen throughout this forum and though I am grateful for everyone trying to help us out here, none of them worked for me except 1. Someone had mentioned they had gotten help from someone Named Max 108. I contacted him and he explained this issue isn't a one for all fix and he spent the time walking me through the steps to not only get all of my files which were irreplaceable to me but how to go on from there since I couldn't boot after my initial install of El Capitan. He made sure I had a clear understanding before we were done working together. I highly recommend that if any of the above fixes hadn't worked for you that you contact him. He is active in the developer forums and has given me a link which I asked for to connect others to him if they are in my similar situation. You can use this to contact him.

    You could link to one of my posts in the developer’s forums - e.g. this one:

    El Capitan gets stuck on loading bar after updating

  • by VoxSephora,

    VoxSephora VoxSephora Dec 27, 2015 6:58 PM in response to marc_rod
    Level 1 (0 points)
    Dec 27, 2015 6:58 PM in response to marc_rod

    Hi,

    Ever since I installed El Capitan, my computer would not boot.  The only way I could get it to operate was to boot in recovery mode (Cmd + R) and reinstall the operating system.  This was getting pretty annoying because that process takes about an hour or so.  I was about to take my computer into the Genius Bar but I thought I would take another shot at fixing it myself.

     

    I tried the method with the terminal commands:

     

    Email this code to yourself, but change the machine name to YOUR EXACT(!) HardDisk-name.

     

    • cd "/Volumes/Macintosh HD/Library/Extensions/" ; mkdir Unsupported ; mv Net* Unsupported ; mv Sym* Unsupported ; mv hp* Unsupported ; mv ndc* Unsupported ; cd "/Volumes/Macintosh HD/System/Library/Extensions/" ; mkdir Unsupported ; mv Belc* Unsupported ; mv Eltima* Unsupported ; mv hp* Unsupported ; mv Hua* Unsupported ; mv Netg* Unsupported ; mv Remo* Unsupported ; mv RIM* Unsupported ; mv USBEx* Unsupported ; rm -Rf /Volumes/MacintoshHD/Library/Filesystems/*fuse* ; rm -Rf /Volumes/Macintosh\ HD/Library/Application\ Support/Sym* ; rm -Rf /Volumes/Macintosh\ HD/var/folders/

    Boot in Restore mode.

    Click OS help and Safari will open

    Open your email and copy the code

    Quit Safari and open Terminal from the top menu

    Paste the code and hit return.

    Give it a minute or two. When it is done you will then be able to quit Terminal.

     

     

    This command attempted to rename several files, but on my system, they were not found.

     

    I then used your method of just selecting the MacIntosh HD to boot from and that worked like a charm!  I can now reboot normally without a problem.

    Thanks,

    Vox

first Previous Page 15 of 17 last Next