(delete)
Dougmeister said:
I had Android 4.1.1 installed on a rooted Sprint Galaxy S3 with ClockworkMod. Someone recommended TWRP, so I installed it and used the backup feature, thinking I was completely covered if my foray into ROM flashing on the SGS3 went awry.
So I booted to TWRP, did a "Wipe Data/Factory Reset", and installed the "Blazer" ROM; didn't like it. So I TWRP'ed again, wiped it and flashed CyanogenMod 10.1. Didn't like it either. So I went back into TWRP, did the "Wipe Data/Factory Reset" again, and restored my backup.
When it finished rebooting, it was good for like 20 seconds. I left it on the "lock" screen, and the date reverted back to Dec 24th at some ungodly hour (4 am?). It wouldn't unlock. After less than a minute, it reboots. It kept doing this.
I had a hard time getting back *into* TWRP. I kept getting this weird picture of the battery (?) and the phone kept buzzing every 10 seconds or so. The battery had at least 30% charge. Eventually, by taking the battery out, I was able to get back into TWRP.
Tried it again 2 or 3 more times with the same result. This last time, I immediately got off the lock screen and let it "sit". It has been stable (no lockups or reboots) for a few minutes now.
Any idea what's going on?
(If I'm leaving out important information, I apologize. Please let me know and I'll add it.)
Click to expand...
Click to collapse
Sprint ??? this is I9300 forum .
jje
Related
Hey guys,
little frustrated here as i am having some issues. I have the ERIS running Gin tazz CM7, and when the phone is on, it runs flawlessly, but as soon as i reboot or turn the phone off, and turn it back on, i get a force close error message stating "com.android.phone" has stopped working, and pretty much makes the phone useless. I then have to wipe and re-flash the ROM and everything is fine again, until I reboot/turn phone off and boot back up.
I experimented a little last night, and put the phone in airplane mode and shut the phone off, rebooted, and turned it off of airplane mode when it was done booting, and i did not get that message. I thought i had found the cure. Rebooted again and got the same error message! I'm pulling my hair out, not sure what else to do. Has anyone heard of this issue, and if so is there a quick fix? FYI i used another ROM and it did the same thing, so i do not think it is the software. It is almost as if on the reboot it can't load the necessary "codes" to get the radios up and running again. Any feedback appreciated!
p.s i attached a screenshot to let you guys see what the error message looked like!
do you do full wipes of data and dalvik for every flash? The same issue hit me one time when I had not done wipes of both. I went back and wiped both, dalvik I just went ahead and wiped three times. Idk that three times matters but I wanted to make sure I was good to go and I know I had seen workshed post before about 3x wipe of dalvik. When I went back and wiped everything like that and re-flashed everything went back to normal for me.
The wipe of Data & Dalvik is a critical step. Like the poster above me, I've heard the "3 times" suggestion and I'm not sure why 1 versus 3 would make a difference. However, just to be safe, I have started wiping Data & Dalvik 5x each, each time I flash. It's most likely just overkill & paranoia, but hey, I've had no issues.
Some roms, depending on what are are upgrading from, may also require you to delete a folder from your sd card. For example, as Workshed states in his GSB v3.7 thread,
"If you're coming from a cm6 or 2.1 ROM, make sure you delete .android_secure folder on your sdcard before flashing."
http://forum.xda-developers.com/showpost.php?p=11178912&postcount=1
Hope this helps!
Having similar problems. Only wiped once, I'll try it a few times and see how that goes.
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.
So I have Tmobile HTC One, rooted, S-off, converted to GPE.
I got the update today, ran it. I have TWRP. It installed, then the boot animation came up, and my screen stayed on but was blank for over 5 minutes. I rebooted it, same thing. I rebooted and cleared Dalvik Cache & Cache. Same thing.
It now wouldn't stay turned off. So I left it sitting while I started looking for some info, about 15 minutes later I heard noises. Saw that my phone had come all the way up. Joyous & Happy I started looking around. Found that it removed a couple of my apps. No bigger. Then I saw weird graphical glitches at the bottom of the screen.
Got worried, tried to reboot. The screen darkened, but the reboot options never came up. I forced it to reboot, it comes up fast like its supposed too. Same thing though. Weird graphical glitches, and no reboot menu.
I'm afraid I screwed it up when I cleared the cache while it was obviously still initializing the install.
First off, any ideas?
Second, can I just rerun the OTA once its posted online?
My WiFi works better now, I love the new dialer.
Hopefully you did a nandroid backup before you run the update, if so try to restore your backup and wait till someone manage to root 4.4.3.
if you didn't create a backup, I'm afraid you have to flash GPE 4.4.2 RUU pre-rooted.
critterhart said:
So I have Tmobile HTC One, rooted, S-off, converted to GPE.
I got the update today, ran it. I have TWRP. It installed, then the boot animation came up, and my screen stayed on but was blank for over 5 minutes. I rebooted it, same thing. I rebooted and cleared Dalvik Cache & Cache. Same thing.
It now wouldn't stay turned off. So I left it sitting while I started looking for some info, about 15 minutes later I heard noises. Saw that my phone had come all the way up. Joyous & Happy I started looking around. Found that it removed a couple of my apps. No bigger. Then I saw weird graphical glitches at the bottom of the screen.
Got worried, tried to reboot. The screen darkened, but the reboot options never came up. I forced it to reboot, it comes up fast like its supposed too. Same thing though. Weird graphical glitches, and no reboot menu.
I'm afraid I screwed it up when I cleared the cache while it was obviously still initializing the install.
First off, any ideas?
Second, can I just rerun the OTA once its posted online?
My WiFi works better now, I love the new dialer.
Click to expand...
Click to collapse
If you can boot into bootloader/FASTBOOT USB and run fastboot getvar all to see where you are in the install. The OTA will not run properly if you do not have the stock recovery and stock rom in place OTA will have two version numbers in the title, the first is the new version and the second is the old version this one must match for the OTA to run. If your getvar is like it was previously, then try to install a stock recovery then the OTA. If you have a backup as @aaswar states then run it first, then the stock recovery.
My Note 2 is rooted/bootloader unlocked with CASUAL. Running Beans stock 4.3 ROM. The phone worked GREAT for over a year but a few months ago, apps began to close randomly and the phone would reboot frequently.
So I decided to wipe the phone and start over. I have done this twice and the issue persists. The last time I wiped the phone, I flashed the stock recovery and wiped it multiple times (wipe cache & factory reset).
Then I reflashed the firmware, the ROM and the radio.
However, the phone is still rebooting several times a day.
I have tried 4 different batteries and it doesn't make a difference.
Any ideas? Is there a way to determine if there is something physically wrong with the phone, i.e. bad memory or processor?
Thanks
Rootabaga said:
My Note 2 is rooted/bootloader unlocked with CASUAL. Running Beans stock 4.3 ROM. The phone worked GREAT for over a year but a few months ago, apps began to close randomly and the phone would reboot frequently.
So I decided to wipe the phone and start over. I have done this twice and the issue persists. The last time I wiped the phone, I flashed the stock recovery and wiped it multiple times (wipe cache & factory reset).
Then I reflashed the firmware, the ROM and the radio.
However, the phone is still rebooting several times a day.
I have tried 4 different batteries and it doesn't make a difference.
Any ideas? Is there a way to determine if there is something physically wrong with the phone, i.e. bad memory or processor?
Thanks
Click to expand...
Click to collapse
Odin back to stock and see if that helps. If it doesn't then it's hardware related.
i am having the same issues, is there a fix?