Contribute
Register

[APFS] High Sierra 10.13.1 - No early logging

Status
Not open for further replies.
Thanks for the post, it worked on both 10.13.1 and 10.13.2.

I tried 10.13.2 and found the 0x55 at 0x22474, replace with 0xC3 as the post #1 and it worked.
MD5 of the original: da1e17572159b5db36f637c9d48ac2cb
MD5 after edit: 21e480e5e3bd91abf964ed46843b1b6c
Applied the edited version on two custom macs and both worked. One of them was Nuc6i7kyk, which used to show the log for quite a few seconds.

Actually, I wrote this string from the post #1 when looking for 0x55:
00 48 83 C4 48 5E 5D C3 55 48 89 E5 4D 89 C1 48
And use it again in 10.13.2 to locate the 0x55. The string appears only once, so it seems safe to try. Of cause, use at your own risk.
 
Yes, copy and then patch the apfs.efi file to your EFI partition with the code below:

Code:
cp /usr/standalone/i386/apfs.efi /Volumes/EFI/EFI/CLOVER/drivers64UEFI

perl -i -pe 's|\x00\x74\x07\xb8\xff\xff|\x00\x90\x90\xb8\xff\xff|sg' /Volumes/EFI/EFI/CLOVER/drivers64UEFI/apfs.efi

You could use it in a script as it seems it should work with future apfs versions.




Thank you this works.
 
Still working on 10.13.3 (17D47) with Clover 4411. Thank you!
 
Last edited:
Yes, copy and then patch the apfs.efi file to your EFI partition with the code below:

Code:
cp /usr/standalone/i386/apfs.efi /Volumes/EFI/EFI/CLOVER/drivers64UEFI

perl -i -pe 's|\x00\x74\x07\xb8\xff\xff|\x00\x90\x90\xb8\xff\xff|sg' /Volumes/EFI/EFI/CLOVER/drivers64UEFI/apfs.efi

You could use it in a script as it seems it should work with future apfs versions.

Thank you, still working fine on apfs.efi from macOS High Sierra 10.13.4
 
Patch per post #11 still works with 10.13.4 Supplemental Update.
 

Attachments

  • apfs.efi.zip
    270.5 KB · Views: 175
Yes, copy and then patch the apfs.efi file to your EFI partition with the code below:

Code:
cp /usr/standalone/i386/apfs.efi /Volumes/EFI/EFI/CLOVER/drivers64UEFI

perl -i -pe 's|\x00\x74\x07\xb8\xff\xff|\x00\x90\x90\xb8\xff\xff|sg' /Volumes/EFI/EFI/CLOVER/drivers64UEFI/apfs.efi

You could use it in a script as it seems it should work with future apfs versions.

EDIT:

I've attached a script below that can be run after an update. It will mount the EFI partition at disk0s1 if necessary then copy and patch the local apfs.efi file to drivers64UEFI if it's timestamp is more recent. It will indicate success or otherwise then unmount the EFI partition. It's quick and easy to do this if you also need to open the Terminal and rebuild your kext cache after an update.
This code is run in Terminal, correct?
 
Status
Not open for further replies.
Back
Top