fendetto | # 31 | 2014-04-23, 11:48 | Report

hey guys wanna ask is it corect what i do ..

juiceme | # 32 | 2014-04-23, 12:24 | Report

Yes, looks good up to that point, but the messages should continue from there.
What has happened, the flasher tool found the N9 from your USB and sent the counterpart to the device.
After that, the flashing should start.

fendetto | # 33 | 2014-04-23, 12:27 | Report

been waiting about 10 minitus still the same hmmm

juiceme | # 34 | 2014-04-23, 12:32 | Report

what??
nothing else appeared on the screen???

Then it did not work, just remove cable, turn off the device if it torns on, and retry the flasher command and connect the cable.

fendetto | # 35 | 2014-04-23, 12:35 | Report

triend 3 times no lock..still stuck on usb cable things..

DJJonosound | # 36 | 2014-04-23, 12:44 | Report

I had this same issue, it was never fixed and the device was stuck in malf state. Ended up putting the open mode kernel on somehow and then a week of no action I woke up to find it working perfectly. No malf, no issues, no loss of data. No one was able to figure out the issue.

fendetto | # 37 | 2014-04-23, 12:51 | Report

let say if i put sailfish will it be work ??

juiceme | # 38 | 2014-04-23, 13:50 | Report

Possibly, however if you cannot flash it that may prove to be difficult.

First thing I'd try, however is to cold-flash it.
Doing that, however, will delete all your data from the device.

fendetto | # 39 | 2014-04-23, 13:59 | Report

what is the problem actually ??

juiceme | # 40 | 2014-04-23, 18:54 | Report

Well, when you start the flasher utility, (with intent to flash, mark it, there are*other ways of using it) it will first check that there is a N9 device connected, and then send the flasher counterpart called APE algorithm to the device.
The APE is actually a small linux kernel that knows how to do some basic initialization to the device, and then it starts to wait for the flasher to push the flashable images to it.

Now it seems to me that the 1st part went OK, as the flasher tells the following info:

Suitable USB interface (bootloader/phonet) not found, waiting...
Found device RM-696, hardware revision 1507
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_005
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 18337 kB/s)

Then, for some reason the process does not continue for you, when it says:

Suitable USB interface (phonet) not found, waiting...

Instead, it should actually continue like this:

Suitable USB interface (phonet) not found, waiting...
USB device found at bus 001, device address 027.
Device identifier: 327324051677480 (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. 1507
Server implements softupd protocol version 1.8
....
....
....

So, there is something wrong with the 2nd part of the loading.
Now, this could be because your device is in some bad state, and that was why I asked if you have tried to cold-flash it.

On the other hand, it maybe could be because you are using Windows. It is a sad fact that Windows is notoriously bad at IO, the USB stack is so poorly implemented it makes a grown man cry
Usually Linux is better for anything except graphics performance, and that is only because video vendors see the target user group in windows-gaming people, not bothering to make as good drivers for Linux...

So, there are 2 alternatives, try different flasher commands or try flashing with Linux.