Ok well lets just start with I think I have quitely possibly found a way to kill a Pronto in ProntoScript.

Was doing some code cleanup on prontoScroll which is a cute little app which scrolls your icons around using the scroll wheel (it's handy for 1 handed use)...

Use to have a fixed array, but thought I would add some smarts and have a dynamic one instead.

This is where life gets sad..
for(i=1;1<13;i++){
//stuff done here
}

Ok on first site that looks ok, but no alas the 1<13 is a ONE not an i...

And as this is in my homepage it's the first thing executed when the remote starts.

Which now leaves me with a remote that wont go past
pr((o))nto
philips
please wait...

Any one got any thoughts of how to either dump the uploaded XCF (eg do a reset to factory?)

So far tried to:
re-upload firmware - no joy
access diagnostic log - no joy
home +menu +page up - well it reboots but still no joy.

Ok,

The force firmware update finally worked and has fixed it.

Once i red about a feature that allows you to start the pronto, but in a way that it just boots and halts before executing the scripts. So then you can reload the corrected script. I don't remember where i saw this feature, but it is there.

EDIT:
There it is, in the prontoscript developers guide:

12.3. Infinite scripts
It is possible to create a script that takes a long time to execute and effectively blocks the control panel. In order to enable the user to fix this situation a key combination can be pressed during the start-up of the control panel that disables the script engine. The key combination to be used is: Backlight + Menu + ChannelUp. It must be pressed continuously during the start-up animation and the please wait screen. A diagnostic message will be logged to indicate the limited functionality available. The user can then use the normal download procedure to download a corrected configuration file into the control panel. Another reboot is required to start the script engine again.

Guess it does pay to RTM. Happy Holidays

YOu can also try downloading a new config, and once it clears the remote, pull the usb plug. Now you have a blank pronto. Then retry downloading. WOrked for me on an older pronto that had a firmware upgrade that was causing me a headache. I was able to backdate my firmware in this manner.

Just to keep everybody using consistent terms, you can "backdate" your firmware using a "complete" firmware reload.

This process is described in the FAQ on Philips website and involves holding Firm2,Firm3,Firm4 during a reboot. Please see the FAQ for more info.