| System Name | Ryzen5900X |
|---|---|
| Processor | AMD Ryzen 5900X |
| Motherboard | Gigabyte B550 AORUS PRO AC |
| Cooling | NZXT Kraken X62 |
| Memory | 4x G.Skill F4-3600C17D-8GTZ |
| Video Card(s) | AMD Radeon RX 6800XT Midnight Black |
Like I said before: I tried to update the signature. Try at own risk.
I understand, I was finishing configuring the computer and I haven't tested it yet, I'm going to build the signature on the device because I want to use the functions on the platform, did you notice how bigger the SecurityFlash_x86_WIN_100.00.02.03 folder is, when did you build isflash.bin and how did you do it? is in the V4 folder, does the SecurityFlash_x86_WIN_100.00.02.03 process itself create the platform based on the FD? Thank you for all your efforts in helping!
Test V4:
| System Name | Ryzen5900X |
|---|---|
| Processor | AMD Ryzen 5900X |
| Motherboard | Gigabyte B550 AORUS PRO AC |
| Cooling | NZXT Kraken X62 |
| Memory | 4x G.Skill F4-3600C17D-8GTZ |
| Video Card(s) | AMD Radeon RX 6800XT Midnight Black |
I used the extractor for that. After reinjecting the certificate, I renamed it back to *****.FD
With the exception of the new folder I created, this only came in v4 and no *.fd present can guide me in what to do after using the extractor to extract the BIOSFILE.fd and after signing the command to merge the 3 back into FD files, BIOSFILE.fd, EC.bin and platforms.ini?
| System Name | Ryzen5900X |
|---|---|
| Processor | AMD Ryzen 5900X |
| Motherboard | Gigabyte B550 AORUS PRO AC |
| Cooling | NZXT Kraken X62 |
| Memory | 4x G.Skill F4-3600C17D-8GTZ |
| Video Card(s) | AMD Radeon RX 6800XT Midnight Black |
I see, I adjusted the platform.ini to read the isflash.bin instead
I saw this too, yes and a lot of information from different cases too, now I understand better, what I have to do is simply update the original FD certificate that has expired and the extractor will no longer be a problem I believe, the question in my case is how to update the specific certificate expired, which creates isflash.bin updates another certificate. And another issue to check after updating is the checksum, whether it matches the original file.
| System Name | Ryzen5900X |
|---|---|
| Processor | AMD Ryzen 5900X |
| Motherboard | Gigabyte B550 AORUS PRO AC |
| Cooling | NZXT Kraken X62 |
| Memory | 4x G.Skill F4-3600C17D-8GTZ |
| Video Card(s) | AMD Radeon RX 6800XT Midnight Black |
Bios didn't die, its corrupted now since the flash failed. Did you try to flash the original bios? Did you make a backup before flashing?
| System Name | RogueOne |
|---|---|
| Processor | Xeon W9-3495x |
| Motherboard | ASUS w790E Sage SE |
| Cooling | SilverStone XE360-4677 |
| Memory | 128gb Gskill Zeta R5 DDR5 RDIMMs |
| Video Card(s) | MSI SUPRIM Liquid X 4090 |
| Storage | 1x 2TB WD SN850X | 2x 8TB GAMMIX S70 |
| Display(s) | 49" Philips Evnia OLED (49M2C8900) |
| Case | Thermaltake Core P3 Pro Snow |
| Audio Device(s) | Moondrop S8's on schitt Gunnr |
| Power Supply | Seasonic Prime TX-1600 |
| Mouse | Lamzu Maya Grey |
| Keyboard | Monsgeek M3 Lavender, Moondrop Luna lights |
| VR HMD | Quest 3 |
| Software | Windows 11 Pro Workstation |
| Benchmark Scores | I dont have time for that. |
Try again! Don’t shut down!
It's still the same, I think I locked it with an Unlocker that I found reading articles on the site that recommended Security Flash but now I can't find the article but I think it's on the same link, this flasher is from the A04 which from the beginning should having used it before testing other alternatives, now I have to find out how Unlocker works to unlock or is it still the same problem with the lack of bios.fd signature, how angry, bro. At least I already know that the Insyde flashes from the A04 bios flashes on my windows.
It's starting normally, thank God and Insyde, the part that updates, I believe it's the EC, it writes just the BIOS just fine, even though it grabs the SM, I still don't even understand what part this part of the bios is, but it has to do with the flashing insurance, it seems!
