Macbook Pro Efi Lock

MacBook Pro with Retina display, OS X El Capitan (10.11.5), EFI/Firmware lock. Posted on May 23, 2016 1:46 AM. Reply I have this question. Oct 19, 2009 COMMAND+ALT+P+R actually DOES work on intel-based, EFI machines. My Unibody MacBook Pro, 27″ iMac, Unibody Mac Mini, and MacBook Air, ALL USE this boot command. It resets PRAM–also known as PARAMETER RAM SETTINGS.

1. Macbook Pro Efi Password Removal
2. Macbook Pro Efi Lock Kit
3. Macbook Pro Efi Firmware
4. Macbook Pro Efi Lock Removal Tool

The Mission

There has been much controversy on removing the firmware lock on a MBP, MBA, or similar Mac's. The MBA is a bit more complicated without a specialty tool to interface with a header on the board. We use to have to remove the board, scratch back traces, and solder directly to them which can be seen in EX-1.1. This is just short of replacing the entire chip, which is what we are all trying to avoid right? I also have a project I have been forking on called the iFLRT (Firmware Lock Removal Tool) that can be found HERE. Donate what you can to keep my development process alive, every little red cent helps.

First you need to understand what the firmware lock is and how removing it will affect you. Then maybe you will be able to decide if this procedure is for you. In most cases a MBP has been purchased from a third party who may have stolen it or simply forgotten to remove their iCloud account. In this case the symptoms would be a four digit pin lock when the OS loads. When you try to do a re-install you are met with a lock screen shown in EX-1. This is the result of the Mac being most definitely locked from the cloud. There are two options from this point which are explained below.

2019 16″ MacBook Pro. 2018-2019 13″ & 15″ Macbook Pro. 2018-2020 MacBook Air. If u cant generate Hash code, so No need to BUY!!! We do unlock EFI only, if u got ACTIVATION LOCK after, we are not responsable, cause NO CHECK before we start the unlock process. Bypassing EFI Lock on Your Mac. MacOS provides multiple methods to protect the data on a Mac: a user account password, encryption via FileVault, and optional low-level security measure that prevents starting up from storage devices other than the selected startup disk. That's known as the firmware password or EFI (Extensible Firmware Interface) lock, which will also block the user's ability to use all startup key combinations, except the NVRAM or PRAM reset combinations. Brand new pre-programmed EFI Bios chip. 100% working and confirmed with clean ME Region. The EFI Bios chip can be used for the followings: – Fix Corrupted Firmware caused during updates. – Remove iCloud Lock (4 or 6 Pin Code) – Remove Mac EFI Password Lock, Unlock Disabled Mac.

EX-1

EX-1.1

NOTE: If you have a 2010 model MBP or earlier all you have to do is change the amount of RAM in your MBP and clear the PRAM. This is all you have to do to get past OS lock. But you will still have a firmware lock as far as I know as in many cases this has happened. There have been occasions where the firmware lock has also been removed but I cannot contest to any exact models. Remember to set the Mac up like new and register the Mac with a new iCloud account to avoid any future lock-downs.

Macbook Pro Efi Password Removal

Option A: You can assume that a firmware lock was never set and brute force the firmware lock with a HID device such as a Teensy. This operation can take quite a while because it has to go through 10,000 iterations of possible pass-phrases in the worst case scenario. This will ONLY work if it was set by the iCloud!

Option B: You can assume that a firmware lock was indeed implicated when the MBP was set up and that the brute force method will not work. This can save you time but requires you to have a SPI programmer at hand such as the Bus Pirate or in this case a Raspberry Pi.

In A Nutshell

I won't waste time on the brute force method as I believe it isn't relevant in most cases. I will focus on the process of flashing the EFI chip that is usually easily accessible by removing the Macs's back-plate, either by a small 15X2 header, 17X2 header, or the 8 pin SOIC chip itself. You can see an image of the SOIC8 chip in EX-2 and the header in EX-2.1. The process is simple but requires a bit of knowledge in micro controllers. I will use the easiest and cheapest route that I know. The process goes briefly like this:

