Clover Suite Builder

[LAbyOne]

New Update v.1.3r8

to reflect latest changes to Clover

[Slice]

I have one more query.

Compilation produced file OpenRuntime.efi but in the installation result we will see OpenRuntime-v12.efi.

Where to insert such renaming?

[LAbyOne]

20 hours ago, Slice said:

I have one more query.

Compilation produced file OpenRuntime.efi but in the installation result we will see OpenRuntime-v12.efi.

Where to insert such renaming?

oh did'n even notice...

anyway the only place where its mentioned is

rEFIt_UEFI/refit/main.cpp

    if ( LStringW(DirEntry->FileName).containsIC("OpenRuntime") ) {
      if ( LStringW(DirEntry->FileName).isEqualIC("OpenRuntime-v12.efi") && LString8(OPEN_CORE_VERSION).isEqual("0.7.5") ) {
        OpenRuntimeEfiName.takeValueFrom(DirEntry->FileName);
      }else
      if ( LStringW(DirEntry->FileName).isEqualIC("OpenRuntime-v12.efi") && LString8(OPEN_CORE_VERSION).isEqual("0.7.3") ) {
        OpenRuntimeEfiName.takeValueFrom(DirEntry->FileName);
      }else
        ..............

 

Edited November 2, 2021 by LAbyOne

[Slice]

37 minutes ago, LAbyOne said:

oh did'n even notice...

anyway the only place where its mentioned is

rEFIt_UEFI/refit/main.cpp

    if ( LStringW(DirEntry->FileName).containsIC("OpenRuntime") ) {
      if ( LStringW(DirEntry->FileName).isEqualIC("OpenRuntime-v12.efi") && LString8(OPEN_CORE_VERSION).isEqual("0.7.5") ) {
        OpenRuntimeEfiName.takeValueFrom(DirEntry->FileName);
      }else
      if ( LStringW(DirEntry->FileName).isEqualIC("OpenRuntime-v12.efi") && LString8(OPEN_CORE_VERSION).isEqual("0.7.3") ) {
        OpenRuntimeEfiName.takeValueFrom(DirEntry->FileName);
      }else
        ..............

 

I mean the package

If I click Install I want to see .../drivers/UEFI/Openruntime-v12.efi

Somewhere in the package it should be copied.

[LAbyOne]

1 hour ago, Slice said:

I mean the package

If I click Install I want to see .../drivers/UEFI/Openruntime-v12.efi

Somewhere in the package it should be copied.

 

Ok i see now...

Please clarify one thing

this is some cosmetic for packaging or the driver has to named this way?

because if the driver has to be named as Openruntime-v12.efi

well the way its done now, we could just do this:

ebuild.sh

    # drivers64UEFI/MemoryFix
    binArray=( OpenRuntime )

    for efi in "${binArray[@]}"
    do
      copyBin "$BUILD_DIR_ARCH"/$efi.efi "$CLOVER_PKG_DIR"/EFI/CLOVER/drivers/$DRIVERS_OFF/$DRIVERS_UEFI/MemoryFix/$efi.efi
    done

replace

    # drivers64UEFI/MemoryFix
    binArray=( OpenRuntime )

    for efi in "${binArray[@]}"
    do
      copyBin "$BUILD_DIR_ARCH"/$efi.efi "$CLOVER_PKG_DIR"/EFI/CLOVER/drivers/$DRIVERS_OFF/$DRIVERS_UEFI/MemoryFix/$efi-v12.efi
    done

 

is it this ?

 

Otherwise if its just having the driver shown as Openruntime-v12.efi

well it become another story

Edited November 2, 2021 by LAbyOne

[LAbyOne]

On 11/1/2021 at 12:29 PM, LAbyOne said:

New Update v.1.3r8

to reflect latest changes to Clover

 

Re-uploaded v1.3r8,

as i indeed added the new changes for Release, just forgot to implement the build as it was suppased to be.

having done those changes into buildme, was convinced to have made the same into CSB... well.

 

Edited November 8, 2021 by LAbyOne

[Slice]

1 hour ago, LAbyOne said:

 

Ok i see now...

Please clarify one thing

this is some cosmetic for packaging or the driver has to named this way?

because if the driver has to be named as Openruntime-v12.efi

well the way its done now, we could just do this:

ebuild.sh

    # drivers64UEFI/MemoryFix
    binArray=( OpenRuntime )

    for efi in "${binArray[@]}"
    do
      copyBin "$BUILD_DIR_ARCH"/$efi.efi "$CLOVER_PKG_DIR"/EFI/CLOVER/drivers/$DRIVERS_OFF/$DRIVERS_UEFI/MemoryFix/$efi.efi
    done

replace

    # drivers64UEFI/MemoryFix
    binArray=( OpenRuntime )

    for efi in "${binArray[@]}"
    do
      copyBin "$BUILD_DIR_ARCH"/$efi.efi "$CLOVER_PKG_DIR"/EFI/CLOVER/drivers/$DRIVERS_OFF/$DRIVERS_UEFI/MemoryFix/$efi-v12.efi
    done

 

is it this ?

 

Otherwise if its just having the driver shown as Openruntime-v12.efi

well it become another story

Is it possible to do this after Install not before?

[LAbyOne]

30 minutes ago, Slice said:

Is it possible to do this after Install not before?

 

Sorry i'm not really following...

what do you mean "after install not before"

 

[Slice]

21 hours ago, LAbyOne said:

 

Sorry i'm not really following...

what do you mean "after install not before"

 

I mean postinstall script that worked inside the package when we clicked "Install".

Because I have a thought to send the driver into /EFI/CLOVER/drivers/5142/OpenRuntime-v12.efi

And yes "-v12" is essential here.

[LAbyOne]

Application Updated v.1.3r9

 

modified/added a few menus

to reflect latest changes made to Clover

 

you can get it as always from main

Edited November 9, 2021 by LAbyOne

[LAbyOne]

Hi all,

waited a bit to post this, as I was a little busy in other matters.

v.1.4 was skipped (as you may know many web legends lead to think many devs skip their builds number out of superstition, not my case but gave it a try)

 

Since I made another version of this tool, which will have a total different approach,

with more options for the user to choose the best way for him to use this tool.

So I was and am hesitant about posting this or the new one directly.

it will make no sense in having 2 tools doing almost the same work,

well while I decide how to proceed.. here's

New Update 1.5

this will most likely be the last update of this tool.

Modified build menu, removed Build with HFS+

in favor of Clover_V2

 

added also for those who prefer their build made with XCode, the release version of such

 

 

Major changes around Utilities,

now the most (in my opinion) useful of them

are directly available into Clover Suite..  so for these no more need to download...

 

system info

 

plist validator

 

macserial *this one probably needs some updated info... hope to hear from you

 

IOReg generator

 

CSRActiveConfig Generator

 

BooterConfig Generator

 

Enroll Apple Seeds

 

USB Boot Drive builder

 

and also the possibility to generate the boot log when needed

Edited March 13, 2022 by LAbyOne

[LAbyOne]

Just made an Updater for Create USB Install media

as per latest Apple seeds to Monterey 12.3 and Big Sur 11.6.5

 

You do not need to re-download the application, only this small file

and follow instructions.

 

updater Download

Edited March 14, 2022 by LAbyOne

[LAbyOne]

New Release, up to 1.6

 

Updated tools

 

1) Create install media updated to new 12.3.1 Monterey

 

2) Added SIP Status

