Database Info

bricked one x

So earlier i attempted to do the 2.2 root.
i managed to get as far as rooting, installing superuser and CWM
now, the problem is when i went to flash the rom, i tried to run the super wipe, but was getting errors about the sdcard not being able to be mounted. and the wipe was not performed/failed/aborted etc
i tried to run flash the rom still, it loaded, but still gave an error at the end and did not work.
reboot the phone, and i get the HTS quietly brilliant screen with red text that says"this build is for development purposes only...." and from here it does nothing but constantly reboot to this screen.
i am able to get to the bootloader screen, and fastboot works.
ive tried factory resetting the phone, as well as using the CWM recovery. i am unable to do any. as the CWM cannot write to e:\sd card
its not mounted, and i cannot mount it, when i try to reformat the sd card, it says it is unmounted.
mount usb storage was not working either, and said files were missing.
i read on other threads about needing the sd card reformatted, but the one x has an internal card.
please help
i feel like it can be fixed, but im really worried my phone is bricked
eta: i tried to revert to the stock ruu, but i think i should have read it more clearly.
so i guess i flashed the ruu that was NOT 2.2
now my CWM is gone, and i can only get onto the bootloader and fast boot
under fastboot devices my device's serial does show up
ETA: i reflashed with twrp, managed to wipe my sdcard, and am now able to mount.
from here my phone is still not able to boot up.
i can attempt to run the super wipe, but am still getting an error
"E:error in /sdcard"

chinaman_chong said:
So earlier i attempted to do the 2.2 root.
i managed to get as far as rooting, installing superuser and CWM
now, the problem is when i went to flash the rom, i tried to run the super wipe, but was getting errors about the sdcard not being able to be mounted. and the wipe was not performed/failed/aborted etc
i tried to run flash the rom still, it loaded, but still gave an error at the end and did not work.
reboot the phone, and i get the HTS quietly brilliant screen with red text that says"this build is for development purposes only...." and from here it does nothing but constantly reboot to this screen.
i am able to get to the bootloader screen, and fastboot works.
ive tried factory resetting the phone, as well as using the CWM recovery. i am unable to do any. as the CWM cannot write to e:\sd card
its not mounted, and i cannot mount it, when i try to reformat the sd card, it says it is unmounted.
mount usb storage was not working either, and said files were missing.
i read on other threads about needing the sd card reformatted, but the one x has an internal card.
please help
i feel like it can be fixed, but im really worried my phone is bricked
eta: i tried to revert to the stock ruu, but i think i should have read it more clearly.
so i guess i flashed the ruu that was NOT 2.2
now my CWM is gone, and i can only get onto the bootloader and fast boot
under fastboot devices my device's serial does show up
ETA: i reflashed with twrp, managed to wipe my sdcard, and am now able to mount.
from here my phone is still not able to boot up.
i can attempt to run the super wipe, but am still getting an error
"E:error in /sdcard"
Click to expand...
Click to collapse
Ruu back to stock 2.20
Edit.
If you can mount then connect to computer and try reinstalling boot image and the rom you were trying to install. Or adb
swagged out rooted jelly bean HOX

tae_254 said:
Ruu back to stock 2.20
Edit.
If you can mount then connect to computer and try reinstalling boot image and the rom you were trying to install. Or adb
swagged out rooted jelly bean HOX
Click to expand...
Click to collapse
so from mounting
im trying to install the Android Revolution HD 9.7.2 Ice Cream Sandwich
it allows me to choose settings, and such and start install.
after starting install, it goes through the files and such, but when it gets to /system/lib/ it just closes on itself, and goes back to twrp screen and recovery home. the rom never finishes installing. right now im gonna re-download the rom and see if that works.
if i cannot install the custom rom, how can i go back to stock exactly?
do i need to find the stock ruu?

fixed it.
turns out im stupid and was using a rom not compatible with this phone.
i flashed http://forum.xda-developers.com/showthread.php?t=1907324 so far, and it seems to be working
however, i prefer something closer to stock. can anyone suggest a rom?

hopefully you aren't using cwm anymore and flashed twrp for the evita.

chinaman_chong said:
fixed it.
turns out im stupid and was using a rom not compatible with this phone.
i flashed http://forum.xda-developers.com/showthread.php?t=1907324 so far, and it seems to be working
however, i prefer something closer to stock. can anyone suggest a rom?
Click to expand...
Click to collapse
I knew what you did the second I saw the words "Android Revolution", as that ROM does not exist for our phone.
Stick to the ROMs listed in our section of the forum (AT&T, Rogers HTC One X, Telstra One XL) in "Android Development" and "Original Android Devepment" here: http://forum.xda-developers.com/forumdisplay.php?f=1538
Or just use my handy index, which is an organized list of all our ROMs and mods:
http://forum.xda-developers.com/showthread.php?t=1671237
And apparently, you missed these:
http://forum.xda-developers.com/showthread.php?t=1813839
http://forum.xda-developers.com/showthread.php?t=1944712
http://forum.xda-developers.com/showthread.php?t=1952942

CleanROM on Viper XL
---------- Post added at 12:14 PM ---------- Previous post was at 12:13 PM ----------
chinaman_chong said:
however, i prefer something closer to stock. can anyone suggest a rom?
Click to expand...
Click to collapse
CleanROM or Viper XL

redpoint73 said:
I knew what you did the second I saw the words "Android Revolution", as that ROM does not exist for our phone.
Stick to the ROMs listed in our section of the forum (AT&T, Rogers HTC One X, Telstra One XL) in "Android Development" and "Original Android Devepment" here: http://forum.xda-developers.com/forumdisplay.php?f=1538
Or just use my handy index, which is an organized list of all our ROMs and mods:
http://forum.xda-developers.com/showthread.php?t=1671237
And apparently, you missed these:
http://forum.xda-developers.com/showthread.php?t=1813839
http://forum.xda-developers.com/showthread.php?t=1944712
http://forum.xda-developers.com/showthread.php?t=1952942
Click to expand...
Click to collapse
OMFG ..how did you get all these results, did you by any chance use that esoteric SEARCH functionality ?
Now all i have to do is read ?? Could you also pre-chew my food please ? :silly:

Crappyvate said:
OMFG ..how did you get all these results, did you by any chance use that esoteric SEARCH functionality ?
Now all i have to do is read ?? Could you also pre-chew my food please ? :silly:
Click to expand...
Click to collapse
I didn't even have to use the search function. 2 are near the top of General. The remaining has slipped past the first page, but its still pretty high up there.
People who flash a ROM for the international version are simply neglecting to do any basic reading and learning before flashing things willy-nilly, that's my point.

thanks for the help guys. i flashed viper xl yesterday night right after, loving it thus far. i was just so used to the sense keyboard already, and hated the cramped jb keyboard, and this rom has simple little tweaks
i did read, but i guess not thoroughly enough. in hindsight, i wasnt aware that the one x was different than the xl, its fairly easy to miss that the other roms are not compatible with this phone. and is completely different alltogether.
if i had known that, i wouldnt have flashed cwm, and would not have need to post a help thread. all "solutions" i attempted on my own were based off readings of the hox, rather than the evita, once again causing more problems. it was easily enough fixed once i figured that bit of information out.
i am a noob, but this phone is not my first time rooting, so with my prior knowledge i felt i was more than ready to tackle this rom flashing, im sure plenty of others will make the same mistake as i did.
the other phones ive rooted and flashed had their one model of phone only, so all the roms available were compatible.
im just glad my phone is not bricked, and i now have root access

chinaman_chong said:
So earlier i attempted to do the 2.2 root.
i managed to get as far as rooting, installing superuser and CWM
now, the problem is when i went to flash the rom, i tried to run the super wipe, but was getting errors about the sdcard not being able to be mounted. and the wipe was not performed/failed/aborted etc
i tried to run flash the rom still, it loaded, but still gave an error at the end and did not work.
reboot the phone, and i get the HTS quietly brilliant screen with red text that says"this build is for development purposes only...." and from here it does nothing but constantly reboot to this screen.
i am able to get to the bootloader screen, and fastboot works.
ive tried factory resetting the phone, as well as using the CWM recovery. i am unable to do any. as the CWM cannot write to e:\sd card
its not mounted, and i cannot mount it, when i try to reformat the sd card, it says it is unmounted.
mount usb storage was not working either, and said files were missing.
i read on other threads about needing the sd card reformatted, but the one x has an internal card.
please help
i feel like it can be fixed, but im really worried my phone is bricked
eta: i tried to revert to the stock ruu, but i think i should have read it more clearly.
so i guess i flashed the ruu that was NOT 2.2
now my CWM is gone, and i can only get onto the bootloader and fast boot
under fastboot devices my device's serial does show up
ETA: i reflashed with twrp, managed to wipe my sdcard, and am now able to mount.
from here my phone is still not able to boot up.
i can attempt to run the super wipe, but am still getting an error
"E:error in /sdcard"
Click to expand...
Click to collapse
Do not use CMW it causes lot of problems(not recommended for our device) . Use TWRP recovery instead
Sent from my HTC One XL using xda premium

