Database Users

[Q] Nexus 4 randomly turning off, intermittently not being able to restart

Hi guys,
Not exactly the most positive of first posts but here we go. There's a problem with my phone that I can't find the solution for...
Essentially my phone randomly turns itself off (no power down sequence, almost as though the battery's being taken out if you know what I mean) and then it has difficulty in fully booting again. For some reason it also likes to revert my wallpaper back to the original as stock.
The first thing that I thought of was malware, with the wallpaper - so I tried a couple of anti-malware apps to no avail. As my device was rooted, I then flashed back to stock, locked and unrooted it and checked the behaviour. Again to no avail (then again I've never rooted/unrooted so this may have been done incorrectly). By the looks of it, the worst case scenario is a problem with battery connections/hardware...
So the question is have you guys come across this before? Is there a solution to this or is Google/LG going to have to give me a replacement?
Many Thanks.

Weird, I just had this happen couple hours ago, I was watching a video and close the app. I press the power button to put it to sleep. Just like 20 second later, I press the power to wake it and it don't do anything. I had to hold the power button to turn it on. I check the battery status afterward and it looks like it drop between 5-10 percent in the chart after it turn on. The battery must have failed or something. This also happen to my wife phone couple weeks back, although she had to do a hard reset(power+volume up and down) it have not happen again though.

Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need

maintains
kyokeun1234 said:
Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need
Click to expand...
Click to collapse
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.

Thrice87 said:
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.
Click to expand...
Click to collapse
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.

kyokeun1234 said:
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.
Click to expand...
Click to collapse
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable

Thrice87 said:
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable
Click to expand...
Click to collapse
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?

kyokeun1234 said:
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?
Click to expand...
Click to collapse
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.

Thrice87 said:
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.
Click to expand...
Click to collapse
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app

kyokeun1234 said:
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, after completely reverting the phone back to its stock version and pretty much everything else, it's still doing it - which surely points to a problem with the chip (or something). So, I've contacted google about a replacement and so far so good - got through in 5 minutes and sorted out the RMA and everything, should be delivered in the next few days.
Thanks for the help anyway. I'm going to avoid rooting this one for the time being to see how it behaves.

I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.

hfuizo said:
I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.
Click to expand...
Click to collapse
Yeah that's not my problem at all Lol. Glad you've figured it out and I bet that magnet caused the issue IMO
Sent from my Nexus 4 using xda app-developers app

Funny I had the same thing happen to me last night. I was using the phone put it down for a minute or two and then could not wake the phone. What was interesting was when I couldn't get it to turn on I plugged in into the charger and let it sit for a few hours. When I was finally able to restart it using the the power, vol button the battery was at the same level before the incident. In other words whatever happened prevented the battery from being charged. I am stock and rooted and haven't loaded any new apps in over 2 weeks
Sent from my Nexus 4 using xda app-developers app

I have almost the same problem as the op but I do have a shut down sequence. It does randomly shut down itself. The first thing I got the phone I rooted it and it was fine working on modaco for 2 weeks then one day it kept shutting down upon boot until like 10 tries later I successfully got back in but lasted only a few mins and sometimes hours. Im gonna rma this pos and I hope I can get it replaced soon. I try it with stock rom and kernel then modaco with stock kernel then modaco with faux kernel. Same problem.

I had these problems earlier ... I just gave HARD RESET by pressing power key for more than 5 sec.
Then i figured, it was due to Undervolting ! and Processor going to a DEEP SLEEP all together !
So i removed UVing and it was cool since then ! ... Although my signature says the rest !

I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.

The same happens several times a week with my nexus 4 running latest cyanogenmod. I will revert it to clean stock in a few days to see how it goes. I don't think that is a hardware problem but time will tell.

MildewMan said:
I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.
Click to expand...
Click to collapse
Don't know if anyone is keeping up or cares, but I wanted to update and say that this did not fix the problem. 4.2.2 also did not fix the problem. I guess I could try getting a new one from Google.

My wife and I are both having this problem. Hers is completely stock, I'm unlocked and rooted. I was hoping it would be fixed with 4.2.2, but if it hasn't then it maybe time to get replacement N4s
I can't imagine this issue is very widespread, since there have only been a few threads about it. Its a big nuisance especially because it usually happens at night when I'm expecting my alarm to go off at night.
I hadn't wanted to send for replacements since it seems like a software issue but I'm getting fed up.
Sent from my Nexus 4 using xda app-developers app

Just had this problem occur with my N4 last night..... Phone is 2 weeks old.
Went to bed, plugged in the phone to charge [it was at about 50% or so, so not exactly low].
Woke up at 8.30 wondering why my alarm didn't go off at 7.30.... looked over and the phone was off.
It also didn't want to turn back on either. Took about a minute of holding in the power button for various amounts of time before it finally kicked to life [at 100% charge too].
This is going to be a real problem if this problem reoccurs. At home I have a clock radio but I travel a lot and rely on my phone to wake me up!
Here's hoping we can start to identify what is causing this issue. All I can add is that it is not low-battery related.
As stated in the sig. Phone is unlocked/rooted with stock rom.

[Q] Phone turning off by itself and renders itself off ever since

Hi all,
My first post here and I'm posting it at a pretty depressing mood.
I've just bought my phone from the states and brought it back to Hong Kong for my own use. Last night, I've been toying it for a couple hours with everything going perfectly fine, but suddenly the phone turned itself off. Everytime I try to turn it on the phone just turns itself back off again. I couldn't do anything.
Has anyone come across the same problem? I've done a hard reset but to no avail, the phone still shuts down right after turning on, it's pretty frustrating to turn on your phone just to see it telling you it's turning off, really frustrating tbh.
I've called google and requested for a replacement so problem's kinda solved for the moment. I just want to know if I'm alone here because I've pressed the operator a couple times and she refused to tell me if mine was an isolated incident or not, for obvious reasons.
I haven't done anything to the phone except installing a couple apps like Aldiko, whatsapp, facebook and a Chinese keyboard (since I'm Asian apparently). I've installed all of them in my old phone and none of them caused any problems so I just want to know if I'm alone and what do you guys think the root of the problem is, or solutions to it if there are any.
Thanks a lot!

franshu said:
Hi all,
My first post here and I'm posting it at a pretty depressing mood.
I've just bought my phone from the states and brought it back to Hong Kong for my own use. Last night, I've been toying it for a couple hours with everything going perfectly fine, but suddenly the phone turned itself off. Everytime I try to turn it on the phone just turns itself back off again. I couldn't do anything.
Has anyone come across the same problem? I've done a hard reset but to no avail, the phone still shuts down right after turning on, it's pretty frustrating to turn on your phone just to see it telling you it's turning off, really frustrating tbh.
I've called google and requested for a replacement so problem's kinda solved for the moment. I just want to know if I'm alone here because I've pressed the operator a couple times and she refused to tell me if mine was an isolated incident or not, for obvious reasons.
I haven't done anything to the phone except installing a couple apps like Aldiko, whatsapp, facebook and a Chinese keyboard (since I'm Asian apparently). I've installed all of them in my old phone and none of them caused any problems so I just want to know if I'm alone and what do you guys think the root of the problem is, or solutions to it if there are any.
Thanks a lot!
Click to expand...
Click to collapse
Mine is happening the samething, glad Im not alone. My was running fine on rooted Modaco custom rom for a few weeks then all of sudden the phone auto shut down like it has its mind. I installed Cantonese keyboard and camera mod too and some other apps. Currently Im tracking down the source. Now I have franco kernel and madaco rom on clean install running with no other app install to see if it will shut down or not. If it does Im going back to stock to see if samething happen.
I have to boot it couple times until it doesnt shut down itself anymore. Sometimes it be stable for couple hours or couple minutes or instantly.

