colonel00
09-05-2007, 08:24 PM
I apologize if this in not in the proper forum, but I did not think that it would get many views in the Apache forum. Besides, I think this will be an issue with any GSM rom that is ported to a CDMA device.
Here is a quick rundown of the problem. Goodlink refuses to install on the Apache when running AKU 3.5 (or 3.3 for that matter). Initially, we thought it had to do with the version numbers as was discussed in threads here. However, I think I have found the source of the problem.
When running AKU 2.0 or 2.2 (both roms designed for CDMA carriers Sprint and Verizon) you can setup up Goodlink correctly. During the initial setup process, when you are entering your email and pin, you can go to Menu/Device Information. In this information is a value for Serial #. This value usually shows as ESN###### where the #'s are the ESN of the device.
However, upon upgrading to AKU 3.5 ported from a benq (GSM) by Helmi, the value changes. Instead of showing ESN####, it shows IMSI######. In this sequence the last numbers are the actual phone number of the device. If setup is attempted, an error occurs and it cannot complete.
So, it would seem that there is a remnant from the GSM portion of the rom that is still identifying the device as a GSM device to Goodlink.
Now, does anyone have any ideas or suggestions as to where to look for this rogue file(s)? Also, is there a good way to track/debug the setup app to see where it is pulling the info from or what .dlls it is calling?
I am hoping that this will ring a bell with someone who has dealt with this before or written an app dealing with IMSI. Thanks for any information you guys might provide.
Here is a quick rundown of the problem. Goodlink refuses to install on the Apache when running AKU 3.5 (or 3.3 for that matter). Initially, we thought it had to do with the version numbers as was discussed in threads here. However, I think I have found the source of the problem.
When running AKU 2.0 or 2.2 (both roms designed for CDMA carriers Sprint and Verizon) you can setup up Goodlink correctly. During the initial setup process, when you are entering your email and pin, you can go to Menu/Device Information. In this information is a value for Serial #. This value usually shows as ESN###### where the #'s are the ESN of the device.
However, upon upgrading to AKU 3.5 ported from a benq (GSM) by Helmi, the value changes. Instead of showing ESN####, it shows IMSI######. In this sequence the last numbers are the actual phone number of the device. If setup is attempted, an error occurs and it cannot complete.
So, it would seem that there is a remnant from the GSM portion of the rom that is still identifying the device as a GSM device to Goodlink.
Now, does anyone have any ideas or suggestions as to where to look for this rogue file(s)? Also, is there a good way to track/debug the setup app to see where it is pulling the info from or what .dlls it is calling?
I am hoping that this will ring a bell with someone who has dealt with this before or written an app dealing with IMSI. Thanks for any information you guys might provide.