WinFlasher GUI | WinFlasher GUI | Easy way to flash your N9



Rep: (472)
GUI toWinflasher to make it easier for inexperienced users
Attached Image


The archive isflasher and graphic interface to it. Both files must be in the same folder.
For the flasher to work, you need to installNokia Connectivity Cable Drivers .
Always the latest versionNCCD can download from the official site
or right here:Attached fileNokia_Connectivity_Cable_Driver_rus.msi(7.51 MB)


1. Simple firmware.
- in fieldFirmware You need to specify the path to the main firmware file.
- if you need to flash withcontent , then you need to put a tick in front of it and select the appropriate file.

2. Flashing individual components.
- in fieldfirmware The main firmware image must be selected in order to obtain the algorithm and the addresses of the component load. The firmware itself will not load.
- at the right edge of the window, one of five elements should be noted if the image for this element is not specified, then the data will be loaded from the main image.

3. Download firmware without flashing the device.
- you need to select the necessary checkboxes on the left side and specify the path to the images containing the required components.

4. Cleaning device
- cleaningcontent will delete only the data from the user partition (MyDocs)
- cleaningdata will remove content , as well as all user settings, will clear the installed lock code.
Attention! When cleaning the device, the content section is completely erased, after which it is not automatically generated. It is recommended to use the content firmware in conjunction with cleaning the device, or after that you need to format the device in the phone settings. Otherwise, you will not have access to memory for storing content.

5. Parameters.
- atcold firmware Winflasher tries to identify a switched off or dead phone by the digital signature of the device. It helps in many cases when the phone does not turn on and is not detected when connected.
- parameterreboot Strangely enough, it reboots the phone after the firmware process. Otherwise, the device will continue to be in firmware mode after the end of all operations and wait for new commands.
- PPreventing warranty notice It can help to avoid the appearance of an ugly big message about the loss of warranty when you turn on the phone, after the firmware is not original images. It works only before flashing to non-original files, if at the same time you clear the Disclaimer section in the device's CAL zone by executing the command disclaimer-cal remove View-openmode in the smartphone terminal. If you already have this message, this checkbox will not help.

6. Expert Mode.
- by ticking "I am an expert!", you can ignore all the parameters created by the program and write your own in the line, you can also try to perform the required operation even when it does not work, and with the tick removed, the execution button is inactive.

The program works inadequately when the paths to the files contain Russian characters or symbols of other languages ​​other than English. Use only English file and folder names.

P.S. just do not forget to read the tooltips when you hover the mouse over the elements of the program.

Attached filewinflasherguiv0.0.4_2252.zip(609.22 KB)


Software and description created by CODeRUS, for which he thanks a lot!

Post has been editedAlexxxl - 27.11.12, 23:36



Rep: (4582)
Detailed instructions on the Nokia N9 firmware using the WinFlasher GUI


I think someone will help. I tried to write in an accessible language. The article has all the necessary links for firmware.

What is contained in the content file?
Pictures, videos, music ... To demonstrate the possibilities in the salons of sales. From the useful there are only maps.

What is the difference between the usual and cold firmware?
With a “cold” firmware, the flasher tries to determine if the smartphone is turned off or dead by the digital signature of the device. It helps in many cases when the smartphone does not turn on and is not detected when connected.


[01] Downloading the WinFlasher GUI and Nokia Connectivity Cable Driver:
  • Current version of WinFlasher GUI: download
  • The current version of Nokia Connectivity Cable Driver: download

[02] Download the firmware image and the required content file:
[size = 10] PCT [/ size]

  • Direct link to the firmware image (Nokia Care Suite): download(1.16 GB)

CRC-32 8c9ea3a3
  • Direct link to the content file (Nokia Care Suite): download(2.78 GB)

CRC-32 d8cd54c4
  • Direct link to the content file (version without maps) (Nokia Care Suite): download(255.46 MB)

CRC-32 94713482
[size = 10] Any gray smartphone [/ size]

These links are also relevant for those who do not know the PR number of the firmware installed in the smartphone!
  • Direct link to the firmware image (Nokia Care Suite): download(1.14 GB)

CRC-32 3290adcc
  • Direct link to the content file (Nokia Care Suite): download(1.55 GB)

CRC-32 09f33f15
  • Direct link to the content file (version without maps) (Nokia Care Suite): download(255.46 MB)

CRC-32 94713482
After downloading, be sure to check the hash sums of files!