EX-2

EX-2.1

Step 1 – Buy a SPI programmer such as the Raspberry Pi and a clip to interface with the chip. You can find the Pi on eBay, doesn't matter what model and you can find the Pomona SOIC8 clip there as well, usually with the female-to-female wires included. If you have a MBA then you can contact me about purchasing a clip for the header.

Step 2 - Read the chip three times and verify MD5 check-sum to ensure you have a good backup if things go wrong.

Step 3 – Make a copy of the dump and open it in a hex editor. I use Notepad ++.

Step 4 - Search for '$SVS' in the dump and you should find 2 instances. The first instance is what you will need to clear out making sure to keep the file length the same. It is safe to replace it with an empty value such as 'ÿ'. The string including the $SVS should be replaced, you can copy and paste a portion of the string below if needed. each 'ÿ' is 2 bits and 8 bits make a byte So keep that in mind when you replace the string. The file size has to be exactly the same size as the chip or it will return an error.

This is an example of what to replace in a hex editor.

Step 4.1 – Get a clean dump that is not firmware locked from the community making sure you use the correct EMC and processor architecture. Make absolutely sure it is the same size as your original dump which is usually 2, 4, or 8 MB. If you go this route then you will need to replace the serial of the donated dump with your own serial in order to not register over their Mac. You can do this my simply searching for 'override-version' and on that same line there will be an 11 to 12 digit serial number that you will replace with your own. I also have a repository found HERE which you can use to search for your EMC number and I may have a clean dump.

Step 5 – Hook your programmer up to the chip, erase the chip, write the new dump and verify it.

Step 6 – Remove the clip and turn your Mac over to turn it on and test. You will immediately use the hot-keys to get to single user mode to test.

Step 7 – If you do not get to SU mode or the Mac does not boot right you will need to erase the chip and write the old dump back to it. You then can exhaust other options.

Step 7.1 – If you do get to SU mode turn the Mac back off and use the hot-keys to clear the PRAM. This will get rid of the 4 digit lock at OS load. Or you can simply re-install at this point. Remember to register the Mac to a new iCloud account to avoid future lock downs.

NOTE: Here are a few things worth mentioning..

• Make sure your chip is supported in Flashrom which is the program you will be using to talk to the chip.
• You need to make sure the clip makes a solid connection to avoid misreads.
• You need to verify your chips datasheet to correctly identify the pin-out to the SPI programmer.
• The wires connecting the clip to the SPI programmer need not be any longer than 8 cm.
• The battery may need to be connected due to voltage drop in special cases (RARE).
• The power cable should be removed from the Mac during the entire process, up until boot time testing.
• Always make sure to back up your original dump and verify the write.
• Optionally you can wire in resistors between the SPI programmer and the clip on the 3.3v pins.

That is the entire process in a nutshell. Now I will explain how you can do this in as much detail as possible. The first thing that you will need to do is pick up your entire inventory before you begin. After that lay everything out and do some testing. Make sure your chip is supported having the datasheet and any diagrams available. I also suggest after you get the clip connected to all the wires you check for continuity from the clips pins to the end of the F-F wires on each pin.

Down And Dirty

NOTE:Read this guide in its entirety before you attempt to do anything to your Mac; Read it twice if you have to. I would also like to take this time to tell you that I am not responsible for any damages to your personal property or your physical/mental wellness if the guide is used. There is no guarantee, implied or expressed, in this procedure. You are following this guide knowingly and accept that damaging your property may be the outcome. Although I do not for see that being the case as I have tested this method many times. With that being said, let's get started.

This is the list of things you will need in order to successfully and easily fix your MBP:

