Reply
Thread Tools
Posts: 31 | Thanked: 11 times | Joined on Apr 2012 @ Germany
#1
My question is already stated in the title -- following some more info how it came about (italics), and at the bottom a summary what I tried so far:

Probably, I was incredible stupid today. After increasing numbers of issues with the tracker, which couldn't be cured by the usual means, I made a tracker reset. No big deal as I saved everything to the MyDocs partition.

To save the SMS I used QTweakN9 (http://talk.maemo.org/showthread.php?t=80600), which I installed the first time. During the first start the "bash" gets installed, too. That reminded me to search if there's a package of my favorite shell "zsh" for the N9. Yes, there is (http://talk.maemo.org/showthread.php?t=55947) and I was happy as it worked really well. So happy, that I appended "exec /bin/zsh" to my ~/.profile -- changing the login shell is sometimes not such a good idea, so I used that workaround. (That was mistake no. 1 I suppose, but I'm not sure, that my problem has something to do with that or if that was just an accidental coincidence...)

However, everything worked well and after an hour everything was restored from tracker reset. Haven't done a backup to my PC quite long, so I thought that now would be a good time. I already had MyDocs opened in the explorer, but then I realised I didn't made a fresh backup with the internal N9 backup app. So, unplugged USB (mistake no. 2), and was about to start the backup, but the keyboard didn't appear to name the backup... crap, what's going on?! I already wanted to copy&paste some string, but than made a reboot instead (mistake no. 3) -- "it won't hurt". But it hurt badly! The N9 get stuck at the NOKIA logo -- nothing happened anymore. (So at that moment no boot-loop.) Damn!


I searched the internet and found some options I have:
  • put the device in R&D mode with flasher (http://talk.maemo.org/showthread.php?t=85596), trying with "no-lifeguard-reset" set or cleared.
    => that enabled some fancy messages, but didn't help to boot the device.
  • flash a rescue system (http://wiki.meego.com/N950/Fixing_MALF_state)
    => sounded very promising and device was recognized by my linux box:

    Code:
    [262423.057512] usb 1-8: Product: Nokia N9
    [262423.057514] usb 1-8: Manufacturer: Nokia
    [262423.057516] usb 1-8: SerialNumber: 357923046591014
    [262423.067414] scsi26 : usb-storage 1-8:1.0
    [262424.069077] scsi 26:0:0:0: Direct-Access     Nokia    Nokia N9         0316 PQ: 0 ANSI: 2
    [262424.071939] sd 26:0:0:0: Attached scsi generic sg9 type 0
    [262424.076530] sd 26:0:0:0: [sdh] Attached SCSI removable disk
    BUT: sdh didn't show up in /proc/partitions.
    According to this (german) site (http://opensmartpad.org/meego/howtos...ll-backup.html) that rescue system does not work with the 16GB version of the N9! *@@$$!!!
  • tried the MOSLO kernel (http://talk.maemo.org/showpost.php?p...&postcount=457)
    => no luck either, but I tried this time with windows, as I never used networking via USB under linux.
  • flashed the firmware (but not the MMC, I want my data alive!)
    => N9 gets stuck at the NOKIA logo, LED lits and then reboots again.

I have no more ideas, but I deeply hope some of the pros in this forum have another one.

Especially I'm interested, if somebody can confirm that the approach with the rescue initrd is working also with 16GB devices.

My phone is not SIM locked, but however I have MfE accounts setup (which can trigger the device lock, according to a page I did not find anymore).

Thanks a lot in advance!
 
Posts: 504 | Thanked: 491 times | Joined on Dec 2011 @ lebanon
#2
try again the moslo kernel but on linux because it will only work in linux . I used it to recover files from my damaged-screen N9 .
 

The Following User Says Thank You to myname24 For This Useful Post:
Posts: 31 | Thanked: 11 times | Joined on Apr 2012 @ Germany
#3
Thanks for your answer! I'll give the MOSLO kernel another try. Today I was not sure, what to expect. Should the device boot into some kind of command line or is this "Warning you modified your device" screen the final state?

The README says you should do "sudo ifconfig usb0 192.168.2.14" -- do you remember, if one needs a special kernel module? The default debian kernel does not offer a network device usb0...
 
Posts: 1,219 | Thanked: 1,857 times | Joined on Feb 2011 @ Quezon City, Philippines
#4
IIRC g_multi (the kernel module which exposes a USB Composite Device with a USB Ethernet and USB Mass Storage device) is supported by the host-side Linux drivers for RNDIS or CDC ACM.
__________________
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@imblying, working on Glacier for Nemo.
 

The Following 2 Users Say Thank You to Hurrian For This Useful Post:
Community Council | Posts: 1,943 | Thanked: 2,840 times | Joined on May 2012 @ Finland
#5
Originally Posted by mpy View Post
Thanks for your answer! I'll give the MOSLO kernel another try. Today I was not sure, what to expect. Should the device boot into some kind of command line or is this "Warning you modified your device" screen the final state?

The README says you should do "sudo ifconfig usb0 192.168.2.14" -- do you remember, if one needs a special kernel module? The default debian kernel does not offer a network device usb0...
When you boot the device with the MOSLO rescue kernel, it does 2 things, firstly it exports all your partitions like the Fix-MALF kernel, and additionally it allows you to telnet into the device via USB.

If the correct module is as Hurrian says the rndis or cdc-acm module, both are available on latest stable:

Code:
juice@neumi:~$ 
juice@neumi:~$ cat /etc/debian_version 
6.0.6
juice@neumi:~$ 
juice@neumi:~$ uname -a
Linux neumi 3.2.0-0.bpo.2-686-pae #1 SMP Sat Jun 30 08:29:17 UTC 2012 i686 GNU/Linux
juice@neumi:~$ 
juice@neumi:~$ find /lib/modules/3.2.0-0.bpo.2-686-pae | grep -e cdc-acm -e ndis
/lib/modules/3.2.0-0.bpo.2-686-pae/kernel/drivers/net/usb/rndis_host.ko
/lib/modules/3.2.0-0.bpo.2-686-pae/kernel/drivers/net/wireless/rndis_wlan.ko
/lib/modules/3.2.0-0.bpo.2-686-pae/kernel/drivers/usb/class/cdc-acm.ko
juice@neumi:~$
 

The Following User Says Thank You to juiceme For This Useful Post:
Posts: 31 | Thanked: 11 times | Joined on Apr 2012 @ Germany
#6
I tried the MOSLO kernel again, with Debian 7 (Wheezy), Knoppix 7 (also Debian based) and another LIVE-Rescue-System (probably Gentoo kernel).

The modules you both mentioned are present and load w/o error. However after the flashing of the MOSLO kernel, dmesg tells me:

Code:
[  202.780040] usb 2-2: new high-speed USB device number 4 using ehci_hcd
[  202.904244] usb 2-2: unable to get BOS descriptor
[  202.905367] usb 2-2: New USB device found, idVendor=0421, idProduct=0106
[  202.905376] usb 2-2: New USB device strings: Mfr=34, Product=38, SerialNumber=0
[  202.905384] usb 2-2: Product: Nokia USB ROM
[  202.905391] usb 2-2: Manufacturer: Nokia
[  205.905888] usb 2-2: USB disconnect, device number 4
[  207.723401] usb 2-2: new high-speed USB device number 5 using ehci_hcd
[  207.853782] usb 2-2: New USB device found, idVendor=0421, idProduct=0105
[  207.853792] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[  207.853800] usb 2-2: Product: N9 (Update mode)
[  207.853807] usb 2-2: Manufacturer: Nokia
[  207.853814] usb 2-2: SerialNumber: 3579***********
[  208.476565] usb 2-2: USB disconnect, device number 5
[  209.961452] NET: Registered protocol family 35
[  210.051338] usbcore: registered new interface driver cdc_phonet
Especially the immediate "USB disconnect" looks bad, and no usb0 interface was shown up. (At that point I really hated the N9 for not having a simple µSD-Card for Data storage!)

Also the USB Mass Storage Mode only works as far as that of the Fix-MALF kernel (initial post), no possibility to read the reported SCSI device /dev/sdb.

After searching some more about that latter problem, I stumbled over a forum post (http://debianforum.de/forum/viewtopic.php?f=13&t=131373, german) describing a very similar behavior with a simple USB stick -- the bottom line was: Flash Memory damaged, Data lost, Stick dumped to landfill

I think I have to look for a replacement, too. Perhaps I can get a (screen) broken unit on ebay...

Thanks again for your hints!
 
Community Council | Posts: 1,943 | Thanked: 2,840 times | Joined on May 2012 @ Finland
#7
Yes, it looks that your USB interface or the flash memory might be broken, if neither Fix-MALF or MOSLO method export anything to your computer. Too bad.

Apart from the USB bus, there is nothing much you can do. There is serial maintanance connection pins under the SIM tray, but you need a special adapter to access that interface.
 
Posts: 981 | Thanked: 2,049 times | Joined on Jan 2012 @ Finland
#8
multiple options:
- telnet into moslo kernel rescue mode and check partitions from there

- rescue kernel, most likely you should not see anything in proc/partitions, did you even try to mount the whole device and/or check with fdisk how it looked?

vs trickier version
- connect serial ttl converter to rx & tx pins and login to serial console and do magic in there.
__________________
IRC: jonni@freenode
Sailfish: ¤ Qt5 SailfishTouchExample ¤ Qt5 MultiPointTouchArea Example ¤ ipaddress ¤ stoken ¤ Sailbox (Dropbox client) ¤
Harmattan: ¤ Presence VNC for Harmattan ¤ Live-F1 ¤ BTinput-terminal ¤ BabyLock ¤ BabyLock Trial ¤ QML TextTV ¤
Disclaimer: all my posts in this forum are personal trolling and I never post in any official capacity on behalf of any company.
 

The Following User Says Thank You to rainisto For This Useful Post:
Community Council | Posts: 1,943 | Thanked: 2,840 times | Joined on May 2012 @ Finland
#9
Originally Posted by rainisto View Post
vs trickier version
- connect serial ttl converter to rx & tx pins and login to serial console and do magic in there.
Well, he already tried rescue kernel and moslo kernel, and neither exported the FS'es or allowed telnet in... It looks to me there could be something wrong with his USB port...
 
Posts: 981 | Thanked: 2,049 times | Joined on Jan 2012 @ Finland
#10
1st post said that it exported sdh, thats why I was asking that did he do fdisk on /dev/sdh.

And most likely its just debian usbnetworking which sucks, maybe he should try ubuntu or something.
__________________
IRC: jonni@freenode
Sailfish: ¤ Qt5 SailfishTouchExample ¤ Qt5 MultiPointTouchArea Example ¤ ipaddress ¤ stoken ¤ Sailbox (Dropbox client) ¤
Harmattan: ¤ Presence VNC for Harmattan ¤ Live-F1 ¤ BTinput-terminal ¤ BabyLock ¤ BabyLock Trial ¤ QML TextTV ¤
Disclaimer: all my posts in this forum are personal trolling and I never post in any official capacity on behalf of any company.

Last edited by rainisto; 03-29-2013 at 04:50 PM.
 

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

Tags
boot-loop, mydocs, n9 16gb, rescue

Thread Tools

 
Forum Jump


All times are GMT -4. The time now is 02:39 PM.