800 boots 3 seconds then dies.... [Archive] - maemo.org

Adam in NYC

01-25-2007, 10:22 AM

Hello there from Adam in NYC.

Shipping my Nokia 800 back to the factory.

It is just booting for 3 seconds then turning off. Looks like maybe I am one of the first to send it back. To those in the USA, the number for repair is here: http://www.nokiausa.com/support/repair/main/1,2846,,00.html#Step1

and they are very helpful. In the US, repairs go back to to a repair depot in Huntsville Alabama.

One point to ponder: my N800 was made in Korea, if that helps. I had 4 Gig of SD in it. Noope, no mods, just using it with xterm.

Another point is that when it died, I could not get it to go into the control panel /Bluetooth to find my BT keyboard. Afterwards, I rebooted and it is doing this quick reboot then die behavior. I reflashed but no go with this. The tablet wont even recharge the battery.

It would be nice if there was a way to do a wipe of all the FLASH so you can get a superclean wipe.

Anyway, the tech support did not even know they moved the sticker from out under the battery. Now they know.

Oh well.

EddieNYC

01-25-2007, 11:34 AM

I reflashed yesterday after memory problems and reboots and I was hanging out at the 34th street mall, trying to get a signal and my N800 kept rebooting, rebooting, and rebooting.

It was very upsetting. I have 2 -2GB memory cards.

I am going to exchange mine at the Nokia store later today. It could be a fluke.

Regrettably, when deliveries are made, the Nokia store probably got nothing but the Korean made one... :(

ziggamon

01-28-2007, 10:11 AM

Are you sure you've loaded the batteries properly?

lbattraw

01-28-2007, 10:49 AM

Hello there from Adam in NYC.

Shipping my Nokia 800 back to the factory.

It is just booting for 3 seconds then turning off. Looks like maybe I am one of the first to send it back.
(snip)

This is a known issue which occurs when you upgrade busybox to the latest version from the maemo repository. If you just accept any updates that are pending in the application manager it will grab busybox automatically (in red pill mode). Happened to me twice and it was rather annoying. Just reflashing will not fix it. I believe you need to disable R&D mode, flash, and then re-enable R&D mode to make it work. There was a thread about this earlier with quite a few people returning their n800's before the solution was discovered. To the best of my knowledge that "poison" version is still out there and I'm not sure why Nokia doesn't just pull it to avoid these issues.

Larry

aflegg

01-28-2007, 12:36 PM

I'm not sure why Nokia doesn't just pull it to avoid these issues

Three reasons:

1) The upgrade is for Maemo ARM targets in Scratchbox.
2) The repository in question isn't *designed* for the N800, just the scratchbox SDK - it's a side effect that most packages work on the device itself
3) Red pill mode isn't for end users. If you follow maemo-developers, you'll know not to accept an upgrade in red pill mode. If you've got red pill mode enabled and you don't follow maemo-developers a lot of problems will result.

lbattraw

01-28-2007, 08:05 PM

Three reasons:

1) The upgrade is for Maemo ARM targets in Scratchbox.
2) The repository in question isn't *designed* for the N800, just the scratchbox SDK - it's a side effect that most packages work on the device itself
3) Red pill mode isn't for end users. If you follow maemo-developers, you'll know not to accept an upgrade in red pill mode. If you've got red pill mode enabled and you don't follow maemo-developers a lot of problems will result.

I don't think it's reasonable to assume this. I ran my 770 in that mode without issues and unless I was pulling from the sardine repos I never had problems. Some people like to be able to install command line utilities that are invisible otherwise from the app manager. To have a version of scratchbox that's guaranteed to not only trash the device but it make it difficult to recover from even after re-flashing seems unwise. Thus far I've seen at least six different posts by people who have returned their n800s because of this issue. What a waste of money and time, for something that could be simply remedied by removing the package.

I hang out on maemo-devel and I must have missed the message that said don't upgrade scratchbox. Nonetheless, for j-random-user who wants to install a utility like 'unzip', there's very little chance they're going to know next time they go to accept packages for upgrade that scratchbox is going to destroy their tablet for all intents and purposes. Now Nokia is getting a reputation for crash-prone n800s is doesn't really deserve. Worse, people are confusing it with a hardware defect the 770s had. It doesn't help that they'll never see the problem until they reboot, making it seem like something else entirely is wrong since it occurs so early on in the boot process.

