maemo.org - Talk - The screen doesn't turn on, help me figure out how to access internal memory

maemo.org - Talk (https://talk.maemo.org/index.php)

- Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)

- - The screen doesn't turn on, help me figure out how to access internal memory (https://talk.maemo.org/showthread.php?t=97331)

The screen doesn't turn on, help me figure out how to access internal memory

Hi all.

A few years ago my N900 stopped working, and I got another phone.

However it had some sentimental value holding photos and videos, so now I'm trying to recover them.

Turns out my phone turns on as it's supposed to, the music plays, the keyboard lightens up and such, however the screen stays black. Is there a way to test if a touchscreen is responsive maybe?

At first I would very much like to somehow access the old files, and then try to fix the screen/get the replacement in some time maybe.

I was considering a few options:

The obvious one, USB to PC. When I connect N900 to my laptop, 'lsusb' states that 'Nokia Mobile Phones N900 (Storage Mode)' is there, however 'lsblk' doesn't any other connected drives. Any way I could force it to 'connect' without pressing something on the phone? Or, alternatively, if the touchscreen is responsive, maybe I could press something to allow for 'mass storage' mode?

Also I was trying to connect the phone to TV via RCA cable (red yellow white). The TV does react to the plugging in of the phone, however it too stays black.

If at least the keyboard is responsive, maybe I could do some useful things with it?

Edit: I'm fairly certain my touchscreen is responsive, since I hear clicking sounds when it's on. So maybe someone could direct me what kind of messages pop up when the phone turns on, what happens when it gets plugged in to PC, and I would try to click on them to enable 'mass storage'?

Re: The screen doesn't turn on, help me figure out how to access internal memory

tv out is known to not work when screen can't display

i would actually suggest rescueOS as the best alternative

when you plugin pc, there is normally a dialog roughly in the middle of the lower half of the screen ... so you can touch in that general area and hope USB mounts. Mass storage is above PC Suite Mode

You may also want to try rescueOS .. which

Re: The screen doesn't turn on, help me figure out how to access internal memory

If it's connected in storage mode you should see the content mounted in '/media/Nokia N900'

What does dmesg tell you after connecting USB ?

Re: The screen doesn't turn on, help me figure out how to access internal memory

Quote:

Originally Posted by nieldk (Post 1513161)

If it's connected in storage mode you should see the content mounted in '/media/Nokia N900'

What does dmesg tell you after connecting USB ?

Code:

[ 2844.518017] usb 2-1.2: USB disconnect, device number 3

[ 2847.369485] usb 2-1.2: new high-speed USB device number 4 using ehci-pci

[ 2847.548096] usb 2-1.2: New USB device found, idVendor=0421, idProduct=0105

[ 2847.548107] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=5

[ 2847.548114] usb 2-1.2: Product: Nokia N900 (Update mode)

[ 2847.548118] usb 2-1.2: Manufacturer: Nokia

[ 2847.548123] usb 2-1.2: SerialNumber: 4D554D333737313636

[ 2848.165106] NET: Registered protocol family 35

[ 2848.183825] usbcore: registered new interface driver cdc_phonet

[ 2849.274547] usb 2-1.2: USB disconnect, device number 4

[ 2855.902278] usb 2-1.2: new high-speed USB device number 5 using ehci-pci

[ 2855.996984] usb 2-1.2: New USB device found, idVendor=0421, idProduct=01c7

[ 2855.996995] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 2855.997001] usb 2-1.2: Product: N900 (Storage Mode)

[ 2855.997006] usb 2-1.2: Manufacturer: Nokia

[ 2855.997010] usb 2-1.2: SerialNumber: 372041756775

[ 2855.998288] usb-storage 2-1.2:1.0: USB Mass Storage device detected

[ 2855.998716] scsi7 : usb-storage 2-1.2:1.0

[ 2857.000122] scsi 7:0:0:0: Direct-Access     Nokia    N900              031 PQ: 0 ANSI: 2

[ 2857.000819] scsi 7:0:0:1: Direct-Access     Nokia    N900              031 PQ: 0 ANSI: 2

[ 2857.001598] sd 7:0:0:0: Attached scsi generic sg2 type 0

[ 2857.002201] sd 7:0:0:1: Attached scsi generic sg3 type 0

[ 2857.013112] sd 7:0:0:0: [sdb] Attached SCSI removable disk

[ 2857.015976] sd 7:0:0:1: [sdc] Attached SCSI removable disk

[ 2863.415351] usb 2-1.2: USB disconnect, device number 5

[ 2873.652698] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:c0:c1:c0:1e:9a:b0:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 

[ 2874.267446] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:c0:c1:c0:1e:9a:b0:08:00 SRC=192.168.1.1 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 

[ 2999.777682] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:c0:c1:c0:1e:9a:b0:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 

[ 3003.876076] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:c0:c1:c0:1e:9a:b0:08:00 SRC=192.168.1.1 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 

[ 3050.106003] usb 2-1.2: new high-speed USB device number 6 using ehci-pci

[ 3050.199459] usb 2-1.2: unable to get BOS descriptor

[ 3050.201191] usb 2-1.2: New USB device found, idVendor=0421, idProduct=0106

[ 3050.201203] usb 2-1.2: New USB device strings: Mfr=34, Product=38, SerialNumber=0

[ 3050.201209] usb 2-1.2: Product: Nokia USB ROM

[ 3050.201213] usb 2-1.2: Manufacturer: Nokia

[ 3050.513211] usb 2-1.2: USB disconnect, device number 6

[ 3050.990494] usb 2-1.2: new high-speed USB device number 7 using ehci-pci

