Database Info

[Q] Black screen on Start Up and Vibrates for about 2 minutes

hi,
Ive recently rooted my phone with no problems using the ace hack kit. i tried flashing the newest andriod revolution hd rom and was having problems with the superuser app force closing and the phone wasnt giving me root privledges. i decided to try and reroot the phone using the ace hack kit. (i realize this was my mistake). it stopped in the middle of the process. so i had to pull the battery. when i tried turning the phone back on the screen was black for about 6 or 7 mins. no vibrations or leds to indicate the phone was on. then the htc white screen comes on and the phone vibrates for 2 or 3 minutes straight and proceeds to come on. Ive tried to flash other roms using cwm recovery and itll load what ever rom i choose but i cant get into the hboot or anything and it does the the black screen everytime along with the vibration. is there anyway to fix this? ive tried over and over to boot into recovery through usb but it doesnt work.
so ive done a little research, could this be a eMMC problem? if so is it fixable... And if not would replacing the hboot help?

You've got a bad or corrupt hboot. The wrong hboot (ENG hboot included in a short-lived version of the hack kit on the newest run of Inspires) or a corrupt hboot from an interrupted hack kit run.

Thanks for the help. I tried replacing the eng hboot with the link provided on freenode and it work.

After a failed attempt at running the ace hack kit (could only get into hboot), and an ever worse failed attempt at restoring to a stock rom (my stupid mistake), I am seeing the same signature as jbryancs.
Would you share the link and instructions for replacing the hboot? Any assistance is much appreciated.

wleven said:
After a failed attempt at running the ace hack kit (could only get into hboot), and an ever worse failed attempt at restoring to a stock rom (my stupid mistake), I am seeing the same signature as jbryancs.
Would you share the link and instructions for replacing the hboot? Any assistance is much appreciated.
Click to expand...
Click to collapse
really? so jumping into the IRC channel is not your best move as instructed to the OP?

I was hoping not to disturb the IRC, but I will jump in tomorrow. Just for background, here's a rough list of what I've done and what I'm seeing now.
Setup: Linux Mint 11 (Ubuntu Derivative) Clean Install for ACE Hack Kit, WinXP for the rest.
1. Ran ACE Hack Kit first time -> stalled early in process
2. Rebooted phone and everything appeared normal
3. Rac ACE Hack Kit second time -> completed process, but noticed some errors/warnings along the way
4. Rebooted phone and it would be stuck at the white HTC logo screen
5. Rebooted to hboot, but none of the options there would restore the phone.
6. Downloaded original ACE firmware and copied ZIP to SD card. It recognized this and performed install, in all appearances successfully until the reboot.
7. On reboot, the phone appeared completely dead. Later discovered that it would spring to life after ~7mins, vibrate 2-3 min, and then boot into Froyo
Phase II
1. Downloaded gingerbread RUU from HTC and ran it. Gets stuck on "Waiting for bootloader"
2. Thought perhaps hboot was corrupted, so ran instructions here "wiki.cyanogenmod.com/wiki/HTC_Ace:_Rooting_%26_CyanogenMod" to install hboot-eng and clockworkmod
3. This did not fix the booting (still wait 7mins, vibrate 2-3), but I do have root now, as verified through su root on the phone's terminal console.
4. Tried the RUU again, stuck on "Waiting for bootloader"
5. Noticed that if I had the phone USB connected to the PC when power cycling, it would come to a black HTC screen after about 7mins. In this mode, the phone seems to connect in Android bootloader interface.
6. Tried the RUU again, and this time it makes it past "Waiting for bootloader", but hangs (no error message) on "Sending". I've left it for nearly an hour with no change -- just keeps showing the black HTC screen.
I still can't get the phone into HBOOT (using the volume down + power method).

Hello,
Could someone tell me if there's an enclosure or a solution to this problem?
I've searched a few forums, and it appear to me that the conclusion is the old (ENG) HBOOT is incompatible with newer hardware.
Thanks.

hchao said:
Hello,
Could someone tell me if there's an enclosure or a solution to this problem?
I've searched a few forums, and it appear to me that the conclusion is the old (ENG) HBOOT is incompatible with newer hardware.
Thanks.
Click to expand...
Click to collapse
You will have to flash the original RUU again and then try to root the cell with the Hack Kit. You can find the original RUU in the general section or go to the htc site and just run the .exe update from fastboot. Let your cell reboot (it will take about 30 minutes) and then flash it.

