Page 2 of 3 1 2 3
Reply
Thread Tools
JonWW's Avatar
JonWW is offline JonWW
2010-07-25 , 07:50
Posts: 623 | Thanked: 289 times | Joined on Jan 2010 @ UK
#11
Plug it in to a PC and see if the computer recognises it. You could try putting it into R&D mode and back to normal mode with the command line flasher (I think you need a Linux machine to set it back to normal mode but not sure as I have never needed to do this) this worked as a early firmware fix where some phone would randomly reboot and after 50 reboot cycles the phone would brick it self. R&D mode would unbrick it.
With the phone switched off you should be able to see both drives on the phone when plugging it in to a PC.

Good luck.
 

The Following User Says Thank You to JonWW For This Useful Post:
tremby is offline tremby
2010-07-25 , 10:08
Posts: 53 | Thanked: 20 times | Joined on Jan 2010
#12
Originally Posted by andreas.k View Post
well if i were you i whould leave the battery for more than 1 minute (just for sure) about 5 minutes
I left it out overnight and there doesn't seem to be any change.
 
tremby is offline tremby
2010-07-25 , 10:08
Posts: 53 | Thanked: 20 times | Joined on Jan 2010
#13
Originally Posted by n900 lover View Post
have you tried connecting it to your pc while it was "switched on"?
The same happens there as when I plug it in when "switched off" which I'll respond to in a sec...
 
tremby is offline tremby
2010-07-25 , 10:18
Posts: 53 | Thanked: 20 times | Joined on Jan 2010
#14
Originally Posted by JonWW View Post
Plug it in to a PC and see if the computer recognises it. You could try putting it into R&D mode and back to normal mode with the command line flasher (I think you need a Linux machine to set it back to normal mode but not sure as I have never needed to do this) this worked as a early firmware fix where some phone would randomly reboot and after 50 reboot cycles the phone would brick it self. R&D mode would unbrick it.
With the phone switched off you should be able to see both drives on the phone when plugging it in to a PC.

