Database Users

[Q] EPIC random shutdowm

Ok odd thing keeps happening. My epic will randomly power off but will not power back on until i do a battery pull. I am currently running 2.2.1 RandomRom 2.2 Final EC05. I dont think it is the rom but who knows. Any Ideas would be great! Thanks Everyone in advance.

Do you use setcpu or anything like that? Some phones dont like to run below 200mhz.
Posted by Mr. Z's Epic 4G via Tapatalk

Nope not running anything. It only does it when the phone is not charging. If its on the charger it stays on. If i pull it off the charger it could turn off 20min to 3 hrs later.

harmhimself said:
Nope not running anything. It only does it when the phone is not charging. If its on the charger it stays on. If i pull it off the charger it could turn off 20min to 3 hrs later.
Click to expand...
Click to collapse
My last one did that, but it was because I dropped it. Have you ruled out a hardware problem?
Posted by Mr. Z's Epic 4G via Tapatalk

Not that i know of. Its never been dropped. I wonder if i should factory reset and start all over. I just dont know what else it could be.

It's most likely that it's a third party app causing the issue.
That said, the best way to exonerate the software is to ODIN to the stock EC05. If it does it with that, it's probably a hardware issue. If it doesn't, it's probably a ROM or kernel issue.
P.S. it's humorous that RandomROM might be causing RandomREBOOTS.

Haha.....yea. I liked it at first but guess its back to finding something new.

Yeah I'm having a similar problem also but only recently like no more then a couple weeks... my phone doesn't shut down completely but it randomly restarts itself and the ODD thing is that when it would power back up it would be in AIRPLANE mode. No matter how many times I tryed to disable airplane mode it just would not turn off! Even after I would shut down my phone and power back up it was still in airplane mode. So I took out the battery for a couple of seconds and put it back in, powered up and every thing works fine again... its only happened about 3 times I'm running that new gingerbread leak so that might be the issue but I've been rnning it for a while now and only recently had this problem with the phone.

I run ACS Frozen 1.2 have the same issues, I've had the same issue since froyo sourced roms have come out.... phone randomly powers off..... only happens maybe once or twice a week. It happened extremely more frequently before I changed back to RFS and turned journaling on. It didn't completely correct the problem, but it helped a lot.
Nothing like waiting for a text back from your GF only to find out that your phone has turned off sometime in the last hour since you sent out a text. I call it "The Samsung **** Block"

this happens to me sometimes, if you have journaling off, something might be corrupted. when the phone tries to access the corrupted data it puts the phone in an infinite loop, you might notice a huge decrease in battery life when you do reboot. A fresh clean install is the best way to fix it.

mrhocuspocus said:
this happens to me sometimes, if you have journaling off, something might be corrupted. when the phone tries to access the corrupted data it puts the phone in an infinite loop, you might notice a huge decrease in battery life when you do reboot. A fresh clean install is the best way to fix it.
Click to expand...
Click to collapse
Thanks. I've noticed this.
Sent from my SPH-D700 using XDA Premium App

overheating caused data corruption and FC's

I was on my way home from vacation (5 hour drive) and I had my phone plugged in the car charger with GPS, Google Maps and Pandora running all at the same time, when my phone overheated and shut-down. A warning sign came on saying that it was either "too hot or too cold to charge." Well, i decided to swap batteries and that point when I booted the phone, I got a FC boot loop. I had journaling ON btw.
I had a CWM backup ready, and simply restored it. So nothing was lost. But still, i didn't know our phones could heat up like that.
btw: i was on srf 1.2 w/Genocide 1.2. Underclocked to 800mhz and undervolted slightly.
Anyone else experience and issue like this?

Yep, except I was on bonsai and my problem with the fc made me Yank the battery. Upon reboot there was the android telling me to touch him to begin.
Sent from my Illudium Q-36 Explosive Space Modulator.

I've had that happen once, while using the tethering function, but couldn't replicate it even when trying (yes, I don't know why I tried to break my phone either, but I guess that's what they say about curiosity killing things..)

I did over memorial day weekend. Visiting the west side of Mi... Phone outside charging via wall, streaming pandora through wifi, plugged into speakers sitting in the sun. I use a battery monitor widget that gives a readout of temp... I looked ay the phone and it was at 128°F! Quickly unplugged, shut down the phone, pulled battery and took inside to cool. After 30 minutes when phone and battery seemed to return to room temp I turned the phone back on and once the os booted up everything fc... Nothing would run at all! Luckily I also had a backup to cover me. I was on srf 1.1.1 btw...
Sent from my SPH-D700 using XDA App

