Quote:
Originally Posted by JRSCCivic98
Humm, well, if that file is the same throughout each carrier OS release (which apperently it is because loading up the Bell OS does nothing), then I'd be willing to bet that the file (if it is the one controlling the GPS capability) is written in such a way that it looks at the phone's internal config to figure out what "carrier" it's for. So, that being said, the only way this is apperently controlled is via the carrier ID... for testing purposes why not just change the carrier ID on the phone? Is there a way to do this? Technically speaking the phone would load up the OS options for whatever test carrier you set it as, some things may not work properly, but at least GPS functions can be tested. Once it's verified that this is really what it is, then it's just a matter of finding a way to change the carrier ID lockout in the sfi file. Even a single digit edit on the "exclusion" statement from 105 to something else would render the statment useless. That is, if that's the file that really controls this.
|
Exactly.
I have also been trying to gain some insight into the locking mechanism by contacting various BlackBerry enthusiasts who have a niche for reverse engineering cod files. Hopefully they can provide me with some hints as to how receiver is disabled.
I will be sure to post my findings.
Cheers,
randyman