search

Red54 / firmware-mod-kit

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

Failed to extract the dd-wrt v24 image built by build_firmware.sh #7

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. ./extract_firmware.sh dd-wrt.v24-10431_VINT_std.bin work_ddwrt
2. ./build_firmware.sh outdir/ work_ddwrt/
3. ./extract_firmware.sh outdir/custom_image-generic.bin work_custom/

What is the expected output? What do you see instead?
I'd like to see all the 3 steps to succeed, but step 3 fails:
#./extract_firmware.sh outdir/custom_image-generic.bin work_custom/

 Firmware Mod Kit (extract) v0.62 beta, (c)2008 Jeremy Collake
 http://www.bitsum.com
 Checking for updates ...
  You have the latest version of this kit.
 LINUX system detected. Compatibility ok.
 Testing file system of work_custom/ ...
 Building tools ...
 Build seems successful.
 Preparing working directory ...
 Removing any previous files ...
 Creating directories ...
 Extracting firmware
 Attempting squashfs 3.0 lzma ...
 Trying 'damn small' variant - used by DD-WRT v24 ...
./extract_firmware.sh: line 172:   993 Segmentation fault      
"src/squashfs-3.0-lzma-damn-small-variant/unsquashfs-lzma" -dest 
"$2/rootfs" "$2/image_parts/squashfs-lzma-image-3_0" 2> /dev/null >> 
extract.log
 Error: filesystem not extracted properly.
  firmware image format not compatible?

What version of the product are you using? On what operating system?
http://firmware-mod-kit.googlecode.com/svn/trunk/trunk@r153
OS: Ubuntu 8.04 LTS

Please provide any additional information below.
# ls -R work_custom/
work_custom/:
image_parts  installed_packages

work_custom/image_parts:
segment1  segment2  squashfs-lzma-image-3_0  squashfs_magic

work_custom/installed_packages:

#ls -R work_ddwrt
gives a lot of stuff which seems to be of no problem.

Original issue reported on code.google.com by hanjun....@gmail.com on 5 May 2009 at 9:52

GoogleCodeExporter commented 9 years ago 
I solved eliminating the "EXIT 1" line into the extract_firmware.sh file. That 
caused exiting without try other metods because didn't work untrx and splitter3

I have it at line 113

109         echo "! untrx failed, trying splitter3";
109         "src/splitter3" "$1" "$2/image_parts" >> extract.log 2>&1
110         if [ $? != 0 ]; then
111             echo " ERROR: Could not split firmware into 
112 component parts (unrecognized)";
113         #   exit 1
114         else
115             touch "$2/.linux_raw_type3"

Original comment by desiga...@gmail.com on 13 Dec 2010 at 1:00

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I initially commented about the wrong model (got user reports confused). I had 
made some changes to support a new firmware type and in doing so broke support 
for others. As a F/OSS project I leave the regression testing to users ;). I 
will apply this patch as a temporary fix pending a proper switch on the 
firmware image type by splitter3 or scripting method ID.

Original comment by jeremy.collake@gmail.com on 13 Dec 2010 at 3:48

GoogleCodeExporter commented 9 years ago 
This issue appears to be fixed, closing.

Original comment by heffne...@gmail.com on 30 Aug 2011 at 12:05