• Raspberry Pi (Doesn't matter what version) with power supply and an SD card with Rasbian installed.
• 8 Pin Pomona SOIC clip or my EFI Easy Flash clip.
• 8 Female-to-Female wires.
• Flashrom.
• Your chip's datasheet (To verify the chips pin-out and voltage requirements).

Now, I am going to assume that you at least have some experience in Linux and basic troubleshooting skills. You will run into problems and they are not all going to be the same as everyone else's problems. So critical thinking is also required although I have not added it to the list. When you have your Raspberry Pi all set up and Raspian is booted up you will need to set it up for the first time. if you have already set it up go to the terminal and type:

sudo raspi-config

While in this configuration screen make sure to turn SPI on under Advanced. You may also turn on SSH if needed.

Then you will need to do an update by typing:

sudo apt-get update

Followed by an upgrade:

sudo apt-get upgrade

Optionally doing a distrobution upgrade:

sudo apt-get dist-upgrade

Now we have to install a few libraries that Flashrom relies on:

sudo apt-get install pciutils

sudo apt-get install libftdi-dev

sudo apt-get install libusb-dev

sudo apt-get install libpci-dev

Then you need to download the latest flashrom version:

sudo git clone https://github.com/stefanct/flashrom.git

It will be downloaded into a folder called 'flashrom' so change directory into the folder:

cd flashrom

And make it:

sudo make

Then install it:

sudo make install

Now we need to modify the blacklist by commenting out the SPI entry if it exists:

Sudo nano /etc/modprobe.d/raspi-blacklist.conf

You will need to put '#' in front of the line that reads blacklist spi-bcm2708 effectively commenting it from the configuration file. If there is nothing in the file don't worry about it, that means SPI is not blacklisted. You can then save by hitting CTL+X, Y, and ENTER. You will then need to hook the wires up to the Pi and to the clip according to the diagrams below and your chip's datasheet. In MOST cases it will be just like what you see below.

The actual pinout for most 25 series chips depicted above is as follows for those of you who need a more definitive answer:

• Pin 1 of the chip (marked with a small dot) which is CS (Chip Select) goes to pin 24 on the Raspberry Pi.
• Pin 2 of the chip which is MISO (Master Oin Slave Out) goes to pin 21 on the Raspberry Pi.
• Pin 3 of the chip which is WP (Write Protect) goes to pin 17 on the Raspberry Pi. (Usually Not Needed)
• Pin 4 of the chip which is GND (Ground) goes to pin 25 on the Raspberry Pi.
• Pin 6 of the chip which is MOSI (Master Out Slave In) goes to pin 19 on the Raspberry Pi.
• Pin 7 of the chip which is HOLD (Hold) goes to pin 17 in the Raspberry Pi. (Usually Not Needed)
• Pin 8 of the chip which is VCC (Positive Supply Voltage) goes to pin 17 on the Raspberry Pi (3.3v)

Connect the wires on the clip to the Raspberry Pi making sure it is turned off following the diagram above. The GPIO pin that is closest to the corner of the Raspberry Pi is pin 2, keep that in mind or read the manual. After you are all connected you will place the clip on the chip snugly and turn the Pi on. Go to your working directory and run the following commands using some discretion.

**Start of the Flashrom process**

Get to the help page:

sudo flashrom --help

List the supported chips:

sudo flashrom –L

Read the flash chip by using the below command three times:

sudo flashrom –r ~/efi/read1.bin -V -p linux_spi:dev=/dev/spidev0.0

Erase the chip after you have verified all three reads have a matching MD5 hash: Firefox for apple laptop.

sudo flashrom -E -V -p linux_spi:dev=/dev/spidev0.0

Using the methods explained above either modify or get a clean dump making sure it is the same size as the original ROM and write it to the chip:

sudo flashrom -w ~/efi/new.bin -V -p linux_spi:dev=/dev/spidev0.0

Verify the chips contents with the file that you just wrote to ensure its integrity:

sudo flashrom -v ~/efi/bnew.bin -V -p linux_spi:dev=/dev/spidev0.0

If you have not run into any problems you will have a freshly flashed chip. If you did run into issue, use the forum here to start a thread and we will help you troubleshoot your error messages. The reason I always use the –V command is to ensure a verbose output. At this point shut your Pi down and then remove the clip. You will then replace your power supply to the Mac and then turn it on using hot-keys to try and get to SU mode. If you get to SU mode you will shut back down and use the hot-keys to clear PRAM and reinstall setting the Mac up as a new machine. Make sure to register it with a newly created or existing iCloud account to prevent further incidents. If you did not get to SU mode you will need to erase your chip and try again.

That's it folks, this is the long awaited guide that has more than enough information to get you through the process. It is specifically designed to save you money in the recovery of your Mac and to seamlessly work through any prior issues you may have had using Flashrom with a windows PC. If this guide has helped you please think about the years of work I have spent making this possible for you and donate to my iFLRT project to make it even easier for others. Or you can donate to me by using the slider on the edge of the left hand side of the page to donate to my personal PayPal account. Good luck to you all and Happy Hunting…

My company was really kind to get me a Macbook Pro (the 13.3-inch '5.5' variant). It is an awesome piece of hardware! (especially after my own PoS HP laptop I've been cussing at for a while now)

Game of the day apple. That said, I still don't like the idea of running a proprietary operating system on it (as beautiful as OS X is ;)), so I continue to happily use Gentoo. The standard amd64 install works just fine with some minor hiccups (keyboard doesn't work on the LiveCD, kernel only shows a console with vesafb).

Macbook Pro Efi Lock Kit

The one thing that did bother me is BIOS-emulation. For those coming from the PC world, Macs don't have a BIOS. They run something called EFI which is significantly more advanced (though I think the jury's out on quirkiness issues and Linus certainly doesn't approve of the added complexity).

Anyway, in order to support booting other OSes (=> Windows) exactly as they would on PCs, Apple has added a BIOS emulation layer. This is how Ubuntu (at least as of 9.10) boots on Macbooks. Given that both the bootloader (be it Grub2 or elilo) and the Linux kernel support booting in an EFI environment, it rubbed me the wrong way to take the easy way out and just boot them in BIOS mode. There is a reasonable technical argument for this – I see no good reason to add one more layer of software (read bugs) when there is no need at all. After a lot of pain, I did manage do make Linux boot in EFI-only mode. There is not enough (accurate, easily-findable) documentation out there, so this is hard-won knowledge. :) I'm putting this up to help others avoid this pain.

