@100PIER Thanks for taking the time to test. Recent results are correct.
I’ll try to explain. Folder TMPR is not constant as TMP. It is created when the file is extracted and then deleted. If the TMPR folder is not deleted, then UEFIExtract will not be able to extract a single file in this folder.
If you look at the script carefully, you will see how it works. An example of parts of the script.
1 2 3 4 5 6 7 8 9 10 11
..... set ren=move tmpr\body.bin set renf=move tmpr\file.ffs set rdir=if exist tmpr rd /s /q tmpr ...... :rtk ...... %ur% %%a 10 %fefi% -o bios.bin && %ue% %%a -o tmpr -m body -t 10>nul && %ren% tmp\lanr_%%a>nul ) %rdir% .....
%ur% (UEFIReplace) replaces file %ue% (UEFIExtract) extracts the updated file from BIOS to the TMPR folder %ren% move the extracted file to the folder TMP %rdir% delete the TMPR folder BUT, if for some reason the TMPR folder exists at the time of the file replacement, then the extraction of the new file does not take place.
I made some changes with the TMPR folder in the script and uploaded version rc14.1. I think that such incidents will no longer occur
Hi guys. I’m trying to update msi z97-g43 latest bios to new roms and get some errors. this happens when I try to update gop, realtek lan and cpu code with “u” choice, while m option works well. Is it normal? coz I don’t think so… After I flashed modded bios with these errors, everything works, but realtek lan has stability issues and sometimes force me to on/off it to find the internet connection. Update: There was a problem with my router not realtek orom. so… modded bios works fine.
@Sonix, I understand now the TMP and TMPR folders respective rôles. Many thanks again for the time to follow the reported problem. This minor incident is now fixed, and you offer us one outstanding top quality UBU Tool.
@xBurn These messages are not critical, just some FFS are not quite compiled by the standard. But it is critical that this BIOS contains the BootGuard. You can see if you open this file in UEFIool NE. I can not say that it affects the work of LAN Realtek.
Traceback (most recent call last): File “MCE.py”, line 1265, in <module> File “site-packages\colorama\ansitowin32.py”, line 40, in write File “site-packages\colorama\ansitowin32.py”, line 141, in write File “site-packages\colorama\ansitowin32.py”, line 166, in write_and_convert File “site-packages\colorama\ansitowin32.py”, line 174, in write_plain_text File “c:\python\python36-32\lib\encodings\cp850.py”, line 19, in encode UnicodeEncodeError: ‘charmap’ codec can’t encode character ‘\u255f’ in position 43: character maps to <undefined> Press enter to exit
I use MC Extractor v1.24.0 r85 from UBU_v1_70_rc14_1_fix.
The line “File "c:\python\python36-32…” makes me confused. The program language Python uses the .py extension. But how does it get involved when extracting microcodes???
The error shows up after the display when you have to choose what to do and select “X” <enter>.
(I wish I knew how to insert a picture here so you could see…)
I also have learned that MCExtractor is a python project so that explains why there are python references in the error message
I turned echo on and the last lines executing look like this:
Choice:X
C:\UBUTool>if not defined ec goto mnmc
C:\UBUTool>if defined mcguid ( if /I x == c goto createffs if /I x == e Files\Intel\mcode\MCUpdate.txt if /I x == m goto mcg if /I x == v start mmtool bios.bin /p && goto cpu )
C:\UBUTool>if /I x == x echo Extracting… && mce bios.bin -skip 1>nul && goto cpu Extracting… Traceback (most recent call last): File “MCE.py”, line 1265, in <module> File “site-packages\colorama\ansitowin32.py”, line 40, in write File “site-packages\colorama\ansitowin32.py”, line 141, in write File “site-packages\colorama\ansitowin32.py”, line 166, in write_and_convert File “site-packages\colorama\ansitowin32.py”, line 174, in write_plain_text File “c:\python\python36-32\lib\encodings\cp850.py”, line 19, in encode UnicodeEncodeError: ‘charmap’ codec can’t encode character ‘\u255f’ in position 43: character maps to <undefined>
Doesn’t work on ASRock Z370 Extreme4 UEFI version 3.10. In UEFI says failed security check, never happened before. Use older UBU version same thing, ASRock changed something in this version so i can’t flash modded UEFI anymore. UBU doesn’t say “remove ASRock protection and new protection” anymore either when i load the UEFI file.
Asrock Fatal1ty Z370 Gaming K6. When I try to flash the modified by UBU_v1_70_rc14_2 UEFI, it says "Secure Check Failed". I am trying the newest UEFI, which is version 3.20.
@bobypf : ASRock has changed beginning with the latest Intel 300-Series Chipset mainboards the BIOS protection efforts to prevent the flashing of “unsecure” (modded) BIOSes. Our Forum member lordkag has recently written a workaround how to get such modded BIOS successfully flashed. You should find it within the thread about how to successfully flash a modded UEFI BIOS.
