dnpinpon / firmware-mod-kit1 Goto Github PK

What steps will reproduce the problem?
1. Would like that it be abble to "open" realtek 8186 firmware files
2. willing to donate to help your project
3. donation could be in the 4 digits ammount.

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

Will provide all the help and previous knowdlegd on this firmware.

What version of the product are you using? On what operating system?


Please provide any additional information below.

What steps will reproduce the problem?

I have tried to extract a dd-wrt v24 firmware with this command

/extract_firmware.sh ~/Desktop/dd-wrt.v24_mini_generic.bin 
~/Desktop/dd-wrt.v24_mini_generic

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

I see a zlib unknown error:

./extract_firmware.sh v0.51 beta, (c)2006-2008 Jeremy Collake
 Checking for updates ...
  You have the latest version of this kit.
 LINUX system detected. Compatibility ok.
 Testing file system of /home/jesus/Desktop/dd-wrt.v24_mini_generic ...
 Building tools ...
 Build seems successful.
 Preparing working directory ...
  Removing any previous files ...
  Creating directories ...
 Extracting firmware ...
zlib::uncompress failed, unknown error -3
zlib::uncompress failed, unknown error -3
FATAL ERROR aborting: uncompress_inode_table: failed to read block
Bus error (core dumped)
 Error: filesystem not extracted properly.
   firmware image format not compatible?

What version of the product are you using? On what operating system?

I have tried with the lastest versión from 
http://www.bitsum.com/files/firmware_mod_tools.tar.gz

and with the svn trunk.

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.

What steps will reproduce the problem?
1. Cant find to edit the GUI pages or it is not extracted


What is the expected output? What do you see instead?
Everything runs fine

What version of the product are you using? On what operating system?
Ubuntu 

Please provide any additional information below.

Everything is extracted/build correctly, I dont know were to go now after
extrating the firmware (never extrated ddwrt before), my guess is that 1mb
file on
/root/ddwrt/firmware-mod-kit-read-only/trunk/firm/image_parts/squashfs-lzma-imag
e-3_0
is an lzma file, do I add the extension .lzm and attempt to extract it ?

When I try to extract the cramfs image  I got following error:
"
./cramfsck  -v -x /root/tmp /root/IMAGGINI_CRAMFS/cramfs.2.img 
./cramfsck: unsupported filesystem features
"

The cramfs image is based on a openrg firmware of  BCM96358 broadcom plaform.

file cmd output:

file cramfs.2.img

cramfs.2.img: Linux Compressed ROM File System data, little endian size
1376256 version #2 sorted_dirs CRC 0xe514a6b4, edition 0, 85 blocks, 30 files.


The uncramfs command gives "uncompress error":

./uncramfs  /root/tmp /root/IMAGGINI_CRAMFS/cramfs.2.img 
[Volume size: 0x150000]
[Volume serial: b4a614e500000000550000001e000000]
[Volume name: Compressed]

/root/tmp: File exists
drwxr-xr-x 1020/120           16(16)      /

/:
drwxr-xr-x 1020/120           20(20)      lib

/lib:
drwxr-xr-x 1020/120          732(732)     modules

