Clover General discussion

[chris1111]

1 minute ago, Sherlocks said:

No need both BaseSystem.dmg and InstallESD.dmg.

What is your process?

1. In 10.13.x, did you use startosinstall to install 10.13.4?

2. In 10.12.x or older, did you use starosinstall to install 10.13.4?

No this is for my personal Test 

[Sherlocks]

1 minute ago, chris1111 said:

No this is for my personal Test 

Okay. But i need info to resolve problem on all cases

Please upload zip. I need to check info of correct installation.

[chris1111]

10 minutes ago, Sherlocks said:

Okay. But i need info to resolve problem on all cases

Please upload zip. I need to check info of correct installation.

Here the file FILE

Edited April 1, 2018 by chris1111

[Sherlocks]

20 minutes ago, chris1111 said:

Here the file FILE

i see. there are old data in your ia.log. strange. normally, recorded one info about os build. 

but you have many os info since 2017.10.1

Oct  1 10:13:34 chriss-iMac Installer[618]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  1 10:21:16 chriss-iMac Installer[761]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  1 10:21:28 chriss-iMac Installer[765]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  1 12:46:20 chriss-iMac Installer[787]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  1 12:46:20 chriss-iMac Installer[787]: Installation check failure.  Mac OS X version is not compatible. Mac OS X version 10.12.6 (16G29) is not supported with this package. Please see NVIDIA’s website for further driver information..
Oct  2 15:15:34 chriss-iMac Installer[397]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  2 15:16:03 chriss-iMac Installer[427]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  2 15:16:17 chriss-iMac Installer[434]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  2 15:16:41 chriss-iMac Installer[460]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  2 20:25:35 chriss-iMac Installer[422]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  4 06:19:17 chriss-iMac Installer[499]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  4 14:28:12 chriss-iMac Installer[594]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  4 14:28:21 chriss-iMac Installer[601]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  4 18:23:13 chriss-iMac Installer[429]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  4 20:04:39 chriss-iMac Installer[14365]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  4 20:05:20 chriss-iMac installd[290]: ./preinstall: ProductName:	Mac OS X
Oct  4 20:08:21 chriss-iMac Installer[14636]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  4 20:08:46 chriss-iMac installd[290]: ./preinstall: ProductName:	Mac OS X
Oct  4 20:18:00 chriss-iMac Installer[14709]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  4 20:20:07 chriss-iMac Installer[26789]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  4 20:20:33 chriss-iMac installd[313]: ./preinstall: ProductName:	Mac OS X
Oct  4 20:29:07 chriss-iMac Installer[12609]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  4 20:29:28 chriss-iMac installd[286]: ./preinstall: ProductName:	Mac OS X
Oct  4 20:36:35 chriss-iMac Installer[26789]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  4 20:36:56 chriss-iMac installd[317]: ./preinstall: ProductName:	Mac OS X
Oct  5 09:37:30 chriss-iMac Installer[493]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  5 13:53:51 chriss-iMac Installer[494]: Running OS Build: Mac OS X 10.12.6 (16G29)
Oct  5 13:54:24 chriss-iMac installd[349]: ./preinstall: ProductName:
~~~~~~~~~~~omitted~~~~~~~~----
2018-03-31 16:12:34-04 iMac-de-chris Installer[18259]: Running OS Build: Mac OS X 10.13.4 (17E199)
2018-03-31 16:55:36-04 iMac-de-chris Installer[925]: Running OS Build: Mac OS X 10.13.4 (17E199)
2018-03-31 17:06:49-04 iMac-de-chris Installer[1209]: Running OS Build: Mac OS X 10.13.4 (17E199)
2018-03-31 17:49:14-04 iMac-de-chris Installer[1424]: Running OS Build: Mac OS X 10.13.4 (17E199)
2018-03-31 17:54:00-04 iMac-de-chris Installer[543]: Running OS Build: Mac OS X 10.13.4 (17E199)
2018-03-31 19:12:18-04 iMac-de-chris Installer[613]: Running OS Build: Mac OS X 10.13.4 (17E199)
2018-03-31 21:01:10-04 iMac-de-chris Installer[763]: Running OS Build: Mac OS X 10.13.4 (17E199)
2018-03-31 21:01:19-04 iMac-de-chris Installer[773]: Running OS Build: Mac OS X 10.13.4 (17E199)
2018-03-31 21:03:01-04 iMac-de-chris Installer[778]: Running OS Build: Mac OS X 10.13.4 (17E199)
2018-03-31 21:10:31-04 iMac-de-chris Installer[823]: Running OS Build: Mac OS X 10.13.4 (17E199)
2018-03-31 21:11:50-04 iMac-de-chris Installer[835]: Running OS Build: Mac OS X 10.13.4 (17E199)
2018-03-31 21:12:16-04 iMac-de-chris Installer[837]: Running OS Build: Mac OS X 10.13.4 (17E199)
2018-03-31 21:12:46-04 iMac-de-chris Installer[839]: Running OS Build: Mac OS X 10.13.4 (17E199)
2018-03-31 21:22:00-04 iMac-de-chris Installer[862]: Running OS Build: Mac OS X 10.13.4 (17E199)
2018-03-31 22:22:01-04 iMac-de-chris Installer[18126]: Running OS Build: Mac OS X 10.13.4 (17E199)

 

