GET CERTICATE TO your NOKIA 701 N8 C7 E7 C6 5800 5320 n97 700 or any other

We are not responsible if you screw up your phone by this. This method is tested and has no hazardous effects.

So basically it's one of the ancient Symbian hacking alike method.

There's a security hole in Dr.Web Antivirus which is taken advantage of and used to access the system files.

IMPORTANT!

You can only do this with a PC. Connect your phone via Mass Storage 

You need to view the hidden files and folders to access the Private folder.

We suggest you to copy all files and install everyhting on the Memory Car

1. Get proper drivers:

- If you are going to use Memory card download:

QuarantineDriversLDD.rar


- If you are going to use Mass storage download:QuarantineDriversF.rar

2. Unpack archive and move to the files to the Private folder, so that the path will be E:/Private/20024113/Quarantine/...

(ONLY THE FILE INTO THE PATH SHOWN ABOVE! DO NOT REPLACE ANYTHING!)
E:/Private/20024113/Quarantine/patcherS3.dwq
E:/Private/20024113/Quarantine/patcherShadow.dwq
E:/Private/20024113/Quarantine/patcher.dwq
E:/Private/20024113/Quarantine/index

Download and install DrWeb6or Norton
4. Launch DrWeb / Norton and use the Demo key.
5. Go to Options - Quarantine




6. Go Options - Select all (if there are no files to select, then: 1) make sure you copied all 4 files, 2) restart phone)
For those of you having error message  "E:/sys/bin/patcher*. LDD not found!" , please do step 6 by select one by one , don't select all.
7. Go Options - Restore
After doing this all files should dissapear. If they duplicated, then this means that wrong QuarantineDrivers were used. Go back to the first step and make sure to clear the Quarantine folder before copying new files.
8. Download and install RomPatcher+ 3.1 Lite
9. Launch RomPatcher+ and apply Open4all patch
If RP+ gives you error "E:/sys/bin/patcher*. LDD not found!" then you have used wrong QuarantineDrivers from first step. Go back, and start all over again with the correct drivers copied!