redpoint73 said:
I knew what you did the second I saw the words "Android Revolution", as that ROM does not exist for our phone.
Click to expand...
Click to collapse
That and Superwipe. I remember that zip from other phones I used that rom on.
Sent from my HTC One XL

Dang you guys are slipping through the cracks in the bricks lol, excuse my pun. You are lucky. You're the only person I've seen that has flashed android revolution and not overwrite boot and having a beautiful brick lol.
Subscribe to the OneXL forums and stay here till you recognize your community!
Sent from my HTC One XL using xda app-developers app

can't brick from it after 2.20

DvineLord said:
can't brick from it after 2.20
Click to expand...
Click to collapse
Good thing eh
Sent from my HTC One XL using xda app-developers app

InflatedTitan said:
Dang you guys are slipping through the cracks in the bricks lol, excuse my pun. You are lucky. You're the only person I've seen that has flashed android revolution and not overwrite boot and having a beautiful brick lol.
Click to expand...
Click to collapse
From what others are saying, the newer hboot that came with 2.20 is write protected. Hboot can't be overwritten by flashing a ROM for the international One X. ROM just fails to flash, and you get a recoverable condition like this one, as opposed to hard bricks on the older hboot.

Yea, at least there's one good thing that came with the dreaded update
Sent from my HTC One XL using xda app-developers app

How do i ruu back to stock 2.20? I unlocked my device. Tried flashing the boot.img but after I couldnt mount my sdcard to flash the rest of the ROM. I can enter recovery and bootloader though. Really need some help

h1m said:
How do i ruu back to stock 2.20? I unlocked my device. Tried flashing the boot.img but after I couldnt mount my sdcard to flash the rest of the ROM. I can enter recovery and bootloader though. Really need some help
Click to expand...
Click to collapse
If you want to ruu grab the ruu file...lock your bootloader from within fastboot and run the ruu

omario8484 said:
If you want to ruu grab the ruu file...lock your bootloader from within fastboot and run the ruu
Click to expand...
Click to collapse
Where do i get the ruu file? I can't mount my sdcard

[Q] Bootloop after rebooting

Well I've been having this problem for a while, my phone goes into a bootloop whenever I restart it. It shows the white HTC screen, goes black, then the white HTC screen...over and over again.
The only way I have found to get it to boot up normally is when I connect a USB cable to it
But if I remove the cable and reboot, I get the same problem again.
Any ideas? Has anyone had this happen before??

That may be a Hardware issue. They easiest way I can think of is to RUU back to Stock, and Reformat the SD Card. If it still does it, then it may be a Hardware related issue.

CNexus said:
Well I've been having this problem for a while, my phone goes into a bootloop whenever I restart it. It shows the white HTC screen, goes black, then the white HTC screen...over and over again.
The only way I have found to get it to boot up normally is when I connect a USB cable to it
But if I remove the cable and reboot, I get the same problem again.
Any ideas? Has anyone had this happen before??
Click to expand...
Click to collapse
I've had that happen a couple times but it was because it was something I did/flashed, I agree with prboy, ruu back and format memory card (save your stuff to the computer first)- I've forgotten to save first a couple times

prboy1969 said:
That may be a Hardware issue. They easiest way I can think of is to RUU back to Stock, and Reformat the SD Card. If it still does it, then it may be a Hardware related issue.
Click to expand...
Click to collapse
I'll definitely try that, I don't know if this shed anymore light on it but my sdcard doesn't mount through my phone anymore either...happened around the same time as the restarting thing
But I'll tr and see what happens, if not I'll just take it in to sprint, I know it can't be something I flashed, I've been on stock for a while because of my utility
Sent from my PG06100 using xda premium

I would start by Formatting the SD Card. Then if that doesn't resolve issue. Format the SD Card again, and then RUU. If at that point the issue is still present, it's time to take it in to Sprint. Out of curiosity, are you using a custom Kernel ? Reason I ask is that I've run across something slightly similar after Flashing an Experimental Kernel Dirty. Meaning I did not wipe Cache, or Dalvik before Flashing. Mind you this was a very long time ago, in my HERO days. But I seem to remember it acting sort of like the symptoms you described.

prboy1969 said:
I would start by Formatting the SD Card. Then if that doesn't resolve issue. Format the SD Card again, and then RUU. If at that point the issue is still present, it's time to take it in to Sprint. Out of curiosity, are you using a custom Kernel ? Reason I ask is that I've run across something slightly similar after Flashing an Experimental Kernel Dirty. Meaning I did not wipe Cache, or Dalvik before Flashing. Mind you this was a very long time ago, in my HERO days. But I seem to remember it acting sort of like the symptoms you described.
Click to expand...
Click to collapse
Nope, no custom anything. 100% stock 2.2 with temproot, but since I can't reboot its really permroot lol
Sent from my PG06100 using xda premium

