flashrom January 2014

flashrom@flashrom.org

28 participants
73 discussions

HP AAHD3-H8 Motherboard flashing with Uno
by Elvis Kit 21 Jan '14

21 Jan '14

Hello, I am getting this error message when i attempt to re-flash the bricked bios of this motherboard. Any help would be greatly appreciated! e6410 Test # flashrom -p serprog:dev=/dev/ttyACM0:2000000 -w HIB_716.ROM flashrom v0.9.7-r1764 on Linux 3.2.0-4-486 (i686) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. serprog: Programmer name is "serprog-duino" Found Winbond flash chip "W25Q16.V" (2048 kB, SPI) on serprog. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00000fff: 0x1000 ERASE FAILED! Reading current flash chip contents... done. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00007fff: 0x8000 ERASE FAILED! Reading current flash chip contents... Error: invalid response 0x00 from device Can't read anymore! Aborting. FAILED! Uh oh. Erase/write failed. Checking if anything changed. Error: invalid response 0x00 from device Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! Thanks in advance! Rob Stewart

1 0

Re: [flashrom] F2A85-M with flashrom
by HacKurx 20 Jan '14

20 Jan '14

Hi, Thank you for the informations. I just tested with succes flashrom on the versions 6002, 6004, 6102, 6402. Only the 6404 version does not work with flashrom and it is the only version that has the printable character sequence "SecureBootSetup"... I still have a few things to do with coreboot. Thank you very much. Best regards, 2014/1/18 Idwer Vollering <vidwer(a)gmail.com>: > Please include the mailinglist on the To: field hereafter, thanks :) > > 2014/1/18 HacKurx <hackurx(a)gmail.com>: >> Hello, >> >> I have a error with flashrom on f2a85_m : >> ERROR: State of SpiAccessMacRomEn or SpiHostAccessRomEn prohibits full access. >> >> flashrom --programmer internal -r sauvegarde-bios.rom >> flashrom v0.9.7-r1720 on Linux 3.12.7 (x86_64) >> flashrom is free software, get the source code at http://www.flashrom.org >> >> Calibrating delay loop... OK. >> Found chipset "AMD FCH". Enabling flash write... ERROR: State of >> SpiAccessMacRomEn or SpiHostAccessRomEn prohibits full access. >> PROBLEMS, continuing anyway >> No EEPROM/flash device found. >> Note: flashrom can never write if the flash chip isn't found automatically. >> >> How to solve this problem? > > I ran into this too, and found out that F2A85M's BIOS v6404 prohibits > access where v5018 (the version that was preloaded on my board) does > not. > > I haven't tried whether any other build (5103 or 5104 or 51047 or 5202 > or 6002 or 6004 or 6102 or 6402) blocks full access. > > To solve this problem: either downgrade or read the chip using (a > breadboard and) an external programmer. > >> >> Thanks, Best regards, >> >> Loic >> http://hackurx.wordpress.com > > HTH, > > Idwer -- Best regards, HacKurx www.hackurx.info

1 0

Re: [flashrom] F2A85-M with flashrom
by Idwer Vollering 18 Jan '14

18 Jan '14

Please include the mailinglist on the To: field hereafter, thanks :) 2014/1/18 HacKurx <hackurx(a)gmail.com>: > Hello, > > I have a error with flashrom on f2a85_m : > ERROR: State of SpiAccessMacRomEn or SpiHostAccessRomEn prohibits full access. > > flashrom --programmer internal -r sauvegarde-bios.rom > flashrom v0.9.7-r1720 on Linux 3.12.7 (x86_64) > flashrom is free software, get the source code at http://www.flashrom.org > > Calibrating delay loop... OK. > Found chipset "AMD FCH". Enabling flash write... ERROR: State of > SpiAccessMacRomEn or SpiHostAccessRomEn prohibits full access. > PROBLEMS, continuing anyway > No EEPROM/flash device found. > Note: flashrom can never write if the flash chip isn't found automatically. > > How to solve this problem? I ran into this too, and found out that F2A85M's BIOS v6404 prohibits access where v5018 (the version that was preloaded on my board) does not. I haven't tried whether any other build (5103 or 5104 or 51047 or 5202 or 6002 or 6004 or 6102 or 6402) blocks full access. To solve this problem: either downgrade or read the chip using (a breadboard and) an external programmer. > > Thanks, Best regards, > > Loic > http://hackurx.wordpress.com HTH, Idwer

1 0

Please support my laptop!
by Max Stevens 17 Jan '14

17 Jan '14

Here's the output of flashrom -V -p internal

1 0

W836xx: Latitude E4300: flashrom -V
by Spudnik＠sbcglobal.net 15 Jan '14

15 Jan '14

flashrom v0.9.6.1-r1564 on Linux 3.2.0-52-generic (x86_64) flashrom is free software,get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.0, GCC 4.7.3 little endian Command line ( args): flashrom -V

1 0

Re: [flashrom] Trouble disabling write-protection on Chromebook
by David Hendricks 14 Jan '14

14 Jan '14

On Tue, Jan 14, 2014 at 8:23 AM, Cory Henderson <dcoryh192(a)gmail.com> wrote: > With the chromebook powered on (be careful), and your multimeter in DC > volt mode, touch one probe to any metallic part of the computer chassis or > any known ground (could even use the ground pin of the flash), then touch > the other probe to the /WP pin (there was a datasheet sent out before with > pictures of all of the different packages and their pinouts). If your meter > reads 0V then the pin is being pulled down and the hardware /WP is being > enforced. If it reads 1.8V or something around there then it might be a bad > chip or something off in flashrom. > Yep, that's exactly right. For reference, here is the datasheet link posted earlier: http://www.winbond-usa.com/hq/enu/ProductAndSales/ProductLines/FlashMemory/… . The chip layout is on page 6--We're using the SOIC 208-mil package. The black dot which indicates pin 1 corresponds with a small dimple on the chip itself (and perhaps a white dot silkscreened on the mainboard PCB). IIRC this system is using the 1.8V chip, but it could be 3.3V. The procedure Cory outlined is correct, in either case. -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

Re: [flashrom] Trouble disabling write-protection on Chromebook
by BM-2cWKH3wgq8zXX9eHfba16oTc8b61ead4Yq＠bitmessage.ch 14 Jan '14

14 Jan '14

> Darn, still no luck then... > > Well, I guess all that's left is to try finding a multimeter and seeing > if > /WP is being held low somehow. Also, do you have an external programmer > such as a Bus Pirate? > I now have a Bus Pirate. I also have a multimeter. What is the best way to check if /WP is being held low?

2 1

Re: [flashrom] Failed flash
by Stefan Tauner 14 Jan '14

14 Jan '14

On Mon, 13 Jan 2014 17:02:02 -0500 Paul <langpenguin(a)gmail.com> wrote: > Is it safe to > reboot? no. Try writing the backup you made with flashrom -r/--read before you wrote the new image. If that is successful you can reboot/shut down etc. Which device are you using? -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Failed flash
by Paul 13 Jan '14

13 Jan '14

It failed. I might not have the write protector connected. Is it safe to reboot? Penagwin flashrom v0.9.4 : d02ee0f : Nov 02 2013 00:09:09 UTC on Linux 3.4.0 (x86_64), built with libpci 3.1.10, GCC 4.7.x-google 20130114 (prerelease), little endian Block protection could not be disabled! Erasing and writing flash chip... spi_block_erase_20 failed during command execution at address 0x0 ERASE FAILED at 0x00400000! Expected=0xff, Read=0x00, failed byte count from 0x00400000-0x00400fff: 0x1000 ERASE FAILED! Reading current flash chip contents... spi_block_erase_52 failed during command execution at address 0x0 ERASE FAILED at 0x00400000! Expected=0xff, Read=0x00, failed byte count from 0x00400000-0x00407fff: 0x8000 ERASE FAILED! Reading current flash chip contents... spi_block_erase_d8 failed during command execution at address 0x0 ERASE FAILED at 0x00400000! Expected=0xff, Read=0x00, failed byte count from 0x00400000-0x0040ffff: 0x10000 ERASE FAILED! Reading current flash chip contents... spi_chip_erase_60 failed during command execution ERASE FAILED! Reading current flash chip contents... spi_chip_erase_c7 failed during command execution ERASE FAILED! FAILED! Uh oh. Erase/write failed. Checking if anything changed. Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with FAILED: your board name in the subject line! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! FAILED

1 0

Problems with Jetway Board and Winbond chip
by HaMa 09 Jan '14

09 Jan '14

Hey there… first of all: Thank you for that incredible flashrom tool. But sadly: I can not write my BIOS chip on my Jetway Board. I got a Jetway NC96FL Mainboard with a Winbond W25Q80BV BIOS Chip, Intel NM10 Chipset and running Ubuntu 10.10. Flashrom detects the chip and the chipset well, but can not disable block protection. So it is not possible to write. I also tried to flash the chip with the Serprog/Arduino-Flasher on an Arduino Uno and it works. (But I want to burn it with my Jetway Board.) Then I tried to write it in my Jetway Board with manual raising the /WP-Pin of the Winbond Chip to VCC and it works too. So is it something (GPIO) to raise the /WP-Pin in the chipset? Can somebody help me? I attached the logs from: $ flashrom -p internal -V (flash.log) $ lspci -nnvvxxx (lspci.log) $ superiotool -deV (superio.log) Thanks a lot, Hans-Martin

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom January 2014