WAG320N . Request Support for.

[GoogleCodeExporter]

The .bin image is lzma-something...  Tried to mount it with a loop sentence, 
but no luck so far. 
This router is quite expensive (100€) .. it would be nice if supported..

Original issue reported on code.google.com by vuk...@gmail.com on 7 Dec 2011 at 5:49

Attachments:

• WAG320N-EU-ANNEXA-ETSI-1.00.12.bin

[GoogleCodeExporter]

[root@dans34 trunk]# ./extract-ng.sh 
/home/Dans34/firmware_mod_kit/WAG320N-EU-ANNEXA-ETSI-1.00.12.bin test22
Firmware Mod Kit (build-ng) 0.73 beta, (c)2011 Craig Heffner, Jeremy Collake
http://www.bitsum.com

Scanning firmware...

DECIMAL         HEX             DESCRIPTION
--------------------------------------------------------------------------------
-----------------------
7190480         0x65747962      Squashfs filesystem, big endian, lzma 
signature, version 3.0, size: 6445866 bytes, 910 inodes, blocksize: 65536 
bytes, created: Mon Mar 22 02:52:16 2010

Extracting 65792 bytes of  header image at offset 0
Extracting squashfs file system at offset 65792
Extracting 16 byte footer from offset 8388592
Extracting squashfs files...
Firmware extraction successful!
Firmware parts can be found in 'test22/*'


it seams to already be supported

Original comment by danarn...@gmail.com on 7 Dec 2011 at 1:49

[GoogleCodeExporter]

Well, extraction is supported anyway. I can't guarantee that it will re-build a 
valid firmware image - let us know if it works or not. :P

Original comment by heffne...@gmail.com on 7 Dec 2011 at 11:07

[GoogleCodeExporter]

I suppose we must start listing more supported formats, or telling people to 
'try' first, then submit a ticket. Gotta love these new binwalk based scripts 
of Craig's, work on so many unknown formats.

Original comment by jeremy.collake@gmail.com on 8 Dec 2011 at 1:42

[GoogleCodeExporter]

Of course, there is a bit more risk since it means more untested devices might 
have their firmwares seemingly correctly extracted and built, but could be 
bricked on flash.

Original comment by jeremy.collake@gmail.com on 8 Dec 2011 at 5:31

[GoogleCodeExporter]

What about a page with a table of firmware that has been used with fmk , 
something like http://betaftp.co.uk/ , would then be easy to search , maybe on 
the wiki here ?

Original comment by danarn...@gmail.com on 8 Dec 2011 at 12:34

[GoogleCodeExporter]

Yes, bricking is possible, but in *most* cases if the firmware isn't built 
properly the header/footer checksums won't match and the devices *should* 
reject the firmware. Not always the case though, so still be cautious.

A list of supported and tested firmware would probably be a good idea, but to 
be honest I wouldn't hold my breath. Testing takes a bit of time (and money to 
get the routers), and Jeremy and I are usually pretty busy with everything else 
we have going on. Maybe a wiki/submission page where users can report 
successes/failures would be a good idea.

Original comment by heffne...@gmail.com on 8 Dec 2011 at 1:18

[GoogleCodeExporter]

I'll get my Gentoo Machine next week ... Debricking is perfectly feasible by 
software (kudos to Mr. Eko :) ) and Linksys WAG320N source tar does include 
image builder (whilst source code is another story) .. I will report feedback 
next week .. thank you so much ;)

Original comment by vuk...@gmail.com on 8 Dec 2011 at 2:32

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

yep... header is not supported..
'http://www.filehosting.org/file/details/285071/WAG320N_v1.00.12-A_GPL.tar.gz, 
wag320n source code is crap.. Ages ago I had managed to compile an image.. Now, 
kernel doesn't even compile... 
So I am trying to rebuild image using  the Linksys image builder, which need 
rootfs (I have it) and the kernel_fs (I don't know where to find It)

Original comment by vuk...@gmail.com on 5 Feb 2012 at 3:55

Attachments:

• Makefile

[GoogleCodeExporter]

rootfs.img is 8M ... that's impossible, because 8M is the size of flash... I am 
trying vmlinuz extracted by old extract tool .. wish me luck..
this is standard build command :

/root/WAG320N_v1.00.12-A_GPL/bcm963xx_4.02L.01/hostTools/bcmImageBuilder 
--output /root/WAG320N_v1.00.12-A_GPL/image/bcm963xx_fs_kernel --chip 6358 
--board "96358GWVG" --blocksize 64 --cfefile 
/root/WAG320N_v1.00.12-A_GPL/image/cfe6358.bin --rootfsfile 
/root/WAG320N_v1.00.12-A_GPL/image/fsa.bin --kernelfile  
/root/WAG320N_v1.00.12-A_GPL/kernel/vmlinux.lz.a
bcmImageBuilder
    File tag size                 : 256
    Root filesystem image size    : 6438912
    Kernel image size             : 920932
    Combined image file size      : 7360100

cd /root/WAG320N_v1.00.12-A_GPL/image && cp -f wag320n.pid.a wag320n.pid && 
./bb && mv wag320n.bin wag320n_A_1.00.12.bin
CheckSum...
Protect Area CheckSum OK: 0x00
CheckSum OK: 0x00
-------------------------------
checksum = 0C 1E FD 7C 43 12 76 45 84 21 CF BC 97 77 C9 34 

Original comment by vuk...@gmail.com on 7 Feb 2012 at 1:05

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

OK.. So.. my initial need is fulfilled... the extracted fs (rootfs folder) can 
be used to rebuild a working image (using Linksys source code) by just being 
compressed and named as target.tgz .
Case closed :) .. Thanks a lot..
PD: I mean, router is still unsopported.. but at least fs can be extracted :D

Original comment by vuk...@gmail.com on 7 Feb 2012 at 4:17

[GoogleCodeExporter]

Original comment by jeremy.collake@gmail.com on 11 Jun 2013 at 8:14

• Changed state: WontFix