Then I would defiantly try what I stated above. See if it can resolve the issue.

prboy1969 said:
Then I would defiantly try what I stated above. See if it can resolve the issue.
Click to expand...
Click to collapse
Will do
Sent from my PG06100 using xda premium

Getting the same issues. I've tried ruu through both the exe and pg06 img. Tried factory reset with no luck, in the stock recovery ive wiped everything with no luck also. It's read by fastboot and i can issue commands, flashing through fastboot just gives me a sig verification failure. I've tried every method i've found and none have worked. Happened after downgrading to 2.2. I got temproot and went to permroot to go into this. I used htcdev to unlock the bootloader and it was successful. I cant access my sdcard since flashing the 2.2 ruu reverted it to stock and i cant get into the system to disk drive it. It boots for about 3 seconds then reboots. If any of the mmcblk... commands were mistyped or something was done wrong, how would i go about checking or fixing them if thats even possible? Any help or leads would be amazing.
SPEEDY XF SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot

KiDxNinja said:
Getting the same issues. I've tried ruu through both the exe and pg06 img. Tried factory reset with no luck, in the stock recovery ive wiped everything with no luck also. It's read by fastboot and i can issue commands, flashing through fastboot just gives me a sig verification failure. I've tried every method i've found and none have worked. Happened after downgrading to 2.2. I got temproot and went to permroot to go into this. I used htcdev to unlock the bootloader and it was successful. I cant access my sdcard since flashing the 2.2 ruu reverted it to stock and i cant get into the system to disk drive it. It boots for about 3 seconds then reboots. If any of the mmcblk... commands were mistyped or something was done wrong, how would i go about checking or fixing them if thats even possible? Any help or leads would be amazing.
SPEEDY XF SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Click to expand...
Click to collapse
So at this point your just trying to run the RUU ? Or do you still want to achieve Root ?

prboy1969 said:
So at this point your just trying to run the RUU ? Or do you still want to achieve Root ?
Click to expand...
Click to collapse
I had temp root and in between gaining perm root this happened. Root does me no good if I'm boot looped and can't even adb. I'm trying to get the phone to boot. Or read through adb. I can't fast boot any of the partitions either so I'm basically stuck in limbo

KiDxNinja said:
I had temp root and in between gaining perm root this happened. Root does me no good if I'm boot looped and can't even adb. I'm trying to get the phone to boot. Or read through adb. I can't fast boot any of the partitions either so I'm basically stuck in limbo
Click to expand...
Click to collapse
Have you tried booting it up while connected to a USB cord? That works for me because my phone will otherwise go into a bootloop whenever I restart it
Sent from my PG06100 using xda premium

KiDxNinja said:
I had temp root and in between gaining perm root this happened. Root does me no good if I'm boot looped and can't even adb. I'm trying to get the phone to boot. Or read through adb. I can't fast boot any of the partitions either so I'm basically stuck in limbo
Click to expand...
Click to collapse
Are you trying the PG06IMG , or the RUU.exe ? Have you tried doing the 2.2 RUU.exe through Fastboot ?

prboy1969 said:
Are you trying the PG06IMG , or the RUU.exe ? Have you tried doing the 2.2 RUU.exe through Fastboot ?
Click to expand...
Click to collapse
Yes and Yes, read my first post -_-

KiDxNinja said:
Yes and Yes, read my first post -_-
Click to expand...
Click to collapse
Must have missed that somehow. My bad . But on to the issue at hand. I'm wondering if maybe your SD Card went wonky. I would remove the SD Card, format it. Load the PG06IMG back onto the Card, reinstall. Then try to flash it. Of course backup your card to the PC first.
TEAM MiK
MikROMs Since 3/13/11

prboy1969 said:
Must have missed that somehow. My bad . But on to the issue at hand. I'm wondering if maybe your SD Card went wonky. I would remove the SD Card, format it. Load the PG06IMG back onto the Card, reinstall. Then try to flash it. Of course backup your card to the PC first.
TEAM MiK
MikROMs Since 3/13/11
Click to expand...
Click to collapse
Tried this with same result. flashing through hboot works for the 2.2 ruu, but im still stuck in the bootloop.
I also tried flashing a custom recovery via hboot, but the pgo6img loads then doesnt ask me if i want to update or not. I have literally no idea where to go or what to check.

