5.1.1 Update / Phone shuts off automatically - Nexus 5 Q&A, Help & Troubleshooting

Can someone please help me. After the 5.1.1 OTA update my phone randomly shuts off (like pulling the plug off an appliance). I already did the factory reset and it still has this problem.

I have the same problem, and the only way to switch it back on, is to plug it in the charger, wait for the battery icon to appear, and then try to switch it on.
It shut off twice while I was using the camera, and I thought it was caused by the HDR+ bug, but it also happened twice later, while idle in my pocket.
Anyone else seen this?
Android 5.1.1, stock, Rooted.
Sent using Tapatalk.

Same
I have the same problem. For the last two weeks it only crashed when I was using my camera. Yesterday it crashed while I used maps and gmail. This is very frustrating and have made the phone useless. I'm really surprised this has not gotten more attention.
I have seen people say that replacing the battery has solved the problem.

igimmi said:
I have the same problem. For the last two weeks it only crashed when I was using my camera. Yesterday it crashed while I used maps and gmail. This is very frustrating and have made the phone useless. I'm really surprised this has not gotten more attention.
I have seen people say that replacing the battery has solved the problem.
Click to expand...
Click to collapse
The battery has been replaced about a month ago.
I've used all the tricks I know, (wipe cache, dalvic, clear data from some core apps).
There seems to be no pattern to the lock-ups. It happened 5 times since last Saturday, when it first appeared.
God have mercy on our phones [emoji26]
Sent using Tapatalk.

kted said:
The battery has been replaced about a month ago.
I've used all the tricks I know, (wipe cache, dalvic, clear data from some core apps).
There seems to be no pattern to the lock-ups. It happened 5 times since last Saturday, when it first appeared.
God have mercy on our phones [emoji26]
Sent using Tapatalk.
Click to expand...
Click to collapse
Are you running 5.1.1?
I'm afraid to update my wife's Nexus 4 to 5.1.1.

Damn 5.1.1

I had no issues with 5.1.1, so you all probably should just flash factory images through fastboot.

I am with stock 5.1.1, rooted, xposed+gravitybox, after a clean install.
It worked fine at first, the random shutdowns started a week ago.
What annoys me most, is that after the shutdown, the only way to power on the phone, is to plug it in a charger. As soon as the battery icon shows, you can power on. It happened again a few hours ago, during a photo (with HDR+), and I had to wait till I returned home and plugged it in.
Sent using Tapatalk.

kted said:
I am with stock 5.1.1, rooted, xposed+gravitybox, after a clean install.
It worked fine at first, the random shutdowns started a week ago.
What annoys me most, is that after the shutdown, the only way to power on the phone, is to plug it in a charger. As soon as the battery icon shows, you can power on. It happened again a few hours ago, during a photo (with HDR+), and I had to wait till I returned home and plugged it in.
Sent using Tapatalk.
Click to expand...
Click to collapse
I wonder if we have to wait for an official bug fix from Android.

I have this same problem, I did have issues prior to the 5.1.1 update with having to press the power button 2-3 times OCCASIONALLY to present the lockscreen and have it stay on so unlock (it would present itself and go off the first few times). But that was a pretty intermittent problem, and not that annoying.
Now with 5.1.1 OTA instead of that issue, merely tapping the power button brings up the power off dialogue and the phone automatically shuts off. This seems to pop up every other day or so. Seems like a pretty horrid bug. Trying a cache partition wipe again now.
My Nexus 5 on lollipop has been all sorts of problems. I love the new design and changes, but reliability is gone to cow patties

HEY!!!
kted said:
I am with stock 5.1.1, rooted, xposed+gravitybox, after a clean install.
It worked fine at first, the random shutdowns started a week ago.
What annoys me most, is that after the shutdown, the only way to power on the phone, is to plug it in a charger. As soon as the battery icon shows, you can power on. It happened again a few hours ago, during a photo (with HDR+), and I had to wait till I returned home and plugged it in.
Sent using Tapatalk.
Click to expand...
Click to collapse
Xposed for 5.1.x is unofficial, even Official Xposed for 5.0.x is in alpha phase, so don't use it yet if you're aiming for stability.
igimmi said:
I wonder if we have to wait for an official bug fix from Android.
Click to expand...
Click to collapse
tesla45 said:
I have this same problem, I did have issues prior to the 5.1.1 update with having to press the power button 2-3 times OCCASIONALLY to present the lockscreen and have it stay on so unlock (it would present itself and go off the first few times). But that was a pretty intermittent problem, and not that annoying.
Now with 5.1.1 OTA instead of that issue, merely tapping the power button brings up the power off dialogue and the phone automatically shuts off. This seems to pop up every other day or so. Seems like a pretty horrid bug. Trying a cache partition wipe again now.
My Nexus 5 on lollipop has been all sorts of problems. I love the new design and changes, but reliability is gone to cow patties
Click to expand...
Click to collapse
Regardless, you all need to go back to stock, a fresh start, by flashing factory images from Google. I'm sure you know how to do it, so take your backups and go do it.

beekay201 said:
HEY!!!
Xposed for 5.1.x is unofficial, even Official Xposed for 5.0.x is in alpha phase, so don't use it yet if you're aiming for stability.
Regardless, you all need to go back to stock, a fresh start, by flashing factory images from Google. I'm sure you know how to do it, so take your backups and go do it.
Click to expand...
Click to collapse
The thing is it started all of a sudden, a week ago...
Sent using Tapatalk.

