Did I really kill my n900? - Page 2 - maemo.org

giff53 | # 11 | 2011-12-16, 09:21 | Report

Originally Posted by king Ralphred View Post

I have also tried another charger and although it said it was charging, the battery still went flat. I checked the milliamps and it was 300. the n900 charger is 1200 ma. Just a thought, your charger may not be kicking out enough juice.

Thanks. But no, it's not the charger nor the battery, since I have changed the battery to the one of my girlfriend's n900, fully charged using the official charger.

And by the way, when I plug it to the charger, the same looping behavior as described earlier appears (yellow led and faded nokia sign)...

Last edited by giff53; 2011-12-16 at 09:23.

freemangordon | # 12 | 2011-12-16, 09:37 | Report

Seems like bootloader is KO, so try to cold flash it (google on how to do that). It is tricky, but it can be done.

The Following User Says Thank You to freemangordon For This Useful Post:
Estel

giff53 | # 13 | 2011-12-16, 10:06 | Report

Originally Posted by freemangordon View Post

Seems like bootloader is KO, so try to cold flash it (google on how to do that). It is tricky, but it can be done.

Thanks. I am reading here about cold flashing:

http://wiki.maemo.org/Flasher

It says I have to give the "hw revision number" as an argument to the flasher. Do you know how to find out which number is my device, given that I can't turn it on?

Tried a few numbers, nothing, the flasher does not see the device...

Last edited by giff53; 2011-12-16 at 10:22.

freemangordon | # 14 | 2011-12-16, 10:58 | Report

Originally Posted by giff53 View Post

Thanks. I am reading here about cold flashing:

http://wiki.maemo.org/Flasher

It says I have to give the "hw revision number" as an argument to the flasher. Do you know how to find out which number is my device, given that I can't turn it on?

Tried a few numbers, nothing, the flasher does not see the device...

Hmm, I don't think you can find your HW revision. Could be wrong anyway.

BTW by saying "tricky" I mean that there is a very short interval (about 200ms or so) flasher to see your device. You need to be persistent

, i.e. it will see it once every 15-20 tries. Or it cannot see it at all and you need to try on a different PC.

EDIT:
The procedure for putting device in cold-flash mode (as long as I can remember) is:

with flasher running

1. disconnect USB cable
2. remove the battery
3. connect USB cable
4. insert the battery

if nothing happens go back to 1

Last edited by freemangordon; 2011-12-16 at 11:07.

The Following 2 Users Say Thank You to freemangordon For This Useful Post:
Estel, giff53

giff53 | # 15 | 2011-12-16, 11:13 | Report

Originally Posted by freemangordon View Post

BTW by saying "tricky" I mean that there is a very short interval (about 200ms or so) flasher to see your device. You need to be persistent

, i.e. it will see it once every 15-20 tries. Or it cannot see it at all and you need to try on a different PC.

EDIT:
The procedure for putting device in cold-flash mode (as long as I can remember) is:

Thanks for the help. To cold flash I do simply thsi:

$ flasher-3.5 -c -h RX-51:<hw_id> -F <FIASCO image> -f

Do I need to hold the u when inserting the battery?

So after a few trials of plugging in and and out the battery, something moved:

Suitable USB device not found, waiting.
USB device found found at bus 002, device address 003.
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 34 30 07 57 13 02 01 00 12 15 01 df
e3 44 e2 22 fe ec a5 d1 d4 6b e7 53 03 a9 02 87
de 51 6b 14 15 01 87 3b 4d cd ca f5 44 4d 24 ec
b2 ac 95 53 88 41 4f ab cd 66 15 09 01 f7 48 8f
28 a0 27 e5 b3
Sending 2nd image (14720 bytes)... done.
Sending ping... timeout!
failed.
Sending ping... pong.
Sending secondary (109440 bytes)... done.
Suitable USB device not found, waiting.

it all was very quick! Ideas?

Last edited by giff53; 2011-12-16 at 11:25.

The Following User Says Thank You to giff53 For This Useful Post:
Estel

freemangordon | # 16 | 2011-12-16, 11:30 | Report

Originally Posted by giff53 View Post