KiDxNinja said:
Tried this with same result. flashing through hboot works for the 2.2 ruu, but im still stuck in the bootloop.
I also tried flashing a custom recovery via hboot, but the pgo6img loads then doesnt ask me if i want to update or not. I have literally no idea where to go or what to check.
Click to expand...
Click to collapse
Its not pgo6img. Its PG06IMG.zip. its a zero before the 6 not the letter "o". Idk if capitalized letters matter or not but I always capitalize all the letters
Sent from my EVO using Tapatalk 2

YoungCorruptionV2.0 said:
Its not pgo6img. Its PG06IMG.zip. its a zero before the 6 not the letter "o". Idk if capitalized letters matter or not but I always capitalize all the letters
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I was just about to say that, if the name of the file isn't correct, the bootloader won't pick it up.

Yeah i know, i was just too lazy to type it out. I know what im doing as far as general modding and flashing, and I actually managed to fix it. I'm not positive how but I used the unroot back to stock guide for the stock locked bootloader. After flashing it through hboot I tried the 2.3.4 RUU. Still bootlooped but I was at stock with locked bootloader. I then used htcdev to reunlock the bootloader and I was then able to flash partitions through fastboot. I flashed cwm and was able to adb through it. I basically just reran through the rooting phase and gained temproot. From here I redid the steps to engineer hboot and finally received s-off. After this it booted normally. I might be leaving steps out but if anyone needs specifics, just pm me and maybe I can figure it out again for you.
Sent from my PG06100 using Tapatalk 2

help with boot loop loop loop
hi
someone can help whit phone?
in summer i restart phone and it stuck in loop htc logo in white over and over agen
till batrtery go down and nothing happen when trying to charg only led was flashing
no to long ago i plug to charger ad phone torn back on, sd card was out
I turn it off put sd card back on phone turn back on, try to software update one and second time it go back to loop agen=[
rand battery down agen and it does not torn back on, to hboot
well it does if i play whit it holding power bottom volume down longer time
speed xe ship s-on
hboot-0.99.0001
radio-1.08.01.0111
emmc-boot
can some one give me step by step instruction?

[Q] Help, may have bricked

A little foreshadow. I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install. I was silly and decided to clear the system... Which erased my OS completely.
For a while I was able to get to the TWRT(?) screen where I could mount my sd card, etc. While researching the problem I came across this:
a solution of fastbooting a recovery.img
I ran the fastboot recovery.img. The only problem is the only screen I can now access is the bootloader. I have bootloader 1.14.0002 loaded onto my phone if that helps.
Is there anyway to try to get a operating system or flash a rom onto this phone still or is it bricked for good? Also if I was able to put a rom onto it, what do you sugggest?
When I try to go to Recovery or Factory Reset, I get the HTC screen with the red text underneath it and it never goes any further.
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
That is the information listed in my bootloader as of now. I am not showing it listed as a drive in my computer when connected to USB. Also when I 'power off' I am in a reset cycle that doesn't stop.
I really appreciate any help in advance. This was a big wake up call to myself about how I should be a lot more careful when messing with these things.
Thank you to everyone that answers!

http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
You might be hosed. Can you get into bootloader?
Sent from my One X using xda premium

Read before doing anything. Such a simple task. It's easy to read, it's hard to come back from a brick.
Sent from my One XL using XDA Premium

You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer. http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.0-evita.img
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2

Not only does fastboot erase cache not take long it avoids many stupid little issues. I would say it's a must when flashing a new recovery.
Sent from my One X using xda app-developers app

sinkthehalffoot said:
I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install.
Click to expand...
Click to collapse
The reason it went to recovery is very simple. The OTA needs to have stock recovery in order to install. You don't have stock recovery on your phone anymore, you have custom recovery (TWRP). So the OTA stalled there, when it didn't find stock recovery.
sinkthehalffoot said:
I was silly and decided to clear the system... Which erased my OS completely.
Click to expand...
Click to collapse
Of course it did, what were you expecting to happen? Wiping the OS is the very definition of what happens when you wipe system. If you didn't know what wiping system would do, you shouldn't have done it. For that matter, you shouldn't be doing anything on your phone if you don't know what its for.
A lot of this points to a fundamental lack of reading and understanding:
- Don't know the name of the custom recovery installed on the system
- Wiping things without knowing what they are
- Basic rule (that many folks here seem to ignore, for reasons unknown): Don't install any OTA on a rooted device without first researching what will happen
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
You aren't bricked. With very few exceptions (and this isn't one of those) if the screen turns on, and you can get into hboot, the phone is recoverable. And probably fairly easily so, with the right steps. But you need to do some homework before proceeding.

