You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. ./extract-ng.sh test.bin 3com
What is the expected output? What do you see instead?
firmware to extract
What version of the product are you using? On what operating system?
Latest on CentOS Linux 6.1
Please provide any additional information below.
(test.bin is the renamed firmwarefile)
[root@dans34 trunk]# ./extract-ng.sh test.bin 3com
Firmware Mod Kit (build-ng) 0.73 beta, (c)2011 Craig Heffner, Jeremy Collake
http://www.bitsum.com
Scanning firmware...
DECIMAL HEX DESCRIPTION
--------------------------------------------------------------------------------
-----------------------
Extracting 0 bytes of header image at offset 0
ERROR: No supported file system found! Aborting...
Downloaded the firmware image from
http://download.modem-help.co.uk/mfcs-U/USR/3CRWE754G72/Firmware/r1-31/3crwe754g
72-x-02June2005.exe.php
there is a perl script that seams to extact the firmware available
http://web.archive.org/web/20070509231706/http://www.adslayuda.com/modules.php?o
p=modload&name=XForum&file=viewthread&tid=25054
I have serial access to the router if any aditional info is needed
Original issue reported on code.google.com by danarn...@gmail.com on 12 Dec 2011 at 3:04
The text was updated successfully, but these errors were encountered:
The automated extract and build scripts are pretty generic and target
Linux-based firmware only. This 3COM router uses a RTOS (real-time operating
system), and is not supported by FMK.
WIth that said, you should be able to use the tools included in the FMK
(binwalk in particular) to identify the different sections of the firmware,
which you can extract from the firmware image with dd.
Original comment by heffne...@gmail.com on 13 Dec 2011 at 3:56
Original issue reported on code.google.com by
danarn...@gmail.com
on 12 Dec 2011 at 3:04The text was updated successfully, but these errors were encountered: