Thanks! Nothing useful there, see my edit above about backup.

Also, try to run this CMD from same folder with EXE (Run CMD as Admin) >> H2OFFT-W.exe backup.bin /g
If you do not know how to run Admin CMD prompt from exact location, install this registry fix and you may need to reboot before it wo, then you can click anywhere inside folder with EXE and choose "Open CMD Window here as Admin"
https://ufile.io/rwxofn2a

Zitat von Lost_N_BIOS im Beitrag #14

---

Great, now click options, what do you see?

* edit -
Edit platform.ini again and add this, see if it makes backup after you open program. if not, use 5.13 version, it already has this in platoform.ini (you will need to make same edits (above) as before again too)
[BackupROM]
Flag=1
FilePath=
FileName=backup.bin
;Flag default : 0.
; 0 : No backup BIOS.
; 1 : Backup current BIOS and new BIOS binary.
;FilePath default : empty.
; empty : Use current directory.
; String : Directory for backup BIOS.
;FileName default : empty.
; empty : Use platform ID as file name.
; String : File name for backup BIOS.

If no file created, try same again, but edit this instead from above, and then check ROOT of C drive for BIOS backup.bin
FilePath=c:

---

Did you try to run command instead, that I mentioned above? This would be quick and easy way.
Platform.ini above looks good, but add a space between that last section and your addition

Zitat von Lost_N_BIOS im Beitrag #18

---

Did you try to run command instead, that I mentioned above? This would be quick and easy way.
Platform.ini above looks good, but add a space between that last section and your addition

---

Did you try both ways? Edit platform again and add C: to path, instead of blank path? Did you check the folder you ran from, backup would be there, if made. Then once you add C: it will be made at root of C:, if it gets created.

Do not install any new BIOS yet, but see if that will run properly. If it does, close exit, don't flash, if that is an option. Then, we will edit platform.ini and make backup while it flashes in the update.
To do that go to where ever it extracts the exe (ie C:\SWSetup\sp107493) and edit platform.ini there and edit the backup section or add it if missing etc.

Zitat von Lost_N_BIOS im Beitrag #20

---

Did you try both ways? Edit platform again and add C: to path, instead of blank path? Did you check the folder you ran from, backup would be there, if made. Then once you add C: it will be made at root of C:, if it gets created.

Do not install any new BIOS yet, but see if that will run properly. If it does, close exit, don't flash, if that is an option. Then, we will edit platform.ini and make backup while it flashes in the update.
To do that go to where ever it extracts the exe (ie C:\SWSetup\sp107493) and edit platform.ini there and edit the backup section or add it if missing etc.

---

YOu said >> when installing sp107493 << Do you mean "After you installed sp107493"?? If yes, OK, just wanted to make sure what you meant
So you updated BIOS, you could have dumped it this way before too, without update

Anyway, now, lets change this setting! Hmm, still same issue, corrupted structure to main DXE BIOS volume, and it does not expand properly for me to get what we need here
When you run the sp107493 do you have option to extract or save BIOS to some location? If yes, do that, and send me the files.
I do not mean how the exe normally extracts files to C:\SWSetup\sp107493 when you first run it, and in there you find 2 x 4.37MB BIOS files, this is not what I need here

Send a PM to AmagicalFishy at BIOS-mods and hopefully he will reply! Ask him how he extracted the setup module, and or to send you the setup IFR from sp107493 BIOS
He was last there in 2019, so maybe he will get an email from your PM and reply, or you can also maybe email from his profile too.
Ahh! Never mind, you do not even have same model as that user in thread you linked! So his setup and or IFR would not match, and probably he got this info easily because his BIOS properly expanded this section!

Why do I see such different BIOS exe package names for your BIOS here - https://support.hp.com/us-en/drivers/sel...8/model/5282698
^^ Is that the correct BIOS for your system?? I was looking in google, trying to find other users dumps, or someone trying to recover this model, so I could check those BIOS to see if setup broken in those too or not, then I see the above stock BIOS does not match what we've been discussing?