Good luck.
OK, when plugged in (in it's "off" or "on" state -- no difference) I get this dmesg stuff:

Code:
[  767.870293] usb 2-1: new high speed USB device using ehci_hcd and address 9
[  768.022617] usb 2-1: configuration #1 chosen from 2 choices
[  768.025526] scsi9 : SCSI emulation for USB Mass Storage devices
[  768.025878] usb-storage: device found at 9
[  768.025883] usb-storage: waiting for device to settle before scanning
[  773.020819] usb-storage: device scan complete
[  773.021649] scsi 9:0:0:0: Direct-Access     Nokia    N900              031 PQ: 0 ANSI: 2
[  773.022210] scsi 9:0:0:1: Direct-Access     Nokia    N900              031 PQ: 0 ANSI: 2
[  773.023230] sd 9:0:0:0: Attached scsi generic sg2 type 0
[  773.029574] sd 9:0:0:1: Attached scsi generic sg3 type 0
[  773.033433] sd 9:0:0:0: [sdb] Attached SCSI removable disk
[  773.037423] sd 9:0:0:1: [sdc] Attached SCSI removable disk
I then have /dev/sdb and /dev/sdc but I can't mount them:

<bjn@segnus:~>$ sudo mount /dev/sdb usb
mount: /dev/sdb: unknown device

Same for /dev/sdc. /dev/sdb1 and /dev/sdb2 don't exist.

sudo fdisk -l only shows my hard drive's partitions -- nothing for the N900.

And when I unplug it I get the dmesg
Code:
[ 1027.929244] usb 2-1: USB disconnect, address 9
I don't know off hand how to get to R&D mode -- I'll look into this once I've tried a few other things on the list here. Interesting you mention 50 boot cycles -- I think I could be around there. I got the phone at the beginning of March. I updated /something/ to get it to work on the Three network but I don't know if it was firmware or what. I've been fairly good at keeping it up to date with software updates since but I'm not sure if I've ever reflashed anything.
 
tremby is offline tremby
2010-07-25 , 10:31
Posts: 53 | Thanked: 20 times | Joined on Jan 2010
#15
Originally Posted by dynomot View Post
Have you tried a TV out cable ? Here in the UK they weren't shipped with the phone for some reason, but they work as they do on an a S60 phone.

I'd try a reflash, if you have a complete backup it takes about ten minutes (depending what and how many applications you had installed).
OK, here we go! I'd never tried that cable before. When I plugged it in to my TV the "unlock" screen was up. I stabbed blindly at the touch screen until I got the code in (why it doesn't let you use the keyboard for that code is beyond me...) and next it went to the set up the phone screen, now it wants the time and date (which has reset to 2009-01-01 and currently reads 0602 -- I wonder if that's a clue. that's roughly when I went to bed, but I don't know why it would have reset at that point).

And now that I've entered that I'm on my home screen, complete with my own background and icons.

It's now on the network -- I can get all my stuff off. So I guess it was just waiting at the lock screen the whole time.

Still no action from the screen. I guess I'll look into reflashing it once I've got my stuff off.

So thanks for the TV cable suggestions, people!
 
tremby is offline tremby
2010-07-25 , 11:12
Posts: 53 | Thanked: 20 times | Joined on Jan 2010
#16
I've got everything important off. I'm looking at the firmware flashing wiki page -- do I want to flash just rootfs or eMMC and rootfs?
 
JonWW's Avatar
JonWW is offline JonWW
2010-07-25 , 11:31
Posts: 623 | Thanked: 289 times | Joined on Jan 2010 @ UK
#17
Before flashing I would first do a backup, at least that way if the phone needs repairing or replacing you can set it up the way it was when you get it back, also it will make setting it up again easier if you fix it yourself.
Flash with the Vanilla image first, if it comes back to life then all well and good.
If not then flash the Vanilla and then the eMMC and try again. Do not boot phone inbetween flashes.
 
tremby is offline tremby
2010-07-25 , 11:51
Posts: 53 | Thanked: 20 times | Joined on Jan 2010
#18
Originally Posted by JonWW View Post
Flash with the Vanilla image first, if it comes back to life then all well and good.
If not then flash the Vanilla and then the eMMC and try again. Do not boot phone inbetween flashes.
I'm a little confused. The only mentions of "vanilla" on the repository page are eMMC content.

I tried flashing the latest UK firmware but it doesn't seem to be working... I run
sudo ./flasher-3.5 -F ~/RX-51_2009SE_10.2010.19-1.203.1_PR_COMBINED_203_ARM.bin -R

and it gives
Code:
flasher v2.5.2 (Oct 21 2009)

SW version in image: RX-51_2009SE_10.2010.19-1.203.1_PR_203
Image 'kernel', size 1705 kB
	Version 2.6.28-20101501+0m5
Image 'rootfs', size 173696 kB
	Version RX-51_2009SE_10.2010.19-1.203.1_PR_203
Image 'cmt-2nd', size 81408 bytes
	Version BB5_09.36
Image 'cmt-algo', size 519808 bytes
	Version BB5_09.36
Image 'cmt-mcusw', size 5826 kB
	Version rx51_ICPR82_10w08
Image '2nd', size 14720 bytes
	Valid for RX-51: 2217, 2218, 2219, 2220, 2120
	Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
	Valid for RX-51: 2217, 2218, 2219, 2220, 2120
	Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
	Valid for RX-51: 2217, 2218, 2219, 2220, 2120
	Version 1.4.14.8+0m5
Image '2nd', size 14720 bytes
	Valid for RX-51: 2101, 2102, 2103
	Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
	Valid for RX-51: 2101, 2102, 2103
	Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
	Valid for RX-51: 2101, 2102, 2103
	Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
	Valid for RX-51: 2307, 2308, 2309, 2310
	Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
	Valid for RX-51: 2307, 2308, 2309, 2310
	Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
	Valid for RX-51: 2307, 2308, 2309, 2310
	Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
	Valid for RX-51: 2407, 2408, 2409, 2410
	Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
	Valid for RX-51: 2407, 2408, 2409, 2410
	Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
	Valid for RX-51: 2407, 2408, 2409, 2410
	Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
	Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
	Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
	Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
	Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
	Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
	Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
	Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
	Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
	Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
	Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
	Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
	Version 1.4.14.8+0m5
Image '2nd', size 14720 bytes
	Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2113, 2114, 2115, 2116, 2117, 2118, 2119
	Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
	Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2113, 2114, 2115, 2116, 2117, 2118, 2119
	Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
	Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2113, 2114, 2115, 2116, 2117, 2118, 2119
	Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
	Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
	Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
	Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
	Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
	Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
	Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
	Valid for RX-51: 2607, 2608, 2609, 2610
	Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
	Valid for RX-51: 2607, 2608, 2609, 2610
	Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
	Valid for RX-51: 2607, 2608, 2609, 2610
	Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
	Valid for RX-51: 2507, 2508, 2509, 2510
	Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
	Valid for RX-51: 2507, 2508, 2509, 2510
	Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
	Valid for RX-51: 2507, 2508, 2509, 2510
	Version 1.4.14.8+0m5
Image '2nd', size 14720 bytes
	Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2210, 2211, 2212, 2213, 2214, 2215, 2216
	Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
	Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2210, 2211, 2212, 2213, 2214, 2215, 2216
	Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
	Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2210, 2211, 2212, 2213, 2214, 2215, 2216
	Version 1.4.14.8+0m5
Image '2nd', size 14848 bytes
	Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
	Version 1.4.14.8+0m5
Image 'xloader', size 14848 bytes
	Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
	Version 1.4.14.8+0m5
Image 'secondary', size 109440 bytes
	Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
	Version 1.4.14.8+0m5
Suitable USB device not found, waiting.
I hold the "u" key and plug the USB cable into the phone. It vibrates and then right away this happens...

Code:
USB device found found at bus 002, device address 022.
Found device RX-51, hardware revision 2101
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_3.2010.02-8_PR_MR0
and I'm straight back to my prompt. Then the phone vibrates again and switches on. (If I plug in the TV cable I can see that it goes to the enter code screen.) What's going on?
 
JonWW's Avatar
JonWW is offline JonWW
2010-07-25 , 11:54
Posts: 623 | Thanked: 289 times | Joined on Jan 2010 @ UK
#19
Just a thought when on the theme park ride might the phone recieved a knock. I had a ribbon connector come loose in an old Nokia 6600 after a knock. The N900 screen has two ribbon connectors one for the display and the other for the digitizer. Check out http://www.youtube.com/watch?v=aVEHm325-z8
 
tremby is offline tremby
2010-07-25 , 12:09
Posts: 53 | Thanked: 20 times | Joined on Jan 2010
#20
Originally Posted by JonWW View Post
Just a thought when on the theme park ride might the phone recieved a knock. I had a ribbon connector come loose in an old Nokia 6600 after a knock. The N900 screen has two ribbon connectors one for the display and the other for the digitizer. Check out http://www.youtube.com/watch?v=aVEHm325-z8
Grr, none of my screwdrivers are quite small enough for the crosshead ones. That's definitely worth trying first though -- thanks.
 
Reply
Page 2 of 3 1 2 3

« Previous Thread | Next Thread »

 
Forum Jump


All times are GMT. The time now is 08:04.

Contact Us - Home - Archive - Top