Did i read the wrong chip?

lxx33 wrote: When I scan-n-patch my file i got the following message.

File size: 0x003fffff (4194304) bytes. Record format type 1 detected
Image for 4 Mbytes flash chip
SVS Area not detected.

Is this because I download the wrong file, or is something else wrong.

sudo flashrom -p linux_spi:dev=/dev/spidev0.0
flashrom v0.9.9-r1954 on Linux 4.4.13+ (armv6l)
flashrom is free software, get the source code at https://flashrom.org

Calibrating delay loop... delay loop is unreliable, trying to continue OK.
Found Macronix flash chip "MX25L3205(A)" (4096 kB, SPI) on linux_spi.
Found Macronix flash chip "MX25L3205D/MX25L3208D" (4096 kB, SPI) on linux_spi.
Found Macronix flash chip "MX25L3206E/MX25L3208E" (4096 kB, SPI) on linux_spi.
Found Macronix flash chip "MX25L3273E" (4096 kB, SPI) on linux_spi.
Multiple flash chip definitions match the detected chip(s): "MX25L3205(A)", "MX25L3205D/MX25L3208D", "MX25L3206E/MX25L3208E", "MX25L3273E"
Please specify which chip definition to use with the -c <chipname> option.

I selected the MX25L3206E/MX25L3208E chip

hope somebody can help me

I always select the last chip on the list that it found.

What programmer are you using?

A couple suggestions for your problem...

If you are encountering issues with the "unexpected token" error then try "quoting" the chip model number. So instead of typing your command like:

sudo flashrom -r chip.bin -c MX25L3205(A) -p linux_spi:dev=/dev/spidev0.0

Try typing it like this:

sudo flashrom -r chip.bin -c "MX25L3205(A)" -p linux_spi:dev=/dev/spidev0.0

But I don't think the issue you're facing is related to the chip type being incorrect... In my experience I have typically always used the first possible chip type whenever I encounter an instance where there are multiple possibilities, and now reading Cygnus comment he always chooses the last possible chip type and I know he has success just as often. I was curious to see if there was any difference between specifying other chip types and I have went through and tried every possible chip type before on a single device and checked the hashes for each and they were all the same. I have even specified the EXACT chip type that was printed on the chip and tried to specify in my flashrom command and it wouldn't read it; the only way I could get flashrom to read it was to just run flashrom -p linux_spi:dev=/dev/spidev0.0 and use whatever options that flashrom THOUGHT the chip type was.

I have taken a look at all three of the files you have provided and each one of them is identical to the next. Also if you check the md5's for your files you would see that the hashes are all exactly identical as well (see pic I have attached), so specifying chip types (at least in the situations that we use flashrom for) does not change the dump in any way.





The link you have given (in the post with the attached video) no longer works, but I see in the URL that you are referencing an iMac with model number A1312. Here's a website that will help you in your Apple pursuit www.everymac.com use this as a tool for your arsenal. If you reference the model number A1312 on EveryMac then you will see that your iMac is a Core-2-Duo Late 2009 model. The EFI password on ANY Mac product from before 2011 can be easily removed by removing a RAM stick and resetting PRAM/NVRAM by powering on the device while holding Command+Option+R+P. In the case that you are using an iMac then you will need to connect an external keyboard to be able to complete this.

The reason the Scan-N-Patch script does not work for your model is the same reason why it will not work for all models prior to 2011: There is no $SVS area in the ROM dumps for any of these models.

Hey that's awesome!! I'm glad I was able to help! I just ran into a similar problem the other day so as soon as I took a look at your provided bin file I knew exactly what needed to happen I WISH I was in Amsterdam >.< never been to Europe though unfortunately :'( if you feel inclined to "Help me help you help us all" though click the link beneath any of my posts (totally not necessary, but would be greatly appreciated!!!) If you do choose to do so drop a good contact method for u in the notes and I'll respond with a direct line in case you ever need some help in the future I'll be able to respond much quicker!