I have the same problem, Just got my phone from google everything is stock nothing has been changed and the phone just turns it self off and then i cant turn it back on for sometime.
Does anyone know what causing this problem?

Mine also turns off multiple times a day, sometimes by itself, sometimes during a call, often when taking a picture.
Today every single time I took a picture it would shut down.
I'm f*cking pissed at waiting 5 weeks to get a useless phone... and god know how long it will take to get a replacement if I ca get one.

Hi guys, I have the same problem too
I've used my Nexus 4 for 2 weeks without any kind of problem when suddenly it turned itself off. If I try to turn it on, the phone just turns itself back off again and I haven't solved the problem even with a reset.
But I've noticed that the battery doesn't charging even with the charging cable. I think the phone detects that hasn't enough battey level and for that reason turns itself back off.
Do you think it can be an harware or software problem?

Damn - i have recently been having the same problem! It only happens (so far) when i'm charging the phone overnight. I wake up and it's off and takes a few tries to get it running again. I'm rooted with stock. Does this mean we all need replacements? Ugh!
Sent from my Nexus 7 using xda premium

kalipedia said:
Damn - i have recently been having the same problem! It only happens (so far) when i'm charging the phone overnight. I wake up and it's off and takes a few tries to get it running again. I'm rooted with stock. Does this mean we all need replacements? Ugh!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
The exact same thing happened to me as well. I charged it overnight, unplugged it and it was off. I couldn't even turn it on again - I had to keep holding the power button for ~15 seconds plus try plugging/unplugging the phone to the charger etc. and it finally powered on. I orginally thought it may have been a kernel issue since I had just flashed Franco r29. However, looking at his thread, nobody had that issue.
I'm glad I'm not alone but this issue really worries me, especially if it is a hardware fault. Google will replace it but I don't feel like going through the fuss since God knows when the replacement will arrive. I hope this get's 'magically' fixed as it has only happened to me once so far.

