Database Info

Noob Unlocks and Subsequently Kills Phone

A day or two ago I unlocked my ChaCha using the HTCDev.com instructions. I then used DooMLoRD_v4_ROOT-zergRush-busybox-su to root it. Everything was going fine until I apparently deleted one too many system apps and now my phone is in extremis.
The problem: As the phone boots up and reaches the HTC logo screen, just when the main interface should appear, an error pops up. It says:
Code:
Sorry!
The process com.htc.bg has stopped unexpectedly. Please try again.
[Force close]
When I close it, the HTC logo appears again as the main GUI is reinitialised, which leads to the same error popping up again, thus entering into an infinite loop.
I can just about manage to connect the phone to my PC as a disk drive, but it's not connected in such a way that RUU or unrooting applications can "find" it from within Windows, so if I'm to fix this it's gotta be from the SD card/Hboot.
Details:
* HTC ChaCha with the latest Android firmware.
* Unlocked and rooted, but remains S-ON (Superuser was installed and worked).
* Used Titanium to delete apps, but made backups and have them on my hard drive for safe keeping but can't access the phone in order to restore them properly.
* I was unable to restore backed-up system apps prior to this critical problem emerging, which I think is because my phone isn't "truly" rooted. I can apparently remove from but not add to the protected areas of the phone.
* I've tried flashing the device with numerous recovery ROMs and they all fail (wrong image, etc.). I'm having an extremely difficult time finding the original ROM anywhere and more importantly finding one which will work without the phone being connected to the PC at any stage of the flashing job.
* Factory resets and recovery boots don't seem to have any effect.
* It's a carrier-locked/branded phone, from Three/Hutchison 3G UK. I'm locked into my contract for another year at least.
* Before I rebooted the phone for the last time [prior to the beginning of the above problem] I noticed that my ringtones and related media were all gone and I was unable to download new ones even using third-party apps; the "unable to download sound" error was constantly popping up and when I received messages or phone calls the phone would vibrate but wouldn't play any tones.
* My brother and I spent the better part of 6 hours scouring the net and trying every combination of steps we could think of to try and resolve this. I wouldn't have posted here if I wasn't at the end of my tether and if I hadn't tried every solution I could find from others on various forums including this one, nor would I be so quick to reveal myself to be a deletion-happy moron to a forum of experts (I saw that anti-noob YouTube clip!).
Is there any hope of fixing this issue given my obvious lack of critical faculties?
Thank you for reading this.

You can always install clockworkmod recovery and from there a custom rom. Check the relevant thread, it is pinned.

