Sunday, January 8, 2023

Flash Asus H170 PRO GAMING BIOS with flashrom

sudo flashrom -p internal

flashrom v1.2 on Linux 5.19.0-15-generic (x86_64)

flashrom is free software, get the source code at https://flashrom.org


Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).

Found chipset "Intel H170".

This chipset is marked as untested. If you are using an up-to-date version

of flashrom *and* were (not) able to successfully update your firmware with it,

then please email a report to flashrom@flashrom.org including a verbose (-V) log.

Thank you!

Enabling flash write... Warning: BIOS region SMM protection is enabled!

Warning: Setting Bios Control at 0xdc from 0xaa to 0x89 failed.

New value is 0xaa.

SPI Configuration is locked down.

FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only.

FREG2: Management Engine region (0x00003000-0x0027ffff) is locked.

Not all flash regions are freely accessible by flashrom. This is most likely

due to an active ME. Please see https://flashrom.org/ME for details.

At least some flash regions are read protected. You have to use a flash

layout and include only accessible regions. For write operations, you'll

additionally need the --noverify-all switch. See manpage for more details.

Enabling hardware sequencing because some important opcode is locked.

PROBLEMS, continuing anyway

Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000.

No operations were specified.


-------------------------------------------------------------------------------

sudo flashrom -p internal -r /home/bk1.bin

flashrom v1.2 on Linux 5.19.0-15-generic (x86_64)

flashrom is free software, get the source code at https://flashrom.org


Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).

Found chipset "Intel H170".

This chipset is marked as untested. If you are using an up-to-date version

of flashrom *and* were (not) able to successfully update your firmware with it,

then please email a report to flashrom@flashrom.org including a verbose (-V) log.

Thank you!

Enabling flash write... Warning: BIOS region SMM protection is enabled!

Warning: Setting Bios Control at 0xdc from 0xaa to 0x89 failed.

New value is 0xaa.

SPI Configuration is locked down.

FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only.

FREG2: Management Engine region (0x00003000-0x0027ffff) is locked.

Not all flash regions are freely accessible by flashrom. This is most likely

due to an active ME. Please see https://flashrom.org/ME for details.

At least some flash regions are read protected. You have to use a flash

layout and include only accessible regions. For write operations, you'll

additionally need the --noverify-all switch. See manpage for more details.

Enabling hardware sequencing because some important opcode is locked.

PROBLEMS, continuing anyway

Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000.

Reading flash... Transaction error between offset 0x00003000 and 0x0000303f (= 0x00003000 + 63)!

Read operation failed!

FAILED.


-------------------------------------------------------------------------------

sudo flashrom --programmer internal -r /home/bk1.bin -i bios --ifd

sudo flashrom -p internal -r /home/bk2.bin -i bios --ifd

sudo flashrom -p internal -r /home/bk3.bin -i bios --ifd

sudo flashrom -p internal -r /home/bk4.bin -i bios --ifd


sudo flashrom -p internal -v /home/bk4.bin -i bios --ifd


md5sum bk1.bin bk2.bin bk3.bin bk4.bin a3403.bin

8dccbad887dc112574a8999713029b7a  bk1.bin

8dccbad887dc112574a8999713029b7a  bk2.bin

8dccbad887dc112574a8999713029b7a  bk3.bin

8dccbad887dc112574a8999713029b7a  bk4.bin

058bce361fd03ef3f9de2285dd12e5b4  a3403.bin

-------------------------------------------------------------------------------


sudo flashrom -p internal -w /home/a3403.bin -i bios --ifd --noverify-all

flashrom v1.2 on Linux 5.19.0-15-generic (x86_64)

flashrom is free software, get the source code at https://flashrom.org


Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).

Found chipset "Intel H170".

This chipset is marked as untested. If you are using an up-to-date version

of flashrom *and* were (not) able to successfully update your firmware with it,

then please email a report to flashrom@flashrom.org including a verbose (-V) log.

Thank you!

Enabling flash write... Warning: BIOS region SMM protection is enabled!

Warning: Setting Bios Control at 0xdc from 0xaa to 0x89 failed.

New value is 0xaa.

SPI Configuration is locked down.

FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only.

FREG2: Management Engine region (0x00003000-0x0027ffff) is locked.

Not all flash regions are freely accessible by flashrom. This is most likely

due to an active ME. Please see https://flashrom.org/ME for details.

At least some flash regions are read protected. You have to use a flash

layout and include only accessible regions. For write operations, you'll

additionally need the --noverify-all switch. See manpage for more details.

Enabling hardware sequencing because some important opcode is locked.

PROBLEMS, continuing anyway

Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000.

Reading ich descriptor... done.

Using region: "bios".

Reading old flash chip contents... done.

Erasing and writing flash chip... Transaction error between offset 0x00280000 and 0x00280fff (= 0x00280000 + 4095)!

Reading current flash chip contents... done. Looking for another erase function.

Looking for another erase function.

Looking for another erase function.

Looking for another erase function.

Looking for another erase function.

Looking for another erase function.

Looking for another erase function.

No usable erase functions left.

FAILED!

Uh oh. Erase/write failed.

Your flash chip is in an unknown state.

Get help on IRC at chat.freenode.net (channel #flashrom) or

mail flashrom@flashrom.org with the subject "FAILED: <your board name>"!

-------------------------------------------------------------------------------

DO NOT REBOOT OR POWEROFF!

root@kubuntu:/home#


https://x86sec.com/posts/2022/09/08/removing-intel-ME-on-x1-carbon/

No comments:

Post a Comment