Related
Ok, I know some other people posted about black screen but all the other threads seem to be about it happening after a call.
Mine happens when the phone been sitting for a while with the screen off (and it's not all the times) it seems more prone to it if the screen been off for longer times.
I tried two different roms with two different kernels both have the cpu idle speed setup at 384 or more. As soon as I flash they seem to work ok but after a day or so the freaking black screen comes back. I also have pimp my rom installed with the "no black-screen after a call" tweak ticked.
I've went through the process of unrooting going all the way back to stock and start from the beginning all the way from unlocking the bootloader to S-off.
Downloaded fresh copies of the roms zip files
I don't think it's any of the apps since this does not start right away it takes a day or so after everthing been runing (but I might be wrong).
Obviously it's not the rom or the kernel since it does it with two different ones, what else is there that can be messing with my phone???
It's driving me crazy!!!!
Can it be hardware related????
I'm lost with this, and started thinking on a new phone already but I can't buy it until mid 2013 so I don't want to give up yet (actually can't).
This been working just fine up until a month ago or so, it's just now that the black screen started harrasing me.
Edit: It just happened again and since I could not get the screen up, I decided to pull the batt and when I turned the phone on again I got the vibration but the screen didn't light up during booting at all until I pressed the button few times.
Could my screen be dying?
ferincr said:
Ok, I know some other people posted about black screen but all the other threads seem to be about it happening after a call.
Mine happens when the phone been sitting for a while with the screen off (and it's not all the times) it seems more prone to it if the screen been off for longer times.
I tried two different roms with two different kernels both have the cpu idle speed setup at 384 or more. As soon as I flash they seem to work ok but after a day or so the freaking black screen comes back. I also have pimp my rom installed with the "no black-screen after a call" tweak ticked.
I've went through the process of unrooting going all the way back to stock and start from the beginning all the way from unlocking the bootloader to S-off.
Downloaded fresh copies of the roms zip files
I don't think it's any of the apps since this does not start right away it takes a day or so after everthing been runing (but I might be wrong).
Obviously it's not the rom or the kernel since it does it with two different ones, what else is there that can be messing with my phone???
It's driving me crazy!!!!
Can it be hardware related????
I'm lost with this, and started thinking on a new phone already but I can't buy it until mid 2013 so I don't want to give up yet (actually can't).
This been working just fine up until a month ago or so, it's just now that the black screen started harrasing me.
Edit: It just happened again and since I could not get the screen up, I decided to pull the batt and when I turned the phone on again I got the vibration but the screen didn't light up during booting at all until I pressed the button few times.
Could my screen be dying?
Click to expand...
Click to collapse
have you ever considered its the tweaks your doing to your phone.. have you tried just flashing the rom and running it without doing the tweaks... not every phones hardware is identical so not all tweaks might work... ive flashed a rom recently that experienced some boot loops after doing some tweaks to the rom, and now im running that rom flawlessly without any tweaks...
---------- Post added at 12:01 AM ---------- Previous post was at 12:00 AM ----------
you might also want to try the rom with the default kernel that comes with the phone not faux which i'm assuming your using
To be honest, no I haven't thought of that.
I just re flashed everthing, if the problem starts again I'll remove all the tweaks.
But the thing is the phone was working well and one day without changing anything it started with this. But I'll try removing the tweaks if this persist
Thanks,
Nope, it wasn't the tweaks.
Fresh flash, no tweaks and I still have to press the on button many times to get the screen to turn on
which rom are you using again?
I'm on NRG blue but I tried the Bulletproof for a while and it did it too that's why I'm thinking that is not rom related. It has to be something deeper than the rom.
Phone was working great until last month that I travelled abroad.
As soon as I got to the country I was visiting I put a local sim card and it took me a while to be able to boot, to the point that I had to restore from a backup.
Then during the time I was there I had several random reboots (like once or twice a day).
When I came back I swapped the sim again and no more reboots but after a week or so I started with this black screen problem, it was really bad to the point when sometimes I needed to pull the battery off to see if that helped and the rom got really screwed (I think sense got screwed because the screens were doing weird things). So I reflashed, it fixed all the weird things but not the black screen.
Now it's not as bad (I only need to press 3 or 4 times the button) and it's not alway, only if the screen been off for a while but my previous experiencest tells me that it will get worse in few days time...
okay i have a few suggestions.. do you do a full wipe when you flash a rom? wipe data/factory then format system then wipe cache partition's then wipe delvik cache.. and you should try going back to stock completely then trying a different rom and see.. its about testing all possibilities before coming to the conclusion your phone is damaged somehow
yes I always do a full wipe and/or the 4ext wipe and clear dalvik and cache. Not sure about the factory reset since I wasn't sure where that would take me.
you should try going back to stock completely
Click to expand...
Click to collapse
Do you mean relock, S-ON and goall the way to GB? or to ICS T-mous stock??? I did go to ICS (this one) http://d-h.st/3VD but I can do it again (I can alway use some practice with these procedures...)
I
you dont have to S-ON again i mean Stock ICS from your carrier.. and stock Ruu's are located in my signature if that link is one you got from there go right ahead... and try and flash back to stock, if you need instructions let me know
Ninjistix said:
you dont have to S-ON again i mean Stock ICS from your carrier.. and stock Ruu's are located in my signature if that link is one you got from there go right ahead... and try and flash back to stock, if you need instructions let me know
Click to expand...
Click to collapse
I did that yesterday and yes the ruu Iused is the same as the one listed there as most recent.
I just found an interesting discusion on the faux kernel thread about a problem, with the earlier version (which is the one I was running when the whole thing started) and that happened to me before this black screen.
This is the thread http://forum.xda-developers.com/showthread.php?t=1359951&page=232 and it's mentioned in the quote on post #2316 and ahead.
I PM'd AJ to see if he thinks this could be related since in one of his posts he said something like reverting to stock won't help (for some reason)
but overall from what i just read... the issue seems to be related to the faux kernel.. i only flashed it once but ii didnt do any tweaks,, i mostly use the stock kernel that comes with most of the rom's i flashed... here's what to try... in 4ext wipe all partitions except sd card, then wipe both sd card partitions internal and external.. toggle usb storage and flash this super wipe script in recovery.. then flash a different rom and don't flash faux.. test the rom out to see if your problem occurs again.. or flash the super wipe then place the ruu on the SD card then attempt to flash back to stock
Try this thread and see if it will help your situation.
http://forum.xda-developers.com/showthread.php?t=2070438
Double0EK said:
Try this thread and see if it will help your situation.
http://forum.xda-developers.com/showthread.php?t=2070438
Click to expand...
Click to collapse
I'll try it.
Thanks,
Tried that and didn't help, but thanks for the suggestion.
What I noticed today is that since Icouldn't get the screen on no matter how many times I pressed the darn button I pulle dhte batt out and then rebooted the phone to see if that helped and even though I got the little vibration confirmation when the phone boots up there was no white HTC splash screen or bootanimation whasoever, anyway since I could still not get the screen on I tried the same thing a few time and then once I finally managed to the the screen on I said int the bottom left corner SAFE MODE (never seen that one before). I'm running Bulletproof reloaded now.
Oh and the batt was kind of low (may be 20%).
Wow!!!! I do own a very messed up phone!!!
Today this piece of crap threw a total temper tantrum.
Would nos turn the screen on no matter what. I removed the batt and not even rebooting to the point that when I finally got it to boot it had an internal SD error. It didn't allow me to format, wipe or partition it from bootloader or recovery.
Now I'm at home so I flashed stock RUU (again) and it seems like its running one more time but I was really close to throw it over the cliff where I was Flying my RC gliders.
We'll see if I can make it last a bit longer...
so its working once again, cuz you said you flashed back the stock ruu right?
Yes,it's alive (will for how long this time). I flashed stock a couple of times , I unlocked once again, flashed 4ext, flashed JP hboot, superSU, NRG rom, supersu again (since IO wasn't sure in which order I should have done this) flash rom 2nd time, flashed Faux's v 24 (twice) and Downloaded most of the apps clean from Gplay.
I'm getting a lot of practice with this, who knows, may be one day I become good at it
its good your practicing now, but don't forget to do backups before you flash anything to your phone, this this way you'll have a stable install to restore back to incase anything goes wrong again
I been doing more tests and yesterday I run it on stock most of the day with no apparent issues, then I restored the NRG rom from a backup and still no issues so I started to think it was something I messed up flashing the JB Hboot, I moved to a bulletproof rom and decided to do another test.
I sat on the phone as to block signal and the issue came back.
Now I'll try the same with NRG, yep it seems like it's when the phone loses signal the screenwon't come back afterwards.
I'll try the same in stock rom next...
Yes, it did it in stock too but not so bad, it seems like after few attempts the screen worked againgvs. on bulletproof didn't
Ok, I found this in some other thread...
[QUOTE8. Black Screen - Phone will not wake-up
I'm accidentally find out and solved the problem of Black Screen during in-coming call (BulletProof 2.2.0). By replacing the service.jar from the previous version (BulletProof 2.1.0) with the intention to get rid of the CRT file in my system, by doing this I am also discovered that the black screen problem is gone. However, this problem can be easier solved by simply dis-able the screen-on/off animation setting instead of replacing the service.jar with the one from previous build which doesn't have CRT.
It's worth to be note that during my old days with the HTC HD2 running Nandroid I've encountering similar problem of black screen when waking up the phone and it was caused by the CRT as well. This, at least happened to me with more than 3 Rom, including the famous AmeriCanAndroid, HyperDroid and Tytung's ...
So if you are experiences Black Screen problem, please check to see if you did flashed the CRT and/or enable it? ][/QUOTE]
Can somebody tell me to how do I check this?
Thanks,
My pocket felt hot, so I pulled out my phone and saw that it kept rebooting itself. It just shows the initial Samsung splash for maybe a second or two, then loops again. I can get into Recovery and Download modes fine. I tried wiping the cache, factory reset, restoring a cwm backup. No luck so far. I've been using the CM9 rom for months. I haven't flashed or changed anything in months, I haven't even installed new apps in a while. Before this happened, it said I had no signal, so I had to restore my EFS(which I've had to do several times since I got the phone, mostly when I was switching back and forth from CM9 and stock to see which I prefer). After going into and out of airplane mode to reset the antenna, the signal and all worked fine. I let the phone cool down to make sure it wasn't just rebooting due to heat, but that didn't change anything. I've been searching here and google for anyone else with an identical issue, but I've failed so far. Everyone else seems to get to the home screen or just having random reboots during use.
Just to clarify, my question is: How can I fix my phone? Is there any other information I can give that would help?
I have the international i9300. I also tried removing the SD card and SIM card, since one thread concerning a different kind of rebooting issue reported success with that. Nope.
Try to reflash a stock rom on Odin
Is that different from restoring the original rom with CWM? I did that already. I don't have or know how to use Odin, but I'll download it and figure it out if that's the next step.
Solution?
Ok, I never didn't have to figure out Odin. I fixed it by wiping dalvik, factory resetting, restoring the stock rom, wiping it all again, rebooting into stock(it worked), then restoring back to the backup I made after the crash. Some of these steps might not be crucial, but at worst you waste a few minutes to make sure it works right again. Hopefully it'll help others with similar problems.
When I flashed 7/18 version of tweaked vzw remix I stated getting random shutdowns not reboots ( i pull my phone out and screen won't turn on, hold down power and it boots up fine and I have no isseus). I was getting atleast 3-4 of those a day. The new release was on its way so I wasn't worried, figured might be a bad download or kernel issue. the next release came out and I flashed it along with pbj kernel and same thing. After a few days they decreased and then hadn't had any for a week or so.
Today I went back to clean rom 3.5 and I started getting them again.
Anyone have any ideas what could be causing this? The only new app I have downloaded recently is the game dots. Neither time have I restored any data from tibu (I have been to lazy to do it)
any help is appreciated.
Have you tried going back to stock with odin and starting from scratch?
droidstyle said:
Have you tried going back to stock with odin and starting from scratch?
Click to expand...
Click to collapse
No I have not tried that. I just got the phone back in July, samsung had to replace cdma radio so it was all stock then. During the times I've had issues,there was a day I was on beans build 21 and cant remember the shut down issues happening that day. If it doesn't get better the next few days may try using Odin then rooting and unlocking it again.
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?
had been trying roms for months now, and 2 weeks ago just starting bootlooping. was running carbon rom when the bootloop started. changed to padawan v2, bootloop went away for a few days and then came back. thought it was power button but when im in cwm it doesnt bootloop.
even all my backups they bootloop. today i went back to stock and using odin and reboots after the att logo.
is my phone done for? thanks
Try an emergency recovery with kies.
fixed it!
i would try it but keeps rebooting. would reboot within 1 minute.
so it turns out it was my radio, even the one in the stock rom would be no good.
i had to flash padawan twice so i would reboot much less frequent, i know why but it worked. then i downloaded a different radio version and seems to be working great. no more reboots after a few days, and i still get 4g on simple mobile.
i dont know how the radio was messing with the reboot but good thing it stopped, was about to give up on my phone.
ufuknut said:
i would try it but keeps rebooting. would reboot within 1 minute.
so it turns out it was my radio, even the one in the stock rom would be no good.
i had to flash padawan twice so i would reboot much less frequent, i know why but it worked. then i downloaded a different radio version and seems to be working great. no more reboots after a few days, and i still get 4g on simple mobile.
i dont know how the radio was messing with the reboot but good thing it stopped, was about to give up on my phone.
Click to expand...
Click to collapse
Hi, I wanted to know what radio version you flashed, because I'm getting the exact same error but none of the radios works for me, I'm also using padawan because of what you said.