OK,
don't panic. I almost thought you'd hard bricked your phone when modifying the NAND. This is a soft brick and ALL soft bricks can be recovered, they just take a bit of pain and suffering. Sometimes more suffering than others, but that's irrelevant.
Question, you say you can't restore system apps? How did you try? If a phone is perm rooted, it's rooted. Obviously a temp root is different to a perm root, but I believe this is a perm root as you can REMOVE apps from the system memory. If a root wasn't perm, every app would be sandboxed so no app, including titaniumbackup would work.
* Unlocked and rooted, but remains S-ON (Superuser was installed and worked).
Click to expand...
Click to collapse
S-ON is part of HTC's snap on BL protection. The fact your phone is S-ON is now not that important, the BL is unlocked, thats what matters.
* Used Titanium to delete apps, but made backups and have them on my hard drive for safe keeping but can't access the phone in order to restore them properly.
Click to expand...
Click to collapse
Ok, important advice here (for future ref), you shouldn't go mad with deleting unless you've tried freezing first. Freezing allows you to recover by simply doing a factory reset. Most bootloaders (including HTC's) allow you to perform an emergency factory reset from there. You might lose all the **** on there, but you will have a working phone. You also need to be careful with TitaniumBackup, I'm sure you didn't remove the obvious important ones, but the fact you lost access to your audio means you removed a sound/media package. Next time, google "HTC chacha, safe to remove" as more people root this phone in the next few weeks, safe to remove lists will appear. For SGS (my phone) there is a whole shared google doc with a list of system apps, and the consequence of removing them.
* I was unable to restore backed-up system apps prior to this critical problem emerging, which I think is because my phone isn't "truly" rooted. I can apparently remove from but not add to the protected areas of the phone.
Click to expand...
Click to collapse
You can't restore a system app if there is a conflict. Try and identify the conflict.
* I've tried flashing the device with numerous recovery ROMs and they all fail (wrong image, etc.). I'm having an extremely difficult time finding the original ROM anywhere and more importantly finding one which will work without the phone being connected to the PC at any stage of the flashing job.
Click to expand...
Click to collapse
By the sounds of it, you are using ROMs designed for CWM. If you are going to do that, flash CWM first. There are shed loads of tutorials. If you want to install the stock rom all over again, just download the stock RUU.
* Factory resets and recovery boots don't seem to have any effect.
Click to expand...
Click to collapse
See above about freezing.
* It's a carrier-locked/branded phone, from Three/Hutchison 3G UK. I'm locked into my contract for another year at least.
Click to expand...
Click to collapse
Doesn't matter, you'll fix it, guarantee it.
* Before I rebooted the phone for the last time [prior to the beginning of the above problem] I noticed that my ringtones and related media were all gone and I was unable to download new ones even using third-party apps; the "unable to download sound" error was constantly popping up and when I received messages or phone calls the phone would vibrate but wouldn't play any tones.
Click to expand...
Click to collapse
See what I said above.
* My brother and I spent the better part of 6 hours scouring the net and trying every combination of steps we could think of to try and resolve this. I wouldn't have posted here if I wasn't at the end of my tether and if I hadn't tried every solution I could find from others on various forums including this one, nor would I be so quick to reveal myself to be a deletion-happy moron to a forum of experts (I saw that anti-noob YouTube clip!).
Click to expand...
Click to collapse
Have you tried every combination of steps? You've clearly not tried CWM. I'm not suggesting that as a silver bullet (personally, I try to avoid CWM if I can) but it's the best way to give you low level access to the NAND so you could easily flash an OTA ROM, modded ROM or even return it to stock dead quick.

For a safe to remove list, check the Themes and Apps section.

skezza said:
OK,
don't panic. I almost thought you'd hard bricked your phone when modifying the NAND. This is a soft brick and ALL soft bricks can be recovered, they just take a bit of pain and suffering. Sometimes more suffering than others, but that's irrelevant.
Click to expand...
Click to collapse
Music to my ears!
skezza said:
Question, you say you can't restore system apps? How did you try? If a phone is perm rooted, it's rooted. Obviously a temp root is different to a perm root, but I believe this is a perm root as you can REMOVE apps from the system memory. If a root wasn't perm, every app would be sandboxed so no app, including titaniumbackup would work.
Click to expand...
Click to collapse
In Titanium Backup I tried restoring the backups I made; the "Recovering Backup" notice would just hang indefinitely until I forced TB to close. This only happened with system apps. The backed up files are still on my PC hard drive from when I copied them from my SD card, but I'm not sure they're of any use at this stage.
skezza said:
S-ON is part of HTC's snap on BL protection. The fact your phone is S-ON is now not that important, the BL is unlocked, thats what matters.
Click to expand...
Click to collapse
Ahhh, this is probably my problem then. I ignored most of the fixes and workarounds listed as [S-OFF] because I didn't think they'd work for my device haha.
skezza said:
Ok, important advice here (for future ref), you shouldn't go mad with deleting unless you've tried freezing first. Freezing allows you to recover by simply doing a factory reset. Most bootloaders (including HTC's) allow you to perform an emergency factory reset from there. You might lose all the **** on there, but you will have a working phone. You also need to be careful with TitaniumBackup, I'm sure you didn't remove the obvious important ones, but the fact you lost access to your audio means you removed a sound/media package. Next time, google "HTC chacha, safe to remove" as more people root this phone in the next few weeks, safe to remove lists will appear. For SGS (my phone) there is a whole shared google doc with a list of system apps, and the consequence of removing them.
Click to expand...
Click to collapse
I'm disappointed in myself for being so haphazard in my deleting, I'm usually not that stupid but I think I was a little overexcited to have finally gotten rid of some of the bloatware that'd irritated me for so long haha. I was like "oh boy, I can save even more battery power and internal space if I just remove a little more!". Lesson learnt
skezza said:
By the sounds of it, you are using ROMs designed for CWM. If you are going to do that, flash CWM first. There are shed loads of tutorials. If you want to install the stock rom all over again, just download the stock RUU.
...
Have you tried every combination of steps? You've clearly not tried CWM. I'm not suggesting that as a silver bullet (personally, I try to avoid CWM if I can) but it's the best way to give you low level access to the NAND so you could easily flash an OTA ROM, modded ROM or even return it to stock dead quick.
Click to expand...
Click to collapse
As I said above I didn't realise I could make use of [S-OFF] materials so I didn't even attempt them for fear of making matters worse. I just now attempted to flash CWM and it hung on "parsing" which is what happened with previous flash attempts. If a flash attempt doesn't hang on "parsing" it parses for a second and then goes back to the main menu, apparently having no effect.
I'd be lying if I said I'm not overwhelmed by all of this; the tutorials I've read seem to assume a fair degree of prior knowledge that I definitely don't have haha. I hope I don't stretch anyone's patience here, but if you could explain it to me like a 6-year-old whose mother drank heavily during pregnancy I think it will help move things along!
Thank you for the thorough reply, much appreciated

Follow this to flash CWM, you need to do it with your computer and using fastboot, this is needed for S-ON phones.
http://forum.xda-developers.com/showthread.php?t=1449681

dapaua said:
Follow this to flash CWM, you need to do it with your computer and using fastboot, this is needed for S-ON phones.
http://forum.xda-developers.com/showthread.php?t=1449681
Click to expand...
Click to collapse
Unfortunately I can't do anything via my computer; my phone isn't "discovered" by the command line, unrooting tools or anything else. It does allow me to access the SD card as a hard drive but that's all it does. Obviously this wasn't the case before my problems started, because I used my PC to root and unlock the phone originally, but now the phone's boot process can't reach a point where it becomes receptive to the PC's commands. I don't know why it lets me access the SD card though.
Is there any way to do this without my PC being involved beyond transferring files to the SD card? If not, am I screwed? haha
Thanks mate!

Can you boot into the bootloader (Whith the phone off, press Volume down + power for five seconds)?
Then boot into it, move up with the volume keys and then choose fastboot.
Then follow the procedures in the link I posted previously http://forum.xda-developers.com/showthread.php?t=1449681 (start from step 3). Fastboot mode should be recognized.
The fastboot binary is here C:\Program Files (x86)\Android\android-sdk\tools , if you installed the android SDK, which I asume you did.
Good luck, I hope this works!

dapaua said:
Can you boot into the bootloader (Whith the phone off, press Volume down + power for five seconds)?
Then boot into it, move up with the volume keys and then choose fastboot.
Then follow the procedures in the link I posted previously http://forum.xda-developers.com/showthread.php?t=1449681 (start from step 3). Fastboot mode should be recognized.
Click to expand...
Click to collapse
Dear CHRIST thank you for that - I didn't know about this feature, and it worked! I was able to connect to my PC and do everything I needed to. I used the command line to flash the CWM, then followed instructions for partitioning the SD card and installing a custom ROM. I feel like a real [email protected] I wonder if Anonymous are looking for any new recruits...
dapaua said:
Good luck, I hope this works!
Click to expand...
Click to collapse
It did - I'm back in business!! Thank you mate, if I could fellate you via WiFi I probably would. You'd have to be wearing some anti-virus trousers though, I'm not a slut.
Cheers!

PaddyM said:
Dear CHRIST thank you for that - I didn't...
Click to expand...
Click to collapse
Great news (I thought you already knew about the recovery menu feature otherwise I'd have mentioned it).
As I said in my reply earlier, every soft brick can be fixed somehow. Some are just harder than others. If I'm honest, it seems like yours was pretty straightforward once you got into the Recovery menu.
By the way, if you decide you want to return to stock, you can do that quite easily. Also, if I was you, do the freezing technique I suggested earlier and use the safe list that's available.
If you keep CWM, do a Nandroid backup. You don't have to keep it on your SD, but they are great for doing a very fast recovery. I can usually restore my phone in about 10 - 15 minutes using Nandroid.

PaddyM said:
Dear CHRIST thank you for that - I didn't know about this feature, and it worked! I was able to connect to my PC and do everything I needed to. I used the command line to flash the CWM, then followed instructions for partitioning the SD card and installing a custom ROM. I feel like a real [email protected] I wonder if Anonymous are looking for any new recruits...
It did - I'm back in business!! Thank you mate, if I could fellate you via WiFi I probably would. You'd have to be wearing some anti-virus trousers though, I'm not a slut.
Cheers!
Click to expand...
Click to collapse
I'm happy it worked. Let's hope WiFi technology improves in the future

skezza said:
Great news (I thought you already knew about the recovery menu feature otherwise I'd have mentioned it).
Click to expand...
Click to collapse
I knew about the recovery menu (the stock one, at least) but I didn't realise I could go into the Fastboot option and for the phone to then be recognisable to the PC, thus making it possible to flash via the command line. If I had known that I probably wouldn't have needed to post this thread at all haha.
skezza said:
As I said in my reply earlier, every soft brick can be fixed somehow. Some are just harder than others. If I'm honest, it seems like yours was pretty straightforward once you got into the Recovery menu.
Click to expand...
Click to collapse
Yeah... I think if it happened to one of you guys you probably would have had it sorted in about 6 minutes. 3 days isn't bad for my first attempt though! hahaha
skezza said:
By the way, if you decide you want to return to stock, you can do that quite easily. Also, if I was you, do the freezing technique I suggested earlier and use the safe list that's available.
If you keep CWM, do a Nandroid backup. You don't have to keep it on your SD, but they are great for doing a very fast recovery. I can usually restore my phone in about 10 - 15 minutes using Nandroid.
Click to expand...
Click to collapse
Thanks for the advice man, I'll definitely be looking into the Nandroid backup option, although I hope I've learnt enough from this experience to have no need for it
Thanks to everyone who posted here, I appreciate the patience and the tolerance of my noobery.

Funnily enough, I tried TitaniumBackup today and the original poster is correct. While you can freeze, remove apps etc, you can't return them. especially system. I've not tried any of the alternative install methods that TB uses, but it's quite interesting.

TB is a bit quirky, I think. The system apps won't restore at all, but sometimes apps that I've downloaded myself will restore and other times they won't (the "Restoring App" notice just hangs there indefinitely). I usually find that forcing TB to close and then trying again does the trick, but I can't figure out why it happens in the first place.

Im wondering if anyone else has worked out a good configuration that will allow it to work every time?

[GUIDE] T-Mobile US One S - How to ROOT and flash ROMs

So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. You MUST use this interim CWM version for the moment, as the others do not work properly. Some things like USB mount dont work in this interim version, but the important functions like wipe and flash, backup and restore, and restart do work. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.

bump... i see US users still asking.
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.

Worked great for me
Sent from my HTC VLE_U using xda premium

So if we root and flash a custom ROM is there any way to get the phone back to factory state, and get rid of the *TAMPERED* and *UNLOCKED* notification??

Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?

cyberchuck9000 said:
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
Click to expand...
Click to collapse
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.

nickmv said:
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Click to expand...
Click to collapse
+1

androidcues said:
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
Click to expand...
Click to collapse
If you need to perform a hard reset on the One S, you hold down the power button for about 7-10 secs.

First of all, thanks for this thread...I used the HTC One S All in one tool kit to unlock my phone, unfortunately I miss understood one of the directions(#5) and stopped using the tool kit and followed another thread, much to my surprise, my bootloader is unlocked, hooray My question is, how do I get back to the original state if that is possible? The reason I ask, is I would like to go back and do it correctly...I used better terminal emulator to see if I had root, but all I got was the $ sign instead of the # sign So I would like to start over...
Thanks in advance for the help

I'm honestly not sure what the procedure is for relocking an HTC bootloader. Perhaps do some Google research on some of the latest models, and I bet you'll find something.
That being said, once you unlock the bootloader a single time, the best you can do is go to **RELOCKED** state. You'll never get back **LOCKED**. Once it's gone it's gone. I'm curious about the **TAMPERED** message though. That's an ugly word.

not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.

suhailtheboss said:
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
Click to expand...
Click to collapse
Uh oh that doesn't sound good
Sent from my HTC VLE_U using xda premium

yeah, tried reflashing both CWM & stock recovery. phone still boots to CWM everytime.
Luckily i can still access the phone via ADB, (while in recovery) so i'm sure i'll be able to sort it out. just need to take a fresh crack at it tomorrow. gonna switch back to my galaxy nexus tonight. (oh wait, i dont have any other phones that use microsim)
haha.

Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.

nickmv said:
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. Some things like USB mount dont work, but the important functions like wipe and flash and restart do. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart. I cant speak for the non-interim solutions, but from what I can gather, they are problematic, so avoid them for now.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
Click to expand...
Click to collapse
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.

Thongvilay said:
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Click to expand...
Click to collapse
That step is only if you want to flash ROMs, or need to wipe cache, dalvik, etc. CWM is used for flashing and recovery/backup purposes. If you're not using ROMs yet, then you have no need for it.

nickmv said:
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
Click to expand...
Click to collapse
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!

suhailtheboss said:
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
Click to expand...
Click to collapse
Wow, I have no idea dude. That sounds kinda crazy. Hopefully all will be well in the future and you won't come across it again.

the only variable i can think of is that i did have the phone about a week before launch. HTC mailed it to me directly.
I thought maybe that had somethign to do with it, but as far as i can tell the phone was the final shipping version.

I sent you a PM, trying to find a solution.

[Q] At&t One X: Boot Loop after Font Change

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

What software version were you on? 2.20 is not rootable, and previous versions (1.73, 1.85) correspond with different root methods.
The AT&T One X needs to be rooted and SuperCID before unlocking the bootloader, so that is why unlocking the bootloader failed.
What you have (red exclamation mark) is the stock recovery.
I'm betting that getting the RUU for your particular firmware version and running it, will get your phone back to working order. RUUs and other resources can be found in my index thread: http://forum.xda-developers.com/showthread.php?t=1671237

Verifying Software/Firmware version for RUU
redpoint73 said:
What software version were you on? 2.20 is not rootable, and previous versions (1.73, 1.85) correspond with different root methods.
Click to expand...
Click to collapse
Are you saying that the website I used to root my device (Believe it was ABD Daemon root) shouldn't have worked since if I was on 2.20 it couldn't have been rooted and if I was on (1.73 OR 1.85) a different website/rooting method than I used would've been necessary to root my device?
Also after rooting I wanted to make sure my device was rooted, and searched how to find out. I downloaded an app Root Checker and it verified I had Super user root access or whatnot.
redpoint73 said:
I'm betting that getting the RUU for your particular firmware version and running it, will get your phone back to working order. RUUs and other resources can be found in my index thread: http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
Which RUU do I need? Do they correspond to the software version I am running? Or is firmware version different? Since my phone is in a bootloop are there other ways to determine which software/firmware version I am using?
Once I have the correct RUU to download, do I just boot the device in fastboot and use command prompt to "zap?" it over?
Thank you redpoint73,
-LawyerLounge

Thanks for what you did provide
I installed 1.82 RUU onto my device (found out my version was 1.73) and it factory reset my phone! Thank you for your help, could have had more help explaining how to go about choosing correct RUU, but I figured it out through process of elimination and got the right RUU i guess.
Thanks for your partial help,
LawyerLounge

LawyerLounge said:
Are you saying that the website I used to root my device (Believe it was ABD Daemon root) shouldn't have worked since if I was on 2.20 it couldn't have been rooted and if I was on (1.73 OR 1.85) a different website/rooting method than I used would've been necessary to root my device?
Click to expand...
Click to collapse
No what I am saying is "what firmware are you on", lol
A questions you never did answer.
And no, 2.20 is not rootable, and I don't think you out of everyone here magically found a 2.20 root solution when nobody else (including very talented and experienced developers) has been able to.
---------- Post added at 09:16 AM ---------- Previous post was at 09:12 AM ----------
LawyerLounge said:
Thank you for your help, could have had more help explaining how to go about choosing correct RUU,
Click to expand...
Click to collapse
I wasn't online at the time you asked the question about the RUU.
---------- Post added at 09:22 AM ---------- Previous post was at 09:16 AM ----------
LawyerLounge said:
Which RUU do I need? Do they correspond to the software version I am running? Or is firmware version different? Since my phone is in a bootloop are there other ways to determine which software/firmware version I am using?
Click to expand...
Click to collapse
RUU for your current version is the best way. Higher numbers will also work, but never lower numbers (downgrades are not normally allowed, without things like SuperCID). But I only recommend running a higher number RUU, if you know what has been changed, and are okay with those changes. For instance, 2.20 plugs the holes by which root was obtained, and also has a patched hboot that plugs the holes by which kernels and radios could be flashed from recovery. So I believe the 2.20 RUU would have worked, but also would have left you stuck without root.
I asked the firmware versions, hoping that you already knew what it was. You really shouldn't be rooting and modding the phone, without knowing what firmware version you are on.

[Q] Unable to return to install recovery / return to stock

Trouble here - sending HOX in for warranty replacement, already received new phone (original could not connect to 4g/lte, only edge) and am unable to run RUU to return to stock
bootloader screen info:
tampered/relocked
s-on
hboot - 1.09
on 1.85
I can boot into phone and use it, but when connecting to pc, get driver error 10 (cannot start) - however, when i plug in new phone, the driver works fine. This driver issues has occurs on multiple pc's - if it wasn't for this, I would be fine. Phone is still rooted. Also, I can browse files on phone when using disk mode, but when charge only, the "my htc" driver says it cannot start - this is preventing me from using any toolkits/running RUU, which I desperately need to do for warranty purposes. This means it is not recognized by adb/fastboot.
Cannot boot into recovery - tried installing through rom manager (says recovery flashed, but just goes back to bootloader when choosing recovery)
Please, let me know what other info you need - I've tried to be complete in my description, but that doesn't mean I was
I have searched forums, but haven't found my particular issue addressed - being unable to install/boot into recovery or connect to PC properly to return to stock

I saw Rom manager and I thought eek... Flash twrp

a box of kittens said:
I saw Rom manager and I thought eek... Flash twrp
Click to expand...
Click to collapse
I have tried installing twrp - it was installed, but now the folder is gone - CWM was a second choice, and ROM manager was a last ditch effort in attempting to install a recovery - ROM manager even says that CWM is installed, but agian, when in bootloader and choosing recovery, it just boots back into bootloader. That's the root (no pun intended - or was it of the problem - I am unable to boot into recovery at all, nor can I use fastboot when connected to pc due to driver error - the same driver that functions properly when connecting my replacement phone.

futureprimate said:
I have tried installing twrp - it was installed, but now the folder is gone - CWM was a second choice, and ROM manager was a last ditch effort in attempting to install a recovery - ROM manager even says that CWM is installed, but agian, when in bootloader and choosing recovery, it just boots back into bootloader. That's the root (no pun intended - or was it of the problem - I am unable to boot into recovery at all, nor can I use fastboot when connected to pc due to driver error - the same driver that functions properly when connecting my replacement phone.
Click to expand...
Click to collapse
Just download goo.im hit menu install open recovery then install.
Sent from my One X using Tapatalk 2

Kole_Ackerson said:
Just download goo.im hit menu install open recovery then install.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I've attempted to install recovery with goo manager as well - it states that recovery script is installed, but when attempting to boot into recovery, it just jumps back to the bootloader - that is what has got me biting my nails. Any ideas as to why I can't boot into recovery despite the fact that goo manager states that twrp was installed?

Finally able to kind of use fastboot - was able to reboot phone using fastboot, but cannot flash recovery image. When I use fastboot to look for devices I get this:
C:\oneX>fastboot devices
|÷cl≈═?/?π┌?╨
ñ fastboot
Not a typo - I get the mysterious message. Just some more info in case anyone can assist.

I'm willing to bet something on the phone is damaged, probably the miniUSB port. You're getting garbage because the phone can't communicate properly.

iElvis said:
I'm willing to bet something on the phone is damaged, probably the miniUSB port. You're getting garbage because the phone can't communicate properly.
Click to expand...
Click to collapse
Interesting thought - I had considered that, but I can connect in other ways (disk drive, etc.) as well as using fastboot to reboot into hboot - so I had discounted that possibility. I suppose I should not have....
That's why this is so frustrating - I can do some things, but not others - and I still don't understand why I am unable to flash a custom recovery, even just using goo manager or similar tool. Why would that be affected by my miniUSB port?
I have 4 days to send this one back for warranty (as stated earlier - I have the replacement already) - I'll probably pull my hair out trying until then :cyclops:
Thanks for the responses so far folks!

1.85, so AT&T right? AT&T seems pretty lax about checking bootloader, root, etc. for warranty returns. There have even been a few folks on here that sent phones running CM10 and other custom ROMs for warranty repair, with no issues. It seems you are on the stock ROM at least. Just make sure you go through AT&T, and not HTC (which are much more strict).

futureprimate said:
That's why this is so frustrating - I can do some things, but not others - and I still don't understand why I am unable to flash a custom recovery, even just using goo manager or similar tool. Why would that be affected by my miniUSB port?
Click to expand...
Click to collapse
You're right, the port would not affect any of that.
Still, something on your phone is corrupted. This is the same phone that could not connect to LTE? That suggests you've probably got hardware gremlins in there somewhere.
As redpoint said, don't worry about being rooted on the return. AT&T doesn't seem to care.

iElvis said:
You're right, the port would not affect any of that.
Still, something on your phone is corrupted. This is the same phone that could not connect to LTE? That suggests you've probably got hardware gremlins in there somewhere.
As redpoint said, don't worry about being rooted on the return. AT&T doesn't seem to care.
Click to expand...
Click to collapse
Well good gravy then it is through Att - - thanks for putting an alleged gentleman's mind at ease.
Although I have to say, this makes for a good case study all around - it truly is bizarre how some things seem to work while others don't -
at this point I'll just focus on clearing all personal data - no wipes seem to work either .
Again - thanks to the damn fine XDA community for the support - it's inspired me to figure out solutions on my own, while still knowing that there are fine folks willing to offer assistance in a pinch.
It's a good lesson that is repeated here often - do the research first! You learn a lot by breaking things

futureprimate said:
Well good gravy then it is through Att - - thanks for putting an alleged gentleman's mind at ease.
Although I have to say, this makes for a good case study all around - it truly is bizarre how some things seem to work while others don't -
at this point I'll just focus on clearing all personal data - no wipes seem to work either .
Again - thanks to the damn fine XDA community for the support - it's inspired me to figure out solutions on my own, while still knowing that there are fine folks willing to offer assistance in a pinch.
It's a good lesson that is repeated here often - do the research first! You learn a lot by breaking things
Click to expand...
Click to collapse
You can't flash recovery with a locked bootloader and S-ON (you relocked already judging by OP)... You can run the RUU from within bootloader, while in fastboot after it has been relocked and the RUU will flash stock recovery (assuming ofcourse fastboot driver works as it seems not to be). Good Luck!

exad said:
You can't flash recovery with a locked bootloader and S-ON (you relocked already judging by OP)... You can run the RUU from within bootloader, while in fastboot after it has been relocked and the RUU will flash stock recovery (assuming ofcourse fastboot driver works as it seems not to be). Good Luck!
Click to expand...
Click to collapse
Good advice, but the damn fastboot driver appears to be the rub - thought I had it, but now I get an error from the RUU regarding the charge (below %30 -- but it's fully charged of course). So all sorts of weirdness!

Did I just brick my OPO?

Hey everyone.
I was using a custom ROM, just to try Lollipop, and saw the OTA rolling out today.
I started Bacon Root Toolkit and returned my phone to stock, with the 4.4.4 original ROM, with the automatic download.
Then I tried updating it through the phone, but the OTA was not available for me yet. So I downloaded the file everyone was using to manually update it (cm-12.0-YNG1TAS0YL-bacon-signed.zip).
Used to same option on BRT to return to stock but this time selected the zip file I downloaded.
It started ok, with the prompt window showing the files pushed to the phone, like modem, system, cache, etc.
But then it stopped, waiting for the device.
I looked at it and the screen was turned off. I had full battery.
Waited some minutes and nothing. The phone was not recognized anymore. And it's also not turning on.
Any idea what happened and what I can do?
Thanx.

Cappelletti said:
Hey everyone.
I was using a custom ROM, just to try Lollipop, and saw the OTA rolling out today.
I started Bacon Root Toolkit and returned my phone to stock, with the 4.4.4 original ROM, with the automatic download.
Then I tried updating it through the phone, but the OTA was not available for me yet. So I downloaded the file everyone was using to manually update it (cm-12.0-YNG1TAS0YL-bacon-signed.zip).
Used to same option on BRT to return to stock but this time selected the zip file I downloaded.
It started ok, with the prompt window showing the files pushed to the phone, like modem, system, cache, etc.
But then it stopped, waiting for the device.
I looked at it and the screen was turned off. I had full battery.
Waited some minutes and nothing. The phone was not recognized anymore. And it's also not turning on.
Any idea what happened and what I can do?
Thanx.
Click to expand...
Click to collapse
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon

timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone.
Click to expand...
Click to collapse
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)

Spannaa said:
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Click to expand...
Click to collapse
Thanks man, good to know.
Transmitted via Bacon

Spannaa said:
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Click to expand...
Click to collapse
That's why I tried it. People were using it on TWRP.
As I had just returned the phone to stock I didn't have a modified recovery. So I used BRT.
I had flashed lots of times before. On previous phones and tablets. Found BRT just yesterday.
I'll take a look at the provided link in a moment. I'll let you guys know if it worked for me.
Thanx.

timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
Click to expand...
Click to collapse
I didn't try it yet, but I forgot to mention that the phone is totally dead. No lights or whatever. Neither the charging light is turning on.

Cappelletti said:
I didn't try it yet, but I forgot to mention that the phone is totally dead. No lights or whatever. Neither the charging light is turning on.
Click to expand...
Click to collapse
Numerous people who had phones which were showing absolutely no signs of life whatsoever have revived their phones using that unbrick tool I linked you to. All indications from these phones were that they were hard bricked but that tool saved them, it might take several attempts and a few hours but it's worth a try.
Transmitted via Bacon

timmaaa said:
Numerous people who had phones which were showing absolutely no signs of life whatsoever have revived their phones using that unbrick tool I linked you to. All indications from these phones were that they were hard bricked but that tool saved them, it might take several attempts and a few hours but it's worth a try.
Transmitted via Bacon
Click to expand...
Click to collapse
I'll try it, for sure.
Thanx.

timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
Click to expand...
Click to collapse
IT WORKED!
It was 1am yesterday when I messed up, so I decided to create the thread here and go sleep, after some troubleshooting that didn't work. I believe I'd come accross that thread you pointed, but thanks for it.
I mean... really, THANX!

Cappelletti said:
IT WORKED!
It was 1am yesterday when I messed up, so I decided to create the thread here and go sleep, after some troubleshooting that didn't work. I believe I'd come accross that thread you pointed, but thanks for it.
I mean... really, THANX! [emoji14]
Click to expand...
Click to collapse
Awesome, no worries, glad to help.
Transmitted via Bacon