Related
Hello
My HD2 Worked well for a long time, but now everytime I press the "sleep" key it turns off for half a second then turns back on and proudly displays the lockscreen without me pressing anything. There is no way to turn the screen off and go in standby mode anymore.
Obviously the battery drains so much faster from not being able to have the screen off and this silly problem actually makes the phone unusable
I flashed a few roms using HardSPL and now HSPL2. I'm currently running Artemis 11.0, the problem appeared may days after flashing while using Artemis ROM 9.0. A hard reset seemed to fix it but the problem reappeared. Today flashing 11.0 only solved the problem at first boot.
Anyone had that before? Not sure if it's software/rom related or not anymore. HELP
As far as Ive seen, its only you an me who have had this problem so far.
Honestly, Im relieved to see someone else with this problem.
I had exactly as you described, but using Axlor roms.
It worked fine for 1/2months, then all of a suddon the screen backlight wouldnt go off, but a reset fixed it.
But it got worse and worse.
Now nothing will work...
Ive taken everything back to stock, and i mean EVERYTHING! Not a single app installed.
And I still have this problem. I've tried it all.
I think its a warrenty job....
EDIT:
I also noticed the backlight will go off fine when the phone is charging, is that the same for you?
I just sent the phone off to Tmob today, to see if they can fix/replace it.
I'll keep you informed.
Same problem. Was running fine on stock ROM 1.66 then backlight did not dim and would not go into standby. Put into standby, screen goes off then straight back on to the lock screen. Since then have had other problems at boot, sometimes it locks on HTC white screen needing battery removal, sometimes launches straight into Navipanel and will not exit, HTC sense homescreen sometimes launches in landscape and will not go into normal portrait mode. Reflashed with different ROM's same symptoms persist so have returned to Vodafone UK under warranty, fingers crossed.
i've had this on early versions of the rom i use, the chef fixed it, making me think its the software, not your phone.
I experienced this issue when I minimised a game called virtual pool. Closing it in task manager would then allow me to permanently make the phone sleep.
samsamuel said:
i've had this on early versions of the rom i use, the chef fixed it, making me think its the software, not your phone.
Click to expand...
Click to collapse
How come Ive still got the problem after reflashing several times and taking everything back to exactly as it came from the box?
flannco said:
Same problem. Was running fine on stock ROM 1.66 then backlight did not dim and would not go into standby. Put into standby, screen goes off then straight back on to the lock screen. Since then have had other problems at boot, sometimes it locks on HTC white screen needing battery removal, sometimes launches straight into Navipanel and will not exit, HTC sense homescreen sometimes launches in landscape and will not go into normal portrait mode. Reflashed with different ROM's same symptoms persist so have returned to Vodafone UK under warranty, fingers crossed.
Click to expand...
Click to collapse
I too have had the navi panel problem.
Im praying they fix mine under warrenty
Yes the problem is exactly what you describe, hard reset and flashing to a stock rom doesn t fix it with no programm running in the background
Navipanel seems to be on randomly sometimes so can I guess it could be related.
I found a fix, after starting the phone, plugging and unplugging the usb cable to the phone WHILE THE SCREEN IS ON fixes it but only until the next restart
Considering sending it for warranty now.
Thanks for replies! If anybody knows more let us know
Update re standby problem
Got my phone back from Vodafone UK today. Was advised software corrupted and that they had reflashed and it had been fully tested and was now working fine.
On power up (even without SD card or SIM) it had exactly the same fault as before, when put into sleep mode the screen comes back on after about 1 second.
I tried the plug in and remove USB lead fix and this also works for me until the next restart so it would seem that this must be a hardware problem.
flannco said:
Got my phone back from Vodafone UK today. Was advised software corrupted and that they had reflashed and it had been fully tested and was now working fine.
On power up (even without SD card or SIM) it had exactly the same fault as before, when put into sleep mode the screen comes back on after about 1 second.
I tried the plug in and remove USB lead fix and this also works for me until the next restart so it would seem that this must be a hardware problem.
Click to expand...
Click to collapse
I have a feeling mines going to come back from tmob in the same state i sent it in...
What other options do with have if they sent it back without fixing it?
any info? I still have not had mine back.
bump... any more infos on this?
CrocMonsieur said:
bump... any more infos on this?
Click to expand...
Click to collapse
Ive noticed allot more people getting this problem. So its not only us.
Tmob are replacing mine, so Im guessing its out of our control now.
did any of you guys try performing a task 29 in between flashing roms? it may help
Audio Oblivion said:
did any of you guys try performing a task 29 in between flashing roms? it may help
Click to expand...
Click to collapse
Actually no, I overlooked it.
Probably would have been a good idea
Prehaps thats worth a try Mr Opr
CrocMonsieur said:
I found a fix, after starting the phone, plugging and unplugging the usb cable to the phone WHILE THE SCREEN IS ON fixes it but only until the next restart
Click to expand...
Click to collapse
Thanks for this workaround. Now with the urgency gone hopefully somebody finds a lasting solution without the need of sending it in..
I have same problem guys after 4 months using. ...and my HD2 is unusable with no standby. I mean battery gets weak during 2-3 hours. Whats your guess guys is it software problem. Cause Im afraid of this is hardware prob because after reset goes my device in wrong state.
Help!
Sadly I'm running into this same error with my t-mobile hd2....getting serious power drain...can anyone confirm if the task 29 helped at all? Mine won't stay off for more than 30 seconds.
** Found out the google easy sms beta app I was running had a service which was causing the app to come out of standby...uninstalling this app cured the problem.
For me, it was a sd slot problem. When i removed the sd card, phone always waked up after 0.5 seconds, and card was detected as bad.
Now the SD slot was changed (under guarranty) and it work fine, no wake up if sd slot is empty.
Any update on this? My HD2 starting doing this today as well
And I have no usb cable at work to 'trick' it. The only option is to pull the battery which I don't want to do. This is ridiculous. Am I going to have to hard-reset the damn thing to fix it?
FYI I didn't do *ANYTHING* to my phone in a couple of weeks (no new apps, etc.) and it started doing this out of the blue.
You hit the red 'end call' button and it goes black..then comes right back on.
The odd thing is it *thinks* its plugged in because the only screen setting I can get it to acknoweldge is the 'backlight level when charging'. So somehow my phone thinks its plugged in even though my only usb cable is back home.
Grrr. No registry tweaks or temp files I can delete to reset this behavior?
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
This might be happening because of the WiFi/BT connectivity bug. If you watch the logcat (or maybe it was in kmesg), you'll probably see lots of errors regarding mmc0.
On the other hand, anything that would get the CPU stuck at 100% throughtput, might do the same, and it might be some other bug.
Try to turn off WiFi and BT and do the same, see if it helps any.
Neither are enabled.. Now it is doing this For sure, completely everytime. I can pull battery and boot phone. Seems to run ok, can open apps. go to market. whatever. but when I go into settings I get Activity FC and it freaks out. I just tried to power off my phone. It's been at the Shutting Down spinning circle part for over 15 minutes. Is it possible the build it 512mb went bad and thats why it can't resume from standby, and stuff?
I'm still testing things. but I've completely wiped and had no luck. and also nandroided to a good working version also. Basically if my phone goes to sleep at all. I can't turn it back on. I have to pull battery.
Same thing here..
Screen will not wakeup from sleep unless I do a battery pull... Any updates?
Its been 1 year since nobody posted, anybody came up with an explanation/solution?
This Issue just appeared in my phone after two years of use.
-When the screen goes to sleep it won't be possible to switch it on again. Either via the power button, time up or proximity sensor.
-The phone and the touchscreen work as always, haptic feedback reveals my unlock slider is still active and the phone can recieve calls and notifications.
-Plugging in the phone or using another button won't revive the screen either.
-The backlight of the screen turns on, but the screen remains black.
-Only removing the battery and waiting at least 10 seconds before putting it in again will let the screen to come back.
-Shouldn't be a software problem as i have wiped several times everything that could be wiped and instaled diffrent Roms, even tested ICS.
-In my case, removing the microSD doesn't change anything.
-Swapping batteries also doesn't help.
Anybody out there with the same problem?
Programmed obsolescense on HTC?
http://forum.xda-developers.com/showpost.php?p=22625457&postcount=11
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
anomalyconcept said:
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
Click to expand...
Click to collapse
Format your SD-Card. It's known to fix it.
Thanks for your suggestion, but unfortunately it does not fix my issue.
I've tried different SD cards, repartitioned & formatted the card (previously had a sd-ext partition), and even running it without an SD card- all either won't turn the screen on during boot (starting with the battery out) or will fail to wake the screen.
My logs don't show the mmc0 errors which would indicate an issue with the card; it seems to be pretty normal for the screen turning on and off, just that the screen doesn't actually initialize and display anything.
About a week before the screen wake issue developed, I had a problem with the camera and gallery thinking that the SD card was not present. I eventually wiped and reloaded an older ROM and the problem went away.
I replaced the AMOLED screen and it now properly works. Since the screen was able to turn on by itself after an hour or so, I suspect it might be a capacitor or something that's gone bad on the flex cable itself. I'm not sure how much effort I'll spend tracing it down, but I might at least give it a shot.
Change the Screen
Had same issue with a Nexus 5. I changed the screen and it worked great.
xguntherc said:
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
Click to expand...
Click to collapse
my battery was running low, (and coz poor battery issues with JPY), i didnt notice when it switched of. normally i use the power button to turn the screen on to unlock, but instead i realised the phone had been off as it was now booting up...it booted up fine went into the homescreen and then vibrated once and powered down.......now it was powering down for a long time and occasionally there were vibrations and the lights on the home keys were constantly on. the screen was black. i got home and tried to charge it but the progress bar showed no progress on charging, i tried to switch it on but it would go to startup screen vibrate cupla times and power down. so eventually had to do a hard reset in recovery mode. tried every option but in the end had todo it by wiping data.
now the thing is, is this supposed to happen? if ur battery suddenly losses power ur whole fone will screw up?
for future ref if ur battery dies dont try to switch ur fone on until u got some charge in it and use the home key to put screen on..
Sounds like it could have been faulty firmware .
JPY does not have a significant battery drain problem per se .
jje
Black screen, vibrations and no boot after restart
Hello! I had almost the same experience (Black screen after reboot and occasional vibrations) only mine refused to boot even after memory wipe and after flashing new roms.
Was your phone rooted? Because I think rooting a 2.2.1 rom (XWJS3) was the beginning of my nightmare. keep in mind that the phone was working like charm for two months. This was the second time I had a problem. The first time the phone started after performing a factory reset by itself!
In case this happens to you next time and for every non experienced galaxy player (like me) reading this:
Don't panic! Blank screen, vibrations and no boot doesn't necessarily mean a hardware problem. Finally I managed to fix it flashing eclair and repartitioning with pit512. Now I'm a happy XWJS8 user
And a question for the experts: Any clue why this happened? Is it really a rooting issue? Can a cheap Chinese battery from ebay cause this?
everything was stock on mine, no root.......maybe thats why i could recover it??!!
Maybe! and I hope the reason is faulty firmware as JJEgan says. If this is true, your phone will be fixed by the next update.
I was very urge... the same happened again. It's been a month of smooth functioning and now after a simple restart, the device doesn't boot for absolutely no reason (Stuck on black screen constantly vibrating). Since my phone wasn't rooted, and I haven't seen many people talking about a problem like this I suspect:
1. Faulty hardware (for a few devices including yours and mine)
2. A Bad app.
Contacts Vanished
Hey Everyone
Im having similar problems, i updated my sgs to the js7 version of froyo, then rooted it with oneclick method. this was as i got the phone a month ago. Its been smooth sailing since then. But last night the phone powered down and wen it loaded up it had no contacts, my sms where still there but all the apps had a force close issue none worked. so cleared the cache in recovery. Still nothing so i did a factory reset and once loaded up. i formatted the sd and internal within the settings option. So the phone was now clean. I then connected to pc luckily had backups so installed titanium restored all my apps n settings. Using kies restored my contacts n thanks to an app called sms backup i restored those.
So all was well and worked again. I didnt restore the apps i had installed within the last week to make sure it was not a faulty app. I was happy, but now tonight it did it again. No contacts again.
Pls help
Any suggestions
That's exactly how it started for me. One month after rooting froyo 2.2.1 Suddenly everything force closes and the device hard resets by itself. I reinstall all the apps and then after one month and performing a simple restart, it refuses to boot. Stays in a black screen and vibrates every some seconds. I flash a new rom but does the same. Problem solved after repartitiong and flashing original eclair with pit 512. Reflashed a 2.2.1 rom and everything works perfect (the phone now is unrooted and with a nice clear stock rom). But then after one month again (!) I realise that some videos refuse to play. Trying to restart and craaash. black screen, vibrations and no boot. Did the same again (repartitioning and flashing) and now I wait for another month to pass and lose an hour of my life to do the same again. No idea why this is happening. Is it possible that rooting messes with something that stays faulty after restoring the file system? is there an app that we all installed and caused this mess? please this is the most serious problem I've red in this forum and still a mystery. I believe this thread should be sticky and we all share similar experiences because this looks completely random!
I believe this thread should be sticky and we all share similar experiences because this looks completely random![/QUOTE]
+ 1
Hi everyone, after trying everything I could to fix this phone I don't know what to do anymore so I'm here asking for other options.
So the story is, I was just using my phone as I usually would that day and it just randomly turned off and won't turn back on anymore.
(it randomly turned off before a couple of times but it would always turn back on)
- It won't go into recovery mode or any other of the 'modes' (I tried all the different combinations of pressing the keys).
- It's not a battery issue as I've tried my battery on my brother's phone (he has a Note 4 too) and it worked fine and I tried his battery on mine and it wouldn't work.
- I tried the 'drain' method (removing the battery and holding the power button for a minute or more).
- I tried using multiple cables to charge my phone nothing worked.
I didn't drop my phone, wet it, root it or anything and it was working fine the day it happened until it just powered off by itself. When I plug it in my laptop it would make
a sound indicating I've plugged something in but nothing happens. It was version 5.1.1 model SM-N910F.
TLDR; Is there a way to somehow recover the files in the internal phone memory?
This is happening to me as well, also started in February. I'm suspecting a hardware issue. Tried it ALL but rooting. In the past 30 minutes my phone has booted and rebooted itself till it died. If someone can confirm it is a hardware issue. Maybe it's time to unite and get it fixed for free. ~Tamarnouche
Recovering data from a brain dead phone may not be possible, as it probably need some internal component replacement which may erase the data(Mostly). Have u tried connecting it to pc? Better give it to service immediately. Good Luck.
My phone has done exactly the same thing, happened in February too, initially it did the random freeze then started to reboot itself, went back to stock software and full wipe but no improvement; now it will only boot if I leave the battery out for a prolonged period, otherwise it doesn't respond to the power button at all.
I occasionally see MMC Read Fail on boot but not all the time so presumably the internal memory has a bad contact or is failing.
Can it be replaced?
HXOY said:
My phone has done exactly the same thing, happened in February too, initially it did the random freeze then started to reboot itself, went back to stock software and full wipe but no improvement; now it will only boot if I leave the battery out for a prolonged period, otherwise it doesn't respond to the power button at all.
I occasionally see MMC Read Fail on boot but not all the time so presumably the internal memory has a bad contact or is failing.
Can it be replaced?
Click to expand...
Click to collapse
I have the same problem with my Note 3. Only if I keep the battery out for a long (over 24 hours) time I can see the boot logo. So if you find a solution to this kindly don't forget to tag me, will really appreciate it.
I was wondering..
I came across this Forum group since I was looking for boot problems with my SM-N910T3
I hope flashing pit will resolve this..
I recently started to have some low level issue and was hoping it was partition/boot related and not hardware.
Randomly phone boot directly into Download mode with error;
ddi: mmc_read failed
Often I have to pull battery and hold down /power / home for 10 sec to boot up again.
Thanks
I've been having some problems with my Galaxy S5 recently after ~2 years and some change of owning it. I'm stock rooted on the original ANCG KitKat version.
The problem: If I power off my phone, it will cause it to go into a bootloop, not going past the first screen (Samsung Galaxy S5, powered by android). I haven't found a reliable way to fix it from the loop, but I usually just remove the battery, wait, and try again until somehow it just works and boots up. This is extremely problematic because sometimes my battery runs out and after charging I'll have to go through this game of chance again until my phone works.
The next problem also adds to this frustration as well. When I attempt to pick up a call, my phone will sometimes just not work and restart itself. This leads to lots of confusion and I can't call them back for some time because the phone is stuck in a bootloop.
In the few times that I do get my phone to actually boot up, everything works fine except sometimes my Wifi just doesn't work. It gets stuck on "turning on" where the notification drawer quick setting icon is dim green and never gets to the turned on full green state, eventually just turning itself off (no green color).
I haven't done a factory reset or any real troubleshooting yet, as I'm a bit worried I won't even be able to boot up the phone and I don't have the time yet to spend a full day fixing it. Any help would be appreciated, thanks!
The calling problem may be caused by the google dialer app not being set as the the default phone app but as for the other issues i have no idea a factory reset is a good start though
unfortunately I had the same problem but I have marshmallow but the factory reset helped with the not booting up and see a big difference with the battery