Support extraction of YAFFS

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Try to extract firmware containing yaffs filesystem

Any chance of YAFFS support?

Firmware Mod Kit (extract) 0.87, (c)2011-2013 Craig Heffner, Jeremy Collake

Scanning firmware...

Scan Time:     2013-05-28 16:21:38
Signatures:    193
Target File:   
/media/shares/Deuterium/RevEng/Philips/BDP3200-79/Firmware/Original/bdp3200_79_f
us_eng/UPG_ALL/BDP_3200_T.BIN
MD5 Checksum:  3b5eee59f087c38f2a681d9a3111e452

DECIMAL         HEX             DESCRIPTION
--------------------------------------------------------------------------------
-----------------------
68170           0x10A4A         Mediatek bootloader
95162           0x173BA         Mediatek bootloader
335416          0x51E38         LZMA compressed data, properties: 0x02, 
dictionary size: 16777216 bytes, uncompressed size: 16804096 bytes
392451          0x5FD03         LZMA compressed data, properties: 0x0B, 
dictionary size: 33554432 bytes, uncompressed size: 1376252 bytes
392471          0x5FD17         LZMA compressed data, properties: 0x0B, 
dictionary size: 33554432 bytes, uncompressed size: 1114108 bytes
418903          0x66457         LZMA compressed data, properties: 0x02, 
dictionary size: 1048576 bytes, uncompressed size: 1073741824 bytes
418927          0x6646F         LZMA compressed data, properties: 0x02, 
dictionary size: 1048576 bytes, uncompressed size: 1073741824 bytes
418999          0x664B7         LZMA compressed data, properties: 0x02, 
dictionary size: 2097152 bytes, uncompressed size: 1073741824 bytes
419023          0x664CF         LZMA compressed data, properties: 0x02, 
dictionary size: 2097152 bytes, uncompressed size: 1073741824 bytes
419095          0x66517         LZMA compressed data, properties: 0x02, 
dictionary size: 4194304 bytes, uncompressed size: 1073741824 bytes
419119          0x6652F         LZMA compressed data, properties: 0x02, 
dictionary size: 4194304 bytes, uncompressed size: 1073741824 bytes
419191          0x66577         LZMA compressed data, properties: 0x02, 
dictionary size: 8388608 bytes, uncompressed size: 1073741824 bytes
419215          0x6658F         LZMA compressed data, properties: 0x02, 
dictionary size: 8388608 bytes, uncompressed size: 1073741824 bytes
419239          0x665A7         LZMA compressed data, properties: 0x02, 
dictionary size: 8388608 bytes, uncompressed size: 1073741824 bytes
419359          0x6661F         LZMA compressed data, properties: 0x02, 
dictionary size: 16777216 bytes, uncompressed size: 1073741824 bytes
425418          0x67DCA         uImage header, header size: 64 bytes, header 
CRC: 0xF33A5223, created: Wed Sep 12 16:15:30 2012, image size: 1543416 bytes, 
Data Address: 0xDA00000, Entry Point: 0xDA00000, data CRC: 0xBF9A9C57, OS: 
Linux, CPU: ARM, image type: OS Kernel Image, compression type: none, image 
name: ""
442274          0x6BFA2         gzip compressed data, from Unix, last modified: 
Wed Sep 12 16:11:23 2012, max compression
1968906         0x1E0B0A        gzip compressed data, was "initrd.img", from 
Unix, last modified: Wed Sep 12 16:36:37 2012
3339994         0x32F6DA        Squashfs filesystem, little endian, version 
3.1, size: 24681197 bytes,  142 inodes, blocksize: 131072 bytes, created: Wed 
Sep 12 16:36:40 2012
48359130        0x2E1E6DA       PNG image, 1920 x 1080, 8-bit/color RGBA, 
non-interlaced
50253993        0x2FED0A9       LZMA compressed data, properties: 0x04, 
dictionary size: 33554432 bytes, uncompressed size: 67305984 bytes
50284674        0x2FF4882       LZMA compressed data, properties: 0x0B, 
dictionary size: 16777216 bytes, uncompressed size: 67108864 bytes
50284786        0x2FF48F2       YAFFS filesystem
50284818        0x2FF4912       LZMA compressed data, properties: 0x0A, 
dictionary size: 16777216 bytes, uncompressed size: 134217728 bytes
50284882        0x2FF4952       LZMA compressed data, properties: 0x0B, 
dictionary size: 16777216 bytes, uncompressed size: 1073741824 bytes
50285042        0x2FF49F2       LZMA compressed data, properties: 0x04, 
dictionary size: 16777216 bytes, uncompressed size: 268435456 bytes
50285234        0x2FF4AB2       LZMA compressed data, properties: 0x13, 
dictionary size: 16777216 bytes, uncompressed size: 1073741824 bytes

Extracting 50284786 bytes of  header image at offset 0
Extracting yaffs file system at offset 50284786
Extracting 512 byte footer from offset 50761660
Unsupported file system 'yaffs'! Quitting...

Original issue reported on code.google.com by volta...@voltagex.org on 28 May 2013 at 12:19

[GoogleCodeExporter]

Good call. I'll put this on my agenda. For reference, YAFFS extraction/build 
utility is here: https://code.google.com/p/yaffs2utils/

Original comment by jeremy.collake@gmail.com on 30 May 2013 at 11:52

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I got the same message too when i tried to extract modem.bin file of Huawie 
b593u-91 router
I hope is there away to get this supported in Firmware-mod-kit

Original comment by tab.sa...@gmail.com on 22 Jun 2013 at 1:48

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I tossed in yaffs2 support to the package and scripts, but have not even tested 
it the slightest bit ... provide a URL to this firmware image and I'll at least 
make sure it seems to work.

Original comment by jeremy.collake@gmail.com on 25 Jun 2013 at 2:01

• Changed state: Started

[GoogleCodeExporter]

Though there is a second problem here ... this image has two filesystems.. the 
scripts don't support that at all. They'll have to be redesigned for that

Original comment by jeremy.collake@gmail.com on 25 Jun 2013 at 2:02

[GoogleCodeExporter]

you are right about two filesystems .... in the first its start extracting 
without any problem after that when its start to extract YAFFS file it shows 
the error

here is the link to the firmware
dropbox.com/s/lpjxpao3oje7qra/V100R001C82SP055.bz2

Original comment by tab.sa...@gmail.com on 28 Jun 2013 at 12:47

[GoogleCodeExporter]

I haven't yet done any testing, but for now I'm going to mark this issue as 
done. I'll fix it later if it proves to be broken.

Support for more than one filesystem is a different issue, so we'll have to 
create an issue for that. I can't say that I see much chance it'll be addressed 
any time soon. It requires some fairly large changes to the FMK, and that isn't 
likely to happen unless we find that images with multiple filesystems are 
common-place.

Original comment by jeremy.collake@gmail.com on 1 Jul 2013 at 1:19

• Changed state: Fixed

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

In a case like this, is it possible to dd the firmware up to the point where 
the YAFFS file is located then run it through the extract script? 

Original comment by slipfric...@gmail.com on 14 Feb 2015 at 6:26