Larry

penguinbait

01-28-2007, 11:06 PM

I think there is a couple of different issues going on. I have now just toasted my second N800. Just as the first one and as this title states "boots 3 seconds and dies"

I compiled the kernel and everything went fine, used the linux flasher-3.0 and flashed the kernel, and it would not boot. OK, no problem, used the flasher and unacked the original kernel image from Nokia image, flashed the original kernel back. Booted up and died. WTF, ok I will reflash the whole thing, used the flasher-3.0 and it started to flash, xloader ok, initfs ok, kernel wrote 256 and hung. After I was sure it was not comming back, I unplugged it and killed the process, it took a few but finally died. I tried again same thing but hangs at 512 written. Hearts racing, danm it. OK, Try in windows, flashes completely, thank goodness. Oh wait, still wont boot. Crap! 21 days will be tomorrow morning, we'll see how happy COMPUSA will be to replace the second one.

I tried all kinds of various things after the above to bring it back. I started having problems where I could not even turn it on. I held home plugged in the usb and put in the power cord and was able to reflash again. This brought it back to be able to power on again, but still no boot, reflash linux, reflash windows, reflash, kernel, initfs, rootfs manually. I think there is an issue where something is writing to the wrong place on flash memory. Not really sure though. I

Is there a way to unpack the entire image, mine always dies after unpacking kernel, rootfs, initfs, 2nd image dies? Is this what is needed for cold flash, would cold flash possibly fix it, i dont know. POOOOP!!!!

ANY BRAINIACS GOT ANYTHING TO TRY.

Milhouse

01-28-2007, 11:21 PM

Have you removed the SD cards before booting?

penguinbait

01-29-2007, 08:24 AM

yes , I removed everything, nothing seems to be working, I am leaning towards flash corruption (physical or caused by flasher), I would not be surprised if we get a new flasher sometime in the future, it may have something to do with the devices state when flashing? The first time this happened to me I was using only the windows flasher when it died, this time it was the linux flasher. The first time it was reflashed maybe 3 times. The second one was reflashed from windows and linux multiple (15+ times when testing bootmenu) without issues before this problem.

I am so tempted to replace this with the 770 at COMPUSA. This will be my second n800 to die, I had 770 for over a year and never had an issue. I could never do it though, no matter how much I would like to.

penguinbait

01-29-2007, 10:42 AM

OK, did I ever mention I love :rolleyes:COMPUSA

I took back my N800 in the box with all the parts and papers, with reciept with copies in a nice little folder, prepared for the worst. 21 day return policy, I took it back today on day 21. Without me even asking a question, she looked inside the box, went and got me a new one, did a return on it, and gave me a NEW reciept with 21more days of return policy. I also purchased a TAP replacement plan, but I did not have to use it because I was within my 21 days, barely:D

This is why I would never ever ever ever ever again buy directly from Nokia.

This being said I am very hesitant to try my kernel image again, I am 99% sure it had nothing to do with my problem, but I am hesitant to find out. I think I can boot new kernel without applying it can't I. maybe I'll give that a try.

lbattraw

01-29-2007, 05:24 PM

I think there is a couple of different issues going on. I have now just toasted my second N800. Just as the first one and as this title states "boots 3 seconds and dies"
(snip)

Is there a way to unpack the entire image, mine always dies after unpacking kernel, rootfs, initfs, 2nd image dies? Is this what is needed for cold flash, would cold flash possibly fix it, i dont know. POOOOP!!!!

ANY BRAINIACS GOT ANYTHING TO TRY.

Did you try enabling/disabling R&D mode before and after flashing like I suggested? I went through the same process you did, flashing the entire thing, just the initfs, etc. Nothing fixed it until I toggled R&D mode before flashing, and then again after I flashed. Honestly I can't remember if I turned it off then flashed, then turned it back on or the other way around. The end result was it stopped the 3-second powerdown/reboot cycle when nothing else would touch it. Cold flashing is not an option since you need a serial connection to the port on the device. Sorry to hear you had to go through the hassle of replacing it.

Larry

penguinbait

01-29-2007, 06:17 PM

I did try, r n d mode enable, flash, disable, notthing, flashed every way I could think of. If I was not at day 21 on my return policy, I would have played more, but I am going to avoid Nokia repair, at all costs.:cool:

