I wasn't able to find anything about the problem online and since this seems to be an oddly specific issue I decided to open this thread.
I wrote about what happened here yesterday:
"My N5 shattered back in May so I had to replace my screen+digitizer.
After I was done I plugged the N5 in to charge and it responded immediately with a blinking red LED. I let charge for half an hour or so and then started it up. Everything seemed to work perfectly fine. Then it began to restart every once in a while. Eventually it shut down and since that point there is zero reaction from plugging it in or hitting any number of combinations of power + volume keys."
Late last night I turned the phone on while the battery cover was removed and everything worked perfectly fine. I have been using it since then and there no issues with the anything else.
How can I get the phone working again with the cover where it should be?
Related
I bought my gtablet from woot around 3 weeks ago and installed cyanogen 7.0.3 on it on the first day. I had been working great till today. Last night I charged the tablet fully before going to bed and disconnected it once it was fully charged. Today morning when I woke up the screen would not turn ON. I thought the battery must have drained and so I connected the power supply and it started charging the tablet. After 15 mins the screen came on by itself. So I then switched off the screen and left for work.
Once I got back from work I switched the screen on and the screen came on without any issues. But then it just hung. None of the buttons respond, not even the power button. The screen has been on for the last 4 hours. My computer is unable to detect it when connected via USB. If I connect the power supply I can see the charging light come on.
Has anyone else come across this issue? Is there a way to resolve this issue?
sounds very very familiar to my issue... been up all night trying to figure it out no luck thus far... nvflash wont recognize it on two different computers and not a chance at getting to cwm...
It shutdown once the battery drained. Charged it up and it started fine. Now I am issues updating my apps from the market place . The error I get is "There was an error downloading the update"
Hi,
i have very strange issue which i noticed right now. It seems that i can not turn on my mobile/screen. I have to say that mobile is bought less then month ago and no modifications are made like rooting or something like that. Today it worked without any problems and when i got home i left it on my desk but two hours later i wanted to check for my e mail but screen/mobile is not turning on. I checked on/off button and it's not jammed. What else can i do considering that i can not remove the battery
Ramiell said:
Hi,
i have very strange issue which i noticed right now. It seems that i can not turn on my mobile/screen. I have to say that mobile is bought less then month ago and no modifications are made like rooting or something like that. Today it worked without any problems and when i got home i left it on my desk but two hours later i wanted to check for my e mail but screen/mobile is not turning on. I checked on/off button and it's not jammed. What else can i do considering that i can not remove the battery
Click to expand...
Click to collapse
Charge the phone. Could be dead. Are you SURE nothing has been modified? Also, hold down the power button until you see the capacitive buttons flashing, and don't let go until they stop flashing and the phone reboots.
Battery probably died. This phone is known to lose power abruptly. It's happened to nearly everyone at some point--it will appear to have some charge left and then suddenly drop to 0%.
Just leave it plugged in for a while and see if it revives.
nothing helped from what you mentioned but it works now. When i plugged in the charger there was no sign of charging. When i pressed and hold power button also nothing happened. Then i tried to hold volume down and power button but also no reaction from the phone and then i pressed the mobile bit harder around display to check that maybe there is no loose wire and at this point mobile turned on by itself (boot screen) and after booting there was crash report. I have HTC phones for years now and such problem never occurred to me before but phone works for now :good:
thank you
Hopefully it isn't a defect, my one x has never went off on me at a random battery percentage, except for some ROMs he he
As mentioned, some people have had instances of randomly losing charge, or phone not seeming to take a charge after running the battery down. Leaving the phone on the wall charger (not USB, which takes much longer) for several hours (overnight) and then trying to power on seems to solve the problem. One guy here could not get any response (even after charging for hours) except by holding the power button while the phone was on the charger.
The issue seems completely random. So unless it persists, probably nothing to worry about.
I have a Samsung i727R. I’ve had the phone for about a month. Have not used it a lot, no rooting, just ‘normal’ usage. I have not downloaded anything interesting at all.
The problem started a couple weeks ago. It started when I plugged the phone in to charge and nothing happened. I could still turn the phone on and everything worked fine, but it just would not charge. This makes me believe it is not the battery.
So I bought a new OEM cable. It still would not charge (not into the wall or computer. BTW my computer has never recognized that my phone was plugged into it since I’ve had, which I assume is an unrelated issue). But I decided to leave it plugged in longer, and after about an hour, it started doing a short vibration every few seconds, and every few minutes it would just turn on and stay on until I turned it off. Still does not charge. This makes me believe it is not the cable.
I have read about the sticky power button. The power button seems to be working fine (it feels fine / not sticky), and I can turn it on and off without a problem, and operates normally. It just starts on its own as well when plugged in.
Could it be the charging port? I’m unsure because the vibration only happens when I plug it in, so the phone is recognizing that it is plugged in; it’s just not charging.
If not the charging port, what else could it be?
any takers? if you know the answer is posted elsewhere, please direct me where to go. I don't think its the sticky button problem, so not sure what next.
ok, I've had no responses from other members, so I dismantled and checked out the power button, as my problem has some symptoms of the power button problem. but after cleaning, pushing, reassembling, there is no change from the situation I described above.
there is one bit of new info: I left the phone plugged in (it turned on after about 4 vibrations, as usual), but while it is on and plugged in, every minute or so the message indicates it is charging! this lasts for about 5 seconds, and then it proceeds to tell me to plug it in again.
really sounds like it would be a poor connection (replace the charging port?), but seems odd that the pattern of events would be so consistent. if the phone had a poor connection, I would think it would work well for a bit, and then not work at all for a bit, etc.
please help!
frankenish said:
ok, I've had no responses from other members, so I dismantled and checked out the power button, as my problem has some symptoms of the power button problem. but after cleaning, pushing, reassembling, there is no change from the situation I described above.
there is one bit of new info: I left the phone plugged in (it turned on after about 4 vibrations, as usual), but while it is on and plugged in, every minute or so the message indicates it is charging! this lasts for about 5 seconds, and then it proceeds to tell me to plug it in again.
really sounds like it would be a poor connection (replace the charging port?), but seems odd that the pattern of events would be so consistent. if the phone had a poor connection, I would think it would work well for a bit, and then not work at all for a bit, etc.
please help!
Click to expand...
Click to collapse
u answered ur own question, bad connection, its either the cord or charging port or batterycontacts or even a bad battery but more likely a connection prob
S2 SKyrocket wont start up!
k, so here is the scenario. I have rooted and have jelly bean running since the official update came out from at&T. It has been working fine. No issues just some bug with the camera and the pictures that I managed to deal with. 2 Days ago my phone after battery reached 1% went dead. It has happened before, I just plug it in and charge, everything works smooth. Until, the phone never charged and when I attempted to turn on it just vibrates once , Samsung logo quickly comes up and disappears.
I know its not a sticky Power button issue as the phone does not start up when I insert the battery. I attempted to go into recovery mode but nothing happens.
Don't think the phone is bricked since it shows some kind of life. Not sure if I should buy another battery or charge the battery on another device...While I try to troubleshoot this. Does anyone have any suggestions, and IF i have missed a sticky please direct me to it, since their is so much content here.
Thank you in advance!
Hi at all,
about a week ago my girlfriend dropped her Galaxy S6 into the toilet (NEVER put your phone into your back pocket).
After some days of drying I was able to turn it on while plugged in and except for the battery everything worked. I replaced the battery and everything went back to normal. Sometimes the battery wouldn't charge over a specific level and sometimes it just turned off but since yesterday it keeps turning off as soon as I can see the lockscreen. If it's plugged in it stays on and I can use it as always, everything still works, but it's basically impossible to use it without a charger
What could be wrong? How I can identify the source of the problem? Is there a log I can use or some diagnostic tool?
Thanks a lot,
Thomas
tombond said:
Hi at all,
about a week ago my girlfriend dropped her Galaxy S6 into the toilet (NEVER put your phone into your back pocket).
After some days of drying I was able to turn it on while plugged in and except for the battery everything worked. I replaced the battery and everything went back to normal. Sometimes the battery wouldn't charge over a specific level and sometimes it just turned off but since yesterday it keeps turning off as soon as I can see the lockscreen. If it's plugged in it stays on and I can use it as always, everything still works, but it's basically impossible to use it without a charger
What could be wrong? How I can identify the source of the problem? Is there a log I can use or some diagnostic tool?
Thanks a lot,
Thomas
Click to expand...
Click to collapse
Did you use an oem battery? If after using a genuine Samsung battery you still having issues, it may point to the charging part of the motherboard.
The battery I bought was sold as "official" Samsung and it looked exactly the same. I also didn't buy the cheapest one so I guess that's fine. I don't think that it's a problem with the battery since the phone boots up until the lockscreen appears and then shuts down. If the battery was dead it would crash at any random point and not always at the exact same time. The overall behavior is pretty strange since it stays on and works perfectly fine as long as the charger is connected.
So is there a log I can search through? Mayber there's some kind of low voltage warning or something like that. Otherwise I'd have to sell it as a defect device on ebay and I would rather like to keep it
I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
alienjon said:
I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
Click to expand...
Click to collapse
See if you still can get your phone into download, fastboot or recovery mode. Here you can see the button combos: https://m.youtube.com/watch?v=YFaq4g-oa2Q
If you can get to recovery mode, click on wipe cache and reboot. If your phone still is stuck afterwards, go to recovery again. There is an option to wipe and reset the phone. Note that your data will be lost!!! Do it at your own risk. But a reset often is the last working choice when your phone behaves strangely.
If you get none of the three mentioned modes to work, I think your Pixel has a hardware fault.
Hope this helps.
check the charging port first....whether it is charging or not......try to connect to PC
i guess the phone is not charging
So the bottom line is this is still somewhat ongoing, though I’ve confirmed the phone is definitely bricked. I brought it into UBreakIFix and after taking it apart (noting that the device seemed physically in great shape) that there wasn’t anything obviously wrong with any of the particular hardware (they mentioned that replacing the motherboard would likely do it, but it would be about as expensive and effective as buying a new phone anyway...).
I ended up writing back to Google and am in back and forth talks with them now. I’m not sure what they can or will do, but my final answer will have to be getting a new phone one way or the other.