×

Discussion Board

Results 1 to 3 of 3
  1. #1
    Registered User
    Join Date
    Jul 2008
    Posts
    4

    Exclamation "Hello World!" signed sis from carbide.vs = "file is corrupted" on device (E65)

    Hi!

    environment:
    XP Pro SP2
    VS2005+SP1
    Carbide.vs 3.0.1
    SDK 3rd Edition MR (device target = E65 eg OS 9.1, french language)

    I am beginner with Symbian development and I am trying to install a .sis file (generated from SDK sample application) on device E65.
    I have generated "Hello World" application (.sis release build through GCCE) using carbide.vs default certificate (.cer and .key in 'Certificates' folder) and auto-signing carbide.vs property.

    After sis file deployment (with PC Suite or NAI), I select this .sis signed file on device (E65), and following error occurs :
    "File is corrupted" (well the true message is "Fichier corrompu"...)

    From carbide VS help, I read this section:
    ...
    "File is corrupted."

    There might be file(s) with invalid name(s) in the installation package, or the installation package might be corrupted, or a file is missing or cannot be found and installation can't proceed, or trying to install a file that is not recognized as a valid SISX file.
    ...

    Please could you give me some support to solve this problem ?
    What the difference between .sis and .sisx file ? Is .sisx file mandatory for OS 9.1 ? If yes, how to generate it ?
    May I copy sis/sisx file to specific folder on device ?
    How to get some details on "File is corrupted" (eg a tool to check a .sis file, ...) ?

    Thanks in advance.

    PKG file contents:
    ------------------

    ; E65.pkg
    ;
    ;Language - standard language definitions
    &EN

    ;Standard SIS file header
    #{"E65"},(0xeadb1213),1,0,0

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

    ;Unique Vendor name
    :"Vendor Name"

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

    ;Files to install
    "C:\Symbian\9.1\S60_3rd_MR\epoc32\release\gcce\urel\E65.exe" -"!:\sys\bin\E65.exe"
    "C:\Symbian\9.1\S60_3rd_MR\epoc32\data\z\resource\apps\E65.rsc" -"!:\resource\apps\E65.rsc"
    "C:\Symbian\9.1\S60_3rd_MR\epoc32\data\z\resource\apps\E65_reg.mif" -"!:\resource\apps\E65_reg.mif"
    "C:\Symbian\9.1\S60_3rd_MR\epoc32\data\z\private\10003a3f\apps\E65_reg.rsc" -"!:\private\10003a3f\import\apps\E65_reg.rsc"
    "..\help\E65_0xeadb1213.hlp" -"!:\resource\help\E65_0xeadb1213.hlp"
    "..\group\PrivacyStatement.txt" -"!:\private\eadb1213\PrivacyStatement.txt"

    ;Required for application to be covered by backup/restore facility
    "backup_registration.xml" -"!:\private\eadb1213\backup_registration.xml"

  2. #2
    Nokia Developer Moderator
    Join Date
    Feb 2006
    Location
    Oslo, Norway
    Posts
    28,672

    Re: "Hello World!" signed sis from carbide.vs = "file is corrupted" on device (E65)

    Though you could search for file is corrupted in the Wiki, and locate "S60 SW installer troubleshooting", your .pkg file seems to be correct actually.
    .sis: unsigned installation file (SIS=Symbian Installation System, or something really similar), it can not be installed because it is unsigned
    .sisx: .sis file, signed with some certification. This is the one you should send to the device - it might happen that automatically signed files from Carbide.vs also have .sis extension - I do not know.

    Command line:
    Code:
    makesis Your.pkg
    makekeys -cert -password test -dname "CN=YourName OU=MobileDev" test.key test.cert
    signsis Your.sis Your.sisx test.cert test.key test

  3. #3
    Registered User
    Join Date
    Jul 2008
    Posts
    4

    Lightbulb Re: "Hello World!" signed sis from carbide.vs = "file is corrupted" on device (E65)

    Hi all,

    thanks to wizard_hu_, I have found a solution.
    Firstly and just for information, search results from wiki has no more details than carbide.vs help about "file is corrupted".
    If someone knows about tool(s) to analyse/check sis/sisx files, it would be useful.

    But command lines posted by wizard_hu_ help me to find what is wrong.
    Signing sis file (or sisx but both succesfully install) using your test.cert results on correct installation and execution on device.

    Installation process using defaut carbide.vs certificate fails, I dont know why at this time but this is the only difference.
    I add your test certificate with carbide.vs and I can successfully build and deploy a sis file on E65 phone ;-)

    For information (both certificates headers) :

    carbide.vs default certificate header (fails on E65):
    Maybe C=FI should be replaced with CO=xx ?
    -----------------------------------------------------
    C:\Nokia\Tools\Carbide_vs30\Certificates>makekeys -view Carbide_vs.cer
    Certificate:
    Data:
    Version: 3 (0x2)
    Serial Number: 0 (0x0)
    Signature Algorithm: dsaWithSHA1
    Issuer: C=FI , O=Company, OU=Development , CN=Developer /Email=test@comp
    any.com
    Validity
    Not Before: Oct 26 14:47:49 2007 GMT
    Not After : Oct 25 14:47:49 2008 GMT
    Subject: C=FI , O=Company, OU=Development , CN=Developer /Email=test@com
    pany.com
    Subject Public Key Info:
    Public Key Algorithm: dsaEncryption
    DSA Public Key:
    pub:
    6b:dc:23:b9:1b:76:ab:6e:f1:5a:b7:f6:33:3b:f6:
    ab:8c:b0:cb:1d:5c:17:44:81:b8:fa:72:1d:83:8c:
    dc:83:6a:c2:87:3a:38:74:51:20:7b:9a:bc:b5:a1:
    84:09:35:5a:8b:15:7e:e1:f5:7d:01:72:d6:a6:bc:
    f8:41:bd:41:a0:46:27:01:92:9c:77:c4:2a:2e:60:
    f6:22:93:d7:a0:8a:08:5b:6d:27:ca:fa:c0:21:e1:
    35:01:4a:63:c1:15:a0:0c:24:b7:a6:61:a4:24:ca:
    d1:7b:c8:6a:c1:75:26:c7:f4:5c:da:cb:a4:3e:d3:
    34:25:f9:df:0e:6c:12:26:81:d8:6b:9d:91:58:42:
    7d:38:b7:69:05:a2:77:c1:f4:5e:c9:88:cb:19:2d:
    e8:41:39:8a:25:30:f6:24:94:27:b0:4e:0f:df:53:
    a9:8b:0e:e6:f1:17:6a:a9:5d:a1:8f:cc:0e:c6:94:
    4a:43:51:6b:61:1d:cb:70:70:57:f7:41:57:e3:c2:
    e3:9a:dd:3d:21:d1:fc:8a:98:87:2a:e9:c0:a6:e8:
    1d:c1:c1:fc:ad:54:2d:ab:4e:04:e7:e2:63:60:a9:
    b7:be:c1:bf:d8:00:58:d1:dd:00:43:63:52:fe:ad:
    8a:40:53:b5:b8:da:96:f0:f6:ce:0f:6e:8f:28:2b:
    89
    ...

    test certificate header (OK on E65):
    ------------------------------------
    Certificate:
    Data:
    Version: 3 (0x2)
    Serial Number: 0 (0x0)
    Signature Algorithm: dsaWithSHA1
    Issuer: OU=MobileDev, CN=YourName
    Validity
    Not Before: Aug 21 09:42:53 2008 GMT
    Not After : Aug 21 09:42:53 2009 GMT
    Subject: OU=MobileDev, CN=YourName
    Subject Public Key Info:
    Public Key Algorithm: dsaEncryption
    DSA Public Key:
    pub:
    00:84:18:19:80:d1:a0:6a:2a:02:c1:cb:01:20:f9:
    fd:c0:94:3b:6c:01:6d:bd:b9:7e:61:21:96:15:41:
    62:6a:72:a3:37:d3:d5:b4:ac:b4:35:6b:59:4c:b1:
    d3:51:a2:4a:9c:c0:e3:3f:46:d0:d8:0c:12:88:fa:
    99:26:50:ed:a0:7f:24:eb:0f:35:71:5d:0d:f1:bf:
    37:2a:9b:60:96:b2:7d:fb:6f:e5:87:ec:f3:a9:60:
    d3:99:32:42:9b:34:ac:6d:09:28:69:ba:70:ae:04:
    b9:bf:3f:b6:c5:66:b0:5e:12:2f:92:d2:da:9e:12:
    03:fe:f7:a4:77:58:b7:c0:b2
    ...

Similar Threads

  1. Old unsigned sis and new Symbian Signed
    By y.a.k in forum Symbian
    Replies: 22
    Last Post: 2008-07-22, 07:44
  2. Replies: 9
    Last Post: 2008-07-20, 05:55
  3. Startup List API and self signed sis
    By tal.shahar@mobile-mx.com in forum Symbian
    Replies: 10
    Last Post: 2007-03-22, 00:10
  4. Bluetooth Security: What exactly is an untrusted device?
    By rahulmcs in forum Bluetooth Technology
    Replies: 1
    Last Post: 2005-12-02, 06:26
  5. unable to merge two sis file on device .
    By amardeep in forum Symbian
    Replies: 0
    Last Post: 2003-04-25, 08:08

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×