so i tried to flash a rom yesterday and it went in a bootloop. I've been flashing roms for a while now and i've never encountered this even though i have dealt with bootloops before. The big problem my power button doesn't work and i manage to hold the volume buttons to get to that white screen with the options on it but when i get there the freakin volume buttons dont work at all. I have absolutely no idea how to fix and i NEED it fixed ASAP. Can anyone help me out with this? There's like no one in the world with this same problem apparently...
Related
Hi guys, its been doing this a lot now, till the point it stopped working at once, now my down volume button is not working, no matter how hard i press it, its probably a hard ware problem, but anyone knows how to fix it?
i dont think its a hard ware problem
rohithksaj said:
i dont think its a hard ware problem
Click to expand...
Click to collapse
Hey! Ive made some research and i think its a common problem on DHD, i mean i have to really push it so hard to work , im sure its hardware, i just cant give my DHD for warranty as its over, so i was looking if anyone knows how i can actually fix this thing :S
I'm not allowed to post links cuz i'm new..
but if you search google you can easily find a new volume button for your DHD.
dhd volume button
I just ordered new DHD volume button on htcrepairparts.com for 9.9USD. I will take photos when it arrives.
Any idea on how to install it? I couldnt find instructions on the web.
i have the same problem with the volume up button. It could be hardware.. since it has problems in recovery too. It's working tho.. but VERY HARD to press.
I think there is a video on YouTube to how disassemble desire hd . Plz use it and see of u can fix the buttons . Ill be waiting later
Sent from my Desire HD using XDA Premium App
fearkillerr said:
Hi guys, its been doing this a lot now, till the point it stopped working at once, now my down volume button is not working, no matter how hard i press it, its probably a hard ware problem, but anyone knows how to fix it?
Click to expand...
Click to collapse
i had exactly the same problem but somehow solved. it is not purely a hardware problem. i figured out that, there is a connection between proximity sensor and vol. buttons. its something about proximity sensor but i can't really tell you, i couldn't understand the reason exactly, maybe a driver issue. if you are using custom rom, try formatting(not wiping, full format) cache-system-data, wipe dalvik cache and install a stock rom(or cwm backup). then install custom rom again.
also you can try tapping proximity sensor while your button is not working. mine started to work after tapping several times(than broke again of course). after that experiment, i thought proximity sensor is somehow blocks vol buttons.
I was updating roms and doing my usual fiddling when i noticed that my power button was starting to give me issues. I noticed it specifically after updating CWM from 6.0.3.1 to 6.0.4.3 (i think, from memory).
Now it will randomly flick on and off, bring up the pewer menu and even shut itself down without me touching it. It seems t be overly sensitive and not very sensitive at the same time.
Any hope this can be a software issue and not a hardware one? I've dont lots of searching but i havent found anything more than the possibility of it being a broken power button.
Any help would be greatly appreciated. I wanted to keep this phone till the S5, but i may be forced to go to the S4 or note 3 if theres no way to fix it....
aussie88 said:
I was updating roms and doing my usual fiddling when i noticed that my power button was starting to give me issues. I noticed it specifically after updating CWM from 6.0.3.1 to 6.0.4.3 (i think, from memory).
Now it will randomly flick on and off, bring up the pewer menu and even shut itself down without me touching it. It seems t be overly sensitive and not very sensitive at the same time.
Any hope this can be a software issue and not a hardware one? I've dont lots of searching but i havent found anything more than the possibility of it being a broken power button.
Any help would be greatly appreciated. I wanted to keep this phone till the S5, but i may be forced to go to the S4 or note 3 if theres no way to fix it....
Click to expand...
Click to collapse
The constant use of the power button damaged it. Its a hardware problem. Get it repaired.
I am wondering if anyone ever encountered these kind of problems,
First of all i've been running cm10.2rc for the past month or so and was having no problem whatsoever. Then out of the blue last night, my screen started flicking on and off, then it'd reboot off for no reason. It goes into apps of widget for no apparent reason either. Even in recovery mode (recovery touch) it clicks options without me touching anything.
I've flashed a dirty/clean, Cm11 (don't like it came back to cm10).
It's as if my power button gets stuck.
I'm wondering if this is a common hardware issue that i could solve by changing a part myself off ebay or any kind of solution for this insane phone?
Thanks
I was hoping someone might be able to help me. I had the Gnex power button issue, so I disassembled and successfully repaired it. Unfortunately during a flash my battery fell out and now it shuts down 3 secs after boot (nothing after Google logo). I can't get into recovery/download mode, so I tried an omap flash which ran successfully but still the same problem. I got 300k worth of resistors and have been trying to make a jig but so far I'm unsuccessful.
Does anyone have any extra advice?
Thanks!
discussed bonknot
I'm desperate! 1 year free web hosting whoever helps me solve my issue!
you can't get into bootloader mode??(power and BOTH volume keys)
ashclepdia said:
you can't get into bootloader mode??(power and BOTH volume keys)
Click to expand...
Click to collapse
Nope! I'm wondering maybe if perhaps the volume buttons have the same issue that the power button did?
I was using volume wake after my power button failure. Now I can only boot with a battery pull. I'm thinking my only choice now is to buy a broken gnex and replace the screen - but it would really be nice to get this device working somehow!
When I boot I get the Google/lock screen - but yeah, insata shutdown after that point. I'm thinking maybe the bad flash overwrote the OS?
Any advice is greatly appreciated, if I can avoid buying a new phone that'd be optimal - I've only had this one for two months.
Hey there guys , I've been searching through the forum topics about my issue but so far I've found nothing close to my scenario.
A few months ago I bought my first HTC phone (M8). Its a great device for sure , despite the fact that I had to return it back twice.
First time it was a faulty microphone , so they sent me back a brand new device. Great isn't it ?
However recently I've noticed a few .... let me call them 'glitches' .
Let me give you some details on what I've experienced with the device:
Despite the issues that i'm going through ... the phone works great, but...
Sometimes the screen wont turn on when I'm receiving incoming calls (same goes for the alarm clock) but the phone is able to recognize touches - i've managed to pick up the call when I swiped the screen in the area where the "green" answer button appears .
The above issue doesnt happen so often but the thing that bothers me is the unlocking issue.
At first I thought that it was stuck or faulty power button.
When the phone is idle for some time and I pick it up and press the unlock button ... nothing seems to happen I've tried pressing it hard ... i've tried pressing it gently ... i've tried pressing it multiple times until the screen wakes up .
Same goes for motion launch unlocking .
When I use motion launch to unlock it the phone only gives me a vibration feedback ... and thats it until I try harder to bring the screen back to ''life'' .
(I can also press my security pattern buttons while the screen is dead and feel the phone vibrating , BUT NOT ALWAYS , sometimes is just .. dead )
I already sent the phone back describing the same problems and they just flashed the firmware , which did not fix any of the issues.
Stock Rom android 5.0.1 , not rooted
Soo what do you guys think? What can I do next .. is it android bug or a faulty unit ?
is it possible to be a sensor problem (proximity , accelerometer)
Already tried factory reset and dalvik cache wipe.
Any advice would be useful.
Thanks for taking your time .
Cheerz
I have the same issue. There are times it takes me hitting the power button 20 times for it to finally light up but I can press buttons with it black. The weird thing is it does it on every single ROM but I havent noticed it on Stock...maybe I'm not using stock enough to see. I'll probably throw stock on there today and take it into sprint and let them replace it.
I have the same problem whether it's on stock or custom ROM (KK or L). I am pretty sure this is a hardware problem. Unfortunately, my m8 is out of warranty so HTC won't fix it for free. I read it some where that it could be a faulty proximity switch so shining a light beam to the top part of the phone may wake up the screen. I haven't tried it yet because every time it happens, I don't have a flash light handy. It is an annoying problem to say the least.
When this happens, I pushed the power button, the volume up button, and swiping the screens. Eventually the screen would wake up and every thing works fine... until the next time.
Its a ****ing pain in the ass.
however none of the sensor reading apps report a faulty/stuck sensor.
the wors thing... I've already sent my phone for repair, describing the problems in details. .. and it took them a whole f*cking month to bring it back to me with no results.
I don't think they will replace it because its a problem that takes time to be experienced...and no one is going to wait for it to happen. ...
Any other ideas?
Should I wait for android 6.0 or should I try a custom rom too see if these problems presist.
Fml I love the phone but this is frustrating.
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Ozger said:
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Click to expand...
Click to collapse
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Soulink said:
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Click to expand...
Click to collapse
I think it IS hardware related. I was able to return that one and got another M8. No problems at all.