Clover General discussion

[Riley Freeman]

APFS on my laptop (i3, 5400RPM disk) is unusably slow. On my X79 (i7, 7200RPM disk) it runs pretty well.

[artur_pt]

 

 

Here's a fix for those having issues with the firmware during macOS High Sierra installation.

 

Needs testing to make sure it's not causing issues for others.

 

Best regards.

 

hello

 

very good job with that clover version

 

thanks

[Sherlocks]

hello.

 

i made clear fakecpuid source

 

please test

sierra

high sierra

 

thanks in advance

sherlocks-fakecpuid fixv2.zip

[Kynyo]

APFS on my laptop (i3, 5400RPM disk) is unusably slow. On my X79 (i7, 7200RPM disk) it runs pretty well.

APFS support its still at its first days, its a beta. In fact APFS was designed for flash Disk not HDD. Till HS final release it will be good i suppose.

[wern apfel]

if you got many hard disk connected, try disable spotlight search, indexing all those disks will take days.

 

Sent from my MI 3W using Tapatalk

I use two drives, it is not only slow it's very slow it takes 5 to 10 minutest to startup and the Finder takes minutes to open up. I would say we have to wait for the next update.

[Riley Freeman]

APFS support its still at its first days, its a beta. In fact APFS was designed for flash Disk not HDD. Till HS final release it will be good i suppose.

 

Yep, I wasn't even planning to use it, but curiosity got the better of me. I was surprised at the difference in performance between the two systems.

 

My X79 has a fusion drive so whenever I update the main install to 10.13 I might consider APFS.

[arsradu]

Hey guys.

 

More updates on the installation issues (OSInstall.mpkg missing or damaged).

 

I tried to install HS on another system and it didn't work until I completely formatted the entire HDD. Not just the partition. I don't know why, I don't know what the hell is it trying to do that requires the drive to be completely wiped, but this is annoying as hell.

 

I tried removing only the Recovery partition. I thought this might be the culprit. But nope. Not that.

I tried booting with Clover 4084 (from a few pages back) and the updated BIOS information provided by Needy in another post. Not sure that was related in any way. Still, no luck.

 

ONLY after I completely formatted the entire HDD, I managed to get it to install. And it worked with both 4081 and 4084. Not sure if the updated BIOS information from SMBIOS are doing anything. But...so far it doesn't look like they do. Since it failed even with that, and even with r4084. So, in my experience, that doesn't quite help in this case.

 

The only thing that worked is a full wipe of the entire HDD. Which sucks if you have other things on that HDD.

 

Anyway, hope my experiences help others on their way to install this release. I hope this won't be necessary with future Betas or final version cause I don't want to format my entire SSD just to get this thing installed.

 

Cheers!

[Riley Freeman]

I still don't understand where these osinstall errors are coming from. The only time I saw this was when the beta first dropped and the install was failing to verify the firmware. That was before Clover was updated with the right values.

 

I didn't have to do a full wipe here (my laptop has 10.11 and 10.12 on it and now 10.13 as well -  all on the same disk). I just used the createinstallmedia method to build a usb installer and that was it. I've installed 10.13 about a half dozen times over the last few days onto the laptop and never saw this error.

 

If you get that message and can boot into another system, the ia.log file in the macOS Install Data folder on the target disk might hold some clue as to what's causing it.

[Cyberdevs]

I still don't understand where these osinstall errors are coming from. The only time I saw this was when the beta first dropped and the install was failing to verify the firmware. That was before Clover was updated with the right values.

 

I didn't have to do a full wipe here (my laptop has 10.11 and 10.12 on it and now 10.13 as well -  all on the same disk). I just used the createinstallmedia method to build a usb installer and that was it. I've installed 10.13 about a half dozen times over the last few days onto the laptop and never saw this error.

 

If you get that message and can boot into another system, the ia.log file in the macOS Install Data folder on the target disk might hold some clue as to what's causing it.

 

