Related
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
efan3719 said:
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
Click to expand...
Click to collapse
I had a similar situation where I was toggling my nexus 4s brightness settings and when you have it at the darkest setting it is pitch black. Like there's no light on at all. I just had to hit the spot that I did before and bring the light settings back up. So maybe you can boot it up unlock it on the blank screen and two finger pull down and try pressing the light toggle?
apollohay said:
I had a similar situation where I was toggling my nexus 4s brightness settings and when you have it at the darkest setting it is pitch black. Like there's no light on at all. I just had to hit the spot that I did before and bring the light settings back up. So maybe you can boot it up unlock it on the blank screen and two finger pull down and try pressing the light toggle?
Click to expand...
Click to collapse
it was at ten percent brightness and the screen was completely unresponsive as far as i could tell. doing the power + volume up press made it reboot and return to normal.
efan3719 said:
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
Click to expand...
Click to collapse
Mine did that once too. Exact same thing happened. I was starting to get the feeling in my stomach where my phone had just died and then I hit a random set of buttons and saw the Google logo appear. Must be a software bug.
kingwaffle said:
Mine did that once too. Exact same thing happened. I was starting to get the feeling in my stomach where my phone had just died and then I hit a random set of buttons and saw the Google logo appear. Must be a software bug.
Click to expand...
Click to collapse
exactly the same here. felt like i had dropped a baby on it's head haha. i wish i knew a way to figure out what caused it.
My wife and I have been having the same issue, and I'm surprised that there's not more reports of this behavior The worst part is that I use my phone as an alarm, and the alarm won't go off if this happens in the night.
It has happened to me 3 times now, and 2 times in one day for my wife. Holding down the power button for ~20 seconds will cause the reboot, which is the good news. This morning after holding down the power button I noticed the notification light flashing red.
The phone appears to be still on, because if it happens overnight I will still see the white notification light flashing even though the screen won't turn on.
I had this problem on faux123 kernel on the second day after I got my Nexus 4.
Doesn't encounter it on franco.Kernel...
Sleep of death brozillas! Happens to all android phones. Happened to all my phones listed in my signature. You can reboot the device and you should be good. For the dude that's missing his alarm you should do a factory reset if you are stock or if you have root do not set your min cpu values to less than 3xx MHz.
Sent from my Nexus 4 using xda app-developers app
Same thing happened to me on my N4. Did a hard reboot and it came back on. Has happened at least twice since then, usually after being plugged in.
Sent from my Nexus 10 using XDA Premium HD app
Change chargers, cables. Make sure the charger is 5v 1.2a. Factory reset to stock.
If all that fails, RMA if you can.
Sent from my Nexus 4 using xda
I observed the same issue (going to standby, then cannot switch on within an hour) with my [just bought] Nexus 4 (latest 4.2.2 firmware OTA updated, nothing special in setup, second day of use).
Certainly must be difficult to say if it's hardware of software (that is, JB/drivers, since I cannot see how such issue can be caused by any virtual machine application) and when/if the latter will be fixed. I have another such great device already -- ASUS TF700 transformer, with similar "everything works, just reboots occasionally", which I think is enough for me
As with the ASUS Transformer case, I have trouble understanding: if it's the issue with all devices/firmware, although not too frequent -- then why everybody does not complain/return the units massively: the phone is pretty unusable if it cannot be relied upon. If it's just some isolated cases with particular units -- then what happened to QA/testing at LG...
So I guess I am going to return it while I can.
Too bad, good model otherwise, will have to see other phones or wait/observe.
My point is, I understand: fairly new device, can have quite a few faults to be fixed later -- now everybody seem to work that way, for better or worse.
It can have more or less beautiful (or ugly) designs, more or less features, larger or smaller batteries/working time; it can have problems with data connectivity, it can have better or worse browser (or the lack thereof completely). I'm fine with the lack of text reflow in Chrome although that was surprising.
One thing a phone/communicator/PDA absolutely cannot do, provided its battery is not empty, is going into "sleep of death"-like states -- it just cannot serve its purpose then, I cannot see how people sell it at all...
I have had a similar issue before, but i have experienced it when my phone has been through one of 2 sets of scenarios.
1 - It gets really warm and the screen becomes unresponsive, dead if you will. The hard reboot fixes this.
2 - When the signal to my phone is sporadic. An example of this would be my recent trip to London. I was on the underground quite a lot, and I'd lose signal quite often whilst travelling. On a couple of occasions i had to reboot my phone the hard way to get it going again.
Hope this helps?
In my case the device was lying near me on the sofa, the time between its going to standby and my attempt to switch it on was something within 1 hour. Nothing especially intensive had been done before.
BTW, while the phone was in that state, trying to call it resulted in long tones, i.e., apparently the radio/cell was online.
Hope this will help somebody, I returned mine.
Good evening. First post but long time lurker. My N4 is unrooted and on 4.2.2. I'm troubled with this as well especially so when the alarm doesn't ring in the morning after it's crashed overnight and I'm late for work!
Not sure if this is relevant though. I don't listen to music frequently on my N4 but the 3 times it had crashed overnight I had been listening to music before going to bed. Twice using Google music being streamed via my home wifi and once using poweramp with music on internal memory. I remember on 2 occasions the phone feeling rather hot as I was plugging the charger in as I was about to turn in.
I suspect there's a process that's causing the the phone to overload/ overheat and then switch off as a result. Because it's plugged in, it'll just continue to charge overnight and present you with a 100% battery in the morning once you've got it to reset again.
I have also found that doing a soft reset before going to bed prevents this from happening.
Just my observations.
Hi all, I got my Nexus 4 a week ago to replace a broken HTC One X (The cost of repairs was almost equal to the cost of a new Nexus 4). Since I got it, SoD happened twice, both times when I left it to charge overnight. The weird thing is that I have this LED application that blinks the notification light when charging with screen off. When I unplugged the phone, the LED was still blinking as if charging, so the phone is definitely not dead. I will try to set it to day-dream while charging and see if it helps. If it does, it might be considered a way of Google encouraging developers (like myself) to create more daydream apps .
Good morning from beyond the pond,
had the same thing happening as described in the first post solution (pressing POWER+VOL UP) helped to reboot my device.
Only thing that was showing was the led, flashing a blueish white light.
Now runs again on rasbeanjelly. Thanks to OP.
EDIT: since this happened the first time, I thought about what I had altered in my setup.
Only thing that was new was "Greenify". Maybe it sent the APEX launcher into standby?!
Having same problem on my 1 week older n4, my friend having the same problem . only thing in commune we have is the WHATSAPP app that once the phone restart it give a notification that the phone date is wrong,once I look at the date settings yes it is wrong, it says 1970 ,so I have to reset it. It does it every time the problem happens ,can this be a clue???
Sent from my Nexus 7 using xda app-developers app
guinnes.s said:
it says 1970
Click to expand...
Click to collapse
UNIX equivalent of Pol Pot's year zero
I'm having similar problems.
The first time I believe it was just an issue of slight overheating. I turned off the screen but left Google Maps running & put it in my bag. It didn't actually turn off, but the screen didn't want to come on when I took it out later. I did notice it was hot, and after it cooled for a couple mins, it worked fine again. I haven't done this again, and so far, so good.
However, now, on occasion the phone won't respond to the power button. I've never had to actually do a reset - it will eventually decide to work after a couple of presses.. but when it does, it will be slow to come on. The screen will be backlit (but black) for a few seconds, then it will load and respond as normal.
Since the light comes on prior to the screen, it seems like a software rather than hardware issue to me. If the screen was damaged, I don't think it would act that way. I don't know phones, but that's my intuition. I'm going to try and remember to turn it off on occasion and see if that helps. I don't think it's been reset since the last push update.
(I'm rooted, but stock)
Just bricked my phone. Non-responsive except for capacitative home and back flashing, no charge light nothing.
Option 1) Hold Volume Up & Down, then hold power for 90 seconds. Should vibrate/flash/respond somehow. Sometimes takes some time and a few tries with long waits in between.
Option 2) Hold phone up to bright light (headlight or lamp bulb) and hold power for 15 seconds. Orange charge light will illuminate. Play with power & volume buttons till it boots.
Option 3) If plugged in on USB because you were working in Fastboot, (optional: wait 30 seconds to ensure whatever is going is complete so you don't ACTUALLY brick it), then unplug USB: reboots.
Option 2 resurrected my phone right before I was about to give up. Hope this helps some of you!
Option 3 resurrected my phone the next time.
Did not expect Option 2 to work, but it was the only one working in the end (accidentally flashed a Sprint zip).
Thanks!
Amazing trick
Thanks a million times!
Incredibly for me, the light-bulb-and-play-with-buttons trick worked for me straight away.
Just incredible!
(I might be too noob, but what's the hidden logic for it?)
Thanks again !!
Thanks a million mate, it worked like a charm. God Bless you !!
RDshift said:
Just bricked my phone. Non-responsive except for capacitative home and back flashing, no charge light nothing.
Option 1) Hold Volume Up & Down, then hold power for 90 seconds. Should vibrate/flash/respond somehow. Sometimes takes some time and a few tries with long waits in between.
Option 2) Hold phone up to bright light (headlight or lamp bulb) and hold power for 15 seconds. Orange charge light will illuminate. Play with power & volume buttons till it boots.
Option 3) If plugged in on USB because you were working in Fastboot, (optional: wait 30 seconds to ensure whatever is going is complete so you don't ACTUALLY brick it), then unplug USB: reboots.
Option 2 resurrected my phone right before I was about to give up. Hope this helps some of you!
Option 3 resurrected my phone the next time.
Click to expand...
Click to collapse
These are only soft bricks
Bricks!
MacHackz said:
These are only soft bricks
Click to expand...
Click to collapse
Yep. A real hard brick is a brick. Make a "I dragged my phone behind my car and this is how little it got beat up in my Otterbox" video.
himhz said:
Incredibly for me, the light-bulb-and-play-with-buttons trick worked for me straight away. what's the hidden logic for it?
Click to expand...
Click to collapse
It apparently has something to do with resetting input awareness. Either there's a photodiode that picks up on light levels, or the IR diode detects the heat from the bulb. Thus, when the phone's diode is fully activated, it apparently activates that reset. I haven't heard from anyone, but I strongly suspect if the battery were completely drained somehow, then it might allow you to charge it and turn it back on regularly. Otherwise, the option 2 bypass should still work even on a dead battery refusing to charge till it resets, since it may current from light/heat. I'm also curious to find if anyone can tell if the handset is actually still accepting a charge despite the lack of LED activity while its in the soft-bricked state, or if the charging circuitry refuses to allow current to pass to the battery. HTC? HTC?
Thumbs ups appreciated!
See you all at XDA: DevCon
RDshift said:
Yep. A real hard brick is a brick. Make a "I dragged my phone behind my car and this is how little it got beat up in my Otterbox" video.
See you all at XDA: DevCon
Click to expand...
Click to collapse
A real brick is when hboot is not accessible no matter what you do, and there is no sign of life.
Don't get sarcastic
Matt said:
A real brick is when hboot is not accessible no matter what you do, and there is no sign of life.
Don't get sarcastic
Click to expand...
Click to collapse
I've tried the two steps from above and my phone still just flashes the Back and Home lights when I hold down power.
I was running a cyanogen nightly (from maybe 3 weeks ago) when the phone shut off randomly (not dead battery) and wouldn't turn back on.
When plugged in via usb the device shows up in the eject devices system tray but "fastboot devices" lists no devices. I have the phone plugged into a rear usb2.0 port.
Starting to get nervous...not sure what my options are.
EDIT: Holy smokes option two worked after a third try. That's so wild. Thank you!
XeoNiCaLiTy said:
Did not expect Option 2 to work, but it was the only one working in the end (accidentally flashed a Sprint zip).
Thanks!
Click to expand...
Click to collapse
WOW after an hour of trying to fix the issue option number 2 worked for me lol i can't believe it. sounds so ridiculous
None of the options worked for me... Please help!
My HTC One shutdown and now I can't turn it back up.
Hardware is in flawless condition.
I tried all combinations and options and still my phone is dead.
I know it's not the hardware problem. Checked voltage regulator, phone is charging, voltage and amps are ok. Logic board is in excellent condition, checked with microscope and multimeter.
Was used regularly and one day just turned off by itself.
Also I haven't messed around software because I don't have need for that kind of work.
Again please help me, I'm pretty desperate.
dude!
RDshift said:
Just bricked my phone. Non-responsive except for capacitative home and back flashing, no charge light nothing.
Option 1) Hold Volume Up & Down, then hold power for 90 seconds. Should vibrate/flash/respond somehow. Sometimes takes some time and a few tries with long waits in between.
Option 2) Hold phone up to bright light (headlight or lamp bulb) and hold power for 15 seconds. Orange charge light will illuminate. Play with power & volume buttons till it boots.
Option 3) If plugged in on USB because you were working in Fastboot, (optional: wait 30 seconds to ensure whatever is going is complete so you don't ACTUALLY brick it), then unplug USB: reboots.
Option 2 resurrected my phone right before I was about to give up. Hope this helps some of you!
Option 3 resurrected my phone the next time.
Click to expand...
Click to collapse
Option 2 did the trick for me!you'r a life saver mate!kudos
My is stuck in a reboot loop. It was running GPE which cause the sim unlock code not to stick. One person told me that I need to go back to stock so I tried to flash the stock RUU and now stuck in reboot loop.
Neither method work for me! I can get into fastboot screen but can't flash anything. Having a hard time trying to install adb driver though
HOLY BEJEEZUS!! I just tried your option 2! I thought i just bricked this thing, and i need to return it for the warranty exchange in a few days. Holy cow thank you!!!! I had the capacitive lights blinking and the red charging light on. Coudln't run commands. Held it up to a CFL bulb, played with the power and volume buttons and BAM!! Booted back up. Thanks tons!! Phew!!!
Now to get rid of the frigging tampered stamp in fastboot. Can't get rid of it for the life of me. Tried using just Revone, Tried the All in One toolkit. Nothing. Thanks again.
whitetiger_0603 said:
HOLY BEJEEZUS!! I just tried your option 2! I thought i just bricked this thing, and i need to return it for the warranty exchange in a few days. Holy cow thank you!!!! I had the capacitive lights blinking and the red charging light on. Coudln't run commands. Held it up to a CFL bulb, played with the power and volume buttons and BAM!! Booted back up. Thanks tons!! Phew!!!
Now to get rid of the frigging tampered stamp in fastboot. Can't get rid of it for the life of me. Tried using just Revone, Tried the All in One toolkit. Nothing. Thanks again.
Click to expand...
Click to collapse
Are you S-Off? if yes, you can either use adb commands (if your comfy with that): http://forum.xda-developers.com/showthread.php?t=2477792
or just use this tool: http://www.htc1guru.com/guides/guru-bootloader-reset/
RDshift said:
Just bricked my phone. Non-responsive except for capacitative home and back flashing, no charge light nothing.
Option 1) Hold Volume Up & Down, then hold power for 90 seconds. Should vibrate/flash/respond somehow. Sometimes takes some time and a few tries with long waits in between.
Option 2) Hold phone up to bright light (headlight or lamp bulb) and hold power for 15 seconds. Orange charge light will illuminate. Play with power & volume buttons till it boots.
Option 3) If plugged in on USB because you were working in Fastboot, (optional: wait 30 seconds to ensure whatever is going is complete so you don't ACTUALLY brick it), then unplug USB: reboots.
Option 2 resurrected my phone right before I was about to give up. Hope this helps some of you!
Option 3 resurrected my phone the next time.
Click to expand...
Click to collapse
Unfortunately, neither of these options worked for me. My phone is completely unresponsive with no charge light, no reaction to light, no USB recognition, no hard reset functionality, inability to access bootloader or anything for that matter.
I am uncertain as to what the problem is, but the phone had <40% charge when it failed. Are there any other alternatives?
[pending update(s)]
THANK YOU!!!!
Dude thank you so much, I just formatted my internal storage using the new TWRP 2.7 and for some reason I had a black screen with only the red light on. After a few minutes of failure, not being able to boot up to both recovery and bootloader, I tried OPTION 2, which saved my phone.
THANK YOU SO MUCH!
No OS Installed.
Hi guys. I was flashing ARHD Rom and it was suddenly failed. Now I stuck at recovery mode, twrp 2.6.3.3. I forgot to do back up. and I did some factory reset and now that's how I stuck at the recovery mode. So yeah. I need help. Thanks.
Thanks a ton
Option 2nd worked... i installed insertcoin 2.1.4 and it happened.
flashed back to renovate.
once again thanks mate. cheers
Crazy way to unbrick M7
XeoNiCaLiTy said:
Did not expect Option 2 to work, but it was the only one working in the end (accidentally flashed a Sprint zip).
Thanks!
Click to expand...
Click to collapse
Sounds like urban legend, but i tried everything else. Worked right quick.
BTW, my soft brick came from just trying out droidwall blocking a puzzle game. App must have crashed badly.
No OS Fix
heyAmirulS said:
Hi guys. I was flashing ARHD Rom and it was suddenly failed. Now I stuck at recovery mode, twrp 2.6.3.3. I forgot to do back up. and I did some factory reset and now that's how I stuck at the recovery mode. So yeah. I need help. Thanks.
Click to expand...
Click to collapse
Try sending a rom using adb, then flashing to that rom. That's what I had to do when I had no OS installed on my Kindle Fire.
I upgraded to an HTC One a month ago in T-Mobile and now randomly the phone won't turn on. The phone is rooted, unlocked, custom recovery, and has the Android Revolution ROM. I installed everything the first week I got it and it has been working perfectly fine (No freezes, battery discharging has a good rate) and everything works (Wifi, 4G LTE, Bluetooth). The phone has not been dropped, water damaged, or exposed to any excessive heat, so it should not be having problems.
Yesterday (9/14/13), I was using the phone just fine around 8PM with my friends in a restaurant and everything seemed fine. A few hours later when I was walking down the street, I take my phone out of my pocket and when I hit the power to wake up the phone nothing happened. I pressed the power button for 10-20 seconds and nothing.
When I got back to my room and plugged it in, the LED did not turn on or anything and when I pressed the power button again after being plugged in, nothing happened. I charged it all night and decided to work with it today, but nothing has helped. I have tried holding the power button and volume keys for minutes, holding power button and nothing. When I plug in the phone to the PC it detects it (Windows USB sound in) and when I press the power button for around 15 seconds it makes the sounds but then it makes the removed usb sound.
Since the phone is Rooted, unlocked and has custom recovery and rom, I'm not sure warranty would help, ALTHOUGH since it doesn't turn on and physically is not tampered with, they could get it to at least turn on.
Please help me out here as I am a college student and really need my phone for work and to stay in touch with my parents. Thank you, and I apologize if I didn't follow a posting guideline.
P.S. One of the causes could be a drained battery, but the charging all night should have helped.
terrypro said:
I upgraded to an HTC One a month ago in T-Mobile and now randomly the phone won't turn on. The phone is rooted, unlocked, custom recovery, and has the Android Revolution ROM. I installed everything the first week I got it and it has been working perfectly fine (No freezes, battery discharging has a good rate) and everything works (Wifi, 4G LTE, Bluetooth). The phone has not been dropped, water damaged, or exposed to any excessive heat, so it should not be having problems.
Yesterday (9/14/13), I was using the phone just fine around 8PM with my friends in a restaurant and everything seemed fine. A few hours later when I was walking down the street, I take my phone out of my pocket and when I hit the power to wake up the phone nothing happened. I pressed the power button for 10-20 seconds and nothing.
When I got back to my room and plugged it in, the LED did not turn on or anything and when I pressed the power button again after being plugged in, nothing happened. I charged it all night and decided to work with it today, but nothing has helped. I have tried holding the power button and volume keys for minutes, holding power button and nothing. When I plug in the phone to the PC it detects it (Windows USB sound in) and when I press the power button for around 15 seconds it makes the sounds but then it makes the removed usb sound.
Since the phone is Rooted, unlocked and has custom recovery and rom, I'm not sure warranty would help, ALTHOUGH since it doesn't turn on and physically is not tampered with, they could get it to at least turn on.
Please help me out here as I am a college student and really need my phone for work and to stay in touch with my parents. Thank you, and I apologize if I didn't follow a posting guideline.
P.S. One of the causes could be a drained battery, but the charging all night should have helped.
Click to expand...
Click to collapse
Try holding the power button and volume down buttons down, while holding the proximity sensor directly under a very bright light...
This actually happened to me on my first HTC one I couldn't get it to do anything I ended up sending it to HTC I knew they would deny my warranty claim because of the bootloader and ROM but I knew they would have to turn it on yo figure it out. They called me to tell me that it was not covered and said it would cost 215 to put it back to regular I denied and paid the $35 diagnostic fee when I got it back I booted straight into fastboot and flashed my backup.problem solved
Sent from my HTC One using xda app-developers app
---------- Post added at 10:57 PM ---------- Previous post was at 10:55 PM ----------
I figured it happened because I was s-on and had the stock Cid and flashed the GE ROM
Sent from my HTC One using xda app-developers app
offwiththeface said:
This actually happened to me on my first HTC one I couldn't get it to do anything I ended up sending it to HTC I knew they would deny my warranty claim because of the bootloader and ROM but I knew they would have to turn it on yo figure it out. They called me to tell me that it was not covered and said it would cost 215 to put it back to regular I denied and paid the $35 diagnostic fee when I got it back I booted straight into fastboot and flashed my backup.problem solved
Sent from my HTC One using xda app-developers app
---------- Post added at 10:57 PM ---------- Previous post was at 10:55 PM ----------
I figured it happened because I was s-on and had the stock Cid and flashed the GE ROM
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
This actually sounds like a great, thanks , but before sending it out I think I would like to try other solutions since it would suck to not have my phone for 2-3 weeks. Also, how long did the whole process take for you? (Sending it out, "repair", and getting it back)
This happens to a guy in another thread. He fixed it by leaving it in the wall charge until the red LED turned on, it took 4 days on the charge.
Hey it actually only took about 1week take it back to your carrier have them send it for you. I also heard about leaving it on the charger for a long time I tried over night and it didn't work the next thing I did was send it to "repair" but if you have the patience leave it on change for a few days first
Sent from my HTC One using xda app-developers app
dgtiii said:
Try holding the power button and volume down buttons down, while holding the proximity sensor directly under a very bright light...
Click to expand...
Click to collapse
I also had this issue with Never Rooted HTC One.. To my surprise, shining a bright light at the sensor while powering on did actually work!
xJuicex said:
I also had this issue with Never Rooted HTC One.. To my surprise, shining a bright light at the sensor while powering on did actually work!
Click to expand...
Click to collapse
I thought i was going to fall for a troll with this but wow it actually does work... I don't even know what to say right now... other then thanks dgtiii and xJuicex
EDIT oh and why does this work?
dgtiii said:
Try holding the power button and volume down buttons down, while holding the proximity sensor directly under a very bright light...
Click to expand...
Click to collapse
I have a Verizon HTC One exhibiting the exact same symptoms. The battery went dead after a long day and it will not turn on or charge. I have held the proximity sensor in bright light while powering on and while holding both vol up and power. Neither seemed to change the problem. How bright of a light are we talking? Thanks in advance. I am also curious why this works....
Maby i can help^^
terrypro said:
I upgraded to an HTC One a month ago in T-Mobile and now randomly the phone won't turn on. The phone is rooted, unlocked, custom recovery, and has the Android Revolution ROM. I installed everything the first week I got it and it has been working perfectly fine (No freezes, battery discharging has a good rate) and everything works (Wifi, 4G LTE, Bluetooth). The phone has not been dropped, water damaged, or exposed to any excessive heat, so it should not be having problems.
Yesterday (9/14/13), I was using the phone just fine around 8PM with my friends in a restaurant and everything seemed fine. A few hours later when I was walking down the street, I take my phone out of my pocket and when I hit the power to wake up the phone nothing happened. I pressed the power button for 10-20 seconds and nothing.
When I got back to my room and plugged it in, the LED did not turn on or anything and when I pressed the power button again after being plugged in, nothing happened. I charged it all night and decided to work with it today, but nothing has helped. I have tried holding the power button and volume keys for minutes, holding power button and nothing. When I plug in the phone to the PC it detects it (Windows USB sound in) and when I press the power button for around 15 seconds it makes the sounds but then it makes the removed usb sound.
Since the phone is Rooted, unlocked and has custom recovery and rom, I'm not sure warranty would help, ALTHOUGH since it doesn't turn on and physically is not tampered with, they could get it to at least turn on.
Please help me out here as I am a college student and really need my phone for work and to stay in touch with my parents. Thank you, and I apologize if I didn't follow a posting guideline.
P.S. One of the causes could be a drained battery, but the charging all night should have helped.
Click to expand...
Click to collapse
I lost my phone in the water today and it worked well until i got home! then my htc one started to blink the back and home button, then it just turned off by it self! i tryed very thing!! holding the power button, power button and vol down, directt light to the proximity sensor and power button and vol down but it didnt work....
Then i tryed to connect it to my computer and pressed the power button, the mobile turned on but it failed a cupple of times!! tryed a cupple of times and then suddently everything worked fine!!! ( done **** up the power button, i pressed it so hard and many times i have to press hard to turn the phone on and of-.-) anywayes TRY CONNECTING TO COMPUTER!!
Other small thing i did - took the sim card out and in again..... Thanks for reading.! sry for the bad english^^
this is a **** painfull thing since i got my phone just jet! and i got alot off stuff in it, so i hope it helped!!
xJuicex said:
I also had this issue with Never Rooted HTC One.. To my surprise, shining a bright light at the sensor while powering on did actually work!
Click to expand...
Click to collapse
Another +1 for bright light power button + vol down
Unrooted HTC one on ATT
ryan00793 said:
I thought i was going to fall for a troll with this but wow it actually does work... I don't even know what to say right now... other then thanks dgtiii and xJuicex
EDIT oh and why does this work?
Click to expand...
Click to collapse
Its so that if the phone is in your pocket it won't start up as the proximity sensor detects the phone is in your pocket so tells it not to start up. Sometimes the sensor doesn't work as it should and needs a really intense light to overwhelm the sensor and let the phone start up.
Bobbie
Put it under a desk lamp!
I had the same exact problem. My phone couldn't turn on after it reached 0% and there was no orange light when charging. I put the phone right under my desk lamp and held the power button for 15 seconds and it turned on. Thought people were just trolling... The battery was at 1% when it turned on. I already left the phone in wall charge overnight. Guess it was not charging very well. Thanks for coming up with this solution!
It worked!!!
WOW The light over the sensor worked for me too!! I'm glad I came to this forum first!!:laugh::laugh:
Doesn't work for me
This REALLY sucks I just got this HTC One used and I was using it all yesterday and this morning with no problems. Then all of a sudden a couple hours ago it just shut down - I was just browsing the web, so it wouldn't have overheated.
Now, it won't charge (the LED doesn't come on) although it was at about 50% when it shut down. I can't get into the bootloader or recovery, and ADB doesn't recognize that it's plugged in (despite Windows playing the little jingle indicated it's been connected).
Ever since then I've been scrounging the web for answers, What exactly have you guys done for this light trick to work? Because I've held it under a bright LED and under a desk lamp with a 13W CFL bulb, while holding power + volume down, but haven't had any luck.
How long have you guys held them down for?
I haven't even seen the capactive buttons light up (although it's just kinda hard when you're holding it under a light, so maybe they are flashing I just can't see) and the only sign of life from this is the fact that Windows installed Qualcomm drivers and plays the jingle indicating that it's detected a device.
EDIT: Forgot to include, I've been trying to leave it sit charging (one person mentioned their friends' One worked after leaving it charging for 4 days - I'm not sure I can wait that long, but if I have no other option I will).
Also, should I leave the SIM in or would it not matter (personally, I don't see that making any difference whatsoever, but I really don't care at this point)? And should I alternate light/darkness while holding the buttons under a lamp, or just leave it under the light and hold them? (I've tried all of these things, but I'm willing to pursue whatever avenue had the greatest success rate).
inferno7799 said:
This REALLY sucks I just got this HTC One used and I was using it all yesterday and this morning with no problems. Then all of a sudden a couple hours ago it just shut down - I was just browsing the web, so it wouldn't have overheated.
Now, it won't charge (the LED doesn't come on) although it was at about 50% when it shut down. I can't get into the bootloader or recovery, and ADB doesn't recognize that it's plugged in (despite Windows playing the little jingle indicated it's been connected).
Ever since then I've been scrounging the web for answers, What exactly have you guys done for this light trick to work? Because I've held it under a bright LED and under a desk lamp with a 13W CFL bulb, while holding power + volume down, but haven't had any luck.
How long have you guys held them down for?
I haven't even seen the capactive buttons light up (although it's just kinda hard when you're holding it under a light, so maybe they are flashing I just can't see) and the only sign of life from this is the fact that Windows installed Qualcomm drivers and plays the jingle indicating that it's detected a device.
EDIT: Forgot to include, I've been trying to leave it sit charging (one person mentioned their friends' One worked after leaving it charging for 4 days - I'm not sure I can wait that long, but if I have no other option I will).
Also, should I leave the SIM in or would it not matter (personally, I don't see that making any difference whatsoever, but I really don't care at this point)? And should I alternate light/darkness while holding the buttons under a lamp, or just leave it under the light and hold them? (I've tried all of these things, but I'm willing to pursue whatever avenue had the greatest success rate).
Click to expand...
Click to collapse
Go to device manager and connect your phone. What do you see?
Sent from my iPod touch using Tapatalk
n1234d said:
Go to device manager and connect your phone. What do you see?
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
Ya, I tried looking into that before, and there's nothing there. Now I'm trying to find out what/where that Qualcomm driver is that was installed.
EDIT: I DO see it in the Devices/Printers as Qualcomm HS-USB QDLoader 9008 (COM3).
I've also installed HTC Synce Manager, but I'm not sure if that just automatically installed the drivers or if there's something I should do to manually install those.
inferno7799 said:
Ya, I tried looking into that before, and there's nothing there. Now I'm trying to find out what/where that Qualcomm driver is that was installed.
EDIT: I DO see it in the Devices/Printers as Qualcomm HS-USB QDLoader 9008 (COM3).
I've also installed HTC Synce Manager, but I'm not sure if that just automatically installed the drivers or if there's something I should do to manually install those.
Click to expand...
Click to collapse
Sorry to hear that. You are hard bricked, send it to warranty.
Edit: The motherboard is fried and HTC would have to change it. The phone is used so contact the seller and ask him for warranty information.
danielr18 said:
Sorry to hear that. You are hard bricked, send it to warranty.
Edit: The motherboard is fried and HTC would have to change it. The phone is used so contact the seller and ask him for warranty information.
Click to expand...
Click to collapse
Damn. Really? After just using the phone for a day? Today just really isn't my day.
Would there be any other things I could try? Any jigs to force it to boot into bootloader or anything?
inferno7799 said:
Damn. Really? After just using the phone for a day? Today just really isn't my day.
Would there be any other things I could try? Any jigs to force it to boot into bootloader or anything?
Click to expand...
Click to collapse
Well, since you're under warranty, doing anything else just doesn't make sense. And using jtag would require you to open the phone, and trust me, you don't wanna do that to this phone.. Just out of curiosity, what are the first 5 digits of your serial no?
Sent from my HTC One using Tapatalk
Hey guys,
I left my HTC One to charge and when I tried to unlock it, it wouldn't respond. Right now it's a blank screen, the red LED is on even when I unplug the phone, and the hardware buttons are lit. I've tried to restart the phone by holding the power, holding power + volume down, but nothing is working. Device isn't showing up under adb or fastboot devices. What is going on? How can I fix this?
Help me out. Thanks!
-Coby
Edit: Recently this has been happening to my phone frequently, but I am usually able to get it to restart doing the methods said above. This is the first time I can't get it to do anything.
Put it under a stronger light and longpress power + vol-
Try this
I was actually searching through old threads and found that same answer and tried it. I can't believe it worked! Thanks! Why does this happen though? And will this hopefully prevent it from happening later on?
Are you rooted with a custom rom?
However, idk why it happened
Guich said:
Are you rooted with a custom rom?
However, idk why it happened
Click to expand...
Click to collapse
I have 4.3 Google Edition on my phone with TWRP.
I'll remember this trick next time though. Thanks again!
COBYATCH said:
I have 4.3 Google Edition on my phone with TWRP.
I'll remember this trick next time though. Thanks again!
Click to expand...
Click to collapse
:good:
Strange that you had this issue, but :good:
Guich said:
Put it under a stronger light and longpress power + vol-
Try this
Click to expand...
Click to collapse
Why the stronger light? Im confused! :cyclops:
This has worked for me a ton of times too, I guess it must just trigger something with the light sensor the phone has and wakes it up.
TwinAdk said:
Why the stronger light? Im confused! :cyclops:
Click to expand...
Click to collapse
It's a tips
Maybe the light sensor is always on...
Sent from One with Tapa4
It happened to me when i was rooted and used CWM.
It happened everytime i let the battery run down completely.
I havent rooted my replacement yet and when i let it run down, charged it for ten minutes and it booted straight up.
Seems to be an issue with the phone reading the charge state of the safety circuit in the phone. Mere speculation but i havent heard of it happening to anyone who wasnt rooted with custom recovery....
kungfudavie said:
It happened to me when i was rooted and used CWM.
It happened everytime i let the battery run down completely.
I havent rooted my replacement yet and when i let it run down, charged it for ten minutes and it booted straight up.
Seems to be an issue with the phone reading the charge state of the safety circuit in the phone. Mere speculation but i havent heard of it happening to anyone who wasnt rooted with custom recovery....
Click to expand...
Click to collapse
Can you please give me a little bit more details?
I have exact the same issue: The battery ran out completely, then I can't charge it or turn it on.
I have tried
1. with charger connect to outlet, power + vol-
2. with charger connect to PC, power + vol-
3. under desk light, without charger connected, power + vol-
Nothing worked for me.
Some questions:
- Should I connect the cable when I attempt to turn on the phone?
- Is normal desk fluorescent light "bright enough"?
- Should I move the phone under the light first then press the button, or the other way around?
Thank you for your help!
i have the same problem in my htc eye. i tried your solution. but it won't worked for me. phone still on blank screen and red light is on. how can i fix it?????
When going to bed tonight do these steps.
1. Put your phones brightness display on the lowest setting
2. Plug your phone in for an overnight charge, do not "turn off" your phone.
3. Wake up in the morning
4. Click the power button on your HTC ONE M7
Did the screen turn on? Are the Soft Keys the only part that lights up?
I've been able to replicate this problem over and over on 3-4 different HTC ONE M7's. For some reason the phone's display will not turn on in the morning. The only way to get it to is to either hold down the power button for a few seconds and the restart screen will pop-up which activates the screen again. Or, to do a complete restart.
Eventually the screen starts working again like normal after fiddling with it for 15-20 minutes...
I believe this is either a KitKat problem or light sensor problem or both. I do know this issue was never around before the KitKat upgrade months back.
Soul TKR said:
When going to bed tonight do these steps.
1. Put your phones brightness display on the lowest setting
2. Plug your phone in for an overnight charge, do not "turn off" your phone.
3. Wake up in the morning
4. Click the power button on your HTC ONE M7
Did the screen turn on? Are the Soft Keys the only part that lights up?
I've been able to replicate this problem over and over on 3-4 different HTC ONE M7's. For some reason the phone's display will not turn on in the morning. The only way to get it to is to either hold down the power button for a few seconds and the restart screen will pop-up which activates the screen again. Or, to do a complete restart.
Eventually the screen starts working again like normal after fiddling with it for 15-20 minutes...
I believe this is either a KitKat problem or light sensor problem or both. I do know this issue was never around before the KitKat upgrade months back.
Click to expand...
Click to collapse
I#ve never run across that problem but I know when I enable "ScreenOn" the screen stays on all night and if I just let my phone sit with screen on (because I fell asleep texting ) the screen will be off in the morning.
Soul TKR said:
When going to bed tonight do these steps.
1. Put your phones brightness display on the lowest setting
2. Plug your phone in for an overnight charge, do not "turn off" your phone.
3. Wake up in the morning
4. Click the power button on your HTC ONE M7
Did the screen turn on? Are the Soft Keys the only part that lights up?
I've been able to replicate this problem over and over on 3-4 different HTC ONE M7's. For some reason the phone's display will not turn on in the morning. The only way to get it to is to either hold down the power button for a few seconds and the restart screen will pop-up which activates the screen again. Or, to do a complete restart.
Eventually the screen starts working again like normal after fiddling with it for 15-20 minutes...
I believe this is either a KitKat problem or light sensor problem or both. I do know this issue was never around before the KitKat upgrade months back.
Click to expand...
Click to collapse
I can try it out. I'll report in the morning. ?
Sent from my HTC_0P6B using Tapatalk
Anyone?
Nobody?
Sent from my HTC6500LVW using Tapatalk
Beullar.... Beullar?
with my phone its just a 5 second lag sometimes, and i click the power button again to make sure i clicked it and it instead locks itself back. The third click however, everything works fine.
this has been happening to me for the longest its very irritating, i notice it happens whenever i fall asleep, a nap during the day or when i wake up in the morning its really annoying
Well glad to see I'm not the only one.
I have provided this thread link to HTC and reported the problem. Requested that they chime in if they have any questions.
i had that issue
Soul TKR said:
I have provided this thread link to HTC and reported the problem. Requested that they chime in if they have any questions.
Click to expand...
Click to collapse
Yes I had the same issue as the original post.Long story short I ended up sending the device back. The new one didn't suffer from this problem. This was back in October of 2013.
Same issues, it's probably light sensor:
http://forum.xda-developers.com/showpost.php?p=49918380&postcount=9
nitephlight said:
Same issues, it's probably light sensor:
http://forum.xda-developers.com/showpost.php?p=49918380&postcount=9
Click to expand...
Click to collapse
Nope. I already tried the light sensor calibration trick. It didn't work unfortunately. I ended up swapping out 4-5 HTC ONE's before it worked correctly.
yup, I tried the trick as well a few more times and could not wake the screen either. generally I'm tolerant of stuff like this because I assume it is the byproduct of repeated flashing and combo of mods.. but I I recall this happening quite early on in ownership and now it's back. (was AOSP now Sense base). sigh