Related
My HTC Surround fell out of my hand while on a bike going very fast down a hill and into a puddle of water, and when I got it out it wouldn't turn on. When it finally did my phone was completley wiped and reset and I had to sign in with a different Windows Live ID. Then all of a sudden my phone restarted and turned on and it was back to the original way it was before I had dropped it. It was fine for a few hours until it died, then whenever it rebooted it did in the bootloader screen. When I called HTC I got some hard to understand foreign woman and all she told me to do was a hard reset which doesn't work because when I go to press the volume down button to select the reset option it does absolutley nothing. I have tried the Camera button + Power + volume to downloader mode but it just sits in download mode then reboots into bootloader. It is not recognized by the computer unless it's in Download mode or "connect to pc" mode and Zune tells me that theres an error and it cannot fix the device. I downloaded the Windows Fix Tool and it also says the device cannot be fixed and there's no restore point. And I cannot take it to HTC or AT&T because I am out of warranty. So, any ideas here? Is it completley done?
Dude you should've took the battery out first thing, but it still could be salvageable.
You could try the rice trick:
http://www.ehow.com/how_5043830_dry-cell-phone-out-rice.html
Good luck!
Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock
Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.
a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed
jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:
A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.
Help with LG G3 Turns off During Boot & Unable to Factory Reset (is it a lost cause?)
Hello everyone. This is kind of a complicated issue, and I would love any help I can get.
Back story:
I have a Verizon LG G3, purchased in December of 2014. I never rooted the phone, so it has been stock this whole time. A couple of months ago, the SD card holder randomly stopped working (no spills or drops). I tried multiple, new SD cards, formatted them and everything, but the phone just kept ejecting the SD card, and corrupting them, so I just gave up on it and stopped using an SD card in the phone. This is not the current issue at hand, but I wanted to preface that I've been having issues with the phone.
Fast forward to a month ago. I had my phone plugged into the wall charging, and was not using it. I noticed out of the corner of my eye that my phone turned off. I unplugged the phone and tried turning it back on. It showed the LG logo screen, then the verizon screen, and then just turned off. When I tried powering it again, it did nothing. I pulled the battery, put it back in, and pressed the power button. I got the same series of lg logo, verizon logo, then off. I thought maybe it was a battery issue and took it to a local phone repair shop. They put in a new battery, but got the exact same boot problem I did. I left the phone with them, and they took it apart to see if it was a hardware issue (and the infamous stuck power button issue). When I returned, they told me that they did not find any hardware issues. It also was not an issue of the stuck power button/power button not working. They decided that it must be a software issue. Their explanation was that the phone had probably tried doing a software update and something went wrong. They said they could only fix it by completely wiping the phone and installing the software back on. I was reluctant to go through with it because (1) I would lose all my data (and I did not back it up, my fault, I know) and (2) it seemed like they wanted me to pay almost 100$ for something I could do at home. So I kept the phone and left it alone for a while. Now, it has been a month since the issue began, and I'm trying to see if I can fix it. Here is what I have tried.
1. Tried to power it normally again, but now the phone won't boot past the lg logo screen (no verizon screen, just turns off)
2. Held down the power button and volume down button, and able to get into recovery.
3. Tried safe mode -> boots to lg logo and turns off
4. Tried wipe cache -> boots to lg logo and turns off, does it twice
5. Tried USB debug -> shows the android icon, looks like its working, turns off
6. Finally tried factory data reset -> goes through the "are you sure" screen; select yes; shows android icon, looks like its working, turns off
7. Tried holding down the up button and plugging it into a computer to reinstall firmware, shows logo and turns off
8. When I plug the phone into the wall, it charges normally. Simply won't turn on past that.
I'm not sure what else I can do to the phone. Is there a way to factory reset from a pc or mac without the phone being on? Will I just have to take it to the tech store so they can do whatever magic they seem to possess? I already plan on never getting another android after the issues with this phone (and many androids before this one), but I need this phone to last until December.
Sorry for rambling and thank you for any help!
Bump
Hey everyone who reads this.
I'd like to start my topic with apologising if I post this in the wrong section.
So, I have a LG Spirit H440N LTE for about 3 years now, maybe a little less. I've always taken good care of it, both physically and in updates / security wise aswell.
My phone has been working flawlessly until the last 2 days. 2 days ago i was charging my phone, and when it vibrated (meaning its 100%) I pulled the cable off, and pressed the power button (power button locks - unlocks the screen) the screen didn't turn on. I was like "wow that's strange" but didn't care much, i just kept pressing the button every 5-6 seconds, nothing.
At that point I pulled the battery out, let it sit for a short time and then put it back, start the phone, I felt the vibration (meaning it's starting up) but no screen, so my first idea was that I need to get a new firmware and completely reinstall my phone, as it seems like it got bricked.. for no reason, by itself ? Strange thing but I accepted it and literally been googling for 9 hours now and I find more and more issues.
After I got LG FlashTool, drivers, and even 3 different firmwares, I wanted to start the phone in download mode to start upgrading, but even though I held down "volume up for 5 seconds and then put the usb cable in" nothing happened, no screen, my PC didn't recognise the phone either.
So I got a little bit mad and pulled the cable out from the phone, I wanted to remove the battery, but out of nowhere the phone suddenly started loading in, screen working completely fine, i could do whatever i want, so my first thing was to do a hard reset. After the hard reset I set up my usual stuff (important apps etc) and I locked the screen so my battery won't go down. Little did I know, I ****ed up again, because ever since that happened, I can't get my screen to work again. I tried everything I could but my PC still doesn't recognise the phone (even after a LOT of drivers being installed), charging the phone doesn't do anything. Regardless if I remove - put back the battery no screen, no screen in download - hard reset mode either, it's just completely black.
I'd like to have some sort of help, because I am just completely out of ideas, I really feel like a firmware change could fix the phone, but if the computer doesn't recognise it, I have no idea what to do.
rawon3 said:
Hey everyone who reads this.
I'd like to start my topic with apologising if I post this in the wrong section.
So, I have a LG Spirit H440N LTE for about 3 years now, maybe a little less. I've always taken good care of it, both physically and in updates / security wise aswell.
My phone has been working flawlessly until the last 2 days. 2 days ago i was charging my phone, and when it vibrated (meaning its 100%) I pulled the cable off, and pressed the power button (power button locks - unlocks the screen) the screen didn't turn on. I was like "wow that's strange" but didn't care much, i just kept pressing the button every 5-6 seconds, nothing.
At that point I pulled the battery out, let it sit for a short time and then put it back, start the phone, I felt the vibration (meaning it's starting up) but no screen, so my first idea was that I need to get a new firmware and completely reinstall my phone, as it seems like it got bricked.. for no reason, by itself ? Strange thing but I accepted it and literally been googling for 9 hours now and I find more and more issues.
After I got LG FlashTool, drivers, and even 3 different firmwares, I wanted to start the phone in download mode to start upgrading, but even though I held down "volume up for 5 seconds and then put the usb cable in" nothing happened, no screen, my PC didn't recognise the phone either.
So I got a little bit mad and pulled the cable out from the phone, I wanted to remove the battery, but out of nowhere the phone suddenly started loading in, screen working completely fine, i could do whatever i want, so my first thing was to do a hard reset. After the hard reset I set up my usual stuff (important apps etc) and I locked the screen so my battery won't go down. Little did I know, I ****ed up again, because ever since that happened, I can't get my screen to work again. I tried everything I could but my PC still doesn't recognise the phone (even after a LOT of drivers being installed), charging the phone doesn't do anything. Regardless if I remove - put back the battery no screen, no screen in download - hard reset mode either, it's just completely black.
I'd like to have some sort of help, because I am just completely out of ideas, I really feel like a firmware change could fix the phone, but if the computer doesn't recognise it, I have no idea what to do.
Click to expand...
Click to collapse
You might be having hardware issues, such as a faulty power button. If you are the type of user that frequently presses the power button to lock/unlock the screen, this leads to excessive wear on the button components, this is why some users prefer to use the "tap to sleep" and "tap to wake" feature, to avoid wearing the power button out. On my LG, this feature is called "KnockOn", it's located in Accessibility settings.
Sent from my LGL84VL using Tapatalk
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
bigblkyj said:
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
Click to expand...
Click to collapse
If what you've described is correct, all of the solutions involve flashing the stock firmware which will of course wipe the device.
Were your photos not stored in a folder on the SD card?
There is a chance you can recover the device using Samsung Kies with the emergency recover option but if you've encountered the "no command" screen it's not looking good.
Unfortunately I did have an SD card installed, but I normally kept my camera pics on the phone's memory, since I have had an SD card fail as well and lost everything on there.
So this took an unexpected turn yesterday pretty much right after posting this... I've been messing with the phone, unplugging the battery each time, and have managed to get into different menus which kept making me think that something still had to be working if I could do that. Well, after leaving the No Command message on the screen it magically booted into the Recovery menu with (finally) the option to wipe the cache partition, which I did and rebooted normally. Believe it or not, it booted normally and into the OS like nothing ever happened?!
I instantly plugged it into my PC and ran Smart Switch which started taking a backup! About 25% though the device restarted again and was really warm to the touch on the RF covers inside. Bummer...
So I figured heat was now the issue for some reason... I waited for it to cool and then reinstalled the SD card and figured, if I could get it to boot long enough, the SD card is a quicker transfer and I'd just use ES File Explorer to try and do a photo dump to the SD card and see how far it would get. It actually made it all the way through and gave me enough time to grab some other stuff before getting hot and restarting again.
I believe the overheating is being caused by my opening of the device though... Currently I have the antennas removed and the speaker so that I'm able to quickly access the battery connector (which BTW seems to be the trick here to this working) But inadvertently, without the larger wireless charging coil in place, it relieved the pressure on the motherboard and broke the thermal paste connection between the chipset and the copper heatsink (I didn't tear it down further to check, but I can hear the 'sticking and peeling' when you press down on it).
I think what I'm going to do is apply pressure with a chip clip or something similar (non conductive) and see if I can grab a backup again before it restarts. After the cache wipe the phone seems to understand that it's plugged in and charging now which is a new thing as well...
Sorry for the long winded posts, but if this at all helps even one person with the same situation as I have, maybe that'll be worth getting lost in here