Unable to install .sis file signed with Dev Cert

[skumar_rao]

Thanks. I am using the correct .cer file but I still get the error.

can you read all the posts above and need the necessary setting changes.

[Mikhail617]

Yes, I read all the posts and tried all the suggested changes but still getting the same result. My E51 phones are set to accept 'all' installations, not 'signed only'. I have changed the UID2 to 0x100039CE, made sure that I am using the correct .cer file and my IMEIs appear to be correct but I am still getting the same error. What else could it be???

can you read all the posts above and need the necessary setting changes.

[skumar_rao]

Yes, I read all the posts and tried all the suggested changes but still getting the same result. My E51 phones are set to accept 'all' installations, not 'signed only'. I have changed the UID2 to 0x100039CE, made sure that I am using the correct .cer file and my IMEIs appear to be correct but I am still getting the same error. What else could it be???

i suggest you match the error you are getting with the reasons stated in http://developer.symbian.org/wiki/in...n_supplier..22 and let us know.

[wizard_hu_]

The extra error code will not help (E51 is older than S60 3rd FP2), but you can still benefit from checking the list of possible causes: http://blogs.forum.nokia.com/blog/lu...er-debug-guide
Some blind guesses: older devices do not necessarily like if a file is signed multiple times, make sure that it is signed exactly with one certificate, the devcert. Disable online certification checks if they are enabled.
Show your .pkg file.

[Mikhail617]

Ok, I'll check out those links and see what I can learn.

here is my pkg file:

; Installation file for Symbian OS 9.x for generic console application
; Installation file for CallMode EXE
;
; This is an auto-generated PKG file by Carbide.
; This file uses variables specific to Carbide builds that will not work
; on command-line builds. If you want to use this generated PKG file from the
; command-line tools you will need to modify the variables with the appropriate
; values: $(EPOCROOT), $(PLATFORM), $(TARGET)
;

;
; UID is the exe's UID
;
#{"CallMode EXE"},(0xED93BF02),1,0,0

;Supports Series 60 v 3.0
[0x101F7961],0,0,0,{"S60ProductID"}

;Localised Vendor name
%{"Vendor-EN"}

;Unique Vendor name
:"Vendor"

"$(EPOCROOT)Epoc32\release\$(PLATFORM)\$(TARGET)\CallMode.exe"		  -"!:\sys\bin\CallMode.exe"

"$(EPOCROOT)Epoc32\data\z\private\10003a3f\apps\ConsoleMenu4_reg.rsc"	  -"!:\private\10003a3f\import\apps\ConsoleMenu4_reg.rsc"

[kiran10182]

Hmm. What does it show when you type the following on command prompt:

signsis -o yourDevCertSigned.sisx

And to list down IMEIs from the dev cert, try this link: http://wiki.forum.nokia.com/index.ph...s_in_a_DevCert

[Mikhail617]

it says "file I/O fault, cannot open CallMode.sisx."

Hmm. What does it show when you type the following on command prompt:

signsis -o yourDevCertSigned.sisx

And to list down IMEIs from the dev cert, try this link: http://wiki.forum.nokia.com/index.ph...s_in_a_DevCert

[kiran10182]

it says "file I/O fault, cannot open CallMode.sisx."

Interesting! Does signsis -o anySisxfile.sisx command give the same result with any other .sisx file?

[Mikhail617]

yup. I just tried it on a few of my older sisx files and I keep getting the same result.

Interesting! Does signsis -o anySisxfile.sisx command give the same result with any other .sisx file?

[kiran10182]

yup. I just tried it on a few of my older sisx files and I keep getting the same result.

Which is the SDK in use and which OS? Also see the version number of signsis. signsis -?

[Mikhail617]

S60_3rd_FP2_SDK_v1.1 and I am attempting to install on nokia E51 which I believe is S60 3rd FP1. The signsis is version 4.0.0.4.

oh and I am working in Windows XP version 2002, service pack 2

Which is the SDK in use and which OS? Also see the version number of signsis. signsis -?

[kiran10182]

This is strange! I have not encountered such an error with signsis -o ever.

Let's do it like this: Can you try submitting to OpenSigned Online and then install that signed sis on your E51. Does it work?

[Mikhail617]

It looks like OpenSigned Online won't work for this app as it requires MultimediaDD and the last bullet under service information for OpenSigned Online says "SIS files can be signed for all Platform Security Capabilities except CommDD, MultimediaDD, NetworkControl, DiskAdmin, DRM, AllFiles, TCB."

This is strange! I have not encountered such an error with signsis -o ever.

Let's do it like this: Can you try submitting to OpenSigned Online and then install that signed sis on your E51. Does it work?

[skumar_rao]

It looks like OpenSigned Online won't work for this app as it requires MultimediaDD and the last bullet under service information for OpenSigned Online says "SIS files can be signed for all Platform Security Capabilities except CommDD, MultimediaDD, NetworkControl, DiskAdmin, DRM, AllFiles, TCB."

Can you try just installing any sis file that falls under OpenSigned online category, even you can create one easily.

[Mikhail617]

I can certainly do that but I don't think it will tell us anything relevant to this problem since all my other sis files were self-signed and successfully installed using the same tools and phones I am using now (except DevCert). Deductive reasoning tells me that this problem is either specific to my latest app or to the OpenSigned Offline process so I am not sure what would be the point of signing and installing some other random .sis file. Do you agree?

Can you try just installing any sis file that falls under OpenSigned online category, even you can create one easily.