Just on that unsimlocking subject that is not directly linked to android. About what lbcoder has just explained, and about what has been done on the iPhone there is a solution to remove simlock. Basically, it works with a single version of the "baseband" (the soft for the dedicated "processor" for all radio telephony aspects). The unlocking is a small daemon that works on the application processor and that is launched on boot. It injects a necessary payload on boot of the "radio" processor).
Then, more generally, about unsimlocking. It seems to me that at the very beginning of GSM telephony, there were an agreement between GSM operators (GSM Association) that simlocking was tolerated (and justified by the fact operators were subsidising the phones for new subscriptions). The agreement was that the operator would provide unlocking codes for free six months after the start of the contract (this was also applied to prepaid then). I have no idea whether this is still valid and is also applicable to non EU operators, but, at least in my country, I think this is still applied by all GSM/3G operators (although some are communicating on this and some are not). The only problem is that you need to have a valid contract (or an active SIM) with the operator that provided the phone. As a small notice, I do not intend to provide the information on the iPhone as a way to support or encourage unsimlocking but as technical information. According to me, if you signed a contract and respected a contract, you should always have a free way to unlock your phone. I used to consider that the other means to get unlocking codes were only necessary for people that had stolen a phone ... or that did not know their operator was supposed to give it them for free ;-) 2009/5/27 lbcoder <[email protected]>: > > Hmm, that brings up an interesting thought... from a purely academic > point of view... the simlock can't be associated with the actual radio > firmware, since the radio firmware can be written without affecting > the simlock, which means that the simlock must be on another part of > the radio memory that is not written during a normal radio update, so > might it be possible to bypass the simlock with a radio image > customized to ignore it? Or might it be possible to in some manner > overwrite the simlock portion of the memory in a manner similar to a > normal radio update? I doubt that they would have huge security over > the simlock memory since every gsm phone is made such that it *can be* > unlocked.. there probably exists a very simple solution. > > > On May 27, 10:50 am, Jean-Baptiste Queru <[email protected]> wrote: >> Actually SIM locking on Dream is done at a much lower level than what >> Android can reach (it's in the radio code itself, running on a >> separate CPU). >> >> JBQ >> >> 2009/5/27 Cédric Berger <[email protected]>: >> >> >> >> > On Wed, May 27, 2009 at 16:20, mike quinn <[email protected]> wrote: >> >> At this point in time no ones post has any value in it, no one has >> >> answered >> >> the OPs question. >> >> > If you get root access and flash a dev image I guess it won't be locked ? >> > Of course with root access you could also just spot/replace the >> > locking code, but I have no idea how this is managed. >> >> -- >> Jean-Baptiste M. "JBQ" Queru >> Android Engineer, Google. >> >> Questions sent directly to me that have no reason for being private >> will likely get ignored or forwarded to a public forum with no further >> warning. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
