[HD2 Android Q&A, Help & Troubleshooting and Genera] voyager529:
Hey guys!

I've got 2 of the T-Mobile HD2 handsets, both 'yellow reset button' revisions. One runs Windows Mobile 6.5 (have yet to find an alternative for texting through Outlook/Exchange), the other running some flavor of Android. This setup has been working just fine for months, but last month I started experiencing random restarts, sleep death, and charge death. In two known instances, this happened during calls.

Now having been educated on How to ask a question properly, I have done my best to attempt all the due diligence I could muster...

--The Android handset is presently running the Nexus ICS 1.5 ROM with the Dormanix ICS kernel. After the first few random restarts, I tried it with the regular kernel (tyung's?) and had the same issue. I then reverted to my mainstays of Typhoon Cyanogen and Hyperdroid, both with stock kernels, both demonstrating the same issue after the first day or two.

--I've tried every radio release from 2.10-2.15, being careful to only install the '50' releases, not the '51's. None of these have alleviated the issue.

--I used setCPU to try overclocking, underclocking, then just set it back to stock and uninstalled setCPU.

--The most recent format attempt, while I didn't task29, I did format /system and /data from within CWM.

--Also with the most recent attempt, I didn't install any backup software or create any backups, except with text messages through GoSMS. I did not restore any backups with Titanium Backup or MyBackup Pro.

--I have not uninstalled any system apps with ROM Toolbox.

--I have tried updating my CWM install version to 5.x.

--I have attempted switching the OSes of the two handsets; both have had the same issue with Android but neither have SoD'd with Windows Mobile.

Just about the only thing I haven't tried was switching the the cLK bootloader instead of MagLDR; my logic for not doing so is that I do keep an archive of all the old versions of the ROMs I've installed so that, in cases like these, I could try some older known-stable-to-me releases, and all the ones I've downloaded were for MAG. Additionally, none of the other threads I read indicated that the seemingly mature MAG platform was found to be the cause of anyone else's issues; all the other threads seemed to relate to either titanium backup restoring something in an extremely wonky manner, or an unstable/incompatible release of the baseband firmware.

The only other thing I could think of that could cause the issue that started roughly around the time that this problem started was my use of LBE Privacy Guard. I'm hesitant to blame LBE for the following reasons:

1.) LBE has been perfectly stable on my Incredible 2.

2.) LBE hasn't been blamed for any of the other SoD issues discussed in these threads.

3.) The Google Play page for LBE indicates no such issues reported in either the dev writeup or the first five pages of reviews.

4.) The SoDs don't seem to coordinate with the times that LBE blocks things.

5.) Uninstalling didn't make the issue go away.

However, given the nature of LBE and the kind of low-level access it gets to the system, I felt it worth mentioning.

Thanks for reading my lengthy plight; any assistance (including thread links if I missed a thread in my searches) would be greatly appreciated. In the meantime, I'm going to give Task29 and installing CLK a try.

Joey