- Now you have access to write in all system folders
- You can now apply installserver patch (it's required for installing all unsigned applications without any certificate restrictions).
10. Now, decide which version of Symbian is your device and download respective installserver:
If you don't know which one is yours, then click here to find out!
Symbian^3/Anna/Belle: Use Coderus's Install server.

S60v5 and S60v3 FP2: Use s60v3_s60v5_installserver
S60v3 FP1: Use s60v3_FP1 installserver
S60v3 PreFP1: Use s60v3_Pre_FP1 installserver
alternative Anna / Belle: Use this installserver
11. Download, extract and move the installserver.exe to E:/sys/bin
12. Enable the installserver.exe patch in Rompatcher and you're all set to install unsigned apps!

That's It! Congratulations!

or do this

A self-signed application is one that is signed with a user-created certificate. Self signed applications are not trusted - they can only be used for applications with basic capabilities, and the user must acknowledge a warning before they can be installed. The benefit of self signing is that it is free, and can be used on any device.

Applications can also be locally signed using a Developer Certificate obtained from Symbian Signed. The certificate locks signed applications to install on specific devices, but in return grants more capabilities than self-signing. There are still installation warnings.

Both self signed and DevCert signing can be done locally through your IDE or the command line, as discussed in the following sections.

Note: 

• Basic capabilities include LocalServices capability can also be granted to self-signed applications.
• An application that does not require any capabilities can also be self-signed.
• You cannot self-sign applications with a UID3/SID in the protected range. During development choose a random UID from the 0xE******* range. For application release use a UID in the 0xA******* range that you obtain from Symbian Signed.

Qt Creator IDE

Qt Creator self-signs applications by default. As shown in the screenshot below you can also specify a "Custom certificate" and browse to your Developer Certificateand it's private key.

1. Open your project in Qt Creator

• Projects >> Targets >> Symbian Device >> Run >> Run Settings >> Create SIS Package

• Select "Self signed certificate" or "Custom certificate" (and browse to the certificate and key file)

Tip: Using the "Custom certificate" section can also self-sign an application using your own certificate rather than the default certificate provided with Qt Creator. However in this case you will need to create the certificate/key pair using the command line

Carbide.c++

Carbide.c++ IDE offers inbuilt feature to create and sign the .sis file with Self-signed certificate or Developer Certificate. See the images below:

1. Open your project in Carbide.c++

   Project >> Properties >> Carbide.c++ >> Build Configurations >> SIS Builder

   

2. Project >> Properties >> Carbide.c++ >> Build Configurations >> SIS Builder >> Add

   

Command Line

Following is the example which illustrates the Self-Signing procedure using the command line.

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 creates WorldKey.key and WorldCert.cer key and certificate files files which you will need to sign your HelloWorld.sis file in the following statement.

Important: Versions of MakeKeys prior to Symbian 9.2 always generate certificates with a validity period of 1 year. This may be too short for released code, as it restricts the lifetime of the signed SIS files. You can create a certificate using OpenSSL to choose a different validity period, or use the update to MakeKeys in latests SDKs to specify an alternative validity period.

Step-2 Signing Application

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

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

Tip: Instead of using makesis to create the .sis and then signsis to sign it, you can use createsis to perform both operations at once:

createsis create -cert WorldCert.cer -key WorldKey.key -pass YourPassWord HelloWorld.pkg

also these steps can help u

1st way

1.  Install      Safe Manager   in E drive/Mass memory

(ignore all warnings and continue with
  Installation). Safe Manager  will launch itself after installation (launch  from menu if not), select No/Cancel at all the three prompts.

2. Now if the Safe Manager app interface is in Chinese, we will have to change the language to English (to make it usable). To do this, connect your phone with computer in “Mass Storage Mode” (close Nokia Suite/PC Suite if it is running). Open E (Mass memory) via My Computer. Now go to the files extracted in step 1 above and open folder “English files for Safe Mgr”. Copy the files inside these folders to E: drive (Mass Memory) of phone exactly according to the path in folders (replace if prompted).

3. Disconnect the phone from PC and launch Safe Manager from menu (select No at the prompt). Go to “Other/FileMgr” and open E:/FP2hack. Now select and copy “updatedswicertstore.dat” file and paste it inside C:/resource/swicertstore/dat folder (via options/insert, confirm replace).

4. install ROMPatcherPlus_3.1_FP2.sisx. After installation run ROMPatcher+ and apply all patches and enjoy installing any unsigned app/game!

5. download this and extract to c/sys/bin  :- http://www.mediafire.com/?s5kwdpfb0ak0cd5

  

Safe Manager   AND ROMPatcherPlus_3.1_FP2.sisx

 DOWNLOAD HERE :-

 http://www.mediafire.com/?b2udx24hfu31ogl

must read

i don't have the responsibility for any problem with ypur phone

its a moding so it may or may not affect the phone

so please take responsibilities own 

A CA certificate is downloaded from a WML page (example given below). When the handset receives a special MIME-type (for WTLS CA certificates, this is "application/vnd.wap.wtls-ca-certificate&quot the handset stores the certificate until the user exits the browser. Once the user has exited the browser, the user has the possibility to see the details (issuer, owner, validity period, etc.), verify the finger print, and possibly store the certificate if (s)he can accept it based on the information provided in the display.

One the server side, it is important that the server is configured to hand out certificates with the correct MIME type. For example, if CA certificates are stored with suffix .cer, then the server should be configured to automatically associate this file suffix witht the "application/vnd.wap.wtls-ca-certificate" MIME-type.
An example of a WML certificate download page:

<?xml version="1.0"?>

<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">

<wml>
<card id="Certs" title="Cert Download">
<p>Download Certificate

<anchor>Main Page<go href="main.wml"/></anchor>
<anchor>A CA Certificate<go href="CACertificate.cer"/></anchor>

</p>
</card>
</wml>

---------------------------------------------------------

 2nd way

1. YOU HAVE TO DOWNLOAD THIS :-

2. Install SAFE MANGER TO E drive/Mass memory (ignore all warnings and continue with installation)
[Safe Manager will launch itself after installation (launch from menu if not), select No/Cancel at all the three prompts.]

3. Now if the Safe Manager app interface is in Chinese, we will have to change the language to English (to make it usable). To do this, connect your phone with computer in “Mass Storage Mode” (close Nokia Suite/PC Suite if it is running). Open E (Mass memory) via My Computer. Now go to the files extracted in step 1 above and open folder “English files for Safe Mgr”. Copy the files inside these folders to E: drive (Mass Memory) of phone exactly according to the path in folders (replace if prompted).

4. Disconnect the phone from PC and launch Safe Manager from menu (select No at the prompt). Go to “Other/FileMgr” and open E:/FP2hack. Now select and copy “updatedswicertstore.dat” file and paste it inside C:/resource/swicertstore/dat folder (via options/insert, confirm replace).

5. NOW install ROMPatcherPlus_3.1_FP2.sisx. After installation run ROMPatcher+ and apply all patches and enjoy installing any unsigned app/game!

must read

i don't have the responsibility for any problem with ypur phone

its a moding so it may or may not affect the phone

so please take responsibilities own 

or this way by nokia

Symbian Signed is a testing and signing program run by Nokia.

Please find the test criteria here

Symbian Signed supported devices table can be found here

The Symbian Signed service allows you to:

1. Register UIDs
2. Sign your Symbian OS application with a test certificate so that you can test it on a live device
3. Sign your Symbian OS application with a publishing certificate so that you can distribute it to your customer

Please see the chart below for a summary of the services:

Process	Symbian Signed account required	Verified account	Test house testing the application	IMEI and UID restriction
Registering UIDs	Yes	No	No	No
Development Certificate for less than 10 IMEIs	Yes	No	No	Yes
Development Certificate for up to 1000 IMEIs	Yes	Yes	No	Yes
Express Signed	Yes	Yes	No	No
Certified signed	Yes	Yes	Yes	No

The services are mapped based on the Symbian OS Platform Security capabilities. Please see the following chart with the details how the capabilities are mapped per different service.

2. Registering to the Symbian Signed service

• To register you need to have a valid e-mail address. We may have some limitations to which e-mail domains we accept to the service.

Taxation within the EU

Value Added Tax (VAT) ID and country information is needed for VAT handling whenever you purchase Content IDs for Express Signed. Companies within the European Union should have a VAT ID to provide at the time of purchasing Content IDs. Whether or not VAT is added to your invoice depends on your stated location (Country), and, whether or not you have provided us with your VAT ID. Additionally, when purchasing Content IDs, the VAT Invoice will be sent to you via e-mail, no matter where you are.

Our service is based in Finland. While selling within Finland, we know how much tax to apply for Finnish companies. Other, EU-based, companies can report their 0% taxed purchases locally with the invoices we provide for their VAT ID, as per local law. Then VAT will be locally applied to their derivative products. If there is no VAT ID we will apply the seller local VAT amount - as if the buyer was a end-consumer, not a company producing derivative products. Therefore our VAT handling rules are as follows:

If you have a VAT ID to provide at the time of the purchase, and

• buying location in Finland VAT = 24% which is included to the price of the purchase
• buying location in EU VAT = 0%
• buying location in non-EU VAT = 0%

If you don't have a VAT ID to provide at the time of the purchase:

• buying location in Finland VAT = 24% which is included to the price of the purchase
• buying location in EU VAT = 24% which is included to the price of the purchase
• buying location in non-EU VAT = 0%

For example:

1. If a company from Finland with a VAT ID is buying 10 Content IDs they will be invoiced 124€.
2. If a company from China without a VAT ID is buying 10 Content IDs they will be invoiced 100€.
3. If a company from Germany without a VAT ID is buying 10 Content IDs they will be invoiced 124€.

3. Development Certificates

To request new development certificate, you must request for UIDs of your applications first, if not it does not allow you to request for development certificate, because in the new portal, development certificate associated with application UIDs also.

Add IMEI numbers: There are two ways to add IMEI numbers of the devices on which your application will run:

1. Enter all your devices IMEI numbers manually.
2. You can upload all IMEIs stored in .txt files form your local machine.

How to request new UIDs:

Using ManageUIDs tab, you can request for new UIDs, and you will see allocated UIDs for your applicaions from previouse requests.You can edit application names and version numbers of allocated UIDs. There are two types of UIDs:

1. Protected UIDs
2. Unprotected UIDs.

What's the difference between "Protected" and "Unprotected range" UIDs?

• Any UID values less than or equal to 0x7FFFFFFF are classed as "protected" and are only intended for use with signed applications (or those pre-installed in ROM). The software installer will refuse to install an unsigned application if it uses a package UID in the protected range.
• New UID allocations will start from 0x20000000 for the protected range and from 0xA0000000 for the unprotected range.

Application needs more capabilities?

If you application needs more than system, user capabilities,then you need to request for manfacturer capabilities.you need to request them by using AllFiles,DRM,TCB Tab in the portal. For details about it,you can refer to 8. AllFiles, DRM, TCB & Invitation only chapter of this wiki page.

After all these,Click on Download Certificate tab to download your certificate, key. Then it would display download window to save deveoloper certificate, key local to your machine.

Tip: You can use the updated DevCerList tool to list the contents of your developer certificate in order to verify that it matches your requested capabilities, allocated UIDs and supported device IMEIs.

4. Content ID

Content IDs are signing tokens for the Express Signed service. One application signing event consumes one Content ID. Content IDs are sold via our PayPal seller service; one content ID costs 10 Eur plus VAT. 

Click on 'purchase' 

Set the amount of Content IDs to purchase. The service will direct you to our PayPal service (seller is Nokia). Complete the purchase on PayPal. You will receive an invoice for your purchase into the e-mail address you have specified in your user account.

5. Express Signed

1. Login to Symbian Signed and check that your account is verified.
2. Check that your account has unused Content IDs 
3. Click "Submit app for Signing" and fill in the application details 
   

   
   

4. Submit for analysis. Analysis will take a few seconds. 
   

   
   

   Check that your account has at least one unused content ID (see the top bar on the screen - here shown 5 content IDs). If you have no Content IDs the Express Signed will not be presented as a signing option. 

5. Once your submission is verified click "Complete Signing". 
   

   
   

6. Select "Express Signed" for the process and click "Next Step" to submit your application for signing. 
   

   
   

7. After successful submission you'll get your application signed and downloadable from the portal. You will also receive an e-mail with a link to download the signed application. 
   

   
   

Express signed not available

The main reason is failing an audit. This means that one of your submissions has been tested by a test house and it has been found not to comply with the Symbian Signed criteria. You can find a test report with the submission which was audited.
You can get the access back to Express Signed by passing the Certified Signed once.

6. Certified Signed

In this option the test house will test your application and sign it when it has passed the testing. One test round has a cost of 230€.

After your application has been successfully verified you can select the option of “Complete Signing” and through it submit the application to the test house. Please follow the following steps:

A) Please make sure you have provided all the needed data for Sogeti to test your application. For example license to use the application or potential usernames and password.
B) Before submitting you need to accept the Sogeti legal agreement.
C) After you have submitted the application, Sogeti will e-mail you a quotation of the testing cost which you need to approve by replying to the e-mail. 

