Mischka... one question

[Pondo]

On your spanish firmware post, you said a brazilian user by the name of RUIZ shared some parts of his firmware, my question is how he did that? and why cant we just extract a full firmware like that?

[TheSin]

On your spanish firmware post, you said a brazilian user by the name of RUIZ shared some parts of his firmware, my question is how he did that? and why cant we just extract a full firmware like that?

I know I sure would LOVE to beable to extract a firmware and I can't see why it can't be done, if it can be written it can be read :\ I assume the program we inject firmwares with just doesn't have a read function but it doesn't mean it can't be done if we knwo the areas to read and the order to read them in.

[mischka]

On your spanish firmware post, you said a brazilian user by the name of RUIZ shared some parts of his firmware, my question is how he did that? and why cant we just extract a full firmware like that?

bOOster posted a tool with which it's possible to copy every thing (including hidden things) in phone memory to TF, and asked ruiz to do this for us. This tool creates a couple of files that can be opened with linux tools.

Ruiz shared the complete content of his phone memory, not only parts. But it's only a part of this that I could use.

The problem is, to put this together the right way to make a working .sbf flashfile from this. This is not only to be able to read it but also to be able to pack it the right way and create the right info files for flashing. I don't know anybody who has the right tools for this (except motorola development)

File structure is not the same in installed fw and flashfile The info and data in flashfile is put together in phone while flashing. Doing this in the other direction you need the info about how this was done exactly.

In short words: We can extract the firmware but we cannot make a flashfile of this

[TheSin]

On your spanish firmware post, you said a brazilian user by the name of RUIZ shared some parts of his firmware, my question is how he did that? and why cant we just extract a full firmware like that?

bOOster posted a tool with which it's possible to copy every thing (including hidden things) in phone memory to TF, and asked ruiz to do this for us. This tool creates a couple of files that can be opened with linux tools.

Ruiz shared the complete content of his phone memory, not only parts. But it's only a part of this that I could use.

The problem is, to put this together the right way to make a working .sbf flashfile from this. This is not only to be able to read it but also to be able to pack it the right way and create the right info files for flashing. I don't know anybody who has the right tools for this (except motorola development)

File structure is not the same in installed fw and flashfile The info and data in flashfile is put together in phone while flashing. Doing this in the other direction you need the info about how this was done exactly.

this would be a super easy task with dd, just dd all of the phones rom dev to MMC and then we coudl have a working copy, but just as simple to restore it that way, of course that wouldnt' so much be firware as OS but still be cool to beable to edit the OS and add utils like sshd

[Alpha43]

On your spanish firmware post, you said a brazilian user by the name of RUIZ shared some parts of his firmware, my question is how he did that? and why cant we just extract a full firmware like that?

bOOster posted a tool with which it's possible to copy every thing (including hidden things) in phone memory to TF, and asked ruiz to do this for us. This tool creates a couple of files that can be opened with linux tools.

Ruiz shared the complete content of his phone memory, not only parts. But it's only a part of this that I could use.

The problem is, to put this together the right way to make a working .sbf flashfile from this. This is not only to be able to read it but also to be able to pack it the right way and create the right info files for flashing. I don't know anybody who has the right tools for this (except motorola development)

File structure is not the same in installed fw and flashfile The info and data in flashfile is put together in phone while flashing. Doing this in the other direction you need the info about how this was done exactly.

In short words: We can extract the firmware but we cannot make a flashfile of this

Question.. What type of files come out of the firmware you extract.?

~Alpha~

[mischka]

Question.. What type of files come out of the firmware you extract.?

~Alpha~

Most have *.img type, the other are without type. I tried opening some *.img files with cramfs tool and luckily it worked. That's all. I didn't try to open all of them but I guess that all .img files are cramfs.But only few CG files in .sbf file are cramfs, especially, what I guess is flex CG, is not!

So it's easy to find flex in these *.img files, but to what (and how) should we convert it to make a CG file from that one? And I think, we need other info too for building fw

These are the filenames:

