MBP early 2011 flash reading problems

Hi guys
Im new to this forum but Im hoping you can help me. I have got MBP early 2011 with efi password on. tried to read my chip flash but getting message
"This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the content of this chip (see main page for details)"
Reading flash... Error: opening file "/home/pi/efi/read1.bin" failed: No such file or directory

MacBook Pro 2011
A1278
EMC 2419
chip: MX25L6406E

Looks like you´re using the wrong command. Try something like
sudo flashrom -p linux_spi:dev=/dev/spidev0.0 -c "MX25L6406E" -r /flashrom/efi/read1.bin

or rather
sudo flashrom -p linux_spi:dev=/dev/spidev0.0 -c "MX25L6406E/MX25L6408E" -r /flashrom/efi/read1.bin

type command as you did but leave out the efi section, it will put dump in the pi directory...ive spent about 27 pretty much straight going through the same things lol
its because the efi folder is not in the image/flashrom directory

Of course you can´t write to an directory that don´t exists. Adjust the command to a directory that fits you

Ok
I have used the first command without ~/efi/ and it worked (I think) got the dump file and replaced everything after $SVS.
I'm just a bit worried about that message about one time programmable memory
Is this normal?

Buddy ive flashed the same chip about 9 times in the last 24hrs and at one point my programmer wouldnt even detect the chip, so dont panic...its the size of the file youre going to flash back to it that has to be right

Thanks
Will have a go and see what happens

Good luck and let us know how it worked out

Hi,

My head's seems to be somewhere else right now. I'm trying to erase and write my clean bin to an MacBook Air "Core i5" 1.7 13" (Mid-2011) EMC 2469 and ca't seem to get my commands in order.

To erase I use: sudo flashrom -E -V -p linux_spi:dev=/dev/spidev0.0 -c "MX25L6406E/MX25L6408E"

then I get:
flashrom was built with libpci 3.2.1, GCC 4.9.2, little endian
Command line (6 args): flashrom -E -V -p linux_spi:dev=/dev/spidev0.0 -c MX25L6406E/MX25L6408E
Calibrating delay loop... OS timer resolution is 3 usecs, 196M loops per second, 10 myus = 10 us, 100 myus = 102 us, 1000 myus = 989 us, 10000 myus = 9917 us, 12 myus = 15 us, OK.
Initializing linux_spi programmer
Using device /dev/spidev0.0
The following protocols are supported: SPI.
Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017
Found Macronix flash chip "MX25L6406E/MX25L6408E" (8192 kB, SPI) on linux_spi.
Chip status register is 0x00.
Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set
Chip status register: Bit 6 is not set
Chip status register: Block Protect 3 (BP3) is not set
Chip status register: Block Protect 2 (BP2) is not set
Chip status register: Block Protect 1 (BP1) is not set
Chip status register: Block Protect 0 (BP0) is not set
Chip status register: Write Enable Latch (WEL) is not set
Chip status register: Write In Progress (WIP/BUSY) is not set
This chip may contain one-time programmable memory. flashrom cannot read
and may never be able to write it, hence it may not be able to completely
clone the contents of this chip (see man page for details).

Can someone please privide me with erase and write command

Kindly Kim

At first try simply write modified file into chip with command:
sudo flashrom -p linux_spi:dev=/dev/spidev0.0 -c "MX25L6406E/MX25L6408E" -w <file_name>
Flashrom will erase blocks before data write, so you don't need to erase entire chip actually.
Try to disconnect pin 3 (WP) of the chip and leave 3.3v on pins 8 and 7

Brilliant. Thanks paul

No, still doesn't work. Won't go into to SU mode. How do I erase the chip?

YESSSS!!!!!! Massive THANK YOU to all of you guys. All working fine. Thanks a lot for all your help

Glad you got there in the end Alex

Nice Alex1982. And thank you again Paul for your help.

I got mine working to. Had everything done but I expected the MBA to start in superuser mode (cmd+r). But flashing the NVRAM (hold the Command-Option-P-R keys during startup) hit the spot and it started up as it should.