[03] Extract the WinFlasher GUI folder from the archive to any local disk
[04] Rename the firmware image to ape.bin content file - in emmc.bin and move them to the WinFlasher GUI folder (This procedure is done only for your CONVENIENCE, if there is little experience in the firmware - leave the original file names, they may be needed for debriefing.)
[05] Install or update Nokia Connectivity Cable Driver. If at the end of the installation you need to restart the PC - agree
[06] We backup all the necessary information (contacts, photos, music, etc.) and turn off the smartphone
[07] Run WinFlasher GUI.exe
Attention: the application does not work correctly when the paths to the files contain Russian characters or characters of other languages ​​other than English. Use only English file and folder names!
Cleaning takes about 20 minutes even on a “clean” smartphone! So have patience!
In articles on other sites you can read that the smartphone must be connected in synchronization mode. This is true, but there is no fundamental difference. The flasher will still switch the smartphone to the "dead" state by a reboot command. And the article has fewer letters.
Firmware file
  • Click on the button with 3 dots opposite the Firmware item and select the firmware image (ape.bin )
  • Put a tick on the Content item, click on the button with 3 dots opposite and select the content file (emmc.bin )
  • Put a tick on the items Cleaning and Data
  • Press the key>>>
  • We connect the switched off smartphone to the PC. After a few seconds, the firmware process will begin.
  • We are waiting until the lines appear in the command window:

Updating SW release
Success
To continue, press any key ...

  • Press Enter and disconnect the smartphone. That's all!

Firmware with content file - cold mode
  • Click on the button with 3 dots opposite the Firmware item and select the firmware image (ape.bin )
  • Put a tick on the Content item, click on the button with 3 dots opposite and select the content file (emmc.bin )
  • Put a tick on the items Cleaning, Data and Cold Firmware
  • Press the key>>>
  • We connect the switched off smartphone to the PC. After a few seconds, the firmware process will begin.
  • We are waiting until the lines appear in the command window:

Updating SW release
Success
To continue, press any key ...

  • Press Enter and disconnect the smartphone. That's all!


Post has been editedAlexxxl - 06.11.14, 12:56
Reason for editing: merging posts



Rep: (0)
How to connect the bodies to your computer?



Rep: (472)
by usb cable



Rep: (0)
That's what got out

Attached images
Attached Image



Rep: (472)
SATURN27,

Well, first of all, intelligently put the question: what are you doing, how why?
Secondly - it would not be bad to lay a screen of Win-flasher settings

ps it would also be good to indicate the paths where the firmware you are in .. and the flasher folder itself is transferred from the desktop to the C: \ drive, for example



Rep: (0)
I played with N9 QuickTweak, something went wrong and a constant reboot started. I tried to flash it, it turned out that it turned out but after the firmware I decided to do a reset through the settings, after that the body does not turn on and when I try to re-flash it issues ERROR. What can be done, I have 4 bodies and this is the first N9 firmware experience. Tell me what to do, I'm in a panic !!!
I tried to install the folder with the firmware on different disks!

Post has been editedSATURN27 - 29.01.13, 21:57



Rep: (472)
SATURN27,
Not with your firmware you flashed the phone ... Go to the theme of the firmware n9 there exactly the same situation is described on the last pages



Rep: (0)
Hi, help with the problem. I installed the nitroid 4 release, played a day, changing systems, glitches started to pop up, with a blink especially, it just didn’t load the system, at first the waiting circle spun for a long time, rebooted a couple of times, then it only reached the choice of systems, poked a blink, and then dumb and rebooted, and in the end, just on the first screen saver, Nokia reboots, more precisely, it reboots only on charging, and it was so stupidly cut down .. I downloaded this winflasher, firmware DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM, everything was as it should for my body, renamed it (it seems it’s not it is especially important) in ape and threw it into the folder with the flasher, put a check ki for cleaning and data .. started .. everything went fine, launched, set the time, accounting, it came to Reset-Clean the device, cleared it, it rebooted itself and again the waiting circle and dumb on it! What it is?)

I poured a lot of water, but in order to be as informative as possible

Post has been editedParanoid01 - 09.02.13, 15:28



Rep: (472)
Please try again, this time with the content file. Put a dawData cleansing And do not do a full cleaning after this, it will be useless.



Rep: (0)
I will try, but something seems to me to Khan to him ... the error constantly gives
D: \ WinFlasherGUI>flasher.exe -F "D: \ WinFlasherGUI \ ape.bin" -f --erase-user-data =
secure
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Suitable USB interface (bootloader / phonet) not found, waiting ...
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_001
Sending ape-algo image (7096 kB) ...
100% (7096 of 7096 kB, avg. 19990 kB / s)
Suitable USB interface (phonet) not found, waiting ...
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1603
Server implements softupd protocol version 1.8

