nrk8286 / firmware-mod-kit

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

extract and build only #94

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
I am using the kit to extract this file 
"ftp://support.dlink.co.in/broadband/DSL-2750U/firmware/DSL-2750U_IN_1.10_B038_K
8B_0K-IN-00-2916_20110822.zip"
which is firmware for Dlink DSL-2750U router.

I can extract the file successfully however when a try to build it without any 
modifications I get the message 

"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."

Why has size changed when I have not modified the firmware

Original issue reported on code.google.com by vikraman...@gmail.com on 6 May 2013 at 12:14

GoogleCodeExporter commented 8 years ago
 Original file size: 8078214
./build-firmware.sh: line 135: FOOTER_SIZE_MSG: command not found
       Current file size:  8458496 

Original comment by vikraman...@gmail.com on 6 May 2013 at 12:16

GoogleCodeExporter commented 8 years ago
On the FOOTER_SIZE_MSG problem, looks like I made an oopsie and never tested. 
Some day I will learn. It's easy to be complacent with these hobby projects. 
Anyway, I am testing the firmware image now. Please hold.

Original comment by jeremy.collake@gmail.com on 6 May 2013 at 12:59

GoogleCodeExporter commented 8 years ago
Fixed the FOOTER_SIZE_MSG error, but I will have to evaluate this further to 
determine why the file is so much larger than the original. In the interim, I 
recommend trying to prune the image, for example by removing applications you 
don't need.

Original comment by jeremy.collake@gmail.com on 6 May 2013 at 1:05

GoogleCodeExporter commented 8 years ago

Original comment by jeremy.collake@gmail.com on 6 May 2013 at 2:15

GoogleCodeExporter commented 8 years ago
The FOOTER_SIZE_MSG error is gone but the size problem still persists. Could it 
because the file is in"img" format and the build_firmware packs it in "bin" 
format ?

Original comment by vikraman...@gmail.com on 7 May 2013 at 4:35

GoogleCodeExporter commented 8 years ago
No, the file extension doesn't matter. The issue is the packed size of the file 
system. I'm not sure why the new image is larger, could be any number of 
things. I did confirm that even with a maximum block size there is no big 
chance.

Original comment by jeremy.collake@gmail.com on 7 May 2013 at 1:34

GoogleCodeExporter commented 8 years ago
any progress on the problem. Any manual way I can extract and rebuilt the image 
?

Original comment by vikraman...@gmail.com on 22 May 2013 at 3:56

GoogleCodeExporter commented 8 years ago
I have determined the issue is a bug in binwalk that causes GZIP to be used 
instead of LZMA. A fix is pending.

Original comment by jeremy.collake@gmail.com on 10 Jun 2013 at 3:36

GoogleCodeExporter commented 8 years ago

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