Signing using Mobile signer(in mobile itself)

Signing using Mobile signer(in mobile itself)

-Caps OFF using helocarbide or secman.sis or rompatcher

Run Mobile signer 1.03 on your phone
* use X-plore or......:

- Copy cert.cer & key to E:\private\EC696702 or E:\private\EC696702-> click Overwrite all

- Copy 00000001 file to C:\resource\swicertstore\dat
Make swicertstore\dat if it's haven't

- Restart phone.

* Open Mobile signer-> click sis file->options->SelfSign
file sign(.sisx) near flie .sis

Dowload mobile signer:http://www.box.net/shared/0k9tojqiuu

key & cert files :http://www.box.net/shared/0k9tojqiuu

00000001 files :http://www.box.net/shared/nuqgdea0uq

Offline Apps Signing Final Working 100%

Offline Apps Signing Final Working 100%



Offline Apps Signing Final Working 100%

Full & Final Working Signing Tutorial for Signing apps for S60 v3 apps.Tried &

Tested on Nokia N73 ME.

Files U will need:
Quote:
1) X-Sign Setup
2) Signsis.exe
3) Certificate File (Cert20Years.cer)
4) Key File Name (Key20Years.key)
5) Key Password: 12345
I have included all the files in the attachments

Instructions:
Quote:

1. Extract All to a folder: C:\X-Sign
2. Install X-sign by running "X-Sign Setup.msi"
3. Run XSign
4. Select "Files to Process Unsigned Files" [1] >> Go To C:\X-Sign & Select: Signsis.exe>> Done
5. Select "Certificate File" [2] >> Go To C:\X-Sign & Select: Cert20Years.cer >> Done
6. Select "Key File Name" [3] >> Go To C:\X-Sign & Select: Cert20Years.key >> Done
7. In the Filed "Key Password" [4] Enter: 12345
8. Select the [+] Sign & Go to the Folder you have stored your Unsigned.Sis File (E.g:Advanced.Device.Locks.Pro.v2.00.37. S60v3.SymbianOS9.1.Unsigned.sis)>> Select the File >>Done
9. Click "Start"
10. The Program should stall for a few seconds & return with a Response "Completed 1/1"
11. If it gives the above response then the App is signed & a folder will opened showing the file as Advanced.Device.Locks.Pro.v2.00.37.S60v3 .SymbianOS9.1.signed.sis.
12. Transfer the file to the Phone via, BT/Data-Cable/IR etc & install it.
13. Done. Enjoy a SIS file signed for 20 Years. You can Store this file someplace safe for use at a later stage on any s60 v3 Device..

Download Here For Free
http://www.box.net/shared/gbsikrt55l

Sign Any Unsigned Files using secman.sis

Sign Any Unsigned Files using secman.sis

In order to install "Unsigned" releases from BiNPDA only and hack your phone{i.e to view all private folder}, you need to go trough a one-time procedure.

You will need to run "SecMan.exe", This program allows you to install all unsigned files from BiNPDA without signing them every time...

1)Install secman.sis in your phone memory.

2)Application is too simple to use..

Open the Secman from your phone

"Turn Plat security OFF"

This option will Hack your phone in other words you will be able to enjoy the Symbian Freedom, like any other hacked phone you can Edit and move Private files n folders..
When your phone is hacked you see this screen :

You can " Turn plat security ON " when you are Done.

Now the Important part..


" Install Root certificate " With this you can install unsigned files from BiNPDA, you will not be prompted for any certificate errors during installation of unsigned files like Normal Signed files.

" Restore Default " This will Remove all Root certificates and Remove Capabilities, making you phone like you used to use your phone before hacking.


" Uninstall Secman " will remove it from your phone.

NOTE :
Please keep in mind, if you format / upgrade your phones firmware, you'll need to do steps 1 & 2 again and after that manually install those apps from Application Manager.

Benefits :
Your Phone is now Hacked plus
Now you can install Unsigned files from BiNPDA and your Phone will not ask for Certificate errors and Blah blah..

No Certificates no symbiansigned...!!

Download Here For Free
http://www.box.net/shared/e7pb1jpdlv

Hacking s60v3 mobiles using Hellocarbide.sisx and installserver.exe

Hacking s60v3 mobiles using Hellocarbide.sisx and installserver.exe

1:Install xplore.sis and hellocarbide.sisx in phone memory(a must)

2:Open x-plorer provided.Goto options->tools--Config and tick on 1st four options.Goto main page of x-plorer(i mean back) then press Menu Key so that u leave it in background

