CRC update Failed

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Linux debian 2.6.32-5-686 
2. ./extract-ng.sh factory-to-ddwrt.bin
3. ./build-ng fmk (without any modification)

What is the expected output? What do you see instead?
Expected: Build Successful

This what I see: 
"Remaining free bytes in firmware image: 69632
Processing 0 header(s) from fmk/new-firmware.bin...
CRC update failed.
Firmware header not supported; firmware checksums may be incorrect. New 
firmware image has been saved to: fmk/new-firmware.bin"

What version of the product are you using? On what operating system?
My router is TP-LINK TL-WR741ND, Linux debian 2.6.32-5-686 

Please provide any additional information below.
In the output directory I find new-firmware.bin, large 3.8M as the original 
file; my question is: can I flash it to my router without brick it?

Furthermore:
If I use ./extract_firmware.sh and then build_firmware.sh (without 
modification) the process ends successfull, but in the output directory I find 
4 files .bin large 1k!!! 

Any help is well received!!

Thanks

Original issue reported on code.google.com by ffuc...@gmail.com on 2 Apr 2012 at 2:19

[GoogleCodeExporter]

That error indicates that the build-ng script doesn't know the firmware header 
format used by the TP-Link images. You can try flashing it, but the router will 
likely reject it, and there is a possibility that it could brick the device, so 
proceed at your own risk!

Original comment by heffne...@gmail.com on 20 Apr 2012 at 9:16

[GoogleCodeExporter]

I just received a new tool submission from Jonathan McGowan that supports 
deconstructing and reconstructing TP-Link images. It is currently checked in 
under the trunk/src/tp-tool directory. I'm working on integrating it into the 
FMK scripts.

Original comment by heffne...@gmail.com on 12 Aug 2012 at 5:58

• Changed state: Started

[GoogleCodeExporter]

I believe I have the same/similar issue with wndr3700-factory_NA.img (Netgear 
WNDR3700).

# ./extract-firmware.sh wndr3700-factory_NA.img
# ./build-firmware.sh

Without any modifications.

I wonder if TP-Link images and Netgear images requires different integration 
effort (or maybe it's a completely different issue).

=== Output START ===

irmware Mod Kit (build-ng) 0.83, (c)2011-2013 Craig Heffner, Jeremy Collake

Building new squashfs file system...
Creating big endian 3.0 filesystem on 
/home/alexlee/firmware-mod-kit/fmk/new-filesystem.squashfs, block size 131072.

Big endian filesystem, data block size 131072, compressed data, compressed 
metadata, compressed fragments
Filesystem size 5578.55 Kbytes (5.45 Mbytes)
    30.98% of uncompressed filesystem size (18005.31 Kbytes)
Inode table size 6710 bytes (6.55 Kbytes)
    24.05% of uncompressed inode table size (27896 bytes)
Directory table size 7971 bytes (7.78 Kbytes)
    56.45% of uncompressed directory table size (14120 bytes)
Number of duplicate files found 5
Number of inodes 892
Number of files 609
Number of fragments 51
Number of symbolic links  195
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 88
Number of uids 1
    root (0)
Number of gids 0
ERROR: New firmware image will be larger than original image!
       Building firmware images larger than the original can brick your device!
       Try re-running with the -min option, or remove any unnecessary files from the file system.
       Refusing to create new firmware image.

       Original file size: 6762625
       Current file size:  6762624

       Quitting...

=== Output END ===

Any help/pointers appreciated.

Cheers,

~Alex

Original comment by alex...@coloursinlife.net on 29 Apr 2013 at 2:36

[GoogleCodeExporter]

Alex, your issue is not the same. There is a slight display anomaly in the 
build script in that it isn't reporting the filler size along with the current 
file size, which is why the sizes don't correspond with the error. Regardless, 
you need to reduce the size of the firmware image. I'd suggest removing some 
unnecessary applications and/or try the -min switch.

Original comment by jeremy.collake@gmail.com on 29 Apr 2013 at 5:15

[GoogleCodeExporter]

err, footer size rather. I will adjust it if you provide a link to the image.

Original comment by jeremy.collake@gmail.com on 29 Apr 2013 at 5:17

[GoogleCodeExporter]

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

• Changed state: WontFix