dd-wrt v24 TEW-652brp support

[nwmonster]

dd-wrt v24 TEW-652brp support

[GoogleCodeExporter]

In the older scripts, I only added support for the TEW-632BRP, the TEW652BRP I 
have not analyzed. Did you try the older scripts to (the ones without -ng)?

Original comment by [email protected] on 18 Oct 2011 at 11:42

[GoogleCodeExporter]

Yes, I've try with both, the -ng and the old one.

I've also try with the TEW-632BRP firmware and I get the same error.
(http://www.dd-wrt.com/dd-wrtv2/downloads/others/eko/BrainSlayer-V24-preSP2/2011
/06-14-11-r17201/trendnet-tew632brp/tew632brp-firmware.bin)

Original comment by [email protected] on 18 Oct 2011 at 11:50

[GoogleCodeExporter]

I only tested with the stock images, not DD-WRT images. Those may have a 
different squashfs-lzma signature, or something else, that makes them 
incompatible with the assumptions the original script made.

Original comment by [email protected] on 18 Oct 2011 at 12:06

[GoogleCodeExporter]

Just tested both of these firmware images and both were extracted successfully 
with extract-ng (see output below). I suspect that the images you have are 
corrupt; the first time I ran extract-ng against the TEW-652 firmware image it 
failed because of a corrupt image. I find that this happens fairly regularly to 
me when dragging-and-dropping into a VMWare VM, so be careful if you are using 
VMWare, and always validate your checksums.

The MD5 checksums that I have for these images are:

8ca97d5c85948739e512349eee7eec17  tew632brp-firmware.bin
fa15e20138e249dde38fe8ac906384db  tew652brp-firmware.bin


--------------------------------------------------------------------------------
----------------------------------------------


# ./extract-ng.sh tew632brp-firmware.bin 
Firmware Mod Kit (build-ng) 0.71 beta, (c)2011 Craig Heffner, Jeremy Collake
http://www.bitsum.com

Scanning firmware...

DECIMAL     HEX         DESCRIPTION
--------------------------------------------------------------------------------
-----------------------
0           0x0         TRX firmware header, little endian, header size: 28 
bytes,  image size: 3596316 bytes, CRC32: 0x6ABF4BA flags/version: 0x10001
28          0x1C        uImage header, header size: 64 bytes, header CRC: 
0xA28A6E0A, created: Tue Jun 14 05:10:58 2011, image size: 852757 bytes, Data 
Address: 0x80002000, Entry Point: 0x80006150, data CRC: 0x96594AD1, OS: Linux, 
CPU: MIPS, image type: OS Kernel Image, compression type: lzma, image name: 
MIPS Linux Kernel Image
856092      0xD101C     Squashfs filesystem, big endian, DD-WRT signature, 
version 3.0, size: 2738075 bytes, 654 inodes, blocksize: 131072 bytes, created: 
Tue Jun 14 05:12:11 2011

Extracting 856092 bytes of trx header image at offset 0
Extracting squashfs file system at offset 856092
Extracting squashfs files...
Firmware extraction successful!
Firmware parts can be found in 'fmk/*'






# ./extract-ng.sh tew652brp-firmware.bin 
Firmware Mod Kit (build-ng) 0.71 beta, (c)2011 Craig Heffner, Jeremy Collake
http://www.bitsum.com

Scanning firmware...

DECIMAL     HEX         DESCRIPTION
--------------------------------------------------------------------------------
-----------------------
0           0x0         TRX firmware header, little endian, header size: 28 
bytes,  image size: 3596316 bytes, CRC32: 0x9D641CF3 flags/version: 0x10001
28          0x1C        uImage header, header size: 64 bytes, header CRC: 
0xA28A6E0A, created: Tue Jun 14 05:10:58 2011, image size: 852757 bytes, Data 
Address: 0x80002000, Entry Point: 0x80006150, data CRC: 0x96594AD1, OS: Linux, 
CPU: MIPS, image type: OS Kernel Image, compression type: lzma, image name: 
MIPS Linux Kernel Image
856092      0xD101C     Squashfs filesystem, big endian, DD-WRT signature, 
version 3.0, size: 2738071 bytes, 654 inodes, blocksize: 131072 bytes, created: 
Tue Jun 14 05:13:26 2011

Extracting 856092 bytes of trx header image at offset 0
Extracting squashfs file system at offset 856092
Extracting squashfs files...
Firmware extraction successful!
Firmware parts can be found in 'fmk/*'

Original comment by [email protected] on 18 Oct 2011 at 2:57

[GoogleCodeExporter]

No response from original poster? Firmware is extracted properly for me. 
Closing as invalid.

Original comment by [email protected] on 21 Oct 2011 at 12:14

• Changed state: Invalid

[GoogleCodeExporter]

A thank you woulda been nice, eh? ;).

Original comment by [email protected] on 21 Oct 2011 at 1:03