How to flash / Phoenix advanced tutorials

For those who want to read, a brief instruction on Phoenix is available here.
For those who do not want to read, there are masters', they know how to do.

I believe that you have already read information on Delight Custom Firmwares legacy blog by having followed the link above, but thanks to KIV6666 from AllNokia.ru, I can extend some Phoenix flashing stuff. So, let me pinpoint some really important things here. You know Phoenix is a professional software and its logs are not so informative to general user, thus being understandable only to specialists. This is why you must keep some information in mind.

Before you start Phoenix installation to Windows 7 or higher, the User Account Control (UAC) is suggested to be turned off from Windows Control Panel settings. Microsoft .NET version 2 Service Pack 2 is the minimum requirement, Phoenix installation will check PC for the .NET version and update it automatically when PC has online connection. Without online connection, you might need to update old .NET versions manually.

Having Phoenix installed, first of all, every program by NOKIA must be closed before flashing! It is also better to close other unnecessary applications, such as automatic garbage sweepers or whatsoever. Use the original USB cable (shipped in one box with your phone) when flashing.

If the above window appears during the flashing, do click OK button in no case! This will cause Phoenix to close and your phone will be bricked! Wait until the end of the flashing process!

I know that it is written on Delight legacy blog: "phoenix crashed - Pheonix Dump window - IF the phone is being flashed in the background, then DO NOT press OK in that window, just ignore it and wait till phone flashing is done", but it is done in such an easy-living way, so that many people simply do not understand how severe and fatal outcome could be out of the wrong action, which will put an end to your bright dreams! This is extremely important to know, so please make yourself acquainted with this error!

Important information for Windows 10 users

It is highly recommended to flash with Phoenix using USB 2.0 port on PCs with Windows XP - 7 OS. If your PC runs Windows 8 or higher, then you might need to take some additional actions (may not be applicable to current Win 10 updated versions at all, unfortunately):

1) If your PC lacks USB 2.0 ports, then try flashing by connecting your phone to newer port the way it is. Do not exploit additional adapters or hubs, as there is not much sense in using them in this case.

2) If your phone cannot be identified by system, you should install Huawei drivers. Please read this post for more information (though you can skip installation of the latest Nokia Ovi Suite).

3) If you receive a Kernel Security Check error or Blue Screen of Death on Windows 10 (especially on 64-bit version) when you initialise the flashing process, then do the following:
- Uninstall Phoenix.
- Disable Signed Driver Enforcement (search Google for it). Your PC will reboot.
- Install Phoenix and do not restart your PC!
- Connect your phone and wait until it will be identified by system.
- Flash your phone (Signed Driver Enforcement must still be disabled).

Still no positive outcome? Whenever you have problem with Phoenix on Windows 10 or lower (even on Windows 7 because of the non-native USB 3.0 drivers), there is an alternate solution - try using Virtual Machine with clean Windows XP or 7 32-bit (on VirtualBox or VMware Player, of course only with native USB 2.0 support), and this can work out as well.

A few words about using Phoenix on Linux machines

Though it was reported by several users that they could flash their smart phones successfully using VMware on Windows 10, in this paragraph you will learn about Linux showing different behaviour. A first and concrete example - it is not possible to flash through a virtual environment like VirtualBox with Ubuntu or its derivatives as a host machine. An explanation of this is plain easy: the USB connection will always be recognised by the host PC first, and you have to manually accept the connection through the options in the VM afterwards. This is a fundamental problem since your phone is first connected, but as soon as Phoenix commences flashing, it puts the phone into flash mode and thereby disrupts the USB connection again and again... As a result, Phoenix cannot accept it when you immediately and manually re-establish connections (no matter how fast you act, it will not simply work that way). All in all, using a VM on Linux PC should be regarded as a waste of time...

Consequently, a good recommendation is a clean Windows 7 32-bit installation on a separate drive, which you can delete afterwards. Will you need to take care of additional points, only if your PC has two SSD hard drives in the RAID mode (i.e. both are recognised as one drive). Windows might not identify this properly during installation even though this problem is not applicable to GNU / Linux! So, at the beginning, you must run the hard drives separately in AHCI mode in order to be able to install Windows 32-bit versions correctly.

Many thanks to Battal Ates who shared this information!

Dead phone USB flashing