jbryancs said:
hi,
Ive recently rooted my phone with no problems using the ace hack kit. i tried flashing the newest andriod revolution hd rom and was having problems with the superuser app force closing and the phone wasnt giving me root privledges. i decided to try and reroot the phone using the ace hack kit. (i realize this was my mistake). it stopped in the middle of the process. so i had to pull the battery. when i tried turning the phone back on the screen was black for about 6 or 7 mins. no vibrations or leds to indicate the phone was on. then the htc white screen comes on and the phone vibrates for 2 or 3 minutes straight and proceeds to come on. Ive tried to flash other roms using cwm recovery and itll load what ever rom i choose but i cant get into the hboot or anything and it does the the black screen everytime along with the vibration. is there anyway to fix this? ive tried over and over to boot into recovery through usb but it doesnt work.
so ive done a little research, could this be a eMMC problem? if so is it fixable... And if not would replacing the hboot help?
Click to expand...
Click to collapse
I am having this same problem I have searched and searched and this post was the only one that had the same issue could someone please help me out on this and post the fix. Thanks

[Q] Phone won't boot into recovery, please help

Hi. This is the first time I've tried to install custom rom's on my phone so bear with me. I followed a post (since I can't post links yet just google: CyanogenMod 9 (CM9) for HTC One X is Here. It's the first link) detailing how to install CM9 on the OneX. Everything worked up until step 16 where you have to boot into recovery mode. When I select recovery mode from the bootloader, the phone just tries to restart and gets stuck at the HTC loading screen with a message underneath saying that this ROM is not official etc.
Is there an easy way to try and fix this and make it work properly? I've tried erasing the fastboot cache and that didn't make a difference. At this point I don't really care if I have to erase everything and just go back to what I had before. The phone doesn't show up as a drive on the PC when I plug it in.
Any help would be great!
SOLUTION: Ok this is what I did to get it working again. My phone is on Rogers so I had to download this RUU and then follow these steps to flash the RUU onto the phone. Pretty simple actually.

Well, I can tell you that the ROM you were trying to flash was not for the S4 variant of the HTC One X, the ROM you saw was for the international Tegra 3 chip which is VERY different. I would attempt to flash an RUU from the At&T HOX thread if that is possible. Sorry if I can't be of any more help, that's all I've got.

I just had this exact same problem on mine. Well I didn't try to install a full rom, but accidently tried to apply the mod where you remove the menu bar and remap the keys that was for the HTC One X (Internation/Tegra3) to my HTC One X (AT&T) and what happened was it would freeze at the HTC One Beats Audio screen and not do anything. Tried going to Recovery as well and nothing. So I thought. What I had to do was unplug my phone from USB, hold down power for about 7 seconds until screen goes black, immediately after screen goes black, release power button and start to hold down volume down button, this should get you to the Recovery menu. From here what you will need to do is go into FlashBoot, and then from ur PC (or mac... hopefully PC though) you need to relock your BootLoader, and get stock recovery (if you changed it). After this reboot and then go back into Recovery, FastBoot, and connect to PC. Now download the AT&T RUU (i used the newest, 1.85) and run through those steps. After this is finished phone should boot fine and your expensive device is saved.
Oh by the way, I'm an evolving Noob. Just started to do anything ...interesting... with my phone today, crap went down, and using these steps I was able to fix it, so if I am off on some of my steps or unclear, just comment please and I'll try and correct myself or giver farther details on what I did.
-Good Luck

Thanks for the replies but I think my situation is further complicated by the fact that my phone is a Rogers phone. I know the RUU is 1.73.631.1 but I don't know if a stock recovery is available for Rogers yet. It sounds like all I have to do is find the correct RUU and flash it to the phone.
TrueLandon, you said after you held the power button down for 7 seconds you could put the phone into recovery mode. Would that be the same thing as the bootloader menu (where you can select fastboot, factory reset etc)?

achoj said:
Thanks for the replies but I think my situation is further complicated by the fact that my phone is a Rogers phone. I know the RUU is 1.73.631.1 but I don't know if a stock recovery is available for Rogers yet. It sounds like all I have to do is find the correct RUU and flash it to the phone.
TrueLandon, you said after you held the power button down for 7 seconds you could put the phone into recovery mode. Would that be the same thing as the bootloader menu (where you can select fastboot, factory reset etc)?
Click to expand...
Click to collapse
Yes, sorry if I were unclear, still trying to learn the lingo and technical terms , and yea, that's what you would need then is the RUU for Rogers, but I think the other steps should work for you.
I'll PM you a link to 1.73 RUU for Rogers

