Basically the result is more or less the same..

juha-R530-R730 Downloads # sudo flasher -f -F main.bin -F emmc.bin --erase-user-data=secure -c
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Using 1st image to detect HW
Suitable USB interface (bootrom) not found, waiting...
USB device found at bus 002, device address 086.
Device identifier: (null) (SN: N/A)
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 36 30 07 07 13 02 01 00 12 15 01 18
47 35 43 69 fe 08 e3 d3 3e 4c 21 a3 d8 7b b1 7c
76 5c e7 14 15 01 12 dd 2f 66 d4 55 fe 19 2c 62
b9 b8 e2 65 0a fc 1d 9f 3f 90 15 09 01 13 bf 3e
ef 15 52 e7 03
HW variant: HS
Found matching 1st (916)
Sending 1st image (26496 bytes)... done.
Sending HWID query... Received 11 bytes from 1st
Got HWID: RM-696:1603
Suitable USB interface (bootrom) not found, waiting...
USB device found at bus 002, device address 087.
Device identifier: (null) (SN: N/A)
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 36 30 07 07 13 02 01 00 12 15 01 18
47 35 43 69 fe 08 e3 d3 3e 4c 21 a3 d8 7b b1 7c
76 5c e7 14 15 01 12 dd 2f 66 d4 55 fe 19 2c 62
b9 b8 e2 65 0a fc 1d 9f 3f 90 15 09 01 13 bf 3e
ef 15 52 e7 03
Sending 2nd image (26112 bytes)... done.
Sending ping... pong.
Sending ape-algo (7266816 bytes)... done.
Suitable USB interface (bootloader/phonet) not found, waiting...
USB device found at bus 002, device address 088.
Device identifier: 357923041979909 (SN: N/A)
Raw data transfer EP found at EP2.
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 100 %, continuing.
Erasing, this may take a while.
Erase done.
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_001
Image moslo not present
Image tar skipped
Image config skipped

Battery level 94 %, 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 ]
[ ] mmc [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 ]
[x] cmt-mcusw [finished 100 % 6050 / 6050 kB 3012 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 3706 kB/s]
[f] rootfs [pending 0 % 1024 / 1170282 kB NA ]
[-] mmc [pending 0 % 0 / 0 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: sfdisk returned status 1
mmc: Could not exec 'tune2fs -L rootfs /tmp/sudmmcWiPfCt/internal0p2'
mmc: Could not remove mount directory /tmp/sudmmcWiPfCt/mnt: No such file or directory
[Pipe 4] Finishing in error state with status 1
========================================

ERROR: Failed to flash images
juha-R530-R730 Downloads # sudo flasher -R
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

USB device found at bus 002, device address 088.
Device identifier: 357923041979909 (SN: N/A)
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1603
Server implements softupd protocol version 1.8
Success

How can i look at my /tmp/ while flashing? With another terminal screen? What command?

You cannot, since it is inside the N9 device, it does not refer to the "/tmp" in your linux PC
Same with the sfdisk and tune2fs it is referring, those processes run in the device flasher environment.
(When the flasher starts, it pushes a specific binary called "APE Algorithm" to the device and boots it. The APE is actually a full mini-linux distro running off a ramdisk inside the device, and it contains the tools to prepare and flash the device...)

Now, your device is running DFL61_HARMATTAN_40.2012.21-3_PR_001 Which is the PR1.3 Norteherneurope variant, used in Finland for example.
I happen to have the correct binaries, and I can say that your MD5SUM's match the files I have exactly, which means you do not have a corrupted binary.

You should be totally OK flashing those binaries to your device, no downgrade issues, no corruption issues, nada.

From this I can only draw one conclusion; the flash memory in your device is bad on some location and there is not enough free eraseblocks to cycle in to fix the problems. Too bad

As it seems, you are not able to install Harmattan on your device. However, unless I am mistaken when I look at your flashing logs, you are able to flash kernel which means your MTD is not bad.
It might well be possible to install Nemo or SailfishOS on your device still. (Harmattan is the tricky one because it has all the protection stuff built in, other OS'es are always easier to install)

Yep, seems like 'broken' flash.

As juiceme said you might be able to run other OSes or:
it just came to my mind, it might not work at all but I would try...
As the log says it has problems with p2 which is rootfs. But before that is p1 (MyDocs). So in the N900 there was the possibility to hexedit the firmware file to modify the size of p1. So possibly there is a chance to resize MyDocs (decrease 6GB, rootfs 4, opt 2) and flash with --no-preserve???

@juiceme, whatdoyouthink?

OK, Thanks.

This was really helpful. I'll try to flash only the kernel and then install Sailfish. I'll get back here if i have problems that i can't find solutions otherwise and then you can tell me that my N9 is completely broken.

Oh, didn't notice this message before i wrote the last one. If I decrease the memory on my phone, will I have any space left for programs, pictures, etc. anymore?

Also. Don't actually have a clue how to do this. Allthough i somewhat understand the basic idea.

Thanks.

I installed Bless, made a copy of the main.bin and opened it with Bless. Just don't know what to look for.

Regarding the resizing of partitions to go around the damaged flash area, yes pretty neat idea indeed!

It might be doable, but there is a catch; I am almost sure that when flashing the device if the APE detects that the partition layout is not what it thinks as "correct" it will forcibly repartition the device.
A safety feature, it is.

Now; there is a way around it but it requires some tweaking, and also help from somebody who can get you the "fresh" uninitialized images as tarfiles for example. (it might be also possible to prepare these from the firmware and emmc binaries but I have not tried that)

So the procedure would be something like that:

• boot the device into ubiboot maintanance mode
• partition it to your liking, for example so that your root and home are partitions 1 and 2, and Mydocs is partition 3
• copy the fresh tarfiles to partitions
• modify your /etc/fstab to point to correct partitions
• enjoy

The procedure to get "fresh" tarfiles; Somebody who has a device with same country variant flashes her device clean, and then before the device boots up flashes it to ubiboot maintanance mode and creates tarfiles from partitions.

Rationale why this works; When an N9 device is flashed clean, the actual device localization and initialization happens at first boot. If the first boot is intercepted by booting the device into maintanance mode the partitions contain the filesystem in such a state it can be copied to any device where it will work correctly when the device boots.

Well it is not easy to edit the image files directly; as the contents are checksummed the flasher will refuse to flash them if mucked about.

You can use the N900 flasher v2.5.2 to extract the contents from the binaries. (the extracting option was removed from the N9 flasher v3.12.1)

Okay, this is getting a little too science fiction for me to understand. I might be able to extract but then what? I certainly can't get my hands on another device.