Battery level 49%, continuing.
Erasing, this may take a while.
Erase done.
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_001
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 53%, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100% 1/1 kB NA]
[] cmt-2nd [pending 0% 0/0 kB NA]
[] cmt-algo [pending 0% 0/0 kB NA]
[] cmt-mcusw [pending 0% 0/0 kB NA]
[x] xloader [finished 100% 23/23 kB NA]
[x] secondary [finished 100% 94/94 kB NA]
[] kernel [pending 0% 0/0 kB NA]
[] rootfs [pending 0% 0/0 kB NA]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100% 1/1 kB NA]
[x] cmt-2nd [finished 100% 95/95 kB NA]
[x] cmt-algo [finished 100% 789/789 kB NA]
[x] cmt-mcusw [finished 100% 6050/6050 kB 3166 kB / s]
[x] xloader [finished 100% 23/23 kB NA]
[x] secondary [finished 100% 94/94 kB NA]
[x] kernel [finished 100% 2714/2714 kB 2757 kB / s]
[f] rootfs [pending 0% 0/1170282 kB NA]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
mmc: sfdisk returned status 1
mmc: Could not exec 'tune2fs -L rootfs / tmp / sudmmc2lh7Di / internal0p2'
mmc: Could not remove mount directory / tmp / sudmmc2lh7Di / mnt: No such file or dir
ectory
[Pipe 4] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

D: \ WinFlasherGUI>pause
To continue, press any key. .

Then it turns on and writes about the guarantee

At the beginning of this nebylo ..
Content pulls, I'll try, but I hardly believe that it will help

Post has been editedParanoid01 - 10.02.13, 06:03



Rep: (472)
Paranoid01,
Download the firmware again, and download the hash of the downloaded file.



Rep: (472)
M



Rep: (0)
People help please!
When you turn on the NOKIA N9, the inscription appears: "Device not working properly ... etc."
I wanted to flash it with a flash, but he writes that the battery charge is low, but I cannot charge it, as I connect to it, this sign appears.

Help.



Rep: (472)
Rus7an,
and the full text and photo you can do?



Rep: (0)
Good day.
Help is needed. They brought me a phone nokia n9, they said that it was buggy and they tried to flash it. As a result, when turned on, it writes the full-screen warning of the modified by, etc. I tried to flash as described in the header, did everything in order, sewed files from the header. The result is the same, it gives an error and that's it.

Here is what he writes:


E: \ flash>flasher.exe -F "E: \ flash \ ape.bin" -F "E: \ flash \ emmc.bin" -f
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Suitable USB interface (bootloader / phonet) not found, waiting ...
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_001
Sending ape-algo image (7103 kB) ...
100% (7103 of 7103 kB, avg. 6182 kB / s)
Suitable USB interface (phonet) not found, waiting ...
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1603
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3.480.04.1_PR_480
Image moslo not present
Image tar skipped
Image config skipped

Battery level 66%, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100% 1/1 kB NA]
[x] cmt-2nd [finished 100% 95/95 kB NA]
[] cmt-algo [pending 0% 0/0 kB NA]
[] cmt-mcusw [pending 0% 0/0 kB NA]
[x] xloader [finished 100% 23/23 kB NA]
[x] secondary [finished 100% 94/94 kB NA]
[_] kernel [finished 100% 2714/2714 kB 1734 kB / s]
[_] rootfs [finishing 100% 4096/1170393 kB NA]
[] mmc [pending 0% 0/0 kB NA]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100% 1/1 kB NA]
[x] cmt-2nd [finished 100% 95/95 kB NA]
[x] cmt-algo [finished 100% 789/789 kB NA]
[x] cmt-mcusw [finished 100% 6050/6050 kB 3240 kB / s]
[x] xloader [finished 100% 23/23 kB NA]
[x] secondary [finished 100% 94/94 kB NA]
[x] kernel [finished 100% 2714/2714 kB 1734 kB / s]
[f] rootfs [finishing 0% 5120/1170393 kB NA]
[-] mmc [pending 0% 0/0 kB NA]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
mmc: sfdisk returned status 1
mmc: Could not exec 'tune2fs -L rootfs / tmp / sudmmcnPpvck / internal0p2'
mmc: Could not remove mount directory / tmp / sudmmcnPpvck / mnt: No such file or dir
ectory
[Pipe 5] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

E: \ flash>pause
To continue, press any key. . .

Attached Image


Help who can, how to revive him?

Post has been editedAndrey_K - 18.06.13, 02:33



Rep: (472)
Andrey_K,
The name of the firmware file that you are trying to sew



Rep: (0)
Screen and report after flashing with these files.
ape.bin - DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin (1.16 GB)
emmc.bin - D8CD54C4_DFL61_HARMATTAN_40.2012.13-7.EURASIA_EMMC_EURASIA.bin (2.78 GB)