clover read only one OS Build information from ia.log. because there is no systemversion.plist in macos install data folder.. so best way is that read ia.log to find os build number.

but your ia.log has history log. i first see this case. in your ia.log, first line Oct  1 10:13:34 chriss-iMac Installer[618]: Running OS Build: Mac OS X 10.12.6 (16G29)

so your install entry shown 10.12.6. i think you have to cleanup ia.log.

cleanup means that no remove ia.log. i don't know where is location ia log history in your booted partition.

 

Edited April 1, 2018 by Sherlocks

[chris1111]

I have 5 OS on my PC I never have issue before 10.13.4 to see the good icon on startosinstall

its not a problem with Create Install Media

also  its not a Probleme with Clover r 4419 because I test the command before your commits Fix 

maybe you have to test on your side the command ? ? ?

 

EDIT  ***** I test on my Laptop now, I only have one macOS and I report after test 

Edited April 1, 2018 by chris1111

[Sherlocks]

31 minutes ago, chris1111 said:

I have 5 OS on my PC I never have issue before 10.13.4 to see the good icon on startosinstall

its not a problem with Create Install Media

also  its not a Probleme with Clover r 4419 because I test the command before your commits Fix 

maybe you have to test on your side the command

try this

-removed- to avoid confusion.

 

EDIT1.

this is not other issue. just only OS version detection.

we need to find best way for remaining other side. i'm thinking....

EDIT2.

can you upload screenshot OSVersion with 10.13.4 entry in GUI on r4419?

i want to see whether OSversion 10.13.4 correctly.

Edited April 1, 2018 by Sherlocks

[chris1111]

16 minutes ago, Sherlocks said:

try this

test1.zip

EDIT1.

this is not other issue. just only OS version detection.

we need to find best way for remaining other side. i'm thinking....

EDIT2.

can you upload screenshot OSVersion with 10.13.4 entry in GUI on r4419?

i want to see whether OSversion 10.13.4 correctly.

Ok I test in my Laptop Clover 4423 and Icon is show correct  so you have right I need to clean ialog 

How can do this ? Thank you man for the effort and your work

Edited April 1, 2018 by chris1111

[Sherlocks]

7 minutes ago, chris1111 said:

Ok I test in my Laptop Clover 4423 and Icon is show correct  so you have right I need to clean ialog 

How can do this ? Thank you man for the effort and your work

I'm thinking.. Without clean ia.log, get more correct os version.

But now, i don't have better idea that osversion read from ia.log like your case that recorded old history about installation of startosinstall.

Its not normal case. But still there is 1% issue. I want to clear it. I will consider later if i think best idea.

Thank you for report

 

Edited April 1, 2018 by Sherlocks

[apianti]

5 hours ago, chris1111 said:

Its not a copy its startosinstall Apple tools deploy macOS on any volume

edit *** you need to redo installation tests to get you up to date my friend  

Do you need InstallESD.dmg

I hope not ?

Yeah and I was asking if you copied it because I don't see the folder Locked Files...? And more importantly I was asking why not just run the upgrade in place?

3 hours ago, Sherlocks said:

I'm thinking.. Without clean ia.log, get more correct os version.

But now, i don't have better idea that osversion read from ia.log like your case that recorded old history about installation of startosinstall.

Its not normal case. But still there is 1% issue. I want to clear it. I will consider later if i think best idea.

Thank you for report

 

Just read InstallInfo.plist then the key "Payload Image Info\version" holds the version of the installer...?

[Sherlocks]

12 hours ago, apianti said:

Yeah and I was asking if you copied it because I don't see the folder Locked Files...? And more importantly I was asking why not just run the upgrade in place?

Just read InstallInfo.plist then the key "Payload Image Info\version" holds the version of the installer...?

i didn't notice this. thank you so much!

[chris1111]

13 hours ago, apianti said:

 importantly I was asking why not just run the upgrade in place?

 

Because I testing  the Apple startosinstall tools on 10.13.4  macOS installer.app

I have already 10.13.4 on my main SSD since the first days update 10.13.4

Edited April 2, 2018 by chris1111

[apianti]

16 minutes ago, chris1111 said:

Because I testing  the Apple startosinstall tools on 10.13.4  macOS installer.app

I have already 10.13.4 on my main SSD since the first days update 10.13.4

Hahaha, Chris I was telling just messing with you man. I got what you were doing, I was just teasing you. I really was just making sure you hadn't copied the files, that's all.

43 minutes ago, Sherlocks said:

i didn't notice this. thank you so much!

Oh np, although when is that file available? Just for startosinstall?

[Sherlocks]

47 minutes ago, apianti said:

Oh np, although when is that file available? Just for startosinstall?

yes. i checked all. 1% issue(startosinstall) was resolved now.

also i checked 10.8.5/10.7.5 2nd stage file again

i reported this long time ago.

 

there is no version part that you mentioned Payload Image Info\version. we still need to read ia.log for old macos.

anyways i did think all cases.

 