You have two possibilities to pay for this service:

1. By credit card, the quotation e-mail contains a link to our online shop. This link is specific to your submission and you will access directly to your basket on our online store. There you will have the possibility to choose the service level and to pay with your credit card.
2. By wire transfer. If you prefer to order a wire transfer, Sogeti High Tech Banking details are listed within the quotation e-mail.

D) When you have paid the test, please provide Sogeti with the proof of payment. For example a scanned copy of your transaction. Only after Sogeti has been paid you can receive the test report and/or the signed application. 

If you have failed the testing please assure that you have fixed all the errors and you have not provided any additional errors. Additionally you should consider the fact that each test round has an additional cost.

7. AllFiles, DRM, TCB & Invitation only side of Symbian Signed

• Main requirements:
  1. A valid and accepted technical justification to use AllFiles, DRM or TCB
  2. Your company is known to us
  3. We have a legal agreement about the capability use
  4. Your application complies with Symbian Signed and additional Nokia criteria
• For technical reasoning it is advisable to provide as detailed information about your application and the use of the AllFiles, DRM or TCB as possible. If your company is not known to us earlier we may come back to you and ask for more details.
• After we have accepted your technical reason for using AllFiles, DRM or TCB, we will grant you access to the Development Certificates with the capabilities you have requested. Later we can grant your account access rights to our Invitation only side of Symbian Signed web site allowing you to submit an application to a test house with AllFiles, DRM or TCB.