aftermtd.screenshot
afterproc.screenshot
afterroflash.screenshot
df-k.out
mtd0.img
mtd1.img
mtd10.img
mtd11.img
mtd12.img
mtd13.img
mtd2.img
mtd3.img
mtd4.img
mtd5.img
mtd6.img
mtd7.img
mtd8.img
mtd9.img
mtdblock8-ezx_user.img
mtdblock9-ezxlocal.img
proc-cmdline
proc-cpuinfo
proc-devices
proc-execdomains
proc-filesystems
proc-interrupts
proc-iomem
proc-ioports
proc-meminfo
proc-misc
proc-modules
proc-motusbd
proc-mounts
proc-mtd
proc-partitions
proc-roflash_info
proc-slabfree
proc-slabinfo
proc-stat
proc-uptime
proc-usbd-switch
proc-usbd-switch_bmc
proc-version
roflash-root.img
roflash1-usr-language.img
roflash2-usr-data_resource.img
roflash3-usr-setup.img
roflash4-usr-securesetup.img

Opening "roflash1-usr-language.img" folders look exactly the same as if I opened merged CG41/CG42 from any other flashfile. Difference is only, that instead of chinese/english there is engl/fren/port/span files in it, so I was able to use these for my modding

[TheSin]

Question.. What type of files come out of the firmware you extract.?

~Alpha~

Most have *.img type, the other are without type. I tried opening some *.img files with cramfs tool and luckily it worked. That's all. I didn't try to open all of them but I guess that all .img files are cramfs.But only few CG files in .sbf file are cramfs, especially, what I guess is flex CG, is not!

So it's easy to find flex in these *.img files, but to what (and how) should we convert it to make a CG file from that one? And I think, we need other info too for building fw

These are the filenames:

aftermtd.screenshot
afterproc.screenshot
afterroflash.screenshot
df-k.out
mtd0.img
mtd1.img
mtd10.img
mtd11.img
mtd12.img
mtd13.img
mtd2.img
mtd3.img
mtd4.img
mtd5.img
mtd6.img
mtd7.img
mtd8.img
mtd9.img
mtdblock8-ezx_user.img
mtdblock9-ezxlocal.img
proc-cmdline
proc-cpuinfo
proc-devices
proc-execdomains
proc-filesystems
proc-interrupts
proc-iomem
proc-ioports
proc-meminfo
proc-misc
proc-modules
proc-motusbd
proc-mounts
proc-mtd
proc-partitions
proc-roflash_info
proc-slabfree
proc-slabinfo
proc-stat
proc-uptime
proc-usbd-switch
proc-usbd-switch_bmc
proc-version
roflash-root.img
roflash1-usr-language.img
roflash2-usr-data_resource.img
roflash3-usr-setup.img
roflash4-usr-securesetup.img

Opening "roflash1-usr-language.img" folders look exactly the same as if I opened merged CG41/CG42 from any other flashfile. Difference is only, that instead of chinese/english there is engl/fren/port/span files in it, so I was able to use these for my modding

just at a quick glance I'd say each img file is a dir, and it seems to even have levels, the mtd stuff looks like the linux core stuff and I knwo the ezx_user and local are root level dirs from the MyStuff program. So I'm guessing there is a patern with the firmware install and the first part of the filename. just a keep guess though. BTW which fireware did you get this from?

[mischka]

BTW which fireware did you get this from?

We are talking about extracted fw from A1200i. These files have been created by atool, that can extract fw from the phone. Unfortunately it cannot put it back to the phone!

[TheSin]

BTW which fireware did you get this from?

We are talking about extracted fw from A1200i. These files have been created by atool, that can extract fw from the phone. Unfortunately it cannot put it back to the phone!

ahhh so if we coudl find out how to read an sbf we might beable to mod one, very nice.

[TheSin]

BTW which fireware did you get this from?

We are talking about extracted fw from A1200i. These files have been created by atool, that can extract fw from the phone. Unfortunately it cannot put it back to the phone!

Also I just found this link http://wiki.openezx.org/Rokr_E2 it's not for the A1200 but it still looks like lots of great info for this idea.