1 Device
Connect the living phone to PC, select sync and connect - it should reboot into flash mode. Else, power the phone off completely, hold the Volume Up key and plug in the USB cable. A white/blue LED should light up: the phone is now in flashing mode and does not show anything on the screen. Connecting first lets the tool pick the image variants that match your exact product code and hardware revision.
2 Firmware images
Add one or more files. A typical N9 flash uses two: the main firmware
(DFL61_HARMATTAN_…_ARM.bin) and the eMMC/VARIANT image
(…_EMMC_….bin). A firmware file usually holds one variant of
each image per product code and hardware revision — only the ones matching the
connected phone are picked, exactly like the original flasher does. Everything ticked
is written in a single update session.
| Image | Version | Product / HW rev | From | Size |
|---|
3 Options
4 Flash
Log
Notes & troubleshooting
-
Linux: the kernel binds
cdc_phonetto the flashing interface, which prevents the browser from claiming it. Runsudo modprobe -r cdc_phonet(and blacklist it) before connecting, and make sure your user may access the device, e.g.SUBSYSTEM=="usb", ATTR{idVendor}=="0421", MODE="0666"in/etc/udev/rules.d/51-nokia.rules. - Windows: bind the WinUSB driver to the Nokia flashing interface with Zadig, otherwise WebUSB cannot open the device.
- Flashing writes directly to the phone's storage. A failed rootfs write leaves the phone unbootable but recoverable — simply flash again. Do not unplug the cable while the progress bar is moving.
-
Cold flashing (a phone whose bootloader is gone, showing up as an OMAP boot ROM device
0451:d00e) is not implemented here; use the originalflasher --cold-flashfor that.