crwdns2933423:0crwdne2933423:0

MacBook Booting From USB By Default, Keyboard Not Working

I apologize for the length of this post but I wanted to be thorough. I have a 2009 MacBook Pro that someone gave me because they spilled coffee on it. It ran, but the keyboard typed in like Webdings until I pressed the Fn key, then it kind of worked but the Delete, Command, and Option keys didn’t.

I bought a replacement keyboard and installed it, along with more RAM and an SSD, since I already had it open. I thought I could just boot from a USB device and install OSX on the SSD from there, but it didn’t work so I swapped the original HDD back in. The keyboard worked fine the first try and booted into recovery the first time I tried, but when OSX booted up the keyboard stopped working correctly. Caps Lock is on permanently now, and the delete key still doesn’t work. I don’t think Command and Option keys do, either, so I can’t change my startup disks after a restart.

That’s to preface this by saying I can’t rely on the keyboard to boot into Startup Manager or Recovery Mode. I plugged in a USB keyboard to use with the HDD, and attached an SSD via USB as well. I installed El Capitan onto the SSD then swapped the drives out, but I got the “prohibitory” symbol. When I plug the SSD back in via USB, WITHOUT a disk attached to the Mac SATA cable, it boots into El Capitan from the SSD. If I reconnect the original HDD to the Mac SATA cable and change the startup disk in OSX to boot from the original HDD, that works.

Why can’t I just connect the SSD to the Mac SATA cable and boot from there? And how do I fix the dadgum keyboard? If the options key doesn’t work I’m not sure what to do next.

Thanks!

Edit 1: Here is a picture of the error I was getting while trying to install the OS on my SSD, via USB:

Block Image

crwdns2934089:0crwdne2934089:0 crwdns2934093:0crwdne2934093:0

crwdns2934109:0crwdne2934109:0

crwdns2889612:0crwdne2889612:0 0
crwdns2942205:01crwdne2942205:0

Replace your SATA cable with a new one and see if that helps

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

crwdns2933313:01crwdne2933313:0

crwdns2934057:0crwdne2934057:0

You have some conflicting diagnostic processes here.

I’m suspecting the SSD’s format was not setup correctly. You need to format a raw drive with GUID either with HFS+ (Journaled file system) or APFS (if you are using High Sierra or newer). So with an older model you like this one we can mess up without realizing using a newer Mac to prep the drive! Here we need to use HFS+ as the system has no means to support APFS.

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 1

crwdns2944067:03crwdne2944067:0:

Thanks for the response. I used my WIndows 10 computer to format the drive as GPT, then tried installing El Capitan onto it. I kept getting an error until I manually rebooted the Mac but then the installation completed. I'll post an image of the error in a sec.

I'll reformat the SSD using the old OS on the original HDD and try again.

Do you have any advice on the keyboard? Does it sound like a software issue?

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

The drive was already set up as a Journaled file system. So the SSD is booting via USB but not via the internal SATA cable.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

Who's SSD and model did get?

The CPU crash is telling you have more damage on the logic board from the liquid spill.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

crwdns2934229:0crwdne2934229:0

Zebediah Jenkins crwdns2934231:0crwdne2934231:0
crwdns2936625:0crwdne2936625:0:

crwdns2936751:024crwdne2936751:0 1

crwdns2936753:07crwdne2936753:0 6

crwdns2936753:030crwdne2936753:0 11

crwdns2942667:0crwdne2942667:0 542