> > Anyway, a cause for this bug has been found and a fix is in works.
> > AFAIK it will require updating the device bootloader (can be done
> > with flasher), but I don't know when the fix will be available.
>
> Great - so what is the advice for people with this problem?
>
> How best should they work around this problem until the fix is available?

There's no currently known workaround.

However, if you can reflash the device (can get the device to boot up, you've
taken backup and have nothing else that you would miss, battery is full etc)
with the latest N800 OS2007 or OS2008 release we would be interested about
whether that has any effect.


> Can you (or someone more familiar with the problem) provide more details other
> than good news (bug is identified) and bad news (but no ETA for a fix)?

The issue seems to be related to SW timings used in Omap initializations.
(that could explain why in some blog post it was claimed that freezing
the device helped i.e. that temperature could affect it.)

If everything works well, the fix could be available in a few weeks.