This will give you infos about your CsrActiveConfig settings, and integrity Protection status

 

Download (Updater only, you need the main app already installed)

Clover Suite Builder upd.7z

 

 

Edited April 3, 2022 by LAbyOne
added explanation, to avoid confusion.

[Matgen84]

Hi @LAbyOne

 

Troubleshooting here : 1.6 app version seems to be not compatible on Catalina system. Or I made a mistake 

 

Spoiler

 

Edited April 3, 2022 by Matgen84

[LAbyOne]

48 minutes ago, Matgen84 said:

Hi @LAbyOne

 

Troubleshooting here : 1.6 app version seems to be not compatible on Catalina system. Or I made a mistake 

 

  Hide contents

 

I don't think so...

You Only should have that message if the app is not found into Applications folder..

is your copy into Applications?

 

i just booted into Cata and all was fine..

 

P.S.

if you are still experiencing problems updating, let me know

Edited April 3, 2022 by LAbyOne
pies'd

[Matgen84]

42 minutes ago, LAbyOne said:

I don't think so...

You Only should have that message if the app is not found into Applications folder..

is your copy into Applications?

 

i just booted into Cata and all was fine..

 

P.S.

if you are still experiencing problems updating, let me know

 

Thanks. I don't have previous version into Applications folder. It's a first install, not an update 🙂

 

