I would like to update my laptop bios. Actually, arrandale microcodes are not listed on UBU. It is possible to support it in the future ?



Thanks for all your work !

@BrN - only microcodes you see are in your BIOS.

Zitat von BrN im Beitrag #4681

---

I would like to update my laptop bios. Actually, arrandale microcodes are not listed on UBU. It is possible to support it in the future ?



Thanks for all your work !

---

There is a problem with "cecho.exe". )-; It happens to be the only x86_64 .exe file.

Vacuum:UBU_v1.70.rc18.5 nms$ file $(find . -name \*.exe | sort)
./Files/Workfiles/GenFfs.exe: PE32 executable (console) Intel 80386, for MS Windows
./Files/Workfiles/GenSec.exe: PE32 executable (console) Intel 80386, for MS Windows
./MCE.exe: PE32 executable (console) Intel 80386, for MS Windows
./SetDevID.exe: PE32 executable (console) Intel 80386, for MS Windows
./UEFIExtract.exe: PE32 executable (console) Intel 80386 (stripped to external PDB), for MS Windows
./UEFIFind.exe: PE32 executable (console) Intel 80386 (stripped to external PDB), for MS Windows
./UEFIReplace.exe: PE32 executable (console) Intel 80386 (stripped to external PDB), for MS Windows
./UEFITool.exe: PE32 executable (GUI) Intel 80386 (stripped to external PDB), for MS Windows
./UEFITool_NE.exe: PE32 executable (GUI) Intel 80386 (stripped to external PDB), for MS Windows
./VBIOS2Pad.exe: PE32 executable (console) Intel 80386, for MS Windows
./cecho.exe: PE32+ executable (console) x86-64, for MS Windows
./drvver.exe: PE32 executable (console) Intel 80386, for MS Windows
./findhex.exe: PE32 executable (console) Intel 80386, for MS Windows
./findver.exe: PE32 executable (console) Intel 80386, for MS Windows
./ifrextract.exe: PE32 executable (console) Intel 80386, for MS Windows
./mCodeFIT.exe: PE32 executable (console) Intel 80386, for MS Windows
Vacuum:UBU_v1.70.rc18.5 nms$

@nms

Strange. It seems to have always been x32. Perhaps mistakenly replaced.
Archived x32 (PE32).

Hello @Fernando. :)

In general, all information about the BIOS version, manufacturer and motherboard is usually located in GUID AB56DC60-0057-11DA-A8DB-000102EEE626 (FreeForm section).
And usually almost all manufacturers follow this rule.
At ASRock probably their opinion where to store the BIOS version. Therefore, we see such a result.

I initially tried to display the version, but then refused the idea. Since it is impossible to predict where the real version of BIOS will be located.

So now I will make the rc20 as the rc20.1, with an ASRok check. If there are problems on other BIOS files, then this function will be under 'REM'.

Zitat von Fernando im Beitrag #4684

---

By the way: When can we expect the UBU tool v1.71?

---

@SoniX - any negative reports on Asrock J4105B (BIOS in question here)?
Asking because I used UBU_v1_70_rc12_3 to remove Asrock Protection only, and then moved 4 bytes to unsuppress something and seems to have bricked users board.
I know it could just simply be a bad flash too, but wanted to ask if you've have any negative reports on this model, or if you could check it's BIOS and see if the area UBU FF's is indeed the protection module on this board or not.
Since it's not mainstream model I thought maybe it could be different and wrong thing got FF's (I know it's probably not likely)

@Lost_N_BIOS
Typical BIOS, there is nothing like that.

Try a minimum:
- Restore BIOS.
- UBU -> Removed ASRock Protect (only) -> Flash
If everything works, continue modifying.
If it doesn't work, let me know.

Thanks @SoniX - we found later, the file he downloaded I modified did not have same MD5 checksum, he used VPN to download so I think something happened to the package mid-stream
I will let you know once he recovers if all is OK, thanks again!

I've found a bug with latest UBU:



I was trying to update microcodes in this BIOS: https://dlcdnets.asus.com/pub/ASUS/nb/G53SX/G53SXAS209.zip

@mooms

Use MMTool v5.0.0.7


Added:
Line 1335

if %mmtool%==0 if %aa% neq 0 cecho {0E}Recommended. It is recommended to use MMTool.{#}{/n}
 

Correct:
{/n} -> {\n}

@SoniX

I have MMTool v5.2.0.24 in the UBU folder.
Can we have MMTool v5.0.0.7 and v5.2.0.24 at the same time (maybe with renaming one of the two) ?