i disassembled my entire phone and when i reassembled it i got a bunch of force closes till i restored a back up.

I have had this happen quite often.. It is usually when I am charging and talking on me way home from work.. I will have the phone sitting on the seat next to me, using a headset, sitting in the sun most the time. And it will give me the warning and then reboot, usually when I get off the phone. And when it loads FC's out the butt and just loops. I normally never have a backup, so I just clockwork and reload the rerfs zip and it takes me back to rooted stock and i reload from there.. I can do it pretty quick these days... It actually did it over the weekend and I tried clearing the dalvik cache(sp??) and the cache and it seem to fix the fc's. But I need to just get in the habit of keeping a current backup.. Any way to schedule one in clockwork??? That would be a nice feature..
I actually had a post on this a long time back and got 1 reply..

I think thats a serious flaw in the design of the phone.
You can't charge AND use the phone at the same time? Because it will over heat and cause data corruption? That's ridiculous.
Does this only happen to rom'd phones? or does this happen to stock phones as well?

futureprospect said:
I think thats a serious flaw in the design of the phone.
You can't charge AND use the phone at the same time? Because it will over heat and cause data corruption? That's ridiculous.
Does this only happen to rom'd phones? or does this happen to stock phones as well?
Click to expand...
Click to collapse
i think it only happens to phones with journaling off.

it happen to me as well
but it messed everything up had to wipe and reflash sfr then everything was good but the phone was useless. luck was on my side and it was at the end of my trip.

I have always ran with journaling on!! And dang it, just got back from lunch and guess what... I didnt even have the phone plugged in.. Just talking on it.. It was sitting on my seat and all of a sudden it just rebooted. When it came back up the fc's were there and the same loop as always.. I am currently trying to see what will get me going again. I did the wipes and nothing.. The last time I got the fc's to stop, I also hit fix permissions by accident.. So I am running that now. I am not even sure what that does, but like I said last time it seemed to work.. We shall see... LOL and yeah no backup to use in clockwork.. You think I would have made one this morning huh? And I never noticed this problem until after froyo...
BTW- The fix permissions and combo cache wipe has me back in business..

I think the ability to schedule a regular backup weekly or something would be a GREAT feature for any recovery....
Sent from my SPH-D700 using XDA Premium App

[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

Phone is Broken

Alright, so like many people, I tried to play Pokemon GO. I was playing for about 20 minutes on my break at work, and I noticed that as I was switching between it and other apps, my phone was getting pretty laggy and bogged down, to a point where the phone just froze for a minute, then when the screen turned off. I couldn't turn it on for a further minute or so. Eventually after a few minutes of this, the phone just crashed, Upon trying to restart it, it went to the odin screen, saying "mmc_read error", or something like that. I pulled out the battery and let it sit for a few minutes and tried again. It started to boot, but it was stuck on the phone's model splash screen for several minutes, which its never done before. After the phone finally got booted up, it would freeze often, and I would not be able to turn the screen back on for several minutes at a time. This has persisted all night, crashing and freezing for the remainder of my shift. After I got home I tried restarting it again, and the phone wouldn't turn on at all, so I again pulled the battery and let it sit for a while. I've done this a few times now.
Sorry it's a bit lengthy, but I tried to recreate the events of what's happened as best I could. If you need any other info just ask
I have uninstalled the game from my phone now, the phone is completely stock, no roms, not rooted. I do not recall it feeling too hot as if it had overheated
I really am not experienced with issues like this, and I really would not like to have to buy a new phone

Hmm, that error is supposedly of the EMMC failing, now you will be lucky if it was a one time incident. Now to be quite honest I don't think anyone could tell you that whether the problem will come back or not, and you can't do much anyway. I will say if the phone is running okay now, let it. Or if you are really unlucky then the problem will come back, the EMMC might fail permanently. But if you see one or two more reboot incidents like that, I think its fair to conclude that your phone is done mate.

Currently I can turn on the phone, but after I turn the screen off, it won't come back on again

Oh darn mate. You could try to wipe the phone completely from recovery (TWRP) and then flash the stock ROM. Now please don't blame me if the phone gets dead or something after that, cause my Note 3 died just few months back, and it took me a good couple of months to get over that fact. However one thing is for sure, if your emmc is supposed to fail, or motherboard, then it will no matter what.