Of course, issue is the same if I launch the pkg from desktop or from applications folder.  

[LAbyOne]

18 minutes ago, Matgen84 said:

 

Thanks. I don't have previous version into Applications folder. It's a first install, not an update 🙂

 

Of course, issue is the same if I launch the pkg from desktop or from applications folder.  

Naturellement, Je vois,

alors ce qu'il faut faire c'est d'abord télécharger la 1.5 et la placer dans Applications

après tu peux utiliser la mis à jour

[Matgen84]

4 minutes ago, LAbyOne said:

Naturellement, Je vois,

alors ce qu'il faut faire c'est d'abord télécharger la 1.5 et la placer dans Applications

après tu peux utiliser la mis à jour

 

Ok. It's less convenient
If I understand well: 1.6 version is an update not a standalone app. Is it possible that future updates will install without needing the previous version in the Applications folder. Or that they will be installed on top like native Mac applications.

[LAbyOne]

8 minutes ago, Matgen84 said:

 

Ok. It's less convenient
If I understand well: 1.6 version is an update not a standalone app. Is it possible that future updates will install without needing the previous version in the Applications folder. Or that they will be installed on top like native Mac applications.

 

I guess for the time being, if minor updates will come up, this is the way, i will manage them.

[Matgen84]

10 minutes ago, LAbyOne said:

 

I guess for the time being, if minor updates will come up, this is the way, i will manage them.

 

OK. When you publish a minor update, you should then specify which major version must be previously installed in the Applications folder.

[LAbyOne]

21 minutes ago, Matgen84 said:

 

OK. When you publish a minor update, you should then specify which major version must be previously installed in the Applications folder.

the Major versions are always the ones published here, and present in main thread download.

so following updates are related to that.

I'm not in measure to know if someone has or not skipped a release, that's up to the users to verify.

 

[LockDown]

just upload the full app on each update to make things simplier imo

[LAbyOne]

Update v.1.7

 

This Update will:

- Update Enroll, IOReg-Devices, CsrUtil, MacSerials modules (corrected typos)

- Update ConfigPlistValidator module (enhanced menu options)

- Update:

  re-wrote and enhanced makeusb module,

 

  re-wrote warnings

 

 

  and added Downloader.
  Now it will seek for newest seeds (betas included)

  and can get all previous OS since 10.7 (as per Apple generosity)

 

------------------==========   NEW   ==========------------------
- Added Value Converters to Utilities

  a few values converters to fill config.plit values when needed.

 

Clover Suite Builder 1.7 upd.pkg.zip

can be found in main thread

Edited April 30, 2022 by LAbyOne

[LAbyOne]

Clover Suite Builder Update v.1.8

the file on main thread

Clover Suite Builder upd 1.8b.7z

updates from 1.5 or later to 1.8

 

This Update will:

- Update main script

 

- Update Enroll,

Now when selecting, it will also visualize via software update preferences the available seeds

 

- Update: makeusb module

 

Now check your machine SMBIOS and also latest supported OS for it (officially ofc..)

modified USB creation your device will be now formatted GPT/JHFS+ before proceeding

(before it only rewrote the partition)

and of course added Ventura to Downloader

 

- Update: Value Convertes module

 

 

Edited October 25, 2022 by LAbyOne
mistype

[Slice]

You wrote "Ventura 22A38" while it is 380. Zero missing.