Active Topics

 


Reply
Thread Tools
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#11
Originally Posted by rainisto View Post
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.
Granted, it's possible debian doesn't handle it correctly. I have to admit I have always used Ubuntu for connecting to my device in rescue mode since my laptop runs 12.04. I do have several pure Debian 6.0.6 installations but they are run on machines I use just remontely.
 

The Following User Says Thank You to juiceme For This Useful Post:
Posts: 32 | Thanked: 19 times | Joined on Apr 2012 @ Germany
#12
Originally Posted by rainisto View Post
- rescue kernel, (...) did you even try to mount the whole device and/or check with fdisk how it looked?
Indeed, I tried to read the whole device with sfdisk (cannot read device) and testdisk (device does not show up at all). And after some time, the device even vanished out of /dev. I think that is connected to the kernel message: "[ 208.476565] usb 2-2: USB disconnect, device number 5"

Originally Posted by rainisto View Post
- connect serial ttl converter to rx & tx pins and login to serial console and do magic in there.
I think I'll give that a try... can't get worse Is the serial console enabled with MALF and MOSLO kernel or even with NOKIA kernel? I stumbled over a R&D flag in flasher:
Code:
flasher --set-rd-flags=serial-console
I suppose that flag must be set? Apart from that, can you direct me to some link... okay, searching TMO helps. I found your post (http://talk.maemo.org/showpost.php?p...39&postcount=2) giving the essentials

Originally Posted by juiceme View Post
It looks to me there could be something wrong with his USB port...
I really hope that that's the case, and the flash memory is still fine!

Originally Posted by rainisto View Post
And most likely its just debian usbnetworking which sucks, maybe he should try ubuntu or something.
Originally Posted by juiceme View Post
I have always used Ubuntu for connecting to my device in rescue mode since my laptop runs 12.04.
Fine, I used Debian and Gentoo kernels, but no one from Ubuntu. I'll try that first. Unfortunately I have no other device I can test with, but thanks for the explicit Ubuntu version number!

Last edited by mpy; 2013-03-30 at 10:45.
 
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#13
Originally Posted by mpy View Post
Originally Posted by rainisto View Post
- connect serial ttl converter to rx & tx pins and login to serial console and do magic in there.
I think I'll give that a try... can't get worse Is the serial console enabled with MALF and MOSLO kernel or even with NOKIA kernel? I stumbled over a R&D flag in flasher:
Code:
flasher --set-rd-flags=serial-console
I suppose that flag must be set?
There serial console can also be activated on the default Harmattan kernel. The tricky part is the physical connection. When you remove the sim tray you can see the contacts on the PCB edge. The levels are 3v3 TTL, so you need a level shifter (or 3 volt TTL <-> USB serial) adapter between the device and your computer.
 

The Following User Says Thank You to juiceme For This Useful Post:
Posts: 32 | Thanked: 19 times | Joined on Apr 2012 @ Germany
#14
So, only 33 month later I can report the outcome of my efforts with my bricked N9/16GB.

Perhaps for future visitors which are interested in this topic (more and more unlikely as time goes by), but mainly to give the guys an update who helped a lot (hopefully you are still subscribed to this thread).

Cut a long story short: I was able to rescue my phone and also my data

But much less spectacular than you might think:

After digging through the schematic and the layout to find the serial rx/tx port (my thought-so last resort), I though it would be a good idea to fresh up my memory how the phone behaves when booted via the flasher. So, I tried to boot the bare mainboard via the flasher (under Debiab GNU/Linux 8.2 (jessie)):

Code:
flasher -l -b --enable-rd-mode --set-rd-flags=serial-console --suppress-warranty-warning -k malf/vmlinuz-2.6.32.20112201-11.2-adaptation-n950-bootloader -n malf/initrd.img-rescue-2.6.32.20112201-11.2-n950
(This could be, but must not be the command I used before, because I didn't documented it back then)

And, just by accident the volumes of my phone popped up after some time! Just for a few seconds, but reproducible after a reboot, so that was enough to rescue the important files I was after and to fix the issue with ~/.profile.

I put the mainboard back in its case and my thought-dead N9/16GB was back to life again. No problems what-so-ever! Either it was some self-healing over the years (that's my favorite guess ), I did something wrong with the flasher back then because I had blinders on or some kernel update on my computer helped. I don't know.

So, the lesson is clear:

- the MALF kernel works also on the Nokia N9 with only 16GB
- and most important: Don't ever mess with the .profile file!


Thanks to those who answerd my questions patiently, especially juiceme

Last edited by mpy; 2015-12-28 at 21:58. Reason: formatting, wrong calculation
 

The Following 7 Users Say Thank You to mpy For This Useful Post:
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#15
Excellent, I am so happy you managed to finally do it
And incidentally, this probably is the longest duration a fix took, indeed 2-and-3/4-years!
 

The Following 6 Users Say Thank You to juiceme For This Useful Post:
Reply

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


 
Forum Jump


All times are GMT. The time now is 15:44.