lbattraw: Did you have a reboot loop or a 3sec powerdown? From what I have seen, reboot loop is software issue, and will be fixed by flashing. 3sec powerdown is not fixed by flashing. Anybody else want to chime in here????

Its not really a problem, I just reflashed, reinstalled becomeroot, xterm, bootmenu, and booted off my mmc card, the only thing I had to do was re-pair all my bluetooth devices. since my bt mac changed - Thanks Again Fanoush, I love bootmenu...

lbattraw

01-29-2007, 08:34 PM

Adam in NYC

01-30-2007, 04:02 PM

lbattraw: Did you have a reboot loop or a 3sec powerdown? From what I have seen, reboot loop is software issue, and will be fixed by flashing. 3sec powerdown is not fixed by flashing. Anybody else want to chime in here????

Its not really a problem, I just reflashed, reinstalled becomeroot, xterm, bootmenu, and booted off my mmc card, the only thing I had to do was re-pair all my bluetooth devices. since my bt mac changed - Thanks Again Fanoush, I love bootmenu...

Adam again. I can't get control unless I have the USB cable plugged into a live computer. Yep, it is flash problem. That is what you will get when you use large presistent flash along with data structures that will trash a linux box. I wish they had put a real reset button in the box. You can go into USB mode but can't jump into a monitor.

Great. I miss my old machines with a monitor builtin.

Never installed bootmenu and should have in hindsight.

penguinbait

01-30-2007, 04:48 PM

OMG

I killed another one for no apparrent reason. This one I bought yesterday, I was running, it crashed and shut down. Now its boots 3secs and dies. I have 20 days left to return, but I will probably play tonight to recover it. If I am unable to recover I will return it and not get another one. The first one lasted 7 days, the second one lasted 14 days, the third one lasted 1 day, OK, maybe about 30hours.

This is just nuts, if I new how to recover it I would probably keep it, but this is insane and Nokia support sucks, maybe I will give them a call and see what they say, but I am sure it will be send it in, which aint gonna happen.

Ugh!! I wish I knew why this was happening, I have heard of a few people with this problem, but it seems like I am special or something. 3 of these things I have killed now.

Adam in NYC

01-30-2007, 05:08 PM

Have you removed the SD cards before booting?

Yes, there is no difference with or without the SD cards.

Milhouse

01-30-2007, 05:30 PM

Xyzo

01-30-2007, 05:31 PM

