Ever since i flashed clockword recovery, i shut off the phone to charge it at night, but once i plug in the phone, it boots into recovery! Always. Maybe i messed up something in the process? What can i do to fix it?
I'm running on stock, rooted n s-offed
Sent from my T-Mobile G2 using XDA App
Dream Reality Syndrome said:
Ever since i flashed clockword recovery, i shut off the phone to charge it at night, but once i plug in the phone, it boots into recovery! Always. Maybe i messed up something in the process? What can i do to fix it?
I'm running on stock, rooted n s-offed
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
it is a known issue with CWM.
You didn't do anything wrong, nor is there anything messed up. This is a known issue with ClockWorkMod at the moment. There is a 'fixed' version (unofficial) floating around somewhere, but it's not ideal. Depending on why you're turning your phone off, there are a number of alternatives:
1. put your phone in airplane mode while charging - this turns off all the radios, so your phone will charge *MUCH* quicker than it would otherwise. You can, of course, turn the display off, if the light is bothering you
2. Simply put the phone in silent mode (and either put it face down or turn the display off) if you're doing this while you're asleep.
There's an explanation on the ClockworkMod thread, but it doesn't really matter - fact is, that's how it is (for now).
Thank you Orange Bandit. I shut off my phone only to feel better about it charging, not getting hot I suppose. I always got this feeling charging the phone while it's on isn't too healthy. I think I will try the airplane mode!
Sent from my T-Mobile G2 using XDA App
I don't turn my phone off ever, unless it's locked up or something. I do have an app that I got from the market called CT Scheduler that automatically reboots my phone at a specified time (I have it at 2am every morning, while i'm asleep). Aside from that, my phone is literally always on.
The phones nowadays are designed to be used all the time - charging it with the phone on won't hurt it, but it most definitely charges faster in airplane mode. Often, if my battery is low and I've got 15-20 minutes to drive somewhere, I'll put it on airplane mode to charge in the car, just to get a bit more juice.
Somebody did post in that thread with a fix to the recovery. I have had it for some time now and it works great.
Is the fix official? Or at least work as well as the original wit no hiccups?
Sent from my T-Mobile G2 using XDA App
hey folks, im coming over from the galaxy s section...besides not staying off to charge, are any other problems reported? for instance, we use a program called odin to flash without cwm. its a kind of fail-safe. but, i cant get my pc to recognize the phone....anything similar with your phones? not looking for help necessarily, just similar occurrences.
Related
Hey as everyone knows there are some people having LOS and it will remain that way until after a reboot. First I'm rooted but not with a custom kernel. I'm on the stock kernel(just flashed CWM and then root.zip) So I have had LOS a few times since I got my phone. Just a few minutes ago I got LOS after a phone call and it remained that way. AbsolutZeroGI on IRC wanted me to try something whlile I had LOS before I rebooted. I went into the task manager, selected the ram tab and then pressed the clear button. That didnt bring service back but after I did that I did get the roaming notification(but still had LOS) so I plugged my phone into my PC(not to try to fix it but to boot into recovery) and then I noticed my signal came back without a reboot as soon as I plugged in the cable. Now I'm not really sure if/why plugging in the USB would correct this or if it was just a coincidence or if it fixed it. Although I know the other times I had LOS it didnt come back until a reboot no matter how long I waited.. So I would like to run a test..
The next time you get LOS go into the taskmanager, select the ram tab and then click clear, then plug your phone into your PC (Edit: While your screen is off). Did your signal come back or do you still have LOS?
EDIT:
I just got home, was sending a few text messages had a signal, put my phone down, came back and turned on the screen and I had no service. So I came back to my PC to test this out again. When I came back to the PC I had a PM from AbsolutZeroGI. He told me he just got the LOS and the steps didnt work. And so far I've been the only one to get it to come back without a reboot. So I tried again.. I plugged it in and unplugged it multiple times... nothing.. still no service, I tried to remember the exact steps I did the first time and I thought "when I plugged it in and it worked was my screen on or off" So I tried one more time. I turned the screen off, waited a few minutes, had the usb cable plugged into the pc then plugged in the phone. I waited a few more seconds, turned the screen on and boom, I had almost all the bars but no 3G icon and a few seconds later the 3g icon came back on.
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
Thank you in advance for everyone who tests this out for us. If we can find a real method that works every time we can start working on a temporary fix until Sammy gives us a firmware update so LOS won't be so bothersome.
i have not experienced the los, but have experienced very poor signal when trying to connect to the net. but when i rebooted the signal did get better
Although I know some people stated that they had this issue on unrooted phones as well as rooted, I myself had the issue with my first Epic Touch after I rooted. Before I rooted, I never experienced the issue.
I exchanged my phone Thursday because there was no way to return to stock at the time and I haven't experienced the LOS of service at all.
plmiller0905 said:
Although I know some people stated that they had this issue on unrooted phones as well as rooted, I myself had the issue with my first Epic Touch after I rooted. Before I rooted, I never experienced the issue.
I exchanged my phone Thursday because there was no way to return to stock at the time and I haven't experienced the LOS of service at all.
Click to expand...
Click to collapse
Hmm maybe I'll install the stock kernel and see of that fixes it. I only had my phone since yesterday and it was rooted after an hour or so of having it and since I've had at least 5 Los. :-( but I have read the same that people claim its happening to them as well without ever rooting
Sent from my SPH-D710 using XDA App
I'll definitely try in a few when my los kicks in. Had my first touch for three days and no los occurrences but my new one has had them 5 times in two days.
Sent from my SPH-D710 using xda premium
I've had my phone since launch day. I didn't root until the 20th. I had no LOS in that time I was completely stock. Right after I installed bubby's CWM and root the problems started. I mean the same night. It had happened several times until I went back to the stock kernel. I have since had the LOS for literally 5 seconds while it switched from Sprint to roaming and service was right back. Not a problem since. I'm not saying these other kernels are the complete problem and that the phone is not without bugs. I just think that maybe the other kernels make the problem (if any) worse.
---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------
jirafabo said:
I'll definitely try in a few when my los kicks in. Had my first touch for three days and no los occurrences but my new one has had them 5 times in two days.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
The other night I had 5 times in two hours. Literally!!
I'm completely stock and picked up my phone on Launch day. I had several LOS during the first few days. I updated my PRL, Profile, Firmware etc. and it hasn't been an issue since.
I do have an issue roaming, as in my phone wont.
Ok guys, I'm going to update the OP but here is a new development.
I just got home, was sending a few text messages had a signal, put my phone down, came back and turned on the screen and I had no service. So I came back to my PC to test this out again. When I came back to the PC I had a PM from AbsolutZeroGI. He told me he just got the LOS and the steps didnt work. And so far I've been the only one to get it to come back without a reboot. So I tried again.. I plugged it in and unplugged it multiple times... nothing.. still no service, I tried to remember the exact steps I did the first time and I thought "when I plugged it in and it worked was my screen on or off" So I tried one more time. I turned the screen off, waited a few minutes, had the usb cable plugged into the pc then plugged in the phone. I waited a few more seconds, turned the screen on and boom, I had almost all the bars but no 3G icon and a few seconds later the 3g icon came back on.
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
graffixnyc said:
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
Click to expand...
Click to collapse
I saw that theory from someone else around here as well. Definitely seems like something is going to sleep and not coming back on and the modified kernels seem to exacerbate the issue for some reason. (Maybe the source Samsung released is older than what the phone shipped with and the issue was improved between the two versions?)
Nothing against the devs or anything like that, but this LOS issue is why I havent rerooted my current Epic Touch.
As much as I want to flash that new
midnight roms, I'm holding back just for that reason.
This message was developed and sent from my SGSII-EPIC 4G TOUCH!
graffixnyc said:
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
Click to expand...
Click to collapse
That wouldn't work, because in reality, the phone checks cell towers for new calls something like every 5-10 seconds. No sleep for the wicked radio.
No. It is definitely something that disables the radio entirely.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
plmiller0905 said:
Nothing against the devs or anything like that, but this LOS issue is why I havent rerooted my current Epic Touch.
As much as I want to flash that new
midnight roms, I'm holding back just for that reason.
This message was developed and sent from my SGSII-EPIC 4G TOUCH!
Click to expand...
Click to collapse
There's no reason not to root the phone now AT ALL.
The current root method of:
1) Install custom recovery+kernel,
2) Flash su binary,
3) Flash stock recovery+kernel
---
The current root method does nothing but add files to /system partition -
you change nothing else in the operation of the phone but add root privileges.
Flashing roms while they are in beta though, that's just asking for trouble, unless you are testing for the rom builder.
I have the LOS icon at this very moment, yet I just received a call? Also, I plugged it into my computer, but nothing changed.
Hi all. I just had LOS and tried to use my car charger instead of my computer. It didn't fix the issue but I did notice that the charging led wouldn't illuminate. after reboot the phone gets signal and the led is working fine. I don't know if that is significant but wanted to mention it.
Sent from my SPH-D710 using XDA App
Interesting thread. Ive had mine for 3 days now and havent experienced this at all.
Sent from my SPH-D710 using Tapatalk
about 5 times a day when i try to place a call the call get stuck in "dialing" mode and never connects. if I try to end it it is still stuck in the task bar and there is no way to make another call unless I reboot. The signal bars look normal. is this the LOS?
I bought two E4GT's on launch day and I told the lady to just activate them and I would do the rest of the setup. She was messing around with them for awhile and I asked her what was going on, and she said they were doing a system update.
That makes me think that the factory firmware had the bug, but they already had an update at launch. If that is the case, I think there's a good chance the source code released was for the original firmware, which reintroduced the bug into all the custom kernels.
This could also explain why some unrooted users have the los - maybe their Sprint store was too lazy to do the update for them (although they should have got a notice for the ota update by now).
FWIW, neither of our phones have this issue and both are still stock. Baseband version is EG30.
Sent from my SPH-D710 using xda premium
leond said:
about 5 times a day when i try to place a call the call get stuck in "dialing" mode and never connects. if I try to end it it is still stuck in the task bar and there is no way to make another call unless I reboot. The signal bars look normal. is this the LOS?
Click to expand...
Click to collapse
No, but that is major suckage, happens to me once a day. Makes me want to punch babies.
los, which I get too, is when you get the no smoking signal instead of a cdma signal.
I went to root+stock kernel and the problem is gone and LOS is gone to
txmikester said:
I bought two E4GT's on launch day and I told the lady to just activate them and I would do the rest of the setup. She was messing around with them for awhile and I asked her what was going on, and she said they were doing a system update.
That makes me think that the factory firmware had the bug, but they already had an update at launch. If that is the case, I think there's a good chance the source code released was for the original firmware, which reintroduced the bug into all the custom kernels.
This could also explain why some unrooted users have the los - maybe their Sprint store was too lazy to do the update for them (although they should have got a notice for the ota update by now).
FWIW, neither of our phones have this issue and both are still stock. Baseband version is EG30.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
There was no update when these phones were released. If she was activating the phone then she was 9/10 referring to a profile update and prl update which each phone does when being activated.
Sent from my SPH-D710 using xda premium
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.
I was going to update to latest AOKP, I selected reboot to recovery, phone turned off and never turned back on. I can't get into recovery mode either this is very odd any ideas?
This is very strange because this should not cause a hard brick... when I selected reboot to recovery it seemed like it froze for a second, but though it was just in the middle of restarting, then it just shut off. Why would that cause this, only thing I can think is maybe my battery drained... I have it hooked up to a charger right now. But like I said I can't get the phone to do anything.
Same thing happened to me with Galaxy Note from AT&T, I've been looking in several forums about this, but since the phone is not even charging the battery or booting, I'm loosing hope.
This suck ass
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
i apologize if this has been solved but i am on a very tight time frame as i need this phone for work and cant spend any longer searching. my phone randomly turned off by itself this morning and will not turn back on. it gets to the samsung splash screen and the screen just goes black and the phone wont do anything, its like the screen is stuck off, i have to take the battery out to make it turn do anything at all again. it was stock this morning, never been rooted or anything, i just rooted it about an hour ago and installed twrp and flashed jedi invasion 5 on it in hopes it would help. now it gets past the splash screen and to the initial setup screen but it only stays on it for about 3 seconds before the screen goes black again and i have to take the battery out for it to do anything again. im not an expert by any means but i have flashed note 2's and played with them a bit and know my way arround them for the most part. any help would be EXTREMELY appreciated.
almost forgot to mention, in download mode it says qualcomm secureboot: enable
not sure if that means anything but i didnt get any errors while flashing or anything
thanks everyone
samsung sgh-i747m
d_tuned said:
i apologize if this has been solved but i am on a very tight time frame as i need this phone for work and cant spend any longer searching. my phone randomly turned off by itself this morning and will not turn back on. it gets to the samsung splash screen and the screen just goes black and the phone wont do anything, its like the screen is stuck off, i have to take the battery out to make it turn do anything at all again. it was stock this morning, never been rooted or anything, i just rooted it about an hour ago and installed twrp and flashed jedi invasion 5 on it in hopes it would help. now it gets past the splash screen and to the initial setup screen but it only stays on it for about 3 seconds before the screen goes black again and i have to take the battery out for it to do anything again. im not an expert by any means but i have flashed note 2's and played with them a bit and know my way arround them for the most part. any help would be EXTREMELY appreciated.
almost forgot to mention, in download mode it says qualcomm secureboot: enable
not sure if that means anything but i didnt get any errors while flashing or anything
thanks everyone
samsung sgh-i747m
Click to expand...
Click to collapse
I would make sure you have to correct drivers installed for the phone on your computer and ODIN back to stock. You can give that a try and see if it helps.
I'll check that out when I get home but I'm pretty sure everything is right, it was doing it before I even flashed anything so I think something else is the problem
Sent from my SAMSUNG-SGH-I317 using Tapatalk
d_tuned said:
i apologize if this has been solved but i am on a very tight time frame as i need this phone for work and cant spend any longer searching. my phone randomly turned off by itself this morning and will not turn back on. it gets to the samsung splash screen and the screen just goes black and the phone wont do anything, its like the screen is stuck off, i have to take the battery out to make it turn do anything at all again. it was stock this morning, never been rooted or anything, i just rooted it about an hour ago and installed twrp and flashed jedi invasion 5 on it in hopes it would help. now it gets past the splash screen and to the initial setup screen but it only stays on it for about 3 seconds before the screen goes black again and i have to take the battery out for it to do anything again. im not an expert by any means but i have flashed note 2's and played with them a bit and know my way arround them for the most part. any help would be EXTREMELY appreciated.
almost forgot to mention, in download mode it says qualcomm secureboot: enable
not sure if that means anything but i didnt get any errors while flashing or anything
thanks everyone
samsung sgh-i747m
Click to expand...
Click to collapse
Faulty battery or power button. You can try ODIN back to stock, not likely it will help.
It's not a battery or power button problem. Before I rooted it if I took the battery out and turned it on again it would turn on fine if I kept the screen from turning off. and the battery was staying charged, and if it wer a power button problem why would it work to turn the phone on but not again after its on?
Sent from my SAMSUNG-SGH-I317 using Tapatalk
d_tuned said:
It's not a battery or power button problem. Before I rooted it if I took the battery out and turned it on again it would turn on fine if I kept the screen from turning off. and the battery was staying charged, and if it wer a power button problem why would it work to turn the phone on but not again after its on?
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
My vote is a faulty power button. Has been known to happen on the S3. Could be power issues though. Bad battery could be the culprit. If flashing stock does not work see if you can get a battery to test out.
Sent from my Inspire 4G using xda app-developers app
ok so i flashed stock and it fixed it temporarily. after i flashed it it was working great so i decided to root it and flash jedi. so i did this and it still worked great. (at this point i should mention that the sim card in the phone has been deactivated this whole time) so since its working i activate the simcard, restart the phone, and the problem started again. so i took the sim card right out and turned it back on and it works perfectly fine without the sim card in... what do you guys figure? should i try a new sim card? has anyone ever herd of this happening before?
EDIT: tried my other sim card in it and it doesn't work either, so it snot the simcard itself
Bump
Sent from my SAMSUNG-SGH-I317 using Tapatalk
How could it be the battery or power button at all... Very helpful guys
I was beginning to think I was crazy, thank you lol
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Flash back to stock and return.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hey guys,
since ~a week I got a heavy-ass problem with my Samsung Galaxy Nexus (GSM). I am using the Cyanogenmod Nightly Version cm-11-20150412-NIGHTLY-maguro.zip (bootloader version primemd04; cwm version 6.0.5.1). I know that nightly versions are not really stable and still have a lot of problems, but so far everything didn't went that badly. At least I was able to use the phone...
So last week I put my phone in airplane mode. That was when the disaster started.
Now what happens when I start my phone is, that it starts in airplane mode with wi-fi on and no matter what I do, restarts after ~1min. Sometimes it even shuts down, when starting it in recovery mode.
What I tried so far is:
factory reset ---> most of the time it shuts down halfway done and restarts as if nothing happened.
updating CM ---> restarts as if nothing happened.
I'm really lost right now, but still don't want to give up all hope.
Thanks for every kind of help!!
Cheers,
Lovis
Try to get a legit application that tells you the real CPU temperature like FKUpdater, in case you have franco.Kernel. Then just run heavy tasks on in. If it just ****s doen,might be a problem with the battery. Mine just shutdown on itself just by doing common tasks like calling. Replacing the battery fixed it. Another thing O realized was that if you plug it in the charger and use it was helping it not restart. Try this method. If it restarts then its pretty much a ROM or hardware related problem, if not then a battery problem for sure.
Sent from my Galaxy Nexus
It has to be some kind of ROM problem. Before I got in airplane mode the phone worked almost perfectly.
AdmiralulNipples said:
Try to get a legit application that tells you the real CPU temperature like FKUpdater, in case you have franco.Kernel. Then just run heavy tasks on in. If it just ****s doen,might be a problem with the battery. Mine just shutdown on itself just by doing common tasks like calling. Replacing the battery fixed it. Another thing O realized was that if you plug it in the charger and use it was helping it not restart. Try this method. If it restarts then its pretty much a ROM or hardware related problem, if not then a battery problem for sure.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse