Hello guys,
I'm trying flash my N9 with Win Flasher and got errors on rootfs.
Something related with "can't remove mount directory..."
I tried everything that is wrote on "Comprehensive Firmware Flashing Guide for N9 " thread and no success.

The error is following:
C:\Flasher>flasher --no-preserve -f -F main2.bin
flasher 3.12.1 (Oct 6 2011) Harmattan
Warning: --no-preserve is not recommended, instead use erase commands
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

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_PR_001
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 84 %, 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 ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[_] cmt-mcusw [init 67 % 4096 / 6050 kB NA ]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 1668 kB/s]
[_] rootfs [init 0 % 21504 / 1170282 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 3518 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 1668 kB/s]
[f] rootfs [init 0 % 23552 / 1170282 kB NA ]
Fetching error list:
========================================
Update content failed to verify against cert: SW certificate not updated
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: Could not find device path under /sys/class/mmc_host/mmc0
mmc: Failed to init mmc block device
scconf_parse_entries failed: (null)
Unable to parse layout
mmc: Could not remove mount directory /tmp/sudmmchFw4aF/mnt: No such file or dir
ectory
mmc: Could not unlink (null): Bad address
[Pipe 4] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

Someone can help me ?

TIA

i think this is related firmware version. but the another problem is mmc. So try first to do : flash only mmc. put here log.

and althoug advicing to do flash operations on the computer under linux os with root privilegies - in some cases this is helping to solve issues related on permissions and security

must to ask - which version is your n9? hope that not china (which is PR Legacy 003)

Hi TonyUkUk, thanks for your reply.

I tried flash only mmc but I got following error:

C:\Flasher>flasher -f -F main2.bin -F emmc.bin --flash-only=mmc
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended 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. 14482 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_PR_001
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image kernel skipped
Image moslo skipped
Image rootfs skipped
Image tar skipped
Image config skipped

Battery level 92 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[_] mmc [init 0 % 32768 / 1463443 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 ]
[f] mmc [init 0 % 32768 / 1463443 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: Could not find device path under /sys/class/mmc_host/mmc0
mmc: Failed to init mmc block device
scconf_parse_entries failed: (null)
Unable to parse layout
mmc: Could not remove mount directory /tmp/sudmmcwECQli/mnt: No such file or dir
ectory
mmc: Could not unlink (null): Bad address
[Pipe 1] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

C:\Flasher>

As your suggestion, I'm flashing using Windows but I tried Linux also, and guess what, no result... same errors.

My phone is legacy 001 - Central Europe Black 16GB.
I tried also flash with a superior legacy (005) but with no success.

So, I really don't know what I can do more. This is why I open this post hoping that you experts on N9 can help me.

Thanks again

Let us know please :



1)answer please first - is your device powering on and booting to OS instead of errors? if yes, go to the settings>reset>cleanup device. Try this (not forgetting fully charging before) and after try to flash again - firmware and mmc.

2)if not help,same errors (put here log),then try to normal flash (-F main.bin -f and then -F main.bin -F emmc.bin -f --flash-only=mmc), no success then try ZEROES flash,then mmc.

3) have you ever flashed your device? exactly this device

a) if yes - was it successsefull?

b) the last successfull flash operation - which was the firmware?

4) if no (never flashed with success),then try with this recurses to do the flash operations(the site is in russian,prefer with chrome to translate into eglish. there are two type of firmwares (with mmc.bin, although there two mmc.bin files -that's mmc files with/without ready downoaded maps) try normal flashing,no success then try with zeroes flash. (in this site you have two options firmware to download, chech them two. I'll prefer to use chrome to translate,because the site in russian)



follow this steps amd dont forget logs. Hope some of this variants will help,because i dont wanr think that this is a phisical damage of your mmc. lets see,hope that the software but not hardware issue.

Your answers:

1) I can power on device but it doesn't boot the OS, it stops in Warning Screen "You changed the software bla bla bla"

2)
C:\Flasher>flasher -f -F main.bin -F emmc.bin --flash-only=mmc
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended 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. 13942 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_PR_001
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image kernel skipped
Image moslo skipped
Image rootfs skipped
Image tar skipped
Image config skipped

