Maemo Wiki Mirror - User contributions [en]

Python/Harmattan/Getting started with Harmattan Python

2018-03-05T18:17:29Z

181.179.18.175: Why ''./dosomething.py'' works, and why not. and the role of packaging.

== How to setup the device ==

Depending on the device model that you are using, some extra steps are needed to have Python installed on it. Currently there are two models running Meego 1.2 Harmattan:

* '''N950''': this is the developer edition and comes with Python, [http://www.pyside.org PySide] and [http://www.pyside.org/docs/pyside-mobility/ bindings for QtMobility] already installed.
* '''N9''': this is the mass-market end-user device. Development packages does not come pre-installed. See below how to install Python on it!

==== Developer mode ====

Meego 1.2 Harmattan has a special mode - [http://library.developer.nokia.com/topic/MeeGo_1.2_Harmattan_API/html/guide/html/Developer_Library_Developing_for_Harmattan_Activating_developer_mode_1fa5.html Developer Mode] - that enables connectivity between the device and the software development kit (SDK) running on the host. This mode is useful to test applications into device as you develop. Follow the instructions [http://library.developer.nokia.com/topic/MeeGo_1.2_Harmattan_API/html/guide/html/Developer_Library_Developing_for_Harmattan_Activating_developer_mode_1fa5.html here] to enable/disable it.

Once you have got connected to the device using e.g. ssh, you can use ''devel-su'' command to become superuser. Use '''rootme''' as password and you become root.

<nowiki>
$ devel-su
Password:
</nowiki>

However, this will not allow you to execute unregistered scripts or applications. See section ''Security framework'' below to get more information about security on MeeGo 1.2 Harmattan environment.

==== Installing only Python ====

Following the steps shown in the last section you will be able to use ''apt-get''. This application is responsible for package handling on Debian like distributions. If you want to install other modules, like bindings for Qt and QtMobility, see the topic below. As they depend on Python, it will be automatically installed too - there is no need to install just Python before them.

To have only Python installed on your device, run:

<nowiki>
$ apt-get update
...

$ apt-get install python
</nowiki>

Welcome to the Python world!

==== Installing other Python-related packages ====

MeeGo 1.2 Harmattan platform uses [https://web.archive.org/web/20120929010040/http://library.developer.nokia.com/topic/MeeGo_1.2_Harmattan_API/html/guide/html/Developer_Library_Application_development_framework_ebcf.html QtQuick] as its preferred method to develop interfaces. The [http://www.pyside.org PySide] project provides Python bindings for Qt allowing Python developers to develop their interfaces. [https://web.archive.org/web/20120929010040/http://developer.qt.nokia.com/wiki/PySideDocumentation/ Here] you can find useful information on how to develop using PySide/QtQuick/QML. If you plan to develop applications that use just Qt (without QML) they will not integrate (use and feel) with the native interface.

To install these new packages you can continue from the same terminal opened in the last section. Again, use ''apt-get'' to install all the needed packages:

<nowiki>
# Install PySide:
$ apt-get install python-pyside
</nowiki>

There are also [https://web.archive.org/web/20120929010040/http://qt-project.org/wiki/PySideDocumentation/#704d2ca247b8787c6738c5a47d3f98ec bindings] for [https://web.archive.org/web/20120929010040/http://doc.qt.nokia.com/qtmobility-1.2/index.html QtMobility]. To install them:

<nowiki>
# Install PySide-QtMobility
$ apt-get install python-qtmobility
</nowiki>

There are some other modules already ported / being ported and the easiest way to install all of them is:

<nowiki>
# Install all available python bindings
$ apt-get install python-modules-all
</nowiki>

== Tasting PySide/QML ==

If you have skipped any of the previous sections and have PySide installed you can see here an [https://web.archive.org/web/20120929010040/http://developer.qt.nokia.com/wiki/Hello_World_in_PySide_and_QtQuick example] taken from PySide documentation website.

[https://web.archive.org/web/20120929010040/http://doc.qt.nokia.com/4.7/qdeclarativeintroduction.html QML] is a declarative language designed to describe the user interface of a program: both what it looks like, and how it behaves. In QML, a user interface is specified as a tree of objects with properties. In this tutorial we will show how you can make a simple Hello World application with PySide and QML.

A PySide/QML application consists, at least, of two different files – a file with the QML description of the user interface, and a python file which loads the qml file. To avoid problems for now, don’t forget to save both files in the same folder.

Here is a simple QML file, called ''view.qml'':

<nowiki>
import Qt 4.7

Rectangle {
width: 200
height: 200
color: "red"

Text {
text: "Hello World"
anchors.centerIn: parent
}
}
</nowiki>

We start by importing Qt 4.7. As it is pretended that QtQuick has a different build schedule than Qt/PySide, in the near future you will have to change this to import QtQuick 1.0. But for now, it works as is.

The rest of the QML code, is pretty straigthforward for those who have used previously HTML or XML files. Basically, we are creating a red rectangle with the size ''200*200'' and, inside that rectangle, we are adding a Text element which says ''Hello World''. The code ''anchors.centerIn: parent'' just makes the text appear centered in relation to its imediate parent.

Now, let’s see how the code looks on the PySide. Let’s call it main.py:

<nowiki>
#!/usr/bin/python
# -*- coding: utf-8 -*-

import sys
from PySide.QtCore import *
from PySide.QtGui import *
from PySide.QtDeclarative import QDeclarativeView

# Create Qt application and the QDeclarative view
app = QApplication(sys.argv)
view = QDeclarativeView()
# Create an URL to the QML file
url = QUrl('view.qml')
# Set the QML file and show
view.setSource(url)
view.show()
# Enter Qt main loop
sys.exit(app.exec_())
</nowiki>

To run the example remember to use:

<nowiki>
$ python ./main.py
</nowiki>

As this script is not packaged/registered it will fail if you call just ''./main.py''. The next section better explains these concepts.

If you are already familiar with PySide and have followed our tutorials, much of this code is already familiar. The only novelties is that you must import QDeclarativeView and set the source of the QDeclarativeView object to the URL of your QML file. Then, as any Qt widget, you call ''QDeclarativeView.show()''.

Take your time exploring this example. You can try to do basic things as changing the colors, the text, or set other properties to each element, setting a radius on the rectangle color. Check the elements and their properties in [https://web.archive.org/web/20120929010040/http://doc.qt.nokia.com/4.7/qdeclarativeelements.html QML Elements].

== Security framework for Python scripts ==

To run applications (binaries and scripts) it is necessary to follow some security guidelines. Information about the implications of the security framework for applications in general can be found [https://projects.maemo.org/mediawiki/index.php/Developer_Library/Developing_for_Harmattan/Harmattan_security here].

If your ''dosomething.py'' python script is marked as executable (as the result of ''chmod +x dosomething.py''), it is somewhere in the PATH (for example ''/usr/local/bin/''), it starts with the line

<nowiki>
#!/usr/bin/env python
</nowiki>

then you can invoke it from the command line, just as any other program. This however is not exactly what you would call "end-user friendly".

Proper packaging of your python software will allow you hand it over to your friends, who will be able to use it as any other Maemo program.

The next section shows how to package your Python application.

'''Note:''' if the script is modified after it is installed it will fail to run!

== Packaging ==

As explained in the previous section there are some restrictions to run applications/scripts. Your application has to be installed from a Debian package.

The easiest way to create Python packages for MeeGo 1.2 Harmattan is to use ''pyside-assistant''. After a few steps you will have a Debian package ready to be installed. You will have to inform all the resources that your application needs - avoiding problems with the Security Framework. To see all supported features and how to use ''pyside-assistant'', including an example, follow this [[Documentation_for_pyside-assistant|link]].

Python/Harmattan/Getting started with Harmattan Python

2018-03-05T14:55:44Z

181.179.18.175: rely on webarchive for now broken nokia links.

== How to setup the device ==

Depending on the device model that you are using, some extra steps are needed to have Python installed on it. Currently there are two models running Meego 1.2 Harmattan:

* '''N950''': this is the developer edition and comes with Python, [http://www.pyside.org PySide] and [http://www.pyside.org/docs/pyside-mobility/ bindings for QtMobility] already installed.
* '''N9''': this is the mass-market end-user device. Development packages does not come pre-installed. See below how to install Python on it!

==== Developer mode ====

Meego 1.2 Harmattan has a special mode - [http://library.developer.nokia.com/topic/MeeGo_1.2_Harmattan_API/html/guide/html/Developer_Library_Developing_for_Harmattan_Activating_developer_mode_1fa5.html Developer Mode] - that enables connectivity between the device and the software development kit (SDK) running on the host. This mode is useful to test applications into device as you develop. Follow the instructions [http://library.developer.nokia.com/topic/MeeGo_1.2_Harmattan_API/html/guide/html/Developer_Library_Developing_for_Harmattan_Activating_developer_mode_1fa5.html here] to enable/disable it.

Once you have got connected to the device using e.g. ssh, you can use ''devel-su'' command to become superuser. Use '''rootme''' as password and you become root.

<nowiki>
$ devel-su
Password:
</nowiki>

However, this will not allow you to execute unregistered scripts or applications. See section ''Security framework'' below to get more information about security on MeeGo 1.2 Harmattan environment.

==== Installing only Python ====

Following the steps shown in the last section you will be able to use ''apt-get''. This application is responsible for package handling on Debian like distributions. If you want to install other modules, like bindings for Qt and QtMobility, see the topic below. As they depend on Python, it will be automatically installed too - there is no need to install just Python before them.

To have only Python installed on your device, run:

<nowiki>
$ apt-get update
...

$ apt-get install python
</nowiki>

Welcome to the Python world!

==== Installing other Python-related packages ====

MeeGo 1.2 Harmattan platform uses [https://web.archive.org/web/20120929010040/http://library.developer.nokia.com/topic/MeeGo_1.2_Harmattan_API/html/guide/html/Developer_Library_Application_development_framework_ebcf.html QtQuick] as its preferred method to develop interfaces. The [http://www.pyside.org PySide] project provides Python bindings for Qt allowing Python developers to develop their interfaces. [https://web.archive.org/web/20120929010040/http://developer.qt.nokia.com/wiki/PySideDocumentation/ Here] you can find useful information on how to develop using PySide/QtQuick/QML. If you plan to develop applications that use just Qt (without QML) they will not integrate (use and feel) with the native interface.

To install these new packages you can continue from the same terminal opened in the last section. Again, use ''apt-get'' to install all the needed packages:

<nowiki>
# Install PySide:
$ apt-get install python-pyside
</nowiki>

There are also [https://web.archive.org/web/20120929010040/http://qt-project.org/wiki/PySideDocumentation/#704d2ca247b8787c6738c5a47d3f98ec bindings] for [https://web.archive.org/web/20120929010040/http://doc.qt.nokia.com/qtmobility-1.2/index.html QtMobility]. To install them:

<nowiki>
# Install PySide-QtMobility
$ apt-get install python-qtmobility
</nowiki>

There are some other modules already ported / being ported and the easiest way to install all of them is:

<nowiki>
# Install all available python bindings
$ apt-get install python-modules-all
</nowiki>

== Tasting PySide/QML ==

If you have skipped any of the previous sections and have PySide installed you can see here an [https://web.archive.org/web/20120929010040/http://developer.qt.nokia.com/wiki/Hello_World_in_PySide_and_QtQuick example] taken from PySide documentation website.

[https://web.archive.org/web/20120929010040/http://doc.qt.nokia.com/4.7/qdeclarativeintroduction.html QML] is a declarative language designed to describe the user interface of a program: both what it looks like, and how it behaves. In QML, a user interface is specified as a tree of objects with properties. In this tutorial we will show how you can make a simple Hello World application with PySide and QML.

A PySide/QML application consists, at least, of two different files – a file with the QML description of the user interface, and a python file which loads the qml file. To avoid problems for now, don’t forget to save both files in the same folder.

Here is a simple QML file, called ''view.qml'':

<nowiki>
import Qt 4.7

Rectangle {
width: 200
height: 200
color: "red"

Text {
text: "Hello World"
anchors.centerIn: parent
}
}
</nowiki>

We start by importing Qt 4.7. As it is pretended that QtQuick has a different build schedule than Qt/PySide, in the near future you will have to change this to import QtQuick 1.0. But for now, it works as is.

The rest of the QML code, is pretty straigthforward for those who have used previously HTML or XML files. Basically, we are creating a red rectangle with the size ''200*200'' and, inside that rectangle, we are adding a Text element which says ''Hello World''. The code ''anchors.centerIn: parent'' just makes the text appear centered in relation to its imediate parent.

Now, let’s see how the code looks on the PySide. Let’s call it main.py:

<nowiki>
#!/usr/bin/python
# -*- coding: utf-8 -*-

import sys
from PySide.QtCore import *
from PySide.QtGui import *
from PySide.QtDeclarative import QDeclarativeView

# Create Qt application and the QDeclarative view
app = QApplication(sys.argv)
view = QDeclarativeView()
# Create an URL to the QML file
url = QUrl('view.qml')
# Set the QML file and show
view.setSource(url)
view.show()
# Enter Qt main loop
sys.exit(app.exec_())
</nowiki>

To run the example remember to use:

<nowiki>
$ python ./main.py
</nowiki>

As this script is not packaged/registered it will fail if you call just ''./main.py''. The next section better explains these concepts.

If you are already familiar with PySide and have followed our tutorials, much of this code is already familiar. The only novelties is that you must import QDeclarativeView and set the source of the QDeclarativeView object to the URL of your QML file. Then, as any Qt widget, you call ''QDeclarativeView.show()''.

Take your time exploring this example. You can try to do basic things as changing the colors, the text, or set other properties to each element, setting a radius on the rectangle color. Check the elements and their properties in [https://web.archive.org/web/20120929010040/http://doc.qt.nokia.com/4.7/qdeclarativeelements.html QML Elements].

== Security framework for Python scripts ==

To run applications (binaries and scripts) it is necessary to follow some security guidelines. Information about the implications of the security framework for applications in general can be found [https://projects.maemo.org/mediawiki/index.php/Developer_Library/Developing_for_Harmattan/Harmattan_security here].

Without a proper package it will not be possible to run executable Python scripts without pre-pending ''python''. The following call would fail:

<nowiki>
$ ./dosomething.py
-sh: ./dosomething.py: Permission denied
</nowiki>

However, using the Python interpreter for calling the script works as expected:

<nowiki>
$ python ./dosomething.py
</nowiki>

The next section shows how to package your Python application.

'''Note:''' if the script is modified after it is installed it will fail to run!

== Packaging ==

As explained in the previous section there are some restrictions to run applications/scripts. Your application has to be installed from a Debian package.

The easiest way to create Python packages for MeeGo 1.2 Harmattan is to use ''pyside-assistant''. After a few steps you will have a Debian package ready to be installed. You will have to inform all the resources that your application needs - avoiding problems with the Security Framework. To see all supported features and how to use ''pyside-assistant'', including an example, follow this [[Documentation_for_pyside-assistant|link]].

Python/Harmattan/Getting started with Harmattan Python

2018-03-05T14:53:57Z

181.179.18.175: replacing now broken nokia links with webarchive 20120929010040

== How to setup the device ==

Depending on the device model that you are using, some extra steps are needed to have Python installed on it. Currently there are two models running Meego 1.2 Harmattan:

* '''N950''': this is the developer edition and comes with Python, [http://www.pyside.org PySide] and [http://www.pyside.org/docs/pyside-mobility/ bindings for QtMobility] already installed.
* '''N9''': this is the mass-market end-user device. Development packages does not come pre-installed. See below how to install Python on it!

==== Developer mode ====

Meego 1.2 Harmattan has a special mode - [http://library.developer.nokia.com/topic/MeeGo_1.2_Harmattan_API/html/guide/html/Developer_Library_Developing_for_Harmattan_Activating_developer_mode_1fa5.html Developer Mode] - that enables connectivity between the device and the software development kit (SDK) running on the host. This mode is useful to test applications into device as you develop. Follow the instructions [http://library.developer.nokia.com/topic/MeeGo_1.2_Harmattan_API/html/guide/html/Developer_Library_Developing_for_Harmattan_Activating_developer_mode_1fa5.html here] to enable/disable it.

Once you have got connected to the device using e.g. ssh, you can use ''devel-su'' command to become superuser. Use '''rootme''' as password and you become root.

<nowiki>
$ devel-su
Password:
</nowiki>

However, this will not allow you to execute unregistered scripts or applications. See section ''Security framework'' below to get more information about security on MeeGo 1.2 Harmattan environment.

==== Installing only Python ====

Following the steps shown in the last section you will be able to use ''apt-get''. This application is responsible for package handling on Debian like distributions. If you want to install other modules, like bindings for Qt and QtMobility, see the topic below. As they depend on Python, it will be automatically installed too - there is no need to install just Python before them.

To have only Python installed on your device, run:

<nowiki>
$ apt-get update
...

$ apt-get install python
</nowiki>

Welcome to the Python world!

==== Installing other Python-related packages ====

MeeGo 1.2 Harmattan platform uses [https://web.archive.org/web/20120929010040/http://library.developer.nokia.com/topic/MeeGo_1.2_Harmattan_API/html/guide/html/Developer_Library_Application_development_framework_ebcf.html QtQuick] as its preferred method to develop interfaces. The [http://www.pyside.org PySide] project provides Python bindings for Qt allowing Python developers to develop their interfaces. [https://web.archive.org/web/20120929010040/http://developer.qt.nokia.com/wiki/PySideDocumentation/ Here] you can find useful information on how to develop using PySide/QtQuick/QML. If you plan to develop applications that use just Qt (without QML) they will not integrate (use and feel) with the native interface.

To install these new packages you can continue from the same terminal opened in the last section. Again, use ''apt-get'' to install all the needed packages:

<nowiki>
# Install PySide:
$ apt-get install python-pyside
</nowiki>

There are also [https://web.archive.org/web/20120929010040/http://qt-project.org/wiki/PySideDocumentation/#704d2ca247b8787c6738c5a47d3f98ec bindings] for [https://web.archive.org/web/20120929010040/http://doc.qt.nokia.com/qtmobility-1.2/index.html QtMobility]. To install them:

<nowiki>
# Install PySide-QtMobility
$ apt-get install python-qtmobility
</nowiki>

There are some other modules already ported / being ported and the easiest way to install all of them is:

<nowiki>
# Install all available python bindings
$ apt-get install python-modules-all
</nowiki>

== Tasting PySide/QML ==

If you have skipped any of the previous sections and have PySide installed you can see here an [http://developer.qt.nokia.com/wiki/Hello_World_in_PySide_and_QtQuick example] taken from PySide documentation website.

[http://doc.qt.nokia.com/4.7/qdeclarativeintroduction.html QML] is a declarative language designed to describe the user interface of a program: both what it looks like, and how it behaves. In QML, a user interface is specified as a tree of objects with properties. In this tutorial we will show how you can make a simple Hello World application with PySide and QML.

A PySide/QML application consists, at least, of two different files – a file with the QML description of the user interface, and a python file which loads the qml file. To avoid problems for now, don’t forget to save both files in the same folder.

Here is a simple QML file, called ''view.qml'':

<nowiki>
import Qt 4.7

Rectangle {
width: 200
height: 200
color: "red"

Text {
text: "Hello World"
anchors.centerIn: parent
}
}
</nowiki>

We start by importing Qt 4.7. As it is pretended that QtQuick has a different build schedule than Qt/PySide, in the near future you will have to change this to import QtQuick 1.0. But for now, it works as is.

The rest of the QML code, is pretty straigthforward for those who have used previously HTML or XML files. Basically, we are creating a red rectangle with the size ''200*200'' and, inside that rectangle, we are adding a Text element which says ''Hello World''. The code ''anchors.centerIn: parent'' just makes the text appear centered in relation to its imediate parent.

Now, let’s see how the code looks on the PySide. Let’s call it main.py:

<nowiki>
#!/usr/bin/python
# -*- coding: utf-8 -*-

import sys
from PySide.QtCore import *
from PySide.QtGui import *
from PySide.QtDeclarative import QDeclarativeView

# Create Qt application and the QDeclarative view
app = QApplication(sys.argv)
view = QDeclarativeView()
# Create an URL to the QML file
url = QUrl('view.qml')
# Set the QML file and show
view.setSource(url)
view.show()
# Enter Qt main loop
sys.exit(app.exec_())
</nowiki>

To run the example remember to use:

<nowiki>
$ python ./main.py
</nowiki>

As this script is not packaged/registered it will fail if you call just ''./main.py''. The next section better explains these concepts.

If you are already familiar with PySide and have followed our tutorials, much of this code is already familiar. The only novelties is that you must import QDeclarativeView and set the source of the QDeclarativeView object to the URL of your QML file. Then, as any Qt widget, you call ''QDeclarativeView.show()''.

Take your time exploring this example. You can try to do basic things as changing the colors, the text, or set other properties to each element, setting a radius on the rectangle color. Check the elements and their properties in [http://doc.qt.nokia.com/4.7/qdeclarativeelements.html QML Elements].

== Security framework for Python scripts ==

To run applications (binaries and scripts) it is necessary to follow some security guidelines. Information about the implications of the security framework for applications in general can be found [https://projects.maemo.org/mediawiki/index.php/Developer_Library/Developing_for_Harmattan/Harmattan_security here].

Without a proper package it will not be possible to run executable Python scripts without pre-pending ''python''. The following call would fail:

<nowiki>
$ ./dosomething.py
-sh: ./dosomething.py: Permission denied
</nowiki>

However, using the Python interpreter for calling the script works as expected:

<nowiki>
$ python ./dosomething.py
</nowiki>

The next section shows how to package your Python application.

'''Note:''' if the script is modified after it is installed it will fail to run!

== Packaging ==

As explained in the previous section there are some restrictions to run applications/scripts. Your application has to be installed from a Debian package.

The easiest way to create Python packages for MeeGo 1.2 Harmattan is to use ''pyside-assistant''. After a few steps you will have a Debian package ready to be installed. You will have to inform all the resources that your application needs - avoiding problems with the Security Framework. To see all supported features and how to use ''pyside-assistant'', including an example, follow this [[Documentation_for_pyside-assistant|link]].

Flashing N9

2018-03-04T13:28:47Z

181.179.18.175: /* Download Firmware image */

{{ambox
|type=notice
|text=This '''unofficial''' guide recommends downloads from '''untrusted''' third party servers. Nobody knows who hosts the content and whether the software has not been altered (e.g. spyware). '''Use at your very own risk.'''
}}

== Warnings ==
* Improperly using flasher could damage your phone and void your warranty. However, following these directions precisely to use flasher to install "stock" Nokia firmware images is quite safe, and can fix problems that would otherwise require warranty service. In any case, '''flashing your phone is at your own risk'''. Do not use this guide if you aren't somewhat familiar with the command prompt/terminal on your operating system. While many users have experienced success with this process, it is not officially recommended by Nokia in any way. '''Read the entire guide ''before'' you start.'''
* Due to artificial limitations placed by Nokia, it is not possible to downgrade the installed firmware on the device using Flasher.
* Do not modify your device's product code. It does not affect a device's ability to receive software updates, and may permanently damage your device.

==Selecting a Firmware Image==

Main firmware images for the Nokia N9 are divided up into "variants" by regions of the world. Except for carrier-branded variants and the 003 (China) firmware, these images are more or less the same.

001 - Europe (1), Latin/South America, South Africa
003 - China
005 - Asia/Pacific (incl. Australia/New Zealand, excl. China)
006 - Middle East
009 - Europe (2)
2xx, 3xx, 4xx - "Country Variant" and carrier-branded images

Downgrades of firmware are '''blocked''' by the phone.
Whether something is a "downgrade" is determined by comparing the entire version strings of the old and new firmware versions, which include the variant code, from left to right. As a result, the variant code must be the same or higher unless you also upgrade the firmware version at the same time. For example:

PR 1.1 variant 009 to PR 1.1 variant 003: '''Blocked'''
PR 1.1 variant 003 to PR 1.1 variant 009: '''Allowed'''
PR 1.1 variant 009 to PR 1.2 variant 001: '''Allowed'''
PR 1.1.1 variant 006 to PR 1.2 variant 005: '''Allowed'''
PR 1.2 variant 001 to PR 1.1 variant 001: '''Blocked'''

Additionally, there is a content image ("eMMC image") for most countries/regions that can be used to reset the user data on the phone and restore the wallpaper/music/map files that originally shipped with it. It is possible to "mix and match" any content image with any main firmware image, which is useful for installing your home country's maps on an imported N9. If you don't require preinstalled maps, or if Nokia doesn't produce a content image for your country (e.g. US and Canada), you can save time by using the content image for product code '''059J1Z5''' ("rest of world"), which doesn't include map files.

When downloading firmware images, it doesn't matter which color or capacity (16/64 GB) you select - the files are the same for all models.

Nokia recommends always using the latest firmware image for your phone's product code (printed on the SIM card tray). This is the safest option. However, you may wish to change to a different variant than what shipped with the phone for the following reasons:

* Receiving updates sooner - new firmware versions are normally released for the 001 variant first
* Removing carrier branding - installing 00x variant firmware makes your subsidized N9 act just like an unlocked one
* Switching away from 003 (China) firmware - firmware images for N9s shipped in China lack Western online service integration (Twitter, Facebook, Skype, Dropbox) and include the Chinese IM service QQ instead

==Download Firmware image==

Use the following steps to retrieve the appropriate firmware files for your phone:

Note: The official firmware source is not currently working, skeiron.org is also gone, www.mrcrab.net answers with 404. [http://www.swagman.org/juice/ubiboot/ swagman.org] contains files which look interesting, [https://archive.org/download/RM696/ this archive] contains a couple of firmware files, too. But what is what? who can fill in the blanks?

===Windows===
Download and run [http://www.symbian-toys.com/navifirm.aspx NaviFirm+], a utility for downloading firmware files from Nokia's servers.
Make sure Server is set to Nokia Care Suite.
Find Nokia N9 (RM-696) in the Products list, then select the firmware release you wish to install.

10.2011.34.1 = PR1.0
20.2011.40.4 = PR1.1
22.2011.44.2 = PR1.1.1 (Middle East only)
30.2012.7.1 = PR1.2
40.2012.21.3 = PR1.3

Select the appropriate product code in the Variants list. In most cases, you should use the product code printed on the SIM tray.
Click Unmark All, then scroll to the bottom of the Files section. Tick the boxes for the two files starting with DFL61_HARMATTAN.
Click Download. Wait for the download to complete, then close NaviFirm+.

===Linux===
Install WINE using your Linux distribution's package manager.
Download and run [http://code.google.com/p/navifirmex/ NaviFirmEx], a replacement for Navifirm+ that doesn't use .NET.
Select Option > Server > Nokia Care Suit [sic] in the menu.
Find Nokia N9 (RM-696) in the Products list, then select the firmware release and variant you wish to install (see above).
Click Add to Download Task, then Inverse Select. Tick the boxes for the two files starting with DFL61_HARMATTAN.
Click Download. Wait for the download to complete, then close NaviFirmEx.

===Any OS===
Go to [http://www.btusers.com.ar/nan/nokia/ Nokia Firmwares] (unofficial firmware download site) and search for Nokia N9. Click CHECK! toward the right-hand side.
Click the link for the firmware release you wish to install (see above).
Click the link for the file starting with DFL61_HARMATTAN.
Unlike NaviFirm+, this website cannot retrieve content/eMMC images.

==Back up your data==

'''All''' of the procedures described below will destroy some or all of the data on your phone, so you should be sure to back up anything you care about first. This includes contacts, messages, game saves, music, .deb packages, etc. You can do this either through the built-in backup feature, or manually using tools in developer mode.

==Prepare to Flash==

If your phone has a low battery charge (less than 50%), plug it in and let it charge for a while. Then, make sure your phone is disconnected from any USB cables (including USB chargers). Power off the phone.

You need the flasher program: with Nokia gone, skeiron also off-line, hopefully [http://www.swagman.org/juice/flasher_3.12.1_i386.deb this deb link] still works. '''Do not''' use Flasher 3.5 - it isn't compatible with the N9/N950.
You can skip this step if you've already installed Flasher.

On Windows, open a Command Prompt with Administrator permissions (with UAC, right-click Command Prompt and select Run as administrator). On Linux, open a root shell (sudo -i/su). Change to the directory containing the firmware images you downloaded.

On Windows, run the following command in order to add Flasher to the system path:

set PATH="C:\Program Files\Nokia\Flasher;%PATH%"

'''Note''': In the following the main firmware image is called "main.bin" and the eMMC image is called "emmc.bin". You must replace main.bin and emmc.bin in the commands with the actual names of the image files you are flashing or rename the downloaded files like this (e.g. under linux)

mv DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin main.bin
mv DFL61_HARMATTAN_40.2012.13-7.ALPS_EMMC_ALPS.bin emmc.bin

==Flash the phone==

Run the following command, then connect the phone to your PC.

flasher -i

The current firmware version of your phone should appear. It is now time to flash.

Use the following list to determine which of the steps below you need to use to accomplish a particular task:

* Upgrade operating system: Replace operating system
* Recover from damaged OS install: Replace operating system
* "Unbrick" phone: Replace operating system or Comprehensive reset
* Reset back to a "clean slate": Comprehensive reset
* De-brand phone: Comprehensive reset
* Prepare for enabling open mode: Comprehensive reset
* Disable open mode: Comprehensive reset
* Prepare for selling, recycling, or destroying phone: Zeroize device
* Clear data before returning phone for warranty service (if possible): Zeroize device
* Reset device lock code: Zeroize device

===Replace operating system (preserves user data)===

The following command will replace your phone's operating system with the supplied firmware image. All applications will be removed, but music/documents/maps/etc. will be kept. This is equivalent to updating/restoring your phone using the Nokia Software Updater (NSU) utility.

flasher -f -F main.bin

===Comprehensive reset (destroys user data)===

The following commands will remove all data from your phone and restore it to factory state. The provided content files (sample music, wallpaper, etc.) will be restored.

flasher -f -F main.bin
flasher -f -F main.bin -F emmc.bin --flash-only=mmc

===Zeroize device (destroys user data)===

The following commands will securely erase your phone such that no data can be recovered later, then restore the operating system and provided content.

{{ambox
|type=delete
|text=The secure erase feature has not been audited by a 3rd party. Do not rely on it to protect all traces of highly sensitive information from a well-funded attacker. The first part will take a very long time - let it run overnight.
}}

flasher -f -F main.bin --erase-user-data=secure
flasher -f -F main.bin -F emmc.bin --flash-only=mmc

==Recovering from flash errors==

'''Note''': If you did not receive any errors, you can skip this section.

In some cases, the new firmware image includes cellular modem (CMT) firmware that is older than what is already installed. This has typically happened when flashing N9s running 003 (China) firmware with other firmware variants. If you received an error about flashing the CMT, obtain the image for the firmware that was previously installed, then run:

flasher -f -F old_main.bin --flash-only=cmt

If you previously upgraded your phone "over the air" (through SSU) and now receive a Downgrade disallowed error when flashing, try flashing an image with a higher variant code. For example, if you experienced the error with variant 001, try using variant 005 instead.

==Reboot into the new operating system==

The phone is now ready to leave flashing mode:

flasher -R

Use the power/lock button to boot your phone into the new system. Your N9 is now ready to use!

== Tutorial ==
* YouTube Video Tutorial: http://youtu.be/u5Qp92WttU4

== References ==
[http://talk.maemo.org/showthread.php?t=82693 HOWTO Comprehensive Firmware Flashing Guide for N9 by itsnotabigtruck]

[[Category:N9]]

Flashing N9

2018-03-03T15:35:27Z

181.179.18.175: /* Prepare to Flash */

{{ambox
|type=notice
|text=This '''unofficial''' guide recommends downloads from '''untrusted''' third party servers. Nobody knows who hosts the content and whether the software has not been altered (e.g. spyware). '''Use at your very own risk.'''
}}

== Warnings ==
* Improperly using flasher could damage your phone and void your warranty. However, following these directions precisely to use flasher to install "stock" Nokia firmware images is quite safe, and can fix problems that would otherwise require warranty service. In any case, '''flashing your phone is at your own risk'''. Do not use this guide if you aren't somewhat familiar with the command prompt/terminal on your operating system. While many users have experienced success with this process, it is not officially recommended by Nokia in any way. '''Read the entire guide ''before'' you start.'''
* Due to artificial limitations placed by Nokia, it is not possible to downgrade the installed firmware on the device using Flasher.
* Do not modify your device's product code. It does not affect a device's ability to receive software updates, and may permanently damage your device.

==Selecting a Firmware Image==

Main firmware images for the Nokia N9 are divided up into "variants" by regions of the world. Except for carrier-branded variants and the 003 (China) firmware, these images are more or less the same.

001 - Europe (1), Latin/South America, South Africa
003 - China
005 - Asia/Pacific (incl. Australia/New Zealand, excl. China)
006 - Middle East
009 - Europe (2)
2xx, 3xx, 4xx - "Country Variant" and carrier-branded images

Downgrades of firmware are '''blocked''' by the phone.
Whether something is a "downgrade" is determined by comparing the entire version strings of the old and new firmware versions, which include the variant code, from left to right. As a result, the variant code must be the same or higher unless you also upgrade the firmware version at the same time. For example:

PR 1.1 variant 009 to PR 1.1 variant 003: '''Blocked'''
PR 1.1 variant 003 to PR 1.1 variant 009: '''Allowed'''
PR 1.1 variant 009 to PR 1.2 variant 001: '''Allowed'''
PR 1.1.1 variant 006 to PR 1.2 variant 005: '''Allowed'''
PR 1.2 variant 001 to PR 1.1 variant 001: '''Blocked'''

Additionally, there is a content image ("eMMC image") for most countries/regions that can be used to reset the user data on the phone and restore the wallpaper/music/map files that originally shipped with it. It is possible to "mix and match" any content image with any main firmware image, which is useful for installing your home country's maps on an imported N9. If you don't require preinstalled maps, or if Nokia doesn't produce a content image for your country (e.g. US and Canada), you can save time by using the content image for product code '''059J1Z5''' ("rest of world"), which doesn't include map files.

When downloading firmware images, it doesn't matter which color or capacity (16/64 GB) you select - the files are the same for all models.

Nokia recommends always using the latest firmware image for your phone's product code (printed on the SIM card tray). This is the safest option. However, you may wish to change to a different variant than what shipped with the phone for the following reasons:

* Receiving updates sooner - new firmware versions are normally released for the 001 variant first
* Removing carrier branding - installing 00x variant firmware makes your subsidized N9 act just like an unlocked one
* Switching away from 003 (China) firmware - firmware images for N9s shipped in China lack Western online service integration (Twitter, Facebook, Skype, Dropbox) and include the Chinese IM service QQ instead

==Download Firmware image==

Use the following steps to retrieve the appropriate firmware files for your phone:

Note: The official firmware source is not currently working, skeiron.org is also gone, www.mrcrab.net answers with 404. [http://www.swagman.org/juice/ubiboot/ swagman.org] contains files which look interesting, but what is what? who can fill in the blanks?

===Windows===
Download and run [http://www.symbian-toys.com/navifirm.aspx NaviFirm+], a utility for downloading firmware files from Nokia's servers.
Make sure Server is set to Nokia Care Suite.
Find Nokia N9 (RM-696) in the Products list, then select the firmware release you wish to install.

10.2011.34.1 = PR1.0
20.2011.40.4 = PR1.1
22.2011.44.2 = PR1.1.1 (Middle East only)
30.2012.7.1 = PR1.2
40.2012.21.3 = PR1.3

Select the appropriate product code in the Variants list. In most cases, you should use the product code printed on the SIM tray.
Click Unmark All, then scroll to the bottom of the Files section. Tick the boxes for the two files starting with DFL61_HARMATTAN.
Click Download. Wait for the download to complete, then close NaviFirm+.

===Linux===
Install WINE using your Linux distribution's package manager.
Download and run [http://code.google.com/p/navifirmex/ NaviFirmEx], a replacement for Navifirm+ that doesn't use .NET.
Select Option > Server > Nokia Care Suit [sic] in the menu.
Find Nokia N9 (RM-696) in the Products list, then select the firmware release and variant you wish to install (see above).
Click Add to Download Task, then Inverse Select. Tick the boxes for the two files starting with DFL61_HARMATTAN.
Click Download. Wait for the download to complete, then close NaviFirmEx.

===Any OS===
Go to [http://www.btusers.com.ar/nan/nokia/ Nokia Firmwares] (unofficial firmware download site) and search for Nokia N9. Click CHECK! toward the right-hand side.
Click the link for the firmware release you wish to install (see above).
Click the link for the file starting with DFL61_HARMATTAN.
Unlike NaviFirm+, this website cannot retrieve content/eMMC images.

==Back up your data==

'''All''' of the procedures described below will destroy some or all of the data on your phone, so you should be sure to back up anything you care about first. This includes contacts, messages, game saves, music, .deb packages, etc. You can do this either through the built-in backup feature, or manually using tools in developer mode.

==Prepare to Flash==

If your phone has a low battery charge (less than 50%), plug it in and let it charge for a while. Then, make sure your phone is disconnected from any USB cables (including USB chargers). Power off the phone.

You need the flasher program: with Nokia gone, skeiron also off-line, hopefully [http://www.swagman.org/juice/flasher_3.12.1_i386.deb this deb link] still works. '''Do not''' use Flasher 3.5 - it isn't compatible with the N9/N950.
You can skip this step if you've already installed Flasher.

On Windows, open a Command Prompt with Administrator permissions (with UAC, right-click Command Prompt and select Run as administrator). On Linux, open a root shell (sudo -i/su). Change to the directory containing the firmware images you downloaded.

On Windows, run the following command in order to add Flasher to the system path:

set PATH="C:\Program Files\Nokia\Flasher;%PATH%"

'''Note''': In the following the main firmware image is called "main.bin" and the eMMC image is called "emmc.bin". You must replace main.bin and emmc.bin in the commands with the actual names of the image files you are flashing or rename the downloaded files like this (e.g. under linux)

mv DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin main.bin
mv DFL61_HARMATTAN_40.2012.13-7.ALPS_EMMC_ALPS.bin emmc.bin

==Flash the phone==

Run the following command, then connect the phone to your PC.

flasher -i

The current firmware version of your phone should appear. It is now time to flash.

Use the following list to determine which of the steps below you need to use to accomplish a particular task:

* Upgrade operating system: Replace operating system
* Recover from damaged OS install: Replace operating system
* "Unbrick" phone: Replace operating system or Comprehensive reset
* Reset back to a "clean slate": Comprehensive reset
* De-brand phone: Comprehensive reset
* Prepare for enabling open mode: Comprehensive reset
* Disable open mode: Comprehensive reset
* Prepare for selling, recycling, or destroying phone: Zeroize device
* Clear data before returning phone for warranty service (if possible): Zeroize device
* Reset device lock code: Zeroize device

===Replace operating system (preserves user data)===

The following command will replace your phone's operating system with the supplied firmware image. All applications will be removed, but music/documents/maps/etc. will be kept. This is equivalent to updating/restoring your phone using the Nokia Software Updater (NSU) utility.

flasher -f -F main.bin

===Comprehensive reset (destroys user data)===

The following commands will remove all data from your phone and restore it to factory state. The provided content files (sample music, wallpaper, etc.) will be restored.

flasher -f -F main.bin
flasher -f -F main.bin -F emmc.bin --flash-only=mmc

===Zeroize device (destroys user data)===

The following commands will securely erase your phone such that no data can be recovered later, then restore the operating system and provided content.

{{ambox
|type=delete
|text=The secure erase feature has not been audited by a 3rd party. Do not rely on it to protect all traces of highly sensitive information from a well-funded attacker. The first part will take a very long time - let it run overnight.
}}

flasher -f -F main.bin --erase-user-data=secure
flasher -f -F main.bin -F emmc.bin --flash-only=mmc

==Recovering from flash errors==

'''Note''': If you did not receive any errors, you can skip this section.

In some cases, the new firmware image includes cellular modem (CMT) firmware that is older than what is already installed. This has typically happened when flashing N9s running 003 (China) firmware with other firmware variants. If you received an error about flashing the CMT, obtain the image for the firmware that was previously installed, then run:

flasher -f -F old_main.bin --flash-only=cmt

If you previously upgraded your phone "over the air" (through SSU) and now receive a Downgrade disallowed error when flashing, try flashing an image with a higher variant code. For example, if you experienced the error with variant 001, try using variant 005 instead.

==Reboot into the new operating system==

The phone is now ready to leave flashing mode:

flasher -R

Use the power/lock button to boot your phone into the new system. Your N9 is now ready to use!

== Tutorial ==
* YouTube Video Tutorial: http://youtu.be/u5Qp92WttU4

== References ==
[http://talk.maemo.org/showthread.php?t=82693 HOWTO Comprehensive Firmware Flashing Guide for N9 by itsnotabigtruck]

[[Category:N9]]

Flashing N9

2018-03-03T15:31:14Z

181.179.18.175: Download Firmware image has no clear candidate

{{ambox
|type=notice
|text=This '''unofficial''' guide recommends downloads from '''untrusted''' third party servers. Nobody knows who hosts the content and whether the software has not been altered (e.g. spyware). '''Use at your very own risk.'''
}}

== Warnings ==
* Improperly using flasher could damage your phone and void your warranty. However, following these directions precisely to use flasher to install "stock" Nokia firmware images is quite safe, and can fix problems that would otherwise require warranty service. In any case, '''flashing your phone is at your own risk'''. Do not use this guide if you aren't somewhat familiar with the command prompt/terminal on your operating system. While many users have experienced success with this process, it is not officially recommended by Nokia in any way. '''Read the entire guide ''before'' you start.'''
* Due to artificial limitations placed by Nokia, it is not possible to downgrade the installed firmware on the device using Flasher.
* Do not modify your device's product code. It does not affect a device's ability to receive software updates, and may permanently damage your device.

==Selecting a Firmware Image==

Main firmware images for the Nokia N9 are divided up into "variants" by regions of the world. Except for carrier-branded variants and the 003 (China) firmware, these images are more or less the same.

001 - Europe (1), Latin/South America, South Africa
003 - China
005 - Asia/Pacific (incl. Australia/New Zealand, excl. China)
006 - Middle East
009 - Europe (2)
2xx, 3xx, 4xx - "Country Variant" and carrier-branded images

Downgrades of firmware are '''blocked''' by the phone.
Whether something is a "downgrade" is determined by comparing the entire version strings of the old and new firmware versions, which include the variant code, from left to right. As a result, the variant code must be the same or higher unless you also upgrade the firmware version at the same time. For example:

PR 1.1 variant 009 to PR 1.1 variant 003: '''Blocked'''
PR 1.1 variant 003 to PR 1.1 variant 009: '''Allowed'''
PR 1.1 variant 009 to PR 1.2 variant 001: '''Allowed'''
PR 1.1.1 variant 006 to PR 1.2 variant 005: '''Allowed'''
PR 1.2 variant 001 to PR 1.1 variant 001: '''Blocked'''

Additionally, there is a content image ("eMMC image") for most countries/regions that can be used to reset the user data on the phone and restore the wallpaper/music/map files that originally shipped with it. It is possible to "mix and match" any content image with any main firmware image, which is useful for installing your home country's maps on an imported N9. If you don't require preinstalled maps, or if Nokia doesn't produce a content image for your country (e.g. US and Canada), you can save time by using the content image for product code '''059J1Z5''' ("rest of world"), which doesn't include map files.

When downloading firmware images, it doesn't matter which color or capacity (16/64 GB) you select - the files are the same for all models.

Nokia recommends always using the latest firmware image for your phone's product code (printed on the SIM card tray). This is the safest option. However, you may wish to change to a different variant than what shipped with the phone for the following reasons:

* Receiving updates sooner - new firmware versions are normally released for the 001 variant first
* Removing carrier branding - installing 00x variant firmware makes your subsidized N9 act just like an unlocked one
* Switching away from 003 (China) firmware - firmware images for N9s shipped in China lack Western online service integration (Twitter, Facebook, Skype, Dropbox) and include the Chinese IM service QQ instead

==Download Firmware image==

Use the following steps to retrieve the appropriate firmware files for your phone:

Note: The official firmware source is not currently working, skeiron.org is also gone, www.mrcrab.net answers with 404. [http://www.swagman.org/juice/ubiboot/ swagman.org] contains files which look interesting, but what is what? who can fill in the blanks?

===Windows===
Download and run [http://www.symbian-toys.com/navifirm.aspx NaviFirm+], a utility for downloading firmware files from Nokia's servers.
Make sure Server is set to Nokia Care Suite.
Find Nokia N9 (RM-696) in the Products list, then select the firmware release you wish to install.

10.2011.34.1 = PR1.0
20.2011.40.4 = PR1.1
22.2011.44.2 = PR1.1.1 (Middle East only)
30.2012.7.1 = PR1.2
40.2012.21.3 = PR1.3

Select the appropriate product code in the Variants list. In most cases, you should use the product code printed on the SIM tray.
Click Unmark All, then scroll to the bottom of the Files section. Tick the boxes for the two files starting with DFL61_HARMATTAN.
Click Download. Wait for the download to complete, then close NaviFirm+.

===Linux===
Install WINE using your Linux distribution's package manager.
Download and run [http://code.google.com/p/navifirmex/ NaviFirmEx], a replacement for Navifirm+ that doesn't use .NET.
Select Option > Server > Nokia Care Suit [sic] in the menu.
Find Nokia N9 (RM-696) in the Products list, then select the firmware release and variant you wish to install (see above).
Click Add to Download Task, then Inverse Select. Tick the boxes for the two files starting with DFL61_HARMATTAN.
Click Download. Wait for the download to complete, then close NaviFirmEx.

===Any OS===
Go to [http://www.btusers.com.ar/nan/nokia/ Nokia Firmwares] (unofficial firmware download site) and search for Nokia N9. Click CHECK! toward the right-hand side.
Click the link for the firmware release you wish to install (see above).
Click the link for the file starting with DFL61_HARMATTAN.
Unlike NaviFirm+, this website cannot retrieve content/eMMC images.

==Back up your data==

'''All''' of the procedures described below will destroy some or all of the data on your phone, so you should be sure to back up anything you care about first. This includes contacts, messages, game saves, music, .deb packages, etc. You can do this either through the built-in backup feature, or manually using tools in developer mode.

==Prepare to Flash==

If your phone has a low battery charge (less than 50%), plug it in and let it charge for a while. Then, make sure your phone is disconnected from any USB cables (including USB chargers). Power off the phone.

Go to the [http://tablets-dev.nokia.com/maemo-dev-env-downloads.php Flasher download site][http://skeiron.org/tablets-dev/maemo-dev-env-downloads/ (mirror)] and download/install the version for your operating system (WinFlasher_3.12.1.exe, MacFlasher_3.12.1.dmg, flasher_3.12.1_i386.deb, or flasher_3.12.1_amd64.deb). Here is [http://www.swagman.org/juice/flasher_3.12.1_i386.deb an other possible link]. '''Do not''' use Flasher 3.5 - it isn't compatible with the N9/N950.
You can skip this step if you've already installed Flasher.

On Windows, open a Command Prompt with Administrator permissions (with UAC, right-click Command Prompt and select Run as administrator). On Linux, open a root shell (sudo -i/su). Change to the directory containing the firmware images you downloaded.

On Windows, run the following command in order to add Flasher to the system path:

set PATH="C:\Program Files\Nokia\Flasher;%PATH%"

'''Note''': In the following the main firmware image is called "main.bin" and the eMMC image is called "emmc.bin". You must replace main.bin and emmc.bin in the commands with the actual names of the image files you are flashing or rename the downloaded files like this (e.g. under linux)

mv DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin main.bin
mv DFL61_HARMATTAN_40.2012.13-7.ALPS_EMMC_ALPS.bin emmc.bin

==Flash the phone==

Run the following command, then connect the phone to your PC.

flasher -i

The current firmware version of your phone should appear. It is now time to flash.

Use the following list to determine which of the steps below you need to use to accomplish a particular task:

* Upgrade operating system: Replace operating system
* Recover from damaged OS install: Replace operating system
* "Unbrick" phone: Replace operating system or Comprehensive reset
* Reset back to a "clean slate": Comprehensive reset
* De-brand phone: Comprehensive reset
* Prepare for enabling open mode: Comprehensive reset
* Disable open mode: Comprehensive reset
* Prepare for selling, recycling, or destroying phone: Zeroize device
* Clear data before returning phone for warranty service (if possible): Zeroize device
* Reset device lock code: Zeroize device

===Replace operating system (preserves user data)===

The following command will replace your phone's operating system with the supplied firmware image. All applications will be removed, but music/documents/maps/etc. will be kept. This is equivalent to updating/restoring your phone using the Nokia Software Updater (NSU) utility.

flasher -f -F main.bin

===Comprehensive reset (destroys user data)===

The following commands will remove all data from your phone and restore it to factory state. The provided content files (sample music, wallpaper, etc.) will be restored.

flasher -f -F main.bin
flasher -f -F main.bin -F emmc.bin --flash-only=mmc

===Zeroize device (destroys user data)===

The following commands will securely erase your phone such that no data can be recovered later, then restore the operating system and provided content.

{{ambox
|type=delete
|text=The secure erase feature has not been audited by a 3rd party. Do not rely on it to protect all traces of highly sensitive information from a well-funded attacker. The first part will take a very long time - let it run overnight.
}}

flasher -f -F main.bin --erase-user-data=secure
flasher -f -F main.bin -F emmc.bin --flash-only=mmc

==Recovering from flash errors==

'''Note''': If you did not receive any errors, you can skip this section.

In some cases, the new firmware image includes cellular modem (CMT) firmware that is older than what is already installed. This has typically happened when flashing N9s running 003 (China) firmware with other firmware variants. If you received an error about flashing the CMT, obtain the image for the firmware that was previously installed, then run:

flasher -f -F old_main.bin --flash-only=cmt

If you previously upgraded your phone "over the air" (through SSU) and now receive a Downgrade disallowed error when flashing, try flashing an image with a higher variant code. For example, if you experienced the error with variant 001, try using variant 005 instead.

==Reboot into the new operating system==

The phone is now ready to leave flashing mode:

flasher -R

Use the power/lock button to boot your phone into the new system. Your N9 is now ready to use!

== Tutorial ==
* YouTube Video Tutorial: http://youtu.be/u5Qp92WttU4

== References ==
[http://talk.maemo.org/showthread.php?t=82693 HOWTO Comprehensive Firmware Flashing Guide for N9 by itsnotabigtruck]

[[Category:N9]]