How To Hard Reset The N900 To The Factory State

As I have mentioned before, unlike Nokia’s Symbian devices, the N900 does not have a code that you can enter to format the device and restore it to the factory state. However, if you like playing with software in the extras-devel repositories, chances are that sooner or later you will like a fresh start and want the N900 to be restored to the state in which you first picked it up.

How To Hard Reset The N900 To The Factory State

There is no seemingly easy way to do this and I really hope Nokia is doing something about it. That being said, how do you go about accomplishing the task? The answer is to flash both the N900’s OS and the 32 GB mass memory. This can be done on a Mac, a Linux or a Windows machine. Since windows is the most popular OS, I will show you how to do this via Windows.

Before we start, please note that this would be done using the command line interface, it may seem tricky but let me assure you that it is simply enough for anyone to accomplish.

  • Download and install the latest version of Maemo Flasher (e.g. maemo_flasher-3.5_2.5.2.2.exe). Since this is a command line application you will see no shortcut on the desktop or in the Program Files option under the Start menu.
  • Next, Download the latest firmware (.bin) file, it will look like “RX-51_xxxxx_ARM.bin”. You will need your IMEI  number to access the downloads, it can be found on the box or by going to Settings > General > About Product.
  • Also download the Vanilla eMMC image (.bin file) from the same page. It will look like “RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM.bin”
  • Save both  to C:\ProgramFiles\maemo\flasher-3.5\. My suggestion is to rename them to something simple such as RX-51.bin for the firmware and R.bin for the eMMC, this will make typing the commands easier later on.
  • Make sure that the battery is fully charged and switch off the device.
  • Open the Command Prompt by going to Start then Run and type cmd, then press Enter.
  • Change directory to the flasher’s program path by entering:
cd "C:\ProgramFiles\maemo\flasher-3.5"
  • Connect the USB cable while holding the ‘u’ key on the N900. Within an instant you will see a USB icon on the top right corner of the N900. Now leave the ‘u’ key.
  • Run the following command:
flasher-3.5.exe -F RX-51.bin -f -R
  • I typed RX-51.bin because I had renamed the file earlier, otherwise it would have been: (this was the name of the latest firmware, the name may vary after a new firmware comes out)
flasher-3.5.exe -F RX-51_2009SE_2.2009.51-1_PR_COMBINED_MR0_ARM.bin -f -R"
  • You will see text similar to the one below on your PC.

How To Hard Reset The N900How To Hard Reset The N900

  • The update will take about 3 minutes after which the N900 will reboot and display the Welcome screen with Regional settings.

The next step is to flash the Mass Storage or the eMMC. The first few steps are identical to the way you would flash the firmware. If you are following on from the above and already have the command prompt open, you can directly proceed to step number 3.

  • Open the Command Prompt by going to Start then Run and type cmd, then press Enter.
  • Change directory to the flasher’s program path by entering:
cd "C:\ProgramFiles\maemo\flasher-3.5"
  • Connect the USB cable while holding the ‘u’ key on the N900. Within an instant you will see a USB icon on the top right corner of the N900. Now leave the ‘u’ key.
  • Execute the following command:

flasher-3.5.exe -F R.bin -f -R"
  • I typed R.bin because I had renamed the file earlier, otherwise it would have been

flasher-3.5.exe -F RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM.bin -f -R
  • You will see text similar to the one below on your PC.
How To Hard Reset The N900
  • The flash will take around 1 minute after which the device will reboot.
  • The bright Nokia screen will come up on the screen with the USB icon on the top right followed by progression dots with yellow LED blinking for a few seconds. The device will then turn off and go into charging mode with the yellow LED blinking (NOTE: If the device appears to reboot, unplug the cable.)
  • Unplug cable and wait for device to turn off completely. You may hear a sound (punk) of the device turning off.

That’s it. You have now hard reset the N900 to the factory state. This procedure can be used to update the firmware on your device as well, if you wish you can leave formatting the eMMC if your intention is only to update the firmware. Please make sure that the battery on your N900 is completely charged, otherwise you might brick it.

This guide has been adapted from this immensely useful wiki on maemo.org.

Disclaimer: Please do this at your own risk.

