Related
So last night I dropped it. It was fine I have a ballistic case. Then pulled it out of my pocket 1 HR later and the Samsung boot logo just keeps repeating. I take the battery out, and as soon as i put it back in it starts doing the same thing. I tried recovery, download mode, plugging it in. Nothing! same thing over and over. Then I just put battery in and pressed the power button over and over probably 40 times aand it starts up and runs fine? It came back on last night for about 30 minutes then did the same booting problem. Do you guys think I messed something up by dropping it? I haven't flashed anything in months. Should I take it and get a new one?
iruleyounow said:
So last night I dropped it. It was fine I have a ballistic case. Then pulled it out of my pocket 1 HR later and the Samsung boot logo just keeps repeating. I take the battery out, and as soon as i put it back in it starts doing the same thing. I tried recovery, download mode, plugging it in. Nothing! same thing over and over. Then I just put battery in and pressed the power button over and over probably 40 times aand it starts up and runs fine? It came back on last night for about 30 minutes then did the same booting problem. Do you guys think I messed something up by dropping it? I haven't flashed anything in months. Should I take it and get a new one?
Click to expand...
Click to collapse
probably ANOTHER broken power button...honestly, seems like everyones power button is failing these days...its starting to become common...one user had luck with this: http://mobiletechvideos.mybigcommerce.com/samsung-infuse-4g-power-button-repair/ i think jscott suggested taking off the phones casing and dusting the inside where the button is with compressed air to clean off the contacts, another user has mentioned to completely desolder the power button and use a usb jig to power on the device...do any of the following at your own risk, i cant guarantee any will work...
Well it hasn't happened again. Clicking the button a hundred times might have fixed it hahaha.
Received my Nexus 5 today after much waiting due to Google/courier making a mess of my delivery details over the last 9 days...another story altogether.
Straight out of the box, and after putting in my SIM, I stuck the phone on charge for a bit and booted her up, though it seemed like there was a bit of charge in it (40-50%) so felt happy unplugging it during some of the set-up...syncing accounts, connecting to wifi, sending a couple of test SMS and inputting my carriers voicemail number.
Then it crashed as I was reading a text, and wouldn't turn on again.
I put it down to teething problems and left it alone and on charge for a bit, and after 10 mins tried again and everything was fine. Booted up (and super fast at that). Spent another 20 mins or so messing around with wallpapers and adding a couple of apps that I use daily.
Stick it in my pocket to run a quick 10 minute errand (including trying to pair it with the Bluetooth in my car, unsuccessfully), and when I get back to the office I find the phone had shut down in my pocket, and it has now been unresponsive for the last 2+ hours.
I've tried leaving it on charge. Tried every combination of holding down buttons to elicit any kid of response, but absolutely nothing. Not so much as a screen flicker.
Would anyone have any advice on things I could try before I contact Google and pack it back off to them? I'm out of ideas. I can't get it to respond in any way to anything!
robotsonic said:
Received my Nexus 5 today after much waiting due to Google/courier making a mess of my delivery details over the last 9 days...another story altogether.
Straight out of the box, and after putting in my SIM, I stuck the phone on charge for a bit and booted her up, though it seemed like there was a bit of charge in it (40-50%) so felt happy unplugging it during some of the set-up...syncing accounts, connecting to wifi, sending a couple of test SMS and inputting my carriers voicemail number.
Then it crashed as I was reading a text, and wouldn't turn on again.
I put it down to teething problems and left it alone and on charge for a bit, and after 10 mins tried again and everything was fine. Booted up (and super fast at that). Spent another 20 mins or so messing around with wallpapers and adding a couple of apps that I use daily.
Stick it in my pocket to run a quick 10 minute errand (including trying to pair it with the Bluetooth in my car, unsuccessfully), and when I get back to the office I find the phone had shut down in my pocket, and it has now been unresponsive for the last 2+ hours.
I've tried leaving it on charge. Tried every combination of holding down buttons to elicit any kid of response, but absolutely nothing. Not so much as a screen flicker.
Would anyone have any advice on things I could try before I contact Google and pack it back off to them? I'm out of ideas. I can't get it to respond in any way to anything!
Click to expand...
Click to collapse
Try pressing and holding the Power and both Volume Buttons for about 15 seconds. Then try to boot.
abaaaabbbb63 said:
Try pressing and holding the Power and both Volume Buttons for about 15 seconds. Then try to boot.
Click to expand...
Click to collapse
Tried this (which I'd tried to no avail previously), and no joy. Wouldn't boot afterwards.
Left it on charge (which it had been for the 20mins previous to trying this) for another 10 mins. Came back to it, pressed power and it just came on. No boot. It was just already on.
Veeery confused now after trying intermittently to get it to boot for what is hours now.
Should I do a factory reset?
I'll log with Google that this has happened so there's less come-back if it dies again and I need to return it. Haven't tried it with a SIM in yet (need a working phone!), but will report back after that.
robotsonic said:
Tried this (which I'd tried to no avail previously), and no joy. Wouldn't boot afterwards.
Left it on charge (which it had been for the 20mins previous to trying this) for another 10 mins. Came back to it, pressed power and it just came on. No boot. It was just already on.
Veeery confused now after trying intermittently to get it to boot for what is hours now.
Should I do a factory reset?
I'll log with Google that this has happened so there's less come-back if it dies again and I need to return it. Haven't tried it with a SIM in yet (need a working phone!), but will report back after that.
Click to expand...
Click to collapse
I'd fully charge it before doing anything else.
jd1639 said:
I'd fully charge it before doing anything else.
Click to expand...
Click to collapse
Have done now. It's charged and I'm about to retry the SIM.
Possibly of note, after I checked it and saw that it had restarted, I checked the battery log and it showed that it had been running for 29m 25s on battery...yet was on charge. I'd attach the screenshot but I haven't posted here enough times for the forum to let me
It was unresponsive no more than 10 mins previously. 10 minutes would be generous.
Anything I can learn from that?
So the phone lasted all night with some light use. Left my Nexus 4 on with no SIM for alarms so I knew I could wake up this morning, but instead, to my joy, I had two phones alarming at me together!
So it was to my dismay that after I'd read some mails, checked some sites, and left the phone to go and get ready for work for 10mins...I came back to it dead again.
I heard some notifications come through (and I was in the middle of a conversation on WhatsApp, so that was normal). I saw the notification light flashing too, so the messages coming through, or at least the first one, didn't crash it.
It did however start up again, with no SIM, after some cajoling.
Is there some way I can see an error log, or a crash log? Or anything I can install to log this for the next inevitable time? Or is this sounding like a permanent hardware issue and I'll need to return the unit?
There's a thread somewhere you can find it, it will show you how to install stock firmware again.
Do that and if it occurs again, call Google to get a RMA
Sent from my Nexus 5 using XDA Premium 4 mobile app
Re-installing the firmware won't jeopardise my position in sending it back to Google, no?
Just went back to it to put the SIM back in it and it's unresponsive again. FFS.
robotsonic said:
Re-installing the firmware won't jeopardise my position in sending it back to Google, no?
Just went back to it to put the SIM back in it and it's unresponsive again. FFS.
Click to expand...
Click to collapse
No, but you have to unlock the bootloader first before you can flash a factory image and install adb (platform-tools) on your pc, and afterwards relock the bootloader again before sending it to Google.
Hello people, first off lemme say I'm not necessarily new to this forum, I for sure have used it a hell of a lot in the past and I know roughly what goes on around here, I've recently created my account in order for me to actually be able to be able to plead for the amazing help the XDA is known for.
Anyway, long story short, I don't know what the hell happened, but allow me to start from the beginning. I went on a camping weekend with my OPO, phone worked flawlessly all weekend and lasted the whole time, everything was fab, went back to a mates house and asked if I could borrow his phone charger (He has a Lumia 625 incase anyone was wondering), we then went out shooting and I left the phone there for a few hours to charge. Came back to it and it was fully charged, but had turned itself off? Because it was on the power off charge screen when I came back to it, and was on lock when I left it, nobody touched it in that time. I took it off charge, powered the phone up and it must of boot looped about 3 times? Eventually it got into CM but there was no lockscreen, went straight to the homescreen. This is where it went nasty, the capacitive keys outright weren't responding, the device wasn't slow as such, nor was the CPU running hot or doing anything intensive (I have CPU load display enabled), but the date was set to Jan 1970, and the phone couldn't pull a signal at all. WiFi outright wouldn't switch on either. So I tried rebooting it a few times, to no prevail. For some reason, I accidentally tapped Bluetooth in the quick settings panel, the phone crashed and rebooted, and wouldn't stay on for more then 3 seconds? Before crashing and rebooting. I've since gone into recovery and tried a factory reset, cleared cache and media too, but to no luck. Phone still doesn't stay on for more than about 3 seconds once it actually gets into CM (The welcome to CM screen, it crashes 3 sec immediately after boot).
I have no idea what I'm supposed to do, can anyone try shed some light on this? Much help would be appreciated and I sincerely APOLOGISE for the wall of text. Many thanks.
^Dat wall of text doe (sorry about that)
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2922849
PS. You might want to consider using paragraphs in future posts, that's one hell of a long paragraph there [emoji13]
Transmitted via Bacon
Thank you man for the pointer, I'll give it a go. And yeah sorry for the wall.
No worries, I hope it works for you.
Transmitted via Bacon
I am having the same issue since last night. Put my phone to charge and when I picked it up it stayed on for about a minute unable to connect to Wifi or cellular signal. Then it went to a crazy boot loop. Wiped cache, media and at the end data. Now it boots and it stays on for a few seconds and reboots. I will try the solution when I get home tonight but I was just curious if it worked for you.
So my story begins with me purchasing a used white Nexus 5 for $155 from swappa over a week ago for my wife. *
Phone arrives in perfect condition.
I first unlocked and flash twrp via adb. I proceed with installing Chroma and elementalx. Spend few hours on making the new Nexus 5 the same as my wife's current Galaxy Nexus.
Phone is running great. Zero issues for about 3 days while the phone was just at home running. She throws the phone into her purse and goes to work. Within hour she calls that her phone won't stop rebooting…. *Oh no…. The dreaded power button issue… right?
So I'm assuming the seller did the old “whack against a solid object” temp fix and sold it. I have no proof of that so I'm assuming.
So what do to? Well fixing the power button is still cheaper than buying another Nexus 5 phone. Everyone one quoted me $60. It is what it is… at this point I could have gotten a refurbished phone but what can you do…
So you would think this is the end of my story, right? Wrong.
I go to a cell phone repair place close to my work. They have this tiny power button in stock and replaced it many times before. I come back later that day to pick it up and they have bad news… of course they do.
After the switch replacement, the phone did the same reboot. Goes to Google logo and reboot. If I fiddle with the power button I can get to the OS but reboot right away. The guy proceeds with that it is me rooting it that caused it and I need a new motherboard, price $100.
I started questioning if he really did replace the switch. If it was OS related, the phone would not have worked for couple days and then break randomly. It would not boot to the OS sometimes or at least it would let me boot into TWRP, right?
Long story short, I left with spending the $100 on getting this used $155 phone fixed. Super annoyed at this point.
So after this long story, is there any chance this was really OS related and not a faulty power switch or did I just got lied to and the power switch was never replaced?
For sure, you should've attempted to restore the phone through Google's factory images first. My power button went super wacky twice since I've had it(day 1 model). I just pulled it out, and now the problem is gone all on it's on.
When it kept rebooting, did you try booting into the bootloader at all?
Sent from my Nexus 5 using Tapatalk
Curiousn00b said:
For sure, you should've attempted to restore the phone through Google's factory images first. My power button went super wacky twice since I've had it(day 1 model). I just pulled it out, and now the problem is gone all on it's on.
When it kept rebooting, did you try booting into the bootloader at all?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I sure tried to get into recovery but wouldn't work. Just kept rebooting. I had a nandroid backup done a day before but the phone would not stay powered on for long enough to do anything. It was the equivalent of having no battery left and phone just shut down and attempted to reboot constantly. I took out the motherboard and played around with the button before I went out to repair it but it was the same results. If I "massaged" the button then maybe the phone would get past the Chroma logo and get into the OS, but as soon as I attempted to touch the power button again it would reboot.
I tried reviewing the old motherboard and unless this shop's soldering skills are top notch, I can't tell that the switch was replaced. The soldering point were identical to the volume buttons. When I questioned the store owner, he stated they are that good with their infrared soldering He took out a package of 3 Nexus 5 switches and one was missing... meaning he installed it.
I highly doubt it was OS related. If you brick a phone when flashing, then it would just be constantly in a boot loop, right? I know I can easily go into recovery and flash whatever .img I need to, but this was just nonstop reboot and different times
First thing this morning, my Note 5 was working fine. Used the navigation to get to the house I was working at today, as well as simultaneously using Autoguard dash cam app. I got to the job, exited the navigation and Autoguard, got out of my van, holstered the phone.
About 15 minutes later, I try to use my phone to take some pictures, but nothing would happen. Black screen. Couldn't restart by holding the power button. Tried getting into both recovery and download modes. Plugged in the phone to see if it would charge. I was getting absolutely nothing. It was like my device had just up and died. I just kept wondering, could the board have been fried or maybe the battery shorted?
I was dreading the thought of seeing if warranty would cover the device, even after having it for only 5 months. I've been screwed before by the insurance and warranty service on other phones. Making me pay the deductible for a new device, and them claiming that there was water damage, showing me the "damage", when it's obviously a fried board and the moisture sticker isn't activated.
But anyway, lunch time rolls around. I go sit in my van, start pressing the buttons again. Still no restart, still no recovery, but then I try download mode, and viola. Device got into download mode. I canceled out, and the device rebooted normally. I was at 100% power when I got to the job site, and after roughly 4 hours later of it being unresponsive brought it down to 60%.
My mind was put at ease. Charged up normally afterward. The rest of the afternoon there were no more hiccups. Has anyone else ever had something like this happen?
needmymorningcoffee said:
First thing this morning, my Note 5 was working fine. Used the navigation to get to the house I was working at today, as well as simultaneously using Autoguard dash cam app. I got to the job, exited the navigation and Autoguard, got out of my van, holstered the phone.
About 15 minutes later, I try to use my phone to take some pictures, but nothing would happen. Black screen. Couldn't restart by holding the power button. Tried getting into both recovery and download modes. Plugged in the phone to see if it would charge. I was getting absolutely nothing. It was like my device had just up and died. I just kept wondering, could the board have been fried or maybe the battery shorted?
I was dreading the thought of seeing if warranty would cover the device, even after having it for only 5 months. I've been screwed before by the insurance and warranty service on other phones. Making me pay the deductible for a new device, and them claiming that there was water damage, showing me the "damage", when it's obviously a fried board and the moisture sticker isn't activated.
But anyway, lunch time rolls around. I go sit in my van, start pressing the buttons again. Still no restart, still no recovery, but then I try download mode, and viola. Device got into download mode. I canceled out, and the device rebooted normally. I was at 100% power when I got to the job site, and after roughly 4 hours later of it being unresponsive brought it down to 60%.
My mind was put at ease. Charged up normally afterward. The rest of the afternoon there were no more hiccups. Has anyone else ever had something like this happen?
Click to expand...
Click to collapse
Yup, has something similar happen to mine. Locked up just like yours while it was in my pocket. No response to anything, even plugging it in to the charger. Just had to hold volume down + power. This is a soft reset and is like a battery pull. Try it out if you have this problem again.