Thanks Alonso for explaining , so no way to unlock advanced bios ?
Re-read my post. I explained what I had to do the finally unlock the advanced menu.
I followed the guide here until the last section where you modify A01ODMDxe
That’s where I had to deviate from the guide, otherwise the menu failed to show up like you’re currently seeing.
If you’ve made it this far, you’re literally one or 2 hex values away from unlocking the advanced menu!
2 Likes
Hi~ o(￣▽￣)ブ, upload the BIOS dump, so that we can get help faster.
Sorry i’ve reached the maximum number of replies a new user can create.
Here’s the bios dump :
Hi Alonso my hex knowledge is 0 so im stopped there
Sorry for pestering but seems that just one step left (so not too difficult) but i dont have any hex knowledge so cannot continue…no kind soul that can help me ?
Thanks a lot ! @Alonso @Sweet_Kitten
The most difficult one left.
There’s no UEFITool for Android, so I can not help.
I see , you are on Android now ?
And past 8 month, either.
Don’t think I’m arrogant but I’m referring to a few posts above where I was told: If you’ve made it this far, you’re literally one or 2 hex values away from unlocking the advanced menu! That’s why i wrote: just one step left
"To disable both “Bios Lock’’ and “Flash Protection Range Registers”, go to the folder H2OUVE, click “GET VARS.bat”, this will give you the vars of your Bios. Open “vars.txt” and search for “PchSetup”, now look the variables that enable Bios Lock and Flash Protection Range Registers, in my case 1C and 683 respectively, you will be able to identify them by seeing the value next to “VarStoreInfo (VarOffset/VarName):” Now go to 1C and 683 and replace the 01 with 00, not done yet tho. Just in case, copy the GUID down below “PchSetup” , in my case “4570B7F1-ADE8-4943-8DC3-406472842384”, and as we did it before replace the 1C and 683 values of 01 with a 00. "
I do not understand where to find the correct 01. Any help?
Inside the vars.txt file. The 4th column for byte 683 and the 13th column for 1C.
sorry but i was told that you could help me with this problem i have a PH315-53-75N8 acer note with the bios blocked to unlock and activate advanced and activate xmp i looked on a youtube channel i would like to know if you could help me i apologize for posting here but i couldn’t find any other way.
Error 167: Protected Range Registers are currently set by BIOS, preventing flash access.
Please contact the target system BIOS vendor for an option to disable
Protected Range Registers
Any fix for this?
1 Like
@pAnkEk3
Thank you very much for having added a guide to the start post of this thread.
Since such guide is very helpful for users with a similar problem, I have moved this thread into the “BIOS Modding Guides” Category and gave it a customized name (you can change it at any time by editing the first post of this thread).
It would be much appreciated, if you would keep your guide up-to-date.
Followed this guide and flashed unlocked bios using flashrom on my Acer A515-56-32DK. It works thank you
Just that 16EA is a different thing for me due to me using a newer bios. Had to compare your stock and modded bios to figure out what was changed then once i found what was changed, i copied the decoded text from the unmodded bios and used it to find that section on my bios
1 Like
acer swift 5, stuck here
" Finally go back to “UEFIToolNEA 59” and replace the “A01ODMDxeDriver” module right click ir and choose “Replace as is”, you must select the edited “Section_PE32_image_A01ODMDxeDriver _A01ODMDxeDriver" and save the changes."
in uefi tools NE, i cannot replace as is, it greyed out. version 0.28 can replace but the structure is kinda different, afraid im bricking the laptop.
any solution?
Yes… bios mod is risky and we all take chances, so take it or NOT, if you care for the current state of your asset don’t proceed then… and don’t ask for any assurance of free risk operations with mod files, unless got a confirmation of a user with same mod file flashed, even then its never risk free.
NE for extraction, regular for operations, so your assumptions are correct.
Structure is different but GUID id is present as also DXE drivers volume.
Wait for other users POV, good luck.
already done bios lock and fprr thru vars edit (h20uve). was ready to brick the bios (already have crisis usb ready with .fd - done it before).
however now stuck here.
“Error 368: Failed to disable write protection for the BIOS space.
FPT Operation Failed.”
What is this random variable? How did you do it? Can’t find the same for my bios, trying to locate something similar.