achoj said:
Hi. This is the first time I've tried to install custom rom's on my phone so bear with me. I followed a post (since I can't post links yet just google: CyanogenMod 9 (CM9) for HTC One X is Here. It's the first link) detailing how to install CM9 on the OneX. Everything worked up until step 16 where you have to boot into recovery mode. When I select recovery mode from the bootloader, the phone just tries to restart and gets stuck at the HTC loading screen with a message underneath saying that this ROM is not official etc.
Is there an easy way to try and fix this and make it work properly? I've tried erasing the fastboot cache and that didn't make a difference. At this point I don't really care if I have to erase everything and just go back to what I had before. The phone doesn't show up as a drive on the PC when I plug it in.
Any help would be great!
EDIT: Is it even possible to do a factory reset at this point?
Click to expand...
Click to collapse
The facepalm is significant and this makes me wish HTC forced carriers to label the S4 One X as the One XL.
If your bootloader was unlocked, lock the bootloader and run the RUU from fastboot.

Thanks for the replies guys. Truelandon sent me the RUU that I need for my phone but there's no .exe file in it. I was just wondering if I can somehow use these files and flash my phone with this RUU. Most of the files that I ended up downloading are disk image files.

Addition to the issue
I flashed a cm9 rom on my hox (international version). Its working fine but the only issue is that i want to install black and cyan theme to it and when i try to flash it and the moment i hit recovery in boot loader my phone restarts and comes back normal.so i can't enter cwm to flash the theme.

manmeets said:
I flashed a cm9 rom on my hox (international version). Its working fine but the only issue is that i want to install black and cyan theme to it and when i try to flash it and the moment i hit recovery in boot loader my phone restarts and comes back normal.so i can't enter cwm to flash the theme.
Click to expand...
Click to collapse
Wrong forum you have the international one x the is the one xl forum so we can't really help your phone has completely different partitions.
The only thing I would suggest is to reflash your cwm and see if it helps.
Sent from my HTC One XL using Forum Runner

[Q] HTC One S Terrible bootloop/soft brick on TrickDroid ,cant find solution

Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Edit: Problem fixed. Downloaded the original all in 1 tool for htc one s, plugged phone into comp went to fastboot and with the tool flashed the phones stock recovery. I reset to factory defaults and cleared storage with it from the bootloader. After that, I flashed clockwork mod recovery again and my SD card was able to be mounted and accepted files from my adb push, and I reflashed cyanogenmod. Wuzzah!

milesmarrero said:
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Click to expand...
Click to collapse
lol, meant to "quote" not "thanks".
Can you fastboot a new recovery?
Did you do a full wipe coming from CM9 to TrickDroid

