
The nice folks at Celio took note of my continued Redfly issues (this time with the new Touch Pro2) and sent me beta drivers for both the TP2 and the Redfly terminal itself with a caveat that both are still beta releases and will be improved in the future. I ended up violating my own Rule #1 because of my desire to get the Redfly working with the TP2. And, what is Rule #1? Never install beta release low-level apps on a production phone.
But, I did. And, you can see the result in the photo of my TP2 above… The TP2′s screen just sat at what you see above for several minutes. I plugged in an A/C adapter to make sure the battery didn’t drain. After waiting a few more minutes, I tried a soft reset with the same result. I tried another soft reset only to see the same screen again.
Hoping it wasn’t bricked, I decided to perform a hard reset. There was one problem though. I didn’t know how to perform a hard reset on the TP2. And, every Windows Mobile phone seems to have a different technique. A quick search turned up this item a XDA-Developers.com…
Here’s the steps I too to perform a hard reset:
1. Turn off the TP2. In my case, I had to pull the battery out since the on-off button didn’t work
2. Press and hold the SEND and END keys simultaneously
3. While continuing to hold the SEND and END keys, press the POWER BUTTON (a bit of finger contortion here)
4. Press the VOLUME UP button
At this point, the Redfly is back in its original box. And, it is going to stay there for a long while. I have no intention of trying it until I stop being annoyed at this product. I may not return to it until next year.











SocialTimes.com Twitter feed loading...
Neil Vidyarthi
Devon Glenn
Staff Writer
Megan O'Neill
Web Video Writer
Nadine Cheung
The Job Post
![[All Facebook Stats: Facebook Analytics for Your Business]](/blogshare/content/images/stpro_allfacebookstats.gif)
![[How can Facebook change your business?]](/blogshare/content/images/FMB_A_MAY2011_336x100_F.gif)