Note: if the phone is locked (branded) for certain operator, performing flashing to unlock will not help! Please go down for finding possible solutions. Though, if you forgot the security code, you can flash the phone in dead mode and the lost code will be erased.

In dead flashing mode, you should first disconnect the USB cable, turn off the phone and pull out the battery. When you start flashing process (via Refurbish or SW Reset) and the message "Press phone's power button" appears, just follow the instruction from connecting the USB cable without pressing anything.


For clarity, watch the video above. Hint: use ActiveX or old Flash-supported browser!
Otherwise, you will have to download it first.

Flashing mass memory drive with single MCC file

If you want to append a custom E-disk content on Delight, you can Refurbish your phone with a single file flashing any time you decide so. Just follow the instructions drawn on the image below...

This method utterly eliminates the possibility of killing a phone since there is no real firmware per se due to the absence of ROM flashing files. In other words, only the mass memory drive is involved in this process.

Formatting memory

You can only format a live phone, both internal memory and memory card. In order to do that, launch Phoenix and select your phone from the "Connections" list. Then press File -> Open Product and select your RM. Then go to Product -> File System Format.

Choose a disk for formatting, and press Start. After formatting, your phone might be set to LOCAL MODE. To solve this problem, select NORMAL or TEST in "Operating Mode" menu and the phone will turn on.

Similarly, Phoenix can be used to retrieve information from the phone. To do this, follow the same initial steps as for the formatting memory, but press "Phone Information" instead. Here you can find out the version of hardware and firmware, product code and IMEI of your phone.

If you choose "Production Data Edit" from the same menu, you can view or change the product code. Press "Read" and you will see the product code of your phone. If you need to change this code, erase the line concerned and enter a new code here, then press "Write". To verify that the code was changed successfully, press "Read" button again.

  

Branding to operator (SIM lock)

Many operators code their phones, thus disallowing any usage of SIM cards belonging to other operators. If you turn on the phone and it asks you for the code, and when you enter the wrong code, the message "SIM is restricted" or similar is being displayed, that means the phone is locked to certain operator. You can check it with Phoenix. Connect the phone without a SIM card and follow the steps indicated on the figure below. On the left part, the phone is branded, on the right one - it is not. You can decode it either at the masters' or obtain the code via the Internet.

  

Typical errors and limitations

1
Dead phone USB flashing box cannot be ticked - select NO CONNECTION mode.

2
Phoenix cannot identify the phone - choose PC SUITE from phone connections. If that doesn't solve the problem on 64-bit system, try Dead phone USB flashing (via Refurbish or SW Reset) - your phone should be identified instantly during flashing.

3
If you see this error when selecting a product code,

then just check the address C:\Program Files\Nokia\Phoenix\Products\RM- for presence of a firmware. The folder name must be, for example, RM-807 for Nokia 808 PureView. Your RM phone value can be different, but the main thing here is RM-807 and not RM807 or RM 807. This dash (-) is important! Also check presence of VPL file in the firmware!

4
If you cannot install Phoenix, try deleting drivers, install Phoenix first, and then install drivers.

5
WARNING: Asic CMT: NAND status reported bad blocks
This error stands for broken blocks. Though it is not so critical, phone usually works fine in spite of this error.

6
Waiting for communication response: 25
Waiting for communication response: <...>
Waiting for communication response: 1
Error 0x8401F121 communicating to phone.
Unable to verify comm.
Warning: Unable to communicate to product after flashing
Starting to recover the phone
Recovering phone

Such log indicates an error related to the downgraded firmware or incorrectly flashed CFW. In this case, you should verify the integrity of the firmware (or its version). If your phone does not boot up, try to flash it with the original firmware. Only if flashing OFW has not brought the phone back to life, try performing Scandinavia DownGrade (leaked Quality Assurance firmware, search Google for its availability on your phone model and download links), and it will fix even severe brick. But if nothing still comes out, bring the phone to the masters'.

7
If you see "Contact Service" message on the display and recovery via dead flashing mode does not help, usually it is a hint on going to the masters'.

8
If the phone does not turn on after flashing and LOŠ”AL MODE is displayed on the screen, simply reinsert the battery.

