charles2gan / charles2gan/firmware-mod-kit
Can't unpack Zyxel NWA-3100 firmware
- Dominant language
- C
- Stars
- 7
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
```
Latest tool version.
root@kali:/opt/fmk# ./extract-firmware.sh
NWA-3100_V3.60\(AAI.8\)C0/360AAI8C0.bin
Firmware Mod Kit (extract) 0.99, (c)2011-2013 Craig Heffner, Jeremy Collake
Preparing tools ...
Scanning firmware...
Scan Time: 2014-08-04 12:36:48
Signatures: 193
Target File: /mnt/hgfs/GSS/0daysearch/NWA-3100_V3.60(AAI.8)C0/360AAI8C0.bin
MD5 Checksum: 1ea9fc764dff1ffaea5dad8f7ee028ce
DECIMAL HEX DESCRIPTION
--------------------------------------------------------------------------------
-----------------------
102400 0x19000 ZynOS header, header size: 48 bytes, rom image type:
ROMBIN, uncompressed size: 299524, compressed size: 61696, uncompressed
checksum: 0x64EA, compressed checksum: 0x10F6, flags: 0xE0, uncompressed
checksum is valid, the binary is compressed, compressed checksum is valid,
memory map table address: 0x0
102448 0x19030 LZMA compressed data, properties: 0x5D, dictionary size:
8388608 bytes, uncompressed size: 299524 bytes
Progress: 19.28% (386807 / 2006008)
Progress: 20.43% (409740 / 2006008)
626688 0x99000 ZynOS header, header size: 48 bytes, rom image type:
ROMBIN, uncompressed size: 6075184, compressed size: 1379272, uncompressed
checksum: 0x3C2D, compressed checksum: 0xCDD8, flags: 0xE0, uncompressed
checksum is valid, the binary is compressed, compressed checksum is valid,
memory map table address: 0x0
626736 0x99030 LZMA compressed data, properties: 0x5D, dictionary size:
8388608 bytes, uncompressed size: 6075184 bytes
Extracting 0 bytes of header image at offset 0
ERROR: No supported file system found! Aborting...
```
Original issue reported on code.google.com by `konrads....@gmail.com` on 4 Aug 2014 at 11:43
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with extract-firmware.sh and the reported scan output, focusing on the ZynOS headers, LZMA data, and the “No supported file system found” failure. Determine whether this firmware format is expected to be supported and identify what successful extraction should produce; no source file or test is named in the report.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100