Pocket PC Hints and Tips
   by Frank McPherson, author of How To Do Everything With Windows Mobile
Sunday, May 25, 2008
Second Tytnn II Meltdown
 
In little more than two months I have had two problems with my HTC Tytnn II resulting in a hard reset. In both cases I let the power get too low and I tried a soft reset. What happens is the initial "Smart Mobility" screen displays, along with the version numbers for the radio and it stays there, rather than completing the rest of the boot process.

The first time this happened I was able to get past this screen after a couple of soft resets until I got a screen telling me that it was resetting the device. This time no matter what I did, I was not able to get past the screen. I called HTC's support and was told, "bad news, you are going to have to do a hard reset" losing your data. Ok, I was already prepared for that. The support guy then said, "the good thing is, HTC just released the Windows Mobile 6.1 update for the Tytnn II so if you were going to install that you would have done a hard reset", which is true.

So, the question is, how do I force a hard reset to get past the screen. The magic key sequence to force a hard reset is here. Unfortunately the key sequence didn't help; I kept getting stuck at the same screen.

I then tried to run the Windows Mobile update, but that didn't work because when I plugged the device in to my desktop PC it wasn't being recognized. Finally I got the device into the bootloader by pressing and holding the Camera button, then pressing the soft reset button and releasing both once the bootloader screen appeared. With the bootloader up I then connected the device to my desktop at which point the USB connection was recognized and the Windows Mobile update ran successfully.

So, in the end all is well, and since I synchronize this device with an Exchange server, all of my data was quickly back, and since the last time this happened I copied all the cab files of the applications use to my storage card, I was able to pretty quickly restore all of my applications. For now the device appears to be running well, though I have to admit that two occurrences of this in a matter of months is not reassurring.

Labels: ,