Not a bug, here’s few examples of asus laptops I got unlock requests for: FA506NC, FA507NVR, FA507NU, Strix G713PI, G513QYAS. All of them have AMD HII drivers loaded, but resources aren’t exported. Some other asus laptops have them exported, AMD menu are available and I couldn’t figure out the reason, the difference.
Not a bug, here’s few examples of asus laptops I got unlock requests for: FA506NC, FA507NVR, FA507NU, Strix G713PI, G513QYAS. All of them have AMD HII drivers loaded, but resources aren’t exported. Some other asus laptops have them exported, AMD menu are available and I couldn’t figure out the reason, the difference.
Which make sense. On G614FRAS heard that ASUS added CCD switch feature. They said this boomed the UMAF menu. Currently, UMAF can only see 2 options, and somehow this option got localization, They speculate ASUS made its own AMD Overclocking Menu, But i have not found anything except AodDxe include this menu. Weird.
Final question, On Lenovo’s newest BIOS, SREP’s Exec OpCode was Refused somehow.
After all patches, while trying Exec SetupUtilityApp, the BIOS will returns to the Boot Menu for somehow. I was curious how lenovo did this, Is the block method just simply GUID judgment or i don’t know ? Because OEM can’t just block every user’s boot input i think. (Otherwise will be slamed by users)
So if i’m not misunderstand, By using this method, it can patch and directly into Setup even with some BIOS that have no SetupUtilityApp or something that was needed to go into patched Setup after patch ?
That’s correct. And the patch is not mandatory. If you push the default hotkey or set OsIndications to 1, computer still should enter bios setup since SREP driver comes before exiting boot services.
I shared the vid just to show more convenient way.
Like this ?
But i remember Smokeless said that SREP can only patch something that has been loaded, In this case the Setup has already loaded into memory just not called right ?
Sorry for my dumb question, I’ve just start learing UEFI.
EDIT:
And, is the complete loading sequence for implementing this consistent as I predicted ?
BootMenuDriver → EFI Shell → Loader → Setup
The loader called SREP and patched Setup before the BootMenuDriver exited, and then let the OEM BIOS load its own Setup
In this case i think the Lenovo issue can be solved, I guess ?
Don’t know how to explain this right… Do you know what async execution by any chance?
Driver can be loaded and, at the same time, be in stall. This what happens with amitse.
I think the sequence is: UEFI loads AMITSE, DXE finishes, AMITSE loaded and didn’t exit yet, SREP loads and patches stuff, AMITSE resumes and launches Setup.
Yes i know async execution. Wow, sounds complicated.
Which seems quite interesting, I’ll gonna try for this on Insyde if i have a chance. I think they’re have same principles.
is there anyway to patch/unlock a hp omen wf-1375ng with this method? it has insyde bios. sorry im new at this topic i want to learn because i need the advanced tab for disabling e cores and undervolting with throttlestop