View Single Post
Posts: 1,038 | Thanked: 3,981 times | Joined on Nov 2010 @ USA
#461
Originally Posted by mihkel View Post
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.
When I do the "Fixing MALF state" everything goes as described in the instruction. No errors, and the computer and phone stay connected the whole time I'm checking for a malf file.

Here's what I see:

Code:
rob@hymie:~/FlashN9$ sudo flasher --load -k vmlinuz-2.6.32.20112201-11.2-adaptation-n950-bootloader -n initrd.img-rescue-2.6.32.20112201-11.2-n950 --boot
[sudo] password for rob: 
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.

Suitable USB interface (bootloader/phonet) not found, waiting...
USB device found at bus 001, device address 111.
Device identifier: 351669052798334 (SN: N/A)
Found device RM-696, hardware revision 1502
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_006
Sending kernel image (2497 kB)...
100% (2497 of 2497 kB, avg. 16652 kB/s)
Sending initfs image (1920 kB)...
100% (1920 of 1920 kB, avg. 21818 kB/s)
Success
After about 15-20 seconds, my desktop notifier tells me I've got 3 volumes I can mount, so I mount "rootfs." After that finishes (2-3 seconds):
Code:
rob@hymie:~/FlashN9$ ls /media/rootfs
bin  boot  cdrom  dev  etc  floppy  home  initrd  lib  lost+found  media  mnt  opt  proc  root  sbin  srv  sys  syspart  tmp  usr  var
rob@hymie:~/FlashN9$ ls /media/rootfs/var
backups  cache  clean-device  lib  local  lock  log  mail  mstartup  opt  run  spool  tmp
This time there was no malf file to delete, so I unmounted rootfs and unplugged the phone.

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.
 

The Following User Says Thank You to robthebold For This Useful Post: