Sylvain Munaut 246tnt@gmail.com wrote:
If that doesn't yield anything you might need to dump the flash (how ? good question ... no idea what option there is without being able to load code. jtag, or chip unsoldering ?), and reverse engineer the boot loader to see what changed.
I have just posted flash images read out of two C139s and one C140, along with an annotated disassembly of the bootloader and other reverse eng notes:
ftp://ftp.ifctf.org/pub/GSM/Compal/
Hopefully someone will find it helpful...
To the OP: in case you haven't already figured it out, you need to use -m c140xor with C139 and C140 phones. I don't know what phones would -m c140 (w/o xor) be correct for, if any. Sylvain's direction to use the -c option as well (and then use *.highram.bin instead of *.compalram.bin) is also correct, because the images are bigger than the ~15k max one can download w/o -c on this phone.
Also you said your C139 came with fw version "V1.9.24" - are you sure it isn't V1.0.24 instead? The imprint on those stickers is a pain to read, too small... If your fw version is actually V1.0.24, then it is the exact same one I have just dumped and reverse-engineered.
HTH, SF
Hi,
I had a similar problem with a tracfone branded c139 (ftmtool error). On IRC, Hoernchen mentioned an older post where the author "fixed" the bootloader. He also mentioned a pastebin that referenced a tool called mot931c. I managed to find it and could successfully reflah my tracfone's bootloader, which now loads osmocom-bb without issue. Here's the reuploaded software package:
https://drive.google.com/file/d/0ByHQWL5Q6bSwdkJReUlJWUQ1Z3M/edit?usp=sharin...
-cde
On Mon, Mar 31, 2014 at 10:53 AM, Michael Spacefalcon < msokolov@ivan.harhan.org> wrote:
Sylvain Munaut 246tnt@gmail.com wrote:
If that doesn't yield anything you might need to dump the flash (how ? good question ... no idea what option there is without being able to load code. jtag, or chip unsoldering ?), and reverse engineer the boot loader to see what changed.
I have just posted flash images read out of two C139s and one C140, along with an annotated disassembly of the bootloader and other reverse eng notes:
ftp://ftp.ifctf.org/pub/GSM/Compal/
Hopefully someone will find it helpful...
To the OP: in case you haven't already figured it out, you need to use -m c140xor with C139 and C140 phones. I don't know what phones would -m c140 (w/o xor) be correct for, if any. Sylvain's direction to use the -c option as well (and then use *.highram.bin instead of *.compalram.bin) is also correct, because the images are bigger than the ~15k max one can download w/o -c on this phone.
Also you said your C139 came with fw version "V1.9.24" - are you sure it isn't V1.0.24 instead? The imprint on those stickers is a pain to read, too small... If your fw version is actually V1.0.24, then it is the exact same one I have just dumped and reverse-engineered.
HTH, SF
Hi,
It should be noted that the new bootloader is very limited (no charging, no loading of the regular phone os). I found another tool, called "C139 FULL SOLUTION UNLOCK AND FLASH", that successfully could flash a proper firmware (European_Software in the archive it is version 1.0.03.E): https://drive.google.com/file/d/0ByHQWL5Q6bSwTWdhRFAyU05uLUk/edit?usp=sharin... Nonethless this particular (trac)phone is still limited to the US bands.
On Tue, Apr 1, 2014 at 11:25 AM, Christophe Devine < devinechristophe@gmail.com> wrote:
Hi,
I had a similar problem with a tracfone branded c139 (ftmtool error). On IRC, Hoernchen mentioned an older post where the author "fixed" the bootloader. He also mentioned a pastebin that referenced a tool called mot931c. I managed to find it and could successfully reflah my tracfone's bootloader, which now loads osmocom-bb without issue. Here's the reuploaded software package:
https://drive.google.com/file/d/0ByHQWL5Q6bSwdkJReUlJWUQ1Z3M/edit?usp=sharin...
-cde
On Mon, Mar 31, 2014 at 10:53 AM, Michael Spacefalcon < msokolov@ivan.harhan.org> wrote:
Sylvain Munaut 246tnt@gmail.com wrote:
If that doesn't yield anything you might need to dump the flash (how ? good question ... no idea what option there is without being able to load code. jtag, or chip unsoldering ?), and reverse engineer the boot loader to see what changed.
I have just posted flash images read out of two C139s and one C140, along with an annotated disassembly of the bootloader and other reverse eng notes:
ftp://ftp.ifctf.org/pub/GSM/Compal/
Hopefully someone will find it helpful...
To the OP: in case you haven't already figured it out, you need to use -m c140xor with C139 and C140 phones. I don't know what phones would -m c140 (w/o xor) be correct for, if any. Sylvain's direction to use the -c option as well (and then use *.highram.bin instead of *.compalram.bin) is also correct, because the images are bigger than the ~15k max one can download w/o -c on this phone.
Also you said your C139 came with fw version "V1.9.24" - are you sure it isn't V1.0.24 instead? The imprint on those stickers is a pain to read, too small... If your fw version is actually V1.0.24, then it is the exact same one I have just dumped and reverse-engineered.
HTH, SF
baseband-devel@lists.osmocom.org
-
Christophe Devine -
msokolov＠ivan.Harhan.ORG