Related
i rooted and bootload unlocked on 2.20 flashed boot.img via fastboot and then flashed cm10. everything work fine. then i decided to flash codename. first thing i did was flash codename boot.img before i did anything and thats where i messed up. cant get into fastboot with power and volume up+down it just goes to htc screen with red warning sign. and when i try to boot up phone it gets to home screen and keeps forclosing not allowing me to do anything....
it sounds like you lost recovery, keep trying to get into bootloader then flash twrp again.
XsMagical said:
it sounds like you lost recovery, keep trying to get into bootloader then flash twrp again.
Click to expand...
Click to collapse
wont let me get into bootloader. the power and volumes just keeps booting the phone up and stuck on infinite forclosing
happend to me a few minutes ago it was nasty try to shut down the phone and then
before it loops quickly power+volume down and after the one xl buttons stop flashing hold the
volume down and keep holding it until bootloader shows up
press and hold power button until capacitive buttons flash 6 times. then hold volume down. phone will boot into bootloader. carry on from there.
The problem is you weren't holding the right keys to get into bootloader.... and everything is fc'ing because your running codenames kernel on cm10.
Sent from my One X using xda premium
XsMagical said:
it sounds like you lost recovery, keep trying to get into bootloader then flash twrp again.
Click to expand...
Click to collapse
speednir123 said:
happend to me a few minutes ago it was nasty try to shut down the phone and then
before it loops quickly power+volume down and after the one xl buttons stop flashing hold the
volume down and keep holding it until bootloader shows up
Click to expand...
Click to collapse
thanks. but wow im an idiot. im so use to samsung phones i was holding volume up and down
This always does the trick for me Turn on, hold power 10-15 seconds, until screen goes black, let off, press n hold volume down, press power just 2-3 seconds, let off power button but continue holding vol. Down
ptesmoke said:
press and hold power button until capacitive buttons flash 6 times. then hold volume down. phone will boot into bootloader. carry on from there.
The problem is you weren't holding the right keys to get into bootloader.... and everything is fc'ing because your running codenames kernel on cm10.
Sent from my One X using xda premium
Click to expand...
Click to collapse
so i would have to wipe, flash rom then flash boot.img
as its booting if u turned on usb debugging computer should detect it while its booting. just run "adb reboot recovery"
Hello all,
I rooted my HTC One XL a couple weeks back, installed CM10 (all was working fine), and in the process of installing the latest CM10 nightly, something went wrong. Flashed boot.img, then rom, then gapps. Wiped cache and dalvic cache, asked TWRP to restart system. This is where it's stuck now. It won't go past the htc logo, and I can't get into the bootloader by holding down power+vol down.
What did I do wrong? Is this fixable? Any help is greatly appreciated!
H8rift is working on a solution right now. If you can flash back to a backup? I would do so.
Sent from my One X using xda premium
---------- Post added at 10:52 PM ---------- Previous post was at 10:51 PM ----------
You can't get into recovery?
Sent from my One X using xda premium
vowelsounds said:
Hello all,
I rooted my HTC One XL a couple weeks back, installed CM10 (all was working fine), and in the process of installing the latest CM10 nightly, something went wrong. Flashed boot.img, then rom, then gapps. Wiped cache and dalvic cache, asked TWRP to restart system. This is where it's stuck now. It won't go past the htc logo, and I can't get into the bootloader by holding down power+vol down.
What did I do wrong? Is this fixable? Any help is greatly appreciated!
Click to expand...
Click to collapse
First off, can you get into TWRP, and do you have a backups of the time before you flashed the rom. When you hold power+vol down are you holding power until the home back and kill app buttons flash 6 times then release and hold vol down around 7 seconds till you see the screen with android skateboarders(Bootloader)
Second, I think their is a kit (Hasoons) Which you can try to boot you into bootloader or twrp recovery. But if your phone powers on, then i think your device is not a paperweight yet so dont worry to much as i think it can be fixed.
vowelsounds said:
Hello all,
I rooted my HTC One XL a couple weeks back, installed CM10 (all was working fine), and in the process of installing the latest CM10 nightly, something went wrong. Flashed boot.img, then rom, then gapps. Wiped cache and dalvic cache, asked TWRP to restart system. This is where it's stuck now. It won't go past the htc logo, and I can't get into the bootloader by holding down power+vol down.
What did I do wrong? Is this fixable? Any help is greatly appreciated!
Click to expand...
Click to collapse
It is fixable.
I did the same thing with my phone. Now I am successfully running ViperXL 2.1.2
Are you able to "fastboot oem lock" from the fastboot cmd prompt?
WhatTheAndroid? said:
First off, can you get into TWRP, and do you have a backups of the time before you flashed the rom. When you hold power+vol down are you holding power until the home back and kill app buttons flash 6 times then release and hold vol down around 7 seconds till you see the screen with android skateboarders(Bootloader)
Second, I think their is a kit (Hasoons) Which you can try to boot you into bootloader or twrp recovery. But if your phone powers on, then i think your device is not a paperweight yet so dont worry to much as i think it can be fixed.
Click to expand...
Click to collapse
I can't get into TWRP, and I have backups on the device. I am sorry for being a dummy, but you're saying the manual way to enter the boot loader is to hold power+voldown for 6 flashes, then release the power button but hold the voldown for 7 more seconds? I've just been holding down both for the full 15 flashes. I am going to look up Hasoons rn.
THANKS!!
vowelsounds said:
I can't get into TWRP, and I have backups on the device. I am sorry for being a dummy, but you're saying the manual way to enter the boot loader is to hold power+voldown for 6 flashes, then release the power button but hold the voldown for 7 more seconds? I've just been holding down both for the full 15 flashes. I am going to look up Hasoons rn.
THANKS!!
Click to expand...
Click to collapse
You are supposed to hold Power and Volume Down until the screen shuts off, then let go of power and continue holding volume down
vowelsounds said:
I can't get into TWRP, and I have backups on the device. I am sorry for being a dummy, but you're saying the manual way to enter the boot loader is to hold power+voldown for 6 flashes, then release the power button but hold the voldown for 7 more seconds? I've just been holding down both for the full 15 flashes. I am going to look up Hasoons rn.
THANKS!!
Click to expand...
Click to collapse
So your saying you can't get into bootloader but, you got into TWRP?
The correct way to get into bootloader is hold power+vol down until screen goes off, then release power button.
If that doesn't work you can try to open bootloader through the fastboot cmd prompt.(if you ahve Win7 just open the file where fastboot is, hold shift+right click and you can open the prompt from there)
Myrder said:
It is fixable.
I did the same thing with my phone. Now I am successfully running ViperXL 2.1.2
Are you able to "fastboot oem lock" from the fastboot cmd prompt?
Click to expand...
Click to collapse
Just tried this, cmd prompt reads "waiting for device". I am glad to know someone else got out of this :/
absolutelygrim said:
You are supposed to hold Power and Volume Down until the screen shuts off, then let go of power and continue holding volume down
Click to expand...
Click to collapse
What he said, but after your phone powers off, when i held it for around 7 more seconds, it booted into bootloader when i did it .But try both methods.I was stuck in a bootloop as well, you will be fine. I forgot commands for fastboot, but if anyone wants to tell them to him he could prob get into fastboot by command prompt mabye?
vowelsounds said:
Just tried this, cmd prompt reads "waiting for device". I am glad to know someone else got out of this :/
Click to expand...
Click to collapse
type "fastboot devices"
your serial number should be on the screen if fastboot recognizes your phone. but I was always able to get into bootloader through commands on the phone.
Also, I can't thank Absolutelygrim and a few others whom I can't think of their names for helping me out of that situation.
ANYTHING Absolutelygrim says, I would listen and take note.
Myrder said:
So your saying you can't get into bootloader but, you got into TWRP?
The correct way to get into bootloader is hold power+vol down for 6 flashes, then release power button.
If that doesn't work you can try to open bootloader through the fastboot cmd prompt.(if you ahve Win7 just open the file where fastboot is, hold shift+right click and you can open the prompt from there)
Click to expand...
Click to collapse
No I couldn't get into either, but I just did the power+voldown until screen off then hold vol down thing, and I got into bootloader and from there to recovery. I am going to flash a backup &c &c...
You people are so amazing!! Saved my life! Thank you, Thank you, Thank you, Thank you!
vowelsounds said:
No I couldn't get into either, but I just did the power+voldown until screen off then hold vol down thing, and I got into bootloader and from there to recovery. I am going to flash a backup &c &c...
You people are so amazing!! Saved my life! Thank you, Thank you, Thank you, Thank you!
Click to expand...
Click to collapse
Glad your device is back, good job. Hope i helped.
vowelsounds said:
No I couldn't get into either, but I just did the power+voldown until screen off then hold vol down thing, and I got into bootloader and from there to recovery. I am going to flash a backup &c &c...
You people are so amazing!! Saved my life! Thank you, Thank you, Thank you, Thank you!
Click to expand...
Click to collapse
Is there a way to close a thread? I've never done this before :/
Thanks to all of you again!
vowelsounds said:
No I couldn't get into either, but I just did the power+voldown until screen off then hold vol down thing, and I got into bootloader and from there to recovery. I am going to flash a backup &c &c...
You people are so amazing!! Saved my life! Thank you, Thank you, Thank you, Thank you!
Click to expand...
Click to collapse
It's always best to Nandroid before you flash a ROM.
I didn't and I almost made my phone into a very expensive paperweight. Thank god for RUUs.
I also tried to flash a ROM that was for the international version and not the XL which is our phone.
Mods will eventually Close it, just ingnore the thread and it will be closed soon.
If you want to, I know posting a thread in here can amount to a long wait time, just shoot me a PM and I'll give you my email. I get that directly to my phone so I'll be able to reply a lot quicker.
I have the same problem as this guy, but when I hol the volume down button, it has no effect... I hold vol down and power, lights flash 15 times, I keep holding volume down while phone reboots, but no matter how long I hold it down, it just stays at the HTC legal screen.
Was running CM 10.0, and updated to 10.1 (9-3-2012 nightly) with 3-03-2013 GAPPS, via TWRP. Made a backup before flash, Installed both the zips succefully, pressed reboot, and now it doesn't get past the legal screen, and no button pressing is getting me back to TWRP =(
I replaced the screen once, and the volume buttons behaved differently after I re-assembled. Both the buttons work, but they act differently. Pressing vol down or vol up both bring up the volume dialog, but instead of increasing or decreasing the amount, it swtiches between mute and non mute. So I'm thinking the button is not actually doing a 'volume down' action. Any thoughts?
AND, how do you actually turn this device off? It keeps turning itself back on after the 15 flashes.
Thanks for any help.
new developer need 10 posts in general discussion sry
Ok.. I'm about to lose hope, please any creative ideas will be much appreciated..
I think i did a big mistake trying to update to the latest nightly release of CM 10.2 using the auto-update feature of cm 10.1...
The end result is a bootloop, gets up to the CM rotating animation for a few seconds and reboots.
on top of that:
unable to get into bootloader using pwr+vol up nor vol down
unable to access device using adb nor fastboot - shows no device connected
the PC does not recognize the device though there are drivers installed, the charging LED lights up but no PC activity
all of the solutions i've seen assume either the recover/bootloader is available or the phone is accessed via fastboot/adb.
in this case neither are correct....
for some time i wanted to upgrade to htc one but not yet....
please help
Press and hold power until the phone shuts off.
Then let go of power and press and hold volume down until bootloader comes up.
Sent from my One X using xda app-developers app
exad said:
Press and hold power until the phone shuts off.
Then let go of power and press and hold volume down until bootloader comes up.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
tried it again several time, but as I said it doesn't work.
I get a black screen (not the CM animation) and than reboot all over again.
You could try letting it drain completely. Then charge a bit and try again.
Is your phone plugged in while your trying? My phone will not enter bootloader while its plugged in.
Sent from my One X using xda app-developers app
spitfireatz said:
tried it again several time, but as I said it doesn't work.
I get a black screen (not the CM animation) and than reboot all over again.
Click to expand...
Click to collapse
You are mostly likely not performing the button combo correctly. If there were no bootloader (hboot), the screen would not be coming on at all. Not getting into bootloader is almost always a case of not doing the button combo correctly. The one possible exception, is if your volume rocker has failed (and simply not registering the vol down being pressed).
Make sure you hold vol down, and do not let go until the while bootloader screen comes up.
Recovery is a different story, as you can indeed not have recovery installed, and the phone will still function. But hboot and recovery are 2 different things.
redpoint73 said:
You are mostly likely not performing the button combo correctly. If there were no bootloader (hboot), the screen would not be coming on at all. Not getting into bootloader is almost always a case of not doing the button combo correctly. The one possible exception, is if your volume rocker has failed (and simply not registering the vol down being pressed).
Make sure you hold vol down, and do not let go until the while bootloader screen comes up.
Recovery is a different story, as you can indeed not have recovery installed, and the phone will still function. But hboot and recovery are 2 different things.
Click to expand...
Click to collapse
I wish it was the case,
when i try to go into hboot the device instead of going into another boot until animation cycle, goes into black screen boot cycle. which means most likely that the action (PWR+Vol) does have an effect otherwise it would have continued to go into same boot cycle through the CM animation..
besides there is a recovery installed, or at least was...
is there anyway to re-install the hboot part without the hboot/fastboot availability?
spitfireatz said:
is there anyway to re-install the hboot part without the hboot/fastboot availability?
Click to expand...
Click to collapse
If you are s-off, try running the RUU.
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.
Hello, just to start I have read through probably 100 post regarding similar issues but none are working. I have the ATT Htc one x EVITA 3.18 version. I did the super CID unlocked my bootloader through htc dev, flashed twrp recovery, and got a custom rom, gapps etc.. in twrp I wiped all data,system,cache, factory reset. Then flashed my rom and gapps (being kinda new to HTC devices I didn't flash the boot.img from the rom) now my phone after restarting just continues a bootloop (HTC Quietly Brilliant) screen, then powers off repeating this over and over.. I tried holding the volume down with the power button it just loops again, the I tried some other suggestions like holding power and vol down until the flashes stop and releasing power while continuing to hold volume down, again loops, then tried using volume up as well...none of these are working I don't understand what happened and why I can't get into any of these? I did not run any RUU. I tried using adb but of course i cant get into fastboot or anything so the phone is not recognized. If anyone could please help I really do appreciate it. I know this has been all over the threads but I read for the past 3 hours and could not get anything to work.. Thanks in advanced for any help it is much appreciated. :crying:
First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita
timmaaa said:
First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply timmaaa... I usually would not try the other button presses just someone else had said that worked for them, but thanks for the advice. I did try what you said and just holding the volume down button, let it bootloop, and keep holding and it just continues to bootloop :/ it stay off for about 20 seconds the same then bootloops, with the htc screen for about 5 seconds the rinse and repeats D**n this thing is annoying. Any other Ideas? Thanks again man appreciate it.
if you are SOFF u can go for RUU?
Sonone said:
if you are SOFF u can go for RUU?
Click to expand...
Click to collapse
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:
sensei_777 said:
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:
Click to expand...
Click to collapse
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!
Sonone said:
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!
Click to expand...
Click to collapse
I had to change the CID to unlock the bootloader on htc dev, its like 11111 so that is super CID right?
Yea I've tried everything to get to adb since I am familiar with adb but its a no go none of the tool kits or even manual cmd is recognizing the device.. I had a one x just like this before and never had the problem getting into bootloader so I don't really get what is blocking it. Only thing I had done was flash twrp recovery, wiped data/factory reset, system and cache, then flashed the rom as one usually would and gapps, just I had forgot about these phones needing you to flash the boot.img. that is all I did to it. Kinda sucks I just got this thing yesterday from a friend too.
Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita
timmaaa said:
Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita
Click to expand...
Click to collapse
Thanks bud, well I can't get it to catch even using super finger speed cmd'ing lol.. oh well.. I'm not gonna try anything else other than the usual ways to get into bootloader until someone else has some idea what might be blocking it from entering. Is there anyway to turn it off? its just restarting over and over with the bootloop. Or does one just let it go dead? I suppose worse case senario sending it for Jtag would fix it right? thanks again to the both of you.
I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita
timmaaa said:
I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita
Click to expand...
Click to collapse
Yes well on my laptop its the up key that's what I was doing was spamming, you can hear the connected device sound on then off, but it just doesn't see it. I will let you all know once its working again and what I did or had to do to get it back so that it may possibly help others that run into the same issue. If not I suppose I'll try to get it Jtagged, too nice of a phone to use as a paperweight really
Yeah sorry, I knew it was one of the arrow keys, kinda took a stab in the dark at that one :sly:
Sent from my Evita
Hold down the power button until the phone turns off. You'll see the buttons flash. This simulates a battery pull. Then wait a few secs then hold vol down and press power button for 2 secs while still holding vol down. Wait for bootloader
Sent from my VENOMized HoxL
You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita
timmaaa said:
You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita
Click to expand...
Click to collapse
Nothing is working guys :/ full Battery drain and everything it just keeps looping no matter what I do it will not go in bootloader :crying: thanks for trying to help
If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developers app
exad said:
If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developer app
Click to expand...
Click to collapse
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.
sensei_777 said:
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.
Click to expand...
Click to collapse
Just flashed the boot.img good to go now thanks for the advice everyone