All the text in the message will be deleted and replaced by text from category template.
Max. showing the last 6 posts - (Last post first)
Great, please submit to me when you have completed.
Sure, I'll write. I think we also need to say about things which better do not do ever if efi-pass set and unknown. Such as 'target-mode', Recovery Disk erasing... etc.
Great alternative Token, can you write a tutorial on this to be posted in the blog section? I need to create a workflow on this. Such as does your mac boot? yes - do this, no - do something else... and so on and so forth.
If you able to boot the better way is take a SSD from your MBP and do corrections inside one file on filesystem. In other words, you need to connect SSD to the machine where you CAN be an admin user.
Edit file <SSD_MOUNT_POINT>/Library/Preferences/SystemConfiguration/com.apple.Boot.plist
File may be a binary plist file, so you may need to convert it into xml by command: sudo plutil -convert xml1 com.apple.Boot.plist
This file can provide a boot arguments for the kernel. -s,-v etc... You need to boot into single user mode, so '-s' is your option.
Here an example of file for booting into single user mode with verbose output:
After you change a file umount SSD, return it back to the MBP and boot. You should be booted into single user mode and you are root......
<dict>
<key>Kernel Flags</key>
<string>-s</string>
<string>-v</string>
</dict>
.....
Reboot, login... enjoy.....
<dict>
<key>Kernel Flags</key>
<string></string>
</dict>
....
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 499.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
Your logic is fine; however I would like to clarify it for you. If a EFI password is set by a person then it will not be changed when the iCloud lock is initiated. If you use another MBP and swap drives or even copy the entire disk image to another drive (clone it) then you will be able to use it as normal. The fact that the iCloud lock has not been set is the actual deciding factor of which way you can go. I need to make a flowchart for the decision making process for everyone. Once you are logged in as and admin then you can actually change the EFI password from the OS, which in your case is like gold. I am not sure if this is actually still valid with late MBP/MBA but its worth a shot. Token.Paul could answer this better maybe?
Step 1: My suggested plan of action for you is to clone a drive and use it to gain access to the MBP.
Step 2: Use command line tools to reset the EFI password if at all possible.
Step 3: Reinstall OSX from the recovery menu to ensure optimized performance.
Step 4: Set the EFI password the normal way and make sure your device is registered under your own account in iCloud.
ALT: If for some reason you cannot reset the EFI password from the OS then you need flash the EFI chip! This will better serve you in the future...
I have a mid 2014 MBP from a university with a efi lock for recovery boot (black screen with lock). It boots to the standard apple login screen. I was thinking of borrowing another 2013-14 MBP and swapping the original SSD to the new one to access recovery and install a fresh copy of OSX. I realize the efi lock would still be on the original, but wouldn't matter if I could use it.
Also, if I set my own iCloud lock and unlock it, I'm guessing that the original efi password would still be on the MPB? Being that this is not an iCloud lock, and a EFI password set by the university.
Is my logic ok here, or am I completely off?
EMC number 2875
We have 414 guests and no members online
This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.
You have declined cookies. This decision can be reversed.
You have allowed cookies to be placed on your computer. This decision can be reversed.
This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.