I'm not familiar with flashing under windows but I'm sure N900 is not meant to dim screen and show yellow/amber LED. During the entire flashing operation (especially without -R specified) your device should still display Nokia screen

I personally use linux here myself. I find that linux doesn't start autoprobing and asking for drivers if the drivers are not there. In other words, its more well behaved than with windows where you have to go around disabling new hardwares being detected

I still don't know why would N900 all of the sudden loses connectivity to the cellular network. It could be anything from a faulty board to maybe dirty contacts or even possibly swapping SIM cards out constantly

about phone stuff, everybody wants everything in a little shiny smartphone, and i'm a developer too, so i want a stylish advanced smartphone that do all the stuff like playing calling messaging and programs ...

I hate to own a smartphone with a smaller screen.. it seems already I have grown accustomed to N900's screen.. web browsing is already difficult as it is and any downsizing would mean I need to zoom into pages more and more

psycho_oreos: usually flashing of cmt FW either works or fails but shouldn't break the IMEI readout. However there might be cases where reflashing COMBINED also reflashes cmt FW and thus fixes some glitch

and for the record i opened up the device twice, and the last time i sprayed and checked the antenna connectors and pulled them up and did other things, it was ok after that! but 8 or 10 hour later the error aperas . so i think it is definitly hardware .

btw, I have one more issue. When I reboot, I can't connect anything-nothing shows up. I had set it to unload wifi drivers when it boots. When I click to load wifi driver, it turns to normal, then I can see GPRS and wifi connections. After I click to unload wifi driver again, everything is normal, can't see wifi connections but GPRS ones. At the beginning I don't see any of them.

QuickConnect failed ((null)): Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

"If "boolean:true" at the end, one-line notification saying "No saved connections available" appears. Maybe affects more than that? Most likely, boolean:true leads to using saved connections if there are any, and boolean:false forces to display the connection dialog. "

Let me try to explain again, if I try to connect just after startup nothing happens, can't even choose which connection to use. But if I load wifi driver, then everything is ok, can unload wifi after that, it is just as to be.

in this case I would need to install the crappy app to get to know what it does and how it does that, or I had to study the friggin sourcecode to the last line. Can't see any of both happening in the near future

and this friggin maemo.org/packages interface could need some maintenance - it takes like 120s after clicking "send" on a comment, and if you dare to click again during that time where page is in reload limbo, the commet gets sent multiple times :-S

i can enable and disable the location on settings but there is no satellite icon on the top, and phone functionality is neither working . and i failed flashing and it was still on the line flashing done ... and no CMT flashed successful message .

pali, what do you get if you open xterm or ssh and type sysinfo-tool -g /certs/ccc/pp/default-language and sysinfo-tool -g /certs/ccc/pp/keyboard-layout and sysinfo-tool -g /certs/ccc/pp/content-region