Well I can't access the phone from usb on my computer (still takes charge though), so I don't think I can flash a recovery thru fastboot (I'm not too experienced though). From cm9, I wiped all and flashed trickdroid + tweak set, then it just stat their at home screen. CMW being lost occurred later.

Im in the same situation rght now. I have trickdroid and I went into my tweaks to set them back to their original setup...so removing all of the options I chose before when I used the tweaks for the first time. When I rebooted my phone it just hangs on the HTC screen. I can get into recovery and I tried reinstalling trickdroid but its still getting stuck. Not sure what to do at this point. I don't think I can put a recovery file on this since I can't connect it to my computer.
Hopefully someone can help us.

But the thing is I can't access recovery. I try to flash it again with the all in 1 tool and it won't work. It says it went through, but accessing it doesn't work.

If its recognised by USB when plugged in computer just run an ruu that's my solution all The time lol
Sent from my HTC One S using xda premium

Ok i somehow managed to get TWR on my phone, but still unable to mount the SD. How do I run the RUU? I downloaded it, but the instructions are flawed I think

Connect with USB to.computer go into faatboot USB then run ruu on pc
Sent from my HTC One S using xda premium

Well I thought the RUU was going to work, but it just stops at the HTC and gives me an error saying I can't. What now?

Ok currently, I relocked my bootloader in an attempt to do the RUU, but I get a 155 Unknown Error up doing such, using the TMOUS 1.53 ruu... other places I have seen say something about returning to the stock img etc, but I'm quite stuck. Any advice appreciated

htc one s stuck in bootloop almost unresponsive
hey guys, got a brain teaser for you.
i have a tmobile htc one s, unlocked, rooted using all in one htc tool, been at it for two days now. im stuck on the boot screen showing its unlocked, i used to be able to get into the boot loader screen but now it seems ive dead ended. ill hold any combination of power and vol up/down, the keys flash for 10 sec and the screen flashes once, i let go and it reboots, keeps that htc screen, after 20-30 sec goes black. my pc doings like it detects a device but i cant locate it. ive used adb and the htc all in one unlock tool trying to get any kind of os to launch.
Shortly before this i was able to go into the boot loader, clear and master reset the files and cache, and search for the rom zip, thus never allowing me to flash. on a journey to place this in the phone through various combinations of the all in one, adb push, and everything else i found on youtube, countless forum posts, i seem to be in a deeper hole now.
I ultimately want to end with a cm10 nightly on my tmo htc one s. I have never done this to a phone without a sd card. i come to this community humbly seeking any and all advice. thank you.

[Q] HTC One messed up

I recently bought an unlocked HTC One and obviously tried to root it.
in the process, i may have completely messed it up.
currently, when i turn it on, it goes to fastboot.
adb cannot find any device.
i have tried flash recovery and all the drivers i could get my hands on.
i would really apreciate it if someone could help me out here.
Thanks.

Can't get past bootloader unlock

Hi everyone,
I am trying to help a buddy out and getting his phone working. The phone is not rooted in any way shape or form.
Here are my issues
The phone will not boot into the stock rom. I can get it into the bootloader. Which I went to htcdev. To unlock the bootloader. Followed the steps and was able to get the phone screen to show unlock bootloader. But when I hit yes it reboots and stays on the white htc screen. Then it will keep rebooting. When I go back into bootloader. It still shows the bootloader as being locked? Any suggestions. I haven't flashed anything in about 3 years. But only Samsung things.

This is my set up

Your best bet is to try latest RUU: http://www.htc.com/us/support/htc-one-sv-boost/news/

I tryed that as well. Thinking it is kinda like Odin for samsungs. But as soon as it try to reboot into bootloader. It stays on the white htc screen

The RUU was running completely through and it still not booting?

I will take a picture of the screen. It does not go all the way through. Also I tryed the Ota. Zip. And changed it to PL80IMG and placed it in my SD card. It looked as if it went through and it told me to reboot. But still nothing.

This is what's happening.

Forget the OTA. It won't solve anything for you.
I also think, your bootloader must be locked to run the RUU.
And i think it is your only chance to get the phone back running, because there is no stock rom or backup for boost (as far as i know).

I am OK with rooting it. But in order for me to do it I have to get the bootloader to unlock which I can't seem to do. It does all the motions to unlock. Until the phone reboots

What i have found in this few minutes, Error 171 should be a driver issue.
So, you should make sure that the correct drivers are running (HTC Sync). Maybe another PC could be also a good try.
And you can't root a phone which is not booting into OS. You need a OS.

Is there different drivers I could try besides tc sync. I have tried both computers that I have one has windows 8. The other has windows vista.both have htc sync on them. Also tried a different cable.

If I type in cmd fast boot devices it shows my device being connected. The error shows up while it is waiting for the boot loader to reconnect

Latest should be this.

I will give it a try thank you for helping me. I'm banging my head against the wall for 2 days trying to figure out why nothing is working on this.

Its really kinda strange, that bootloader should belocked again after reboot.
But your focus must be the RUU.

old.splatterhand said:
Its really kinda strange, that bootloader should belocked again after reboot.
But your focus must be the RUU.
Click to expand...
Click to collapse
Yea, my main goal is to get it to boot up. I was hoping it was an easy fix. Like with the Samsung epic I had. Just slap it in with odin and boom. after I couldn't get the RUU to work I figured I would try to root it. but since I can't even get the bootloader to unlock. I am stuck and that's the biggest reason I posted. normally I wouldn't I try to read other post and/or youtube it to find someone with a similar problem.

Quick question. When I go into the RUU can/should be in fastboot?

Yes, you should be in fastboot (USB) mode.

Ok so I downloaded the drivers you recommend. It was different then the ones I had. I also downloaded the RUU from the htc site as well just in case. Will try when I get back home. Thanks again.

So here is what I have. I downloaded driver v4.11.0.001. And installed. Downloaded ruu k2_cl_jb_45_s_sprint_wwe_boost_3.05.653.4......
I went into cmd and type fastboot devices. My device showed up. Ran the ruu. Samething happened. The ruu stops because when the phone reboots. It doesn't reboot to the bootloader.
Also I tried in cmd to get the phone to reboot to bootloader with no luck. Is there any thing else I can try?