Need help with Dell 7520 SE

[VuurVOS]

https://winraid.level1techs.com/t/tool-h20eze-insyde-easy-bios-editor/33332/7
I found this information from Insyde's .fd editor but still studying everything! If anyone understands the subject well and wants to help, I would be grateful, I want to get to the root of the problem and clear up any doubts.


Extract extracts it without the forceit command, but it does not install even with /nopause /forceit and /forcetype, Also note that even the installer doesn't read the BIOS very strangely, which reinforces my theory that there is some lock preventing it.


View attachment 366843

Did you do a fresh install of Windows? What happens if you just press on OK?

 

[FilhoSenhor]

Did you do a fresh install of Windows? What happens if you just press on OK?

It simply repeats the same warning and cancel closes the installer.

 

[FilhoSenhor]

Can you dump the bios with GPU-Z and share it with us?

Hello brother, I managed to save here the current BIOS installed on the device in version A11 through the Insyde flash program in a *.bin file also containing the VBIOS currently installed on it, also an old version of the original factory bios which is version A04, Even so, I still can't update the BIOS to the latest available version A14, because the *.FD file the BIOS returns is not compatible with the one installed in the BIOS for some reason, I realized that the insyde program and the BIOS use ports specifications for flash are probably the reason why GPU-Z is unable to extract the VBIOS in its current version. I don't know if the files and information could be useful here. If you have contact with Dev, you can let me know that I'm willing to help with whatever is necessary to make GPU-Z more compatible.

 

[VuurVOS]

Hello brother, I managed to save here the current BIOS installed on the device in version A11 through the Insyde flash program in a *.bin file also containing the VBIOS currently installed on it, also an old version of the original factory bios which is version A04, Even so, I still can't update the BIOS to the latest available version A14, because the *.FD file the BIOS returns is not compatible with the one installed in the BIOS for some reason, I realized that the insyde program and the BIOS use ports specifications for flash are probably the reason why GPU-Z is unable to extract the VBIOS in its current version. I don't know if the files and information could be useful here. If you have contact with Dev, you can let me know that I'm willing to help with whatever is necessary to make GPU-Z more compatible.

Sorry you need to do this yourself, we only guide.

A04 and A11 are not valid. At least I can't extract them with InsydeH2O-extractor-2. I can extract A14 with that tool.

GitHub - vaginessa/InsydeH2O-extractor-2

Contribute to vaginessa/InsydeH2O-extractor-2 development by creating an account on GitHub.

github.com

Also when you have downloaded the bios archives directly from dell, you can unzip them with 7zip.

 

[FilhoSenhor]

Sorry you need to do this yourself, we only guide.

A04 and A11 are not valid. At least I can't extract them with InsydeH2O-extractor-2. I can extract A14 with that tool.

GitHub - vaginessa/InsydeH2O-extractor-2

Contribute to vaginessa/InsydeH2O-extractor-2 development by creating an account on GitHub.

github.com

Also when you have downloaded the bios archives directly from dell, you can unzip them with 7zip.

Yes, I did it that way, yes!


What do you mean they are not valid?


I'll take a look at the tool, but I need something that can write the BIOS, tell me more specifically what you need!

How do I download this, do I have to download it file by file or just extractor.exe?

I tried to send along with the BIN's the folders extracted from the original Dell file with the settings made to work without a battery but the ZIP won't upload.

Sorry you need to do this yourself, we only guide.

A04 and A11 are not valid. At least I can't extract them with InsydeH2O-extractor-2. I can extract A14 with that tool.

GitHub - vaginessa/InsydeH2O-extractor-2

Contribute to vaginessa/InsydeH2O-extractor-2 development by creating an account on GitHub.

github.com

Also when you have downloaded the bios archives directly from dell, you can unzip them with 7zip.

I understand, it separates the EC.bin files from the ROM.fd and extracts the platforms, but what do you want me to do on my own that you haven't already done?

 

[VuurVOS]

What do you mean they are not valid?

They are not valid binaries. Unusable.

How do I download this, do I have to download it file by file or just extractor.exe?