Hi,
I've encountered the same problem yesterday: my N800 was booting every 3 seconds. I've tried multiple re-flashes: no hope :( until I've found a solution by googling: enabling RD mode and setting the 'no-lifeguard-reset' flag. After this, I've been able to reboot normally.
Well, I wasn't aware of the busybox upgrade problem, but that's true that, as I was using RedPill mode, I've upgraded to busybox.xxx.sdk2, and today I've re-upgraded to busybox.xxx.sdk3 but the N800 is stil working well, no reboot: is this new release (ie. .sdk3) supposed to fix the problem?
Anyway, after having read this thread, I suppose that I shouldn't have downloaded and installed busybox update, right? I think I'm going to reflash tomorrow to uninstall the upgrade :rolleyes:

Adam in NYC

01-30-2007, 05:39 PM

If you remove the lifeguard (the watchdog), then if you lock it out, you won't be able to recover. Supertight lockup, no?

Adam in NYC

01-30-2007, 05:46 PM

These constant reboots seem to be a serious cause for concern. Whether it's being caused by end users, or is a Nokia fault I really don't know - mine is fine, touch wood - but either way, Nokia should be very concerned about these problems and act before these devices gain a damaging reputation.

If you are running binary apps on the Linux protected mode operating system, the OS should be able to protect the stability of the computer. You should be able to gracefully recover from a segfault but putting that GUI on top and not having a GURU monitor tell you why it segfaulted and then rebooted is so wrong. Older machines like the Amiga and even the Treo/Palm will give you a diagnostic before rebooting.

BTW, if you are using any interpretive language, this would not be happening. Good VMs usually have stable code and good default error-trapping facilities.

Oh well. Maybe I should just get my old Altair 8800 and put it in my pocket. Yes, I own one.

Milhouse

01-30-2007, 06:04 PM

I know there was a time when Sardine would fail to boot due to one of the startup scripts in the boot process requesting a password (duh) all because an executable (alarmd, I think) couldn't be found.

I've no idea what the problem is with these devices cr@pping out left, right and center but it really shouldn't be happening this easily - in fact, it shouldn't be happening at all.

It saddens me to see people having so many serious issues and taking N800s back to CompUSA, most likely ending up with something technically inferior but something that does at least boot.

penguinbait

01-30-2007, 06:09 PM

This is just pissing me off, I would like to ask some questions.

Has anyone had problems after this has happened trying to reflash with the Linux flasher. I try to flash with Linux flasher and it hangs trying to write first block of kernel. Once this happens, you can no longer power on the device to reflash, but you can reflash using the power cord under windows, Linux will continue to hang.

Also when this happens and you start the flash utility in windows, it does not recognize your device, when I pick the update files manually, it shows upgrading IT OS 2006 to IT OS 2007. There is definetly an issue with one or both of the flash utilities it appears. But I am not positive of this, as this last time it happend to me I was not flashing, it just crashed, rebooted and dead.

Ugh!!!!

penguinbait

01-30-2007, 06:56 PM

Holy Crap, it came back.

I flashed several time and it was toast, flash hanging in linux, It just would not boot.

I flashhed under windows one last time before dinner and flash was successful, but it failed to boot. I got done eating dinner and I powered it on. just for kicks, it booted up, it actually booted up.

I have no Idea why it died or why it came back.

I am fricken bewildered!!!!!!!!!!!

:confused:

Peter The Plumber

01-30-2007, 07:17 PM

penguinbait

01-30-2007, 07:20 PM

Thanks Peter, I needed a good laugh. :D

Peter The Plumber

01-30-2007, 07:49 PM

Please forgive me, I just couldn't resist. Must be the cold around here, it finally decided to become winter down here and now I get to come and visit your area!

penguinbait

01-30-2007, 08:02 PM

Peter do you have and N800? Did you get it at COMPUSA?

Yeah I work in Auburn Hills and Live near Flint, I am actually going to be in downtown Detroit tomorrow. Its just as cold down there as it is up here. Especially when you get around those buildings downtown, it just whips around, cold as he77

Peter The Plumber

01-30-2007, 08:14 PM

No I do not have an 800, I'm still plodding along with two 770's. I know about downtown, that's one of the area's I work, when there's work. I live in the western suburbs and I'm going to Flint tommorrow night. Dress warm, it might not be the windy city but it's cold as all h*** as you know! Be careful coming down, traffic has been a bear.

Milhouse

01-30-2007, 08:24 PM

I got done eating dinner and I powered it on. just for kicks, it booted up, it actually booted up.

My N800 will fail to boot, but so far it's never failed to boot twice in a row - it only ever fails once. Typically I'll go to reboot, it will hang at "Nokia" or even just a white screen (always prior to the blue progress bar) so I then have to pop the battery and it always boots correctly on the next power on.

This, sadly, seems fairly typical for me. Maybe after you successfully reflashed it, your N800 was just being temperamental (like mine)? :) Fortunately I don't reboot often!

Glad you now have a functioning device - let's hope it stays that way! :D

penguinbait

01-30-2007, 10:09 PM

Well I am glad it cleared itself up too, that means it is a recoverable issue. I wish I could determine though, why it was happening, and the exact path to recovery. I would feel much more comfortable about the device. I had my 770 for 11 months and flash and hacked and flash and never never had 1 problem. So I am hoping this gets hammered out. I am seriously to the point of not wanting to keep this device. I don't want a device that can brick itself at will, especially on the road.

Texrat

01-30-2007, 10:11 PM

I'm bummed and surprised at these reports. I keep pushing my N800s and I don't experience these issues. it's like the 770 web thing all over again.

What am I doing "wrong"? :/

penguinbait

01-30-2007, 11:45 PM

N800 First 22 days , a recap

First Time DAY 7
I installed the BT plugin, rebooted. At his point it went into a reboot loop. I thought no big deal I will reflash. Using windows reflashed. Boots 3 secs then dies

Second Time DAY 21
built kernel modules, went great. built new kernel. flashed new kernel. Boots 3 secs then dies. I thought no big deal I will reflash original kernel. unpacked original kernel from image using flash tool. flashed the original kernel back. Boots 3 sec then dies.

