Database Info

Help please! Just installed Android Revoluation HD, now won't turn on?

I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.

newr said:
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
Click to expand...
Click to collapse
Try to boot with adb.
Sent from my HTC Sensation Z710e using xda premium

Hi...I am trying to install the new SDK package...but I do have the older ADB and when I tried it..it first says ADB sever out of date...then started daemon...and attached list showed nothing?
When I plug the phone in...there's no response from the PC..it won't beep or show anything connected on USB!

I just tried to run adb after installing the latest sdk package. Running adb from the platform-tool directory...the device listed is empty....doesn't seem to be recognizing the phone!
Any other ideas? Is this completely bricked?

I wouldn't call it a brick per se, but this has happened to more Sensations than you may realize. Most people who've reported said they went to bed (phone on or off the charger) and when they wake up, it just won't turn on.
Honestly, I believe it's a random catastrophic hardware issue. I think some Sensations are faulty and have a lower temperature threshold or something, not sure, but what you described seems hardware related.
Edit: Just reread about that tone. A long tone? Although you were on a phone call so it's no guarantee, something like a long speaker tone or a screen spazzing out (I work in electronics) tend to mean something hardware related. Again, not 100% solid, but that's how it usually turns out.
Also, don't believe this happened because you flashed a different rom or something, there is just no way flashing a rom would kill a phone. If that were true, normal software updates or factory resetting could cause the same thing, and they simply don't.

Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?

newr said:
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
Click to expand...
Click to collapse
take off the battery, SD card, SIM card and then put them back again.....try to press power+volume down (even power+volume up & down, all buttons) to see if you can log into the recovery...I don't know if this works but since your phone is almost dead, you won't lose anything to try any method...Do you think so?
If anything you have tried does not enable the phone to work normally again, please try to turn to some body who can check and repair the hardware of your phone for help...It could take a long time to send it back to HTC.....
Hope everything is going well with you.

Nothing works..I've tried taking out Battery..talked with HTC and they tried that with me too...but basically the phone is completely unresponsive. I am just wondering if it's a problem with the ROM or if it's a hardware thing. It seems strange it booted up ok and then had this long beep/tone thing.
There seem to be one other person posted in Q&A experiencing exactly the same thing...he was using revolution 6.6.3 and also had that sound and now it won't turn on!
I have talked to HTC and got a repair ticket...not sure if anyone locally can fix it...just wonder if HTC will have problems with it being rooted and all.

He was running ARHD 6.6.3?! I just downloaded it, now I'm weary to flash O.O

@newr
can you try one thing?
Remove battery ,sdcard, then connect the phone to power outlet using usb then try to power on the phone.?
If it doesn't turn on then remove the back shell too and try to power it on again?
sent from my blazing fast pyramid through sonic waves

Thanks for the suggestion. But again nothing happened. I've tried taking out SD, SIM, battery...with or without cover. Nothing turns the phone on...also no light when charging. It's like the phone is just dead?
There's one other post by someone on the forum that says his phone doesn't turn on..and it seem to happen the exact same way. He said he was running 6.6.3 and then all of a sudden a long beep/tone...then stuck..so turned it off and won't turn on again. Haven't seen any update / resolution there neither!
I am still not sure if it's a ROM problem or if it's a hardware problem. The thing is, the ROM did get installed and was rebooted...in fact, I used Titanium to reinstalled all the apps...unless restoring some data for things like bluetooth settings, desktop etc..causes it...which was fine when I restored it for InsertCoin...I don't understand how a ROM could cause a phone not to turn on at all?
I guess unless there are other ways to fix this..looks like it's sending back to HTC...hopefully they can't fix it neither and just send a different phone since if they turn it on and notice I have it rooted and S-On..they might just blame it on that!

[Q] Random Reboots - S-OFF'd and SuperCID

