3

I'm working on unpacking a firmware image. I've already uncompressed the original image, but I'm stuck in the current step.

This is the current uncompressed image: https://www.dropbox.com/s/vxxz3x8ek84iie0/Firmware_N30?dl=0

According to what I have found this is an eCos image: http://ecos.sourceware.org/

I want to separate the binaries, analyse how they work and see if it's possible to make modifications. How can I continue?

  • 1
    What do you mean by separating the binaries? It is one big executable file. Also, do you know what processor is this? – tmr232 Dec 11 '15 at 13:36
  • @tmr232 I don't have a lot of experience with eCos. I assumed there were separate executable files inside the image, but, by your comment, looks like the entire file is the executable? As for the device's CPU, it's a Broadcom BCM5357C0. According to binwalk, this is little endian MIPS (MIPSEL) code. – tnas Dec 12 '15 at 19:18
  • Well, as you can see (I added bitmap headers to the firmware using this) the strings (gray part) are all located together. This usually means that this is a single executable file and not a mashup of many. What you should do now is figure the correct loading address of the firmware so that you can analyze it. This can be done either by looking at specs (for the processor), using the device's shell, or by maximizing the number of string references. – tmr232 Dec 12 '15 at 20:38
  • 1
    @tmr232 By your comment and by further research I've been doing on eCos, it now seems clear to me that this is a single executable. Thanks! Unfortunately I don't have access to a shell on the device, since it doesn't appear to have an UART port or anything. I'll try to look up processor specs, but in case I don't find anything useful, could you explain the part about maximizing the number of string references? – tnas Dec 12 '15 at 23:17

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.