Reboot fail after installing El Capitan help!!

Thank you.

I found my problem to be that my Mac was loading a kext file (Loaded: Yes) that, according to the listing was not suitable for loading (Loadable: No) and this was causing the problem.

So, as well as moving the kext files that were unsigned, I moved the ones like this that had loaded but were "not Loadable".

The easiest way to do all this is to boot from a USB drive (google how to do this), then run the command:

system_profiler SPExtensionsDataType > ~/Desktop/kextList.txt to create a tect file that you can look at on the desktop.

Now look in the resulting text file for anything suspicious, unsigned or loaded when it states clearly it is unloadable.

Then use terminal on the resulting working computer to fix the files by using

sudo mkdir Unwanted to create a directory to move the files into

Then using mv command to move the unwanted kext directories.

Good luck.

Phil

My apologies - I mean reinstall from thumb drive.",

Then get rid if offending .kext files before upgrading and rebooting.

Aldi a good idea to check disk integrity

Hope that helps

Phil

Sent from my iPhone

Supcumps wrote:

My apologies - I mean reinstall from thumb drive.",

Then get rid if offending .kext files before upgrading and rebooting.

Aldi a good idea to check disk integrity

Hope that helps

Phil

Sent from my iPhone

I had to restore from Time Machine backup, scan and remove the .kext files, and then the 10.11.1 update was successful.

THank you so much for your Help. I have installed el capitan more than five times. But today's update forced me to install again. On my secind trial of the update, I decided to read this post and give a smarter trial. it worked like a sweet dream.

Hi Carlos, Just saw your post coming by... Think you worry to much, 10.11.1 works good. No problem at all, seems faster than 10.11.

According to Apple, it has some bug fixes regarding the install.

If you did the Kext-things posted in these threads I'm sure you will be all OK.

Keep in mind that Apple cannot do much about what we did install -years ago?- on our systems.

If you did not do a clean install since the Mavericks-days you may or will have strange, old, not working, things that will cause ElCap booting to hang.

It will be hard to solve this problem for all different systems affected worldwide by the Cupertino guys.

Just check all suspicious, unsigned and old Kexts (Google them if in doubt) and get rid of them, unless you are sure you can trust them. Save the suspects in a different folder so you can put them back when needed for that one app that needs it...

Do not forget, if you MOVE them with Finder, (sometimes?) they will not be deleted from their original location so booting will hang again.

So: Please check the original folder if they are gone, if not make sure to put them in the trash.

I believe when 10.11.2 is seeded it will have the same problems, so do the Kext check/move/delete things, and update now.

No worries, cheers, Gerard.

Thanks Gerard. I did it via the command line as your original post directed. I also fixed my brother's MBP with it. Interestingly, I had two kexts from the same developer, but only one was signed. And it is still supported and they offered to help but I spent some time last time recovering and can't afford to experiment with my computer again (I would use MS Windows if I wanted to do that 😁). I'm not su sure is hard to fix for all the different systems when the fix made a simple query and moved a few files around. Actually, a few years ago the MacOS installer did exactly that with unsupported applications and system extensions (I think even one of the pre OS X versions did it).

But your point is well taken and I thank you again for providing the fix to this issue.

Good morning GSfromNL.

After I did the recovery and all is downloaded, the computer asks for my password and after giving it in, it starts installing. It says It will take approx 35 minutes. After twe hours it still says it will take 30 minutes. After I went for a walk the computer was switched off. So I had to start it again. I get the photo of El Capitan and the little ball turning and nothing happens.

I started it in safe mode and updated to 10.11.1. About 1.35 gig was downloaded and installed and then I get the photo of El Capitan and a turning ball. Nothing happens then.

If I look in the safe mode in the Apple Store I see that the El Capitan 10.11.1 was purchased. If I click at the Apple-symbol it mentions El Capitan 10.11.1.

What should I do now?

Fred

Thank you so much GSfromNL.

After reinstalling GP three times, this is the first time a reboot works for me, just after following your instructions. In my case I had the usual suspects

/System/Library/Extensions/EltimaAsync.kext

/System/Library/Extensions/JMicronATA.kext

