Not able to extract google built binaries

[GoogleCodeExporter]

What steps will reproduce the problem?
1. I downloaded the binary from 
https://dl.google.com/dl/android/aosp/tungsten-ian67k-factory-468d9865.tgz
2. Extracted the update.zip and unzipped it to get a system.img
3. Used the following commandline 2 commandlines to try and get the contents of 
the binary.

./unyaffs2 --verbose --yaffs-ecclayout ../system.img test-yaffs2
./unyaffs2 --verbose -e --yaffs-ecclayout ../system.img test-yaffs2 

What is the expected output? What do you see instead?
both fail. The second one does not give me any errors but no contents in the 
destination directory.

What version of the product are you using? On what operating system?
2.9 with the patch that was there in issue 28.

Please provide any additional information below.
It may be just that these binaries have somekind of header. I think this would 
be the case since I am able to use the binary that I built using the AOSP setup.

Please feel free to get more info if needed.

BR
Kozak

Original issue reported on code.google.com by c.a.subr...@gmail.com on 10 Dec 2012 at 6:50

[GoogleCodeExporter]

Dear,

In my opinion, the file "system.img" may not the YAFFS2 format.
But I will try double checking its correct file format, after work. 

Have a nice day. :D

Original comment by penguin.lin on 11 Dec 2012 at 1:57

[GoogleCodeExporter]

Thank you for your prompt response. I am pretty sure the img that AOSP 
generates is a yaffs2 image. And hence the one that Google releases should also 
be a yaffs2 one. BTW, really cool tool you developed. Thanks for sharing.
BR
Kozak

Original comment by c.a.subr...@gmail.com on 11 Dec 2012 at 3:45