[AT&T, Rogers HTC One X, Telstra One XL] LawyerLounge:
Hello, just registered for an account here after trying to fix my problem from 2-3 days worth of "google-ing" related articles and threads of my current problem. Although there has been too many boot loop complications to count, I couldn't seem to stumble upon a scenario in which the user's circumstances were related to my own specifications (I am aware of how important it is to review and research before creating a new thread).

I will proceed to list in, chronological order, the recent alterations my phone has undergone within the last couple of days...

1. Giving the "bootloader" the Boot

I've had my At&t One X for about five to six months and have gotten pretty comfortable with the Android platform, and decided to research in the journey that any brave "pioneer of technology" would partake in, gaining super user-access through rooting! Of course, at the time, I knew as little about the topic that I could have safely assumed that "to root" a phone had to have involved planting your device in soil, adding water, and providing ample sunlight.. SO I began to research and learned quickly that one would need to "unlock the boot loader" on their device before they could proceed to rooting. I figured that I had a green-thumb when it came to following instructions and carried on to "HTCdev's" website to unlock my phone. I installed Sync, updated my Java, and downloaded Android SDK.zip onto my (Windows PC). In the end, I learned both: how to use fastboot in my pc's command prompt, and that my phone was apparently incompatible to be unlocked. At the end i received an error message "Error Code: 160 Error Reason: MID Not Allowed".

2. Root of my Problems

Although I had failed to unlock my phone's boot loader, I was still determined to root my phone and through more research I found I could still "root" my phone, but I would have less options when it comes to flashing roms and some other jive. Since I was only needing root to be able to run "Sixaxis" (to sync a PS3 controller as an IME for my phone) at the time, I was okay with that.

I found a simple root website (Can't upload link due to my "ten-posts-cherry" not being popped yet, but the link was named "How to ROOT HTC AT&T One X with one-click method" in Google) and followed the steps carefully. I downloaded "root-one-x.zip", extracted files, and double-clicked on the batch file. My phone restarted a couple times and everything seemed to run smoothly after rooting.

3. Creative Control Causes Chaos

After being rooted for a week or two, I started to delve into the tweaking possibilities my phone could endure now, such as the ability to change fonts (when I should've been taking advantage of apps like Titanium Backup). I searched the play store for a while and came across an app called "Custom Android Font Switcher" (by Bentotbox), which claimed compatible with my device and boasted the simplicity of switching to hundreds of new fonts for your device. (Seemed pretty neat!) It did note the requirement of "root with busybox?" but I continued to download and install. I launched the app, browsed some obnoxious fonts, settled on a more simplistic variance of my original, and loaded the new font. When finished loading I noticed the new font had correctly taken effect on most parts of my phone, with the latter erroneously displaying in Chinese-like characters. (wasn't sure if it was Japanese or Korean, but in my opinion they all look the same only joking..) Since I am not talented in reading any other language thoroughly enough, I went back into the app to find a way to revert back to the original font, yet found no way to do so. My next decision was to un-install the app hoping that might bring my original font back, and when it didn't I decided a Restart would do the trick! Well now it seems my phone has learned a new trick indeed! Being able to continuously "loop" the loading screen. (Boots to welcome screen, then At&t screen, then flips over to a screen that just shows "ONEx" and stays there until I either: power-down the phone to start the process again OR smash with a hammer)

4. Trial and Error to no Prevail and Much Error

My phone has been in a bootloop since about 2-3 days ago, and like I mentioned, I have searched many forums and threads for solutions (Which I've done all throughout my technological life and usually had no problem finding out how to do something, whether it would be changing a radiator to performing open-heart surgery on a monkey). This is actually the first time I've posted on any forum for help since I usually find a way to fix issues myself from other user's parallel problems.

So far, I have tried the following with no resolution to my phone's boot revolution:

- Enter "Recovery" mode by holding volume-down while powering on the phone.

- Choosing the "Clear Storage" in the phone's hboot menu.

- Choosing the "Factory Reset" in the phone's hboot menu

- (I've read many places to clear cache and dalvic cache?, but cannot seem to find these options)

- (I've read that one can re-flash? CWM recovery to fix loop, but I couldn't do so because it apparently Requires an Unlocked Bootloader)

- Been able to stop the loop by choosing the "Power-Down" option in the hboot menu (Also enables me to charge phone via wallcharger! Also noticed other people on the internet having troubles finding a way to charge their phone in a boot loop. Maybe I stumbled on to a potential universal solution?)

- When I choose the actual option "Recovery" in the hboot or (recovery mode) the screen goes black and eventual shows a phone icon with a red triangle on the screen and stays there until I re-boot. Is this supposed to be the Recovery page?

Conclusion

I know I've made a pretty long "first-post", but I wanted to make sure I gave all the details that might matter when trying to diagnose my problem and might help others with a problem like mine. So anyways, thank you for reading and I appreciate your help in advanced!

-LawyerLounge