Database Info

[Q] HOX Evita in bootloop - can't get to bootloader/recovery

Hi - I just flashed ViperXL via TWRP (2.5, IIRC), but haven't flashed boot.img yet. Phone is now rebooting to the dev screen, then the One logo screen, then black again. I can't get to the bootloader or to TWRP. I've tried the volume-down button during boot to no avail. I've got ADB at the ready if needed...
S-On, hboot 1.14. I've done this many times before w/o issue.
Any ideas?

While the phone is rebooting just keep holding volume down. If it isn't working it's a case of bad timing. You need to flash the boot.img, why didn't you? Also, you should upgrade to TWRP 2.6 because 2.5 is full of bugs.
Sent from my Evita

I agree with timmaaa, failure to get into hboot if the screen comes on, is almost always a matter of not performing the button sequence correctly.
The most common errors while dooing this:
1) Letting go of the vol down rocker too early
2) If you press the vol down rocker after the white "HTC One X" boot splash screen is already up, its too late. You have to do it before the boot splash appears.
The most foolproof way to do it, is hold both vol down and power at the same time. Hold them for several seconds while the screen is on, and the capacitive buttons should flash a few times, then the screen should go black as the phone restarts. Let go of the power button ONLY, and DO NOT let go of the vol down rocker until the bootloader screen appears.
EDIT. Thanks (sarcastically) for solving your issue on another thread here, and then not updating us here. (cross posting is against the rules for a reason). I wasted my time trying to help, when you already solved it.

[Q] help me

viperXL installing 4.2.0 the installation Prosesa am alone in not moving for 20 minutes ... what should I do?

I press the power button and does not turn off ... help please

You have to be able to power off. If not your problem might be hardware related.
Hold the power button down how awhile. You should see the capacitive lights blink
What version of TWRP are you using?
Sent from my One X using XDA Premium 4 mobile app

Not enough information for us to help you.
S-off or S-on? If s-on, you have to manually flash boot.img in fastboot every time you flash a ROM.
What version of TWRP?

Thanks
just wait for it to wear down the battery and did not respond to the power button, connect the charger to start with the rom I had before installation could not understand what had happened, I have S-off, and bootloadre unlocked, the recovery is TWRP 2.6 ... is a Nomentum of desperation, I think it'll change as ROM after this almost heart-stopping moment, Thanks for the Replies

[Q] AT&T HTC One X Stuck at Viper XL Animation Screen

Hey guys,
I'll apologize in advance, since I'm sure I'm not the only one who's had this problem. I did try to use the search function, google, you name it. Didn't really come across any results that reflected my problem.
That all being said...
Tonight, my phone "died." I've been running Venom Viper XL for sometime now with no issues other than a pretty quick battery drain.
I was logging into 4square to check in tonight and I was getting a GPS error and a Wi-Fi disabled pop up. So I go into settings and check the Location stuff, turn the Google crap back on. Go back into 4square, same thing. I go back to the location settings, they were off again. Turned them back on. Saw that my wi-fi was enabled but "disconnected" so I disabled/enabled. Then my phone drops to the Viper XL splash screen. Tried to hold the power button to recycle it. HTC screen comes up, then to the Viper XL splash and stops. I tried a hard factory reset (volume down + power), same thing.
I can't get to anything. I plug it into my pc, can't get to anything.
I'm not sure what version of the Venom ROM I'm running. As far as I know, I haven't updated it in several months, even though something came out in September.
Am I stuck?

Firstly, volume down plus power isn't a factory reset, it's a hard reset. A factory reset is a very different thing. Have you tried flashing the ROM again or restoring a backup?
Sent from my Evita

timmaaa said:
Firstly, volume down plus power isn't a factory reset, it's a hard reset. A factory reset is a very different thing. Have you tried flashing the ROM again or restoring a backup?
Sent from my Evita
Click to expand...
Click to collapse
I just now was able to get into recovery. I'm running a back up and will go from there.
Thank you for responding though.

Ok, cool. In future you should probably exhaust possible options before creating a new thread though.
Sent from my Evita

timmaaa said:
Ok, cool. In future you should probably exhaust possible options before creating a new thread though.
Sent from my Evita
Click to expand...
Click to collapse
Like I said... I searched for a couple hours, so I thought I had. I can see how nearly every thread in here is pretty much started with "Search more." I didn't want to be one of those guys.
For anyone else reading that may have a similar issue:
As long as your phone turns on, you should be able to get to the bootloader. My problem was ignorance on this part, I didn't think I was able to.
1. Hold the power button + volume down until you get into the bootloader. I found that if I held these down, release when the screen went blank, then immediately pushed them down and held them, it got me into the bootloader.
2. Boot into recovery.
3. Take a back up of your stuff.
4. Re-install your ROM. If you don't have a copy of your ROM saved on your phone, plug your phone into your computer and mount your storage. This should make your phone storage available to your PC. Copy your ROM over to your phone, re-install.
5. Reboot. Though my phone was stuck in a restart loop after this. I initially did a reflash with the latest version of Viper XL without wiping. I went back into recovery and did a new install with a wipe. Problem solved.
6. Once you're sure your phone is back up and running, reboot into recovery and do a restore of your data from the back up you made earlier.
7. Enjoy having a phone again.