I feel a little dirty having this as my first post, but this problem has been eating at me for a week now.
Current Bootloader Status:
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I bought this Sensation from eBay a week ago in a Used state, the owner said the only problem it has was the radio did not function correctly, most likely due to a dodgy flash (it was already rooted, S-OFF and with SuperCID), which I solved by re-flashing using RevolutionHD. All seemed fine until the second boot, where it began to reboot randomly, but ONLY when it has been normally booted and not in the charger. Thinking how it only rebooted due to the charger, I immediately thought it was the battery, but after swapping the battery from my perfectly working EVO 3D with the one in the Sensation, it STILL rebooted constantly. When in either the Bootloader or 4ext, it does not reboot or show any problems.
Just as a precaution, I went through the S-OFF and SuperCID processes again to see if he did something wrong along the way. I then re-loaded 4ext and ran the superwipe script, followed by re-flashing with a re-downloaded RevolutionHD. After its first boot, everything seemed fine for a day, no reboots and working like a charm, but soon went back to its rebooting error again, exactly like before. The same with other ROMs, both ICS and Gingerbread.
As the last extreme, I opened the Sensation to see if anything seemed odd or out-of-place, which is when I found out that the WiFi flex cable was missing, which even though I know I can easily buy a replacement, it annoyed me a bit, but I was wondering if that could upset the OS?
So yeah, at the moment I am at an impasse with this phone and, if I can't get this to work, try to get a refund due to the missing parts.
Any ideas?

Hi,
you said you tried both GB and ICS. Did you flash the correct firmware with the roms? And which kernel did you use?

I used the firmwares recommended in the ROM threads and kernels that came with them.

That seems strange. Android Revolution HD is a very stable rom. I ran it for quite a long time until i couldnt see Sense anymore.. So your problem should not be rom related. I think the only thing you didnt try was wiping dalvik cache. I read in some rom threads that it is recommended to do it when you flash the rom. But I dont know if this would help. I only heard of people getting random reboots when they ran an unstable rom.

so when flashing Roms you used the 3.32 firmware? In my "personal" opinion I would be a bit upset for the missing part. Even if you were able to get the device to function as it should, missing parts are not acceptable unless previously stated in the purchase contract. Like i said only MY " opinion" but if it were my device and I was certain their was no mention of the missing parts, I would definitely take the device back. And I would buy another with all parts present, however this is just a opinion and its up to you on what you want to do. I think its wrong to sell a device with missing parts unless the buyer is aware of this before sale. So if it were mine, I'd take it back and have him explain why you were NOT told ahead of time about the missing part! I wish you the very best in whatever you decide to do! Good luck to you! The sensation is a great device and I think you will love it!
Sent from my HTC Sensation Z710e using xda premium

Thanks for the advice so far guys.
That's what I told my Dad (it's actually his phone he bought, but I'm doing all of the legwork, I'm an EVO 3D man ), I said he should ask for a full refund due to the product not being as advertised, but he still wants to keep it and replace the cable. Dads, eh? I assume that firmware updates the radio, correct? I noticed that when I flashed the latest firmware on the Sensation, the radio version DID NOT change. I have just finished flashing with the latest radio and RIL available for ICS ROMs, which has given me a new version number. I'll keep posted to tell you guys if it solved the issue or not.

Nope, still rebooting. Can the the lack of the flex cable cause issues with the OS? I think I've ruled out software by now, unless you guys have other suggestions?

Tezuka101 said:
Nope, still rebooting. Can the the lack of the flex cable cause issues with the OS? I think I've ruled out software by now, unless you guys have other suggestions?
Click to expand...
Click to collapse
do you have wifi turned on or what... it was the wifi cable right, I would check to see under setting that only mobile data is being used not wifi.... just my thought.

Sadly I can't switch it off, it constantly tries to switch it on, but due to the cable missing it always fails and retries constantly.

Tezuka101 said:
Sadly I can't switch it off, it constantly tries to switch it on, but due to the cable missing it always fails and retries constantly.
Click to expand...
Click to collapse
well you could try to reinstall the rom and in setup it asks about data usage i think try to click for mobile data only....
what rom are you using on the phone ????