Notorious544d said:
The exact same thing happened to me as well. I charged it overnight, unplugged it and it was off. I couldn't even turn it on again - I had to keep holding the power button for ~15 seconds plus try plugging/unplugging the phone to the charger etc. and it finally powered on. I orginally thought it may have been a kernel issue since I had just flashed Franco r29. However, looking at his thread, nobody had that issue.
I'm glad I'm not alone but this issue really worries me, especially if it is a hardware fault. Google will replace it but I don't feel like going through the fuss since God knows when the replacement will arrive. I hope this get's 'magically' fixed as it has only happened to me once so far.
Click to expand...
Click to collapse
You know, I'm looking at my battery history (using battery monitor) and i see the period that the phone was shut down and then when i powered it back up this morning and i notice the battery temp is extremely high so it probably has to do with the phone shutting down due to overheating, which obviously shouldn't happen. I wasn't using the oem charger, so I'll switch to that for the time being and keep an eye on temp. Hopefully it's a software bug and not a faulty battery because it should definitely be cutting off charging when it reaches 100%.
Sent from my Nexus 7 using xda premium

[Q] My Nexus 7 just exploded. What do I do?

Hey XDA,
I received my 16GB Nexus 7 from Google 4 days ago. I immediately updated to 4.2.1, rooted, and then flashed franco.Kernel. I was running the latest update to franco's kernel, and had left the settings untouched from the defaults with interactive governor. Yesterday I flashed the latest nightly for Cyanogenmod.
I was using the Facebook app when my tablet ran out of battery (I intentionally let it die), and after it powered itself off, I plugged it in with the charger provided to me by Asus/Google. Because I am new to this tablet, I wasn't aware that plugging the charger in meant that the device would power on. Anyways, it did power on, and I had no plans to turn it off now that it had turned itself off. I went to turn the wi-fi off so that it would charge with less power drain, but just before I turned the wi-fi off, the device began to power down again (The charger is still plugged in, and it didn't become unhooked at any time). I begin to walk away to do other things while it turns off again, but I stop when I hear a weird grinding noise. It's hard to explain, other than it sounded like a kettle getting progressively louder and then shutting itself off when it reaches its desired temperature, only it sounded like gears and not a kettle.
A little worried, I wait a bit and then I turn it on. I'm relieved when I see the Google logo appear, and then the Cyanogenmod logo appear. After a long boot, I'm greeted by a black screen with what tiny white flashing dots randomly appearing. I turn the device off, and restart it. Same thing, only now it seems like there may be more flashing white dots than the last boot. I unplugged the device from the wall, and force shut it off (power + volume keys).
I've never heard of this happening before, which is why I'm hoping someone can give me some advice. Obvious things for me to do would be to flash stock 4.2.1 onto my Nexus 7. The reason I haven't done this is that I'm worried that my device may now be dangerous (battery melt, processor malfunction). Does XDA have any recommendations before I phone Google? I'd like to avoid Google because I've voided my warranty with them by rooting and flashing a custom kernel, so any other help is MUCH appreciated.
Thank you so much for reading my essay, and for taking the time to help,
Robert

