Originally Posted by mihkel

Rob, have you ever gotten the "device descriptor read/64, error -110" error while trying to clear the MALF state?
And does your phone stay connected to the computer correctly? Mine disconnects as soon as I try to load a custom kernel and goes into a connect-disconnect loop.

Originally Posted by robthebold

Thanks very much.

Okay, I can telnet in to device. (Took me a little while, since everything I know about usb networking fits in a thimble, and I was using 192.168.2.* as my local LAN, so using offline device finally did the trick. )

Anyway, I can see the root directory with "ls" and I can ping back to the USB host PC, so I guess the phone has booted up. From what you wrote, I gather the screen is dead but the phone lives. Anything else I should test before attempting to get it fixed?

Thanks again,
Rob

Originally Posted by mihkel

Tried it, but still no change,
I can't set an IP address to to the phone because it will not stay connected to the PC with a custom kernel. Probably why I can't clear the MALF state either.

dmesg gives me:

Code:

[  915.000065] usb 1-2: new high speed USB device using ehci_hcd and address 17
[  918.154552] usb 1-2: USB disconnect, address 17
[  920.030081] usb 1-2: new high speed USB device using ehci_hcd and address 18
[  920.762702] usb 1-2: USB disconnect, address 18

It disconnects as soon as I load the custom kernel for your tool or for flasher.
After it disconnects, lsusb won't list the phone - it's as if it wasn't connected to the computer at all.

With just

Code:

sudo flasher -i

the phone stays connected to the computer and lsusb gives me:

Code:

Bus 001 Device 024: ID 0421:0105 Nokia Mobile Phones Nokia Firmware Upgrade Mode

Do any of you know, if the phone is still supposed to boot and vibrate with the proximity sensor and screen disconnected?
I bought a replacement screen for the phone from eBay so I don't believe that it's faulty. It COULD be a faulty sensor, but I really doubt it because I just replaced it as well..

Originally Posted by robthebold

Of course, I've still apparently got my hardware fault in the display, but at least the flasher works for me.

Hope this info helps you diagnosing your device.

Originally Posted by juiceme

Rob, You can export the partitions to your Linux via USB when you can telnet in.

1.) Enter one of the following commands to export the partition:
"echo /dev/mmcblk0p1 > /sys/devices/platform/musb_hdrc/gadget/lun0/file" # This is for MyDocs partition
"echo /dev/mmcblk0p2 > /sys/devices/platform/musb_hdrc/gadget/lun0/file" # This is for root partition
"echo /dev/mmcblk0p3 > /sys/devices/platform/musb_hdrc/gadget/lun0/file" # This is for home partition

2.) exit from the telnet connection

3.) Disconnect the USB for about one second and reconnect it

What wil happen, the partition will be detected by Linux and automatically mounted. (if not, you can look it up from dmesg and mount it manually)

After copying what you need form the partition, you can again set the IP addredd, telnet to the device and export the next partition.

If you have lots of storage space it is of course best to back up all three partitions, when you get the new/repaired device back it will be EXACTLY in the same state that your old device was when you upload back the backups. "sudo tar -cvf <filename> <mountpoint>" is good way to do that.

Originally Posted by mihkel

One last try before giving up - what distro are you running for flashing?

Originally Posted by robthebold

mihkel:

I'm using 64-bit Kubuntu 12.04, with the x64 version of the flasher (flasher_3.12.1_amd64.deb). However, I've also successfully used the i386 version on a Lubuntu 12.04 Eee PC.

Originally Posted by Rusnak-COBRA

USB yes, but drivers are not the same. anyway, cable with too high impedance...