WOW, nothing but problems........ - T-Mobile Samsung Galaxy S II SGH-T989

So, I was running Cyankang 4.3 ROM, and everything was good. I tried the new nightly with PDROID, and everything was fine, except I was having some issues with some apps. So I went to the nightly W/O PDroid, and now everytime I try to reboot, it just hangs at the black screen, I have to restore to a previous version (9/18) that I had on it. But that's not all, even after I restore to that version, if I need to reboot, it gets stuck as well, and I have to restore again in order to get it to boot.
I'm about to go back to stock at this point, it's pissing me off.

Related

Crazy and extremely anooying reboots

I have a dinc running skyraider 3.3final and each time i reboot, i get the setup when i unlock
i tried skyraider, virtuous, and cyanogenmod and they all took me to setup after reboot and uninstalled all apps
~~~~please help~~~~
this happens even when you don't wipe?
I haven't tried not wiping
but everytime i do a full install and wipe everything, i still get the problem when i reboot. I've been going all day and everything has been working fine, i just don't want to reboot because i won't have anything
any suggestions
I had this happen to me also not too long ago, never tracked down what was causing it. No matter what ROM i flashed, or nandroid restored, I would end up with the setup screen and a multitude of FC's.
I ended up just returning to stock with the official RUU, and re-rooting. Haven't had an issue since. Make sure you back EVERYTHING up though.

[Q] Suddenly Boot Loop

So I was just sitting at the computer, not even using my phone, and I see it restart. However, upon it trying to start back up it is going through the Samsung animation, then the Sprint 4g animation, then it pops back to the samsung one again, and again, and again, forever. I have had the same rom, Blazer ROM [12/9/12] [v2.0] since about mid-December, and have made no changes to my phone other than a theme in late december.
So things have been working fine all the past few months, and just today this happens out of nowhere. I haven't even installed any new apps in the past two weeks, so I'm not sure what is up, I have tried to re-install the Blazer Rom after wiping dalvik and cache, but it still gets stuck in this loop. I know I could try to factory wipe, but don't want to lose my text data if possible. Does anyone have anything they can suggest? Thank you.
Ok, make a backup as is. Then clear everything, multiple times
Redownload Blazer (verify md5sum) and flash again. If it boots up you can advanced restore your data
Ah, thank you, I was going to do this and then turns out the backup didn't work properly, and I lost everything anyhow. Thanks for your help, guess it's time to start all over again with the phone as fresh.

[Q]

Hi, I flashed CM 10.2 on my Galaxy S4, and I used titanium backup to restore all my apps, only apps I didn't choose was TouchWiz and the TouchWiz simpler one. And it said I needed to reboot my device for the changes to apply, so I did that. When I rebooted it said everything stopped working. Even the core thing. Screen went black. Then I took out the battery and when I tried to go to my custom recovery, it just skipped the recovery screen and booted into cm again and same thing happened. Everything just stopped working. Help please. Also I am able to get into download mode. I just don't know how to recover from this. I am running 4.3.1 cm nightly, well I was. I don't know if I could count it was 4.3
if you are able to access the download mode then flash a stock rom. then root your device again.

N7100 keeps freezing

