search

wellcomez / firmware-mod-kit

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

mksquashfs-lzma: invalid option, using build-ng.sh #62

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. ./extract-ng.sh firmware.bin
2. ./build-ng.sh
3.

What is the expected output? 
A new (identical) firmware.bin

What do you see instead?
Firmware Mod Kit (build-ng) 0.76 beta, (c)2012 Graig Heffner, Jeremy Collake 
http://bitsum.com

Building new squashfs file system...
./src/others/squashfs-4.0-lzma/mksquashfs-lzma: invalid option
SYNTAX:./src/others/squashfs-4.0-lzma/mksquashfs-lzma source1 source2 ...  dest 
[options] [-e list of exclude
dirs/files]

Options are
[followed by an explanation of all the options]
Failed to create new filesystem! Quitting...

What version of the product are you using? On what operating system?
0.76 beta on Linux Mint 12 32-bit

Please provide any additional information below.

Original issue reported on code.google.com by maartens...@gmail.com on 11 May 2012 at 4:19

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
To clarify: I successfully extract the firmware, but when rebuilding it, always 
the above error message appears regarding mksquashfs-lzma. Is this a bug, or do 
I do something wrong?

Original comment by maartens...@gmail.com on 13 May 2012 at 5:16

GoogleCodeExporter commented 8 years ago 
Yes, same for me. May be this is typo error in the script which leads to this 
error. Also, this script not updated since long time but, extract-ng.sh is just 
updated. Please, try to sync the issue between the scripts.
OR let us know how I may generate and submit debug logs.

this is what happens

Building new squashfs file system...
./src/others/squashfs-4.0-realtek/mksquashfs: invalid option

Thanks.

Original comment by jongo.ji...@gmail.com on 4 Jun 2012 at 12:10

GoogleCodeExporter commented 8 years ago 
This is in Craig's domain, but I will look into it when I get a chance.

Original comment by jeremy.collake@gmail.com on 7 Jun 2012 at 10:46

GoogleCodeExporter commented 8 years ago 
Removing $ENDIANESS from the script works but, also need to add -comp lzma to 
get lzma compression as default is gzip.
But, still it fails at checksum Also, does not allow to build if image size is 
little big. Need to adjust it to place footer after the $FSOUT even if it not 
same size as $FW_SIZE with warning acceptance.
Thanks again.

Original comment by jongo.ji...@gmail.com on 14 Jun 2012 at 4:10

GoogleCodeExporter commented 8 years ago 
Agreed. It will be a quick mod, I'll try to do it soon.

Original comment by jeremy.collake@gmail.com on 14 Jun 2012 at 5:42

GoogleCodeExporter commented 8 years ago 
Some mksquashfs implementations don't support the -le option to specify a 
little endian image (little endian is used by default). I've updated build-ng 
with a patch that should fix this.

Working on adding support for the -comp option, but this option is specific to 
the realtek squashfs 4.0 implementation, so a bit more parsing of the config 
log file will be needed, as well as an updated binwalk version included with 
FMK.

As for the checksum failure, build-ng currently only supports updating the 
checksums for TRX and uImage headers; you should have received a warning during 
the build-ng process to this effect.

Original comment by heffne...@gmail.com on 8 Jul 2012 at 12:38

GoogleCodeExporter commented 8 years ago

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