Also, I see you've been asking about this model since 2017, and since then you've not purchased a $7 flash programming tool set, why not? Please order now, maybe direct dump of chip will give valid file. You need CH341A + SCOI8 test clip with cable.

Zitat von Lost_N_BIOS im Beitrag #22

---

YOu said >> when installing sp107493 << Do you mean "After you installed sp107493"?? If yes, OK, just wanted to make sure what you meant
So you updated BIOS, you could have dumped it this way before too, without update

Anyway, now, lets change this setting! Hmm, still same issue, corrupted structure to main DXE BIOS volume, and it does not expand properly for me to get what we need here
When you run the sp107493 do you have option to extract or save BIOS to some location? If yes, do that, and send me the files.
I do not mean how the exe normally extracts files to C:\SWSetup\sp107493 when you first run it, and in there you find 2 x 4.37MB BIOS files, this is not what I need here

Send a PM to AmagicalFishy at BIOS-mods and hopefully he will reply! Ask him how he extracted the setup module, and or to send you the setup IFR from sp107493 BIOS
He was last there in 2019, so maybe he will get an email from your PM and reply, or you can also maybe email from his profile too.
Ahh! Never mind, you do not even have same model as that user in thread you linked! So his setup and or IFR would not match, and probably he got this info easily because his BIOS properly expanded this section!

Why do I see such different BIOS exe package names for your BIOS here - https://support.hp.com/us-en/drivers/sel...8/model/5282698
^^ Is that the correct BIOS for your system?? I was looking in google, trying to find other users dumps, or someone trying to recover this model, so I could check those BIOS to see if setup broken in those too or not, then I see the above stock BIOS does not match what we've been discussing?

Also, I see you've been asking about this model since 2017, and since then you've not purchased a $7 flash programming tool set, why not? Please order now, maybe direct dump of chip will give valid file. You need CH341A + SCOI8 test clip with cable.

---

Ohh, OK, at least you could then dump BIOS at least! You did not answer my question about stock BIOS names, versions and that page at HP?

Thanks, I will check out PERL thing. UEFITool usually is able to do all this itself (extract setup, then I generate txt IFR using universal IFR extractor)
That is what I was using to look at BIOS, but it does not decompress only the volume we need to look at so I can extract and get IFR text output from setup (Nor does PhoenixTool, which is used in the PERL guide)
So, all same stuff I already do, just different way. And trying to follow that guide just to be sure, at step #10 there is no matching file name, or type. But I confirmed by trying to extract IFR from all larger sized possible modules that may be "Setup" (23KB-908KB), after BIOS is dumped into DUMP folder
Then I repeated this check on all possible targets using ActivePerland the perl script, same outcome. So that method does not apply to this BIOS, and main DXE volume is still not extracted/decompressed with this method either, which I already knew from trying PhoenixTool extract before you linked this guide


What you linked second is not a script/code, that is just info the user collected while inspecting BIOS

What is above package about H20? I am on limited internet, and already have TONS of versions of all H2O tools (EZE, FFT, UVE SDE)
I assume I have all that already, and same versions or more/newer etc, and that may even be my upload (where did you see the link posted?)

On most systems you do not have to desolder BIOS chip, you can clip onto it and then read/write directly. Sometimes you need to have main batter and or PSU cable attached, sometimes only one of those, sometimes neither, all depends on the board.
Rare cases you may have to remove chip to read/write, but it's rare. This will not help though, file will be same as what you already sent me I assume Sorry for thinking it may differ, and it still might, but I would not get my hopes up

If you could get some version of UVE to work, then you could dump vars and setup then we could change!
Try all versions of UVE and this command (H2OUVE.exe used next is generic name for the EXE in folder, not all are named same) >> H2OUVE.exe -gs setupsettings.txt -all

Once you find working version, run this command too >> H2OUVE.exe -gv vars.txt
^^ That is how we'll change the setting, once you can dump/create setupsettings.txt using first command.

Zitat von Lost_N_BIOS im Beitrag #24

---

Ohh, OK, at least you could then dump BIOS at least! You did not answer my question about stock BIOS names, versions and that page at HP?