With an error, the firmware ends with two others.
ape.bin - 3290ADCC_DFL61_HARMATTAN_40.2012.21-3.480.04.1_PR_LEGACY_480_ARM_RM-696_PRD_signed.bin (1.14GB)
emmc.bin - 09F33F15_DFL61_HARMATTAN_40.2012.21-3.ALPS.15_EMMC_ALPS.bin (1.55GB) (Already confused, I have not tried it)

Checksums are the same.



Rep: (472)
Andrey_K,
I don’t understand ... Your phone seems to have a 480 bootloader, and you 001 was the first to try to fill in



Rep: (0)
I tried to flash these files:
ape.bin - 3290ADCC_DFL61_HARMATTAN_40.2012.21-3.480.04.1_PR_LEGACY_480_ARM_RM-696_PRD_signed
emmc.bin - 09F33F15_DFL61_HARMATTAN_40.2012.21-3.ALPS.15_EMMC_ALPS
Act on this instruction: (Firmware with content file - cold-mode)


Here is the result ...


E: \ flash>flasher.exe -F "E: \ flash \ ape.bin" -F "E: \ flash \ emmc.bin" -f --erase-use
r-data = secure -c
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Using 1st image to detect HW
Suitable USB interface (bootrom) not found, waiting ...
Waiting for ASIC id ...
Got 69 bytes.
ASIC ID:
05 01 05 01 36 30 07 07 13 02 01 00 12 15 01 6e
a4 0d f5 71 d8 15 3e 6b 69 0b fb 6a d8 fb 54 20
ef 43 d1 14 15 01 12 dd 2f 66 d4 55 fe 19 2c 62
b9 b8 e2 65 0a fc 1d 9f 3f 90 15 09 01 13 bf 3e
ef 15 52 e7 03
HW variant: HS
Found matching 1st (916)
Sending 1st image (26496 bytes) ... done.
Sending HWID query ... Received 11 bytes from 1st
ERROR: ReadFile error 31
usb_bulk_read: No error
Got HWID: RM-696: 1603
Suitable USB interface (bootrom) not found, waiting ...
Waiting for ASIC id ...
Got 69 bytes.
ASIC ID:
05 01 05 01 36 30 07 07 13 02 01 00 12 15 01 6e
a4 0d f5 71 d8 15 3e 6b 69 0b fb 6a d8 fb 54 20
ef 43 d1 14 15 01 12 dd 2f 66 d4 55 fe 19 2c 62
b9 b8 e2 65 0a fc 1d 9f 3f 90 15 09 01 13 bf 3e
ef 15 52 e7 03
Sending 2nd image (26112 bytes) ... done.
Sending ping ... pong.
Sending ape-algo (7273728 bytes) ... done.
Suitable USB interface (bootloader / phonet) not found, waiting ...
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1603
Server implements softupd protocol version 1.8

Battery level 69%, continuing.
Erasing, this may take a while.
Erase done.
Image SW version DFL61_HARMATTAN_40.2012.21-3.480.04.1_PR_480
Image moslo not present
Image tar skipped
Image config skipped

Battery level 73%, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100% 1/1 kB NA]
[] cmt-2nd [pending 0% 0/0 kB NA]
[] cmt-algo [pending 0% 0/0 kB NA]
[] cmt-mcusw [pending 0% 0/0 kB NA]
[x] xloader [finished 100% 23/23 kB NA]
[x] secondary [finished 100% 94/94 kB NA]
[] kernel [pending 0% 0/0 kB NA]
[] rootfs [pending 0% 0/0 kB NA]
[] mmc [pending 0% 0/0 kB NA]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100% 1/1 kB NA]
[x] cmt-2nd [finished 100% 95/95 kB NA]
[x] cmt-algo [finished 100% 789/789 kB NA]
[x] cmt-mcusw [finished 100% 6050/6050 kB 3390 kB / s]
[x] xloader [finished 100% 23/23 kB NA]
[x] secondary [finished 100% 94/94 kB NA]
[x] kernel [finished 100% 2714/2714 kB 3711 kB / s]
[f] rootfs [pending 0% 0/1170393 kB NA]
[-] mmc [pending 0% 0/0 kB NA]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
mmc: sfdisk returned status 1
mmc: Could not exec 'tune2fs -L rootfs / tmp / sudmmcpHPTYG / internal0p2'
mmc: Could not remove mount directory / tmp / sudmmcpHPTYG / mnt: No such file or dir
ectory
[Pipe 4] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

E: \ flash>pause
To continue, press any key. . .

Attached Image

Attached Image


Full version    

Help     rules

Now: 08/14/19, 12:04