Hi guys,
so the main Problem is, my GT-I9100 does not Boot properly, or turns off pretty fast (it somehow does boot, but it turns off while booting).
I'll try to explain step by step what i did so far.
I had a Custom Cyanogenmod 9 Rom on my Phone and it worked for like half a year now (was too lazy to update).
And suddenly it wasn't able to boot anymore as described. I thought it was the Battery so i charged it for a few hours, but still couldn't boot.
After that i tried to start into CW Recovery, wiped Cache, Wiped Dalvik -> still same problem.
Then i just let the phone on on Recovery mode until the Battery was totally empty, recharged to 100% -> still same problem.
So i thought, the rom might got crushed howsoever -> installed Original Kernel with Odin BUT the problem still occured....
That's the point where i am right now.
The Phone starts, the "Samsung Galaxy S2 GT-I9100"-Logo shows, the Boot-Logo shows up (Cyanogenmod logo showd up as well as now the Samsung Logo). On CM the Phone turned off while booting, now it always gets through the Samsung boot Logo, it initialized some apps (cause off Factory Reset) like 9/46 Apps then shuts down, after turning it on again it starts returning to initializing the apps now and again after a few initialized apps like 10/37 it shuts down again.
I kept on turning it on until all apps were initialized and now it tries to instal the initialized apps but shuts down after a short time again. And it is not able to instal a app in that short time, so i wont make any progress anymore with turning it on over and over again...
Don't really know whats wrong, already unplugged SIM. I thought about it being a Hardware Problem... But maybe it's not and you might know some way to fix it
I'll get my HTC One soon, delivery started yesterday, so it's not that much of a problem, but it's a shame 'cause i wanted to give my S2 to my brother
Hello xda!
Well, I have a problem, yesterday my phone was working great, but today when I woke up, I found my phone in the CM9 boot screen and it never pass through it. Sometime during the night I woke up and checked the time with the phone and everything was FC'ing, calendar, contacts, and many other system and non-system app were crashing, then I rebooted to fix that crazyness and here I am, stuck in the boot screen. :/
I don't know what's wrong, yesterday everything was fine! I did not fiddle with anything this night! Did I sleepwalk?
The phone is a SGS2 i9100 with CM 9.1 (and the boot animation of CM10).
So far, I tried wiping the dalvik cache, but I'm still stuck. I hope we can fix this without having to wipe everything... It was long ago since I did the last backup.
You could try a dirty flash of whatever CM9 build you're currently running without wiping. To be honest though, this probably won't work (but it won't make things 'worse'). Then try a wipe. And if none of that works, back to stock via Odin & either restore your backup or start from scratch (re-flash whatever rom/kernel you want, restore your apps & contacts, etc, etc).
But what it puzzles me is what happened tonight that the SO broke.
And the upper part of the phone, around the camera (where the main board is placed) gets extremely hot, I even left the phone 5 minutes in the refrigerator stuck at the boot screen to see if waiting long enough would do something, but it didn't.
I guess I'll try doing what you said, and if that doesn't work I'll start from scrath. Anyway I wanted to update to JB. I'll lose some pulled apps from the Play Store but... meh
Could be something hardware on the fritz, or the heat could be related to the firmware problems you're seeing. Don't put the phone in the fridge; fridges tend to be a bit moist, you don't want to expose the phone to moisture like that.
I guess you'll find out if it's hardware or not when you fix it; if the heating issue remains once you've got it running 'normally', then there might well be something hardware-related going on.
pealery ito
Deses said:
Hello xda!
Well, I have a problem, yesterday my phone was working great, but today when I woke up, I found my phone in the CM9 boot screen and it never pass through it. Sometime during the night I woke up and checked the time with the phone and everything was FC'ing, calendar, contacts, and many other system and non-system app were crashing, then I rebooted to fix that crazyness and here I am, stuck in the boot screen. :/
I don't know what's wrong, yesterday everything was fine! I did not fiddle with anything this night! Did I sleepwalk?
The phone is a SGS2 i9100 with CM 9.1 (and the boot animation of CM10).
So far, I tried wiping the dalvik cache, but I'm still stuck. I hope we can fix this without having to wipe everything... It was long ago since I did the last backup.
Click to expand...
Click to collapse
Just try to flash CM9 again without wiping data, wipe only cache partition and dalvik cache, you will not lose data.
I tried reflashing CM9.1, but it's still not working... I'm starting to get worried.
This night I will try to flash a stock rom with odin and wipe everything. And if that don't works... well, damn.
I did say it probably wouldn't work. You're getting in a tizz over nothing, to be honest. You're acting as if your phone's busted (it isn't). Go back to stock & start from there.
Man, I guess it's normal to get a little worried when your phone doesn't get through the boot if I didn't do anything to it... but I wasn't THAT desperate, I was pretty sure it was something software related. Sorry if I gave that impression. D:
I just tried to load a backup that I did back in January and the phone booted, so I guess my only option is start from scratch (and leave my phone far away from me during night).
Thanks for the help!
You are not the 1st person for things going "bump in the night",and you wont be the last.
Seems mostly to happen when cm10 is mentioned.
-------------------------------------------
maybe your an iphone expert
------------------------------------------
Hello,
I have created a simliar thread in the Nexus 5 subforum a while ago but didn't get much help or attention. My problem happended to me today again and I though maybe I crate a thread here to get more help.
I am running a Nexus 5 with everything stock 4.4.4, ART runtime, root enabled.
Some weeks ago my phone switched off automatically and when it rebooted it started to optimize my apps for dalvik. So after the crash it switched from ART to dalvik. I wiped it and installed everything fresh. On the same day it happened again. It just turned off and switched back to ART. I was running ART since I bought this phone and now it makes problems suddenly?
This morning I woke up and my phone was turned off. I switched it on and it took unusuallly long in the "google" screen and after the boot I was presented with the install wizzard. Also the phone tells me that I have not enough storage (no external storage).
Before wiping the phone completly again I first want to check how to save my files.
But does anybody know what is happening here?
EDIT: Also I have no connection to my provider anymore.
EDIT2: Tryed fo flash factory images but it keeps on failing: "FAILED (remote: flash write failure)".
Guess I have to send it to repair ... but it is rooted. Will google still take care of it?
My phone (Nexus 4) appears to be soft-bricked, and will not boot up. When I turn on the device, it appears to get part way through the boot process but it never completes, and the bootsplash just keeps spinning forever. The top of the phone where the radios/gps/etc are gets very hot during this time.
I've tried: clearing caches within TWRP, factory reset, loading a couple new ROMs, wiping all partitions and reformatting, updating TWRP. Nothing seems to help.
I'm starting to think it's a hardware problem, but I'm hoping that someone might be able to give me some ideas that I haven't tried yet. I can get into TWRP and can load ROMs.
Some background: My phone is a Nexus 4 (mako) and had Cyanogenmod 13.1 prior to the issues, which has been running fine since last year. Recently my phone was acting glitchy/slow, so I decided to clear the cache and dalvik cache a couple weeks ago. This worked great and got things working well again. When I set things up again I also decided to start using DroidWall, which was the only app on my phone using root. About a week ago I also replaced the battery inside the phone since my old battery was shot and could barely keep a charge. The new battery has been working well, and does not appear to be the part of the phone heating up when the phone is stuck booting.
An update. I found that with the Slim ROM loaded, I can run `adb logcat` while the phone is booting to see what's happening. Lineage OS does not seem to ever get far enough to be seen by adb.
When viewing the Slim logcat, there are a lot of logs generated. Within, there are some DEBUG and backtraces displayed. And, I think the phone may be stuck trying the same thing over and over again as I've seen a section appear about the camera several times.
Earlier today I opened up my phone again, and noticed some pressure contacts on the back cover of the case. I cleaned them all to make sure they were making good contact, but it hasn't helped.
Hi, I received this phone today, I updated to miui 9.6.25.0... Everything was working fine, until out of nowhere, all the applications started crashing, I thought it was a error and I restarted. However, it did not turn on the phone again, it only went into recovery, I made wipe data and it was solved, but, when reconfiguring the device, the same thing happened. Do you know about any solution?