Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

Guys I am having this error digital signature error on my samsung phone, I know i indicated the correct ESN but still produced the same error, what do you think caused this error?

Double-check the ESN by taking off the battery pack. Underneath you will find the barcode and the decimal and hex ESN code. I would double-check them. Maybe the phone was switched in the box when you bought it and the box has a different ESN than the actual handset.
Just a thought...

Double-check the ESN by taking off the battery pack. Underneath you will find the barcode and the decimal and hex ESN code. I would double-check them. Maybe the phone was switched in the box when you bought it and the box has a different ESN than the actual handset.
Just a thought...

Dragon,
I already checked it on the back of the phone, I successfully produced a sig for lgVX4400 and it worked now I don't know what's happening
Could it be possible that the testsig generator produces a sig that is wrong?

Dragon,
I already checked it on the back of the phone, I successfully produced a sig for lgVX4400 and it worked now I don't know what's happening
Could it be possible that the testsig generator produces a sig that is wrong?

is the phone test enabled??

is the phone test enabled??

yes louie. if it's not test enabled the app will be deleted.

yes louie. if it's not test enabled the app will be deleted.

Did you resolve your issue? What is the error code? (1028)?

Did you resolve your issue? What is the error code? (1028)?

Kevin,
Not yet, I really don't know what to do, the error generated was exactly "Application digital failure (1028)".

Kevin,
Not yet, I really don't know what to do, the error generated was exactly "Application digital failure (1028)".

The signature you generated has expired. Signatures last 90 days. You can look up the error code in the header for future reference. Please generate a new signature file.

The signature you generated has expired. Signatures last 90 days. You can look up the error code in the header for future reference. Please generate a new signature file.

Kevin,
I think that was not the problem because I generated 10 sig files using the ESN on the phone and it generated the same error. Do you think the erro can be caused by a wrong ESN?

Kevin,
I think that was not the problem because I generated 10 sig files using the ESN on the phone and it generated the same error. Do you think the erro can be caused by a wrong ESN?

Kevin,
I have been using the same signature for a device since at least december of 2002, well over the 90 days.. how is the 90 day restriction implemented... I also had a device that I was never able to get a working signature for, much similar to putek20's apparent problem.
regardless, what exactly is the point of a 90-day restriction if it does exist? The only way to get signatures is if we are "authorized" developers with a verisign signature, right? It just seems to be a good way to cause more headaches for the developer..
-Tyndal

Kevin,
I have been using the same signature for a device since at least december of 2002, well over the 90 days.. how is the 90 day restriction implemented... I also had a device that I was never able to get a working signature for, much similar to putek20's apparent problem.
regardless, what exactly is the point of a 90-day restriction if it does exist? The only way to get signatures is if we are "authorized" developers with a verisign signature, right? It just seems to be a good way to cause more headaches for the developer..
-Tyndal

I think that may be a securyty issue, if someone get acces to this file, it would be heaven, he could download anything, so if someone gets this file, it wouldn´t work forever, just for 90 days, so if you´re a developer, nothing to worry, since you can get more without problem..

I think that may be a securyty issue, if someone get acces to this file, it would be heaven, he could download anything, so if someone gets this file, it wouldn´t work forever, just for 90 days, so if you´re a developer, nothing to worry, since you can get more without problem..

Which device are you using, and what is the OEM build? Is it test enabled?

Which device are you using, and what is the OEM build? Is it test enabled?

I am using Samsung SCH A350, yes it is test enabled.

I am using Samsung SCH A350, yes it is test enabled.

I emailed samsung about the ESN and they confirmed that the ESN is correct. So what could be the error?
Please help me.

I emailed samsung about the ESN and they confirmed that the ESN is correct. So what could be the error?
Please help me.

Have you found the answer to this issue?
I am having the same 1028 error message with my signature file, but only when trying to run in an analog only service area. Once the digital service is re-instated, the app loads and runs okay. I support 3 other handsets and the problem only occurs on this one.
Any suggestions?

Have you found the answer to this issue?
I am having the same 1028 error message with my signature file, but only when trying to run in an analog only service area. Once the digital service is re-instated, the app loads and runs okay. I support 3 other handsets and the problem only occurs on this one.
Any suggestions?

IIRC this was due to the time and date being fetched from the network, i believe there was a user in brasil that had set the time and date manually and it had worked for him..

IIRC this was due to the time and date being fetched from the network, i believe there was a user in brasil that had set the time and date manually and it had worked for him..

Is time and date fetched from a local network or from Qualcomms?
We have the same problem with the a530, all other handsets are fine.
Ive noticed that all files seem to be stamped as 01/05/80 23:59:47 no matter when they are transferred to the phone.

Is time and date fetched from a local network or from Qualcomms?
We have the same problem with the a530, all other handsets are fine.
Ive noticed that all files seem to be stamped as 01/05/80 23:59:47 no matter when they are transferred to the phone.

Ok , i think i found the answer to this problem,
your device clock time is either set wrong to a old date... thats why u get a error with even new app sigs. when u set it correctly to the current date and if the sig file still has expiry time, it runs fine.

Ok , i think i found the answer to this problem,
your device clock time is either set wrong to a old date... thats why u get a error with even new app sigs. when u set it correctly to the current date and if the sig file still has expiry time, it runs fine.

Is there a place that lists what these error codes mean?
1028 means the signature has expired (apparently)
1030 means the signature is for a different phone (I think)
Someone recently mentioned 1033 to me. Not sure what that means, but I'd like to know.
Thanks
--t

Is there a place that lists what these error codes mean?
1028 means the signature has expired (apparently)
1030 means the signature is for a different phone (I think)
Someone recently mentioned 1033 to me. Not sure what that means, but I'd like to know.
Thanks
--t

AEEError.h

AEEError.h

Ah, thanks Max. I should have known.
How the heck did he have an invalid signature version?
He must have reported the wrong error code.
--t

Ah, thanks Max. I should have known.
How the heck did he have an invalid signature version?
He must have reported the wrong error code.
--t

Can't say I've ever seen that error before. :confused:

Can't say I've ever seen that error before. :confused:

I believe that the only possibility is that the BREW staff responsible for test enabling your device made a mistake on the number. As a brew apps developer, u should know that how irresponsible they are.......

I believe that the only possibility is that the BREW staff responsible for test enabling your device made a mistake on the number. As a brew apps developer, u should know that how irresponsible they are.......

Thanks for the productive comment...

Thanks for the productive comment...

BREW_IS_ON9 wrote:u should know that how irresponsible they are.......Ouch, dude, that's just wrong.
Guys from the QIS group have actually called me to discuss handsets I've sent down there. We even played phone tag for a while, and they never failed to call me back. They were taking a lot of responsibility about getting the handset test-enabled or reflashed and returned to me.
If you're ever having a problem with QIS, just send them an email. I get the sense that they're pretty busy there, so cut them a break.
--t

BREW_IS_ON9 wrote:u should know that how irresponsible they are.......Ouch, dude, that's just wrong.
Guys from the QIS group have actually called me to discuss handsets I've sent down there. We even played phone tag for a while, and they never failed to call me back. They were taking a lot of responsibility about getting the handset test-enabled or reflashed and returned to me.
If you're ever having a problem with QIS, just send them an email. I get the sense that they're pretty busy there, so cut them a break.
--t