@ptran3014 - Same size is not the issue possibly, it may need to be exact format too (bit depth, mod, resolution etc, sometimes same exact program needs to be used too) I think main issue probably was UBU breaking this BIOS, or change logo also breaking BIOS etc.
I'd have to compare your mod BIOS with stock BIOS to be sure, but what I just noticed happened to file I sent you initially above, I bet same happens with 1.74 UBU too. Padding/Non-UEFI file is removed on volume rebuild and FIT table is then missing/broke
Here is fixed security removed BIOS, please confirm it flashes OK and boots to BIOS OK
http://s000.tinyupload.com/index.php?fil...906522630092711

If you have already make 12KB JPEG Logo, send to me

* Edit - @ptran3014 - Here, please test, logo replaced x2 (one had Chinese characters, I assume if Chinese language selected)
UEFITool 25 used to replace logo's @ GUID 7BB28B99-61BB-11D5-9A5D-0090273FC14D (RAW Section 1 + 3 = Logo Images)
http://s000.tinyupload.com/index.php?fil...501819324851048

If that fails, then I will redo images with CS3 instead of Paint.Net (original was 3.5.10, I used 4.2.1)

Your file is working fine, boots to BIOS. This file is the same as I did as per your instruction: I used UBU_v1.74.0.3 to remove the Instant Flash Protection from the original BIOS, it boots to BIOS.
I don't have my own 12KB JPEG logo. By the way, I used Changelogo program to extract the original Asrock logo, then I used Changelogo to replace the stock logo with the extracted Asrock logo, same size same thing. However i still does not work. I think Changelogo causes the problem.

See my edit above, BIOS posted w/ Logo swapped In regards to what you mentioned with changelogo and extract/replace stock, then changelogo is breaking the BIOS. Yes, I checked, same issue as I mentioned on previous page, Non-UEFI Pad file is removed on rebuild, breaking FIT Table
I'm going to split this into your own topic, since this is not UBU issue in general, or maybe we should leave, since I am still unsure if Asrock Protection has been removed from latest UBU's
I'll wait until SoniX replies about that, before I decide to split/move this into it's own topic (These comments are for Fernando mainly, so you are aware I'm already planning to split/move if SoniX says Always present, has not changed etc, except for the known limitation on some BIOS series)

It works, I see my logo on the screen. How did you do it? Manually?

@ptran3014 - Yes, manually I saved image with paint.net as JPEG 4:2:0 and made sure it was under original size (in KB) in case larger would cause issue.
Then replaced images @ GUID 7BB28B99-61BB-11D5-9A5D-0090273FC14D (RAW Sections 1 + 3 = Logo Images >> replace body w/ image) via UEFITool 25.0

Zitat von Lost_N_BIOS im Beitrag #1283

---

@SoniX - Can you confirm about that, I know some models/chipsets this does not work anymore, but is there some versions you have removed this entirely from, or just some may not show it at visual output in the CMD window?

---

@Ludolf
Thanks, I tried (W10 x64) but did not worked nor with Python v3.8 nor with v3.9b version.
I tried also default settings (users) for the Python emplacement on system disk and also the personalised emplacement such as C:\program.
No success. UBU does not detect Python.

@SoniX - "AMI Change Logo, then this utility has not been working on new platforms for a long time". I agree with you, however I found this:
I have some new Gigabyte B450 AORUS PRO WIFI motherboards. I use @BIOS program to change the logo. The software extracts two files: ChangeLogo32.exe and ChangeLogo64.exe. I copy those files to use for normal logo replacement with Asrock and MSI. I don't understand why it works with Gigabyte BIOS, MSI BIOS (new motherboards) but not with this Asrock BIOS.

@SoniX - Sorry if my question was not clear, it was about Asrock protection removal and UBU. I know it does not work for some chipsets, not part of my question.
My question is >> Is there some newer versions of UBU, not all, maybe some, that Asrock protection removal function was removed or left out of?
I am not 100% sure, but I think sometimes, I had to go back and use old version because new one did nothing, not show message or remove/edit anything, but older one did.
I cannot remember specific cases, UBU versions, or BIOS. So, I was just asking in general, did sometimes, you accidentally or on purpose remove this function from UBU at any version of the newer 1.7-current UBU's
I do notice it does not always give user message when removing, like it used to, this applies even when I know it's being removed. I can always remove manually, I only ask this info in case others have issue.

@ptran3014 - ALL BIOS are different, and editing BIOS is tricky task sometimes, some tools break BIOS for simple reasons, other tools break BIOS for difficult reasons, even doing same things.
So it's hard to know why one tool works for one BIOS yet not another, easier than trying to figure out is to do the edit in question differently with another tool or manually etc

@ptran3014

AMI Change Logo can work if the original version of the image storage is saved.
AMI provides manufacturers with a source code template. The manufacturer can make its own changes and, accordingly, its software.
Moreover, no one knows what is the most recent version of this AMI Logo.
BIOS contents change, and the utility is old. This is like a BCP.

@Lost_N_BIOS

Previously, the UBU removed the ASrok protection capsule by default, on the machine.
On the latest chipsets this makes no sense. Therefore, now the removal is done by choice.

@SoniX - Thanks, I had not noticed this change, and Fernando just mentioned to me in PM too.
This explains why I didn't see auto removal after running a BIOS through without making any changes sometimes, I will keep my eye out for it now, thanks

@Lost_N_BIOS

Every year, with the release of new platforms, everything changes. Just have time to follow and make changes, and mention already quickly. Ж))

Asroсk was interested.
1) No security flash
2) Capsule Header as Asus (Cut and Ok)
3) Capsule Header + Internal Capsule (Cut and Ok)
4) Internal Capsule (Replfce and Ok)
Latest BIOSes have already changed the firmware utility itself (Instant Flash).

In my opinion, while the MSI is holding on and does not introduce protection from modds.

@SoniX - Yes, they need to quit!! They (Asus, Asrock) should leave this kind of security up to user to configure if they want BIOS security, and leave all unlocked like Gigabyte and MSI

Hi all
@SoniX
Latest UBU_v1_79_4 works well with latest MSI X570 TOMAHAWK UEFI, UBU_v1_79_3 did recognized STRIX X570-E Gaming 2203 UEFI as Aptio V, unfortunately my STRIX are in a RMA process, It is on a endless loop about updating Led Firmware flash, always had LED problems since day one.
About changelogo, bcp and mmtool they do not work on new MSI UEFIs, however @ptran3014 I could change the boot logo of MSI 115 UEFI by replacing the 2 logos detected by ChangeLogo 5.0.0.2.