Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 11 hrs, 7 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 23 hrs ago - more...
|
2013-01-09
, 14:26
|
|
Posts: 1,038 |
Thanked: 3,980 times |
Joined on Nov 2010
@ USA
|
#452
|
thedead1440:
I did the cold flash as described.
I don't see errors, so I guess that worked. I followed that with a reset:
Still doesn't boot. So I flash it "warm" again. After the reset step, the LED flashes 8 (I think) short flashes and goes dark. I pull the cable and try to start it. As before, the LED comes on steady, but no vibrate. Eventually the LED turns off, but the phone is not working as expected. This is the same result as I've gotten previously.
BTW, I can still plug it in to USB port and run "lsusb" and find,
"Bus 001 Device 110: ID 0421:0518 Nokia Mobile Phones" after a short wait.
This is the same as before, so it's sort of running.
I did the cold flash as described.
rob@hymie:~/FlashN9/Firmware/059M5V1$ sudo flasher -c -F main.bin -F emmc.bin
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.
Using 1st image to detect HW
Suitable USB interface (bootrom) not found, waiting...
USB device found at bus 001, device address 094.
Device identifier: (null) (SN: N/A)
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 36 30 07 07 13 02 01 00 12 15 01 ec
43 05 3d 10 1c 32 01 cd 9d 2b 32 c3 3d 12 6a fe
23 a4 07 14 15 01 12 dd 2f 66 d4 55 fe 19 2c 62
b9 b8 e2 65 0a fc 1d 9f 3f 90 15 09 01 13 bf 3e
ef 15 52 e7 03
HW variant: HS
Found matching 1st (916)
Sending 1st image (26496 bytes)... done.
Sending HWID query... Received 11 bytes from 1st
Got HWID: RM-696:1502
Suitable USB interface (bootrom) not found, waiting...
USB device found at bus 001, device address 095.
Device identifier: (null) (SN: N/A)
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 36 30 07 07 13 02 01 00 12 15 01 ec
43 05 3d 10 1c 32 01 cd 9d 2b 32 c3 3d 12 6a fe
23 a4 07 14 15 01 12 dd 2f 66 d4 55 fe 19 2c 62
b9 b8 e2 65 0a fc 1d 9f 3f 90 15 09 01 13 bf 3e
ef 15 52 e7 03
Sending 2nd image (25984 bytes)... done.
Sending ping... pong.
Sending ape-algo (7266816 bytes)... done.
rob@hymie:~/FlashN9/Firmware/059M5V1$ sudo flasher -R
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.
USB device found at bus 001, device address 096.
Device identifier: 351669052798334 (SN: N/A)
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1502
Server implements softupd protocol version 1.8
Success
BTW, I can still plug it in to USB port and run "lsusb" and find,
"Bus 001 Device 110: ID 0421:0518 Nokia Mobile Phones" after a short wait.
This is the same as before, so it's sort of running.
|
|
2013-01-09
, 14:32
|
|
Moderator |
Posts: 6,215 |
Thanked: 6,400 times |
Joined on Nov 2011
|
#453
|
robthebold,
Does this mean your display is not working? The signs are that after some while its still detected so the device has power and life but the display is spoilt/damaged hence nothing appears?
Edit: For your reference my device in sync&connect:
Similar right? Hence my suspicion of a damaged/spoilt display not a spoilt device per se...
Last edited by thedead1440; 2013-01-09 at 14:38.
Does this mean your display is not working? The signs are that after some while its still detected so the device has power and life but the display is spoilt/damaged hence nothing appears?
Edit: For your reference my device in sync&connect:
Code:
Bus 002 Device 028: ID 0421:0519 Nokia Mobile Phones
Last edited by thedead1440; 2013-01-09 at 14:38.
|
|
2013-01-09
, 14:39
|
|
Posts: 1,038 |
Thanked: 3,980 times |
Joined on Nov 2010
@ USA
|
#454
|
Originally Posted by thedead1440
It's possible . . . I also never get the vibrate either when powering it up, but I don't know the exact boot sequence . . .
robthebold,
Does this mean your display is not working? The signs are that after some while its still detected so the device has power and life but the display is spoilt/damaged hence nothing appears?
Do you know of any further test to rule in/out a dead screen?
Thanks
|
|
2013-01-09
, 14:42
|
|
Moderator |
Posts: 6,215 |
Thanked: 6,400 times |
Joined on Nov 2011
|
#455
|
Originally Posted by robthebold
Do you know of any further test to rule in/out a dead screen?
Not sure of any further test; since you've flashed your device you can't SSH in too so it can't be confirmed that the device is working and screen spoilt... But my guess would be on a damaged screen...
Maybe someone else can help out too; try pinging Hurrian or juiceme or jonni on #harmattan on freenode as they know much more about hardware...
| The Following User Says Thank You to thedead1440 For This Useful Post: | ||
|
|
2013-01-09
, 15:20
|
|
Posts: 1,038 |
Thanked: 3,980 times |
Joined on Nov 2010
@ USA
|
#456
|
thedead1440
I remember reading in one of your posts (IIRC) you gave another user a contact to ask about US warranty service for his N9. But I don't remember enough to successfully search out the post. Would you repeat that here or message me, please, if it's ok with him/her?
Thanks
I remember reading in one of your posts (IIRC) you gave another user a contact to ask about US warranty service for his N9. But I don't remember enough to successfully search out the post. Would you repeat that here or message me, please, if it's ok with him/her?
Thanks
|
|
2013-01-10
, 12:09
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#457
|
There is a quick way to boot the device to maintanance mode and telnet into it. This would make sure if the problem is indeed the screen or if the device does not boot at all.
Get my MOSLO based maintanance boot from svn repository;
"svn co https://toosa.swagman.org/svn/sillykbd/TRUNK/moslo", and have a look at the README file for details.
If you can telnet to the device you can be sure it's just the screen that is broken.
Also, you can manually export your mmcblk partition via the USB connection to take backup on external PC, if you for example need to send the device for repair.
Get my MOSLO based maintanance boot from svn repository;
"svn co https://toosa.swagman.org/svn/sillykbd/TRUNK/moslo", and have a look at the README file for details.
If you can telnet to the device you can be sure it's just the screen that is broken.
Also, you can manually export your mmcblk partition via the USB connection to take backup on external PC, if you for example need to send the device for repair.
| The Following 7 Users Say Thank You to juiceme For This Useful Post: | ||
|
|
2013-01-10
, 14:14
|
|
Posts: 8 |
Thanked: 0 times |
Joined on Jan 2013
|
#458
|
Originally Posted by juiceme
Tried it, but still no change,
There is a quick way to boot the device to maintanance mode and telnet into it. This would make sure if the problem is indeed the screen or if the device does not boot at all.
Get my MOSLO based maintanance boot from svn repository;
"svn co https://toosa.swagman.org/svn/sillykbd/TRUNK/moslo", and have a look at the README file for details.
If you can telnet to the device you can be sure it's just the screen that is broken.
Also, you can manually export your mmcblk partition via the USB connection to take backup on external PC, if you for example need to send the device for repair.
I can't set an IP address to to the phone because it will not stay connected to the PC with a custom kernel. Probably why I can't clear the MALF state either.
dmesg gives me:
Code:
[ 915.000065] usb 1-2: new high speed USB device using ehci_hcd and address 17 [ 918.154552] usb 1-2: USB disconnect, address 17 [ 920.030081] usb 1-2: new high speed USB device using ehci_hcd and address 18 [ 920.762702] usb 1-2: USB disconnect, address 18
After it disconnects, lsusb won't list the phone - it's as if it wasn't connected to the computer at all.
With just
Code:
sudo flasher -i
Code:
Bus 001 Device 024: ID 0421:0105 Nokia Mobile Phones Nokia Firmware Upgrade Mode
I bought a replacement screen for the phone from eBay so I don't believe that it's faulty. It COULD be a faulty sensor, but I really doubt it because I just replaced it as well..
|
|
2013-01-10
, 16:01
|
|
Posts: 1,038 |
Thanked: 3,980 times |
Joined on Nov 2010
@ USA
|
#459
|
Originally Posted by juiceme
Thanks very much.
There is a quick way to boot the device to maintanance mode and telnet into it. This would make sure if the problem is indeed the screen or if the device does not boot at all.
Okay, I can telnet in to device. (Took me a little while, since everything I know about usb networking fits in a thimble, and I was using 192.168.2.* as my local LAN, so using offline device finally did the trick.
)Anyway, I can see the root directory with "ls" and I can ping back to the USB host PC, so I guess the phone has booted up. From what you wrote, I gather the screen is dead but the phone lives. Anything else I should test before attempting to get it fixed?
Thanks again,
Rob
|
|
2013-01-10
, 16:45
|
|
Posts: 8 |
Thanked: 0 times |
Joined on Jan 2013
|
#460
|
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.
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.
 |
| Tags |
| flashing, nokia n9 |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
All times are GMT. The time now is 04:49.
Most of it should be in meta.db located in ~/.cache/tracker/meta.db
Last edited by thedead1440; 2013-01-09 at 14:55.