I've recently started having trouble with my N7100 freezing/locking up.
I bought it shortly after launch, so it's a little over 1 1/2 years old. I had flashed one of the first rooted 4.1.2 firmware that was available, and never bothered updating because it was stable and got great battery life and I didn't feel like dealing with ROM stuff. But recently with the official 4.4.2, I decided to finally update, and decided on trying out DN3. So I flashed the latest TWRP, did the usual backing every thing up, flashed the MJ5 bootloader, and flashed it. It kept bootlooping, so I figured something went wrong, so I restored my 4.1.2 backup. This was where the freezing began. It was to the point where I couldn't use it. Tried rebooting a few times, but every time it would freeze as soon as it booted or shortly after. I assumed something just went wrong with the backup, so I tried flashing DN3 again. This time it booted successfully, but would occasionally freeze, most often when loading an app, but sometimes just randomly. After a couple days it seemed to subside. Then I decided to try out OmniRom. Same thing -- it would occasionally freeze up, then after a while would be fine. (Note: these were both clean installs.) Seems like every time I'd flash an updated version of Omni, the freezing issue would flare back up. Just now, I flashed the latest homemade build, and the freezing was really bad again, to the point where I can't even use it. Sometimes it'll freeze the instant it finishes booting, sometimes it'll freeze a few seconds after, sometimes it'll finish booting and will be fine until I load an app, then would freeze, and sometimes it would be fine for a couple minutes and the just freeze randomly. What's odd about it is that the screen is still responding to touch. Every thing's locked up, but when I touch the screen, the capacitive buttons light up as though it's still working fine, but nothing else works. I've even had a couple times where I let it sit for about 10 minutes and then it started responding again.
What's really frustrating is that I can't find a common cause here.Started on 4.1.2 (which had never had any issues beforehand), continues on a clean install of DN3, and continues on a clean install of OmniRom. Disabling Xposed and removing my SD card had no effect. It boots fine into recovery and download modes.
Does anyone know what the issue could be here?
EDIT: And now I've done a complete wipe, again, and reflashed DN3, again, and it appears to be working fine. Go figure.
It's not suddenly death?
see this: http://forum.xda-developers.com/showthread.php?t=2093599
sorry my english

[Q] S3 Turning Off on its Own

I've been regularly running cyanogenmod 11 on my Bell S3 without many issues. Last going off, I believe I was running either M11 or M12 of CM11, and all was well. Then, curiosity got the best of me, and I slapped on CyanideL Lollipop beta, and while that ran pretty damn well for me for about a month, I reverted back to CM11 a few days ago due to some minor bugs and annoyances (mostly camera). Anyways, since reverting back to CM11 M12, my phone has been randomly shutting off, not rebooting, just off. It has happened while it's in my pocket not really in use, or it can happen while I'm going to check my text messages.
Thinking this was an issue maybe with M12, I updated to the latest nightly, but nope, its still the same. Some of the times that its happened in my hands, I've seen the Power Button menu pop up, and then disappear. A few seconds later, boom, off she goes. It always powers up again when I power it back on, but I would like to try to get to the bottom of what is causing this, as it is being very annoying for me.
The question is, what can I do to try and nail down this issue? When flashing back to CM11, I did the full wipe, then dalvik/cache after the flash. Is there something that happens when you go from 5.0 back to 4.4 that may cause this?
This is possibly related. I tried out an unofficial cyanogemmod 12 rom on my AT&T S3 for a while, but decided to revert due to camera not working. So I installed S3Rx ROM on the phone and had some issues. The phone would get stuck on the loading screen and never get past that. I did the standard data/factory reset, cache wipe and dalvik wipe before installing S3Rx back, but no luck. The only way I could get it to install correctly was by formatting /system, /cache, /data and /data/media in ClockworkMod recovery. But be aware that you will lose all personal data when you do that so be sure to backup.
Alright, I'll backup what I need to, and do a full wipe as you suggested. I'm pretty sure I did that when I downgraded to begin with, but no hurt in trying it again.
You could flash back to completely stock 4.4.2 using firmware from sammobile.com, depending on the bootloader on your phone.
audit13 said:
You could flash back to completely stock 4.4.2 using firmware from sammobile.com, depending on the bootloader on your phone.
Click to expand...
Click to collapse
If I do go back to Stock 4.4.2, would I be able to re-root again? Its been a couple of years since I had to mess with stock, so I don't know what has changed.
I've tried a few different things here, completely wiping everything, installing a 4.4.4 kernel, installing CM11 from scratch, restoring from TWRP, etc etc. Still having the issue.
Last thing I'll try before going to stock is to try going back to lollipop.
Update: I'm starting to think that this is just a coincidental hardware issue. It seems to have something to do with my power button, perhaps there's something stuck in it that's cause the button to be pressed. Right before it shuts off, the power menu pops up for a split second once or twice, then the phone becomes unresponsive for a second, then its off. Certainly sounds hardware related. Just attempted lollipop again, and same result.
I think you are correct in your assessment. Open up the phone and see if you can find anything that looks odd.

Categories

Resources