redpoint73 said:
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
Click to expand...
Click to collapse
+1000
This is exactly the kind of situation that occurs when people get in over their heads and start blundering around.
http://forum.xda-developers.com/showthread.php?t=2232141

InflatedTitan said:
You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer.
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
In case anyone ends up stumbling here with a similar issue, this solution worked to a 'T'. Thank you again InflatedTitan.
To everyone else, yes I know, I should of read more than I had. I saw the jellybean update and have been wanting it for a while and acted with haste. I learned a valuable lesson from it all.

Lol this "solution" was around before you posted. You just didn't read or search enough.
Sent from my One X using xda app-developers app

F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium

Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Lol :beer:
Sent from my HTC One X using xda app-developers app

Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2

InflatedTitan said:
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I thought I was the only one. In fact I just rooted a nook tablet and installed twrp. Slides to flash... And I could swear I was on cloud 9.
But bravo on the explanation sir. Love a good write up. Even though i already know it, feels good to read it.
Sent from my Carbon-ize Evita using xda-developers app

[HELP] Not sure if bricked or hardware issue?
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28

pharrjw said:
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Click to expand...
Click to collapse
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?

exad said:
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?
Click to expand...
Click to collapse
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?

If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Sent from my HTC One X using xda app-developers app

pharrjw said:
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?
Click to expand...
Click to collapse
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.

Thanks again for the replies guys.
31ken31 said:
If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Click to expand...
Click to collapse
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
exad said:
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.
Click to expand...
Click to collapse
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.

pharrjw said:
Thanks again for the replies guys.
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.
Click to expand...
Click to collapse
factory reset in bootloader corrupts the SD card. We wont worry about that just yet as there's nothing we can do about it until we can get recovery on there.
You're going to have to be very careful because it sounds like your EMMC partitions might have some issues. if you can get it to bootlaoder KEEP IT AT THAT SCREEN. don't power it off or anything, leave it there. Because one wrong move could be a perma brick. If we can get a rom on there to S-OFF with, we can RUU to restore your emmc partitions.

[Q] HTC One X: Stock, stuck in bootloop, need to recover pics please!

Hello, newb here with a problem...
My girlfriend's phone (HTC One X) randomly reboots today and gets stuck in a bootloop, HTC screen and then black, over and over... seems like it won't load the OS. I do a little research and manage to time it just right to get it into HBOOT and just shut it down so I can try and figure out the problem later.
I have no experience rooting phones, minimal experience with Linux and Java coding. Her phone is new, bought unlocked with GSM carrier bands. She lives in Romania and will be taking the phone home with her in a week, so no SIM card yet, just airplane mode and wifi. This does mean I'm on a timetable to get it fixed though, it needs to work before she leaves as I'm not sure of the support she may get back home.
The boot screen shows the following:
***LOCKED***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT- 1.14.0002
RADIO- 0.19as.32.09.11_2
OpenDSP- v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
HBOOT
<VOL UP>...
....
<POWER>...
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
POWER DOWN
Now, from what I've read, I may be able to fix the problem with a reset, but here is the hiccup... I need to save the pics and video that are on the phone. Is there any way to do this with a phone that is only stable powered on in HBOOT? Normal boot ALWAYS responds with a loop, HBOOT can sit for hours with no issue. I have my GF's laptop with Win 8 Pro and could do cmds if there is a way to get the phone recognizable by the computer.
I have searched for hours this afternoon/evening to try and find a similar problem, but it always seemed to be with rooting the phone. If anyone has ANY ideas how to save the pics and get this phone stable, I would be incredibly grateful. Thanks in advance! :laugh:

