Customized OpenCore with additional features

[LAbyOne]

59 minutes ago, Andrey1970 said:

@n.d.k

As you declare your BootPicker for official OpenCore, you shall change path for icons that there was no confusion.

EFI/OC/Resources/Image

 

Well as end user I just like the way it is...

this way if i want to use official icons i just select opencanopy and deselect ndkbootpicker, without messing with the files inside OC

so any choice you may make will have its own path.

the suggestion you propose imho will result in unwanted placing/replacing files which (always in my opinion) is unlikely needed by ndkbootpicker users 

 

To be honest I fail to see any benefit from this.

Edited April 22, 2020 by LAbyOne
adding a last comment

[vit9696]

Actually I think I will agree here, while Resources is the expected place for the UI data, it is a good idea to have filenames not intersect for no reason.

[Sherlocks]

hi n.d.k

can you implement this ACPI process in OC?

my laptop has only battery patched DSDT with Additional custom SSDT files in Clover.

 

i'm using this process is in clover

1. Load Battery Patched DSDT(ignore original DSDT)

2. Rename GFX0 to iGPU(for example) in Patched DSDT and original SSDT files.

3. and load Additional custom SSDT files.

 

can i use this process in OC?

 

나의 SM-N960N 의 Tapatalk에서 보냄

 

 

 

 

 

 

[nmano]

Tiny background edit.

You can download PSD files.Change your Details.Finally save to png from Adobe photoshop.

background.psd

background4k.psd

Edited April 24, 2020 by nmano

[btwise]

2 hours ago, nmano said:

Tiny background edit.

You can download PSD files.Change your Details.Finally save to png from Adobe photoshop.

background.psd

background4k.psd

Should be implemented in toolbar button code, not as a background picture!

[nmano]

24 minutes ago, btwise said:

Should be implemented in toolbar button code, not as a background picture!

I like this code

 

 

 

[btwise]

27 minutes ago, nmano said:

I like this code

Did you added this code ?

[nmano]

23 minutes ago, btwise said:

Did you added this code ?

No that's sample code.

Hi @n.d.k

If you have time Can you do background Detail.

Thank You.

Edited April 24, 2020 by nmano

[Matgen84]

19 minutes ago, nmano said:

No that's sample code.

Hi @n.d.k

If you have time Can you do background Detail.

Thank You.

 

What do you think about "Info" button like Clover's theme menu (config, smbios, etc) near shutdown button. But I don't think that @n.d.k have the time to do this, especially if each user requests additions.

[ameenjuz]

@n.d.k 

when i compiled with latest commit changes  and add Bootprotect to config to None then completely disappear my windows partition from boot Menu

this is behavior of bootstrap.efi and bootprotect

m i missing something else?

how to set bootprotect path

[t3chfr3ak]