I'm currently using RevolutionHD. I have tried Virtuous and getting the same result. I'm re-downloading RevolutionHD to try what you said and choose mobile only.

With WiFi on the off setting (but saying "Error") it still reboots. I've now run out of ideas what this could be. What else could be causing this?

Phone acting stooopid.

Ok, so my phone is just not wanting to work. One day it just started to randomly reboot. I was thinking since it was around 100 degrees in my house, my phone was over heating. Then it would go from random hard reboots, to not turning on at all. It would even happen in recovery, and my phone can rarely flash a rom now. I know this is because some really stupid reason. I feel like my battery comes loose, or something XO Any help is good help =D

AgentCherryColla said:
Ok, so my phone is just not wanting to work. One day it just started to randomly reboot. I was thinking since it was around 100 degrees in my house, my phone was over heating. Then it would go from random hard reboots, to not turning on at all. It would even happen in recovery, and my phone can rarely flash a rom now. I know this is because some really stupid reason. I feel like my battery comes loose, or something XO Any help is good help =D
Click to expand...
Click to collapse
Well maybe put a different battery in, maybe the one you have if failing.
Sent from my myTouch_4G_Slide using Tapatalk 2

wiswis said:
Well maybe put a different battery in, maybe the one you have if failing.
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
I have no clue where my other battery is at XO

I keep on getting status 0 in recovery with any rom. But when that isn't happening, the rom will hang on flashing. Like Bulletproof 1.1, it will hang at Apply Kevlar ...please be patient.

Fixed it, flashed a backup :3 Any clue why it did this? I had to format the phone like a million times Xo
::Sense 4.0::

????? That's weird ???????
Sent from my myTouch_4G_Slide using Tapatalk 2

Ok, so my phone was acting dumb. I was finally able to get it to boot, but knock on wood *knocks on wall*. I had to flash to stock (Still S-Off). Now I'm booted and running fine. I have no idea why. :T Puzzles me, also I'm tired as hell. So this might be very random.
I couldn't get my phone to stay on for more than 10 minutes. Sometimes it just wouldn't. Boot. I was not able to get Roms to flash (status 0).
So I (re)flashed CWM 5.5, and that seemed to help. Then I was only able to use backups.
Then I just couldn't get my phone to work :T
So I flash the update in the Hboot to get back to stock.
1st it booted fine. But I rebooted to Hboot, and got funky issues (would not boot past bootanimation)
Flash Hboot update twice.
Then I did two factory resets in Hboot.
Then I got my phone working. I've been slowly typing this over 1 1/2 30 Rock episodes. No reboots :T Should I unlock and get CWM on here? I feel like my issue was not being on a stock kernel. Plus on stock I'm getting crazy battery life.
I'll see how my night charge goes. Hopefully she stays booted :d
Sent from my myTouch_4G_Slide using xda app-developers app

Sounds like maybe the internal memory chip is going south. At least something to consider.
How long have you had it now? Approaching the limit of rewrites flash memory is good for?
Sent from a digital distance.

Blue6IX said:
Sounds like maybe the internal memory chip is going south. At least something to consider.
How long have you had it now? Approaching the limit of rewrites flash memory is good for?
Sent from a digital distance.
Click to expand...
Click to collapse
I just got a replacement phone about a month and half ago. The only Rom it stays stable with is the stock Rom. That makes a lot of sense tho', I was thinking my phone couldn't handle a UV. My phones running perfectly (and faster, and smoother than ever). I'm going to try unlocking it again, and reflashing the recovery. See how far that takes me.

Ok, so I unlocked my bootloader (No recovery). It was having trouble booting. Wouldn't boot with the USB plugged in. But I'm still 100% stock (S-Off, Unlocked). I'm going to run stock for 2 hours, and see if I get reboots.

So my phone acts up on custom kernels, that's what I'm seeing.