jkalbin said:
Hello, newb here with a problem...
My girlfriend's phone (HTC One X) randomly reboots today and gets stuck in a bootloop, HTC screen and then black, over and over... seems like it won't load the OS. I do a little research and manage to time it just right to get it into HBOOT and just shut it down so I can try and figure out the problem later. BTW picture and video are save on your SD card ....and make sure u don't wipe SD card during factory wipe from recovery......
I have no experience rooting phones, minimal experience with Linux and Java coding. Her phone is new, bought unlocked with GSM carrier bands. She lives in Romania and will be taking the phone home with her in a week, so no SIM card yet, just airplane mode and wifi. This does mean I'm on a timetable to get it fixed though, it needs to work before she leaves as I'm not sure of the support she may get back home.
The boot screen shows the following:
***LOCKED***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT- 1.14.0002
RADIO- 0.19as.32.09.11_2
OpenDSP- v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
HBOOT
...
....
...
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
POWER DOWN
Now, from what I've read, I may be able to fix the problem with a reset, but here is the hiccup... I need to save the pics and video that are on the phone. Is there any way to do this with a phone that is only stable powered on in HBOOT? Normal boot ALWAYS responds with a loop, HBOOT can sit for hours with no issue. I have my GF's laptop with Win 8 Pro and could do cmds if there is a way to get the phone recognizable by the computer.
I have searched for hours this afternoon/evening to try and find a similar problem, but it always seemed to be with rooting the phone. If anyone has ANY ideas how to save the pics and get this phone stable, I would be incredibly grateful. Thanks in advance! :laugh:
Click to expand...
Click to collapse
Firstable ......u might want to erase your IMEI and SN......u do not want to share it. Secondable.....u need to go to www.htcdev.com to unlock your bootloader & u would be able to install custom rom that more stable or u can flash beastmode kernel if u are on Android 4.2.2 sense 5 rom right now or u can just upgrade your firmware to 2.15 since u S-off and supercid
Swyped From BlueICESense_JBE

ted77usa said:
Firstable ......u might want to erase your IMEI and SN......u do not want to share it. Secondable.....u need to go to htcdev.com to unlock your bootloader & u would be able to install custom rom that more stable or u can flash beastmode kernel if u are on Android 4.2.2 sense 5 rom right now or u can just upgrade your firmware to 2.15 since u S-off and supercid
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
I have deleted those two from my post, but unfortunately you quoted them in your post and I can't delete that... do me a favor? Thanks.
I should have mentioned in the first post that I don't want to root her phone if I don't have to, first priority is to get it running. Second priority is to save the pictures that are on the phone. Everything I have read tells me that the SD contents will be deleted during a factory reset or when rooting, so I am saving those for a last resort.
Is there a way to upgrade the firmware without doing any resets?
btw- I am not the one who turned S-off, it came from the factory like that... fairly confusing to me. Thanks again!

jkalbin said:
I have deleted those two from my post, but unfortunately you quoted them in your post and I can't delete that... do me a favor? Thanks.
I should have mentioned in the first post that I don't want to root her phone if I don't have to, first priority is to get it running. Second priority is to save the pictures that are on the phone. Everything I have read tells me that the SD contents will be deleted during a factory reset or when rooting, so I am saving those for a last resort.
Is there a way to upgrade the firmware without doing any resets?
btw- I am not the one who turned S-off, it came from the factory like that... fairly confusing to me. Thanks again!
Click to expand...
Click to collapse
ERASED my quote....... Well if u like to mod your phone S-off is a good think u can just pretty much do anything with ur phone cuz it by passed security check point..... S-off......I see what u saying....Do not do factory reset from bootloader......try click on recovery by pressing vol up or down to navigate and see what comes up.......if twrp team win comes up.....u good to go.....choose back up ......and u can back all your files .....or connect ur phone to PC using USB cable and choose mount>USB mass storage and save all your files to pc
PS.....BTW if I somehow help you please hit thanks button.....
Swyped From BlueICESense_JBE

ted77usa said:
ERASED my quote....... Well if u like to mod your phone S-off is a good think u can just pretty much do anything with ur phone cuz it by passed security check point..... S-off......I see what u saying....Do not do factory reset from bootloader......try click on recovery by pressing vol up or down to navigate and see what comes up.......if twrp team win comes up.....u good to go.....choose back up ......and u can back all your files .....or connect ur phone to PC using USB cable and choose mount>USB mass storage and save all your files to pc
PS.....BTW if I somehow help you please hit thanks button.....
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
Thanks button hit, and I would gladly hit it a dozen times if I can get this phone to work long enough to recover pictures and then try a factory reset. On another forum someone had suggested putting the phone in a fridge for 5 minutes or so and that would somehow let it boot long enough to get the pics via USB. Idk about putting her phone in a fridge though... :silly:
I also forgot to mention I had tried recovery as well, I don't recall seeing TWRP, just 3 or 4 yellow lines of "cache error", then eventually a blue menu. From there I had tried "reboot", same problem. Got back to that screen and tried "clear cache", still the same thing.
Just got to recover again, looks like this:
Android system recovery <3e>
Use volume key to highlight;
click power key to select.
Reboot system now
Apply update from external storage
Wipe data/factory reset
Wipe cache partition
Apply update from cache
Apply update from internal storage
________________________________________
E:Can't open /cache/recovery/command
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
I have already tried the Reboot option and Clear cache option... should I next be trying to apply an update via external storage? If so, which update? I obviously can't update from internal since I can't send/receive files to the phone in its current state and I never put an update in the phone storage. Thanks again!

