On eMMC flashing, the N900 should boot from USB flash mode into eMMC flash mode (running dots). Did this happen? If so, try restarting the flasher in this mode.

Also, did your device drop lately? This caused a broken electrical eMMC connection on my device and made flashing the eMMC impossible.

have you seen this part?

no it didnt go into emmc flash mode(runnin dots).there was just a vibration and i could see da nokia writen faintly

to windows7
have you seen this part? ....
well i first tried and failed.tats wat i told u i got stuck while flashin emmc...

if you have windows 7,vista 64 bit or xp sp1-2 then just forget it

i had the same problem before. if your pc is sp1 or 2, then you will have to upgrade to sp3. and install nokia pc suite and make sure its running so you have all the usb drivers needed. after i did those my emmc flashed successfully. it was actually atilla who gave me the advise. goodluck!

i tried to hard reste of my n900 today and successfully flash firmware then tried to flash emmc but could not do it!!!

here is detial..i typed in flasher
"flasher-3.5 -F RX-51_2009SE_20.2010.36-2.004_PR_COMBINED_004_ARM.bin -f" successfully flashed

and then i type for emmc
"flasher-3.5 -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin -f -R" but it does not start flashing!! it gives me this....

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

C:\Program Files\maemo\flasher-3.5>flasher-3.5 -F RX-51_2009SE_10.2010.13-2.VANI
LLA_PR_EMMC_MR0_ARM.bin -f -R
flasher v2.5.2 (Sep 24 2009)

Unknown arguments specified!
Usage: flasher [OPTIONS]
Options:
-F, --fiasco=ARG Location of a FIASCO image
-k, --kernel=ARG Location of kernel image
-n, --initfs=ARG Location of initfs image
-r, --rootfs=ARG Location of root JFFS2 image
--cmt-2nd=ARG Location of CMT FIASCO 2nd image
--cmt-algo=ARG Location of CMT FIASCO algorithm image
--cmt-mcusw=ARG Location of CMT FIASCO MCUSW image
--cmt-no-verify Disable verification of CMT programming
-x, --xloader=ARG Location of X-Loader image
-s, --secondary=ARG Location of NOLO secondary bootloader image
-2, --2nd=ARG Location of NOLO cold flasher ("2nd") image
-u, --unpack[=ARG] Unpack a FIASCO image
-f, --flash Load and flash all supplied images
-l, --load Only load all supplied images
-b, --boot[=ARG] Boot the kernel with optional cmdline
-R, --reboot Reboot the board (e.g. after flashing NOLO)
-i, --read-device-id Print out the device type
-S, --serial-port=ARG Serial port used for cold flashing or "usb"
-I, --init-port Only initialize the serial port
-c, --cold-flash "Cold flash" the device
-h, --hw-revision=ARG Specify product code and HW revision
--enable-rd-mode Enable R&D mode on the device
--disable-rd-mode Disable R&D mode on the device
--set-rd-flags[=ARG] Set R&D mode flags on the device
--clear-rd-flags[=ARG] Clear R&D mode flags on the device
--query-rd-mode Query the device R&D mode status and flags
--set-hw-revision[=ARG] Set HW revision override on device
--flash-only=ARG Flash only certain components
-U, --usb-device=ARG Specify USB device to use (bus:device address)

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


the phone is working after a restart ans tried to flash it many times but gets the same even i tried to flash firmware but did not start and gives the same error(both .bin files of firmware and emmc image are in the maemo falsher folder)plz help i did no start a new thead!!!

ok emmc flash after flashing frimware stuck here..............


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

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

Image 'mmc', size 255947 kB
Version RX-51_2009SE_10.2010.13-2.VANILLA
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
105.
Found device RX-51, hardware revision 2204
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_20.2010.36-2.004_PR_004
Booting device into flash mode.
Suitable USB device not found, waiting.
NOTE:- my device booted after firmware
any idea

I have the same problem. Any progress?