HackBGRT
HackBGRT copied to clipboard
Metabolix
What about using for a preinstallation kit or installation image/disc?
Just curious if this process works with a preinstallation kit or installation image rather than the actively installed operating system. If so, I could use a little assistance. I'd like to find a way that doesn't involve enabling test mode, and I've seen bits and pieces of how this could be done on the internet... Feel free to comment, here, or if you'd like to send me some mail, my email is [email protected]
I am exceptionally interested in this project, I just think that the method needs a more proactive approach, like changing the bootres.dll file on the installation or wim files themselves.
Changing resources in the bootres.dll file will not affect the splash of a computer with a BGRT. If it did, this project wouldn't really have existed.
Would this help? https://chocolatey.org/packages/fwup
I know it says it's linux based, but is that not what [U]EFI is based on?
https://chocolatey.org/packages/dfu-util - This one was hasn't been in active development for a few years... wonder why?
--- I had to edit my prior comment.... Had the breakthrough I've been waiting for. I won't lie, I'm not real happy with MS lately, but I'm sure it goes both ways.
Let's start with the basics: EFI has nothing to do with Linux. HackBGRT resides in the EFI boot partition, not firmware.
Preinstalling HackBGRT with any custom logo is trivial. HackBGRT is as simple as copying files in place. If you plan to preinstall it, it's better to create a new boot entry for it (pointing directly to \EFI\HackBGRT\bootx64.efi) instead of the current (1.5.1) method of overwriting Windows boot loader. That's actually on the todo list anyway - easy to do by hand with proper tools but not so easy to reimplement from scratch.
To support Secure Boot, you need to sign the EFI executable. There's many tutorials in the wild on how to do that. It requires either a paid signing key or tampering with the Secure Boot firmware settings to add your personal key/certificate there. If you're a computer manufacturer or some such, this should not be a problem.
What you actually need to do depends on what exactly is your goal. Creating a Linux-based image which copies HackBGRT files and creates a boot entry would be trivial.
This is a bit older now, but the reason I was looking to modify boot images/graphics was because I had a reason to suspect that manufacturers and/or 3rd party vendors may or may not have been distributing devices with signed firmware that contains exploits.
I've since moved on from this idea, but it would be pretty cool to revisit.
On Sun, Mar 1, 2020 at 11:08 AM Lauri Kenttä [email protected] wrote:
Let's start with the basics: EFI has nothing to do with Linux. HackBGRT resides in the EFI boot partition, not firmware.
Preinstalling HackBGRT with any custom logo is trivial. HackBGRT is as simple as copying files in place. If you plan to preinstall it, it's better to create a new boot entry for it (pointing directly to \EFI\HackBGRT\bootx64.efi) instead of the current (1.5.1) method of overwriting Windows boot loader. That's actually on the todo list anyway - easy to do by hand with proper tools but not so easy to reimplement from scratch.
To support Secure Boot, you need to sign the EFI executable. There's many tutorials in the wild on how to do that. It requires either a paid signing key or tampering with the Secure Boot firmware settings to add your personal key/certificate there. If you're a computer manufacturer or some such, this should not be a problem.
What you actually need to do depends on what exactly is your goal. Creating a Linux-based image which copies HackBGRT files and creates a boot entry would be trivial.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Metabolix/HackBGRT/issues/36?email_source=notifications&email_token=AKWFP2YRBMU6QLMP6X3X2VTRFKB6HA5CNFSM4G4G4MNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENNDFYY#issuecomment-593113827, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKWFP25EGDCVLUIMJZNTEV3RFKB6HANCNFSM4G4G4MNA .
I don't fully understand your question. Where would you be installing HackBGRT? Is there some feature which would be needed at HackBGRT level or is it more about packaging the files and/or scripting the installation? Please reopen if you have some clearly defined use case which can't be implemented with the current tools.