* Serguei Miridonov <mirsev@cicese.mx> wrote:
> What are the key parameters of mtd device 
> which are necessary to start the scanning? I know that page size is 
> 4096 bytes. With hex dump I can see object headers and data chunks. 
> But I could not find anything like spare areas, so I don't even know 
> where tags, like objectId, are located.

Having the contents of the spare areas is (usually) essential, in
order to get the YAFFS tags; without those you don't know the order in
which chunks were written and it would be impossible to properly
recreate the filesystem.

You need to know the exact format of the mtd dump - what tool has created
it? It's just about conceivable that the spare areas for all the chunks 
are sitting at the end of the file. 

It's also just about possible that the filesystem was created with the
inband_tags mode, in which case you don't need the spare areas and you'll
find the tags occupying the last 16 bytes of each chunk's data.

unyaffs is probably the best tool for the job, but you'll need to tweak
it when you've figured out where the tags are.

Ross