Third Time DAY 22
loaded some kernel modules usbcore and ohci-hcd. No problems, crashed within 2 minutes, screen lost power turned black. Turned back on, boots 3 secs then dies.

The first time this happend to me, I thought it was a fluke and after trying to reflash several times, I exchanged. The second time it happend I was on Day 21 of my 21 day return policy, so after spending several hours trying linux and windows flashers and different combination of options, I returned it and got a new one again with new 21 day return policy. That was yesterday, after about 30 hours I totaled it again. I had plenty of return time left so I figured start messing with it. I tried all the same things again, nothing worked. When it did work I had no SD cards (not sure if this matters, but they were out) in and it was the windows flasher (not sure that this matter either. No R&D options set, or anything else. I guarantee this will happen again to me, I hope I can or someone can, or nokia will quickly come up with a sequence of events or new flashing tool to make this not an issue. It seems to be correctable, but I can not understand how the third time it happened to me. The first two times it happened it failed to boot only after using the flasher, the third time, it failed for unknown reasons, I had loaded those kernel modules previously and since so it has nothing to do with them. IF it just crashed and failed to boot, this might seem to indicate an actual harware problem, though it seems unlikely.

Perhaps this will help Textrat figure out what hes doing wrong;)

Milhouse

01-31-2007, 06:57 AM

Keep an eye on bugs #957 (https://maemo.org/bugzilla/show_bug.cgi?id=957) and #999 (https://maemo.org/bugzilla/show_bug.cgi?id=999), and provide any further detail if possible. It would probably best to add extra detail in bug #957 as bug #999 is almost certainly a duplicate of #957.

robot

02-01-2007, 12:15 AM

I too had the problem of the infinite reboot.

I set up a linux partition on my HDD and installed linux (from being a windows user), and then used the Research and Dev flasher sudo ./flasher-3.0 -F RX-34_2007SE_2.2006.51-6_PR_COMBINED_MR0_ARM.bin --enable-r-d --reboot

My Nokia N800 now works again!!!

Adam in NYC

02-09-2007, 09:10 AM

Looked at the Nokia website and saw this:

Repair Status Results
The repair status of your phone is:
Upon inspection by the Nokia Authorized Service Center, your Nokia N800 device, serial number XXXXXXX, was determined to be out of warranty. Generally devices are deemed out of warranty due to either liquid/physical damage or the warranty coverage time period has expired. Please contact the Nokia Authorized Service Center below to receive an out of warranty repair quote or to have your unrepaired phone returned to you.

Palco Customer Service:

Repair History:
Status Date Status
02/02/2007 Device is Out of Warranty
02/02/2007 Received
This information is provided as a courtesy. All information is provided "as is". It may not reflect the most current status of your repair.

Time to call Nokia and see what is up.

Adam in NYC

Looked up the ESN and got this on Nokia's website.

Warranty Verification Results
The status of the warranty on your Nokia device is:

Your device, serial number XXXXXXXX, appears to be within the initial warranty period. This warranty verification covers the following 10 days. If you send your device in for repair after 10 days, please include a copy of the proof of purchase with your device to confirm that your unit is within the warranty period.

Please visit our Warranty section or reference your purchase documentation for detailed information about your phone's limited warranty. For answers to frequently asked questions, visit our Warranty/Repair FAQs.

Please note that liquid and physical damage are not covered by the warranty. If the out of warranty device is "repairable", you will be contacted by the Nokia Authorized Service Center with a repair quote before the repair can begin. Prices vary by product and the nature of the repair. If the device is deemed "unrepairable" it will be returned to you without prior notification. Please note that the cost of return shipping and handling for out of warranty repair is the responsibility of the customer. Generally, the cost of return shipping and handling will not exceed $15.00. More information about out of warranty repair.

Talked to the Nokia rep on the line. Gotta wait 72 hours. It is Friday. Gotta get back to them on Wednesday.

Adam in NYC

Milhouse

02-09-2007, 09:31 AM

Best of luck Adam!

See bug #957 (https://maemo.org/bugzilla/show_bug.cgi?id=957) for details as to why enabling R&D mode may result in a sucessful boot:

There's a potential reason found for this. In the case there have been earlier >=10 consecutive reboots, the device doesn't clear the reboot count ever and thinks that an error has occured too often in a row. As a result it always powers the device off.