Unlock bootloader via HTC dev, install twrp 2.6 recovery then mount usb in recovery and you will have access to sd card
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
Unlock bootloader via HTC dev, install twrp 2.6 recovery then mount usb in recovery and you will have access to sd card
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Appreciate the help, I am still new to rooting and the like...
Won't unlocking the bootloader wipe the SD? Or will it just wipe the apps and data? I don't much care if I have to reinstall apps, but losing the SD contents I would like to avoid.
I'm also trying to avoid voiding the warranty as the phone is only a month old, is there any way to get the computer to "see" the sd contents through the bootloader without unlocking it? Perhaps a software that the computer could force the phone to show the sd?
Thanks again all!

I thought it wiped the sd until I did it some stuff was gone but my music and pics remained but that's just my experience, maybe someone else can chime in.
Sent from my HTC One XL using XDA Premium 4 mobile app

Ah, ok. I'll use that as a last resort then, not voiding the warranty has become a higher priority than recovering the pics. Unless someone suggests another option, I think a factory reset will happen tonight.
Thanks for the help guys, and any other suggestions are gratefully accepted!
Sent from my HTC One X+ using xda app-developers app

The unlock process only wiped my text messages but my images and music were untouched.
Sent from my Evita

Anyone have any experience with CPR? I don't know if it's worth it to wait until Monday to get them to try and fix it, if they could even do anything.
If it was my phone, I would root and reboot, but I don't want to risk messing up my gfs phone more than it is. Still open to suggestions, thanks a lot for the help everyone.
Sent from my HTC One X+ using xda app-developers app

Run RUU...
Sent from my HTC One XL using Xparent Green Tapatalk 2

Morning all
I'm in a similar situation...can anyone help?
Stock HTC with no mods, water damaged, had screen/cable replaced, after two days back with me screen went multi coloured, exclamation mark appeared on battery icon, phone stayed on at 1% battery with mains charger plugged in...now in bootloop and until until its run flat can I plug it into Mac to charge... Won't charge from mains
If there's a step by step guide to getting it stable enough to extract data (android file transfer doesn't work) that would be v helpful
Currently this is like death by a thousand cuts

Was there a conclusion? My wife has similar situation, but her contacts and notes are more important than pics. The phone froze on the updating of the software (trying to use HTC Syn).... Please let me know if there is a private solution as well. Pay to fix. my email: [email protected]
Peace,
Steven Chao

please help how to go back to stock

so i used sunshine to get s off, i downloaded twrp and rebooted, and got hit with the red text,
i run a logcat and i see proccess but it restarts about about 10 minutes to do the same thing.
something is wrong and i need to go back to ruu
i have no idea where to start
m8_wlv ship s off
cid vzw_001
hboot 3.16

freshkid87 said:
so i used sunshine to get s off, i downloaded twrp and rebooted, and got hit with the red text,
i run a logcat and i see proccess but it restarts about about 10 minutes to do the same thing.
something is wrong and i need to go back to ruu
i have no idea where to start
m8_wlv ship s off
cid vzw_001
hboot 3.16
Click to expand...
Click to collapse
What the heck do you mean hit with the red text? Does your phone boot?
My ruu threads are pretty self explanatory. I even have exe versions ready to go.
Sent from my Nexus 6 using Tapatalk

i got it, but it seems like the rom installed to the sd card rather than the internal storage... any fix?

freshkid87 said:
i got it, but it seems like the rom installed to the sd card rather than the internal storage... any fix?
Click to expand...
Click to collapse
Take the sdCard out of the phone. Boot into bootloader, then fastboot.
Then run one ofDottat's "exe" RUU's and it will repair the storage problem pronto.

now i get red text about htc

ugh, i can drag my roms to my internal but when i go to twrp it doesn't see them! this is so frustrating i've never had this much trouble flashing roms

freshkid87 said:
ugh, i can drag my roms to my internal but when i go to twrp it doesn't see them! this is so frustrating i've never had this much trouble flashing roms
Click to expand...
Click to collapse
One thread please. I closed your other two in this section.
Sent from my Nexus 6 using Tapatalk

freshkid87 said:
ugh, i can drag my roms to my internal but when i go to twrp it doesn't see them! this is so frustrating i've never had this much trouble flashing roms
Click to expand...
Click to collapse
Gonna have to run the exe RUU in order to get your partitions right.
Am guessing TWRP would see it in internal if everything was OK.