*** Already downloaded! ***
*** Backing up existing ROM to current directory ***
flashrom v0.9.4 : 14ce0cf : Oct 09 2013 22:16:28 UTC on Linux 3.16.1-1-ARCH (x86_64), built with libpci 3.1.10, GCC 4.7.x-google 20130114 (prerelease), little endian w25q_disable_writeprotect(): error=1. FAILED
*** Downloading latest available custom ROM for Peppy ***
*** Already downloaded! ***
--2014-08-19 17:42:40-- https://johnlewis.ie/Chromebook-ROMs/md5sums.txt Resolving johnlewis.ie (johnlewis.ie)... 37.187.3.40 Connecting to johnlewis.ie (johnlewis.ie)|37.187.3.40|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 4941 (4.8K) [text/plain] Saving to: ‘md5sums.txt’
100%[==============================================================================================================================>] 4,941 --.-K/s in 0s
2014-08-19 17:42:41 (479 MB/s) - ‘md5sums.txt’ saved [4941/4941]
About to flash new ROM, repeat 'If this bricks my Chromebook/box, on my head be it!' observing exact case and punctuation: If this bricks my Chromebook/box, on my head be it!
dd: failed to open ‘backup-190814.rom’: No such file or directory flashrom v0.9.4 : 14ce0cf : Oct 09 2013 22:16:28 UTC on Linux 3.16.1-1-ARCH (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 0x00600000! Expected=0xff, Read=0x5f, failed byte count from 0x00600000-0x00600fff: 0x148 ERASE FAILED! Reading current flash chip contents... spi_block_erase_52 failed during command execution at address 0x0 ERASE FAILED! Reading current flash chip contents... spi_block_erase_d8 failed during command execution at address 0x0 ERASE FAILED at 0x00600000! Expected=0xff, Read=0x5f, failed byte count from 0x00600000-0x0060ffff: 0x148 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@flashrom.org with FAILED: your board name in the subject line! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! FAILED
*** Assuming you didn't get any errors beyond the ubiquitous 'spi_block_erase_20 failed during command execution at address 0×0 Verifying flash… VERIFY FAILED at 0×00000062! Expected=0xff, Read=0x0b, failed byte count from 0×00000000-0x007fffff: 0×4' you may reboot. Otherwise, do not reboot under ANY circumstances, and seek help! ***
On Tue, 19 Aug 2014 18:01:39 +0200 Gerard Looije jglooije@hotmail.com wrote:
*** Already downloaded! ***
*** Backing up existing ROM to current directory ***
flashrom v0.9.4 : 14ce0cf : Oct 09 2013 22:16:28 UTC on Linux 3.16.1-1-ARCH (x86_64), built with libpci 3.1.10, GCC 4.7.x-google 20130114 (prerelease), little endian w25q_disable_writeprotect(): error=1. FAILED
*** Downloading latest available custom ROM for Peppy ***
*** Already downloaded! ***
--2014-08-19 17:42:40-- https://johnlewis.ie/Chromebook-ROMs/md5sums.txt Resolving johnlewis.ie (johnlewis.ie)... 37.187.3.40 Connecting to johnlewis.ie (johnlewis.ie)|37.187.3.40|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 4941 (4.8K) [text/plain] Saving to: ‘md5sums.txt’
100%[==============================================================================================================================>] 4,941 --.-K/s in 0s
2014-08-19 17:42:41 (479 MB/s) - ‘md5sums.txt’ saved [4941/4941]
About to flash new ROM, repeat 'If this bricks my Chromebook/box, on my head be it!' observing exact case and punctuation: If this bricks my Chromebook/box, on my head be it!
dd: failed to open ‘backup-190814.rom’: No such file or directory flashrom v0.9.4 : 14ce0cf : Oct 09 2013 22:16:28 UTC on Linux 3.16.1-1-ARCH (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 0x00600000! Expected=0xff, Read=0x5f, failed byte count from 0x00600000-0x00600fff: 0x148 ERASE FAILED! Reading current flash chip contents... spi_block_erase_52 failed during command execution at address 0x0 ERASE FAILED! Reading current flash chip contents... spi_block_erase_d8 failed during command execution at address 0x0 ERASE FAILED at 0x00600000! Expected=0xff, Read=0x5f, failed byte count from 0x00600000-0x0060ffff: 0x148 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@flashrom.org with FAILED: your board name in the subject line!
DO NOT REBOOT OR POWEROFF! FAILED
*** Assuming you didn't get any errors beyond the ubiquitous 'spi_block_erase_20 failed during command execution at address 0×0 Verifying flash… VERIFY FAILED at 0×00000062! Expected=0xff, Read=0x0b, failed byte count from 0×00000000-0x007fffff: 0×4' you may reboot. Otherwise, do not reboot under ANY circumstances, and seek help! ***
Hi
I don't (want to) know John's script in detail, but apparently it continues if making a backup fails which IMHO is a bad idea. Was there a backup file created, did you make a backup yourself by chance? Can you please send a verbose log of flashrom just probing for the flash chip (e.g. flashrom -V)?
On 21/08/14 08:00, Stefan Tauner wrote:
On Tue, 19 Aug 2014 18:01:39 +0200 Gerard Looije jglooije@hotmail.com wrote:
*** Already downloaded! ***
*** Backing up existing ROM to current directory ***
flashrom v0.9.4 : 14ce0cf : Oct 09 2013 22:16:28 UTC on Linux 3.16.1-1-ARCH (x86_64), built with libpci 3.1.10, GCC 4.7.x-google 20130114 (prerelease), little endian w25q_disable_writeprotect(): error=1. FAILED
*** Downloading latest available custom ROM for Peppy ***
*** Already downloaded! ***
--2014-08-19 17:42:40-- https://johnlewis.ie/Chromebook-ROMs/md5sums.txt Resolving johnlewis.ie (johnlewis.ie)... 37.187.3.40 Connecting to johnlewis.ie (johnlewis.ie)|37.187.3.40|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 4941 (4.8K) [text/plain] Saving to: ‘md5sums.txt’
100%[==============================================================================================================================>] 4,941 --.-K/s in 0s
2014-08-19 17:42:41 (479 MB/s) - ‘md5sums.txt’ saved [4941/4941]
About to flash new ROM, repeat 'If this bricks my Chromebook/box, on my head be it!' observing exact case and punctuation: If this bricks my Chromebook/box, on my head be it!
dd: failed to open ‘backup-190814.rom’: No such file or directory flashrom v0.9.4 : 14ce0cf : Oct 09 2013 22:16:28 UTC on Linux 3.16.1-1-ARCH (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 0x00600000! Expected=0xff, Read=0x5f, failed byte count from 0x00600000-0x00600fff: 0x148 ERASE FAILED! Reading current flash chip contents... spi_block_erase_52 failed during command execution at address 0x0 ERASE FAILED! Reading current flash chip contents... spi_block_erase_d8 failed during command execution at address 0x0 ERASE FAILED at 0x00600000! Expected=0xff, Read=0x5f, failed byte count from 0x00600000-0x0060ffff: 0x148 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@flashrom.org with FAILED: your board name in the subject line!
DO NOT REBOOT OR POWEROFF! FAILED
*** Assuming you didn't get any errors beyond the ubiquitous 'spi_block_erase_20 failed during command execution at address 0×0 Verifying flash… VERIFY FAILED at 0×00000062! Expected=0xff, Read=0x0b, failed byte count from 0×00000000-0x007fffff: 0×4' you may reboot. Otherwise, do not reboot under ANY circumstances, and seek help! ***
Hi
I don't (want to) know John's script in detail, but apparently it continues if making a backup fails which IMHO is a bad idea. Was there a backup file created, did you make a backup yourself by chance? Can you please send a verbose log of flashrom just probing for the flash chip (e.g. flashrom -V)?
Hi Stefan,
I'm not entirely convinced that's necessary from a technical safety point of view, since I'm unaware of circumstances under which Flashrom will not read a chip, but will still write to it. However, I've added something in an attempt to exit out if the status is non-zero.
I'm unsure as to why this user is contacting you when this is my script.
On Thu, 21 Aug 2014 10:04:43 +0100 John Lewis jlewis@johnlewis.ie wrote:
I'm not entirely convinced that's necessary from a technical safety point of view, since I'm unaware of circumstances under which Flashrom will not read a chip, but will still write to it. However, I've added something in an attempt to exit out if the status is non-zero.
I am not sure about chromiumos' version of flashrom, but I guess it will behave similar to vanilla flashrom: if it can't read the flash completely, it won't succeed in writing either (apart from file access problems for example).
I'm unsure as to why this user is contacting you when this is my script.
I presume because the flashrom output told him so. That's the reason why I have created the patch to change the support mail address printed by flashrom. I have sent a copy of the patch submission mail to you too BTW.
On 21/08/14 11:54, Stefan Tauner wrote:
On Thu, 21 Aug 2014 10:04:43 +0100 John Lewis jlewis@johnlewis.ie wrote:
I'm not entirely convinced that's necessary from a technical safety point of view, since I'm unaware of circumstances under which Flashrom will not read a chip, but will still write to it. However, I've added something in an attempt to exit out if the status is non-zero.
I am not sure about chromiumos' version of flashrom, but I guess it will behave similar to vanilla flashrom: if it can't read the flash completely, it won't succeed in writing either (apart from file access problems for example).
I have made a vague attempt at dealing with file access problems, like writing, but it does rely on the user copying and pasting correctly.
I'm unsure as to why this user is contacting you when this is my script.
I presume because the flashrom output told him so. That's the reason why I have created the patch to change the support mail address printed by flashrom. I have sent a copy of the patch submission mail to you too BTW.
Still, it's a bit like contacting the dd developer because dd is used in the script. And I guess that's why things like email addresses shouldn't be hard-coded (at least outside of scripts).
I did see the patches thank you, but, my concern is having to use the CrOS dev environment to change the ebuild and recompile, as compiling outside that environment seems more problematic. It would be much easier from my point of view if there were no email address/IRC info or it were able to be defined with a command line parameter.
In the meantime, I'm going to use an inverted grep to blank that output and see if I can make some of the script messages a bit more obvious as to where help should be sought.
John.
-
Gerard Looije -
John Lewis -
Stefan Tauner