If this is the cause of the bug, enabling the R&D mode (where this check is
not done) with flasher should allow the device to boot up completely.

Adam in NYC

02-09-2007, 09:46 AM

Milhouse

02-09-2007, 10:11 AM

If enabling R&D mode results in a successful boot, why keep off the watchdog monitor? It is there for a reason, no. It is there so if there is a lockup, the Nokia will reboot.

What happens if there is a segfault and the watchdog is off? This is not a regular PC and I don't see a hardware reset nor a control-alt-delete would resolve things.

I imagine you can disable R&D mode once you have successfully booted and the reboot count has been reset to zero.

If you were to disable the lifeguard reset the worst thing that can happen is the device hangs instead of rebooting - if it hangs you just pull the battery out for a second and reinsert. If it is indeed necessary to disable the lifeguard reset to resolve the reboot issue, the inconvenience of having to pull the battery surely outweighs the inconvenience you would experience from a reboot loop. :)

I would rather work with a safety net than have access to the N800 and then some buggy code gives it the final bork.

Pulling the battery is the ultimate three-fingered-salute, essentially the same as power cycling a PC which I've had to do from time to time in Windows when it locks solid and no longer responds to the keyboard/mouse.

on my Nokias. Let my Nokia reboot a dozen times until I get a stable screen. As for my N800, I am thinking of writing it off and taking the brick to the Nokia store if the depot does not want to repair it.

Fair enough.

jurop88

02-09-2007, 08:34 PM

OK, it happened to me, too :-(: My N800 (well, my wife's one at this point ;), and this forum's people should know why this statement) woke me up in the middle of the night while going in a reboot loop.

No reason, no problem, no previous advices, simply reboot loop!

At the end, everything went fine thanx to the --set-rd-flag/--disable-rd-mode procedure, and now I'm going back to sleep rather peaceful.
The matter is that I have nothing more to add to the bug filed in bugzilla #957, and I didn't think just and only to --set-rd-flag before trying turning on the machine.
I thought that switch on and off the flags should have been enough to reset the consecutive-resets counter as mr. Taaminen explained, but I didn't try to boot with the RD mode on.
What I can say is that the procedure

flasher 3.0 --set-rd-flag=no-lifeguard-reset
flasher 3.0 --disable-rd-mode
boot

didn't ended in a succesful boot.

So i flashed the device following exactly the instructions found here and on the list - i.e.

flasher-3.0 --set-rd-flag=no-lifeguard-reset -F RX-34_2007SE_2.2006.51-6_PR_COMBINED_MR0_ARM.bin -f -R

and the device booted on its second try.

After that I disabled the RD mode with
flasher3.0 --disable-rd-mode
and rebooted with
flasher3.0 -R
before disconneting the usb cable, and now it seems everything works fine

Just for the sake of specifying, the device wasn't too hacked: xterm, ssh, horizon and vnc, nothing else (didn't I say that it's my wife's device ?.....)

Conclusions:

it's a pity that such a device could encounter with such troubles. Why, after all the discussion we had about that and the reason for a whole flash instead a step by step update in case of upgrading of the OS, a software problem couldn't be resolved with a simple flash but needed some tricks? Nokia couldn't expect the joe user to try everything, the flash is the simplest and safest way to repair every software problem. Also members of service center could not be able to repair such a problem and could be tempted to send the device to Nokia main centers, all in all probably they are not members of ITT forum nor Maemo lists ;)
thanx to everybody who pointed me towards the right direction to unbrick the device.
I am still in love with these devices, the 770 is the first palm that works for me for more than two months without ending up sinking in some drawer, but... definitely, these problems should not happen! (oh, btw never had this kind of problem with my 770, only a broken display :mad: fortunately covered by warranty)

Milhouse

02-09-2007, 09:48 PM

So i flashed the device following exactly the instructions found here and on the list - i.e.

flasher-3.0 --set-rd-flag=no-lifeguard-reset -F RX-34_2007SE_2.2006.51-6_PR_COMBINED_MR0_ARM.bin -f -R

and the device booted on its second try.

