p.s. i havent rebooted yet so idk if its bricked or not anvil@t430:~ $ sudo ./Downloads/skulls-1.1.3/skulls.sh -b t430 [sudo] password for anvil: Sorry, try again. [sudo] password for anvil: 1) ./t430_coreboot_seabios_free_4931b978d9_top.rom 2) Quit file not specified. Please select a file to flash. Please read the README for details about the differences: 1 t430_coreboot_seabios_free_4931b978d9_top.rom: OK Flash the BIOS now? y/N: y flashrom 1.4.0 on Linux 7.0.14-2-liquorix-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Using region: "bios". Found chipset "Intel QM77". Enabling flash write... SPI Configuration is locked down. FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only. FREG1: BIOS region (0x00500000-0x00bfffff) is read-write. FREG2: Management Engine region (0x00003000-0x004fffff) is locked. FREG3: Gigabit Ethernet region (0x00001000-0x00002fff) is read-write. 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. PR1: Warning: 0x00b40000-0x00bfffff is read-only. PR2: Warning: 0x00b10000-0x00b10fff is read-only. PR3: Warning: 0x00ad0000-0x00adefff is read-only. PR4: Warning: 0x00800000-0x00aaffff is read-only. 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 due to multiple flash chips detected. OK. Multiple flash components detected, skipping flash identification. Found Programmer flash chip "Opaque flash chip" (12288 kB, Programmer-specific) on internal. Reading old flash chip contents... done. Transaction error between offset 0x00800000 and 0x00800000 (= 0x00800000 + 0)! Erase/write done from 800000 to bfffff Write Failed!Uh oh. Erase/write failed. Your flash chip is in an unknown state. Get help on IRC (see https://www.flashrom.org/Contact) or mail flashrom@flashrom.org with the subject "FAILED: <your board name>"!------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF!
Looks like it didn't do anything, since the PR4 warning line says the address range you're trying to write is read-only and it failed while erasing. You'll need to remove write protection in order to flash it, and I expect rebooting is safe. On Fri, Jul 31, 2026 at 10:51 AM nyangela--- via flashrom < flashrom@flashrom.org> wrote:
p.s. i havent rebooted yet so idk if its bricked or not
anvil@t430:~ $ sudo ./Downloads/skulls-1.1.3/skulls.sh -b t430 [sudo] password for anvil: Sorry, try again. [sudo] password for anvil: 1) ./t430_coreboot_seabios_free_4931b978d9_top.rom 2) Quit file not specified. Please select a file to flash. Please read the README for details about the differences: 1 t430_coreboot_seabios_free_4931b978d9_top.rom: OK Flash the BIOS now? y/N: y flashrom 1.4.0 on Linux 7.0.14-2-liquorix-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org
Using region: "bios". Found chipset "Intel QM77". Enabling flash write... SPI Configuration is locked down. FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only. FREG1: BIOS region (0x00500000-0x00bfffff) is read-write. FREG2: Management Engine region (0x00003000-0x004fffff) is locked. FREG3: Gigabit Ethernet region (0x00001000-0x00002fff) is read-write. 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. PR1: Warning: 0x00b40000-0x00bfffff is read-only. PR2: Warning: 0x00b10000-0x00b10fff is read-only. PR3: Warning: 0x00ad0000-0x00adefff is read-only. PR4: Warning: 0x00800000-0x00aaffff is read-only. 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 due to multiple flash chips detected. OK. Multiple flash components detected, skipping flash identification. Found Programmer flash chip "Opaque flash chip" (12288 kB, Programmer-specific) on internal. Reading old flash chip contents... done. Transaction error between offset 0x00800000 and 0x00800000 (= 0x00800000 + 0)! Erase/write done from 800000 to bfffff Write Failed!Uh oh. Erase/write failed. Your flash chip is in an unknown state. Get help on IRC (see https://www.flashrom.org/Contact) or mail flashrom@flashrom.org with the subject "FAILED: <your board name>"!------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF!
_______________________________________________ flashrom mailing list -- flashrom@flashrom.org To unsubscribe send an email to flashrom-leave@flashrom.org
participants (2)
-
nyangela＠tuta.io -
Peter Marheine