So my phone starts acting up when the battery is below 15%, and not running a stock kernel. :T

[Q] Phone occasionally becomes completely unresponsive with non-stock ROMs

Quick background: I purchased a One X from AT&T a few weeks ago. It came with the 2.20 firmware, so I used the X-Factor Exploit and unlocked the bootloader via HTCDev. From there I flashed TWRP Recovery and then AOKP.
Pretty much everything was fine at that point, except for the fact that once or twice a day I would pull my phone out of my pocket and it would be completely unresponsive. None of the buttons would wake the phone up, plugging it in didn't do anything, and it wouldn't receive calls. I would then have to do a hard reboot (Power + Volume Down) to get anywhere.
I thought maybe it was an AOSP problem, so I flashed a Sense-based ROM (CleanROM 5). I experienced the same issue.
From there, I re-locked the bootloader and ran the latest RUU. That was 4 days ago and I have yet to experience the problem again.
Has anybody else experienced this, and is there any way to prevent it?

power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?

redpoint73 said:
power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?
Click to expand...
Click to collapse
I would just select reboot and it would boot normally. Power alone would also work, I believe. I usually just did power and vol down out of habit I guess.
GPS and WiFi were always on.

What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app

c5satellite2 said:
What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
HBoot 1.14. Didn't mess with the radio, so the stock AT&T 2.20 one (0.19as.32.09.11_2_10.105.32.25L).
Yes, I flashed the correct kernel. It did it with both the plain AOKP kernel and rohan's kernel.
Cleared caches several times.

GPS on when this happens, by any chance?

redpoint73 said:
GPS on when this happens, by any chance?
Click to expand...
Click to collapse
I hardly ever disable it, so it was likely on. No idea if it was actually in use any of the times.
I can say one time it happened immediately after a call, one time it was immediately after a SMS notification, and the rest just seemed to be randomly in the middle of the day.

Try going straight to CR5 directly from the stock ruu rom and see if it persists. Maybe the aokp Rom borked something along the way and the ruu has restored it now. I have seen issues similar to this that only the ruu will fix.
Sent from my HTC One X using xda app-developers app

Have the same issue.Try going to ViperXl and see what happens.My phone constantly reboots and enters sleep of death.I always have the gps disabled.have 1.09 hboot.And currently I am on 1.85 stock at&t.This issue is kikling me

I only mention GPS, since my old phone (Desire Z) had an issue where leaving the GPS on, would make the phone shutdown, and only a battery pull would start it (never tried going into hboot). Which sounds similar to what you were seeing. In my case, no ROM, kernel, or radio flashing ever remedied it. And I could isolate the issue to the GPS being on. If the GPS was used, the phone was going to black screen within a couple hours, without fail. But rebooting the phone after using the GPS (and shutting off GPS) prevented it every time. A few other owners of the DZ had the same problem. One guy sent his into HTC, and they told him it was a defect of the GPRS module, and replaced the motherboard, which fixed the problem.
Hopefully, its not a similar hardware issue in your case. But the fact that you have the GPS on all the time, and the black screen hasn't cropped up like clockwork (like it did in my case) seems to point to the fact that it might not be the exact same issue.
These types of issues tend to be really hard to troubleshoot (and pinpoint the cause). In my case, it took me a couple months to realize it was the GPS, since I usually have it off, and don't use it all that often (usually just when travelling). And I also suffered a lot of "placebo effect" type incidents while flashing various ROMs and kernels trying to fix the issue. If the issue doesn't crop up again after running the RUU, I'd consider myself lucky, and leave it well enough alone.

No it is not the same problem redpoint73.This only happens on Custom ROMS.I have tried every combo on the 3 ROMS i flashed.Could it be an int.d problem???My only is this.

nighthawk696969 said:
No it is not the same problem redpoint73.This only happens on Custom ROMS.
Click to expand...
Click to collapse
Yeah, I already said its probably not the same problem. But it doesn't hurt to check everything. As I mentioned, its easy to get sucked into thinking you have the cause isolated, when you really do not.

