Reply
Thread Tools
Posts: 5 | Thanked: 0 times | Joined on Jan 2007
#21
My 800 is toast as well. I tried to add a feed and it went into the reboot loop described above. Nokia needs to figure out quality control - this is sad.
 
Posts: 32 | Thanked: 0 times | Joined on Jan 2007
#22
Probably it's too late for advice, but I found similar (if not such severe in case of RSS access) problem with mine N800, caused by the fact that RSS feed app is configured to do automatic update by default. It does this every 30 minutes, and also on startup, if network connection is available. Note, that connection manager is also by default configured to establish connection automatically at startup, if available. It does this even before the GUI is started so you can't prevent this. Now, as soon as connection is established at later stages of bootup sequence and the RSS app tries to get a feed update -- it crashes hard and the system goes to reboot again, thus you get your reboot loop. To get rid of it you need to switch off your wireless AP or get away from whatever AP is configured as your default WLAN connection, reboot and disable automatic WLAN connection and also disable automatic RSS updates. Anyway, this is an indication of of a serious hardware bug, probably the same kind my unit had, so I recommend returning it.
 
Posts: 209 | Thanked: 8 times | Joined on Nov 2005 @ Fishers, Indiana
#23
Originally Posted by ju55i View Post
How long is flashing supposed to take? Mine goes through in less then a minute. Is that a normal time?
Yes, that's about right for a USB 2.0 connection. It makes a huge difference in flashing time.

Larry
 
Posts: 46 | Thanked: 1 time | Joined on Jan 2007 @ Tampere, Finland
#24
Unfortunately I'm joining the club... I tried to install Maemo Mapper using this guide: Guide
After it finished everything was OK, but after turning it off it doesn't go on anymore. When turning it on, it shows the white screen, with Nokia logo on it, for couple of seconds and then turns off.

I ordered from Nokia and it took a week to get it to Finland and I wouldn't want to send it somewhere again. Luckily girlfriend worked in a company that fixes Nokia's phones so I'll try to find out if they can fix this too...

But it really seems that there is something wrong with this because so many reports about the same problem.
 
Posts: 4 | Thanked: 0 times | Joined on Jan 2007 @ Jyväskylä, Finland
#25
I got my N800 back to its feets by using these instructions:
http://maemo.org/pipermail/maemo-use...ry/002768.html

Basicly you put your N800 to R&D mode, set flag, reflash, unset flag and then reboot. After succesful boot you can set the R&D mode off. That worked for me!
 
Posts: 3 | Thanked: 0 times | Joined on Jan 2007
#26
Originally Posted by ju55i View Post
I got my N800 back to its feets by using these instructions:
http://maemo.org/pipermail/maemo-use...ry/002768.html

Basicly you put your N800 to R&D mode, set flag, reflash, unset flag and then reboot. After succesful boot you can set the R&D mode off. That worked for me!
Well, that makes me feel a little safer... I, too, am on my second N800 from CompUSA. Installed MaemoMapper as described in the guide upthread, managed to crash it, and got into a reboot loop. After pulling battery, plugging in charger, USB, etc., it finally ended up not booting at all - would power up for a few seconds on the "Nokia" screen, go white, then shut itself off. This even persisted through a normal (and allegedly "successful") reflash, so I decided to exchange it for a new unit while I still could.

Frankly, it scares the crap out of me to think that this thing is so "fragile" that it could be rendered inert by software, and unrecoverable even by reflashing the firmware! Here's hoping I never have to try that reflashing trick with R&D mode myself, but I'm glad to know about it just in case...

--John
 
Posts: 46 | Thanked: 1 time | Joined on Jan 2007 @ Tampere, Finland
#27
Originally Posted by ju55i View Post
I got my N800 back to its feets by using these instructions:
http://maemo.org/pipermail/maemo-use...ry/002768.html

Basicly you put your N800 to R&D mode, set flag, reflash, unset flag and then reboot. After succesful boot you can set the R&D mode off. That worked for me!
This sounds interesting. So does that mean that first you run flash-command with that flag-setting included, like this:
./flasher-3.0 -F RX-34_2007SE_2.2006.51-6_PR_COMBINED_MR0_ARM.bin -f -R --set-rd-flags=no-lifeguard-reset
(all that together)

But what you run after that?
./flasher-3.0 --clear-rd-flags=no-lifeguard-reset ??


Now I'm thinking that should I go get my N800 back from service center and try this..
 
Posts: 3,401 | Thanked: 1,255 times | Joined on Nov 2005 @ London, UK
#28
@Gluz

Just "./flasher-3.0 --set-rd-flags=no-lifeguard-reset" alone may fix a N800 that is stuck in a reboot loop. The device may be rebooting because an application is consuming to much CPU at startup in which case the lifeguard reset feature kicks in and reboots the N800. If you disable the lifeguard reset the N800 may make it through the boot process. Once you identify the rogue application and remove it/stop it misbehaving you can then re-enable the lifeguard reset with:

./flasher-3.0 --clear-rd-flags=no-lifeguard-reset

Reflashing with a new image is a last resort if all else fails!
 

The Following 2 Users Say Thank You to Milhouse For This Useful Post:
Posts: 46 | Thanked: 1 time | Joined on Jan 2007 @ Tampere, Finland
#29
Originally Posted by Milhouse View Post
@Gluz

Just "./flasher-3.0 --set-rd-flags=no-lifeguard-reset" alone may fix a N800 that is stuck in a reboot loop. The device may be rebooting because an application is consuming to much CPU at startup in which case the lifeguard reset feature kicks in and reboots the N800. If you disable the lifeguard reset the N800 may make it through the boot process. Once you identify the rogue application and remove it/stop it misbehaving you can then re-enable the lifeguard reset with:

./flasher-3.0 --clear-rd-flags=no-lifeguard-reset

Reflashing with a new image is a last resort if all else fails!
Ok, thanks

I have flashed it already couple of times, so I thinks it "empty" already. But I'll give it a try if I can get it back today.
 
Posts: 147 | Thanked: 5 times | Joined on Jan 2007
#30
Do I need a Linux box to do ./flasher-3.0 --clear-rd-flags=no-lifeguard-reset ?

Can I use the Windows flasher to do the same thing? Perhaps by editing its config file?

I am getting reboots every three or four seconds. I've flashed it four times now, and the same thing keeps happening. Turning off my wifi does not help (although the reboots coming so quickly suggests to me that it isn't the RSS problem).
 
Reply


 
Forum Jump


All times are GMT. The time now is 19:30.