[Offer] Mod Chatreey AN1 AMD Ryzen 3550H Mini-PC BIOS

[Vic_Banner]

EDIT: Read the entire discussion before downloading and flashing.
_{Discussion was before in [BIOS Modding Requests]}

I can’t update the Cpu Microcodes within UBU, since I have not the options with that AMD bios.
But can I insert directly in an Hex Editor replacing the old ones with the new one since it’s exactly the same size and occupy the same space in the Hex Editor and will that not work?

Cpu Microcodes cpu00810F80 cpu00810F81cpu00820F01 Old and New.zip (New from 2024)

OFFERED: AN1_3550H_3750H_1AVSZ024_modded.zip (all other updates available in UBU applied and it works. vv See below vv. Done from Bios downloaded from the Chatreey AN1 support page on their website marqued “3550H/3750H version”. It is dated 2022)
works for Mini PC → T-Bao MN35, Chatreey AN1 and Minisforum DMAF5.

But you should check with AFUWINGUI.exe that is given in the zip package that your computer is an increment of “Firmware ID” like 1AVSZ017 to 1AVSZ024 and the same “Firmware GUID”, because Pc dealers do different ones with the same names with what I saw different Cpu or Gpu or other components but need different Bios. (AN1 exist with 2700U, with 3550U Vega 9, not the same bios)

As an example, before I even flashed the Bios of a similar mini pc the Minisforum UM350, same “Firmware ID” (1AVSZ024), same “Firmware GUID”, same Motherboard.(that was before I found that Bios file for the AN1)
System started, but no Wifi because that model have dual Wifi. So caution.

Before I was using the AF5PN01_mod Firmware ID 1AVSZ017 (found in this forum).
It was based on the Minisforum Bios for the DMAF5 from 2021 that added support for TPM and secure boot.

(First I had AR357V3P01.rom 1AVSZ011 on my T-Bao MN35, it didn’t have secure boot and TPM)

What’s already done, before and after:

From Matt85R22

run AFUWINGUIx64.EXE open the .rom and then from the setup tab select “program all blocks” and then press the Flash button , then press ok at the prompt to continue (it is vital to keep powered the pc until flash is done and you see all green blocks , with few grey blocks that remained untouched , it is normal )

after that shutdown the pc clear cmos (via jumper or software using load defaults from bios setup) and you’re done tpm should be recognized straight away (however you must have uefi & secure boot in bios to be w11 compatible, but that’s another story, very simple to do that if you can reinstall the system from scratch )

You need to disable “CSM support” and enable Secure Boot in Bios to have TPM after flashing, because default setting is CSM.
By default Boot is set to “DUAL” (legacy and UEFI, ot to be confounded with dual-boot). If all your systems installed (Linux and Windows are UEFI installed, you can switch to UEFI.

You might wanna change the values of the fan to ones that make more sense:

If it’s too risky for patching the microcodes in the bios file:

For Linux, the solution I found for Fedora (or CentOs), you can install “Real-Ucode” from divestedcg on github that provide the last Microcodes for the system faster than those included in the distribution right now, worked for me for the moment.
I saw while doing research that there is a method for Ubuntu.

For Windows the system Microcode patch mcupdate_AuthenticAMD.dll is 2022 old so does not include the latest Microcodes…


Edit by Fernando: Thread title shortened

[MeatWar]

A NUC?
Probably yes… same size so offset should stay the same, with AGESA its always a mystery.
You should test first a mod with mcodes only and then the rest of UBU updated components…If it fails you know that the second mod was the cause.

EDIT: So don’t risk it, if you don’t know how or have the means to recover.

[Vic_Banner]

MeatWar You should test first a mod with mcodes only and then the rest of UBU updated components…If it fails you know that the second mod was the cause.

Hello. Thanks.

First One works.
Second One I have prepared, it opens in UBU and shows updated Cpu Microcodes, but I hesitate to apply it because as you say there may be dependencies.
I don’t want to do a brick.

[Vic_Banner]

@MeatWar

So don’t risk it, if you don’t know how or have the means to recover.

For what I saw, basic rescue means Cmos resetting via removing battery inside.

Or most likely advanced rescue that imply an electronic tool that I don’t have and don’t want to bother with

So as you say, caution is the best here for me.

Best it will provide my mod for others that want it.

[Fernando]

@Vic_Banner
Thanks for your work and the offer of your modded BIOS.
Since your chosen thread title was too long, I have tried to shorten it. If you should know a better solution (a title should be as short as possible, but meaningful), feel free to change it again by editing the first post.

[Vic_Banner]

@Fernando
Ok thanks
Even in my post, I’m covering too much