Install OS with defective Firewire Port

Question

Level 1

4 points

Install OS with defective Firewire Port

Hi, the last days I tried to install the OS X "El Capitan" in my Mac Mini 4.1, but since the Firewire chip is defective, I can't get the installator to run.

I tried with the app store installer, and when it restart the mac, it hangs after the Airport configuration with this message:

com.apple.xpc.launchd[1] (org.ntp.sntp.117) Service exited with abnormal code: 255

In the Single User mode I erase the FirmwareIO kexts in the System/Library/Extensions and then it get stuck a couple of steps after the "com.apple.xpc.launchd[1]" with the message:

considerRebuildOfPrelinkedKernel com.apple.nke.webcontentfilter triggered rebuild

I left it for an hour and nothing happend.

The funny thing, is that with my Snow Leopard DVD it boots and I can install it without any problem and works like charm (except the Firewire of course), but with any other OS X newer than it, it is impossible (I've tried with Snow Lion, Maveriks and El Capitan, and all get stucked)

Anyone know a solution to install the El Capitan with the defective firewire port?

Thanks

Mac mini, Mac OS X (10.6.8)

Posted on Aug 31, 2016 2:27 PM

Reply

Answer 1

Aug 31, 2016 2:54 PM in response to Er_Garry

You could try creating an installer in a usb flash drive and see if it goes any further.

In any event, messing around with kexts in single user mode seems like a recipe for disaster.

Reply

Answer 2

Er_Garry Author

Level 1

4 points

Aug 31, 2016 3:00 PM in response to Luis Sequeira1

Hi, I've alredy tried it, and the result was the same, they even get stucked in the same points (if I erase the Kext in the USB)

In and old message I red that some people could get it installed in a Macbook Pro with the same problema as my Mini, but they don't explain the method they followed, so I couldn't get any information (but at least I know that it is possible).

Thanks for the reply 🙂

Reply

Answer 3

Sep 1, 2016 12:11 AM in response to Er_Garry

I wonder if it is just the installer that complains and if the system, once installed, would work.

You may try installing on an external drive, using another mac. Then try starting your Mini from the external and see how it goes. If all goes well, it will be a matter of cloning that external to your internal drive.

Reply

Answer 4

Er_Garry Author

Level 1

4 points

Sep 1, 2016 2:20 AM in response to Luis Sequeira1

The problem is that now, I don´t have other Mac to do that 😟

But I think that the system will work, because before the update try, it was working with Mavericks OS (but silly of me I didn´t create a Time Machine of that System).

I´ll search for another solution to get the installator running (because I´m sure it can be).

Thanks for the reply 🙂

Reply

Answer 5

Sep 1, 2016 3:06 AM in response to Er_Garry

Er_Garry wrote:

The problem is that now, I don´t have other Mac to do that 😟

Maybe you can borrow one from a friend for an hour so.

Reply

Answer 6

Er_Garry Author

Level 1

4 points

Sep 1, 2016 4:03 AM in response to Luis Sequeira1

Yes, if I don't find another solution it will be that.

But this morning I successfully installed Mavericks in my Mini, with a USB Installer with the Firewire Kext removed (created with the latest installer from the App Store), and it works perfect 🙂

Now I'll try to do the same with a new El Capitan installer (maybe the old one I was using was corrupt) but this time I'll create a Time Machine Backup of the System before.

Thanks for the reply 🙂

Reply

Answer 7

Er_Garry Author

Level 1

4 points

Sep 5, 2016 12:47 PM in response to Er_Garry

I manage to install Mavericks erasing the Kext of the USB installer, but when I do it with Yosemite or El Capitan, it allways get stuck rebuilding the kernel.

I've also get an external drive with a clean installation of El Capitan, when I tried to boot it, it get stuck in the same point as the installer, and if I erase the kext, it get stuck rebuilding the kernel again.

I know that some people manage to get it run in a Macbook Pro with the same failure as my Mini, so maybe I do something wrong? 😕

Thanks

Reply