8. Requesting Waivers

Using waivers is allowed for verified users only. If your account hasn’t been verified yet, please do so before applying for waivers.

Once verified, your dashboard will show you a tab labelled ‘Waivers’. From here you can submit new waiver requests. The requests will be listed by their status, and for each application you have requested them for. After an admin has approved your waiver you can use that with your application submission when submitting to either Express Signed or Certified Signed. The selected test house will see your waiver along with your application information and will act accordingly. Note that the waiver is linked to an application by the UID given on your waiver request. Be sure to give your application UID in the correct format '0x2........'. You can write multiple waivers for one UID, and these waivers can all have different app name defined (e.g. when submitting different language variants of the same application).

Please note that if your application is not associated with a waiver it must then conform to the Symbian Signed (and Nokia test) criteria to the letter – and will be failed in the tests if it doesn’t!

Filling out a waiver

Please take time and care when filling in a waiver request. If it does not include enough information – or clearly enough – it will be rejected and you will need to go through the trouble of re-writing the same request!

You should write out the following:

• Correct application UID! If you enter a wrong UID the waiver will not be attached to your application.

• Your application (Functional Description); what the application does and why.

• The test case your application is not able to pass without this waiver (Failure Description). It is most helpful if you can describe how this test will fail with your application. You can also attach images etc. for clarification.

• Then the most important part (Functional Justification): why should this application be granted the waiver; what are the technical grounds on which the application will not conform to the test criteria, and thus needs this waiver?

---------------------------------------------------------
I AM always excited to hear from you! If you have any feedback, questions

JUST COMMENT