Battery level 81 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[_] mmc [init 0 % 29696 / 1463443 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 ]
[f] mmc [init 0 % 31744 / 1463443 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: Could not find device path under /sys/class/mmc_host/mmc0
mmc: Failed to init mmc block device
scconf_parse_entries failed: (null)
Unable to parse layout
mmc: Could not remove mount directory /tmp/sudmmcUQQ7qi/mnt: No such file or dir
ectory
mmc: Could not unlink (null): Bad address
[Pipe 1] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

ZERO FLASH
C:\Flasher>flasher -f -F main.bin --erase-user-data=secure
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

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 82 %, continuing.
Erasing, this may take a while.
ERROR: SU_BEGIN_ERASE_REQ terminated with error code 1: Unknown error
Fetching error list:
========================================
Update content failed to verify against cert: SW certificate not updated
bb5_rdc_cert_read failed
========================================
ERROR: Failed to erase user data using 'secure' method

C:\Flasher>
ZERO FLASH MMC
C:\Flasher>flasher -f -F main.bin -F emmc.bin --flash-only=mmc
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

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_PR_001
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image kernel skipped
Image moslo skipped
Image rootfs skipped
Image tar skipped
Image config skipped

Battery level 82 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[_] mmc [init 0 % 32768 / 1463443 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 ]
[f] mmc [init 0 % 32768 / 1463443 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
mmc: Could not find device path under /sys/class/mmc_host/mmc0
mmc: Failed to init mmc block device
scconf_parse_entries failed: (null)
Unable to parse layout
mmc: Could not remove mount directory /tmp/sudmmcAwP92K/mnt: No such file or dir
ectory
mmc: Could not unlink (null): Bad address
[Pipe 1] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

3) a) Yes, in the past I flashed several times this device and I got no problem at all.

3) b) The last firmware flashed was PR1.3 DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.BIN.

4) I tried all instruction on this Russian site and got no success at all. Always got same error and stops when try to flash mmc.

Just some information about how this happened:
My device runs out of battery during 2 day. When I connected to the wall charger he doesn’t did anything. I wait about 3 hours and nothing, No power on, no led flashing.

After some research on the web, I found a site where they say to make the flashing procedure, and we’ll got an message saying phone has no enough battery, he will charge battery and then starting flash normally, when reached 11%.

So, all of that happen, I got the not enough battery error, started charging battery, when reached 11% flash was started, but I got immediately the MMC error.
Since then, it’s always same story…

Do you think this is a hardware issue?

hmm seems it is partition error. If this, then it must be recreated. Here some howto ,but dont do anything over the 6th step. Howto, follow the post-steps of YakatA (it will be nice i you can use linux on your computer). First read and understand, if you dont understand what you are doing, do not do it yourself. If you want, i can do screencast howto do this.

So, the firmware with which you flashed with success is the firmware that you want flash know - yes?

I hope that it is not hardware issue... We'll do another options first sowtware, check all and then can think about hardware. Hope that not hardware. But, as we see the problem is enough long, if you have there Nokia Care then it will be better to check, because the operations with partition may harm device in hands non-advanced users.

few month ago, i had issue like this, i just checked ONE BY ONE the firmwares with emmc from here and at last have a success - that was too long but i reached to the success. Thats why i hope that in your case, it will not hardware issue,but have some suspect. Lets see.

forget - did you try to cold flash ? Let first do normal flash
look what errors and log here (please,if you can,put the logs with screen photo)
then do it (ofcourse if normal not help)
log here

Thanks for your support.

Normal flash log:
http://postimg.org/image/40hmks4qf/

Cold flash log:
http://postimg.org/image/zac06azgh/
http://postimg.org/image/5wg9qpwqp/

I'll try the rest now...

1)getting my mind to certifications fo device
2)getting mind to hope that this is partition issue
3) in technichan language,this mean that this is hardware issue)) must check these things

Wow...

Do you think Nokia Care can solve this? Or my device is damage forever?

noo,device working. just the problem a little more difficult. You can left message to YakatA or Shturman,CodeRus or to some of these advanced users,what they say.

Why, but i think that if do wright partiton recreating, this maybe solve. But, it will be good to show your device on nokia care, just ask what is the problem - hardware or software, ofcourse if hardware then left device them, if software then here soon will resolve.

Although, here the are some russian commandos for remote help (s.o.s. as you see on the thread). Chrome with translation ofcourse