Here's what I did (I might Apple multimedia framework. be missing some stuff since this was done almost a month ago). The basic boot steps look something like this:

1. EFI firmware starts on boot
2. Starts rEFIt, a program that extends the default bootloader to provide a nice bootloader menu, shell, etc.
3. Scans FAT/HFS partitions (no ext* support, despite some claims on the Internet) for bootable partitions (i.e. having a /efi/… directory with valid boot images)
4. Runs the Grub2 EFI image from a FAT partition
5. Loads the Linux kernel (and initrd/initramfs if any) from /boot
6. Kernel boots normally with whatever your root partition is

Macbook Pro Efi Firmware

Now you could use elilo instead of Grub2, but I found this it to not work well (or at all) for me, so I just used a Grub2 (1.97.1, with some minor modifications) (just adds an 'efi' USE-flag to build with --with-platform=efi). While I could make /boot a FAT partition, this would break the installkernel script (it's run by make install in your kernel source directory), which makes symlinks for your latest/previous kernel image.

Macbook Pro Efi Lock Removal Tool

Instructions for installing the Grub2 EFI image are here. Just ignore the 'bless' instructions (that's for OS X), and put the EFI image and other stuff in something like /efi/grub (the /efi is mandatory). You can create a basic config file using grub-mkconfig and then tweak it to taste. The Correct Way™ to do this, though, is to edit the files in /etc/grub.d/.

Of course, you need to enable EFI support in the kernel, but that's it. With this, you're all set for the (slightly obsessive-compulsive) satisfaction of not having to enable yet another layer to support yet another proprietary interface, neither of which you have visibility or control over.