Introduction
Upgrade your hard drive for more storage capacity!
-
-
Remove the following 10 screws securing the lower case to the MacBook Pro 13" Unibody:
-
Seven 3 mm Phillips screws.
-
Three 13.5 mm Phillips screws.
-
-
-
Use the flat end of a spudger to lift the battery connector up out of its socket on the logic board.
-
-
-
Remove two Phillips screws securing the hard drive bracket to the upper case.
-
-
-
Remove the two T6 Torx screws from each side of the hard drive (four screws total).
-
To reassemble your device, follow these instructions in reverse order.
To reassemble your device, follow these instructions in reverse order.
Cancel: I did not complete this guide.
486 other people completed this guide.
32 Comments
THANK YOU! I'm still on a high from repairing my husband's Macbook. It feels so nice to have two computers up and running again. You saved me nearly a grand, and made me realize how much I really did learn as a kid building PC towers with my dad.
I'm about to take this on. A little nervous as I haven't done anything like this before. When I get the new drive in, can I just restore from Time Machine? Do I actually need to reinstall the operating system first?
Replaced my HD a couple of days ago. I did disconnect the battery. No problems. Thanks iFixit!.
Installed osx (yosemite) on blank hard drive in 2010 macbook pro according to
http://www.youtube.com/watch?v=0K82njigC...
BUT instead of getting the spinning planet at first step, I got a padlock (apparently to keep non-apple employees from futzing around). However, the following got me past that point:
http://www.justanswer.com/mac-computers/...
and to be a little more descriptive than the link, with one memory stick out I held down r+p+option+command, hit power button until it restarted, and *continued* holding r+p+opt+command as it rebooted (screen on, off, fan&cd noises were the only indication) like 4 or 5 times.
THAT got me past the padlock but then there was another problem getting the new OS (non-descriptive error message "there was a problem..."). The solution there was to open terminal and change the date according to
https://bensmann.no/changing-system-date...
Finally it was smooth sailing after that.