I recently gave my Verizon GSIII to my father, and it was rooted/unlocked/TWRP recovery. I gave it to him running a stock ROM (Clean ROM I believe) and no tweaks. It was 4.3 android version. All was well since April or so, but today he called me (from a different phone) with these symptoms:
1) He got a notification that made his notification LED pop on. He usually used the home button to turn on screen, and that didn't work. He tried the power button, and that didn't turn on the screen either.
2) I called his number and it did NOT go straight to voicemail. It rang 5 times and then went to VM. On his end, he heard and saw nothing. So the phone must have power I assume?
3) I had him hold down the power button for about 30 seconds - nothing seemed to happen.
My question is this: what should I do to try and troubleshoot this issue? I'm seeing him tonight for a little while, and I want a plan of attack. Should I try pulling battery/SIM/SD? Trying to boot into download or recovery mode? Anyone heard of this issue before? Thanks in advance for your help!
PsiPhiDan said:
I recently gave my Verizon GSIII to my father, and it was rooted/unlocked/TWRP recovery. I gave it to him running a stock ROM (Clean ROM I believe) and no tweaks. It was 4.3 android version. All was well since April or so, but today he called me (from a different phone) with these symptoms:
1) He got a notification that made his notification LED pop on. He usually used the home button to turn on screen, and that didn't work. He tried the power button, and that didn't turn on the screen either.
2) I called his number and it did NOT go straight to voicemail. It rang 5 times and then went to VM. On his end, he heard and saw nothing. So the phone must have power I assume?
3) I had him hold down the power button for about 30 seconds - nothing seemed to happen.
My question is this: what should I do to try and troubleshoot this issue? I'm seeing him tonight for a little while, and I want a plan of attack. Should I try pulling battery/SIM/SD? Trying to boot into download or recovery mode? Anyone heard of this issue before? Thanks in advance for your help![/QUOTE
If youd just included the led color. Could have saved you alot of time. As is. Could be anything.. Sorry. More input please
Click to expand...
Click to collapse
Related
My phone runs perfectly fine until I enable Gps location. Once I enable GPS location, it freezes, then it reboots my phone and it slowly do a system check, then it continuously rebooting the lg logo screen. I tried taking out the battery and put it back in, even took out my battery for a day and it still does the same. I'm not sure if it's the hardware problem, but it's a pretty rare case, since I read most of the threads in forums, people said it can be fix once you pull out the battery, but somehow it's not working for me. Anyone knows the reason why? Btw, my phone is not rooted or used any 3rd party program.
Ah. Posted too soon. There's a master reset that I believe is Power and Volume Up. Try that.
Unfortunately, it's still not working. Is there any other possible way? Or else I have to call in and return it.
Try turning off the phone, then press power + vol down and hold it until you see the word android. This should do the factory reset.
efrem989 said:
My phone runs perfectly fine until I enable Gps location. Once I enable GPS location, it freezes, then it reboots my phone and it slowly do a system check, then it continuously rebooting the lg logo screen. I tried taking out the battery and put it back in, even took out my battery for a day and it still does the same. I'm not sure if it's the hardware problem, but it's a pretty rare case, since I read most of the threads in forums, people said it can be fix once you pull out the battery, but somehow it's not working for me. Anyone knows the reason why? Btw, my phone is not rooted or used any 3rd party program.
Click to expand...
Click to collapse
It sounds like the permissions are not correct, or perhaps that your ROM was not flashed correctly. I have seem this problem happen numerous times due to bad firmware flashes or ROM issues. I would just download a new copy of the latest CM 7 ROM or whatever your favorite ROM is and flash it through CWM.
Thanks guys for the help. I found out that you have to hold down first then power button for around 30 second and then the droid animation comes out. I was so close to returning it. Thanks!
my girls volume wont turn on at all? anyone ever hear about this problem? it isn't rooted....
not sure if it will help, but try this: from the home screen, press the menu button, then choose settings>sound>volume, and check the settings for the various volumes, i.e incoming call, media, system, etc. when my phone was stock like hers, sometimes one or more of those volumes got pushed down to 0 for some reason... it was annoying, and it seemed to happen especially to my notifications volume every time i rebooted the phone! hope that helps
I'm having the exact same issue
Hey everyone. So I bought a sidekick 4g on craigslist the other day. I checked it out and thought everything was okay, but I was wrong. So far no response from the jerk who sold it to me without telling me about this problem.
The phones volume up key doesn't work 90% of the time. If I reboot the phone or leave it off for a while, the volume up key will work for a few minutes and then stop again. The funny thing is the volume up key works when I want to reboot (holding vol.up + vol.down and power button at the same time).
So is there any fix for this? Will rooting it and loading a rom fix it? Also I am new to all of this, is it even possible to root and load generginger 2.0 with a broke volume up button? The phones firmware is all up to date.
Thanks for any info and help everyone.
i'd suggest using this thread: http://forum.xda-developers.com/showthread.php?t=1275116
root the phone, and then go back to stock with the heimdall and see if that fixes the problem. and if it does then you should try rooting it again and install one of the Custom ROMs because the stock OS on this phone is garbage out of the box.
but i'm no expert either, it just seems strange that only when its been on for a bit that it stops working. that it works when you boot it seems to suggest that its a software issue? somebody help me out here guys lol
I have an unlocked HSPA+ Galaxy Nexus imported from the UK to the US. Ordered from Negri Electronics.
It's not rooted or modded in any way.. Mainly because I don't know how to. As far as I know, it's running stock ICS.
I was using it normally, (using the fb messenger app if it makes any difference) when it suddenly rebooted by itself. The Google logo comes up, then the start up animation, and sometimes the home screen will appear but is not touch sensitive (i cannot slide it to unlock), and then it 'hangs' and the screen goes black. Repeat.
I've tried to fix this by myself and there's a video on youtube (sorry, noob here. can't post links. video is by robbidwv and title is "my galaxy nexus won't boot..") of the same problem that I have, but the posted solution doesn't work for me.
So far, I have entered Coin Mode and pressed Start. Entered Fastboot mode and gone into Recovery Mode (no options appear after that. it just starts booting up and the loop begins), and I've also tried Restart Bootloader.
I've almost given up. Now all I want is to extract my SMS, if they're still on my phone. I can't access the folders on my computer because it won't boot up and connect. Is there a way that I can extract my SMS by using DOS in either Coin Mode or Fastboot mode?
Or even better, does anyone have a solution to this boot loop problem? I'll contact Negri Electronics tomorrow and hopefully they can send me a replacement.
Please help!! Thanks
that problem just started happening with me an hour ago!!
i hate this!!
we need a solution please!
Hey guys, sorry about the issue.the major problem I see here is you wanting to retrieve your txt messages, which might be possible with a little Modding, but if yourwilling to lose them to get a working phone back, then this is what your going to have to do. Make sure your phone is completely off. Hold the 2 volume buttons and the power button together. You will get into a mode with an android Guy. Press the volume button up or down until it says reboot recovery at the top. Press the power button. It will rebootand come to a screen with an android. Hold volume up,down and power at the same time. A menu will come up. Go down to wipe data. Click it, and after it is done reboot. Your phone should work now.
If this helped you, or you simply appreciate me taking the time to write this out then please press the thanks button
Hey!
Thanks. Yeah I 'fixed' it already. I was just about to post something similar. After a while I just gave up on trying to recover my data. Good thing that Google syncs everything so the only issue would be recovering my messages, which I decided weren't worth sending it in for a repair which would probably not be able to recover anything anyway.
The thing I didn't know about was to press power + volume up WHILE on the recovery screen. I thought navigating to the recovery screen was it!
Still, this kind of sucks. I love my GNex, but I can't help but be slightly pissed seeing that my crappy iPhone 3GS never did this in the 2 years I had it. Oh well, hope it doesn't happen again!
hey guys! i also did a complete wipe on my phone and got it working again!
but i wonder why this happened in the first place?
last application i installed before the crash was double twist, i dunno why but i feel that it was the reason behind the boot loop!
Sorry for reviving this thread, but I just had this happen to me TWICE!
It happened to me first last Monday, the 23rd - the phone crashed when trying to send an email with an attachment - and went into a boot loop - Google logo would appear, no make it to the animation, and reboot....
I performed a full reset and things worked again. I didn't install all the apps I had before - figuring it must have been due to some app messing with the OS.
Well, it happened again to me yesterday! I was connecting to my bluetooth headset when the phone crashed and went into the boot loop. Full reset worked again, and I've installed even fewer apps - essentially only those that I use on a daily basis.
My phone is still on 4.0.1 and I'm hoping once 4.0.4 is pushed this may get resolved? I have a canadian GNex from Negri. I will call them again (I called the first time, but when the full reset worked I never contacted them again).
I would like to this this is a software issues, and not hardware.
I have the same problem. If you figure it out let me know.
Today my phone also entered a boot loop: [Google logo]->[black screen]->[vibration]->[Repeat]
I tried Recovery Mode, but this is what happens: (sorry for the link but I am not trusted with powerful tools such as outside links apparently, as I have not yet reached the maturity of a person with eight posts... )
dl(dot)dropbox(dot)com/u/53568097/Android.jpg
This is what I see when I navigate to Recovery Mode
For a split second I can see an image of an Android with spinning cogs in his innards, but then this little sad fellow appears. WTF is this?
EDIT:
Oh, and I'm running Android stock 4.0.2, never rooted or unlocked, Swedish. At the time when the phone started doing this, I was using Endomondo, and was about to set off on my bike when it died on me.
Stock ROM galaxy nexus bootlooping after wiping data also.
Hi,
My GNex went into a bootloop so i searched xda and found that factory reseting would be helping my prob. But after wiping the data also its still in going through the loop . Please help .:crying:
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.
Hi everyone, I'm throwing this out there because I've run out of ideas about what has just happened to my U12+ (64gb) today.
I woke up and used my phone as normal, caught up on Twitter and the news, the usual apps etc. nothing untoward. The same routine I've had with my phone for the past 18 months of owning it with zero issues. My handset is stock OS (Android 9) and so not rooted or anything like that. Virtually all the apps I use are standard issue from the Play Store, nothing really "out there" and I have BitDefender installed to look after security. Same setup I've had for over a year. The battery was around 35% so I plugged it into my wall charger while I went off to grab some breakfast. When I returned a couple of hours later the light on the handset was green, I unplugged the charger and attempted to unlock it with my fingerprint.
The phone asked for my PIN, no big deal so I entered it. Black screen. Tapped the power button again, it requested my PIN again, I entered and... black screen. Okay, I was a little bit concerned now. I held down the power button so the haptic buzz occurred, held for 10/20/30 seconds, a minute... nothing, no restart. Tap the power button and it asks me for my PIN again and shows yet another black screen. I held down Power + Volume Down but again, nothing and no restart.
I asked someone to call me, the screen came to life and I could take the call but each time I tried to pull down the system tray in order to try and reach Settings to restart it asked me for my PIN, I entered it = black screen. The call was unaffected.
I removed my SIM + microSD card tray = same deal as above.
The phone is clearly responsive in some way and the screen does display to ask for my PIN but I can't get into it in order to reboot it. Extremely worrying.
Does anyone have any advice? At the moment I am faced with the prospect of simply allowing the battery to run out so the phone shuts down naturally but that is going to take the best part of 2 days.
I'm really disappointed because I was planning another 1-2 years use for this handset as I just bought a 1TB microSD card which has been fine in the phone for weeks so I don't think that's the cause. It is also genuine SanDisk.
Any suggestions or advice? Thanks in advance.
Hello, I hope you have made a backup with google backup recently... This does not happen often on android, but sometimes the system could have a problem. You can try this go the bootloader with the power and volume buttons , after recovery.. after apply a wipe data/ factory reset.. is will make a factory reset of your phone except the sd card. You should by fine after that and profit again.
Thanks, I appreciate your reply.
At the moment I am running the battery down until the handset switches off naturally. When it comes back on I will try to launch the phone normally, if that doesn't work I'll run the battery down again and attempt to reach the bootloader.
My photos are backed up to the cloud, I may lose some text messages but I managed to transfer the majority of my 2FA over to another Android device bar one.
At the end of the day if it's a choice between wiping it or a bricked/unusable handset then I don't really have one. What a pain.
Magimix^ said:
Thanks, I appreciate your reply.
At the moment I am running the battery down until the handset switches off naturally. When it comes back on I will try to launch the phone normally, if that doesn't work I'll run the battery down again and attempt to reach the bootloader.
My photos are backed up to the cloud, I may lose some text messages but I managed to transfer the majority of my 2FA over to another Android device bar one.
At the end of the day if it's a choice between wiping it or a bricked/unusable handset then I don't really have one. What a pain.
Click to expand...
Click to collapse
At the moment I am running the battery down until the handset switches off naturally <----- why that??? Even on a bootloop or a black screen you can reset it hold the buttons power and the volume, you can go on the bootloader.
Max128 said:
At the moment I am running the battery down until the handset switches off naturally <----- why that??? Even on a bootloop or a black screen you can reset it hold the buttons power and the volume, you can go on the bootloader.
Click to expand...
Click to collapse
The first thing I tried to do was hold down the power button or the power button in tandem with the volume buttons but the handset won't restart. I tried loads of times holding it for different amounts of time and... nothing.
Trust me, I tried.
The only way I can get the device to switch off is by draining the battery. I'm almost at 20% so it shouldn't be too much longer.
Well I already got a black screen after flashing a module magisk.. I have holding the power button and the phone have restart no problem, same thing on bootloop. You need to be sure to hold the button correctly.
Max128 said:
You need to be sure to hold the button correctly.
Click to expand...
Click to collapse
Yeah, I'm certain I was holding the buttons correctly. I tried about 20 times using different combinations just to be sure but the device would not restart. The haptic shock buttons are one of my least favourite features of the u12+, it's got to be said.
Anyway, the phone ran out of battery about 15 minutes ago. I left it alone for few minutes and switched it back on. It allowed me back in and the device appears to be fully functional again. I can unlock by thumb print, face or PIN without issue.
Basically, it's fixed. My only concern is I have no idea what caused it or if it will happen again.
Thanks for offering help though, I appreciate it. I'm not sure if this thread can be closed/locked now? I'll look into that.
Cheers.
Yes.. i love the buttons too i never got a problem with this. Great if is fixed! Maybe make a factory reset the next time.
I am wondering if the new flagship have haptic buttons too.. htc will announce it Tuesday.