According to this (http://www.gossamer-threads.com/lists/maemo/users/16330?nohighlight=1#16330) post in the Maemo newsgroup, N800 (not sure about 770) devices no longer boot fully after being flashed if the USB cable is still connected. This is so that the user can continue to adjust flasher flags, however for most ordinary users this behaviour is inappropriate as such users won't continue tweaking flags. Unless the user is expecting the device to return to flasher mode it appears as though the device has hung on the first boot.

A warning in the flasher might be a good idea, Nokia! :) And perhaps add a switch to control the reboot behaviour - by default the device should reboot fully, with a switch to reboot in flasher mode as a convenience to the user. No way should developer oriented convenience behaviour be the default on a consumer device! :rolleyes:

jurop88

02-10-2007, 03:57 AM

I can say that the device booted with the USB cable plugged in just issuing the flasher3.0 -R command. To be precise, it is the -R flag. If you don't send it, the device wont reboot and lets you play with flags and flasher.

When I wrote
and the device booted on its second try
I meant that on the first boot, it made the 'reboot after 3 seconds issue' again and I thought something was wrong with the device. In other posts I found that's a rather usual behaviour, so I tried to reboot again and on the second try the device booted reularly. At the end of the boot, my ubuntu pc (Athlos, btw) popped up two windows about the two cards inserted in Armis2, because the USB cable was still connected and it automounted the cards :)

Nash

02-11-2007, 06:54 PM

Hi,

I just went through this same thing yesterday and today. I was not able
to get the N800 to boot up. I just exchanged it at Comp Usa. I had
bought the extended service plan.

I do not know how to flash the device and add lines of code in the
process. I hope the new one I got will not have this same problem.

If it does I will be getting a refund on it and go back to using my 770 100%
of the time. Since I don't know anything about computers, besides using
them, I will have no choice.

Back when I got the 770, I installed the FB reader. That was the first time
I installed software that did not have a "wizzard".

I have learned so very much reading these boards. But this problem was
just over my head.

JN

Adam in NYC

02-16-2007, 12:35 AM

Still waiting from Palco.

Now they say it is a warranty repair but they are waiting for replacement units. So I wait.

YMMMV.

freeman

02-17-2007, 01:47 AM

I brought the CompUSA replacement plan also, simply because I afraid of the famous WSOD that I had on my 770.

walshga

02-21-2007, 01:26 PM

Misery loves company, Adam in NYC. I had my new N800 for just a week when it went into "3 second endless reboot" mode. Damn frustrating! Tried some of the various fixes discussed here, with no success. So, I sent the unit to Palco in Alabama. A few days later, I checked the Nokia USA Repair Status website, and also got the "out of warranty" message (as you did with your problematic N800).
So, I promptly (& apoplectically) called Palco. A gentle southern lass named Patricia assured me the "out of warranty" status was a mistake - and that the N800 would be forwarded for repair. Well, that was ten days ago (2/12). Today, the Nokia USA repair site still shows my N800 as "out of warranty." I again talked to Patricia at Palco, and she politely informed that Nokia will be sending me a replacement tablet - but it might take a month!:mad:
I think Palco has been good about explaining what's going on. But I agree with some others on this forum - Palco doesn't want to mess with some new-fangled gadget with an embedded Linux OS. (They're MS, Novell network & cell phone people (http://www.palcotelecom.com/index.html).) But Patricia mentioned some delays in getting replacement N800s from Nokia. She also mentioned that I should call Nokia customer service and attempt to expedite replacement. My question is: should I call Nokia & *****, or just shut-up and wait for a new N800?
The upshot to all this? I've fallen in love again with my 770! The N800 is very slick (when it's not in endless reboot mode) but it lacks the 60's retro spy gadget look & feel of the 770. And I really miss the sliding aluminum cover! The N800 just seems more fragile than the 770. Anyway, that's my two cents worth.
Peace, y'all!

penguinbait

02-21-2007, 03:21 PM

A Couple of things I noticed after smoking 3 of them. and returning 2 of them. You can recover this. I am not sure if you are having the same troubles I had noticed but.

First of all endless reboot is a software issue and should be fixed by reflashing. The problem is that reflashing is what causes the 3 sec boot then off. It starts to power on, then dies. This is different from the endless reboot. This can also be recovered. I did this three times, and the first two I returned. I was experiencing oddness with flashing under linux (hanging flashing kernel) and windows would flash no problem. But niether would work.

What ultimately I found to be my problem, was that I have about 10 different USB cables. If I did not use my 770 or n800 cable, I had problems. Verify that you are using the correct cable for the device. Just because it fits in both ends does not mean it will work.

