Related
My friend and I both have Rezounds. I have yet to get the update, he had Scott's ICS ROM on his. The update forced itself onto his phone and bricked it. When he went to the store, the reps told him the update seems to be doing this to alot of people (rep said they saw 10 of them today!). Anyone else have the OTA brick a ROM's phone or even stock?
durthquake said:
My friend and I both have Rezounds. I have yet to get the update, he had Scott's ICS ROM on his. The update forced itself onto his phone and bricked it. When he went to the store, the reps told him the update seems to be doing this to alot of people (rep said they saw 10 of them today!). Anyone else have the OTA brick a ROM's phone or even stock?
Click to expand...
Click to collapse
No, but I am sure if you have a custom recovery on your phone with a custom rom an official update sure isn't going to help ..but I figured it would just error out. How did it brick it ? he was unable to load Hboot anymore ?
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
durthquake said:
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Could you get into hboot and run the ruu? If you can do that, the phone isn't bricked...
Sent from my ADR6425LVW using XDA App
durthquake said:
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
I suspect the no charging is due to running the battery down all the way. There's a thread or two about that issue. I think the solution was to pull the battery, plug in the charger then put the battery back in while phone is connected to charger. Then you might have to wait up to 30 minutes for the light to turn on and for it to start charging.
And yeah, if you can boot into hboot you should be able to get the phone back with RUU or if the ROM is fine then flash Amon Ra recovery in fastboot.
It didn't allow anything to be done in hboot. It won't even turn on now, i have him my battery to try and still doesn't turn on.
Sent from my ADR6425LVW using Tapatalk
Well read through this thread:
http://forum.xda-developers.com/showthread.php?t=1434532
and see if you can at least get it charged up again. Then go from there.
Both me and my wife have had the OTA for at least a week and we have not had any issues with the OTA.
Also, I must say, this is the first time I have heard of the OTA causing bricking of the unit.
If you can't get it charged, try the writing hack to get it involved. Basically you just take a regular usb cable and snip the connector off. From there you take the ground and the power, and then you put the ground and power to the battery in the respective places. Worked for a bad Atrix flash that killed my battery.
Sent from my Galaxy Nexus using Tapatalk
I hadn't heard of it bricking it till I saw it first hand... As far as charging, it's a non issue since I have my friend my fully charged battery to try and wouldn't turn on. (Note that this is happened only after it stayed on the HTC screen for about 30 minutes, so it may have overheated or something during that time?)
Sent from my ADR6425LVW using Tapatalk
It bricked my stock Rezound. Could not have happened on a worse day to. I had to do a factory reset to get it to come back. Real PIA
Chris
drtnsnw said:
It bricked my stock Rezound. Could not have happened on a worse day to. I had to do a factory reset to get it to come back. Real PIA
Chris
Click to expand...
Click to collapse
That's not a brick. That's a pain in the ass.
tekhna said:
That's not a brick. That's a pain in the ass.
Click to expand...
Click to collapse
+1
a brick is just what it is.. a brick.
which means the phone is done. you can't use it again.
durthquake said:
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
If it can get to the HTC screen, it isn't bricked. Put your battery in his phone and see if it can get to HBOOT.
durthquake said:
I hadn't heard of it bricking it till I saw it first hand... As far as charging, it's a non issue since I have my friend my fully charged battery to try and wouldn't turn on. (Note that this is happened only after it stayed on the HTC screen for about 30 minutes, so it may have overheated or something during that time?)
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
I don't think you can write off the battery/charging issue. It takes some time for people who have let their battery fully drain to get the phone to charge it again although they were able charge on an external charger iirc. Anyway, point is it may be the phone not the battery that needs to "wake up" (for lack of a better term) again.
So definitely go through that dead battery charging thread and try everything in there to get the phone to charge the battery again. Then you'll know the phone is functioning as it should, atm it may not be.
I don't understand how the the OTA forced itself since all of Scotts ROMs are debloated. Everyone that rooted and debloated running stock, said that the update failed in recovery, I know I witnessed it on mine. Being on an ICS build, one would think that the update wouldn't even be downloaded.
yeah it is strange. Even if I force check for update on my Rez the update doesn't come. Are you sure your friend is telling you the whole story?
con247 said:
yeah it is strange. Even if I force check for update on my Rez the update doesn't come. Are you sure your friend is telling you the whole story?
Click to expand...
Click to collapse
I am said friend.
Durthquake sits in the cube next to me. He watched the whole event transpire.
Here's what happened and what was tried and the resolution,
Rezound reboots to the HTC screen. Won't show the think brilliantly words. Just stayed on HTC.
So I did a battery pull and rebooted phone and same thing. Just HTC.
Now I reboot to recovery, get hboot and try to do a wipe. It blinks like its going to try to go to recovery then turns off.
Do another battery pull boot maneuver and it does the same thing.
As we are at work I did have to work so I leave it on the stock wall charger for about an hour and try to turn on again. HTC screen so I leave it to see what happens, maybe I didn't wait long enough.
Like 35 minutes later screen goes black.
Now it won't power on, won't go to hboot, basically a brick. So I pull my battery give it to durthquake who gives me his rezound battery. His phone turns on, mine doesn't.
Now I try pulling sim, sdcard, and putting my battery back in. Still nada. Phone be properly bricked.
Bring it home put sim, sdcard, and battery back in and put on HTC wall charger overnight. In the am nothing. Still a pretty beats brick.
Go to vzw and the try charging turning on etc. Nada. They say since the ota they've had about 5 of these in.
The resolution is vzw sending me a new rezound and I buying a new phone so I can give the resound to my gf.
Sent from my Galaxy Nexus using Tapatalk
Hey all I was wondering if anyone could help me with my HTC Amaze. It stopped turning on maybe a month ago. I was sleeping and forgot to charge the phone so I woke up in the morning and put it on the charger and went back to sleep. When I woke up again there wasn't an LED light or anything. Eventually after messing around with it for a while the orange light would turn on for maybe 10 seconds then it would turn off and the phone would vibrate for a while and turn off too. I went on eBay and bought a new battery that came with an outlet charger. Waited a while then it finally came I charged the original battery as well as the new one. The phone still won't turn on, but now the orange LED light will stay on and after a while the green light will come on. I'm not tech savvy so I never rooted or unlocked my phone or whatnot I've just been using it normally since I've gotten it. I tried to make a claim from Asurion but they won't cover it without the deductible so I thought I'd try here before I just gave up and got a new one. If anyone can help please me please help. =)
There have been some posts of battery issues. Have you tried a different battery?
yep . i tried to charge the battery on the adapter and use the origional/new battery with no luck. :crying:
If it goes green, the battery says full charged, you're not telling us something.
Dark Nightmare said:
If it goes green, the battery says full charged, you're not telling us something.
Click to expand...
Click to collapse
Before when it first wouldn't turn on, when i tried to charge it, the orange light would come on for 10 seconds before turning off and vibrating periodically. Now the phone will act like it's charging (staying orange for a long time then turning green). But when I wait until it's green and try and turn it on no avail.
gooseprince7 said:
Before when it first wouldn't turn on, when i tried to charge it, the orange light would come on for 10 seconds before turning off and vibrating periodically. Now the phone will act like it's charging (staying orange for a long time then turning green). But when I wait until it's green and try and turn it on no avail.
Click to expand...
Click to collapse
Did it fall down by chance?
Dark Nightmare said:
Did it fall down by chance?
Click to expand...
Click to collapse
yea once but that was like 2 weeks ago before this started to happen. do u think it would be the digitizer or a part inside the phone ?
gooseprince7 said:
yea once but that was like 2 weeks ago before this started to happen. do u think it would be the digitizer or a part inside the phone ?
Click to expand...
Click to collapse
Something could've gotten loose and normal shaking in the weeks to follow probably finished the job getting it undone. Did you call your carrier or HTC about it?
Just tell them it randomly shut down after the ICS update and then eventually it stopped coming on or something, yes I know that's lying, but I don't think hardware is usually covered under warranty, unless it was faulty from the get go.
try removing the back cover and pressing the power button. the button on my back cover doesn't work as well as it used to, it'll power the screen on when it feels like it....must've come loose.
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1759925
-Also, did you buy the phone new? And you said you didn't root/unlock? If you bought it used the person before you may have installed a custom recovery.
very weird i agree just call htc and say you phone got messed up doe to the ics ota update im sure they will replace it :laugh:
So something very weird has happened..
I had my phone plugged in charging as I was going to sleep, everything was working fine. I wake up 4 hours later, and go to check my phone but nothing happens, and I notice that I have no charging light, nothing. I unplug the charger and plug it into my computer...nothing, I try a different cord...nothing. I tried holding the power button, but still nothing. I'm really confused as to what could have happened, because like I said it was just sitting there charging, I don't keep any open water anything near it either, so that couldn't have happened.
My phone is rooted, and is s-off, I was running MeanRom 4.3 when this happen, and it had been on that for 4 days without any issues.
Any Ideas what could have happened, or what I can?
so quick update, phone started rebooting like crazy all of a sudden. I heard it vibrate on my night stand, and noticed it was on the HTC boot screen, then it went black, and did it again. So I held power+volume down and got to the bootloader, but again it just randomly rebooted while it was in bootloader, as it was restarting it made it to the start up animation, however just went black again for about 3-4 mintues, then started rebooting again....I am very confused...
Well I had the same problem, but my phone Never got reboots or anything just dead.. Ended up with service on guarantee and they had to change the moderboard of my phone
Sent from my GT-I9100 using Tapatalk 2
man I hope that not the issue, but its rebooting like crazy now, and I actually rebooted enough to fully boot at one point, and the weird thing is, the Back buttong, home button and recent apps button were flashing, just like they do when you hold the power button in...
cvinton07 said:
man I hope that not the issue, but its rebooting like crazy now, and I actually rebooted enough to fully boot at one point, and the weird thing is, the Back buttong, home button and recent apps button were flashing, just like they do when you hold the power button in...
Click to expand...
Click to collapse
I had the same problem with my first 2 EVOS, the just went dead but in my case they never came back up, Sprint replaced both under the 2 weeks warranty period... Bad batch maybe?
elculito said:
I had the same problem with my first 2 EVOS, the just went dead but in my case they never came back up, Sprint replaced both under the 2 weeks warranty period... Bad batch maybe?
Click to expand...
Click to collapse
Well looks like a trip to Best buy at lunch today (I have the Bestbuy insurance because there is no fee for insurance claims...)
I'm just worried that while I'm there that it will try to start bootlooping, and they will see the text on the "Quietly Brilliant" screen, or it will go far enough to show MeanRom's boot animation, and they will stop the thing on the spot. After posting this morning it has had 2-3 sessions of wild boot loops, where it is continuous every couple of seconds rebooting. In the 3 minutes I've been typing this, it has gone through probably 10 cycles, each time making to the end of the Quietly Brilliant HTC screen where it shows the "This build is for HTC Development only..." yikes...
Best buy doesn't care if its rooted man. I brought in 2 rooted EVO's and exchanged them on the spot. Most of them don't even know what root is. If they did they don't know about the HTC dev screen.
as you read in the topic title. My HTC thunderbolt is dead. nothing. no yellow / green light at all. This has happened before..but a simple battery pull for about 20 minutes and a restart got me going again. Now...it won't work. I'm not a noob where I flashed the wrong radio or something stupid like that. I had fully functioning Thunderbolt with LiquidSmooth ICS JMOD MR2. Before my phone decided to commit permanent suicide, it was rebooting to the boot screen every hour or so to the LiquidSmooth boot animation while I was using PowerAmp. Then I shut if off normally (just like last time..) and now it won't charge turn on, or do ANYTHING. It won't even go to the HTC logo where I can go to clockwork or the hBOOT menu. I'm running out of options. If anyone could give me advice. That would be great, as I cannot afford another one :___;
Thanks for your time = ]
stanleyopar2000 said:
as you read in the topic title. My HTC thunderbolt is dead. nothing. no yellow / green light at all. This has happened before..but a simple battery pull for about 20 minutes and a restart got me going again. Now...it won't work. I'm not a noob where I flashed the wrong radio or something stupid like that. I had fully functioning Thunderbolt with LiquidSmooth ICS JMOD MR2. Before my phone decided to commit permanent suicide, it was rebooting to the boot screen every hour or so to the LiquidSmooth boot animation while I was using PowerAmp. Then I shut if off normally (just like last time..) and now it won't charge turn on, or do ANYTHING. It won't even go to the HTC logo where I can go to clockwork or the hBOOT menu. I'm running out of options. If anyone could give me advice. That would be great, as I cannot afford another one :___;
Thanks for your time = ]
Click to expand...
Click to collapse
Flashing the radio is the only thing u can flash and completely brick your phone with no fix if you flash wrong or the radio is for a different device then I think your just gonna have to move on to a different phone.
Sent from my AOKP HTC Thunderbolt from Tapatalk 2.4
jonah1234 said:
Flashing the radio is the only thing u can flash and completely brick your phone with no fix if you flash wrong or the radio is for a different device then I think your just gonna have to move on to a different phone.
Sent from my AOKP HTC Thunderbolt from Tapatalk 2.4
Click to expand...
Click to collapse
This is exactly what I didn't do. I was just stating that because I bet some users on here flash the wrong radio or unplug it during flashing and cry on here later for a solution. This is what I did not do.
With that said...is there any possible solution for my dilemma?
stanleyopar2000 said:
This is exactly what I didn't do. I was just stating that because I bet some users on here flash the wrong radio or unplug it during flashing and cry on here later for a solution. This is what I did not do.
With that said...is there any possible solution for my dilemma?
Click to expand...
Click to collapse
Try a different battery maybe. It might be dead. Your USB port could have gone bad too.
Sent from my Thunderbolt using Tapatalk 2
Not any solution or consolidation, but my first bolt did the exact same thing after flashing a rom that I won't name here. The issue was most likely mine,but it happened to me and at least one other user as well.
If yours spontaneously croaked, most likely not the same issue, but mine presented exactly what you described.
I had to get a replacement.
Sent from my ADR6400L using xda premium
smtom said:
Not any solution or consolidation, but my first bolt did the exact same thing after flashing a rom that I won't name here. The issue was most likely mine,but it happened to me and at least one other user as well.
If yours spontaneously croaked, most likely not the same issue, but mine presented exactly what you described.
I had to get a replacement.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I had 4.0 LiquidSmooth ICS JMOD my custom ROM on my phone ever since the rom first came out.and it was perfectly...fine...
and this same problem happened when I had GB ThunderShed CM7..but my gf told me to pull the battery out and leave it out for 20 minutes..then it put it back in. It worked. She did this many times with her Droid 1. Since it was problematic with this issue. (first android phone OF COURSE its going to have problems) Now she's an iPhone user i'm constantly trying to convert back lol
anyway...as stated before..it's now done it again and this time it's totally dead. my phone was trying to tell me something I bet.
How old is your phone?
Nothing to do with radios or ROMs. A bricked phone will still receive a charge. You need to try a different battery ( preferrably 1 that is charged and for the Thunderbolt) once you get it booted into whatever ROM you're using, go to menu, settings, power and make sure that "fastboot" isn't checked. By default fast boot is checked by HTC and by most ROMs. What fastboot does is just put your phone into "hibernate" much like a PC does.
So when you turn your phone off, it appears that its off, but its really just sleeping. If the battery dies and fastboot is checked, the phone is hella confused about its current state. HTC did this by default for a better customer experience, but its kinda dumb and bad in the long run as your phone never gets a freaking break. Lol
Thats why I'm suggesting getting a good battery to boot up to a ROM or whatever, turn off fastboot, properly turn off the phone then charge your battery. It may take up to 10+ min before you to get an orange light that'll flash then eventually go solid. Let it go solid for about 20+ min to be on the safe side, then boot
Good luck man
Sent from my Geeked n Tweaked GS3
Man I bought one off craigslist that did the exact same thing. Had it about a week. Started random reboots so I was restoring a backup. While trying that recovery randomly rebooted a couple times them finally restore finished. It bootlooped so I pulled the battery and that was the last time it did anything. PC won't see it, won't get a charge light. Put a fully charged battery from my other tbolt in it. Still nothing. It literally died in my hands. I guess a hardware failure was the cause. Also picked up the wireless charging battery cover to try my power mat to see if that would at least make the charging light come on ....nope
dopediculous said:
Nothing to do with radios or ROMs. A bricked phone will still receive a charge. You need to try a different battery ( preferrably 1 that is charged and for the Thunderbolt) once you get it booted into whatever ROM you're using, go to menu, settings, power and make sure that "fastboot" isn't checked. By default fast boot is checked by HTC and by most ROMs. What fastboot does is just put your phone into "hibernate" much like a PC does.
So when you turn your phone off, it appears that its off, but its really just sleeping. If the battery dies and fastboot is checked, the phone is hella confused about its current state. HTC did this by default for a better customer experience, but its kinda dumb and bad in the long run as your phone never gets a freaking break. Lol
Thats why I'm suggesting getting a good battery to boot up to a ROM or whatever, turn off fastboot, properly turn off the phone then charge your battery. It may take up to 10+ min before you to get an orange light that'll flash then eventually go solid. Let it go solid for about 20+ min to be on the safe side, then boot
Good luck man
Sent from my Geeked n Tweaked GS3
Click to expand...
Click to collapse
You should try this, heck order a battery and wall charger off of Amazon for about $15.... Put the battery in and use ADB to put your phone into recovery....
Sent from my Inspire 4G using xda app-developers app
playerjunglejosh said:
You should try this, heck order a battery and wall charger off of Amazon for about $15.... Put the battery in and use ADB to put your phone into recovery....
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
Doubt that'll work if its the same as mine. PC and adb won't see it. And I used known good batteries and charger from my other bolt.just gonna hold on to it in case I find one with a busted screen for cheap on craigslist
Well I've searched the net and this has happened to several people that weren't even rooted or on a custom Rom. To me it seems like the motherboard(or the phones equivalent) is fried....that would explain why it happens on many thunderbolts(but it could just be a simple fix that I don't know of)
Sent from my Inspire 4G using xda app-developers app
Lightning Won't Strike Twice Folks
disconnecktie said:
Try a different battery maybe. It might be dead. Your USB port could have gone bad too.
Sent from my Thunderbolt using Tapatalk 2
Click to expand...
Click to collapse
I had 2 differernt batteries one extended...the other the stock small one. both would not charge. and both had decent battery power when I shut it off.
Shadow Death said:
How old is your phone?
Click to expand...
Click to collapse
Got it a month after it came out first 4G LTE phone maaan
dopediculous said:
Nothing to do with radios or ROMs. A bricked phone will still receive a charge. You need to try a different battery ( preferrably 1 that is charged and for the Thunderbolt) once you get it booted into whatever ROM you're using, go to menu, settings, power and make sure that "fastboot" isn't checked. By default fast boot is checked by HTC and by most ROMs. What fastboot does is just put your phone into "hibernate" much like a PC does.
So when you turn your phone off, it appears that its off, but its really just sleeping. If the battery dies and fastboot is checked, the phone is hella confused about its current state. HTC did this by default for a better customer experience, but its kinda dumb and bad in the long run as your phone never gets a freaking break. Lol
Thats why I'm suggesting getting a good battery to boot up to a ROM or whatever, turn off fastboot, properly turn off the phone then charge your battery. It may take up to 10+ min before you to get an orange light that'll flash then eventually go solid. Let it go solid for about 20+ min to be on the safe side, then boot
Good luck man
Sent from my Geeked n Tweaked GS3
Click to expand...
Click to collapse
this phone does not. I had two batteries with a decent charge and they didn't charge on it. The ROM I was using was a AOSP rom. not sense based...so there was no power menu and a fastboot option to uncheck
wampuscat said:
Man I bought one off craigslist that did the exact same thing. Had it about a week. Started random reboots so I was restoring a backup. While trying that recovery randomly rebooted a couple times them finally restore finished. It bootlooped so I pulled the battery and that was the last time it did anything. PC won't see it, won't get a charge light. Put a fully charged battery from my other tbolt in it. Still nothing. It literally died in my hands. I guess a hardware failure was the cause. Also picked up the wireless charging battery cover to try my power mat to see if that would at least make the charging light come on ....nope
Click to expand...
Click to collapse
yep. it did die in my hands. I'm chalking this up to hardware failure as well...
playerjunglejosh said:
You should try this, heck order a battery and wall charger off of Amazon for about $15.... Put the battery in and use ADB to put your phone into recovery....
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
two batteries and they do the same thing..and I cant boot into ADB mode if the damon can't detect the device on.
playerjunglejosh said:
Well I've searched the net and this has happened to several people that weren't even rooted or on a custom Rom. To me it seems like the motherboard(or the phones equivalent) is fried....that would explain why it happens on many thunderbolts(but it could just be a simple fix that I don't know of)
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
Yep. the Motherboard is fried. has to be.
Thank you so much everyone for your advice, concern and help..but nothing can fix or repair hardware failure to this extent
I got a used HTC Rezound. It's amazing...it's everything the T-Bolt should have been
even though I had this problem before and a long term battery pull fixed it...Looks like Lightning Will Not Strike Twice for The Thunderbolt.
Thank you for your concern and support....but it's just as good as a future spare parts phone on craigslist.
This thread can be locked now.
I'm completely at a loss here. I was running a 4.3 rom for the past week or two with no issues. Pulled my phone out of my pocket 30 min ago, hit the power button and the screen wouldn't light up. I tried it again and still no go. I tried swiping to unlock, even with the black screen and i felt it vibrate.
Ever since then my phone is non responsive. I can't get it to boot, can't hard reset it, nothing. The vibrates stop when I'm holding down power and down volume but that's about it. I timed the constant vibrates and they happen every 34 seconds according to the Win8 clock (which i've heard in inaccurate).
I'm gonna let the battery drain and hope that it will boot back up after it dies...but until then, any ideas?
Try plugging it into your computer and see what comes up. Which 4.3 ROM were you on?
Sent from my EVO using XDA Premium 4 mobile app
FinZ28 said:
Try plugging it into your computer and see what comes up. Which 4.3 ROM were you on?
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's the first thing I tried. I get nothing when i plug it into my comp. Nothing pops up in device manager. The comp doesn't detect it at all.
And I was running the 8/23 release of carbon 4.3 and I didn't have one problem with it until this happened :\
EDIT: The phone's battery finally ran out. It stopped vibrating and after a bit i plugged it in. After a few min it just starting doing it again.
I disassembled the phone and removed the battery for awhile hoping it would somehow help. Didn't do anything. It showed the flashing charge light (like when it's really low) for maybe a minute then it stop lighting up at all. Sometimes if i leave it unplugged for a bit and plug it back in it will flash the light again. That's about all I'm getting out of it now.
I'm thinking something failed internally. It happened while it was on and I was using it so there's no possibility that it was from a flash or anything like that.
Took my phone to the sprint store. The tech wasn't sure either but he thought it might be the screen that died. The vibrating could be the phone trying to boot then realizing there's no screen. They took it apart to check for moisture/damage and said I'm good to go for the $50 replacement.
So my new Evo will be here Tuesday.
BiNiaRiS said:
Took my phone to the sprint store. The tech wasn't sure either but he thought it might be the screen that died. The vibrating could be the phone trying to boot then realizing there's no screen. They took it apart to check for moisture/damage and said I'm good to go for the $50 replacement.
So my new Evo will be here Tuesday.
Click to expand...
Click to collapse
did you resolved it i'm having same had same issue as you mine is htc sensation but think is the same thing ive replacet the digitizer some day ago and it was working very good untill it start to vibrate and than died, now it flashes an orange light when i try to charge and after a while stops but i cant power it on nothing hapens when i press power button
Did you resolve the issue?
Did you ever resolve this issue? My Evo LTE started doing the exact same thing this evening and all of the Sprint stores are closed until tomorrow. I figure it's something internal that died and I can't see what it's trying to do... I guess you just got the replacement and didn't ever get it resolved with that particular phone?
BiNiaRiS said:
I'm completely at a loss here. I was running a 4.3 rom for the past week or two with no issues. Pulled my phone out of my pocket 30 min ago, hit the power button and the screen wouldn't light up. I tried it again and still no go. I tried swiping to unlock, even with the black screen and i felt it vibrate.
Ever since then my phone is non responsive. I can't get it to boot, can't hard reset it, nothing. The vibrates stop when I'm holding down power and down volume but that's about it. I timed the constant vibrates and they happen every 34 seconds according to the Win8 clock (which i've heard in inaccurate).
I'm gonna let the battery drain and hope that it will boot back up after it dies...but until then, any ideas?
Click to expand...
Click to collapse