Giter VIP home page Giter VIP logo

uefi-editor's People

Contributors

boringboredom avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

uefi-editor's Issues

Failsafe and Optimal are being ignored

Failsafe and Optimal are being ignored, as seen here and here. I lack the necessary information on how to proceed implementing a workaround for these (probably very common) cases. If anyone can point me towards documentation or forum/blog posts dissecting this topic, please post here.

Changes to defaults don't take because they seem to get pulled from NVRAM

My issue is similar to this in that the changes made by UEFI-Editor do not take effect when I load the "Optimized Defaults".

What I do, is this:

  • I follow the guide and extract the files.
  • I load the files into UEFI Editor.
  • I change the value of a setting in the "Optimal" column.
  • I download the files. I get Section_Freeform_subtype_GUID_setupdata_setupdata_AMITSESetupData_body.bin only (and the changelog)
  • I re-instert the files, flash, reboot, load optimized defaults
  • The setting is not changed

Changelog is
`========== Section_Freeform_subtype_GUID_setupdata_setupdata_AMITSESetupData_body.bin ==========

Low Power S0 Idle Capability | QuestionId 0x225: Optimal 00 -> 01`

So, I looked into this and it seems in my BIOS (Gigabyte Z690 Aorus Elite DDR4, version F23), a copy of the default settings is stored in NVRAM. If I edit the setting in NVRAM, it takes. The optimized default value is changed and the current value is changed accordingly when I load optimized defaults. If UEFI Editor makes changes to AMITSESetupData_body.bin, the settings don't take.

It seems editing AMITSESetupData_body.bin does nothing.

Location of Optimized Defaults

Also, I'd like to say: Thank you for this great tool! Even if it doesn't currently work for me, I can see all the settings in their proper category, which is very useful!

A two-layer configuration menu appears in the BIOS

Provide the official URL to the UEFI you tried to modify.

1

Did you modify a previously modified UEFI or the stock one?

Stock

What flashing method did you use?

ESP32

Did you successfully flash a stock UEFI with said method?

Yes

SHA256 hash of unmodified Setup SCT

1

SHA256 hash of IFR Extractor output TXT

1

SHA256 hash of unmodified AMITSE SCT

1

SHA256 hash of unmodified Setupdata BIN

1

Attach the data.json file with the modification you attempted to do.

1

SHA256 hash of modified UEFI

Not a double menu

Describe the expected outcome as detailed as possible.

1

Describe the actual outcome as detailed as possible.

[
backupbios.zip
](url)

Attached are several values ​​that I decompressed and the original bios backed up by the tool. I don’t know why a double menu configuration appears after opening it.

6d5d5500e87067fc10370acbca38ee3

No File safe!

Hello
since yesterday the UEFI EDITOR doesn't work properly for me anymore.
The days before everything worked perfectly, the files AMITSESetupData_body, PE32_image_Setup etc. were always saved (after editing).
Now, when saving the changed files, an error message appears "Something went wrong. Please file a bug report on Github.”

Can you help me with the problem?

(Screenshot)
nosafe

Getting help

Provide the official URL to the UEFI you tried to modify.

N/A

Did you modify a previously modified UEFI or the stock one?

Previously modified

What flashing method did you use?

N/A

Did you successfully flash a stock UEFI with said method?

No

SHA256 hash of unmodified Setup SCT

N/A

SHA256 hash of IFR Extractor output TXT

n/A

SHA256 hash of unmodified AMITSE SCT

N/A

SHA256 hash of unmodified Setupdata BIN

N/A

Attach the data.json file with the modification you attempted to do.

N/A

SHA256 hash of modified UEFI

N/A

Describe the expected outcome as detailed as possible.

Sorry for opening an issue.
Would be awesome if you could add some information in README where to ask questions.

Currently trying to understand howto get access to the hidden Setup->Advanced menu but my MAIN menu contains a list of doublets. You have an example on MSI but it does not look the same in my bios.