Before clover 4084 I've seen both OSInstall.mpkg and Firmware Verification error while I was trying to instal High Sierra, I even encountered some errors using disk utility to erase my SSD to AFPS system, but since clover 4084 I've tested the whole process over and over but no more errors.

 

I got to say I never tried to install macOS on another partition so I wouldn't know if installing it on a hard disk that already has another macOS on it might complicate things. All my installations were clean installs on an independent drive.

 

But the weird thing is that people are still getting those errors. IMHO there must be some other factors at play on their systems, like what arsradu posted earlier.

[Badruzeus]

Hey guys.

 

More updates on the installation issues (OSInstall.mpkg missing or damaged).

 

Interesting  appl*insider.com: "The MacBook Pro needed a re-install of High Sierra after the machine's EFI partition was corrupted for reasons unknown —but it hasn't happened since." I think Appl* plan to sell separated SSD with preformated APFS on it LoL 

[hugotai]

Interesting appl*insider.com: "The MacBook Pro needed a re-install of High Sierra after the machine's EFI partition was corrupted for reasons unknown —but it hasn't happened since." I think Appl* plan to sell separated SSD with preformated APFS on it LoL

I think the error maybe cause by the APFS container thing?

 

Sent from my MI 3W using Tapatalk

[arsradu]

I still don't understand where these osinstall errors are coming from. The only time I saw this was when the beta first dropped and the install was failing to verify the firmware. That was before Clover was updated with the right values.

 

I didn't have to do a full wipe here (my laptop has 10.11 and 10.12 on it and now 10.13 as well -  all on the same disk). I just used the createinstallmedia method to build a usb installer and that was it. I've installed 10.13 about a half dozen times over the last few days onto the laptop and never saw this error.

 

If you get that message and can boot into another system, the ia.log file in the macOS Install Data folder on the target disk might hold some clue as to what's causing it.

 

Well, now I managed to install it. So, even though I would have been able to get that from another system, I'm not anymore, since the installation completed successfully now. Twice.

 

But maybe I'll fiddle some more with the spare HDD I've got it installed right now. See if I can get it to fail again. I think the the fail might be related to the Recovery partition though... Meaning, if you try to update from 10.12 to 10.13, without a full wipe, that Recovery partition might cause problems. However, I had the same issue even after manually removing the Recovery partition from one disk on which I had Sierra and Windows. I thought the reason why it didn't work was that Recovery. So I only removed that. But it looks like it didn't work after that either. The only things that worked so far, was a full wipe of the HDD...

 

So, I find it very intriguing that it worked for you. ) I'm glad for you. But I'm also confused. Cause I couldn't get it to work until that full wipe.

 

I'll try another full wipe. But this time, I'm gonna try to put back Sierra. And then attempt an update... It worked for me once. And I don't think I formatted the entire drive then... But I'll try again. See if that might cause any issues. Otherwise, this looks random as hell. And annoying as hell, as well.

 

I didn't have to format anything on my MBP. Why the hell would I need to format the HDD in order for this to work? It makes no sense to me.

 

Also, I didn't encounter any issues with slow performance with the drive formatted as HFS. However, I got issues on boot (now, reading everyone's comments so far, it looks like it might have been booted if I let it) with the drive formatted as APFS. Meaning it looked like it hanged on boot. Like when you don't have FakeSMC and it can't get to the desktop. That kind of issue.

 

Sorry for the long post. I just hope that maybe, some of the details I'm sharing here could help someone else.

[cecekpawon]

I still don't understand where these osinstall errors are coming from. The only time I saw this was when the beta first dropped and the install was failing to verify the firmware.

 

Can we just NOP this jump to tricks firmware/APFS check?

 

** Meh, I think its just a routine for displaying error message

Edited June 9, 2017 by cecekpawon

[Cyberdevs]

Hi guys,

 

First of all, I would like to thank you all for all the hard work you are doing. You guys ROCK!

 