I'm going to run in SAFE MODE for a day and see how it goes. Maybe it's an app is not working well with 5.1.1 What I noticed that each time it shuts off ALL the apps have to be optimized again.

GripR said:
I'm going to run in SAFE MODE for a day and see how it goes. Maybe it's an app is not working well with 5.1.1 What I noticed that each time it shuts off ALL the apps have to be optimized again.
Click to expand...
Click to collapse
Safe mode didn't work for me.

My problem is not the same, it seems.
It happens one in every two times I take a photo with HDR+.
The phone switches off instantly, and the only way to switch it on again, is to plug it into a charger.
Sent using Tapatalk.

Safe mode didn't work...

I have the same issue.
Started like a week ago while came back from M preview to cataclysm. Was very frustrating and made a clean install of stock, reboot continued, more accurately it seems like a reboot with the Google logo, and then it turns off.
Happens with and without xposed.
What I have noticed though is that it happens much much less when WiFi is off.

Any updates on this?
Happens to me too. Just shuts of. Not like a reboot... just goes of. When I try to power it on again it begins to boot, but after a while on the bootanimation it shuts of again. Only If plug it in the charger it boot completely again. (mostly with optimizing all apps afterwards, but not every time. I also noticed that when maybe the battery is at 50 when it is shutting down, then after I plugged it in the charger for like 5 minutes and boot it, Battery is showing arround 90% already. (can't be, right?... ?)
So I think it's the battery, Imo.
Tomorrow I will clean flash the Google 5.1.1 stock factory image to check if it happens there too. If so then I have to send it in I guess...
I'm on BlissPop 5.1.1 + ElementalX atm, but tried many things already. Once without ElementalX, once with stock bliss kernel and a clean flash after factory reset. I even flashed the 5.0.1 bootloader and radio again + the 5.0.1 rom I used a few weeks before where everything was ok. (ExodusRom) but it happend too. So it almost must be the hardware (motherboard, battery etc.)
Greetings, Strainhunter
Gesendet von meinem Nexus 5 mit Tapatalk

strainhunter said:
Any updates on this?
Happens to me too. Just shuts of. Not like a reboot... just goes of. When I try to power it on again it begins to boot, but after a while on the bootanimation it shuts of again. Only If plug it in the charger it boot completely again. (mostly with optimizing all apps afterwards, but not every time. I also noticed that when maybe the battery is at 50 when it is shutting down, then after I plugged it in the charger for like 5 minutes and boot it, Battery is showing arround 90% already. (can't be, right?... )
So I think it's the battery, Imo.
Tomorrow I will clean flash the Google 5.1.1 stock factory image to check if it happens there too. If so then I have to send it in I guess...
I'm on BlissPop 5.1.1 + ElementalX atm, but tried many things already. Once without ElementalX, once with stock bliss kernel and a clean flash after factory reset. I even flashed the 5.0.1 bootloader and radio again + the 5.0.1 rom I used a few weeks before where everything was ok. (ExodusRom) but it happend too. So it almost must be the hardware (motherboard, battery etc.)
Greetings, Strainhunter
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
I also think it's the battery. I will be be changing the battery soon. if there is any improvements after that I will provide update.

So today, my phone kept dying when the battery was around 40%. So I said screw it and got the battery replaced.
The old battery (on the right) looked bloated compared to the new one. The battery could have been the cause of all our problems.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Related

[Q] Stuck on Asus boot screen

Hey folks, need a bit of help here.
I have a weird problem. I took my TF off of charge a few hours ago and laid it on the table. I just came back to it now, and its on the "ASUS - Inspiring Innovation. Persistent Perfection" and stuck. The progress indicator is about half way around.
I press and held the power button for 5-10 seconds, then 30 seconds, then a minute, no change. I press and held the Vol- and power for 10/30/60 and no change. It just won't budge from this screen way now.
Is there a way to forcefully power off the tablet? Or do I have to wait for the battery to drain out?
It was working fine before this, and I didn't make any changes recently except ran a few application updates last night. Any suggestions?
I'm rooted with Revolution HD rom on it. I can't get into recovery, and no response from ADB. Its just stuck where it is.
So you can't even get into recovery with the manual button combo?
What about your serial number? NVFlash compatible?
baseballfanz said:
So you can't even get into recovery with the manual button combo?
What about your serial number? NVFlash compatible?
Click to expand...
Click to collapse
I can't get any response out of it all. Serial number on the bottom is B60K**, its nvflash compatible (I did a restore back to stock with nvflash not too long ago), but, I can't get it to "reboot" at all to put it into APX mode.
I'm assuming once the battery dies and the thing shuts off I may have a few more options, but right now I'm stuck here.
Edit: Here is the screen its stuck on (progress ring at the bottom is frozen)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Holding just the power button should eventually power it off
Sure the power button is working ?
*Detection* said:
Holding just the power button should eventually power it off
Sure the power button is working ?
Click to expand...
Click to collapse
Well, I guess at this point I can't gaurentee 100% that its working. However, the power button was always working until this happened. I haven't had any other issues other than the deep sleep issue with ICS.
Yeah holding down your power button should turn it off I had this happen to me like a week ago.
Thats working fo me, but it keeps coming back every day, very annoying.
Sent from my Transformer TF101 using xda premium
tegezee said:
Yeah holding down your power button should turn it off I had this happen to me like a week ago.
Click to expand...
Click to collapse
I wish it was that easy for mine, no matter how long I hold the power button, nothing happens. I'm sitting here now waiting for the battery to drain out. Will probably take a few days seeing that I just finished charging it when this happened.
Just to give an update, I left it for overnight, and when I woke up this morning, the battery had finally died. So, I plugged in the charger, and the tablet booted up fine.
Power button, volume buttons, etc, work fine. I have no idea what caused this problem, but i'm glad its working now.
Should I go back to stock to be safe? Or am I fine with ARHD?
My t101 has done the exact same thing. I woke up an hour ago from a nite of charging and now it is stuck at the ASUS loading logo. It was at first loading, the wheel spinning, then it stopped. I can not turn it off nor enter recovery . It cannot do anything. adb will not recognize it at all. I havent tried nvflash.
Rooted & running cwm.
Any suggestions or am I sol until it manually dies form no juice?
8milerd said:
My t101 has done the exact same thing. I woke up an hour ago from a nite of charging and now it is stuck at the ASUS loading logo. It was at first loading, the wheel spinning, then it stopped. I can not turn it off nor enter recovery . It cannot do anything. adb will not recognize it at all. I havent tried nvflash.
Rooted & running cwm.
Any suggestions or am I sol until it manually dies form no juice?
Click to expand...
Click to collapse
Sounds like the exact same issue I had. Nvflash wasn't possible for me either because when it was stuck on the loading screen with the spinner frozen, I couldn't power it off, enter recovery, or anything.
I have no suggestions other than wait for the battery to die. My only fear was that the logo and spinner being lit on the screen for such a long period of time would cause some sort of burn-in. But, luckily, screen technology these days that doesn't seem to be an issue. Mine suffered no ill-effects.
Thank you for the help. I tried NVFlash and it was a no go as well. My battery was at 100% when this happened, hopefully it isnt a 2 day wait to drain it. I have only had the thing since the 19th of this month so I may just return it for another one as they have a 15 day return policy. I also wrote Asus about it. Seems they are aware because they on their support site have this listed as an issue.
Either way lesson learned. I will no longer leave it connected to the keyboard dock charging all night...
---------- Post added at 03:42 PM ---------- Previous post was at 02:49 PM ----------
Update:
Ok, I got it to reboot.
Using Windows 7 I hooked up the tf101 with the it attached to the Keyboard dock to the usb
I went to device manager, options, Add legacy hardware.
Clicked Choose from list
Added Android ADB interface, Android adb composite interface.
Then added Android adb bootloader interface.
Restart pc
Held power and it finally powered down.
I had android sdk installed before hand as well.
Hope thi helps anyone if it happens to them.
I believe it's Volume up and power for 10 seconds that's a could boot. I hadn't seen anybody mention that yet so thought I would through it it.
chadcspencer said:
I believe it's Volume up and power for 10 seconds that's a could boot. I hadn't seen anybody mention that yet so thought I would through it it.
Click to expand...
Click to collapse
Yeah, I tried that as well at the time, no luck.
So, just to update. After this happened the first time, I let the tablet battery die out, after which it booted up fine. About a week later, the exact same thing happened again. So, thinking it for some reason was related to the custom rom i was running, I nvflashed back to stock. However, I still have the issue from time to time. Its very frustrating, and I'm not quite sure if its a software issue or a hardware issue.
I'm gonna leave it for a little bit, but if it continues to happen on a regular basis, I'll have to call Asus.
chadcspencer said:
I believe it's Volume up and power for 10 seconds that's a could boot. I hadn't seen anybody mention that yet so thought I would through it it.
Click to expand...
Click to collapse
This does not do anything here
Same boat, 3rd time coming back from RMA. My other has absolutely no issues, Asus refuses to repair or fix the one which has had all the issues...
Stuck on this all the time, and I'm on stock :/
cquilliam said:
Yeah, I tried that as well at the time, no luck.
So, just to update. After this happened the first time, I let the tablet battery die out, after which it booted up fine. About a week later, the exact same thing happened again. So, thinking it for some reason was related to the custom rom i was running, I nvflashed back to stock. However, I still have the issue from time to time. Its very frustrating, and I'm not quite sure if its a software issue or a hardware issue.
I'm gonna leave it for a little bit, but if it continues to happen on a regular basis, I'll have to call Asus.
Click to expand...
Click to collapse
When using some custom kernels/roms the boot process stucks after the Asus logo when the tablet is connect to a PC or power supply.
To solve this disconnect the USB / powercable before booting.
Or flash a 9.2.2.3. based kernel like guever-test13 (or higher).
Had the same problem here. I tried to solve this myself, but after 4 days I nvflashed all stock and RMA'd it.
They sent me a new tab... But now it's all okay! I just can't exactly remember how I bricked my tab and this is frightening me.. I don't want to do the same error!
Sent from my Transformer TF101 using XDA
I have actualy had the same problem occor and what i did was hold power then boot holding power down then switch to press up to enter CWM recovery then just select reboot device now... works great, had to use this method 3-4 times once today
Sent from my Transformer TF101 using XDA Premium App
I'm having this problem with my non-rooted Transformer on ICS.
Usually holding the power button down will get it boot normally.
But then randomly when I leave it alone for a while, it will re boot but then get stuck in a loop at the 'Eee Pad' screen with the screen going off every 15 seconds or so. To then get it to re boot then I have to hold the power down button when the screen is off until it comes back on, and then hold the power button down again afterwards for about 10 seconds when it is on for it too boot normally again.
I was hoping that rooting would fix that issue, but it seems not.

[Q] How to debug Infuse restarting randomly?

Hi,
I just bought a 2nd hand infuse 2 weeks back. I was using the stock GB for a while, and the phone was restarting sometimes. To fix this and get ICS features, I rooted and moved to the ICS CM9 ROM. Still the restarting didn't go away. I flashed everything before installing the rom. So, I guess this can't be an issue with either of the roms but probably something else. Also, when the restart happens the battery gets drained significantly.
After some searching, I saw in some threads that memory issues can do this or probably a bad app (I only have popular apps only though). I was wondering is there a way whether I can some info to debug the problem, when this restart happens?
Any help is greatly appreciated.
It might not be a ROM issue but a faulty power button. The are several threads on this. You may want to search "power button".
Sent from my SGH-I997 using xda premium
psal217050 said:
It might not be a ROM issue but a faulty power button. The are several threads on this. You may want to search "power button".
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Hmmm, the power button seems to work alright. But if the power button is always pressed, I shouldn't be able to press it again and make it function properly, right? All the functions of the power button seem to be doing OK, i.e. menus pop up and it puts the phone to sleep mode, etc.
Is there anything more I can check to confirm that it is not the power button?
Is there a way to get a thread dump or any other log at the time of restart?
A few more details -
- I believe it goes to a boot loop when it restarts (loops from the cm logo back to samsung
- goes to a charge loop if I connect to a charger
- long holding the power button at this time restarts the phone and brings it back to normal
- I notice it happens a lot at the lock screen, but it happens at other times too,still to figure out a pattern
mccloud35 said:
Is there a way to get a thread dump or any other log at the time of restart?
A few more details -
- I believe it goes to a boot loop when it restarts (loops from the cm logo back to samsung
- goes to a charge loop if I connect to a charger
- long holding the power button at this time restarts the phone and brings it back to normal
- I notice it happens a lot at the lock screen, but it happens at other times too,still to figure out a pattern
Click to expand...
Click to collapse
Try to get a logcat using aLogcat from the marketplace.
mccloud35 said:
Hi,
I just bought a 2nd hand infuse 2 weeks back. I was using the stock GB for a while, and the phone was restarting sometimes. To fix this and get ICS features, I rooted and moved to the ICS CM9 ROM. Still the restarting didn't go away. I flashed everything before installing the rom. So, I guess this can't be an issue with either of the roms but probably something else. Also, when the restart happens the battery gets drained significantly.
After some searching, I saw in some threads that memory issues can do this or probably a bad app (I only have popular apps only though). I was wondering is there a way whether I can some info to debug the problem, when this restart happens?
Any help is greatly appreciated.
Click to expand...
Click to collapse
I have the exact same problem. Please let me know what you and people come up with.
Battery drops at least 4 or 5% after those random reboots.
I put liquid smooth JB on the infuse and was able to reduce the reboots to maybe 1 or 2 a day but the battery drain is still insane. from full to empty in 7 hours (but the battery usage says 17hrs, so please dont be confused, its really only 7hrs), texting, checking emails but nothing else. no music, or gps or anything that it intense.
The battery usage shows a constant battery drain, everything is at either 5 or 10% usage, except the screen which is at 42 - 60%
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas?
I've managed to get some logs when this happens using alogrec (attached). I haven't worked with the dalvik kernel or android apps much to understand what is going on.
I hope someone would be able to go through them and pick up something. My knowledge on the subject is not enough to pick whether anything is wrong here.
Also, I noticed sometimes the battery drops from around 30% to a whooping 5% when this happens. So, maybe this is a faulty battery problem??
mccloud35 said:
I've managed to get some logs when this happens using alogrec (attached). I haven't worked with the dalvik kernel or android apps much to understand what is going on.
I hope someone would be able to go through them and pick up something. My knowledge on the subject is not enough to pick whether anything is wrong here.
Also, I noticed sometimes the battery drops from around 30% to a whooping 5% when this happens. So, maybe this is a faulty battery problem??
Click to expand...
Click to collapse
I ordered a new battery and hope that this will fix the problem, if anyone knows anything else please let me know. the battery is only 1 year old.
I had similar symptom (reboot followed by battery indicating lower) once when I had applied too much undervoltage applied.
I've had the same things happen with my phone.
1) the huge drops in battery isn't an actual drop. 99% of the time if you don't plug in a charger the battery will start 'charging' on it's own until it gets to the right amount.
2) just because the power button works doesn't mean there isn't something wrong. The infuse is notorious for messed up power buttons. There is a thread around here somewhere about fixing it. I've not done it because I managed to get things under control.
3) I've noticed that the reboots seem to occur more frequently when a large number of apps ( popular or not) are installed, or apps that are resource intensive. For instance I bought minecraft because my daughter has become adducted to it. Sometimes its fine other times it freezes and reboots. My solution is to only keep apps I use on my phone. I will most likely uninstall minecract until a later date.
4) For me smaller ROMs work better. The current slimrom works the best for me. Also finding time to remember to reboot my phone once a day no matter how it is running helps.
I'm down to a reboot every one or two days now. Unless I try to play minecraft. I blame those damn creepers. Good luck!
Sent from my SGH-I997 using xda app-developers app
OK so my reboots were because of my power button, I sent it in to mobiletech and they repaired it.
Now it's fixed and I have not had a single reboot.
Sent from my SGH-T999 using xda premium
Glad to hear that. Thanks for sharing your results.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

[Q] G2X Keeps Turning off -- Needs Charger to turn back on

Hi Everyone:
I am getting an issue with G2X that it randomly shuts off and that pulling the battery won't do anything. I would need to plug the charger into the phone in order to turn it back on. Last night I left the charger and I found this morning that it turned off while charging. Battery read 100% after I turned it on.
Originally I rooted it with CM7 Stable and the only problem was that whenever I called someone or someone called me, it sounded like a helicopter on the phone.
I flashed with NVFlash, cleared cache, all data, davlik, and then installed CM7 stable.
I tried it again and everything worked out great.
Last week I changed my room. NVFlash, Cleared Cache, All Data, Davlik, and installed HellsFire Rom with the CPU OCed to 1.5 Ghz.
The issue I ran into was that it drained power really fast. I ran out of power within 4 Hours.
I got tired of this and then I went back to CM7 Stable.
I began to have the issue where the phone keeps thinking there is no battery power and the phone keeps turning off. When I try to turn it on, it goes to the White LG Logo, and then Blue LG Logo, and then it turns off. I need the charger to turn the phone on. When the phone turns on it says "60% Power Left".
And then later on (5 Minutes at most) it will turn off, try to reboot, White LG/Blue LG, turn off. When it does turn on with the charger it will say "10% battery left please connect charger" and then it will turn off. When I remove the charger and turn it back on, it will have the battery symbol in grey with an exclamation point.
I thought I would try to do everything again, I booted into ClockworkMod and then it turned off.
What I tried after was maybe it was the Kernel. I reflashed and deleted everything, and then installed the CM7 stable rom and then TRINITY Kernel. The phone would not load on Trinity Kernel. It was stuck on the Trinity loading screen for like 5 minutes and I turned it off and Reflashed/Redeleted everything. I then reinstalled CM7 Stable and it loaded up.
I changed to a new ROM after it worked. I downloaded a new ROM yesterday, I am using Mokee Rom right now.
The issue still happens. Every few minutes the phone will turn off. Sometimes the phone would attempt to reboot and the White LG Logo comes up, and goes off, and loops this.
I have no apps on my phone currently.
The gray battery with the ! is there when I pull the battery and try to reboot.
I need the charger there to get the phone going.
Anyone have any suggestions of what I should do? The phone isn't even 2 years old yet.
Thank you.
N1rve said:
Hi Everyone:
I am getting an issue with G2X that it randomly shuts off and that pulling the battery won't do anything. I would need to plug the charger into the phone in order to turn it back on. Last night I left the charger and I found this morning that it turned off while charging. Battery read 100% after I turned it on.
Originally I rooted it with CM7 Stable and the only problem was that whenever I called someone or someone called me, it sounded like a helicopter on the phone.
I flashed with NVFlash, cleared cache, all data, davlik, and then installed CM7 stable.
I tried it again and everything worked out great.
Last week I changed my room. NVFlash, Cleared Cache, All Data, Davlik, and installed HellsFire Rom with the CPU OCed to 1.5 Ghz.
The issue I ran into was that it drained power really fast. I ran out of power within 4 Hours.
I got tired of this and then I went back to CM7 Stable.
I began to have the issue where the phone keeps thinking there is no battery power and the phone keeps turning off. When I try to turn it on, it goes to the White LG Logo, and then Blue LG Logo, and then it turns off. I need the charger to turn the phone on. When the phone turns on it says "60% Power Left".
And then later on (5 Minutes at most) it will turn off, try to reboot, White LG/Blue LG, turn off. When it does turn on with the charger it will say "10% battery left please connect charger" and then it will turn off. When I remove the charger and turn it back on, it will have the battery symbol in grey with an exclamation point.
I thought I would try to do everything again, I booted into ClockworkMod and then it turned off.
What I tried after was maybe it was the Kernel. I reflashed and deleted everything, and then installed the CM7 stable rom and then TRINITY Kernel. The phone would not load on Trinity Kernel. It was stuck on the Trinity loading screen for like 5 minutes and I turned it off and Reflashed/Redeleted everything. I then reinstalled CM7 Stable and it loaded up.
I changed to a new ROM after it worked. I downloaded a new ROM yesterday, I am using Mokee Rom right now.
The issue still happens. Every few minutes the phone will turn off. Sometimes the phone would attempt to reboot and the White LG Logo comes up, and goes off, and loops this.
I have no apps on my phone currently.
The gray battery with the ! is there when I pull the battery and try to reboot.
I need the charger there to get the phone going.
Anyone have any suggestions of what I should do? The phone isn't even 2 years old yet.
Thank you.
Click to expand...
Click to collapse
I think your battery is dead. Try another battery if not already.
-- The noob says:
Sent to the Facebook of cellular phones.
mansa_noob said:
I think your battery is dead. Try another battery if not already.
-- The noob says:
Sent to the Facebook of cellular phones.
Click to expand...
Click to collapse
I will try that. Thanks.
Same boat.
I am also having that same problem, I just bought a OEM (original equipment manufacturer) battery on Amazon will receive by hopefully next wednesday or thursday. i'm still using weapon g2x. I'm comfortable with it, after messing around with other roms a year ago. I just got lazy and stayed with it.
40zJuice said:
I am also having that same problem, I just bought a OEM (original equipment manufacturer) battery on Amazon will receive by hopefully next wednesday or thursday. i'm still using weapon g2x. I'm comfortable with it, after messing around with other roms a year ago. I just got lazy and stayed with it.
Click to expand...
Click to collapse
Could you tell me if this fixes the issue? If it does I'm going to buy a new battery than a new phone lol.
Here is a graph of my battery stats.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
battery came in!
N1rve said:
Could you tell me if this fixes the issue? If it does I'm going to buy a new battery than a new phone lol.
Here is a graph of my battery stats.
Click to expand...
Click to collapse
Okay so good news people, I received my battery on saturday june 15, 2013 from OEM4less in 2 DAYS!. I charged it up at 100% before using. I have not experienced any sudden reboots, or my screen going completely black, nor my screen only being lit up half way (yes it happened, litterally halfed the back of my screen was dim). I did experience my phone freezing but that was cause i was TEXTING someone back, WHILE commenting on FB, then I received a CALL, so total overload.
It has been approximately 16-18 hour of use, a total of approximately 8 hours constant reading pdfs, using fb, instagram, twitter, AND NO SUDDEN SHUTOFFS.
I HAVEN'T tried HOTSPOT, cause t-mobile be whining and *****ing.
I HAVEN'T tried BLUETOOTH cause I don't have any device that needs to use it.
So far the problem was the battery. I checked my old batteries VOLTAGE it read 4 volts, which is fine cause voltage can be approximate.
I did NOT check it's amperage levels which is strength or pressure of the voltage being spread into the phones circuits/body.
ill check later on the amp reading.
I have read online that its BAD to use your phone while it charges, WHICH i found out too f-ing late. BUT YES! problem so far fixed, will keep updating status on my phones behavior.

[Q] nexus 5 keeps shutting down for no apparent reason

my nexus 5 d820 16 gigs would randomly shutdown for no reason, it wouldn't turn on without plugging it in. i was rooted and running cm11, then i tried carbon ROM, then c-ROM. c-ROM started to give me problems so i factory reset and switched to carbon but the problems remained. then i unrooted, thinking that root was the problem but no signs of improvement, so i re-locked the bootloader but still the problem remained. it would sometimes also shut down if i unplug it and would always forget my WiFi connection for some reason. help me please. thanks in advance.
Well sounds like a hardware problem since you already unroofed and relocked boot loader I would say call lg and get a warranty replacement
Sent from my Nexus 5 using Tapatalk
Sorry to bring this post back after a long time.
I had a similar but not exactly the same problem.
2 nights ago I left the phone on the table, and a few minutes later, when I picked it up, it was off (It had about 60% battery left when I put it down).
Then it would not wake up; I kept the power button pressed for like 20 seconds to force a shutdown, and then tried to power up with no luck, so I'm thinking I'm screwed.
I tried again and it powered up to a graphical noise screen as seen in the attached image, but then it showed the boot animation and came back to life.
This morning it shut off by itself while listening to music (Google play), but powered back on right away...
Rooted 4.4.4, stock ROM, Xposed with Greenify, Amplify and wakelock detector (all latest versions). But no changes for a couple weeks before this started happening.
No specific app running (at least in the foreground).
Any one knows where I can find any kind of log or trace about this, if any at all?
Has anyone experienced this as well?
Thanks

Cannot boot into any Rom. Phone is restarting.

This issue started yesterday. My setup at that moment was as following:
Multirom : Installed
Primary Rom: Lineage OS 14.1
Secondary Rom: TugaPower 48.0
I was using TugaPower rom. I opened music player and the phone got switched off. I tried restarting but into the middle of the booting process, again it shut down. I tried booting into primary rom but the same issue happened. Then I connected it into a charger and it booted normally. Phone's battery level was >80% at that moment. I unplugged the charger and kept it idle, it stayed on. However, if I try to perform any action like opening an app, it switches off if not connected to a charger. So, I kept the phone on charge entire day to use it.
Today I thought of fixing the problem by wiping it clean. So I wiped everything in the phone including Internal Storage. Then I flashed Lineage OS again but the same issue is there. It won't work without a charger despite the battery being full. Please note that TWRP was working fine without a charger so I don't think the battery is faulty. Anyway, I decided to flash COS 13 using fastboot. The issue was still there. then I flashed TWRP again but this time it is also getting shut down in the middle of installing Lineage OS. I plugged it, but still Rom is flashing fine but in the middle of Open Gapps flashing process, it shuts down despite being connected to charger. Now it won't boot to any rom. Just shuts down when it starts to boot.
So now I have a dead OPO with working TWRP(?) and fastboot. Another thing I noticed is that when it is connected to PC via MTP it does not show the available space it used to. Just Internal storage
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not able to identify the actual issue. Is it a hardware problem? or any partition is corrupted?
Are the days of OPO are finally over?
EDIT: It was the battery all along! Thank you everyone for your feedback and helping me sort out the issue. OPO is still running fine.
Mystel said:
This issue started yesterday. My setup at that moment was as following:
Multirom : Installed
Primary Rom: Lineage OS 14.1
Secondary Rom: TugaPower 48.0
I was using TugaPower rom. I opened music player and the phone got switched off. I tried restarting but into the middle of the booting process, again it shut down. I tried booting into primary rom but the same issue happened. Then I connected it into a charger and it booted normally. Phone's battery level was >80% at that moment. I unplugged the charger and kept it idle, it stayed on. However, if I try to perform any action like opening an app, it switches off if not connected to a charger. So, I kept the phone on charge entire day to use it.
Today I thought of fixing the problem by wiping it clean. So I wiped everything in the phone including Internal Storage. Then I flashed Lineage OS again but the same issue is there. It won't work without a charger despite the battery being full. Please note that TWRP was working fine without a charger so I don't think the battery is faulty. Anyway, I decided to flash COS 13 using fastboot. The issue was still there. then I flashed TWRP again but this time it is also getting shut down in the middle of installing Lineage OS. I plugged it, but still Rom is flashing fine but in the middle of Open Gapps flashing process, it shuts down despite being connected to charger. Now it won't boot to any rom. Just shuts down when it starts to boot.
So now I have a dead OPO with working TWRP(?) and fastboot. Another thing I noticed is that when it is connected to PC via MTP it does not show the available space it used to. Just Internal storage
I am not able to identify the actual issue. Is it a hardware problem? or any partition is corrupted?
Are the days of OPO are finally over?
Click to expand...
Click to collapse
I'm pretty sure it's the battery.
replace the batteries and everything will be solved...no need to format of flash anything...
Mr.Ak said:
I'm pretty sure it's the battery.
Click to expand...
Click to collapse
Is there a way to confirm?
iPusak Gaoq™ said:
replace the batteries and everything will be solved...no need to format of flash anything...
Click to expand...
Click to collapse
Ok now you are telling that also means the battery is the main culprit..
Should I buy a battery from ebay ir contact OP service centre?
Now even twrp won't boot without power!
Mystel said:
Is there a way to confirm?
Ok now you are telling that also means the battery is the main culprit..
Should I buy a battery from ebay ir contact OP service centre?
Now even twrp won't boot without power!
Click to expand...
Click to collapse
There you go,the confirmation.
Anyways,have a look at battery thread in accessories,they have some nice recommendations there.
OP SVC don't have any batteries left,so don't bother contacting 'em.
Mystel said:
Ok now you are telling that also means the battery is the main culprit..
Should I buy a battery from ebay ir contact OP service centre?
Now even twrp won't boot without power!
Click to expand...
Click to collapse
Yes...i know this problem first hand cause i'm one of the first that have this problem 1 years ago...when a phone required a constant power from charger to boot normally then it is a clear sign of a dying batteries...don't be fool the with batteries percentage while you connect the phone cause it is not accurate anymore...
if you have OP service center nearby then i suggest you buy new batteries from them but if there no service center then buy new batteries in ebay, amazon or etc but you might get OEM's batteries instead of original batteries if you bought it online....still using OEM's batteries can give you around 3-4 hours of SOT depend on how you use it....
iPusak Gaoq™ said:
Yes...i know this problem first hand cause i'm one of the first that have this problem 1 years ago...when a phone required a constant power from charger to boot normally then it is a clear sign of a dying batteries...don't be fool the with batteries percentage while you connect the phone cause it is not accurate anymore...
if you have OP service center nearby then i suggest you buy new batteries from them but if there no service center then buy new batteries in ebay, amazon or etc but you might get OEM's batteries instead of original batteries if you bought it online....still using OEM's batteries can give you around 3-4 hours of SOT depend on how you use it....
Click to expand...
Click to collapse
I was getting around 1.5 - 2 hr SOT so I think OEM batteries will be fine too. I will still contact oneplus service center to inquire about battery replacement cost. I have seen some videos on youtube. Do you think changing battery by myself will be fairly easy?
Mr.Ak said:
There you go,the confirmation.
Anyways,have a look at battery thread in accessories,they have some nice recommendations there.
OP SVC don't have any batteries left,so don't bother contacting 'em.
Click to expand...
Click to collapse
Ok I will check the threads if there is any good battery recommendation in India, Thank you!
Mystel said:
I was getting around 1.5 - 2 hr SOT so I think OEM batteries will be fine too. I will still contact oneplus service center to inquire about battery replacement cost. I have seen some videos on youtube. Do you think changing battery by myself will be fairly easy?
Click to expand...
Click to collapse
Easy AF.
Mystel said:
I was getting around 1.5 - 2 hr SOT so I think OEM batteries will be fine too. I will still contact oneplus service center to inquire about battery replacement cost. I have seen some videos on youtube. Do you think changing battery by myself will be fairly easy?
Click to expand...
Click to collapse
Yes easy to change it yourself...even i change the batteries myself back then....
Mystel said:
This issue started yesterday. My setup at that moment was as following:
Multirom : Installed
Primary Rom: Lineage OS 14.1
Secondary Rom: TugaPower 48.0
I was using TugaPower rom. I opened music player and the phone got switched off. I tried restarting but into the middle of the booting process, again it shut down. I tried booting into primary rom but the same issue happened. Then I connected it into a charger and it booted normally. Phone's battery level was >80% at that moment. I unplugged the charger and kept it idle, it stayed on. However, if I try to perform any action like opening an app, it switches off if not connected to a charger. So, I kept the phone on charge entire day to use it.
Today I thought of fixing the problem by wiping it clean. So I wiped everything in the phone including Internal Storage. Then I flashed Lineage OS again but the same issue is there. It won't work without a charger despite the battery being full. Please note that TWRP was working fine without a charger so I don't think the battery is faulty. Anyway, I decided to flash COS 13 using fastboot. The issue was still there. then I flashed TWRP again but this time it is also getting shut down in the middle of installing Lineage OS. I plugged it, but still Rom is flashing fine but in the middle of Open Gapps flashing process, it shuts down despite being connected to charger. Now it won't boot to any rom. Just shuts down when it starts to boot.
So now I have a dead OPO with working TWRP(?) and fastboot. Another thing I noticed is that when it is connected to PC via MTP it does not show the available space it used to. Just Internal storage
I am not able to identify the actual issue. Is it a hardware problem? or any partition is corrupted?
Are the days of OPO are finally over?
Click to expand...
Click to collapse
I can confirm it is a problem with the batteries because I had almost the same issue on my one running RR.
Just got mine replaced 30 minutes ago and its running smooth. Just need to do few power cycles for calibration.
Good Luck!
Mystel said:
This issue started yesterday. My setup at that moment was as following:
Multirom : Installed
Primary Rom: Lineage OS 14.1
Secondary Rom: TugaPower 48.0
I was using TugaPower rom. I opened music player and the phone got switched off. I tried restarting but into the middle of the booting process, again it shut down. I tried booting into primary rom but the same issue happened. Then I connected it into a charger and it booted normally. Phone's battery level was >80% at that moment. I unplugged the charger and kept it idle, it stayed on. However, if I try to perform any action like opening an app, it switches off if not connected to a charger. So, I kept the phone on charge entire day to use it.
Today I thought of fixing the problem by wiping it clean. So I wiped everything in the phone including Internal Storage. Then I flashed Lineage OS again but the same issue is there. It won't work without a charger despite the battery being full. Please note that TWRP was working fine without a charger so I don't think the battery is faulty. Anyway, I decided to flash COS 13 using fastboot. The issue was still there. then I flashed TWRP again but this time it is also getting shut down in the middle of installing Lineage OS. I plugged it, but still Rom is flashing fine but in the middle of Open Gapps flashing process, it shuts down despite being connected to charger. Now it won't boot to any rom. Just shuts down when it starts to boot.
So now I have a dead OPO with working TWRP(?) and fastboot. Another thing I noticed is that when it is connected to PC via MTP it does not show the available space it used to. Just Internal storage
I am not able to identify the actual issue. Is it a hardware problem? or any partition is corrupted?
Are the days of OPO are finally over?
Click to expand...
Click to collapse
Try reflashing an older version of TWRP/ modded version and if that doesn't work, try an AOSP ROM. I had the same problem and got OMNI and AOSP 8.xx to boot.
valvze said:
Try reflashing an older version of TWRP/ modded version and if that doesn't work, try an AOSP ROM. I had the same problem and got OMNI and AOSP 8.xx to boot.
Click to expand...
Click to collapse
Now TWRP shuts down in the middle of flashing rom so no other ways. Sorry I was busy these days and OPO was lying dead. I just ordered one battery from eBay and will update once I replace the battery.
Well, I have the exact same issue & coincidentally or not, I was also running Tugapower 49. Phone will boot only with the charger connected. So, battery issue is confirmed.
I'll join your club. About 3 weeks ago had a similar problem but managed to get the phone to boot after an over night charge. The battery was around 13 months old. Ordered a new battery from ebay. Fitted it two days ago and flashed an updated lineage rom last night. My oneplus 1 is now stuck in a boot loop. After flashing and leaving it over night to update, it was still in the boot up logo this morning. Held in power button to kill power. Numerous attempts to boot up the phone failed. Only twice have I managed to get it to boot to TWRP recovery. Both times I have tried to resort to flashing the previous ROM, but still get stuck in the loop. I'm waiting to let it get to a full charge, then I'll try a fastboot method and pray that that works. I'll update if/when I get sorted
---------- Post added at 10:34 PM ---------- Previous post was at 09:48 PM ----------
Well.... had phone plugged into laptop charging. Wrote the above post. not 10 mins after, booted into Recovery first time, reflashed and got it working again........ wish I knew what was going off here but, its working now.
Had the same issue 4 months ago and I'm 99% sure it's the battery. Change it.
Replaced th battery.But in the process something messed up. First, touch would not recognize. Upper connector was loose. Now reconnected that and flashed lineage os. Having ghost touch constantly on "wipe" button position of twrp. This just started after setting up lineage. But the main issue was battery!
Mr.Ak said:
I'm pretty sure it's the battery.
Click to expand...
Click to collapse
iPusak Gaoq™ said:
replace the batteries and everything will be solved...no need to format of flash anything...
Click to expand...
Click to collapse
Quoting you if you have any idea about the ghost touches I am having after replacing the battery. The main issue is gone.
Mystel said:
Quoting you if you have any idea about the ghost touches I am having after replacing the battery. The main issue is gone.
Click to expand...
Click to collapse
There shouldn't be ghost touch problem after you changes the batteries unless you disconnect other ribbons and didn't reconnect it properly...dissemble the phone and disconnect all ribbon and reconnect it again for further test....
Sent from my A0001 using Tapatalk
iPusak Gaoq™ said:
There shouldn't be ghost touch problem after you changes the batteries unless you disconnect other ribbons and didn't reconnect it properly...dissemble the phone and disconnect all ribbon and reconnect it again for further test....
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Here is a sample video I just took. only the area between sim tray and power button is affected.
https://ufile.io/iql19

Categories

Resources