Problem with Test Signature File | developer.brewmp.com Problem with Test Signature File | developer.brewmp.com

Developer

Problem with Test Signature File

Forums:

Hi,
I have download the test signature file(.sig file) for the Samsung SCH-259 with the ESN number, but still on executing the application on device it showing error 'application digital signature failure (1030)' which implies invalid signature file.(from AEEError.h). What could be the reason behind it? :mad:
help appreciated.....

Prayag wrote:Hi,
I have download the test signature file(.sig file) for the Samsung SCH-259 with the ESN number, but still on executing the application on device it showing error 'application digital signature failure (1030)' which implies invalid signature file.(from AEEError.h). What could be the reason behind it? :mad:
help appreciated.....
This simply means that the signature file that created is not for the particular device and hence u r getting the message.
I hope u remembered that ESN should be 8 digits which should be prefixed with 0X everytime.
Akshay

Prayag wrote:Hi,
I have download the test signature file(.sig file) for the Samsung SCH-259 with the ESN number, but still on executing the application on device it showing error 'application digital signature failure (1030)' which implies invalid signature file.(from AEEError.h). What could be the reason behind it? :mad:
help appreciated.....
This simply means that the signature file that created is not for the particular device and hence u r getting the message.
I hope u remembered that ESN should be 8 digits which should be prefixed with 0X everytime.
Akshay

hi, akshay
I have generated the test signature from the correct ESN number which is printed on the back side of the phone. Earlier when I generate the sig file its fine. I am regenerating the sig file due to expiration of the earlier sig file(90 days), but with new sig file I am facing this problem (1030)!
Is there is any other methods for finding the ESN of the device? :confused:

hi, akshay
I have generated the test signature from the correct ESN number which is printed on the back side of the phone. Earlier when I generate the sig file its fine. I am regenerating the sig file due to expiration of the earlier sig file(90 days), but with new sig file I am facing this problem (1030)!
Is there is any other methods for finding the ESN of the device? :confused:

Prayag wrote:hi, akshay
I have generated the test signature from the correct ESN number which is printed on the back side of the phone. Earlier when I generate the sig file its fine. I am regenerating the sig file due to expiration of the earlier sig file(90 days), but with new sig file I am facing this problem (1030)!
Is there is any other methods for finding the ESN of the device? :confused:
As far as I know, the test SIG files do not get expired before 9 months (this I know since I generated a sig file yesterday and its expiry time is March 2010).
For which device are you generating the SIG file?
If u say that earlier you created a same device sig file - then its better to ask the MODS. But that 1030 msg clearly says that the SIG is not for the particular device.

Prayag wrote:hi, akshay
I have generated the test signature from the correct ESN number which is printed on the back side of the phone. Earlier when I generate the sig file its fine. I am regenerating the sig file due to expiration of the earlier sig file(90 days), but with new sig file I am facing this problem (1030)!
Is there is any other methods for finding the ESN of the device? :confused:
As far as I know, the test SIG files do not get expired before 9 months (this I know since I generated a sig file yesterday and its expiry time is March 2010).
For which device are you generating the SIG file?
If u say that earlier you created a same device sig file - then its better to ask the MODS. But that 1030 msg clearly says that the SIG is not for the particular device.

yes akshay you are right I have generated a sign file just now and its showing expiration date 2010-Jun-05. Earlier I have found some threads on forums that it is valid for only 90 days. I am generating the sig file by using correct ESN with prefixing it 0x for hexadecimal representation, but the problem still persist? I have goggled the forums but can't find any valid reason for it.
I am using Samsung SCH-259. :mad:

yes akshay you are right I have generated a sign file just now and its showing expiration date 2010-Jun-05. Earlier I have found some threads on forums that it is valid for only 90 days. I am generating the sig file by using correct ESN with prefixing it 0x for hexadecimal representation, but the problem still persist? I have goggled the forums but can't find any valid reason for it.
I am using Samsung SCH-259. :mad:

Hi Prayag,
I faced the similar problem on SCH259,
The service provider suggested me to use ESN = 0x30303030.
It will work on any SCH259 handset.
Good Luck...!

Hi Prayag,
I faced the similar problem on SCH259,
The service provider suggested me to use ESN = 0x30303030.
It will work on any SCH259 handset.
Good Luck...!

Quote:
The service provider suggested me to use ESN = 0x30303030.
It will work on any SCH259 handset.
HI,
Thanks for the reply......
The signature file generated with the ESN you suggested is working now.
thanks for your valuable help :)

Quote:
The service provider suggested me to use ESN = 0x30303030.
It will work on any SCH259 handset.
HI,
Thanks for the reply......
The signature file generated with the ESN you suggested is working now.
thanks for your valuable help :)