9
If a firmware on your phone is unstable, the phone cannot be turned on anymore for unknown reasons, and it can only be brought back to life by constant flashings, then this problem is connected with hardware. There is only one sober solution to this problem - a masters'.

10
Error 0x84009427 communicating to phone. Unable to verify comm.
Warning: Unable to communicate to product after flashing

That means Phoenix cannot reset the phone after flashing. It is highly likely that the problem is in battery to have drained during the flashing process. Therefore, it is always recommended to fully charge the battery before.

11
The flashing failed. Do you like to retry the flashing?
HRESULT 0x8401223f (-2080300481)
Flash: Unable to verify communication with device after flashing has finished.

Remove the battery from the phone and insert it back, then try to turn it on.

12
If your PC is searching for Nokia USB ROM during flashing and cannot find it, not speaking about flashing Generic and Parent drivers, then make sure that Nokia Flashing Cable Driver is really installed on your computer. If so, before starting flashing process, turn off the phone, then open Windows Device Manager and quickly press phone's power button for 1-2 seconds. Meanwhile, 2 devices will appear in the Device Manager: PARENT and GENERIC. If the drivers are not installed from the first time or are installed with an error, press phone's power button a couple more times, until the drivers are installed properly. When the devices involved are detected, you can turn on the phone and go ahead with flashing process.

13
If Phoenix issued an error, log of which ends on
--- Press phone's power button! ---
Connection opened to BootCode successfully
First wait command succeeded.
Close RAW connection!
Failed to send config request!
Unable to set the phone to flash mode. Unable to flash.

or
Erasing User Data Area...
FUR: ALGO reported error in Control Frame. Unable to continue.
ERROR: Programming error reported for asic CMT
--- Error Type 0x02
--- Error Specifier 0x12
--- Offending Addr 0xFFFFFFFF
--- Expected content 0x0000FFFF
--- Detected content 0xFFFFFFFF
User Data Area erasing failed
Unable to flash phone 0x8401F173

Make sure that you are using a recommended version of Phoenix. Symbian^3 smartphones (C7-N8 and similar) need to be flashed with Phoenix Service Software 2012.04.003.47798. Nokia 808 PureView is the only exception - you can use both Phoenix Service Software 2012.16.004.48159 (recommended) or 2012.24.000.48366.

14
If Phoenix cannot identify your phone no matter how hard you have tried, then refer to your hardware components. Phoenix is proven to work properly with branded hardware and drivers, such as Intel or Realtek. If your PC has some cheap or rare hardware (especially USB-related), then this might also be the reason of failure regardless the installed OS. In this case, you will have to switch to another PC.

15
After you close Phoenix, it may not restart. To rectify this, use Windows Task Manager to manually shut down phoenix.exe and FuseService.exe processes, or optionally restart your PC.

16
To be able to use the official Phoenix help files in Windows 7 and newer, you need to install Windows Help program (WinHlp32.exe).

17
Even if you have read these text passages with pleasure up to this point, you should still stay in reality and not parallelise all Delight-focused information on other Nokia phone models or recklessly go beyond the scope of this article! Nobody will save you if, for instance, you decide to perform Energy Management Calibration for products using the "Quantum" engine (such as RM-689, RM-702, RM-704 or other product using the same engine). Another example shows that phones using FLS-5 / USB_FBUS connection cannot be serviced in 64-bit operating systems simply because FLS drivers do not support 64-bit OS. As a matter of fact, all non-Delight cases should be handled carefully and the official documentation is supposed to be referred!

18
And the last one, yet important: if you suddenly became a lucky possessor of "Nokia" N8 or whatever of unofficial "Chinese" assembly, and you want to flash Delight on it; then do not even "Phoenix" this "Nokia"! It is not Nokia at all and if you try to flash it with Phoenix, your phone will just "die".

Technical information


Phoenix Service Software 2012.16.004.48159


Main changes and error corrections from previous version:
New product support: RM-807
Product API 2012.14.7
Nokia Connectivity Cable USB Driver version 7.1.78.0
Flash Update Package 2012.11
FUSE Connection Manager version 2012.14
Envira CL 2012.16

Phoenix Service Software 2012.04.003.47798


Main component versions in this release:
Product API 2012.2.2
Nokia Connectivity Cable USB Driver version 7.1.69.0
Flash Update Package 2011.50
FUSE Connection Manager version 2011.51