Do your very best to revert it back to stock os and kernel and re lock the bootloader. Yes it is possible. Look for the nexus 7 toolkit. Then send it to google/asus. Best I can think of dude.
Sent from my MB612 using xda app-developers app

I have heard people with similar issues start device in bootloader and leave it there to charge to prevent the on/off loop and after a few hours when charged boot normally.
Hope this helps
Sent from my SGH-I927 using xda app-developers app

The screen with white dots has turned into what appears to be a screen with no signal like you see on tv's.
This is even happening while I'm in recovery mode, it'll just randomly happen.
What's going on?

Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195

BlackFire27 said:
Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195
Click to expand...
Click to collapse
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert

Trewyy said:
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert
Click to expand...
Click to collapse
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.

BlackFire27 said:
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.
Click to expand...
Click to collapse
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert

Trewyy said:
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert
Click to expand...
Click to collapse
Anytime man! PM me if you have anything else man.

It's 4 days old. Send it back as defective.

turn it off, let it charge for long time, after tha download toolkit and revert it back to stock.
You should be good to go.

I'd bring it back, as it is possible to cause an injury to you. Better to be safe than sorry.
Its new so just bring it back (or send) and get a new one.
Sent from my Nexus 7 using xda premium

Try to relock it and flash the stock rom.
After that, phone up Google and explain what happened AND ask for a compensation. This could have harmed you, and Google/ASUS IS responsible for it. Unless, of course you have messed something up while rooting or flashing the custom rom.
Anyway, you should be able to get a compensation, maybe a 32GB version.
This is not something that should happen to a 4 days old device.

