chensiqia / firmware-mod-kit

Automatically exported from code.google.com/p/firmware-mod-kit
0 stars 0 forks source link

edimax firmware leads to unsquashfs endless loop #88

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. extract-ng.sh  
2.
3.

What is the expected output? What do you see instead?

The output looks like it should. But the process never ends. I have a unsuqshfs 
process looping forever:
root     11801 90.6  0.0   7660   592 pts/3    R    00:36   1:41 
./src/squashfs-2.1-r2/unsquashfs -dest /mypath/out/rootfs 
/mypath/out/image_parts/rootfs.img

$ extract-ng.sh EW7438RPN_Edimax_1.13_upg.bin out
Firmware Mod Kit (build-ng) 0.78 beta, (c)2011-2012 Craig Heffner, Jeremy 
Collake
http://www.bitsum.com

Scanning firmware...

Scan Time:     2013-03-21 00:36:31
Signatures:    193
Target File:   /mypath/EW7438RPN_Edimax_1.13_upg.bin
MD5 Checksum:  2ebc50b17ae2c0bbbbb38bfb2c944c70

DECIMAL     HEX         DESCRIPTION
--------------------------------------------------------------------------------
-----------------------
509         0x1FD       LZMA compressed data, properties: 0x88, dictionary size: 
1048576 bytes, uncompressed size: 65535 bytes
11280       0x2C10      LZMA compressed data, properties: 0x5D, dictionary size: 
8388608 bytes, uncompressed size: 1933312 bytes
655360      0xA0000     Squashfs filesystem, big endian, version 2.0, size: 
987980 bytes, 351 inodes, blocksize: 65536 bytes, created: Mon Sep 24 13:41:40 
2012 

Extracting 655360 bytes of  header image at offset 0
Extracting squashfs file system at offset 655360
Extracting 16 byte footer from offset 1646578
Extracting squashfs files...
[sudo] password for uli: 

What version of the product are you using? On what operating system?
svn checkout from 2013-03-18; extract-ng.sh r389
OS: Ubuntu 12.04.2 LTS 64bit

Please provide any additional information below.

- using unsquashfs-lzma instead of unsquashfs from the same directory seems to 
work. However this must be called manually.
- This device ist sold by many vendors, eg Smartlink, Medion, Sitecom, 
Intellilink, Logilink... All have their own firmware for the deivce and all of 
them have that problem.

Original issue reported on code.google.com by ulrich.s...@gmail.com on 20 Mar 2013 at 11:47

GoogleCodeExporter commented 8 years ago
Device description and firmware download: URL: 
http://www.edimax.com/en/support_detail.php?pd_id=404&pl1_id=1

Original comment by ulrich.s...@gmail.com on 20 Mar 2013 at 11:50

GoogleCodeExporter commented 8 years ago
It seems the firmware's filesystem is improperly identified by binwalk.

Original comment by jeremy.collake@gmail.com on 10 Apr 2013 at 6:34