I would like to share something. I've been testing macOS High Sierra and so far It works great, I'm using clover 4084 and it's working great, I was able to install macOS High Sierra successfully several times, so I decided to give installing macOS High Sierra on flash drive another shot with the new clover.

 

I wasn't able to install it on USB flash drive on my hackintosh for some unknown reason, after the first stage of the installation process, clover won't be able to show the USB flash drive after the first reboot, so I decided to make the USB disk on my MacBook Air, which I already succeeded to install Mac OS High Sierra on USB disk before.

 

So I plugged in the macOS Sierra installer and the USB drive that I had completed the first stage of the installation on my hackintosh to my MacBook Air and then I noticed that I can boot into the flash drive to continue the installation and it just booted to the second stage of installation.

 

I thought it might be useful to report this.

 

Thanks a lot and Cheers!

[Sherlocks]

i added kabylake smbios 

 

please test kabylake users

 

also

if you use fakecpuid,

test in 10.13

and in 10.12

 

enjoy and report result to me

sherlocks-fakecpuid fix-v3.zip

[frnic]

Is there a setting in the Config file that would prevent Clover from recognizing an HD that has High Sierra installed on it as bootable? Everything on the disk I am installing HS onto looks right, and I can not get Clover to show it. It shows up fine in my BIOS and if I install clover on the drive, it still does not show up, but if I remove all other drives from the computer and point my BIOS at it, it will boot Clover, but not show any drives to select from.

[Needy]

Can we just NOP this jump to tricks firmware/APFS check?

 

** Meh, I think its just a routine for displaying error message

The idea is not touch the original files. As long as we provide valid data the check will succeed.

 

This is the check, you're looking in the wrong direction.

0000000000023a5e push rbp ; Objective C Implementation defined at 0x5d350 (instance method), DATA XREF=0x5d350
0000000000023a5f mov rbp, rsp
0000000000023a62 push r15
0000000000023a64 push r14
0000000000023a66 push rbx
0000000000023a67 push rax
0000000000023a68 mov rax, qword [_kIOMasterPortDefault_52210]
0000000000023a6f mov ebx, dword [rax]
0000000000023a71 lea rsi, qword [0x49504] ; "IODeviceTree:/rom@0", argument "path" for method imp___stubs__IORegistryEntryFromPath
0000000000023a78 mov edi, ebx ; argument "masterPort" for method imp___stubs__IORegistryEntryFromPath
0000000000023a7a call imp___stubs__IORegistryEntryFromPath
0000000000023a7f mov r14d, eax
0000000000023a82 test r14d, r14d
0000000000023a85 jne loc_23aa1

0000000000023a87 lea rsi, qword [0x49518] ; "IODeviceTree:/rom@e0000", argument "path" for method imp___stubs__IORegistryEntryFromPath
0000000000023a8e mov edi, ebx ; argument "masterPort" for method imp___stubs__IORegistryEntryFromPath
0000000000023a90 call imp___stubs__IORegistryEntryFromPath
0000000000023a95 mov r14d, eax
0000000000023a98 test r14d, r14d
0000000000023a9b je loc_23b3f

loc_23aa1:
0000000000023aa1 mov rax, qword [_kCFAllocatorDefault_52178] ; CODE XREF=-[OSIVerifyROMElement apfsSupportedByROM]+39
0000000000023aa8 mov rdx, qword [rax] ; argument "allocator" for method imp___stubs__IORegistryEntryCreateCFProperty
0000000000023aab lea rsi, qword [cfstring_firmware_features] ; @"firmware-features", argument "key" for method imp___stubs__IORegistryEntryCreateCFProperty
0000000000023ab2 xor ecx, ecx ; argument "options" for method imp___stubs__IORegistryEntryCreateCFProperty
0000000000023ab4 mov edi, r14d ; argument "entry" for method imp___stubs__IORegistryEntryCreateCFProperty
0000000000023ab7 call imp___stubs__IORegistryEntryCreateCFProperty
0000000000023abc mov rdi, rax ; argument "cf" for method imp___stubs__CFMakeCollectable
0000000000023abf call imp___stubs__CFMakeCollectable
0000000000023ac4 mov rsi, qword [0x5d6a8] ; @selector(autorelease), argument "selector" for method _objc_msgSend
0000000000023acb mov rdi, rax ; argument "instance" for method _objc_msgSend
0000000000023ace call qword [_objc_msgSend_52268] ; _objc_msgSend
0000000000023ad4 mov rbx, rax
0000000000023ad7 test rbx, rbx
0000000000023ada jne loc_23aef