BigJanko said:
1. Hold the power button + volume down until you get into the bootloader. I found that if I held these down, release when the screen went blank, then immediately pushed them down and held them, it got me into the bootloader.
Click to expand...
Click to collapse
So many people are confused about how to get into bootloader. The main reason is that vol down needs to be held and not at any point released, until you get into bootloader. But the power button actually has to be released. The easiest way to accomplish this is:
- If the screen is on at all, hold both the power button and vol down until the capacitive buttons flash several times and the screen turns off. Once the screen is off, release the power button but keep holding vol down until you are in bootloader.
- If the screen is still black (or phone was powered off to begin with) simply keep holding vol down, and press the power button for a few seconds, then release it. But again, always holding vol down until the bootloader comes up.
If the phone boots normally, or goes to the boot splash, its almost always because you pressed vol down too late, or let go of it too early. As long as the screen comes on, failure to get into bootloader is almost always due to this user error.
People will often say "Press power and vol down" for bootloader. But this isn't really a complete and accurate description. And likely the reason why a lot of folks get confused.
Aside from this failure to get into bootloader, the remainder of your issue would have been easily solved if you had just originally had a nandroid on your phone. Recovering would have been as easy as:
1) Bootloader
2) Boot recovery
3) Restore nandroid
4) Keep on trucking
I'm surprised how so many people lately seem to be the practice of flashing ROMs or other mods without first making a nandroid backup. This to me is just a fundamental step in the process, and good basic practice. Failure to do so either signifies lack of knowledge, or doing mods in a careless fashion. Either way, its not good.
If you don't want the nandroid taking up all the space on the SD, I can understand that. In that case, have one on your PC that can be easily moved to your phone's SD in case of an emergency.

hi i was using my htc one x with viper xl but now i reset my system extsd cache everything .now when my device is on it shows me viper xl image alone so please kindly help me with this

kknaveenkk24 said:
hi i was using my htc one x with viper xl but now i reset my system extsd cache everything .now when my device is on it shows me viper xl image alone so please kindly help me with this
Click to expand...
Click to collapse
I think you have erased system and data partition too if u have done this you must have to flash viper Rom again

[Q] [HELP] HTC One X Rooting Problem PLEASE HELP