I am not saying this is everyones issue, but I have not had a single problem since I started only using the correct cable.

walshga

02-21-2007, 06:02 PM

Thanks for the tip, Penguinbait! After my replacement N800 arrives, I'll be sure to only use a Nokia-issue USB cable.
Take care,
Jim

sapporobaby

03-16-2007, 09:36 PM

Well, add me to the list. The "reboot of life" it seems. I have read about setting a flag, but I am not using a Linux box. Actually I am on an Intel-Mac, and using the Nokia flasher. Is there a way to correct this or should I just go get a new tomorrow morning?

TIA

Milhouse

03-17-2007, 01:47 AM

Just use a Linux LiveCD - there's no need to take the N800 back for exchange.

sapporobaby

03-17-2007, 08:20 AM

Just use a Linux LiveCD - there's no need to take the N800 back for exchange.

Thanks for the somewhat, in my case, cryptic advise. As I stated many times before, I am on the user end of the spectrum when it comes to this environment. To just get a Linux LiveCD does not strike any bells with me. For the most part, if it is not something I can do within say, 30 mins to an hour, I simply do not have the time for it. Second, as I also mentioned previously, I am using a Mac which is not a Linux machine, so unless I was willing to install a virtualization software after paying for it, I am stuck again.

While I am sure that many to most where will understand and appreciate your assistance, I don't. I see it as you saying I need a communications solution and I say, just install a: AN-GRC/39 Terminal.

Once again, thanks for the help.

BTW: Took it back, got a new one.

Milhouse

03-17-2007, 12:35 PM

Thanks for the somewhat, in my case, cryptic advise.

Use the search function - lots of information about LiveCD to be found. Even try Google. Educate yourself, perhaps by reading the second Google link (LiveDistro Wiki) that appears when you Google for "LiveCD".

Secondly, your Mac is an Intel based computer - you need to get over this "Mac is not Linux" thing. "Mac" is your OS, it's no longer the hardware platform, which is now pretty much common-or-garden Intel PC kit.

fpp

03-17-2007, 12:41 PM

Sapporobaby, is your Mac one of the more recent Intel machines ?

If so, I would guess using a run-of-the-mill Linux Live CDs (such as Knoppix) should be possible, and certainly doable in a 30-to-60 minutes time frame, even the first time. Could save you tons of time in the future, too.

If your Mac is Intel-based I can elaborate on those simple steps (although I believe I already did some months ago).

sapporobaby

03-17-2007, 12:52 PM

@Milhouse and FPP,

Cool. I will look it up. Being that a new firmware upgrade for the N800 is coming, I will play more with it before I turn it into a "production" machine.

Good point you made about the Mac is not Linux thing.

Anyway, I will do some research on it and give it a try.

Cheers.

fpp

03-17-2007, 02:12 PM

Here's the quick-n-dirty 10-step howto I did last year :
http://www.internettablettalk.com/forums/showpost.php?p=6726&postcount=35

The only difference I can think of is automounting (or not) of MacOS disk volumes by Knoppix.

If not, easy workarounds :

* Knoppix figures out the network stuff and Internet works : just download image and flasher with Firefox

* else : move these to an USB key before booting to Knoppix, it will detect and automount those

Also, the actual command line for the latest flasher is probably a bit different. No big deal.

Polymira

03-17-2007, 07:06 PM

Just download and burn knoppix, boot it, download everything you need from within knoppix, and run it from there...

Everything worked fine on my hackintosh, and on my macbook.

DryLand404

03-19-2007, 12:56 PM

Beware of the Weather Applet and No Data days.
I noticed a few days ago that the weather applet was showing no info for weather on upcoming days. I tried adding in CapeCoral again to no avail.
Following the final day of weather data had passed, I awoke to the N800 booting up for three seconds and then shutting down.
Others had commented that they believed that the Weather applet was causing an issue as well.
Having not read this.. I have already re-flashed the N800 and still have the same situation. Booting for 3 seconds and then it shuts down.
I will disable / enable developer mode switch as soon as I can figure out how to do it from a windows machine.
I had in the previous 2 days been installing other applications, so there is deniability that OSSO Weather app was the culprit.
I had installed Doom, Tux, Bejweled, and crazy parking the day previous to the crashes. Anyone know where the log files are?