0000000000023adc lea rsi, qword [0x4bd99] ; "ROM Features returned nil!", argument "message" for method imp___stubs__syslog
0000000000023ae3 mov edi, 0x76 ; argument "priority" for method imp___stubs__syslog
0000000000023ae8 xor eax, eax
0000000000023aea call imp___stubs__syslog

loc_23aef:
0000000000023aef mov rsi, qword [0x5dd18] ; @selector(unsignedLongLongValue), argument "selector" for method _objc_msgSend, CODE XREF=-[OSIVerifyROMElement apfsSupportedByROM]+124
0000000000023af6 mov rdi, rbx ; argument "instance" for method _objc_msgSend
0000000000023af9 call qword [_objc_msgSend_52268] ; _objc_msgSend
0000000000023aff mov rbx, rax
0000000000023b02 lea rsi, qword [0x4bdb4] ; "ROM Features returned: %llu", argument "message" for method imp___stubs__syslog
0000000000023b09 mov edi, 0x76 ; argument "priority" for method imp___stubs__syslog
0000000000023b0e xor eax, eax
0000000000023b10 mov rdx, rbx
0000000000023b13 call imp___stubs__syslog
0000000000023b18 test ebx, 0x1c0000
0000000000023b1e setne r15b
0000000000023b22 xor ebx, ebx
0000000000023b24 mov edi, r14d ; argument "object" for method imp___stubs__IOObjectRelease, CODE XREF=-[OSIVerifyROMElement apfsSupportedByROM]+296
0000000000023b27 call imp___stubs__IOObjectRelease
0000000000023b2c test bl, bl
0000000000023b2e jne loc_23b57

loc_23b30:
0000000000023b30 movsx eax, r15b ; CODE XREF=-[OSIVerifyROMElement apfsSupportedByROM]+247
0000000000023b34 add rsp, 0x8
0000000000023b38 pop rbx
0000000000023b39 pop r14
0000000000023b3b pop r15
0000000000023b3d pop rbp
0000000000023b3e ret
; endp

loc_23b3f:
0000000000023b3f lea rsi, qword [0x4bd5a] ; "ROM Features failed to open IORegistryEntry!", argument "message" for method imp___stubs__syslog, CODE XREF=-[OSIVerifyROMElement apfsSupportedByROM]+61
0000000000023b46 xor r15d, r15d
0000000000023b49 mov edi, 0x76 ; argument "priority" for method imp___stubs__syslog
0000000000023b4e xor eax, eax
0000000000023b50 call imp___stubs__syslog
0000000000023b55 jmp loc_23b30

loc_23b57:
0000000000023b57 call imp___stubs__objc_exception_rethrow ; CODE XREF=-[OSIVerifyROMElement apfsSupportedByROM]+208
; endp
0000000000023b5c mov r14, rax
0000000000023b5f jmp -[OSIVerifyROMElement apfsSupportedByROM]+266
0000000000023b61 mov r14, rax
0000000000023b64 test bl, bl
0000000000023b66 je -[OSIVerifyROMElement apfsSupportedByROM]+271
0000000000023b68 call imp___stubs__objc_end_catch ; CODE XREF=-[OSIVerifyROMElement apfsSupportedByROM]+257
0000000000023b6d mov rdi, r14 ; CODE XREF=-[OSIVerifyROMElement apfsSupportedByROM]+264
0000000000023b70 call imp___stubs___Unwind_Resume
0000000000023b75 call imp___stubs__objc_terminate
0000000000023b7a jmp -[OSIVerifyROMElement apfsSupportedByROM]+286
0000000000023b7c mov rdi, rax ; CODE XREF=-[OSIVerifyROMElement apfsSupportedByROM]+284
0000000000023b7f call imp___stubs__objc_begin_catch
0000000000023b84 mov bl, 0x1
0000000000023b86 jmp -[OSIVerifyROMElement apfsSupportedByROM]+198