I downloaded the whole master branch of that repo (https://github.com/vaginessa/InsydeH2O-extractor-2/archive/refs/heads/master.zip)

I tried to send along with the BIN's the folders extracted from the original Dell file with the settings made to work without a battery but the ZIP won't upload.

I've attached a zip with a modified platform.ini. BatteryCheck is now 0 instead of 1.

You only need to extract all files from 7520A14.zip and run "InsydeFlash.exe" (at own risk)

 

[FilhoSenhor]

They are not valid binaries. Unusable.


I downloaded the whole master branch of that repo (https://github.com/vaginessa/InsydeH2O-extractor-2/archive/refs/heads/master.zip)


I've attached a zip with a modified platform.ini. BatteryCheck is now 0 instead of 1.

View attachment 369832

You only need to extract all files from 7520A14.zip and run "InsydeFlash.exe" (at own risk)

Yes, that was the change I made too, where did you find this, here on the website?
If in this update the change only in platform does not work, it must have been done directly in FD.
It didn't work either!

 

[VuurVOS]

Yes, that was the change I made too, where did you find this, here on the website?

Find what? I just checked the ini and just change. There are more options which you can change.

it must have been done directly in FD.

The flasher accepts the parameters in the config file. The FD file should not contain those parameters since it contains the Flash Data.

I disable more battery like settings in platform.ini. Also error codes of empty battery are now also 0 (which means its fine) in the config file.

 

[FilhoSenhor]

Find what? I just checked the ini and just change. There are more options which you can change.


The flasher accepts the parameters in the config file. The FD file should not contain those parameters since it contains the Flash Data.

I disable more battery like settings in platform.ini. Also error codes of empty battery are now also 0 (which means its fine) in the config file.

I understand now, you are doing the same thing as me here, the extractor helped a lot, it separated everything from the original FD! My question now is regarding EC.BIN whether I should indicate the file in FilePath in platform.ini or just leave it blank with the file in the flasher folder. Lots of settings Yes, loving the experience and farting a lot too Check the modifications I made to platform.ini before sending me V2! Thank you for your attention with me.

 

[VuurVOS]

I understand now, you are doing the same thing as me here, the extractor helped a lot, it separated everything from the original FD! My question now is regarding EC.BIN whether I should indicate the file in FilePath in platform.ini or just leave it blank with the file in the flasher folder. Lots of settings Yes, loving the experience and farting a lot too Check the modifications I made to platform.ini before sending me V2! Thank you for your attention with me.

I wouldn't try to modifying by adding an EC.BIN.

Did you try the latest v2 zip?

 

[FilhoSenhor]

I wouldn't try to modifying by adding an EC.BIN.

Did you try the latest v2 zip?

Yes, I continued testing with the platform in FD, this BIOSFILE.fd, EC.BIN and platform.ini are the result of the extractor that you recommended, playing QCL01A14.fd on it gave me these files and I mounted this folder and changed the platform of this Is the mode going well? =)

 

[VuurVOS]

Yes, I continued testing with the platform in FD, this BIOSFILE.fd, EC.BIN and platform.ini are the result of the extractor that you recommended, playing QCL01A14.fd on it gave me these files and I mounted this folder and changed the platform of this Is the mode going well? =)

Thats not an answer I am looking for.

Did you:

1. Unzip 7520A14_v2.zip
2. While keeping those files together, did you run InsydeFlash.exe?

If it doesnt work. Rename platform.ini to platforms.ini and try to run InsydeFlash again.

 

[FilhoSenhor]

Find what? I just checked the ini and just change. There are more options which you can change.


The flasher accepts the parameters in the config file. The FD file should not contain those parameters since it contains the Flash Data.

I disable more battery like settings in platform.ini. Also error codes of empty battery are now also 0 (which means its fine) in the config file.

Yes, but if you open QCL01A14.fd in the HEX Editor you will find the parameters inside it that rewrites the platforms every time the Insyde flasher starts, while the extractor you indicated does the separation and disables this so you can change it in the platforms flash settings, but it also separates the EC.BIN from the FD File and now it doesn't flash due to the lack of EC!

I wouldn't try to modifying by adding an EC.BIN.

Did you try the latest v2 zip?

I flashed the EC by accident and it was alone, right? Yes, I tested it, yes! The change has to be in the FD, not in the platform. The platforms is generated by QCL01A14.fd

Thats not an answer I am looking for.

Did you:

1. Unzip 7520A14_v2.zip
2. While keeping those files together, did you run InsydeFlash.exe?

If it doesnt work. Rename platform.ini to platforms.ini and try to run InsydeFlash again.

which files are BIOSFILE.FD and EC.BIN?

 

[VuurVOS]

it that rewrites the platforms every time the Insyde flasher starts

You can also make platform.ini and platforms.ini read only so InsydeFlash cannot overwrite it

1. Unzip 7520A14_v2.zip
2. Make copy of platform.ini and name it platforms.ini
3. Change file attribute of both ini files to read only
4. Run InsydeFlash.exe

 

[FilhoSenhor]

You can also make platform.ini and platforms.ini read only so InsydeFlash cannot overwrite it

1. Unzip 7520A14_v2.zip
2. Make copy of platform.ini and name it platforms.ini
3. Change file attribute of both ini files to read only
4. Run InsydeFlash.exe

It won't, as read-only doesn't even open the blinker! Very strange. I believe the way is to flash the extractor's BIOSFILE.fd without having to write EC.bin again or whatever.

 

[VuurVOS]