Does anyone has an idea why my TimeMachine entry looks like this (only on USB on which I test my config, this issue doesn't exist on my name esp):

 

I play around a little with some free to get Icons.

The Only one which is not working, also with Hide Entry in plist, ist this one.

 

In my config I take a look about hide entries and create this one:

 

 

But it's not working.

 

How can I change or hide this entry?

Edited April 25, 2020 by t3chfr3ak

[davidm71]

Ok, 

 

Got NDK fork installed but have questions:

 

1. How to boot an existing Windows installation?

 

2. Does NDKpicker tool replace Opencanopy?

 

Thanks

 

 

Also: Opencore boot menu does show me 'Windows' but when selected it goes straight into 'Automatic Repair' dialogue and then instant blue screen. Perhaps it scanned the wrong partition? 
 

And OpenShell not recognized by NdkPicker.

 

Thanks

 

Edited April 26, 2020 by davidm71

[ken394]

4 hours ago, davidm71 said:

Ok, 

 

Got NDK fork installed but have questions:

 

1. How to boot an existing Windows installation?

 

2. Does NDKpicker tool replace Opencanopy?

 

Thanks

 

 

Also: Opencore boot menu does show me 'Windows' but when selected it goes straight into 'Automatic Repair' dialogue and then instant blue screen. Perhaps it scanned the wrong partition? 
 

And OpenShell not recognized by NdkPicker.

 

Thanks

 

I am not an expert but am booting Windows with OC by adding to my SSDT's so they are dead to windows.

If (_OSI ("Darwin"))
                    {
                        Return (0x0F)
                    }
                    Else
                    {
                        Return (Zero)

I think in NDK config setting EnableForAll to NO in ACPI-Quirks does the same.
NDKpicker replaces Opencanopy

This may or may not be of some use and I am on OC 0.5.8 at the moment, also win and Mac on different drives.

[davidm71]

53 minutes ago, ken394 said:

I am not an expert but am booting Windows with OC by adding to my SSDT's so they are dead to windows.

If (_OSI ("Darwin"))
                    {
                        Return (0x0F)
                    }
                    Else
                    {
                        Return (Zero)

I think in NDK config setting EnableForAll to NO in ACPI-Quirks does the same.
NDKpicker replaces Opencanopy

This may or may not be of some use and I am on OC 0.5.8 at the moment, also win and Mac on different drives.

 

Well I did disable EnableForAll  and set it to false however doesn't work and Windows goes straight into 'Automatic Repair'. Is there way to manually add Windows to a boot entry in config.plist such that NdkPicker or Opencanopy sees it?

 

Thanks

 

BTW: NdkPicker fails to recognize OpenShell for some reason.

[ken394]

44 minutes ago, davidm71 said:

 

Well I did disable EnableForAll  and set it to false however doesn't work and Windows goes straight into 'Automatic Repair'. Is there way to manually add Windows to a boot entry in config.plist such that NdkPicker or Opencanopy sees it?

 

Thanks

 

BTW: NdkPicker fails to recognize OpenShell for some reason.

No info on the Shell issue maybe NDK or someone will chime in on it.

Have you read thru section 12 in the PDF? that is where I started then trial and error followed.

You might be able to use Misc-Entries to set a boot path.

Edited April 27, 2020 by ken394

[davidm71]

2 minutes ago, ken394 said:

No info on the Shell issue maybe NDK or someone will chime in on it.

Have you read thru section 12 in the PDF? that is where I started then trial and error followed.

You might be able to use Misc-Entries to set a boot path.

 

I tried setting a custom boot path straight to the device path to the windows boot partition and it didn't matter if I picked 'BOOTx64.efi' from 'EFI/BOOT' or the other 'BOOTMGFW.efi' in 'EFI/MICROSOFT' the same thing happens. Get a 'Preparing Automatic repair' and Blue screen  error 0x0c000000d. Fwiw had to use opencanopy for the custom boot entry  to show. Not only that changing order of the children of 'TOOLS' in Config.plist entries had an impact on how many entries showed up on NdkBootPicker. All except OpenShell.efi for some reason. Think NdkBootPiker might have a bug. Anyhow think that when Windows tries to load its bootmgr there is an  error in the BCDStore. This is beyond my knowledge to know the solution but will keep on researching it. Thanks.

[ameenjuz]

1 hour ago, davidm71 said:

 

I tried setting a custom boot path straight to the device path to the windows boot partition and it didn't matter if I picked 'BOOTx64.efi' from 'EFI/BOOT' or the other 'BOOTMGFW.efi' in 'EFI/MICROSOFT' the same thing happens. Get a 'Preparing Automatic repair' and Blue screen  error 0x0c000000d. Fwiw had to use opencanopy for the custom boot entry  to show. Not only that changing order of the children of 'TOOLS' in Config.plist entries had an impact on how many entries showed up on NdkBootPicker. All except OpenShell.efi for some reason. Think NdkBootPiker might have a bug. Anyhow think that when Windows tries to load its bootmgr there is an  error in the BCDStore. This is beyond my knowledge to know the solution but will keep on researching it. Thanks.

try this your config

extract your path using uefishell.efi

put into config section Entries

config.plist

[davidm71]

41 minutes ago, anmool said:

try this your config

extract your path using uefishell.efi

put into config section Entries

config.plist

Thanks. About extracting path using uefishell.efi. You mean use openshell.efi and find it via map -r and adjust custom boot entry accordingly? Anyhow looked at the config.plist file. All you did was add the path to Blessedoverride?

Will try again tomorrow,

 

Thanks again.

[Ellybz]

13 hours ago, davidm71 said:

Thanks. About extracting path using uefishell.efi. You mean use openshell.efi and find it via map -r and adjust custom boot entry accordingly? Anyhow looked at the config.plist file. All you did was add the path to Blessedoverride?

Will try again tomorrow,

 

Thanks again.

Here's the method I use for booting windows in OC and it is 100% effective:

If you can boot windows thru Clover:

Select your Windows Icon, press spacebar, you'll get something like this: ( screenshot attached )

 

PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x5,0xFFFF,0x0)\HD(1,GPT,4C15DB92-F532-11E9-AF6E-E172391D34E9,0x800,0xFA000)\EFI\microsoft\Boot\bootmgfw.efii

 

But the custom entry path recognized by OC is actually this one: ( The custom entry path I use in my config.plist )

 

PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x5,0xFFFF,0x0)/HD(1,GPT,4C15DB92-F532-11E9-AF6E-E172391D34E9,0x800,0xFA000)/\EFI\Microsoft\Boot\bootmgfw.efi

( some dashes are reversed & clover efi is written "efii" )

 

Create a new entry with your path in OpenCore/Misc/Entries 

Done.

 

Edited April 27, 2020 by Ellybz

[MacNB]

9 hours ago, ken394 said:

I am not an expert but am booting Windows with OC by adding to my SSDT's so they are dead to windows.

If (_OSI ("Darwin"))
                    {
                        Return (0x0F)
                    }
                    Else
                    {
                        Return (Zero)

I think in NDK config setting EnableForAll to NO in ACPI-Quirks does the same.
NDKpicker replaces Opencanopy

This may or may not be of some use and I am on OC 0.5.8 at the moment, also win and Mac on different drives.

 

would you please share your SSDT's where you added the _OSI checks ?

[newsguytor]

I cannot figure out how to get tools and custom entries to show. I just don't see them at all (I am right clicking).

 

My config.plist is attached.

config.plist

[davidm71]

16 hours ago, ken394 said:

I am not an expert but am booting Windows with OC by adding to my SSDT's so they are dead to windows.

If (_OSI ("Darwin"))
                    {
                        Return (0x0F)
                    }
                    Else
                    {
                        Return (Zero)

I think in NDK config setting EnableForAll to NO in ACPI-Quirks does the same.
NDKpicker replaces Opencanopy

This may or may not be of some use and I am on OC 0.5.8 at the moment, also win and Mac on different drives.

 

Not sure setting 'EnableForAll' to 'false' or 'no' is appropriate because NDK said it should be set to yes or true:

 

Quote

[ Multi-Boot ]

  - ACPI patches and Booter Quirks are optional for non macOS with setting ACPI->Quirks->EnableForAll / Booter->Quirks->EnableForAll to yes (default is no).

 

Furthermore I was able to finally boot into Windows 10 but it wasn't even in the NDK fork! I made a couple changes adding the Microsoft boot loader path to 'BlessOverride' and here's the real important part which I am not sure is responsible but I think the character case, wether upper case or lower case, of the microsoft path was important! Because last night it didn't work with BlessOverride but maybe I did it wrong I don't know. Anyhow thanks to @Ellybz idea to boot Clover and press spacebar I noticed the path to bootmgfw.efi was '\EFI\microsoft\Boot\bootmgfw.efi' with a lowercase 'M'! Not sure if it mattered.

 

Also thanks to @anmool for helping with editing the config.plist. I didn't use it but took from it the 'BlessOverride' section and 'SyncRuntimeServices=true'. I studied the file in detail and can now with same changes adding in 'EnableForAll=true' can boot from the NDK fork as well but still have one problem in that OpenShell fails to get listed with either NdkBootPicker or OpenCanopy. Heres my relevant part of my plist. Opencore main branch 5.8 has no issues with this:

 

Quote

<key>Tools</key>
        <array>
            <dict>
                <key>Comment</key>
                <string>CleanNvram.efi</string>
                <key>Name</key>
                <string>CleanNvram.efi</string>
                <key>Enabled</key>
                <true/>
                <key>Arguments</key>
                <string></string>
                <key>Path</key>
                <string>CleanNvram.efi</string>
                <key>Auxiliary</key>
                <false/>
            </dict>
            <dict>
                <key>Comment</key>
                <string>OpenShell.efi</string>
                <key>Name</key>
                <string>OpenShell.efi</string>
                <key>Enabled</key>
                <true/>
                <key>Arguments</key>
                <string></string>
                <key>Path</key>
                <string>OpenShell.efi</string>
                <key>Auxiliary</key>
                <false/>
            </dict>
        </array>

 

I went as far as comparing the EFI folder I made directly with files copied from NDK_Opencore Xcode compiled project and as well as just replacing bootx64.efi and opencore.efi into the working main fork efi folder. Also copied the 'Bootstrap' folder or files over. Not sure if they are needed but point is don't see openshell for some reason. Maybe I have to create a direct boot entry for it..

 

Anyhow wow what a ride and learning experience this has been!

 

Thank you all for your help.

 

 

 

Edited April 27, 2020 by davidm71

[ken394]

9 hours ago, MacNB said:

 

would you please share your SSDT's where you added the _OSI checks ?

 

9 hours ago, MacNB said:

 

would you please share your SSDT's where you added the _OSI checks ?

They are already in SSDT's if you are using the ones provided in Opencore, in my comment above  related to 2 I had that did not have the check and was having trouble

with windows till  I came across the If (_OSI ("Darwin")) in one of the PDF Instructions.

Edited April 27, 2020 by ken394

[MacNB]

59 minutes ago, ken394 said:

 

They are already in SSDT's if you are using the ones provided in Opencore, in my comment above  related to 2 I had that did not have the check and was having trouble

with windows till  I came across the If (_OSI ("Darwin")) in one of the PDF Instructions.

 

Thx. Yes I know there some SSDT's provided with OC and know the PDF very well.

I was asking if you would share what modifications you made to your SSDT's to be able to boot Windows. 

[davidm71]

@n.d.k

 

I think theres a bug with latest fork release. I checked the spelling and case of 'OpenShell.efi' and have it registered in the plist file such that the main branch has no issues displaying it on the boot gui menu. And its where its suppose to be in the Tools folder. So wonder why it works with main branch and not with the fork?

 

Thanks