It checks the IORegistry for rom and its variables.

 

This fixes the firmware issue.

http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2438129

I wanted to see if it's not causing issues first. From the reports I see in the installation topic, I conclude that it's fixing the issue with no side effects.

 

The code will be updated soon.

 

 

Is there a setting in the Config file that would prevent Clover from recognizing an HD that has High Sierra installed on it as bootable? Everything on the disk I am installing HS onto looks right, and I can not get Clover to show it. It shows up fine in my BIOS and if I install clover on the drive, it still does not show up, but if I remove all other drives from the computer and point my BIOS at it, it will boot Clover, but not show any drives to select from.

Hey there,

http://www.insanelymac.com/forum/topic/324194-pre-release-macos-high-sierra/?p=2438960

Best regards.

[mashny]

i added kabylake smbios 

 

please test kabylake users

 

also

if you use fakecpuid,

test in 10.13

and in 10.12

 

enjoy and report result to me

 

Boots fine on 10.12, doesn't work on 10.13 set up (non usb). I get the MACH reboot error.

 

 

config.plist.zip

[Sherlocks]

Boots fine on 10.12, doesn't work on 10.13 set up (non usb). I get the MACH reboot error.

Fakecpuid?

Tell me exactly.

MACH reboot error maybe relate ACPI.

need to drop some ACPI tables. Test step by step

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

[p.H]

hello.

 

i made clear fakecpuid source

 

please test

sierra

high sierra

 

thanks in advance

 

 Maybe quote me next time so I can receive notification as soon as possible. I will give it a shot now. BTW, is this one fakeid updated?

i added kabylake smbios 

 

please test kabylake users

 

also

if you use fakecpuid,

test in 10.13

and in 10.12

 

enjoy and report result to me

I think it works for 10.13. If fakecpuid doesn't work, my hack would reboot instantly.

[mashny]

Fakecpuid?

Tell me exactly.

MACH reboot error maybe relate ACPI.

need to drop some ACPI tables. Test step by step

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

[Sherlocks]

 

Fakecpuid?

Tell me exactly.

MACH reboot error maybe relate ACPI.

need to drop some ACPI tables. Test step by step

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

Give me your clover log with config.plist removed private info in 10.12

 

나의 LG-F800S 의 Tapatalk에서 보냄

[p.H]

Give me your clover log with config.plist removed private info in 10.12

 

나의 LG-F800S 의 Tapatalk에서 보냄

Does the fix v3 update fakeid patch?

[Sherlocks]

Does the fix v3 update fakeid patch?

What fakeid? Wifi?

 

Gpu? If you said igpu, yes it update. Just checked intel inject.(fakeintel-blank and platformid-blank)

 

Iike i said before, i think that dont expect work about pentium igpu(hd630,hd530).

 

나의 LG-F800S 의 Tapatalk에서 보냄

[p.H]

What fakeid? Wifi?

 

Gpu? If you said igpu, yes it update. Just checked intel inject.(fakeintel-blank and platformid-blank)

 

Iike i said before, i think that dont expect work about pentium igpu(hd630,hd530).

 

나의 LG-F800S 의 Tapatalk에서 보냄

Yeah. I got you. But I want to fake a nonsense id so that the related Kabylake iGPU kexts won't load. In the past, I always installed the system without minimal kexts. No graphics, no ethernet, no wifi, etc. This would give me minimal interference. So what I want to know is whether fake gpu id will work for 10.13 with your fix.