/lib/modules:
Uncompression failed-rw-r--r-- 1020/120         9160(2344116) bcm53xx_mod.o
Uncompression failed-rw-r--r-- 1020/120       628452(21000700
bcm963xx_adsl_mod.o
Uncompression failed-rw-r--r-- 1020/120        22124(-1519611
bcm963xx_atm_mod.o
Uncompression failed-rw-r--r-- 1020/120        99508(-1958960
bcm963xx_atmapi_mod.o
Uncompression failed-rw-r--r-- 1020/120        22752(-1519649
bcm963xx_br2684_mod.o
Uncompression failed-rw-r--r-- 1020/120        41944(19738572
bcm963xx_eth_mod.o
Uncompression failed-rw-r--r-- 1020/120        21560(-1519671
bcm963xx_jdsp_mod.o
Uncompression failed-rw-r--r-- 1020/120         3360(1384)    bcm_vdsl_mod.o
Uncompression failed-rw-r--r-- 1020/120         8036(53656177 be_pppoa_mod.o
Uncompression failed-rw-r--r-- 1020/120         7196(53655890 btn.o
Uncompression failed-rw-r--r-- 1020/120       734660(-1976173 dspdd_mod.o
Uncompression failed-rw-r--r-- 1020/120       851900(-1578481 endpointdd_mod.o
Uncompression failed-rw-r--r-- 1020/120        37892(99333825 igmp_proxy_mod.o
Uncompression failed-rw-r--r-- 1020/120         3928(1422)    jtimer.o
Uncompression failed-rw-r--r-- 1020/120         5580(53614190 log_chardev.o
Uncompression failed-rw-r--r-- 1020/120       499380(62128140 one_module.o
Uncompression failed-rw-r--r-- 1020/120        12548(-1859023 phone_mod.o
Uncompression failed-rw-r--r-- 1020/120        18788(13965768 pppoe_relay.o
Uncompression failed-rw-r--r-- 1020/120         2808(1034)    qos_ingress.o
Uncompression failed-rw-r--r-- 1020/120        10668(1838416)
rg_auth1x_pktfil.o
Uncompression failed-rw-r--r-- 1020/120         8516(1283848) rg_dhcp_pktfil.o
Uncompression failed-rw-r--r-- 1020/120         2656(936)     rg_ipv4.o
Uncompression failed-rw-r--r-- 1020/120         5520(53597077 rg_pppoe_relay.o
Uncompression failed-rw-r--r-- 1020/120        19980(13964082 rtp.o
Uncompression failed-rw-r--r-- 1020/120         4232(53596146 tcp_mss.o
Uncompression failed-rw-r--r-- 1020/120         3820(1428)    vnet_mod.o
Uncompression failed-rw-r--r-- 1020/120      1233220(16881115 wl.o

[Summary:]
[Total uncompressed size:      4320956]
[Total compressed size:      1186721213]
[Number of entries:                 30]
[Number of files compressed:        15]
[Number of files expanded:          15]

Hi,

apparently the extractor doesn't work with WL530gV2 firmware from

http://dlcdnet.asus.com/pub/ASUS/wireless/WL-530gV2/FW_WL_530gV2_1956EN.zip

The result is a rootfs with many broken symlinks and untrx creates a
segment1 file that is not considered by extract_firmware.sh but seems to
contain parts of the FW.

Here is the untrx output:

me@marva:~/tmp/firmware-mod-kit/trunk$ src/untrx
~/Desktop/WL-530gV2_1.9.5.6_EN.bin ../
 untrx 0.54 beta - (c)2006 Jeremy Collake
 Opening /home/me/Desktop/WL-530gV2_1.9.5.6_EN.bin
 read 2957312 bytes
  Writing ../segment1
    size 655328 from offset 32 ...
  CRAMFS v? image detected
  Writing ../cramfs-image-x_x
    size 2301952 from offset 655360 ...
  Done!

Thanks.

What steps will reproduce the problem?
1. Trying to extract the content of DD-WRT FON firmware
2. Trying to extract the content of DD-WRT Ubiquiti firmware
3. Trying to extract the content of original Ubiquiti firmware

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

All end up with errors very similar to this (except for the file and folder
names of course)

 Extracting NS2.ar2316.v3.2.3734.080909.1631.bin to NS2 ...
 Error: filesystem not extracted properly.
  firmware image format not compatible?

What version of the product are you using? On what operating system?
v0.6
CentOS release 5, X86_64

Please provide any additional information below.

The same kit works perfectly on DD-WRT linksys images

What am I missing? any tweaks should I be aware of?
Kindly advice

OS X Compatibility changes; tested under 10.5.7/PPC

I may test on 10.5.7/Intel if I have time later.

Not sure how you want your diffs, but here they are :)

Necessary to support firmwares that use a normal squashfs (zlib) based 
file system instead of squashfs-lzma.

Hi, 

When I run 

sudo ./extract_firmware.sh dir600b-revb-ddwrt-webflash.bin ./work/ 

have error: 
=========== 
Firmware Mod Kit (extract) v0.62 beta, (c)2008 Jeremy Collake 
http://www.bitsum.com 
Checking for updates ... 
! WARNING: Could not check for update. No connectivity or server down? 
LINUX system detected. Compatibility ok. 
Testing file system of ./work/ ... 
Building tools ... 
Build seems successful. 
Preparing working directory ... 
Removing any previous files ... 
Creating directories ... 
Extracting firmware 
Attempting raw linux style firmware package (i.e. TEW-632BRP) ... 
Extracting dir600b-revb-ddwrt-webflash.bin to ./work/ ... 
Can't find a SQUASHFS superblock on ./work//image_parts/squashfs-3-lzma.img 
Error: filesystem not extracted properly. 
firmware image format not compatible?

What steps will reproduce the problem?
1. Extract DD-WRT v24 SP2
2. Rebuild
3. Flash

What is the expected output? What do you see instead?
Router should fully boot, instead it halts. Serial output not obtained.

Please use labels and text to provide additional information.
unreproduced in developer. Cause unknown. Specific model versions unknown.