I understand what you're saying but i have checked it,i'm sure..

nighthawk696969 said:
I understand what you're saying but i have checked it,i'm sure..
Click to expand...
Click to collapse
It also doesn't sound like your problem is exactly the same as the OPs. You mention reboots, while OP does not (just BSOD, or shutdown requiring rebooting in hboot).

No my main problem are the Sleeps of Death.There are no BSODs in android

nighthawk696969 said:
No my main problem are the Sleeps of Death.There are no BSODs in android
Click to expand...
Click to collapse
Some people have been calling this condition BSOD = Black screen of death. Yes, its a little too derivative of things like Windows blue screen, XBox RROD etc. But you get the idea.

Update: I re-unlocked the bootloader and flashed CM 10.0.0 upon its release. I've yet to encounter this issue, so I'm thinking my stint on CleanROM might have buggered something. I probably forgot to wipe something somewhere along the line. D'oh.
I am, however, having a pretty severe albeit unrelated problem with an app called Voxer. Every time I listen to a message it kills the microphone until I Force Stop the app. I guess I'll pop over to one of the other AOSP ROMs and see if it persists.

I was having a similar problem on king kang and pacman. I could turn the phone on and off with the power button, but the touch screen was completely unresponsive. Happened randomly, I would have to hold the power button down and watch the lights flash until the phone shut down, and would be fine after a reboot. When I tried installing viperxl, I had the same issue during the aroma installer, I had to try flashing it 7-8 times, because it kept freezing during the install. No issues running it after a successful install. I was using king kang and rohans b5 kernel when it was happening most often

Not getting texts until reboot?

Ever since I bought my phone, before being rooted and even on stock ROM, I'll get delayed text messages and they wont recieve until I reboot my phone or switch airplane mode on and off. Then they hit me ALL at once. This happens atleast once a day and people will end up thinking I'm ignoring them because of this problem. Is it a problem with the HTC One X in general? or Android? It still happens on every single ROM I tried too and I have tried various radios and none fix it. I am on AT&T, and currently on MagioRom. It still does it regardless of what ROM though. This is the one single thing that I have just sort of learned to put up with, as much as I hate it. I came from an iPhone and they never had that problem so I really miss that. I reboot my phone about 5 times a day to remedy it. Besides that this phone is amazing of course.
Oh and was the bug with iPhone screenshots being sent through text to the One X and coming out really really tiny ever fixed? Im still getting that problem too.

It's not a problem with the phone or Android as such. Do you ever suffer signal drops which may cause this to happen? Or do you live in an area with low signal? It sounds more like a carrier bug to me.
Sent from my Evita

timmaaa said:
It's not a problem with the phone or Android as such. Do you ever suffer signal drops which may cause this to happen? Or do you live in an area with low signal? It sounds more like a carrier bug to me.
Sent from my Evita
Click to expand...
Click to collapse
I always have great signal, no signal drops ever, so I never thought it would be my carrier, thats strange... Now I don't know if its AT&T or a defect with my phone...

It could be an issue with your phone? Have you tried running an RUU? I'd do that and leave it stock fire a few days to see if it continues. You'll want to make sure you're safe to RUU first though, what are your hboot details?
Sent from my Evita

Hboot 1.14
I can't RUU yet though cause I'm still S-On, which I haven't tried to do yet because I didnt wanna risk messing my phone up... Would that actually help?
And could it be an Hboot version problem or firmware problem? Cause I bought my phone about 1 year ago and it came with Icecream Sandwich. And I've had to deal with this problem the entire year.

It could be anything. Do you have SuperCID? You definitely must get s-off before running an RUU.
Sent from my Evita

Yep, it says 111111111111
I'll try getting S-Off and running RUU then, I just really wanted to avoid doing that but I guess I have no choice.

Sometimes it's the only way to find out what you're dealing with. The process is simple, it took me five minutes.
Sent from my Evita