Thanks, I will check out PERL thing. UEFITool usually is able to do all this itself (extract setup, then I generate txt IFR using universal IFR extractor)
That is what I was using to look at BIOS, but it does not decompress only the volume we need to look at so I can extract and get IFR text output from setup (Nor does PhoenixTool, which is used in the PERL guide)
So, all same stuff I already do, just different way. And trying to follow that guide just to be sure, at step #10 there is no matching file name, or type. But I confirmed by trying to extract IFR from all larger sized possible modules that may be "Setup" (23KB-908KB), after BIOS is dumped into DUMP folder
Then I repeated this check on all possible targets using ActivePerland the perl script, same outcome. So that method does not apply to this BIOS, and main DXE volume is still not extracted/decompressed with this method either, which I already knew from trying PhoenixTool extract before you linked this guide


What you linked second is not a script/code, that is just info the user collected while inspecting BIOS

What is above package about H20? I am on limited internet, and already have TONS of versions of all H2O tools (EZE, FFT, UVE SDE)
I assume I have all that already, and same versions or more/newer etc, and that may even be my upload (where did you see the link posted?)

On most systems you do not have to desolder BIOS chip, you can clip onto it and then read/write directly. Sometimes you need to have main batter and or PSU cable attached, sometimes only one of those, sometimes neither, all depends on the board.
Rare cases you may have to remove chip to read/write, but it's rare. This will not help though, file will be same as what you already sent me I assume Sorry for thinking it may differ, and it still might, but I would not get my hopes up

If you could get some version of UVE to work, then you could dump vars and setup then we could change!
Try all versions of UVE and this command (H2OUVE.exe used next is generic name for the EXE in folder, not all are named same) >> H2OUVE.exe -gs setupsettings.txt -all

Once you find working version, run this command too >> H2OUVE.exe -gv vars.txt
^^ That is how we'll change the setting, once you can dump/create setupsettings.txt using first command.

---

I was talking about BIOS linked for this model at post #22, the link to HP's site. I was thinking sp107493 was BIOS when you mentioned that, so didn't see it there and that's why I asked
I see now, the latest version is the 77491 we're using here

Zitat von Lost_N_BIOS im Beitrag #26

---

I was talking about BIOS linked for this model at post #22, the link to HP's site. I was thinking sp107493 was BIOS when you mentioned that, so didn't see it there and that's why I asked
I see now, the latest version is the 77491 we're using here

---

@sagael - No, that's used for much different purpose, change/comment ME/AMT or TPM states, update/change DMI info (such as Serial, UUID, etc)
If someone is helping you there, ask them if they can extract Setup module or Setup PE32 for you, from the file at post #23, so you can generate IFR text file (<< This is your end goal, you need all setup variables.)

Zitat von Lost_N_BIOS im Beitrag #28

---

@sagael - No, that's used for much different purpose, change/comment ME/AMT or TPM states, update/change DMI info (such as Serial, UUID, etc)
If someone is helping you there, ask them if they can extract Setup module or Setup PE32 for you, from the file at post #23, so you can generate IFR text file (<< This is your end goal, you need all setup variables.)

---

@sagael - We already have decrypted BIOS, your dumped BIOS from #23 - Ask Serg008 if he can get "SetupUtility PE32" from that BIOS
Why would he mention "Bin is wrong"?? Maybe he thought you were trying to recover BIOS with these? If so, yeah, I tell you that too, should not be used for recover.

H2OUVE and H2OFFT are very different, FFT made your BIOS dump, we need to find working/compatible version of UVE to get NVRAM variables to edit, and setup variables to use to make that edit (Both of these can be done with UVE, once we find compatible version)

Ahh, great! Those are not messed up like your dumped one! I can get setup from there, but we don't know which one applies to your system, unless it shows you the family ID in BIOS main Page or during BIOS update process.
Check BIOS Main Page, and or run BIOS update again, do you see either one of these values >> 01847F2A, or 0188DF2A

Never mind, I checked both BIOS, and there is no video memory, DVMT, etc option. So you cannot adjust this setting on this model.
Here is both BIOS setup in IFR form, so you can search, scroll through etc all the settings and see what I mean, no such setting here
https://ufile.io/zs678waw