did you void the warranty by flashing? i don't actually know.
granted, this sounds like a hardware malfunction (again, i don't know, could be a kernel), but, modder beware. this is a risk we take.

I'd put it back in the box and return it if possible. Save some time. If they are jerks about it then proceed:
If you can flash anything to it through recovery, download the updated Galaxy Nexus (Samsung) JB Bootloader and flash it.
I have a Galaxy Nexus and a Nexus 7. I killed my first N7 by getting confused and flashing it to my N7. It won't even power on afterwards. That should screw up your partitions enough where it won't be recoverable without a full format/reflash.

I had this issue when my battery died. I took off the back cover and unplugged the battery and plugged it back in. Put it back together and charged it up for a few hours. All has been well since, I'm pretty sure its a common issue with N7's when the battery gets low.

Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app

Do your best to revert it back to factory and call them up about that possible firecracker before something else can happen
keep us informed about what happens too if thats ok

Stock - and the same problem...
Hi, my N7 is two months old and worked perfectly. It's clear stock - never rooted, modded etc. Today I suddenly can't run it - it boots, battery level is 24% (on bootscreen), and after few seconds shows 1% and starts to snow - sometimes with sound. I haven't installed anything new for few weeks, so I'm sure it's not a virus, trojan etc. WTF?
PS. Sorry for my English...

djexacto said:
Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I confirm that. I had this issue already a lot of times. When the battery is completley discharged it seems that the display or the graphics hardware is not able to start as expected. I just left it powered of (or in that charging screen) for some time (>1h) without using it. Then it started normal.
But also for me, no noise, just the screen like on an old TV without signal.

S4 Not Charging

Unplugged my phone this morning at 100%, went to charge it just now with factory charger and cable and nothing. Tried reboot and battery pull. Sitting at 60% right now. It's off in case I need to return to stock to exchange it. Any ideas?

Planktron said:
Unplugged my phone this morning at 100%, went to charge it just now with factory charger and cable and nothing. Tried reboot and battery pull. Sitting at 60% right now. It's off in case I need to return to stock to exchange it. Any ideas?
Click to expand...
Click to collapse
I had a bad cable, it is not the phone...damn cables were cheaply made.

Tried 2 cables. When the phone is off I get the battery icon with the circle in it, but it just loops this icon. It comes up, vibrates, turns off repeatedly. I tried to wipe cache and it said error. I'm rooted, defrosted everything I had frozen.

What I don't understand is why I'm getting an error when trying to wipe cache partition.I unrooted, so as far as I know im now totally stock. Is it safe to try to do a factory reset?

Planktron said:
Tried 2 cables. When the phone is off I get the battery icon with the circle in it, but it just loops this icon. It comes up, vibrates, turns off repeatedly. I tried to wipe cache and it said error. I'm rooted, defrosted everything I had frozen.
Click to expand...
Click to collapse
Sounds like kernel panic. Whatever rooting/custom mod/ blabla you have on that device is either buggy, badly flashed or something like that.
You need to have a good connection to Odin established, flash only stock rom (the untouched version/odexed), let it reboot normally from Odin, and wait. (it is important to have at least 50% battery left, you don't want it to quite on you in the middle of a flash)
Doesn't matter if it doesn't go all the way and setup the first time. Just pull the batter (after Odin rebooted), go into recovery, cleanup everything, and reboot.
Thank should get you back in the world of the living ...

http://forum.xda-developers.com/showthread.php?t=2261573&highlight=return+to+stock
So just do exactly what is written in this thread then? Do I have to go that far or can I try a factory reset from recovery?
Thanks BTW

Planktron said:
http://forum.xda-developers.com/showthread.php?t=2261573&highlight=return+to+stock
So just do exactly what is written in this thread then? Do I have to go that far or can I try a factory reset from recovery?
Thanks BTW
Click to expand...
Click to collapse
Easier things first, so if you haven't tried a factory reset yet then go ahead ( although that won't unroot you) try your factory reset first.
But then if your battery gets too low and still doesn't charged, you need to get it charged up first.
And yes that hotfile link is the original factory ROM dump, it is good.
That is the at&t stock file or you're on bell or rogers or ... get a samfirmware/sammobile account and download your ROM from there.

No dice on the factory reset, and I'm about 40%. I'm thinking I'm just going to exchange it. Device status says Official so I should be good, no?

Planktron said:
No dice on the factory reset, and I'm about 40%. I'm thinking I'm just going to exchange it. Device status says Official so I should be good, no?
Click to expand...
Click to collapse
you should be ok exchanging it although for most devices rooting voids the warranty
that was my main reason sending you the odin flashing route in case you wanted to exchange it but it is no big deal.

Well I'll be...
Did another factory reset from the settings menu this time, ON THE WAY to the AT&T store(while parked, of course), plugged it into the 'ol 12v and she fired right up. I agree about the kernel panic deal. I've had strange things happen before. The only thing that changed on my phone from last night until the no-charge state was the installation of SugarSync. It kept FC'ing so I uninstalled it. I think it may have changed some items deep deep in the areas of the OS that I know nothing about and it freaked out the bowels of Android.
Back when I had my Atrix 4G, I installed Dolphin Browser, and it sent my phone into a whirlwind of FC's.
Thank you for your assistance, Commodore.

Planktron said:
Well I'll be...
Did another factory reset from the settings menu this time, ON THE WAY to the AT&T store(while parked, of course), plugged it into the 'ol 12v and she fired right up. I agree about the kernel panic deal. I've had strange things happen before. The only thing that changed on my phone from last night until the no-charge state was the installation of SugarSync. It kept FC'ing so I uninstalled it. I think it may have changed some items deep deep in the areas of the OS that I know nothing about and it freaked out the bowels of Android.
Back when I had my Atrix 4G, I installed Dolphin Browser, and it sent my phone into a whirlwind of FC's.
Thank you for your assistance, Commodore.
Click to expand...
Click to collapse
That is always good to hear. thanks for reporting back.
Plus if you did reset it while you were driving, not that some people haven't ... , at&t will start making new screen stickers saying :
"don't factory reset your phones and drive ... it can wait".

Oh well. Since im a junkie and couldn't wait to re root, as soon as it charged back up I re rooted. All was well until I started freezing bloat, then it stopped charging. Got a replacement on the last day of the return period. Wish I knew what was causing this. Looks like im staying stock until we get recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

It's been a few days so I'm bringing this thread back from the grave, but I want to know if anyone else has experienced similar issues. It's really strange, what happened, and I'd like to know more about why it happened. I should have made a logcat but too late now. I'm not the type of person to experience something like that and take the easy way out with an exchange (I've experienced worse), but with my battery percent remaining an ODIN flash would have been risky at best. Like I said, everything was fine for days until I installed sugarsync.
I only froze bloat. Everything starting with AT&T, and some Samsung apps like S-Voice, ChatOn and push service.
Until I can figure this out or get custom recovery, I'm stuck stock because I'm not going to cheat again for another exchange.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