hmm. seems sf is down. after sf back, i will commit.

thanks apianti and chris1111

[pkdesign]

On 3/31/2018 at 4:06 PM, Moorre said:

@Sherlocks

MP51 is also has an update.

BiosVersion:     MP51.88Z.0085.B00.1802021746
BiosReleaseDate: 18/02/02

 

Does this mean I should change this info in my config.plist to match the above?

[apianti]

10 hours ago, Sherlocks said:

yes. i checked all. 1% issue(startosinstall) was resolved now.

also i checked 10.8.5/10.7.5 2nd stage file again

i reported this long time ago.

 

there is no version part that you mentioned Payload Image Info\version. we still need to read ia.log for old macos.

anyways i did think all cases.

 

hmm. seems sf is down. after sf back, i will commit.

thanks apianti and chris1111

There has to be some file there that holds the version, they would not make it so they would have to determine the version in some crazy way, like by reading a log. But I meant is this a new naming of the file, or was it there before this newest release for startosinstall....? Plus those two versions of macOS don't include ability to use startosinstall... On another note, I'm fairly positive the second method you described doesn't create a viable installer for us because of still using the BaseSystem image not the content inside the image. I seem to recall before createinstallmedia, the BaseSystem/InstallESD method is the actual way to create a hackintosh installer because if you look at your dumps of the folders it has this in com.apple.Boot.plist:

	<key>Kernel Flags</key>
	<string>root-dmg=file:///OS%20X%20Install%20Data/BaseSystem.dmg</string>

Which the BaseSystem.dmg does have the SystemVersion.plist inside as you already said.

[Shaneee]

Issues with AMD CPUs again. I'm still using r4392 as updating to the release on SF or above ends with the X64 Exception Type error we had before. Has the code for AMD changed at all or is it something else. All tests of Clover were booting the same system with only r4392 booting successfully. Slice sorted it before in r4114.

Here's the debug log.

debug.log.zip

[Cyberdevs]

I'm getting double entries in the clover GUI for macOS Sierra USB Installer disk in clover 4423 and 4424, not sure about other version like 4421 or 4422 Haven't tested them.

[Awesome Donkey]

I'm getting a phantom installer entry here with r4424, even after already previously installing 10.13.4. If it helps, I am using only custom entries (no Auto or any tools or anything like that) and I do have a OS X Installer entry there normally, which should only appear when there's actually an update, otherwise it shouldn't appear in the list. Whatever changed in the last couple revisions has made it always appear, even though there shouldn't be an update or anything. In the meantime, I set that OS X Installer custom entry to hidden though that's not really desirable just in case there's actually an update and I need to see the OS X Installer entry. Might be limited to custom entries, not sure, haven't checked other options.

Edited April 4, 2018 by Awesome Donkey

[Cyberdevs]

13 minutes ago, Awesome Donkey said:

I'm getting a phantom installer entry here with r4424, even after already previously installing 10.13.4. If it helps, I am using only custom entries (no Auto or any tools or anything like that) and I do have a OS X Installer entry there normally, which should only appear when there's actually an update, otherwise it shouldn't appear in the list. Whatever changed in the last couple revisions has made it always appear, even though there shouldn't be an update or anything. In the meantime, I set that OS X Installer custom entry to hidden though that's not really desirable just in case there's actually an update and I need to see the OS X Installer entry. Might be limited to custom entries, not sure, haven't checked other options.

I had the same entry and I removed it by mounting the Preboot partition from another macOS (because if you mount the Preboot partition on the same macOS you can't modify it) and deleting the container inside the partition. I don't suggest using this method because it might be useful for future updates (although I did perform successful updates even without it) but yet again if this is related to clover maybe our devs can shed some light on the matter.

[apianti]

Yes, I brought the double entry issue to Sherlocks attention when he made the commit. He added the default macOS loader path to the installer paths array, and there are situations when both get detected now.

[Sherlocks]

23 minutes ago, apianti said:

Yes, I brought the double entry issue to Sherlocks attention when he made the commit. He added the default macOS loader path to the installer paths array, and there are situations when both get detected now.

yes

i missed custom entry part and 10.10+ usb installer part. i checked their usb files tree.

and tested again.

@Cyberdevs @Awesome Donkey

please test and report. 

test.zip

[Cyberdevs]

4 minutes ago, Sherlocks said:

yes

i missed custom entry part and 10.10+ usb installer part. i checked their usb files tree.

and tested again.

@Cyberdevs @Awesome Donkey

please test and report. 

test.zip

It seems to be working Ok, Thanks Sherlocks

[Awesome Donkey]

Yep, working good here too, no more phantom installer!

[Cyberdevs]

Update:

macOS is detected as macOS and OS X is detected as OS X all is working as they supposed to. I tested Yosemite, El Capitan, macOS Sierra and High Sierra

Thanks again

[apianti]

1 hour ago, Cyberdevs said:

Update:

macOS is detected as macOS and OS X is detected as OS X all is working as they supposed to. I tested Yosemite, El Capitan, macOS Sierra and High Sierra

Thanks again

Pre-Sierra versions should say OS X, Sierra and after should say macOS. That is what is happening? And no duplicates?