3:Start HelloCarbide->Options->Menu1. it will say 18 messages. Say YES to all of them. It will crash. That is OK

4:Move installserver.exe to Phone,

5:Switch to X-plorer,Move installserver.exe to c:/sys/Bin

RESTART YOU DEVICE, its compulsory......

Now you can install any unsigned application in your s60v3 mobiles.

get xplore.six from http://www.box.net/shared/av3hv8ojb8

get xplore.sis keygen from http://www.box.net/shared/l3ncrlhgex

get installserver.exe from http://www.box.net/shared/ljndtab2im

get hellocarbide.sisx fromhttp://www.box.net/shared/edzmifhbr5

The ROMpatcher Patches Index

The ROMpatcher Patches Index

No Camera Capture Sounds
Confirmed Working on: Nokia N95, Nokia 6220 Classic
Confirmed not to work on: Nokia E51, Nokia N81, 5700
Not needed on: None
Download:Download Here For Free
Details: This Patch will mute the Camera Sound 4 (from camera settings, change Tone 4 to be used)

No Calendar in Active Standby
Confirmed Working on: Nokia N95, 5700
Confirmed not to work on: Nokia 6220 Classic
Not needed on: Nokia E51
Download:Download Here For Free
Details: This Patch will remove the Calendar bar from the Active Standby. for this to take effect, you need to disable and re-enable Active Standby from the Settings, or use latest ROMPatcher, and set this patch to be run on Startup.


No Search in Active Standby
Confirmed Working on: Nokia N95
Confirmed not to work on: Nokia N81, Nokia 6220 Classic
Not needed on: Nokia E51, 5700
Download:Download Here For Free
Details: This Patch will remove the Search bar from the Active Standby. for this to take effect, you need to disable and re-enable Active Standby from the Settings, or use latest ROMPatcher, and set this patch to be run on Startup.

