Related
Hi everyone,
It's been a while since I've been active here, but I've recently discovered a weird problem with my phone - I can't get it to turn *off*.
I rarely try to turn it off, so I have no idea how long it's been doing this, but I was on a plane recently and discovered that whenever I try to power it off, it'll pop right back on as soon as it shuts down.
I'm on CM7.1.0, but it's the same when I go back to my nandroid backups of 7.0.3, 7.0.2, and even stock 2.2! I have then eng-hboot (0.76.2000), radio is 26.08.04.16_M, recovery is CWM 5.0.2.0, but the same thing happened on 3.0.2.4. I can provide more info if needed.
Can anyone help?
Just... take the battery out?
martonikaj said:
Just... take the battery out?
Click to expand...
Click to collapse
Thats not really a permanent solution is it ?
bombadier said:
Thats not really a permanent solution is it ?
Click to expand...
Click to collapse
But I mean how long is he going to keep his phone off for? If you're keeping the phone off for a long time, you shouldn't store it with the battery inside anyways.
chinly43 said:
Hi everyone,
It's been a while since I've been active here, but I've recently discovered a weird problem with my phone - I can't get it to turn *off*.
I rarely try to turn it off, so I have no idea how long it's been doing this, but I was on a plane recently and discovered that whenever I try to power it off, it'll pop right back on as soon as it shuts down.
I'm on CM7.1.0, but it's the same when I go back to my nandroid backups of 7.0.3, 7.0.2, and even stock 2.2! I have then eng-hboot (0.76.2000), radio is 26.08.04.16_M, recovery is CWM 5.0.2.0, but the same thing happened on 3.0.2.4. I can provide more info if needed.
Can anyone help?
Click to expand...
Click to collapse
Does this only happen when the device is plugged into the charger/connected via USB?
Sent from my HTC Vision using XDA App
1) Yes, pulling the battery works of course, but there should be a way to turn it off without doing that. And it comes on instantly when the battery is reinserted.
2) It happens regardless of whether it's plugged in or not.
Maybe I should try re-installing the engineering fastboot? Or try a different radio?
This was happening to a lot of CM Nightly users a few months ago (myself included), and it fixed itself a few days after it started. I still have no idea what caused it.
Sent from my Transformer TF101 using xda premium
This happened to me just the other night. I needed to power off for a short while - I pulled the battery. I don't think it happens every time, but I was able to pull the battery and then reinsert it without the phone rebooting immediately.
It happens to me form times to times but i think its nothing serious so i just take the battery out
An update - I tried turning it off while plugged into my computer and watching the log in DDMS; it *CAN* turn off when it's plugged in! Still nothing when it's unplugged, though.
Anyone have any ideas how to fix this? Like others have said, it's not like this is a major problem - I can always just pull the battery if I need the power to be off for some reason. And it's not like phones really need to be off for air travel, so I can't even think of a reason I would need it off, but still - this is obviously a flaw in something, and I can't stand knowing that it's not working exactly right. I think I'm going to flash a different radio, see if it makes a difference, but if anyone has any ideas how/why this is happening, I'd really appreciate you sharing them.
ETA: updating the radio didn't change anything.
same problem--- keeps turning back on
IOn my Desire Z running MIUI, i turn it off and it shuts down to turn itself back on! Very annoying, particulary when on a plane. Taking the battery off, OBVIOULSY fixes it. But not a very practical solution.
Similar to post above, it stays off when connected to USB. Go figure!
I think I read somewhere that this was a clwm issue with the most recent recovery, have you tried flashing a different one? Older or maybe try 4ext?
PS just reread your first post sorry, it seems you already tried a different recovery.
For the OP, since you tried reflashing, and I'm sure you wiped, then I would imagine it isn't a issue with the ROM, the radio didn't help so maybe bootloader or recovery.
OP here, sorry I hadn't checked in for a while. For unknown reasons, the problem's gone. No big changes to my phone, so the issue vanished as mysteriously as it appeared.
Alright so ive used the search and couldnt find anything. I have a rooted s2 running eagles blood v1.1 and last night i flashed over lite'ing theme and now my phone screen will shut off and wont allow me to turn it back on, i have to hold the power button and it restarts. Ive reflashed eagleblood even recovered back to stock with just root and it continues to do it.
Any help would be much appriciated :/
Sent from my SGH-T989 using XDA App
Probably best to post this in the rom developer's thread. Any number of things can cause this behavior.
I would but my post count is low and i am unable to post there, so for now i am seeking help here.
ive tried un-rooting the phone, flashing the stock rom and no root, but have the same issue.
Did you wipe the caches in recovery?
treo...not! said:
Did you wipe the caches in recovery?
Click to expand...
Click to collapse
sure did, every time i reflashed/flashed i wiped everything
still contines, ive wiped everything, unrooted with factory resets, tried stock rom, eagles blood rom, reflashed multiple times.
screen shuts off and will not turn back on, have to hold power button and phone reboots.
IProbablyDidit said:
still contines, ive wiped everything, unrooted with factory resets, tried stock rom, eagles blood rom, reflashed multiple times.
screen shuts off and will not turn back on, have to hold power button and phone reboots.
Click to expand...
Click to collapse
Are you using SetCPU? I had this problem from a screen off profile where I could get calls or have my alarm go off yet not able to wake the screen unless I manually powered it off and on.
Sent from my EagleBlood-infused SGSII or my GTab 10.1 now "In Paris"
bhowanidin said:
Are you using SetCPU? I had this problem from a screen off profile where I could get calls or have my alarm go off yet not able to wake the screen unless I manually powered it off and on.
Sent from my EagleBlood-infused SGSII or my GTab 10.1 now "In Paris"
Click to expand...
Click to collapse
setcpu ? youll have to bare with me a little bit as i dont know probably all i should
odin back to stock with zedomax file! that usually fixes all probs
GRAB THIS STUFF :http://forum.xda-developers.com/showthread.php?t=1323878
Enjoy and also make sure u have the proper samsung drivers
movieaddict said:
odin back to stock with zedomax file! that usually fixes all probs
GRAB THIS STUFF :http://forum.xda-developers.com/showthread.php?t=1323878
Enjoy and also make sure u have the proper samsung drivers
Click to expand...
Click to collapse
i have tried this already, does not work :/
I'm having the same problem on rooted stock rom. It's getting more and more frequent. The phone just refuses to come back on after going to sleep. If I plug in the power/usb cable, it actually makes the connected noise as if it's actually awake but the screen stays off.
I've uninstalled all cpu and memory tweaking apps and am still experiencing the issue.
KaneHusky said:
I'm having the same problem on rooted stock rom. It's getting more and more frequent. The phone just refuses to come back on after going to sleep. If I plug in the power/usb cable, it actually makes the connected noise as if it's actually awake but the screen stays off.
I've uninstalled all cpu and memory tweaking apps and am still experiencing the issue.
Click to expand...
Click to collapse
ive tried everything, flashed over and over, un rooted, different roms etc nothing has worked so i just used zedomax's stock rom to restore the phone ( problem still continues) called tmobile and will have my replacement within a day or so, nothing else i can do i suppose.
though my problem did seem to start right when i flashed lite'ing theme for eaglesblood (not saying that caused it )
IProbablyDidit said:
ive tried everything, flashed over and over, un rooted, different roms etc nothing has worked so i just used zedomax's stock rom to restore the phone ( problem still continues) called tmobile and will have my replacement within a day or so, nothing else i can do i suppose.
though my problem did seem to start right when i flashed lite'ing theme for eaglesblood (not saying that caused it )
Click to expand...
Click to collapse
i had the same problem with the phone when i got it , i think its gotta be something with the phone.if mine continues then im sending it back also
tigerz0202 said:
i had the same problem with the phone when i got it , i think its gotta be something with the phone.if mine continues then im sending it back also
Click to expand...
Click to collapse
im starting to think it is a phone issue myself, going to find out Tuesday when my new one arrives though i am hoping it was an error on my part because this phone has the chance to be fantastic.
I was having random shutdowns with my 1st phone, the thing is I never did have stock long enough (rooted after 45min of gettjng) to see if it was the phone or root/rom(s).
My second phone is working great without any random shutdowns, but I'm still stock(running on second day of testing).
Gonna root and flash tomorrow and hope everything remains the same if not back it goes before my remorse period ends.
I really think it's phone related rather then a rom because I've never had this problem with previous phones.
So I would suggest on exchanging it.
Sent from my SGH-T989 using xda premium
htc2364 said:
I was having random shutdowns with my 1st phone, the thing is I never did have stock long enough (rooted after 45min of gettjng) to see if it was the phone or root/rom(s).
My second phone is working great without any random shutdowns, but I'm still stock(running on second day of testing).
Gonna root and flash tomorrow and hope everything remains the same if not back it goes before my remorse period ends.
I really think it's phone related rather then a rom because I've never had this problem with previous phones.
So I would suggest on exchanging it.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
i do appreciate the feed back, and from everyone who did give it. after lots of research and back and fourth between stock and custom roms i definitely wanted it to be the rom so it was fixable but im about 96% sure its the actual phone its self.
First, I'd like to thank the DEV for the Energy ROM. I've run the last two releases and it is truly spectacular. The latest version with Hashcode's Kernel makes it a completely functional daily user (not that the SOD's in the last one made it any less amazing). I understand the battery issues associated with it, and have read through the workarounds in the DEV forum, but this issue seems to be beyond those. On any given day, I leave the house for work with a full charge and, even if I'm not able to use it during the day, I get home and am hovering around the 50% level. Not a big deal, but the last two days I've taken it a step further and did a hard power off before I left (held power for the 20s). When I got back 10 hours later and tried to power it back on, it was completely dead. First day I thought, just a fluke, maybe the power button got bumped accidentally. But two days in a row, while the KF was secured in a hard case, got me concerned. Is anyone else running into this sort of issue? This is by far the best ROM i've run on the KF, and tomorrow I won't bother to shut it down, but I'm curious as to what could be the cause. I'm running at the standard 1200/600 clock speed, but with it shut down, to my understanding I shouldn't see any significant battery loss, right? I'm definitely a noob when it comes to android, so if this is an issue easily remedied, I apologize up front. Thanks in advance for any help offered, and thanks again to all that made this ROM possible!
It's a known issue for older kernels (not sure about the latest one) that if you force the shutdown, it may sometimes turn on at random a while later - this is probably what happened, it turned on a while after you left it off, and then just ate through the battery during the day until you got back home.
If you have flashed the latest kernel, using the "normal" Shutdown option should work (not sure if the ROM would need to be updated or not) fine, so far I've never had it turn back on after using it, but I'm using Hashcode's ROM instead.
Otherwise, just reboot into TWRP and press "Reboot" - "Power Off", which will make it stay off... hopefully.
Thanks, I'll give it a try through TWRP and see what happens. FYI I'm running release #8 of the 3.0 kernel if that sheds any light on the problem
Sent from my Amazon Kindle Fire using XDA
I too had battery issues with EnergyROM... things seem stagnant there so I flashed gedeROM last night and so far so good.
psudeke said:
FYI I'm running release #8 of the 3.0 kernel if that sheds any light on the problem A
Click to expand...
Click to collapse
It'd be for the best if, at the very least, you flash kernel #10, as it allows for "normal" shutdown (ie, no need to go through TWRP or to force the shutdown by holding the power button 10-20s), though I'd recommend switching to Hashcode's ROM (better support, plus a few more ROM only features) instead, at least until everything slows down a bit.
Thanks for the advice. I'll take a look at his ROM as well. I thought about just flashing the #10 kernel, but i understand you lose some of the functionality of the kernel since the ROM isn't designed to take full advantage of it.
Sent from my Amazon Kindle Fire using XDA
So, lately my phone has been acting kinda weird.. Basically, it'll shut off on it's own, no matter what my battery level or if I'm on the charger, its pretty random. When I go to turn it on, it shows me the samsung logo and shuts off after about 3 seconds of the galaxy s3 logo. It does the same in download mode and recovery. The phone will stay off and do that for an hour or more, and then itll turn on and be all dandy again for hours or at least another day. I'm going to take off all my pictures on the sdcard and odin back to stock as soon as possible for warranty, but does this sound like a hardware failure or software? I read about the s3 sudden death syndrome, but this one isnt permanent. Any ideas?
I agree with your assessments.
I'd wonder about overheating or a bad battery.
Sent from my SGH-T999 using xda app-developers app
what's your setup as of right now?
Beware if it shuts down when your flashing back to stock in the middle of the process it may never turn back on.
Sent From My Galaxy S3 Boricua 100%
It might be the kernel that came with the ROM you installed. I used to have problem with ktoon kernel.
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
mejorguille said:
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
Click to expand...
Click to collapse
If you have an app that controls kernel voltage that is still set up for set on boot and the voltage is too low when it boots or is granted root it'll kill it in this manner. Otherwise your phone is [email protected]#
Sent from my SGH-T999 infected with AnthraX using Tapatalk 2
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
I used the phone for work, not play, no overclocking was done neither was any undervolting. I ran stock kernel settings.
Aerowinder said:
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
Click to expand...
Click to collapse
I remember a time when XDA had helpful answers and users weren't reduced to insults. I've been around a couple years, hacked more phones than I can count and flashed hundreds of roms in my days, back when everything was still done in adb and terminal emulator. It's no wonder a lot of decent user has started moving over to rootzwiki
Phone decided to start acting strange.
Barely responsive like processor went bad or it has no ram.
I reflashed SPH-D700-FC09-8Gb-REL.tar.md5 though odin thinking it might clear it up like its a kernal issue.
But now I got stock bootloader and I cannot even use the options in it It wont boot otherwise, just sits at the S logo and the graphic plays really really slow. 1 frame every 5 seconds or so.
not sure what's going on.
I don't keep up on the kernals and roms and all that, I was running a rom from june last year and was happy with it.
What am I missing?
A lot of the development links are starting to go bad for things like roms and such.
Okay. so after flashing this and doing that and messing with this and that.
I can get it to boot now. Sometimes it works good, other times its boot hanging on me.
When I do get it to boot, the screen will not respond.
So if I flash the FC09 stock rom, it will let me touch the button on the first pop up, but after that the screen is locked out or something.
I found a clean rom and installed that.
Looks like the rest of my files and such are already the same ones that are currently being used, no major advancements in the last year. That makes it easy.
So currently getting boot lockup after flash and reset. Not sure whats going on there.
I just dont' do this often enough.
And the screen lock up.
Not sure on the screen lock up after clean kernal install.
It's re-flashing fc09 again and I'm tired and going to bed.
Touch screen only working when keyboard slid out.
Very weird.
Not really getting anywhere with this.
First fc09 install will boot.
Screen will not work right.
after restart wont move past samsung screen.
After a deodex install and CWM, it acts really slow again.
I'm going to guess it has memory corruption.
During one of my installs the phone worked like normal and after the deodex update it started working laggy again and has been that way ever since.
ODIN?
To clarify, you used ODIN to flash FC09? In case not, instructions are here
http://forum.xda-developers.com/showthread.php?p=24694921
Also, I think other people have reported general weirdness on their OG Epic 4g's when the battery is bad. There's a battery thread in the Q/A forums.
good luck
pentium0 said:
To clarify, you used ODIN to flash FC09? In case not, instructions are here
http://forum.xda-developers.com/showthread.php?p=24694921
Also, I think other people have reported general weirdness on their OG Epic 4g's when the battery is bad. There's a battery thread in the Q/A forums.
good luck
Click to expand...
Click to collapse
Wasn't a bad battery. I have multiples.
Just went and got a new phone. Something was wrong with the hardware.
Thanks for the help though.
sarinhighwind said:
Wasn't a bad battery. I have multiples.
Just went and got a new phone. Something was wrong with the hardware.
Thanks for the help though.
Click to expand...
Click to collapse
If you run into it again you may have a bad download or cable. Bothe resulted in all the errors you where discribing. Solved it with a good download and a different cable.
Expereanced slow 'S' boot and boot loops with a bad cable mainly and bad downloads caused all sorts of slowness, hangs, unresponsiveness and one moment of very warm lap.
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
I had an issue where my modem wouldn't work...ever. it was totally bricked. In my quest I found the pc re-recognizes the device when I used a different usb cable,(from my note 2) & I changed the com port in device manager. I know its lame to pump my own stuff but at the end of my thread in this section, I have a pic that shows how & where you can pick your own com port in advanced settings in windows. I hope any of this helps.