Created a thread on url bellow, but don't know if it's here UEFI Editor community is.
https://www.bios-mods.com/forum/Thread-UEFI-editor-add-2nd-hidden-advanced-menu

Describe the actual outcome as detailed as possible.

N/A

Support for Aptio IV

Hi,

I actually own an Aptio IV mb that I want to play with, just modifying, etc, and I tried your fantastic tool but although the format is OK, the part of IFR data does not correspond to the "Setup" GUID, but the MiniSetupResourceSection instead. This generates a lot of files with ifrextractor 1.5.1:
imagen

There are a lot of files and each file contains one form only, so I guess I would have to go one by one.
Here I have some questions:

With this scenario, do you think you could arrange to create (or copy actual one and paste & modify into another version) some other frontend to upload and modify IFR for older versions?

I have another mobo aptio IV (asus this time) and it seems to have the same way of working, with the same GUIDs and names where IFR data is stored, so I could truly say that Aptio IV works that way.

Let me attach the files for you in case you have time to take a look at, and generate a new version, which would be sooooo appreciated and thankful for me.

IPISB-CH2.zip

Thank you soo much in advance.

Stuck at Loading Circle

Provide the official URL to the UEFI you tried to modify.

https://www.asus.com/motherboards-components/motherboards/prime/prime-h610m-a-d4/helpdesk_bios/

Did you modify a previously modified UEFI or the stock one?

Previously modified

What flashing method did you use?

intel FPT

Did you successfully test it with a stock UEFI first?

Yes

Did you use the specific version of IFR-Extractor-RS linked on the UEFI Editor page?

Yes

Attach the data.json file with the modification you attempted to do.

CANNOT ATTACH it

Describe the expected outcome as detailed as possible.

image

Stuck at loading circle after upload all needed files, that error happen sometimes in my desktop, in my Laptop i neved able to past loading screen
browser tried :chrome,edge,firefox

Describe the actual outcome as detailed as possible.

image

Stuck at loading circle after upload all needed files, that error happen sometimes in my desktop, in my Laptop i neved able to past loading screen
browser tried :chrome,edge,firefox

Modded bios dont flash on MSI Z790 EDGE D4 and UefiTool DOS signature: invalid

Provide the official URL to the UEFI you tried to modify.

https://ru.msi.com/Motherboard/MPG-Z790-EDGE-WIFI-DDR4/support#bios

Did you modify a previously modified UEFI or the stock one?

Stock

What flashing method did you use?

MSI FLASH BIOS

Did you successfully flash a stock UEFI with said method?

Yes

SHA256 hash of unmodified Setup SCT

39a150201410b5867403bc072b4a4513bcea06143d89e604d8f4f09dae68ddb6

SHA256 hash of IFR Extractor output TXT

0f269e6bd21f80f93ba69b36a5140ab22165a2fe71cce8b9b38eff184220fa4a

SHA256 hash of unmodified AMITSE SCT

ba83dc18dd76ec1f00513325aaaf67986c06cc7ec98acbddbd535d64b0ffda0f

SHA256 hash of unmodified Setupdata BIN

8941b16202069820e222b157931ac310b15a6c8effe05f85fcfd4c9acce1e329

Attach the data.json file with the modification you attempted to do.

data.txt

SHA256 hash of modified UEFI

online generator broken after that im try to upload it in .txt

Describe the expected outcome as detailed as possible.

  1. Flashed bios
  2. Enable RTC timer
  3. Enable IO low latency

Describe the actual outcome as detailed as possible.

Bios not flashing
Uefi shows DOS signature: invalid
Untitled
image

Hide bios menu item

@BoringBoredom I have asus zenbook and is it possible to hide menu item using this?
And is there any risky item to do this?

I am newbie to custom bios and I want to make sure about this. :D

Freeze in Loading Cannot Open Stock BIOS

Provide the official URL to the UEFI you tried to modify.

https://mysupport.razer.com/app/answers/detail/a_id/4631

Did you modify a previously modified UEFI or the stock one?

Stock

What flashing method did you use?

Razer software (afu)