No To-Do in Active Standby
Confirmed Working on: Nokia N95, 5700
Confirmed not to work on: Nokia 6220 Classic
Not needed on: Nokia E51
Download:Download Here For Free
Details: This Patch will remove the To-Do bar from the Active Standby (This is not visible if there are no active To-Do's). for this to take effect, you need to disable and re-enable Active Standby from the Settings, or use latest ROMPatcher, and set this patch to be run on Startup.


No WLAN Search in Active Standby
Confirmed Working on: Nokia N95
Confirmed not to work on: Nokia 6220 Classic
Not needed on: Nokia E51, 5700
Download:Download Here For Free
Details: This Patch will remove the WLAN Search bar from the Active Standby. for this to take effect, you need to disable and re-enable Active Standby from the Settings, or use latest ROMPatcher, and set this patch to be run on Startup.


Change the Whole *#0000# Screen
Confirmed Working on: Nokia N95, Nokia E51, 5700
Confirmed not to work on: None
Not needed on: None
Download: Download Here For Free
Details: This Patch will change the whole screen thats displayed when you type *#0000# in the Idle display.
Note: this Patch needs additional files to be copied from the Z:\ Drive to the Memorycard.


No Running App indicator Circle
Confirmed Working on: Nokia N95, Nokia E51 (*1), 5700
Confirmed not to work on: None
Not needed on: None
Additional Files Needed: 1
Muuh.mif to be placed in C:\resource\apps\muuh.mif
Download:Download Here For Free
Details: This Patch will remove the little Circle seen in the menu on the Icon of a Application that is currently running


Change the Browser On Key 0
Confirmed Working on: Nokia N95, Nokia N80
Confirmed not to work on: 5700
Not needed on: None
Download:Download Here For Free
Details: This Patch will change the Application that will be opened when you hold the 0 (zero) key pressed in Idle display


Extra Voice Commands
Confirmed Working on: Nokia N80
Confirmed not to work on: 5700
Not needed on: None
Download:Download Here For Free
Details: This Patch will Allow you to Change Applications available in Voice Commands.



Change SWIpolicy Path
Confirmed Working on: Nokia N95, Nokia N80, Nokia 5700, Nokia 6220 Classic
Confirmed not to work on: None
Not needed on: None
Download:Download Here For Free
Details: This will change the Path of the swipolicy.ini file used, allowing installing of applications not normaly possible to install
Note: This Patch needs additional files to be coped from Z:\ to E:\ and editing of it, read below for Instructions



Enable hidden Menus
Confirmed Working on: Nokia N95, Nokia N80, 5700
Confirmed not to work on: None
Not needed on: None
Download:Download Here For Free
Details: This Patch will Show the Menu Options that are hidden for some reason.
Note: All options shown will not work, but there can be some really usefull options, such as renaming


C before Z Patch
Confirmed Working on: Nokia N95, Nokia N80
Confirmed not to work on: None
Not needed on: None
Details: This Patch will change about 10% of the files to be used from C:\ Drive instead of the Z:\ Drive, so by this, its possible to change something on files already on the phone, such as default icons or names
Note: This is a Special Patch, it Needs a Computer for Generating the Patch
Additional Files needed: 1 Archive
Download Here For Free


Midlet Permissions Hack
Confirmed Working on: Nokia E65
Confirmed not to work on: None
Not needed on: None
Details: This overrides the Java policies, such as asking for connectiong to internet every time
Note: This is a Special Patch, it Needs additional patches to work
How to use: Appy c2z patch (found above), then copy the contents of Java_permissions.zip to c:\System\data\midp2\security\policy\ (you might need to make the folders by yourself)
Additional Files needed: 1 Archive
Download Here For Free


-Download All Patches:
Download Here For Free

ROM patcher method of Hacking s60v3 mobiles

ROM patcher method of Hacking s60v3 mobiles

What is ROMPatcher?

ROMPatcher is an amazing piece of code, application allowing you to patch the ROM in a very easy and secure way. We are only limited by our imagination when it comes to the number of uses for it. There is no real danger in using it because it maps the ROM into RAM and then modifies it, so the patch is not permanent and a phone restart will clean all changes made by the patcher. After restart, you have to manually enable the patches again.

Install the ROM Patcher in Phone memory.
Place the Patches in "E:\Patches" folder(you need to make patcher folder)

Another usage of ROMpatcher is to gain access of hidden folder
(Private,sys and resource folders)

To disable caps (can view hidden folder): Select Options->Disable caps
To enable caps (hidden folder ivisibility is off) : Select Options->Enable caps



Download Here For Free

Signing S60v3 using SIS Files Very Easy (Only for Hacked Mobiles)

Signing sis files Easy [only for hacked phones]

1. Click Here And Download Required Files> Extract it > RUN GenialSIS.Exe

2. create certificate
Enter your phones IMEI (you can find by entering *#06#)& press generate.

3.Symbian signed certificate
skip this step

4.Sign SIS/SISX
skip this step.

5.Import
Open/browse to cert.cert & key.key files (included in sign keys.zip folder in attachment). If you want give password.
press import.

6.Now go to (3)Sign sis/sisx

In profile give a desired name. Now open un-signed file you want to sign. Press Sign! tab. All done. your signed file will go in folder on which your doing all this or in the same folder where is your unsigned file.
Download Here For Free

Signing SIS Files

Signing SIS Files - Creating Certificate and Private Keys.

Do it yourself!!!

download the attach file to create certificate, private keys and signing your sis files... I included the manuals and syntax on how to do it...

for simplier signing use the BiNPDA SIGNSiS v0.1 to sign sis file. also included...

This article is specific to S60 3rd Edition development or newer. From S60 3rd Edition, which is based on Symbian OS 9, a user can install only signed applications. If an application requires basic capabilities only, it can be signed with self−signed certificate. Basic capabilities include LocalServices, Location, NetworkServices, ReadUserData, UserEnvironment and WriteUserData. An application that does not require any capabilities can also be signed with self−signed certificate.

The drawback of self−signed certificate is that a user will be prompted a warning dialog. It says that the application is not trusted and the user can decide whether or not to continue the installation. The warning dialog does not appear when the application is signed via Symbian Signed.

Following is the example which illustrates the Self−Signing procedure.

Step−1 Creating Certificate and Keys
From your Desktop Screen: Start−> Run −> Cmd then go in your Sis file path using cd DOS command.

C:\HelloWorld\sis> makekeys −cert −password World123 −len 1024 −dname "CN=World User OU=Development OR=WorldCompany CO=FI EM=World@test.com" WorldKey.key WorldCert.cer

This will create WorldKey.key and WorldCert.cer files which you will need to sign your HelloWorld.Sis file in the following statement.

Step−2 Signing Application

C:\HelloWorld\sis>signsis HelloWorld.sis HelloWorld.sis WorldCert.cer WorldKey.key World123

Note: Here you may find that World123 is the password.

Finally you will get your Self−Signed certified HelloWorld.Sis file. Install it on the device. Have fun !!!


Download Here For Free

Drakkarious Hack 3.01

Drakkarious Hack 3.01 For S60v3 SymbianOS 9.1/9.2/9.3 - Install Unsigned And Expired SIS Filess

Drakkarious Hack - All applications installer {unsigned and Expired Files} update 01/10/2008

Drakkarious 3.01 FP1, FP2 & PreFP1

Have you ever wanted to install an unsigned file without having to sign it like we used to on s60v2 phones?
Have you ever wanted to send an application over bluetooth and install it right away on the receivers phone?

Well this is your lucky day, Drakkarious.sis, an application especially developed for this very same reason.

All you have to do is install this application, follow the on screen instructions wich you easly learn after doing it 1 time and your ready to hack any phone, anywere...

With this app you can install:

Unsigned, Signed, Binpda, Non-Binpda, Dated, Out-Dated files etc etc etc... Give it a try and you'll see. Even n-gage cracked games will be installable after this hack.

Inside instructions:

Change phone date to 15-05-2007

Drakkarious Hack Compilation.

This program will install:
CapsOn
CapsOff
HelloCarbide
X-plore

*Note: If you have any of these programs installed on your mobile there is no problem continuing the installation, however, this ones have been tested, none others, so if you have any trouble during the procedure uninstall the ones you have and re-install Drakkarious.sis.

After installing please follow this procedure:
1.-Run X-plore and press "0", tick the 4 boxes (dont un-tick if ticked already)
2.-Without closing X-plore switch to the menu and run hellocarbide
3.-Inside hellocarbide press options and chose Menu1 and answer "yes".
4.-Go back to X-plore and extract installserver.exe and CProfDriver_SISX.ldd from your c:\hack.rar into c:\sys\bin
5.-Restart your phone.
6.-Install whatever you want on your phone, even if it is unsigned

Run capsOff if you wish to see private folders using X-plore and capsOn to hide them again
Note: I advice you to always hide private folders after you have completed whatever you wanted to do inside them...

Enjoy... Signed(lol) Drakkarious

Special thanks to:

BinPda
farhazadeeb

NOTE: AFTER COMPLETING YOU MUST RESTART YOUR PHONE TO BE ABLE TO INSTALL ANY APP, AND REMEMBER TO ALWAYS PUT YOUR PHONES DATE BACK TO THE PRESENT AGAIN, ALWAYS CHOOSE THE CORRECT VERSION FOR YOUR PHONE, AND IF YOU DONT YOULL NEED TO MANUALLY REMOVE INSTALLSERVER.EXE FROM C:\SYS\BIN\ USING X-PLORE AND HELLOCARBIDE... IF YOU MAKE THIS MISTAKE PLEASE REPEAT THE PROCESS USING THE CORRECT VERSION: FP1 & FP2 OR PREFP1

Devices list:

Pre-FP1 devices:
-------------------
Nokia N77
Nokia E61i
Nokia E65
Nokia N93i
Nokia N91 8GB
Nokia E62
Nokia E50
Nokia 5500
Nokia N93
Nokia N73
Nokia N80
Nokia N71
Nokia N92
Nokia E70
Nokia E60
Nokia E61
Nokia 3250

FP1 devices:
---------------
Nokia 6124 classic
Nokia N82
Nokia N95-3 NAM
Nokia E51
Nokia N95 8GB
Nokia N81
Nokia N81 8GB
Nokia 6121 classic
Nokia 6120 classic
Nokia 5700 XpressMusic
Nokia 6110 Navigator
Nokia E90 Communicator
Nokia N76
Nokia 6290
Nokia N95

FP2 devices
-------------
Nokia 5320 XpressMusic
Nokia N78
Nokia N96
Nokia 6210 Navigator
Nokia 6220 classic

Specific devices
-------------
Nokia 3250 v4.14
Nokia 3250 v4.60
Nokia 5500
Nokia E50
Nokia E51
Nokia E61

VersioN 3,01(3) <- released on 01 \ 10 \ 2008 The Version of X-plore installed with this package is 1.22, you must update it after hacking

Download Here For Free

How to Re-package the SIS file

How to Re-package the SIS file

1. Select Menu Extras --> Configurations.

2. From configurations window, on application setting group, check the item 'Use defined offset when export session'.

3. Uncheck item 'Extract all files to the same folder' and click OK button.

4. Open the SIS file.

5. Extract SIS file.

6. At this step, edit the PKG session as required.

7. If SIS file that opened(Item4) is Symbian9.x SIS file and that SIS file has embedded sis file(s) (otherwise go to Item8)which you will see the multiple of tabs, the first tab is the main sis file and the another one(s) is the embedded sis file which within main sis file.

To re-build up main sis file you must re-build that embedded sis file(s)again by select that embedded sis file tab and build.

After the embedded sis file(s) was built then you are ready to re-package or re-build main sis file by select the first tab on the screen.

Before you start to re-build, make sure you have alter the path of embedded sis file(s) to the embedded sis file which you re-built and save to that path. Note:

Due to 3rd sis file has embedded its embedded sis file as the contents which indices with SISController then you extract 3rd sis file that contains embedded sis file inside, all of embeded sis file will be extracted as contents in that embedded sis package.

This perfom one extraction for all contents in main 3rd sis package. This unlike the older sis file version which its embedded sis file will be stored in the main sis package as sis file.

8. If SIS file that opened(Item4) is Pre-Symbian9.x sis file you can re-built it now by go to menu Tools -----> Build SIS File of Press F3

What is Symbian OS v9.x Platform Security

What is Symbian OS v9.x Platform Security

It is a fine-grained way to efficiently restrict or completely prevent
unauthorised access to sensitive APIs and data on the mobile
phone while keeping the device open to developers.

It follows a per-process capability-based model
It compartmentalises the system, according to access capabilities,
to APIs and files
It makes sure that the users can make policy decisions they
understand
It is Kernel mediated but server enforced

Why a finer-grained Platform Security model ?

Phones are open, networked & data communication devices
• Users expect their phones to be highly reliable
• Users care about their privacy – and their phone bills
• Mobile networks are not like the internet – they can restrict
access
• Existing “Perimeter Security” model enables unrestricted
access to all phone capabilities once installed

Benefits of Platform Security

For developers

Maintains network operator & user confidence in open
phone environment
…
Grows opportunity for mass market applications,
content & services
…
enables m-commerce applications & high value DRM
content

For network operator

Protects network & handsets from malware
…
Protects customer data & privacy

New Symbian OS concept – Data Caging
Separating code from data
• File-system structure changes
…
\sys, \resource, \private\, \
…
Executables will be placed in and only run from \sys\bin
• Processes are confined to their own part of the file-system
• Access rules based on directory path
…
Single user, no access control list required
…
No extra storage needed
• Support for removable media file systems
tamper evidence for binaries

SISWare v4.7.Built.1722607

SISWare v4.7.Built.1722607



SISWare is the best tools for Symbian Application Install package builder. SISWare providing as freeware and usage limitation of this software described on License item.
SISWare 4.6 supports sisx and sis file creation and extraction for Symbian9.x and pre-version.

Supports UIQ3.x platform and most bugs fixed from last version.

Standard features including:
* Open SIS file or pkg script file.
* Extract files from sis package.
* Edit SIS file or pkg script and re-build.
* Compile sis file or pkg script.
* Build sis file with multiple options.
* Batch extraction of multiple sis files.
* Sign and UnSign sis file and create self-signed certificate file.

What's new in SISWare 4.7 :
* New Product / Platform ID's added, UIQ 3.0, UIQ 3.1 and Series60 v3.
* PKG compiler bugs fixed for UIQ v3.x platform and signature strings.
* UIQ 3.x sis file gathering information bugs fixed.

Release Note
Known Issue :
When the sis file contains special characters such as @ # ! &. These character is reserved for special character in PKG file. Then some exception will occur when compile the pkg script, the file path which contains these chars will be set as invalid and all lines of pkg are ignored. To get the uncompiled pkg script, use the SIS Explorer tool inside the SISWare and select the button PKG Script to show it. Contents in sis file still able to extract even the extract path contains these special characters.

System requirements :
* Windows Me, 2000 or Windows XP
* CPU Pentium 200 MHz or higher
* 20 MB Hard Disk space
* 128 MB of RAM

http://www.box.net/shared/s3e5skq3c4

How to sign sis file for Symbian9.x

How to sign sis file for Symbian9.x

Introduction

In S60 3rd Edition application development all .sis files must be signed before installing

them to a device. When an application requires no capabilities or utilizes APIs which are open

to all, you can use the Self Signed certificate. This can be used when testing an application in

one’s own device or when shipping the application. Using the Self Signed certificate is recommended for freeware applications using unrestricted capabilities.

Self Signed Certificate

When an application requires no capabilities or utilizes APIs, which are open to all. This can be used when testing an application in one’s own device or when shipping the application.

Note: The application is regarded as Untrusted if signed with the Self Signed Certificate.

This process is recommended for freeware applications using unrestricted capabilities(User grantable capabilities)

Developer Certificate

When testing the application in developer’s own device(s). This certificate is received from Symbian.

The Symbian Developer Certificate can be used by developers to sign their applications in order to obtain the restricted capabilities for device testing. The certificate is restricted to a certain set of IMEIs and the set cannot be changed. There are a few requirements to get a Symbian Developer Certificate.

Symbian Signed

Mandatory if the application is using capabilities beyond the scope of APIs open to all and the application is shipped.

This is the sets of certificates respeected to APIs utilized.

60% of APIs (no restricted certificate)

User-Grantable Capabilities (need atleast self signed certificate)

ReadUserData

WriteUserData

NetworkServices

LocalServices

UserEnvironment

Symbian Signed Capabilities (need Symbian signed certificate)

User-Grantable Capabilities + sets of following

Location

ReadDeviceData

WriteDeviceData

PowerMgmt

SurroundingsDD

ProtServ

TrustedUI

SwEvent

Licensee/Platform Approval Capabilities (need Symbian signed certificate)

Symbian Signed capabilities + sets of following

Manufacturer

DRM

TCB

S60

DiskAdmin

AllFiles

CommDD

MultiMediaDD

NetworkControl

For more access capabilities details see also Enum TCapability

Sign SIS file

To self-sign the sis file with SISWare you must have the key file(.key) and certificate file(.cer).

The key file and certificate file may be given Symbian Signed Certificate from trusted Certificate Authority such as Verisign

and Symbian Signed or create your own self-sign certificate

To use the SISWare's sign tool, go to menu Tools ---> Digitally Sign Tools.

At Sign SIS File tab, follow these steps.

1. Specifile original SIS to be signed, this file will not effacted by signing process. The result of signing process is the target signed sis file.

2. Specify the target sis file which will create.

3. Specify key file

4. specify certificate file

5. Specify password(if that certificate file encrypted with password)

6. Specify algorithm. If you use symbian tool named makekeys.exe (even use in SISware) to produce key and certificate file, please choose DSA algorithm because that file created with that algorithm.


7. Click Sign button.


If no error occurs the signing will complete with some signature information that given by certificate file that seen from Signing Info box. Then this signed sis file will be able to install to Symbian9.x OS devices.




Create self-sign certificate file


You can create your own key and certificate file to use in signing process and your sis file will be regarded as Untrusted. To create key and certifiate file, go to Create Self-Signed Certificate tab in Digitally Sign Tools window.



Selct option create a private key and self signed certificate. Then follow the steps.

1.Specify key file to create.

2. Specify certificate file.

3. Specify common name(issuer) organization unit(name of certificate issued for), country, key length, password, email address and algorithm(DSA default)
4. Click Create button, then SISWare will call makekeys.exe for creation.

When command window(DOS window) appears, please follow the instruction on the screen, it may ask you to provide password or not(if you are not given password yet)
Then it asks you to moving the mouse on the screen or input the keyboard then it collected the data and after that please wait for a while until the window close and the create process completed.

Use these key file and certificate file to self sign your sis file, if you provide the password to make key and certificate file, when you signing with these file you must give the same password.

How to build sis file for Symbian9.x

How to build sis file for Symbian9.x

This section described about creation of Symbian9.x sis file, firstly make sure the current mode is Edit Mode, if not go to menu Mode ---> Edit Mode. Use the following guide to create your sis file.

1.Select the device platform by select menu Extras ------> Change Device Platform as shown in Picture21. Then select option 'Series60 3nd Edition / Symbian v9.x'.

Picture21. Select Device Platform

2.Select menu File ------>New Session, then the screen will show as shown in Picture22.

Picture22. Session Editor Window after New Session was choosen.

2.Assuming that we want to copy file on the computer to the mobile device. Double click at the Command Box at the Copy File node under the Entry as shown in Picture23.

Picture23. Quick Menu

3.After double click at Copy File node, the window named Entry - Copy File will show as in Picture24.

Picture24 Entry Editor Window.

4.Specify source file, see the Source file input box and type in the full path of file to be installed to mobile device or click at the small right hand button to browse the files.

5.Specify target file, see the Target file input box and type in the desired location on mobile device which the source file to be installed to.

6.The target Type List is the guide for specific location on mobile device depending on file categories. And you can use Target Drive List to specify the Drive of installation.

7.If you want to run this file during install/uninsatll process, choose File Option and select Run File and it's options.

8.If you want to open this file during install process, choose File Option and select Open File and specify MIME type and it's options.

9.If you want to specify the language dependent file, select the option Language Dependent. After select this option you'll see the list of languages and source files. Then double click at the Source File portion as in Picture25., the dialog File Open will show.



Picture25. Language Dependent option.

10.Finally, click at Entry Placement button group as in Picture26. Due to this example we want to copy new file then click at Place New button.


Picture26. Entry Placement button.

11.The entry that you make will paste to the Session Editor Window at the lastest line as show in Picture27.


Picture27. Session Editor Window after placed the new entry.

12.From this step you can add other new entries by doule click at the entries nodes under Entry gouup in Quick Menu panel as show in Picture28.


Picture28. The entries added to Session Editor Window.

13.After you added the entries, you can configures your sis packae such as package name, requisites or dependencies or component that your application depends on and so on.

14.To configures package information see the Command Box and double click at Package Info node under Package. Then the Package Info window will show as in Picture29.


Picture29. Package Info Window.

Save SIS File As input box, specify the target sis file output after build.

App UID input box, specify the application UID or sis package UID.

Major Version input box, specify major version of sis package.

Minor Version input box, specify minor version of sis package.

Built Number input box, specify built number of sis package.

Product/ Platform Major Version input box, specify major version of product/ platform.

Product/ Platform Minor Version input box, specify minor version of product/ platform.

Product/ Platform Build Number input box, specify built number of product/ platform.

Product / Platform ID input box, specify compatibility ID of product or platform.

Device Platform input box, specify the compatibility of device platform.

Package Type input box, specify the type of package such as contained application package.

Package Option input box, specify the option of the package.

The following input box refer to Sign SIS option

Key File input box, specify private key file for self signed your sis file.

Certificate File input box, specify certificate file for self signed your sis file.

15.To configures package name see the Command Box and double click at Package Nmae node under Package. Then the Package Name window will show as in Picture30.

Picture30. Package Name Window.

The device support languages list on the right side is the list of application or component name that will be show to user as his phone supported language. Double click at Application's Name portion to edit the application's name.

16.To configures requisites see the Command Box and double click at Requisites node under Package. Then the Requisites window will show as in Picture31.


Picture31. Requisites Window.

Specify the dependency name and its UID, version (currently installed on the mobile device)which your application dependent.

17.To configures vendor and logo see the Command Box and double click at Vendor / Logo node under Package. Then the Vendor / Logo window will show as in Picture32.


Picture32. Vendor /Logo Window.

18.After configures all information and entries, Select menu Tools ------> Build SIS File to build your sis file.

19.Sign your SIS file.

see also How to sign Series60 3rd SIS file

Steps to Get Latest Firmware for s60v3 Mobiles

Steps to Get Latest Firmware for s60v3 Mobiles

To find out if new software is available for your particular Nokia device model, you need to know your device product number.

1. Turn the Nokia device off
2. Remove the battery from your Nokia device to read the 7-digit product code located on the white label as shown below



3. Check if new software is available for your device at Device software update or your local Nokia website and enter the product code into the field at
   
4. Step 2/2: See if there's an update.

Please note that your mobile service provider, operator, or carrier may not have approved the latest Nokia device firmware available.

Nokia produces many different variants of each product (for different countries and languages) and not all variants have the latest Nokia device firmware. It is our priority to update all variants as quickly as possible, and we apologize for any delay. New software may become available at a later date, however, so please check back soon.

Signing Error Messages Means In S60 3rd Edition

Signing Error Messages Means In S60 3rd Edition

Message: Certificate error. Contact the application supplier.

Hint: You may have tried installing unsigned application.

Note that signing is mandatory S60 3rd Edition.You can use self-signed certificate
or developer certificate from Symbian Signed to sign your application.

Message: Unable to install. Constrained by the certificate.

Hint: This message pops up when you attempt to install developer certificate in
the unsupported device.

The developer certificate from Symbian Signed can only be used in a limited number
of devices. Remember that you have to send your IMEIs to Symbian Signed when
requesting certificate. You cannot use the certificate in other devices that
is not in your IMEIs list.

Message: Required application access not  granted.

Hint: Check that your certificate can be used to sign
all capabilities needed by your application.

For example, if you use self-signed
certificate, you can only sign basic set capabilities, i.e. NetworkServices,
ReadUserData, WriteUserData, LocalServices and UserEnvironment.

If your application requires one of the extended capabilities, for example
SwEvent, you cannot sign it with self-signed certificate.

In this case, apply for developer certificates from Symbian Signed.

Message: Unable to install a protected application from an untrusted supplier.

Hint: If you use self-signed certificate, make sure that your application
uses unprotected UID, i.e. 0xA0000000 - 0xAFFFFFFF.

If you use protected UID (0x20000000 - 0x2FFFFFFF)
or legacy UID (0x10000000 - 0x1FFFFFFF), you will get this message.

Message: Unable to install.

Hint: This message may come up when your installation file (.sis/.sisx) copies
files to other applications private folder, i.e. \private\uid.

Note that Symbian 9.X introduces data caging concept, it means you don't
have access to other application's private folder.sys folder and cant
modify resource folder content.

Message:  Expired Certificate 

Hint: Do this Set the phone date back by 7-8months..

Message: Update error

Hint: Uninstall any previous version of the application, then switch on/off
the phone and install again..

Nokia Firmware upgrade using NSU(Nokia software Upgrader)

Nokia Firmware upgrade using NSU(Nokia software Upgrader)

Do you use a Nokia phone? Are you not satisfied with the current software in the phone? Have you come across any software error in the phone? Are you not satisfied with the battery life-time of your phone ?

If yes, do read this:

‘People’, once they buy the Nokia phone are not aware of the fact that updates for their phone would be available approximately every month. I just want to spread the awareness of it.

‘Firmware’ is the software that runs on your Nokia phone. It is important for you to keep your phone firmware updated. The various applications which interact with the hardware of the phone as well as those which mainly provides an user interface also gets updated. New applications, features are provided.

Requirements for Firmware update on PC side:

• Nokia Software updater ( NSU) is the software on the PC which assists in the firmware installation on your phone. So, to find out whether your phone has a ‘firmware update’ option and to download appropriate NSU check: NSU. Once you have downloaded the NSU, install it in your PC.

• Windows Xp/Vista, minimum of 256 MB RAM,
• (better to use 512MB RAM as 256MB RAM will give effective RAM of 248MB)
  
• 1GHz processor.
• High speed ( Broadband) internet connection.
• UPS backup for the PC. Make sure their is no power failure during updation.

Requirements for the Phone:

• Phone should be switched ON.
• It should have a valid SIM card.
• General profile should be activated.
• Its is very important for the phone to be fully charged prior to updation / connect the charger during the process. Otherwise, it could cause unrevertible damage to the phone.
• Backup your phone memory and/or memory card. Phone memory can be backed-up on the memory card. To do this. go to: Menu->Tools->Memory->Options->Backup phone memory. OR you can backup using Nokia PC Suite. In the PC suite, you have a application ‘Content Copier’. Using it, you can backup phone memory, memory card, messages, calender entries on your PC. I would suggest you to backup on your PC. During software update, the phone memory will be formatted.
• USB cable which comes with your handset.

With above requirements/ precautions taken care, use the following steps:

1. Connect your phone to the PC using the USB cable. Use ‘PC Suite’ option in the phone. Accept the cable drivers installation on your PC during the first time of connection.

2. Open the NSU. It will detect your phone type and checks for the software update. It will display the Current firmware version and the available version. The other way to check whether update is available is: Availability

3. If you want to continue with updation, click on “Update”. The software will be downloaded from the server to your PC. Note: Internet connection should not be lost during this process.(It usually takes 40-50mins depends on internet connection.connect between pc and nokia mobile should be there but not must)

4. After the software is downloaded, your phone screen will go blank and updation starts.(i.e flashing the mobile with the firmware,it usually takes 10-20mins) On updating the phone reboots.

5. A message on your PC indicates the completion. Restore the contents either from the memory card or from the PC using the PC suite.

6. Allow the applications to installed again in your phone.

Do read the FAQ’s

Do post in your queries and watch out this space for more tips.

Enjoy the new features of the phone…

My device "died" during an update. What should I do?

Firstly, it is normal for the Nokia device display to go blank during an update.

However, it may be that the Nokia Software Updater application has lost contact with your Nokia device and the device display is suspended.

• Disconnect the Nokia device from the PC's USB cable and remove the device's battery for 5 seconds.
• Re-insert the battery then press and hold the device power button for 1 second.
• Re-connect the Nokia device to the PC's USB cable and wait for 10 seconds.
• Try the Nokia Software Updater again

If there is no response from your Nokia device, try to recover the device by formatting it:

• Press and hold the following device keys: 3, and *
• Press the device power button for 1 second
• Continue to hold down 3, and * until you hear the device start-up tone.

If there is still no response:

• Take the Nokia device to your nearest Nokia Care point. If the device is within its warranty period, Nokia will repair the device under the usual warranty terms and conditions.
• Note: If the Nokia device is not within its warranty period, Nokia is not liable for any loss as defined within the End-User Software Agreement. See for www.nokia.com/repair details.