does it matter if i put mmc at all

did that here it is

C:\N9>flasher --erase-mmc -F DFL61.bin -f -R
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 1501
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.280.04.1_PR_280
Sending ape-algo image (7103 kB)...
100% (7103 of 7103 kB, avg. 16254 kB/s)
Suitable USB interface (phonet) not found, waiting...
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1501
Server implements softupd protocol version 1.8

Battery level 86 %, continuing.
Erasing, this may take a while.
Erase done.
Image SW version DFL61_HARMATTAN_40.2012.21-3.280.04.1_PR_280
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 86 %, 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 ]
[_] cmt-algo [init 100 % 789 / 789 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 ]
[x] kernel [finished 100 % 2714 / 2714 kB 1571 kB/s]
[_] rootfs [writing 3 % 39936 / 1170774 kB 8998 kB/s]
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 ]
[f] cmt-algo [init 0 % 789 / 789 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 ]
[x] kernel [finished 100 % 2714 / 2714 kB 1571 kB/s]
[x] rootfs [finished 100 % 1170774 / 1170774 kB 9034 kB/s]
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
Timeout while waiting for the HWBREAK
Could not reboot into cold bootmode
[Pipe 6] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

C:\N9>

as far as cold flash goes

C:\N9>flasher -F DFL61.bin -f -c
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.

Using 1st image to detect HW
Suitable USB interface (bootrom) not found, waiting...
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 36 30 07 07 13 02 01 00 12 15 01 23
e1 57 14 5b 18 23 f5 85 9c df df da 6b e3 7d 9e
c9 ca e9 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
ERROR: ReadFile(1) GetOverlappedResult() error 31 timeout -19 ms
usb_bulk_read: No error
Got HWID: RM-696:1501
Waiting for ASIC id...
ERROR: ReadFile error 31
usb_bulk_read: No error
ERROR: Cold flashing failed.

C:\N9>

so far I was able to flash mmc only

it seems that [_] cmt-algo [init 100 % 789 / 789 kB NA ]
[ ] cmt-mcusw [pending 0 % 0 / 0 kB NA ]

making me issue

Any idea, anyone what to do - flash next

First one would be to keep posting in one thread only.
Would make it easier to follow.

I should have read your OP more thoroughly.
You had a device with (one of the) asian firmware. You MUST NEVER flash such a device with any other localized firmware than asian.

Afaik there is no way back now.
Only "possible" solution you posted yourself in the big N9 flashing thread.
Sorry

Do you think hardware is fixable, I am thinking about doing this

TonyUkuk is offline TonyUkuk
09-05-13 , 06:07 PM
Posts: 86 | Thanked: 12 times | Joined on Dec 2011 @ Turkey
Report This | #938
Hi guys.

At last, after 5 or 6 ( no sleep no eat ) hardly days workings, testings and lookings for, i just found the way to solve the problem with Nokia N9 cmt problem during flashing.

Yea,till it i red many post from many forums from nice guys Thank you at all!!!

So lets begin. I'll tell you just the way with which one i solved it - in most situations this problem with cmt happening with chines versions of Nokia N9 (ofcourse brand), that why. If any questions feel free to ask.

(I do all these in Ubuntu 12.04) Steps:
1) Go here (prefer with Chrome browser to translate to english,cause site in russian)

2) Go to the section For any "gray" smartphones and download one firmware file and one content(emmc) file (i prefer to download just firmware file,no need to flash emmc,but if you want and have a time and patienсе download and flash also emmc). Save this (them if u decide to flash firmware and emmc) somewhere in the folders of /home/user/. In my option this folder was Downloads (I prefer to clean the folder before putting there the flashing files.

3) I prefer...no, I INSISTENLY prefer to have flash operations on computers with LINUX OS. If You cant, so just find someone who using Linux distributins Maann))
You must install flasher.3.12....deb.
here you can download it. But something get wrong during downloads, i think tablets-dev site went down,never mind - if problems, then click to the file at the end of this post, download and install it.


4) So, after steps 1 and 2, do these:
a)make sure that phone is FULLY charged
b)make sure that you did step a) and detach your Nokia N9 from all connections - charging, usb.. just put your phone back.
c)open terminal, type
Code:
sudo su
If live-cd no need, if installed OS then type your superuser password and then type this
Code:
flasher -F TheFirmwareWhichYouDownloadedByStepTwo.bin --flash-only=cmt -f -R
5) If success Your log must be like that
Code:
root@aceraspire4935g:/home/penryn/Загрузки# flasher -F D2C89BF2_DFL61_HARMATTAN_40.2012.21-3.418.2_PR_LEGACY_418_ARM_RM-696_PRD_signed.bin --flash-only=cmt -f
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 033.
Device identifier IMEIIMEIIMEIIME (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. 1601
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3.418.2_PR_418
Image cert-sw skipped
Image xloader skipped
Image secondary skipped
Image kernel skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped

Battery level 95 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[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 3087 kB/s]
Success
root@aceraspire4935g:/home/penryn/Загрузки# 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 033.
Device identifier: IMEIIMEIIMEIIME (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. 1601
Server implements softupd protocol version 1.8
Success
If no success, just put here output, let us to see. In 99% if no success, then we will try download another firmware - if need, we will download one by one firmwares (in this time here and try it again))) funny, but it will work 100% at last!

6) So after succes, just type

when I Typed in number under simcard tray it came out sweedesh version of software for download, also scaned the code from about product same number came out

TBH
I have no idea about fixability.
But above seems only possible way...

SIM tray may of course directly lie into your face but scanned code should have not done so
One more proof you should always check with 'flasher -i' on a device you are not 100% sure about.