Well that's the situiation, it sim-locks even though i have my phone with the sim from the carrier i bought it, i'd like to know if it is just me or other people with e10a are experiencing the same problem?:s
And also since this happened i noticed that in previous version of e10a firmware there was no sim-lock enforcement like this one, just hardware, even though i flashed firmwares from other countries and even e10i; and this new sim-lock it's not the firmware, because i installed cyanogenmod and it still gave me the sim-lock
Anyways what i'm trying to say is, and it might be a wild guess, but the sim-lock is enforced by kernel from 2.1.1.A.0.6 onwards, maybe not entierly but in a way that the kernel or one of the other files that are flashed (excep system, ruled it out by trial and error) has the region code or the carrier number or whatever it is that tells the device that the sim is not from the carrier it's lock down to, so with that maybe we could locate that code and modify it to our actual carrier number or maybe an unlocked mode, kind of like how the galaxy S unlock works
And also since this happened i noticed that in previous version of e10a firmware there was no sim-lock enforcement like this one, just hardware, even though i flashed firmwares from other countries and even e10i; and this new sim-lock it's not the firmware, because i installed cyanogenmod and it still gave me the sim-lock
Anyways what i'm trying to say is, and it might be a wild guess, but the sim-lock is enforced by kernel from 2.1.1.A.0.6 onwards, maybe not entierly but in a way that the kernel or one of the other files that are flashed (excep system, ruled it out by trial and error) has the region code or the carrier number or whatever it is that tells the device that the sim is not from the carrier it's lock down to, so with that maybe we could locate that code and modify it to our actual carrier number or maybe an unlocked mode, kind of like how the galaxy S unlock works