Recieved further follow up email from portagadgets, but no additional information. Again, these guys have been great, and I would definitely purchase from them in future.

I now have externel battery charger, and successfully cold flashed device. Here is output:

C:\Program Files\maemo\flasher-3.5>flasher-3.5.exe -c -h RX-51:2101 -S usb -F RX
-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin -f
flasher v2.5.2 (Sep 24 2009)

SW version in image: RX-51_2009SE_20.2010.36-2_PR_MR0
Image 'kernel', size 1705 kB
Version 2.6.28-20103103+0m5
Image 'rootfs', size 185728 kB
Version RX-51_2009SE_20.2010.36-2_PR_MR0
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.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.9+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.9+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.9+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.9+0m5
Using serial port usb
Suitable USB device not found, waiting.
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
106.
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 34 30 07 57 13 02 01 00 12 15 01 30
af 1b a5 39 63 46 15 0b bb cd 4e a5 e8 12 8b 64
7f 23 5d 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 (zu bytes)... done.
Sending ping... usb_bulk_read: No error
failed.
Sending ping... pong.
Sending secondary (zu bytes)... done.
Suitable USB device not found, waiting.
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
105.
Found device RX-51, hardware revision 2204
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_20.2010.36-2.206.1_PR_206
Overriding revision information given by board.
Sending xloader image (14 kB)...
100% (14 of 0 kB, avg. 14 kB/s)
Sending secondary image (106 kB)...
100% (106 of 0 kB, avg. 106 kB/s)
Flashing bootloader... done.
Sending cmt-2nd image (79 kB)...
100% (79 of 0 kB, avg. 79 kB/s)
Sending cmt-algo image (507 kB)...
100% (507 of 0 kB, avg. 507 kB/s)
Sending cmt-mcusw image (5826 kB)...
100% (5826 of 0 kB, avg. 5826 kB/s)
Flashing cmt-mcusw... done.
Sending kernel image (1705 kB)...
100% (1705 of 0 kB, avg. 1705 kB/s)
Flashing kernel... done.
Sending and flashing rootfs image (185728 kB)...
100% (185728 of 0 kB, avg. 185728 kB/s)
Finishing flashing... done
CMT flashed successfully

I then tried to flash emmc, here is output:

C:\Program Files\maemo\flasher-3.5>flasher-3.5.exe -F RX-51_2009SE_10.2010.13-2.
VANILLA_PR_EMMC_MR0_ARM.bin -f
flasher v2.5.2 (Sep 24 2009)

Image 'mmc', size 255947 kB
Version RX-51_2009SE_10.2010.13-2.VANILLA
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
105.
Found device RX-51, hardware revision 2204
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_20.2010.36-2_PR_MR0
Booting device into flash mode.
Suitable USB device not found, waiting.
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
1c8.
Raw data transfer EP found at EP2.
Image(s) flashed successfully in 28.015 s (9135 kB/s)!

Device won't boot, and I am having trouble getting flasher3.5 to see it when connected via USB. Holding 'u' will not put n900 into flash mode, i am going to experiment with live linux distro to gain more control over usb port. I have tried flashing with 2 different notebooks now, one winxp SP3, one vista starter

looking at output, i flashed with wrong parameters for device, my device is hardware revision 2204, i flashed 2101

coldflashing in linux now, i am not sure, i think i should flash mmc again before reboot, for this first time i will flash fiasco with normal flash as well, so will be cold flash -> emmc -> fiasco...

...can't get it to boot, having trouble performing uninterrupted boot between pr1.3 and mmc, dunno. Probably play around later, and then take to repair centre.

...I can flash phone normally now, but holding "u" will not halt phone in flash ready state. When flashing mmc the phone appears to start loading OS, but flash proceeds and is reported successful on laptop. When flashing OS, a green bar appears on the n900 and fills to completion, and flash is reported successful on laptop. I'll post outputs later.
Device will not boot, halts on flashing dots after cycling a few times, powers off.

Interesting thread, my N900 also shut down whilst plugged into a car charger. Now in endlessly reboots when connected to pc via usb or mains charger. I can't get it to boot past the 5 dots, it always highlights the middle doot and then shuts down.

I've quickly read this whole thread, is there anything I can do to fix my phone. It's been suggested i try flashing the framebuffer kernel.

Does this mean I need to flash 1.3 then flash the emmc?

Any help would be greatly appreciated.

p.s. I did have backupmenu installed, which allowed me to copy off my files. But when I reflashed 1.3 this has gone.

Thanks

Steven

Screw emmc, just flash 1.3 *then* framebuffer kernel - you'll be able to see on which part of booting process something goes wrong.

This way, people have un-puzzled most mysterious problems, like guy, whose device stopped accepting any batteries (via wrong BSI raw values - of course that was conclusion, at the beginning we haven't got a clue what's going on. Long story short, it was semi-fixed by using modified getbootstate).

what is and where can I find frame kernelbuffer?

Thanks in advance.

forum /search
wiki /search

I'm not providing "just links", because You need to read about it before using - it's not fool proof. More you read about usage during search, the higher chance of succeeding You have.

A service centre flash will quite possibly fix (portagadgets flashed my device and fixed). So, maybe flashing with phoenix will fix (long stretch), dunno (I absolutely do not know what im talking about here, but there are a couple of reports on internet of people flashing successfully with phoenix). I'm going to do a few more flashes over weekend (pr1.2) , then send to nokia.
Portagadgets told me no hardware replacement was needed to fix, and they just flashed device.

I can't find frame buffer kernel page by searching, there is a link to the file in the first page in this thread, but i can't find any page explaining its use.
When I installed it, the text flashed too quickly to see what was going on.

here is page describing flashing with phoenix,
http://gsmobserver.blogspot.com/2010...h-phoenix.html

@ziggadebo, did you encounter problem when turning ignition with n900 plugged in? i did

My N900 was happily plugged into car charger, playing ACDC through rockbox at an obscene volume, when it made a pop sound and shutdown.

I'll be returning mine to the service provider today, I beleive it's in warranty as I have a two year contract.

I did get it to boot last night in R&D mode, but the battery was critical and after a couple of minutes shutdown

Now I can't charge it, so I'm going to have to hope it can be repaired and not replaced with a lesser phone.

off-topic - your posts, guys, just made me suddenly not willing to plug my N900 into any cheap car chargers...[/off-topic]

I'm just wondering what the hell can make such accidents. N900 contain overvoltage and overcurrent protection... The charger suddenly gave high voltage to data pins, or what?