Hello,
I would like to start off with saying I am new here and so far I love this site it has helped me a lot with rooting my phone. However, I have a problem:
Okay so I rooted the phone successfully and installed SuperSU and all that. After I did this the phone was rooted and running on jellybean just fine. Well the whole reason I wanted to root the phone in the first place was so I could install a custom ROM. So i followed this tutorial for the whole rooting process: http://forum.xda-developers.com/showthread.php?t=2069904
So after I rooted I downloaded the .zip file for the rom i wanted, which in this case was one of the Beanstalk roms for evita HTC One X.
After I moved the .zip file to the phone, I booted the phone into TWRP recovery. (I am using TWRP v2.7) and flashed the ROM. After I did this I extracted the boot.img file to my desktop. After I did this I opened up the toolkit and pressed Flash a Kernel, it said it did so successfully. I rebooted the phone and got stuck at the Beanstalk boot screen, and couldnt get it to fully boot up at all.
So I booted the phone back into recovery mode, made a backup, and wiped the phone clean so i could try to start over. Well when i wiped the phone i tried to back up the phone in TWRP, only to find that my backup file has disappeared.
Now my phone is ROMless and i can only boot the phone into recovery and bootloader mode.
This wouldn't be that much of a problem, if it weren't for my PC acting up. (I'm using Windows 7 Professional) My PC recognizes the device but the drivers never successfully install, the only place where i can find the device on my computer is in the Device Manager and it says Needs troubleshooting, when i try to troubleshoot it never troubleshoots correctly and i cant find the driver. So I can't access the files on the phone to put a different ROM on the phone, and i also tried running the RUU exe file for it and that did nothing. Is there any possible way to at least get this phone back to normal?? At this point I could care less about the root or custom ROM.
If anyone can help it would be greatly appreciated. I'm currently stuck without a phone until I can find a way to fix this
Thanks in advance for anyone able to help me.

First off, do you have the HTC One X (Endeavoru) or the HTC One XL / at&t One X (Evita)? I ask this because you linked to a guide for the Endeavoru but you have mentioned an Evita ROM, which means you're lurking in both device forums which is dangerous. What are your bootloader details?
Sent from my Evita

I have the AT&T HTC One X (Evita, US verison) and what do you mean by bootloader details? Sorry if i sound like a noob, i'm new to rooting and such.

Your bootloader details are the lines of text that your see in your bootloader screen. To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines.
Sent from my Evita

timmaaa said:
Your bootloader details are the lines of text that your see in your bootloader screen. To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
Yes i'm aware of what bootloader is (not trying to sound sarcastic or anything) but the first five lines are these:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PUT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:-1
its a little more than 5 lines but yeah. I heard theres a way to flash the device with a third party software called ODIN if the pc wont recognize the device normally? Do you know anything about that?

ViolentPoptart said:
Yes i'm aware of what bootloader is (not trying to sound sarcastic or anything) but the first five lines are these:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PUT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:-1
its a little more than 5 lines but yeah. I heard theres a way to flash the device with a third party software called ODIN if the pc wont recognize the device normally? Do you know anything about that?
Click to expand...
Click to collapse
Well, you did ask what I meant by bootloader details, so I answered. You absolutely can't use ODIN, that's Samsung software.
My advice is to get rid of whatever toolkit you're using and learn to do things manually, it's very easy, plus clearly toolkits are unreliable. You're gonna need to resolve your driver issue, probably by installing HTC Sync Manager, which will install drivers. Once you've gotten your drivers sorted out you can head to my How-To Guide For Beginners thread for detailed instructions on how to flash the boot.img manually.
Sent from my Evita

timmaaa said:
Well, you did ask what I meant by bootloader details, so I answered. You absolutely can't use ODIN, that's Samsung software.
My advice is to get rid of whatever toolkit you're using and learn to do things manually, it's very easy, plus clearly toolkits are unreliable. You're gonna need to resolve your driver issue, probably by installing HTC Sync Manager, which will install drivers. Once you've gotten your drivers sorted out you can head to my How-To Guide For Beginners thread for detailed instructions on how to flash the boot.img manually.
Sent from my Evita
Click to expand...
Click to collapse
yeah you just cleared up what you meant by details with the text lines
and ive tried uninstalling and reinstalling sync manager a few times now, it recognizes the device, but i cant access the files, the phone only shows up in Devices and Printers, and it shows up as Evita with an exclamation mark and says needs troubleshooting. when i try to troubleshoot it it doesn't work. however there are also other problems with my PC, the monitor is listed as a generic pnp monitor and the graphics card is listed as standard vga graphics adapter. i think thats my main problem, im going to try to wipe my pc and reinstall windows and see if that works.

ViolentPoptart said:
yeah you just cleared up what you meant by details with the text lines
and ive tried uninstalling and reinstalling sync manager a few times now, it recognizes the device, but i cant access the files, the phone only shows up in Devices and Printers, and it shows up as Evita with an exclamation mark and says needs troubleshooting. when i try to troubleshoot it it doesn't work. however there are also other problems with my PC, the monitor is listed as a generic pnp monitor and the graphics card is listed as standard vga graphics adapter. i think thats my main problem, im going to try to wipe my pc and reinstall windows and see if that works. Where can i find your how to guide for beginners?
Click to expand...
Click to collapse
Ok, yeah you probably need to sort out your PC first. My guide thread is in my signature.
Sent from my Evita

timmaaa said:
Ok, yeah you probably need to sort out your PC first. My guide thread is in my signature.
Sent from my Evita
Click to expand...
Click to collapse
my problem is now solved. thanks for your help

[Q] AT&T One X wont go to bootloader after RUU

Hey guys, I need a bit of help. I had CM11 installed on my one x with 4.4.2, i decided id like to update it to cm12. So i read the instructions. I was S-off and supercid already .so i went to ruu 3.18. Got success in cmd line, reboot into bootloader. saw it worked. went to update to 5.18 at&t firmware as per the cm 12 instructions, i got success. but when i hit reboot, the htc logo just appears, and then it shuts off. It will not go into fastboot, bootloader, or recovery.
Is the phone bricked? or is there a way to fix this. This isn't my main device so i'm not too worried about it, just want to get it working if possible.

Arkalos13 said:
Hey guys, I need a bit of help. I had CM11 installed on my one x with 4.4.2, i decided id like to update it to cm12. So i read the instructions. I was S-off and supercid already .so i went to ruu 3.18. Got success in cmd line, reboot into bootloader. saw it worked. went to update to 5.18 at&t firmware as per the cm 12 instructions, i got success. but when i hit reboot, the htc logo just appears, and then it shuts off. It will not go into fastboot, bootloader, or recovery.
Is the phone bricked? or is there a way to fix this. This isn't my main device so i'm not too worried about it, just want to get it working if possible.
Click to expand...
Click to collapse
Wrong forum mate go in the right forum

Arkalos13 said:
Hey guys, I need a bit of help. I had CM11 installed on my one x with 4.4.2, i decided id like to update it to cm12. So i read the instructions. I was S-off and supercid already .so i went to ruu 3.18. Got success in cmd line, reboot into bootloader. saw it worked. went to update to 5.18 at&t firmware as per the cm 12 instructions, i got success. but when i hit reboot, the htc logo just appears, and then it shuts off. It will not go into fastboot, bootloader, or recovery.
Is the phone bricked? or is there a way to fix this. This isn't my main device so i'm not too worried about it, just want to get it working if possible.
Click to expand...
Click to collapse
It isn't bricked, if it powers on at all it isn't a brick. Not being able to get to the bootloader is almost always a case of user error. To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines.
Transmitted via Bacon

You are correct, thanks for the help. I guess I wasn't doing the right technique to get into boot loader. (Volume down+power button) I was doing vol up.
Thanks again, all is well and running cm12 now.
Sent from my LG-D850 using XDA Free mobile app

No probs, glad to help.
Transmitted via Bacon