Plus these printer and drawing tablet extension files:

/System/Library/Extensions/EPSONUSBPrintClass.kext

/System/Library/Extensions/Pen Tablet.kext

/System/Library/Extensions/hp_Inkjet1_io_enabler.kext

/System/Library/Extensions/hp_Inkjet_io_enabler.kext

/System/Library/Extensions/hp_fax_io.kext

Hope I can use the printers and tablet later with some new installation software. But that's a minor problem Thanks a lot!

Hello Fred, a rainy day here, so, some time to check things. It appears in your postings that you have these problems for weeks, and sometimes they where solved, correct? I do not think that your symptoms are kext related,

Starting your system (correct me if I'm wrong):

1. First a grey screen with Apple logo and completing the progress bar seems to work,

2. A fussy ElCap photo (meaning it did boot) If you did set a password you did have to give in this fussy screen,

3. A clear ElCap photo with the spinning beachball looks to me that an faulty app trying to start.

Things to check if there are suspected apps starting:

First: click the apple top left: -> System Preferences -> Users -> Login items and disable anything you do not need at startup.

Then check:

Users/yourname/Library/LaunchAgents

System/Library/LaunchAgents

System/Library/LaunchDaemons

System/Library/StartupItems

Library/StartupItems

for suspects and move them to a temporary folder.

Maybe this helps, but there can be many other reasons, including faulty hardware.

If you have a second 'working' Mac and a Firewire cable it is easy to find out. Try to start the not working Mac with the Harddisk in your 'working' Mac using Target (Firewire) mode:

1. Start your (working) mac holding down the T on your keyboard, a Firewire symbol will hoover over the screen.

2. Connect the Firewire cable to both computers.

3. Start your not working Mac holding down the Alt key, (brings up the bootmanager) select the Firewire disk and restart.

If the startup works good than your 'not working' Mac has no hardware issues.

You can reverse the procedure with starting the not working Mac in Target mode (startup holding the T) and try starting the 'working' Mac with the Hard disk in the 'not working Mac. If this fails, there is something definitely wrong with your ElCap system. Then, I think it is time to grab all your important files from the not working Mac and do a clean install.

You can use the same Target mode to move files: Have the Firewire cable connected, start your working mac normal and start the not working Mac holding the T.

The harddisk in the not working Mac will be visible on your working Mac and you can use it as any normal external disk to move files around.

Good luck, Gerard.

Thanks! This finally helped. I'm only sorry that I reinstalled the OSX 3 times in order to just boot the mac before finding your solution

The problem started to occur on MBP Retina early 2015 after upgrade to 10.11.1. DO NOT UPGRADE!

Dear Gerard,

At last I did a clean installation of El Capitan. Everything is working now. To re-install my virus-protection and Word/Excel/Powerpoint I need the cd's. And those are at home.

Thank you very much for your help.

Fred

Tsofa, I spent days trying to get this figured out and numerous calls to Apple Care including a trip to the Apple Store and nothing helped. As a last resort I tried your fix and it worked through multiple restarts and cold boots. I take my hat off to you, many thanks, I was at wits end. I would like to ask what does the text I pasted into Terminal actually doing. I know this is kind'a after the fact but I wouldn't mind knowing. Thank you again, Neil

I agree - if you aren't au fait in getting into terminal commands and deleting stuff then DONT INSTALL! Mine did all the same things - hanging progress bar, Safe mode not working etc. Had back up I did straight after install - that didn't work either! Have reverted back to Yosemite as the fight between my WiFi and bluetooth is easier to deal with.

Not impressed that Apple are choosing not to assist anyone with this!

Hi GSfromNL

I went trhought the steps found CUDA.kext and JMicronATA.kext in /System/Library/Extensions and I didn't find anything in /Library/Extensions.

Copied them and deleted the originals.

Unfortunately didn't work for me, my mac book pro still the same, do not want to restart, the only way is forcing the power button.

Any idea or suggestion?

Thanks.

Thank you so much for this, this was driving me crazy. Every time I restarted my iMac it was getting stuck at the gray screen with apple logo with the progress bar not moving and I had to do a restore. This fixed it. THANK YOU!!