So I haven't used my Nexus for somewhere around 2 months since I got a new phone. The Nexus S was working fine prior, I had actually just got it back from Samsung after them fixing an issue related to my top volume button. After, I received it, the phone was in a complete stock condition, like it was just bought from a store (no unlocked bootloader, fastboot, Clockwork, etc.). A bit later, the OTA Jelly Bean update comes in, but I don't use it too much as I just got my new phone.
I left it on and ignored it for the past 2 months. I just assumed the battery would run out, and if I wanted to use it I would just plug it back in and that would work. Now the Nexus S won't show any sign of life. I've tried removing the battery and trying to turn it on while plugged in, when it's plugged in with my battery in, the charging indicator it used to show never shows up. Plugging it into my computer with or without a battery does nothing, it doesn't even show up in my device manager as "Unknown". I've also tried holding VOLUP + PWR for 10 seconds with all these different situations. Nothing. The phone is essentially dead. Any clue why this happened and how I should go about fixing it?
Nevermind. After leaving it plugged in with the battery for ~20 minutes it finally powered on! Hopefully this thread helps out someone in the same situation. It just seems as though it takes a long time to get it to a state in which it'll power on.
Related
So today, as i was on my way to work I accidentally held down the lockscreen button and the power menu popped up (I was on Glorious Overdoes V2) in the middle of a text and i pressed reboot accidentally... My phone never rebooted... It was stuck on the black Sidekick 4G/T-Mobile screen and then it would go black, then once again that screen would pop up... I removed the battery and put it back in, and without me pressing any buttons the same screen came back up... I let it sit for a while and after 20minutes nothing changed except the phone got really hot. Luckily I had my OLD Nokia in my car and popped my SIM card in it so that i could continue having a phone. I let The Sidekick sit for 4hours and it was extremely hot and then eventually it just turned off completely (Im assuming the battery drained, it was at 90% 4 hours before.) I got home, plugged it in and it wouldn't even turn on the charging screen. Somebody told me that my Motherboard is fried but I don't know. I called T-mobile and they're going to send me a new phone since it's still in the 1-year warranty period.
Anyone know if they're going to be able to inspect my old device and find out if i rooted/flashed it? because i can't get into it or anything to ODIN
I feel like they will try putting a new battery in it, and if it still wont turn on you should be fine.
It got hot because the CPU was churning over something and couldn't enter a low power state. I bet you could coax the phone into download mode and reflash it.
what do you mean coax the phone into download mode? by using the button combo to get it into download mode when turning on? I've tried that and it doesn't work. I tried rebooting into recovery and that wont work either. Also, it wont charge the battery anymore...
I've always had a hard time getting into download mode, and my phone works fine. I just spent 5 minutes trying different combinations until I got it.
I've heard people say trackpad-power button, volume down-home-power button, volume up/down-put battery in-plug in USB, etc etc etc. But the only method that works for me is to put in the battery, plug in the USB, wait for the charging screen, then hold volume down-trackpad-power, releasing power as soon as the screen goes black
You say your phone is turning on as soon as the battery is inserted? What if you have it plugged into USB first?
I had the exact same problem, I sent it into samsung and they just replaced a part(never told me which one) and it was fixed. I did noticed that when the sccreen was poped open to show the keyboard, it would stop. But it's probably a loose cable like I've read before.
Sent from my SGH-T839 using Tapatalk
Worst case scenario if you can't figure it out here on XDA, you could always sell it on eBay for parts as defective.
My HOS is 2 weeks old today. I have rooted it (unlocked BL) and spent many hours with it...kept the stock ROM for now.
I had been using it today and last night and the battery was low so I plugged in the charger (using AC outlet), and left it on. I went back to it 20-25 minutes later and it was extraordinarily hot (I realize this happens...I posted on a thread 2 weeks ago when my phone first overheated to this degree). I saw that like the first time this phone overheated (which was within 48 hours after purchasing it) it wasn't charging. Similarly, this time, the battery showed only ~halfway charged. In my experience, it only takes about 20 minutes to fully charge it... so I was concerned.
I decided to power it off and keep it charging--hoping that the heat would lessen and it would just cool off and charge.
However, I checked it now (perhaps 2 hours later after powering off), and it won't even start. I plugged it in again and waited about a minute (thinking maybe somehow the battery drained), but no luck.
This never happened to me with my last HTC... I have never not had a phone not power up... this seems really weird.
Any suggestions?
Thanks!!!
Mine takes longer than 20mins to charge.....however its not good if it wont even power on, you gotta take it back
Have you tried to power it on by holding the power & volume down button?
frazzeld said:
Have you tried to power it on by holding the power & volume down button?
Click to expand...
Click to collapse
Yes, I tried booting into recovery.. No luck... This is so frustrating because I have not really dropped it or got it wet or anything. I don't like the thought that it might have overheated and caused permanent damage.
I will take it back today I guess... Is 14 days still within the return/replace period? I won't even say I rooted it.. Just that it stopped working. Although I will be irritated to have to unlock the bootloader and root a new one.
I am wondering... Is there a way to power up the phone using ADB??
Thank you
unless your phone is recognised in ADB, No !
Well...good news, I think anyway...I tried taking the SIM card out and it didn't do anything so I left it alone plugged in for maybe an hour.
But.....
When I later looked at it, it was on again, and..it had booted into recovery. I had tried earlier to do this as mentioned above, but nothing happened (using power on and holding the volume rocker down:
So after putting the SIM card in it was fine...go figure.
Thanks for the replies!
Sent from my HTC One-S (rooted), stock ROM
Hi,
I have TMO Nexus 5, 2.5 yrs old. Suddenly, my phone shuts down with more than have battery charge remaining. I cannot do anything by pressing any buttons. it is dead. If I connect to the charger, phone goes on the loop. The google sign appears on the screen, then it goes dark in a second or 2, then sign appears again, and so on. I can access the bootloader menu but only for a second. Then the phone goes off again. I cannot even properly turn it off, even when press power/volume up/down keys together. It just will not shut off.
Happened a few times before, but I was able to revive it by charging 3-4 hours and eventually it stopped looping. This time, no luck. Between the episodes like this, it worked just fine. Stock, never rooted, latest android 6.01.
Bad battery or something else? I did order the battery and will try to swap it, but would like to know if this could be anything else.
Normally, I would try to simply remove the battery and then put it back, but this battery is a little trickier to remove. I do not want to do this until I decide the battery needs to be changed.
Thanks very much.
I've had this phone for about 2 months now, and from the beginning, it's had an issue where it would randomly freeze, restart, and get stuck in a boot loop for random amounts of time. Sometimes it would be fine after 2 minutes, sometimes it would need 10. I kept thinking this was a firmware issue - the phone WAS rooted with TWRP installed, but none of my past phones have had this issue and hardly anybody online seems to have had it, either - and just thought that maybe installing a custom ROM would fix it, but never got around to doing so.
3 days ago, my S7 went into a boot loop again, so I just decided to put it down and let it do its thing. After 20 minutes, however, it still wasn't booting, so I booted into TWRP, and cleared the cache and Dalvik cache. Another 20 minutes later, I went into panic mode and started doing Nandroid backups of my stuff. I decided that I had no other choice but to commence with finding a ROM to replace stock. In the meantime, I just plugged it in and let it keep looping, hoping against hope that it would just fix itself like it always did.
About half an hour later, I was ready to install the ROM I'd decided on. I went and picked up my phone, but all that I saw was the screen was black, and the blue notification LED was lit up. I tried holding Vol- + Power to start booting it into TWRP, but nothing happened. The phone didn't vibrate, the screen didn't change, and the LED stayed lit. I tried holding every button combination possible, for even as long as a minute, but the phone refused to respond. I tried plugging it into my computer, but Windows didn't detect anything.
Skip to today, and the phone's battery has long since died(the LED isn't lit up, so I can only assume...), and I just decided to plug the phone in for the hell of it just to see if maybe it would maybe work again. To my astonishment, 2 minutes later, the battery icon came up on the screen, but the charging animation wasn't there. When I held Vol- + Power, the phone actually responded and restarted! Though, it wouldn't boot past the Galaxy S7 splash screen, and when I tried to boot it into TWRP, it went back to being a brick. I let it sit for about 10 minutes, plugged it in, and this time tried to get it into Download Mode, and it worked!
I downloaded the Switzerland version of the G930F firmware, flashed it in Odin, and everything seems to have worked. Odin says it succeeded, but when the phone tried to restart, it got to the splash screen, and after a few minutes, the screen went black again. When I plug it in now, the Galaxy S7 screen will come up, but now I can't seem to get into Download Mode anymore(though, it DOES still seem to respond to me pressing Vol- + Power).
Does anyone have any idea what's going on? I can only seem to find 3 or 4 other threads on various forums about this problem, but none of them have any answers. People just keep saying the usual "Hold Vol- and Power to make the phone restart", but in case I haven't made it clear, THAT ISN'T WORKING.
And before you suggest that I return it to where I bought it for a replacement or refund: I bought this phone on eBay from a seller who said it was in pretty much mint condition. When the phone arrived, there was not a dent or scratch anywhere on the phone, even around the charger port, so I have no reason to believe he was lying. When I asked him about any possible problems with the phone's operational stability the other day, he says he tested it for about 2 weeks, and that he didn't notice anything.
Sounds like a hardware fault, not much else you can do other than flashing stock and factory resetting, which you've done
Considering it had a fault from day 1 it sounds like that fault finally caught up with it
Likely scenario if sent for repair, new motherboard replacement needed
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.