It won't, as read-only doesn't even open the blinker! Very strange. I believe the way is to flash the extractor's BIOSFILE.fd without having to write EC.bin again or whatever.

Run the following command:
extractor.exe QCL01A14.fd replace platform.ini

Output:

InsydeFlashExtractor v0.31+genBTC
Starting .ini file re-injection back into isflash.bin
Read 31963 bytes
Wrote 24 byte header to 6419656
Wrote 31963 bytes
File platforms.ini successfully injected back into isflash.bin

It will update QCL01A14.fd with the custom platform.ini

 

[FilhoSenhor]

Run the following command:
extractor.exe QCL01A14.fd replace platform.ini

Output:

InsydeFlashExtractor v0.31+genBTC
Starting .ini file re-injection back into isflash.bin
Read 31963 bytes
Wrote 24 byte header to 6419656
Wrote 31963 bytes
File platforms.ini successfully injected back into isflash.bin

It will update QCL01A14.fd with the custom platform.ini

InsydeFlashExtractor v0.31+genBTC
Starting .ini file re-injection back into isflash.bin
platforms.ini input file can't be opened

 

[VuurVOS]

It seems you need to extract first before replacing. I only show you the replace part command....

I've modified the FD with the adjusted ini

 

[FilhoSenhor]

It seems you need to extract first before replacing. I only show you the replace part command....

I've modified the FD with the adjusted ini

Have you read the extractor settings file? I'm on Win8.1x64!

Any edit we make to FD could be resulting in this, the extractor is probably not working on activating the Insyde signature.

 

[VuurVOS]

I see it is possible to update the signature:

• Guide: https://winraid.level1techs.com/t/insyde-h2o-bios-unlocking-flashing/33324
• SecurityFlash_x86_WIN_100.00.02.03.zip downloaded from winraid.level1techs.com
• Microsoft Windows SDK for Windows 7 and .NET Framework downloaded from microsoft.com

I tried to update the signature. Try at own risk.

 

[FilhoSenhor]

I see it is possible to update the signature:

• Guide: https://winraid.level1techs.com/t/insyde-h2o-bios-unlocking-flashing/33324
• SecurityFlash_x86_WIN_100.00.02.03.zip downloaded from winraid.level1techs.com
• Microsoft Windows SDK for Windows 7 and .NET Framework downloaded from microsoft.com

I tried to update the signature. Try at own risk.

Thank you for your help, as you can see I seem to be unable to find the available solutions,

As always on the MS website, download pain! Are you ready to download the SDK? Send me here please! Does this tutorial and files work for Win 8.1 x64?

 

[VuurVOS]

As always on the MS website, download pain! Are you ready to download the SDK? Send me here please! Does this tutorial and files work for Win 8.1 x64?

You need makecert.exe and pvk2pfx.exe from the SDK. Maybe they are still getting installed if you press on OK.

 

[FilhoSenhor]

Did you do a fresh install of Windows? What happens if you just press on OK?

Yes, sir, I did a clean installation and I'm still configuring and updating to continue where we left off. I managed to install .net3.5 and the SDK, but I still couldn't understand how to update the FD signature. In this tutorial, the v4 that you sent also didn't understand. as well as use.

You need makecert.exe and pvk2pfx.exe from the SDK. Maybe they are still getting installed if you press on OK.

I can't find the QA.pfx from tudorial to install in the SecurityFlash_x86_WIN_100.00.02.03.zip downloaded to follow the instructions. Should I find these two that you mention in the SDK installation and copy them to the extracted zip folder?

 

[VuurVOS]

Yes, sir, I did a clean installation and I'm still configuring and updating to continue where we left off. I managed to install .net3.5 and the SDK, but I still couldn't understand how to update the FD signature. In this tutorial, the v4 that you sent also didn't understand. as well as use.


I can't find the QA.pfx from tudorial to install in the SecurityFlash_x86_WIN_100.00.02.03.zip downloaded to follow the instructions. Should I find these two that you mention in the SDK installation and copy them to the extracted zip folder?

You need to generate a signature yourself with MakeKey.bat. Since makekey.bat uses makecert.exe and pvk2pfx.exe, it must be present on the system by installing the Windows SDK.
The signature which is generated by MakeKey.bat has a different name. It will be called CerTest.pfx instead of QA.pfx but the installation is the same beside a different file name.

Did you try to flash the v4?

 

[FilhoSenhor]

You need to generate a signature yourself with MakeKey.bat. Since makekey.bat uses makecert.exe and pvk2pfx.exe, it must be present on the system by installing the Windows SDK.
The signature which is generated by MakeKey.bat has a different name. It will be called CerTest.pfx instead of QA.pfx but the installation is the same beside a different file name.

Did you try to flash the v4?

No, not yet. Should I blink or do as you described?