I used tobe able to run ICS roms fine.
But, out of no where, My phone froze up completely, so I had to do the usual pull out the battery trick.
It always worked, but This time it happens that the screen never woke up again.
The soft button lightings came up but the screen stayed dead.
I thought this was the rom issue and switched to other roms.
What I found out is that this happens with only ICS roms.
Gingerbread roms work fine.
Has anyone experienced this problem?
and Is there some kind of solution to this?
I really want to go back to ICS
Thanks in advance )
pyg1991 said:
I used tobe able to run ICS roms fine.
But, out of no where, My phone froze up completely, so I had to do the usual pull out the battery trick.
It always worked, but This time it happens that the screen never woke up again.
The soft button lightings came up but the screen stayed dead.
I thought this was the rom issue and switched to other roms.
What I found out is that this happens with only ICS roms.
Gingerbread roms work fine.
Has anyone experienced this problem?
and Is there some kind of solution to this?
I really want to go back to ICS
Thanks in advance )
Click to expand...
Click to collapse
Welcome to the club. There are five or six of us in the same boat. For some reason the system loses the ability to remount the system partition.
No fix as of yet. You can try ReignerD's guide to unrooting and going back to stock and rerooting, but it only worked for about a week on my phone.
Related
Is anyone else having this problem? I'm using one of Sleuth255's ROMs -- and hoping I don't need to reinstall, but if nobody else is having this problem I guess I'll spend the afternoon and upgrade.
When I push the button, the phone turns on, but no backlight, it prompty turns back off. The second time I push it, there is the usual 2 second delay and on she comes like usual.
I've had this problem w/ many rom
I think i've got the same problem. I have over the past two days flashed many ROM to get the right fit.
But with all of them i'll have this problem. I didn't really think it was a ROM thing b/c i'm getting it w/ the official rOM's and cooked ROM's i think it's just part of the hardware..
please do let me know if u find something.
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.
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
PLEASE TAKE THE TIME TO READ, THANK YOU.
Hello,
I am a Galaxy Nexus user, non rooted, running Android version 4.3. Yesterday I was running 4.2.2 and everything was fine and running as normal. Keep in mind I never rooted my phone, although I have to others in the past. My Nexus was running pure official 4.2.2. I had been waiting for the 4.3 update and was extremely excited when I was the notification that it was ready for my phone. I quickly downloaded it and then it rebooted the phone, as any update should. That's where everything went downhill. The phone started to lag immediately when I turned it on. It was sputtering and jerking but I just thought it was getting used to the update. Then the phone would loose its onscreen buttons and turn the page that I was looking at full screen (meaning I couldn't press home or back, because they simply just weren't there). Then the phone froze all together and after waiting 20 minutes I finally took the battery out and tried again. The EXACT same thing has been happening ever since yesterday and it has made the phone unusable because it will freeze 5 minutes into turning it on. And we then screen times out, the screen will not turn back on, as if the phone was off, when it is not. I'm very frustrated because the phone was working flawlessly before the update and now I have to use my retired G1 because the phone is that unresponsive. I was just hoping someone could please help me, or has a similar story and could make this known to Google. Thank you for reading, please if you can, help me.
Justin
holiday29 said:
PLEASE TAKE THE TIME TO READ, THANK YOU.
Hello,
I am a Galaxy Nexus user, non rooted, running Android version 4.3. Yesterday I was running 4.2.2 and everything was fine and running as normal. Keep in mind I never rooted my phone, although I have to others in the past. My Nexus was running pure official 4.2.2. I had been waiting for the 4.3 update and was extremely excited when I was the notification that it was ready for my phone. I quickly downloaded it and then it rebooted the phone, as any update should. That's where everything went downhill. The phone started to lag immediately when I turned it on. It was sputtering and jerking but I just thought it was getting used to the update. Then the phone would loose its onscreen buttons and turn the page that I was looking at full screen (meaning I couldn't press home or back, because they simply just weren't there). Then the phone froze all together and after waiting 20 minutes I finally took the battery out and tried again. The EXACT same thing has been happening ever since yesterday and it has made the phone unusable because it will freeze 5 minutes into turning it on. And we then screen times out, the screen will not turn back on, as if the phone was off, when it is not. I'm very frustrated because the phone was working flawlessly before the update and now I have to use my retired G1 because the phone is that unresponsive. I was just hoping someone could please help me, or has a similar story and could make this known to Google. Thank you for reading, please if you can, help me.
Justin
Click to expand...
Click to collapse
Did you tried a full wipe?
tatazeuz said:
Did you tried a full wipe?
Click to expand...
Click to collapse
I have not tried that, only because I hoped there would be an alternate way without me having to format anything.
holiday29 said:
PLEASE TAKE THE TIME TO READ, THANK YOU.
Hello,
I am a Galaxy Nexus user, non rooted, running Android version 4.3. Yesterday I was running 4.2.2 and everything was fine and running as normal. Keep in mind I never rooted my phone, although I have to others in the past. My Nexus was running pure official 4.2.2. I had been waiting for the 4.3 update and was extremely excited when I was the notification that it was ready for my phone. I quickly downloaded it and then it rebooted the phone, as any update should. That's where everything went downhill. The phone started to lag immediately when I turned it on. It was sputtering and jerking but I just thought it was getting used to the update. Then the phone would loose its onscreen buttons and turn the page that I was looking at full screen (meaning I couldn't press home or back, because they simply just weren't there). Then the phone froze all together and after waiting 20 minutes I finally took the battery out and tried again. The EXACT same thing has been happening ever since yesterday and it has made the phone unusable because it will freeze 5 minutes into turning it on. And we then screen times out, the screen will not turn back on, as if the phone was off, when it is not. I'm very frustrated because the phone was working flawlessly before the update and now I have to use my retired G1 because the phone is that unresponsive. I was just hoping someone could please help me, or has a similar story and could make this known to Google. Thank you for reading, please if you can, help me.
Justin
Click to expand...
Click to collapse
Hi Justin,
I'm also a Galaxy Nexus user and the exact same thing happened to me.
I guess you already did a full wipe or threw your phone in the trash since you posted this several days ago haha. I did wipe my phone cuz it appeared to be the only option left, I fastbooted 4.3 factory image that I downloaded from the Google site.
It just so happens that yesterday I reinstalled (on 4.3 already) Lightflow LED Notifications app (last version, 3.8 I think, - when all of this happened I didn't have the last version - and the curse was back on. The same thing started to happen, the freeze, the buttons dissapearing, etc. So I obviouly proceeded to uninstall the app and guess what? Problem solved.
So I was just telling you this in case you still have your issue or if anybody else comes accross with the same problem.
I cannot be absolutely sure it's a crash between the update and the app but I think, at least on my phone, it was pretty obvious.
Hi, Since i updated to android 6.0 I have been experiencing alot of issues. My phone recently started to turn off for no reason for every Rom I install. I cant use it for 10 minutes for it to turn off. Sometimes I must try like 5 times for it to boot. Is there anything I can do about it? Im just thinking I should throw it to garbage and get the S7?
Thanks
Does the same thing on a stock ROM? Possible battery problem?
audit13 said:
Does the same thing on a stock ROM? Possible battery problem?
Click to expand...
Click to collapse
I am trying to install the stock rom right now but during installation it shuts down randomly. I have tried another battery and it still does the same thing so I think the battery is not the problem.
Also wanted to say that I dropped the phone few times without any screen damage. Maybe that caused a hardware problem?
EDIT: I successfully installed the stock rom. I will let you know if it runs smooth now, thanks!
It seems that my power button has a problem, every time I press it, sometimes it opens the menu where you can select if you want to reboot/turn off/vibrate and the phone turns off.