Thanks for the help. To cold flash I do simply thsi:

$ flasher-3.5 -c -h RX-51:<hw_id> -F <FIASCO image> -f

Do I need to hold the u when inserting the battery?

An additional parameter is needed (something about to use USB for serial port).
You don't need 'u' pressed. And try first to flash only bootloader or bootloader and kernel, not the whole rootfs, it will save you a lot of restoring.

The Following 3 Users Say Thank You to freemangordon For This Useful Post:
Estel, giff53, nkirk

giff53 | # 17 | 2011-12-16, 11:37 | Report

Originally Posted by freemangordon View Post

An additional parameter is needed (something about to use USB for serial port).
You don't need 'u' pressed. And try first to flash only bootloader or bootloader and kernel, not the whole rootfs, it will save you a lot of restoring.

You are right, it does not work without the usb post argument.

I am flashing this one:

RX-51_2009SE_2.2009.51-1.002_PCOMBINED_002_ARM.bin

What should I flash to limit myself to the bootloader?

The above behavior of the flasher outputting that matix of numbers appears only once, that is, if I want that to happen again I have to restart the flasher, and it happens when I start the flasher with the cable plugged and the battery in, remove the battery, and finally plug it back it. At that stage the phone shakes and the nokia faded logo appears...

The Following User Says Thank You to giff53 For This Useful Post:
Estel

karam | # 18 | 2011-12-16, 12:18 | Report

that happened with me once
the problem was actually caused by windows XP (it was not detecting my N900 with flasher) neither linux did (i didn't know why)

just changed to windows 7 and it detected it
after that i made another reflash with linux (and it worked) tried with XP again (and it worked)

...so
you may wanna try to change the windows you are using and try plugging N900 in different USB ports
don't forget to have a charged battery first
that's all what i can say

freemangordon | # 19 | 2011-12-16, 12:36 | Report

Originally Posted by giff53 View Post

You are right, it does not work without the usb post argument.

I am flashing this one:

RX-51_2009SE_2.2009.51-1.002_PCOMBINED_002_ARM.bin

What should I flash to limit myself to the bootloader?

There should be an option like -flash-only=nolo (for bootloader). Read flasher documentation on how to flash only the kernel.

Originally Posted by

The above behavior of the flasher outputting that matix of numbers appears only once, that is, if I want that to happen again I have to restart the flasher, and it happens when I start the flasher with the cable plugged and the battery in, remove the battery, and finally plug it back it. At that stage the phone shakes and the nokia faded logo appears...

And the above behaviour with matrix of numbers is?

EDIT:

The firmware you are flashing seems outdated, there should be 2 newer firmwares available.

The Following User Says Thank You to freemangordon For This Useful Post:
Estel

giff53 | # 20 | 2011-12-16, 12:50 | Report

Originally Posted by freemangordon View Post

There should be an option like -flash-only=nolo (for bootloader). Read flasher documentation on how to flash only the kernel.

And the above behaviour with matrix of numbers is?

EDIT:

The firmware you are flashing seems outdated, there should be 2 newer firmwares available.

Thanks for spotting the option to flash only the bootloader. The doc is all in here, isn't it?

http://wiki.maemo.org/Flasher

This is the ' above behaviour with matrix of numbers', output of the flasher:

Suitable USB device not found, waiting.
USB device found found at bus 002, device address 003.
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 34 30 07 57 13 02 01 00 12 15 01 df
e3 44 e2 22 fe ec a5 d1 d4 6b e7 53 03 a9 02 87
de 51 6b 14 15 01 87 3b 4d cd ca f5 44 4d 24 ec
b2 ac 95 53 88 41 4f ab cd 66 15 09 01 f7 48 8f
28 a0 27 e5 b3
Sending 2nd image (14720 bytes)... done.
Sending ping... timeout!
failed.
Sending ping... pong.
Sending secondary (109440 bytes)... done.
Suitable USB device not found, waiting.

And yes, that is an old firmware, I was in fact flashing the newest one, just wrote it wrong.

Gonna try now again... naaa, same story...

Last edited by giff53; 2011-12-16 at 13:03.