I had exactly the same thing happen to my rooted s4. Took it back to the shop i bought it ( Unrooted ) and they replaced it.

Same here.
I get it to charge sometimes for about 10 minutes and then it'll disconnect.
USB via the PC doesn't work as well.
I think replacement is probably a safest bet.
We aren't the only ones either...
http://forums.androidcentral.com/samsung-galaxy-s4/275276-galaxy-s4-wont-charge.html

This has just happened to me. I plugged it in last night with about 19% remaining, woke up this morning and it was at 7%-- hadn't charged. I tried a couple different chargers and cables, and nothing has worked so far. The charge has since dwindled to 4%. I'm running slimrom, and I guess I can't risk flashing back to stock since the battery is likely to die completely during the process.
When I did a shutdown and then plugged it in, I got the "charging" icon, of the battery with the green bar repeatedly moving up through it. But after leaving it for half and hour, I tried to boot it, and that was the point where it had gone from 7% to 4%, so apparently it wasn't really charging. Might have to buy another battery and see if that's the problem or the charging circuit in the phone.
---------- Post added at 03:01 PM ---------- Previous post was at 02:48 PM ----------
Ok, so this is weird. I have been using some older chargers/cables that I had left over from my Captivate, and they've been working fine for a month, until now. But I went and got out the charger that came with the GS4 and tried that, and although the ROM still says "not charging/connect your charger", the battery % is increasing. Very strange.

I think u need to get back to stock rom to solve this issue..and u won't get warranty as your device is rooted even if u revert back to stock your bincounter will ramain same that's of you had flashed your device twice with custom rom your bin counter will be 2...so samsung can easily understand it by going into download mode...u can also see the number of bin counts by entering into download mode screen ....so u need to reset bin counter before taking it to customer care otherwise they will woid ur warranty:thumbup:
Sent from my GT-I9500 using xda premium

[Q] Random shut downs and battery drops. Battery problem?

I've been facing these problems for over a week now and it's extremely frustrating. I get these random shutdowns when I'm just opening an app or using my phone longer than a certain amount of time. The phone will have 100% charge in the morning then shuts down and if I try restarting the Google splash screen shows up and shuts down again. Then the battery level will be at 70% and the whole thing happens again till I have no charge.
So when 4.4 came out I thought I'd update and these problems will go away and they didn't. Now the same thing happens I've done a data wipe/factory reset, cleared cache but still nothing. I thought some apps were causing problems so I uninstalled everything but still no use. I'm currently on stock 4.4 using the stock kernel. I was also on stock 4.2.1 when these problems started. Does anyone have any idea what the problem could be?
Thanks.

Do you also have a bad network connection/sim locks? Then you should read this topic. It could be a faulty battery.

Faeshaas said:
Do you also have a bad network connection/sim locks? Then you should read this topic. It could be a faulty battery.
Click to expand...
Click to collapse
Yeah my sim is deactivated but I think that's a sim problem. I spoke to my network provider to reactivate it tomorrow. Thanks for that thread I must've missed it somehow. Hopefully its just a battery problem so I can just get a replacement.