Did you successfully test it with a stock UEFI first?

No

Did you use the specific version of IFR-Extractor-RS linked on the UEFI Editor page?

Yes

Attach the data.json file with the modification you attempted to do.

did not have

Describe the expected outcome as detailed as possible.

expect that more responsive, i only test uefii editor online version, not tested yet in local with Xampp, so i think if it limit for javascript for iteration process by github.io but i dont know without test with local version yet

Describe the actual outcome as detailed as possible.

Razer Book 13
Bios version :v202
bios format in exe, extract with 7zip to get bios.bin
Uefi tool NE 62 For extract PE32

Browser test
Chrome v107.0.5304.88 ( : no log on console
firefox latest v108.0.1 (64-bit) : detail log in console

Chrome
Page not responsive pop up coming up, but no log in console
image

Firefox
Uncaught (in promise) InternalError: too much recursion in scriptt.ts line 389
image

MSI BIOS Unresponsive while Using Modified Image

Provide the official URL to the UEFI you tried to modify.

https://www.msi.com/Motherboard/MPG-Z390-GAMING-PLUS/support version 7B51v1E

Did you modify a previously modified UEFI or the stock one?

Stock

What flashing method did you use?

MSI M-FLASH

Did you successfully flash a stock UEFI with said method?

Yes

SHA256 hash of unmodified Setup SCT

3e0d2286b6da0059dfdaf0f124ba57ca3075547a82076f8324f3092637a6b19b

SHA256 hash of IFR Extractor output TXT

9c97e18e492c6839ac9f212628c6efe6816449cc1804d585a80dc17ee06b6677

SHA256 hash of unmodified AMITSE SCT

80115bfd31c9380f777d4134dbe9f1c9e485ae76d2a0d461cd121e426fbe94ec

SHA256 hash of unmodified Setupdata BIN

871d05317b6c77a2479977485ab5cd6eebf7113292cc340eb263ae1d263d5aea

Attach the data.json file with the modification you attempted to do.

I've attached both the stock and modified json files. I've also attached the simple changelog.

data.json.txt
data_modified.json.txt
changelog.txt

SHA256 hash of modified UEFI

f419cd1b251ee9ded6dc6522a70bb19ce147c0c75e700c161f68d485b1e8da8f

Describe the expected outcome as detailed as possible.

I would like to dive deep into this BIOS firmware. My goal of using this very useful tool is to enable certain PCIE settings. However, for testing purposes, I simply switched the OC Profile to the advanced form ID.

Describe the actual outcome as detailed as possible.

The BIOS appeared to flash successfully using M-Flash, however, clicking any setting in the advanced menu of the modified BIOS caused it to freeze and require a hard reboot. In addition, the BIOS displayed incorrect hardware information, such as zero installed memory, and no devices connected to the MB were detected. Despite these issues, I was able to boot into an operating system and still access M-Flash. To resolve the problem, I had to flash the BIOS again using the stock image, after which I was able to change settings without further issues.

Menu function behaved weirdly

I changed the m-flash into integrated graphics settings but when i pressed the m-flash button and hit esc it just displays the main setup menu, is this normal?

I change from this:
image

to this:
image

the actual menu it displays:
image

modifying default (optimal) settings ignored

I tried to modify default (optimal) settings of an ASUS H610T bios according to the instructions given. All went as described, except:

  • when downloading the modified files, only changelog.txt and Section_Freeform_subtype_GUID_setupdata_setupdata_AMITSESetupData_body.bin are being downloaded
  • when inserting the modified file into the original .cap in UEFITool_0.28 at the corresponding GUID, all "text" looked totally different and non readable compared to the UEFITool_NE version
  • I flashed and verified the resulting binary onboard using a USB SPI programmer
  • The main-board boots, it has the new bios, except that it seems to have ignored all my changes
  • When checking the modified .cap file by also extracting and opening it in UEFI-Editor, all changes are displayed correctly

Am I missing something in the process, or what could be the problem?

Thanks for the excellent work!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.