[ 3051.168891] usb 2-1.2: New USB device found, idVendor=0421, idProduct=0105

[ 3051.168902] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=5

[ 3051.168908] usb 2-1.2: Product: Nokia N900 (Update mode)

[ 3051.168913] usb 2-1.2: Manufacturer: Nokia

[ 3051.168917] usb 2-1.2: SerialNumber: 4D554D333737313636

[ 3052.074767] usb 2-1.2: USB disconnect, device number 7

[ 3125.800354] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:c0:c1:c0:1e:9a:b0:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 

[ 3133.074754] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:c0:c1:c0:1e:9a:b0:08:00 SRC=192.168.1.1 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2

Not sure what it all means:) As I said tho, it does "see" that the N900 is connected, however it does not mount it. I think it just waits for me to press 'mass storage' mode button on my phone, and since I do not press it for some reason (maybe it's getting blocked by some other popups, or maybe the touchscreen is not in fact responsive, and the "click" sound I hear is just that... a meaningless sound), the system does not recognize the drive. The same happens on Win10 btw, it shows that two drives are getting connected, but they are blurred, and if I try to click on them I get some error about waiting or something.

Re: The screen doesn't turn on, help me figure out how to access internal memory

Quote:

Originally Posted by sicelo (Post 1513158)

Thanks, trying it now, however having some problems. I follow the instructions from here, and it says

Code:

For maemo_flasher, it's:



  flasher-3.5 -k rescueOS_n900_kernel_1.2.zImage -n rescueOS-1.2.img -l -b"rootdelay root=/dev/ram0"

So in my case I enter this:

Code:

jusno@juac47:~$ flasher-3.5 -k "/home/jusno/Downloads/rescueOS_n900_kernel_1.2.zImage" -n "/home/jusno/Downloads/rescueOS-1.2.img" -l -b"rootdelay root=/dev/ram0"

I see this:

Code:

flasher v2.5.2 (Oct 21 2009)



Suitable USB device not found, waiting.

USB device found found at bus 002, device address 007.

Found device RX-51, hardware revision 2101

NOLO version 1.4.14

Version of 'sw-release': RX-51_2009SE_20.2010.36-2_PR_MR0

Sending kernel image (1823 kB)...

100% (1823 of 1823 kB, avg. 28488 kB/s)

Sending initfs image (5260 kB)...

100% (5260 of 5260 kB, avg. 28279 kB/s)

Using kernel command line: "rootdelay root=/dev/ram0"

and that's it. I just get back to my terminal. If I understand correctly a console should boot up, where I would be able to see the said /rescueOS/ dir, run scripts etc, but I see nothing. Am I missing something here?

Re: The screen doesn't turn on, help me figure out how to access internal memory

Quote:

Originally Posted by elementaru (Post 1513219)

I see this:

Code:

flasher v2.5.2 (Oct 21 2009)



Suitable USB device not found, waiting.

USB device found found at bus 002, device address 007.

Found device RX-51, hardware revision 2101

NOLO version 1.4.14

Version of 'sw-release': RX-51_2009SE_20.2010.36-2_PR_MR0

Sending kernel image (1823 kB)...

100% (1823 of 1823 kB, avg. 28488 kB/s)

Sending initfs image (5260 kB)...

100% (5260 of 5260 kB, avg. 28279 kB/s)

Using kernel command line: "rootdelay root=/dev/ram0"

That is correct. What do you see on N900? :)

Re: The screen doesn't turn on, help me figure out how to access internal memory

Quote:

Originally Posted by sicelo (Post 1513220)

What do you see on N900? :)

Are you kidding me?

elementaru, type on n900:
/rescueOS/mass-storage-enable.sh or mse on latest image (I don't tested it)
Be aware that under rescueos there are no sticky keys

Re: The screen doesn't turn on, help me figure out how to access internal memory

Quote:

Originally Posted by elros34 (Post 1513225)

Are you kidding me?

elementaru, type on n900:
/rescueOS/mass-storage-enable.sh or mse on latest image (I don't tested it)
Be aware that under rescueos there are no sticky keys

Lol! Silly me. Of course it boots on the phone. I just can't see it:)

Anyway, I enabled mass storage by typing 'mse', however this error pops up:

http://picturehost.eu/uploads/fb26a1...2018:16:38.png

When I go to gnome-disk or whatever it's called, and press "mount" on the 'Nokia N900' drive, I get this:

http://picturehost.eu/uploads/480a03...2018:28:30.png

That smaller drive does mount when I type 'mse', I can see and access some files from my old games, apps, however when I go there, it says I don't have the permissions (not that I think there's anything in this dir, most likely it's empty or something, just interesting that it says so):

http://picturehost.eu/uploads/6bd28f...2018:17:57.png

I also tried to enable USB networking, and successfully connected to the device through FTP, however I only saw some newly created files I'm guessing by the RescueOS, its dir, its bash scripts, etc. No sign of my actual phone files.

Any suggestions?

I'm guessing the biggest obstacle is that the 29GB drive doesn't mount.. I'm just not sure where to start in trying to solve this.

Re: The screen doesn't turn on, help me figure out how to access internal memory

could you pastebin the output of dmesg? ( just after trying to mount the 29G device)

Re: The screen doesn't turn on, help me figure out how to access internal memory

Quote:

Originally Posted by chainsawbike (Post 1513285)

could you pastebin the output of dmesg? ( just after trying to mount the 29G device)

Everything?:) Here you go. http://pastebin.ca/3703728

In the mean time I was playing around, and had ordered gnome-disk to create disk image of the drive, and that's what I got after some time:

http://picturehost.eu/uploads/d1b83b...2022:58:59.png

Ain't good I suppose.