Hi, i have the Easy Clip Adapter from Ghost. I already use the Raspberry Pi with pomona and flashrom in several ocations with perfect results in the past. This is my first test with the Easy Clip.
My Setup:
Motherboard efi chip says: 25L640EZNI-12GF
im Using Easy Clip Adapter
Using a 2A Samsung Power adapter
Motherboard has no power at all from any source.
Using -p it detect varios types
pi@raspberrypi:~ $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0 flashrom v0.9.9-unknown on Linux 4.4.13+ (armv6l)
flashrom is free software, get the source code at flashrom.org
Calibrating delay loop... delay loop is unreliable, trying to continue OK.
Found Macronix flash chip "MX25L6405" (8192 kB, SPI) on linux_spi.
Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.
Found Macronix flash chip "MX25L6406E/MX25L6408E" (8192 kB, SPI) on linux_spi.
Found Macronix flash chip "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E" (8192 kB, SPI) on linux_spi.
Multiple flash chip definitions match the detected chip(s): "MX25L6405", "MX25L6405D", "MX25L6406E/MX25L6408E", "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E"
Please specify which chip definition to use with the -c <chipname> option.
I can read the file perfectly,with:
sudo flashrom -r /tmp/romwrite0.bin -V -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -c MX25L6406E/MX25L6408E
But when i try to write the file, i recive ERASE FAILED! All the time.
Flashrom says:
No usable erase functions left.
FAILED!
Uh oh. Erase/write failed. Checking if anything has changed.
Reading current flash chip contents... done.
Good, writing to the flash chip apparently didn't do anything.
Please check the connections (especially those to write protection pins) between
the programmer and the flash chip. If you think the error is caused by flashrom
please report this on IRC at chat.freenode.net (channel #flashrom) or
mail , thanks!
That is a common error, although can seem frightening. Actually if you have watched the video in my Tutorial
which can be found here if you look close enough you'll see that I actually encounter that same error in the example that I show when I am first explaining how to erase and write to the chip. I just really didn't want to have to hook up my entire setup all over again to redo that portion of the video so I just edited that part to where you can only see it for just a split second lol. I've encountered this error a few times and honestly it used to freak me out and I'm sure that there really IS something happening that's preventing flashrom from working how we're all used to, but in my experience as long as I have been able to get a solid read from the chip, multiple times, and verify the md5's, then any time I encounter the ERASE FAILED I just continue onward with my usual progress and the Mac has always booted up for me no problem. PLEASE NOTE THAT THIS VERY WELL MAY NOT BE THE CASE FOR EVERYBODY!!! If your Mac does NOT boot afterwards then please let me know and I'll do my job better at helping get you taken care of
Hey I'm glad I could help you bro! I really wish I knew more about why that error occurs but the way I go about it is to just make sure that I am able to get a good copy of the chip first then if that error happens afterwards I usually just take it as a sign to push forward anyways. This could be giving out very bad advice right now still though because the error would not occur if nothing wrong had happened, but at least in our cases everything was alright
im working on same.. is your hcw section MD232LL ? i need that dump badly!.
my tips.. plug in programmer.. with power and batt .. unplug power cord and detect chip.
sometimes have to unplug battery too if it fails. unplug batt and power press power butt 30 sec. then retry .
the calibration loopback showed failed at first with mine on CH341A_spi usb
but im using -c "MX25L6406E/MX25L6408E"
but at second try with just batt but power cord plug on 1 time and unplug does the trick.. wish i had known this when i first went to make a dump and it bricked.
i think appl got wise to the clip and did something to this models with debugging dump protection.. for those that went overseas and leave their mbairs in hotel when they go to lounge and not let spy maids root the efi.
This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.
You have declined cookies. This decision can be reversed.
You have allowed cookies to be placed on your computer. This decision can be reversed.
This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.