92 thoughts on “How To Hard Reset The N900 To The Factory State”

  1. Mughalgxt; I did this procedure as indicated, but I missed your comments, so I did flash the firmware first and then I tried to flash the eMMC, but I keep getting the a massege saying that the usb port is not found. Is there any other way to flash the eMMS ?

    Thanks

  2. The Maemo Development Environment Downloads seems to be down???? why is that??? i was interested in flashing my N900 because the screen calibration utility will not work any more. (when i push the 1st ex it closes down) i have rebooted many times.

    Every thing else seems to be working fine. I did install a zagg invisible shield last night. and you have to use this soapy water solution to install it. Could that soapy water have damaged my N900????

    Has any one else had of heard or know the remedy to my screen calibration issue???

    please help. thank you

  3. I have downloaded and installed flasher 3.5 on windows XP.. I have downloaded and copied the latest firmware and copied it to the flasher directory.

    I run the mobile on Flasher mode and I can see the USB icon on top right corner with Nokia written in centre of screen

    When I give the command as specified in directory, it gives %m.. I dont know whts is that?? Following is the copy of commands and response from command prompt of Win Xp

    D:\Program Files\maemo\flasher-3.5>flasher-3.5 -F RX-51_2009SE_3.2010.02-8.003_P
    R_COMBINED_003_ARM.bin -f -R
    flasher v2.5.2 (Sep 24 2009)

    RX-51_2009SE_3.2010.02-8.003_PR_COMBINED_003_ARM.bin: %m

    D:\Program Files\maemo\flasher-3.5>flasher-3.5 -F RX-51_2009SE_3.2010.02-8.003_P
    R_COMBINED_003_ARM -f -R
    flasher v2.5.2 (Sep 24 2009)

    RX-51_2009SE_3.2010.02-8.003_PR_COMBINED_003_ARM: %m

    D:\Program Files\maemo\flasher-3.5>

    It does not flash but gives %m.. What does it means.>?????? And what to do now??

  4. Ammad i had the same problem an could not figgure out where i had gone wrong but in a last ditch attempt i moved
    RX-51_2009SE_3.2010.02-8.003_PR_COMBINED_003_ARM.bin
    RX-51_2009SE_1.2009.41-1.VANILLA_PR_EMMC_MR0_ARM.bin
    into the same directory as the flasher tool C:\Program Files\maemo\flasher-3.5 (u might of saved it somewhere else) an that solved the RX-51_2009SE_3.2010.02-8.003_PR_COMBINED_003_ARM.bin: %m problem! an it worked like a charm 😀 hope that helps you out!!

  5. you know just by clicking Tab key when in the command prompt it will choose the different files in the folder, so you don’t have to rename the files.

  6. Ok, so I began to try to flash the eMMC first, and I followed the steps to the “T” but this is what I get every time. It never gets past the “Suitable USB device not found, waiting.” I even tried flashing the firmware first, but got the same result. I already installed the flasher-3.5 and made it install to my C: Drive in program files, but not under the (x86) 64bit program files folder. I am running windows 7 64 bit. Maybe that is my problem……I’m not sure. I know that it says only XP and Vista, but 7 has been out for a little bit now, so I assumed having windows 7 wouldn’t make a difference. Can anyone point me in the right direction. I appreciate any help I can get. Thanks.

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\Vegito168>cd “C:\Program Files\maemo\flasher-3.5″

    C:\Program Files\maemo\flasher-3.5>flasher-3.5.exe -F R_EMMC.bin -f -R”
    flasher v2.5.2 (Sep 24 2009)

    Image ‘mmc’, size 241163 kB
    Version RX-51_2009SE_1.2009.41-1.VANILLA
    Suitable USB device not found, waiting.

  7. ” MUGHALGXT said:

    Bro…. very important FIRST FLASH eMMC and THAN Firmware not the other way round!”

    Is this true? Cause in the description it is written the other way around, right?

  8. i did everything in the order it was described in the manual (firmare and then eMMC) and it works, but it’s slow as fuck. Does any1 know what to do?

  9. Hello ,

    Ammad + burnzie.85 ,,,

    i have the same problem , and i am using win xp , and i followed all the steps and i checked more than once , and i found everything is ok but still it doesnt work ! it keeps sending me this

    flasher v2.5.2 (sep 24 2009)

    RX-51_2009SE_3.2010.02-8.003_PR_F5_003_ARM.bin-f: %m

    !!! , i dont know what does it mean , it’s weird , i am sure that i installed all required files and i checked in the folder , all files are in their right place ! . i sent many times asking for help but no answers unfortnately ,

    this n900 is great device , but it has many problems (incorrect number) one of the worst problems in this device , i loved this phone but what should i do now if i can not use it ! , sometimes i think to sell it and buy something else , sometimes i think to wait ! . if anyone can help , thank you in advance .

  10. helo i m from INDIA. My N900 OS was curupt last night when i instol kernal power flasher via xterminal. My big mistake after instolation i boot via xterminal then my phone not started yet. When switch on show NOKIA and switch OFF automaticlly i think OS not responcs to starting hanset. Now bettry totally empty. I m not able to flshe without flesher mood reason batry empty. I will any body have solution for this ?????? Help.

  11. Hello berison, I think you should chang path of desair file with ( cd “C:\ProgramFiles\maemo\flasher-3.5″ ) after run comand like ( flasher-3.5.exe -F RX-51_2009SE_2.2009.51-1_PR_COMBINED_MR0_ARM.bin -f -R” )

  12. dear kapun364 ,

    thanks a lot for your reply , i appreciate it , i think there’s something wrong or some mistale i did but i dont know where is it and i dont know how i can fix it exactly , so i need detailed explanation please …..

    let’s see what i did …

    i downloaded these 2 files after i downloaded the flasher

    RX-51_2009SE_3[1].2010.02-8.003_PR_COMBINED_003_ARM
    RX-51_2009SE_1[1].2009.41-1.VANILLA_PR_EMMC_MR0_ARM

    when i open maemo folder in the c drive , i see the flasher and i see the 2 files BUT their type is : bin , should they be exe ? , if they should be exe type , then how i can convert them from bin type to exe type ? .

    thanks in advance for reply

  13. dears ,

    finally my problem solved , and i want to tell everyone face a problem while flashing the device , please make sure that you write the exact file name , because i missed the right file name , so it didnt work in the beginning , finally it worked ! . thanks a lot .

    * special thanks to :

    kapun364

  14. Good article.

    Anyway there is something important that is wrong. You have to drop the -R from the flash firmware command. This way the device wont auto reboot after the flash and will give you a chance to flash the mmc. If the device reboots the things may get ugly.

  15. Excelent, one tip !!!

    for windows 7 user, first reboot your PC, press F8, select option “Turn off signed drivers”….is ready for flash.

  16. Hi,
    I am on windows 7, I disabled the driver verification enforcement. Everytime I type “flasher3.5.exe -f RX51.bin -f -R” it says:
    Suitable USB device not found..Waiting..
    Note: when I hold the U key and plug the USB, the USB sign and the nokia sign appears on the screen but the screen light appears to be turned off or something. In other words, the screen is all black but the nokia sign and the USB sign appears faded.
    what should I do?

  17. hi!! can u provide a step by step procedure on how to flash the device with a mac? sorry im not so techy but i will surely be able to follow u. 🙂

  18. Awesome! Just to second what has previously been corrected, I had to do the eMMC first followed by the firmware. Worked like a charm! My wife thinks I am nuts for doing a manual upgrade for something I would get tomorrow with less effort. There is no place in geekdom for slouchers.

  19. berisun ,

    Use : RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin , this is the latest version, give it a shot .

  20. Very clearly stated in the page: http://tablets-dev.nokia.com/nokia_N900.php

    NOTE: Always flash the FIASCO image first, then the eMMC image immediately after that. Never boot up the device between flashing the FIASCO image and the eMMC image!

    First update firmware with:
    cd “C:\ProgramFiles\maemo\flasher-3.5”
    then
    flasher-3.5.exe -F RX-51_2009SE_10.2010.19-1_PR_COMBINED_MR0_ARM.bin -f

    Don’t use the -R option if u intend to flash eMMC, -R will reboot the device.

    after updating the firmware update eMMC:
    flasher-3.5.exe -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin -f -R

    now u can use the -R option for rebooting the device after the update.

  21. After a flashing attempt my device displays “Missing Image. Is there a way to recover it? Does not respond to pressing -u and plugging the usb.

  22. I figured out how to start up in USB mode and I flashed the 1.2 image onto the phone. I turned it off afterward and did the eMMC flash. When I turn the phone on, all i get is squares. No image whatsoever. I used Win 73/2

  23. I actually figured it out. I did it with no -R between the flash processes. Thank to a comment above 😀

  24. Hi Everybody
    I am in UK, i received Nokia N900 from Neilsen for free for research purpose. Like everybody i was waiting for New firmware, i have been trying to update through Nokia Software Updater (Nokia PC Suite) but there was something wrong either with network or server, i couldnt manage to download, i followed the same instruction as mention above and it worked for me. I have just done it.
    i have also included the output of command prompt so you can have a look how i did it. I didn’t include -R in 1st command to install firmware but used in second time to restart mobile after flashing eMMC.
    After disconnecting my device from computer, it took atleast 1 minute or so to start. even if your mobile doesn’t start you can start it manually.
    ALL THIS INFORMATION IS OUTPUT THAT WORKED FOR ME, PLEASE TRY IT ONLY IF YOU KNOW WHAT YOU ARE DOING ITS NOT DIFFICULT AT ALL. AT YOUR OWN RISK PLEASE.

    So far its working properly, i will restore my backup in a minute and come back to confirm if everything is as smooth as it was before installing or anything else.

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Program Files\maemo\flasher-3.5>dir
    Volume in drive C has no label.
    Volume Serial Number is 2065-CC48

    Directory of C:\Program Files\maemo\flasher-3.5

    26/05/2010 16:09 .
    26/05/2010 16:09 ..
    21/10/2009 13:04 135,539 flasher-3.5.exe
    21/10/2009 18:13 4,642 Help.txt
    26/05/2010 14:20 licenses
    26/05/2010 14:37 246,951,288 R.bin
    21/10/2009 18:12 6,690 Readme_Maemo_Flasher-3.5.txt
    26/05/2010 14:17 187,852,801 RX-51.bin
    26/05/2010 14:20 2,974 unins000.dat
    26/05/2010 14:20 707,418 unins000.exe
    7 File(s) 435,661,352 bytes
    3 Dir(s) 88,885,653,504 bytes free

    C:\Program Files\maemo\flasher-3.5>flasher-3.5.exe -F RX-51.bin -f
    flasher v2.5.2 (Sep 24 2009)

    SW version in image: RX-51_2009SE_10.2010.19-1.203.1_PR_203
    Image ‘kernel’, size 1705 kB
    Version 2.6.28-20101501+0m5
    Image ‘rootfs’, size 173696 kB
    Version RX-51_2009SE_10.2010.19-1.203.1_PR_203
    Image ‘cmt-2nd’, size 81408 bytes
    Version BB5_09.36
    Image ‘cmt-algo’, size 519808 bytes
    Version BB5_09.36
    Image ‘cmt-mcusw’, size 5826 kB
    Version rx51_ICPR82_10w08
    Image ‘2nd’, size 14720 bytes
    Valid for RX-51: 2217, 2218, 2219, 2220, 2120
    Version 1.4.14.8+0m5
    Image ‘xloader’, size 14848 bytes
    Valid for RX-51: 2217, 2218, 2219, 2220, 2120
    Version 1.4.14.8+0m5
    Image ‘secondary’, size 109440 bytes
    Valid for RX-51: 2217, 2218, 2219, 2220, 2120
    Version 1.4.14.8+0m5
    Image ‘2nd’, size 14720 bytes
    Valid for RX-51: 2101, 2102, 2103
    Version 1.4.14.8+0m5
    Image ‘xloader’, size 14848 bytes
    Valid for RX-51: 2101, 2102, 2103
    Version 1.4.14.8+0m5
    Image ‘secondary’, size 109440 bytes
    Valid for RX-51: 2101, 2102, 2103
    Version 1.4.14.8+0m5
    Image ‘2nd’, size 14848 bytes
    Valid for RX-51: 2307, 2308, 2309, 2310
    Version 1.4.14.8+0m5
    Image ‘xloader’, size 14848 bytes
    Valid for RX-51: 2307, 2308, 2309, 2310
    Version 1.4.14.8+0m5
    Image ‘secondary’, size 109440 bytes
    Valid for RX-51: 2307, 2308, 2309, 2310
    Version 1.4.14.8+0m5
    Image ‘2nd’, size 14848 bytes
    Valid for RX-51: 2407, 2408, 2409, 2410
    Version 1.4.14.8+0m5
    Image ‘xloader’, size 14848 bytes
    Valid for RX-51: 2407, 2408, 2409, 2410
    Version 1.4.14.8+0m5
    Image ‘secondary’, size 109440 bytes
    Valid for RX-51: 2407, 2408, 2409, 2410
    Version 1.4.14.8+0m5
    Image ‘2nd’, size 14848 bytes
    Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
    Version 1.4.14.8+0m5
    Image ‘xloader’, size 14848 bytes
    Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
    Version 1.4.14.8+0m5
    Image ‘secondary’, size 109440 bytes
    Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
    Version 1.4.14.8+0m5
    Image ‘2nd’, size 14848 bytes
    Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
    Version 1.4.14.8+0m5
    Image ‘xloader’, size 14848 bytes
    Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
    Version 1.4.14.8+0m5
    Image ‘secondary’, size 109440 bytes
    Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
    Version 1.4.14.8+0m5
    Image ‘2nd’, size 14720 bytes
    Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
    113, 2114, 2115, 2116, 2117, 2118, 2119
    Version 1.4.14.8+0m5
    Image ‘xloader’, size 14848 bytes
    Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
    113, 2114, 2115, 2116, 2117, 2118, 2119
    Version 1.4.14.8+0m5
    Image ‘secondary’, size 109440 bytes
    Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
    113, 2114, 2115, 2116, 2117, 2118, 2119
    Version 1.4.14.8+0m5
    Image ‘2nd’, size 14848 bytes
    Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
    Version 1.4.14.8+0m5
    Image ‘xloader’, size 14848 bytes
    Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
    Version 1.4.14.8+0m5
    Image ‘secondary’, size 109440 bytes
    Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
    Version 1.4.14.8+0m5
    Image ‘2nd’, size 14848 bytes
    Valid for RX-51: 2607, 2608, 2609, 2610
    Version 1.4.14.8+0m5
    Image ‘xloader’, size 14848 bytes
    Valid for RX-51: 2607, 2608, 2609, 2610
    Version 1.4.14.8+0m5
    Image ‘secondary’, size 109440 bytes
    Valid for RX-51: 2607, 2608, 2609, 2610
    Version 1.4.14.8+0m5
    Image ‘2nd’, size 14848 bytes
    Valid for RX-51: 2507, 2508, 2509, 2510
    Version 1.4.14.8+0m5
    Image ‘xloader’, size 14848 bytes
    Valid for RX-51: 2507, 2508, 2509, 2510
    Version 1.4.14.8+0m5
    Image ‘secondary’, size 109440 bytes
    Valid for RX-51: 2507, 2508, 2509, 2510
    Version 1.4.14.8+0m5
    Image ‘2nd’, size 14720 bytes
    Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
    210, 2211, 2212, 2213, 2214, 2215, 2216
    Version 1.4.14.8+0m5
    Image ‘xloader’, size 14848 bytes
    Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
    210, 2211, 2212, 2213, 2214, 2215, 2216
    Version 1.4.14.8+0m5
    Image ‘secondary’, size 109440 bytes
    Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
    210, 2211, 2212, 2213, 2214, 2215, 2216
    Version 1.4.14.8+0m5
    Image ‘2nd’, size 14848 bytes
    Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
    Version 1.4.14.8+0m5
    Image ‘xloader’, size 14848 bytes
    Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
    Version 1.4.14.8+0m5
    Image ‘secondary’, size 109440 bytes
    Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
    Version 1.4.14.8+0m5
    USB device found found at bus bus-0, device address \\.\libusb0-0003–0x0421-0x0
    105.
    Found device RX-51, hardware revision 2101
    NOLO version 1.4.14
    Version of ‘sw-release’: RX-51_2009SE_3.2010.02-8_PR_MR0
    Sending xloader image (14 kB)…
    100% (14 of 0 kB, avg. 14 kB/s)
    Sending secondary image (106 kB)…
    100% (106 of 0 kB, avg. 106 kB/s)
    Flashing bootloader… done.
    Sending cmt-2nd image (79 kB)…
    100% (79 of 0 kB, avg. 79 kB/s)
    Sending cmt-algo image (507 kB)…
    100% (507 of 0 kB, avg. 507 kB/s)
    Sending cmt-mcusw image (5826 kB)…
    100% (5826 of 0 kB, avg. 5826 kB/s)
    Flashing cmt-mcusw… done.
    Sending kernel image (1705 kB)…
    100% (1705 of 0 kB, avg. 1705 kB/s)
    Flashing kernel… done.
    Sending and flashing rootfs image (173696 kB)…
    100% (173696 of 0 kB, avg. 173696 kB/s)
    Finishing flashing… done
    CMT flashed successfully

    C:\Program Files\maemo\flasher-3.5>flasher-3.5.exe -F R.bin -f -R
    flasher v2.5.2 (Sep 24 2009)

    Image ‘mmc’, size 241163 kB
    Version RX-51_2009SE_1.2009.41-1.VANILLA
    USB device found found at bus bus-0, device address \\.\libusb0-0003–0x0421-0x0
    105.
    Found device RX-51, hardware revision 2101
    NOLO version 1.4.14
    Version of ‘sw-release’: RX-51_2009SE_10.2010.19-1.203.1_PR_203
    Booting device into flash mode.
    Suitable USB device not found, waiting.
    USB device found found at bus bus-0, device address \\.\libusb0-0003–0x0421-0x0
    1c8.
    Raw data transfer EP found at EP2.
    Image(s) flashed successfully in 44.312 s (5442 kB/s)!

    C:\Program Files\maemo\flasher-3.5>

  25. Hi

    I have received the PR1.2 update. Successful download and the installs start. After a few minutes the N900 reboots and shows Standard Nokia screen with message ‘Installing Software Updates – Please do not interrupt’. This now continues on and on. The device cannot be powered off – it just continuously reboots. This also prevents me from flashing the device as I understand I need it into the USB mode’
    Any suggestions?

  26. Is any one else requested to use NSU for the FW upgrade? I tried to do the upgrade via the N900, but was told to “Use the PC and USB connect the N900 to obtain the 1.2 FW upgrade” – OTA is much easier ! But doing so, and now tried it from 3 (!) Laptops, it stops the download in NSU at 33.6 mb (out of apx 187 mb)

    Any good ideas why, and how to move on….I am a little bit afraid of the whole “home flashing” stunt 🙂

  27. @Birger just let it be it will stop. Make long press for the power off button. Just follow what robin wrote above. It will not damage the device easily if you don’t disconnect the process in flashing. Just relax and make the flash for image/firmware without the -R(or the reboot) then flash the emmc. But be sure to backup or copy the backup file(or all file) in your pc.

  28. The web-page where the images are located mentions

    NOTE: Always flash the FIASCO image first, then the eMMC image immediately after that. Never boot up the device between flashing the FIASCO image and the eMMC image!

    So, I went ahead and flashed the “COMBINED” image. But to my (BAD?) luck, the phone automatically rebooted and then when I flashed the eMMC and rebooted, all the screen displayed was jibberish! I tried restarting a few times without success.

    Then, I went ahead and re-flashed the 1st image again.. and this time the phone booted up correctly and everything seems to be fine!!!
    hhhhuuufff!

  29. When i hold the U key while plugging in my USB cable i get the message:

    Connected to USB device
    Current State: Charging only
    Mass Storage Mode
    PC Suite Mode

    I cant get it to show me the USB icon in the top right corent as per the instructions. What am i doing wrong?

  30. RX-51_2009SE_10.2010.19-1_PR_COMBINED_MR0_ARM.bin
    izzit this firmware suite my n900 version 3.2010.02-8.207?

  31. pls i don know what to do anymo about this %m problem when am running command to flash. am sure d files are in the folder where they are supposed to but i still get this %m and it wont flash. pls somebody help me….dont know what to do anymo.

  32. %m fleshing error with maemo flasher3.5 %m %m %m %m %m %m %m SOLUTION………
    Open any random folder in windows. in that window, press alt, click tools and folder options. on the view tab, untick the box next to ‘hide file extensions for known file types’

    then go into the folder with the image files, and rename the image file to os.bin so we can make sure youve got the correct file name this time. and make sure its in the same folder as flasher-3.5.exe, not in some other folder within the folder.

    then run command prompt, go into the flasher folder, type in the following

    flasher-3.5.exe -F os.bin -f

    then connect your n900 in the update mode.

  33. this message appears after doing the steps

    ” suitable USB device not found, waiting. ”

    please help me and really appreaciated

  34. i got the same problem as Isless200045

    ” suitable USB device not found, waiting. ”

    i waited 1hr still the same.im using window xp ferrari 1000.
    anyone pls help me

  35. TTTHHHHAAANNNNKKKSSSS in a million dude, you saved my phone. The way you descriped how to do it is GREAT. Again thanks in a million.

Comments are closed.