Actually comp128-2 has a 54bit Kc it seems.
246tnt(a)gmail.comschreef:
>> On a related note, does anyone have any SIMs for sale, implementing
>> A3/A8 with COMP128-2, still to be provisioned with its Ki or already
>> provisioned with a known Ki?
>
>Comp128v2 ?
>I don't think so ...
>
>All the cards we have use COMP128 v1, the spec for v2 have not been leaked
>(yet ?).
>
>For those, you best bet is ebay, search for "super sim" / 16-in-1 / "magic
>sim" things like that.
>Dealextreme also has some.
>
>If you need more quantity, you can often contact those vendor directly and
>they'll be happy to send you a bunch.
>I myself bought a lot directly emailing the guys at magicsim.com
>
>Cheers,
>
>Sylvain
Found who is the manufacturer (but didn't find a website or email address) SZ
PXHT Inc., I attached a picture from an Star A3000 sticker. Hope this helps.
Hy, I have the datasheet, but it will get me a while before I will finish to
read it (1500 pages), but first i thought that would be great if I can get as
much already done data from the compiled kernel, I will see if I can manage to
decompile it, maybe get the make file off it. I have sent 3 or 4 email to MTK
with no response, Gigabyte answered me and they said that they don't plan to
make an Android or Linux ROM form GSmart S1205 (witch like I said runs on
Windows Mobile 6.5); but for the Star A3000 I'm still looking for the
manufacturer, so, if I find it I will post the name here and I will try to ask
them nicely if they can give it to me too.
Thanks to all,
Getting back to decompiling and looking at hex...
The phone is a Star A3000 made in China, but i can't find their website, or the manufacturer, i have only an Android ROM downloaded from a forum, and from there I extracted the compiled kernel, and now I'm trying to find more info, but I don't know ho made this phone, my phone is Gigabyte Gsmart S1205 with the MT6516 processor, but runs WM6.5 and I want to make it run Linux or Android, I know that it wont be easy, but it keeps my mind occupied.
From: "Harald Welte" <laforge(a)gnumonks.org>
To: "burebista" <blassmegod(a)yahoo.com>
Cc: baseband-devel(a)lists.osmocom.org
Sent: Tuesday, March 8, 2011 6:31:20 PM
Subject: Re: how to decompile a linux kernel zImage
On Tue, Mar 08, 2011 at 05:51:55AM -0800, burebista wrote:
> Does anybody know how to decompile a linux kernel zImage file, I need to extract
> some info about MT6516 processor from there. I successfully extracted the
> .config make file, but want to see other parameters too.
why don't you simply contact the manufacturer of the phone? Which exact
vendor + model is that? As the Linux kernel is GPL licensed, they _have to_
release the source code to it.
It is not MTK who needs to release it, but the phone manufacturer.
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Does anybody know how to decompile a linux kernel zImage file, I need to extract
some info about MT6516 processor from there. I successfully extracted the
.config make file, but want to see other parameters too.
Thanks,
Andreas said he is OK with applying them, so I will do that.
>
> OK :)
> However, if I read your code correctly, it still seems to me that there is
> a fixed compile time decision if gpsd or built-in gps support is to be
> used.
>
> I think it would be better to keep it a runtime decision, i.e.
>
> 1) if gpsd headers/library available during compilation,
> build support for _both_ gpsd and built-in gps into the program,
> 2) if they are not available, only include the built-in gps support.
>
> That's easy to do. I can maintain the original gps interface, so old code
doesn't need to be fixed, and choose the support to use from an internal
state.
> The decision which method to use should be a config file option. Please
> make
> sure that a config file configured for built-in gps support will work with
> both
> versions of the program.
>
> A config file requesting the use of gpsd support should make the program
> abort if it was compiled without gpsd support included.
>
> Not sure to agree. Execs from layer23/misc don't rely on config files.
Probably that's due to the low number of switches used. I think that, even
if cell_log options are increased, we can still use cmd switches. Do you
agree?
Ciao
Dario.
Hi -
I apologize if this is slightly off topic, but has anyone here used a SIM-MaxTechnology "Super SIM" and its associated USB programmed to generate SIMs with a known A3/A8 and a known Ki? (I have been trying, but without success.)
-- David