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
Related
Hi, i've got a big problem...
After a system crash i pull-out the battery and then pull-in to reset the device.
after that now when i turn on the telephone it remain stucked on the white screen with htc logo. tryed to factory reset but remain stucked after i press on it.
my htc has original rom. no modification. what can i do? i don't really want to spend 3 weeksfor htc assistance.
Thanks
Semi-bricked phone E:Can't mount /cache/recovery/command
[solved]BRICKed: inside eMMC's dead, with E:Can't open /cache/recovery/log
For everyone who Bricked their phone - Help prevent the others
[Guide] How to brick your Desire S
Have i to flash a stock rom? how can i do without remove warranty? in the case it does'nt work i have to take it to htc center
You probobly fried your EMMC chip when you removed your battery.
it would be best to return it in for repair.
I think you may have same problem with me before. No choice but to bring it to repair.
Sent from my HTC Desire S using XDA App
It was s-off before? Can you boot 2 recovery?
It's unlikely your chip is fried. This happened to my phone. You need to get into recovery - restart holding volume down button - and reflash a ROM, any one should do. The phone should reboot from there.
Edit: thus assumes you have a ROM stored on your phone, and you have Clockwork recovery or similar. If not, you can use adb to push a ROM to your card and reflash that. Adb comes with Android Developer Kit. Search!
Peace.
Sent from my HTC Desire S
chris5s said:
It's unlikely your chip is fried. This happened to my phone. You need to get into recovery - restart holding volume down button - and reflash a ROM, any one should do. The phone should reboot from there.
Edit: thus assumes you have a ROM stored on your phone, and you have Clockwork recovery or similar. If not, you can use adb to push a ROM to your card and reflash that. Adb comes with Android Developer Kit. Search!
Peace.
Sent from my HTC Desire S
Click to expand...
Click to collapse
Same problem as topic poster, i,ve been messing a lot with custom roms on win 6.5 phones, but I havn´t done anything fancy on my Desire S , as to rooting or custom roms. (work phone!) Now I´m just curious as how I get a recovery going, when the PC doesent recognice the device when USB connected.
The eng-off file (mine is ON) with the .bat file cant connect to phone, and maybe im better off sending it to repair, but my pride wants me to solve it myself.
-Damn phone just went AWOL last night after an marked Angry Birds update, rebooted it a couple of times, because of a lot of process errors, and then all dead. (white HTC screen on -until morning)
Have the latest FOTA (DK, Nordic)
ROM: SAGA PVT SHIP S-ON RL
Hboot: 0,98.0002
Radio: 3805.06.02.03_M
Are there any ninja tricks or is it just a "bite down", send in?
/Psudo
psudo said:
Same problem as topic poster ....
Are there any ninja tricks or is it just a "bite down", send in?
/Psudo
Click to expand...
Click to collapse
Maybe best sending it in if that's a viable option.
You say it's not rooted? With stock ROM? If there is a ROM on the sdcard that you can boot then try that - power + volume up + volume down will reboot the phone, try pressing volume down as it reboots to get into recovery.
If you can't (by pressing volume down) then power off and restart (holding volume down). I had to do a battery pull to power off - if you do this while the phone is off as it reboots, and leave it out for 30 secs you should avoid any danger of bricking the phone (which has happened with some people when removing battery while phone is in this state).
Good luck!
Peace
chris5s said:
Maybe best sending it in if that's a viable option.
You say it's not rooted? With stock ROM? If there is a ROM on the sdcard that you can boot then try that - power + volume up + volume down will reboot the phone, try pressing volume down as it reboots to get into recovery.
If you can't (by pressing volume down) then power off and restart (holding volume down). I had to do a battery pull to power off - if you do this while the phone is off as it reboots, and leave it out for 30 secs you should avoid any danger of bricking the phone (which has happened with some people when removing battery while phone is in this state).
Good luck!
Peace
Click to expand...
Click to collapse
"ROM on SDcard": what format would that be in? RUU.exe or?
I can get into recovery menu (HBOOT) but chosing recovery option results in "a green recycle icon with an arrow on black background" screen, a few seconds then it virbrates 6-8 times, and then fades to black, so to speak!
Factory reset option: Locks the HBOOT screen and nothing but a battery pull, will change that.
I MAY have pulled the battery and not left it out for the 30 sec bricking danger senario, that I wasn´t aware of, until resently.
So the diag. is that is probably bricked!
Thanks for the reply
/Psudo
Rom on sdcard would have to be *.zip to be flashable. If you're unrooted + stock then you won't have Clockwork recovery or similar.
Tough that factory reset doesn't give any joy. These devices.....
Looking like masonry then, unless someone else can help.
Peace
Sent from my HTC Desire S using xda premium
surprisingly i got the same issue yesterday after i installed proxuser's official htc rom. Everything started fine went through setup so i assume it's not because of the rom because i don't think the phone would've started up in the first place. Anyway i am about to try and install some different roms and have also copied a backup over from my other desire s.
Will let you guys know if it worked.
Noob here.
Sorry for the cross post, posted in the worng section (Sensation Android Dev)
Was working through the S-Off, rooting procedure http://forum.xda-developers.com/show...php?p=16125286
Got as far as configuring the s-off mod, rebooted my device to install recovery v5.0.0.8, copied the file to the SD card, power down to hboot (vol -, power on) but it will not go to h-boot, just restarts everytime. Pulled battery, tried rebooting 15 different times, still will not go to h-boot.
Any ideas?
tlgerdes said:
Noob here.
Sorry for the cross post, posted in the worng section (Sensation Android Dev)
Was working through the S-Off, rooting procedure http://forum.xda-developers.com/show...php?p=16125286
Got as far as configuring the s-off mod, rebooted my device to install recovery v5.0.0.8, copied the file to the SD card, power down to hboot (vol -, power on) but it will not go to h-boot, just restarts everytime. Pulled battery, tried rebooting 15 different times, still will not go to h-boot.
Any ideas?
Click to expand...
Click to collapse
Hi,
On your phone,go to settings/power and have you unticked fastboot?
Restart the phone and when the screen turns black, hold the vol down button
Or remove the battery, insert and hold the vol down button
Then power on while holding that
Sent from my HTC Sensation using XDA App
Reflash with an official rom: Tested
Reflash back with an official rom like this
RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198179_signed_2
love_mido said:
Reflash back with an official rom like this
RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198179_signed_2
Click to expand...
Click to collapse
And how's that supposed to help? His problem is most probably fastboot..
Sent from my HTC Sensation using XDA App
If the phone boots it will go into hboot. What you need to do is pull the battery out, wait 10 seconds. Put battery back in and first PRESS AND HOLD vol down button. Then keep the vol down pressed and at the same time press and hold power button.
You need to keep hold of the buttons for about 10 seconds
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Power button on my HTC One S stopped working to I decided to fix it. I discharged the phone completely and opened the phone. I got to the switch and it fall apart from the motherboard so I soldered it in place. I dont know what could cause this, but now The phone doesnt want to boot. Its stuck on HTC logo with red warnings. Phone was running great on TrickDroid 9.1.0 before the discharge/opening. However Im able to enter bootloader. I can use fastboot usb ( I triend to flash different boot.img and recovery but it doesnt help. fastboot show flask OKAY but still, phone doesnt want to boot. When I choose recovery from hboot It will reboot into htc logo without warning, the status bar in the corner will pass 2 times and after 30sec it will just reboot into warning logo.
I have HBOOT 1.09.
Does anyone know what happend?
Discharging the phone is bad.This is a common issue, especially if youre using CWM.
If you are using CWM - change to TWRP.
Goatshocker said:
Discharging the phone is bad.This is a common issue, especially if youre using CWM.
If you are using CWM - change to TWRP.
Click to expand...
Click to collapse
Great advice cuz in my opinion 'TWRP' is way better interface but can you give him more detail and I'm sure in this case he would not mind being treated as a noob, I would but I'm not as good as you and Darknites lol :good:
I downloaded t-mobiles ruu and installed it in fastboot. everthing installed fine, updated radio and hboot. But still its looping on htc logo. hboot is 1.14 and is relocked. Any ideas?
krzysiek033 said:
I downloaded t-mobiles ruu and installed it in fastboot. everthing installed fine, updated radio and hboot. But still its looping on htc logo. hboot is 1.14 and is relocked. Any ideas?
Click to expand...
Click to collapse
Re check the power button, and are the touch keys blinking at anytime when you turn on the device?
ultraprimeomega said:
Re check the power button, and are the touch keys blinking at anytime when you turn on the device?
Click to expand...
Click to collapse
They blinking only if I hold the power button for few sec.
krzysiek033 said:
They blinking only if I hold the power button for few sec.
Click to expand...
Click to collapse
Its not good that its still looping after using a RUU but try factory reset or you can try just unlocking the bootloader and trying a custom rom.
Hi there, I'm new at this forum and new at android so please be patient with me!! This is my problem and I have a few questions too.
I wanted to perform my htc one x AT&T interface so I rooted it succesfully, then I installed recovery PWRP v2.6.0.0 but i dont know what went wrong and now i cannot start my phone, it is stuck on htc boot screen. I'm really afraid of what can happen now. I've read that if you install the wrong ROM i can brick it. I want to know how to fix this, and if i can flash any any any ROM at this forum. I know that htc is not upgrading this phone to android 4.2, just to 4.0.4, which is the one i have, but can i upgrade to 4.2 sense 5 using a custom ROM? please if you need any info ask for it and thank you!! Evermore, I wiped system, sdcard, cahce, etc...
We will need some further information from you. You said your phone hangs at the HTC screen when you try to boot it, does it stay on that screen constantly, or does it perform multiple boot loops? Here's a couple of options:
Scenario A (phone stays in htc screen constantly): hold volume down + power together, keep holding them and your button lights will start flashing then the screen will turn off. After a couple of seconds let go of the power button but continue holding volume down until you reach the bootloader (a white screen with text).
Scenario B (phone performs multiple boot loops): hold the volume button while it's booting, the next time it reboots it will enter bootloader as long as you keep holding volume down.
Now that you're in the bootloader, please post the first five lines of text you see. Also please tell us which root/unlocking method you used, and whether you've flashed any custom ROMs or anything at all before your phone stopped booting.
Sent from my Evita
timmaaa said:
We will need some further information from you. You said your phone hangs at the HTC screen when you try to boot it, does it stay on that screen constantly, or does it perform multiple boot loops? Here's a couple of options:
Scenario A (phone stays in htc screen constantly): hold volume down + power together, keep holding them and your button lights will start flashing then the screen will turn off. After a couple of seconds let go of the power button but continue holding volume down until you reach the bootloader (a white screen with text).
Scenario B (phone performs multiple boot loops): hold the volume button while it's booting, the next time it reboots it will enter bootloader as long as you keep holding volume down.
Now that you're in the bootloader, please post the first five lines of text you see. Also please tell us which root/unlocking method you used, and whether you've flashed any custom ROMs or anything at all before your phone stopped booting.
Sent from my Evita
Click to expand...
Click to collapse
Thank you for your reply. I fixed this problem installing DM9 ROM and now works great. Here are the first five lines you asked:
It is unlocked
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
I used X-Factor root and at a first time it used to get stucked on htc white scrren logo, then i performed a cache restore through adb and at that time it started rebooting over and over again.
If you can help me now with the following will be great: I want to know if i can upgrade my OS to 4.2 JB with Sense 5 having superCID and s-on, or if there's a ROM out there that can simulate Sense 5 for 4.0.4. If it exist, could you tell me which will work fine? thank you very much
You can definitely run the Android 4.2.2 / Sense 5 ROMs with your current setup, no problems. You will need to flash the Beastmode kernel as well as the ROM to fix signal drop issues though. All of this can be found in our Android Development section.
Sent from my Evita
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