charles2gan / charles2gan/firmware-mod-kit

Can't rebuild the changed firmware

Open
#108 4 comments 0 reactions 0 assignees View on GitHub
auto-migrated Priority-Medium Type-Defect
Dominant language
C
Stars
7
Forks
0
PR merge metrics
No merged PRs in 30d

Description

```
What steps will reproduce the problem?
1./home/pc/Desktop/fmk/extract-firmware.sh /home/pc/Desktop/fmk/lc2.bin
2.Changing some files of the extracted firmware
3./home/pc/Desktop/fmk/build-firmware.sh /home/pc/fmk

What is the expected output? What do you see instead?
Expected output: Rebuild the changed firmware in this directory:
/home/pc/fmk/new-firmware.bin like it's written in the instructions of the
firmware-modkit
Seeing instead: Preparing tools ...
Building new squashfs file system... (this may take several minutes!)
Squahfs block size is 64 Kb
sudo: /home/pc/fmk/rootfs: command not found
Failed to create new file system! Quitting...

What version of the product are you using? On what operating system?
Product verion: Firmware Mod Kit (build) 0.99
OS: Ubuntu 10.04 LTS -Lucid Lynx-

Please provide any additional information below.
I only changed the version.txt file and a few images of the extracted firmware,
which have exactly the same resolution as the original files. Tried with
[-nopad] and [-min] too, but i just get an error message saying:
cat: /home/pc/[-nopad]/logs/config.log: File or directory not found

Could someone please help me with this problem? Thanks in advance!

```

Original issue reported on code.google.com by `Michi....@googlemail.com` on 16 Jul 2013 at 12:43

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading extract-firmware.sh and build-firmware.sh, then reproduce the command sequence with the reported /home/pc/fmk paths. Inspect how build-firmware.sh invokes the squashfs tool and handles rootfs, including the -nopad and -min options. Done means rebuilding the modified firmware into new-firmware.bin without the reported command-not-found or log-path errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
embedded-iot, tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.