I am sorry but I do not understand.
If this assumption that you started flashing to charge battery and only after a few minutes you started again and this time the flashing process started. And then you stopped it (how?) then you might have produced a problem.
Try the cold flashing switch '-c'.

I ran the "flasher -i" command,
then I had trouble locating the .bin file in CMD, so I messed with that trouble some time before I could do the "-f -F *image*
Then it already had charged a bit.

Stopped the process with Ctrl + C

Right now I am trying to flash my phone, and I am following this line
that I found in another thread:


flasher -F main.bin -F emmc.bin --erase-user-data=secure --erase-mmc=secure --no-preserve -f -R

But what should I write as emmc.bin when there is nothing on the phone?

This is the errors I get

Image mmc not present
Image tar skipped
Image config skipped

Battery level 54 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[ ] cmt-2nd [pending 0 % 0 / 0 kB NA ]
[ ] cmt-algo [pending 0 % 0 / 0 kB NA ]
[ ] cmt-mcusw [pending 0 % 0 / 0 kB NA ]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[ ] kernel [pending 0 % 0 / 0 kB NA ]
[ ] rootfs [pending 0 % 0 / 0 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 ]
[_] cmt-mcusw [finishing 0 % 6050 / 6050 kB 3381 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 1953 kB/s]
[f] rootfs [pending 0 % 1024 / 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 ]
[f] cmt-mcusw [finishing 0 % 6050 / 6050 kB 3381 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 1953 kB/s]
[f] rootfs [pending 0 % 1024 / 1170282 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
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
mmc: sfdisk returned status 1
mmc: Could not remove mount directory /tmp/sudmmccYoyLH/mnt: No such file or directory
[Pipe 4] Finishing in error state with status 1
MTC_NOS_READY not received
MTC_NOS_READY not received
MTC_NOS_READY not received
CMT RFS failed
[Pipe 7] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

I know very well how to flash but I am not a Nokia engineer knowing all those error messages.
Please follow also all sub links in
https://talk.maemo.org/showpost.php?...01&postcount=9
for a possible answer

But I have no idea what you wanted to achieve? Simply charging by flasher:
'flasher -i'
is enough.
Now you started flashing firmware and interrupted. Definitely not a good idea, a NoGo.
Is this a chinese phone?

Why did you not try my advice with parameter '-c'?

And flasher throws a big warning when started, did you read that?
I propose you read a bit more about flashing process in wiki and/or itsnotabigtruck flashing thread.
And give more info what device, aims, actions, output.

btw: emmc.bin is a synonym for a file containing the contents of the 'hard disk'. You do not really need it but it can be fetched from the net as well as the firmware files.

Slightly off topic:

I am not using my N9 anymore, but it has installed Ubiboot with NitDroid as seconday rom. However it has the problem that it doesn't charge if its off.

How to remove completely NitDroid and Ubiboot without loosing the data on MeeGo and restoring the battery charge when powered off?

To just remove ubiboot without wiping the device is very easy.
All you need to do is flash a regular kernel to the device to replace the ubiboot kernel and you are done

If you have just Nitdroid and no Nemo on your device it is easy to reclaim the space used by Nitdroid after you boot to normal Harmattan; just remove the directory containing the Android subsytem and that's it.
If you hsve also Nemo/Sailfish/Ubunti/Firefox/whatever it is a bit more difficult since that means your device has been repartitioned accordingly.
That's doable too, but requires a bit more expertise.

@Gamerouge Best guess is the flash memory of device have gone bad, Not much to do about it.

@claustn

You could try
flasher -i
trick.
Or just connect/disconnect a few times to give battery a bit of charge to load at least the second kernel and start (with charging). That is how I revivdd my N9s when emptied via Nitdroid.

Thanks for your answer.
I simply followed the thread about the dead battery, and assumed I would see the battery precente rising if I used the -f -F command as well.

This is an european device, 16gb cyan.

Would you mind writing out the whole line for a cold flashing?

I know I made some mistakes.

Best regards